CROSS-REFERENCE TO RELATED APPLICATIONSThis application is a continuation of U.S. patent application Ser. No. 16/042,315, filed on Jul. 23, 2018, which is a continuation of U.S. patent application Ser. No. 15/477,323, filed on Apr. 3, 2017, now U.S. Pat. No. 10,032,154, issued on Jul. 24, 2018, which is a continuation of U.S. patent application Ser. No. 14/988,406, filed on Jan. 5, 2016, now U.S. Pat. No. 9,619,976, issued on Apr. 11, 2017, which is based upon and claims the benefit of priority from Japanese Patent Application No. 2015-002392, filed Jan. 8, 2015, Japanese Patent Application No. 2015-003431, filed Jan. 9, 2015, Japanese Patent Application No. 2015-105761, filed May 25, 2015, and Japanese Patent Application No. 2015-239946, filed Dec. 9, 2015; the entire contents of all of these applications are incorporated herein by reference.
FIELDEmbodiments described herein generally relate to a method for processing a purchase transaction using a plurality of transaction systems.
BACKGROUNDIn the related art, a self-registration system is known as a system that can simplify a purchase transaction. In the self-registration system, a customer launches a self-registration program on a hand-held computing device and registers data of commodities to be purchased through the computing device. As the data registered are transmitted to a point-of-sale (POS) terminal, a process required to complete the transaction at the POS terminal can be simplified.
In the related art, an electronic receipt system is also known as a system that can digitalize contents of a purchase transaction. In the electronic receipt system, a customer launches an electronic receipt program on a computing device and sends a request for electronic receipts related to purchase transactions made by the customer.
Usually, for each of the above computer-based commerce systems, a customer needs a customer (user) ID to log into the system and an authentication process of the system is separately established. It would be desirable if a plurality of computer-based commerce systems can be used in a single purchase transaction in a more convenient manner.
DESCRIPTION OF THE DRAWINGSFIG. 1 schematically illustrates a retail store having a commodity sales processing system according to a first embodiment.
FIG. 2 is a block diagram of the commodity sales processing system.
FIG. 3 is a block diagram of a POS apparatus in the commodity sales processing system.
FIG. 4 is a block diagram of a portable information terminal in the commodity sales processing system.
FIG. 5 is a block diagram of a support server in the commodity sales processing system.
FIG. 6 schematically illustrates a data structure of a commodity transaction file.
FIG. 7 is a block diagram of an electronic receipt server in the commodity sales processing system.
FIG. 8 schematically illustrates a data structure of an electronic receipt file.
FIG. 9 schematically illustrates a data structure of a linkage table.
FIG. 10 is a flowchart illustrating a main procedure of a processing carried out by a processor of the portable information terminal according to a self-registration terminal program.
FIG. 11 is a flowchart illustrating a main procedure of a process carried out by a processor of the support server according to a self-registration terminal program.
FIG. 12 is a flowchart illustrating a main procedure of a process carried out by a processor of the POS apparatus according to a control program when the POS apparatus receives a settlement request.
FIG. 13 is a flowchart illustrating a main procedure of a process carried out by a processor of the electronic receipt server according to an electronic receipt server program.
FIG. 14 is a block diagram of a portable information terminal according to a second embodiment.
FIG. 15 schematically illustrates a data structure of a commodity transaction file according to the second embodiment.
FIG. 16 is a flowchart illustrating a part of a process carried out by a processor of the portable information terminal according to a self-registration terminal program in the second embodiment.
FIG. 17 is a block diagram of a POS apparatus according to a third embodiment.
FIG. 18 is a flowchart illustrating a main procedure of a process carried out by a processor of the POS apparatus according to a control program in the third embodiment when the POS apparatus receives a settlement request.
FIG. 19 is a flowchart illustrating a procedure of a process carried out by a processor of the portable information terminal according to a fourth embodiment.
FIG. 20 is a flowchart illustrating a procedure of a process carried out by a processor of the support server according to the fourth embodiment.
FIG. 21 is a flowchart illustrating a procedure of a process carried out by a processor of the POS apparatus according to the fourth embodiment.
FIG. 22 is a flowchart illustrating a procedure of a process carried out by a processor of an electronic receipt server according to the fourth embodiment.
FIG. 23 is a flowchart illustrating a procedure of a process carried out by a processor of a portable information terminal according to the fourth embodiment.
FIG. 24 is a flowchart illustrating a procedure of a process carried out by a processor of a portable information terminal according to the fourth embodiment.
FIG. 25 is a flowchart illustrating a procedure of a process carried out by a processor of an electronic receipt server according to the fourth embodiment.
FIGS. 26-28 each schematically illustrate a screen displayed on a touch panel of the portable information terminal according to the fourth embodiment.
FIG. 29 schematically illustrates a data structure of a commodity transaction file according to a fifth embodiment.
FIG. 30 is a flowchart illustrating a part of a process carried out by a processor of the portable information terminal according to the fifth embodiment.
DETAILED DESCRIPTIONAccording to an embodiment, a method for processing a purchase transaction of a customer at a store using a plurality of transaction systems connected over a network, the transaction systems including a store server, a user computing device in which the customer has installed a self-registration program, and an electronic receipt server, includes the steps of: launching the self-registration program in the user computing device; capturing with the user computing device, an image of a product code identifier placed on a product to be purchased; generating a transaction file with respect to a transaction to be made by a customer at the store, the transaction file containing a product code of the product to be purchased, the product code being transmitted from the user computing device when the user computer device captures the image of the product code identifier placed on the product, a first user ID of the customer that was created for the customer when the customer installed the self-registration program on the user computing device, and an indicator of whether or not the customer has opted in to receive electronic receipts; generating an electronic receipt for the transaction based on the transaction file; storing a conversion table containing the first user ID for the self-registration, in association with a second user ID of the customer that was created for the customer when the customer opted in to receive electronic receipts; converting the first user ID contained in the transaction file to the second user ID based on the conversion table, when the indicator indicates that the customer has opted in to receive electronic receipts; and storing in a storage device by the electronic receipt server, the electronic receipt in association with the second user ID converted from the first user ID. The electronic receipt server transmits the stored electronic receipt over the network in response to a request received over the network from a computing device associated with the second user ID.
Embodiments of a commodity sales processing system in which a self-registration system is associated with an electronic receipt system, are described below with reference to the accompanying drawings.
First Embodiment[Commodity Sales Processing System]
FIG. 1 schematically illustrates aretail store100 having a commodity sales processing system, andFIG. 2 is a block diagram of the commodity sales processing system.
As shown inFIG. 1 andFIG. 2, the commodity sales processing system includes a facing-type POS (Point Of Sales)apparatus10, a self-service POS apparatus20, and arelay device30 in theretail store100. Further, as shown inFIG. 2, the commodity sales processing system includes astore server40, a self-registration support server (hereinafter referred to as a support server)50, and arouter60 in theretail store100. Moreover, in theretail store100, the commodity sales processing system includes a LAN (Local Area Network)70 with which thePOS apparatuses10 and20, therelay device30, thestore server40, thesupport server50, and therouter60 are connected. TheLAN70 may be a wired LAN or a wireless LAN. Therouter60 relays data communication between theLAN70 and anetwork200.
In the commodity sales processing system,POS apparatuses10,20, and thesupport server50 function as a commodity sales processing apparatus. The support server includes a registration unit having a commodity detector configured to detect commodity codes input by customers, and thePOS apparatuses10,20 function as a settlement unit having an input device for inputting sales data.
Theelectronic receipt server80 is connected with thenetwork200. Theelectronic receipt server80 also stores electronic receipt data, i.e., electronic receipts. By accessing theelectronic receipt server80 from aninformation processing apparatus210 connected with thenetwork200, a customer can browse his or her electronic receipts on theinformation processing apparatus210. Theinformation processing apparatus210 may be a personal computer, a smart phone, a mobile phone, a tablet terminal, or the like. Thenetwork200 is, for example, the Internet or a mobile communication network.
Although only the commodity sales processing system of one store is shown inFIG. 2, the commodity sales processing systems of a plurality ofretail stores100 may be connected with thenetwork200. Moreover, the commodity sales processing systems of theretail stores100 may share theelectronic receipt server80.
[POS Apparatus (Commodity Sales Data Processing Apparatus)]
As shown inFIG. 1, the facing-type POS apparatus10 located at acheckout counter2 in acheckout region1 is operated by acashier3. ThePOS apparatus10 includes ascanner11 located on thecheckout counter2. Thescanner11 is also operated by thecashier3. Thecashier3 faces acustomer4 waiting to check out across thecheckout counter2. Thecashier3 reads, with thescanner11, a barcode affixed on acommodity5 to be purchased by thecustomer4. Thescanner11 sends barcode data obtained by reading the barcode to thePOS apparatus10. ThePOS apparatus10 specifies thecommodity5 according to the barcode data sent from thescanner11 and registers sales quantities, the sales amount and the like of thecommodity5, in a transaction region in memory. Further, thePOS apparatus10 displays the commodity name, the sales quantities, the sales amount and total amount of thecommodities5 registered in the transaction region, on a display13. The display13 includes adisplay13afor operator and adisplay13bfor customer.
If thecommodities5 purchased by thecustomer4 are all registered, then thecashier3 inputs payment data through the input device of thePOS apparatus10. For example, thecashier3 operates akeyboard12 to input an amount paid by the customer. ThePOS apparatus10 executes a settlement process on the commodity transaction with thecustomer4 according to the payment data. During the settlement process, thePOS apparatus10 drives aprinter14 to issue a receipt (hereinafter referred to as a paper receipt) by printing the details of the commodity transaction on receipt paper. If thecustomer4 is an electronic receipt member (subscriber), then the issuing of the paper receipt may be optional.
The self-service POS apparatus20 is located at thecheckout region1 for thecustomer4 to operate. ThePOS apparatus20 has ascanner21, atouch panel22, an automaticchange dispensing machine23, and aprinter24 for printing a receipt. Thecustomer4 standing in front of thePOS apparatus20 operates thescanner21 to read the barcode affixed on acommodity5 to be purchased by thecustomer4. ThePOS apparatus20 specifies thecommodity5 according to the barcode read by thescanner21 and registers the sales quantities, the sales amount, and the like of thecommodity5 in a transaction region. Further, thePOS apparatus20 displays the commodity name, the sales quantities, the sales amount, and the total amount ofcommodities5 registered in the transaction region, on thetouch panel22.
After the registration processing of thesales commodities5 is completed, thecustomer4 inputs payment data through the input device of thePOS apparatus20. For example, thecustomer4 operates thetouch panel22 to select a payment method. If a cash payment is selected, thecustomer4 puts cash into the automaticchange dispensing machine23. If an electronic money payment is selected, thecustomer4 directs an electronic money card to a reader/writer (not shown). ThePOS apparatus20 carries out a settlement process for the commodities transaction for thecustomer4 according to the payment data. During the settlement process, thePOS apparatus20 drives theprinter24 to issue a paper receipt on which the content of the commodity transaction is printed. If thecustomer4 is an electronic receipt member (subscriber), then the issuing of the paper receipt may be optional.
Instead of or in addition to the foregoing payment methods, other payment methods such as credit card payment and merchandise coupon payment may be included in the payment methods available in thePOS apparatus20. Instead or in addition to cash payment, other payment methods such as electronic money payment, credit card payment, or merchandise coupon payment can also be included in the payment methods available in thePOS apparatus10.
ThePOS apparatus10 or20 is referred to as a commodity sales data processing apparatus.
FIG. 3 is a block diagram of thePOS apparatus10 or20. ThePOS apparatus10 or20 includes aprocessor101, amain memory102, anauxiliary storage device103, acommunication interface104 and an I/O (Input/Output)interface105. Theprocessor101 is connected with themain memory102, theauxiliary storage device103, thecommunication interface104 and the I/O interface105 via asystem transmission line106 including an address bus line, a data bus line, a control signal line and the like.
ThePOS apparatus10 or20 comprises a computer including theprocessor101, themain memory102, theauxiliary storage device103, and thesystem transmission line106 connecting these sections.
Theprocessor101 acts as a central component of the computer. Theprocessor101 controls each section to perform the various functions of thePOS apparatus10 or20 according to an operating system or application program.
Themain memory102 acts as main memory of the computer. Themain memory102 includes a nonvolatile memory unit and a volatile memory unit. Themain memory102 stores an operating system or application program in the nonvolatile memory unit. Further, in some cases, themain memory102 also stores data required by theprocessor101 to control each component in the nonvolatile or volatile memory unit. Themain memory102 uses the volatile memory unit as a work area for theprocessor101 to rewrite data properly. The work area includes a transaction region. The transaction region is a region in which the sales data of the commodities sold in a commodity transaction and the settlement data of the commodity transaction are stored.
Theauxiliary storage device103 acts as auxiliary memory of the computer. Theauxiliary storage device103 may be, for example, an EEPROM (Electric Erasable Programmable Read-Only Memory), a HDD (hard disk drive) or an SSD (solid state drive). Theauxiliary storage device103 persistently stores the data used by theprocessor101 to carry out various processes or the data generated in the process carried out by theprocessor101. Theauxiliary storage device103 may also store the foregoing operating system and application program.
Thecommunication interface104 is an interface for carrying out data communication between thestore server40 and thesupport server50 which are connected with each other via theLAN70.
The I/O interface105 is an interface for data communication among various input/output devices. In the case of facing-type POS apparatuses10, thescanner11, thekeyboard12, the display foroperator13a, the display forcustomer13b, and theprinter14 are connected with the I/O interface105. In the case of the self-service POS apparatus20, thescanner21, thetouch panel22, the automaticchange dispensing machine23, and theprinter24 are connected with the I/O interface105.
No specific limitations are given to the number of the facing-type POS apparatuses10 or the self-service POS apparatuses20 installed in aretail store100. A proper number of facing-type POS apparatuses10 and a proper number of self-service POS apparatuses20 are installed in theretail store100 according to the scale or the layout inside theretail store100. Further, it is not necessary to include both of the facing-type POS apparatuses10 and the self-service POS apparatuses20. Instead, only one of the facing-type POS apparatus10 and the self-service POS apparatus20 may be installed at thecheckout region1 for the commodity sales processing system.
The POS ID of each of thePOS apparatuses10 and20 is stored in theauxiliary storage device103. The POS ID of each of thePOS apparatuses10 and20 may also be stored in themain memory102. The POS ID is the fixed identification information of each of thePOS apparatuses10 and20. The POS ID of each of thePOS apparatuses10 and20 is also unique. Thestore server40 and thesupport server50 identify each of thePOS apparatuses10 and20 connected with theLAN70 according to the POS ID of thePOS apparatus10 or20.
Each of thePOS apparatuses10 and20 is marked with abarcode7 representing the POS ID thereof. For example, as shown inFIG. 1, in the case of the facing-type POS apparatuses10, abarcode7 is marked on a surface of thescanner11 opposite to the side where thecashier3 operates thescanner11, that is, on the side of thecustomer4. In the case of the self-service POS apparatus20, thebarcode7 is marked on the front side of the housing of the self-service POS apparatus20 opposite to thecustomer4. Further, the position of thebarcode7 shown inFIG. 1 is only an example. No specific limitations are given to the position of thebarcode7. In addition, thebarcode7 may be replaced by a two-dimensional code.
[Store Server]
As shown inFIG. 2, thestore server40 includes acommodity database41. In thecommodity database41, the commodity data, for example, the commodity name and the price, of each commodity sold in theretail store100 is stored in association with the commodity code thereof. The commodity code is unique to eachcommodity5. Eachcommodity5 has a barcode of the commodity displayed thereon. By reading the barcode using thescanner11 or21, thePOS apparatus10 or20 registers the sales data of thecommodity5 in the transaction region.
Thestore server40 collects, via theLAN70, the sales data of eachcommodity5 registered by each ofPOS apparatuses10 and20. Then, thestore server40 sorts the collected sales data by commodity, by time range and the like. That is, thePOS apparatus10 or20 and thestore server40 function as a well-known POS system.
[Relay Device]
Therelay device30 conforms to, for example, a wireless communication standard such as Wi-Fi (Wireless Fidelity). One or more of therelay devices30 are located in the retail store so that the wireless communication region of therelay devices30 substantially covers the entire region of asales floor6 and thecheckout region1 in theretail store100. Therelay device30 sends or receives data through wireless communication, using one or moreportable information terminals400 existing in the wireless communication region. No specific limitations are given to the number of therelay devices30. A proper number ofrelay devices30 may be installed in theretail store100 according to the scale or the internal layout of theretail store100.
[Portable Information Terminal]
FIG. 4 is a block diagram of theportable information terminal400. Theportable information terminal400 includes aprocessor401, amain memory402, anauxiliary storage device403, atouch panel404, acamera unit405, and awireless unit406. Theprocessor401 is connected with themain memory402, theauxiliary storage device403, thetouch panel404, thecamera unit405, and thewireless unit406 via asystem transmission line407 including an address bus line, a data bus line, a control signal line, and the like.
Theportable information terminal400 comprises a computer including theprocessor401, themain memory402, theauxiliary storage device403 and thesystem transmission line407 connecting these sections.
Theprocessor401 acts as a main component of the computer. Theprocessor401 controls each section to perform the functions of theportable information terminal400 according to an operating system or application program.
Themain memory402 acts as main memory of the computer. Themain memory402 includes a nonvolatile memory unit and a volatile memory unit. Themain memory402 stores an operating system or application program in the nonvolatile memory unit. Further, themain memory402 also stores the data required by theprocessor401 to control each section in the nonvolatile or volatile memory unit. Themain memory402 uses the volatile memory unit as a work area for theprocessor401 to rewrite data properly.
Theauxiliary storage device403 acts as auxiliary memory of the computer. Theauxiliary storage device403 is, for example, an EEPROM. A HDD and an SSD may also be used as theauxiliary storage device403. Theauxiliary storage device403 persistently stores the data used by theprocessor401 to carry out various processes or the data generated in the process carried out by theprocessor401. Theauxiliary storage device403 may also store the foregoing operating system and application program.
Thetouch panel404 functions as the input device and a display device of theportable information terminal400. An icon for starting the foregoing application program may be displayed on thetouch panel404.
Thecamera unit405 has a resolution that is sufficient to recognize a barcode. Thewireless unit406 sends data to or receives data from therelay device30 through wireless communication. For example, among portable information processing apparatuses such as smart phones, mobile phones and tablet terminals, an information processing apparatus having thecamera unit405 and thewireless unit406 functions as theportable information terminal400.
By executing a self-registration terminal program P1, theportable information terminal400 with such a structure functions as an information terminal corresponding to a self-registration system. The self-registration system can perform the registration process in place of thePOS apparatus10 or20 by enabling thecustomer4 to register data of a sales commodity through the information terminal. The settlement process of the commodity purchase is executed by thePOS apparatus10 or20 in the conventional manner.
When the processor executes the self-registration terminal program P1, theportable information terminal400 functions as an information terminal corresponding to the self-registration system. The self-registration terminal program P1 is stored in theauxiliary storage device403. Further, a self-registration management region W1 is formed in theauxiliary storage device403 of theportable information terminal400.
By executing an electronic receipt terminal program P2, theportable information terminal400 functions as an information terminal corresponding to an electronic receipt system. The electronic receipt system is a system which formats the information of a receipt (receipt data) generated by each of thePOS apparatuses10 and20, stores the electronic receipt data in theelectronic receipt server80, such that the receipt data can be retrieved by theinformation processing apparatus210 via thenetwork200. That is, the portable terminal containing the electronic receipt terminal program P2 functions as theinformation processing apparatus210.
When theprocessor401 executes the electronic receipt terminal program P2, theportable information terminal400 functions as an information terminal corresponding to the electronic receipt system. The electronic receipt terminal program P2 is stored in theauxiliary storage device403. Further, an electronic receipt management region W2 is formed in theauxiliary storage device403 of theportable information terminal400.
[Support Server (Commodity Data Input Support Server)]
FIG. 5 is a block diagram of thesupport server50. Thesupport server50 includes aprocessor501, amain memory502, anauxiliary storage device503, and acommunication interface504. Theprocessor501 is connected with themain memory502, theauxiliary storage device503, and thecommunication interface504 via asystem transmission line505 including an address bus line, a data bus line, a control signal line, and the like.
Thesupport server50 comprises a computer having theprocessor501, themain memory502, theauxiliary storage device503, and thesystem transmission line505 connecting these sections.
Theprocessor501 acts as a main component of the computer. Theprocessor501 controls each section to perform the functions of thesupport server50 according to an operating system or application program.
Themain memory502 acts as main memory of the computer. Themain memory502 includes a nonvolatile memory unit and a volatile memory unit. Themain memory502 stores an operating system or application program in the nonvolatile memory unit. Further, themain memory502 may also store the data needed by theprocessor501 to control each section in the nonvolatile or volatile memory unit. Themain memory502 uses the volatile memory unit as a work area for theprocessor501 to rewrite data properly.
Theauxiliary storage device503 acts as auxiliary memory of the computer. Theauxiliary storage device503 is, for example, an EEPROM, a HDD, or an SSD. Theauxiliary storage device503 persistently stores the data used by theprocessor501 to carry out various processes or the data generated by the process carried out by theprocessor501. Theauxiliary storage device503 may also store the foregoing operating system and application program.
Thecommunication interface504 is an interface for data communication between thestore server40 and each ofPOS apparatuses10 and20 which are connected with each other via theLAN70.
Thesupport server50 having the foregoing structure functions as a commodity data input support server that supports a user input of commodity data related to a self-registration process, and has a self-registration server program P3 in theauxiliary storage device503. Further, thesupport server50 forms a store information region W3 and a transaction file region W4 in theauxiliary storage device503.
The self-registration server program P3 stays in thesupport server50. Through thesupport server50 executing the self-registration server program P3 in cooperation with theportable information terminal400 executing the self-registration terminal program P1, thecustomer4 can carry out a self-registration process for commodities to be purchased.
The store information region W3 is a region for storing information relating to the retail store (seller)100, in which thesupport server50 is arranged, for example, seller information such as the name of a store.
The transaction file region W4 is a region for storing acommodity transaction file510 having a data structure shown inFIG. 6. Thecommodity transaction file510 is formed for eachcustomer4 executing a self-registration process. A plurality of commodity transaction files510 corresponding to a plurality ofcustomers4 can be synchronously stored in the transaction file region W4.
The data in thecommodity transaction file510 consists of a self-registration ID, store information, an association flag F, one or more commodity sales data, and a total sales data.
The self-registration ID (first ID) is a unique code for identifying acustomer4 who performs a self-registration operation. That is, the self-registration ID (first ID) is an ID of the user of theportable information terminal400. A self-registration ID is set for eachcustomer4 when eachcustomer4 installs the self-registration terminal program P1 in theportable information terminal400. The self-registration ID is used as an authentication ID for acustomer4 to log into thesupport server50 from theportable information terminal400. If thecustomer4 logs into thesupport server50, then the self-registration ID is stored in the self-registration management region W1 of theportable information terminal400. Eachcustomer4 is assigned an optional but unique self-registration ID.
The association flag F is 1-bit data indicating whether or not the self-registration system is associated with the electronic receipt system. Acustomer4 who installs the self-registration terminal program P1 and the electronic receipt terminal program P2 in theportable information terminal400 can make the self-registration system become associated with the electronic receipt system. That is, thecustomer4 can download details of the transaction for the commodities self-registered to theportable information terminal400 as an electronic receipt and browse the details of the commodity transaction. Whether or not the self-registration system is associated with the electronic receipt system can be optionally set by thecustomer4. If the association of the self-registration system with the electronic receipt system is set by thecustomer4, then an association flag F is set in the self-registration management region W1 of theportable information terminal400. If the association is not set, then the association flag F is not set therein. Thecustomer4 can change the setting of the association flag F by operating theportable information terminal400.
Further, thesupport server50 can use, for example, a conventional server device or a conventional computing device as the basic hardware thereof. Thesupport server50 may not initially contain the self-registration server program P3 in theauxiliary storage device503 thereof, and the self-registration server program P3 may be installed later. In this case, the self-registration server program P3 is delivered by being recorded in a removable recording medium such as a magnetic disc, a magneto-optical disc, a compact disc, or a semiconductor memory, or by being downloaded through a network. Moreover, in this case, the self-registration server program P3 is written into theauxiliary storage device503 through an operation of the user.
[Electronic Receipt Server]
FIG. 7 is a block diagram of theelectronic receipt server80. Theelectronic receipt server80 includes aprocessor801, amain memory802, anauxiliary storage device803 and acommunication interface804. Theprocessor801 is connected with themain memory802, theauxiliary storage device803, and thecommunication interface804 via asystem transmission line805 including an address bus line, a data bus line, a control signal line, and the like.
Theelectronic receipt server80 comprises a computer having theprocessor801, themain memory802, theauxiliary storage device803, and asystem transmission line805 connecting these sections.
Theprocessor801 acts as a main component of the computer. Theprocessor801 controls each section to perform the functions of theelectronic receipt server80 according to an operating system or application program.
Themain memory802 acts as main memory of the computer. Themain memory802 includes a nonvolatile memory unit and a volatile memory unit. Themain memory802 stores an operating system or application program in the nonvolatile memory unit. Further, themain memory802 may also store the data required by theprocessor801 to control each component in the nonvolatile or volatile memory unit. Themain memory802 uses the volatile memory unit as a work area for theprocessor801 to rewrite data properly.
Theauxiliary storage device803 acts as auxiliary memory of the computer. Theauxiliary storage device803 is, for example, an EEPROM, an HDD, or an SSD. Theauxiliary storage device803 persistently stores the data used by theprocessor801 to carry out various processes or the data resulting from the process carried out by theprocessor801. Theauxiliary storage device803 may store also the foregoing operating system and application program.
Thecommunication interface804 is an interface for the data communication between thestore server40 and theinformation processing apparatus210 which are connected with each other via thenetwork200.
Theelectronic receipt server80 having this structure contains an electronic receipt server program P4 in theauxiliary storage device803. Further, theelectronic receipt server80 has an electronic receipt region W5 and a linkage table region W6 in theauxiliary storage device803.
The electronic receipt server program P4 is stored in theelectronic receipt server80. Through execution of the electronic receipt server program P4 by theelectronic receipt server80 and the electronic receipt terminal program P2, theportable information terminal400 can display an electronic receipt thereon.
The electronic receipt region W5 is a region for storing anelectronic receipt file810 having a data structure shown inFIG. 8. Theelectronic receipt file810 is formed for each commodity transaction for which an electronic receipt is generated. A plurality of electronic receipt files810 corresponding to a plurality of commodity transactions can be simultaneously stored in the electronic receipt region W5.
The data in theelectronic receipt file810 consists of an electronic receipt ID, a store name, a transaction date and time and a total amount, which represent simplified data of an electronic receipt, and the actual data of the electronic receipt. Further, the simplified data are not limited to the combination of a store name, a transaction date and time, and a total amount. For example, the simplified data may be a combination of a store name and a transaction date and time, or the combination of a transaction date and time, and a total amount. Further, other items different from a store name, a transaction date and time, and a total amount may also be contained in the simplified data.
The electronic receipt ID (second ID) is a unique code for identifying acustomer4 using the electronic receipt system. To use the electronic receipt system, acustomer4 carries out a member registration operation with respect to a system manager in advance. Thecustomer4 who completed the member registration receives a fixed electronic receipt ID assigned by the system manager. The electronic receipt ID is used as an authentication ID for thecustomer4 to log into theelectronic receipt server80 from theportable information terminal400. If thecustomer4 logs into theelectronic receipt server80 from theportable information terminal400, an electronic receipt ID is stored in the electronic receipt management region W2 of theportable information terminal400. Eachcustomer4 who completed the member registration receives a unique electronic receipt ID. That is, the electronic receipt ID (second ID) is an ID used by the customer to receive an electronic receipt.
The linkage table region W6 is a region for storing a linkage table820 having a data structure shown inFIG. 9. The linkage table820 stores the electronic receipt ID of acustomer4 who sets the association of the self-registration system with the electronic receipt system in association with a self-registration ID. That is, when thecustomer4 sets the association of the self-registration system with the electronic receipt system, the electronic receipt ID of thecustomer4 is stored in the linkage table820 in association with a self-registration ID.
Here, theelectronic receipt server80 can be set up using, for example, a conventional server device or computer device as the basic hardware thereof. Theelectronic receipt server80 may not initially contain the electronic receipt server program P4 in theauxiliary storage device803 thereof, and the electronic receipt server program P4 may be installed later. In this case, the electronic receipt server program P4 is recorded in a removable recording medium such as a magnetic disc, a magneto-optical disc, a compact disc, or a semiconductor memory, or by being downloaded through a network. Moreover, in this case, the electronic receipt server program P4 is written into theauxiliary storage device803 through an operation of the user.
[Operation of Commodity Sales Processing System]
Next, an operation carried out by the commodity sales processing system when the self-registration system is associated with the electronic receipt system is described below with reference to flowcharts ofFIG. 10-FIG. 13.FIG. 10 is a flowchart illustrating a main procedure of a process carried out by theprocessor401 of theportable information terminal400 according to the self-registration terminal program P1.FIG. 11 is a flowchart illustrating main operation of a process carried out by theprocessor501 of thesupport server50 according to the self-registration server program P3.FIG. 12 is a flowchart illustrating a main procedure of a process carried out by theprocessor101 of thePOS apparatus10 or20 according to a control program when the POS apparatus receives a settlement request (described below).FIG. 13 is a flowchart illustrating main procedures of a process carried out by theprocessor801 of anelectronic receipt server80 according to the electronic receipt server program P4. Here, the content of each processing described below with reference toFIG. 10-FIG. 13 is merely an example, and various other processes that can achieve the same structure can be properly performed.
Before shopping in theretail store100, thecustomer4 operates thetouch panel404 of theportable information terminal400 to start the self-registration terminal program P1. That is, thecustomer4 touches the icon to launch the self-registration terminal program P1, displayed on thetouch panel404. If the self-registration terminal program P1 is started, then theprocessor401 of theportable information terminal400 starts the process shown inFIG. 10.
First, theprocessor401 determines whether or not the customer has logged into the support server50 (Act1). If the self-registration terminal program P1, after being launched, is ended without being logged out, the login state of the customer is maintained. A self-registration ID serving as an authentication ID is stored in the self-registration management region W1 during the login state.
If the customer has not logged into the support server50 (No in Act1), theprocessor401 displays a login screen on the touch panel404 (Act2). Acustomer4 logs in by inputting a self-registration ID on the login screen. Thecustomer4 may input a self-registration ID and a password.
When the customer logs in, theprocessor401 wirelessly sends login information including the self-registration ID. The login information is received by therelay device30 and transmitted therefrom to thesupport server50 via theLAN70. Thesupport server50 authenticates the login operation. Then, thesupport server50 notifies theportable information terminal400 of the result of the authentication through a route inverse to that for login information.
Theprocessor401 determines whether or not the login is approved (Act3). If it is determined that the login is not approved (No in Act3), theprocessor401 may perform a login operation again (Act2). If it is determined that the login is approved (Yes in Act3), theprocessor401 stores the self-registration ID used for the login operation in the self-registration management region W1 (Act4).
If the login is approved and the self-registration ID is stored in the self-registration management region W1 or the self-registration ID is stored in the self-registration management region W1 during the login process (Yes in Act1), theprocessor401 extracts the self-registration ID from the self-registration management region W1. Further, theprocessor401 extracts an association flag F in the self-registration management region W1 (Act5). The association flag F is set as ‘1’ if the user sets the association of the self-registration system with the electronic receipt system. The association flag F is set as ‘0’ if the association of the self-registration system with the electronic receipt system is not set.
Theprocessor401 wirelessly sends a registration start command containing the self-registration ID and the association flag F extracted from the self-registration management region W1 (Act6). The registration start command wirelessly sent from thewireless unit406 is received by therelay device30 and transmitted therefrom to thesupport server50 via theLAN70.
As shown inFIG. 11, theprocessor501 of thesupport server50 in which the self-registration server program P3 runs, waits for the registration start command (Act21). If theprocessor501 receives the registration start command sent from theportable information terminal400, theprocessor501 acquires store information from the store information region W3 of the auxiliary storage device503 (Act22). Moreover, theprocessor501 generates acommodity transaction file510 in the transaction file region W4. Then, theprocessor501 stores the self-registration ID and the association flag F that are contained in the registration start command and the store information acquired from the store information region W3 in the commodity transaction file510 (Act23).
Theprocessor501 sends the store information to theportable information terminal400 from where the registration start command is originally sent (Act24). The store information is wirelessly sent from therelay device30 and received by thewireless unit406 of theportable information terminal400 that has sent the registration start command. Further, not limited to the foregoing sequence,Act22 andAct23 may be executed in a reverse sequence. Further, not limited to the foregoing sequence,Act23 andAct24 may be executed in a reverse sequence.
As shown inFIG. 10, theprocessor401 of theportable information terminal400 which has sent the registration start command waits to receive the store information (Act7). If thewireless unit406 receives the store information (Yes in Act7), theprocessor401 displays a registration screen on the touch panel404 (Act8). Further, theprocessor401 drives the camera unit405 (Act9). Here, not limited to the foregoing sequence, Act8 and Act9 may be executed in a reverse sequence.
The registration screen displays, for example, the store information. Detail columns, including columns of ‘commodity name’, ‘price’, and ‘total amount’ are displayed on the registration screen. Information for urging thecustomer4 to carry out a self-registration operation may also be displayed on the registration screen. Thecustomer4 who viewed the registration screen starts shopping on thesales floor6. Then, thecustomer4 photographs the barcode affixed on acommodity5 to be purchased, using thecamera unit405. The photographedcommodity5 is placed in a shopping cart.
Theprocessor401 of theportable information terminal400 waits until a barcode is detected from an image captured by the camera unit405 (Act10). If the barcode is detected (Yes in Act10), theprocessor401 adds the self-registration ID stored in the self-registration management region W1 to the barcode data and wirelessly sends the processed barcode data (Act11). The barcode data containing the self-registration ID sent from thewireless unit406 is received by therelay device30 and transmitted therefrom to thesupport server50 via theLAN70.
As shown inFIG. 11, theprocessor501 of thesupport server50 which has sent the store information to theportable information terminal400 waits until the barcode data are sent from the portable information terminal400 (Act25). If theprocessor501 receives the barcode data containing the self-registration ID (Yes in Act25), theprocessor501 determines whether the barcode data are a commodity code or a POS ID (Act26 and Act27). Abarcode7 of a POS ID is different in the code system from a barcode of a commodity code. Theprocessor501 determines the type of the barcode according to the difference in the code system.
If the barcode data represent a commodity code (Yes in Act26: commodity detector), theprocessor501 accesses thestore server40. Then, theprocessor501 acquires, from thecommodity database41 of thestore server40, commodity data (e.g. commodity name, price) associated with the commodity code (Act28).
Theprocessor501 generates commodity sales data containing a commodity code, a commodity name, a unit price, sales quantities, a sales amount (Act29) after theprocessor501 acquires the commodity data. Moreover, theprocessor501 registers the commodity sales data in thecommodity transaction file510 specified by the self-registration ID attached to the barcode data (Act30: storage module). Further, theprocessor501 sends the commodity sales data to theportable information terminal400 from which the barcode data have been originally sent (Act31). The commodity sales data are wirelessly sent from therelay device30 and received by thewireless unit406 of theportable information terminal400 that has sent the barcode data. Further, not limited to the foregoing sequence,Act30 and Act31 may be executed in a reverse sequence.
Theprocessor501 completing the processing inAct30 and Act31 waits until new barcode data are from the same portable information terminal400 (Act25).
As shown inFIG. 10, theprocessor401 of theportable information terminal400 which sends the barcode data waits until data are sent from the support server50 (Act12). If theprocessor401 receives data from the support server50 (Yes in Act12), theprocessor401 determines whether or not the data are commodity sales data (Act13). If it is determined that the data are commodity sales data (Yes in Act13), theprocessor401 displays the commodity name, the price, and the like of a purchased commodity contained in the commodity sales data in detail columns of the registration screen (Act14). Then, theprocessor401 waits for detection of a new barcode from an image captured by the camera unit405 (Act10).
In this way, theprocessor401 of theportable information terminal400 carries out Act10-Act14 every time acustomer4 photographs the barcode affixed on acommodity5 using thecamera unit405. On the other hand, thesupport server50 carries out Act25-Act31. As a result, acommodity transaction file510 containing the self-registration ID of thecustomer4 is formed in the transaction file region W4 of thesupport server50. Then, the store information and the association flag F as well as the sales data (commodity data) of thecommodity5 purchased by thecustomer4 are stored in thecommodity transaction file510.
Thecustomer4 who has finished shopping in thesales floor6 goes to thecheckout region1 to carry out settlement operation. The settlement may be carried out at thecheckout counter2 or the self-service POS apparatus20. To settle the payment for the commodities to be purchased at thecheckout counter2, thecustomer4 photographs thebarcode7 marked on thescanner11 located on thecheckout counter2 using thecamera unit405. To settle the payment of purchased commodities using the self-service POS apparatus20, thecustomer4 photographs thebarcode7 marked on the housing of thePOS apparatus20 using thecamera unit405.
If thecustomer4 photographs thebarcode7 using thecamera unit405, theprocessor401 of theportable information terminal400 carries out an operation same as the one carried out when thecustomer4 photographs the barcode affixed on acommodity5. That is, if a barcode is detected from an image obtained by the camera unit405 (Yes in Act10), theprocessor401 attaches the self-registration ID stored in the self-registration management region W1 to the barcode data and wirelessly sends the barcode data along with the self-registration ID (Act11). The barcode data containing the self-registration ID sent from thewireless unit406 are received by therelay device30 and transmitted therefrom to thesupport server50 via theLAN70.
On the other hand, if theprocessor501 receives the barcode data containing the self-registration ID (Yes in Act25), theprocessor501 of thesupport server50 determines whether the data are a barcode of a commodity code or abarcode7 of a POS ID (Act26 and Act27). If the data are abarcode7 of a POS ID (Yes in Act27), theprocessor501 determines that thePOS apparatus10 or20 corresponding to the POS ID is a settlement object (settlement POS apparatus) (Act32).
For example, theprocessor501 inquires each of thePOS apparatuses10 and20 that are connected with each other via theLAN70 about the POS ID. Moreover, theprocessor501 determines that thePOS apparatus10 or20 in response to the POS ID detected according to the barcode data is a settlement POS apparatus. Theprocessor501 sends a settlement request to thesettlement POS apparatus10 or20 if thesettlement POS apparatus10 or20 is determined (Act33). Here, the settlement request is sent to thesettlement POS apparatus10 or20 via theLAN70.
Theprocessor101 of thesettlement POS apparatus10 or20 receiving the settlement request carries out a process in accordance with the procedure shown inFIG. 12. That is, theprocessor101 determines whether or not a commodity transaction is being continued (Act41).
In case of the self-service POS apparatus20, the commodity transaction of thecustomer4 is ended when another customer photographs abarcode7 using thecamera unit405 thereof. However, in case of the facing-type POS apparatuses10, the commodity transaction of thecustomer4 may not be ended even when another customer photographs abarcode7 using thecamera unit405 thereof. If the commodity transaction of a customer is not ended, theprocessor101 determines that a commodity transaction is being continued. In this case (Yes in Act41), theprocessor101 waits for completion of the commodity transaction. If the commodity transaction is completed (No in Act41), theprocessor101 sends an approval response to the support server50 (Act42).
As shown inFIG. 11, theprocessor501 of thesupport server50 which has sent the settlement request to thesettlement POS apparatus10 or20 waits for an approval response (Act34). After receiving the approval response from thesettlement POS apparatus10 or20 (Yes in Act34), theprocessor501 detects thecommodity transaction file510 having the self-registration ID attached to the barcode data. Then, theprocessor501 sends the data in thecommodity transaction file510 to thesettlement POS apparatus10 or20 (Act35: a first transmitting module).
As shown inFIG. 12, theprocessor101 of thesettlement POS apparatus10 or20 which has sent the approval response to thesupport server50 waits for the commodity transaction file510 (Act43). Theprocessor101 loads the commodity sales data contained in thecommodity transaction file510 to the transaction region of themain memory102, if theprocessor101 receives the data contained in the commodity transaction file510 from thesupport server50 via the communication interface504 (Yes in Act43). Then, theprocessor101 displays the information, such as the commodity name and the price, contained in the commodity sales data loaded to the transaction region, on thedisplay13aor the touch panel22 (Act44).
Then, theprocessor101 waits for input of payment data (Act45). If the barcode of a commodity is read by thescanner11 or21 whileprocessor101 is waiting for the input of payment data, theprocessor101 identifies the commodity according to the barcode and loads the sales data thereof to the transaction region.
If payment data are input via thekeyboard12 or the touch panel22 (Yes in Act45), then theprocessor101 carries out, according to the payment data, a settlement process corresponding to the commodity sales data stored in the transaction region. During the settlement process, theprocessor101 generates print data of the receipt data (Act46: a generation module).
After the settlement process is ended, theprocessor101 checks the association flag F contained in thecommodity transaction file510 sent from the support server50 (Act47). Here, if the association flag F is set to be ‘1’, thecustomer4 completing a self-registration operation sets the association of the self-registration system with the electronic receipt system. If the association of the self-registration system with the electronic receipt system is set (Act47: Yes), theprocessor101 generates an electronic receipt by formatting the receipt data (Act48). Further, theprocessor101 displays, on thedisplay13aor thetouch panel22, a screen to inquire thecustomer4 about whether or not to issue a paper receipt. Moreover, theprocessor101 waits for an input indicating whether or not to issue a paper receipt (Act49: a reception module).
Here, if an input indicating no issue of a paper receipt is received through the operation on thekeyboard12 or touch panel22 (No in Act49), theprocessor101 adds the self-registration ID contained in thecommodity transaction file510 to the electronic receipt. Then, theprocessor101 sends the electronic receipt having the self-registration ID added thereto, to the electronic receipt server80 (Act50: a second transmitting module).
On the other hand, if an input indicating issue of a paper receipt is received through the operation on thekeyboard12 or touch panel22 (Yes in Act49), theprocessor101 controls theprinter14 or24 to issue a paper receipt (Act51: a control module). Also if the association flag F contained in thecommodity transaction file510 is set as ‘0’ (No in Act47), theprocessor101 causes a paper receipt to be issued (Act51).
In this way, if the electronic receipt is sent to theelectronic receipt server80 or issue of a paper receipt is instructed, theprocessor101 sends a settlement end command to the support server50 (Act52). Then, theprocessor101 ends the process carried out when a settlement request is received.
As shown inFIG. 11, theprocessor501 of thesupport server50 which has sent thecommodity transaction file510 to thesettlement POS apparatus10 or20 waits for a settlement end command (Act36). If theprocessor501 receives a settlement end command from thesettlement POS apparatus10 or20 (Yes in Act36), theprocessor501 wirelessly sends the settlement end command to theportable information terminal400 which has sent the barcode data of a POS ID (Act37). Further, theprocessor501 deletes thecommodity transaction file510 the data in which is sent to thesettlement POS apparatus10 or20, from the transaction file region W4 (Act38). Then, theprocessor501 ends the process carried out after the registration start command is received. Further, not limited to the foregoing sequence, Act37 and Act38 may be executed in a reverse sequence. Further, thecommodity transaction file510 deleted from the transaction file region W4 may also be stored in another region formed in theauxiliary storage device503.
As shown inFIG. 10, theprocessor401 of theportable information terminal400 which receives the barcode data waits for data from the support server50 (Act12). If the data are received from the support server50 (Yes in Act12), theprocessor401 determines whether or not the data are commodity sales data (Act13). If the received data are not commodity sales data (No in Act13), theprocessor401 determines whether or not the received data are an end command (Act15). If the data received are the end command (Yes in Act15), theprocessor401 deletes the registration screen displayed on the touch panel404 (Act16). Then, theprocessor401 ends the process carried out according to the self-registration terminal program P1.
As shown inFIG. 13, theprocessor801 of theelectronic receipt server80 waits to receive data (Act61). After theprocessor801 receives the data via the network200 (Yes in Act61), theprocessor801 determines whether or not the data received are an electronic receipt (Act62). If it is determined that the received data is an electronic receipt (Yes in Act62), theprocessor801 identifies the ID included in the data is a self-registration ID or an electronic receipt ID (Act63).
If an electronic receipt ID is added to the electronic receipt (No in Act63), theprocessor801 generates anelectronic receipt file810 containing the electronic receipt ID and the electronic receipt, and stores the generatedelectronic receipt file810 in the electronic receipt region W5 (Act65).
If a self-registration ID is added to the electronic receipt (Yes in Act63), theprocessor801 retrieves the linkage table820. Then, theprocessor801 searches an electronic receipt ID set in the linkage table820 in association with the self-registration ID (Act64). Then, theprocessor801 converts the self-registration ID to the electronic receipt ID found in the linkage table820. After converting the self-registration ID into the electronic receipt ID, theprocessor801 generates anelectronic receipt file810 containing the electronic receipt ID obtained by the conversion and the electronic receipt and stores the generatedelectronic receipt file810 in the electronic receipt region W5 (Act65). Then, theprocessor801 ends the process carried out when an electronic receipt is received.
In this way, the self-registration ID of acustomer4 who completed a self-registration operation is added to the electronic receipt of a commodity transaction of the commodities registered through the self-registration operation, and the electric receipt data containing the self-registration ID are sent to theelectronic receipt server80. If the electronic receipt contains the self-registration ID, theelectronic receipt server80 converts the self-registration ID into the electronic receipt ID of thecustomer4. Then, theelectronic receipt server80 generates anelectronic receipt file810 containing the electronic receipt ID and stores the generatedelectronic receipt file810 in the electronic receipt region W5. On the other hand, when theelectronic receipt server80 receives electronic receipt containing an electronic receipt ID but not a self-registration ID, theelectronic receipt server80 generates anelectronic receipt file810 containing the electronic receipt ID and stores the generatedelectronic receipt file810 in the electronic receipt region W5.
The electronic receipt ID is used as an authentication ID for thecustomer4 who is an electronic receipt member (subscriber) to log in theelectronic receipt server80 from theportable information terminal400. Thus, thecustomer4 who completed a self-registration operation using theportable information terminal400 can browse, using theportable information terminal400, the electronic receipt for the commodity transaction of the commodities registered through the self-registration operation.
Further, not limited to theportable information terminal400, the apparatus that can log in theelectronic receipt server80 using an electronic receipt ID may also function as theinformation processing apparatus210 such as a personal computer and the like. Thus, an electronic receipt for a commodity transaction of the commodities registered through a self-registration operation may also be browsed on theinformation processing apparatus210 such as a personal computer and the like.
Moreover, thecustomer4 and thecashier3 do not need to input an electronic receipt ID using thePOS apparatus10 or20 for the commodities registered through a self-registration operation. As a result, the association of the self-registration system with the electronic receipt system causes no increased workload for thecustomer4 and thecashier3.
According to the present embodiment, the self-registration system can simplify the commodity registration by the cashier and reduce time required for the settlement process. In addition, the electronic receipt system can reduce time required to issue paper receipts. By combining the self-registration system and the electronic receipt system, processing speed of thecheckout region1 can be largely improved, which leads to reduction of customers' wait time at thecheckout region1. Further, as thecustomers4 do not need to present their electronic receipt ID at thecheckout region1, customer convenience can be improved.
In the present embodiment, the POS apparatuses10,20 generate the electronic receipt and transmit it to theelectronic receipt server80. Alternatively, thestore server40 or thesupport server50 may generate the electronic receipt and transmit it to theelectronic receipt server80.
In case of thestore server40, the commodity sales data or the payment data that are necessary to generate the electronic receipt are transmitted from the POS apparatuses10,20 to thestore server40. On the other hand, in case of thesupport server50, the payment data and the self-registration ID are transmitted from the POS apparatuses10,20 to thesupport server50, because the commodity sales data are stored in thecommodity transaction file510 of thesupport server50.
Second EmbodimentNext, a second embodiment is described below with reference toFIG. 14-FIG. 16. Here, elements shown inFIG. 14-FIG. 16 that correspond to those described in the first embodiment are depicted with same reference signs and therefore may not be described in detail.
FIG. 14 is a block diagram of a portable information terminal400-2 according to the second embodiment. The portable information terminal400-2 is different from theportable information terminal400 according to the first embodiment in the data stored in the self-registration management region W1 of theauxiliary storage device403. That is, the portable information terminal400-2 stores an electronic receipt ID in the self-registration management region W1.
Similar to the first embodiment, in the second embodiment, thecustomer4 determines whether or not the self-registration system is associated with the electronic receipt system. If it is set that the self-registration system is associated with the electronic receipt system, theprocessor401 of theportable information terminal400 sets an association flag F in the self-registration management region W1. Further, theprocessor401 stores the electronic receipt ID used by thecustomer4 to log in theelectronic receipt server80 in the self-registration management region W1.
The electronic receipt ID is stored in the electronic receipt management region W2 by logging in theelectronic receipt server80. When setting the association of the self-registration system with the electronic receipt system, thecustomer4 starts the electronic receipt terminal program P2 in advance to log into theelectronic receipt server80. If so, the electronic receipt ID is stored in electronic receipt management region W2, and then theprocessor401 copies the electronic receipt ID stored in the electronic receipt management region W2 to the self-registration management region W1. Theprocessor401 also sets the association flag F. The electronic receipt ID is not deleted even if thecustomer4 logs out of theelectronic receipt server80. Similarly, the association flag F is not reset, even if thecustomer4 logs out of theelectronic receipt server80. That is, if the association of the self-registration system with the electronic receipt system is set, the electronic receipt ID is stored and the association flag F is set in the self-registration management region W1. When the association of the self-registration system with the electronic receipt system is deactivated, thecustomer4 launches the self-registration program P1 and performs a predetermined operation to delete the electronic receipt ID from the electronic receipt management region W2, and to clear the association flag.
FIG. 15 schematically illustrates a data structure of a commodity transaction file510-2 stored in the transaction file region W4 of thesupport server50 according to the second embodiment. The commodity transaction file510-2 according to the second embodiment is different from thecommodity transaction file510 according to the first embodiment in the number of types of the IDs stored therein. Only a self-registration ID is stored in thecommodity transaction file510 according to the first embodiment. However, besides the self-registration ID, an electronic receipt ID is also stored in the commodity transaction file510-2 according to the second embodiment.
FIG. 16 is a flowchart illustrating a part of a process carried out by theprocessor401 of the portable information terminal400-2 in accordance with the self-registration terminal program P1 in the second embodiment. As shown inFIG. 16, in the second embodiment, Acts71 and72 are performed between Act5 (detecting a self-registration ID and an association flag F) and Act6 (sending a registration start command).
That is, theprocessor401 carries out Act71 after completingAct5. In Act71, theprocessor401 determines whether or not an association flag F is detected in the self-registration management region W1. No association flag F is detected if the association of the self-registration system with the electronic receipt system is not set in theportable information terminal400. In this case, theprocessor401 carries outAct6 as the result of Act71 is determined to be ‘No’. That is, theprocessor401 wirelessly sends the registration start command which is acquired from the self-registration management region W1 containing the self-registration ID and the association flag F.
In contrast, the association flag F is detected if the association of the self-registration system with the electronic receipt system is set in the portable information terminal400-2. In this case, theprocessor401 carries out Act72 as the result of Act71 is determined to be ‘Yes’.
In Act72, theprocessor401 detects an electronic receipt ID from the self-registration management region W1. After detecting an electronic receipt ID, theprocessor401 carries outAct6. That is, theprocessor401 wirelessly sends the registration start command containing a self-registration ID, an electronic receipt ID, and the association flag F, which are acquired from the self-registration management region W1. The process carried out afterAct6 in the second embodiment is the same as that carried out afterAct6 in the first embodiment.
Then, similarly to the first embodiment, after receiving the registration start command, thesupport server50 carries out a process according to the procedure shown inFIG. 11. However,Act23 in the second embodiment is partially different fromAct23 in the first embodiment. Specifically, inAct23 of the first embodiment, theprocessor501 generates acommodity transaction file510 according to the self-registration ID and the association flag F that are contained in the received registration start command, and the store information acquired inAct22. In contrast, inAct23 of the second embodiment, theprocessor501 also generates acommodity transaction file510 according to the self-registration ID and the association flag F that are contained in the registration start command.
However, as described with reference toFIG. 16, in addition to the self-registration ID and the association flag F, an electronic receipt ID may be also contained in the registration start command in some cases. In these cases, theprocessor501 generates a commodity transaction file510-2 inAct23. That is, theprocessor501 generates the commodity transaction file510-2 (storage module) according to the self-registration ID and the association flag F that are contained in the received registration start command and the store information acquired inAct22.
Further, similarly to the first embodiment, theprocessor101 of thePOS apparatus10 or20 that receives the settlement request carries out a process in accordance with the procedure shown inFIG. 12. However, inAct5, theprocessor101 attaches the electronic receipt ID contained in the commodity transaction file510-2 to an electronic receipt. The self-registration ID is not added to the electronic receipt. Theprocessor101 sends the electronic receipt containing the electronic receipt ID to the electronic receipt server80 (second transmitting module).
Similarly to the first embodiment, theprocessor801 of theelectronic receipt server80 that receives the electronic receipt carries out a process in accordance with the procedure shown inFIG. 13. However, as the ID added to the electronic receipt is an electronic receipt ID, the result of the determination of Act63 should be ‘NO.’ Thus, Act64 is not executed. For that reason, in the second embodiment, the linkage table820 is not needed in theelectronic receipt server80.
According to the second embodiment, the self-registration system can be associated with the electronic receipt system d without increasing the workload of thecustomer4 and thecashier3 in a similar manner as the first embodiment. As a result, the processing speed of thecheckout region1 can be largely improved, and customers' wait time can be reduced. Also, as thecustomers4 do not need to present their electronic receipt ID at thecheckout region1, customer convenience can be improved.
Moreover, according to the second embodiment, it would be beneficial that a conventional electronic receipt server can be used as theelectronic receipt server80.
Further, according to the second embodiment, thecustomer4 can change the setting of whether to receive a paper receipt or an electronic receipt, by changing the setting of the association flag F in the portable information terminal400-2. It would be easy for the customer to change the setting in each purchase transaction.
In the second embodiment, the association flag F is set in the portable information terminal400-2, but the association flag F may not be set therein in other embodiments. For example, theelectronic receipt server80 may contain a member database, which stores the association flag F for each electronic receipt ID. Then, if the registration start command from the portable information terminal400-2 contains the electronic receipt ID, theprocessor501 of thesupport server50 may receive the association flag F in the member database, and store the received association flag F in the commodity transaction file510-2.
Third EmbodimentNext, a third embodiment is described below with reference toFIG. 17-FIG. 18. Here, elements shown inFIG. 17-FIG. 18 that correspond to those described in the first embodiment are depicted with the same reference signs and not described in detail.
FIG. 17 is a block diagram of a POS apparatus10-3 or20-3 according to the third embodiment. The POS apparatus10-3 or20-3 is different from thePOS apparatus10 or20 in formation of a linkage table region W7 in theauxiliary storage device103. The linkage table region W7 is a region for storing a linkage table820 having the data structure shown inFIG. 9.
In the first embodiment, theelectronic receipt server80 comprises a linkage table820. In the third embodiment, the POS apparatus10-3 or20-3 comprises a linkage table820, and theelectronic receipt server80 comprises no linkage table820.
FIG. 18 is a flowchart illustrating a main procedure of a process carried out by theprocessor101 of the POS apparatus10-3 or20-3 according to a control program when thePOS apparatus10 or20 receives the settlement request (described below). Further, the procedure (FIG. 10) of the process carried out by theprocessor401 of theportable information terminal400 according to the self-registration terminal program P1 and the procedure (FIG. 11) of the process carried out by theprocessor501 of thesupport server50 according to the self-registration server program P3 in the third embodiment are the same as those described in the first embodiment, and therefore not described here.
The third embodiment is different from the first embodiment in that Act48 is carried out after Act81 if the result of the determination in Act47 is ‘Yes’, as shown inFIG. 18.
That is, if it is determined that the association flag F contained in thecommodity transaction file510 sent from thesupport server50 is set as ‘1’ (Yes in Act47), theprocessor101 searches the linkage table820 for the electronic receipt ID set in the linkage table820 in association with the self-registration ID, and converts the self-registration ID into the electronic receipt ID (Act81). Then, theprocessor101 generates an electronic receipt by formatting the receipt data (Act48). Further, not limited to the foregoing sequence, Act81 and Act48 may be executed in a reverse sequence.
That is, in the third embodiment, the POS apparatuses10-3 and20-3 both comprise a linkage table820. If the association flag F contained in thecommodity transaction file510 sent from thesupport server50 is set as ‘1’, the POS apparatus10-3 or20-3 converts the self-registration ID to an electronic receipt ID. Moreover, the POS apparatus10-3 or20-3 adds the electronic receipt ID in the electronic receipt generated based on the commodity sales data stored in thecommodity transaction file510 and sends the processed electronic receipt to theelectronic receipt server80.
As a result, also according to the third embodiment, the self-registration system can be associated with the electronic receipt system without increasing the workload of thecustomer4 and thecashier3. Further, the processing speed of thecheckout region1 can be largely improved, and customers' wait time can be reduced. Also, as thecustomers4 do not need to present their electronic receipt ID at thecheckout region1, customer convenience can be improved.
Moreover, as an electronic receipt containing an electronic receipt ID is sent to theelectronic receipt server80, a conventional electronic receipt can be used as theelectronic receipt server80.
In the present embodiment, the POS apparatuses10,20 generate the electronic receipt and transmit it to theelectronic receipt server80. Alternatively, thestore server40 or thesupport server50 may generate the electronic receipt and transmit it to theelectronic receipt server80.
In case of thestore server40, the commodity sales data or the payment data that are necessary to generate the electronic receipt are transmitted from the POS apparatuses10,20 to thestore server40. On the other hand, in case of thesupport server50, the payment data and the self-registration ID are transmitted from the POS apparatuses10,20 to thesupport server50, because the commodity sales data are stored in thecommodity transaction file510 of thesupport server50.
Fourth EmbodimentA fourth embodiment is described below with reference toFIG. 19-FIG. 28. Here, elements and steps shown inFIG. 19-FIG. 28 that correspond to those described in the first embodiment are depicted with same reference signs and therefore may not be described in detail. In the present embodiment, a terminal ID is used instead of or in addition to the self-registration ID.
[Portable Information Terminal]
Theportable information terminal400 according to the fourth embodiment has a storage region W0 for storing a terminal ID in theauxiliary storage device403. The terminal ID is an ID unique to theportable information terminal400, such as a phone number.
[Support Server (Commodity Data Input Support Server)]
The data in thecommodity transaction file510 further consists of the terminal ID, in addition to the self-registration ID, store information, the association flag F, one or more commodity sales data, and total data described in the first embodiment.
That is, the commodity transaction file510 functions as a storage module which stores the commodity data of a sales commodity associated with a commodity code input from theportable information terminal400, in association with the terminal ID of theportable information terminal400 and the self-registration ID of thecustomer4. Here, the commodity data may be stored in a file same as the one containing the terminal ID and the self-registration ID or, alternatively, different from the one.
[Electronic Receipt Server]
The data in theelectronic receipt file810 further consists of the terminal ID, in addition to the electronic receipt ID, the simplified data of an electronic receipt consisting of a store name, the transaction date and time and a total amount, and the actual data of the electronic receipt.
[Operations of Commodity Sales Processing System]
Next, an operation carried out by the commodity sales processing system when the self-registration system is associated with the electronic receipt system is described below with reference to flowcharts ofFIG. 19-FIG. 22.FIG. 19-FIG. 22 in the present embodiment correspond toFIG. 10-FIG. 13 in the first embodiment, respectively.
InAct5 inFIG. 19, theprocessor401 further searches the terminal ID in the terminal ID region W0, in addition to the search of the self-registration ID in the self-registration management region W1. Then, inAct6, theprocessor401 wirelessly sends the registration start command containing the self-registration ID, the terminal ID, and the association flag F.
InAct23 inFIG. 20, theprocessor501 of thesupport server50, after receiving the registration start command, stores the self-registration ID, the terminal ID, and the association flag F in the registration start command in thecommodity transaction file510.
As a result, acommodity transaction file510 containing the self-registration ID of thecustomer4 and the terminal ID of theportable information terminal400 used by thecustomer4 is formed in the transaction file region W4 of thesupport server50.
In Act35, theprocessor501 of thesupport server50 sends the commodity data stored in thecommodity transaction file510, and the terminal ID and the self-registration ID, to thePOS apparatus10 or20 associated with a POS ID input from theportable information terminal400. Here, theprocessor501 may send the commodity data, together with or separately from the terminal ID and the self-registration ID.
If the input indicating no issue of a paper receipt is received through the operation on thekeyboard12 or touch panel22 (No in Act49) inFIG. 21, theprocessor101 further adds the terminal ID to the electronic receipt, in addition to the self-registration ID. Then, inAct50, theprocessor101 sends the electronic receipt along with the self-registration ID and the terminal ID to theelectronic receipt server80.
InFIG. 22, if an electronic receipt ID is added to the electronic receipt (Act63: No), theprocessor801 creates anelectronic receipt file810 containing the electronic receipt ID and the electronic receipt and stores the createdelectronic receipt file810 in the electronic receipt region W5 (Act65). Here, no terminal ID is stored in theelectronic receipt file810.
If a self-registration ID is not added to the electronic receipt (Act63: Yes), theprocessor801 searches the linkage table820. Then, theprocessor801 converts the self-registration ID to an electronic receipt ID which is associated therewith in the linkage table820 (Act64: a conversion module). After converting the self-registration ID to the electronic receipt ID, theprocessor801 creates anelectronic receipt file810 according to the converted electronic receipt ID and the electronic receipt, and stores the createdelectronic receipt file810 in the electronic receipt region W5. Here, theprocessor801 stores the terminal ID attached to the electronic receipt together with the self-registration ID in the created electronic receipt file810 (Act65). Then, theprocessor801 ends the process carried out when receiving the electronic receipt.
Theprocessor801 and theelectronic receipt file810 function as a storage module which stores the electronic receipt in association with the electronic receipt ID corresponding to the self-registration ID, and the terminal ID, with reference to the linkage table820, when the terminal ID and the self-registration ID are associated with the electronic receipt received from thePOS apparatus10 or20.
In this way, the electronic receipt for the transaction of the commodities registered by thecustomer4 through the self-registration transmitted to theelectronic receipt server80, together with the self-registration ID of thecustomer4 and the terminal ID of theportable information terminal400 used by thecustomer4. If the electronic receipt contains the self-registration ID, theelectronic receipt server80 converts the self-registration ID to the electronic receipt ID of thecustomer4. Then, theelectronic receipt server80 creates anelectronic receipt file810 containing the electronic receipt ID and the terminal ID, and stores the createdelectronic receipt file810 in the electronic receipt region W5. On the other hand, if an electronic receipt containing an electronic receipt ID rather than the self-registration ID, theelectronic receipt server80 creates anelectronic receipt file810 containing the electronic receipt ID and stores the createdelectronic receipt file810 in the electronic receipt region W5.
In theelectronic receipt file810, in addition to the electronic receipt ID, the terminal ID is also stored. The terminal ID is unique to theportable information terminal400. Thus, using theportable information terminal400 containing the electronic receipt terminal program P1, an electronic receipt can be retrieved with a terminal ID, instead of an electronic receipt ID.
Next, the operations to view, on theportable information terminal400, the electronic receipt generated through the association of the self-registration system with the electronic receipt system are described with reference toFIG. 23-FIG. 28.FIG. 23 andFIG. 24 are flowcharts illustrating a main procedure of a process carried out by theprocessor401 of theportable information terminal400 according to the electronic receipt terminal program P2.FIG. 25 is a flowchart illustrating a main procedure of a process carried out by theprocessor801 of theelectronic receipt server80 according to the electronic receipt server program P4.FIG. 26-FIG. 28 schematically illustrate a screen displayed on thetouch panel404 of theportable information terminal400. Further, the content of each process described below with reference toFIG. 23-FIG. 25 is merely an example, and other processes that can achieve the same effect can be performed properly.
Thecustomer4 who desires to view an electronic receipt operates thetouch panel404 of theportable information terminal400 to activate the electronic receipt terminal program P2. To activate it, thecustomer4 touches the icon of the electronic receipt terminal program P2 displayed on thetouch panel404. If the electronic receipt terminal program P2 is activated, theprocessor401 of theportable information terminal400 starts the process shown in the flowchart ofFIG. 23.
First, theprocessor401 determines whether or not theelectronic receipt server80 is being logged into (Act71). If the electronic receipt terminal program P2 is ended without being logged out, the login state is maintained. An electronic receipt ID used as an authentication ID is stored in the electronic receipt management region W2 during the login process.
If theelectronic receipt server80 is not being logged into (Act81: No), theprocessor401 displays a login screen on thetouch panel404 for login (Act72). Thecustomer4 inputs own electronic receipt ID on the login screen to log in. Thecustomer4 may input an electronic receipt ID and a password.
If thecustomer4 logs in, theprocessor401 wirelessly sends login information containing the electronic receipt ID. The log information wirelessly sent from thewireless unit406 is received by a base station (not shown) and sequentially forwarded to theelectronic receipt server80 via thenetwork200. Theelectronic receipt server80 authenticates the login. Moreover, theelectronic receipt server80 notifies theportable information terminal400 of the result of the authentication through a route inverse to that of login information.
Theprocessor401 determines whether or not the login is approved (Act73). If it is determined that the login is not approved (Act73: No), theprocessor401 may perform the login operation again (Act72). If it is determined that the login is approved (Act73: Yes), theprocessor401 stores the electronic receipt ID used for the login in the electronic receipt management region W2 (Act74).
If the electronic receipt ID is stored in the electronic receipt management region W2 as the login is approved or when the login is ongoing (Act71: Yes), theprocessor401 displays the electronic receipt ID on the touch panel404 (Act75).
FIG. 26 illustrates an example of a screen G1 displayed on thetouch panel404 in Act75. As shown inFIG. 26, a barcode B1, a ‘view’ button B2 and an ‘end’ button B3 are displayed on the screen G1. The barcode B1 represents the electronic receipt ID. An electronic receipt member who does not set the association with the self-registration system but prefers reception of the electronic receipt uses thescanner11 or21 of thePOS apparatus10 or20 to read the barcode of the electronic receipt ID when settling a commodity transaction. Then, electronic data indicating the details of the commodity transaction are sent to theelectronic receipt server80 along with the electronic receipt ID. As a result, anelectronic receipt file810 in which the electronic receipt ID and the electronic receipt are stored is stored in the electronic receipt region W5 of theelectronic receipt server80.
Thecustomer4 viewing the screen G1 selects the ‘view’ button B2 to view the electronic receipt stored in theelectronic receipt server80. Thecustomer4 selects the ‘end’ button B3 to end the view of the electronic receipt.
Theprocessor401 waits for the selection of the ‘view’ button B2 or the ‘end’ button B3 displayed on the screen G1 (Act76 and Act77). If the selection of the ‘view’ button B2 is received (Act76: Yes), theprocessor401 displays an ID selection screen on the touch panel404 (Act78).
FIG. 27 illustrates an example of a screen G2 displayed on thetouch panel404 in Act78. As shown inFIG. 27, a ‘user’ button B4 and a ‘terminal’ button B5 are displayed on the screen G2.
To search an electronic receipt by an electronic receipt ID, thecustomer4 selects the ‘user’ button B4. To search an electronic receipt by a terminal ID, thecustomer4 selects the ‘terminal’ button B5.
Theprocessor401 waits for the selection of the ‘user’ button B4 or the ‘terminal’ button B5 displayed on the screen G2 (Act79 and Act80). If the selection of the ‘user’ button B4 is received (Act79: Yes), theprocessor401 sends a view request command containing the electronic receipt ID to the electronic receipt server80 (Act81). If the selection of the ‘terminal’ button B5 is received (Act80: Yes), theprocessor401 sends a view request command containing the terminal ID to the electronic receipt server80 (Act82). The view request command wirelessly sent from thewireless unit406 is received by the base station and sequentially received by theelectronic receipt server80 via thenetwork200.
As shown inFIG. 25, theprocessor801 of theelectronic receipt server80 waits to receive data (Act101). If the data are received via the network200 (Act101: Yes), theprocessor801 determines whether or not the received data are a view request command (Act102). If it is determined that the received data are a view request command (Act102: Yes), theprocessor801 determines whether the ID contained in the command is an electronic receipt ID or a terminal ID (Act103: identification module). An electronic receipt ID is different from a terminal ID in code system. Theprocessor801 determines whether the ID contained in the command is an electronic receipt ID or a terminal ID according to the difference in code system. Further, not limited to the determination method based on a code system, the ID contained in the command may also be identified according to the number of specific digits unique to the electronic receipt ID or the terminal ID.
If the ID contained in the view request command is an electronic receipt ID (Act103: Yes), theprocessor801 searches the electronic receipt region W5 for anelectronic receipt file810 containing the electronic receipt ID. Then, theprocessor801 reads simplified data including a store name, a transaction date and time, and a total amount from eachelectronic receipt file810 to create a list of simplified data (Act104: creation module).
If the ID contained in the view request command is a terminal ID (Act103: No), theprocessor801 detects, from the electronic receipt region W5, anelectronic receipt file810 in which the terminal ID is stored. Moreover, theprocessor801 reads simplified data including a store name, a transaction date and time and a total amount from each detectedelectronic receipt file810 to create a list of simplified data (Act105: creation module). Theprocessor801 sends the simplified data list representing the electronic receipt data found according to the electronic receipt ID or the simplified data list representing the electronic receipt data found according to the terminal ID to theportable information terminal400 from which the view request command has been originally sent (Act106: a third sending module).
Theprocessor401 of theportable information terminal400 which has sent the view request command in Act81 or Act82 waits to receive the simplified data list from the electronic receipt server80 (Act83). If theprocessor401 receives the simplified data list (Act83: Yes), theprocessor401 displays the simplified data list on the touch panel404 (Act84), as shown inFIG. 24.
FIG. 28 illustrates an example of a screen G3 displayed on thetouch panel404 in Act84. As shown inFIG. 19, a simplified data list L1, a ‘select’ button B6, and a ‘return’ button B7 are displayed on the screen G3.
The content of the simplified data list L1 if thecustomer4 selects the ‘user’ button B4 displayed on the screen G2, is different from that of the simplified data list L1 if thecustomer4 selects the ‘terminal’ button B5 displayed on the screen G2. That is, the simplified data (the store name, the transaction date and time, and the total amount) of theelectronic receipt file810 containing the electronic receipt ID of thecustomer4 are displayed in the simplified data list L1 if thecustomer4 selects the ‘user’ button B4.
Theelectronic receipt file810 containing the electronic receipt ID of thecustomer4 is generated according to a commodity transaction with thecustomer4. The commodity transaction may include not only a commodity transaction base on the self-registration through theportable information terminal400, but also a commodity transaction based on a (direct) input to thePOS apparatus10 or20. If thecustomer4 uses a plurality ofportable information terminals400, the commodity transaction includes a commodity transaction corresponding to eachportable information terminal400. Thus, the simplified data of an electronic receipt generated according to a commodity transaction with thecustomer4 is displayed in the simplified data list L1.
On the other hand, the simplified data (the store name, the transaction date and time, and the total amount) of anelectronic receipt file810 containing the terminal ID of theportable information terminal400 are displayed in the simplified data list L1 if thecustomer4 selects the ‘terminal’ icon B5.
Anelectronic receipt file810 containing the terminal ID of aportable information terminal400 is generated according to a self-registration through theportable information terminal400 associated with the terminal ID. Thus, even for thesame customer4, the commodity transaction according to the self-registration through anotherportable information terminal400 having different terminal ID is not searched, because the terminal ID is different. Thus, only the simplified data of an electronic receipt generated according to a commodity transaction through the specificportable information terminal400 is displayed in the simplified data list L1.
Thecustomer4 viewing the simplified data list L1 selects (touches) a commodity transaction and selects the ‘select’ button B6, to download the corresponding electronic receipt from the list. Thecustomer4 selects the ‘return’ button B7 to end the display of the simplified data list L1.
Theprocessor401 of theportable information terminal400 displaying the simplified data list L1 waits for the selection of the ‘select’ button B6 (Act85) or the ‘return’ button (Act86). If the ‘select’ button is selected (Act85: Yes), theprocessor401 sends a download request command requesting the electronic receipt corresponding to the simplified data selected (touched) from the simplified data list L1, to the electronic receipt server80 (Act87). The download request command is received by theelectronic receipt server80 via thenetwork200.
Theprocessor801 of theelectronic receipt server80 which sends the simplified data list waits to receive the download request command (Act107). If the download request command is received from the portable information terminal400 (Act107: Yes), theprocessor801 reads the electronic receipt requested from theelectronic receipt file810 containing the selected simplified data. Then, theprocessor801 downloads the data of the electronic receipt in theportable information terminal400 from which the download request command has been originally sent (Act108).
Theprocessor401 of theportable information terminal400 which has sent the download request command waits to receive the download of the electronic receipt (Act88). If the electronic receipt is downloaded via thewireless unit406, then theprocessor401 stores the electronic receipt in the electronic receipt management region W2 of the auxiliary storage device403 (Act89). Sequentially, theprocessor401 waits for the selection of the ‘select’ button B6 (Act85) or the selection of the ‘return’ button (Act86).
If the ‘return’ icon B7 is selected (Act86: Yes), theprocessor401 returns to carry out Act75. That is, theprocessor401 causes the screen of the touch panel to return to the display screen G1 of the electronic receipt ID. Theprocessor401 waits for the selection of the ‘view’ button B2 (Act76) or the ‘end’ button B3 (Act77).
If the ‘end’ button B3 is selected (Act77: Yes), theprocessor401 deletes the display screen G1 of the electronic receipt ID (Act91). Then, theprocessor401 ends the process carried out according to the electronic receipt terminal program P2.
The data of the electronic receipt stored in the electronic receipt management region W2 of theportable information terminal400 are displayed on thetouch panel404 of theportable information terminal400. By selecting the ‘user’ button B4 on the screen G2, thecustomer4 can view the electronic receipt associated with the electronic receipt ID, which is used by thecustomer4 to log into theelectronic receipt server80. Further, by selecting the ‘terminal’ button B5 on the screen G2, thecustomer4 can view the electronic receipt associated with the terminal ID of theportable information terminal400 used by thecustomer4.
For example, it is assumed that a first portable information terminal400ais used by thecustomer4 for the self-registration during five commodity transactions and a second portable information terminal400bis used by the (same)customer4 for the self-registration of another five commodity transactions. Moreover, it is assumed that thecustomer4 receives an electronic receipt for each commodity transaction.
In this case, in either one of the portable information terminals400aor400b, by selecting the ‘user’ button B4 on the screen G2, a simplified data list L1 relating to electronic receipts for all ten commodity transactions is displayed on thetouch panel404 of the portable information terminal400aor400b.
On the other hand, if the ‘terminal’ button B5 is selected on the screen G2 displayed on thetouch panel404 of the portable information terminal400a, a simplified data list L1 relating to electronic receipts for the five commodity transactions for which self-registrations are carried out using the portable information terminal400ais displayed on thetouch panel404. Simplified data relating to electronic receipts for the other five commodity transactions for which self-registrations are carried out using the portable information terminal400bare not included in the list L1.
Contrarily, a simplified data list L1 relating to electronic receipts for the five commodity transactions for which self-registrations are carried out using the portable information terminal400bis displayed on thetouch panel404 of the portable information terminal400b, if the ‘terminal’ button B5 is selected on the screen G2 displayed on thetouch panel404 of the portable information terminal400b. Simplified data relating to electronic receipts for the other five commodity transactions for which self-registrations are carried out using the portable information terminal400aare not included in the list L1.
Thus, a retrieval using the ‘terminal’ button B5 is effective if thecustomer4 knows the commodity transaction carried out through theportable information terminal400. A retrieval using the ‘user’ button B4 is effective if the commodity transaction is not through the self-registration, or if thecustomer4 does not know the commodity transactions carried out through theportable information terminal400.
Fifth EmbodimentNext, a fifth embodiment is described below with reference toFIG. 29-FIG. 30. Here, elements shown in FIG.29-FIG. 30 that correspond to those described in the above embodiments are depicted with same reference signs and therefore may not be described in detail. The present embodiment corresponds to the second embodiment, and the terminal ID is used for the self-registration, similarly to the fourth embodiment.
FIG. 29 schematically illustrates a data structure of a commodity transaction file510-2 stored in the transaction file region W4 of thesupport server50 according to the fifth embodiment. The commodity transaction file510-2 according to the fifth embodiment is different from thecommodity transaction file510 according to the fourth embodiment in the number of the stored IDs. A self-registration ID and a terminal ID are stored in thecommodity transaction file510 of the fourth embodiment. In addition to a self-registration ID and a terminal ID, an electronic receipt ID is also stored in the commodity transaction file510-2 of the fifth embodiment.
FIG. 30 is a flowchart illustrating a part of a process carried out by theprocessor401 of the portable information terminal400-2 according to the self-registration terminal program P1 in the fifth embodiment. As shown inFIG. 30, in the fifth embodiment, Acts111 and112 are carried out between the detection process of a self-registration ID, a terminal ID, and an association flag F inAct5 and the sending process of the registration start command inAct6.
That is, theprocessor401 carries out Act111 after completingAct5. In Act111, theprocessor401 determines whether or not an association flag F is detected in the self-registration management region W1. No association flag F can be detected if the association of the self-registration system with the electronic receipt system is not set by the portable information terminal400-2. In this case, theprocessor401 carries outAct6, determining that the result of Act111 is ‘No’. That is, theprocessor401 wirelessly sends the registration start command containing the self-registration ID, the terminal ID, and the association flag F acquired from the self-registration management region W1.
On the other hand, the association flag F is detected if the association of the self-registration system with the electronic receipt system is set by the portable information terminal400-2. In this case, theprocessor401 carries out Act112, determining that the result of Act111 is ‘Yes’.
In Act112, theprocessor401 detects an electronic receipt ID from the self-registration management region W1. After detecting an electronic receipt ID, theprocessor401 carries outAct6. That is, theprocessor401 wirelessly sends the registration start command containing the self-registration ID, the terminal ID, and the electronic receipt ID and the association flag F acquired from the self-registration management region W1. The process next to Act6 of the fifth embodiment is the same as that next to Act6 of the first embodiment.
Then, similarly to the first embodiment, after thesupport server50 receives the registration start command, thesupport server50 carries out a process according to the procedure shown inFIG. 11. However,Act23 carried out in the fifth embodiment is partially different fromAct23 carried out in the first embodiment. That is, in the first embodiment, theprocessor501 creates acommodity transaction file510 according to the store information acquired inAct22, the self-registration ID, the terminal ID, and the information indicated by the association flag F which are contained in the received start command inAct23. In the fifth embodiment, inAct23, theprocessor501 creates acommodity transaction file510 according to the self-registration ID, the terminal ID, and the association flag F contained in the registration start command.
However, in addition to the self-registration ID, the terminal ID, and the association flag F, an electronic receipt ID may be also contained in the registration start command in some cases. In these cases, theprocessor501 creates a commodity transaction file510-2 inAct23. That is, theprocessor501 creates a commodity transaction file510-2 (storage module) according to the self-registration ID, the terminal ID, the electronic receipt ID and the association flag F that are contained in the received registration start command, and the store information acquired inAct22.
Further, like in the first embodiment, theprocessor101 of thePOS apparatus10 or20 receiving the request command carries out a process according to the procedure shown inFIG. 12. During the process, theprocessor101 adds the electronic receipt ID contained in the commodity transaction file510-2, together with the terminal ID, in the data of the electronic receipt inAct50. The self-registration ID is not attached to the electronic receipt. Theprocessor101 sends the electronic receipt associated with the electronic receipt ID and the terminal ID to theelectronic receipt server80.
Like in the first embodiment, theprocessor801 of theelectronic receipt server80 that receives the electronic receipt carries out the process according to the procedure shown inFIG. 13. During this process, as the ID associated with the electronic receipt is an electronic receipt ID, the result of Act63 should be ‘NO.’ Thus, Act64 is not executed. That is, in the fifth embodiment, the linkage table820 set in theelectronic receipt server80 is not needed.
Like in the first embodiment, in the fifth embodiment, the self-registration system can be associated with the electronic receipt system without increasing the workload of thecustomer4 andcashier3. Moreover, an electronic receipt corresponding to a commodity transaction conducted through the association of the self-registration system with the electronic receipt system can be retrieved from theelectronic receipt server80 by using the terminal ID of the portable information terminal400-2 used in the self-registration as a search key.
Sixth EmbodimentNext, a sixth embodiment is described. The present embodiment corresponds to the third embodiment, and the terminal ID is used for the self-registration, similarly to the fourth embodiment.
According to the sixth embodiment, the self-registration system can be associated with the electronic receipt system without increasing the workload of thecustomer4 andcashier3. An electronic receipt for a commodity transaction conducted through the association of the self-registration system with the electronic receipt system can be retrieved from theelectronic receipt server80 using the terminal ID of theportable information terminal400 used for the self-registration as a search key. Moreover, as an electronic receipt associated with an electronic receipt ID is sent to theelectronic receipt server80, a conventional electronic receipt can be used for theelectronic receipt server80. Although several embodiments are described, the present invention is not limited to the foregoing embodiments. For example, in the foregoing embodiments, whether or not to associate the self-registration system with the electronic receipt system can be set by thecustomer4. Alternatively, the association of the self-registration system with the electronic receipt system may be fixed. In this case, the association flag F is not needed. Further, theprocessor101 of thePOS apparatus10 or20 does not need to carry out Act47 shown inFIG. 12. Further, in the foregoing embodiments, thecustomer4 can select a type of receipt to receive, i.e., a paper receipt or an electronic receipt. Alternatively, the electronic receipt may be always selected, and the paper receipt as an option. In this case, Acts47,49, and51 shown inFIG. 12 may be omitted.
The second transmitting module can be any module that adds the self-registration ID to an electronic receipt and sends the processed electronic receipt to theelectronic receipt server80 when a self-registration ID is associated with the commodity sales data (commodity data) of commodity transaction to be settled, that is, the input of commodity data is through the self-registration operation with theportable information terminal400.
Further, in the foregoing embodiments, acustomer4 itself registers commodity data using theportable information terminal400, but the input of commodity data is not limited to the self-registration. For example, a shop clerk may accompany thecustomer4 and operate theportable information terminal400 to input the data of a commodity purchased by thecustomer4.
Further, in the foregoing embodiments, in order to determine aPOS apparatus10 or20 as a settlement object, thecustomer4 photographs the barcode of thePOS apparatus10 or20 using thecamera unit405. If theportable information terminal400 is provided with a NFC (Near Field Communication) reader, a NFC tag instead of abarcode7 may be attached to thePOS apparatus10 or20, so that the NFC reader can read a POS ID from the NFC tag.
Further, in the first embodiment, in Act64 theprocessor801 of theelectronic receipt server80 converts the self-registration ID to the electronic receipt ID with reference to the linkage table820. However, the conversion process may not be carried out. Theprocessor801 may only extract the electronic receipt ID which is set in the linkage table820 in association with the self-registration ID. That is, theprocessor801 may generate anelectronic receipt file810 containing the extracted electronic receipt ID and the electronic receipt, and stores the generatedelectronic receipt file810 in the electronic receipt region W5 in Act65.
Similarly, in Act81 of the third embodiment, theprocessor101 of the POS apparatus10-3 or20-3 converts the self-registration ID to an electronic receipt ID with reference to the linkage table820. Alternatively, theprocessor101 may extracts the electronic receipt ID set in the linkage table820 in association with the self-registration ID. Then, theprocessor101 may add the extracted electronic receipt ID to the electronic receipt and sends the processed electronic receipt to theelectronic receipt server80 inAct50.
For example, in the foregoing embodiments, inAct11 shown inFIG. 19, theprocessor401 of theportable information terminal400 embeds the self-registration ID in the barcode and wirelessly sends the barcode data containing the self-registration ID. Alternatively, inAct11, theprocessor401 may embeds the self-registration ID and the terminal ID in the barcode and wirelessly sends the barcode data.
Further, in the foregoing embodiments, in Act78 shown inFIG. 23, theprocessor401 of theportable information terminal400 displays an ID selection screen on thetouch panel404. That is, in the foregoing embodiments, the keys for searching electronic receipts include an electronic receipt ID and a terminal ID. Alternatively, only the terminal ID can be used as the key for searching the electronic receipts. That is, the electronic receipt that can be searched by theportable information terminal400 may also be limited to commodity transactions registered through the self-registration by theportable information terminal400. In this case, if the selection of the ‘view’ button B2 is received in Act76 (Act76: Yes), theprocessor401 sends a view request command containing the terminal ID to the electronic receipt server80 (Act82).
Further, in the foregoing embodiments, thestore server40 and thesupport server50 are located in theretail store100. Alternatively, the functions of both thestore server40 and thesupport server50 may be integrated in one server. Further, theportable information terminal400 is not necessarily carried by acustomer4. For example, theportable information terminal400 may be replaced by an information terminal mounted on a shopping cart.
Further, in the foregoing embodiments, theelectronic receipt server80 stores the electronic receipt in theelectronic receipt file810 in association with an electronic receipt ID and a terminal ID. Alternatively, theelectronic receipt server80 may store the electronic receipt in theelectronic receipt file810 only in association with the terminal ID. That is, the electronic receipt may not be stored in association with an electronic receipt ID. In this case, thecustomer4 using the electronic receipt system extracts the electronic receipt using the terminal ID of theportable information terminal400. That is, theprocessor501 may send the commodity data stored in thecommodity transaction file510, together with the terminal ID, to thePOS apparatus10 or20 designated by the data input from theportable information terminal400. When the terminal ID is associated with commodity data, theprocessor101 associates the terminal ID with an electronic receipt and then sends the electronic receipt associated with the terminal ID to theelectronic receipt server80. When the terminal ID is associated with an electronic receipt received from thePOS apparatus10 or20, the storage module stores the electronic receipt associated with the terminal ID.
While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the invention. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the invention. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the invention.