Gate device, information processing program, and checkout system

Abstract

To provide a gate device, an information processing program and a checkout system that are able to properly guide customers who have completed a payment to leave a store.SOLUTION: According to an embodiment, a gate device comprises notification means, reading means, confirmation means, and a control means. The notification means performs notification that a customer is allowed to pass. The reading means reads an optically readable code. The confirmation means confirms whether settlement is completed on the basis of the code read by the reading means. The control means controls the notification means, in response to the code being read by the reading means, so as to provide notification upon the confirmation means confirming that the settlement is completed. The control means does not cause the notification means to provide notification when the settlement device, which has performed the settlement process relating to the transaction specified by the code read by the reading means, is not subject to exit control.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] Embodiments of the present invention relate to a gate device, an information processing program, and a checkout system.

Background Art

[0002] In a store that conducts transactions up to settlement for transactions such as the sale and purchase of goods, it is desirable to appropriately guide customers who have completed settlement to leave the store.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a gate device, an information processing program, and a checkout system that can appropriately guide a customer who has completed settlement to leave the store.

Means for Solving the Problems

[0005] The gate device according to the embodiment includes a notification unit, a reading unit, a confirmation unit, and a control unit. The notification unit notifies that it is permitted for a customer to pass through. The reading unit reads an optically readable code. The confirmation unit confirms whether settlement has been completed based on the code read by the reading unit. The control unit controls the notification unit to perform a notification when it is confirmed by the confirmation unit that settlement has been completed in response to the code being read by the reading unit. Further, when the settlement device that has performed processing for settlement regarding the transaction specified by the code read by the reading unit is not subject to exit control, the control unit does not cause the notification unit to perform a notification.

Brief Description of the Drawings

[0006] [Figure 1] A diagram illustrating the overall configuration of a product sales system according to one embodiment. [Figure 2] A schematic diagram showing an example layout of the checkout area in a store that has implemented a product sales system. [Figure 3] A block diagram showing the main circuit configuration of the transaction processing device in Figure 1. [Figure 4] A block diagram showing the main circuit configuration of the POS terminal in Figure 1. [Figure 5] A block diagram showing the main circuit configuration of the POS terminal in Figure 1. [Figure 6] A block diagram showing the main circuit configuration of the accounting gate in Figure 1. [Figure 7] A perspective view showing the exterior of the accounting gate in Figure 1. [Figure 8] A block diagram showing the main circuit configuration of the information processing terminal in Figure 1. [Figure 9] A block diagram showing the main circuit configuration of the monitoring terminal in Figure 1. [Figure 10] A block diagram showing the main circuit configuration of the POS server in Figure 1. [Figure 11] A sequence diagram showing the transaction processing using the information processing terminal in Figure 1. [Figure 12] A flowchart of the gate control process. [Figure 13] A flowchart of the gate control process. [Figure 14] A flowchart of the gate control process. [Figure 15] This screen shows an example of a standby screen displayed on the touch panel in Figure 6. [Figure 16] Figure 6 shows an example of a standby screen to be displayed on the display unit. [Figure 17] Flowchart for the process of allowing passage. [Figure 18] A diagram showing an example of the first guidance screen. [Figure 19] A diagram showing an example of the second guidance screen. [Figure 20]Sequence diagram related to the processing of transactions using the POS terminal in FIG. 1. [Figure 21] Sequence diagram related to the processing of transactions using the POS terminal in FIG. 1. [Figure 22] Flowchart of the transaction search process. [Figure 23] Diagram showing an example of an additional request screen. [Figure 24] Flowchart of the clerk calling process by the processor in FIG. 6 and the order issuing process by the processor in FIG. 9. [Figure 25] Diagram showing an example of a calling screen. [Figure 26] Diagram showing an example of a warning screen. [Figure 27] Flowchart of the exit confirmation process. [Figure 28] Flowchart of the mis-passing process by the processor in FIG. 6 and the alarm process by the processor in FIG. 9. [Figure 29] Diagram showing an example of the first warning screen. [Figure 30] Diagram showing a modified example of the gate control process. [Figure 31] Diagram showing an example of a standby screen adapted for modified implementation.

Mode for Carrying Out the Invention

[0007] Hereinafter, a merchandise sales system that performs processing related to the sale of merchandise to customers in a store will be described with reference to the drawings. The merchandise sales system is also an example of a transaction processing system that processes merchandise sales as target transactions. The transactions to be processed may be of a type different from merchandise sales, such as the provision of any service in a store. However, it is assumed that after the completion of the settlement for the transactions to be processed, the customer is allowed to leave the store.

[0008] FIG. 1 is an overall configuration diagram of the merchandise sales system 1 according to the present embodiment. The product sales system 1 includes a transaction processing device 100, POS (point-of-sale) terminals 200 and 300, an accounting gate 400, an information processing terminal 500, a monitoring terminal 600, and a POS server 700. The product sales system 1 is configured so that the transaction processing device 100, POS terminals 200, accounting gates 400, information processing terminals 500, monitoring terminals 600, and POS server 700 can communicate with each other via a communication network 2. The POS terminals 200 and accounting gates 400 can also 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 view an electronic receipt screen showing the details of transactions processed by the product sales system 1 on any information terminal.

[0009] In Figure 1, one each of the POS terminals 200, 300, 500, 600, and 700 are shown, and three accounting gates 400 are shown, but the number of each is arbitrary. One or two of the POS terminals 200, 300, and 500 may be provided, while the other two or one may not be provided. When the POS terminals 200, 300, and 500 are provided, in most cases multiple units are included in the product sales system 1.

[0010] Communication network 2 can use the Internet, VPN (virtual private network), LAN (local area network), public communication network, mobile communication network, etc., individually or in appropriate combinations. As an example, communication network 2 may be a combination of LAN, Internet, and mobile communication network. For communication between the transaction processing device 100, POS terminal 200, accounting gate 400, information processing terminal 500, monitoring terminal 600, and POS server 700, for example, LAN is used. For communication between the transaction processing device 100 and the information processing terminal 500, for example, LAN is used. However, the information processing terminal 500 is connected to communication network 2 via wireless access through access point 21 included in communication network 2. For communication between the POS terminal 200 or accounting gate 400 and the electronic receipt server 3, for example, LAN and Internet are used.

[0011] Figure 2 is a schematic diagram showing an example of the layout of the checkout counter in a store that has implemented product sales system 1. The information processing terminal 500 is temporarily operated by a customer CU shopping in the store. The information processing terminal 500 is attached to a shopping cart (hereinafter simply referred to as "cart") CA, for example. The information processing terminal 500 may also be carried by the customer CU. As the information processing terminal 500, existing portable information processing devices such as a tablet computer, smartphone, or smartwatch can be used. The information processing terminal 500 may be one provided by the store and temporarily used by the customer CU, or it may be one owned by the customer CU. The customer CU walks around the sales floor pushing the cart CA and places the items they intend to purchase directly onto the cart CA or into a basket placed on the cart CA. At this time, the customer CU operates the information processing terminal 500 to register the items placed on the cart CA as transaction items. The transaction processing device 100 registers the transaction items according to the operation on the information processing terminal 500. The information processing terminal 500 may also be operated by a store employee CL on behalf of the customer CU. Once a customer (CU) has selected all the items they wish to purchase, they proceed to the checkout counter and use the checkout gate 400 to complete the transaction. After this, the customer (CU) exits the store by passing through the checkout lane LA that the checkout gate 400 faces. As shown in Figure 2, if multiple checkout gates 400 are installed, each of these gates faces a different checkout lane LA. The checkout gate 400 also has an exit gate function to control the passage of customers (CU) through the checkout lane LA it faces, and is an example of a gate device. This exit gate function will be described later. After passing through the checkout lane LA, the customer (CU) bags their items at the packing table SU as needed. Thus, the product sales system 1 also serves as a checkout system for the store.

[0012] Alternatively, the customer (CU) can entrust the registration of the items they intend to purchase as transaction items to the store clerk (CL) who operates the POS terminal 200, without using the information processing terminal 500. The store clerk (CL) operates the POS terminal 200 to register the items brought in by the customer (CU) as transaction items and process the payment. In other words, the POS terminal 200 is a so-called face-to-face type. The operation of the POS terminal 200 may be the same as that of existing POS terminals of the same type. In Figure 2, the POS terminal 200 is an example of a separate type separated into a main unit 298 and a scanner unit 299. The POS terminal 200 may also be an integrated type or have other configurations. Furthermore, the POS terminal 200 may be a semi-self-service type consisting of a registration terminal operated by the store clerk (CL) and a payment terminal operated by the customer (CU). After completing payment at the POS terminal 200, the customer (CU) exits the store without passing through the checkout lane (LA).

[0013] Furthermore, customers can also register and pay for the items they intend to purchase by operating the POS terminal 300 themselves, without using the information processing terminal 500. In other words, the POS terminal 300 is a so-called fully self-service type. The operation of the POS terminal 300 may be the same as that of existing POS terminals of the same type. After completing payment at the POS terminal 300, customers exit the store by passing through the checkout lane LA. The monitoring terminal 600 assists the store clerk CL in monitoring fraudulent passage through checkout lane LA. The POS server 700 manages transactions processed by the merchandise sales system 1.

[0014] Figure 3 is a block diagram showing the main circuit configuration of the transaction processing device 100. 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, etc. The processor 101, the main storage unit 102, the auxiliary storage unit 103, and the communication unit 104 are able to communicate with each other via the transmission line 105.

[0015] By connecting the processor 101, the main storage unit 102, and the auxiliary storage unit 103 with a transmission line 105, a computer is configured to perform information processing for controlling the transaction processing device 100. The processor 101 corresponds to the central part of the computer described above. The processor 101 performs information processing to control each part in order to realize various functions as a transaction processing device 100, in accordance with information processing programs such as the operating system and application programs.

[0016] The main memory unit 102 corresponds to the main memory portion of the computer described above. The main memory unit 102 includes a read-only memory area and a rewritable memory area. The main memory unit 102 stores a portion of the information processing program described above in the read-only memory area. The main memory unit 102 may also store data necessary for the processor 101 to perform processing to control each part in the read-only memory area or the rewritable memory area. The main memory unit 102 uses the rewritable memory area as a work area for the processor 101.

[0017] The auxiliary storage unit 103 corresponds to the auxiliary storage portion of the computer described above. The auxiliary storage unit 103 can utilize, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk 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 processing performed by the processor 101. The auxiliary storage unit 103 may also store the information processing program described above. In this embodiment, the auxiliary storage unit 103 stores the transaction processing program PRA, which is one of the information processing programs. The transaction processing program PRA is an application program that describes the procedure for transaction processing, which will be described later. A portion of the storage area of ​​the auxiliary storage unit 103 is used as an area for storing transaction data DAA. Transaction data DAA is data that represents the content of a single transaction.

[0018] The communication unit 104 performs communication processing for data communication via the communication network 2. For example, an existing wired communication device for the internet can be used as the communication unit 104. Alternatively, a wireless communication device connected to the communication network 2 via wireless communication may be used as the communication unit 104, either in place of or in addition to the wired communication device. The transmission line 105 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected parts.

[0019] As the basic hardware for the transaction processing device 100, for example, a general-purpose server device can be used. Generally, the transfer of the transaction processing device 100 is carried out with the transaction processing program PRA stored in the auxiliary storage unit 103. However, the hardware and the transaction processing program PRA may be transferred separately, either without the transaction processing program PRA stored in the auxiliary storage unit 103, or with a different version of the same type of application program stored in the auxiliary storage unit 103. Furthermore, the transaction processing device 100 may be configured by writing the transaction processing program PRA to the auxiliary storage unit 103 in response to an operation by any operator. The transfer of the transaction processing program PRA can be carried out by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The transaction processing program PRA may also be stored in the main storage unit 102.

[0020] Figure 4 is a block diagram showing the main circuit configuration of the POS terminal 200. The POS terminal 200 includes a processor 201, a main memory unit 202, an auxiliary memory unit 203, a staff-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-facing display 212, a sound unit 213, a communication unit 214, and a transmission line 215. For example, the processor 201, main memory unit 202, auxiliary memory unit 203, staff-side touch panel 204, keyboard 205, change unit 209, receipt printer 210, and communication unit 214 are located in the main unit 298. For example, the fixed scanner 206, handheld scanner 207, payment terminal 208, customer-side touch panel 211, customer-facing display 212, and sound unit 213 are located in the scanner unit 299. However, some elements may be located in the opposite units. Furthermore, some elements, such as the clerk's touch panel and keyboard, may be provided on both the main unit 298 and the scanner unit 299.

[0021] The general functions of the processor 201, main memory unit 202, auxiliary memory unit 203, communication unit 214, and transmission line 215 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission line 105. However, the auxiliary storage unit 203 stores the 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 procedure for the processor 201 for transaction processing in response to operations performed by a store clerk on a device provided in the POS terminal 200.

[0022] The employee-side touch panel 204 is positioned facing the side where the employee CL is standing (hereinafter referred to as the employee side) when operating the POS terminal 200. The employee-side touch panel 204 displays a screen for presenting information to the employee CL. The employee-side touch panel 204 also receives instructions from the employee CL via touch operations on the screen. Keyboard 205 is equipped with numerous hard keys to facilitate operation by the store staff (CL). The keyboard 205 receives instructions from the CL by pressing these hard keys.

[0023] The fixed scanner 206 has a reading window facing the store clerk. The fixed scanner 206 captures an image of the product held in front of the reading window and then recognizes the barcode information represented by the barcode formed on the product through image processing. The fixed scanner 206 then outputs the barcode information to the processor 201. The fixed scanner 206 can also utilize other types of well-known devices that optically read barcodes using the reflection of laser light. Furthermore, the fixed scanner 206 can also utilize a type of well-known device that has the function of identifying products using object recognition technology from the image of the product itself obtained by capturing the product. The handheld scanner 207 is held in the hand of a store employee CL and optically reads the barcode placed opposite the reader. The handheld scanner 207 outputs the barcode information represented by the read barcode to the processor 201.

[0024] The payment terminal 208 reads data recorded on payment cards such as credit cards, prepaid cards, and electronic money cards. The payment terminal 208 also writes data to payment cards. The payment terminal 208 is equipped with reading devices corresponding to IC reading, magnetic reading, and proximity communication reading of credit cards. The IC reading device reads data stored in the integrated circuit (IC) on the credit card through communication via electrical contacts. The magnetic reading device reads data magnetically recorded on the magnetic stripe formed on the surface of the credit card using a magnetic head. Thus, both IC reading and magnetic reading involve contact between the payment terminal 208 and the credit card, and are examples of contact reading. The IC reading and magnetic reading devices are examples of contact reading devices. The proximity communication reading device reads data stored in the integrated circuit (IC) on the credit card through wireless communication such as NFC (near field communication). Thus, proximity communication reading is an example of contactless reading. Furthermore, a reading device for proximity communication is an example of a contactless reading device.

[0025] The change unit 209 counts the coins inserted through the coin slot and stores them in an internal storage compartment. The change unit 209 then discharges the coins stored in the storage compartment into a coin tray via a coin discharge port. The change unit 209 counts the banknotes inserted through the banknote slot and stores them in an internal storage compartment. The change unit 209 then discharges the banknotes stored in the storage compartment through a banknote discharge port. The banknote discharge port holds the discharged banknotes with a portion of them exposed to the outside.

[0026] The receipt printer 210 prints an image of a receipt, invoice, or sales slip onto receipt paper. The receipt printer 210 then ejects the receipt paper with the printed image from the receipt output slot. In the following, the receipt paper with the printed receipt image will be referred to as a paper receipt.

[0027] The customer-side touch panel 211 is positioned facing the customer's side (hereinafter referred to as the customer side) when the customer registers the transaction items through the store clerk's (CL) operation. The customer-side touch panel 211 displays a screen for presenting information to the customer. The customer-side touch panel 211 also receives input from the customer via touch operations on the screen.

[0028] The customer-facing display unit 212 is positioned facing the customer. The customer-facing display unit 212 displays a screen for presenting information to the customer CU. The customer-facing display unit 212 is primarily suited for displaying text and displays a simpler screen than the customer-facing touch panel 211. The sound unit 213 outputs sounds and voices for various announcements and warnings. Various well-known sound devices, such as a speech synthesis device and a buzzer, can be used as the sound unit, either individually or in combination.

[0029] As the basic hardware for the POS terminal 200, for example, the hardware of another existing POS terminal can be used. In this case, the transfer of the POS terminal 200 is generally carried out with the transaction processing program PRB stored in the auxiliary storage unit 203. However, the hardware of the POS terminal 200 and the transaction processing program PRB may be transferred separately, without the transaction processing program PRB stored in the auxiliary storage unit 203. The transaction processing program PRB may then be written to the auxiliary storage unit 203 in response to an operation by any worker. Alternatively, the hardware of the POS terminal 200 and the transaction processing program PRB may be transferred separately, with a different version of the same type of information processing program stored in the auxiliary storage unit 203. The transaction processing program PRB may then be written to replace the information processing program already stored in the auxiliary storage unit 203. The transfer of the transaction processing program PRB can be carried out by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The transaction processing program PRB may be stored in the main memory unit 202.

[0030] Figure 5 is a block diagram showing the main circuit configuration of the POS terminal 300. The POS terminal 300 includes a processor 301, a main memory unit 302, an auxiliary memory unit 303, a touch panel 304, a keyboard 305, a fixed scanner 306, a handheld scanner 307, a payment terminal 308, a change dispenser 309, a receipt printer 310, a sound unit 311, a communication unit 312, and a transmission line 313.

[0031] The general functions of the processor 301, main memory unit 302, auxiliary memory unit 303, communication unit 312, and transmission line 313 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission line 105. However, the auxiliary storage unit 303 stores the 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 procedure for the processor 301 for transaction processing in response to customer operations on the device provided in the POS terminal 300.

[0032] The touch panel 304 is positioned facing the customer service center (CU) who is operating the POS terminal 300. The touch panel 304 displays a screen for presenting information to the customer service center. The touch panel 304 also receives input from the customer service center through touch operations on the screen. The general functions of the keyboard 305, fixed scanner 306, handheld scanner 307, payment terminal 308, change unit 309, receipt printer 310, and sound unit 311 are equivalent to those of the keyboard 205, fixed scanner 206, handheld scanner 207, payment terminal 208, change unit 209, receipt printer 210, and sound unit 213. However, the keyboard 305, fixed scanner 306, handheld scanner 307, and payment terminal 308 are provided for easy operation by the customer control unit (CU) and are primarily operated by the customer CU.

[0033] As the basic hardware for the POS terminal 300, for example, the hardware of another existing fully self-service POS terminal can be used. In this case, the transfer of the POS terminal 300 is generally performed with the transaction processing program PRC stored in the auxiliary storage unit 303. However, the hardware of the POS terminal 300 and the transaction processing program PRC may be transferred separately, without the transaction processing program PRC stored in the auxiliary storage unit 303. The transaction processing program PRC may then be written to the auxiliary storage unit 303 in response to an operation by any worker. Alternatively, the hardware of the POS terminal 300 and the transaction processing program PRC may be transferred separately, with a different version of the same type of information processing program stored in the auxiliary storage unit 303. The transaction processing program PRC may then be written to replace the information processing program already stored in the auxiliary storage unit 303. The transfer of the transaction processing program PRC can be performed by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The transaction processing program PRC may be stored in the main storage unit 302.

[0034] Figure 6 is a block diagram showing the main circuit configuration of the accounting gate 400. The accounting gate 400 includes a processor 401, a main memory unit 402, an auxiliary memory unit 403, a touch panel 404, a display unit 405, a fixed scanner 406, a handheld scanner 407, a receipt printer 408, a human presence sensor 409, a lamp unit 410, a sound unit 411, a communication unit 412, and a transmission line 413.

[0035] The general functions of the processor 401, main memory unit 402, auxiliary memory unit 403, communication unit 412, and transmission line 413 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission line 105. However, the auxiliary storage unit 403 stores the gate control program PRD instead of the transaction processing program PRA. The gate control program PRD is an application program that describes the information processing procedure of the processor 401 for the gate control processing described later. The auxiliary storage unit 403 also stores the rejection list data DAB. The rejection list data DAB represents a list of POS terminals predetermined to be rejected. Which of the POS terminals 200 and 300 is to be rejected can be appropriately determined by any setter, such as the administrator of the product sales system 1. In this embodiment, POS terminal 200 is to be rejected.

[0036] The touch panel 404 displays a screen for providing information to the operator performing the checkout process. The touch panel 404 also accepts input from the operator via touch gestures on the screen. Typically, the operator of the checkout gate 400 is the customer (CU). However, in some cases, a store employee (CL) may operate the checkout gate 400.

[0037] The display unit 405 displays a screen for providing information to customers CU who are about to pass through the checkout lane LA facing the accounting gate 400 on which the display unit 405 is installed. In the following description of the accounting gate 400, when "checkout lane LA" is simply referred to, it refers to the checkout lane LA facing the accounting gate 400 in question.

[0038] The fixed scanner 406 has a reading window. The fixed scanner 406 recognizes the barcode information represented by the barcode held in front of the reading window through image processing. The fixed scanner 406 then outputs the barcode information to the processor 401. The fixed scanner 406 can also utilize other types of well-known devices that optically read barcodes using the reflection of laser light. Furthermore, the fixed scanner 406 can also utilize a type of well-known device that has the function of identifying products using object recognition technology from images of the products themselves obtained by imaging the products.

[0039] The handheld scanner 407 is used by the customer CU, holding it in their hand, and optically reads the barcode placed opposite the reader. The handheld scanner 407 outputs the barcode information represented by the read barcode to the processor 401. The receipt printer 408 prints an image of a receipt, invoice, or sales slip onto receipt paper. The receipt printer 408 then ejects the printed receipt paper from the receipt output slot. In short, the receipt printer 408 is used to issue paper receipts.

[0040] The motion sensor 409 detects customers CU passing through the checkout lane LA. As the motion sensor 409, any well-known detection device such as a light sensor or an infrared sensor can be used as appropriate. In other words, the motion sensor 409 is an example of the first detection means. The ramp unit 410 indicates whether it is permissible for a customer CU to pass through the checkout lane LA.

[0041] The sound unit 411 outputs sounds and voices for various announcements and warnings regarding the passage of a customer CU through the checkout lane LA. As the sound unit, various well-known sound devices such as a speech synthesis device and a buzzer can be used individually or in combination.

[0042] The transfer of the accounting gate 400 is generally performed with the gate control program PRD stored in the auxiliary storage unit 403. However, the hardware and the gate control program PRD may be transferred separately, either without the gate control program PRD stored in the auxiliary storage unit 403, or with a different version of the same application program stored in the auxiliary storage unit 403. The accounting gate 400 may also be configured by writing the gate control program PRD to the auxiliary storage unit 403 in response to an operation by any worker. The transfer of the gate control program PRD can be performed by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The gate control program PRD may also be stored in the main storage unit 402.

[0043] Figure 7 is a perspective view showing the exterior of the accounting gate 400. In Figure 7, elements identical to those shown in Figure 6 are given the same reference numerals. Furthermore, in the following explanation of Figure 7, the left and right sides of Figure 7 are referred to as the front and rear, respectively. The checkout gate 400 has a housing 450 that is roughly rectangular in shape. The checkout gate 400 is installed with one side 451 of the housing 450 facing the checkout lane LA in order to control the movement of the customer CU in the direction of movement represented by the arrow AR via the checkout lane LA. The side of the housing 450 that is in the direction of movement of the customer CU will be referred to below as the front 452.

[0044] The enclosure 450 holds the fixed scanner 406 in a position to read barcodes held over it from the front 452 side. The enclosure 450 holds the display unit 405 near the end of the top surface 453 opposite to the front 452, in a position that makes the display surface easily visible to customers CU passing through the checkout lane LA. The enclosure 450 holds the receipt printer 408 below the fixed scanner 406, in a position that ejects receipts towards the front 452 side.

[0045] The touch panel 404 is mounted above the fixed scanner 406 in a position that allows the display surface to be easily seen by the customer CU facing the front panel 452. The handheld scanner 407 is connected via a cable to a transmission line 413 located inside the housing 450 and can be pulled out to the front of the front panel 452 for use. In Figure 7, the handheld scanner 407 is shown in a state where it is set in a folder. The human presence sensor 409 is located inside the housing 450 to detect customer CUs passing through the checkout lane LA via a slit 454 formed on the side panel 451. The lamp unit 410 is mounted on the tip of a pole 460 erected on the top surface 453 of the housing 450. Note that the processor 401, main memory unit 402, auxiliary memory unit 403, sound unit 411, and communication unit 412 shown in Figure 6 are located inside the enclosure 450.

[0046] Figure 8 is a block diagram showing the main circuit configuration of the information processing terminal 500. The information processing terminal 500 includes a processor 501, a main memory unit 502, an auxiliary memory unit 503, a touch panel 504, a sound unit 505, an interface unit 506, a wireless communication unit 507, and a transmission line 508, among other things.

[0047] The general functions of the processor 501, main memory unit 502, auxiliary memory unit 503, and transmission line 508 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission line 105. However, the auxiliary storage unit 503 stores the terminal program PRE instead of the transaction processing program PRA. The terminal program PRE is an application program that describes the information processing procedure of the processor 501 to enable the information processing terminal 500 to function as a user interface for registering trading products on the transaction processing device 100.

[0048] The touch panel 504 displays a screen for presenting information to the operator. The touch panel 504 also accepts input from the operator via touch gestures on the screen. The operator of the information processing terminal 500 is usually a customer (CU). However, a store employee (CL) may also operate the information processing terminal 500. The sound unit 505 outputs sounds and voices for various announcements and alarms. Various well-known sound devices, such as speech synthesis devices and buzzers, can be used as the sound unit, either individually or in combination.

[0049] The interface unit 506 is connected to external devices such as the barcode scanner 599. The interface unit 506 interfaces with the connected external devices for data exchange. Existing USB (universal serial bus) controllers 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 recognizes the barcode information represented by the barcode held in front of the reading window through image processing. The barcode scanner 599 then outputs the barcode information. Note that the barcode scanner 599 can also use other types of well-known devices that optically read barcodes using the reflection of laser light. Alternatively, the barcode scanner 599 can use a well-known type of device that has the function of identifying products using object recognition technology from images of the products themselves obtained by imaging the products. In place of, or in addition to, the camera provided on the information processing terminal 500 may be used to read barcodes.

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

[0051] The basic hardware of the information processing terminal 500 is expected to be, for example, the hardware of a tablet-type information processing device. Generally, the transfer of the information processing terminal 500 is carried out with the terminal program PRE stored in the auxiliary storage unit 503. However, the hardware and the terminal program PRE may be transferred separately, either without the terminal program PRE stored in the auxiliary storage unit 503, or with a different version of the same type of application program stored in the auxiliary storage unit 503. The information processing terminal 500 may also be configured by writing the terminal program PRE to the auxiliary storage unit 503 in response to an operation by any worker. The transfer of the terminal program PRE can be carried out by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The terminal program PRE may also be stored in the main storage unit 502.

[0052] Figure 9 is a block diagram showing the main circuit configuration of the monitoring terminal 600. The monitoring terminal 600 includes a processor 601, a main memory unit 602, an auxiliary memory unit 603, a touch panel 604 for the store clerk, a keyboard 605, a fixed scanner 606, a handheld scanner 607, a payment terminal 608, a change dispenser 609, a receipt printer 610, a touch panel 611 for the customer, a customer display 612, a sound unit 613, a communication unit 614, and a transmission line 615.

[0053] The general functions of the processor 601, main memory unit 602, auxiliary memory unit 603, sound unit 613, communication unit 614, and transmission line 615 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission line 105. Furthermore, the functions of the employee-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-facing display 612, and sound unit 613 are equivalent to those of the employee-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-facing display 212, and sound unit 213. In other words, the monitoring terminal 600 has the same hardware configuration as the POS terminal 200.

[0054] However, the auxiliary storage unit 603 stores the monitoring program PRF in addition to the transaction processing program PRB. The monitoring program PRF is an application program that describes the information processing procedures to assist the store clerk CL in monitoring fraudulent passage through the checkout lane LA. Thus, the monitoring terminal 600 is a device that adds monitoring support functions to the POS terminal 200. However, the monitoring terminal 600 can also be configured without transaction processing functions. In this case, the basic hardware of the monitoring terminal 600 can be various types of general-purpose computer devices, such as desktop, book-type, or tablet-type computers.

[0055] The transfer of the monitoring terminal 600 is generally carried out with the transaction processing program PRB and the monitoring program PRF stored in the auxiliary storage unit 603. However, the hardware in which at least one of the transaction processing program PRB and the monitoring program PRF is not stored in the auxiliary storage unit 403, or in which a different version of the same type of application program is stored in the auxiliary storage unit 603, may be transferred separately from the transaction processing program PRB and the monitoring program PRF. Furthermore, the monitoring terminal 600 may be configured by writing the transaction processing program PRB and the monitoring program PRF to the auxiliary storage unit 603 in response to the operation of any operator. The transfer of the transaction processing program PRB and the monitoring program PRF can be carried out by recording them on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The transaction processing program PRB and the monitoring program PRF may also be stored in the main storage unit 402.

[0056] Figure 10 is a block diagram showing the main circuit configuration of the POS server 700. 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. The general functions of the processor 701, main memory unit 702, auxiliary memory unit 703, communication unit 704, and transmission line 705 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission line 105.

[0057] However, the auxiliary storage unit 703 stores the transaction management program PRG instead of the transaction processing program PRA. The transaction management program PRG is an application program that describes the procedures for information processing by the processor 701 for managing transactions processed by the product sales system 1. In addition, a portion of the storage area of ​​the auxiliary storage unit 703 is used to store the transaction database DBA. The transaction database DBA is a database that aggregates transaction data representing the details of settled transactions for each transaction.

[0058] The basic hardware of the POS server 700 can be, for example, a general-purpose server device. Generally, the POS server 700 is transferred with the transaction management program PRG stored in the auxiliary storage unit 703. However, the hardware and the transaction management program PRG may be transferred separately, either without the transaction management program PRG stored in the auxiliary storage unit 703, or with a different version of the same application program stored in the auxiliary storage unit 703. Furthermore, the POS server 700 may be configured by writing the transaction management program PRG to the auxiliary storage unit 703 in response to an operation by any worker. The transaction management program PRG can be transferred by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network. The transaction management program PRG may also be stored in the main storage unit 702.

[0059] Next, the operation of the product sales system 1 configured as described above will be explained. Note that the content of the various processes described below is merely an example, and it is possible to change the order of some processes, omit some processes, or add other processes as appropriate. For example, in the following explanation, some processes have been omitted in order to clearly illustrate the characteristic operation of this embodiment. For example, if an error occurs, processing to deal with that error may be performed, but such processing has been omitted from the description.

[0060] Figure 11 is a sequence diagram showing the process of handling transactions using the information processing terminal 500. In the transaction processing device 100 and the information processing terminal 500, processors 101 and 501 perform registration processing as ACT101 and user interface processing as ACT501 in coordination. As a result, processor 101 uses the information processing terminal 500 as a user interface terminal to receive instructions from the customer CU, registering the products that the customer CU intends to purchase as transaction products, and generating transaction data representing a list of transaction products. The registration process involves, for example, having the information processing terminal 500 read the barcode of the product that the customer CU intends to purchase, or the customer CU operating a pre-configured preset key to specify a product displayed on the information processing terminal 500, thereby adding the specified product as a transaction product.

[0061] When the customer CU performs a predetermined operation on the information processing terminal 500 to specify the start of payment, the processor 501 on the information processing terminal 500 proceeds to ACT 502. As ACT502, processor 501 notifies transaction processing unit 100 that accounting commencement has been designated.

[0062] When the transaction processing unit 100 receives notification of the accounting commencement designation, the processor 101 proceeds to ACT 102. As ACT102, processor 101 instructs information processing terminal 500 to display the handover screen.

[0063] When the processor 501 in the information processing terminal 500 is instructed to display the handover screen, it proceeds to ACT 503. As ACT503, the processor 501 displays a handover screen on the touch panel 504. The handover screen is a screen for transferring the functions of the information processing terminal 500 as a user interface terminal for transactions being processed to the accounting gate 400. The handover screen includes, for example, a two-dimensional code (hereinafter referred to as the handover code) that represents handover data for the accounting gate 400 to request accounting data based on transaction data from the transaction processing device 100.

[0064] Meanwhile, at the accounting gate 400, when the processor 401 is in an operating state that allows use by the customer CU, it executes gate control processing according to the gate control program PRD. Figures 12, 13, and 14 are flowcharts of the gate control process. As ACT401, processor 401 displays a standby screen on touch panel 404 and display unit 405. The standby screen is a screen that guides the customer CU on what operations to perform when it is waiting for an operation from the customer CU.

[0065] Figure 15 shows an example of a standby screen displayed on the touch panel 404. Note that the standby screen and the various screens described later illustrate the main display objects, and the illustration of some display objects may be omitted. For example, the screen may include images to help the user visualize the operations they should perform. The content of the various screens may be determined as appropriate by, for example, the person who determined the specifications for product sales system 1.

[0066] The standby screen shown in Figure 15 includes text messages MEA and MEB. Text message MEA guides a customer CU who has completed payment for a transaction and is about to leave the store to scan one of the product barcodes or receipt barcodes of the transaction items. Text message MEB guides the customer CU to touch the screen of the touch panel 404 in order to start payment for the transaction items registered using the information processing terminal 500. A product barcode is a barcode displayed on a product that includes barcode information containing a product code as an identifier for that product. A receipt barcode is a barcode displayed on a receipt that includes barcode information containing a transaction code as an identifier for the transaction. Typically, one-dimensional barcodes are used as product barcodes and receipt barcodes. However, other types of optically readable codes, such as two-dimensional codes, may also be used as product barcodes and receipt barcodes.

[0067] Figure 16 shows an example of a standby screen to be displayed on the display unit 405. The waiting screen shown in Figure 16 is a screen that guides a customer (CU) who has completed payment for a transaction and is about to leave the store to scan the barcode of one of the items in the transaction.

[0068] In Figure 12, processor 401, as ACT402, checks whether the barcode has been scanned. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT403. As ACT403, processor 401 checks if the touch panel 404 screen has been tapped. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT404. As ACT404, processor 401 checks whether a person has passed through checkout lane LA. If processor 401 cannot confirm the event, it determines NO and returns to ACT402. Note that "checkout lane LA" here and in the following explanation refers to checkout lane LA that the accounting gate 400 being described faces. Thus, processor 401, as ACT402~ACT404, awaits barcode scanning, screen taps, or the passage of a person.

[0069] As described above, a customer CU using an information processing terminal 500 that displays the handover screen on the touch panel 504 will, if multiple accounting gates 400 are installed, arbitrarily select one of the accounting gates 400 that is displaying the standby screen and touch the screen of the touch panel 504 on that accounting gate 400. When the touch panel 504 detects the tap, the processor 401 determines YES in ACT 403 and proceeds to ACT 405.

[0070] As ACT405, processor 401 displays a handover guidance screen on touch panel 404 and display unit 405. The handover guidance screen is a screen that guides the customer CU to have the handheld scanner 407 read the handover code included in the handover screen displayed on touch panel 504 using the information processing terminal 500, as described above. As ACT406, processor 401 waits for the takeover code to be scanned.

[0071] As described above, the customer CU touches the screen of the touch panel 504, and then positions the reading port of the handheld scanner 407 opposite the transfer code. The handheld scanner 407 then reads the transfer code and outputs the barcode information represented by the transfer code to the processor 401. In response, the processor 401 determines YES in ACT 406 and proceeds to ACT 407. The transfer code may also be read by the fixed scanner 406. In other words, for example, the information processing terminal 500 may be detachable from the cart CA, or if a portable information processing device is used as the information processing terminal 500, the touch panel 504 of the information processing terminal 500 may be positioned opposite the fixed scanner 406. The transfer guidance screen should preferably guide the customer CU through the expected method of reading the transfer code.

[0072] As ACT407, processor 401 acquires accounting data based on the handover data represented by the barcode information output from handheld scanner 407. In other words, as shown in Figure 11, processor 401 requests accounting data from transaction processing device 100. In the transaction processing unit 100, when the processor 101 receives a request for accounting data from the accounting gate 400, it proceeds to ACT 103.

[0073] As ACT103, processor 101 sends predetermined accounting data for accounting and settlement of the payment corresponding to the transaction details represented by the transaction data to the requesting accounting gate 400. Thereupon, at accounting gate 400, processor 401 takes in the accounting data sent in this manner and received by communication unit 412 as ACT407.

[0074] Once processor 401 has obtained the accounting data in this manner, it proceeds to ACT408 in Figure 12. As ACT408, processor 401 performs accounting processing based on the acquired accounting data. That is, processor 401 performs accounting processing to determine the settlement amount for the relevant transaction based on the acquired accounting data. This accounting processing may be similar to the processing performed by the accounting machines of existing semi-self-service POS systems. Then, processor 401 performs settlement processing to settle the settlement amount determined as described above. One example of settlement processing is that it is assumed to be performed using electronic money provided independently by the company operating the store. In this case, the customer CU identifier is acquired when the information processing terminal 500 is started to be used, and settlement is performed using the electronic money balance associated with this identifier. However, various payment methods such as credit card payment, code payment, prepaid payment, point payment, gift certificate payment, or cash payment may be available as appropriate for settlement at the accounting gate 400. Furthermore, electronic money payment provided by a payment service provider other than the company operating the store may be available for settlement at the accounting gate 400. Depending on the payment method available, additional devices not shown in Figure 6 may be required for payment processing using that method.

[0075] As ACT409, processor 401 checks whether an electronic receipt should be applied. If the customer CU identifier has been obtained as described above, processor 401 checks whether the setting to apply an electronic receipt has been set in advance for the customer CU identified by this identifier. Alternatively, processor 401 may have the customer CU specify whether or not to apply an electronic receipt and then check whether an electronic receipt should be applied according to that specification. If it cannot be confirmed that an electronic receipt should be applied, processor 401 determines NO and proceeds to ACT410.

[0076] As ACT410, processor 401 issues a paper receipt that shows the transaction details, accounting results, and a receipt barcode. In other words, processor 401 generates a receipt image that shows the transaction details, accounting results, and a payment completion code, and causes receipt printer 408 to print this receipt image. As a result, receipt printer 408 prints the receipt image onto receipt paper, and a paper receipt is issued.

[0077] On the other hand, if processor 401 confirms that an electronic receipt should be applied, it determines YES in ACT409 and proceeds to ACT411. As ACT411, processor 401 registers an electronic receipt containing the transaction details, accounting results, and receipt barcode with the electronic receipt server 3. In other words, processor 401 sends predetermined request data to the electronic receipt server 3 to request registration of the electronic receipt, along with notification of the transaction details, accounting results, and payment completion code. Upon receiving this request data, electronic receipt server 3 makes the electronic receipt screen, which displays the notified transaction details, accounting results, and receipt barcode, viewable from any information terminal.

[0078] After completing either ACT410 or ACT411, processor 401 proceeds to ACT412 in either case. As ACT412, processor 401 notifies transaction processing unit 100 of the result of the accounting process. In response to this notification, processor 101 in transaction processing unit 100 proceeds to ACT104 in Figure 11.

[0079] As ACT104, processor 401 sends transaction data related to the transaction being processed to POS server 700. This transaction data may be the same as transaction data in existing POS systems. In other words, the transaction data may include transaction headers, item data, combined discount data, customer data, closing data, and credit data. The item data represents a list of the products being traded. The data to be included in the transaction data may be determined as appropriate by, for example, the person who determined the specifications of the product sales system 1. However, the transaction data should at least be capable of determining what products were traded in the transaction in question. Processor 401 also includes exit data, which represents the customer CU's exit status from the store, as a status indicating that the customer has not yet exited, in the transaction data.

[0080] Upon receiving the above transaction data, processor 701 in POS server 700 proceeds to ACT701. As ACT701, processor 701 updates the transaction database DBA to include the above transaction data.

[0081] Now, at the accounting gate 400, the processor 401 notifies the accounting result as ACT412 in Figure 12, and then proceeds to ACT413. As ACT413, processor 401 performs pass-through acceptance processing. Figure 17 is a flowchart of the pass-through permission process. As ACT451, processor 401 initiates a pass-through permission notification. The pass-through permission notification is a notification to inform the customer CU and people in the surrounding area that they are permitted to pass through checkout lane LA. For example, processor 401 illuminates lamp unit 410 in blue for the pass-through permission notification. For example, processor 401 outputs an audio message such as "Please pass through the gate" to sound unit 411 for the pass-through permission notification. Alternatively, processor 401 may perform other actions for the pass-through permission notification, such as outputting a predetermined notification sound to sound unit 411. However, processor 401 may perform only some of these actions for the pass-through permission notification.

[0082] In addition to the above, the processor 401 displays, for example, a first guidance screen on the touch panel 404 when notifying passage is permitted. In addition to the above, the processor 401 displays, for example, a second guidance screen on the display unit 405 when notifying passage is permitted. Figure 18 shows an example of the first guidance screen. The first guidance screen shown in Figure 18 includes a text message indicating that the customer is permitted to pass through checkout lane LA because payment has been completed.

[0083] Figure 19 shows an example of the second guidance screen. The second guidance screen shown in Figure 19 includes a text message indicating that there is a time limit for passing through checkout lane LA, and a number representing the remaining time for passing through checkout lane LA. The second guidance screen shown in Figure 19 is an example where the remaining time is 10 seconds, and the number "10" represents that remaining time. With respect to the second guidance screen, the processor 401 updates the number representing the remaining time each time the remaining time changes. This second information screen allows customers to see the remaining time they are allowed to pass through the checkout lane (LA). Based on this screen, customers can then decide whether they should hurry through or not.

[0084] The various displays and sound outputs exemplified here are all examples of how to notify a customer CU that they are permitted to pass through the checkout lane LA. Thus, the touch panel 404, display unit 405, lamp unit 410, and sound unit 411 are examples of notification means.

[0085] Processor 401 proceeds to ACT452 while issuing a pass-through permission notification. As ACT452, processor 401 checks if a human has passed through checkout lane LA. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT453. As ACT453, processor 401 checks whether a predetermined allowable time has elapsed since the start of the pass-through permission notification as ACT451. If processor 401 cannot confirm the relevant event, it determines NO and returns to ACT452. Thus, processor 401 waits for a human to pass or for an allowable time to elapse, as ACT452 and ACT453.

[0086] If the customer CU passes through the checkout lane before the allowable time has elapsed, and the human presence sensor 409 detects the passage of a person, the processor 401 determines YES in ACT452 and proceeds to ACT454. As ACT454, processor 401 requests the POS server 700 to update the exit data. Upon receiving this request, the POS server 700 prompts processor 701 to proceed to ACT702 in Figure 11. Alternatively, this request to update the exit data may be made by processor 601 to the POS server 700 after receiving notification of the exit from processor 401. In Figure 11, processor 701, designated as ACT702, updates the exit data included in the transaction data that ACT701 has included in the transaction database DBA to indicate that it has been exited.

[0087] At the checkout gate 400, after the processor 401 has finished issuing the notification in ACT454 in Figure 17, it proceeds to ACT455. If the processor 401 has not been able to confirm that the customer CU has passed through the checkout lane LA and the allowable time has elapsed, it will determine YES in ACT453, skip ACT454, and proceed to ACT455. For example, even after completing the checkout, a customer CU may return to the sales floor without passing through the checkout lane LA, and in such a case, the processor 401 will determine YES in ACT453. As ACT455, processor 401 stops the pass-through permission notification. With this, processor 401 terminates the pass-through permission process and returns to ACT401 in Figure 12 to prepare for the next customer CU.

[0088] Figure 20 is a sequence diagram showing the process of processing a transaction using the POS terminal 200. In the POS terminal 200, when the processor 201 receives a notification to start registration through a predetermined operation by the store clerk CL, it proceeds to ACT201. As ACT201, processor 201 registers the items that customer CU intends to purchase as transaction items according to the operations of store clerk CL using various devices of POS terminal 200, and generates transaction data representing a list of transaction items. Then, when the store clerk CL declares that the registration is complete, processor 201 proceeds to ACT202.

[0089] As ACT202, processor 201 performs accounting processing for the accounting and settlement of payments according to the transaction details represented by the transaction data generated by ACT201. In other words, processor 201 performs accounting processing to determine the settlement amount for the relevant transaction based on the generated transaction data. Then, processor 201 performs settlement processing to settle the settlement amount determined as described above. Various payment methods such as credit card payments, code payments, prepaid payments, point payments, gift certificate payments, or cash payments may be used as appropriate for the settlement processing. The above registration and accounting processes may be similar to those performed by existing face-to-face POS terminals. Thus, the POS terminal 200 is equipped with the functionality of a payment device.

[0090] As ACT203, processor 201 checks whether an electronic receipt should be applied. If the customer CU identifier has been obtained during the registration or accounting process described above, processor 201 checks whether the setting to apply an electronic receipt has been made in advance for the customer CU identified by this identifier. Alternatively, processor 201 may have the customer CU or store clerk CL specify whether or not to apply an electronic receipt, and then check whether an electronic receipt should be applied according to that specification. If it cannot be confirmed that an electronic receipt should be applied, processor 201 determines NO and proceeds to ACT204.

[0091] As ACT204, processor 201 issues a paper receipt that shows the transaction details, accounting results, etc., along with a receipt barcode. In other words, processor 201 generates a receipt image that shows the transaction details and accounting results, etc., and has receipt printer 210 print this receipt image. As a result, receipt printer 210 prints the receipt image onto receipt paper, and a paper receipt is issued.

[0092] On the other hand, if processor 201 confirms that an electronic receipt should be applied, it determines YES in ACT203 and proceeds to ACT205. As ACT205, processor 201 registers an electronic receipt containing the transaction details, accounting results, and receipt barcode with the electronic receipt server 3. In other words, processor 201 sends predetermined request data to the electronic receipt server 3 to request registration of the electronic receipt, along with notification of the transaction details and accounting results. Upon receiving this request data, the electronic receipt server 3 makes the electronic receipt screen, which displays the notified transaction details, accounting results, and receipt barcode, viewable from any information terminal.

[0093] After completing either ACT204 or ACT205, processor 201 proceeds to ACT206 in either case. As ACT206, processor 201 sends transaction data related to the transaction processed in this instance to POS server 700. This transaction data may be the same as transaction data in existing POS systems. In other words, the transaction data may include transaction headers, item data, combined discount data, customer data, closing data, and credit data. The item data represents a list of the traded products. The data to be included in the transaction data may be determined as appropriate by, for example, the person who determined the specifications of the product sales system 1. However, the transaction data should at least be data that allows for the determination of what products were traded in the relevant transaction. In this embodiment, customer CUs for transactions processed by POS terminal 200 are excluded from exit control by the accounting gate 400 and are operated independently of the accounting gate 400. For this reason, processor 201 does not include exit data in the transaction data. In other words, existing face-to-face POS terminals may be used as POS terminal 200.

[0094] Upon receiving the above transaction data, processor 701 in POS server 700 proceeds to ACT711. As ACT711, processor 701 updates the transaction database DBA to include the above transaction data.

[0095] Figure 21 is a sequence diagram showing the process of processing a transaction using the POS terminal 300. In the POS terminal 300, when the processor 301 receives a notification to start registration through a predetermined operation by the customer CU, it proceeds to ACT301. As ACT301, the processor 301 registers the products that the customer CU intends to purchase as transaction items according to the customer CU's operations using various devices of the POS terminal 300, and generates transaction data representing a list of transaction items. For example, the processor 301 registers a product as a transaction item when the customer CU has the barcode of the product read by the fixed scanner 306 or handheld scanner 307, or when the product is displayed on the touch panel 304, or when the customer CU operates a preset key included in the keyboard 305 to which the product is pre-associated. Then, when the customer CU declares that the registration is complete, the processor 301 proceeds to ACT302.

[0096] As ACT302, processor 301 performs accounting processing for the accounting and settlement of payments according to the transaction details represented by the transaction data generated by ACT301. In other words, processor 301 performs accounting processing to determine the settlement amount for the relevant transaction based on the generated transaction data. Then, processor 301 performs settlement processing to settle the settlement amount determined as described above. Various payment methods such as credit card payments, code payments, prepaid payments, point payments, gift certificate payments, or cash payments may be used as appropriate for the settlement processing. The registration and accounting processes described above may be similar to those performed by existing fully self-service POS terminals. Thus, the POS terminal 200 is equipped with the functionality of a payment device.

[0097] As ACT303, processor 301 checks whether an electronic receipt should be applied. If the customer CU identifier has been obtained during the registration or accounting process described above, processor 301 checks whether the setting to apply an electronic receipt has been set in advance for the customer CU identified by this identifier. Alternatively, processor 301 may have the customer CU specify whether or not to apply an electronic receipt and then check whether an electronic receipt should be applied according to that specification. If processor 301 cannot confirm that an electronic receipt should be applied, it determines NO and proceeds to ACT304.

[0098] As ACT304, processor 301 issues a paper receipt that shows the transaction details, accounting results, and a receipt barcode. In other words, processor 301 generates a receipt image that shows the transaction details, accounting results, and a receipt barcode, and has receipt printer 310 print this receipt image. As a result, receipt printer 310 prints the receipt image onto receipt paper, and a paper receipt is issued.

[0099] On the other hand, if processor 301 confirms that an electronic receipt should be applied, it determines YES in ACT 303 and proceeds to ACT 305. As ACT305, processor 301 registers an electronic receipt containing the transaction details, accounting results, and receipt barcode with the electronic receipt server 3. In other words, processor 301 sends predetermined request data to the electronic receipt server 3 to request registration of the electronic receipt, along with notification of the transaction details, accounting results, and receipt barcode. Upon receiving this request data, electronic receipt server 3 makes the electronic receipt screen, which displays the notified transaction details, accounting results, and receipt barcode, viewable from any information terminal.

[0100] After completing either ACT304 or ACT305, processor 301 proceeds to ACT306 in either case. As ACT306, processor 301 sends transaction data related to the transaction processed in this instance to POS server 700. This transaction data may be the same as transaction data in existing POS systems. In other words, the transaction data may include transaction header, item data, combined discount data, customer data, closing data, and credit data. The item data represents a list of the traded items. The data to be included in the transaction data may be determined as appropriate by, for example, the person who determined the specifications of the product sales system 1. However, the transaction data should at least be data that allows for the determination of what products were traded in the relevant transaction. In this embodiment, customer CUs for transactions processed at POS terminal 300 are subject to exit control by the accounting gate 400. For this reason, processor 301 includes exit data in the transaction data indicating that the customer has not yet exited.

[0101] Upon receiving the above transaction data, processor 701 in POS server 700 proceeds to ACT721. As ACT721, processor 701 updates the transaction database DBA to include the above transaction data.

[0102] As mentioned above, if a customer CU has completed payment at checkout gate 400 but has not passed through checkout lane LA within the allowed time, and wishes to leave the store without making any additional purchases, they will have the receipt barcode displayed on the paper receipt or electronic receipt screen issued at checkout gate 400 read by a fixed scanner 406 or handheld scanner 407 at any checkout gate 400 that is in standby mode. In other words, the fixed scanner 406 and handheld scanner 407 are examples of reading means that read receipt barcodes, which are an example of optically readable codes.

[0103] Customer CU who has completed payment at POS terminal 300 has the receipt barcode displayed on the paper receipt or electronic receipt screen issued by POS terminal 300 read by the fixed scanner 406 or handheld scanner 407 of any checkout gate 400 that is in standby mode. Furthermore, in cases where it is difficult to have the receipt barcode read by the fixed scanner 406 or handheld scanner 407 due to various circumstances, such as losing the paper receipt issued by the accounting gate 400 or POS terminal 300, or being unable to display the electronic receipt screen because the customer does not have a smartphone, the customer CU can also use the exit confirmation function by matching the transaction items. When using this function, the customer CU has the fixed scanner 406 or handheld scanner 407 read the barcode of one of the transaction items that has been paid for.

[0104] When the fixed scanner 406 or the handheld scanner 407 reads a barcode, it notifies the processor 401 of the barcode information it represents. The processor 401 then determines YES at ACT402 in Figure 12 and proceeds to ACT421 in Figure 13.

[0105] As ACT421, processor 401 checks if the scanned barcode is a product barcode. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT422. As ACT422, processor 401 checks if the scanned barcode is a receipt barcode. If processor 401 cannot confirm the event, it determines NO and returns to the standby state of ACT402~ACT404 in Figure 5. At this time, processor 401 may perform guidance actions such as displaying a screen prompt to guide the customer CU to scan a product barcode or receipt barcode.

[0106] If the product barcode has been read as described above, processor 401 determines YES in ACT421 and proceeds to ACT423. As ACT423, processor 401 reads the product barcode and, along with notifying the POS server 700 of the product code contained in the barcode information obtained, queries the POS server 700 for the transaction.

[0107] When the processor 701 on the POS server 700 receives a transaction inquiry as described above, it executes information processing based on the transaction management program PRG (hereinafter referred to as transaction search processing). Figure 22 is a flowchart of the transaction search process. In the following description of the transaction search process, "accounting gate 400" refers to the accounting gate 400 that initiated the above query.

[0108] As ACT731, processor 701 searches past transactions that have been settled for which the product identified by the product code notified during the query is included as the transaction product. For example, processor 701 first searches the transaction data contained in the transaction database DBA, • Regarding transactions conducted within a predetermined search period. • Products identified by the notified product code will be included as trading products. • Includes exit data indicating that the user has not yet left. Extract transaction data that matches the specified conditions.

[0109] The search period is expected to be a fixed time range, such as the most recent 10 minutes. The duration of this search period may be determined as appropriate by the person who decided on the specifications for product sales system 1, or the store manager. For example, the search period could be the current day. Alternatively, the search could target a predetermined number of recent transactions. In this case, the search period would be the period during which that number of transactions occurred. For example, the number of recent transactions is expected to be 20, but this number may be determined as appropriate by the person who decided on the specifications for product sales system 1, or the store manager.

[0110] As ACT732, processor 701 checks whether the matching transaction was found through the above search. If, for example, ACT731 did not extract any transaction data that matched the conditions, processor 701 determines NO, stating that there are no matching transactions, and proceeds to ACT733.

[0111] As ACT733, processor 701 notifies accounting gate 400 of an error in response to the transaction query. In other words, if processor 701 finds no transactions that match the above conditions, it determines it is an error and notifies accounting gate 400 of this. Processor 701 then terminates the transaction search process.

[0112] If processor 701 can extract at least one transaction data that matches the conditions in ACT731, it will determine that there is a relevant transaction in ACT732 and proceed to ACT734. Processor 701, as ACT734, checks whether multiple transactions were found through the above search. If, for example, ACT731 extracted only one transaction data that matches the criteria, Processor 701 determines that there are not multiple transactions and verifies NO, then proceeds to ACT735.

[0113] As ACT735, processor 701 notifies accounting gate 400 of permission in response to the transaction inquiry. In other words, if processor 701 has narrowed down the transaction to one based on the above conditions, it decides to grant permission and notifies accounting gate 400 of this. Then processor 701 terminates the transaction search process.

[0114] If, for example, there are multiple transaction data points extracted in ACT731, processor 701 determines YES in ACT734 and proceeds to ACT736. As ACT736, processor 701 checks whether the termination condition for filtering has been met. The termination condition may be determined as appropriate by the person who determined the specifications for product sales system 1, or the store manager, etc. Specific examples of termination conditions will be described later. If processor 701 cannot confirm the relevant event, it determines NO and proceeds to ACT737. As ACT737, processor 701 requests notification of another product from accounting gate 400.

[0115] At the accounting gate 400, the processor 401 queries for the transaction as ACT423 in Figure 13, and then proceeds to ACT424. As ACT424, processor 401 checks if a notification for a different product has been requested. If processor 401 cannot confirm the relevant event, it determines NO and proceeds to ACT425. As ACT425, processor 401 checks whether a permission notification has been issued. In other words, processor 401 determines whether or not it will receive a permission notification from processor 701. If processor 401 cannot confirm the relevant event, it determines NO and proceeds to ACT426. As ACT426, processor 401 checks if an error notification has been issued. If processor 401 cannot confirm the relevant event, it determines NO and returns to ACT424. Thus, processor 401 waits for either a notification request, permission notification, or error notification to be made as ACT424~ACT426. When processor 401 receives a notification for another product from POS server 700 as described above, it determines YES in ACT424 and proceeds to ACT441 in Figure 14.

[0116] As ACT441, processor 401 displays an additional request screen on touch panel 404. The additional request screen requests customer CU to scan a product barcode of a different transaction item than those previously scanned using the fixed scanner 406 or handheld scanner 407.

[0117] Figure 23 shows an example of an additional request screen. The additional request screen shown in Figure 23 is a screen that displays a window WIA overlaid on the waiting screen. The window WIA displays the text message for the above request, as well as a button BUA. The button BUA is a soft key that the customer CU uses to declare that there are no other products available.

[0118] If customer CU has other items to be traded that have not yet had their product codes scanned, they have one of those items' product barcodes scanned by the fixed scanner 406 or the handheld scanner 407. Alternatively, if the customer has already scanned the product barcodes for all items to be traded, they declare that they have no items by performing a predetermined operation, such as tapping button BUA.

[0119] After the processor 401 displays the additional request screen as ACT441 in Figure 14, it proceeds to ACT442. As ACT442, processor 401 checks if the product barcode has been scanned. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT443. As ACT443, processor 401 checks if "no goods" has been declared. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT444. As ACT444, processor 401 checks whether the customer CU has passed through checkout lane LA. If processor 401 cannot confirm the event, it determines NO and returns to ACT442. Thus, processor 401 awaits the occurrence of either a product barcode scan, a declaration of no products, or a pass-through as ACT442~ACT444.

[0120] 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. As ACT445, processor 401 requests filtering from POS server 700, along with notification of the product code contained in the barcode information obtained by the fixed scanner 406 or handheld scanner 407 after reading the product barcode. After this, processor 401 returns to the waiting state of ACT424~ACT426 in Figure 13.

[0121] Furthermore, when the processor 401 detects, for example, an operation to declare no goods on the touch panel 404, it determines YES in ACT 443 and proceeds to ACT 446. As ACT446, processor 401 notifies POS server 700 that there are no products available. After this, processor 401 returns to the waiting state of ACT424~ACT426 in Figure 13.

[0122] At the POS server 700, the processor 701 requests notification of another product as ACT737 in Figure 22, and then proceeds to ACT738. As ACT738, processor 701 checks if a refinement request was made. If processor 701 cannot confirm the relevant event, it determines NO and proceeds to ACT739.

[0123] As ACT739, processor 701 checks if a notification of "no product available" has been received. If processor 701 cannot confirm the event, it determines NO and proceeds to ACT740. As ACT740, processor 701 checks if a mispass has been reported. If processor 701 cannot confirm the event, it determines NO and returns to ACT738.

[0124] Thus, processor 701 waits for either a filtering request, a notification of no products, or a notification of incorrect processing to be made in ACT738-ACT740. If filtering is requested as described above, processor 701 determines YES in ACT78 and proceeds to ACT741.

[0125] As ACT741, processor 701 narrows down the multiple transactions found in the search of ACT731 to those that include both the product identified by the product code notified at the time of the query and the product identified by the product code notified at the time of the refinement request as trading products. After this, processor 701 repeats ACT734 and subsequent steps as described above. Thus, if processor 701 is unable to narrow down to a single transaction in ACT741, it repeats the refinement in ACT741 while receiving further refinement requests accompanied by notification of other product codes. When processor 701 executes ACT741 for the second time or later, it narrows down to transactions that include both the product identified by the product code notified at the time of the query and the multiple products identified by the product codes notified in the previous refinement requests as trading products.

[0126] Now, the termination condition that processor 701 checks in ACT736 is expected to be defined as, for example, when the number of products used to narrow down the transactions reaches a specified number. If processor 701 cannot narrow down to a single transaction even if the termination condition is met, it will determine YES in ACT736 and proceed to ACT742. In other words, if there are multiple transactions that similarly include the specified number of products as trading products, processor 701 will proceed to ACT742.

[0127] As ACT742, processor 701 notifies accounting gate 400 of an error in response to the transaction query. In other words, if processor 701 cannot narrow down to a single transaction even if the termination conditions are met, it determines it is an error and notifies accounting gate 400 of this. Processor 701 then terminates the transaction search process.

[0128] If processor 701 is notified that there are no products, as described above, it determines YES in ACT739 and proceeds to ACT743. As ACT743, processor 701 narrows down the multiple transactions that have been narrowed down so far to those where the number of transactions matches the number of trading products used in the previous filtering. The number of transactions is represented, for example, in the transaction header included in the transaction data.

[0129] As ACT744, processor 701 checks if multiple transactions were found through the above filtering. If it has narrowed it down to one transaction, processor 701 determines that there are no multiple transactions and proceeds to ACT745. As ACT745, processor 701 notifies accounting gate 400 of permission in response to the transaction inquiry. In other words, if processor 701 has narrowed down to a single transaction through the filtering in ACT743, it decides to grant permission and notifies accounting gate 400 of this. With this, processor 701 terminates the transaction search process.

[0130] If processor 701 finds multiple transactions through the above filtering process, it determines YES in ACT744 and proceeds to ACT746. As ACT746, processor 701 notifies accounting gate 400 of an error in response to the transaction query. In other words, if another transaction involving the exact same trading instrument as the transaction targeted by the current query occurred during the search period, processor 701 determines it is an error and notifies accounting gate 400 of this. Processor 701 then terminates the transaction search process.

[0131] At the accounting gate 400, when the processor 401 receives the authorization notification from the POS server 700 in ACT735 or ACT745 as described above, it determines YES in ACT425 in Figure 13 and proceeds to ACT427. As ACT427, processor 401 performs the pass-through acceptance process, similar to ACT413 in Figure 12. Once processor 401 has completed the pass-through acceptance process, it returns to ACT401 in Figure 12.

[0132] As mentioned above, when processor 401 receives an error notification from POS server 700 in ACT733, ACT742, or ACT746 in Figure 22, it determines YES in ACT426 in Figure 13 and proceeds to ACT428. As ACT428, processor 401 executes a call process. The call process involves calling the person responsible for handling errors at the accounting gate 400 (hereinafter referred to as the person in charge) and receiving a response from that person in charge.

[0133] Figure 24 is a flowchart showing the call processing by processor 401 at accounting gate 400 and the order issuance processing by processor 601 at monitoring terminal 600. As ACT461, processor 401 initiates a calling notification. The calling notification is a notification to the customer CU that an employee is being called. For the purpose of the calling notification, processor 401 may, for example, display a calling screen on touch panel 404. For the purpose of the calling notification, processor 401 may, for example, display a warning screen on display unit 405. For the purpose of the calling notification, processor 401 may, for example, light up or blink lamp unit 410 in yellow. For the purpose of the calling notification, processor 401 may, for example, output a predetermined notification sound to sound unit 411. Alternatively, processor 401 may perform other operations for the purpose of the calling notification, for example, output a predetermined voice message to sound unit 411. However, processor 401 may perform only some of these operations for the purpose of the pass-through permission notification.

[0134] Figure 25 shows an example of a calling screen. The calling screen shown in Figure 25 is a screen in which a window WIB is overlaid on the waiting screen. The window WIB displays the text message for the guidance mentioned above. Figure 26 shows an example of a warning screen. The warning screen shown in Figure 26 is a screen designed to warn customer service personnel (CUs) to prevent them from accidentally leaving the premises.

[0135] In Figure 24, the processor 401, as ACT462, requests the issuance of an order to a predetermined recipient. In this embodiment, the monitoring terminal 600 is designated as the recipient of the order request. The monitoring terminal 600 is installed, for example, at the service counter of a store. The monitoring terminal 600 performs transaction processing operations in the same manner as existing POS terminals of the same type. This allows the monitoring terminal 600 to be used to assist when the POS terminal 200 is congested. The monitoring terminal 600 can also be used to respond to various requests from customer service representatives, such as returns.

[0136] Now, when the processor 601 at the monitoring terminal 600 receives the order issuance request from the accounting gate 400 as described above, it executes the order issuance process shown in Figure 24 according to the monitoring program PRF. As ACT601, the processor 601 initiates the issuance operation. The issuance operation is an operation to issue a command to the person in charge of monitoring using the monitoring terminal 600 to deal with an error at the accounting gate 400. As part of the issuance operation, the processor 601 displays a command screen on the employee's touch panel 604 instructing them to deal with the error at the accounting gate 400 so that it can recognize which accounting gate 400 the command was requested from. As part of the issuance operation, the processor 601 outputs a predetermined command sound to the sound unit 613. Alternatively, the processor 601 may perform another operation as part of the issuance operation, such as outputting a predetermined voice message to the sound unit 613. However, the processor 601 may perform only a part of these operations as part of the issuance operation.

[0137] At accounting gate 400, processor 401 requests an order in ACT462, and then proceeds to ACT463. As ACT463, processor 401 awaits the commencement of operations by the responsible party.

[0138] The person in charge goes to the accounting gate 400 in response to the command issued by the monitoring terminal 600 and performs the predetermined operations that the person in charge is required to perform. Upon confirmation that these operations have been performed, the processor 401 determines YES in ACT463 and proceeds to ACT464. As ACT464, processor 401 performs an authentication process to confirm that the operator is responsible. This authentication may be a well-known process for operator authentication. If the authentication is successful, processor 401 proceeds to ACT465.

[0139] As ACT465, processor 401 performs transaction confirmation processing to allow the person in charge to confirm that the settlement of the transaction of the customer CU currently using the accounting gate 400 has been completed. In this transaction confirmation processing, processor 401 displays, for example, a transaction confirmation screen showing the details of the settled transaction on touch panel 404. Then, processor 401 receives, for example, a designation from the person in charge as to which of the settled transactions the current transaction of the customer CU in question belongs to.

[0140] As ACT466, processor 401 stops calling notifications. As ACT467, processor 401 notifies monitoring terminal 600 that the process is complete. With this, processor 401 terminates the current call processing and proceeds to ACT427 in Figure 13, where it performs the pass-through permission processing as described above.

[0141] At monitoring terminal 600, processor 601 begins issuing commands as ACT601, and then proceeds to ACT602. As ACT602, processor 601 waits for completion notification. Then, as described above, when completion is notified from accounting gate 400, processor 601 determines it to be YES and proceeds to ACT603. As ACT603, processor 601 stops the issuance operation. With this, processor 601 terminates the current issuance process.

[0142] At the checkout gate 400, if the barcode read while the standby screen is displayed is a receipt barcode, the processor 401 determines YES at ACT422 in Figure 13 and proceeds to ACT429. As ACT429, processor 401 verifies whether the read receipt barcode is valid for exit check using the checkout gate 400. Processor 401 checks whether the receipt barcode meets predetermined conditions and determines that it is valid if it does. The above conditions are assumed to be, for example, that the receipt barcode in question is a receipt barcode relating to a transaction processed by a device that is not a POS terminal included in the rejection list data DAB and is installed in the same store where the checkout gate 400 is installed. However, these conditions may be determined as appropriate by the person who determined the specifications of the product sales system 1 or the store manager. For example, only one of the above two conditions may be used. Alternatively, other conditions may be added, such as that the elapsed time since the completion of settlement of the transaction relating to the receipt barcode is less than a specified time. If processor 401 can determine that it is valid, it proceeds to ACT430 as YES. In this embodiment, the processor 401 proceeds to ACT 430 when it reads a receipt code relating to a transaction for which settlement processing has been performed at the POS terminal 300, the accounting gate 400, or the monitoring terminal 600. After completing payment, the customer CU can have the receipt barcode read by a fixed scanner 406 or a handheld scanner 407. In other words, confirming that the read receipt barcode relates to a transaction settled by a device installed in the same store where the checkout gate 400 is installed is equivalent to confirming that payment has been completed. Thus, by having the processor 401 perform information processing based on the gate control program PRD, the computer with the processor 401 as its central component functions as a verification means.

[0143] As ACT430, processor 401 queries POS server 700 for the customer CU's exit status, along with notification of the transaction code contained in the barcode information represented by the read receipt barcode. When the processor 701 on the POS server 700 receives an inquiry about the exit status as described above, it executes information processing based on the transaction management program PRG (hereinafter referred to as the exit confirmation process).

[0144] Figure 27 is a flowchart of the exit confirmation process. As ACT751, processor 701 checks whether the customer CU for the transaction identified by the notified transaction code has not left the store. For example, processor 701 searches the transaction database DBA for transaction data related to the transaction identified by the notified transaction code and checks whether the exit data included in the relevant transaction data indicates that the customer has not left. If the relevant exit data indicates that the customer has not left, processor 701 determines YES, that the customer CU has not left the store, and proceeds to ACT752. As ACT752, processor 701 notifies the originating accounting gate 400 that the user has not yet exited, in response to the inquiry about the exit status.

[0145] Furthermore, if the corresponding exit data does not indicate that the customer has not left the store, processor 701 determines NO, and proceeds to ACT753. As ACT753, processor 701 notifies the originating accounting gate 400 that the user has exited, in response to the inquiry about the exit status. Then, once the processor 701 has finished sending notifications via ACT752 or ACT753, it terminates the current exit confirmation process.

[0146] At the accounting gate 400, the processor 401 queries as ACT430 in Figure 13, and then proceeds to ACT431. As ACT431, processor 401 checks if it has been notified that the user has not exited. If processor 401 has been notified by POS server 700 that the user has not exited, as described above, it determines the result to YES and proceeds to ACT427, where it performs the pass-through permission process as described above. Thus, if the processor 401 determines YES in ACT431 and proceeds to ACT427, the processor 401 will perform control to notify if it can confirm that the payment has been completed based on the receipt barcode, which is an example of a code, that has been read. In this way, the computer with the processor 401 as its central component functions as a control means by the processor 401 executing information processing based on the gate control program PRD.

[0147] Now, if processor 401 determines YES in ACT431 as described above and proceeds to ACT427, when it requests an update of the exit data in ACT454 in Figure 17, it notifies the transaction code contained in the barcode information represented by the read receipt barcode. Upon receiving such a request, processor 701 of POS server 700 proceeds, for example, to ACT722 in Figure 21. As ACT722, processor 701 retrieves the transaction data identified by the notified transaction code from the transaction database DBA and updates the exit data contained in the relevant transaction data to indicate that it has been exited.

[0148] If the processor 401 cannot confirm that the read receipt barcode is valid for exit check using the checkout gate 400, it determines that the read receipt barcode is invalid, and determines NO at ACT429 in Figure 13, proceeding to ACT428 to execute the call process as described above. Thus, for example, if a receipt barcode related to a transaction processed by the POS terminal 300 is read, the system will not allow the customer to pass through, but will instead call a store employee. As a result, depending on the function of the processor 401 as a control means, if the settlement device that performed the settlement processing for the transaction identified by the read code is not subject to exit control, no notification is sent. Thus, the rejection list data DAB is an example of list data representing a list of POS terminals 200 as settlement devices that are not subject to exit control. The auxiliary storage unit 403 is an example of a storage means.

[0149] Furthermore, if processor 401 receives notification from POS server 700 that the customer has already left the store, as described above, it determines NO in ACT431 and proceeds to ACT428 to execute the call process as described above. Thus, if a receipt barcode related to a transaction in which the customer has been confirmed to have left the store is read, the system will not allow the customer to pass through but will instead call a store employee.

[0150] Incidentally, when processor 401 is in the standby state of ACT402~ACT404 in Figure 12, if a customer CU passes through checkout lane LA and this is detected by the human presence sensor 409, it determines that the customer has passed through and processes it to ACT404, and proceeds to ACT414. As ACT414, processor 401 performs error handling.

[0151] On the other hand, when processor 401 is in the standby state of ACT442 to ACT444 in Figure 14, if a customer CU passes through checkout lane LA and this is detected by the motion sensor 409, it determines that the customer has passed through and proceeds to ACT444, where it returns YES. As ACT447, processor 401 notifies POS server 700 of the incorrect pass-through. As ACT448, processor 401 performs error handling.

[0152] At the POS server 700, when processor 401 is in the waiting state for ACT442 to ACT444 in Figure 14, processor 701 is in the waiting state for ACT738 to ACT740 in Figure 22. Therefore, when processor 701 receives the notification of the above-mentioned erroneous transaction, it determines YES at ACT740 and terminates the transaction search process.

[0153] Figure 28 is a flowchart showing the error handling process performed by the processor 401 at the accounting gate 400 and the alarm handling process performed by the processor 601 at the monitoring terminal 600. The error handling procedure is the same as shown in Figure 28, whether executed as ACT414 in Figure 12 or as ACT448 in Figure 14.

[0154] As ACT471, processor 401 initiates an incorrect passage notification. An incorrect passage notification is a notification to the customer CU and other people nearby that the customer CU has passed through a checkout lane LA that is not permitted. For the purpose of an incorrect passage notification, processor 401 may, for example, display a first warning screen on the touch panel 404. For the purpose of an incorrect passage notification, processor 401 may, for example, display a second warning screen on the display unit 405. For the purpose of an incorrect passage notification, processor 401 may, for example, light up or flash the lamp unit 410 in red. For the purpose of an incorrect passage notification, processor 401 may, for example, output a predetermined alarm sound to the sound unit 411. Alternatively, processor 401 may perform other actions for the purpose of an incorrect passage notification, for example, outputting a predetermined voice message to the sound unit 411. However, processor 401 may perform only some of these actions for the purpose of an incorrect passage notification. Figure 29 shows an example of the first warning screen. The second warning screen is similar to the warning screen shown in Figure 26, for example.

[0155] In Figure 28, the processor 401, as ACT472, requests an alarm to a predetermined recipient. In this embodiment, the monitoring terminal 600 is designated as the recipient of the alarm request. When the processor 601 at the monitoring terminal 600 receives the alarm request from the accounting gate 400 as described above, it executes the alarm processing shown in Figure 28 according to the monitoring program PRF.

[0156] Processor 601, as ACT611, initiates alarm processing. Alarm processing is the process of issuing an alarm to the store employee CL, who is responsible for monitoring using the monitoring terminal 600, regarding unauthorized passage through the checkout lane LA. For alarm processing, processor 601 displays an alarm screen on the store employee's touch panel 604 to make the store employee CL aware that unauthorized passage has occurred. For alarm processing, processor 601 outputs a predetermined alarm sound to the sound unit 613. Alternatively, processor 601 may perform other operations for alarm processing, such as outputting a predetermined voice message to the sound unit 613. However, processor 601 may perform only some of these operations for alarm processing.

[0157] As ACT612, processor 601 waits for the alarm release condition to be met. The release condition may be determined as appropriate by, for example, the person who determined the specifications of the product sales system 1 or the administrator of the monitoring terminal 600. The release condition is expected to be, for example, when the release is instructed by a predetermined operation on the store clerk's touch panel 604 or keyboard 605. Alternatively, the release condition is expected to be when the duration of the alarm processing exceeds a predetermined time. Then, if the release condition is met, processor 601 determines YES and proceeds to ACT613. As ACT613, processor 601 stops the alarm processing. With this, processor 601 terminates the current alarm processing.

[0158] Now, at the accounting gate 400, after the processor 401 requests an alarm in ACT472, it proceeds to ACT473. As ACT473, processor 401 waits for the termination condition for the erroneous passage notification to be met. The termination condition may be determined as appropriate by, for example, the person who determined the specifications of the product sales system 1 or the manager of the accounting gate 400. The termination condition is expected to be, for example, when the duration of the erroneous passage notification exceeds a predetermined time. Alternatively, the release condition is expected to be when an instruction to release the alarm processing is given at the monitoring terminal 600. In this case, at the monitoring terminal 600, processor 601 will determine YES in ACT612 if a release instruction has been given, and will notify the accounting gate 400 that a release instruction has been given before or after ACT613. Alternatively, the termination condition is expected to be when a predetermined release operation is performed by a store employee at the accounting gate 400. Then, if the termination condition is met, processor 401 will determine YES and proceed to ACT474. As ACT474, processor 401 stops the erroneous pass notification. With this, processor 401 terminates the erroneous pass processing and returns to ACT401 in Figure 12.

[0159] As described above, the checkout gate 400 excludes customer CUs (Customer Users) from exit control for transactions processed by the POS terminal 200. Furthermore, even if a customer CU scans the receipt barcode related to a transaction settled at the POS terminal 200, the checkout gate 400 will not allow them to pass through the checkout lane LA. This allows the checkout gate 400 to appropriately guide customers who have completed payment at the POS terminal 200 and left the store, or another customer CU who has obtained a receipt discarded by such a customer, to re-enter the store and use the receipt code related to the aforementioned transaction to exit through the checkout lane LA.

[0160] Furthermore, the accounting gate 400 determines whether a POS terminal included in the list represented by the rejection list data DAB is subject to exit control. This eliminates the need for each POS terminal to generate a receipt barcode that can determine whether it is subject to exit control, and allows existing barcodes to be used as is.

[0161] Furthermore, the checkout gate 400 is configured to allow customers to confirm transactions in the checkout lane LA that have been verified as having resulted in their exit. Even if a customer scans a receipt barcode related to a transaction for which their exit from the store has already been confirmed, the gate will not allow them to pass through the checkout lane LA. This allows the checkout gate 400 to appropriately guide customers to prevent them from using receipt barcodes that were legitimately used to exit through the checkout lane LA, or receipt barcodes displayed on receipts that have been discarded by such customers.

[0162] This embodiment can be modified in various ways as follows: The determination of whether a payment device that settled a transaction related to a scanned receipt barcode is exempt from exit control may be made by an alternative method, such as those shown below, instead of using the rejection list data DAB. For example, data indicating whether or not it is exempt from exit control may be included in the barcode data represented by the receipt barcode, and this data may be referenced. Alternatively, for example, the code system of the receipt barcode or the transaction number system may be made different for transactions subject to exit control and those not subject to it, and the system of which is being used may be confirmed.

[0163] Confirmation of whether payment has been completed can be done, for example, by the accounting gate 400 querying the POS server 700 to confirm whether payment has been completed for the transaction identified by the transaction code contained in the scanned barcode. The processor 701 on the POS server 700 then refers to the transaction database DBA to perform this check. In this case, the computer with the processor 701 as its central component functions as the confirmation means. However, this confirmation function may also be implemented by a computer in any information processing device separate from the POS server 700.

[0164] The accounting gate 400 may be configured with separate components: one for the accounting machine function and another for the gate function.

[0165] Alternatively, the system may be equipped with a mechanism that can selectively create states where the checkout lane LA is physically blocked and states where it is not blocked, and the opening and closing operation of this mechanism may be performed as one of the notifications.

[0166] Alternatively, the POS terminal 300 can be used to register the transaction items, while the accounting is performed at the accounting gate 400.

[0167] The customer CU can omit touching the waiting screen before scanning the transfer code. Figure 30 shows a modified example of the gate control process. Note that Figure 30 shows only the changes from Figures 12 and 13 in the gate control process, and the same reference numerals are used for identical processes. After displaying the standby screen as ACT401, processor 401 transitions to the standby states of ACT402 and ACT404 in Figure 30, instead of the standby states of ACT402 to ACT404 in Figure 12. In other words, in this standby state, processor 401 waits for barcode scanning or human passage, but does not wait for screen taps. The customer CU then points the reading port of the handheld scanner 407 towards the transfer code without touching the screen of the touch panel 504. Alternatively, the customer CU has the fixed scanner 406 or handheld scanner 407 read the receipt barcode or product barcode. Once barcode information is received from the fixed scanner 406 or handheld scanner 407, the processor 401 proceeds to ACT 481. As ACT481, processor 401 checks if the read barcode is a handover code. If processor 401 confirms that it is a handover code, it determines YES and executes ACT407 and subsequent steps as described above. If processor 401 cannot confirm that the read barcode is a transfer code, it determines NO in ACT481 and proceeds to ACT421. Then processor 401 executes ACT421 and subsequent steps in the same manner as described above. Furthermore, when implementing such modifications, it is preferable to also change the standby screen. Figure 31 shows an example of a waiting screen adapted to this modification. The standby screen shown in Figure 31 includes text messages MEA and MEC. In other words, the standby screen shown in Figure 31 represents text message MEC instead of text message MEB in the standby screen shown in Figure 15. Text message MEC informs the customer CU that in order to start settlement of the transaction product registered using the information processing terminal 500, they should have the handover barcode read. Furthermore, the standby screen shown in Figure 31 has been modified so that the central illustration also represents the customer's operation of scanning a barcode.

[0168] Each function realized by each processor through information processing can also be partially or entirely realized by hardware that performs non-program-based information processing, such as logic circuits. Furthermore, each of the above functions can also be realized by combining the aforementioned hardware, such as logic circuits, with software control.

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

[0170] 1...Product sales system, 2...Communication network, 3...Electronic receipt server, 100...Transaction processing device, 200, 300...POS terminal, 400...Checkout gate, 500...Information processing terminal, 600...Monitoring terminal, 700...POS server, 101, 201, 301, 401, 501, 601, 701...Processor, 102, 202, 302, 402, 502, 602, 702...Main memory unit, 103, 203, 303, 403, 503, 603, 703...Auxiliary memory unit, 204, 604...Clerk-side touch panel, 205, 305, 605...Key - Board, 206, 306, 406, 606... Fixed scanner, 207, 307, 407, 607... Handheld scanner, 208, 308, 608... Payment terminal, 209, 309, 609... Change unit, 210, 310, 408, 610... Receipt printer, 211, 611... Customer-side touch panel, 212, 612... Customer-facing display, 213, 311, 411, 505, 613... Sound unit, 304, 404, 504... Touch panel, 405... Display unit, 409... Human presence sensor, 410... Lamp unit, 599... Barcode scanner.

Claims

1. A means of notifying that a customer is permitted to pass through, A reading means for reading an optically readable code, A verification means that confirms whether the payment has been completed based on the code read by the aforementioned reading means, A control means controls the notification means to provide a notification when the confirmation means confirms that the payment has been completed, in response to the code being read by the reading means. It is equipped with, The control means shall not allow the notification means to send a notification if the settlement device that has performed the settlement processing for the transaction identified by the code read by the reading means is not subject to exit control. Gate device.

2. A storage means for storing list data representing a list of payment devices that are not subject to exit control. Furthermore, The control means prevents the notification means from sending a notification when a settlement device that has performed settlement processing for a transaction identified by the code read by the reading means is included in the list represented by the list data stored by the storage means. The gate device according to claim 1.

3. If the control means confirms that the customer has already left the store based on the code read by the reading means, it will not allow the notification means to send a notification. The gate device according to claim 1.

4. A means of notifying that a customer is permitted to pass through, A reading means for reading an optically readable code, A computer installed in a gate device equipped with the following: A verification means that confirms whether the payment has been completed based on the code read by the aforementioned reading means, A control means controls the notification means to provide a notification when the confirmation means confirms that the payment has been completed, in response to the code being read by the reading means. and make it work Furthermore, the control means shall not cause the notification means to send a notification if the settlement device that has performed the settlement processing for the transaction identified by the code read by the reading means is not subject to exit control. Information processing program.

5. A means of notifying that a customer is permitted to pass through, A reading means for reading an optically readable code, A verification means that confirms whether the payment has been completed based on the code read by the aforementioned reading means, A control means controls the notification means to send a notification when it is confirmed by the confirmation means that payment has been completed, It is equipped with, The control means shall not allow the notification means to send a notification if the settlement device that has performed the settlement processing for the transaction identified by the code read by the reading means is not subject to exit control. Checkout system.

Images