JP2005115451A - Portal site system, order receiving/sending system, and its method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform electronic order receiving/sending by such a simple form that retail stores and end users in a distribution system are not burdened with a complicated operation. <P>SOLUTION: Devices installed in end users A, retail stores B, wholesale stores C, and makers D are mutually connected through the Internet. Each wholesale store C is equipped with a store portal site system (HPS). The HPS directly receives order data from an end user without passing the retail store, stores the received data as order receiving data, temporarily allocates the number of commodities received from the end user to the stock data in the wholesale store, and transmits data indicating the reception of the order and the delivery date information of the wholesale store to the retail store which is an order destination originally supposed by the end user. Since the stock of the wholesale store is temporarily ordered at the time of receiving the order from the end user, the delivery date of the wholesale store can be surely presented before the retail store receives the order even when the wholesale store is short of stock. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a portal site system, an ordering / ordering system, and a method in which a dealer automatically orders goods from a wholesaler. In particular, the present invention is used for ordering / ordering via a network, and is used by end users, dealers, and wholesalers. The present invention relates to a portal site system, an ordering / ordering system, and a method of a store that can smoothly exchange data between manufacturers and can reliably present delivery date / price information of a wholesale store.

  For example, a technique described in Patent Document 1 or the like is known as a conventional technique related to an order for a sales product, an ordering method and order, and an ordering system. This prior art is configured by connecting a manufacturer terminal that has accessed the order receiving system in advance, an agency terminal, and a dealer terminal managed by each agency via a network. In such a system, when the order receiving system is accessed from the dealer terminal and the input data is transmitted, the order receiving system registers the ordering data as the order receiving data, and selects the corresponding agent from the pre-registered related data. Obtain and send data indicating that an order has been placed to the terminal of the agency. After this processing, the order data is displayed on the agency terminal of the agency, and when the approval work is performed here, the order receiving system sets the status of the order data to the approval state. The order receiving system also displays the order data and status on the manufacturer's terminal so that the shipping operator can work according to the status, and when the status is in the order acceptance state, the dealership terminal approves it. Send data to the effect.

As another conventional technique, for example, a technique described in Patent Document 2 is known. This conventional technology is related to a product shipment ordering device. When the order quantity is acquired and the total order quantity is less than the inventory, an instruction is given to ship stock products for the order quantity, and the total order quantity is the inventory quantity. In the case of exceeding the direct delivery minimum amount, the product supplier instructs the product receiving party to send the product directly. In addition, when the total order quantity exceeds the inventory quantity and is less than or equal to the sum of the inventory quantity and the unordered receipt quantity, this prior art merchandise shipment ordering apparatus is equivalent to the difference between the order quantity and the inventory quantity of unreceived goods. If the total amount of orders exceeds the sum, an order for an excess of the order quantity is instructed.
JP 2002-117281 A JP-A-5-165865

  When the conventional techniques described in Patent Document 1 and Patent Document 2 described above are applied to transactions in the distribution business, they will be described next in order processing and ordering between end users, dealers, wholesalers, and manufacturers. Cause problems.

  1. In the case of the prior art described in Patent Document 2, when the sales store cannot accept all orders for the end user, the sales store places an order without confirming the delivery date of the wholesale store.

  2. If the dealer inquires the wholesaler about the delivery date in advance before placing the order, the delivery date response will be delayed if the wholesaler is short of stock.

  3. Compared with manufacturers and wholesalers, end users and dealers have a large number and are relatively small in scale, so introducing a product shipment ordering device as described in Patent Document 2 is a large cost burden. It is difficult to introduce.

  4). Assuming that the distributor in the prior art described in Patent Document 1 is an end user, the agent is a dealer, and the manufacturer is a wholesaler, when the wholesaler obtains the approval of the dealer and delivers all orders of the end user, The wholesale store needs to check the status on the terminal and manually change the number of stocks and answer the delivery date.

  5). In the system described in Patent Document 1, when the wholesale store does not participate in the system, the wholesale store has no way of knowing the order contents from the end user to the store. It is impossible to know how much an arbitrary product is ordered from the wholesale store.

  An object of the present invention is to solve the problems of the prior art as described above, and to perform electronic ordering in a form that does not impose a burden on small-scale stores and end users in the distribution industry. It is to provide a portal site system of a dealer, an order receiving / ordering system and a method.

  According to the present invention, the object is a portal site system of a store for an end user to order a product from a store, and a wholesale store where the store conducts a transaction provides the portal site system, The portal site system is connected to the terminal of the end user and the terminal of the store via a network, and the portal site system directly receives the order data of the product from the terminal of the end user, Store as order data, provisionally reserve the number of products ordered from the end user's terminal for the inventory data of the wholesale store, and place an order at the terminal of the store that the end user assumes This is achieved by transmitting data indicating that there has been and the delivery date information of the wholesale store.

  In addition, the object is an order receiving / ordering system for an end user to order a product from a store, the portal site system of a store provided by a wholesale store in which the store makes a transaction, and a terminal of the end user And the store terminal are connected via a network, and the portal site system directly receives the order data from the end user's terminal, stores this as order data, and receives the order received from the end user's terminal. Temporarily reserve the inventory data of several minutes for the inventory data of the wholesale store, as well as data indicating that the product has been ordered at the terminal of the store that the end user assumes and the delivery date information of the wholesale store. This is accomplished by sending.

  Further, the object is an order receiving / ordering method for an end user to order a product from a store, and a portal site system of a store provided by a wholesale store in which the store makes a transaction, and a terminal of the end user And the store terminal are connected via a network, and the portal site system directly receives the order data from the end user's terminal, stores this as order data, and receives the order received from the end user's terminal. Temporarily reserve the inventory data of several minutes for the inventory data of the wholesale store, as well as data indicating that the product has been ordered at the terminal of the store that the end user assumes and the delivery date information of the wholesale store. This is accomplished by sending.

  According to the present invention, it is possible to electronically accept orders and orders for merchandise to a small-scale store or end user without imposing an economical and human burden.

  DESCRIPTION OF EMBODIMENTS Embodiments of a store portal site system, an order receiving / ordering system, and a method according to the present invention will be described below in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of an order receiving / ordering system according to an embodiment of the present invention. In FIG. 1, 10 is a user management table, 20 is a store management table, 30 is a price management table, 40 is an inventory / delivery date management table, 50 is a status management table, 60 is an order management table, 70 is a product management table, 80 Is a purchase history table, 90 is an order processing apparatus, 100 is a portal site system of a dealer (hereinafter referred to as HPS), 110 is an end user, 120 is a web browser of the end user, 130 is a dealer, 140 is a dealer WEB browser, 150 is a wholesale store, 160 is a WEB browser of a wholesale store, 170 is a manufacturer, 180 is a manufacturer's terminal, and 190 is a communication line.

  The order receiving / ordering system according to the embodiment of the present invention is constructed in the HPS 100, the WEB browser 120 constructed in a PC as a terminal used by the end user 110, and the PC as a terminal used in the store 130. A web browser 140, a terminal 160 held by a wholesale store 150 that provides the HPS 100, and a terminal 180 held by a manufacturer 170 are configured to be connectable via a communication line 190 such as the Internet. The HPS 100 includes an order receiving / ordering apparatus 90 that performs ordering / ordering processing, a user management table 10, a store management table 20, a price management table 30, a stock / delivery time management table 40, a status management table 50, an order management table 60, a product. The table includes a management table 70 and a purchase history management table 80.

  FIG. 2 is a block diagram showing the configuration of the HPS 100 ordering / ordering apparatus 90. 2, 210 is a WEB server device, 220 is a mail transmission device, 230 is a manufacturer ordering device, 240 is a user / dealer authentication device, 250 is an order management device, 260 is a stock / delivery date inquiry device, and 270 is a price inquiry device. Reference numeral 280 denotes a purchase history management apparatus, 290 denotes a session area, and other reference numerals are the same as those in FIG.

  The HPS 100 ordering / ordering device 90 includes a WEB server device 210, a mail transmission device 220, a manufacturer ordering device 230, a user management table 10, a user / dealer authentication device 240 connected to the store management table 20, and a status. Order management device 250 connected to management table 50, order management table 60, product management table 70, inventory / delivery date inquiry device 260 connected to inventory / delivery date management table 40, and price connected to price management table 30 The inquiry device 270, the purchase history management device 280 connected to the purchase history management table 80, and a session area 290 are configured.

  In the above description, the WEB server apparatus 210 manages data transmission / reception on the WEB screen via a communication line, and the mail transmission apparatus 220 transmits mail to the end user / sales store. The manufacturer ordering device 230 instructs the manufacturer 170 to place an order when the inventory of the wholesale store 150 is insufficient in the provisional ordering process at the wholesale store 150. The manufacturer ordering device 230 is installed between the wholesale store 150 and the manufacturer 170, and receives the manufacturer's price and delivery date from the manufacturer 170 as a processing result of the ordering instruction. The user / store authentication device 240 determines whether the store 130 or the end user 110 has the authority to use the HPS 100.

  The order management apparatus 250 processes orders / orders received between the end user 110 and the store 130 and orders / orders received between the store 130 and the wholesale store 150. The inventory / delivery date inquiry device 260 inquires about the inventory and delivery date of the product, and the price inquiry device 270 inquires about the price of the product. The purchase history management apparatus 280 registers and acquires an order determined for each store as a purchase history. The session area 290 is a storage area for temporarily storing data acquired by each of the above-described devices and data transmitted from the store 130, the end user 110, and the manufacturer 170 for each order item from the end user. It is.

  3 is a diagram for explaining the data held in the user management table 10, FIG. 4 is a diagram for explaining the data held in the store management table 20, and FIG. 5 is the data held in the price management table 30. 6 is a diagram for explaining the data held in the inventory / delivery date management table 40, FIG. 7 is a diagram for explaining the data held in the status management table 50, and FIG. 8 is the order management table 60. 9 is a diagram for explaining data held in the history management table 80, FIG. 9 is a diagram for explaining data held in the product management table 70, FIG. With reference to these drawings, the use of each table shown in FIGS. 1 and 2 and the details of data to be held will be described.

  The user management table 10 shown in FIG. 3 is a table for managing end user information. An end user ID 310 for uniquely identifying an end user, an end user name 350, an address 360, an e-mail address 320, a password 330, an ordering process. Stores the authorized store ID 340. This data is data registered by the wholesale store 150 by providing information registered in FIG. 3 by the contracting end user from the store 130 to the wholesale store 150. This data may be registered by the store 130 from the WEB browser 140.

  The dealer management table 20 shown in FIG. 4 is a table for managing dealer information. A dealer ID 410 that uniquely identifies the dealer, a dealer name 440, an address 450, an e-mail address 420, and a password 430. And holding.

  The price management table 30 shown in FIG. 5 is a table for managing the product price of the store and the product price of the wholesale store, and holds the product ID 510 and the store ID 520 of the store 130 that accepts orders for the product as key values. The store price 530 and the wholesale store price 540, which are the product prices of the store 130, are held. The retail store price 530 is registered by the wholesale store 150 by providing price information from the retail store 130 to the wholesale store 150 in advance. The store price 530 may be registered by the store 130 from the WEB browser 140.

  The inventory / delivery date management table 40 shown in FIG. 6 is a table for managing the number of stocks, the provisional reserve number, and the delivery date of each product at a wholesale store, and mainly stores the product ID 610 as a key value. The provisional reserve number 630, the due date 640 for inventory, and the manufacturer order number 650 are held. If there is no particular change in the due date 640 for inventory, the due date 640 for inventory is shifted by one day and re-registered by a date / time batch or the like. When there is a change in the delivery date 640, the wholesale store 150 inputs the product ID and the delivery date in the file for setting the delivery date of the inventory, acquires the delivery date by referring to the previous period file by the date and time batch, Registration is made on the delivery date 640 for the stock of the corresponding product. The manufacturer order quantity 650 manages the quantity ordered from the manufacturer when the provisional allocation quantity 630 is larger than the inventory quantity 620 and the inventory is insufficient in the wholesale store.

  The status management table 50 shown in FIG. 7 is a table for managing the flow of processing in ordering / order receiving among the store 130, the wholesale store 150, and the end user 110 with respect to orders generated by the end user 110. An order ID 710 that uniquely identifies an order mainly generated by the end user 110, an ID 720 of the dealer involved in the order, an ID 730 of the end user, a status 740 indicating the progress of processing, and an order response deadline 750 of the dealer 130 keeping.

  The order management table 60 shown in FIG. 8 is a table for managing the detailed information of each order. The order ID 810 is used as a key value, the product ID 820 of the product handled in the order, the number of orders 830 for the end user 110, and the store 130. The number of orders received 840, the number of orders received 850 of the wholesale store 150, and a URL 860 for displaying a sales order screen 1300 for a store which will be described later with reference to FIG.

  The purchase history management table 80 shown in FIG. 9 is a table for managing completed orders for each store 130 as a purchase history. The store ID 910, the received product ID 920, the number of user orders 930, and the store It holds the number of orders 940 and the completion date 950 delivered to the end user 110 of the purchase.

  A product management table 70 shown in FIG. 10 is a table for managing product information, and stores a product name 1020, a manufacturer name 1030, and a store ID 1040 of a store having the product with the product ID 1010 as a key value. .

  FIG. 11 is a diagram for explaining the processing operation in the business model using the HPS 100 in the above-described embodiment of the present invention. Next, this will be explained. In the example illustrated in FIG. 11, it is assumed that the end user A 1100 orders the product S from the store B 1110 through the HPS 100 provided by the wholesale store C 1120. Further, it is assumed that the store B1110 that has received the order has an insufficient inventory of the product S and places an order for this shortage to the wholesale store C1120 using the HPS 100.

Step 1160
The process in this step is a process from when the end user A 1100 logs in to the system until the order data is transmitted to the HPS 100. In the description of this step, the process from the login to the display of the order entry screen 1200 shown in FIG. 12 by the end user A 1100 will be described later using the screen examples of FIGS. Here, an example of the following two login methods will be described for the login of the end user A1100 to the store B1110. Before that, examples of the order input screen 1200, the login screen 1800, and the store list screen 1900 are described. explain.

  FIG. 12 is a view showing an example of an order entry screen 1200 displayed on the end user's WEB browser 120. This order entry screen is a product searched by the input area 1210 of the product ID 1215, the search button 1220, and the search button 1220. Name and price display areas 1235 and 1240, an input area 1250 for the number of orders 1225, and an order button 1260 are displayed.

  FIG. 18 is a diagram showing an example of a login screen 1800 of the end user A1100. The login screen 1800 includes an ID column 1810 for inputting the ID 1815 of the end user A1100, and a password column 1820 for inputting the password 1825 of the end user A1100. The login button 1830 is displayed.

  FIG. 19 is a diagram illustrating an example of a dealer list screen 1900, which is configured as a collection of links such as a link 1910 to the order entry screens 1200 of all the dealers A to D acquired by the user / store authorization device 240. Yes.

Returning to the description of the processing in step 1160 in FIG.
First Method The end user A 1100 accesses the HPS 100 and displays a login screen 1800 of the end user A 1100 shown in FIG. The end user A 1100 inputs the end user A ID 1815 (“12345” in the illustrated example) in the ID field 1810 of the login screen and the end user A password 1825 (“passwd” in the illustrated example) in the password field 1820, and logs in. By clicking a button 1830, the input end user ID 1815 and password 1825 are transmitted to the HPS 100. The HPS 100 acquires all the store IDs 340 from the user management table 10 using the user ID 1815 and the password 1825 transmitted as described above as key values using the user / store authentication device 240. The user / dealer authentication device 240 generates a store list screen 1900 shown in FIG. 19 which is a collection of links to the order entry screens 1200 of all the stores acquired from the store ID 340. The end user A1100 displays the screen on the WEB browser 120, and clicks a link 1910 of a store where the order is placed, for example, the store B1110, whereby the order input screen 1200 of the store B1110 as shown in FIG. To get.

Second Method The end user A 1100 accesses the HPS 100 and displays the store list screen 1900 shown in FIG. 19 which is a collection of links to the order entry screens 1200 of all the stores registered in the store management table 20. Display on browser 120. The end user A1100 clicks a link 1910 to the login screen 1800 to the store B1110 to order from the screen, and acquires the login screen 1800 having the ID information of the store B1110 as shown in FIG. The end user A 1100 transmits the end user ID 1815 and password 1825 input through the login screen and the ID of the store B 1110 held on the screen to the HPS 100 by clicking the login button 1830. The HPS 100 uses the user / dealer authentication device 240 to perform authentication from the user management table 10 using the end user ID 1815 and password 1825 transmitted as described above and the ID of the store B 1110 as key values. If the authentication is successful, the HPS 100 generates an order entry screen 1200 shown in FIG. 12 for the store B 1110 and displays it on the WEB browser 120 of the end user A 1100.

  When the end user A 1100 inputs “0005” as the product ID 1215 in the product ID input area 1210 and clicks the search button 1220 on the order entry input screen 1200 to the store B 1110, the end user A 1100 clicks the search button 1220 and the product ID 1215 input to the HPS 100 from the browser 120 and the store ID of B1110 is transmitted. The HPS 100 acquires the product S from the item name item 1020 through the order management apparatus 250 using the product ID 1215 transmitted from the product management table 80 as a key value. Further, the price inquiry device 270 acquires the price 1240 of the store B from the store price 530 using the product ID 1215 transmitted from the price management table 30 and the ID of the store B 1110 as key values, and displays the order entry screen 1200. A product name field 1235 and the price field 1240 are generated by putting the price 1240 of the store B acquired from the store price 530 in the price field 1240. The end user A 1100 redisplays the order entry screen 1200 generated above, designates, for example, 100 pieces as the order quantity 1255 in the order quantity column 1250, clicks the order button 1260, and enters the entered product ID 1215, order. The number 1255 and the ID of the store B 1110 are transmitted to the HPS 100.

Step 1170
In the process of step 1170, the HPS 100 generates the order request screen 1300 shown in FIG. 13 for the store B 1110 after executing the process of step 1140, which will be described later, and the store sent from the end user A 1100 in step 1160 described above. Based on the ID of B1110, the mail address 420 of the store B1110 is acquired from the store management table 20 through the user / store authentication device 240, and the order request mail is transmitted to the acquired address.

  FIG. 13 is a diagram showing an example of an order request screen 1300 for the store B 1110. Here, an example of the order request screen 1300 will be described. The order request screen 1300 displays the product name 1230 ordered by the end user, the user name 1100, the order request number 1255, and the order number field for inputting the order number 1315 that can be ordered with respect to the order request number 1255. 1310 and a due date column 1325 for inputting a due date 1325 is provided. The order request screen 1300 also includes columns for a wholesale store name 1120, a delivery date 1350 of the wholesale store, and a wholesale price 1360 for placing an order shortage to the wholesale store. As a method, a column for specifying a delivery method 1335 to the user from the delivery method list 1330 and an order confirmation button 1340 are provided.

Step 1175
In the process of step 1175, when the store B 1110 receives the mail by the process of step 1170, the store B 1110 accesses the HPS 100 and displays a login screen 1800 on the WEB browser 140 of the store B 1110. In this screen, after entering the ID of the store B 1110 in the ID column 1810 and the password of the store B 1110 in the password column 1820, the login button 1830 is clicked, and the data input above is transmitted to the HPS 100.

  The HPS 100 uses the user / dealer authentication device 240 to authenticate the transmitted store ID and password of the store B 1110 based on the contents of the store management table 20 as a key value. If the authentication is successful, the HPS 100 uses the order management apparatus 250 to acquire all the order IDs 710 whose status is “waiting for an order response” from the status management table 50 using the ID of the store B 1110 as a key value. Each order screen URL 860 is acquired from the table 60 using all the order IDs 710 acquired as described above as key values, and a link collection screen for each URL is generated. Further, a response deadline 750 is acquired from the status management table by using the order ID 710 acquired above as a key, and displayed next to the URL link.

  The WEB browser 140 of the store B 1110 displays the screen generated by the HPS 100 as described above, clicks a link to the order request screen 1300 from the end user A 1100, and displays the acquired order request screen 1300 on the WEB browser 140.

  Dealer B1110 inputs 60 as the number of orders 1315 that can be accepted in the order quantity column 1310 for 100 orders received 1255 on the order request screen 1300, and the shop B1110 enters the delivery date column 1320 at the time of ordering. The delivery date 1325 is entered. At this time, since the input number of orders 1315 is less than the number of order requests 1255, 40 shortages will be ordered from the wholesale store C1120, so the delivery date 1350 and wholesale price 1360 of the wholesale store are confirmed, A delivery method 1335 for the user is designated and selected from the delivery method list 1330 as a delivery method. After these operations are completed, the order confirmation button 1340 is clicked.

  By operating the order request screen 1300 of the store B 1110 as described above, the ID of the store B 1110, the number of orders 1315, the delivery date 1325, and the delivery method data 1335 are transmitted from the WEB browser 140 to the HPS 100.

Step 1180
After executing the processing of step 1150, which will be described later, the HPS 100 generates an order confirmation screen 1400 as shown in FIG. 14 for confirming that the order has been confirmed from the store B1110 to the wholesale store C1120, and the store B1110 The confirmation notification mail describing the URL of the screen generated in the above is transmitted.

  FIG. 14 is a diagram showing an example of an order confirmation screen 1400 for the store B1110. Here, an example of the order confirmation screen 1400 will be described. The order confirmation screen 1400 basically confirms the order request processing described above, and thus has the same contents as the order request screen shown in FIG.

  Then, the store B 1110 displays the order confirmation screen 1400 on the WEB browser 140 of the store B 1110 by accessing the URL described in the mail. On the order confirmation screen 1400, the number of orders 1315 and the delivery date 1325 of the store B1110 are displayed, the number of orders 1430 to the wholesale store C1120, the delivery date 1440 of the wholesale store C1120, the wholesale price 1450, and the total price 1460. The delivery method 1335 is displayed.

Step 1185
After generating the order confirmation screen 1500 shown in FIG. 15, the HPS 100 confirms that the end user A 1100 has received an order request from the number of orders 1315 of the store B 1110 and the number of orders 1430 of the wholesale store C 1120 in the processing described above. Then, a confirmation notification email describing the URL of the generated order confirmation screen 1500 is transmitted to the end user A1100. The end user A 1100 displays the order confirmation screen 1500 on the WEB browser 120 of the end user A 1100 by accessing the URL described in the mail.

  FIG. 15 is a diagram showing an example of an order confirmation screen 1500 for the end user. Here, an example of the order confirmation screen 1500 will be described. On the order confirmation screen 1500, the number of orders 1315 and the delivery date 1325 of the store B1110 are displayed, and the number of orders 1430 and the date of delivery 1440 of the wholesale store C1120 are displayed as orders of the store B1110. This order confirmation screen 1500 is displayed on the WEB browser 120 of the end user A1100.

Step 1190
Dealer B1110 delivers 60 products S received from end user A1100 to end user A1100.

Step 1195
The wholesale store C1120 directly delivers 40 products S received from the store B1110 to the end user A1100 because the user delivery 1335 is designated on the order request screen 1300 of the store B1110. Here, when “delivery to the store” is selected as the delivery method 1330, the product is delivered to the store B1110. At this time, the employee who processed the delivery of the wholesale store C1120 uses the HPS 100 to take out a list of orders that are “waiting for delivery” from the order management apparatus 250, select the corresponding order from the list, and described above. In response to the order, a completion instruction is issued using the HPS 100. After this processing, the HPS 100 uses the inventory / delivery date inquiry device 260 to register the inventory quantity 620 in the inventory / delivery time management table 40 by reducing 40 items corresponding to the delivery quantity. Further, the HPS 100 deletes the data related to the order of this processing from the status management table 50 and the order management table 60 using the order management device 250 and deletes the data in the purchase history management table 80 using the purchase history management device 280 as described above. From the acquired data, the store ID 720, the product ID 820, the number of user orders 830, the number of store orders 840, and the date of completion are registered in the purchase history management table 80, respectively.

  FIG. 16 is a flowchart for explaining the processing operation of step 1140 of the HPS 100 shown in FIG. 11. Next, this will be described. Note that the flow described here is expressed as N orders for the end user A1100 and M orders for the store B1110 for the convenience of explaining processing in cases other than the example described above. In this process, data transmitted from the end user A 1100 and the store B 1110 or data used for screen generation is secured in the session area 290.

(1) The WEB server apparatus 210 of the HPS 100 receives N orders for the product S from the end user A 1100 through the order input screen 1200. Thereafter, the order management apparatus 250 registers the order ID 810 and the ID of the product S in the product ID 820 and the order number transmitted as described above in the user order number 830 in the order management table 60. Further, the order management apparatus 250 sets the order ID to the order ID 710, the ID of the store B 1110 to the store ID 720, the ID of the end user A 1100 to the end user ID 730, and the status 740 to the status management table 50. The reply deadline is registered in “waiting for reply” (step 1600).

(2) The stock / delivery date inquiry device 260 of the HPS 100 acquires the stock quantity 620 and the provisional reserve quantity 630 from the stock / delivery time management table 40 using the ID of the product S transmitted from the end user A 1100 as a key value. The inventory / delivery date inquiry device 260 determines whether or not the difference between the inventory quantity 620 and the provisional allocation quantity 630 acquired in this way is equal to or greater than the order quantity N transmitted from the end user A1100 (step 1610).

(3) If it is determined in step 1610 that the difference between the inventory quantity 620 and the provisional allocation quantity 630 is N or more, the HPS 100 sends the provisional order quantity in the inventory / delivery date management table 40 through the inventory / delivery time inquiry device 260. 630 is incremented and registered, and then a delivery date 640 for the inventory is acquired and held in the session area 290 (step 1620).

(4) If the difference between the inventory quantity 620 and the provisional allocation quantity 630 is less than N in the determination in step 1610, the HPS 100 passes through the manufacturer ordering device 230 and exceeds the shortage of the product S compared in step 1610. The number is ordered from manufacturer D1130. At this time, the HPS 100 registers the number of orders to the manufacturer D 1130 in the manufacturer order quantity 650 of the inventory / delivery date management table 40 through the inventory / delivery date inquiry device 260. As a result of the ordering process to the manufacturer D1130, the manufacturer ordering apparatus 230 acquires the delivery date from the manufacturer D1130, adds the work schedule until delivery to the wholesale store C1120 to the delivery date, and sets this as the delivery date of the wholesale store C1120. The session area 290 is held. After this processing, the HPS 100 registers the number of temporary orders 630 in the inventory / delivery date management table 40 by N through the inventory / delivery date inquiry device 260 (step 1630).

  In addition, when the product S is delivered from the manufacturer D1130, the update of the inventory quantity is registered by adding the delivery quantity to the inventory quantity 620 of the inventory / delivery date management table 40 through the inventory / delivery date inquiry device 260, and This is done by reducing the number of deliveries from the number 650 of manufacturer orders.

(5) After completing the above-described processes, the HPS 100 acquires the wholesale store price 540 from the price management table 30 using the ID of the product S as a key value through the price inquiry device 270, and holds this in the session area 290. (Step 1640).

(6) Next, the HPS 100 uses the order management device 250 to secure the delivery date of the product S, the wholesale store price, and the product S transmitted from the end user, which are secured in the session area 290 by the processing from Step 1620 to Step 1640 described above. The order receiving request screen 1300 for the store B is generated from the ID and the number of orders (step 1650).

(7) Next, the HPS 100 acquires the mail address 420 from the store management table 20 through the user / store authentication device 240, and then sends an order request mail to the store B 1110 by the mail transmitter 220 (step) 1660).

  After the processing of step 1140 of the HPS 100 described above, if there is no order response from the store B 1110 even after the response time limit set by the store B in step 1600, the HPS 100 stores the inventory in the temporarily ordered product S. Use the delivery date inquiry device 260 to register the inventory / delivery date management table 40 by subtracting N from the provisional allocation number. After the above processing, the HPS 100 again performs the provisional ordering processing of step 1140 and transmits to the store B 1110 by e-mail that the due date for response to the order has been changed and the delivery date of the wholesale store will be changed again. To do.

  FIG. 17 is a flowchart for explaining the processing operation of step 1150 of the HPS 100 shown in FIG. 11. Next, this will be described. In this process, data transmitted from the end user A 1100 and the store B 1110 or data used for screen generation is secured in the session area 290.

(1) The WEB server apparatus 210 of the HPS 100 receives, from the sales order B 1110, the response of the order quantity M for the order quantity N of the product S in the end user A 1100 from the sales order B 1110. After this processing, the order management apparatus 250 registers M pieces in the store order quantity 840 of the order management table 60 (step 1700).

(2) Next, the HPS 100 uses the order management device 250 to determine whether or not the number M of orders received from the store B 1110 is less than the number N ordered from the end user A 1100 (step 1710).

(3) If it is determined in step 1710 that the number M of orders received from the store B 1110 is less than the number N ordered by the end user A 1100, the HPS 100 sends (N−M) pieces from the store B 1110 to the wholesale store C 1120. (N−M) pieces are secured in the session area 290 as the number of orders received from the wholesale store 1120. Further, the HPS 100 registers (N−M) pieces in the wholesale store order quantity 850 of the order management table 60 by using the order management device 250 and updates the status 740 of the status management table 50 to “waiting for delivery”. After this processing, the inventory / delivery date inquiry device 260 updates N by subtracting N from the provisional allocation number 630 in the inventory / delivery date management table 40 (step 1720).

(4) If it is determined in step 1710 that the number M of orders received at the store B 1110 is N or more, the HPS 100 uses the order management device 250 to manage the order management table 60 and status management. The order of this processing is deleted from the table 50, and the order information is registered in the purchase history management table 80 using the purchase history management device 280. Further, the HPS 100 uses the inventory / delivery date inquiry device 260 to register the product S in the inventory / delivery date management table 40 by subtracting N from the provisional allocation number 630 (step 1725).

(5) After performing the above-described processing, the HPS 100 generates an order confirmation screen 1400 described with reference to FIG. 14 from the session area 290 secured using the order management apparatus 250 (steps). 1730).

(6) Next, the HPS 100 generates the order confirmation screen 1500 described with reference to FIG. 15 from the session area 290 secured by using the order management apparatus 250 (step 1740).

(7) The HPS 100 transmits the order confirmation screen 1400 generated by the processing of Step 1730 to the WEB browser 140 of the store B 1110 (Step 1750).

  By executing the processing in step 1750 described above, when the order confirmation button 1340 is pressed on the order request screen 1300 in the processing in step 1700 at the store B 1110, the order confirmation screen 1400 is returned from the HPS 100 as a result. It will be a flow of processing.

(8) Next, the HPS 100 establishes a link so that the order confirmation screen 1500 described with reference to FIG. 15 can be displayed after the end user A logs in at step 1160. After this processing, the HPS 100 acquires the mail address 420 of the end user A 1100 from the user management table 20 through the user / dealer authentication apparatus 240, and requests the order confirmation from the mail address 420 acquired above by the mail transmission apparatus 220. send mail. The sent mail displays that the order confirmation screen 1500 can be displayed when the end user A 1100 performs the log-in process of step 1160 (step 1760).

  By executing the processing in step 1760 described above, the end user can display the order confirmation screen 1500 after the login in step 1160.

  Each processing in the above-described embodiment of the present invention can be configured as a processing program, and this processing program is stored in a recording medium such as HD, DAT, FD, MO, DVD-ROM, and CD-ROM and provided. can do.

  FIG. 20 is a diagram showing an example of a screen when the wholesale store C1120 performs a purchase history analysis on the product S of the store B1110, which will be described next.

  On the purchase history analysis screen screen 2000 for the product S of the store B, the total number of orders 2010 received from each end user by the store B 1110 for the product S within a certain period, and the store B 1110 to the wholesale store C 1120 The number of products S ordered 2020 and the number Z of products 30 delivered by the wholesale store C1120 to the store B1110 without an order from each end user are displayed. If X2010-Y2020-Z2030 is calculated as 2040 and this analysis value 2040 is large, it is an index that the possibility that the product S is delivered from another wholesale store is high. Here, it is assumed that Z, which is the sum of the numbers delivered by the wholesale store C1120 to the store B1110, is held in a table different from the table used in the system according to the embodiment of the present invention described.

  When the calculation as described above is performed for all the products handled by the store B1110 and the total of the respective analysis values 2040 is calculated, the ratio of orders to the wholesale store C1120 of all the products of the store B1110 is calculated. be able to.

  According to the embodiment of the present invention as described above, the effects described below can be obtained.

  1. When an end user places an order with a retail store, provisional provisions are made in advance at the wholesale store. At this time, if the inventory is insufficient at the wholesale store, in order to place an order from the manufacturer, If more than a few orders are received, the product can be delivered to the dealer and the end user at an early stage.

  2. By the provisional provisioning process described above, it is possible to reliably present the price and delivery date even when the inventory of the wholesale store is insufficient. This reliable provision of information leads to an increase in the number of orders from dealers to wholesalers, and it is possible for dealers to provide reliable delivery times to end users.

  3. The dealer can operate without problems even when the number of stocks is zero, so that the cost of the dealer can be reduced, and the order quantity to the wholesale shop can be increased.

  4). The system usage rate can be improved because orders and orders can be processed for products by using an Internet browser and e-mail function without requiring special equipment for dealers and end users. In addition, since the ordering work of the wholesale store is automated, the labor cost of the wholesale store can be reduced.

  5). Since the HPS stores past orders in the purchase history management table, the purchase history for a certain period is referred to from this table, and the total number of orders for any product at any store and the store. Compared with the total number of orders placed in the product from the wholesale store C, if the number of orders is higher, it can be analyzed that the product is ordered to another wholesale store. It is possible to obtain information on measures to improve sales, such as acquiring products that are currently flowing into the market and selling them with emphasis on the products.

It is a block diagram which shows the structure of the order-receiving / ordering system by one Embodiment of this invention. It is a block diagram which shows the structure of the ordering / ordering apparatus of a store portal site system (HPS). It is a figure explaining the data currently hold | maintained at the user management table. It is a figure explaining the data hold | maintained at a store management table. It is a figure explaining the data currently hold | maintained at the price management table. It is a figure explaining the data currently hold | maintained at a stock and delivery date management table. It is a figure explaining the data currently hold | maintained at the status management table. It is a figure explaining the data currently hold | maintained at the order management table. It is a figure explaining the data currently hold | maintained at the log | history management table. It is a figure explaining the data currently hold | maintained at the merchandise management table. It is a figure explaining the processing operation in the business model using HPS in embodiment of this invention mentioned above. It is a figure which shows the example of the order input screen displayed on an end user's WEB browser. It is a figure which shows the example of the order request screen for the store B. It is a figure which shows the example of the order confirmation screen with respect to the store B. FIG. It is a figure which shows the example of the order confirmation screen with respect to an end user. 12 is a flowchart for explaining a processing operation of step 1140 of HPS shown in FIG. 12 is a flowchart for explaining a processing operation in step 1150 of the HPS shown in FIG. It is a figure which shows the example of the login screen of the end user A. It is a figure which shows the example of a store list screen. It is a figure which shows the example of a screen in case the wholesale store C performs the purchase log | history analysis in the goods S of the store B. FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 User management table 20 Dealer management table 30 Price management table 40 Inventory / delivery date management table 50 Status management table 60 Order management table 70 Merchandise management table 80 Purchase history table 90 Order processing apparatus 100 Dealer portal site system (HPS)
110 End User 120 End User Web Browser 130 Dealer 140 Dealer WEB Browser 150 Wholesale Shop 160 Wholesale Shop WEB Browser 170 Manufacturer 180 Manufacturer Terminal 190 Communication Line 210 Web Server Device 220 Mail Sending Device 230 Manufacturer Ordering Device 240 User・ Dealer authentication device 250 Order management device 260 Stock / delivery date inquiry device 270 Price inquiry device 280 Purchase history management device 290 Session area

Claims (10)

  A portal site system of a store for an end user to order a product from a store, and a wholesale store where the store performs a transaction provides the portal site system, and the portal site system is connected to a network via a network. An end user terminal and a store terminal are connected to each other, and the portal site system directly receives the order data of the product from the end user terminal, stores this as order data, and stores the end user data. The provisional number of products for the number of orders received from the terminal in the store are provisionally reserved for the inventory data of the wholesale store, and data indicating that the end user has placed an order at the terminal of the store and the wholesale store The portal site system of a store characterized by sending delivery date information.   When the provisional provision is made for the product ordered by the end user, the portal site system, if the inventory of the product is insufficient in the wholesale store, the shortage number is sent to the manufacturer terminal connected via the network. 2. The portal site system of a dealer according to claim 1, wherein the portal site system of the dealer is transmitted as order data, and the delivery date of the wholesale store is calculated from the delivery date of the manufacturer by the order.   The portal site system receives an answer of the number of orders from a store terminal corresponding to the transmitted data, and there is a difference between the number of orders from the end user terminal and the number of orders from the store terminal The difference is recognized as order data to be ordered from the store to the wholesale store, and an order is received, and each delivery date of the store and the wholesale store is transmitted to the terminal of the end user. Portal site system of the listed store.   The portal site system stores an order history from the end user to the store, an order history from the store to the wholesale store, and a history of the number of deliveries from the wholesale store to the store. 4. The store portal site system according to claim 3, wherein an analysis is made of how much the product is ordered from another wholesale store.   An order receiving / ordering system for an end user to place an order for a product at a store, a portal site system of a store provided by a wholesale store in which the store performs a transaction, a terminal of the end user, and a terminal of the store And the portal site system directly accepts order data from the end user's terminal, stores this as order data, and wholesales the products for the number of orders received from the end user's terminal. The provisional provision is made for the inventory data of the store, and the data indicating that the product has been ordered and the delivery date information of the wholesale store are transmitted to the terminal of the store which is the order destination assumed by the end user. Ordering / ordering system.   When the provisional provision is made for the product ordered by the end user, the portal site system, if the inventory of the product is insufficient in the wholesale store, the shortage number is sent to the manufacturer terminal connected via the network. 6. The order receiving / ordering system according to claim 5, wherein the ordering data is transmitted as ordering data, and the delivery date of the wholesale store is calculated from the delivery date of the manufacturer by the ordering.   The portal site system receives an answer of the number of orders from a store terminal corresponding to the transmitted data, and there is a difference between the number of orders from the end user terminal and the number of orders from the store terminal 6. The apparatus recognizes the difference as order data to be ordered from the store to the wholesale store, accepts an order, and transmits each delivery date of the store and the wholesale store to an end user terminal. The ordering / ordering system described.   The portal site system stores an order history from the end user to the store, an order history from the store to the wholesale store, and a history of the number of deliveries from the wholesale store to the store. 8. The order receiving / ordering system according to claim 7, wherein an analysis is made of how much the product is ordered from another wholesale store.   An order receiving / ordering method for an end user to order a product from a store, a portal site system of a store provided by a wholesale store in which the store performs a transaction, a terminal of the end user, and a terminal of the store And the portal site system directly accepts order data from the end user's terminal, stores this as order data, and wholesales the products for the number of orders received from the end user's terminal. The provisional provision is made for the inventory data of the store, and the data indicating that the product has been ordered and the delivery date information of the wholesale store are transmitted to the terminal of the store which is the order destination assumed by the end user. How to order / order. A processing program for constructing a portal site system of a dealer provided by a wholesaler with which a dealer conducts a transaction in order for the end user to order a commodity from the dealer, and ordering the commodity from the terminal of the end user A processing step for directly receiving data, a processing step for storing this as order data, a processing step for temporarily allocating products for the number of orders received from the terminal of the end user to the inventory data of the wholesale store, and an end user The processing step of transmitting data indicating that an order has been placed at the terminal of the store that is the ordering destination assumed by the customer and the delivery date information of the wholesale store, and when making provisional provisions for the products ordered by the end user, A process of sending order data to a manufacturer's terminal connected via a network when the inventory of the product is insufficient at a wholesale store. A processing step of calculating a delivery date of the wholesale store from the delivery date of the manufacturer by the ordering, a processing step of accepting an answer of the number of orders from the terminal of the store corresponding to the transmitted data, and from the terminal of the end user When there is a difference between the number of orders and the number of orders received from the terminal of the store, the processing step of recognizing the difference as order data to be ordered from the store to the wholesale store and receiving the order; the store and the wholesale store And processing steps for transmitting the respective delivery dates to the end user's terminal, and executing the processing steps to execute a product ordering process.

Images