Checkout system

Abstract

To reduce the risk that an article is left unpaid owing to missed registration.SOLUTION: According to an embodiment, there is provided a checkout system that includes a gate device provided facing a lane that a customer having finished a transaction at a store passes through, and also comprises detection means, determination means, and alarm means. The detection means detects a predetermined specific article approaching the gate device. The determination means determines that the specific article is not included in articles as objects of the transaction with the customer approaching the gate device. The alarm means generates an alarm on condition that the detection means detects the specific article approaching the gate device and the determination means determines that the specific article is not included.SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] FIELD OF THE INVENTION An embodiment of the present invention relates to a checkout system. [Background technology]

[0002] In stores where customers register items picked up from the sales floor as trading items and then pay for the registered trading items, some of the picked items may not be registered as trading items. For example, products placed on the bottom shelf of a two-tiered shopping cart often go unregistered. In view of these circumstances, it has been desired to reduce or prevent the risk of products remaining unpaid due to omission of registration. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2024-8708 Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a checkout system that can reduce the risk of products remaining unpaid due to incomplete registration. [Means for solving the problem]

[0005] An embodiment is a checkout system including a gate device provided facing a lane through which customers who have completed a transaction at a store pass, and the system includes a detection means, a determination means, and an alarm means. The detection means detects the proximity of a predetermined specific commodity to the gate device. The determination means determines that the specific commodity is not included in the commodity to be traded with a customer who has approached the gate device. The alarm means issues an alarm when the detection means detects the proximity of the specific commodity and the determination means determines that the specific commodity is not included. [Brief explanation of the drawings]

[0006] [Figure 1] 1 is an overall configuration diagram of a product sales system according to an embodiment. [Figure 2] 2 is a schematic diagram showing an example of the layout of a checkout counter in a store that has introduced the product sales system shown in FIG. 1. [Figure 3] FIG. 2 is a block diagram showing the main circuit configuration of the transaction processing device. [Figure 4] FIG. 2 is a block diagram showing the main circuit configuration of a POS terminal. [Figure 5] FIG. 2 is a block diagram showing the main circuit configuration of a POS terminal. [Figure 6] FIG. 2 is a block diagram showing the main circuit configuration of an accounting gate. [Figure 7] FIG. 2 is a perspective view showing the appearance of the checkout gate. [Figure 8] FIG. 2 is a block diagram showing the main circuit configuration of the information processing terminal. [Figure 9] FIG. 2 is a block diagram showing the main circuit configuration of the monitoring terminal. [Figure 10] FIG. 2 is a block diagram showing the main circuit configuration of the POS server. [Figure 11] FIG. 10 is a sequence diagram relating to transaction processing using an information processing terminal. [Figure 12] 10 is a flowchart of a gate control process. [Figure 13] 10 is a flowchart of a gate control process. [Figure 14] 10 is a flowchart of a gate control process. [Figure 15] 10 is a flowchart of a gate control process. [Figure 16] 10 is a screen showing an example of a standby screen to be displayed on a touch panel at the checkout gate. [Figure 17] FIG. 10 is a diagram showing an example of a standby screen displayed on a display unit at the checkout gate. [Figure 18] 10 is a flowchart of an alarm process. [Figure 19] 10 is a flowchart of an alarm process. [Figure 20] FIG. 10 is a diagram illustrating an example of a calling screen. [Figure 21] FIG. 10 is a diagram illustrating an example of a warning screen. [Figure 22] 10 is a flowchart of a passage permission process. [Figure 23] FIG. 10 is a diagram illustrating an example of a first guide screen. [Figure 24] FIG. 10 is a diagram illustrating an example of a second guidance screen. [Figure 25] Sequence diagram for processing a transaction using a POS terminal. [Figure 26] Sequence diagram for processing a transaction using a POS terminal. [Figure 27] 10 is a flowchart of a transaction search process. [Figure 28] 10 is a flowchart of a transaction search process. [Figure 29] 10 is a flowchart of call processing by a processor at an accounting gate. [Figure 30] 10 is a flowchart of an exit confirmation process. [Figure 31] 10 is a flowchart of a false passage process by a processor at an accounting gate and an alarm process by a processor at a monitoring terminal. [Figure 32] FIG. 10 is a diagram illustrating an example of a first warning screen. DETAILED DESCRIPTION OF THE INVENTION

[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] FIG. 1 is a diagram showing the overall configuration of a product sales system 1 according to this embodiment. Merchandise sales system 1 includes transaction processing device 100, POS (point-of-sale) terminals 200 and 300, checkout gate 400, information processing terminal 500, monitoring terminal 600, and 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 communication network 2. POS terminal 200 and checkout gate 400 can also communicate with electronic receipt server 3 via communication network 2. 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 terminal 500 are provided, in many cases, multiple terminals 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. As communication network 2, for example, a combination of a LAN, the Internet, and a mobile communication network is used. 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 of the layout of a checkout counter in a store that has introduced the product sales system 1. A customer CU shopping in a 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, which is a vehicle for transporting products in a store. 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, a smartphone, or a smartwatch. The information processing terminal 500 may be installed in a 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 to be transacted. Transaction processing device 100 registers the products to be transacted 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 that the checkout gate 400 they used for the transaction faces, and then 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 functions as an exit gate to control the passage of customer CUs 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 product 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 a 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 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 at 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 himself / herself, 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 using 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 fraudulent passage through the checkout lane LA. The POS server 700 manages transactions processed in the product sales system 1.

[0014] FIG. 3 is a block diagram showing the main circuit configuration of transaction processing device 100. As shown in FIG. Transaction processing device 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 line 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 unit to realize various functions of transaction equipment 100 in accordance with information processing programs such as an operating system and application programs.

[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 required 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, and control signal lines, 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 equipment 100 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 be stored in main storage unit 102.

[0020] FIG. 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-side touch panel 204, a keyboard 205, a fixed scanner 206, a handheld scanner 207, a payment terminal 208, a change unit 209, a receipt printer 210, a customer-side touch panel 211, a customer-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-side 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, the handheld scanner 207, the payment terminal 208, the customer-side touch panel 211, the customer-side display 212, and the sound unit 213 are provided in a scanner unit 299. However, some elements may be provided in the opposite units. Furthermore, some elements such as the store clerk touch panel and keyboard may be provided on both the main unit 298 and the scanner unit 299.

[0021] The functions of the processor 201, main memory unit 202, auxiliary memory unit 203, communication unit 214 and transmission path 215 are roughly equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104 and transmission path 105. However, auxiliary storage 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 the clerk CL touching the screen. The keyboard 205 is provided with a number of hard keys to allow the store clerk CL to easily operate the keyboard 205. The keyboard 205 allows the store clerk CL to input instructions by pressing these hard keys.

[0023] Fixed scanner 206 has a reading window facing the store clerk. Fixed scanner 206 captures an image of a product held in front of the reading window and recognizes barcode information represented by the barcode formed on the product through image processing. Fixed scanner 206 then outputs the barcode information to processor 201. Note that fixed scanner 206 may also use other types of well-known devices that optically read barcodes using reflected laser light. Fixed scanner 206 may also use other types of well-known devices that have the function of identifying products using object recognition technology from images of the products themselves obtained by capturing images of the products. The handy scanner 207 is held by the store clerk CL and optically reads a barcode placed in front of the reading port. The handy scanner 207 outputs 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 require 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 slot to a coin tray through the coin ejection slot. 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 slot from the banknote ejection slot. The banknote ejection slot holds the discharged banknotes with a portion of them exposed to the outside. 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, hereafter, receipt paper with a printed receipt image will be referred to as a paper receipt.

[0026] The customer-side touch panel 211 is provided facing the side where the customer CU stands when the transaction product is registered by the store clerk CL (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 touching the screen. 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 to display character strings, and displays a simpler screen than the customer-side touch panel 211. The sound unit 213 outputs sounds and voices for various guidance and warnings. As the sound unit, various well-known sound devices such as a voice synthesis device and a buzzer can be used alone or in combination.

[0027] The basic hardware of POS terminal 200 may be, for example, the hardware of another existing POS terminal. In this case, POS terminal 200 is generally transferred with transaction processing program PRB stored in auxiliary storage unit 203. However, the hardware of POS terminal 200 and transaction processing program PRB may be transferred separately without transaction processing program PRB stored in auxiliary storage unit 203. Transaction processing program PRB may be written into auxiliary storage unit 203 in response to an operator's operation. Alternatively, the hardware of POS terminal 200 and transaction processing program PRB may be transferred separately with a different version of an information processing program of the same type as transaction processing program PRB stored in auxiliary storage unit 203. Transaction processing program PRB may be written to auxiliary storage unit 203, replacing the information processing program already stored therein. Transaction processing program PRB may 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 .

[0028] FIG. 5 is a block diagram showing the main circuit configuration of the POS terminal 300. As shown in FIG. 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.

[0029] The functions of the processor 301, main memory unit 302, auxiliary memory unit 303, communication unit 312 and transmission path 313 are roughly equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104 and transmission path 105. However, auxiliary storage 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 a device provided in POS terminal 300.

[0030] The touch panel 304 is provided facing the side where the customer CU who operates the POS terminal 300 stands. The touch panel 304 displays a screen for presenting information to the customer CU. The touch panel 304 also allows the customer CU to input instructions by touching the screen. The functions of the keyboard 305, fixed scanner 306, handheld scanner 307, payment terminal 308, change unit 309, receipt printer 310, and sound unit 311 are generally the same as those of the keyboard 205, fixed scanner 206, handheld scanner 207, payment terminal 208, change unit 209, receipt printer 210, and sound unit 213. However, the keyboard 305, fixed scanner 306, handheld scanner 307, and payment terminal 308 are provided to simplify operation by the customer CU, and are primarily operated by the customer CU.

[0031] The basic hardware of POS terminal 300 can be, for example, the hardware of another existing self-service POS terminal. In this case, POS terminal 300 is generally transferred with transaction processing program PRC stored in auxiliary storage unit 303. However, the hardware of POS terminal 300 and transaction processing program PRC may be transferred separately without transaction processing program PRC stored in auxiliary storage unit 303. Transaction processing program PRC may be written into auxiliary storage unit 303 in response to an operator's operation. Alternatively, the hardware of POS terminal 300 and transaction processing program PRC may be transferred separately with a different version of an information processing program of the same type as transaction processing program PRC stored in auxiliary storage unit 303. Transaction processing program PRC may be written to auxiliary storage unit 303, replacing the information processing program already stored therein. Transaction processing program PRC may 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 .

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

[0033] The processor 401, main memory unit 402, auxiliary memory unit 403, communication unit 414 and transmission path 415 have roughly the same functions as the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104 and transmission path 105. However, auxiliary storage unit 403 stores gate control program PRD instead of transaction processing program PRA. Gate control program PRD is an application program that describes the information processing procedures of processor 401 for gate control processing, which will be described later.

[0034] The touch panel 404 displays a screen for presenting information to the operator who performs the transaction. The touch panel 404 also allows the operator to input instructions by touching the screen. The operator of the transaction gate 400 is usually a customer CU. However, there are also cases where the store clerk CL operates the transaction gate 400.

[0035] The display unit 405 displays a screen for presenting 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.

[0036] 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. The handy scanner 407 is held by the customer CU and optically reads a barcode placed in front of the reading port. The handy scanner 407 outputs barcode information represented by the read barcode to the processor 401.

[0037] The receipt printer 408 prints an image of a receipt, invoice, sales slip, or other voucher onto receipt paper. The receipt printer 408 then ejects the receipt paper with the image printed on it from the receipt ejection port. In other words, the receipt printer 408 is used to issue paper receipts. The human presence sensor 409 detects customers CU passing through the checkout lane LA. As the human presence sensor 409, a well-known detection device such as an optical sensor or an infrared sensor can be used as appropriate.

[0038] The lamp unit 410 indicates whether the customer CU is permitted to pass through the checkout lane LA. The sound unit 411 outputs sounds and voices for various guidance and warnings regarding the customer CU passing 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.

[0039] The image processing unit 412 detects large items captured in the image acquired by the camera 413 by image processing. The type of items that the image processing unit 412 detects as large items may be determined as appropriate by the person who determines the specifications of the product sales system 1 or the store manager. For example, large items are assumed to be bulky or heavy items such as bulky items sold in cases or rice. The cart CA is assumed to be a multi-tiered cart with multiple product placement spaces. A typical example of a multi-tiered cart is a two-tiered cart with an upper placement space (hereinafter referred to as the upper space) and a lower placement space (hereinafter referred to as the lower space). In the case of this two-tiered cart, items picked up by customers from the sales floor are primarily placed in the upper space. The lower space is often used for placing large items that are too large or heavy to hold the product barcode over the fixed scanner 306 or that are difficult to lift up to the upper space. When registering products placed in the upper space as transaction items at the POS terminal 300, the products are often sequentially removed from the upper space and held over the fixed scanner 306 to read their product barcodes. When registering products placed in the lower space as transaction items at the POS terminal 300, the product barcodes are often read using the handheld scanner 307 while the products are still placed in the lower space. For this reason, products placed in the lower space are more likely to be overlooked as transaction items compared to products placed in the upper space. Therefore, it is preferable that the image processing unit 412 be configured to detect various products that may be placed in the lower space of the cart CA as large items. That is, the image processing unit 412 is expected to detect, for example, products whose external dimensions are larger than a predetermined standard dimension as large items. Alternatively, it is expected to detect, as large items, products whose appearance is similar to products whose weight is larger than the standard weight.In this embodiment, it is sufficient to be able to identify products included in large items with a high degree of accuracy, such as "case sales products" or "rice," and it is not necessary to identify with a high degree of accuracy which specific products the products are.

[0040] The image processing unit 412 may be, for example, a computer device separate from the computer mainly including the processor 401. The image processing unit 412 may use, for example, a large-scale language model (LLM) to perform processing to detect products predetermined as large items. Large items are an example of specific products.

[0041] The camera 413 is installed with a defined imaging range so that it can capture images of products placed in the lower space of the cart CA that is approaching the checkout gate 400 and about to proceed to the checkout lane LA. The camera 413 then outputs image data obtained by capturing images of the imaging range to the image processing unit 412. In other words, the camera 413 is an example of an imaging device. However, the camera 413 may also be installed with a defined imaging range so that it can, for example, capture an overhead image of the cart CA that is approaching the checkout gate 400 and capture images of products placed in the upper space of the cart CA. Furthermore, multiple cameras 413 may be installed with different imaging ranges. A camera unit installed independently of the checkout gate 400 may be used instead of the camera 413. Thus, image processing unit 412 functions as a detection means for detecting when a large item as a specific item approaches checkout gate 400 so that it comes within the range of camera 413 .

[0042] The accounting gate 400 is generally transferred with the gate control program PRD stored in the auxiliary storage unit 403. However, the hardware and the gate control program PRD may be transferred separately 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 the operation of any operator. 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] FIG. 7 is a perspective view showing the appearance of the accounting gate 400. In Fig. 7, the same elements as those shown in Fig. 6 are denoted by the same reference numerals. In the following description of Fig. 7, the left and right sides of Fig. 7 will be referred to as the front and rear, respectively.

[0044] The checkout gate 400 has a housing 450 in the shape of a substantially rectangular parallelepiped. The checkout gate 400 is installed with one side 451 of the housing 450 facing the checkout lane LA in order to control the movement of the customer CU in the direction of movement indicated by the arrow AR via the checkout lane LA. The side of the housing 450 facing the customer CU's movement direction is hereinafter referred to as the front side 452.

[0045] 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.

[0046] The touch panel 404 is attached 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 415 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 customer CUs 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. The camera 413 is attached to the side surface 451 so as to be exposed to the outside of the housing 450. The shooting direction of the camera 413 is adjusted to face the direction of the dashed arrow in the figure. That is, camera 413 is positioned so as to be able to photograph items placed in the lower space of cart CA, which is located close to checkout gate 400 from the front side in FIG. 7, in order to proceed to checkout lane LA. 6. The processor 401, main memory unit 402, auxiliary memory unit 403, sound unit 411, and communication unit 414 in FIG.

[0047] FIG. 8 is a block diagram showing the main circuit configuration of the information processing terminal 500. As shown in FIG. 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.

[0048] The processor 501 , main memory unit 502 , auxiliary memory unit 503 and transmission path 508 have roughly the same functions as the processor 101 , main memory unit 102 , auxiliary memory unit 103 , communication unit 104 and transmission path 105 . However, auxiliary storage 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 for causing information processing terminal 500 to function as a user interface for registering transaction commodities in transaction processing device 100.

[0049] The touch panel 504 displays a screen for presenting information to the operator. The touch panel 504 also allows the operator to input instructions by touching the screen. The operator of the information processing terminal 500 is usually a customer CU. However, the operator of the information processing terminal 500 may also be a store clerk CL. The sound unit 505 outputs sounds and voices for various 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.

[0050] 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 a product 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 the barcode.

[0051] The wireless communication unit 507 executes communication processing for wirelessly performing data communication via the communication network 2. For example, an existing wireless communication device for a wireless LAN can be used as the wireless communication unit 507. 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.

[0052] 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, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network. The terminal program PRE may be stored in the main storage unit 502.

[0053] FIG. 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 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.

[0054] 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.

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

[0056] 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 storing at least one of transaction processing program PRB and monitoring program PRF in auxiliary storage unit 603, or with a different version of the same application program stored in auxiliary storage unit 603. 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.

[0057] FIG. 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 roughly equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, communication unit 104 and transmission path 105. 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 to manage transactions processed by the product sales system 1. In addition, part of the memory 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 POS server 700 can be, for example, a general-purpose server device. POS server 700 is generally transferred with transaction management program PRG stored in auxiliary storage unit 703. However, the transaction management program PRG may be transferred separately from the hardware without transaction management program PRG stored in auxiliary storage unit 703, or with a different version of the same application program stored in auxiliary storage unit 703. POS server 700 may be configured by writing transaction management program PRG to auxiliary storage unit 703 in response to an operator's operation. 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. Transaction management program PRG may be stored in 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 explanation, in order to clearly explain the characteristic operations of this embodiment, explanation of some of the processes will be omitted. For example, if some kind of error occurs, processing may be performed to deal with the error, but a description of such processing will be omitted.

[0060] (Transaction processing using information processing terminal 500) FIG. 11 is a sequence diagram relating to the processing of a transaction using the information processing terminal 500. In transaction processing apparatus 100 and information processing terminal 500, processor 101 and processor 501 cooperate to perform registration processing as ACT101 and user interface processing as ACT501. As a result, processor 101 uses information processing terminal 500 as a user interface terminal and, while receiving instructions from a customer CU, registers products that the customer CU wishes to purchase as transaction products, and generates transaction data representing a list of transaction products. Note that the registration processing is, for example, processing in which the barcode of the product that the customer CU wishes to purchase is read by information processing terminal 500, or the customer CU operates a preset key that is set in advance for specifying a product displayed on information processing terminal 500, thereby adding the specified product as a transaction product.

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

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

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

[0064] (Exit control using handover code) On the other hand, when the processor 401 in the accounting 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. 12, 13, 14 and 15 are flowcharts of the gate control process. 12, the processor 401 displays a standby screen on the touch panel 404 and the display unit 405. The standby screen is a screen for guiding the operation to be performed by the customer CU while waiting for an operation by the customer CU.

[0065] FIG. 16 shows an example of a standby screen displayed on the touch panel 404. In FIG. 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. 16 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 scan the transfer barcode in order to begin payment for the transaction items registered using the information processing terminal 500. Note that a product barcode is a barcode that is displayed on a product and represents barcode information including a product code as an identifier for the product. A receipt barcode is a barcode that is displayed on a receipt and represents barcode information including a transaction code as an identifier for the transaction. Typically, one-dimensional barcodes are used as product barcodes and receipt barcodes. However, other types of optically readable codes, such as two-dimensional codes, may also be used as product barcodes and receipt barcodes. FIG. 17 is a diagram showing an example of a standby screen displayed on the display unit 405. As shown in FIG. The standby screen shown in FIG. 17 is a screen that prompts a customer CU who has completed payment for a transaction and is about to leave the store to scan a barcode.

[0067] 12, the processor 401 checks whether a barcode has been scanned. If the processor 401 cannot check the event, it determines "NO" and proceeds to ACT403. In ACT 403, 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 returns to ACT 402. Note that the "checkout lane LA" here and the "checkout lane LA" in the following explanation refer to the checkout lane LA facing the checkout gate 400 being explained. Thus, processor 401 waits for a barcode scan or a person to pass by as ACT 402 and ACT 403.

[0068] If multiple checkout gates 400 are installed, a customer CU using the information processing terminal 500 displaying the transfer screen on the touch panel 504 as described above will arbitrarily select one of the checkout gates 400 displaying the standby screen and have the handy scanner 407 read the transfer code. Alternatively, the customer CU may have the fixed scanner 406 or handy scanner 407 read the receipt barcode or product barcode. When barcode information is notified from the fixed scanner 406 or handy scanner 407, the customer CU determines YES in ACT402 and proceeds to ACT404.

[0069] The transfer code may be read by the fixed scanner 406. That is, for example, if the information processing terminal 500 is removable 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 placed opposite the fixed scanner 406. It is desirable that the transfer guidance screen contains content that guides the customer CU on expected ways of reading the transfer code.

[0070] In ACT 404, the processor 401 checks whether the read barcode is a takeover code. If the processor 401 cannot confirm this event, it determines NO and proceeds to ACT 405. In ACT 405, the processor 401 checks whether the read barcode is a product barcode. If the processor 401 cannot check this event, it determines "NO" and proceeds to ACT 406.

[0071] In ACT 406, 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 and ACT 403. At this time, the processor 401 may perform a guidance operation such as a screen display to guide the customer CU to read the transfer code, product barcode, or receipt barcode.

[0072] If it is confirmed that the read barcode is a takeover code, the processor 401 determines YES in ACT 404 and proceeds to ACT 411 in FIG. In ACT 411, processor 401 acquires the accounting data based on the handover data represented by the barcode information output from handy scanner 407. That is, processor 401 requests transaction data from transaction equipment 100, as shown in FIG.

[0073] When accounting data is requested from accounting gate 400, processor 101 in transaction processing device 100 proceeds to ACT103. In ACT 103, processor 101 checks whether any of the transaction items included in the transaction data for the transaction for which accounting data is requested are large items. For example, processor 101 determines that a large item is present if a large item flag is set in the product master database in association with the product code of any one of the transaction items included in the transaction data. The large item definition for each item in the product master database may be determined as appropriate by the person who determines the specifications for product sales system 1 or the store manager. The large item flag is set in the product master database for the product information for the item identified as a large item. For example, if image processing unit 412 detects "case sales items" and "rice" as large items, a large item flag is set in the product information for each of the various items belonging to the "case sales items" category and the "rice" category. However, even if a product belongs to the "rice" category, a small item, such as one with a content of 500 grams, may not have a large item flag set. If the processor 101 confirms that there is a large item, it proceeds to ACT 104. In this way, the processor 101 executes information processing based on the transaction processing program PRA, and the computer with the processor 101 as its central part functions as a determination means.

[0074] In ACT 104, processor 101 generates predetermined accounting data for accounting and settlement according to the transaction details represented by the transaction data for the transaction for which accounting data was requested. Processor 101 includes in this accounting data a large item flag indicating that a large item is included.

[0075] If the processor 101 cannot confirm that there is a large item, it determines NO in ACT103 and proceeds to ACT105. In ACT 105, processor 101 generates predetermined accounting data for accounting and settlement according to the transaction details represented by the transaction data for the transaction for which accounting data was requested. Processor 101 includes in this accounting data a large item flag set to a state indicating that there are no large items.

[0076] When the processor 101 finishes ACT 104 or ACT 105, it proceeds to ACT 106 in either case. In ACT 106, the processor 101 sends the accounting data generated in ACT 104 or ACT 105 to the requesting accounting gate 400. The processor 401 then receives the accounting data sent in this manner and received by the communication unit 414 at the accounting gate 400.

[0077] Once the processor 401 has acquired the accounting data in this manner, it proceeds to ACT 412 in FIG. In ACT 412, the processor 401 checks whether the image processing unit 412 has detected a large item.

[0078] The image processing unit 412 repeatedly performs image processing on the image data output by the camera 413, and determines whether or not there is a large item reflected in the image represented by the image data. The image processing unit 412 detects a large item when a large item is placed in the lower space of the cart CA close to the checkout gate 400. If the image processing unit 412 determines that a large item is present, it notifies the processor 401 that a large item has been detected. If the processor 401 has received such a detection notification, it determines YES in ACT412 and proceeds to ACT413.

[0079] In ACT 413, the processor 401 checks whether the transaction includes any large items. For example, if the large item flag included in the accounting data acquired in ACT 411 indicates that there are no large items, the processor 401 determines the answer as NO and proceeds to ACT 414. As ACT 414, processor 401 executes alarm processing. That is, processor 401 executes alarm processing when image processing unit 412 detects a large item even though the items being traded do not include such an item. Alarm processing is an operation to warn that a large item has been brought near checkout gate 400 even though the items being traded do not include such an item. In this way, by processor 401 executing information processing based on gate control program PRD, the computer with processor 401 as its central part functions as an alarm means.

[0080] 18 and 19 are flowcharts of the warning process. As ACT461 in FIG. 18 , 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 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 operations to notify the passage permission.

[0081] FIG. 20 is a diagram showing an example of the calling screen. The calling screen shown in Fig. 20 is a screen in which a window WIA is displayed overlaid on the standby screen. The window WIA displays the above-mentioned text message for guidance. FIG. 21 is a diagram showing an example of the warning screen. The warning screen shown in FIG. 21 is a screen for warning the customer CU to prevent the customer CU from accidentally leaving.

[0082] 18, the processor 401 requests an alarm to a predetermined request destination. In this embodiment, it is assumed that the monitoring terminal 600 is determined as the alarm request destination. The monitoring terminal 600 is installed, for example, at a service counter or checkout corner of a store. The monitoring terminal 600 performs transaction processing operations in the same manner as existing POS terminals of the same type. This allows the monitoring terminal 600 to be used to 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.

[0083] Now, when processor 601 in monitoring terminal 600 receives an alarm request from checkout gate 400 as described above, it initiates an alarm operation. This operation is to issue an alarm to the clerk (hereinafter referred to as the supervisor) in charge of monitoring using monitoring terminal 600, instructing the clerk to check the registration status of large items. As the alarm operation, for example, processor 601 displays an alarm screen on clerk-side touch panel 604 to instruct the clerk to check the registration status of large items for a customer waiting at that checkout gate 400, so that the clerk can recognize which checkout gate 400 has requested the alarm. As the alarm operation, processor 601, for example, causes sound unit 613 to output a predetermined alarm sound. Alternatively, processor 601 may perform another operation, such as outputting a predetermined voice message from sound unit 613, as the alarm operation. However, processor 601 may execute only a part of these alarm operations.

[0084] After the processor 401 at the accounting gate 400 requests an alert in ACT462, the process proceeds to ACT463. In ACT 463, the processor 401 waits for the supervisor to start an operation. In response to the alarm operation on the monitoring terminal 600, the person in charge goes to the accounting gate 400 and performs the operation that is predetermined as the operation that the person in charge should perform. In response to the performance of such an operation, the processor 401 determines YES in ACT463 and proceeds to ACT464. In ACT464, the processor 401 stops the call-in notification.

[0085] As ACT465, the processor 401 performs authentication processing to confirm that the operator is the responsible person.

[0086] The processing in ACT463 to ACT465 may be, for example, the processing described below. The "operation predetermined to be performed by the responsible person" in ACT 463 may be, for example, having the checkout gate 400 read the clerk barcode held by the clerk. In this case, in ACT 463, the processor 401 waits for the clerk barcode information held by the clerk to be input via, for example, the fixed scanner 406 or the handheld scanner 407. When the processor 401 detects that the information has been input, it determines YES. Furthermore, in ACT 465, the processor 401 checks whether the input information is the clerk barcode information of the responsible person, and if it determines that the information is the clerk barcode of the responsible person, it determines that the authentication has been successful.

[0087] Alternatively, the "operation predetermined to be performed by the manager" in ACT 463 may be, for example, an operation on touch panel 404 for inputting clerk identification information that identifies the clerk. In this case, in ACT 463, processor 401 waits for clerk identification information that identifies the clerk to be input via touch panel 404. Then, when processor 401 detects that clerk identification information has been input, it determines YES. Furthermore, in ACT 465, processor 401 checks whether the input clerk identification information is the clerk identification information of the manager, and if it determines that it is the clerk identification information of the manager, it determines that authentication has been successful.

[0088] Alternatively, the "predetermined operation to be performed by the responsible person" in ACT 463 may be, for example, a special input operation performed by the store clerk on the touch panel 404. The special input operation may be, for example, an input operation for specifying multiple predetermined areas on the touch panel 404, or an input operation for long-pressing a predetermined area on the touch panel 404. In this case, in ACT 463, the processor 401 waits for the special input operation on the touch panel 404. Then, upon detecting that the operation has been performed, the processor 401 determines "YES." In this case, in ACT 465, the processor 401 receives the input of the store clerk barcode or store clerk identification information again, and authenticates that the operator is the responsible person as described above based on the store clerk barcode or store clerk identification information. However, it is also possible to omit ACT 465 by determining that the authentication of the responsible person has been successful when the special operation has been performed. In either case, after the person in charge authentication is successful, the warning operation may be canceled, for example, by canceling the display of the window WIA superimposed on the standby screen. In other words, if YES is determined in ACT463, the process may proceed to ACT465 and then to ACT464. If the authentication is successful, the processor 401 proceeds to ACT 471 in FIG.

[0089] The processor 401 checks whether there is any acquired accounting data in ACT 471. When performing the alarm processing in ACT 414 in Fig. 13, the processor 401 determines YES in ACT 411 because the accounting data has already been acquired, and proceeds to ACT 472. In ACT 472, the processor 401 checks whether cancellation has been specified. If the processor 401 cannot confirm the event, it determines "NO" and proceeds to ACT 473. In ACT 473, the processor 401 checks whether additional registration has been specified. If the processor 401 cannot confirm the relevant event, it determines NO and proceeds to ACT 474.

[0090] In ACT 474, the processor 401 checks whether a hold has been specified. If the processor 401 cannot confirm the event, it determines "NO" and returns to ACT 472. Thus, the processor 401 waits for any of release, additional registration, or suspension to be designated as ACT472 to ACT474.

[0091] Once the manager confirms that a large item has not been registered and confirms the customer's intention to include the item in the transaction, the manager will specify whether to add the item or put it on hold using a predetermined operation. If the customer wishes to pay for the added item at checkout gate 400, the manager will specify whether to add the item. If the customer wishes to pay for the added item at a location other than checkout gate 400, such as POS terminal 300, 400 or monitoring terminal 600, the manager will specify whether to put the item on hold.

[0092] When the processor 401 confirms that a predetermined operation for specifying additional registration has been performed, it determines YES in ACT473 and proceeds to ACT475. In ACT 475, processor 401 executes user interface processing to cause transaction equipment 100 to perform registration processing while receiving instructions from the manager or customer CU. That is, in transaction equipment 100, processor 101 uses accounting gate 400 as a user interface terminal and adds and registers the commodity as a transaction commodity while receiving instructions from the manager or customer CU as ACT 107 in Figure 11. In this way, processor 101 executes information processing based on transaction processing program PRA, and the computer with processor 101 as its central part functions as an adding means. Then, upon completing the registration processing, processor 101 proceeds to ACT 108. As ACT108, the processor 101 generates accounting data based on the transaction data updated by the above registration process, and transmits it to the accounting gate 400.

[0093] When the processor 401 at the accounting gate 400 completes the user interface processing as ACT475 in FIG. 19, it proceeds to ACT476. In ACT 476, processor 401 obtains the accounting data transmitted from transaction processing device 100 as described above. In ACT477, the processor 401 notifies the monitoring terminal 600 of the completion of the response. Then, the processor 401 ends this alarm processing and proceeds to ACT415 in FIG.

[0094] After starting the alarm generation operation as described above, the processor 601 in the monitoring terminal 600 waits for a completion notification. Then, when the processor 601 receives a completion notification from the accounting gate 400 as described above, it stops the alarm generation operation. If processor 401 cannot confirm that image processing unit 412 has detected a large item, it determines NO in ACT 412 in Figure 13, passes ACT 414, and proceeds to ACT 415 without performing alarm processing. Also, if the large item flag included in the accounting data acquired in ACT 411, for example, indicates the presence of a large item, processor 401 determines YES in ACT 413, passes ACT 414, and proceeds to ACT 415 without performing alarm processing. Thus, in these cases, processor 101 at transaction processing equipment 100 does not perform ACT 107 or ACT 108, as indicated by the dashed lines in Figure 11, and processor 401 at accounting gate 400 does not perform ACT 475 or obtain accounting data, as indicated by the dashed lines in Figure 11.

[0095] As ACT 415 in FIG. 13 , the processor 401 performs accounting processing based on the acquired accounting data. That is, the processor 401 performs accounting processing to determine the payment amount for the transaction based on the acquired accounting data. This accounting processing may be similar to the processing performed by existing semi-self-service POS system accounting machines. The processor 401 then performs payment processing to settle the payment amount determined as described above. For example, the payment processing is assumed to be performed using electronic money provided by the store operator. In this case, the customer CU 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 checkout gate 400. Furthermore, electronic money payment provided by a payment service provider other than the store operator may be used for payment at the checkout gate 400. Depending on the payment method that is made available, additional devices not shown in FIG. 6 may be provided that are necessary for payment using that payment method.

[0096] In ACT416, 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 ACT417.

[0097] In ACT 417, the processor 401 issues a paper receipt that displays the transaction details, transaction results, etc., along with a receipt barcode. That is, the processor 401 generates a receipt image that displays, for example, the transaction details, transaction results, etc., along with 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.

[0098] On the other hand, if the processor 401 can confirm that an electronic receipt should be applied, it determines YES in ACT416 and proceeds to ACT418. As ACT418, 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.

[0099] After the processor 401 completes either ACT 417 or ACT 418, the processor 401 proceeds to ACT 419. In ACT 419, 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 109 in FIG.

[0100] In ACT 109, 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.

[0101] Upon receiving the above transaction data, the processor 701 in the POS server 700 proceeds to ACT 701 . As ACT 701, the processor 701 updates the transaction database DBA to include the above transaction data. After the processor 401 notifies the customer of the accounting result at the accounting gate 400 in ACT 419 in FIG. 13, the process proceeds to ACT 420. The processor 401 as the ACT 420 performs passage permission processing.

[0102] FIG. 22 is a flowchart of the passage permission process. In ACT491, the processor 401 starts a passage permission notification. The passage permission notification is a notification to let the customer CU and people around know that passage through the checkout lane LA is permitted. 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, causes the sound unit 411 to output a voice message such as "Please pass through the gate." Alternatively, to notify the passage permission, the processor 401 may perform another operation, such as causing the sound unit 411 to output a predetermined notification sound. However, the processor 401 may execute only some of these operations to notify the passage permission.

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

[0104] FIG. 24 is a diagram showing an example of the second guide screen. The second guidance screen shown in Fig. 24 includes a text message indicating that there is a limit to the time allowed to pass through checkout lane LA, and a number indicating the remaining time allowed to pass through checkout lane LA. The second guidance screen shown in Fig. 24 is an example when the remaining time is 10 seconds, and the number "10" indicates the remaining time. With regard to the second guidance screen, 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 during which passage through the checkout lane LA is permitted. Based on this screen, the customer CU can determine whether they should hurry through.

[0105] The processor 401 proceeds to ACT 492 while the passage permission notification is being sent. In ACT492, 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 ACT493. In ACT 493, the processor 401 checks whether a predetermined allowable time has elapsed since the processor 401 started issuing the passage permission notification in ACT 491. If the processor 401 cannot confirm the relevant event, it determines NO and returns to ACT 492. Thus, the processor 401 waits for a person to pass by or for the allowable time to elapse as ACT492 and ACT493.

[0106] If the customer CU passes through the checkout lane before the allowed time has elapsed, and the human sensor 409 detects the passage of a human, the processor 401 determines YES in ACT492 and proceeds to ACT494. In ACT 494, 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.

[0107] In ACT702 in FIG. 11, the processor 701 updates the exit data included in the transaction data included in the transaction database DBA in ACT701 to a state indicating that the transaction has been exited. 22, the processor 401 at the checkout gate 400 proceeds to ACT 495. 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 493, skips ACT 494, and proceeds to ACT 495. For example, even after completing the checkout, the customer CU may return to the sales floor without passing through the checkout lane LA, and in such a case the processor 401 will determine YES in ACT 493. The processor 401 stops the passage permission notification in ACT 495. Then, the processor 401 ends the passage permission process and returns to ACT 401 in Fig. 12 to prepare for handling the next customer CU.

[0108] Incidentally, when the person in charge designates suspension, the processor 401 determines YES in ACT474 in FIG. 19 and proceeds to ACT478. In ACT478, processor 401 requests transaction equipment 100 to suspend the transaction. Upon receiving this request, transaction equipment 100 cancels the state of waiting for the transaction to be completed at accounting gate 400, and transitions to a state of suspending processing related to the transaction.

[0109] In ACT 479, processor 401 issues a hold certificate. That is, processor 401 causes receipt printer 408 to print a hold certificate image in a predetermined form that includes a barcode representing information that enables identification of the transaction that has been placed on hold in transaction processing device 100 as described above. In ACT480, the processor 401 notifies the monitoring terminal 600 of the completion of the response. Then, the processor 401 ends the current alarm processing and ends the current gate control processing instead of proceeding to ACT415 in FIG.

[0110] When the customer CU receives the issued reservation certificate, the customer CU selects a POS terminal 300 that is in standby mode and causes the fixed scanner 306 or handheld scanner 307 of the POS terminal 300 to read the barcode shown on the reservation certificate. In response to this, processor 301 in POS terminal 300 obtains from transaction processing device 100 transaction data related to the transaction identified based on the information represented by the read barcode, and transitions to a state in which registration processing related to the transaction continues. Processor 301 then processes the transaction in response to the operation of the customer CU. That is, the customer CU operates POS terminal 300 to additionally register the product that was not registered as a transaction product, and then performs the transaction.

[0111] The responsible person may have the fixed scanner 606 or handy scanner 607 of the monitoring terminal 600 read the barcode shown on the reservation certificate. Then, the monitoring terminal 600 may perform the same processing as that performed by the POS terminal 300 described above in accordance with the operation of the responsible person.

[0112] (Transaction processing at POS terminal 200) FIG. 25 is a sequence diagram relating 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 process proceeds to ACT201.

[0113] In ACT201, the processor 201 registers the products that the customer CU wishes to purchase as transaction products in accordance with the operations of the store clerk CL using various devices of the POS terminal 200, and generates transaction data representing a list of the transaction products. Then, when the store clerk CL declares that the registration is complete, the processor 201 proceeds to ACT202.

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

[0115] In ACT203, 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 ACT204.

[0116] 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.

[0117] On the other hand, if the processor 201 can confirm that an electronic receipt should be applied, it determines YES in ACT203 and proceeds to ACT205. As ACT205, 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.

[0118] After completing ACT 204 or ACT 205, the processor 201 proceeds to ACT 206 in either case. As 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. Specifically, 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 designed the product sales system 1. However, the transaction data must be data that at least allows for determining the items transacted in the transaction. In this embodiment, customer CUs for 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. Therefore, the processor 201 does not include exit data in the transaction data. In other words, an existing face-to-face POS terminal may be used as the POS terminal 200.

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

[0120] (Transaction processing at POS terminal 300) FIG. 26 is a sequence diagram relating to the processing of a transaction using the POS terminal 300. In the POS terminal 300, when the processor 301 receives a designation to start registration through a predetermined operation by the customer CU, the process proceeds to ACT301.

[0121] In ACT 301, the processor 301 registers the products that the customer CU wishes to purchase as transaction products in accordance with operations by the customer CU using various devices of the POS terminal 300, and generates transaction data representing a list of the transaction products. For example, the processor 301 registers the products as transaction products when the customer CU has the fixed scanner 306 or handheld scanner 307 read the product's barcode, or when the customer CU operates a preset key displayed on the touch panel 304 or included in the keyboard 305 and associated with the product in advance. Then, when the customer CU declares that registration is complete, the processor 301 proceeds to ACT 302.

[0122] As ACT302, processor 301 performs accounting processing to count and settle the price according to the transaction details represented by the transaction data generated by ACT301. That is, processor 301 performs accounting processing to determine the payment amount for the transaction based on the generated transaction data, for example. Then, processor 301 performs payment processing to settle the payment amount determined as described above, for example. The payment processing may use various payment methods as appropriate, such as credit card payment, code payment, prepaid payment, point payment, gift certificate payment, or cash payment. The above registration and transaction processes may be the same as those performed by existing self-service POS terminals, for example. In this way, the POS terminal 300 has the function of a payment device.

[0123] 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.

[0124] 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.

[0125] On the other hand, if the processor 301 can confirm that an electronic receipt should be applied, it determines YES in ACT303 and proceeds to ACT305. In ACT305, 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.

[0126] After completing ACT 304 or ACT 305, the processor 301 proceeds to ACT 306 in either case. 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, 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. In this embodiment, customer CUs related to transactions processed by the POS terminal 300 are subject to exit control by the accounting gate 400. For this reason, the processor 301 includes exit data indicating that the customer has not yet exited in the transaction data.

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

[0128] (Exit control using product barcodes) As described above, if a customer CU who has completed payment at the checkout gate 400 but has not passed through the checkout lane LA within the allowed time wishes to leave the store without purchasing any additional items, the customer CU has the receipt barcode displayed on the paper receipt issued at the checkout gate 400 or the electronic receipt screen read by the fixed scanner 406 or handheld scanner 407 of any checkout gate 400 that is in standby mode.

[0129] A customer CU who has completed payment at the POS terminal 300 has the receipt barcode displayed on the paper receipt issued by the POS terminal 300 or on the electronic receipt screen read by a fixed scanner 406 or a handheld scanner 407 at any accounting gate 400 in a standby state. In cases where it is difficult for the customer CU to have the fixed scanner 406 or handheld scanner 407 read the receipt barcode due to various reasons, such as when the customer has lost the paper receipt issued by the checkout gate 400 or the POS terminal 300, or when the customer does not have a smartphone or the like and is unable to display the electronic receipt screen, the customer CU can also use the exit confirmation function by matching the transacted products. When using this function, the customer CU has the fixed scanner 406 or handheld scanner 407 read the product barcode of one of the transacted products for which payment has been made.

[0130] When the fixed scanner 406 or handy scanner 407 reads a barcode, it notifies the processor 401 of the barcode information represented by the barcode. As a result, the processor 401 determines YES in ACT 402, NO in ACT 404, and YES in ACT 405 in Fig. 12, and proceeds to ACT 431 in Fig. 14. In ACT 431, the processor 401 inquires about the transaction to the POS server 700 along with a notification of the product code contained in the barcode information obtained by reading the product barcode.

[0131] When the processor 701 in the POS server 700 receives the above-mentioned transaction inquiry, it executes information processing (hereinafter referred to as transaction search processing) based on the transaction management program PRG. 27 and 28 are flowcharts of the transaction search process. Hereinafter, when the term "accounting gate 400" is used in the explanation of the transaction search process, it refers to the accounting gate 400 that made the above inquiry.

[0132] 27, the processor 701 searches for transactions that include the product identified by the product code notified at the time of the inquiry as a transaction product from among past transactions for which settlement has been completed. For example, the processor 701 first searches for the following from among the transaction data contained in the transaction database DBA: · Relates to transactions made within a predetermined search period. - The products identified by the notified product code will be included as trading products. -Includes exit data indicating that the user has not yet left the device. Transaction data that matches certain conditions is extracted.

[0133] The search period is assumed to be a fixed time period, such as the most recent 10 minutes, for 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, a predetermined number of recent transactions may be searched for. In this case, the search period is the period during which the relevant number of transactions were made. The number of recent transactions is assumed to be 20, for example, 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.

[0134] In ACT 732, the processor 701 checks whether the relevant transaction was found through the above search. If the processor 701 is unable to extract any transaction data that matches the conditions in ACT 731, for example, it determines that there is no relevant transaction and the result is NO, and proceeds to ACT 733.

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

[0136] For example, if the processor 701 can extract even one transaction data that matches the conditions in ACT731, it determines that a corresponding transaction exists and returns YES in ACT732, and proceeds to ACT734. In ACT 734, the processor 701 checks whether multiple transactions have been found through the above search. If multiple transaction data matches the conditions in ACT 731, the processor 701 determines YES and proceeds to ACT 735.

[0137] In ACT 735, the processor 701 checks whether the narrowing-down termination condition is met. The termination condition may be determined as appropriate by the person who decides the specifications of the product sales system 1, the store manager, or the like. 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 736. In ACT 736, the processor 701 requests the accounting gate 400 to notify the customer of the other product.

[0138] At the accounting gate 400, the processor 401 inquires about the transaction in ACT 431 in FIG. 14, and then proceeds to ACT 432. In ACT 432, the processor 401 checks whether a notification of another product has been requested. If the processor 401 cannot check the relevant event, it determines NO and proceeds to ACT 433. In ACT433, the processor 401 checks whether a permission notice has been sent. That is, the processor 401 determines whether or not to receive a permission notice from the processor 701. If the processor 401 cannot confirm the event, it determines NO and proceeds to ACT434. In ACT 434, 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 432. Thus, the processor 401 waits for any one of a notification request, a permission notification, or an error notification in ACT 432 to ACT 434. Then, when a notification of another product is requested from the POS server 700 as described above, the processor 401 determines YES in ACT 432 and proceeds to ACT 435.

[0139] In ACT 435, the processor 401 checks whether the product barcode has been scanned. If the processor 401 cannot check this event, it determines "NO" and proceeds to ACT 436. In ACT 436, the processor 401 checks whether or not a declaration of no product has been made. If the processor 401 cannot confirm this event, it determines "NO" and proceeds to ACT 437. In ACT437, the processor 401 checks whether the customer CU has passed through the checkout lane LA. If the processor 401 cannot confirm this event, it determines NO and returns to ACT435. Thus, in ACT 435 to ACT 437, the processor 401 waits for the scanning of a product barcode, a declaration that the product is not available, or for the product to pass through. Note that while in this standby state, the processor 401 may display on the touch panel 404 an additional request screen that requests the customer CU to have the fixed scanner 406 or the handheld scanner 407 read the product barcode of a transaction product different from those that have been read so far.

[0140] When the product barcode is read by the fixed scanner 406 or the handheld scanner 407, the processor 401 determines YES in ACT435 and proceeds to ACT438. In ACT438, 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 reading the product barcode using the fixed scanner 406 or the handheld scanner 407. Then, the processor 401 returns to the standby state of ACT432 to ACT434.

[0141] In addition, when a predetermined operation to declare that no products are available, such as touching a button included in the additional request screen, is detected on the touch panel 404, the processor 401 determines YES in ACT436 and proceeds to ACT439. In ACT439, the processor 401 notifies the POS server 700 that there is no product. Then, the processor 401 then returns to the standby state of ACT432 to ACT434.

[0142] In the POS server 700, the processor 701 requests notification of another product in ACT736 in FIG. 27, and then proceeds to ACT737. In ACT 737, the processor 701 checks whether a narrowing down has been requested. If the processor 701 cannot check the relevant event, it determines "NO" and proceeds to ACT 738. In ACT 738, the processor 701 checks whether a notification that the product is out of stock has been received. If the processor 701 cannot confirm this event, it determines the result as NO and proceeds to ACT 739. In ACT 739, the processor 701 checks whether a false passage has been notified. If the processor 701 cannot confirm the event, it determines "NO" and returns to ACT 737. Thus, the processor 701 waits for a narrowing-down request, a notice that there is no product, or a notice that the product has passed by mistake in ACT 737 to ACT 739. If a narrowing-down request is made as described above, the processor 701 determines YES in ACT 737 and proceeds to ACT 740.

[0143] In ACT 740, the processor 701 narrows down the multiple transactions found in the search of 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 740, it repeats the narrowing down in ACT 740 while receiving a narrowing down request accompanied by notification of a further product code. Note that when the processor 701 executes ACT 740 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 product codes notified at each of the previous multiple narrowing down requests.

[0144] If the processor 701 is able to narrow down the transactions to one in ACT731 or ACT740, it determines NO in ACT734 and proceeds to ACT741. In ACT 741, the processor 701 checks whether the traded products related to the narrowed down transaction include a large-sized product. If a large-sized product is included, the processor 701 determines YES and proceeds to ACT 742. In this way, the processor 701 executes information processing based on the transaction management program PRG, and the computer with the processor 701 as its central part functions as a determination means. In ACT 742, the processor 701 notifies the accounting gate 400 of permission as a response to the transaction inquiry. Then, the processor 701 ends the transaction search process.

[0145] On the other hand, if there are no large items, the processor 701 determines NO in ACT741 and proceeds to ACT743. In ACT 743, the processor 701 notifies the accounting gate 400 of permission as a response to the transaction inquiry. Then, the processor 701 ends the transaction search process.

[0146] In other words, if the processor 701 can narrow down one transaction based on the above conditions, it decides to permit it and notifies the checkout gate 400. However, in ACT 742, the processor 701 includes a large item flag indicating that a large item is present in the data sent to notify permission. Also, in ACT 743, the processor 701 includes a large item flag indicating that a large item is not present in the data sent to notify permission.

[0147] The termination condition that the processor 701 checks in ACT 735 is assumed to be set, for example, as 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 735 and proceeds to ACT 744. In other words, if there are multiple transactions that have been carried out that similarly include the specified number of products as transaction products, the processor 701 proceeds to ACT 744.

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

[0149] If the processor 701 is notified that there is no product as described above, it determines YES in ACT 738 and proceeds to ACT 751 in FIG. In ACT 751, the processor 701 narrows down the transactions that have been narrowed down to those whose transaction points match the number of trading products used in the previous narrowing down. The transaction points are indicated, for example, in the transaction header included in the transaction data.

[0150] In ACT 752, the processor 701 checks whether multiple transactions have been found by the narrowing down process. If the narrowing down process has resulted in one transaction, the processor 701 determines that there are not multiple transactions and determines NO, and proceeds to ACT 753. In ACT 753, the processor 701 checks whether the traded products related to the narrowed down transaction include a large-sized product. If a large-sized product is included, the processor 701 determines YES and proceeds to ACT 754. In this way, the processor 701 executes information processing based on the transaction management program PRG, and the computer with the processor 701 as its central part functions as a determination means. In ACT 754, the processor 701 notifies the accounting gate 400 of permission as a response to the transaction inquiry. Then, the processor 701 ends the transaction search process.

[0151] On the other hand, if there are no large items, the processor 701 determines NO in ACT753 and proceeds to ACT755. In ACT 755, the processor 701 notifies the accounting gate 400 of permission as a response to the transaction inquiry. Then, the processor 701 ends the transaction search process.

[0152] That is, if the processor 701 narrows down one transaction by narrowing down in ACT 751, it decides to permit the transaction and notifies the accounting gate 400. However, in ACT 754, the processor 701 includes a large item flag indicating that a large item is present in the data sent to notify the permission. Also, in ACT 756, the processor 701 includes a large item flag indicating that a large item is not present in the data sent to notify the permission.

[0153] If multiple transactions are found as a result of the narrowing down in ACT751, the processor 701 determines YES in ACT752 and proceeds to ACT756. In ACT 756, the processor 701 notifies the accounting gate 400 of an error in response to the transaction inquiry. In other words, if another transaction involving the exact same trading product as the transaction that is the subject of this inquiry has occurred during the search period, the processor 701 determines that an error has occurred and notifies the accounting gate 400. The processor 701 then ends the transaction search process.

[0154] When the processor 401 at the accounting gate 400 receives a permission notification issued by the processor 701 at the POS server 700 in either ACT742, ACT743 in Figure 27, ACT754 or ACT755 in Figure 23 as described above, the processor 401 judges YES in ACT433 in Figure 14 and proceeds to ACT440. In ACT440, the processor 401 checks whether a large item has been detected by the image processing unit 412 in the same manner as in ACT412 in Fig. 13. If a large item has been detected, the processor 401 determines YES and proceeds to ACT441.

[0155] In ACT 441, the processor 401 checks whether the transaction includes any large items. For example, if the large item flag included in the data transmitted from the POS server 700 for permission notification indicates that there are no large items, the processor 401 determines the result as NO and proceeds to ACT 442.

[0156] In ACT442, the processor 401 executes the alarm processing shown in Fig. 18. At this time, the computer with the processor 401 as its central part functions as an alarm means. When the processor 401 finishes the alarm processing, it proceeds to ACT443. If the processor 401 cannot confirm that a large item has been detected by the image processing unit 412, it determines NO in ACT440 and skips ACT442, i.e., proceeds to ACT443 without performing alarm processing. Furthermore, if the large item flag included in the data transmitted from the POS server 700 for permission notification, for example, indicates the presence of a large item, the processor 401 determines YES in ACT441 and skips ACT442, i.e., proceeds to ACT443 without performing alarm processing. In ACT 443, the processor 401 executes the passage permission process in the same manner as in ACT 420 in Fig. 13. Then, when the processor 401 completes the passage permission process, the process returns to ACT 401 in Fig. 12.

[0157] As described above, when the processor 401 receives an error notification from the POS server 700 in ACT733, ACT744 in FIG. 27 or ACT756 in FIG. 28, the processor 401 determines YES in ACT434 in FIG. 14 and proceeds to ACT444. The processor 401 executes call processing as the ACT 444. The call processing is processing for calling a responsible person and receiving a response from the responsible person.

[0158] FIG. 29 is a flowchart of the call processing by the processor 401 in the accounting gate 400. In ACT4101, the processor 401 initiates a calling notification. The calling notification is a notification to the customer CU that a store clerk is being called. For the calling notification, the processor 401 causes the touch panel 404 to display, for example, a calling screen similar to that shown in FIG. 20. For the calling notification, the processor 401 causes the display unit 405 to display, for example, a warning screen similar to that shown in FIG. 21. For the calling notification, the processor 401 causes the lamp unit 410 to light up or flash yellow. For the calling notification, the processor 401 causes the sound unit 411 to output a predetermined notification sound. Alternatively, for the calling notification, the processor 401 may perform another operation, such as outputting a predetermined voice message from the sound unit 411. However, the processor 401 may execute only some of these operations for the passage permission notification.

[0159] 29, the processor 401 requests a predetermined request destination to issue a notice. In this embodiment, it is assumed that the monitoring terminal 600 is determined as the destination of the notice request. Now, when the processor 601 in the monitoring terminal 600 receives the request for issuing a notice from the accounting gate 400 as described above, it executes the issuing process in accordance with the monitoring program PRF. Processor 601 first initiates a notification operation. This notification operation is an operation for issuing a notification to a supervisor using monitoring terminal 600 to deal with an error at a checkout gate 400. As a notification operation, processor 601, for example, displays a notification screen on clerk-side touch panel 604 to instruct the supervisor to deal with the error at that checkout gate 400 so that it is possible to recognize which checkout gate 400 has requested the notification. As a notification operation, processor 601, for example, causes sound unit 613 to output a predetermined notification sound. Alternatively, processor 601 may perform another operation, such as outputting a predetermined voice message from sound unit 613, as a notification operation. However, processor 601 may execute only a part of these notification operations.

[0160] At the accounting gate 400, the processor 401 requests issuance in ACT4102, and then proceeds to ACT4103. As ACT 4103, the processor 401 waits for the supervisor to start an operation.

[0161] The person in charge goes to the accounting gate 400 in response to the issuance of a command on the monitoring terminal 600 and performs the operation that is predetermined as the operation that the person in charge should perform. In response to the performance of such an operation, the processor 401 determines YES in ACT4103 and proceeds to ACT4104. As ACT4104, the processor 401 performs authentication processing to confirm that the operator is the responsible person.

[0162] The processing in ACT4103 to ACT4105 may be, for example, the processing described below. The "operation predetermined to be performed by the responsible person" in ACT4103 may be, for example, having the checkout gate 400 read the clerk barcode held by the clerk. In this case, as ACT4103, the processor 401 waits for the clerk barcode information held by the clerk to be input via, for example, the fixed scanner 406 or the handheld scanner 407. When the processor 401 detects that the information has been input, it determines YES. Furthermore, as ACT4105, the processor 401 checks whether the input information is the clerk barcode information of the responsible person, and if it determines that the information is the clerk barcode of the responsible person, it determines that the authentication has been successful.

[0163] Alternatively, the "operation predetermined to be performed by the manager" in ACT4103 may be, for example, an operation on touch panel 404 for inputting clerk identification information that identifies the clerk. In this case, in ACT4103, processor 401 waits for clerk identification information that identifies the clerk to be input via touch panel 404. Then, when processor 401 detects that clerk identification information has been input, it determines YES. Furthermore, in ACT4105, processor 401 checks whether the input clerk identification information is the clerk identification information of the manager, and if it determines that it is the clerk identification information of the manager, it determines that authentication has been successful.

[0164] Alternatively, the "predetermined operation to be performed by the responsible person" in ACT4103 may be, for example, a special input operation performed by the store clerk on the touch panel 404. The special input operation may be, for example, an input operation of designating multiple predetermined areas on the touch panel 404, or an input operation of long-pressing a predetermined area on the touch panel 404. In this case, the processor 401 waits for the special input operation on the touch panel 404 as ACT4103. Then, upon detecting that the operation has been performed, the processor 401 determines "YES." In this case, the processor 401 receives the input of the store clerk barcode or store clerk identification information again as ACT4105, and authenticates that the operator is the responsible person as described above based on the store clerk barcode or store clerk identification information. However, the performance of the special operation may be deemed successful in authenticating the responsible person, and ACT4105 may be omitted. In either case, after successful person authentication, the warning operation may be cancelled, for example, by cancelling the display of the WIA window superimposed on the standby screen. In other words, if YES is determined in ACT4103, the process may proceed to ACT4105 and then to ACT4104. If the authentication is successful, the processor 401 proceeds to ACT4105.

[0165] In ACT4105, 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. In ACT 4106, the processor 401 stops the call-in notification.

[0166] In ACT4107, 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 ACT427 in Fig. 13, and executes the passage permission processing in the same manner as described above. When the processor 601 in the monitoring terminal 600 receives the completion notice from the accounting gate 400 as described above, the processor 601 stops issuing the notice, and the processor 601 then ends the issuing process.

[0167] (Exit control using receipt barcode) If the barcode read while the standby screen is displayed at the checkout gate 400 is a receipt barcode, the processor 401 determines YES in ACT 406 in FIG. 12 and proceeds to ACT 451 in FIG.

[0168] In ACT 451, the processor 401 checks whether the scanned receipt barcode is valid for exit check 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 conditions may be that the receipt barcode is installed in the same store as the checkout gate 400 and is related to a transaction where the payment was processed by a device other than a POS terminal designated as a refusal target. For example, the POS terminal 200 may be designated as a refusal target. However, the conditions 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 payment for 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 452.

[0169] In ACT 452, the processor 401 inquires of the POS server 700 about the exit status of the customer CU, along with notification of the transaction code included 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 as described above, it executes information processing (hereinafter referred to as exit confirmation processing) based on the transaction management program PRG.

[0170] FIG. 30 is a flowchart of the exit confirmation process. In ACT 761, the processor 701 checks whether the customer CU related to the transaction identified by the notified transaction code has not yet left 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 checks whether the exit data included in the transaction data indicates that the customer CU has not yet left. If the exit data indicates that the customer CU has not yet left the store, the processor 701 determines YES and proceeds to ACT 762.

[0171] In ACT 762, the processor 701 checks whether the traded products related to the identified transaction include a large-sized product. If a large-sized product is present, the processor 701 determines YES and proceeds to ACT 763. In this way, the processor 701 executes information processing based on the transaction management program PRG, and the computer with the processor 701 as its central part functions as a determination means. In ACT 763, the processor 701 responds to the inquiry about the exit status by notifying the accounting gate 400 that made the inquiry that the customer has not yet exited. Then, the processor 701 ends the exit confirmation process.

[0172] On the other hand, if there are no large items, the processor 701 determines NO in ACT762 and proceeds to ACT764. In response to the inquiry about the exit status, the processor 701 notifies the accounting gate 400 that made the inquiry that the customer has not yet exited, as ACT 764. The processor 701 then ends the exit confirmation process.

[0173] That is, if processor 701 can confirm that the transaction identified by the notified transaction code has not yet exited, it notifies checkout gate 400 that the transaction has not yet exited. However, in ACT 763, processor 701 includes a large item flag indicating that a large item is present in the data sent to notify that the transaction has not yet exited. Also, in ACT 764, processor 701 includes a large item flag indicating that a large item is not present in the data sent to notify that the transaction has not yet exited.

[0174] Furthermore, if the relevant exit data is not in a state indicating that the customer CU has not yet exited, the processor 701 determines NO in ACT761 as the customer CU has not yet exited the store, and proceeds to ACT765. In ACT 765, 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, the processor 701 ends this exit confirmation process.

[0175] After the processor 401 makes an inquiry at the accounting gate 400 as ACT 452 in FIG. 15, the process proceeds to ACT 453. In ACT 453, the processor 401 checks whether it has been notified that the customer has not yet exited. If it has been notified by the POS server 700 that the customer has not yet exited, the processor 401 determines YES and proceeds to ACT 454.

[0176] In ACT454, the processor 401 checks whether a large item has been detected by the image processing unit 412 in the same manner as in ACT412 in Fig. 13. If a large item has been detected, the processor 401 determines YES and proceeds to ACT455.

[0177] In ACT 455, the processor 401 checks whether there is a large item in the transaction items. For example, if the large item flag included in the data sent from the POS server 700 to notify that the transaction has not been completed indicates that there is no large item, the processor 401 determines the answer as NO and proceeds to ACT 456.

[0178] In ACT456, the processor 401 executes the alarm processing shown in Fig. 18. At this time, the computer with the processor 401 as its central part functions as an alarm means. When the processor 401 finishes the alarm processing, it proceeds to ACT457. If the processor 401 cannot confirm that a large item has been detected by the image processing unit 412, it determines NO in ACT454 and skips ACT456, i.e., proceeds to ACT457 without performing alarm processing. Furthermore, if the large item flag included in the data transmitted from the POS server 700 to notify that the user has not yet left is in a state indicating the presence of a large item, the processor 401 determines YES in ACT454 and skips ACT456, i.e., proceeds to ACT457 without performing alarm processing. In ACT 457, the processor 401 executes the passage permission process in the same manner as in ACT 420 in Fig. 13. Then, when the processor 401 completes the passage permission process, the process returns to ACT 401 in Fig. 12.

[0179] Now, when the processor 401 determines YES in ACT 453 as described above and proceeds to ACT 457, and requests an update of the exit data in ACT 494 in Fig. 22, 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. 26. 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 included in the transaction data to a state indicating that the transaction has been exited.

[0180] If the processor 401 cannot confirm that the read receipt barcode is valid for the exit check using the checkout gate 400, it determines that the read receipt barcode is invalid, determines NO in ACT 451 in Fig. 15, and proceeds to ACT 458 to execute the call process as described above. Thus, for example, if a receipt barcode related to a transaction processed by the POS terminal 300 is read, the process will not allow the customer to pass through and will call a store clerk.

[0181] Furthermore, if the processor 401 is notified by the POS server 700 that the customer has already left the store, the processor 401 determines NO in ACT 453, proceeds to ACT 458, and executes the call process in the same manner as described above. Thus, when a receipt barcode relating to a transaction that confirms that the customer has left the store is read, the processor 401 will not allow the customer to pass through and will call a store clerk.

[0182] Meanwhile, when the processor 401 is in a standby state in ACT402 and ACT403 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 that the customer has passed through as YES in ACT403 and proceeds to ACT407. In ACT 407, the processor 401 executes the erroneous passage process.

[0183] On the other hand, when the processor 401 is in a standby state from ACT435 to ACT437 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 that the customer has passed through as YES in ACT437 and proceeds to ACT447. In ACT 447, the processor 401 notifies the POS server 700 of the erroneous passage. As ACT448, the processor 401 executes the erroneous passage process.

[0184] When the processor 401 in the POS server 700 is in a standby state for ACT435 to ACT437 in Fig. 14, the processor 701 is in a standby state for ACT737 to ACT739 in Fig. 27. Therefore, when the processor 701 receives the above-mentioned notification of erroneous passage, it determines YES in ACT739 and ends the transaction search process.

[0185] FIG. 31 is a flowchart of the erroneous passage processing by processor 401 at accounting gate 400 and the warning processing by processor 601 at monitoring terminal 600. The incorrect passage process is the procedure shown in FIG. 31 whether it is executed as ACT 407 in FIG. 12 or as ACT 448 in FIG.

[0186] As ACT4111, 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 that is not permitted for passage. 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 some of these operations to notify the erroneous passage.

[0187] FIG. 32 is a diagram showing an example of the first warning screen. The second warning screen is, for example, a screen similar to the warning screen shown in FIG. As ACT4112 in Fig. 31, the processor 401 requests a predetermined destination to issue an alert. In this embodiment, it is assumed that the monitoring terminal 600 is specified as the destination of the alert request. Now, when processor 601 in monitoring terminal 600 receives an alert request from checkout gate 400 as described above, it starts the alert process. The alert process is a process for issuing an alert to store clerk CL, who is responsible for monitoring using monitoring terminal 600, regarding unauthorized passage through checkout lane LA. For example, to perform the alert process, processor 601 displays a screen on store clerk touch panel 604 to make store clerk CL aware of the unauthorized passage. For example, to perform the alert process, processor 601 outputs a predetermined alarm sound from sound unit 613. Alternatively, processor 601 may perform another operation, such as outputting a predetermined voice message from sound unit 613, for example. However, processor 601 may execute only a part of these operations for the alert process.

[0188] The processor 601 performs the alarm generation process while waiting for the conditions for canceling the alarm to be met. The conditions for canceling the alarm may be determined as appropriate, for example, by a person who determines the specifications of the product sales system 1 or an administrator of the monitoring terminal 600. The condition for canceling the alarm may be, for example, when a predetermined operation is performed on the touch panel 604 or keyboard 605 on the sales clerk's side to instruct cancellation. Alternatively, the condition for canceling the alarm generation process may be when the duration of the alarm generation process exceeds a predetermined time. If the condition for canceling the alarm is met, the processor 601 stops the alarm generation process.

[0189] Now, in the accounting gate 400, after the processor 401 requests an alert in ACT4112, the process proceeds to ACT4113. In ACT4113, the processor 401 waits for the termination condition for the erroneous passage notification 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 cancellation condition may be when an instruction to cancel the alarm processing is given at the monitoring terminal 600. In this case, the processor 601 at the monitoring terminal 600 notifies the checkout gate 400 that the cancellation instruction has been given. Alternatively, the termination condition may be when a store clerk performs a predetermined cancellation operation at the checkout gate 400. If the termination condition is met, the processor 401 determines YES and proceeds to ACT4114. In ACT 4114, the processor 401 stops the erroneous passage notification, and with this, the processor 401 ends the current erroneous passage process, and returns to ACT 401 in FIG.

[0190] (Effects of the embodiment) As described above, the product sales system 1 performs an alarm process and issues an alarm when a large item is placed in the lower space of a cart CA used by a customer CU about to pass through the checkout lane LA, but the items in the transaction for that customer CU do not include any large items. This reduces the risk of items remaining unpaid due to missed registration.

[0191] Furthermore, the product sales system 1 detects the proximity of a large product when a product designated as a large product is placed in the lower space of the cart CA that is close to the checkout gate 400. As a result, if there is a product that has been placed in the lower space of the cart CA and has not been registered, an alarm can be issued to prompt appropriate action.

[0192] Furthermore, the product sales system 1 does not check for a perfect match between the product detected by the image processing unit 412 and the product to be traded. Therefore, the image processing unit 412 only needs to detect the presence of a product defined as a large product, and can execute simpler processing than when identifying nearby products in detail.

[0193] Furthermore, the product sales system 1 detects that a large product is approaching when the large product is captured in the image obtained by the camera 413. Therefore, by adjusting the imaging range of the camera 413, it is possible to easily adjust the detection range of the large product so that it is limited to the lower space of the cart CA, for example, as described above.

[0194] Furthermore, after issuing an alarm, if the settlement of the transaction is not yet completed, the product sales system 1 can add the transaction product in response to an operation at the checkout gate 400.

[0195] (Transformation implemented) This embodiment can be modified in various ways as follows. The proximity of a specific product may be detected using various sensors such as an optical sensor or an ultrasonic sensor.

[0196] It is also possible to identify the product detected as a specific product and determine that the product is not included in the trading products.

[0197] For example, if the operation is such that a responsible person is placed so that the person in charge can notice the call notification initiated by the processor 401 as ACT461 in Fig. 18, this call notification may be treated as an alarm, and no alarm operation may be performed by the monitoring terminal 600, etc. In this case, the computer with the processor 401 as its central part will function as the alarm means.

[0198] To determine the settled transactions of a customer CU passing through the checkout lane LA at the checkout gate 400, it is possible to perform only one of reading the receipt barcode or narrowing down the search based on the product barcode. Alternatively, a membership code for identifying the customer may be associated with each transaction, and transactions associated with the membership code acquired at the checkout gate 400 may be searched for. Alternatively, the customer's biometric authentication data may be associated with transactions, and transactions associated with biometric authentication data that is identical to the biometric authentication data acquired at the checkout gate 400 may be searched for.

[0199] The function as the detection means may be provided in any device other than the accounting gate 400.

[0200] The transaction data may be acquired from the POS server 700 by any device such as the accounting gate 400, and the function of the determination means may be realized by that device.

[0201] Transaction data may be acquired from the POS server 700 by any device such as the accounting gate 400, and the device may function as an additional means.

[0202] 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.

[0203] Instead of or in addition to the checkout gate 400, a gate device that does not perform checkout processing may be used. The gate device then controls the passage of settled transactions through the checkout lane.

[0204] A mechanism may be provided that can selectively establish a state in which the checkout lane LA is physically blocked or not, and the opening and closing operation of the mechanism may be executed as one of the notifications.

[0205] 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 .

[0206] 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.

[0207] 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. [Explanation of symbols]

[0208] 1...product sales system, 2...communication network, 3...electronic receipt server, 100...transaction processing device, 200, 300...POS terminal, 400...accounting gate, 500...information processing terminal, 600...monitoring terminal, 700...POS server, 101, 201, 301, 401, 501, 601, 701...processor, 102, 202, 302, 402, 502, 602, 702...main memory unit, 103, 203, 303, 403, 503, 603, 703...auxiliary memory unit, 204, 604...store clerk side touch panel, 205, 305, 605...keyboard, 206, 3 06,406,606...Fixed scanner, 207,307,407,607...Handheld scanner, 208,308,608...Payment terminal, 209,309,609...Change unit, 210,310,408,610...Receipt printer, 211,611...Customer-side touch panel, 212,612...Customer-side display, 213,311,411,505,613...Sound unit, 304,404,504...Touch panel, 405...Display unit, 409...Human sensor, 410...Lamp unit, 412...Image processing unit, 413...Camera, 599...Barcode scanner.

Claims

1. A checkout system including a gate device provided facing a lane through which a customer who has completed a transaction in a store passes, a detection means for detecting the approach of a predetermined specific commodity to the gate device; a determination means for determining that the specific commodity is not included in the commodities to be traded with a customer approaching the gate device; an alarm means for issuing an alarm when the detection means detects the proximity of the specific commodity and the determination means determines that the specific commodity is not included; A checkout system equipped with

2. The detection means detects products placed below the top shelf of a multi-stage carrier used by customers to transport products. The checkout system of claim 1 .

3. The detection means detects proximity when any of a plurality of predetermined specific commodities is in proximity, the determination means determines that the specific commodity is not included when none of a plurality of predetermined specific commodities is included in the commodities to be traded with the customer approaching the gate device; The checkout system of claim 1 .

4. The detection means detects the specific product as being in proximity when the specific product is captured in an image obtained by the imaging device. The checkout system of claim 1 .

5. an adding means for adding a commodity to be traded with a customer who is close to the gate device after the alarm is issued by the alarm means; The checkout system of claim 1 further comprising:

Images