JP2005084854A - Merchandise ordering/order-receiving system, server computer and merchandise shipping state notifying method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To realize a construction allowing a user having ordered merchandise to confirm the merchandise shipping state regarding the ordered merchandise without a complex system structure. <P>SOLUTION: The user having ordered the merchandise by accessing a web server 3 via a client terminal 1 confirms the merchandise shipping state regarding the ordered merchandise by re-accessing the web server 3 via the client terminal 1 after notifying the web server 3 of issuing state status from a label printer 5 having printed and issued a tag regarding the ordered merchandise. Thereby, the construction allowing the user having ordered the merchandise to confirm the merchandise shipping state regarding the ordered merchandise is realized without a complex system structure. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a product ordering system, a server computer, and a product shipping status notification method.

  When performing label printing in a remote place, it is necessary to construct a dedicated line and a dedicated network. Further, in order to print a label on the client terminal, it is necessary to install an application for label printing on the client terminal.

  Therefore, a system is known in which a label issuing program is downloaded from a server to a client terminal via the Internet, and the label issuing program is executed on the client terminal to issue a label (see, for example, Patent Document 1).

JP 2001-261131 A

  However, in a system such as that disclosed in Patent Document 1, since the print status of the label of the client terminal cannot be obtained in real time on the server side, the label issuance status at the label printer connected to the client terminal at the server I can't figure out.

  In recent years, a product ordering system has been constructed that orders a product by accessing a Web server via a client terminal. In such a product ordering system, the user who ordered the product There is a desire to build a mechanism that can confirm the status of product shipment for an ordered product as easily as possible.

  An object of the present invention is to realize a mechanism in which a user who has ordered a product can check the product shipment status of the ordered product without using a complicated system configuration.

  The present invention relates to a product ordering system having a Web server accessible from a client terminal through a communication network, and an order receiving means for receiving a product order from a user via the client terminal accessed to the Web server; An order data generating unit that generates order data in which the ordered product received by the order receiving unit is associated with information on a user who has ordered the product, and the client terminal that has accessed the Web server. A tag printing data providing unit for providing the order data generated by the order data generating unit as tag printing data, and the client terminal from the client terminal to which the tag printing data is provided by the tag printing data providing unit. To an available printer A tag issue means for sending the tag printing data and printing and issuing the tag; an issue status status notifying means for notifying the Web server of an issue status returned from the printer after issuing the tag print by the printer; An issuance status status receiving means for receiving the issuance status status notified by the issuance status status notifying means; an issuance status status storing means for storing the issuance status status received by the issuance status status receiving means; Ship status notifying means for notifying the client terminal that has accessed the Web server of the status of product shipment according to the issue status status stored in the storage unit.

  Accordingly, a user who has ordered a product by accessing the Web server via the client terminal is notified of the issue status from the printer that has printed and issued the tag for the ordered product to the Web server, and then via the client terminal. By accessing the Web server again, it is possible to check the product shipment status for the ordered product.

  According to the present invention, a user who orders a product by accessing a Web server via a client terminal displays the product shipping status of the ordered product from the printer that has printed and issued a tag for the ordered product to the Web server. The system that allows the user who ordered the product to confirm the product shipment status for the ordered product should have a complex system configuration. Can be realized.

  A first embodiment of the present invention will be described with reference to FIGS.

[1. Configuration of Product Ordering System 100]
Here, FIG. 1 is a system configuration diagram schematically showing the overall configuration of the product ordering system 100 of the present embodiment. As shown in FIG. 1, the product ordering system 100 includes a client terminal 1 that is a PC (Personal Computer) used by a user. Such a client terminal 1 is connected to the Internet 2 which is a communication network via a modem, a TA (terminal adapter), and a router (not shown).

  In addition, the product ordering system 100 includes a server computer (hereinafter referred to as a headquarter server) 3 of the manufacturer headquarters. The headquarter server 3 functions as a Web server, and is connected to the Internet 2 via a router (not shown).

  Further, the product ordering system 100 includes a client terminal 4 that is a PC (Personal Computer) installed in a shipping center. Such a client terminal 4 is also connected to the Internet 2 via a modem, TA, and router (not shown). Further, a label printer 5 is connected to the shipping server 4 via the RS232C. Note that the connection between the shipping server 4 and the label printer 5 is not limited to RS232C, and can be performed by Centronics, LAN, wireless, or the like.

  In addition, as shown in FIG. 1, goods are delivered between the shipping center and the user by courier service or the like.

[1-1. Explanation of headquarter server 3]
Next, the headquarter server 3 will be described. Here, FIG. 2 is a block diagram showing an electrical connection of each part of the headquarter server 3. As shown in FIG. 2, the headquarter server 3 includes a central processing unit (CPU) that centrally controls each unit, a read only memory (ROM) that stores a control program, and a random access memory (RAM) that functions as a work area for the CPU. A computer-configured control means 21 composed of a (Memory) or the like is provided, and this control means 21 controls various calculations and data transfer. A communication control unit 22 is connected to the control unit 21 and performs data input / output control via the Internet 2.

  In addition, the control means 21 includes a storage unit (storage medium) 23 such as an HDD (HardDisk Drive) for storing a Web application, an HTML (HyperText Markup Language) file, and an external called via a CGI (Common Gateway Interface). A storage unit (storage medium) 24 such as an HDD for storing a program (hereinafter referred to as a CGI program) is connected. These storage devices 23 and 24 may be provided inside the headquarter server 3 or may be provided outside the headquarter server 3.

  When a web site browsing request is made via the Internet 2 from the client terminal 1 installed at the user's site or the client terminal 4 installed at the shipping center, the web application is transferred by HTML file transfer or CGI program execution. This is a program for sending browsing information to the client terminal 1. For example, when the browsing request from the client terminal 1 is a browsing request for an HTML file already prepared, the Web application transmits the HTML file to the client terminal 1. Further, when there is data transfer or the like in the browsing request from the client terminal 1, the CGI program is executed, and data storage and various calculations are performed.

  As shown in FIG. 2, the control means 21 includes a storage unit (hereinafter referred to as an order data file) 25 for storing order information, a storage unit (hereinafter referred to as a product image file) 26 for storing product information, and a user. A storage unit (hereinafter referred to as a user data file) 27 for storing information is connected. These files 25, 26, and 27 will be described in detail later. Each of these files 25, 26, and 27 may be provided inside the headquarter server 3 or may be provided outside the headquarter server 3. Further, there is no problem even if these files 25, 26, and 27 are all included in one storage device.

[1-2. Explanation of client terminals 1 and 4]
Next, the client terminal 1 installed at each user destination and the client terminal 4 installed at the shipping center will be described. Here, FIG. 3 is a block diagram showing the electrical connection of each part of the client terminals 1 and 4. As shown in FIG. 3, the client terminals 1 and 4 are provided with control means 11 including a CPU for centrally controlling each unit, a ROM for storing a control program, a RAM functioning as a work area for the CPU, and the like. The control means 11 controls various calculations and data transfer. The control means 11 includes a communication control means 12 for performing input / output control of data via the Internet 2, a web browser and a web browser installed in the headquarter server 3 and a web browser, and a label printer 5 and a web browser. A storage device 13 such as an HDD for storing various programs such as a program that realizes a special function for operation on the Internet 2 such as a Web publishing tool (for example, ActiveX (trademark of Microsoft) control) It is connected. Note that the programs stored in the storage device 13 are different depending on the client PCs 1 and 4, and a function specific to each client PC 1 and 4 is exhibited by the difference in the programs stored in the storage device 13. .

  The client terminals 1 and 4 include a display unit 14 such as a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display) controlled by the control unit 11, a keyboard 15 or a mouse 16 that functions as an input unit, and various external devices. An interface (I / F) 17 and the like for executing data connection are provided.

[2. Processing in each part constituting product ordering system 100]
Next, processing in each unit constituting the product ordering system 100 will be described.

[2-1. Product ordering process from client terminal 1 to headquarter server 3]
First, processing for ordering a product from the client terminal 1 installed at the user's site to the headquarter server 3 will be described.

  Here, FIG. 4 is a flowchart showing a screen image displayed on the display unit 14 of the client terminal 1 when ordering a product. In FIG. 4, “HTML +“ number ”” indicates that the control means 21 of the headquarter server 3 executes a process of displaying an HTML file prepared in advance in the storage device 24 based on the Web application of the storage device 23. “CGI +“ number ”” indicates that the CGI program in the storage device 24 is operating, and the control means 21 sends the browsing information in response to the viewer's request. This indicates that the file processing is being executed or is being executed in the Web server.

  In order to place an order for a desired product, it is necessary to access the URL (Uniform Resource locator) of the product ordering Web site of the headquarter server 3 and log in to the Web site. Then, when the “login button” on the screen P1 (the top page of the product ordering website) displayed on the display unit 14 of the client terminal 1 is clicked with the mouse 16, the process proceeds to the next screen P2 (HTML1).

  A screen P2 shown in FIG. 4 is a login page. Since a form for inputting a user ID and a password is displayed on the screen P2, each item is input using the keyboard 15. After inputting the necessary items, the CGI program (CGI1) is executed by clicking the “confirm button” on the login page with the mouse 16.

  Here, FIG. 5 is a flowchart showing the flow of processing in the CGI program (CGI1). In the CGI program (CGI1), the user data file 27 is referred to and it is confirmed whether or not the input user ID and password are correct (step S1). In the user data file 27, as shown in FIG. 6, a user ID, password, name, address, telephone number, e-mail address, etc. are stored as user data. Therefore, it is determined whether or not the input user ID and password are correct by comparing the user ID and password stored in the user data file 27 with the input user ID and password.

  If the input user ID and password are correct (Y in step S1), image data of all products is extracted from the product image file 26 (step S2), and a product list page is displayed on the display unit 14 (step S3). . As shown in FIG. 7, the product image file 26 stores the image data of the product in association with the product name and the identification number indicating the product. A screen P3 in FIG. 4 is a product list page. As shown in FIG. 4, the image data of the product extracted in step S2 is displayed as a thumbnail on the screen P3.

  If at least one of the user ID and password is not correct (N in step S1), the display unit 14 of the client terminal 1 displays an error and returns to the screen P2 (login page) ( Step S4).

  When any one of the “product images” displayed on the screen P3 (product list page) in FIG. 4 is clicked with the mouse 16, the process proceeds to the next screen (order confirmation page) P4 (HTML2). As shown in FIG. 4, the selected “product image” is enlarged and displayed on the screen P4. When the user clicks the “order” button on the screen P4 (order confirmation page) with the mouse 16, the CGI program (CGI2) is executed.

  Here, FIG. 8 is a flowchart showing the flow of processing in the CGI program (CGI2). As shown in FIG. 8, in the CGI program (CGI2), after receiving an order for a product from the user (step S11: order accepting means), user information (information about the ordered product and the user who ordered the product) ( Order data in which the user name, address, telephone number) and label issuance status are associated is generated and stored in the order data file 25 of the headquarter server 3 (step S12: order data generation means). In the order data file 25, as shown in FIG. 9, the order product name, the identification number indicating the order product, the user information (user name, address, telephone number), and the label issuance status are the order data (tag printing data). Is stored as

[2-2. Label issuing process at client terminal 4]
Next, processing for issuing labels from the label printer 5 connected to the client terminal 4 will be described with reference to FIG.

  First, the Web browser of the client terminal 4 is activated. Then, as shown in FIG. 10, the web browser logs in to the web application on the headquarter server 3 (step S21). At this time, it is determined whether the Web publishing tool has been installed (step S22). If it is determined “YES” in step S22, the Web publishing tool can be used. If “NO” is determined in the step S22, a process of installing the Web publishing tool is performed. If the installation process is performed, the function of the Web publishing tool can be used. At this time, a screen for prompting download and installation of the Web publishing tool installation file may be displayed, or the latest Web publishing tool may be automatically installed. This Web browser has a check function for checking whether the Web publishing tool is already activated on another Web browser.

  When the client terminal 4 logs in to the Web application on the headquarter server 3 as in step S21 described above, the Web application on the headquarter server 3 performs the processing shown in the flowchart of FIG.

  That is, the headquarter server 3 obtains the ID number of the logged-in user, and determines whether or not the order data (tag print data) corresponding to the ID number is stored in the order data file 25 (step S51). If “YES” is determined in the determination in step S51, a process for transmitting the tag print data to the client terminal 4 is performed (step S52). Further, since the processing of steps S53 and S54 is processing for data received from the client terminal 4, the processing of the Web issuing tool in the client terminal 4 will be described first, and then the processing after step S53 will be described.

  On the Web browser side of the Web application, a process for receiving data sent from the server side is performed (step S25). When the data is received, the Web browser side performs a CRC check process on the received data (step S26). Next, a process for acquiring a CRC check result is performed (step S27), and a CRC check result is determined (step S28). If "NO" is determined in the step S28, the tag print data is not processed, and the next data is waited to be received. On the server side of the Web application, when the CRC check result is NG on the Web browser side, the process is terminated or the next data is transmitted. At this time, the transmission data determined to be “NO” may be retransmitted several times.

  On the Web browser side, when the CRC check is determined to be OK, the tag check data attribute check process is performed (step S29). Next, a process for acquiring the result of the attribute check is performed (step S30), and the result of the attribute check is determined (step S31). If "NO" is determined in the step S31, the tag print data is not processed, and the next data reception is awaited. In the Web application, when the result of the attribute check on the Web browser side is NG, the process is terminated or the next data is transmitted. At this time, the tag print data determined as “NO” may be corrected and retransmitted.

  If the Web browser determines that the attribute check of the tag print data is OK, the transmission data for the label printer 5 is set in the transmission buffer of the client terminal 4 (step S32). Here, a plurality of tag printing data can be set in the transmission data.

  And the process which transmits transmission data with respect to the label printer 5 is performed (step S33: tag printing data provision means).

  That is, data transmitted from the Web application is transmitted to the label printer 5 via the RS232C. As a result, the label printer 5 performs a process of issuing a label that is a tag. As described above, when the label issuing process (tag issue means) is performed in the label printer 5, the status from the label printer 5 is returned to the client terminal 4. As a result, the Web browser of the client terminal 4 acquires the printer status (step S34), and creates an issue status (step S35).

  As the status classification of the issue status, “0” is displayed when the printing process in the label printer 5 is normally completed, and “1” is displayed when the printing process is interrupted by an interruption button when an error occurs. “2” is set when a system error occurs, “3” is set when printing is in progress, and “4” is set when an error status is received.

  The issue status created by the Web browser of the client terminal 4 is stored in the storage device 13 in the client terminal 4.

  Next, it is determined whether the status is OK, that is, whether printing has been normally completed (step S36). If “YES” is determined in the determination in step S36, it is determined whether the normal completion status for the number of transmitted tag print data is received (step S37). If "NO" is determined in the step S37, the next status is acquired (step S34). If “Yes” is determined, the process proceeds to a notification issuance status creation process to create an issuance status status to be notified to the Web application (step S38), and a process for notifying the Web application of the issuance status is performed. (Step S39). Here, the function of the issuance status status notification means is executed.

  For this reason, the Web application can know the label issuing status in the label printer 5 connected to the client terminal 4 in real time.

  When a plurality of tag printing data is transmitted to the label printer 5, after receiving the status from the label printer 5 for the number of tag printing data, the issue status in the label printer 5 is notified to the Web application as the issue status. Can do. That is, printing can be executed in units of JOB.

  The issue status status thus transmitted to the Web application is received by the Web application (steps S53 to S55: issue status status receiving means), and the label issuance stored in the ordering data file 25 based on the issue status status. The status is updated (step S56: issue status status storage means).

  On the other hand, if “NO” is determined in the determination in step S36, an error display is performed on the display unit 14 of the client terminal 4 (step S40). For example, as shown in FIG. 12, when the print window 51 is opened on the display unit 14 of the client terminal 4 and the label is finished, “the label is finished. ”And a message detail 53“ Paper is finished. Set new paper. ”And a message 54 informing how many pages an error has occurred. The print window 51 also displays a “print interruption” button 55 that is operated when printing is interrupted.

  Then, it is determined whether or not the “print interruption” button 55 has been operated by the operator (step S41). If “YES” is determined in the determination in step S41, the process proceeds to an issue status creation process S38, where an issue status is created to indicate that the printing operation has been interrupted, and is issued to the Web application. Send status.

  As described above, when an error occurs in the label printer 5 and the printing operation is interrupted, the process returns to the process of step S24. Therefore, the process may shift to a reception process (step S25) for the next tag print data. it can.

  On the other hand, even if an error occurs during the printing operation, if the operator does not operate the “print interruption” button 55, the operator may be performing processing to eliminate the cause of the error. For example, it is a case where a label is supplied or a sheet is supplied. In such a case, the error is canceled. The web browser of the client terminal 4 receives the status from the label printer 5 (step S43). When the status is received, the process returns to step S36, and the received status is checked (step S36).

  If “NO” is determined in the determination in step S24, the process of the Web publishing tool ends.

  As described above, if a Web application that issues a label is installed in the headquarter server 3 and a Web browser and a Web issuing tool are installed in the client terminal 4, it is not necessary to download a label issuing program from the Web server. This saves you the trouble of downloading the label issuing program.

  Here, FIG. 13 is an explanatory view showing a label L which is a tag issued from the label printer 5. As shown in FIG. 13, the label L issued from the label printer 5 is attached to the product O. Such a label L is printed with an invoice I in which a label barcode BC for identifying the product O, a delivery destination (orderer, address, telephone number) of the product O, and the like are described.

  Note that various procedures related to the ordered products in the client terminal 4 installed in the shipping center can be processed by a known order processing technique, and thus description thereof is omitted here. Then, the product is delivered to the user by a courier service or the like.

  Further, as described above, in the headquarter server 3 that receives the issue status status transmitted from the label printer 5 in the Web application and updates the label issue status stored in the ordering data file 25 based on the issue status status, Based on the label issuance status stored in the order data file 25, the order data stored in the order data file 25 of the headquarter server 3 is generated as invoice issue data (invoice issue data generation means). The invoice issuance data is transmitted to a printer (not shown) connected to the headquarter server 3 to print and issue the invoice (invoice issuing means). That is, if the issuance status status is “0”, it can be determined that the printing process in the label printer 5 has been completed normally and the label has been attached to the product and shipped properly. In the case of “0”, the bill is automatically issued. On the other hand, if the issuance status is “1”, “2”, “3”, or “4”, the printing process in the label printer 5 has not been completed, so that the invoice is not issued.

[2-3. Processing for confirming shipment status from client terminal 1 to headquarter server 3]
Next, a process for confirming the shipment status of a product from the client terminal 1 installed at the user destination to the headquarter server 3 will be described.

  Here, FIG. 14 is a flowchart showing a screen image displayed on the display unit 14 of the client terminal 1 when confirming the shipment status of the product. In FIG. 14, “HTML +“ number ”” indicates that the control means 21 of the headquarter server 3 executes a process of displaying an HTML file prepared in advance in the storage device 24 based on the Web application of the storage device 23. “CGI +“ number ”” indicates that the CGI program in the storage device 24 is operating, and the control means 21 sends the browsing information in response to the viewer's request. This indicates that the file processing is being executed or is being executed in the Web server.

  In order to confirm the shipping status of the product, it is necessary to access the URL (Uniform Resource locator) of the Web site for checking the shipping status of the product of the headquarter server 3 and log in to the Web site. Then, when the “login button” on the screen P5 (the top page of the website for confirming the product shipment status) displayed on the display unit 14 of the client terminal 1 is clicked with the mouse 16, the process proceeds to the next screen P6 (HTML3).

  A screen P6 shown in FIG. 14 is a login page. Since a form for entering a user ID and password is displayed on the screen P6, each item is entered using the keyboard 15. After inputting the necessary items, the CGI program (CGI3) is executed by clicking the “confirm button” on the login page with the mouse 16.

  FIG. 15 is a flowchart showing the flow of processing in the CGI program (CGI 3). In the CGI program (CGI 3), the user data file 27 is referred to and it is confirmed whether or not the input user ID and password are correct (step S61).

  If the input user ID and password are correct (Y in step S61), the label issuing status is extracted from the ordering data file 25 (step S62), and the product shipping status confirmation page is displayed on the display unit 14 (step S63: shipping). Status notification means). A screen P7 in FIG. 14 is a product shipment status confirmation page. As shown in FIG. 14, on the screen P7, the shipment status of the product based on the label issue status extracted in step S62 is displayed. For example, if the issuance status status is “0”, since the printing process in the label printer 5 has been normally completed, the label is attached to the product and handled as being properly shipped. On the other hand, if the issuance status status is “1”, “2”, “3”, “4”, since the print processing in the label printer 5 has not been completed, it is handled that the product has not yet been shipped.

  If at least one of the user ID and password is not correct (N in step S1), the display unit 14 of the client terminal 1 displays an error and returns to the screen P2 (login page) ( Step S4).

  Then, after confirming the shipment status of the product, clicking the “confirmation button” on the product shipment status confirmation page with the mouse 16 displays a predetermined screen (for example, P1) (HTML4).

  Thus, in the present embodiment, a user who accesses the headquarters server 3 via the client terminal 1 and orders a product from the label printer 5 that prints and issues the label L, which is a tag for the ordered product, from the headquarters server After the issue status status is notified to 3, the product shipment status of the ordered product can be confirmed by accessing the headquarter server 3 again via the client terminal 1. Thus, a mechanism that allows the user who ordered the product to confirm the product shipping status of the ordered product can be realized without using a complicated system configuration.

  Next, a second embodiment of the present invention will be described based on FIG. 16 or FIG. The same parts as those described in the first embodiment of the present invention are denoted by the same reference numerals, and description thereof is also omitted.

  In the first embodiment, if a label is issued from the label printer 5 connected to the client terminal 4, the label is affixed to the product and the product is handled as being properly shipped. . In this embodiment, the label bar code of the label attached to the product is read when the product is shipped, and the product is handled as being properly shipped when the tag bar code is read. Is.

  FIG. 16 is an explanatory diagram illustrating a state where the tag barcode BC of the label L attached to the product O is read. As shown in FIG. 16, in the present embodiment, the label barcode BC of the label L attached to the product O is read by the barcode scanner BS when the product is shipped. The barcode scanner BS that has read the tag barcode BC in this way transmits the reading result to the headquarter server 3. Here, a reading result transmitting means is realized. The transmission of the reading result from the barcode scanner BS to the headquarter server 3 may be performed via the client terminal 4 via the Internet 2 or directly transmitted from the barcode scanner BS to the headquarter server 3. It may be.

  FIG. 17 is a schematic diagram showing the data structure of the order data stored in the order data file 25. As shown in FIG. 17, in addition to the order product name, the identification number indicating the order product, user information (user name, address, telephone number), label issuance status, information on whether or not the product has been shipped includes order data. (Tag print data).

  With such a configuration, the headquarter server 3 receives the reading result of the label barcode BC of the label L attached to the product O from the barcode scanner BS and stores it in the order data file 25. Here, reading result storage means is realized.

  By doing so, the tag barcode BC of the label L affixed to the product O is transferred to the barcode scanner BS when the shipment status of the product from the client terminal 1 installed at the user's site to the headquarter server 3 is confirmed. If it is read and transmitted to the headquarters server 3, the user who ordered the product can confirm that the product has actually been shipped.

  As described above, in the present embodiment, the label barcode BC attached to the label L, which is a label at the time of shipment of goods, is read by the barcode scanner BS, and the symbol reading result is stored in the storage unit of the headquarter server 3. The client terminal 1 accessing the headquarter server 3 is notified of the issue status and the product shipment status according to the symbol reading result. Thereby, the user who ordered the product can confirm that the product was actually shipped.

  In each embodiment, the label printer 5 is connected to the shipping server 4 and the label based on the order of the product from the user is issued from the label printer 5. However, the present invention is not limited to this. For example, a general printer (laser printer or the like) may be connected to the shipping server 4 and a shipping instruction or delivery slip may be issued based on the ordering of products from the user.

  In each embodiment, a PC (Personal Computer) is applied as the client terminal 1 installed at the user. However, the present invention is not limited to this, and a mobile phone or a PDA (Personal Digital Assistants) is used. An information terminal or the like may be used.

  Further, in each embodiment, the Web application is stored in the storage device 23 such as the HDD, and the HTML file and the CGI program are stored in the storage device 24 such as the HDD. However, the present invention is not limited to this. Magnetic storage medium such as disk, magnetic tape, etc., magneto-optical storage medium such as MO, CD, CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-R, DVD-RAM In addition, various types of media such as optical storage media such as DVD-RW and DVD + RW and semiconductor memory may be used as the storage media. Various optical storage media such as CD-ROM and DVD-ROM, various magneto-optical storage media, and various magnetic storage media such as a flexible disk are fixedly provided in the headquarter server 3. However, it is possible to perform various processes by reading the program using various program reading devices (CD-ROM drive or the like) adapted to each medium.

1 is a system configuration diagram schematically showing an overall configuration of a product ordering system according to a first embodiment of the present invention. It is a block diagram which shows the electrical connection of each part of a headquarters server. It is a block diagram which shows the electrical connection of each part of a client terminal. It is the flowchart which showed the screen image displayed on the display part of a client terminal at the time of ordering goods. It is a flowchart which shows the flow of a process by a CGI program (CGI1). It is a schematic diagram which shows the data structure of the user data stored in the user data file. It is a schematic diagram which shows the data structure of the product image data stored in the product image file. It is a flowchart which shows the flow of a process by a CGI program (CGI2). It is a schematic diagram which shows the data structure of the order data stored in the order data file. It is a flowchart which shows roughly the flow of the label issuing process in a client terminal. It is a flowchart which shows the operation | movement in the headquarters server in the case of a label issuing process. It is a front view which shows the display content displayed on the display part of a client terminal. It is explanatory drawing which shows the label issued from a label printer. It is the flowchart which showed the screen image displayed on the display part of a client terminal at the time of confirming the dispatch condition of goods. It is a flowchart which shows the flow of a process by a CGI program (CGI3). It is explanatory drawing which shows a mode that the label tag barcode of the label affixed on the goods of 2nd implementation of this invention is read. It is a schematic diagram which shows the data structure of the order data stored in the order data file.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1,4 ... Client terminal, 2 ... Communication network, 3 ... Web server, 25 ... Memory | storage part, 100 ... Merchandise ordering system, BC ... Tag code symbol, BS ... Scanner, L ... Tag

Claims (5)

In a product ordering system having a Web server accessible from a client terminal through a communication network,
Order receiving means for receiving an order for a product from a user via the client terminal accessing the Web server;
Order data generating means for generating order data associating the ordered product received by the order receiving means with information about the user who ordered the product;
Tag printing data providing means for providing the order data generated by the order data generating means as tag printing data to the client terminal that has accessed the Web server;
A tag issue means for sending the tag print data from the client terminal to which the tag print data is provided by the tag print data providing means to a printer usable by the client terminal, and printing and issuing the tag;
An issuance status status notifying means for notifying the web server of an issuance status status returned from the printer after the tag printing is issued by the printer;
Issuance status receiving means for receiving the issuance status status notified by the issuing status status notifying means;
Issuance status storage means for storing the issuance status status received by the issuance status status receiving means in a storage unit;
Shipping status notifying means for notifying the client terminal that has accessed the Web server of a product shipping status corresponding to the issue status stored in the storage unit;
A product ordering system characterized by comprising: A reading result transmission means for reading a tag code symbol attached to the tag at the time of product shipment with a scanner and transmitting the symbol reading result to the Web server;
Reading result storage means for storing the symbol reading result transmitted by the tag reading result transmission means in a storage unit;
Comprising
The shipping status notifying means notifies the client terminal that has accessed the Web server of the issue status and the product shipping status according to the symbol reading result stored in the storage unit.
The product ordering system according to claim 1, wherein: Bill issuing data generating means for generating the order data stored in the storage unit as bill issuing data based on the issuing status status stored in the storage unit;
A bill issuing means for sending the bill issuing data generated by the bill issuing data generating means to a printer usable by the Web server, and printing and issuing the bill;
The product ordering system according to claim 1 or 2, further comprising: In a server computer accessible from a client terminal through a communication network,
Order accepting means for accepting orders for products from users accessed via the client terminal;
Order data generating means for generating order data associating the ordered product received by the order receiving means with information about the user who ordered the product;
Tag tag print data providing means for providing the order data generated by the order data generating means as tag label print data to the accessed client terminal;
An issuance status receiving means for receiving an issuance status returned from the printer after issuance of a tag printing based on the tag printing data by a printer usable by the client terminal;
Issuance status storage means for storing the issuance status status received by the issuance status status receiving means in a storage unit;
Shipping status notifying means for notifying the client terminal that has accessed the product shipping status according to the issue status status stored in the storage unit;
A server computer comprising: In a product shipping status notification method used in a product ordering system having a Web server accessible from a client terminal through a communication network,
An order receiving step of receiving an order for a product from a user via the client terminal that has accessed the Web server;
An order data generating step for generating order data in which the ordered product received in the order receiving step is associated with information on the user who has ordered the product;
A tag printing data providing step of providing the order data generated by the order data generating step as tag tag printing data to the client terminal that has accessed the Web server;
A tag issue step of sending the tag print data from the client terminal to which the tag print data is provided by the tag print data providing step to the printer usable by the client terminal and printing the tag;
An issuance status notification step of notifying the web server of an issuance status returned from the printer after issuance of tag printing by the printer;
An issuance status receiving step for receiving the issuance status status notified by the issuance status status notifying step;
An issuance status status storing step for storing the issuance status status received in the issuance status status receiving step in a storage unit;
A shipping status notifying step of notifying the client terminal that has accessed the Web server of a product shipping status corresponding to the issue status stored in the storage unit;
A product shipment status notification method comprising:

Images