Checkout system

Abstract

The invention discloses a checkout system which can properly guide a customer who completes settlement to exit from a shop. A checkout system according to an embodiment includes a storage unit, an acquisition unit, a lock unit, a notification unit, and a control unit. And a storage unit that stores list data indicating a list of transaction products to be transacted in the store in correspondence with each of the settled transactions, each of the list data indicating a list of transaction products to be transacted in the store. The acquisition unit acquires an identifier of a product in accordance with an operation by a customer. And a locking unit that locks, by referring to the list data stored in the storage unit, a transaction including, as a transaction product, the product identified by the one or more identifiers acquired by the acquisition unit. The notification unit notifies that the customer is allowed to pass. And a control unit that controls the notification unit so as to perform notification in accordance with a situation in which one transaction has been locked by the locking unit.

Description

[0001] This application claims priority from Japanese patent application No. JP2024-049751, filed on Mar. 26, 2024, and cites the contents of the aforementioned application, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field

[0002] An embodiment of the present invention relates to a checkout system. Background Art

[0003] In a store that processes transactions such as product sales until settlement, it is desirable to appropriately guide customers who have completed settlement to exit the store. Summary of the Invention

[0004] In view of the above problems, the present invention aims to provide a checkout system that can appropriately guide customers who have completed payment to exit a store.

[0005] To address the above-mentioned issues, a checkout system according to an embodiment includes a storage unit, an acquisition unit, a locking unit, a notification unit, and a control unit. The storage unit stores list data representing a list of transaction items in a store, corresponding to each settled transaction. The acquisition unit acquires item identifiers based on a customer's operation. The locking unit locks a transaction containing items identified by one or more identifiers acquired by the acquisition unit by referencing the list data stored in the storage unit. The notification unit notifies the customer that passage is permitted. The control unit controls the notification unit to issue a notification based on the locking of a transaction by the locking unit.

[0006] According to the above-mentioned checkout system, it is possible to appropriately guide customers to exit the store without having to read code information indicating the completion of transaction settlement.

[0007] In the above-mentioned checkout system, the locking unit targets transactions that have been settled within a predetermined period starting from when the commodity identifier was acquired by the acquiring unit.

[0008] According to the above-mentioned settlement system, it is possible to lock transactions that have been settled in the most recent period.

[0009] In the above-mentioned checkout system, the locking unit, when having locked one transaction, excludes the corresponding transaction from subsequent locking targets.

[0010] According to the above-described checkout system, the number of targets to be targeted can be reduced.

[0011] The above-mentioned checkout system further includes a processing unit configured to perform a process for staff to take action when the locking unit cannot lock one transaction before a predetermined end condition is satisfied.

[0012] According to the above checkout system, when locking is impossible, assistance from staff can be requested.

[0013] In the above-mentioned checkout system, the locking object of the locking unit is a transaction in which settlement is completed within a certain time period.

[0014] According to the above-described checkout system, transactions within a certain time period can be targeted.

[0015] In the above-mentioned checkout system, the certain time period is the current day.

[0016] According to the above-mentioned checkout system, transactions on the current day can be targeted.

[0017] In the above-mentioned checkout system, the predetermined period of time during which the locking unit is locked is a period during which a predetermined number of transactions have been performed.

[0018] According to the above-described checkout system, a predetermined number of transactions can be targeted for locking.

[0019] In the above-mentioned checkout system, the notification unit displays a guidance screen notifying the customer that passage is permitted.

[0020] According to the above-described checkout system, a guidance screen can be displayed to inform the customer that the customer can pass.

[0021] In the above-mentioned checkout system, the list data in the storage unit also includes a settlement method, the acquisition unit further acquires the settlement method based on the customer's operation, and the locking unit locks the transaction including the product and settlement method acquired by the acquisition unit from the list data in the storage unit.

[0022] According to the above-mentioned checkout system, a customer who has completed payment can lock in his / her account, and a customer who has not completed payment can easily recognize an operation error.

[0023] Another aspect of the present invention relates to a checkout system, which includes a gate device and an information processing device arranged facing a checkout passage through which a customer passes when exiting a store, and includes: a storage unit, which is arranged in the information processing device and stores list data representing a list of transaction commodities that are the subject of transactions in the store, respectively corresponding to each settled transaction; an acquisition unit, which is arranged in the gate device and acquires an identifier of a commodity based on an operation of the customer; a first notification unit, which is arranged in the gate device and notifies the information processing device of the identifier acquired by the acquisition unit; a locking unit, which is arranged in the information processing device and locks a transaction by referring to the list data stored in the storage unit, wherein the transaction includes commodities identified by one or more identifiers notified by the first notification unit as transaction commodities; a second notification unit, which is arranged in the information processing device and, when a transaction has been locked by the locking unit, notifies the gate device that a transaction has been locked by the locking unit; a third notification unit, which is arranged in the gate device and notifies that the customer is allowed to pass; and a control unit, which is arranged in the gate device and controls the third notification unit so as to make a notification based on the notification that a transaction has been locked by the second notification unit.

[0024] According to the above-mentioned checkout system, it is possible to appropriately guide the customer to exit the store without having to read the code information indicating that the transaction has been completed. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 It is an overall structural diagram of a commodity sales system involved in one embodiment.

[0026] Figure 2 This is a schematic diagram showing an example of the layout of cash registers in a store that has introduced a product sales system.

[0027] Figure 3 Yes Figure 1 Block diagram of the main circuit structure of the transaction processing device.

[0028] Figure 4 Yes Figure 1 Block diagram of the main circuit structure of the POS terminal.

[0029] Figure 5 Yes Figure 1 Block diagram of the main circuit structure of the POS terminal.

[0030] Figure 6 Yes Figure 1 Block diagram of the main circuit structure of the checkout gate.

[0031] Figure 7 Yes Figure 1A three-dimensional image of the appearance of the checkout gate.

[0032] Figure 8 Yes Figure 1 A block diagram of the main circuit structure of the information processing terminal in FIG.

[0033] Figure 9 Yes Figure 1 Block diagram of the main circuit structure of the monitoring terminal.

[0034] Figure 10 Yes Figure 1 Block diagram of the main circuit structure of the POS server.

[0035] Figure 11 Is with use Figure 1 A timing diagram related to the processing of transactions in the information processing terminal.

[0036] Figure 12 This is a flow chart of the gate control process.

[0037] Figure 13 This is a flow chart of the gate control process.

[0038] Figure 14 This is a flow chart of the gate control process.

[0039] Figure 15 It means to make Figure 6 Schematic diagram of an example of a standby screen displayed on the touch panel in .

[0040] Figure 16 It means to make Figure 6 Schematic diagram of an example of a standby screen displayed on the display unit in .

[0041] Figure 17 This is a flow chart of the access permission process.

[0042] Figure 18 This is a schematic diagram showing an example of the first guidance screen.

[0043] Figure 19 This is a schematic diagram showing an example of the second guidance screen.

[0044] Figure 20 Is with use Figure 1 A timing diagram related to the processing of transactions at a POS terminal.

[0045] Figure 21 Is with use Figure 1 A timing diagram related to transaction processing at a POS terminal.

[0046] Figure 22 This is a flowchart of the transaction retrieval process.

[0047] Figure 23 This is a schematic diagram showing an example of an addition request screen.

[0048] Figure 24 is based on Figure 6 The clerk call processing and based on the processor Figure 9 Flowchart of the instruction issuance processing of the processor in.

[0049] Figure 25 This is a diagram showing an example of a call screen.

[0050] Figure 26 This is a schematic diagram showing an example of a warning screen.

[0051] Figure 27 This is a flowchart of the exit confirmation process.

[0052] Figure 28 is based on Figure 6 Error handling of the processor in the Figure 9 Flowchart of warning handling of the processor in.

[0053] Figure 29 This is a schematic diagram showing an example of the first warning screen.

[0054] Figure 30 Schematic diagram showing a modified example of the gate control process.

[0055] Figure 31 This is a schematic diagram showing an example of a standby screen applied to a modified example.

[0056] Description of Reference Numerals

[0057] 1. Commodity sales system 2. Communication network 3. Electronic receipt server

[0058] 100 Transaction processing device 200, 300 POS terminal 400 Checkout gate

[0059] 500 Information Processing Terminal 600 Monitoring Terminal 700 POS Server

[0060] 101, 201, 301, 401, 501, 601, 701 processors

[0061] 102, 202, 302, 402, 502, 602, 702 main storage units

[0062] 103, 203, 303, 403, 503, 603, 703 auxiliary storage units

[0063] 204, 604 clerk side touch panel 205, 305, 605 keyboard

[0064] 206, 306, 406, 606 fixed scanners 207, 307, 407, 607 handheld scanners

[0065] 208, 308, 608 settlement terminals 209, 309, 609 change units

[0066] 210, 310, 408, 610 receipt printers 211, 611 customer-side touch panel

[0067] 212, 612...Customer display 213, 311, 411, 505, 613 sound unit

[0068] 304, 404, 504 touch panel 405 display unit 409 human perception sensor

[0069] 410 Warning Light Unit 599 Barcode Scanner DETAILED DESCRIPTION

[0070] The following describes a merchandise sales system that processes the sale of merchandise to customers in a store, using accompanying drawings. This merchandise sales system is also an example of a transaction processing system that processes transactions targeting the sale of merchandise. The targeted transactions can be transactions different from merchandise sales, such as the provision of any service in a store. However, after completing the settlement for the targeted transaction, the customer is allowed to exit the store.

[0071] Figure 1 It is an overall structural diagram of the commodity sales system 1 involved in this embodiment.

[0072] The commodity sales system 1 includes a transaction processing device 100, POS (Point-of-Sale) terminals 200 and 300, a checkout gate 400, an information processing terminal 500, a monitoring terminal 600, and a POS server 700. The transaction processing device 100, POS terminal 200, checkout gate 400, information processing terminal 500, monitoring terminal 600, and POS server 700 can be configured to communicate with each other via a communication network 2. Furthermore, the POS terminal 200 and checkout gate 400 can communicate with an electronic receipt server 3 via the communication network 2. The electronic receipt server 3 provides an electronic receipt service that allows users to browse an electronic receipt screen showing the details of transactions processed by the commodity sales system 1 using any information terminal.

[0073] exist Figure 1In the figure, one POS terminal 200, one POS terminal 300, one information processing terminal 500, one monitoring terminal 600, and one POS server 700 are shown, and three checkout gates 400 are shown, but the number of these gates is arbitrary. Any one or two of the POS terminal 200, POS terminal 300, and information processing terminal 500 may be provided without the other two or one. In many cases, when multiple POS terminals 200, POS terminals 300, and information processing terminals 500 are provided, the product sales system 1 includes multiple of them.

[0074] The communication network 2 may include the Internet, a VPN (Virtual Private Network), a LAN (Local Area Network), a public communication network, and a mobile communication network, etc., which may be used singly or in appropriate combination. As an example of the communication network 2, a LAN, the Internet, and a mobile communication network are used in combination. For example, a LAN is used for communication between the transaction processing device 100, the POS terminal 200, the checkout gate 400, the information processing terminal 500, the monitoring terminal 600, and the POS server 700. For example, a LAN is used for communication between the transaction processing device 100 and the information processing terminal 500. However, the information processing terminal 500 is connected to the communication network 2 via wireless access via an access point 21 included in the communication network 2. For example, a LAN and the Internet are used for communication between the POS terminal 200 or the checkout gate 400 and the electronic receipt server 3.

[0075] Figure 2 1 is a schematic diagram showing a layout example of cash registers in a store in which the product sales system 1 is installed.

[0076] The customer CU who is shopping in the store temporarily acts as the operator of the information processing terminal 500. The information processing terminal 500 is attached to, for example, a shopping cart (hereinafter referred to as a trolley) CA. The information processing terminal 500 can be carried by the customer CU. As the information processing terminal 500, an existing portable information processing device such as a tablet computer, a smartphone, or a smart watch can be used. The information processing terminal 500 can be an information processing terminal prepared by the store and temporarily used by the customer CU, or it can be an information processing terminal held by the customer CU. The customer CU moves around the store while pushing the trolley CA and places the goods he wants to buy directly on the trolley CA or in a shopping basket placed on the trolley CA. At this time, the customer CU operates the information processing terminal 500 to register the goods placed on the trolley CA as transaction goods. The transaction processing device 100 registers the transaction goods based on the operation of the information processing terminal 500. In addition, the information processing terminal 500 can be operated by the store clerk CL instead of the customer CU. When the customer CU finishes selecting all the items he wants to buy, he goes to the cashier and checks out using the checkout gate 400. After that, the customer CU leaves the store after passing through the checkout lane LA facing the checkout gate 400 for checkout. Figure 2 As shown, when multiple checkout gates 400 are provided, they are positioned facing each of the multiple checkout lanes LA. Each checkout gate 400 also functions as an exit gate, controlling the passage of customers CU in the checkout lane LA it faces, and serves as an example of a gate device. This exit gate function will be described later. After passing through the checkout lane LA, customers CU bag their merchandise at the bagging station SU as needed. In this way, the merchandise sales system 1 also functions as a checkout system for in-store checkout.

[0077] Furthermore, the customer CU can entrust the registration of the goods he wants to purchase as transaction goods to the store clerk CL who is responsible for operating the POS terminal 200, without using the information processing terminal 500. The store clerk CL operates the POS terminal 200, registers the goods brought in by the customer CU as transaction goods, and settles the payment for the goods. In other words, the POS terminal 200 is a so-called face-to-face type. The operation of the POS terminal 200 can be the same as that of an existing POS terminal of the same type. In addition, Figure 2 In the figure, POS terminal 200 is an example of a separate type, consisting of a main unit 298 and a scanner unit 299. POS terminal 200 may also have other configurations, such as an integrated type. Furthermore, POS terminal 200 may be a semi-automatic POS terminal, consisting of a registration terminal operated by a store clerk CL and a checkout terminal operated by a customer CU. Customers CU who complete checkout using POS terminal 200 exit the store without passing through the checkout lane LA.

[0078] Furthermore, customers CU can register the items they wish to purchase as transaction items and proceed to checkout by operating POS terminal 300 independently, without using information processing terminal 500. In other words, POS terminal 300 is a so-called fully self-service POS terminal. The operation of POS terminal 300 is similar to that of existing POS terminals. After completing checkout using POS terminal 300, customers CU exit the store through checkout lane LA.

[0079] The monitoring terminal 600 assists the store clerk CL in monitoring illegal access to the checkout lane LA. The POS server 700 is an information processing device that manages transactions processed using the merchandise sales system 1 .

[0080] Figure 3 It is a block diagram showing the main circuit structure of the transaction processing device 100.

[0081] The transaction processing device 100 includes a processor 101 , a main storage unit 102 , an auxiliary storage unit 103 , a communication unit 104 , and a transmission line 105 . The processor 101 , the main storage unit 102 , the auxiliary storage unit 103 , and the communication unit 104 can communicate via the transmission line 105 .

[0082] The processor 101 , the main storage unit 102 , and the auxiliary storage unit 103 are connected via a transmission line 105 , thereby forming a computer that performs information processing for controlling the transaction processing apparatus 100 .

[0083] The processor 101 corresponds to the core of the computer and executes information processing for controlling each unit according to information processing programs such as an operating system and application programs to realize various functions of the transaction processing device 100 .

[0084] The main storage unit 102 corresponds to the main storage portion of the computer. The main storage unit 102 includes a read-only storage area and a rewritable storage area. The main storage unit 102 stores a portion of the information processing program in the read-only storage area. Furthermore, the main storage unit 102 can store data required for the processor 101 to execute processing to control various components in either the read-only storage area or the rewritable storage area. The main storage unit 102 uses the rewritable storage area as a work area for the processor 101.

[0085] The auxiliary storage unit 103 is equivalent to the auxiliary storage portion of the above-mentioned computer. The auxiliary storage unit 103 can utilize, for example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (hard disc drive), an SSD (solid state drive), or various other well-known storage devices. The auxiliary storage unit 103 stores data used by the processor 101 in performing various processes and data generated by the processes performed by the processor 101. The auxiliary storage unit 103 can also store the above-mentioned information processing programs. In this embodiment, the auxiliary storage unit 103 stores a transaction processing program PRA as one of the information processing programs. The transaction processing program PRA is an application program described later that records the sequence of transaction processing. A portion of the storage area of ​​the auxiliary storage unit 103 is used as an area for storing transaction data DAA. The transaction data DAA is data that represents the content of a transaction.

[0086] The communication unit 104 performs communication processing for communicating data via the communication network 2. For example, an existing wired communication device used for the Internet can be used as the communication unit 104. Alternatively, a wireless communication device connected to the communication network 2 by wireless communication may be used as the communication unit 104 instead of or in addition to the wired communication device.

[0087] The transmission line 105 includes an address bus, a data bus, a control signal line, and the like, and transmits data and control signals exchanged between connected components.

[0088] As the basic hardware of the transaction processing device 100, for example, a general-purpose server device can be used. Then, usually, the transfer of the transaction processing device 100 is carried out in a state where the transaction processing program PRA is stored in the auxiliary storage unit 103. However, the hardware and the transaction processing program PRA can be transferred separately in a state where the transaction processing program PRA is not stored in the auxiliary storage unit 103 or a different version of the same application is stored in the auxiliary storage unit 103. Then, the transaction processing device 100 can also be constructed by writing the transaction processing program PRA to the auxiliary storage unit 103 according to the operation of any staff member. The transaction processing program PRA can be transferred by storing it in a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, a semiconductor memory, etc. or by communicating via a network. The transaction processing program PRA can be stored in the main storage unit 102.

[0089] Figure 4 This is a block diagram showing the main circuit configuration of the POS terminal 200 .

[0090] The POS terminal 200 includes a processor 201, a main storage unit 202, an auxiliary storage unit 203, a clerk-side touch panel 204, a keyboard 205, a fixed scanner 206, a handheld scanner 207, a payment terminal 208, a change unit 209, a receipt printer 210, a customer-side touch panel 211, a customer display 212, an audio unit 213, a communication unit 214, and a transmission line 215. For example, the processor 201, the main storage unit 202, the auxiliary storage unit 203, the clerk-side touch panel 204, the keyboard 205, the change unit 209, the receipt printer 210, and the communication unit 214 are located in a main unit 298. Furthermore, for example, the fixed scanner 206, the handheld scanner 207, the payment terminal 208, the customer-side touch panel 211, the customer display 212, and the audio unit 213 are located in the scanner unit 299. However, some of these elements may be located in units other than the above. In addition, some elements such as a clerk touch panel and a keyboard may be provided on both the main body unit 298 and the scanner unit 299 .

[0091] The functions of the processor 201 , the main storage unit 202 , the auxiliary storage unit 203 , the communication unit 214 , and the transmission line 215 are substantially equivalent to those of the processor 101 , the main storage unit 102 , the auxiliary storage unit 103 , the communication unit 104 , and the transmission line 215 .

[0092] However, the auxiliary storage unit 203 stores a transaction processing program PRB instead of the transaction processing program PRA. The transaction processing program PRB is an application program that describes the information processing procedures of the processor 201 for performing transaction processing based on the clerk's operation of devices provided in the POS terminal 200.

[0093] The clerk-side touch panel 204 is positioned toward the side where the clerk CL, who operates the POS terminal 200, stands (hereinafter referred to as the clerk side). The clerk-side touch panel 204 displays a screen for presenting information to the clerk CL. Furthermore, the clerk-side touch panel 204 allows the clerk CL to input instructions by touching the screen.

[0094] The keyboard 205 includes a plurality of hard keys to simplify the operation by the clerk CL from the clerk side. The clerk CL's instructions are input by pressing these hard keys of the keyboard 205.

[0095] The fixed scanner 206 has a reading window facing the employee. The fixed scanner 206 images the product facing the reading window and, through image processing, identifies the barcode information represented by the barcode on the product. The fixed scanner 206 then outputs the barcode information to the processor 201. Alternatively, the fixed scanner 206 may be any other known device, such as one that optically reads barcodes using laser reflection. Furthermore, the fixed scanner 206 may also use a known device that uses object recognition technology to identify a product based on an image of the product itself, obtained by photographing the product.

[0096] The handheld scanner 207 is held by the store clerk CL and optically reads a barcode facing the reading window. The handheld scanner 207 outputs barcode information represented by the read barcode to the processor 201.

[0097] The settlement terminal 208 reads data stored on settlement cards such as credit cards, prepaid cards, and electronic money cards. Furthermore, the settlement terminal 208 writes data to the settlement cards. The settlement terminal 208 is equipped with readers capable of reading IC cards, magnetic cards, and near-field communication (NFC) cards. A reader for IC reading reads data stored on an IC (Integrated Circuit) on a credit card through communication via electrical contacts. A reader for magnetic reading uses a magnetic head to read data magnetically stored on a magnetic stripe formed on the surface of a credit card. Thus, both IC reading and magnetic reading involve contact between the settlement terminal 208 and the credit card, and are examples of contact reading. Furthermore, the readers for IC reading and magnetic reading are examples of contact reading devices. A reader for near-field communication reading uses wireless communication, such as NFC (Near Field Communication), to read data stored on an IC (Integrated Circuit) on a credit card. Thus, near-field communication reading is an example of contactless reading. Furthermore, the reader for near-field communication reading is an example of contactless reading.

[0098] The change unit 209 counts the amount of coins inserted from the coin slot and stores them in the internal storage. The change unit 209 then discharges the coins stored in the storage into the coin tray via the coin outlet. The change unit 209 counts the amount of banknotes inserted from the banknote slot and stores them in the internal storage. The change unit 209 then discharges the banknotes stored in the storage through the banknote outlet. The banknote outlet holds the discharged banknotes, with some of them exposed to the outside.

[0099] The receipt printer 210 prints an image of a receipt, receipt, or voucher (such as a sales slip) on receipt paper. The receipt printer 210 ejects the receipt paper with the image printed on it from the receipt ejection port. Hereinafter, the receipt paper with the image printed on it is referred to as a paper receipt.

[0100] The customer-side touch panel 211 is positioned toward the side (hereinafter referred to as the customer side) where the customer CU stands when registering traded items through the clerk CL's operations. The customer-side touch panel 211 displays a screen for presenting information to the customer. Furthermore, the customer-side touch panel 211 allows the customer CU to input instructions by touching the screen.

[0101] The customer display 212 is provided facing the customer side. The customer display 212 displays a screen for presenting information to the customer CU. The customer display 212 is mainly used to display character strings, and displays a simpler screen than the screen displayed on the customer-side touch panel 211.

[0102] The sound unit 213 outputs sounds and voices for various guidance and warnings. As the sound unit, various well-known sound devices such as a speech synthesis device and a buzzer can be used alone or in combination.

[0103] The basic hardware of the POS terminal 200 can be, for example, hardware from another existing POS terminal. In this case, the transfer of the POS terminal 200 typically occurs with the transaction processing program PRB stored in the auxiliary storage unit 203. However, it is possible to transfer the POS terminal 200 hardware and the transaction processing program PRB separately, without the transaction processing program PRB stored in the auxiliary storage unit 203. The transaction processing program PRB can then be written to the auxiliary storage unit 203 by any operator. Alternatively, the POS terminal 200 hardware and the transaction processing program PRB can be transferred separately, while the auxiliary storage unit 203 stores another version of an information processing program of the same type as the transaction processing program PRB. The transaction processing program PRB can then be written to replace the information processing program already stored in the auxiliary storage unit 203. The transaction processing program PRB can be transferred by storing it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communicating over a network. The transaction processing program PRB can be stored in the main storage unit 202.

[0104] Figure 5 This is a block diagram showing the main circuit configuration of the POS terminal 300 .

[0105] The POS terminal 300 includes a processor 301 , a main storage unit 302 , an auxiliary storage unit 303 , a touch panel 304 , a keyboard 305 , a fixed scanner 306 , a handheld scanner 307 , a settlement terminal 308 , a change unit 309 , a receipt printer 310 , an audio unit 311 , a communication unit 312 , and a transmission line 313 .

[0106] The functions of the processor 301 , main storage unit 302 , auxiliary storage unit 303 , communication unit 312 and transmission line 313 are substantially equivalent to those of the processor 101 , main storage unit 102 , auxiliary storage unit 103 , communication unit 104 and transmission line 313 .

[0107] However, the auxiliary storage unit 303 stores a transaction processing program PRC instead of the transaction processing program PRA. The transaction processing program PRC is an application program that describes the information processing procedures of the processor 301 for performing transaction processing based on the customer's operation on the device provided in the POS terminal 300.

[0108] The touch panel 304 is positioned toward the side where the customer CU operating the POS terminal 300 stands. The touch panel 304 displays a screen for displaying information to the customer CU. Furthermore, the touch panel 304 allows the customer CU to input instructions by touching the screen. The functions of the keyboard 305, fixed scanner 306, handheld scanner 307, settlement terminal 308, change unit 309, receipt printer 310, and audio unit 311 are roughly equivalent to those of the keyboard 205, fixed scanner 206, handheld scanner 207, settlement terminal 208, change unit 209, receipt printer 210, and audio unit 213. However, the keyboard 305, fixed scanner 306, handheld scanner 307, and settlement terminal 308 are designed to be easily accessible to the customer CU and are primarily operated by the customer CU.

[0109] The basic hardware of the POS terminal 300 can be, for example, hardware from other existing fully self-service POS terminals. Transferring the POS terminal 300 typically occurs with the transaction processing program PRC stored in the auxiliary storage unit 303. However, the POS terminal 300 hardware and the transaction processing program PRC can be transferred separately, even if the transaction processing program PRC is not stored in the auxiliary storage unit 303. The transaction processing program PRC can then be written to the auxiliary storage unit 303 by any operator. Alternatively, the POS terminal 300 hardware and the transaction processing program PRC can be transferred separately, even if another version of the same type of information processing program as the transaction processing program PRC is stored in the auxiliary storage unit 303. The transaction processing program PRC can then be written to replace the information processing program already stored in the auxiliary storage unit 303. The transaction processing program PRC can be transferred by storing it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communicating over a network. The transaction processing program PRC can be stored in the main storage unit 302.

[0110] Figure 6 This is a block diagram showing the main circuit configuration of the checkout gate 400.

[0111] The checkout gate 400 includes a processor 401 , a main storage unit 402 , an auxiliary storage unit 403 , a touch panel 404 , a display unit 405 , a fixed scanner 406 , a handheld scanner 407 , a receipt printer 408 , a human perception sensor 409 , a warning light unit 410 , a sound unit 411 , a communication unit 412 , and a transmission line 413 .

[0112] The functions of the processor 401 , main storage unit 402 , auxiliary storage unit 403 , communication unit 412 and transmission line 413 are substantially equivalent to those of the processor 101 , main storage unit 102 , auxiliary storage unit 103 , communication unit 104 and transmission line 413 .

[0113] However, the auxiliary storage unit 403 stores a gate control program PRD, not a transaction processing program PRA. The gate control program PRD is an application program that describes the information processing sequence of the processor 401 for gate control processing, which will be described later. Furthermore, the auxiliary storage unit 403 stores rejection list data DAB. This rejection list data DAB represents a list of POS terminals designated as rejection targets. Whether to designate either POS terminal 200 or POS terminal 300 as a rejection target can be determined as appropriate by any user, such as an administrator of the merchandise sales system 1. In this embodiment, POS terminal 200 is designated as a rejection target.

[0114] Touch panel 404 displays a screen for presenting information to an operator performing checkout operations. Furthermore, touch panel 404 allows the operator to input instructions by touching the screen. The operator of checkout gate 400 is typically a customer CU. However, a store clerk CL may also operate checkout gate 400.

[0115] The display unit 405 displays a screen for presenting information to customers CU passing through the checkout lane LA facing the checkout gate 400 on which the display unit 405 is installed. In the following description of the checkout gate 400, "checkout lane LA" refers to the checkout lane LA facing the corresponding checkout gate 400.

[0116] Fixed scanner 406 has a reading window. Fixed scanner 406 uses image processing to identify the barcode information represented by a barcode positioned in front of the reading window. Fixed scanner 406 then outputs the barcode information to processor 401. Alternatively, fixed scanner 406 can utilize other known devices, such as those that optically read barcodes using laser reflection. Furthermore, fixed scanner 406 can utilize known devices that use object recognition technology to identify products based on images of the products captured by photographing them.

[0117] The handheld scanner 407 is held in the hand of the customer CU and optically reads the barcode facing the reading window. The handheld scanner 407 outputs the barcode information represented by the read barcode to the processor 401.

[0118] The receipt printer 408 prints an image of a receipt, a receipt, or a voucher (such as a sales slip) on a receipt sheet. The receipt printer 408 ejects the receipt sheet with the printed image from the receipt ejection port. In other words, the receipt printer 408 is used to issue paper receipts.

[0119] The human detection sensor 409 detects a customer CU passing through the checkout lane LA. A known detection device such as an optical sensor or an infrared sensor can be appropriately used as the human detection sensor 409. That is, the human detection sensor 409 is an example of a first detection unit.

[0120] The warning light unit 410 displays the permission status of the customer CU to pass through the checkout lane LA.

[0121] The audio unit 411 outputs various sounds and voices for guiding and warning the customer CU to pass through the checkout lane LA. As the audio unit, various well-known audio devices such as a speech synthesis device and a buzzer can be used alone or in combination.

[0122] Transferring the checkout gate 400 typically occurs while the gate control program PRD is stored in the auxiliary storage unit 403. However, the hardware and gate control program PRD can be transferred separately, even if the auxiliary storage unit 403 does not store the gate control program PRD, or if the auxiliary storage unit 403 stores another version of the same type of application. The checkout gate 400 is then constructed by writing the gate control program PRD to the auxiliary storage unit 403, according to an operation by any operator. The gate control program PRD can be transferred by storing it in a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communicating over a network. The gate control program PRD can be stored in the main storage unit 402.

[0123] Figure 7 It is a perspective view showing the appearance of the checkout gate 400.

[0124] In addition, Figure 7 In, with Figure 6 The same elements shown are given the same reference numerals. Figure 7 In the following description, Figure 7 The left and right sides of the are respectively regarded as the front and the rear.

[0125] The checkout gate 400 has a housing 450 formed in a generally rectangular parallelepiped shape. The checkout gate 400 is positioned with one side surface 451 of the housing 450 facing the checkout lane LA, thereby controlling the movement of customers CU through the checkout lane LA in the direction indicated by the arrow AR. Hereinafter, the side surface of the housing 450 that faces forward in the direction of movement of the customers CU is referred to as the front surface 452.

[0126] The housing 450 holds the fixed scanner 406 in a position for reading a barcode directed from the front surface 452. The housing 450 holds the display unit 405 near the end of the upper surface 453 opposite the front surface 452, so that the display surface is easily visible to customers CU passing through the checkout lane LA. The housing 450 holds the receipt printer 408 below the fixed scanner 406, so that receipts are ejected toward the front surface 452.

[0127] The touch panel 404 is installed above the fixed scanner 406 so that the display surface can be easily seen from the customer CU facing the front surface 452. The handheld scanner 407 is connected to the transmission line 413 provided inside the housing 450 via a cable and can be used by pulling it out to the front side of the front surface 452. Figure 7In the figure, a handheld scanner 407 is shown as being placed in the collection. A human detection sensor 409 is provided within the housing 450 to detect customers CU passing through the checkout lane LA through a slit 454 formed in a side surface 451. A warning light unit 410 is mounted on the top of a rod 460 erected on the upper surface 453 of the housing 450.

[0128] in addition, Figure 6 The processor 401 , the main storage unit 402 , the auxiliary storage unit 403 , the sound unit 411 , and the communication unit 412 are disposed inside the housing 450 .

[0129] Figure 8 This is a block diagram showing the main circuit configuration of the information processing terminal 500 .

[0130] The information processing terminal 500 includes a processor 501 , a main storage unit 502 , an auxiliary storage unit 503 , a touch panel 504 , an audio unit 505 , an interface unit 506 , a wireless communication unit 507 , a transmission line 508 , and the like.

[0131] The functions of the processor 501 , the main storage unit 502 , the auxiliary storage unit 503 , and the transmission line 508 are substantially equivalent to those of the processor 101 , the main storage unit 102 , the auxiliary storage unit 103 , the communication unit 104 , and the transmission line 105 .

[0132] However, the auxiliary storage unit 503 stores a terminal program PRE, not a transaction processing program PRA. The terminal program PRE is an application program that describes the information processing procedures of the processor 501 for making the information processing terminal 500 function as a user interface for registering transaction products in the transaction processing device 100.

[0133] The touch panel 504 displays a screen for presenting information to the operator. Furthermore, the touch panel 504 allows the operator to input instructions by touching the screen. The operator of the information processing terminal 500 is typically a customer CU. However, a store clerk CL may also be the operator of the information processing terminal 500.

[0134] The audio unit 505 outputs sounds and voices for various guidance and warnings. As the audio unit, various well-known audio devices such as a speech synthesis device and a buzzer can be used alone or in combination.

[0135] The interface unit 506 is connected to an external device such as a barcode scanner 599. The interface unit 506 serves as an interface for transferring data with the connected external device. An existing USB (Universal Serial Bus) controller, etc., can be used as the interface unit 506. The barcode scanner 599 is mounted on the cart CA and has a reading window. The barcode scanner 599 uses image processing to identify the barcode information represented by the barcode in front of the reading window. The barcode scanner 599 then outputs the barcode information. Alternatively, the barcode scanner 599 can use other known devices that optically read barcodes using laser reflection. Furthermore, the barcode scanner 599 can use a known device that uses object recognition technology to identify products based on images of the products themselves obtained by photographing the products. Instead of or in addition to the barcode scanner 599, a camera provided in the information processing terminal 500 can also be used to read barcodes.

[0136] The wireless communication unit 507 performs communication processing for wirelessly communicating data via the communication network 2. As the wireless communication unit 507, for example, an existing wireless communication device for wireless LAN can be used. In addition, a communication unit connected to the communication network 2 by wire can be used instead of or in addition to the wireless communication unit 507.

[0137] As the basic hardware of the information processing terminal 500, it is assumed that hardware such as a tablet-type information processing device is used. The information processing terminal 500 is typically transferred while the terminal program PRE is stored in the auxiliary storage unit 503. However, the hardware and the terminal program PRE can be transferred separately, even if the terminal program PRE is not stored in the auxiliary storage unit 503, or if another version of an application of the same type is stored in the auxiliary storage unit 503. The information processing terminal 500 is then configured by writing the terminal program PRE to the auxiliary storage unit 503 in response to an operation by any operator. The terminal program PRE can be transferred by storing it in a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communicating via a network. The terminal program PRE can be stored in the main storage unit 502.

[0138] Figure 9 2 is a block diagram showing the main circuit configuration of the monitoring terminal 600 .

[0139] The monitoring terminal 600 includes a processor 601, a main storage unit 602, an auxiliary storage unit 603, a clerk-side touch panel 604, a keyboard 605, a fixed scanner 606, a handheld scanner 607, a settlement terminal 608, a change unit 609, a receipt printer 610, a customer-side touch panel 611, a customer display 612, a sound unit 613, a communication unit 614 and a transmission line 615.

[0140] The functions of the processor 601, main storage unit 602, auxiliary storage unit 603, audio unit 613, communication unit 614, and transmission line 615 are substantially equivalent to those of the processor 101, main storage unit 102, auxiliary storage unit 103, communication unit 104, and transmission line 105. Furthermore, the functions of the clerk-side touch panel 604, keyboard 605, fixed scanner 606, handheld scanner 607, payment terminal 608, change unit 609, receipt printer 610, customer-side touch panel 611, customer display 612, and audio unit 613 are substantially equivalent to those of the clerk-side touch panel 204, keyboard 205, fixed scanner 206, handheld scanner 207, payment terminal 208, change unit 209, receipt printer 210, customer-side touch panel 211, customer display 212, and audio unit 213. In other words, the monitoring terminal 600 has the same hardware structure as the POS terminal 200.

[0141] However, in addition to the transaction processing program PRB, the auxiliary storage unit 603 also stores a monitoring program PRF. The monitoring program PRF is an application program that contains information processing procedures for assisting store clerks CL in monitoring the checkout lanes LA for unauthorized access. Thus, the monitoring terminal 600 is a device that adds monitoring assistance functionality to the POS terminal 200. However, the monitoring terminal 600 can also be configured without transaction processing functionality. In this case, the basic hardware of the monitoring terminal 600 can be various types of general-purpose computers, such as desktop, laptop, or tablet computers.

[0142] The transfer of the monitoring terminal 600 is typically performed while the transaction processing program PRB and the monitoring program PRF are stored in the auxiliary storage unit 603. However, the hardware and at least one of the transaction processing program PRB and the monitoring program PRF can be transferred separately, provided that the auxiliary storage unit 403 does not store at least one of the two programs, or that the auxiliary storage unit 603 stores another version of an application of the same type. The monitoring terminal 600 can then be configured by writing the transaction processing program PRB and the monitoring program PRF to the auxiliary storage unit 603 in response to an operation by any operator. The transaction processing program PRB and the monitoring program PRF can be transferred by storing them in a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communicating over a network. The transaction processing program PRB and the monitoring program PRF can be stored in the main storage unit 402.

[0143] Figure 10 This is a block diagram showing the main circuit configuration of the POS server 700 .

[0144] The POS server 700 includes a processor 701 , a main storage unit 702 , an auxiliary storage unit 703 , a communication unit 704 , and a transmission line 705 .

[0145] The functions of the processor 701 , main storage unit 702 , auxiliary storage unit 703 , communication unit 704 and transmission line 705 are substantially equivalent to those of the processor 101 , main storage unit 102 , auxiliary storage unit 103 , communication unit 104 and transmission line 105 .

[0146] However, the auxiliary storage unit 703 stores a transaction management program PRG, not a transaction processing program PRA. The transaction management program PRG is an application program that describes the information processing procedures of the processor 701 used to manage transactions processed using the product sales system 1. Furthermore, a portion of the storage area of ​​the auxiliary storage unit 703 is used to store a transaction database DBA. The transaction database DBA is a database that accumulates transaction data indicating the details of settled transactions for each transaction.

[0147] The basic hardware of the POS server 700 can be, for example, a general-purpose server device. Transfer of the POS server 700 is typically performed with the transaction management program PRG stored in the auxiliary storage unit 703. However, it is possible to transfer the hardware and the transaction management program PRG separately, without the transaction management program PRG stored in the auxiliary storage unit 703, or with another version of the same application program stored in the auxiliary storage unit 703. The POS server 700 can then be configured by writing the transaction management program PRG to the auxiliary storage unit 703 in response to an operation by any operator. The transaction management program PRG can be transferred by storing it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communicating over a network. The transaction management program PRG can be stored in the main storage unit 702.

[0148] Next, the operation of the merchandise sales system 1 constructed as described above will be described. The various processes described below are merely examples, and the order of some processes may be modified, some processes may be omitted, or other processes may be added as appropriate. For example, in the following description, the description of some processes has been omitted to facilitate understanding of the characteristic operations of this embodiment. For example, if an error occurs, a process to address the error may be performed, but the description of such a process has been omitted.

[0149] Figure 11 This is a sequence diagram related to transaction processing using the information processing terminal 500.

[0150] In the transaction processing device 100 and the information processing terminal 500, the processor 101 and the server 501 collaborate to perform registration processing (ACT 101) and user interface processing (ACT 501). Accordingly, the processor 101, using the information processing terminal 500 as a user interface terminal, receives instructions from the customer CU, registers the products the customer CU wishes to purchase as transaction items, and generates transaction data representing a list of transaction items. The registration process involves, for example, having the information processing terminal 500 read the barcode of the product the customer CU wishes to purchase, or adding a product designated by the customer CU using a pre-set key as a transaction item.

[0151] When the customer CU performs a predetermined operation on the information processing terminal 500 to designate the start of checkout, the processor 501 of the information processing terminal 500 proceeds to ACT 502 .

[0152] As ACT 502 , the processor 501 notifies the transaction processing apparatus 100 that the start of checkout has been designated.

[0153] When the transaction processing device 100 processor 101 is notified of the checkout start instruction, the process proceeds to ACT 102 .

[0154] As ACT 102 , the processor 101 instructs the information processing terminal 500 to display a handover screen.

[0155] When the processor 501 of the information processing terminal 500 is instructed to display the handover screen, the process proceeds to ACT 503 .

[0156] As ACT 503, processor 501 displays a handover screen on touch panel 504. The handover screen is a screen for handing over the function of the user interface terminal related to the transaction being processed from information processing terminal 500 to checkout gate 400. The handover screen includes, for example, a QR code (hereinafter referred to as a handover code) representing handover data, which is used by checkout gate 400 to request checkout data based on the transaction data from transaction processing device 100.

[0157] On the other hand, when the processor 401 of the checkout gate 400 is in an operating state allowing use by the customer CU, it executes gate control processing according to the gate control program PRD.

[0158] Figure 12 、 Figure 13 and Figure 14 This is a flow chart of the gate control process.

[0159] As ACT 401, the processor 401 causes the touch panel 404 and the display unit 405 to display a standby screen. The standby screen is a screen for guiding the customer CU in performing an operation while waiting for the customer CU to perform an operation.

[0160] Figure 15 This is a screen showing an example of a standby screen displayed on touch panel 404 .

[0161] The standby screen and the various screens described below illustrate the primary display objects; some display objects may be omitted. For example, an image may be included to help the user visualize the operations they are expected to perform. The content of each screen can be appropriately determined, for example, by the specifier of the product sales system 1.

[0162] Figure 15The standby screen shown includes character messages MEA and MEB. The character message MEA guides the customer CU who has completed the settlement related to the transaction and wants to exit the store to scan the product barcode of one of the transaction products (any product barcode included in the transaction product) or the receipt barcode. The character message MEB guides the customer CU to touch the screen of the touch panel 404 in order to start using the information processing terminal 500 to start settling the registered transaction products. In addition, the product barcode is a barcode that is shown on the product and represents the barcode information containing the product code as the identifier of the product. The receipt barcode is a barcode that represents the barcode information containing the transaction code as the transaction identifier and is shown on the receipt. As the product barcode and the receipt barcode, a one-dimensional barcode is typically used. However, as the product barcode and the receipt barcode, other types of optically readable codes such as a two-dimensional code can be used. The receipt barcode (receipt code) is code information that represents the settlement of the completed transaction.

[0163] Figure 16 4 is a schematic diagram showing an example of a standby screen displayed on the display unit 405 .

[0164] Figure 16 The illustrated standby screen is a screen that guides the customer CU who has completed the settlement related to the transaction and wants to leave the store to scan a product barcode of the transaction product.

[0165] As Figure 12 In ACT 402, the processor 401 confirms whether the barcode has been scanned. Then, if the processor 401 cannot confirm the corresponding event, it is determined to be "No" and proceeds to ACT 403.

[0166] As ACT 403 , the processor 401 checks whether the screen of the touch panel 404 is touched. If the corresponding event cannot be confirmed, the processor 401 makes a “No” determination and proceeds to ACT 404 .

[0167] In ACT 404, processor 401 confirms whether the person has passed through checkout lane LA. If processor 401 cannot confirm the corresponding event, it determines "No" and returns to ACT 402. Note that "checkout lane LA" here and in the following description refers to the checkout lane LA facing checkout gate 400, which is the subject of the description.

[0168] In this manner, as ACT 402 to ACT 404 , the processor 401 waits for a barcode to be scanned, a screen to be clicked, or a person to pass by.

[0169] If multiple checkout gates 400 are installed, a customer CU using an information processing terminal 500 displaying a handover screen on the touch panel 504 as described above randomly selects a checkout gate 400 displaying a standby screen from among these checkout gates 400 and touches the screen of the touch panel 504 provided on that checkout gate 400. When the touch panel 504 detects a click, the processor 401 determines "yes" in ACT 403 and proceeds to ACT 405.

[0170] As ACT 405 , the processor 401 causes the touch panel 404 and the display unit 405 to display a handover guidance screen. The handover guidance screen guides the customer CU to have the handheld scanner 407 read the handover code included in the handover screen displayed on the touch panel 504 of the information processing terminal 500 .

[0171] As ACT 406 , the processor 401 waits for the handover code to be scanned.

[0172] As described above, after touching the screen of touch panel 504, customer CU aligns the reading window of handheld scanner 407 with the handover code. Handheld scanner 407 then reads the handover code and outputs the barcode information represented by the handover code to processor 401. Accordingly, processor 401 determines "yes" in ACT 406 and proceeds to ACT 407.

[0173] Alternatively, the handover code can be read by the fixed scanner 406. Specifically, for example, if the information processing terminal 500 is removable from the cart CA or a portable information processing device is used as the information processing terminal 500, the touch panel 504 of the information processing terminal 500 is aligned with the fixed scanner 406. The handover guidance screen preferably includes content that guides the customer CU to read a hypothetical handover code.

[0174] As ACT 407, the processor 401 obtains the transaction data based on the barcode information output from the handheld scanner 407. Figure 11 As shown, the processor 401 requests the checkout data from the transaction processing device 100 .

[0175] When the checkout gate 400 requests the checkout data, the processor 101 in the transaction processing device 100 advances the process to ACT 103 .

[0176] As ACT 103, processor 101 transmits predetermined transaction data for calculating and settling the payment based on the transaction details indicated by the transaction data to checkout gate 400, the requesting source. Therefore, in ACT 407, processor 401 of checkout gate 400 acquires the transaction data transmitted and received by communication unit 412 as described above.

[0177] As described above, if the processor 401 has obtained the checkout data, it proceeds to Figure 12 ACT 408.

[0178] As ACT 408, the processor 401 performs a checkout process based on the obtained checkout data. That is, the processor 401 performs, for example, a calculation process for determining the settlement amount associated with the corresponding transaction based on the obtained checkout data. The calculation process may be the same process as that performed by a checkout machine using, for example, an existing semi-self-service POS system. Then, for example, the processor 401 performs a settlement process for settling the settlement amount determined as described above. As an example, it is assumed that the settlement process is performed using electronic currency provided solely by a business operating a store. In this case, the identifier of the customer CU is obtained when the information processing terminal 500 is started, and the electronic currency balance associated with the identifier is used for settlement. However, in the settlement at the checkout gate 400, various settlement methods can be appropriately used, such as credit card settlement, code settlement, prepaid settlement, points settlement, gift certificate settlement, or cash settlement. Furthermore, in the settlement at the checkout gate 400, electronic currency settlement provided by other settlement providers different from the business operating the store can be used. In addition, according to the settlement method that can be used, necessary additional settings that are not shown in FIG. Figure 6 , in order to settle with that settlement method.

[0179] As ACT 409, processor 401 confirms whether an electronic receipt should be applied. If the customer CU identifier has been obtained as described above, processor 401 confirms whether settings have been previously made to apply an electronic receipt to the customer CU identified by the identifier. Processor 401 can cause the customer CU to specify whether an electronic receipt should be applied, and based on this specification, confirms whether the electronic receipt should be applied. If processor 401 cannot confirm that an electronic receipt should be applied, it determines "No" and proceeds to ACT 410.

[0180] As ACT 410, processor 401 issues a paper receipt showing the transaction details, settlement results, etc., and a receipt barcode. Specifically, processor 401 generates a receipt image showing, for example, the transaction details, settlement results, etc., and a settlement completion code, and causes receipt printer 408 to print the receipt image. Consequently, a paper receipt is issued by receipt printer 408 printing the receipt image on receipt paper.

[0181] On the other hand, if the processor 401 can confirm that the electronic receipt should be used, it determines "yes" in ACT 409 and proceeds to ACT 411.

[0182] As ACT 411, processor 401 registers the electronic receipt containing the transaction details, settlement results, etc., and the receipt barcode in electronic receipt server 3. Specifically, processor 401 transmits predetermined request data for requesting the registration of the electronic receipt, along with notification of the transaction details, settlement results, etc., and a settlement completion code, to electronic receipt server 3. Upon receiving this request data, electronic receipt server 3 can view the electronic receipt screen showing the notified transaction details, settlement results, etc., and the receipt barcode from any information terminal.

[0183] When ACT 410 or ACT 411 is completed, the processor 401 proceeds to ACT 412 in either case.

[0184] As ACT 412, the processor 401 notifies the transaction processing device 100 of the result of the settlement process. Based on the notification, the processor 101 of the transaction processing device 100 proceeds to Figure 11 ACT104 in.

[0185] As ACT 104, the processor 401 sends transaction data related to the transaction being processed this time to the POS server 700. This transaction data can be the same as the transaction data in the existing POS system. That is, the transaction data can include transaction title, product data, combination discount data, customer data, total data, credit data, etc. In addition, the product data is data representing a list of transaction products, which is equivalent to list data. What kind of data is included in the transaction data can be appropriately determined by, for example, the specification determiner of the product sales system 1. However, the transaction data is data that can at least determine what kind of product was traded in the corresponding transaction. In addition, the processor 401 includes exit data indicating the exit status of the customer CU from the store in the transaction data as an indication of a non-exit status. In addition, the settlement method can be included in the list data.

[0186] Upon receiving the transaction data, the processor 701 of the POS server 700 proceeds to ACT 701 .

[0187] As ACT 701, the processor 701 updates the transaction database DBA to include the aforementioned transaction data. In this case, the list data may include the settlement method. Thus, the transaction database DBA is a database that accumulates transaction data, including item data as list data, for each settled transaction. The auxiliary storage unit 703 is an example of a storage unit.

[0188] In addition, as Figure 12 In ACT 412 , the processor 401 of the checkout gate 400 notifies the checkout result and proceeds to ACT 413 .

[0189] As ACT 413 , the processor 401 performs passage permission processing.

[0190] Figure 17 This is a flow chart of the access permission process.

[0191] As ACT 451, the processor 401 initiates a notification of passage permission. This notification is intended to inform the customer CU and nearby personnel that passage through the checkout lane LA is permitted. For example, the processor 401 illuminates the warning light unit 410 in blue to notify that passage is permitted. The processor 401 also causes the audio unit 411 to output a voice message, such as "Please pass through the gate," to notify that passage is permitted. Alternatively, the processor 401 may perform other actions to notify that passage is permitted, such as causing the audio unit 411 to output a predetermined notification sound. However, the processor 401 may only perform some of these actions to notify that passage is permitted.

[0192] Furthermore, in addition to the above, in the notification of passage permission, processor 401 causes touch panel 404 to display, for example, a first guidance screen. In addition to the above, in the notification of passage permission, processor 401 causes display unit 405 to display, for example, a second guidance screen.

[0193] Figure 18 This is a schematic diagram showing an example of the first guidance screen.

[0194] Figure 18 The first guidance screen shown includes a character message indicating that the customer is allowed to pass through the checkout lane LA because the checkout has been completed. In other words, it is a guidance screen notifying that the customer is allowed to pass.

[0195] Figure 19 This is a schematic diagram showing an example of the second guidance screen.

[0196] Figure 19 The second guidance screen shown includes a character message indicating that the time allowed to pass through the checkout lane LA is limited and numbers indicating the remaining time allowed to pass through the checkout lane LA. Figure 19 The second guide screen shown is an example of a case where the remaining time is 10 seconds, and the number "10" represents the remaining time. For the second guide screen, whenever the remaining time changes, the processor 401 updates the number representing the remaining time.

[0197] The second guidance screen allows the customer CU to identify the remaining time allowed to pass through the checkout lane LA. Based on this screen, the customer CU can determine whether to expedite the passage.

[0198] The various displays and various sound outputs illustrated here are examples of notifying the customer CU that he or she is allowed to pass through the checkout lane LA. Thus, the touch panel 404, the display unit 405, the warning light unit 410, and the sound unit 411 are examples of the notification unit and the third notification unit.

[0199] Processor 401 proceeds to ACT 452 in the state of passing permission notification. In ACT 452, processor 401 confirms whether the person has passed through checkout lane LA. Then, if processor 401 cannot confirm the corresponding event, it determines "No" and proceeds to ACT 453.

[0200] As ACT 453, the processor 401 confirms whether a predetermined permitted time has elapsed since the start of the passage permission notification as ACT 451. If the processor 401 cannot confirm the corresponding event, it determines "No" and returns to ACT 452.

[0201] Thus, as ACT 452 and ACT 453 , the processor 401 waits for a person to pass or for a permitted time to elapse.

[0202] When the customer CU passes through the checkout lane before the permitted time has elapsed and the human sensing sensor 409 detects the passage of the person, the processor 401 makes a “Yes” determination in ACT 452 and proceeds to ACT 454 .

[0203] As ACT 454, the processor 401 requests the POS server 700 to update the logout data. Then, upon receiving the request, the processor 701 of the POS server 700 proceeds to Figure 11 Alternatively, the processor 601 may receive a logout notification and request the POS server 700 to update the logout data.

[0204] As Figure 11 In ACT 702 , the processor 701 updates the exit data included in the transaction data included in the transaction database DBA in ACT 701 to indicate an exited state.

[0205] In the checkout gate 400, the processor 401 completes Figure 17 After receiving the notification in ACT 454, the process proceeds to ACT 455. Alternatively, if the processor 401 cannot confirm whether the customer CU has passed through the checkout lane LA and the permitted time has expired, the processor 401 determines "Yes" in ACT 453, skipping ACT 454 and proceeding to ACT 455. For example, even after completing checkout, the customer CU may return to the store without passing through the checkout lane LA. In this case, the processor 401 determines "Yes" in ACT 453.

[0206] As ACT 455, the processor 401 stops the passage permission notification. Then, the processor 401 ends the passage permission processing and returns to Figure 12 ACT401 in the process and prepare to receive the next customer CU.

[0207] Figure 20 This is a sequence diagram related to the transaction process using the POS terminal 200. In the POS terminal 200, when the processor 201 receives a designation to start registration by a predetermined operation by the store clerk CL, the process proceeds to ACT 201.

[0208] In ACT 201, the processor 201 registers the products that the customer CU wants to purchase as transaction products based on the operations of the clerk CL using various devices of the POS terminal 200, and generates transaction data representing a list of transaction products. Then, when the clerk CL declares that the registration is completed, the processor 201 proceeds to ACT 202.

[0209] As ACT 202, processor 201 performs checkout processing for calculating and settling the payment based on the transaction details represented by the transaction data generated in ACT 201. Specifically, processor 201 performs calculation processing, for example, to determine the settlement amount associated with the transaction based on the generated transaction data. Processor 201 then performs settlement processing, for example, to settle the settlement amount determined as described above. The settlement processing can utilize various settlement methods, such as credit card settlement, code settlement, prepaid settlement, points settlement, gift certificate settlement, or cash settlement.

[0210] The above-mentioned processing for registration and checkout may be the same processing as that performed using, for example, an existing face-to-face POS terminal.

[0211] As ACT 203, the processor 201 confirms whether an electronic receipt should be used. If the customer CU identifier is obtained during the aforementioned registration or checkout process, the processor 201 confirms whether settings have been previously made to apply an electronic receipt to the customer CU identified by the identifier. The processor 201 can allow the customer CU or the store clerk CL to specify whether an electronic receipt should be used, and based on this specification, confirms whether an electronic receipt should be applied. If the processor 201 cannot confirm that an electronic receipt should be applied, it determines "No" and proceeds to ACT 204.

[0212] As ACT 204, processor 201 issues a paper receipt that shows the transaction details, payment results, and the like, along with a receipt barcode. Specifically, processor 201 generates a receipt image that shows, for example, the transaction details, payment results, and the like, and causes receipt printer 210 to print the receipt image. Consequently, a paper receipt is issued, created by printing the receipt image on receipt paper by receipt printer 210.

[0213] On the other hand, if the processor 201 can confirm that the electronic receipt should be used, it determines "yes" in ACT 203 and proceeds to ACT 205.

[0214] As ACT 205, processor 201 registers the electronic receipt containing the transaction details, payment results, and the receipt barcode in electronic receipt server 3. Specifically, processor 201 transmits predetermined request data for requesting the registration of the electronic receipt, along with notification of the transaction details, payment results, and the like, to electronic receipt server 3. Upon receiving this request data, electronic receipt server 3 enables the notified electronic receipt screen, which displays the transaction details, payment results, and the receipt barcode, to be viewed from any data terminal.

[0215] When ACT 204 or ACT 205 is completed, the processor 201 proceeds to ACT 206 in either case.

[0216] As ACT 206, processor 201 transmits transaction data regarding the currently processed transaction to POS server 700. This transaction data can be identical to the transaction data in existing POS systems. Specifically, the transaction data can include the transaction title, product data, combination discount data, customer data, total data, and credit data. Furthermore, the product data represents a list of the products traded. The type of data included in the transaction data can be appropriately determined, for example, by the specifier of product sales system 1. However, the transaction data should at least be data that can be used to determine what type of product was traded in the transaction. In this embodiment, the customer CU associated with the transaction processed using POS terminal 200 is not subject to exit control based on checkout gate 400 and is unrelated to the application of checkout gate 400. Therefore, processor 201 does not include exit data in the transaction data. In other words, existing face-to-face POS terminals can be used as POS terminal 200.

[0217] Upon receiving the transaction data, the processor 701 of the POS server 700 proceeds to ACT 711 .

[0218] As ACT 711 , the processor 701 updates the transaction database DBA to include the above-mentioned transaction data.

[0219] Figure 21 This is a sequence diagram related to the transaction process using the POS terminal 300. In the POS terminal 300, when the processor 301 receives a registration start instruction by a predetermined operation of the customer CU, the process proceeds to ACT 301.

[0220] In ACT 301, processor 301 registers the items that customer CU wishes to purchase as transaction items based on their operations using various devices of POS terminal 300 and generates transaction data representing a list of the items. For example, processor 301 registers items specified by customer CU by reading their barcodes using fixed scanner 306 or handheld scanner 307, or by the customer CU operating a pre-associated key displayed on touch panel 304 or included on keyboard 305 as transaction items. When customer CU declares registration complete, processor 301 proceeds to ACT 302.

[0221] As ACT 302, processor 301 performs settlement processing for calculating and settling the payment based on the transaction details represented by the transaction data generated in ACT 301. Specifically, processor 301 performs, for example, calculation processing to determine the settlement amount associated with the transaction based on the generated transaction data. Processor 301 then performs, for example, settlement processing to settle the settlement amount determined as described above. The settlement processing can utilize various settlement methods, such as credit card settlement, code settlement, prepaid settlement, point settlement, gift certificate settlement, or cash settlement.

[0222] The above-mentioned process for registration and checkout may be the same process as that performed using, for example, an existing fully self-service POS terminal.

[0223] As Act 303, processor 301 confirms whether an electronic receipt should be used. If a customer CU identifier is obtained during the aforementioned registration or checkout process, processor 301 confirms whether settings have been previously made to apply an electronic receipt to the customer CU identified by the identifier. Processor 301 can allow the customer CU to specify whether an electronic receipt should be used, and based on this specification, confirms whether the electronic receipt should be used. If processor 301 cannot confirm whether an electronic receipt should be used, it determines "No" and proceeds to Act 304.

[0224] As ACT 304, processor 301 issues a paper receipt that shows the transaction details, payment results, etc., along with a receipt barcode. Specifically, processor 301 generates a receipt image that shows the transaction details, payment results, etc., along with a receipt barcode, and prints the receipt image on receipt paper using receipt printer 310. Consequently, a paper receipt is issued, created by printing the receipt image on receipt paper using receipt printer 310.

[0225] On the other hand, if the processor 301 can confirm that the electronic receipt should be used, it determines "yes" in ACT 303 and proceeds to ACT 305.

[0226] As ACT 305, processor 301 registers the electronic receipt containing the transaction details, settlement results, etc., and the receipt barcode in electronic receipt server 3. Specifically, processor 301 transmits predetermined request data for requesting the registration of the electronic receipt, along with the transaction details, settlement results, etc., and the receipt barcode, to electronic receipt server 3. Upon receiving this request data, electronic receipt server 3 enables the notified electronic receipt screen, which displays the transaction details, settlement results, etc., and the receipt barcode, to be viewed from any information terminal.

[0227] When ACT 304 or ACT 305 is completed, the processor 301 proceeds to ACT 306 in either case.

[0228] As ACT 306, processor 301 transmits transaction data related to the currently processed transaction to POS server 700. This transaction data can be the same as the transaction data in existing POS systems. That is, the transaction data can include the transaction title, product data, combination discount data, customer data, total data, and credit data. Furthermore, the product data is data representing a list of the products traded. The type of data included in the transaction data can be appropriately determined by, for example, the specifier of the product sales system 1. However, the transaction data is data that can at least determine what product was traded in the corresponding transaction. In this embodiment, the customer CU related to the transaction processed using POS terminal 300 is the subject of exit control by checkout gate 400. Therefore, processor 301 includes exit data indicating a non-exit status in the transaction data.

[0229] Upon receiving the transaction data, the processor 701 of the POS server 700 proceeds to ACT 721 .

[0230] As ACT 721 , the processor 701 updates the transaction database DBA to include the above-mentioned transaction data.

[0231] As described above, if a customer CU who has completed payment at the checkout gate 400 but has not passed through the checkout lane LA within the permitted time attempts to exit the store without purchasing additional items, the receipt barcode displayed on the screen of the paper receipt or electronic receipt issued by the checkout gate 400 is read by the fixed scanner 406 or handheld scanner 407 of any checkout gate 400 in a standby state. The fixed scanner 406 and handheld scanner 407 are also referred to as a reading unit, and the reading unit reads the receipt barcode, which is an example of an optically readable code.

[0232] The customer CU who has completed payment using the POS terminal 300 has the fixed scanner 406 or the handheld scanner 407 of any checkout gate 400 in a standby state scan the paper receipt issued by the POS terminal 300 or the receipt barcode displayed on the electronic receipt screen.

[0233] In addition, in the case of a number of situations such as losing the paper receipt issued by the checkout gate 400 or the POS terminal 300 or not being able to display the electronic receipt screen because the customer CU does not carry a smartphone and many other situations make it difficult for the fixed scanner 406 or the handheld scanner 407 to read the receipt barcode (receipt code), the customer CU can also use the exit confirmation function based on the comparison of the transaction goods. In other words, exit confirmation can be performed without reading the receipt barcode. Then, when the customer CU uses this function, the fixed scanner 406 or the handheld scanner 407 reads the product barcode of one of the settled transaction goods. Since the product barcode includes the product code as the product identifier, each scanner of the fixed scanner 406 and the handheld scanner 407 is an example of an acquisition unit that obtains the identifier of the product according to the operation of the customer CU.

[0234] When the fixed scanner 406 or the handheld scanner 407 reads the barcode, the barcode information represented by the barcode is notified to the processor 401. Figure 12 The judgment in ACT 402 is "Yes", and the process proceeds to Figure 13 ACT421 in.

[0235] As ACT 421 , the processor 401 confirms whether the read barcode is a product barcode. If the processor 401 cannot confirm the corresponding event, it determines "No" and proceeds to ACT 422 .

[0236] As ACT 422, the processor 401 confirms whether the read barcode is a bill barcode. Then, if the processor 401 cannot confirm the corresponding event, it determines to be "No" and returns to Figure 5 At this time, the processor 401 may perform a guidance operation such as a screen display, which is used to guide the customer CU to read the product barcode or the receipt barcode.

[0237] If the product barcode is read as described above, the processor 401 determines "Yes" in ACT 421 and proceeds to ACT 423.

[0238] As ACT 423, the processor 401 inquires about the transaction with the POS server 700 and notifies the POS server 700 of the product code contained in the barcode information obtained by reading the product barcode. In this way, as the processor 401 executes information processing based on the gate control program PRD, the computer with the processor 401 as the core functions as a first notification unit.

[0239] When the processor 701 in the POS server 700 receives an inquiry regarding a transaction as described above, it executes information processing (hereinafter referred to as transaction search processing) based on the transaction management program PRG.

[0240] Figure 22 This is a flowchart of the transaction retrieval process.

[0241] In the following description of the transaction search process, "checkout gate 400" refers to the checkout gate 400 that has performed the above-mentioned inquiry.

[0242] As ACT 731, the processor 701 retrieves transactions that have been settled in the past and include the commodity identified by the commodity code notified during the inquiry as a transaction commodity. For example, the processor 701 first extracts transaction data that meets the following conditions from the transaction data included in the transaction database DBA:

[0243] Relevant to transactions conducted during the scheduled search period.

[0244] The commodity identified by the notified commodity code is included as a transaction commodity.

[0245] Contains exit data indicating that the system is in a non-exited state.

[0246] The search period is a predetermined period starting from when the product code (product identifier) ​​is acquired by the acquisition unit and the product code is acquired from the checkout gate 400. Transactions settled during the search period are targeted.

[0247] As an example, it is assumed that the search period is the most recent transactions within a certain time width, such as a 10-minute period (the 10 minutes from the time the product identifier is obtained). The period to be used as the search period can be appropriately determined by the standard determiner of the product sales system 1 or the store manager, etc. In addition, the locking object can be, for example, the current day as the search period (the period from the date when the product identifier is obtained until the date changes to the previous day), and the transactions on the current day as the locking object. In addition, the locking object can be the most recent predetermined number of transactions as the search object. In this case, the search period is the period during which the corresponding number of transactions are performed (the period during which the predetermined number of transactions are performed from the time the product identifier is obtained). As an example of the number of recent transactions, it is assumed that it is 20 transactions (20 transactions from the time the product identifier is obtained), but the number of transactions can be appropriately determined by the standard determiner of the product sales system 1 or the store manager, etc.

[0248] As ACT 732, the processor 701 confirms whether a corresponding transaction is found through the above search. Then, for example, if the processor 701 cannot extract any transaction data that meets the conditions in ACT 731, it determines "No" as no corresponding transaction and proceeds to ACT 733.

[0249] As ACT 733, the processor 701 notifies the checkout gate 400 of an error as a response to the transaction inquiry. That is, if the processor 701 does not find any transaction that meets the above conditions, it determines it as an error and notifies the checkout gate 400. The processor 701 then terminates the transaction search process.

[0250] For example, if the processor 701 can extract at least one transaction data that meets the conditions in ACT 731 , it determines “yes” in ACT 732 as the existence of a corresponding transaction and proceeds to ACT 734 .

[0251] In ACT 734, the processor 701 checks whether multiple transactions have been retrieved by the above search. For example, if only one transaction data meeting the conditions is extracted in ACT 731, the processor 701 determines "no" as not multiple transaction data and proceeds to ACT 735.

[0252] As ACT 735, processor 701 notifies checkout gate 400 of approval as a response to the transaction inquiry. Specifically, if processor 701 locks a transaction based on the aforementioned conditions, it determines that the transaction is approved and notifies checkout gate 400 accordingly. In this manner, by processor 701 executing information processing based on the transaction management program PRG, the computer, centered around processor 701, functions as a second notification unit.

[0253] The processor 701 then ends the transaction retrieval process accordingly.

[0254] For example, if a plurality of transaction data are extracted in ACT 731 , the processor 701 determines “yes” in ACT 734 and proceeds to ACT 736 .

[0255] In ACT 736, processor 701 confirms whether the lock termination condition has been met. The termination condition can be appropriately determined by the specifier of the merchandise sales system 1 or the store manager, etc. Specific examples of the termination condition will be described later. If processor 701 cannot confirm the corresponding event, it determines "No" and proceeds to ACT 737.

[0256] As ACT 737 , the processor 701 requests the checkout gate 400 to notify other products.

[0257] As Figure 13 ACT 423 in the checkout gate 400 proceeds to ACT 424 after the processor 401 inquires about the transaction.

[0258] As ACT 424 , the processor 401 confirms whether a request for notification of other products has been made. If the processor 401 cannot confirm the corresponding event, it determines “No” and proceeds to ACT 425 .

[0259] In ACT 425, the processor 401 confirms whether a permission notification has been issued. That is, the processor 401 determines whether a permission notification has been received from the processor 701. If the processor 401 cannot confirm the corresponding event, it determines "No" and proceeds to ACT 426.

[0260] As ACT 426 , the processor 401 confirms whether an error notification has been made. If the processor 401 cannot confirm the corresponding event, it determines “No” and returns to ACT 424 .

[0261] Thus, as ACT424 to ACT426, the processor 401 waits for any one of the notification request, permission notification and error notification. Then, when the notification of other commodities is requested from the POS server 700 as described above, the processor 401 determines "yes" in ACT424 and proceeds to ACT426. Figure 14 ACT441 in.

[0262] As ACT 441, the processor 401 causes the touch panel 404 to display an addition request screen. The addition request screen is a screen that requests the customer CU to have the fixed scanner 406 or the handheld scanner 407 read a product barcode that is different from the product barcode of the transaction product read so far.

[0263] Figure 23 This is a schematic diagram showing an example of an addition request screen.

[0264] Figure 23 The additional request screen shown is a screen in which a window WIA is superimposed on the standby screen. The window WIA displays a text message for the above request and also displays a button BUA. The button BUA is a soft key for the customer CU to declare that there are no more products.

[0265] If there are other transaction items whose product codes have not been read, the customer CU reads the product barcode of one of the corresponding transaction items with the fixed scanner 406 or the handheld scanner 407. Furthermore, if the customer has read the product barcodes of all transaction items, the customer declares that there are no more items by clicking a predetermined operation such as a button BUA.

[0266] As Figure 14 In ACT 441 , the processor 401 displays the add request screen and then proceeds to ACT 442 .

[0267] As ACT 442 , the processor 401 confirms whether the product barcode has been scanned. If the processor 401 cannot confirm the corresponding event, it determines “No” and proceeds to ACT 443 .

[0268] As ACT 443 , the processor 401 confirms whether or not the product has been declared out of stock. If the processor 401 cannot confirm the corresponding event, it determines “No” and proceeds to ACT 444 .

[0269] As ACT 444 , the processor 401 confirms whether the customer CU has passed through the checkout lane LA. If the processor 401 cannot confirm the corresponding event, it makes a “No” determination and returns to ACT 442 .

[0270] Thus, as ACT 442 to ACT 444 , the processor 401 waits for any one of scanning of a product barcode, announcement of absence of a product, or passage to occur.

[0271] When the product barcode is read by the fixed scanner 406 or the handheld scanner 407 , the processor 401 determines “Yes” in ACT 442 and proceeds to ACT 445 .

[0272] As ACT 445, processor 401 requests POS server 700 to lock the POS server 700 and simultaneously notifies fixed scanner 406 or handheld scanner 407 of the product code contained in the barcode information obtained by reading the product barcode. In this manner, processor 401 executes information processing based on gate control program PRD, allowing the computer, centered around processor 401, to function as a first notification unit.

[0273] Then, the processor 401 returns to Figure 13 Waiting state of ACT424 to ACT426.

[0274] Furthermore, upon detecting an operation for announcing that there is no product on, for example, the touch panel 404 , the processor 401 makes a “Yes” determination in ACT 443 and proceeds to ACT 446 .

[0275] As ACT 446, the processor 401 notifies the POS server 700 that there is no product. Then, the processor 401 returns to Figure 13 Waiting state of ACT424 to ACT426.

[0276] As Figure 22 In ACT 37 , the processor 701 in the POS server 700 proceeds to ACT 738 after requesting notification of other products.

[0277] As ACT 738 , the processor 701 confirms whether a lock request has been made. If the processor 701 cannot confirm the corresponding event, it makes a “No” determination and proceeds to ACT 739 .

[0278] As ACT 739 , the processor 701 confirms whether or not a notification of no product has been received. If the processor 701 cannot confirm the corresponding event, it determines “No” and proceeds to ACT 740 .

[0279] As ACT 740 , the processor 701 confirms whether the error pass has been notified. If the processor 701 cannot confirm the corresponding event, the processor 701 determines “No” and returns to ACT 738 .

[0280] Thus, as ACT738 to ACT740, the processor 701 waits for any one of a lock request, a notification of no merchandise, or a notification of wrong passage. Then, if a lock is requested as above, the processor 701 determines as "yes" in ACT78 and proceeds to ACT741.

[0281] As ACT 741, the processor 701 locks transactions from the multiple transactions found in the search in ACT 731, and the transactions will include as transaction commodities the commodities identified by the commodity code notified at the time of inquiry and the commodities identified by the commodity code notified at the time of the lock request. Then, after this, the processor 701 repeats ACT 734 and subsequent steps in the same manner as described above. In this way, if the processor 701 cannot lock a transaction in ACT 741, it will repeatedly perform the locking in ACT 741 while accepting lock requests accompanied by notifications of other commodity codes. In addition, when the processor 701 executes ACT 741 for the second time and thereafter, the transactions will include as transaction commodities the commodities identified by the commodity code notified at the time of inquiry and the commodities identified by the commodity codes notified separately at the time of the multiple lock requests before this.

[0282] In this way, the processor 701 locks the transaction by processing ACT 731 to ACT 741. In this way, the processor 701 executes information processing based on the transaction management program PRG, so that the computer with the processor 701 as the core functions as a locking unit.

[0283] In addition, the transaction can be locked using the settlement method. Specifically, the settlement method is included in the list data. When multiple transactions are extracted, the processor 401 displays an additional request screen on the touch panel 404 as ACT441. The additional request screen includes options for selecting a settlement method (credit card settlement, code settlement, prepaid settlement, points settlement, gift certificate settlement, and cash settlement). The option for selecting the settlement method on the touch panel is an acquisition unit that acquires the settlement method according to the customer's operation. When the transaction cannot be specified by reading the barcode of one product, the option for selecting the settlement method can be displayed. If the barcodes of multiple products are read and the transaction cannot be specified, the option for selecting the settlement method can be displayed. The locking unit locks the transaction by using the settlement method acquired by the acquisition unit and referring to the list data stored in the storage unit.

[0284] Even for customers who have lost their paper receipts or who are unable to display the electronic receipt screen due to not having a smartphone (and therefore cannot have the receipt barcode read), the settlement method is stored if settlement is complete. Therefore, extracting transactions by both product and settlement method is effective in locking in transactions that have already been settled. Furthermore, by allowing customers to select a settlement method, customers who have not yet completed settlement cannot select a settlement method. This allows customers who have not yet completed settlement to detect operational errors when the settlement method selection screen is displayed, even when reading the product barcode.

[0285] Furthermore, the termination condition confirmed by processor 701 in ACT 736 is assumed to be, for example, that the number of products used in locking a transaction reaches a predetermined number. If, even if the termination condition is met, a transaction cannot be locked, processor 701 determines "yes" in ACT 736 and proceeds to ACT 742. Specifically, if multiple transactions containing the predetermined number of products are locked, processor 701 proceeds to ACT 742.

[0286] As ACT 742, the processor 701 notifies the checkout gate 400 of an error as a response to the transaction inquiry. In other words, if a transaction cannot be locked even if the termination condition is met, the processor 701 determines it as an error and notifies the checkout gate 400. The processor 701 then terminates the transaction search process.

[0287] When the processor 701 is notified that there is no product as described above, it determines "Yes" in ACT 739 and proceeds to ACT 743.

[0288] As ACT 743, the processor 701 locks transactions whose transaction count matches the number of transaction products used in the locked transactions. The transaction count is indicated in the transaction header included in the transaction data, for example.

[0289] As ACT 744, the processor 701 checks whether multiple transactions have been found by the above-mentioned locking. Then, if the processor 701 has locked one transaction, it is determined as "No" because it is not a multiple transaction, and proceeds to ACT 745.

[0290] As ACT 745, the processor 701 notifies the checkout gate 400 of approval as a response to the inquiry regarding the transaction. Specifically, if the processor 701 is able to lock a transaction by locking in ACT 743, it determines that the transaction is approved and notifies the checkout gate 400 of this. The processor 701 then terminates the transaction search process accordingly.

[0291] If a plurality of transactions are found through the above-mentioned locking, the processor 701 determines “Yes” in ACT 744 and proceeds to ACT 746 .

[0292] As ACT 746, processor 701 notifies checkout gate 400 of an error in response to the transaction inquiry. Specifically, if another transaction has already been performed within the search, involving the exact same transaction item as the transaction being inquired about, processor 701 determines this to be an error and notifies checkout gate 400 of this fact. Processor 701 then terminates the transaction search process.

[0293] As described above, when the processor 701 in the POS server 700 receives the permission notification in ACT 735 or ACT 745, the processor 401 in the checkout gate 400 Figure 13 The judgment in ACT425 is "Yes", and the process proceeds to ACT427.

[0294] As ACT427, processor 401 and Figure 12 ACT413 in the same way performs the pass permission process. Then, when the processor 401 completes the pass permission process, it returns to Figure 12 ACT401 in.

[0295] Thus, when processor 401 determines "Yes" in ACT 425 and proceeds to ACT 427 based on the processor 701 receiving the permission notification in ACT 735, processor 401 controls the process to allow passage through checkout lane LA, based on the fact that the transaction is locked. In this way, as processor 401 executes information processing based on gate control program PRD, the computer, with processor 401 as the core, functions as a control unit.

[0296] As described above, when the processor 701 in the POS server 700 receives Figure 22 When an error notification is performed in ACT733, ACT742 or ACT746, the processor 401 Figure 13 The judgment in ACT426 is "Yes", and the process proceeds to ACT428.

[0297] As ACT 428, the processor 401 executes a call process. The call process is a process for calling a staff member (hereinafter referred to as a person in charge) who is responsible for handling errors at the checkout gate 400 and receiving the handling by the person in charge.

[0298] Thus, when processor 401 proceeds to ACT 428 upon receiving an error notification from processor 701, processor 401 performs processing for the responsible staff member to handle the situation in which the transaction cannot be locked as a single transaction. In this manner, by processor 401 executing information processing based on gate control program PRD, the computer centered around processor 401 functions as a processing unit.

[0299] Figure 24 This is a flowchart of call processing by the processor 401 of the checkout gate 400 and instruction issuance processing by the processor 601 of the monitoring terminal 600.

[0300] As ACT 461, the processor 401 starts a call notification. The call notification is to notify the customer CU that a store clerk is being called. The processor 401 displays, for example, a call screen on the touch panel 404 to perform the call notification. The processor 401 causes the display unit 405 to display, for example, a warning screen to perform the call notification. The processor 401 causes the warning light unit 410 to light up or flash in, for example, yellow to perform the call notification. The processor 401 causes the sound unit 411 to output a predetermined notification sound to perform the call notification. Alternatively, the processor 401 may perform other actions, such as causing the sound unit 411 to output a predetermined voice message to perform the call notification. However, the processor 401 may perform only some of these actions to perform the access permission notification.

[0301] Figure 25 This is a diagram showing an example of a call screen.

[0302] Figure 25 The calling screen shown is a screen showing a window WIB superimposed on the idle screen. The window WIB shows a character message for the above-mentioned guidance.

[0303] Figure 26 This is a schematic diagram showing an example of a warning screen.

[0304] Figure 26 The warning screen shown is a screen for warning the customer CU to prevent the customer CU from erroneously logging out.

[0305] As Figure 24 In ACT 462, the processor 401 issues a request to a predetermined request destination. In this embodiment, it is assumed that the monitoring terminal 600 is determined as the request destination for issuing an instruction.

[0306] The monitoring terminal 600 is installed, for example, at a store's service counter. It performs the same operations as existing POS terminals of the same type, thus processing transactions. This allows the monitoring terminal 600 to assist in situations where the POS terminal 200 is congested. Furthermore, the monitoring terminal 600 can be used to handle various requests from customers (CUs), such as returns.

[0307] Furthermore, when the processor 601 in the monitoring terminal 600 receives a request from the checkout gate 400 as described above, it executes the monitoring program PRF. Figure 24 The issuing instruction process shown in .

[0308] As ACT 601, the processor 601 initiates an instruction-issuing action. The instruction-issuing action is an action for issuing instructions to the person responsible for monitoring using the monitoring terminal 600 to address errors at the checkout gate 400. As the instruction-issuing action, the processor 601 displays, for example, on the clerk-side touch panel 604 an instruction-issuing screen for addressing errors occurring at the checkout gate 400, so that the checkout gate 400 for which the instruction is being issued can be identified. The processor 601 causes the audio unit 613 to output, for example, a predetermined instruction-issuing sound as the instruction-issuing action. Alternatively, the processor 601 may perform other actions as the instruction-issuing action, such as causing the audio unit 613 to output a predetermined voice message. However, the processor 601 may only perform some of these actions as the instruction-issuing action.

[0309] After the processor 401 of the checkout gate 400 requests issuance of an instruction in ACT 462 , the process proceeds to ACT 463 .

[0310] As ACT 463 , the processor 401 waits for the person in charge to start the operation.

[0311] The person in charge goes to the checkout gate 400 and performs the predetermined operation that the person in charge should perform in response to the instruction issued by the monitoring terminal 600. When the operation is performed, the processor 401 determines "yes" in ACT 463 and proceeds to ACT 464.

[0312] As ACT 464, the processor 401 performs an authentication process for confirming that the operator is the person in charge. This authentication process may be a well-known process for authenticating the operator. If the authentication is successful, the processor 401 proceeds to ACT 465.

[0313] As ACT 465, processor 401 performs transaction confirmation processing to confirm to the person in charge that the transaction of the customer CU currently using checkout gate 400 has been settled. During this transaction confirmation processing, for example, processor 401 causes touch panel 404 to display a transaction confirmation screen indicating the details of the settled transaction. Processor 401 then receives, for example, a designation from the person in charge as to which of the settled transactions the current transaction of the customer CU is.

[0314] As ACT 466 , the processor 401 stops the call in progress notification.

[0315] As ACT 467, the processor 401 notifies the monitoring terminal 600 of the completion of the response. Then, the processor 401 ends the call processing of this time and proceeds to Figure 13 ACT427 in , and perform the access permission processing in the same manner as above.

[0316] As ACT 601 , the processor 601 of the monitoring terminal 600 starts issuing an instruction operation, and then proceeds to ACT 602 .

[0317] As ACT 602 , the processor 601 waits for a completion notification. Then, when the checkout gate 400 notifies the processor 601 of the completion as described above, the processor 601 determines “Yes” and proceeds to ACT 603 .

[0318] As ACT 603, the processor 601 stops the instruction issuance operation. Then, the processor 601 ends the instruction issuance process.

[0319] When the barcode read by the processor 401 of the checkout gate 400 while the standby screen is displayed is a receipt barcode, Figure 13 The judgment in ACT422 is "Yes", and the process proceeds to ACT429.

[0320] As ACT 429, processor 401 confirms whether the read receipt barcode is valid during the exit check using checkout gate 400. Processor 401 confirms whether the receipt barcode meets predetermined conditions and, if so, determines it to be valid. The above conditions assume, for example, that the corresponding receipt barcode is a receipt barcode related to a transaction that has been settled by a POS terminal located in the same store as the store where checkout gate 400 is located and that is not included in the rejection list data DAB. However, this condition can be appropriately determined by the specifier of the merchandise sales system 1 or the store manager. For example, only one of the two conditions described above may be used. Alternatively, additional conditions may be added, such as a condition that the time elapsed since the settlement of the transaction related to the receipt barcode is less than a specified time. Then, if processor 401 can determine that it is valid, it responds as "Yes" and proceeds to ACT 430. In the case of this embodiment, when the processor 401 reads the receipt code related to the transaction for settlement processing using the POS terminal 300 , the checkout gate 400 , or the monitoring terminal 600 , the process proceeds to ACT 430 .

[0321] As ACT 430 , the processor 401 inquires the POS server 700 about the withdrawal status of the customer CU, and notifies the POS server 700 of the transaction code included in the barcode information represented by the read receipt barcode.

[0322] Upon receiving the above-described inquiry regarding the logout status, the processor 701 in the POS server 700 executes information processing (hereinafter referred to as logout confirmation processing) based on the transaction management program PRG.

[0323] Figure 27 This is a flowchart of the exit confirmation process.

[0324] As Act 751, the processor 701 confirms whether the customer CU associated with the transaction identified by the notified transaction code has not exited the store. For example, the processor 701 retrieves transaction data associated with the transaction identified by the notified transaction code from the transaction database DBA and confirms whether the exit data included in the corresponding transaction data indicates that the customer has not exited. If the exit data indicates that the customer has not exited, the processor 701 determines "yes" that the customer CU has not exited the store and proceeds to Act 752.

[0325] As ACT 752 , the processor 701 notifies the checkout gate 400 that is the source of the inquiry that the user has not checked out as a response to the inquiry about the checkout status.

[0326] In addition, if the corresponding exit data is not in a state indicating that the customer CU has not exited the store, the processor 701 determines "No" and proceeds to ACT 753.

[0327] As ACT 753 , the processor 701 notifies the checkout gate 400 that is the source of the inquiry that the checkout has been completed as a response to the inquiry about the checkout status.

[0328] Then, after completing the notification in ACT 752 or ACT 753, the processor 701 ends the current exit confirmation processing.

[0329] As Figure 13 After executing ACT 430 , the processor 401 of the checkout gate 400 makes an inquiry and proceeds to ACT 431 .

[0330] As ACT 431, the processor 401 confirms whether it has been notified that it has not logged out. Then, when the processor 401 is notified by the POS server 700 that it has not logged out as described above, the processor 401 determines that it is "yes" and proceeds to ACT 427 and performs the pass permission process in the same manner as described above. Figure 17 In ACT 454, when the processor 401 requests the update of the exit data, the transaction code contained in the barcode information represented by the read bill barcode is notified. When such a request is received, the processor 701 of the POS server 700 proceeds to, for example, Figure 21 ACT722 in.

[0331] As ACT 722 , the processor 701 retrieves the transaction data identified by the notified transaction code from the transaction database DBA, and updates the exit data included in the corresponding transaction data to a state indicating exit.

[0332] If the processor 401 cannot confirm that the read receipt barcode is valid during the exit check using the checkout gate 400, it will regard the read receipt barcode as invalid. Figure 13 In ACT429, it is determined to be "No" and the process proceeds to ACT428, and call processing is performed in the same manner as described above. Like this, for example, when reading the bill barcode related to the transaction processed using the POS terminal 300, the clerk is called instead of being directly allowed to pass.

[0333] Furthermore, if the processor 401 is notified by the POS server 700 that the customer has exited the store as described above, it determines "No" in ACT 431 and proceeds to ACT 428, where it performs a call processing in the same manner as described above. Thus, when the receipt barcode associated with the transaction confirming that the customer has exited the store is read, the store clerk is called instead of being allowed to pass directly.

[0334] Incidentally, when Figure 12 In the standby state from ACT 402 to ACT 404, when the customer CU passes through the checkout lane LA and is detected by the human detection sensor 409, the processor 401 determines "yes" in ACT 404 as passing and proceeds to ACT 414.

[0335] As ACT 414 , the processor 401 executes error pass processing.

[0336] On the other hand, when in Figure 14 When the customer CU passes through the checkout lane LA and is detected by the human sensing sensor 409 during the standby state from ACT 442 to ACT 444, the processor 401 determines "yes" in ACT 444 as passing and proceeds to ACT 447.

[0337] As ACT 447 , the processor 401 notifies the POS server 700 of the error pass.

[0338] As ACT 448 , the processor 401 executes error pass processing.

[0339] When the processor 401 is in Figure 14 When the processor 701 of the POS server 700 is in the standby state of ACT442 to ACT444, Figure 22 Therefore, when the processor 701 receives the notification of the above-mentioned erroneous passage, it determines "yes" in ACT 740 and ends the transaction search processing.

[0340] Figure 28 This is a flowchart of an erroneous pass process by the processor 401 in the checkout gate 400 and an alert process by the processor 601 of the monitoring terminal 600 .

[0341] In addition, whether as Figure 12 The execution of ACT414 is still as Figure 14 In the case of ACT448 execution, the error pass processing is Figure 28 in the order shown.

[0342] As ACT 471, the processor 401 initiates wrong-way notification. Wrong-way notification notifies the customer CU and other nearby persons that the customer CU has passed through the checkout lane LA, which is not permitted. The processor 401 causes the touch panel 404 to display, for example, a first warning screen to notify the wrong-way. The processor 401 causes the display unit 405 to display, for example, a second warning screen to notify the wrong-way. The processor 401 causes the warning light unit 410 to light up or flash red to notify the wrong-way. For example, the processor 401 causes the sound unit 411 to output a predetermined warning sound to notify the wrong-way. Alternatively, the processor 401 may perform other actions to notify the wrong-way, such as causing the sound unit 411 to output a predetermined voice message. However, the processor 401 may only perform some of these actions to notify the wrong-way.

[0343] Figure 29 This is a schematic diagram showing an example of the first warning screen.

[0344] The second warning screen is, for example, Figure 26 The same screen as the warning screen shown.

[0345] As Figure 28 In ACT 472, the processor 401 requests a warning from a predetermined request destination. In this embodiment, the monitoring terminal 600 is determined as the request destination for the warning. In addition, when the processor 601 in the monitoring terminal 600 receives the warning request from the checkout gate 400 as described above, it executes the monitoring program PRF. Figure 28 Warning handling shown.

[0346] As ACT 611, the processor 601 initiates a warning process. This process is used to warn the store clerk CL, who is responsible for monitoring using the monitoring terminal 600, about unauthorized passage through the checkout lane LA. For example, the processor 601 performs the warning process by causing the clerk-side touch panel 604 to display a warning screen to alert the store clerk CL to the presence of unauthorized passage. For example, the processor 601 performs the warning process by causing the audio unit 613 to output a predetermined warning sound. Alternatively, the processor 601 may perform other actions, such as causing the audio unit 613 to output a predetermined voice message. However, the processor 601 may only perform some of these actions to perform the warning process.

[0347] As ACT 612, processor 601 waits for the cancellation condition of the warning to be met. The cancellation condition can be appropriately determined by, for example, a person who specifies the specifications of the merchandise sales system 1 or an administrator of the monitoring terminal 600. The cancellation condition may be, for example, a cancellation instruction via a predetermined operation on the employee-side touch panel 604 or keyboard 605. Alternatively, the cancellation condition may be a case where the duration of the warning process exceeds a predetermined time. If the cancellation condition is met, processor 601 determines "yes" and proceeds to ACT 613.

[0348] The processor 601 stops the warning process as ACT 613. Then, the processor 601 ends the warning process.

[0349] Furthermore, in the checkout gate 400 , the processor 401 proceeds to ACT 473 after requesting a warning in ACT 472 .

[0350] As ACT 473, the processor 401 waits for the termination condition of the incorrect access notification to be met. The termination condition can be appropriately determined by, for example, the specifier of the merchandise sales system 1 or the manager of the checkout gate 400. For example, the termination condition is when the duration of the incorrect access notification exceeds a predetermined time. Alternatively, the termination condition is when the monitoring terminal 600 issues an instruction to terminate the warning process. In this case, when the termination is instructed in ACT 612, the processor 601 of the monitoring terminal 600 determines "yes" because the termination condition is met, and notifies the checkout gate 400 of the termination instruction before and after ACT 613. Alternatively, the termination condition is when a store clerk performs a predetermined termination operation at the checkout gate 400. Then, if the termination condition is met, the processor 401 determines "yes" and proceeds to ACT 474.

[0351] As ACT 474, the processor 401 stops the error pass notification. Then, the processor 401 ends the error pass processing and returns to Figure 12 ACT401 in.

[0352] As described above, in the product sales system 1 , if the product barcodes of one or more settled products are read again at the checkout gate 400 and a transaction settled for the product is locked, the customer is allowed to exit the store.

[0353] In this way, a customer CU who has completed the transaction but whose receipt barcode cannot be read by the checkout gate 400 can be guided to exit the store.

[0354] Furthermore, in the product sales system 1, transactions subject to lockout are limited to those settled within the most recent predetermined period. This improves the accuracy of locking out a transaction and reduces the burden on the customer CU by eliminating the need to read multiple product barcodes. Furthermore, the load on the processor 701 associated with the lockout process is reduced.

[0355] Furthermore, in the product sales system 1, for transactions where a customer CU's withdrawal can be confirmed, withdrawal data can be used to confirm that the customer CU has withdrawn, and the transaction can be excluded from the lockout process. This improves the accuracy of locking a transaction and eliminates the need for the customer CU to read multiple product barcodes, thereby reducing the burden on the customer CU. Furthermore, the load on the processor 701 associated with the lockout process can be reduced.

[0356] Furthermore, in the product sales system 1, if a transaction cannot be locked by comparing a predetermined number of transaction items, the system stops scanning the items and instead calls a contact person. Consequently, even when a large number of items are being traded and a transaction cannot be locked by comparing only a few of them, the customer CU does not need to repeatedly scan the product barcodes of multiple items, thereby reducing the burden on the customer CU.

[0357] This embodiment can be implemented in various modified forms as follows.

[0358] There is no need to exclude transactions that are subject to locking based on the settlement period or the withdrawal status of the customer CU.

[0359] There is no need to manage the withdrawal status of the customer CU for each transaction.

[0360] After obtaining multiple commodity codes, the transaction database DBA may be referenced to lock transactions that include these multiple transaction commodities as transaction commodities.

[0361] After obtaining the commodity codes of all transaction commodities, the transaction database DBA can be referenced to lock all transactions that are consistent with these transaction commodities.

[0362] The transaction database DBA can store the original or a copy in the auxiliary storage unit 403 of the checkout gate 400. In other words, in this case, the storage unit is located in the checkout gate 400, which serves as a gate device. Alternatively, the transaction database DBA can be stored in a storage device located in any information processing device separate from the checkout gate 400 and the POS server 700. Furthermore, the transaction database DBA can be stored in an independent storage device external to various information processing devices.

[0363] The information processing for locking transactions can be performed by processor 401 of checkout gate 400. In this case, transactions that have been settled within a predetermined period, starting from the time the product code (product identifier) ​​is acquired by the acquisition unit, are locked. Alternatively, this information processing can be performed by any information processing device separate from checkout gate 400 and POS server 700.

[0364] The information processing as the control unit may be performed by any information processing device other than the checkout gate 400 , such as the POS server 700 .

[0365] The checkout gate 400 may be configured as a device including a function as a checkout machine and a device including a function as a gate.

[0366] A structure may be included to selectively form the checkout lane LA into a physically blocked state and an unblocked state, and the opening and closing actions of the mechanism may be performed as one of the notifications.

[0367] The POS terminal 300 can be used to register the transaction goods, and the checkout gate 400 can be used to pay.

[0368] The customer CU can omit touching the standby screen before reading the handover code.

[0369] Figure 30 Schematic diagram showing a modified example of the gate control process.

[0370] in addition, Figure 30 Only the Figure 12 and Figure 13 Where there are changes in the gate control processing, the same processing is assigned the same figure mark.

[0371] After displaying the standby screen as ACT 401, the processor 401 transitions to Figure 30 In the standby state of ACT402 and ACT404, replace Figure 12 That is, as the standby state, the processor 401 waits for a barcode to be scanned or a person to pass by, but does not wait for a screen to be clicked.

[0372] The customer CU then points the reading window of the handheld scanner 407 toward the handover code without touching the screen of the touch panel 504. Alternatively, the customer CU causes the fixed scanner 406 or the handheld scanner 407 to read the receipt barcode or the product barcode. Accordingly, when the fixed scanner 406 or the handheld scanner 407 receives the barcode information, the processor 401 proceeds to ACT 481.

[0373] As ACT 481 , the processor 401 confirms whether the read barcode is a handover code. If the processor 401 can confirm that it is a handover code, it determines “yes” and executes ACT 407 and subsequent steps in the same manner as described above.

[0374] If the processor 401 cannot confirm that the read barcode is a handover code, it determines "No" in ACT 481 and proceeds to ACT 421. Then, the processor 401 executes ACT 421 and subsequent steps in the same manner as described above.

[0375] In addition, when the above-mentioned transformation is performed, it is preferable to also change the standby screen.

[0376] Figure 31 1 is a schematic diagram showing an example of a standby screen image applicable to this modification.

[0377] Figure 31 The idle screen shown includes character messages MEA and MEC. Figure 31 The standby screen shown is Figure 15 The standby screen shown displays a character message MEC instead of the character message MEB. The character message MEC guides the customer CU to read the transfer barcode so as to start the settlement of the registered transaction product using the information processing terminal 500.

[0378] In addition, Figure 31 In the illustrated standby screen, the central icon is also replaced with an icon that allows the customer CU to imagine the operation of reading the barcode.

[0379] The functions implemented by each processor through information processing can be partially or completely implemented by hardware such as logic circuits that do not perform information processing based on programs. In addition, the above functions can also be implemented by combining software control with hardware such as the above logic circuits.

[0380] While several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments may be implemented in various other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. These embodiments and their variations are intended to be within the scope and spirit of the invention, and are intended to be within the scope of the invention as set forth in the claims and their equivalents.

Claims

1. A checkout system, characterized in that: include: a storage unit for storing list data indicating a list of transaction commodities that are objects of transaction in the store, in correspondence with each settled transaction; an acquisition unit, which acquires a product identifier according to a customer's operation; a locking unit that locks a transaction by referring to the list data stored in the storage unit, the transaction including, as a transaction commodity, commodities identified by the one or more identifiers acquired by the acquisition unit; Notification department, notifying customers to allow passage; as well as The control unit controls the notification unit so as to perform notification in response to the fact that one transaction has been locked by the locking unit.

2. The checkout system according to claim 1, wherein: The locking unit targets transactions that have been settled within a predetermined period starting from when the commodity identifier was acquired by the acquiring unit.

3. The checkout system according to claim 1, wherein: The locking unit, when one transaction has been locked, excludes the corresponding transaction from subsequent locking targets.

4. The checkout system according to claim 1, wherein: Also includes: The processing unit performs processing for staff to take action when the locking unit cannot lock one transaction before a predetermined end condition is satisfied.

5. The checkout system according to claim 2, wherein: The locking object of the locking unit is a transaction that has been settled within a certain time period.

6. The checkout system according to claim 5, wherein: The period of the certain time width is the current day.

7. The checkout system according to claim 2, wherein: The predetermined period of the locking unit is a period during which a predetermined number of transactions have been performed.

8. The checkout system according to claim 1, wherein: The notification unit displays a guidance screen notifying the customer that passage is permitted.

9. The checkout system according to claim 1, wherein: The list data in the storage unit also includes a settlement method, The acquisition unit further acquires the settlement method based on the customer's operation. The locking unit locks the transaction including the product and the settlement method acquired by the acquiring unit from the list data in the storage unit.

10. A checkout system comprising a gate device and an information processing device provided facing a checkout passage through which customers exit a store, characterized in that: include: a storage unit provided in the information processing device and storing list data indicating a list of transaction commodities that are objects of transaction in the store, respectively corresponding to each settled transaction; an acquisition unit, provided in the gate device, and configured to acquire an identifier of a commodity in response to a customer's operation; a first notification unit, provided in the gate device, and configured to notify the information processing device of the identifier acquired by the acquisition unit; a locking unit provided in the information processing device and configured to lock a transaction by referring to the list data stored in the storage unit, the transaction including, as a transaction commodity, commodities identified by the one or more identifiers notified by the first notification unit; a second notification unit provided in the information processing device and configured to notify the gate device that a transaction has been locked by the locking unit when the transaction has been locked by the locking unit; a third notification unit, provided in the gate device, for notifying the customer of the fact that passage is permitted; as well as The control unit is provided in the gate device and controls the third notification unit so as to perform notification in response to the notification that a transaction has been locked by the second notification unit.

Images