Transaction management system and server equipment

Abstract

It helps ensure that all steps necessary to complete a transaction are performed without fail. [Solution] The transaction management system comprises an acquisition means, a recording means, a reception means, an identification means, and a notification means. The acquisition means acquires wireless tag identification information that identifies the wireless tag attached to the basket. The recording means records the acquired wireless tag identification information, transaction identification information that identifies the transaction, and transaction information related to the transaction in association. The reception means accepts the input of wireless tag identification information. The identification means identifies the transaction information corresponding to the transaction identified by the wireless tag identification information and the corresponding transaction identification information. If the notification means determines that the transaction is incomplete based on the identified transaction information, it notifies the customer that the transaction is incomplete.

Description

Technical Field

[0004] ,

[0002] , , , , , , , , , , , , , , ,

[0005] , , ,

[0003]

[0001] Embodiments of the present invention relate to a transaction management system and a server device.

Background Art

[0002] Conventionally, a full self-checkout system (accounting system) in which a customer performs both product registration processing and accounting (settlement) processing is known. Also known is a semi-self-checkout system in which a store clerk performs product registration processing using a registration device and a customer performs accounting processing using an accounting device.

[0003] In an accounting system as described above, since the customer performs accounting himself / herself, there is a possibility of operational oversights such as forgetting to remove the credit card used for payment from the card reader and leaving the store as it is, or forgetting to pick up the change and leaving the store as it is. Thus, if a customer leaves the store without performing the operations necessary to complete the transaction, generally the customer will suffer a loss.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to assist in ensuring that the operations necessary to complete a transaction are performed without omission. ]

Means for Solving the Problems

[0005] The transaction management system of this embodiment comprises an acquisition means, a recording means, a receiving means, an identification means, and a notification means. The acquisition means acquires wireless tag identification information that identifies a wireless tag attached to a basket. The recording means records the acquired wireless tag identification information, transaction identification information that identifies a transaction, and transaction information related to the transaction in association. The receiving means accepts the input of wireless tag identification information. The identification means identifies the transaction information corresponding to the transaction identified by the wireless tag identification information and the corresponding transaction identification information. If the notification means determines that the transaction is incomplete based on the identified transaction information, it notifies the customer that the transaction is incomplete. [Brief explanation of the drawing]

[0006] [Figure 1] Figure 1 shows an example of the overall configuration of the transaction management system according to the embodiment. [Figure 2] Figure 2 is a perspective view showing an example of the appearance of the registration device according to this embodiment. [Figure 3] Figure 3 shows an example of the appearance of a basket according to this embodiment. [Figure 4] Figure 4 is a perspective view showing an example of the external appearance of the accounting device according to this embodiment. [Figure 5] Figure 5 is a perspective view showing an example of the external appearance of the accounting device according to this embodiment. [Figure 6] Figure 6 is a block diagram showing an example of the hardware and functional configuration of the registration device according to this embodiment. [Figure 7] Figure 7 is a block diagram showing an example of the hardware and functional configuration of the accounting device according to this embodiment. [Figure 8] Figure 8 is a block diagram showing an example of the hardware and functional configuration of a store server according to this embodiment. [Figure 9] Figure 9 is a block diagram showing an example of the hardware and functional configuration of the check device according to this embodiment. [Figure 10] Figure 10 is a flowchart showing an example of the processing performed by the registration device and store server according to the embodiment. [Figure 11] Figure 11 is a flowchart showing an example of the processing performed by the accounting device and store server according to the embodiment. [Figure 12] Figure 12 is a flowchart showing an example of the processing performed by the accounting device and store server according to the embodiment. [Figure 13] Figure 13 is a flowchart showing an example of the processing performed by the checking device and store server according to the embodiment. [Modes for carrying out the invention]

[0007] Figure 1 shows an example of the overall configuration of the transaction management system 100 according to the embodiment. The transaction management system 100 mainly comprises a registration device 2 (21, 22), accounting devices 3 (31-35), checking devices 4 (41, 42), and a store server 6. The registration device 2 and accounting devices 3 are examples of product sales data processing devices. The checking device 4 is an example of a notification device.

[0008] In this embodiment, the registration device 2, accounting device 3, and checking device 4 are installed in the store's accounting area 60, and the store server 6 is installed in the store's back room.

[0009] The registration devices 21 and 22 are installed and used on counters 51 and 52, respectively. The check device 4 is located near the exit of the accounting area 60. The check device 4 is a device for checking whether the transaction related to customer C has been completed when customer C leaves the accounting area 60.

[0010] Furthermore, a packing area for customers to transfer purchased items from their baskets into shopping bags or eco-bags is located outside the checkout area 60. These devices are connected to each other via a network NT such as a LAN (Local Area Network), enabling data communication. The connection method is not particularly limited; it may be a wired or wireless connection.

[0011] In Figure 1, an example is shown where two registration devices 2 and five accounting devices 3 are installed in the store's accounting area 60, but the number of each device is not limited to this. One or more registration devices 2 are sufficient, and there is no particular limit to the number of accounting devices 3, as long as there are two or more. Furthermore, the number of check devices 4 can be appropriately determined based on the relationship between the store's entrance and exit and the exit of the accounting area 60, etc.

[0012] In the following explanation, when describing each device without distinction, registration devices 21 and 22 will be referred to as registration device 2, and accounting devices 31 to 35 will be referred to as accounting device 3. Similarly, checking devices 41 and 42 will be referred to as checking device 4, and counters 51 and 52 will be referred to as counters 5.

[0013] An example of how to operate the accounting process according to this embodiment will be outlined. First, before starting the registration process, the operator O, who is a store employee, has the RFID tag 70 (see Figure 3) attached to the basket 80 (see Figure 3) read by the RFID reader 119 (see Figure 2) of the registration device 2. An RFID tag is an example of a wireless tag. As a result, the registration device 2 can obtain a tag ID that identifies the RFID tag 70.

[0014] The registration device 2, having acquired the tag ID, generates a transaction number. The transaction number is unique to each transaction. Since the transaction number can be used to identify a transaction, it is an example of transaction identification information. The registration device 2 associates the acquired tag ID with the generated transaction number and transmits it to the store server 6. The store server 6 associates the tag ID with the transaction number and registers it in the transaction information unit 672 (see Figure 8). Various information related to the transaction is sequentially registered in the transaction information unit 672.

[0015] After the registration device 2 transmits the tag ID and transaction number to the store server 6, operator O operates the registration device 2 to register the products that customer C will purchase. Operator O packs the products into the basket in the order that the registration process is completed. Once registration is complete for all products, the registration device 2 of this embodiment transmits the registration information to the store server 6. The store server 6 associates the registration information with the tag ID and transaction number and registers it in the transaction information unit 672.

[0016] After the registration process, customer C moves to the accounting device 3 with the basket 80 containing the registered products and starts the accounting process on the accounting device 3. When the accounting process is started, the accounting device 3 reads the tag ID from the RFID tag 70 attached to the basket 80, obtains transaction information including the registration information corresponding to the tag ID from the store server 6, and performs the accounting process based on the registration information.

[0017] After the accounting process is completed, the accounting device 3 sends an accounting completion notice indicating that the accounting process is completed to the store server 6. The tag ID and the transaction number are associated with the accounting completion notice. Further, the accounting completion notice includes the change collection information and the card collection information described later. The store server 6 registers information indicating that the accounting process is completed (hereinafter also referred to as accounting completion information) in the transaction information section 672 in association with the tag ID and the transaction number.

[0018] Also, when customer C makes a cash payment and there is change, and when the accounting device 3 detects that the change has been collected, the accounting device 3 sends a change collection notice indicating that the change has been collected to the store server. The tag ID and the transaction number are associated with the change collection notice. The store server 6 registers information indicating that the change has been collected in the transaction information section 672 in association with the tag ID and the transaction number.

[0019] Also, when customer C inserts a card related to settlement such as a point card or a credit card into the card reader 318, and when the accounting device 3 detects that the card has been removed, the accounting device 3 sends a card collection notice indicating that the card has been collected to the store server. The tag ID and the transaction number are associated with the card collection notice. The store server 6 registers information indicating that the card has been collected in the transaction information section 672 in association with the tag ID and the transaction number.

[0020] After the checkout process is complete, customer C moves to the checking device 4 with the basket 80 containing the items that have been checked out. The checking device 4 reads the tag ID from the RFID tag 70 attached to the basket 80, retrieves the transaction information corresponding to the tag ID from the store server 6, and performs a check to determine whether the transaction has been completed based on the transaction information.

[0021] The checking device 4 determines whether a transaction is complete based on whether the transaction information contains information indicating that the accounting process has been completed, information indicating that change has been collected if there is change, and information indicating that the card has been collected if customer C had inserted the card into the card reader 318. If it determines that the transaction is not complete, the checking device 4 provides notification based on the missing information (for example, no payment was made, change was not collected, the card was not removed, etc.).

[0022] Thus, the transaction management system 100 according to this embodiment can efficiently notify customer C if a process for completing a transaction has been missed.

[0023] The configuration of each device and the procedures performed by each device will be explained in more detail below.

[0024] First, the configuration of registration device 2 will be explained using Figure 2.

[0025] Figure 2 is a perspective view showing an example of the appearance of the registration device. As shown in Figure 2, the registration device 2 installed on the top surface of the counter 5 is based on a vertical scanner 111 having a reading window 112. The scanner 111 scans a laser beam over a code symbol (e.g., a barcode) attached to a product and reads the product code from the code symbol. The scanner 111 may also identify products included in the captured image using general object recognition techniques.

[0026] Furthermore, the registration device 2 is equipped with an operator display 114 and an operation unit 115 on top of the scanner 111. The operator display 114 displays the product name and price of the product captured by the imaging unit of the scanner 111. A touch panel 113 is provided on the surface of the operator display 114. The touch panel 113 and the operation unit 115 are for assisting in the input of product information.

[0027] A printer 116 is located to the left of the operator display 114. The printer 116 prints various information. A card reader 118 is located to the right of the operator display 114. The card reader 118 magnetically reads and writes information to magnetic cards such as point cards inserted through the slot 1181. A customer display 117 is located on the back side of the printer 116, opposite the display surface of the operator display 114.

[0028] Furthermore, the registration device 2 is equipped with an RFID reader 119 at the bottom of the scanner 111. The RFID reader 119 reads the tag ID from the RFID tag 70 attached to the basket 80 via short-range wireless communication. After reading the tag ID, the registration device 2 generates a transaction number, associates it with the tag ID, and transmits it to the store server 6.

[0029] Here, Figure 3 shows an example of the appearance of the basket 80. An RFID tag 70 is attached to the basket 80. The attachment position of the RFID tag 70 should be such that it corresponds to the radio wave radiation range of the RFID reader 303 (see Figure 5) of the accounting device 3, which will be described later.

[0030] Furthermore, as will be described later, the RFID tag 70 is read by the checking device 4, so it is desirable that the RFID tag 70 be attached to a location where it can be read from a distance of several meters.

[0031] Note that Figure 3 illustrates an example where a large RFID tag 70 is attached to a basket 80 for ease of explanation. However, the size of the RFID tag 70 only needs to be large enough to be read by each of the multiple RFID readers provided by the transaction management system 100.

[0032] The registration device 2 reads codes such as barcodes and 2D codes attached to products and identifies products based on the product codes contained in those codes. The registration device 2 displays a screen on the operator display 114 that allows the operator to confirm the identified product based on the product code and to input information such as the quantity.

[0033] Then, based on the product code of the product that was received as input, the input quantity, and other information, the registration device 2 reads product information such as the product category, product code, product name, and unit price of the product corresponding to the product code from the PLU file Fa (see Figure 6) and stores it as sales data in the sales file Fb (see Figure 6).

[0034] Once all products have been registered, the registration device 2 generates registration information including the total amount and the number of points awarded, and sends it to the store server 6, associating it with the tag ID obtained by reading the RFID tag 70 with the generated transaction number using the RFID reader 119.

[0035] Next, the configuration of accounting device 3 will be explained using Figure 4.

[0036] Figure 4 is a perspective view showing an example of the external appearance of the accounting device 3. As shown in Figure 4, the accounting device 3 comprises a first housing 301 and a second housing 302.

[0037] The first housing 301 includes a scanner 317 and a change dispenser 320. The scanner 317 has the same structure as scanner 111 (see Figure 6) and is used for adding forgotten items and reading coupon codes, etc. The change dispenser 320 includes a banknote slot 321, a banknote dispensing slot 322, a coin slot 323, and a coin dispensing section 324.

[0038] The change dispenser 320 stores banknotes inserted into the banknote slot 321 in a banknote storage section (not shown). The change dispenser 320 also stores coins inserted into the coin slot 323 in a coin storage section (not shown).

[0039] Then, in response to a change dispensing request from the control unit 340 (see Figure 7), the change dispenser 320 dispenses banknote change into the banknote dispensing slot 322. The change dispenser 320 also dispenses coin change into the coin dispensing unit 324 in response to a change dispensing request from the control unit 340.

[0040] The second housing 302 is located on the top surface 3011 of the first housing 301 and includes a display unit 315, a card reader 318, and a printer 319.

[0041] The display unit 315 is mounted above the second housing 302 and consists of a liquid crystal panel with a touch panel 316 on its surface. The card reader 318 reads and writes information to point cards, credit cards, etc., inserted through the card slot 3181. The printer 319 prints receipts and issues them from the receipt issuing slot 3191, according to the control of the control unit 50.

[0042] Furthermore, the accounting device 3 is equipped with a cylindrical display pole 325 erected on the rear side of the upper surface 3011 of the first housing 301. The display pole 325 has a light-emitting part 326 at its upper tip that selectively emits blue or red light.

[0043] The light-emitting unit 326 changes color and emits light according to the processing status in the accounting device 3 to alert the store staff.

[0044] Furthermore, the processing conditions for illumination, the illumination color, and the illumination pattern can all be set as appropriate. Since the light-emitting unit 326 is located at the top of the tall display pole 325, it is easily visible not only to the operator of the registration device 2 but also to other store employees. The illumination is also easily visible from the position of the registration device 2, making it easy for customers standing in front of the registration device 2 to visually confirm.

[0045] Furthermore, the display pole 325 has an information display unit 327 below the light-emitting unit 326. The information display unit 327 is, for example, made up of a liquid crystal panel and displays image information and text information. The information display unit 327 is fixedly installed with its display surface facing the same direction as the display unit 315. The information display unit 327 displays, for example, the details of an error that occurred in the accounting device 3.

[0046] A mounting platform 329 for placing the basket 80 is provided on the side 3012 of the first housing 301. A hook for hanging the hand scanner 328 is provided on the front side of the mounting platform 329. The hand scanner 328, like the scanner 317, is used for adding forgotten items to a purchase list and reading coupon codes, etc.

[0047] The accounting device 3 of this embodiment includes an RFID reader 303 for reading RFID tags 70 inside the first housing 301. For example, as shown in Figure 4, the RFID reader 303 is provided on the side surface 3012 of the first housing 301. Next, the positional relationship between the RFID reader 303 and the RFID tag 70 when reading the RFID tag 70 will be explained using Figure 5.

[0048] Figure 5 shows an example of the appearance of the accounting device 3 when the basket 80 shown in Figure 3 is placed on the mounting base 329. The RFID reader 303 is positioned to read the RFID tag 70 (see Figure 3) attached to the basket 80 placed on the mounting base 329.

[0049] Here, the basket 80 is placed on the mounting base 329 such that the length of the basket 80 is aligned with the depth of the mounting base 329. By placing the basket 80 in this manner, the width of the accounting device 3 is made more compact.

[0050] As described above, when a customer places the basket 80 on the stand 329 as shown in Figure 5, the RFID tag 70 comes within the range that the RFID reader 303 can read. Therefore, the customer can have the RFID reader 303 read the RFID tag 70 without consciously trying to have it read.

[0051] Next, the general procedure for accounting will be explained. First, the customer takes the basket 80 from the counter 5 of the registration device 2, moves to an empty accounting device 3, and places the basket 80 on the display stand 329 of the accounting device 3.

[0052] When the RFID reader 303 reads the tag ID from the RFID tag 70, the accounting device 3 queries the store server 6 for transaction information corresponding to that tag ID. Based on the registration information contained in the transaction information read from the store server 6, the accounting device 3 displays information such as the total amount on the display 315 and starts the accounting process. The customer operates the accounting device 3 to complete the accounting process and pay for the goods using cash, credit card, electronic money, etc.

[0053] Next, the hardware and functional configuration of registration device 2 will be described.

[0054] Figure 6 is a block diagram showing the hardware and functional configuration of the registration device 2. As shown in Figure 6, the registration device 2 includes a control unit 150.

[0055] The control unit 150 consists of a CPU (Central Processing Unit) that executes control processing, and storage media such as ROM (Read Only Memory) and RAM (Random Access Memory) (neither of which are shown in the diagram). The ROM stores various programs and data executed by the CPU. The RAM temporarily stores data and programs when the CPU executes various programs.

[0056] The control unit 150 is connected to the scanner 111, the touch panel 113, the keyboard and other operation unit 115, the printer 116, the customer display 117, the card reader 118, the RFID reader 119, and the HDD (Hard Disk Drive) 136 via the I / O (Input / Output) device control unit 139 and the bus 138. The control unit 150 may also be connected to other devices such as an electronic money reader.

[0057] Furthermore, the control unit 150 communicates data with the store server 6, which is connected via the network NT (see Figure 1), through the communication interface 140.

[0058] The operation unit 115 is equipped with operation keys such as the current total key 1151 and the confirmation key 1152. The current total key 1151 is an operation key that receives an instruction to close a transaction and move on to payment processing (accounting processing) for that transaction, and is used to update the total amount. The confirmation key 1152 is an operation key used to confirm the total amount by inputting information such as customer type.

[0059] The registration device 2 transmits the registration information when the confirmation key 1152 is operated as a trigger. The aforementioned operation keys may be displayed on the operator display 114, and the selection operation may be accepted via the touch panel 113.

[0060] HDD136 stores the program 137 executed by the CPU of the control unit 150, the PLU file Fa, and the sales file Fb. PLU file Fa stores the product code uniquely assigned to each product, along with product information such as the product name, price, and product category.

[0061] Furthermore, if the registration device 2 is configured to identify products using general object recognition, the PLU file Fa will also store the feature quantities or reference image of each product. Feature quantities are data such as color and surface texture read from the reference image of the product. The sales file Fb is a file that stores the sales data registered by the registration device 2.

[0062] Next, the program 137 executed by the registration device 2 will be described. The program 137 executed by the registration device 2 in this embodiment is provided pre-installed on the HDD 136, etc.

[0063] Furthermore, the program 137 executed by the registration device 2 in this embodiment may be configured to be provided as a file in an installable or executable format, recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk).

[0064] Furthermore, the program 137 executed by the registration device 2 of this embodiment may be configured to be stored on a computer connected to a network such as the Internet and provided by downloading it via the network. Alternatively, the program 137 executed by the registration device 2 of this embodiment may be provided or distributed via a network such as the Internet.

[0065] As shown in Figure 6, the program 137 has a modular configuration including a display control unit 151, a wireless tag reading unit 152, a transaction number generation unit 153, an input reception unit 154, a registration unit 155, and a data communication unit 156. The CPU (processor) of the control unit 150 reads the program 137 from the HDD 136 and loads each of the above units into the main memory. As a result, each of the above units is created in the main memory.

[0066] The display control unit 151 generates display data to be output to the operator display unit 114 and the customer display unit 117, and controls the display processing on these displays. For example, the display control unit 151 displays a registration screen for product registration processing on the operator display unit 114. Also, when the confirmation key 1152 is operated, the display control unit 151 displays a message such as "Please move to the payment machine and make a payment" on the customer display unit 117.

[0067] The wireless tag reader 152 controls the reading of the tag ID by controlling the RFID reader 303.

[0068] Specifically, the wireless tag reader 152 controls the RFID reader 119 and causes its antenna (not shown) to transmit radio waves to communicate with the RFID tag 70 attached to the basket 80 containing the items the customer intends to purchase. The wireless tag reader 152 also obtains the tag ID received by the antenna from the RFID tag 70 via the RFID reader 119.

[0069] The transaction number generation unit 153 generates a transaction number for each transaction. For example, the transaction number generation unit 153 generates a transaction number after the tag ID is obtained by the wireless tag reader unit 152. Specifically, the transaction number generation unit 153 generates a transaction number that can identify a transaction by combining the date and time, the identification number of the registration device 2, and a sequence number (for example, a number that starts with "1" for the first transaction of the day and increments by 1 each time the next transaction begins).

[0070] The input receiving unit 154 receives various inputs from the scanner 111, touch panel 113, operation unit 115, and card reader 118.

[0071] When the product code and name of a product to be sold are entered via the scanner 111 and touch panel 113, the registration unit 155 reads the product information of that product from the PLU file Fa. Then, when an instruction to end a transaction is entered via the totaling key 1151, the registration unit 155 terminates the product registration process for that transaction and calculates the total amount for that transaction.

[0072] The registration unit 155 then generates registration information used for accounting processing, including product information for all products registered in the transaction, the total amount related to the transaction, identification information for the registration device 2, and employee information to identify the employee in charge.

[0073] The data communication unit 156 controls data communication with the store server 6, which is connected via the communication interface 140.

[0074] For example, after a transaction number is generated by the transaction number generation unit 153, the data communication unit 156 associates the tag ID obtained by the wireless tag reader unit 152 with the transaction number generated by the transaction number generation unit 153 and transmits it to the store server 6. Alternatively, for example, the data communication unit 156 associates the registration information generated by the registration unit 155 with the tag ID obtained by the wireless tag reader unit 152 and the transaction number generated by the transaction number generation unit 153 and transmits it to the store server 6.

[0075] Next, the hardware and functional configuration of accounting device 3 will be described.

[0076] Figure 7 is a block diagram showing an example of the hardware and functional configuration of the accounting device 3. The accounting device 3 includes a CPU and a control unit 340 which is a computer configuration consisting of a CPU and storage media such as ROM and RAM (neither of which are shown). The ROM stores various programs and data executed by the CPU. The RAM temporarily stores data and programs when the CPU executes various programs.

[0077] The control unit 340 is connected to the display unit 315, touch panel 316, scanner 317, card reader 318, printer 319, change dispenser 320, light-emitting unit 326, information display unit 327, hand scanner 328, RFID reader 303, and HDD 305 via the I / O device control unit 314 and bus 312. The control unit 340 communicates data with the store server 6, which is connected via network NT, via the communication interface 313.

[0078] The card reader 318 reads information from a card (such as a loyalty card or credit card) inserted through the card slot 3181.

[0079] The printer 319 prints a receipt after payment and issues it from the receipt issuing slot 3191. The change dispenser 320 processes the deposit of banknotes inserted into the banknote slot 321 or coins inserted into the coin slot 323. The change dispenser 320 also dispenses change from the banknote dispensing slot 322 or the coin dispensing section 324 in response to a dispensing instruction from the control unit 340.

[0080] HDD305 stores the program 3051 executed by the control unit 340 and the transaction file Fc. The transaction file Fc is a data file for storing data (transaction data) related to accounting processing performed by the accounting device 3 based on registration information received from the store server 6.

[0081] Next, we will describe the program 3051 executed by the accounting device 3.

[0082] Furthermore, the program 3051 executed by the accounting device 3 in this embodiment is provided pre-installed on the HDD 305.

[0083] Furthermore, the program 3051 executed by the accounting device 3 in this embodiment may be configured to be provided as a file in an installable or executable format, recorded on a computer-readable recording medium such as a CD-ROM, floppy disk, CD-R, or DVD.

[0084] Furthermore, the program 3051 executed by the accounting device 3 of this embodiment may be stored on a computer connected to a network such as the Internet and provided by downloading it via the network. Alternatively, the program 3051 executed by the accounting device 3 of this embodiment may be provided or distributed via a network such as the Internet.

[0085] As shown in Figure 8, the program 3051 has a modular configuration including a display control unit 341, a wireless tag reader unit 342, an input reception unit 343, a data communication unit 344, an accounting processing unit 345, and an error output unit 346. The CPU (processor) of the control unit 340 reads the program 3051 from the HDD 305 and loads each of the above units into the main memory. As a result, each of the above units is created in the main memory.

[0086] The display control unit 341 controls the display operation of the display unit 315 and the information display unit 327.

[0087] The wireless tag reader 342 controls the reading of the tag ID by controlling the RFID reader 303.

[0088] Specifically, the wireless tag reader 352 controls the RFID reader 303 and causes the antenna (not shown) of the RFID reader 303 to transmit radio waves to communicate with the RFID tag 70 attached to the basket 80 containing the registered products. The wireless tag reader 352 also obtains the tag ID received by the antenna from the RFID tag 70 via the RFID reader 303.

[0089] The input reception unit 343 receives various inputs from the touch panel 316, scanner 317, card reader 318, change dispenser 320, hand scanner 328, etc.

[0090] The data communication unit 344 controls data communication with the store server 6 connected via the communication interface 313 and the network NT.

[0091] The accounting processing unit 345 queries the store server 6 for the tag ID obtained by the wireless tag reader 342 and obtains transaction information corresponding to the tag ID from the transaction information unit 672 of the store server 6. Then, the accounting processing unit 345 processes the total amount of the registered information included in the obtained transaction information using the payment method selected by the customer via the touch panel 316.

[0092] In other words, if the payment is made in cash, the accounting processing unit 345 controls the change dispenser 320 to count the amount deposited from the coin slot 323 or the banknote slot 321, calculates the change, and then dispenses the change from the coin dispensing unit 324 or the banknote dispensing slot 322.

[0093] In the case of credit card payments, the accounting processing unit 345 reads the card information from the card reader 318, sends it along with the payment amount to the payment server (not shown), and performs the payment processing.

[0094] Furthermore, in the case of electronic money payment, the accounting processing unit 345 uses an electronic money reader (not shown) to access a contactless card or smartphone, etc., that electronically stores monetary information, using near-field communication technology such as NFC (Near Field Communication). The accounting processing unit 345 then executes the payment process using the amount of payment information stored on the card or smartphone, etc.

[0095] Furthermore, after the accounting processing is completed, the accounting processing unit 345 works in cooperation with the data communication unit 344 to transmit accounting completion information to the store server 6, associating it with the tag ID obtained by the wireless tag reader unit 342 and the transaction number included in the acquired transaction information. Accounting completion information is an example of status information.

[0096] Furthermore, when a cash payment is made, the accounting processing unit 345, in cooperation with the data communication unit 344, transmits change collection information to the store server 6, associating it with the tag ID and transaction number. Change collection information is an example of status information.

[0097] Here, as an example of change collection information, when a cash payment is made, a flag indicating whether or not there is change (hereinafter also called the change availability flag) and a flag indicating that the change has been collected (hereinafter also called the change collection flag) are set in the transaction information unit 672. If the value of the change availability flag is the initial value of 0, then there is no change, and if the value of the change availability flag is 1, then there is change.

[0098] Furthermore, if the value of the change collection flag is the initial value of 0, it means that the change has not been collected, and if the value of the change collection flag is 1, it means that the change has already been collected.

[0099] Furthermore, if a cash payment is made but no change is available, the flag indicating the presence or absence of change and the flag indicating the collection of change may not be set. Only if change is available, the flag indicating the presence or absence of change and the flag indicating the collection of change may be set in the transaction information unit 672. In this case, setting only the flag indicating the collection of change may be considered as change collection information.

[0100] Furthermore, the collection of change can be detected by known techniques, such as using a proximity sensor to measure the distance between the coin and the sensor and detecting the presence or absence of the coin based on that distance. For example, the accounting processing unit 345 executes a process to detect that the change has been collected after a predetermined time (e.g., 60 seconds) has elapsed since the completion of the payment.

[0101] Furthermore, the accounting processing unit 345 works in cooperation with the data communication unit 344 to transmit card retrieval information to the store server 6, associating it with the tag ID and transaction number. Card retrieval information is an example of status information.

[0102] Here, as an example of card retrieval information, when a card is inserted into the card slot 3181 of the card reader 318, a flag indicating whether a card has been inserted (hereinafter also called the card insertion flag) and a flag indicating card retrieval (hereinafter also called the card retrieval flag) are set in the transaction information unit 672. If the value of the card insertion flag is the initial value of 0, then no card has been inserted, and if the value of the card insertion flag is 1, then a card has been inserted.

[0103] Furthermore, if the card retrieval flag value is the initial value of 0, it means the card has not been retrieved, and if the card retrieval flag value is 1, it means the card has already been retrieved.

[0104] Furthermore, the presence or absence of a card can be detected by known techniques, such as using a circuit equipped with a mechanical switch and a current sensor to detect the presence or absence of a card based on the difference in current flowing through the circuit when a card is inserted and when it is not. As an example, the accounting processing unit 345 executes a process to detect that the card has been collected after a predetermined time (e.g., 60 seconds) has elapsed since the completion of the settlement.

[0105] The error output unit 346 performs error output processing if the accounting process does not complete successfully. For example, the error output unit 346 performs error output processing if the payment process cannot be completed within a predetermined time due to a communication error or the like in a credit card payment.

[0106] For example, in error output processing, the error output unit 346 lights up the light-emitting unit 326 in red and displays information indicating the occurrence of an error on the information display unit 327 to notify attendants and other staff of the error. In this case, the error output unit 346 also outputs a message to the display unit 315 indicating that the payment process could not be completed even after a predetermined time has elapsed.

[0107] The destination for error output is not limited to the above. The error output unit 346 may output the transaction number and error information to the store server 6, and display information identifying the source accounting device 3, the transaction number, and the error status on the display unit 66 of the store server 6. The store server 6 may record the error status in the transaction information unit 672 based on the received error information.

[0108] Next, we will describe the hardware and functional configuration of store server 6.

[0109] Figure 8 is a block diagram showing an example of the hardware and functional configuration of the store server 6. The store server 6 includes a control unit 340 which is a computer configuration consisting of a CPU, and storage media such as ROM and RAM (neither of which are shown). The ROM stores various programs and data executed by the CPU. The RAM temporarily stores data and programs when the CPU executes various programs.

[0110] The control unit 61 is connected to the operation unit 65 such as a keyboard, the display unit 66, and the HDD 67 via the bus 62 and the I / O device control unit 64. The control unit 61 communicates data with the registration device 2, the accounting device 3, and the check device 4 via the communication interface 63 and the network NT.

[0111] HDD67 stores the program 671 executed by the control unit 61 and the transaction information unit 672. The transaction information unit 672 (accounting information storage means) is a data file that stores accounting numbers and accounting data received from the registration device 2 in association with each other.

[0112] Next, the program 671 executed by the store server 6 will be described. In this embodiment, the program 671 executed by the store server 6 is provided pre-installed on the HDD 67.

[0113] Furthermore, the program 671 executed by the store server 6 in this embodiment may be configured to be provided as a file in an installable or executable format, recorded on a computer-readable recording medium such as a CD-ROM, floppy disk, CD-R, or DVD.

[0114] Furthermore, the program 671 executed by the store server 6 of this embodiment may be configured to be stored on a computer connected to a network such as the Internet and provided by downloading it via the network. Alternatively, the program 671 executed by the store server 6 of this embodiment may be provided or distributed via a network such as the Internet.

[0115] As shown in Figure 9, program 671 has a modular configuration including a data communication unit 611, a transaction information management unit 612, a response unit 613, and a cart management unit 614. The CPU (processor) of the control unit 61 reads program 671 from the HDD 67 and loads each of the above units into the main memory. As a result, each of the above units is created in the main memory.

[0116] The data communication unit 611 controls data communication between the registration device 2, accounting device 3, and check device 4, which are connected via the communication interface 63 and network NT. The data communication unit 611 is an example of an acquisition means, a receiving means, and a data reception means.

[0117] The transaction information management unit 612 stores various information related to the completion of a transaction in the transaction information unit 672. The transaction information management unit 612 is an example of a recording means.

[0118] For example, when the transaction information management unit 612 receives the tag ID and transaction number from the registration device 2 via the data communication unit 611, it associates the tag ID and transaction number and stores them in the transaction information unit 672. Here, the fact that only the tag ID and transaction number are stored in the transaction information unit 672 indicates that the registration process has started in the registration device 2, but the transaction has not yet been completed.

[0119] Furthermore, for example, when the transaction information management unit 612 receives the tag ID, transaction number, and registration information from the registration device 2 via the data communication unit 611, it stores the registration information in the transaction information unit 672, associating it with the tag ID and transaction number.

[0120] Here, the fact that the transaction information unit 672 stores the tag ID, transaction number, and registration information indicates that the registration process has been completed in the registration device 2.

[0121] Furthermore, for example, when the transaction information management unit 612 receives an accounting completion notice from the accounting device 3 via the data communication unit 611, it stores the accounting completion information in the transaction information unit 672, associating it with the tag ID and transaction number included in the accounting completion notice.

[0122] Here, the fact that the transaction information unit 672 stores the tag ID, transaction number, and accounting completion information indicates that the accounting process has been completed in the accounting device 3.

[0123] Furthermore, for example, when the transaction information management unit 612 receives change collection information from the accounting device 3 via the data communication unit 611, it stores the change collection information in the transaction information unit 672, associating it with the tag ID and transaction number included in the change collection notice.

[0124] If there is no change available, the transaction information management unit 612 stores the change collection information in the transaction information unit 672 with the change availability flag set to flag value = 0 and the change collection flag set to flag value = 0. The fact that the change availability flag and the change collection flag are stored as change collection information indicates that the cash accounting process has been completed in the accounting device 3 and there is no change available.

[0125] On the other hand, if there is change to be given, the transaction information management unit 612 stores the change collection information in the transaction information unit 672 with the change availability flag set to flag value = 1 and the change collection flag set to flag value = 0. The fact that the change availability flag is set to flag value = 1 and the change collection flag is set to flag value = 0 in the change collection information indicates that the cash accounting process has been completed in the accounting device 3 and the change has not yet been collected.

[0126] Furthermore, for example, when the transaction information management unit 612 receives a change collection notification from the accounting device 3 via the data communication unit 611, it sets the change collection flag in the change collection information to flag value = 1, associates it with the tag ID and transaction number included in the change collection notification, and stores it in the transaction information unit 672.

[0127] Here, the fact that the transaction information unit 672 stores a change collection flag value of 1 as change collection information, associated with the tag ID and the transaction number, indicates that the accounting device 3 has completed cash accounting processing and has also completed the collection of change.

[0128] Furthermore, for example, when the transaction information management unit 612 receives card collection information from the accounting device 3 via the data communication unit 611, it stores the card collection information in the transaction information unit 672, associating it with the tag ID and transaction number included in the change collection notice.

[0129] If no card is inserted, the transaction information management unit 612 stores the card insertion status flag with a value of 0 and the card recovery flag with a value of 0 in the transaction information unit 672 as card recovery information. The fact that the card insertion status flag has a value of 0 and the card recovery flag has a value of 0 in the card recovery information indicates that the accounting process has been completed in the accounting device 3 and no card has been inserted.

[0130] On the other hand, if a card is inserted, the transaction information management unit 612 stores the card retrieval information in the transaction information unit 672 with the card presence flag set to flag value = 1 and the card retrieval flag set to flag value = 0. The fact that the change presence flag is set to flag value = 1 and the change retrieval flag is set to flag value = 0 as card retrieval information indicates that the accounting process has been completed in the accounting device 3 and the card has not been retrieved.

[0131] Furthermore, for example, when the transaction information management unit 612 receives a card retrieval notification from the accounting device 3 via the data communication unit 611, it sets the card retrieval flag in the card retrieval information to a flag value of 1, associates it with the tag ID and transaction number included in the card retrieval notification, and stores it in the transaction information unit 672.

[0132] Here, the fact that the transaction information unit 672 stores a card retrieval flag value of 1 as card retrieval information, associated with the tag ID and transaction number, indicates that the accounting process has been completed by the accounting device 3 and the card has also been retrieved.

[0133] The response unit 613 responds to inquiries about transaction information. The response unit 613 is an example of a specific means.

[0134] For example, when the response unit 613 receives a first query including a tag ID from the accounting device 3 via the data communication unit 611, it refers to the transaction information unit 672 and identifies the transaction number and registration information associated with the tag ID. The response unit 613 works in cooperation with the data communication unit 611 and transmits transaction information, including the tag ID sent from the accounting device 3, the identified transaction number, and the registration information, to the accounting device 3 as a response to the first query.

[0135] Furthermore, if the transaction number and registration information are not associated with the tag ID included in the first inquiry, the response unit 613 sends a notification to the accounting device 3 in response to the first inquiry indicating that the registration process at the registration device 2 has not been completed. This allows the system to prompt customers who have moved to the accounting device 3 without completing the registration process to move back to the registration device 2.

[0136] Furthermore, for example, when the response unit 613 receives a second inquiry including a tag ID from the check device 4 via the data communication unit 611, it refers to the transaction information unit 672 and identifies the transaction number associated with the tag ID and various information related to the transaction.

[0137] Then, the response unit 613, in cooperation with the data communication unit 611, transmits transaction information to the check device 4, including the tag ID transmitted from the check device 4, the identified transaction number, and various information related to the transaction, as a response to the second inquiry.

[0138] Furthermore, if the transaction information unit 672 does not have any information associated with the tag ID included in the second query, the response unit 613 will send only the tag ID included in the second query to the check device 4 as transaction information (sending empty transaction information to the check device 4).

[0139] The basket management unit 614 manages the baskets 80 within the store.

[0140] For example, the basket management unit 614 detects the location of each of the multiple baskets 80 within the store. Based on the location of each of the multiple baskets 80 within the store, the basket management unit 614 also detects whether a basket 80 is lingering in the basket 80 collection area or whether a basket 80 has been left unattended in a location other than the collection area. The collection area is located outside the checkout area 60.

[0141] Furthermore, the basket management unit 614 sends notifications to multiple registration devices 2 within the store indicating that baskets 80 are accumulating in the collection area or have been left unattended in a location other than the collection area. This allows store employees operating each registration device 2 to be aware that baskets 80 are accumulating in the collection area or have been left unattended in a location other than the collection area, and to take action to resolve these issues.

[0142] The following describes an example of the process for detecting the location of multiple baskets 80. For example, multiple RFID readers (not shown) are distributed throughout the store. The multiple RFID readers also constantly transmit radio waves to communicate with the RFID tags 70 attached to the baskets 80. When the multiple RFID readers read a tag ID from an RFID tag 70, they associate the tag ID with a reader ID that identifies the RFID reader and transmit it to the store server 6.

[0143] The store server 6 stores information on an HDD 67 or the like that associates a reader ID with the location where the RFID reader identified by that reader ID is located. The basket management unit 614 detects the location of the basket 80 to which the RFID tag 70 identified by the tag ID is attached, based on the location of each of the multiple RFID readers in the store and the information that associates the tag IDs transmitted from each of the multiple RFID readers with the reader ID.

[0144] Furthermore, if the basket management unit 614 detects that the basket 80 has left the checkout area 60, it sends information to the transaction information management unit 612 indicating this fact. Upon receiving this information, the transaction information management unit 612 deletes all information associated with the tag ID of the RFID tag 70 attached to the basket 80 from the transaction information unit 672. This allows the transaction information management unit 612 to manage the transaction status even if the basket 80 is subsequently used by another customer.

[0145] Furthermore, the transaction information management unit 612 may store all information associated with the tag ID of the RFID tag 70 attached to the basket 80 that has moved out of the accounting area 60 as completed transaction information in a separate location from the transaction information unit 672.

[0146] Next, the hardware and functional configuration of the check device 4 will be described.

[0147] Figure 9 is a block diagram showing the hardware and functional configuration of the check device 4. The check device 4 includes a control unit 40 which is a computer configuration consisting of a CPU, ROM, RAM, etc. An RFID reader 45, a display 46, a warning light 47, and a speaker 48 are connected to the control unit 40 via a bus 49 and an I / O device control unit 44. The control unit 40 communicates data with the store server 6 via a communication interface 43 and a network NT.

[0148] The display unit 46 displays information to the customer that represents cautions and warnings related to the transaction. For example, the display unit 46 displays messages to inform the customer that the payment process may not be completed, that change may have been forgotten to be collected, and that the customer may have forgotten to remove their card.

[0149] Warning light 47 alerts store staff to transaction-related notices and warnings. For example, warning light 47 illuminates red to alert staff that a customer may be attempting to leave the checkout area 60 without paying. Alternatively, warning light 47 illuminates yellow to alert staff that a customer may have forgotten to collect their change or card.

[0150] Speaker 48 outputs audio information to the customer that represents cautions or warnings related to the transaction. For example, speaker 48 outputs an audio warning message to the customer that the payment process may not be completed. In addition, by outputting audio, not only the customer but also people in the surrounding area, including store staff and other customers who cannot see the display 46, can understand that there is some kind of problem related to the transaction.

[0151] Next, the program executed by the check device 4 will be described. The program executed by the check device 4 in this embodiment is pre-installed and provided in the ROM of the control unit 40.

[0152] Furthermore, the program executed by the check device 4 in this embodiment may be configured to be provided as a file in an installable or executable format, recorded on a computer-readable recording medium such as a CD-ROM, floppy disk, CD-R, or DVD.

[0153] Furthermore, the program executed by the checking device 4 of this embodiment may be stored on a computer connected to a network such as the Internet and provided by downloading it via the network. Alternatively, the program executed by the checking device 4 of this embodiment may be provided or distributed via a network such as the Internet.

[0154] As shown in Figure 9, the program executed by the check device 4 has a modular configuration including a wireless tag reader 401, a transaction status inquiry unit 402, an error output unit 403, and a data communication unit 404. The CPU (processor) of the control unit 40 reads the program from the ROM and loads each of the above units into the main memory. As a result, each of the above units is created in the main memory.

[0155] The wireless tag reader 401 controls the reading of the tag ID by controlling the RFID reader 45.

[0156] Specifically, the wireless tag reader 401 controls the RFID reader 45 and causes the antenna (not shown) of the RFID reader 45 to transmit radio waves to communicate with the RFID tag 70 attached to the basket 80 containing the paid-for items. The wireless tag reader 401 also obtains the tag ID received by the antenna from the RFID tag 70 via the RFID reader 45.

[0157] The transaction status inquiry unit 402 queries the store server 6 with the tag ID acquired by the wireless tag reader unit 401 and inquires about the transaction status of the transaction identified by the transaction number corresponding to that tag ID.

[0158] The error output unit 403 determines whether the transaction can be completed and outputs an error if it determines that the transaction cannot be completed. The error output unit 403 is an example of a notification means.

[0159] For example, if the transaction information sent from the store server 6 as a response to the second inquiry does not associate the transaction number and registration information with the tag ID read by the wireless tag reader 401, the error output unit 403 determines that the registration process is not complete and performs an error output process.

[0160] For example, in the error output processing, the error output unit 403 displays a warning message indicating that the registration process may not be completed. The error output unit 403 may also illuminate the warning light 47 to notify attendants or other staff of the error. The error output unit 403 may also control the speaker 48 to output an audible warning message indicating that the registration process may not be completed.

[0161] This allows the error output unit 413 to prompt customers who attempt to leave the checkout area 60 without completing the registration process to move to the registration device 2.

[0162] Furthermore, for example, if the transaction information sent from the store server 6 as a response to the second inquiry does not associate the accounting completion information with the tag ID read by the wireless tag reader 401, the error output unit 403 determines that the accounting process is not yet complete and performs an error output process.

[0163] For example, in the error output processing, the error output unit 403 outputs a warning message on the display unit 46 indicating that there may be an outstanding payment. The error output unit 403 may also illuminate the warning light 47 to notify the attendant or other staff that an error has occurred. The error output unit 403 may also control the speaker 48 to output an audible warning message indicating that there may be an outstanding payment.

[0164] This allows the error output unit 413 to prompt customers who attempt to leave the accounting area 60 without completing the accounting process to do so.

[0165] Furthermore, for example, if the transaction information sent from the store server 6 as a response to the second query shows that the change collection information associated with the tag ID read by the wireless tag reader 401 has a change availability flag value of 1 and a change collection flag value of 0, the error output unit 403 determines that the change has not been collected and performs an error output process.

[0166] This allows the error output unit 413 to prompt a customer who is about to leave the checkout area 60 without collecting their change to go and collect it.

[0167] Furthermore, for example, if the transaction information sent from the store server 6 as a response to the second inquiry contains card retrieval information associated with the tag ID read by the wireless tag reader 401, and the flag value of the card insertion status flag is 1 and the flag value of the card retrieval flag is 0, the error output unit 403 determines that the card has not been retrieved and performs error output processing.

[0168] This allows the error output unit 413 to prompt customers who attempt to leave the checkout area 60 without retrieving their cards to go and retrieve them.

[0169] The error output unit 403 may change the manner of error output depending on the nature of the error.

[0170] For example, if it is determined that the accounting process is not complete, the error output unit 403 may output an error by displaying an error on the indicator 46, illuminating the warning light 47 in red, and outputting an error by sound through the speaker 48. In this example, if it is determined that the change has not been collected or the card has not been collected, the error output unit 403 may output an error by displaying an error on the indicator 46 and illuminating the warning light 47 in yellow only (without sound output).

[0171] Furthermore, a gate that opens and closes using a motor or other drive source may be provided at the exit of the accounting area. In this case, the error output unit 403 may perform processing to control the opening and closing of the gate according to the type of error. For example, if it is determined that the accounting process is not yet complete, the error output unit 403 may perform control to close the gate, which is normally in an open state.

[0172] The data communication unit 404 controls data communication with the store server 6 connected via the communication interface 43 and the network NT.

[0173] Next, we will explain the processes performed by the transaction management system 100.

[0174] First, we will explain the processes performed by the registration device 2 and the store server 6. Figure 10 is a flowchart showing an example of the processes performed by the registration device 2 and the store server 6.

[0175] First, the wireless tag reader 152 of the registration device 2 reads the RFID tag 70 attached to the basket 80 (step S1). For example, the wireless tag reader 152 controls the RFID reader 119 to obtain the tag ID of the RFID tag 70 attached to the basket 80 containing the items that the customer wishes to purchase.

[0176] Next, the transaction number generation unit 153 generates a transaction number (step S2). For example, the transaction number generation unit 153 generates a unique transaction number for each transaction by combining the current date and time, the identification number of the registration device 2, and the sequence number.

[0177] Next, the data communication unit 156 associates the tag ID with the transaction number and sends it to the store server 6 (step S3). For example, the data communication unit 156 associates the tag ID obtained in step S1 with the transaction number generated in step S2 and sends it to the store server 6 via the communication interface 140.

[0178] Next, the data communication unit 611 of the store server 6 receives the tag ID and transaction number (step S4). For example, the data communication unit 611 receives the tag ID and transaction number, which have been linked and transmitted by the registration device 2, via the communication I / F 63.

[0179] Next, the transaction information management unit 612 registers the tag ID and transaction number with the transaction information unit 672 (step S5). For example, the transaction information management unit 612 stores the tag ID and transaction number received in step S4 in the transaction information unit 672 in association with each other. Next, the data communication unit 611 sends a registration notification of the tag ID and transaction number to the registration device 2, indicating that the tag ID and transaction number have been registered with the transaction information unit 672 (step S6).

[0180] Next, the data communication unit 156 of the registration device 2 receives a registration notification containing the tag ID and transaction number (step S7). This allows the registration device 2 to understand that the store server 6 is now in a state where it can manage the transaction status of the current transaction.

[0181] Next, the registration device 2 performs the product registration process (step S8). Specifically, the display control unit 151 displays the registration screen on the operator display unit 114. The input reception unit 154 receives product code input via the scanner 111 or touch panel 113. The registration unit 155 reads product information corresponding to the product code from the PLU file Fa and calculates the subtotal amount.

[0182] When the operation unit 115 receives an operation on the totaling key 1151 (step S9: Yes), the registration unit 155 calculates the total amount for the transaction, and the display control unit 151 displays the total amount on the operator display 114 and the customer display 117 (step S10). If the totaling key 1151 is not operated (step S9: No), the process returns to step S8 and continues with product registration.

[0183] When the input reception unit 154 accepts the operation of the confirmation key 1152 (step S11: Yes), the registration unit 155 generates registration information including product information and total amount of the sold products and registers it in the sales file Fb (step S12). If step S11: No, the process returns to step S8.

[0184] Next, the data communication unit 156 transmits the tag ID, transaction number, and registration information to the store server 6 (step S13). For example, the data communication unit 156 associates the tag ID obtained in step S1, the transaction number generated in step S2, and the registration information generated in step S12 and transmits them to the store server 6.

[0185] Next, the data communication unit 611 of the store server 6 receives the tag ID, transaction number, and registration information transmitted from the registration device 2 (step S14). Then, the transaction information management unit 612 associates the tag ID, transaction number, and registration information and registers them in the transaction information unit 672 (step S15).

[0186] Next, the data communication unit 611 sends a product registration notification to the transaction information unit 672 indicating that the registration information has been registered to the registration device 2 (step S16). After step S16, the store server 6 returns to step S4.

[0187] Next, the data communication unit 156 of the registration device 2 receives a product registration notification sent from the store server 6 (step S17). This allows the registration device 2 to understand that the registration information has been successfully registered in the transaction information unit 672 of the store server 6 and that accounting processing based on the registration information is now possible. After step S17, the processing of the registration device returns to step S1.

[0188] Furthermore, after the product registration is complete (after pressing the confirmation key 1152), the operator prompts the customer to move to the payment device 3 to complete the payment process. This allows the customer to move to the payment device 3 quickly after the registration process is finished.

[0189] Next, we will describe the processes performed by the accounting device 3 and the store server 6. Figures 11 and 12 are flowcharts showing an example of the processes performed by the accounting device 3 and the store server 6.

[0190] The customer takes the basket 80 containing the registered items and moves to an empty checkout machine 3, where they place the basket 80 on the stand 329 of the checkout machine 3. In the checkout machine 3, the wireless tag reader 342 controls the RFID reader 303 to obtain the tag ID from the RFID tag 70 attached to the basket 80 (step S21).

[0191] If the tag ID is not obtained (step S21: No), the wireless tag reader 342 continues the tag ID acquisition process (RFID tag 70 reading process) and repeats the process in step S21 until the tag ID is obtained.

[0192] On the other hand, if a tag ID is obtained (step S21: Yes), the accounting processing unit 345, in cooperation with the data communication unit 344, sends a first query including the tag ID to the store server 6 (step S22). Subsequently, the accounting device 3 proceeds to step S27 (step S25: No) or step S30 (step S25: Yes), depending on the processing result of step S25, described below.

[0193] Next, the data communication unit 611 of the store server 6 receives the first query from the accounting device 3 (step S23). Then, the transaction information management unit 612 identifies the transaction information corresponding to the first query (step S24).

[0194] For example, the transaction information management unit 612 refers to the transaction information unit 672 and identifies the information registered in association with the tag ID included in the first query received in step S23 as transaction information. If no information is associated with the tag ID, the transaction information management unit 612 identifies the absence of information as transaction information.

[0195] Next, the transaction information management unit 612 determines whether registration information exists in the transaction information (step S25). For example, the transaction information management unit 612 refers to the transaction information unit 672 and determines that no registration information exists if there is no transaction number and registration information associated with the tag ID obtained in step 21. On the other hand, if there is a transaction number and registration information associated with the tag ID, the transaction information management unit 612 determines that registration information exists.

[0196] If no registration information exists (Step S25: No), the data communication unit 611 sends a notification to the accounting device 3 indicating that no registration information exists in the transaction information (Step S26). Next, the data communication unit 344 of the accounting device 3 receives a notification from the store server 6 indicating that no registration information exists in the transaction information (Step S27).

[0197] Next, the error output unit 346 informs the customer that no registration information exists (step S28). For example, the error output unit 346 displays a message on the display unit 315 prompting the customer to move to the registration device 2 because the registration process may not be complete. After that, the accounting device 3 returns to step S21.

[0198] On the other hand, if registration information is included in step S25 (step S25: Yes), the data communication unit 611 associates the tag ID included in the first query received in step S23 with the transaction information identified in step S24 and transmits it to the accounting device 3 (step S29).

[0199] Next, the data communication unit 344 of the accounting device 3 receives the tag ID and transaction information transmitted from the store server 6 in step S29 (step S30). Then, the display control unit 341 displays the total amount on the display unit 315 based on the registration information contained in the transaction information received from the store server 6.

[0200] Furthermore, the accounting processing unit 345 performs accounting processing according to the payment method selected by the customer from the operation unit 115 (step S31). Next, the accounting processing unit 345 determines whether the accounting processing has been completed successfully (step S32). For example, the accounting processing unit 345 determines that the accounting processing has been completed successfully if it is completed within a predetermined time, and that the accounting processing has not been completed successfully if it is not completed within a predetermined time.

[0201] If the accounting process does not complete successfully (step S32: No), the error output unit 346 lights up the light-emitting unit 326 in warning mode and displays the error details on the information display unit 327 to output the error (step S33). After that, the accounting device 3 returns to step S21.

[0202] On the other hand, if the accounting process is completed successfully (Step S32: Yes), the accounting processing unit 345 generates receipt data based on the registered information, prints the receipt using the printer 319, and issues it from the receipt issuing slot 3191 (Step S34).

[0203] Next, the data communication unit 344 sends a payment completion notification to the store server 6 (step S35). For example, the data communication unit 344 sends a payment completion notification to the store server 6 that includes payment completion information, change collection information and card collection information according to the payment method.

[0204] Next, the data communication unit 611 of the store server 6 receives the accounting completion notification sent from the accounting device 3 in step S35 (step S36). Then, the transaction information management unit 612 registers the accounting completion information in the transaction information unit 672 (step S37).

[0205] For example, the transaction information management unit 612 stores the accounting completion information in the transaction information unit 672, associating it with the tag ID included in the accounting completion notice received in step S36. The transaction information management unit 612 also stores the change collection information and card collection information corresponding to the payment method in the transaction information unit 672, associating them with the tag ID included in the accounting completion notice received in step S36.

[0206] Next, the data communication unit 611 sends an accounting completion information registration notification to the accounting device 3 indicating that accounting completion information has been registered in the transaction information unit 672 (step S38). After step S38, the store server 6 proceeds to step S44 (step S40:Yes) or step S46 (step S40:No), as described below, depending on the processing result of step S40, which will be described below.

[0207] Next, the data communication unit 344 of the accounting device 3 receives the accounting completion information registration notification sent from the store server 6 (step S39). This allows the accounting device 3 to understand that the accounting completion information has been successfully registered in the transaction information unit 672 of the store server 6, and that the check device 4 can determine that accounting has been completed.

[0208] Next, the accounting processing unit 345 determines whether change was generated during the accounting process (step S40).

[0209] For example, the accounting processing unit 345 determines whether change was generated based on the accounting processing performed in step S31 or the change collection information transmitted in step S35. For example, if the flag value of the change presence / absence flag in the change collection information is 1, the accounting processing unit 345 determines that change was generated. On the other hand, if cash payment was not performed, or if the flag value of the change presence / absence flag in the change collection information is 0, the accounting processing unit 345 determines that no change was generated.

[0210] If there is no change (step S40: No), the accounting device proceeds to step S48, described below. On the other hand, if change is available (step S40: Yes), it is determined whether the collection of the change has been detected by known technology (step S41).

[0211] If it is not detected that the change has been collected (Step S41: No), it is determined whether a predetermined time has elapsed since the change was dispensed (Step S42). If the predetermined time has not elapsed (Step S42: No), the accounting device 3 returns to Step S41 described above. On the other hand, if the predetermined time has elapsed (Step S42: Yes), the accounting device 3 proceeds to Step S48 described below.

[0212] On the other hand, if step S41 detects that the change has been collected (step S41: Yes), the data communication unit 344 sends a change collection notification to the store server 6 (step S43). Then, the data communication unit 611 of the store server 6 receives the change collection notification sent from the accounting device 3 in step S43 (step S44).

[0213] Next, the transaction information management unit 612 registers the change collection with the transaction information unit 672 (step S45). For example, the transaction information management unit 612 sets the flag value of the change collection flag to 1 and stores it in the transaction information unit 672, associating it with the tag ID included in the change collection notification received in step S36.

[0214] Next, the data communication unit 611 sends a change collection registration notification to the accounting device 3, indicating that the change collection has been registered with the transaction information unit 672 (step S46). After step S46, the store server 6 proceeds to step S52 (step S48:Yes) described below, or returns to step S23 (step S48:No) described above, depending on the processing result of step S48 described below.

[0215] Next, the data communication unit 344 of the accounting device 3 receives a change collection registration notification sent from the store server 6 (step S47). This allows the accounting device 3 to understand that the change collection has been successfully registered in the transaction information unit 672 of the store server 6, and that the checking device 4 can determine that the change has been collected.

[0216] Next, the accounting processing unit 345 determines whether the customer inserted the card into the card reader 318 during the accounting process (step S48).

[0217] For example, the accounting processing unit 345 determines whether the customer inserted a card based on the card retrieval information transmitted in step S35. For example, if the flag value of the card insertion status flag in the card retrieval information is 1, the accounting processing unit 345 determines that the customer inserted a card. On the other hand, if the flag value of the card insertion status flag in the card retrieval information is 0, the accounting processing unit 345 determines that no card was inserted.

[0218] If no card was inserted (step S48: No), the accounting device returns to step S21 described above. On the other hand, if a card was inserted (step S48: Yes), it is determined whether the card was detected to have been retrieved by known technology (step S49).

[0219] If the system does not detect that the card has been retrieved (step S49: No), it determines whether a predetermined time has elapsed since the card was inserted (step S50). If the predetermined time has not elapsed (step S50: No), the accounting device 3 returns to step S48 described above. On the other hand, if the predetermined time has elapsed (step S50: Yes), the accounting device returns to step S21 described above.

[0220] On the other hand, if it is detected in step S49 that the card has been collected (step S49: Yes), the data communication unit 344 sends a card collection notification to the store server 6 (step S51). Then, the data communication unit 611 of the store server 6 receives the card collection notification sent from the accounting device 3 in step S51 (step S52).

[0221] Next, the transaction information management unit 612 registers the card retrieval with the transaction information unit 672 (step S53). For example, the transaction information management unit 612 sets the flag value of the card retrieval flag to 1 and stores it in the transaction information unit 672, associating it with the tag ID included in the card retrieval notification received in step S53.

[0222] Next, the data communication unit 611 sends a card retrieval registration notification to the accounting device 3 indicating that the card retrieval information has been registered with the transaction information unit 672 (step S54). After step S46, the store server 6 returns to step S23 described above.

[0223] Next, the data communication unit 344 of the accounting device 3 receives a card retrieval registration notification sent from the store server 6 (step S55). This allows the accounting device 3 to understand that the card retrieval has been successfully registered in the transaction information unit 672 of the store server 6, and that the check device 4 can determine that the card has been retrieved. After step S55, the accounting device returns to step S21 described above.

[0224] Next, we will explain the processes performed by the checking device 4 and the store server 6. Figure 13 is a flowchart showing an example of the processes performed by the checking device 4 and the store server 6.

[0225] When a customer has finished paying, they leave the checkout area 60 and move to the packing area, passing through the gates of the checking device 4. In the checking device 4, the wireless tag reader 401 controls the RFID reader 303 to obtain the tag ID from the RFID tag 70 attached to the basket 80 (step S61).

[0226] If the tag ID is not obtained (step S61: No), the wireless tag reader 401 continues the tag ID acquisition process (RFID tag 70 reading process) and repeats the process in step S61 until the tag ID is obtained. On the other hand, if the tag ID is obtained (step S61: Yes), the transaction status inquiry unit 402 sends a second inquiry including the tag ID to the store server 6 (step S62).

[0227] Next, the data communication unit 611 of the store server 6 receives the second query from the check device 4 (step S63). Then, the transaction information management unit 612 identifies the transaction information corresponding to the second query (step S64). For example, the transaction information management unit 612 refers to the transaction information unit 672 and identifies the information registered in association with the tag ID included in the second query received in step S63 as transaction information.

[0228] The data communication unit 611 associates the tag ID included in the second query received in step S63 with the transaction information identified in step S64 and transmits it to the accounting device 3 (step S65). After step S65, the store server 6 returns to step S63 described above.

[0229] Next, the data communication unit 404 of the checking device 4 receives the tag ID and transaction information transmitted from the store server 6 in step S65 (step S66).

[0230] Next, the error output unit 403 determines whether registration information exists in the transaction information (step S67). For example, the error output unit 403 determines whether the transaction information received in step S66 includes the transaction number and registration information. If registration information does not exist (step S67: No), the error output unit 403 provides notification that registration information does not exist, similar to step S28 in Figure 11 (step S68).

[0231] On the other hand, if registration information exists (step S67: Yes), the error output unit 403 determines whether the accounting process has been completed (step S69). For example, the error output unit 403 determines whether the transaction information received in step S66 includes accounting completion information.

[0232] If the accounting process is not completed (Step S69: No), the error output unit 403 notifies the customer of the unpaid amount (Step S70). For example, the error output unit 403 notifies the customer of the unpaid amount by displaying an output on the display unit 46, illuminating the warning light 47 in red, and outputting an audio message from the speaker 48.

[0233] On the other hand, if the accounting process has been completed (step S69: Yes), the error output unit 403 determines whether change was generated in the accounting process (step S71).

[0234] For example, the error output unit 403 determines whether the transaction information received in step S66 contains information indicating that change was given (i.e., whether the flag value of the change presence / absence flag included in the transaction information is 1). If no change was given (step S71: No), the check device 4 proceeds to the process in step S74, which will be described later.

[0235] On the other hand, if change was due (step S71: Yes), the error output unit 403 determines whether the change has been collected (step S72).

[0236] For example, the error output unit 403 determines whether the transaction information received in step S66 contains information indicating that the change has been collected (i.e., whether the flag value of the change collection flag included in the transaction information is 1). If the change has been collected (step S72: Yes), the check device 4 proceeds to the process in step S74, which will be described later.

[0237] On the other hand, if the change has not been collected (Step S72: No), the error output unit 403 notifies the customer that there is a possibility that the change has not been collected (Step S73). For example, the error output unit 403 notifies the customer that there is a possibility that the change has not been collected by displaying an output on the display unit 46 and illuminating the warning light 47 in yellow.

[0238] Furthermore, if no change was generated in step S71 (step S71: No), or if change was collected in step S72 (step S72: Yes), the error output unit 403 determines whether a card was inserted during the accounting process (step S74).

[0239] For example, the error output unit 403 determines whether the transaction information received in step S66 contains information indicating that a card was inserted (i.e., whether the flag value of the card insertion flag included in the transaction information is 1). If no card was inserted (step S74: No), the check device 4 returns to the process of step S61 described above.

[0240] On the other hand, if a card was inserted (step S74: Yes), the error output unit 403 determines whether the card has been retrieved (step S75).

[0241] For example, the error output unit 403 determines whether the transaction information received in step S66 contains information indicating that the card has been recovered (i.e., whether the flag value of the card recovery flag included in the transaction information is 1). If the card has been recovered (step S75: Yes), the check device 4 returns to the process of step S61 described above.

[0242] On the other hand, if the card has not been collected (step S75: No), the error output unit 403 notifies the customer that there is a possibility that the card has not been collected (step S76). For example, the error output unit 403 notifies the customer that there is a possibility that the card has not been collected by displaying an output on the display unit 46 and illuminating the warning light 47 in yellow. After step S76, the processing of the check device 4 returns to the processing of step S61 described above.

[0243] As described above, the transaction management system 100 according to this embodiment acquires the tag ID of the RFID tag 70 attached to the basket 80 that contains the goods to be purchased, records the tag ID in association with transaction information indicating the status of the transaction related to the purchase of the goods, and a transaction number that identifies the transaction, accepts the input of the tag ID, identifies the transaction information corresponding to the transaction identified by the accepted tag ID and the corresponding transaction number, and notifies that the transaction is incomplete according to the status of the transaction indicated by the identified transaction information.

[0244] As a result, the transaction management system 100 according to this embodiment can identify transaction information associated with a tag ID by reading the tag ID from the RFID tag 70. Furthermore, the transaction management system 100 according to this embodiment can determine whether a transaction can be completed by checking whether the identified transaction information includes information obtained by performing the necessary processing to complete the transaction. In addition, if the transaction management system 100 according to this embodiment determines that a transaction is incomplete, it can notify the customer that there is a possibility that the processing necessary to complete the transaction has not been performed, thereby making the customer aware of any omissions in the processing necessary to complete the transaction. In other words, the transaction management system 100 according to this embodiment can help ensure that all processing necessary to complete a transaction is performed without omission.

[0245] The above-described embodiment can also be modified and implemented as appropriate by changing the configuration or some of the functions of each device in the transaction management system 100. Therefore, the following describes modifications of the above-described embodiment as other embodiments. In the following, we will mainly describe the differences from the above-described embodiment, and will omit detailed explanations of points that are common with what has already been described. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.

[0246] (Variation 1) In the above-described embodiment, a transaction management system 100 including a semi-self-service accounting system was explained. In this modified example, a transaction management system 100 including a fully self-service accounting system will be described.

[0247] In this modified example, a self-service POS terminal is provided in the accounting area 60 instead of the registration device 2 and accounting device 3. Alternatively, both the registration device 2 and accounting device 3 and the self-service POS terminal may be provided in the accounting area 60.

[0248] The self-service POS terminal has a hardware configuration similar to the accounting device 3 shown in Figure 7, but differs from the hardware configuration shown in Figure 7 in that it has an operation unit 115 (current total key 1151, confirmation key 1152) and a PLU file Fa and a sales file Fb on the HDD 305.

[0249] Furthermore, the control unit of the self-service POS terminal has a similar functional configuration to the control unit 340 of the accounting device 3 shown in Figure 7, but differs from the functional configuration of the control unit 340 of the accounting device 3 shown in Figure 7 in that it includes a transaction number generation unit 153 and a registration unit 155.

[0250] In this modified example, the self-service POS terminal proceeds to step S31 of the accounting device 3 shown in Figure 11 after the processing in step S17 of the registration device 2 shown in Figure 10, and performs accounting processing based on the registration information generated in step S12. The processing performed by the self-service POS terminal thereafter is the same as the processing of the accounting device 3 in the embodiment described above.

[0251] According to this modified version, it is possible to ensure that even customers using a fully self-service accounting system are able to complete all necessary steps to finalize their transactions.

[0252] (Modification 2) In the above-described embodiment, a configuration was explained in which the checking device 4 determines whether the transaction can be completed. In this modified example, a configuration will be described in which the store server 6 determines whether the transaction can be completed.

[0253] In this modified example, the control unit 61 of the store server 6 is equipped with an error output unit 403, and the check device 4 outputs various errors under the control of the error output unit 403 of the store server 6.

[0254] Furthermore, the RFID reader 45, display unit 46, warning light 47, and speaker 48 may be connected to the control unit 61 of the store server 6 via the bus 62 and the I / O device control unit 64. In this case, since the processing performed by the check device 4 can be performed by the store server 6, the check device 4 does not need to be provided.

[0255] According to this modified version, the degree of flexibility in configuring the transaction management system 100 is improved, making it possible to build a transaction management system 100 that is tailored to the store's environment.

[0256] As described above, the above embodiment can help ensure that all operations necessary to complete a transaction are performed without omission.

[0257] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of symbols]

[0258] 2. Registered device 3. Accounting device 4. Checking device 6 Store Servers 70 RFID tags 80 baskets 100 Transaction Management Systems 301 First cabinet 3012 Side view 303 RFID Reader 329 Mounting platform 672 Trading Information Department [Prior art documents] [Patent Documents]

[0259] [Patent Document 1] Japanese Patent Publication No. 2022-66252

Claims

1. A means for acquiring wireless tag identification information that identifies the wireless tag attached to the basket containing the product to be purchased, A recording means for recording the acquired wireless tag identification information, transaction information indicating the status of the transaction related to the purchase of the product, and transaction identification information identifying the transaction, in association with each other. A receiving means for receiving the input of the aforementioned wireless tag identification information, A means for identifying transaction information that corresponds to a transaction identified by the transaction identification information corresponding to the wireless tag identification information received by the receiving means, A notification means that notifies that a transaction is incomplete, according to the transaction status indicated by the identified transaction information, A transaction management system equipped with the following features.

2. The aforementioned transaction information includes status information indicating the status of operations performed to complete the transaction, The notification means determines whether the transaction has been completed based on the status information included in the transaction information, and if it determines that the transaction has not been completed, it issues a notification. The transaction management system according to claim 1.

3. The aforementioned status information includes information indicating that the change has been collected and that the card has been removed from the card reader. The notification means determines that a transaction is incomplete if the transaction information does not include at least one of the status information items, namely information indicating that the change has been collected and information indicating that the card has been removed from the card reader, and provides notification according to the status information item that is not included in the transaction information. The transaction management system according to claim 2.

4. The aforementioned status information includes information indicating that accounting has been completed. The notification means determines that a transaction is incomplete if the transaction information does not include information indicating that accounting has been completed as status information, and notifies that the transaction is unaccounted for. The transaction management system according to claim 2.

5. The system further includes a detection means for detecting the location of each of the multiple baskets within the store by detecting the location of each of the multiple wireless tags based on the reception results of information transmitted from multiple wireless tags by multiple receivers placed within the store, The notification means, based on the detection results of the location of each of the multiple baskets, notifies the store if it determines that a number of baskets exceeding a predetermined threshold is accumulated at the basket collection area within the store. The transaction management system according to claim 1.

6. A receiving means that receives from at least one product sales data processing device the following: wireless tag identification information that identifies a wireless tag attached to a basket containing the product to be purchased, transaction information indicating the status of the transaction related to the purchase of the product, and transaction information indicating the status of the transaction related to the purchase of the product. A recording means that records the received wireless tag identification information, transaction information indicating the status of the transaction related to the purchase of the product, and transaction identification information identifying the transaction, in association with each other. A receiving means that receives the input of the wireless tag identification information from a notification device that notifies that a transaction is incomplete according to the transaction status indicated by the transaction information, A means for identifying transaction information corresponding to a transaction identified by the transaction identification information corresponding to the wireless tag identification information received by the reception means, A transmission means for transmitting the identified transaction information to the notification device, A server device equipped with the following features.

Images