Gate device, program recording medium, and checkout system

Abstract

A gate device according to an embodiment of the present invention comprises: a notification unit; a reading unit; a confirmation unit; and a control unit. The notification unit performs notification that a customer is allowed to pass. The reading unit reads an optically readable code. The confirmation unit confirms whether settlement is completed on the basis of the code read by the reading unit. The control unit controls the notification unit, in response to the code being read by the reading unit, so as to provide notification when the confirmation unit confirms that the settlement is completed. The control unit does not cause the notification unit 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 unit, is not subject to exit control.

Description

Gate device, program recording medium and checkout system

[0001] FIELD An embodiment of the present invention relates to a gate device, a program recording medium, and a checkout system.

[0002] In a store where a customer makes a payment for a transaction such as buying and selling goods, it is desirable to properly guide a customer who has completed payment to leave the store.

[0003] Japanese Patent Application Publication No. 2022-49680

[0004] The problem to be solved by the present invention is to provide a gate device, a program recording medium, and a checkout system that can appropriately guide customers who have completed payment to exit the store.

[0005] FIG. 1 is a diagram illustrating the overall configuration of a product sales system according to one embodiment. FIG. 2 is a schematic diagram illustrating an example layout of a checkout counter in a store incorporating the product sales system. FIG. 3 is a block diagram illustrating the circuit configuration of the transaction processing device in FIG. 1. FIG. 4 is a block diagram illustrating the circuit configuration of the POS terminal in FIG. 1. FIG. 5 is a block diagram illustrating the circuit configuration of the POS terminal in FIG. 1. FIG. 6 is a block diagram illustrating the circuit configuration of the checkout gate in FIG. 1. FIG. 7 is a perspective view illustrating the appearance of the checkout gate in FIG. 1. FIG. 8 is a block diagram illustrating the circuit configuration of the information processing terminal in FIG. 1. FIG. 9 is a block diagram illustrating the circuit configuration of the monitoring terminal in FIG. 1. FIG. 10 is a block diagram illustrating the circuit configuration of the POS server in FIG. 1. FIG. 11 is a sequence diagram illustrating a transaction process using the information processing terminal in FIG. 1. FIG. 12 is a flowchart of gate control processing. FIG. 13 is a flowchart of gate control processing. FIG. 14 is a flowchart of gate control processing. FIG. 15 is a screen showing an example of a standby screen displayed on the touch panel in FIG. 6 . FIG. 16 is a diagram showing an example of a standby screen displayed on the display unit in FIG. 6 . FIG. 17 is a flowchart of a passage permission process. FIG. 18 is a diagram showing an example of a first guide screen. FIG. 19 is a diagram showing an example of a second guide screen. FIG. 20 is a sequence diagram related to transaction processing using the POS terminal in FIG. 1 . FIG. 21 is a sequence diagram related to transaction processing using the POS terminal in FIG. 1 . FIG. 22 is a flowchart of a transaction search process. FIG. 23 is a diagram showing an example of an addition request screen. FIG. 24 is a flowchart of a store clerk call process by the processor in FIG. 6 and a notice process by the processor in FIG. 9 . FIG. 25 is a diagram showing an example of a calling screen. FIG. 26 is a diagram showing an example of a warning screen. FIG. 27 is a flowchart of an exit confirmation process. FIG. 28 is a flowchart of an erroneous passage process by the processor in FIG. 6 and a warning process by the processor in FIG. 9 . Fig. 29 is a diagram showing an example of a first warning screen, Fig. 30 is a diagram showing a modified example of gate control processing, and Fig. 31 is a diagram showing an example of a standby screen adapted to the modified example. Embodiment

[0006] The gate device of the embodiment includes a notification unit, a reading unit, a confirmation unit, and a control unit. The notification unit notifies the customer that they are allowed to pass. The reading unit reads an optically readable code. The confirmation unit confirms whether the payment has been completed based on the code read by the reading unit. The control unit controls the notification unit to issue a notification when the confirmation unit confirms that the payment has been completed, in response to the reading of the code by the reading unit. Furthermore, the control unit does not cause the notification unit to issue a notification if the payment device that performed the payment process for the transaction identified by the code read by the reading unit is not subject to exit control.

[0007] Below, a product sales system that processes product sales to customers in a store will be described with reference to the drawings. This product sales system is also an example of a transaction processing system that processes product sales as the target transaction. The transaction to be processed may be a type of transaction other than product sales, such as the provision of an optional service in the store. However, it is assumed that the customer is allowed to leave the store after completing the payment for the transaction to be processed.

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

[0009] 1 shows one each of the POS terminal 200, POS terminal 300, information processing terminal 500, monitoring terminal 600, and POS server 700, and three accounting gates 400, but the number of each is arbitrary. One or two of the POS terminals 200, 300, and information processing terminal 500 may be provided, and the other two or one may not be provided. When the POS terminals 200, 300, and information processing terminals 500 are provided, in many cases, multiple POS terminals 200, 300, and information processing terminals 500 are included in the product sales system 1.

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

[0011] FIG. 2 is a schematic diagram showing an example layout of a checkout counter in a store that has introduced the product sales system 1. A customer CU shopping in the store temporarily operates the information processing terminal 500. The information processing terminal 500 is attached to, for example, a shopping cart (hereinafter simply referred to as a cart) CA. The information processing terminal 500 may be carried by the customer CU. The information processing terminal 500 may be, for example, an existing portable information processing device such as a tablet computer, smartphone, or smartwatch. The information processing terminal 500 may be installed in the store and used temporarily by the customer CU, or it may be owned by the customer CU. The customer CU pushes the cart CA around the sales floor and places the products they wish to purchase directly on the cart CA or in a basket placed on the cart CA. At this time, the customer CU operates the information processing terminal 500 to register the products placed on the cart CA as products for sale. The transaction processing device 100 registers the products for sale in accordance with the operation on the information processing terminal 500. The information processing terminal 500 may be operated by a store clerk CL on behalf of the customer CU. Once the 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. The customer CU then passes through the checkout lane LA facing the checkout gate 400 used for the transaction and exits the store. When multiple checkout gates 400 are installed, as shown in FIG. 2 , these gates 400 are installed facing each of the multiple checkout lanes LA. The checkout gate 400 also has an exit gate function to control the passage of the customer 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 the items using a bagger SU as needed. In this way, the merchandise sales system 1 also functions as a checkout system for checking out at a store.

[0012] Alternatively, the customer CU may entrust the registration of the product to be purchased as a transaction item 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 product brought in by the customer CU as a transaction item 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 similar to that of similar existing POS terminals. Note that FIG. 2 illustrates an example of a separate type POS terminal 200 separated into a main unit 298 and a scanner unit 299. The POS terminal 200 may also have a different configuration, such as an integrated type. The POS terminal 200 may also 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 using the POS terminal 200, the customer CU exits the store without passing through the checkout lane LA.

[0013] Furthermore, the customer CU can register the product to be purchased as a transaction product and complete the transaction 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 the transaction at the POS terminal 300, the customer CU passes through the checkout lane LA to exit the store. The monitoring terminal 600 assists the store clerk CL in monitoring for unauthorized passage through the checkout lane LA. The POS server 700 manages transactions processed by the product sales system 1.

[0014] 3 is a block diagram showing the main circuit configuration of transaction equipment 100. Transaction equipment 100 includes processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission path 105. Processor 101, main memory unit 102, auxiliary memory unit 103, and communication unit 104 are capable of communicating with each other via transmission path 105.

[0015] Processor 101, main memory unit 102, and auxiliary memory unit 103 are connected via transmission path 105 to form a computer that performs information processing for controlling transaction equipment 100. Processor 101 corresponds to the central part of the computer. Processor 101 executes information processing for controlling each part to realize various functions of transaction equipment 100 in accordance with information processing programs such as an operating system and application programs. Processor 101 is a processing circuit that is configured with one or more circuits, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an Application Specific Integrated Circuit (ASIC), a programmable logic device (e.g., a Simple Programmable Logic Device (SPLD), a Complex Programmable Logic Device (CPLD), or a Field Programmable Gate Array (FPGA)).

[0016] The main memory unit 102 corresponds to the main memory portion of the computer. The main memory unit 102 includes a read-only memory area and a rewritable memory area. The main memory unit 102 stores part of the information processing program in the read-only memory area. The main memory unit 102 may also store data necessary for the processor 101 to execute processes for controlling each component 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 memory unit 103 corresponds to the auxiliary memory portion of the computer. The auxiliary memory unit 103 may be, for example, an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), an SSD (solid state drive), or any other well-known storage device. The auxiliary memory unit 103 stores data used by the processor 101 when performing various processes and data generated by the processes performed by the processor 101. The auxiliary memory unit 103 may also store the information processing program. In this embodiment, the auxiliary memory unit 103 stores a transaction processing program PRA, which is one of the information processing programs. The transaction processing program PRA is an application program that describes the procedures for transaction processing, which will be described later. A portion of the memory area of ​​the auxiliary memory unit 103 is used as an area for storing transaction data DAA. The transaction data DAA is data representing the contents of one transaction.

[0018] The communication unit 104 executes communication processing for performing 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. Note that, instead of or in addition to the wired communication device, a wireless communication device connected to the communication network 2 via wireless communication may be used as the communication unit 104. The transmission path 105 includes an address bus, a data bus, a control signal line, etc., and transmits data and control signals exchanged between the connected components.

[0019] The basic hardware of transaction equipment 100 may be, for example, a general-purpose server device. Transaction equipment 100 is generally transferred with transaction processing program PRA stored in auxiliary storage unit 103. However, transaction processing program PRA may be transferred separately from hardware without transaction processing program PRA stored in auxiliary storage unit 103, or with a different version of the same application program stored in auxiliary storage unit 103. Transaction equipment 100 may be configured by writing transaction processing program PRA to auxiliary storage unit 103 in response to an operator's operation. Transaction processing program PRA may 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 via a network. Transaction processing program PRA may also be stored in main storage unit 102.

[0020] 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 store clerk 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 touch panel 211, a customer-side display 212, a sound unit 213, a communication unit 214, and a transmission path 215. As an example, the processor 201, the main memory unit 202, the auxiliary memory unit 203, the store clerk touch panel 204, the keyboard 205, the change unit 209, the receipt printer 210, and the communication unit 214 are provided in a main unit 298. As another example, the fixed scanner 206, handheld scanner 207, payment terminal 208, customer-side touch panel 211, customer-side display 212, and sound unit 213 are provided in the scanner unit 299. However, some elements may be provided in the opposite units. Also, some elements, such as the clerk touch panel and keyboard, may be provided in both the main unit 298 and the scanner unit 299.

[0021] The functions of processor 201, main memory unit 202, auxiliary memory unit 203, communication unit 214, and transmission path 215 are generally equivalent to those of processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission path 105. However, auxiliary memory unit 203 stores transaction processing program PRB instead of transaction processing program PRA. Transaction processing program PRB is an application program that describes the information processing procedures of processor 201 for transaction processing in response to operations by a store clerk on a device provided in POS terminal 200.

[0022] The clerk-side touch panel 204 is provided facing the side where the clerk CL who operates the POS terminal 200 is standing (hereinafter referred to as the clerk side). The clerk-side touch panel 204 displays a screen for presenting information to the clerk CL. The clerk-side touch panel 204 also inputs instructions by touching the screen. The keyboard 205 is equipped with a number of hard keys to simplify operation by the clerk CL from the clerk side. The keyboard 205 inputs instructions from the clerk 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 a product held in front of the reading window and 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 may also be any other type of well-known device that optically reads barcodes using reflected laser light. The fixed scanner 206 may also be any well-known device that has the function of identifying a product using object recognition technology from an image of the product itself obtained by capturing an image of the product. The handheld scanner 207 is held by the store clerk CL and optically reads a barcode placed in front of the reading window. 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 capable of IC reading, magnetic reading, and near-field communication reading of credit cards. The IC reading device reads data stored in an integrated circuit (IC) provided on a credit card through communication via electrical contacts. The magnetic reading device uses a magnetic head to read data magnetically recorded on a magnetic stripe formed on the surface of a credit card. 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 reading devices are both examples of contact reading devices. The near-field communication reading reading device reads data stored in an integrated circuit (IC) provided on a credit card through wireless communication such as NFC (near field communication). Thus, near-field communication reading is an example of contactless reading. A reading device for reading proximity communication is an example of a contactless reading device.

[0025] The change unit 209 counts the value of coins inserted through the coin insertion slot and stores them in an internal storage. The change unit 209 discharges coins stored in the storage to a coin tray through the coin discharge port. The change unit 209 counts the value of banknotes inserted through the banknote insertion slot and stores them in an internal storage. The change unit 209 discharges banknotes stored in the storage from the 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, sales slip, or other voucher onto receipt paper. The receipt printer 210 then ejects the receipt paper with the image printed on it from the receipt ejection port. Note that, hereinafter, receipt paper with a printed receipt image will be referred to as a paper receipt.

[0027] The customer-side touch panel 211 is provided facing the side where the customer CU is standing when the clerk CL operates to register the transaction product (hereinafter referred to as the customer side). The customer-side touch panel 211 displays a screen for presenting information to the customer. The customer-side touch panel 211 also inputs instructions by the customer CU by touching the screen.

[0028] The customer-side display 212 is provided facing the customer side. The customer-side display 212 displays a screen for presenting information to the customer CU. The customer-side display 212 is mainly adapted for displaying text, and displays a simpler screen than the customer-side touch panel 211. The sound unit 213 outputs sounds and voices for various kinds of guidance and warnings. As the sound unit, various well-known sound devices such as a voice synthesis device and a buzzer can be used alone or in combination.

[0029] The basic hardware of the POS terminal 200 can be, for example, the hardware of another existing POS terminal. In this case, the POS terminal 200 is generally transferred with the transaction processing program PRB stored in the auxiliary storage unit 203. However, the POS terminal 200 hardware 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 into the auxiliary storage unit 203 in response to an operator's operation. Alternatively, the POS terminal 200 hardware and the transaction processing program PRB may be transferred separately with a different version of an information processing program of the same type as 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, replacing the information processing program already stored therein. The transaction processing program PRB can be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network. The transaction processing program PRB may be stored in the main storage unit 202.

[0030] 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 unit 309, a receipt printer 310, a sound unit 311, a communication unit 312, and a transmission path 313.

[0031] The functions of processor 301, main memory unit 302, auxiliary memory unit 303, communication unit 312, and transmission path 313 are generally equivalent to those of processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission path 105. However, auxiliary memory unit 303 stores transaction processing program PRC instead of transaction processing program PRA. Transaction processing program PRC is an application program that describes the information processing procedures of processor 301 for transaction processing in response to customer operations on devices provided in POS terminal 300.

[0032] The touch panel 304 is provided facing the customer CU who operates the POS terminal 300. The touch panel 304 displays a screen for presenting information to the customer CU. The customer CU also inputs instructions by touching the screen on the touch panel 304. The keyboard 305, fixed scanner 306, handheld scanner 307, payment terminal 308, change unit 309, receipt printer 310, and sound unit 311 have generally the same functions as 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 to simplify operation by the customer CU and are primarily operated by the customer CU.

[0033] The basic hardware of the POS terminal 300 can be, for example, the hardware of another existing self-service POS terminal. In this case, the POS terminal 300 is generally transferred with the transaction processing program PRC stored in the auxiliary storage unit 303. However, the POS terminal 300 hardware and the transaction processing program PRC 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 into the auxiliary storage unit 303 in response to an operator's operation. Alternatively, the POS terminal 300 hardware and the transaction processing program PRC may be transferred separately with a different version of an information processing program of the same type as 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, replacing the information processing program already stored therein. The transaction processing program PRC can be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network. The transaction processing program PRC may be stored in the main storage unit 302.

[0034] 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 sensor 409, a lamp unit 410, a sound unit 411, a communication unit 412, and a transmission path 413.

[0035] The processor 401, main storage unit 402, auxiliary storage unit 403, communication unit 412, and transmission path 413 have generally the same functions as the processor 101, main storage unit 102, auxiliary storage unit 103, communication unit 104, and transmission path 105. However, the auxiliary storage unit 403 stores a 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 procedures of the processor 401 for gate control processing, which will be described later. The auxiliary storage unit 403 also stores rejection list data DAB. The rejection list data DAB represents a list of POS terminals that have been predetermined as targets for rejection. Which of the POS terminals 200 and 300 is to be the target for rejection can be determined as appropriate by any person, such as the administrator of the product sales system 1. In this embodiment, the POS terminal 200 is the target for rejection.

[0036] The touch panel 404 displays a screen for presenting information to the operator performing the transaction. The operator also inputs instructions by touching the screen on the touch panel 404. The operator of the transaction gate 400 is usually a customer CU. However, the store clerk CL may also operate the transaction gate 400.

[0037] The display unit 405 displays a screen for providing information to a customer CU who is about to pass through the checkout lane LA facing the checkout gate 400 where the display unit 405 is installed. Note that hereinafter, when the term "checkout lane LA" is used in the description of the checkout gate 400, it refers to the checkout lane LA facing the checkout gate 400 in question.

[0038] Fixed scanner 406 has a reading window. Fixed scanner 406 recognizes barcode information represented by a barcode held in front of the reading window through image processing. Fixed scanner 406 then outputs the barcode information to processor 401. Note that fixed scanner 406 may also use other types of well-known devices that optically read barcodes using reflected laser light. Fixed scanner 406 may also use other types of well-known devices that have a function of identifying products using object recognition technology from images of the products themselves obtained by capturing images of the products.

[0039] The handheld scanner 407 is held by the customer CU and optically reads a barcode placed in front of the reading port. 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, sales slip, or other voucher on receipt paper. The receipt printer 408 ejects the receipt paper with the image printed on it from the receipt ejection port to the outside. In other words, the receipt printer 408 is used to issue paper receipts.

[0040] The human presence sensor 409 detects customers CU passing through the checkout lane LA. Well-known detection devices such as optical sensors or infrared sensors can be used as the human presence sensor 409. In other words, the human presence sensor 409 is an example of a first detection unit. The lamp 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 guidance 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 voice synthesis device and a buzzer can be used alone or in combination.

[0042] The accounting gate 400 is generally transferred with the gate control program PRD stored in the auxiliary storage unit 403. However, the gate control program PRD may be transferred separately from the hardware 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 be configured by writing the gate control program PRD to the auxiliary storage unit 403 in response to an operator's operation. The gate control program PRD may 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 via a network. The gate control program PRD may be stored in the main storage unit 402.

[0043] Figure 7 is a perspective view showing the exterior of the checkout gate 400. Note that in Figure 7, the same elements as those shown in Figure 6 are designated by the same reference numerals. In the following description 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 having a roughly rectangular parallelepiped shape. The checkout gate 400 is installed with one side 451 of the housing 450 facing the checkout lane LA to control the movement of the customer CU in the direction of movement indicated by the arrow AR through the checkout lane LA. Hereinafter, the side of the housing 450 facing the direction of movement of the customer CU will be referred to as the front side 452.

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

[0045] The touch panel 404 is mounted above the fixed scanner 406 in a position that allows the display surface to be easily viewed from the customer CU facing the front surface 452. The handheld scanner 407 is connected to a transmission path 413 provided inside the housing 450 via a cable and can be pulled out to the front side of the front surface 452 for use. Note that FIG. 7 shows the handheld scanner 407 set in a folder. The human presence sensor 409 is provided inside the housing 450 so as to detect a customer CU passing through the checkout lane LA through a slit 454 formed in the side surface 451. The lamp unit 410 is attached to 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 FIG. 6 are provided inside the housing 450.

[0046] 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, a transmission path 508, and the like.

[0047] The functions of processor 501, main memory unit 502, auxiliary memory unit 503, and transmission path 508 are generally equivalent to those of processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission path 105. However, auxiliary memory unit 503 stores terminal program PRE instead of transaction processing program PRA. Terminal program PRE is an application program that describes the information processing procedures of processor 501 to cause information processing terminal 500 to function as a user interface for registering transaction commodities in transaction processing device 100.

[0048] The touch panel 504 displays a screen for presenting information to the operator. The operator also inputs instructions by touching the screen on the touch panel 504. The operator of the information processing terminal 500 is usually a customer CU. However, the store clerk CL may also operate the information processing terminal 500. The sound unit 505 outputs sounds and voices for various kinds of guidance and warnings. As the sound unit, various well-known sound devices such as a voice synthesis device and a buzzer can be used alone or in combination.

[0049] An external device such as a barcode scanner 599 is connected to the interface unit 506. The interface unit 506 acts as an interface for exchanging data with the connected external device. An existing USB (universal serial bus) controller or the like can be used as the interface unit 506. The barcode scanner 599 is attached to the cart CA and has a reading window. The barcode scanner 599 uses image processing to recognize barcode information represented by a barcode held in front of the reading window. The barcode scanner 599 then outputs the barcode information. The barcode scanner 599 can also be any other type of well-known device that optically reads barcodes using reflected laser light. The barcode scanner 599 can also be any well-known device that has the function of identifying products using object recognition technology from an image of the product itself obtained by capturing the product. Instead of or in addition to the barcode scanner 599, a camera provided in the information processing terminal 500 can be used to read barcodes.

[0050] The wireless communication unit 507 executes communication processing for wirelessly communicating data 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. Note that instead of or in addition to the wireless communication unit 507, a communication unit that is wired connected to the communication network 2 may be used.

[0051] The basic hardware of the information processing terminal 500 is assumed to be, for example, the hardware of a tablet-type information processing device. The information processing terminal 500 is generally transferred with the terminal program PRE stored in the auxiliary storage unit 503. However, the hardware may be transferred separately from the terminal program PRE without the terminal program PRE stored in the auxiliary storage unit 503, or with a different version of the same application program stored in the auxiliary storage unit 503. The information processing terminal 500 may be configured by writing the terminal program PRE to the auxiliary storage unit 503 in response to an operator's operation. The terminal program PRE may 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 via a network. The terminal program PRE may be stored in the main storage unit 502.

[0052] 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 store clerk-side touch panel 604, a keyboard 605, a fixed scanner 606, a handheld scanner 607, a payment terminal 608, a change unit 609, a receipt printer 610, a customer-side touch panel 611, a customer-side display 612, a sound unit 613, a communication unit 614, and a transmission path 615.

[0053] The functions of the processor 601, main memory unit 602, auxiliary memory unit 603, sound unit 613, communication unit 614, and transmission path 615 are generally equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission path 105. The functions of the clerk-side touch panel 604, keyboard 605, fixed scanner 606, handheld scanner 607, payment terminal 608, change unit 609, receipt printer 610, customer-side touch panel 611, customer-side display 612, and sound unit 613 are equivalent to those of the clerk-side touch panel 204, keyboard 205, fixed scanner 206, handheld scanner 207, payment terminal 208, change unit 209, receipt printer 210, customer-side touch panel 211, customer-side 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, in addition to the transaction processing program PRB, the auxiliary storage unit 603 also stores a monitoring program PRF. The monitoring program PRF is an application program that describes information processing procedures to assist the store clerk CL in monitoring fraudulent passage through the checkout lane LA. As a result, the monitoring terminal 600 is a device that adds a monitoring support function to the POS terminal 200. However, the monitoring terminal 600 can also be configured without the transaction processing function. In this case, the basic hardware of the monitoring terminal 600 can be any type of general-purpose computer device, such as a desktop, notebook, or tablet.

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

[0056] 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 memory unit 702, an auxiliary memory unit 703, a communication unit 704, and a transmission path 705. The functions of the processor 701, main memory unit 702, auxiliary memory unit 703, communication unit 704, and transmission path 705 are generally equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104, and transmission path 105.

[0057] However, the auxiliary storage unit 703 stores a 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, part of the storage area of ​​the auxiliary storage unit 703 is used to store a transaction database DBA. The transaction database DBA is a database that accumulates transaction data that shows 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. The POS server 700 is generally transferred with the transaction management program PRG stored in the auxiliary storage unit 703. However, the transaction management program PRG and the hardware may be transferred separately, without the transaction management program PRG being stored in the auxiliary storage unit 703, or with a different version of the same application program stored in the auxiliary storage unit 703. The POS server 700 may be configured by writing the transaction management program PRG to the auxiliary storage unit 703 in response to an operator's operation. The transaction management program PRG may 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 via 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 described. Note that the contents of the various processes described below are merely examples, and it is possible to change the order of some of the processes, omit some of the processes, or add other processes as appropriate. For example, in the following description, in order to clearly explain the characteristic operations of this embodiment, explanation of some of the processes will be omitted. For example, if an error occurs, processing may be performed to deal with the error, but a description of such processing will be omitted.

[0060] 11 is a sequence diagram related to transaction processing using information processing terminal 500. In transaction equipment 100 and information processing terminal 500, processor 101 and processor 501 cooperate to perform registration processing as ACT 101 and user interface processing as ACT 501. As a result, processor 101 uses information processing terminal 500 as a user interface terminal and, while receiving instructions from a customer CU, registers the products that the customer CU intends to purchase as transaction products, and generates transaction data representing a list of the transaction products. The registration processing is, for example, a process in which the barcode of the product that the customer CU intends to purchase is read by information processing terminal 500, or the customer CU operates a preset key displayed on information processing terminal 500 to specify the product, thereby adding the specified product as a transaction product.

[0061] When customer CU performs a predetermined operation on information processing terminal 500 to specify the start of a transaction, processor 501 at information processing terminal 500 proceeds to ACT 502. In ACT 502, processor 501 notifies transaction equipment 100 that the start of a transaction has been specified.

[0062] When processor 101 in transaction equipment 100 is notified of the transaction start designation, the process proceeds to ACT 102. In ACT 102, processor 101 instructs information processing terminal 500 to display a transition screen.

[0063] When processor 501 of information processing terminal 500 is instructed to display the transfer screen, the process proceeds to ACT 503. In ACT 503, processor 501 displays the transfer screen on touch panel 504. The transfer screen is a screen used to transfer the function as a user interface terminal related to the transaction being processed from information processing terminal 500 to accounting gate 400. The transfer screen includes, for example, a two-dimensional code (hereinafter referred to as a transfer code) representing transfer data used by accounting gate 400 to request accounting data based on the transaction data from transaction processing device 100.

[0064] On the other hand, when the processor 401 at the checkout gate 400 is in an operating state that allows use by a customer CU, it executes gate control processing in accordance with the gate control program PRD. Figures 12, 13, and 14 are flowcharts of the gate control processing. In ACT 401, the processor 401 displays a standby screen on the touch panel 404 and the display unit 405. The standby screen is a screen that guides the customer CU through operations that should be performed while waiting for the customer CU to perform an operation.

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

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

[0067] Fig. 16 is a diagram showing an example of a standby screen displayed on the display unit 405. The standby screen shown in Fig. 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 product barcode of one of the products in the transaction.

[0068] In ACT 402 in FIG. 12, the processor 401 checks whether a barcode has been scanned. If the processor 401 cannot confirm the event, it determines "NO" and proceeds to ACT 403. In ACT 403, the processor 401 checks whether the screen of the touch panel 404 has been tapped. If the processor 401 cannot confirm the event, it determines "NO" and proceeds to ACT 404. In ACT 404, the processor 401 checks whether a person has passed through the checkout lane LA. If the processor 401 cannot confirm the event, it determines "NO" and returns to ACT 402. Note that the "checkout lane LA" here and the "checkout lane LA" in the following description refer to the checkout lane LA facing the checkout gate 400 being described. Thus, in ACTs 402 to 404, the processor 401 waits for a barcode scan, a screen tap, or a person to pass through.

[0069] If multiple checkout gates 400 are installed, a customer CU using the information processing terminal 500 displaying the handover screen on the touch panel 504 as described above arbitrarily selects one of the checkout gates 400 displaying the standby screen and touches the screen of the touch panel 504 provided on that checkout gate 400. When a tap is detected by the touch panel 504, the processor 401 determines YES in ACT 403 and proceeds to ACT 405.

[0070] In ACT 405, the processor 401 displays a transfer guidance screen on the touch panel 404 and the display unit 405. As described above, the transfer guidance screen is a screen for guiding the customer CU to have the handy scanner 407 read the transfer code included in the transfer screen displayed on the touch panel 504 of the information processing terminal 500. In ACT 406, the processor 401 waits for the transfer code to be scanned.

[0071] After touching the screen of the touch panel 504 as described above, the customer CU faces the reading port of the handheld scanner 407 toward the transfer code. This causes the handheld scanner 407 to read the transfer code and output 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. Note that the transfer code may be read by the fixed scanner 406. That is, for example, if the information processing terminal 500 is 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 faced toward the fixed scanner 406. It is desirable that the transfer guidance screen contains content that guides the customer CU on expected transfer code reading methods.

[0072] In ACT 407, processor 401 acquires accounting data based on the handover data represented by the barcode information output from handy scanner 407. That is, processor 401 requests the accounting data from transaction equipment 100, as shown in Fig. 11. When the accounting data is requested from accounting gate 400, processor 101 in transaction equipment 100 proceeds to ACT 103.

[0073] In ACT 103, the processor 101 sends predetermined accounting data for accounting and settlement according to the transaction content represented by the transaction data to the requesting accounting gate 400. Then, in ACT 407, the processor 401 at the accounting gate 400 captures the accounting data sent in this manner and received by the communication unit 412.

[0074] Once the processor 401 has acquired the transaction data in this manner, it proceeds to ACT 408 in FIG. 12 . In ACT 408, the processor 401 performs transaction processing based on the acquired transaction data. That is, the processor 401 performs accounting processing to determine the payment amount for the transaction based on the acquired transaction data. This accounting processing may be similar to the processing performed by existing semi-self-service POS system cash registers. The processor 401 then performs payment processing to settle the payment amount determined as described above. For example, the payment processing may be performed using electronic money provided by the store operator. In this case, the customer CU's identifier is acquired when the information processing terminal 500 is first used, and payment is made 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 used for payment at the transaction gate 400. Furthermore, electronic money payments provided by a payment service provider other than the company that operates the store may be accepted for payments at checkout gate 400. Depending on the payment method that is accepted, additional devices not shown in Figure 6 may be required for payments using that payment method.

[0075] In ACT 409, the processor 401 confirms whether an electronic receipt should be applied. If the identifier of the customer CU has been acquired as described above, the processor 401 confirms whether a setting to apply an electronic receipt has been made in advance for the customer CU identified by this identifier. The processor 401 may have the customer CU specify whether or not to apply an electronic receipt, and may confirm whether or not to apply an electronic receipt based on that specification. If the processor 401 cannot confirm that an electronic receipt should be applied, it determines NO and proceeds to ACT 410.

[0076] In ACT 410, the processor 401 issues a paper receipt showing the transaction details, the transaction result, etc., and a receipt barcode. That is, the processor 401 generates a receipt image showing, for example, the transaction details, the transaction result, etc., and a payment completion code, and causes the receipt printer 408 to print the receipt image. This results in the receipt printer 408 printing the receipt image on receipt paper, thereby issuing a paper receipt.

[0077] On the other hand, if the processor 401 can confirm that an electronic receipt should be applied, it determines YES in ACT 409 and proceeds to ACT 411. In ACT 411, the processor 401 registers an electronic receipt including the transaction details, the transaction result, etc., and a receipt barcode in the electronic receipt server 3. That is, the processor 401 transmits predetermined request data for requesting the registration of an electronic receipt, along with a notification of the transaction details, the transaction result, etc., and a payment completion code, to the electronic receipt server 3. Upon receiving this request data, the electronic receipt server 3 makes an electronic receipt screen showing the notified transaction details, the transaction result, etc., and a receipt barcode viewable from any information terminal.

[0078] In either case, upon completion of ACT 410 or ACT 411, processor 401 proceeds to ACT 412. In ACT 412, processor 401 notifies transaction equipment 100 of the results of the transaction processing. In response to this notification, processor 101 in transaction equipment 100 proceeds to ACT 104 in FIG.

[0079] In ACT 104, the processor 401 sends transaction data related to the transaction currently being processed to the POS server 700. This transaction data may be similar to transaction data in existing POS systems. That is, the transaction data may include a transaction header, item data, combination discount data, customer data, closing data, credit data, and the like. The item data is data representing a list of the items transacted. The type of data to be included in the transaction data may be determined as appropriate, for example, by the person who determines the specifications of the product sales system 1. However, the transaction data must be data that at least allows for determining what items were traded in the transaction. The processor 401 also includes exit data, which indicates the customer CU's exit status from the store, in the transaction data as a status indicating that the customer CU has not yet exited.

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

[0081] After notifying the checkout gate 400 of the transaction result in ACT 412 in FIG. 12 , the processor 401 proceeds to ACT 413. In ACT 413, the processor 401 performs a passage permission process. FIG. 17 is a flowchart of the passage permission process. In ACT 451, the processor 401 starts a passage permission notification. The passage permission notification is a notification to let the customer CU and people around them know that they are permitted to pass through the checkout lane LA. To notify the passage permission, the processor 401, for example, lights up the lamp unit 410 in blue. To notify the passage permission, the processor 401, for example, outputs a voice message such as "Please pass through the gate" to the sound unit 411. Alternatively, to notify the passage permission, the processor 401 may perform another operation, such as outputting a predetermined notification sound from the sound unit 411. However, the processor 401 may execute only a part of these operations to notify the passage permission.

[0082] In addition to the above, when the passage permission notification is issued, processor 401 causes touch panel 404 to display, for example, a first guide screen. In addition to the above, when the passage permission notification is issued, processor 401 causes display unit 405 to display, for example, a second guide screen. Figure 18 is a diagram showing an example of the first guide screen. The first guide screen shown in Figure 18 includes a text message indicating that the customer is permitted to pass through checkout lane LA because the transaction has been completed.

[0083] FIG. 19 is a diagram showing an example of the second guidance screen. The second guidance screen shown in FIG. 19 includes a text message indicating that there is a time limit for passing through the checkout lane LA, and a number indicating the remaining time for passing through the checkout lane LA. The second guidance screen shown in FIG. 19 is an example when the remaining time is 10 seconds, and the number "10" represents that remaining time. With regard to the second guidance screen, the processor 401 updates the number indicating the remaining time each time the remaining time changes. This second guidance screen allows the customer CU to recognize the remaining time for passing through the checkout lane LA. Based on this screen, the customer CU can determine whether they should hurry through.

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

[0085] The processor 401 proceeds to ACT 452 while issuing the passage permission notification. In ACT 452, the processor 401 checks whether a person has passed through the checkout lane LA. If the processor 401 cannot confirm this event, it determines "NO" and proceeds to ACT 453. In ACT 453, the processor 401 checks whether a predetermined allowable time has elapsed since the processor 401 started issuing the passage permission notification in ACT 451. If the processor 401 cannot confirm this event, it determines "NO" and returns to ACT 452. Thus, in ACT 452 and ACT 453, the processor 401 waits for a person to pass through or for the allowable time to elapse.

[0086] If the customer CU passes through the checkout lane before the allowed time has elapsed and the human presence sensor 409 detects the passage of a person, the processor 401 determines YES in ACT 452 and proceeds to ACT 454. In ACT 454, the processor 401 requests the POS server 700 to update the exit data. Upon receiving this request, the processor 701 in the POS server 700 proceeds to ACT 702 in Fig. 11. Note that this request to update the exit data may also be made by the processor 601 to the POS server 700 upon receiving a notification of exit from the processor 401. In ACT 702 in Fig. 11, the processor 701 updates the exit data included in the transaction data included in the transaction database DBA in ACT 701 to a state indicating that the customer has exited.

[0087] At the checkout gate 400, the processor 401 proceeds to ACT 455 after completing the notification in ACT 454 in FIG. 17. If the allowed time has elapsed without the processor 401 being able to confirm that the customer CU has passed through the checkout lane LA, the processor 401 determines YES in ACT 453, skips ACT 454, and proceeds to ACT 455. For example, even after completing the checkout, the customer CU may return to the sales floor without passing through the checkout lane LA. In such a case, the processor 401 determines YES in ACT 453. In ACT 455, the processor 401 stops the passage permission notification. The processor 401 then ends the passage permission process and returns to ACT 401 in FIG. 12 to prepare for the next customer CU.

[0088] 20 is a sequence diagram related to the processing of a transaction using the POS terminal 200. When the processor 201 in the POS terminal 200 receives a command to start registration through a predetermined operation by the store clerk CL, the processor proceeds to ACT 201. In ACT 201, the processor 201 registers the products that the customer CU wishes to purchase as transaction products in accordance with the operations by the store clerk CL using various devices of the POS terminal 200, and generates transaction data representing a list of the transaction products. When the store clerk CL declares that registration is complete, the processor 201 proceeds to ACT 202.

[0089] As ACT202, the processor 201 performs accounting processing to calculate and settle the price according to the transaction details represented by the transaction data generated in ACT201. That is, the processor 201 performs accounting processing to determine the payment amount for the transaction based on the generated transaction data, for example. The processor 201 then performs payment processing to settle the payment amount determined as described above, for example. The payment processing may use various payment methods, such as credit card payment, code payment, prepaid payment, point payment, gift certificate payment, or cash payment, as appropriate. The above registration and payment processing may be similar to the processing performed in, for example, existing face-to-face POS terminals. In this way, the POS terminal 200 functions as a payment device.

[0090] In ACT 203, the processor 201 confirms whether an electronic receipt should be applied. If the identifier of the customer CU has been acquired during the registration process or the transaction process, the processor 201 confirms whether a setting to apply an electronic receipt has been made in advance for the customer CU identified by this identifier. The processor 201 may have the customer CU or the store clerk CL specify whether or not an electronic receipt should be applied, and may confirm whether or not an electronic receipt should be applied in accordance with that specification. If the processor 201 cannot confirm that an electronic receipt should be applied, it determines NO and proceeds to ACT 204.

[0091] As ACT 204, the processor 201 issues a paper receipt that displays the transaction details, transaction results, etc., along with a receipt barcode. That is, the processor 201 generates a receipt image that displays the transaction details, transaction results, etc., and causes the receipt printer 210 to print the receipt image. This results in the receipt printer 210 printing the receipt image on receipt paper, thereby issuing a paper receipt.

[0092] On the other hand, if the processor 201 can confirm that an electronic receipt should be applied, it determines YES in ACT 203 and proceeds to ACT 205. In ACT 205, the processor 201 registers an electronic receipt including the transaction details, the transaction result, etc., and a receipt barcode in the electronic receipt server 3. That is, the processor 201 transmits predetermined request data for requesting the registration of an electronic receipt, along with notification of the transaction details, the transaction result, etc., to the electronic receipt server 3. Upon receiving this request data, the electronic receipt server 3 makes an electronic receipt screen showing the notified transaction details, the transaction result, etc., and the receipt barcode viewable from any information terminal.

[0093] After completing ACT 204 or ACT 205, the processor 201 proceeds to ACT 206. In ACT 206, the processor 201 sends transaction data related to the transaction just processed to the POS server 700. This transaction data may be similar to transaction data in existing POS systems. That is, the transaction data may include a transaction header, item data, combination discount data, customer data, closing data, and credit data. The item data represents a list of the items transacted. The type of data to be included in the transaction data may be determined as appropriate by, for example, the person who determines the specifications of the product sales system 1. However, the transaction data must be data that at least allows for determining what items were traded in the transaction. In this embodiment, customer CUs related to transactions processed by the POS terminal 200 are not subject to exit control by the checkout gate 400 and are operated independently of the checkout gate 400. For this reason, the processor 201 does not include exit data in the transaction data. In other words, the POS terminal 200 may be an existing face-to-face POS terminal.

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

[0095] FIG. 21 is a sequence diagram related to transaction processing using the POS terminal 300. When the processor 301 in the POS terminal 300 receives a registration start instruction through a predetermined operation by the customer CU, the process proceeds to ACT 301. In ACT 301, the processor 301 registers the items the customer CU wishes to purchase as transaction items in accordance with the customer CU's operations using various devices on the POS terminal 300, and generates transaction data representing a list of the transaction items. For example, the processor 301 registers the items specified by the customer CU by having the fixed scanner 306 or handheld scanner 307 read the item's barcode, or by the customer CU operating a preset key displayed on the touch panel 304 or included on the keyboard 305 and associated with the item. When the customer CU declares that registration is complete, the processor 301 proceeds to ACT 302.

[0096] As ACT 302, the processor 301 performs accounting processing to calculate and settle the price according to the transaction details represented by the transaction data generated in ACT 301. That is, the processor 301 performs accounting processing to determine the payment amount for the transaction based on the generated transaction data, for example. The processor 301 then performs payment processing to settle the payment amount determined as described above, for example. The payment processing may use various payment methods, such as credit card payment, code payment, prepaid payment, point payment, gift certificate payment, or cash payment, as appropriate. The above registration and payment processing may be similar to the processing performed in, for example, existing full-self-service POS terminals. In this way, the POS terminal 200 functions as a payment device.

[0097] In ACT 303, the processor 301 confirms whether an electronic receipt should be applied. If the identifier of the customer CU has been acquired during the registration process or the transaction process, the processor 301 confirms whether a setting to apply an electronic receipt has been made in advance for the customer CU identified by this identifier. The processor 301 may have the customer CU specify whether or not to apply an electronic receipt, and may confirm whether or not to apply an electronic receipt based on that specification. If the processor 301 cannot confirm that an electronic receipt should be applied, it determines NO and proceeds to ACT 304.

[0098] In ACT 304, the processor 301 issues a paper receipt that displays the transaction details, transaction results, etc., along with a receipt barcode. That is, the processor 301 generates a receipt image that displays the transaction details, transaction results, etc., along with a receipt barcode, and causes the receipt printer 310 to print the receipt image. This results in the receipt printer 310 printing the receipt image on receipt paper, thereby issuing a paper receipt.

[0099] On the other hand, if the processor 301 can confirm that an electronic receipt should be applied, it determines YES in ACT 303 and proceeds to ACT 305. In ACT 305, the processor 301 registers an electronic receipt including the transaction details, the transaction result, etc., and a receipt barcode in the electronic receipt server 3. That is, the processor 301 transmits predetermined request data for requesting the registration of an electronic receipt, along with notification of the transaction details, the transaction result, etc., and the receipt barcode, to the electronic receipt server 3. Upon receiving this request data, the electronic receipt server 3 makes an electronic receipt screen showing the notified transaction details, the transaction result, etc., and the receipt barcode viewable from any information terminal.

[0100] After completing ACT 304 or ACT 305, the processor 301 proceeds to ACT 306. In ACT 306, the processor 301 sends transaction data related to the transaction just processed to the POS server 700. This transaction data may be similar to transaction data in existing POS systems. That is, the transaction data may include a transaction header, item data, combination discount data, customer data, closing data, and credit data. The item data represents a list of the items transacted. The type of data to be included in the transaction data may be determined as appropriate by, for example, the person who determines the specifications of the product sales system 1. However, the transaction data must be data that at least allows for determining what items were traded in the transaction. In this embodiment, customer CUs related to transactions processed by the POS terminal 300 are subject to exit control by the accounting gate 400. Therefore, the processor 301 includes exit data indicating that the customer has not yet exited in the transaction data.

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

[0102] As mentioned above, if a customer CU who has completed payment at checkout gate 400 but has not passed through checkout lane LA within the allowed time attempts to leave the store without purchasing any additional items, the customer CU has the receipt barcode displayed on the paper receipt issued by checkout gate 400 or on the electronic receipt screen read by fixed scanner 406 or handheld scanner 407 of any waiting checkout gate 400. In other words, fixed scanner 406 and handheld scanner 407 are examples of reading units that read receipt barcodes, which are an example of optically readable codes.

[0103] After completing payment at the POS terminal 300, the customer CU has the receipt barcode displayed on the paper receipt or electronic receipt screen issued by the POS terminal 300 read by the fixed scanner 406 or handheld scanner 407 of any waiting checkout gate 400. In cases where it is difficult to have the fixed scanner 406 or handheld scanner 407 read the receipt barcode for various reasons, such as when the customer loses the paper receipt issued by the checkout gate 400 or POS terminal 300, or when the customer does not have a smartphone or other device and is unable to display the electronic receipt screen, 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 product barcode of one of the transaction items for which payment has been made.

[0104] When the fixed scanner 406 or the handy scanner 407 reads the barcode, it notifies the barcode information represented by the barcode to the processor 401. As a result, the processor 401 determines YES in ACT 402 in Fig. 12 and proceeds to ACT 421 in Fig. 13.

[0105] In ACT 421, the processor 401 checks whether the read barcode is a product barcode. If the processor 401 cannot confirm this, it determines "NO" and proceeds to ACT 422. In ACT 422, the processor 401 checks whether the read barcode is a receipt barcode. If the processor 401 cannot confirm this, it determines "NO" and returns to the standby state of ACT 402 to ACT 404 in Figure 5. At this time, the processor 401 may perform a guidance operation such as a screen display to guide the customer CU to read the product barcode or receipt barcode.

[0106] If the product barcode has been read as described above, the processor 401 determines YES in ACT 421 and proceeds to ACT 423. In ACT 423, the processor 401 queries the POS server 700 about the transaction, along with a notification of the product code included in the barcode information obtained by reading the product barcode.

[0107] When the processor 701 in the POS server 700 receives a transaction inquiry such as the one described above, it executes information processing (hereinafter referred to as the transaction search process) based on the transaction management program PRG. Figure 22 is a flowchart of the transaction search process. Hereinafter, when the term "accounting gate 400" is used in the description of the transaction search process, it refers to the accounting gate 400 that made the inquiry.

[0108] In ACT 731, the processor 701 searches past transactions for which settlement has been completed, for transactions that include the product identified by the product code notified at the time of the inquiry as a traded item. For example, the processor 701 first extracts transaction data from the transaction database DBA that meets the following conditions: - relates to transactions that took place within a predetermined search period; - includes the product identified by the notified product code as a traded item; and - includes exit data indicating that the transaction has not been exited.

[0109] It should be noted that the search period is assumed to be a fixed time period, such as the most recent 10 minutes, as an example. The search period may be determined as appropriate by the person who determines the specifications of the product sales system 1, the store manager, or the like. For example, the search period may be the current day. Alternatively, the most recent predetermined number of transactions may be the search targets. In this case, the search period is the period during which the relevant number of transactions were made. As an example, the number of most recent transactions is assumed to be 20 transactions, but this number may be determined as appropriate by the person who determines the specifications of the product sales system 1, the store manager, or the like.

[0110] In ACT 732, the processor 701 checks whether the relevant transaction has been found by the above search. If the processor 701 cannot extract any transaction data that matches the conditions in ACT 731, for example, the processor 701 determines that there is no relevant transaction and determines NO, and proceeds to ACT 733.

[0111] In ACT 733, the processor 701 notifies the accounting gate 400 of an error in response to the transaction inquiry. In other words, if the processor 701 cannot find any transactions that meet the above conditions, it determines that there is an error and notifies the accounting gate 400. The processor 701 then ends the transaction search process.

[0112] For example, if the processor 701 can extract even one transaction data that matches the conditions in ACT 731, it determines that a corresponding transaction exists and answers YES in ACT 732, and proceeds to ACT 734. In ACT 734, the processor 701 checks whether multiple transactions were found by the above search. Then, if the processor 701 has extracted only one transaction data that matches the conditions in ACT 731, it determines that there are not multiple transactions and answers NO, and proceeds to ACT 735.

[0113] In ACT 735, the processor 701 notifies the accounting gate 400 of permission in response to the transaction inquiry. In other words, if the processor 701 can narrow down one transaction based on the above conditions, it determines permission and notifies the accounting gate 400. The processor 701 then ends the transaction search process.

[0114] For example, if there are multiple pieces of transaction data extracted in ACT 731, the processor 701 determines YES in ACT 734 and proceeds to ACT 736. In ACT 736, the processor 701 checks whether the narrowing-down termination condition has been met. The termination condition may be determined as appropriate by the person who decides the specifications of the product sales system 1 or the store manager. Specific examples of termination conditions will be described later. If the processor 701 cannot confirm the relevant event, it determines NO and proceeds to ACT 737. In ACT 737, the processor 701 requests the checkout gate 400 to notify the user of another product.

[0115] At the accounting gate 400, the processor 401 inquires about the transaction in ACT 423 in FIG. 13, and then proceeds to ACT 424. In ACT 424, the processor 401 checks whether a notification of another product has been requested. If the processor 401 cannot confirm the relevant event, it determines "NO" and proceeds to ACT 425. In ACT 425, the processor 401 checks whether a permission notification has been issued. That is, the processor 401 determines whether to receive a permission notification from the processor 701. If the processor 401 cannot confirm the relevant event, it determines "NO" and proceeds to ACT 426. In ACT 426, the processor 401 checks whether an error notification has been issued. If the processor 401 cannot confirm the relevant event, it determines "NO" and returns to ACT 424. Thus, in ACTs 424 to 426, the processor 401 waits for one of a notification request, a permission notification, or an error notification to be issued. Then, when a notification of another product is requested from the POS server 700 as described above, the processor 401 determines YES in ACT 424 and proceeds to ACT 441 in FIG.

[0116] In ACT 441, the processor 401 displays an addition request screen on the touch panel 404. The addition request screen is a screen that requests the customer CU to have the fixed scanner 406 or the handheld scanner 407 read the commodity barcode of a transaction commodity different from the ones that have been read so far.

[0117] Fig. 23 is a diagram showing an example of an additional product request screen. The additional product request screen shown in Fig. 23 is a screen showing a window WIA superimposed on a standby screen. The window WIA shows a text message for the above request and also shows a button BUA. The button BUA is a soft key that allows the customer CU to declare that there is no other product available.

[0118] If there are other products for which the product code has not yet been read, the customer CU has the fixed scanner 406 or the handheld scanner 407 read the product barcode of one of the products. If the customer has already read the product barcodes of all the products for which the product code has been read, the customer declares that there are no more products by a predetermined operation, such as tapping the button BUA.

[0119] After displaying the addition request screen in ACT 441 in FIG. 14, the processor 401 proceeds to ACT 442. In ACT 442, the processor 401 checks whether the product barcode has been scanned. If the relevant event cannot be confirmed, the processor 401 determines "NO" and proceeds to ACT 443. In ACT 443, the processor 401 checks whether a declaration of no product has been made. If the relevant event cannot be confirmed, the processor 401 determines "NO" and proceeds to ACT 444. In ACT 444, the processor 401 checks whether the customer CU has passed through the checkout lane LA. If the relevant event cannot be confirmed, the processor 401 determines "NO" and returns to ACT 442. Thus, in ACTs 442 to 444, the processor 401 waits for any of the following to occur: the scanning of the product barcode, the declaration of no product, or passage.

[0120] When the fixed scanner 406 or the handheld scanner 407 reads the product barcode, the processor 401 determines YES in ACT 442 and proceeds to ACT 445. In ACT 445, the processor 401 requests the POS server 700 to narrow down the search results, along with notification of the product code contained in the barcode information obtained by the fixed scanner 406 or the handheld scanner 407 by reading the product barcode. The processor 401 then returns to the standby state of ACT 424 to ACT 426 in FIG. 13.

[0121] Furthermore, in response to detecting an operation to declare that there are no products left on, for example, the touch panel 404, the processor 401 determines YES in ACT 443 and proceeds to ACT 446. In ACT 446, the processor 401 notifies the POS server 700 that there are no products left. Then, the processor 401 then returns to the standby state of ACT 424 to ACT 426 in FIG. 13.

[0122] In the POS server 700, the processor 701 requests notification of another product in ACT 737 in Fig. 22, and then proceeds to ACT 738. In ACT 738, the processor 701 checks whether narrowing down has been requested. If the processor 701 cannot check the relevant event, it determines "NO" and proceeds to ACT 739.

[0123] In ACT 739, the processor 701 checks whether a notification that there is no product has been received. If the processor 701 cannot confirm this event, it determines "NO" and proceeds to ACT 740. In ACT 740, the processor 701 checks whether a notification of erroneous passage has been received. If the processor 701 cannot confirm this event, it determines "NO" and returns to ACT 738.

[0124] Thus, the processor 701 waits for a narrowing-down request, a notification that there is no product, or a notification that the product has passed by mistake in ACT 738 to ACT 740. If a narrowing-down request is made as described above, the processor 701 determines YES in ACT 78 and proceeds to ACT 741.

[0125] In ACT 741, the processor 701 narrows down the multiple transactions found in the search in ACT 731 to transactions that include, as transaction items, both the product identified by the product code notified at the time of the inquiry and the product identified by the product code notified at the time of the narrowing request. The processor 701 then repeats ACT 734 and subsequent steps in the same manner as described above. Thus, if the processor 701 is unable to narrow down the transactions to one transaction in ACT 741, it repeats the narrowing down in ACT 741 while receiving a narrowing down request accompanied by notification of another product code. Note that when the processor 701 executes ACT 741 for the second or subsequent time, it narrows down the transactions to transactions that include, as transaction items, both the product identified by the product code notified at the time of the inquiry and multiple products identified by the product codes notified at each of the previous multiple narrowing down requests.

[0126] The termination condition confirmed by the processor 701 in ACT 736 is assumed to be, for example, when the number of products used to narrow down the transactions reaches a specified number. If the termination condition is met but the transactions cannot be narrowed down to one, the processor 701 determines YES in ACT 736 and proceeds to ACT 742. In other words, if there are multiple transactions that similarly include the specified number of products as transaction products, the processor 701 proceeds to ACT 742.

[0127] In ACT 742, the processor 701 notifies the accounting gate 400 of an error in response to the transaction inquiry. In other words, if the processor 701 cannot narrow down the transactions to one even when the termination conditions are met, it determines that an error has occurred and notifies the accounting gate 400. The processor 701 then ends the transaction search process.

[0128] If the processor 701 is notified of the absence of the product as described above, it determines YES in ACT 739 and proceeds to ACT 743. In ACT 743, the processor 701 narrows down the transactions that have been narrowed down so far to those whose transaction points match the number of transaction products used in the narrowing down process so far. The transaction points are indicated, for example, in the transaction header included in the transaction data.

[0129] In ACT 744, the processor 701 checks whether multiple transactions have been found by the above narrowing down. If the search has been narrowed down to one transaction, the processor 701 determines that there are not multiple transactions and returns NO, and proceeds to ACT 745. In ACT 745, the processor 701 notifies the accounting gate 400 of permission as a response to the transaction inquiry. In other words, if the search has been narrowed down to one transaction by the narrowing down in ACT 743, the processor 701 determines permission and notifies the accounting gate 400 of this. The processor 701 then ends the transaction search process.

[0130] If multiple transactions are found by the above narrowing down, the processor 701 determines YES in ACT 744 and proceeds to ACT 746. In ACT 746, the processor 701 notifies the accounting gate 400 of an error as a response to the transaction inquiry. In other words, if another transaction involving the exact same trading commodity as the trading commodity in the transaction that is the subject of this inquiry has been carried out during the search period, the processor 701 determines that an error has occurred and notifies the accounting gate 400 of this. Then, the processor 701 ends the transaction search process.

[0131] When the processor 401 at the accounting gate 400 receives the permission notification issued by the processor 701 at the POS server 700 in ACT 735 or 745 as described above, the processor 401 determines YES in ACT 425 in Fig. 13 and proceeds to ACT 427. In ACT 427, the processor 401 executes the passage permission process similar to ACT 413 in Fig. 12. Then, when the processor 401 completes the passage permission process, it returns to ACT 401 in Fig. 12.

[0132] When the processor 401 receives the error notification issued by the POS server 700 in ACT 733, ACT 742, or ACT 746 in Fig. 22 as described above, the processor 401 determines YES in ACT 426 in Fig. 13 and proceeds to ACT 428. In ACT 428, the processor 401 executes a call process. The call process is a process for calling a staff member (hereinafter referred to as the "supervisor") who is responsible for dealing with the error at the accounting gate 400, and receiving a response from that person.

[0133] FIG. 24 is a flowchart of the call processing by the processor 401 in the checkout gate 400 and the issuing processing by the processor 601 in the monitoring terminal 600. In ACT 461, the processor 401 initiates a call notification. The call notification is a notification to the customer CU that a store clerk is being called. For example, the processor 401 displays a call notification screen on the touch panel 404 to notify the call. For example, the processor 401 displays a warning screen on the display unit 405 to notify the call. For example, the processor 401 lights or flashes the lamp unit 410 in yellow to notify the call. For example, the processor 401 outputs a predetermined notification sound to the sound unit 411 to notify the call. Alternatively, the processor 401 may perform another operation, such as outputting a predetermined voice message to the sound unit 411 to notify the call. However, the processor 401 may execute only some of these processes for the purpose of notifying the passage permission.

[0134] Fig. 25 is a diagram showing an example of a calling screen. The calling screen shown in Fig. 25 is a screen showing a window WIB superimposed on a standby screen. The window WIB shows a text message for the above guidance. Fig. 26 is a diagram showing an example of a warning screen. The warning screen shown in Fig. 26 is a screen for warning the customer CU to prevent the customer CU from accidentally leaving the call.

[0135] As ACT 462 in FIG. 24, the processor 401 requests a predetermined request destination to issue a command. In this embodiment, the monitoring terminal 600 is assumed to be the destination of the command. The monitoring terminal 600 is installed, for example, at a service counter in 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 provide support when the POS terminal 200 is busy. The monitoring terminal 600 can also be used to respond to various requests from customer CUs, such as returns.

[0136] Now, when the processor 601 in the monitoring terminal 600 receives a notification request from the checkout gate 400 as described above, it executes the notification process shown in FIG. 24 in accordance with the monitoring program PRF. The processor 601, as ACT 601, initiates a notification operation. The notification operation is an operation for issuing a notification to a supervisor using the monitoring terminal 600 to address an error at the checkout gate 400. As the notification operation, the processor 601, for example, displays a notification screen on the clerk touch panel 604 to instruct the supervisor to address the error at that checkout gate 400 so that the supervisor can recognize which checkout gate 400 has requested the notification. As the notification operation, the processor 601, for example, outputs a predetermined notification sound to the sound unit 613. Alternatively, the processor 601 may perform another operation, such as outputting a predetermined voice message from the sound unit 613, as the notification operation. However, the processor 601 may execute only a part of these notification operations.

[0137] After the processor 401 at the accounting gate 400 requests issuance in ACT 462, the process proceeds to ACT 463. In ACT 463, the processor 401 waits for the supervisor to start an operation.

[0138] In response to the issuance of a notice on the monitoring terminal 600, the supervisor goes to the accounting gate 400 and performs an operation that is predetermined as something that a supervisor should perform. In response to such an operation, the processor 401 determines YES in ACT 463 and proceeds to ACT 464. In ACT 464, the processor 401 performs authentication processing to confirm that the operator is the supervisor. This authentication may be a well-known process for authenticating an operator. If the authentication is successful, the processor 401 proceeds to ACT 465.

[0139] In ACT 465, the processor 401 performs a transaction confirmation process to have the person in charge confirm that the transaction of the customer CU currently using the checkout gate 400 has been settled. In this transaction confirmation process, the processor 401, for example, displays a transaction confirmation screen showing the details of the settled transaction on the touch panel 404. Then, the processor 401 receives, for example, designation from the person in charge as to which of the settled transactions the current transaction of the customer CU in question is.

[0140] In ACT 466, the processor 401 stops the call-in-progress notification. In ACT 467, the processor 401 notifies the monitoring terminal 600 of the completion of the response. Then, the processor 401 ends the current call processing, proceeds to ACT 427 in Fig. 13, and executes the passage permission processing in the same manner as described above.

[0141] After the processor 601 in the monitoring terminal 600 starts the issuance operation in ACT 601, the process proceeds to ACT 602. In ACT 602, the processor 601 waits for a completion notification. When the processor 601 receives a completion notification from the accounting gate 400 as described above, the processor 601 determines YES and proceeds to ACT 603. In ACT 603, the processor 601 stops the issuance operation. The processor 601 then ends this issuance process.

[0142] If the barcode scanned at the checkout gate 400 while the standby screen is displayed is a receipt barcode, the processor 401 determines YES in ACT 422 of FIG. 13 and proceeds to ACT 429. In ACT 429, the processor 401 checks whether the scanned receipt barcode is valid for exit checks using the checkout gate 400. The processor 401 checks whether the receipt barcode meets predetermined conditions and determines that the receipt barcode is valid if it does. For example, the above condition may be that the receipt barcode is installed in the same store as the checkout gate 400 and is related to a transaction processed by a device other than a POS terminal included in the rejection list data DAB. However, the condition may be determined as appropriate by the person who determines the specifications of the product sales system 1 or the store manager. For example, only one of the above two conditions may be satisfied. Alternatively, another condition may be added, such as the time elapsed since the completion of the transaction related to the receipt barcode is less than a specified time. If the processor 401 determines that the receipt barcode is valid, it selects YES and proceeds to ACT 430. In this embodiment, the processor 401 proceeds to ACT 430 when it reads a receipt code related to a transaction processed for payment by the POS terminal 300, the checkout gate 400, or the monitoring terminal 600. After completing the payment, the customer CU can have the fixed scanner 406 or the handheld scanner 407 read the receipt barcode. In other words, confirming that the read receipt barcode is related to a transaction processed by a device installed in the same store as the checkout gate 400 is equivalent to confirming that the payment has been completed. Thus, by the processor 401 executing information processing based on the gate control program PRD, the computer with the processor 401 as its core functions as a confirmation unit.

[0143] In ACT 430, the processor 401 inquires of the POS server 700 about 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 in the POS server 700 receives the inquiry about the exit status, it executes information processing (hereinafter referred to as the exit confirmation processing) based on the transaction management program PRG.

[0144] FIG. 27 is a flowchart of the exit confirmation process. In ACT 751, the processor 701 confirms whether the customer CU related to the transaction identified by the notified transaction code has not yet exited the store. For example, the processor 701 searches the transaction database DBA for transaction data related to the transaction identified by the notified transaction code and confirms whether the exit data included in the transaction data indicates that the customer CU has not yet exited. If the exit data indicates that the customer CU has not yet exited, the processor 701 determines YES as the customer CU has not yet exited the store and proceeds to ACT 752. In ACT 752, the processor 701 notifies the checkout gate 400 that originated the inquiry about the exit status that the customer CU 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 CU has not yet exited, the processor 701 determines that the customer CU has not yet exited the store and proceeds to ACT 753. In ACT 753, the processor 701 notifies the checkout gate 400 that made the inquiry that the customer has already exited, in response to the inquiry about the exit status. Then, after the processor 701 finishes the notification in ACT 752 or ACT 753, it ends this exit confirmation process.

[0146] At the accounting gate 400, the processor 401 makes an inquiry in ACT 430 in FIG. 13 and then proceeds to ACT 431. In ACT 431, the processor 401 checks whether it has been notified that the customer has not yet exited. If the processor 401 has been notified by the POS server 700 that the customer has not yet exited, the processor 401 determines YES in ACT 431 and proceeds to ACT 427, where it executes the passage permission process as described above. In this way, when the processor 401 determines YES in ACT 431 and proceeds to ACT 427, the processor 401 performs control to notify the customer if it has confirmed that the payment has been completed based on the code, in response to the receipt barcode (an example of a code) being read. Thus, by the processor 401 executing information processing based on the gate control program PRD, the computer with the processor 401 as its core functions as a control unit.

[0147] Now, if the processor 401 determines YES in ACT 431 and proceeds to ACT 427 as described above, when requesting an update of the exit data in ACT 454 in Fig. 17, it notifies the transaction code contained in the barcode information represented by the read receipt barcode. Upon receiving such a request, the processor 701 of the POS server 700 proceeds to, for example, ACT 722 in Fig. 21. In ACT 722, the processor 701 searches the transaction database DBA for transaction data identified by the notified transaction code, and updates the exit data contained in the corresponding transaction data to a state indicating that the transaction has been exited.

[0148] If the processor 401 cannot confirm that the scanned receipt barcode is valid for exit check using the checkout gate 400, it determines the scanned receipt barcode as invalid, determines NO in ACT 429 in FIG. 13 , proceeds to ACT 428, and executes the call process as described above. Thus, for example, if a receipt barcode related to a transaction processed by the POS terminal 300 is scanned, the barcode will not be allowed to pass through and a store clerk will be called. As a result, depending on the function of the processor 401 as a control unit, if the payment device that processed the transaction identified by the scanned code is not subject to exit control, no notification will be issued. Thus, the rejection list data DAB is an example of list data representing a list of POS terminals 200 that are not subject to exit control. The auxiliary memory unit 403 is an example of a memory unit.

[0149] Furthermore, if the processor 401 is notified by the POS server 700 that the customer has already left, as described above, it determines NO in ACT 431, proceeds to ACT 428, and executes the call process in the same manner as described above. Thus, when a receipt barcode is read for a transaction that confirms that the customer has left the store, the customer will not be allowed to pass through and will instead call a store clerk.

[0150] Meanwhile, when the processor 401 is in a standby state in ACT 402 to ACT 404 in Fig. 12, if a customer CU passes through the checkout lane LA and this is detected by the human presence sensor 409, the processor 401 determines YES in ACT 404 as a passage and proceeds to ACT 414. In ACT 414, the processor 401 executes an erroneous passage process.

[0151] On the other hand, when the processor 401 is in a standby state in ACT 442 to ACT 444 in Fig. 14, if a customer CU passes through the checkout lane LA and this is detected by the human presence sensor 409, the processor 401 determines YES in ACT 444 as a passage and proceeds to ACT 447. In ACT 447, the processor 401 notifies the POS server 700 of the erroneous passage. In ACT 448, the processor 401 executes erroneous passage processing.

[0152] When the processor 401 in the POS server 700 is in the standby state from ACT 442 to ACT 444 in Fig. 14, the processor 701 is in the standby state from ACT 738 to ACT 740 in Fig. 22. Therefore, when the processor 701 receives the notification of the erroneous passage, it determines YES in ACT 740 and ends the transaction search process.

[0153] 28 is a flowchart of the erroneous passage processing by the processor 401 in the accounting gate 400 and the warning processing by the processor 601 in the monitoring terminal 600. The erroneous passage processing is the procedure shown in FIG. 28 whether it is executed as ACT 414 in FIG. 12 or as ACT 448 in FIG. 14.

[0154] In ACT 471, the processor 401 initiates an erroneous passage notification. The erroneous passage notification is a notification to the customer CU and other people around the customer CU that the customer CU has passed through a checkout lane LA where passage is not permitted. For example, the processor 401 displays a first warning screen on the touch panel 404 to notify the erroneous passage. For example, the processor 401 displays a second warning screen on the display unit 405 to notify the erroneous passage. For example, the processor 401 lights or flashes the lamp unit 410 in red to notify the erroneous passage. For example, the processor 401 outputs a predetermined alarm sound from the sound unit 411 to notify the erroneous passage. Alternatively, the processor 401 may perform another operation, such as outputting a predetermined voice message from the sound unit 411 to notify the erroneous passage. However, the processor 401 may execute only a part of these operations to notify the erroneous passage. FIG. 29 is a diagram illustrating an example of the first warning screen. The second warning screen is, for example, a screen similar to the warning screen shown in FIG.

[0155] As shown in ACT 472 in Fig. 28, the processor 401 requests an alarm from a predetermined destination. In this embodiment, the monitoring terminal 600 is assumed to be the destination of the alarm request. When the processor 601 in the monitoring terminal 600 receives the alarm request from the accounting gate 400 as described above, it executes the alarm processing shown in Fig. 28 in accordance with the monitoring program PRF.

[0156] As ACT 611, the processor 601 starts alarm processing. The alarm processing is processing for issuing an alarm to the store clerk CL, who is responsible for monitoring using the monitoring terminal 600, regarding unauthorized passage through the checkout lane LA. For example, for the alarm processing, the processor 601 displays an alarm screen on the store clerk touch panel 604 to make the store clerk CL aware that unauthorized passage has occurred. For example, for the alarm processing, the processor 601 causes the sound unit 613 to output a predetermined alarm sound. Alternatively, for the alarm processing, the processor 601 may perform another operation, such as outputting a predetermined voice message from the sound unit 613. However, the processor 601 may execute only a part of these operations for the alarm processing.

[0157] In ACT 612, the processor 601 waits for the alarm cancellation condition to be met. The cancellation condition may be determined as appropriate by, for example, the person who determines the specifications of the product sales system 1 or the administrator of the monitoring terminal 600. The cancellation condition may be, for example, when a cancellation instruction is issued by a predetermined operation on the store clerk's touch panel 604 or keyboard 605. Alternatively, the cancellation condition may be when the duration of the alarm processing exceeds a predetermined time. If the cancellation condition is met, the processor 601 determines YES and proceeds to ACT 613. In ACT 613, the processor 601 stops the alarm processing. The processor 601 then ends the current alarm processing.

[0158] After requesting an alarm in ACT 472, the processor 401 at the checkout gate 400 proceeds to ACT 473. In ACT 473, the processor 401 waits for the erroneous passage notification termination condition to be met. The termination condition may be determined as appropriate, for example, by the person who determines the specifications of the product sales system 1 or the administrator of the checkout gate 400. For example, the termination condition may be when the duration of the erroneous passage notification exceeds a predetermined time. Alternatively, the release condition may be when an instruction to release the alarm processing is issued at the monitoring terminal 600. In this case, the processor 601 at the monitoring terminal 600 determines YES in ACT 612 as the release condition being met when the release instruction is issued, and notifies the checkout gate 400 that the release instruction has been issued around the time of ACT 613. Alternatively, the termination condition may be when a predetermined release operation is performed by a store clerk at the checkout gate 400. If the termination condition is met, the processor 401 determines YES and proceeds to ACT 474. In ACT 474, the processor 401 stops the erroneous passage notification. Then, the processor 401 ends the current erroneous passage process and returns to ACT 401 in FIG. 12.

[0159] As described above, the checkout gate 400 excludes customer CUs involved in transactions processed at the POS terminal 200 from its exit control. The checkout gate 400 does not allow them to pass through the checkout lane LA even if the customer CU has the receipt barcode for the transaction settled at the POS terminal 200 scanned. This allows the checkout gate 400 to appropriately guide a customer CU who has completed payment at the POS terminal 200 and exited the store, or another customer CU who has obtained a receipt discarded by such a customer, from re-entering the store and then exiting through the checkout lane LA using the receipt code for the transaction.

[0160] Additionally, 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 accounting gate 400 is able to confirm transactions in which the customer CU has been confirmed to have exited through the checkout lane LA using exit data, and will not allow the customer CU to pass through the checkout lane LA even if the customer CU has a receipt barcode read from a transaction in which the customer CU has been confirmed to have exited the store. This allows the accounting gate 400 to provide appropriate guidance to prevent customers from leaving the store using a receipt barcode that was used to properly exit through the checkout lane LA, or a receipt barcode that appears on a receipt that such a customer has discarded.

[0162] This embodiment can be modified in various ways, such as the following. Instead of using the rejection list data DAB, the determination of whether the payment device that settled the transaction associated with the read receipt barcode is exempt from exit control may be performed using other methods, such as those described below. For example, data indicating whether the transaction is exempt from exit control may be included in the barcode data represented by the receipt barcode, and that data may be referenced. Alternatively, for example, the receipt barcode code system or transaction number system may be different for transactions that are subject to exit control and those that are not, and the system used may be confirmed.

[0163] To confirm whether the payment has been completed, for example, the checkout gate 400 may inquire of the POS server 700 whether the payment for the transaction identified by the transaction code contained in the read barcode has been completed, and the processor 701 in the POS server 700 may then refer to the transaction database DBA. In this case, a computer with the processor 701 as its central component functions as the confirmation unit. Note that the confirmation unit function may also be realized by a computer provided in any information processing device other than the POS server 700.

[0164] The accounting gate 400 may be configured such that a device having the function of a cashier and a device having the function of a gate are separate entities.

[0165] A mechanism may be provided that can selectively physically block or open the checkout lane LA, and the opening and closing operation of the mechanism may be executed as one of the notifications.

[0166] The POS terminal 300 may be used to register the items to be transacted, and the transaction may be carried out at the transaction gate 400 .

[0167] The customer CU may omit touching the standby screen before reading the transfer code. Figure 30 shows a modified version of the gate control process. Note that Figure 30 only shows changes from Figures 12 and 13 in the gate control process, and the same processes are designated by the same reference numerals. After displaying the standby screen in ACT 401, the processor 401 transitions from the standby state of ACTs 402 to 404 in Figure 12 to the standby state of ACTs 402 and 404 in Figure 30. In other words, in this standby state, the processor 401 waits for a barcode scan or a person to pass by, but does not wait for a tap on the screen. The customer CU then points the reading port of the handheld scanner 407 toward 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. As a result, when barcode information is notified from the fixed scanner 406 or the handheld scanner 407, the processor 401 proceeds to ACT 481. In ACT 481, the processor 401 confirms whether the read barcode is a takeover code. If the processor 401 confirms that the barcode is a takeover code, it determines YES and executes ACT 407 and subsequent steps in the same manner as described above. If the processor 401 cannot confirm that the read barcode is a takeover code, it determines NO in ACT 481 and proceeds to ACT 421. The processor 401 executes ACT 421 and subsequent steps in the same manner as described above. Note that when implementing such a modification, it is preferable to also change the standby screen. FIG. 31 is a diagram showing an example of a standby screen suitable for this modification. The standby screen shown in FIG. 31 includes text messages MEA and MEC. That is, the standby screen shown in FIG. 31 displays the text message MEC instead of the text message MEB in the standby screen shown in FIG. 15. The text message MEC informs the customer CU that the transfer barcode should be read in order to start the settlement of the transaction product registered using the information processing terminal 500. Note that the illustration in the center of the standby screen shown in Figure 31 has also been changed to one that helps the customer CU imagine the operation of reading the barcode.

[0168] Some or all of the functions realized by each processor through information processing can be realized by hardware that executes information processing not based on a program, such as a logic circuit. Each of the above functions can also be realized by combining hardware such as the logic circuit with software control.

[0169] Each of the one or more circuits constituting the processing circuit executes one or more processes among the plurality of processes. When the processing circuit is composed of a single circuit, the single circuit executes all of the plurality of processes. When the processing circuit is composed of multiple circuits, each of the multiple circuits executes a part of the plurality of processes. The part of the plurality of processes may be one of the plurality of processes, or two or more of the plurality of processes. When the processing circuit is composed of multiple circuits, the multiple circuits may be included in a single device or may be distributed across multiple devices.

[0170] The program according to this embodiment may be transferred in a state where it is stored in a device, or may be transferred in a state where it is not stored in a device. In the latter case, the program may be transferred via a network, or may be transferred in a state where it is recorded on a recording medium. The recording medium is a non-transitory tangible medium. The recording medium is a computer-readable medium. The recording medium may be in any form, such as a CD-ROM or a memory card, as long as it is capable of storing the program and is computer-readable.

[0171] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims.

[0172] Some of the above-described embodiments may be expressed as follows: (1) A gate device comprising: a notification unit that notifies a customer that they are allowed to pass; a reading unit that reads an optically readable code; a confirmation unit that confirms whether the payment has been completed based on the code read by the reading unit; and a control unit that controls the notification unit to issue a notification when the confirmation unit confirms that the payment has been completed in response to the code being read by the reading unit, wherein the control unit does not cause the notification unit to issue a notification if a payment device that has performed processing for payment for a transaction identified by the code read by the reading unit is exempt from exit control. (2) The gate device described in (1), further comprising: a memory unit that stores list data that lists payment devices that are exempt from exit control, wherein the control unit does not cause the notification unit to issue a notification if the payment device that has performed processing for payment for the transaction identified by the code read by the reading unit is included in the list represented by the list data stored in the memory unit. (3) The gate device according to (1), wherein the control unit does not cause the notification unit to issue a notification when it is confirmed that the customer has already left the store based on the code read by the reading unit. (4) A program recording medium having recorded thereon an information processing program, wherein a computer provided in a gate device equipped with a notification unit that notifies the customer that they are allowed to pass and a reading unit that reads an optically readable code is made to function as: a confirmation function that confirms whether payment has been completed based on the code read by the reading unit; and a control function that controls the notification unit to issue a notification when it is confirmed by the confirmation function that payment has been completed in response to the code being read by the reading unit, and wherein the control function is configured to not cause the notification unit to issue a notification when a payment device that has performed processing for payment for a transaction identified by the code read by the reading unit is not subject to exit control.(5) A checkout system comprising: a notification unit that notifies a customer that they are allowed to pass; a reading unit that reads an optically readable code; a confirmation unit that confirms whether the payment has been completed based on the code read by the reading unit; and a control unit that controls the notification unit to issue a notification when the confirmation unit confirms that the payment has been completed, wherein the control unit does not cause the notification unit to issue a notification when the payment device that has processed the payment for the transaction identified by the code read by the reading unit is not subject to exit control.

Claims

1. A gate device comprising: a notification unit that notifies a customer that they are allowed to pass; a reading unit that reads an optically readable code; a confirmation unit that confirms whether payment has been completed based on the code read by the reading unit; and a control unit that controls the notification unit to issue a notification when the confirmation unit confirms that payment has been completed in response to the code being read by the reading unit; wherein the control unit does not cause the notification unit to issue a notification if the payment device that has processed payment for the transaction identified by the code read by the reading unit is not subject to exit control.

2. A gate device as described in claim 1, further comprising a memory unit that stores list data representing a list of payment devices that are not subject to exit control, wherein the control unit does not cause the notification unit to issue a notification if the payment device that performed processing for settlement regarding the transaction identified by the code read by the reading unit is included in the list represented by the list data stored in the memory unit.

3. The gate device according to claim 1, wherein the control unit does not cause the notification unit to issue a notification when it is determined that the customer has already left the store based on the code read by the reading unit.

4. A program recording medium having recorded thereon an information processing program that causes a computer installed in a gate device equipped with a notification unit that notifies a customer that they are allowed to pass through and a reading unit that reads an optically readable code to function as: a confirmation function that confirms whether payment has been completed based on the code read by the reading unit; and a control function that controls the notification unit to issue a notification when the confirmation function confirms that payment has been completed in response to the code being read by the reading unit, and that causes the control function to not cause the notification unit to issue a notification when the payment device that has processed the payment for the transaction identified by the code read by the reading unit is not subject to exit control.

5. A checkout system comprising: a notification unit that notifies a customer that they are allowed to pass; a reading unit that reads an optically readable code; a confirmation unit that confirms whether payment has been completed based on the code read by the reading unit; and a control unit that controls the notification unit to issue a notification when the confirmation unit confirms that payment has been completed, wherein the control unit does not cause the notification unit to issue a notification when the payment device that has processed payment for the transaction identified by the code read by the reading unit is not subject to exit control.

Images