JPH07230516A - Sales data reusing system in order-receiving and ordering system - Google Patents

Abstract

PURPOSE:To efficiently prepare an estimate sheet, a statement of delivery or a bill by retrieving respective data from an order-receiving side recorder by using an order-receiving side customer identification(ID) code as a key and transmitting a data group to an ordering side. CONSTITUTION:When an operator instructs retrieval based on a retrieving key, an order-receiving side management terminal 1 executes retrieval. In this case, the terminal 1 uses an inputted user ID code as 'customer ID code as a retrieval key'. When an ordering side operator issues a command for transmitting a retrieved result, the terminal 1 transmits a retrieved result to an ordering side management terminal 2. The ordering side operator loads clown the transmitted data to a hard disk or the like in the terminal 2. In this case, parts data inputted from the ordering side (wholesaler for parts) as its own sales data can be reused for preparing a work instruction, an estimate sheet, a statement of delivery, or a bill by the ordering side (repairing plant).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an ordering / ordering system for automobile parts and the like, and more particularly to a sales data reusing system in the ordering / ordering system in which the ordering side can reuse the sales data input by the ordering side.

[0002]

2. Description of the Related Art Conventionally, an order receiving / ordering system has been constructed between a manufacturer of goods and a retailer, or between a wholesaler and a retailer. For example, in an automobile repair shop (order receiving side), an automobile part manufactured by an automobile manufacturer (manufacturer) is ordered from a parts wholesaler. On the wholesaler side (ordered side) that has received the order, after ordering and ordering it from the manufacturer, the parts are delivered to the repair shop (ordering side) together with their own delivery note and invoice.

[0003]

By the way, in the repair shop (ordering side) thus receiving the delivery of the parts from the wholesaler, after (or before) the repair such as the replacement of the necessary parts, Issue invoices / invoices (or quotes) to end users. In this case, it is necessary to enter the details such as the price of parts required for repair on the delivery note / invoice (or quotation) issued by the repair shop operator, but those parts details are requested by the operator of the ordering side. I am manually inputting with the keyboard while referring to the delivery note. However, the ordering side manually inputs the product code (part code) such as the model, product number, and product name of the part to be replaced for such repair, the price (purchased value or suggested retail price), and the quantity. Has a problem that it is extremely complicated and inefficient.

The present invention has been made in view of the above problems of the prior art, and is an ordering / placement system constructed between a manufacturer of goods and a retailer or between a wholesaler and a retailer. It is an object of the present invention to provide a sales data reuse system in an ordering / ordering system, which can streamline the preparation of an estimate, a delivery note, or an invoice issued from the ordering side to the end user.

[0005]

[Means for Solving the Problems] In the sales data reuse system of the ordering / ordering system of the present invention for achieving the above object, the ordering side estimates the customer identification code for identifying the ordering side and the ordering side. Or, an input means for inputting each product data such as a product code for specifying a product to be delivered, a sales unit price of the product, and the quantity of the product,
A recording device for recording each of these product data items in association with the customer identification code, a search means for searching each product data item recorded in the recording device using the customer identification code as a key, and the searched product data. The ordering side includes a reading means for reading out the product data output from the output means, and a quote for the user based on the read product data. It is characterized in that it further comprises a detail creating means for creating details such as delivery details or billing details.

In the sales data reuse system in the ordering / ordering system of the present invention, each data is retrieved from the ordering side recording device by using the ordering side customer identification code as a key by access from the ordering side, The retrieved data group is transmitted from the ordering side to the ordering side.

Further, in the sales data reusing system in the ordering / ordering system of the present invention, the recording device further uses the customer identification code and the date of quotation / delivery or billing from the order receiving side as the product data. The data is stored in association with two pieces of data, and the search means is
It is desirable that each item data is searched using at least two of the customer identification code and the date of the estimate / delivery or bill from the order receiving side as a key.

In the sales data reuse system of the ordering / ordering system of the present invention, the order receiving side is a wholesaler, and the input means on the order receiving side is an EOS (Electric Orderin) constructed between the manufacturer and the order receiving side.
g System), the "data of the product to be delivered" (product) which is transmitted from the manufacturer to the ordering side based on the customer identification data which is previously added to the product data when the ordering side orders the product from the manufacturer. It is preferable that ordering data such as a code and the quantity of products, and additional data such as a manufacturer's suggested retail price newly added by the manufacturer) be written in the recording device in association with the customer identification code.

Further, in the sales data reusing system in the ordering / ordering system of the present invention, it is preferable that the unit price of the commodity inputted from the input means is a retail price desired by the manufacturer for the end user.

Further, according to the present invention, an EOS (Electric Orc) constructed between a manufacturer and its user is constructed.
In the sales data reuse system in the ordering / ordering system based on the Deriving System, on the user side, in the ordering data transmitted from the user side to the manufacturer, the user side management data (customer identification data) associated with each ordering product data is included. Etc.) and the "data of the product to be delivered" sent from the manufacturer to the user (order data such as product code and product quantity, and additional data such as the manufacturer's suggested retail price newly added by the manufacturer). ) Is associated with the user-side management data (customer identification data, etc.), and is written in its own recording device.

[0011]

As described above, in the sales data reuse system in the ordering / ordering system according to the present invention, the order receiving side receives the data of the products to be delivered (product code, product unit price, purchase unit price,
Record the product quantity) in the storage device. The ordering side uses the reading means to read only the merchandise data relating to itself, which is retrieved from the recorded merchandise data by the retrieval means using the customer identification code as a key. Further, the ordering side can use the read product data as it is for creating the details such as a delivery note or invoice issued to the end user by the statement creating means. That is, the ordering side can reuse the product data input by the ordering side (sales data of the ordering side) to create the details of the delivery note or the invoice. Therefore, on the ordering side, it is not necessary to individually input each of the product data as in the conventional case, and the work efficiency for issuing a delivery note or a bill can be greatly improved.

Further, in the sales data reusing system in the ordering / ordering system of the present invention, the ordering side accesses the product data group retrieved from the memory device of the ordering side by using his / her own customer identification code as a key. The data can be sent by the sending means, and the data can be used as it is for preparing the details of the invoice or invoice. Therefore, it becomes extremely easy and efficient to import the sales data input by the ordering side into its own computer for the ordering side to reuse.

Further, in the sales data reuse system in the ordering / ordering system of the present invention, the ordering side uses the retrieval means as a key with the customer identification code and the date of the quotation / delivery or billing from the ordering side. , You can search product data. Therefore, the ordering party searches only the detailed data (ordering side sales data) in the quotation / delivery / billing from the ordering party within a predetermined period, such as from what day of the year to what day of the year. Since it can be used, the convenience of reusing the sales data of the order receiving side on the ordering side is greatly improved.

In the sales data reuse system of the ordering / ordering system of the present invention, the order receiving side is a wholesaler, and the order receiving side input means is an EOS (Electric Ordering) constructed between the manufacturer and the order receiving side.
In the system), digital data indicating the product code, the product unit price, and the product quantity transmitted from the manufacturer to the order receiving side is associated with the customer identification code and is captured in the recording device. Therefore, the ordering side
The delivery / billing data (sales data) of the manufacturer sent from the manufacturer can be used as it is, so that the ordering side avoids the complexity of manually entering each of the above-mentioned product data with a keyboard. become.

Further, in the sales data reusing system in the ordering / ordering system of the present invention, the unit price entered from the input means is the desired retail price for the end user set by the manufacturer, so that the ordering side The product unit price (including the suggested retail price) can be used as it is for the delivery details and billing details for the end user.

Further, according to the present invention, an EOS (Electric Orc) constructed between a manufacturer and its user is established.
In the sales data reuse system in the ordering / ordering system based on the Deriving System), when the user side sends the order data from the user side to the manufacturer, not only each order item data but also the order item data is included in the order data. User side management data (customer identification data, etc.) is also transmitted in association with each product data. After the order is placed, when the manufacturer sends "data on the product to be delivered" (product order data such as product code and product quantity and additional data such as the manufacturer's suggested retail price newly added by the manufacturer) to the user, The user side management code is also transmitted. On the user side, each item data transmitted from the manufacturer is associated with the user side management data (customer identification data, etc.) and written in its own recording device.
This allows the user to incorporate the ordered product data sent from the manufacturer and the data added to it (the manufacturer's suggested retail price, etc.) into their own database as it is, and incorporate this data as it is. It can be used to create details such as invoices, invoices, and quotations.

[0017]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to illustrated embodiments. FIG. 1 is a schematic diagram showing a sales data reuse system in an ordering / ordering system constructed between an automobile parts wholesaler (ordering side) and an automobile repair shop (ordering side) according to an embodiment of the present invention. It is a block diagram. In FIG. 1, reference numeral 1 is a sales management terminal on the ordering side (wholesale), and reference numeral 2
Is an order management terminal on the ordering side (repair shop), and these terminals 1 and 2 are connected to each other via modems 3 and 4 and communication lines.

On the hard disk of the sales management terminal 1 on the order receiving side, sales data, quotation data, and purchase data manually input by the operator on the order receiving side are used as a sales file, a sales statement file, and a purchase file. It is recorded. Sales data, quotation data, and purchase data manually input from these keyboards include the product number, product name, product name code, manufacturer's recommended standard retail price, user purchase price (customer order It includes various product data such as the purchase price on the side and quantity. In addition to the product data described above, the sales data, quotation data, and purchase data that are manually input to the hard disk from this keyboard include the customer (repair shop).
Customer management code such as name / customer identification code, order slip number / order slip number / estimate date / delivery date / billing date / vehicle model / sales (estimate) described in the customer's order slip
Various transaction data such as the person in charge code, shipping time, and return flag are also included. Here, the return flag in the transaction data is for indicating whether or not the merchandise of the record has been returned up to the present time and the number of cases when the merchandise has been returned.

In this embodiment, the operator on the order receiving side manually inputs each of the above-mentioned data by referring to the order slip from the ordering side and the parts price list from the automobile manufacturer. Further, in the present embodiment, when each of the above data is stored in the hard disk, each of the above data is stored as a database file associated with each other. Therefore, in the present embodiment, the above-mentioned respective data can be searched with each other using other data as a key.

Next, on the hard disk of the management terminal 2 on the ordering side, sales data and quotation data manually input by the operator on the ordering side using the keyboard are stored as a database file. In addition, sales data, quotation data, and purchase data transferred from the ordering side sales management terminal 1 through the modem and the communication line are also input to the ordering side database file. Here, the sales / estimation / purchase data transferred from the ordering side to the ordering side includes, for example, a slip (SEQ) number, a sales date,
Delivery date, estimated date, slip classification, product number, product name, product name code, manufacturer's suggested standard retail price (L /
P), user (ordering side) purchase price (partition price), quantity, sales person code, estimate person code, shipping time,
There is a return flag, etc. On the order receiving side, a collection of each of these pieces of data is transmitted as one record from the sales estimate detail file on the order receiving side to the order receiving side. The ordering side can download these transmitted data to the hard disk of its own terminal 2 and use them. In each of the product data, the manufacturer's suggested retail price may not be entered on the order receiving side, but in that case, it is recorded as 0 yen.

Next, the quotation details / delivery details /
The flow of the process of creating the sales details or the work instruction will be described based on the flowchart of FIG. FIG. 2 shows a case where the ordering side prepares a work order for an automobile repair requested by an end user, or the ordering side prepares an estimate statement / delivery statement / invoice statement for repair to the end user. In this case, the operation of this embodiment will be described.
When creating these details, the operator on the ordering side first inputs the sales date, delivery date, or estimated date as a search key for searching the database of the order receiving side for the product data used to create the details. (Step S
1). In this case, the operator can use, as a search key, a key that specifies a range of dates, such as "from what year, what month, what day to what year, what month, what day" (see the transmission screen in FIG. 3). Next, the operator on the ordering side accesses the database on the ordering side by computer communication (step S2). In this case, the operator inputs the user ID code and password for accessing the database.

Next, the operator gives an instruction to search by the search key input in step S1 (step S3).
Then, the management terminal 1 on the order receiving side performs a search. In this case, the management terminal 2 on the order receiving side uses the user ID code (or the one converted into a predetermined code) input at the time of access in step S2 as a "customer identification code as a search key". To do. Therefore, in the search at the management terminal 1 on the order receiving side, the customer identification code and the step S
The search is performed by using both the sales date / delivery date or the estimated date input in 1 as the search keys. And
When the operator on the ordering side issues a command to transmit the search result (step S4), the management terminal 1 on the order receiving side transmits the search result to the management terminal 2 on the ordering side. The operator on the ordering side downloads the transmitted data to the hard disk of his / her terminal 2 or the like (step S5). Note that FIG. 3 shows an example of a transmission command screen on the ordering side terminal 2.

Next, the operator on the ordering side opens the "acceptance process" on the menu screen of the terminal 2 and selects the format of the details to be created, for example, the quotation details, delivery details, billing details, work instructions, etc. To do. Here, it is assumed that the format of “work instruction / estimate / delivery note” as shown in FIG. 4 is selected. In the present embodiment, all of the above-mentioned quotation details, delivery details, billing details, and work instructions can be input in a common format of "work instruction, quotation, delivery note" shown in FIG. Therefore, at the time of printing later, it is possible to select the quotation details, delivery request details (the delivery note also serves as the invoice in this embodiment), work instructions, etc. in the "reception processing". There is. Then, the operator inputs necessary format data (not detailed data) such as a creation date, a vehicle body registration number, a customer name, a vehicle name, a vehicle body number, and a person in charge on the format screen (step S6). In addition,
In this embodiment, when the ordering side inputs the last four digits of the vehicle body registration number, the vehicle body registration number, customer name, vehicle name, and vehicle body number are automatically displayed. In the format of FIG. 4, the item "work Co" indicates a part code (item name code), the item "replacement part" indicates a part name and part number, and the item "unit price" indicates a manufacturer's suggested standard price. The "Cost" item indicates the ordering side (repair shop)
The purchase price is shown, the "man-hour" item shows the quantity of parts, and the "amount" item shows the billing amount calculated by multiplying the unit price and the quantity.

Next, the operator on the ordering side displays the detailed data downloaded in step S5 as a detailed screen in a window in the format screen of step S6, for example (step S7). The detailed data displayed in this window is as shown in FIG. 5, for example.

If the detail data displayed in step S7 is too large and the detail to be created contains a lot of unnecessary noise data, the operator on the ordering side uses it in step S2. You may enter another search key other than the specified date to perform an additional search. That is, the operator may input another search key, for example, a vehicle model, an order slip number, or the like to further narrow down the detailed data. Now, if the operator inputs the vehicle type as another search key (the determination in step S8 is YES).
Then, the detailed data corresponding to this vehicle type is searched, and only that data is displayed on the detailed screen (see FIG. 5) of the window of the format screen (step S9). Further, when both the necessary detailed data and the unnecessary detailed data are displayed on the detailed screen, the operator can select only the necessary detailed data by deleting the unnecessary data (step S10). ). Then, the operator pastes the necessary detailed data on the format screen of FIG. 4 (transfers the data) (step S
11). As a result, the format screen of FIG. 4 becomes as shown in FIG. 6 with the detailed data added. And finally, the operator additionally inputs detailed data of the wages such as inspection / cleaning / replacement of the parts which have not been input yet (step S1).
2) Complete work instructions / quotations / invoices as shown in FIG.

As described above, according to this embodiment,
Allows the ordering side (repair shop) to reuse the part data entered by the order receiving side (parts wholesaler) as its own sales data for creating its own work instructions, quotes, delivery notes, and invoices Therefore, the input work of the operator on the ordering side is greatly reduced. In particular, in this embodiment, since the manufacturer's suggested retail price and quantity of parts are included in the data transmitted from the order receiving side, the order receiving side immediately sends the sent data to the delivery / invoice of itself. It is very convenient because you can paste the amount to be charged.

Next, another embodiment of the present invention will be described with reference to the block diagram of FIG. 8 and the flowchart of FIG. In the other embodiment, in addition to the configuration of the embodiment described with reference to FIGS. 1 to 7 described above, an EOS (Elec) constructed between a parts wholesaler on the order receiving side and an automobile manufacturer of the manufacturer.
A configuration is added to improve the efficiency of the work of inputting product data on the order receiving side by using the tric Ordering System replenishment ordering system).

First, the configuration of another embodiment will be described. In FIG. 8, the wholesaler (the EOS user side) that is the order receiving side
Is equipped with an EOS terminal 11. This EOS terminal 11 includes a manufacturer's supplier computer 12 and a modem 1.
3 and a communication line. Data of the parts ordered from the parts wholesaler (including product number, product name, product name code, suggested retail price, quantity, etc.) is sent from the supplier computer 12 to the wholesaler via the communication line. It In addition, in this other embodiment, in addition to the product data to be ordered and the identification code of the customer, the wholesaler includes the identification code of the customer (the repair shop on the ordering side) and the own code in the data transmitted to the manufacturer. Enter your own management data such as the management code of the customer (repair shop) (for example, the slip number of the order slip issued by your customer) in the comment list (remark) as your own management code in EOS. There is. In this case, the ordered product data and the management data are associated with each other and transmitted.

After the order data is transmitted in this way, the manufacturer sends the "data of the product to be delivered" to the user side in a form associated with the user side management data. This "data of delivered product" includes, in addition to the ordered product data from the user, data newly added by the manufacturer such as the manufacturer's suggested retail price of each product. When such "delivered product data" and the user-side management data are sent to the user, the user side uses the following system to directly send the sent data to his / her own bill / invoice. It can be used to create details of delivery notes / quotations. That is, the EOS terminal 11 on the user side
Is connected to the printer 15 via a switch 14 and a printer cable (Centronics cable) 16. The EOS terminal is connected to the converter 16 via the switch 14 and a printer cable (Centronics cable) 16. This converter 16 is
The Centronics data from the OS terminal is sent to RS232
It is converted to C data and transferred to the sales management terminal 1. Inside the sales management terminal 1, necessary data (management code, product number, product name, planned wholesale price, manufacturer suggested retail price, quantity, etc.) is selected from the converted and transferred Centronics (print) data. (Wholesale purchase price etc.)
Is converted into data that can be written in the sales statement file / purchase file, and then written into the database file (sales statement / purchase statement).

As a result, the wholesaler on the user side can
Based on the product data sent from the manufacturer through S (manufacturer's suggested retail price, planned wholesale price, etc.), create invoices, invoices, and quotation statements from your company to wholesalers such as repair factories. Will be able to.

That is, in the conventional EOS, when the product data is transmitted from the manufacturer to the EOS terminal of the wholesaler, the wholesaler transfers the data to the printer 15 to make a hard copy for use. It was On the other hand, in this other embodiment, on the wholesaler side, the data transmitted to the EOS terminal is converted into RS232C data by the converter 16 (step S20 in FIG. 9), and the self (ordering side) is used. Are transferred to the sales management terminal 1. Then, the sales management terminal 1 catches the transferred data (step S21), converts the data into the data format of the sales purchase file (step S22), inputs the converted data into a file on the hard disk, and saves it (step S22). Step S23). Therefore, as described above, the operator of the wholesaler (ordering side) uses the data stored in this step S23 to create details such as a delivery bill to the ordering side (repair shop). You can

Furthermore, the wholesaler (the user side of the EOS, the order receiving side in relation to the repair shop) sends the data stored in step S23 to the ordering side (repair shop) from itself (FIG. 2). It can also be used as detailed data (recorded in a database file). Therefore, in this other embodiment, the operator of the wholesaler (ordering side) uses the conventional items such as the delivery bill from the self to the ordering side (repair factory) (particularly, the manufacturer's suggested retail price and wholesaler sales). It will not be necessary to manually enter (price etc.) with the keyboard, and the work of creating delivery bills will be greatly streamlined.

[0033]

As described above, according to the present invention,
The ordering side records the data of the products to be delivered (product code, product unit price, product quantity) in the storage device, and the ordering side stores
From the recorded product data, only the product data relating to itself can be read and used as it is for preparing the details of the invoice or bill issued by the end user. Therefore, on the ordering side, it becomes possible to avoid the complexity of manually inputting each of the above-mentioned product data one by one as in the conventional case, and the ordering side creates a delivery note, an invoice, a quotation, a work order, etc. Will be greatly improved in efficiency.

Further, according to the present invention, since the ordering side can have the storage of the ordering side send the product data group relating to itself by the access of the ordering side, the sales of the ordering side on the ordering side are possible. The convenience of using the data will be greatly improved.

Further, according to the present invention, the ordering side can search the product data by the searching means using the customer identification code and the estimate date, delivery date or billing date from the ordering side as keys. it can. Therefore, the ordering side retrieves only the detailed data (ordering side sales data) in the quotation / delivery / billing from the ordering side within a predetermined period, such as “from what year and what month to what day and what year”. Therefore, the convenience of reusing the sales data on the order receiving side on the ordering side is greatly improved.

According to the present invention, the order receiving side is a wholesaler, and the order receiving side is an EOS (El) constructed with the manufacturer.
In the electronic ordering system, the product code, the product unit price (including the manufacturer's suggested retail price, etc.) and the digital data indicating the product quantity transmitted from the manufacturer to the order receiving side are associated with the customer identification code and taken into the recording device. I am trying. Therefore, the ordering side will deliver the product from the manufacturer sent from the manufacturer.
The billing data (sales data) can be used as it is, and it is possible to avoid the complexity of the ordering party inputting each of the above-described product data as in the conventional case.

Furthermore, in the sales data reusing system in the ordering / ordering system of the present invention, the unit price input from the input means is the retail price desired by the manufacturer set by the manufacturer, so that the ordering side The product unit price (recommended retail price) can be used as it is for the delivery details and billing details for end users.

Further, according to the present invention, the desired retail price for the end user, which is set by the manufacturer, is input as the unit price of the commodity input to the database file of the recording device from the input means. Itemized delivery price (retail price) as it is to the end user
It can be used for billing statements. Further, according to the present invention, an EOS (Electric Ordering Sys) built between a manufacturer and its user.
In the sales data reuse system in the ordering / ordering system according to tem), when the user side sends order data from the user side to the manufacturer, not only each order product data but also each order data is included in the order data. User-side management data (customer identification data, etc.) is also transmitted in association with each product data.
After the order is placed, when the manufacturer sends the "data of the product to be delivered" (the product code, the product unit price, the product quantity, and other ordered product data and data added thereto) to the user, the user side The control code is also sent. On the user side, each item data transmitted from the manufacturer is associated with the user side management data (customer identification data, etc.) and written in its own recording device. This allows the user to incorporate the ordered product data sent from the manufacturer and the data added to it (such as the manufacturer's suggested retail price) into their own database as it is, and incorporate this data into their own database. It can be used to create details such as invoices, invoices, and quotations.

[Brief description of drawings]

FIG. 1 is a schematic block diagram showing a sales data reuse system in an ordering / ordering system according to an embodiment of the present invention.

FIG. 2 is a flow chart for explaining the operation of this embodiment.

FIG. 3 is a diagram showing a data transmission screen for explaining the operation of the present embodiment.

FIG. 4 is a diagram showing a format input screen for explaining the operation of the present embodiment.

FIG. 5 is a diagram showing a detailed display screen for explaining the operation of the present embodiment.

FIG. 6 is a diagram showing a screen for creating a delivery note for explaining the operation of the present embodiment.

FIG. 7 is a diagram showing a screen for creating a delivery note for explaining the operation of the present embodiment.

FIG. 8 is a schematic block diagram showing another embodiment of the present invention.

FIG. 9 is a schematic flowchart for explaining the operation of another embodiment of the present invention.

[Explanation of symbols]

 1 Sales Management Terminal on Ordering Side 2 Management Terminal on Ordering Side 3, 4, 13 Modem 11 EOS Terminal 12 Supplier Computer 14 Switching Machine 17 Converter

Claims (5)

[Claims] 1. A sales data reusing system in an order receiving / ordering system constructed between a product ordering side and an ordering side, wherein the ordering side includes at least a customer identification code for identifying the ordering side and an ordering side. Input means for inputting the product code for specifying the product to be quoted or delivered (or delivered), product sales price of the product, quantity of the product, and the like, and the input product data. A recording device that records the product in association with the customer identification code, a search unit that searches the product data recorded in the recording device using the customer identification code as a key, and outputs the searched product data as digital data. And sending means for sending the order data to the ordering side. The ordering side reads the product data output by the output means and the reading means. Taken quotation items of on the basis of the product data to the user, the delivery specification or claims, characterized in that with a, and item creation means for creating a specification such as specification, sales data reuse system in ordering system. 2. The sales data reusing system in the ordering / ordering system according to claim 1, wherein the recording device includes the customer identification code and a date of quotation / delivery or billing from an order receiving side. And records the data in association with each other, and the search means searches each item data by using at least two of the customer identification code and the date of quotation / delivery or billing from the order receiving side as a key. A sales data reuse system in an ordering / ordering system, characterized in that 3. The sales data reuse system in the ordering / ordering system according to claim 1, wherein the order receiving side is a wholesaler, and the inputting means on the order receiving side is constructed between the manufacturer and the order receiving side. EOS (Electric Ord)
eringSystem), the "data of the delivered product" (product code) transmitted from the manufacturer to the ordering side based on the customer identification data which is previously added to the product data when the ordering side orders the product from the manufacturer. ,
The sales data reusing system in the ordering / ordering system, wherein a product unit price, a product quantity, and the like) are written in the recording device in association with the customer identification code. 4. The sales data reuse system in the ordering / ordering system according to any one of claims 1 to 3, wherein in the product data input by the input means,
It includes the suggested retail price (end-point retail price) set by the manufacturer for the end user,
Sales data reuse system in ordering system. 5. An EOS (Electric Ordering Sy) constructed between a manufacturer and its user.
In the sales data reuse system in the ordering / ordering system based on the system, on the user side, the user side management data (customer identification data etc.) associated with each ordering item data is included in the ordering data transmitted from the user side to the manufacturer. And the "data of the product to be delivered" sent from the manufacturer to the user (product order data such as product code and product quantity and additional data such as the manufacturer's suggested retail price newly added by the manufacturer). And a writing means for writing in the recording device of the user in association with the user side management data (customer identification data etc.).
S (Electric Ordering System)
The sales data reuse system in the ordering system according to m).