Transaction state monitoring device

Abstract

To enable a store side to grasp a state of a durative transaction in an article sales data processing system in which a custer uses a customer terminal device to perform article registration and also uses a checkout device for payment.SOLUTION: An article sales data processing system comprises a customer terminal device used by a customer to perform article registration corresponding to transaction units, and a transaction state monitoring device for performing processing related to monitoring of transaction. The transaction state monitoring device comprises display control means for displaying, based upon transaction information on which results of the article registration in the transaction units performed by the customer terminal device are reflected, durative transaction information presenting information related to durative transactions after the start of the article registration by the customer terminal device in response to the start.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present invention relates to a transaction status monitoring device. [Background technology]

[0002] BACKGROUND ART In a self-checkout system equipped with a plurality of self-checkout terminals, a technique is known in which an attendant terminal displays the operating status and error occurrence status of the self-checkout terminals (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-95026 Summary of the Invention [Problem to be solved by the invention]

[0004] A product sales data processing system is known in which, when shopping at a store, a customer registers products using their own smartphone or a customer terminal device loaned by the store, and then pays for the registered products using a payment device installed in the store. In such a merchandise sales data processing system, it is preferable that the store be able to grasp the status of ongoing transactions after merchandise registration has begun, using the customer terminal device by the customer.

[0005] The present invention has been made in consideration of the above circumstances, and aims to enable the store to grasp the status of ongoing transactions in a product sales data processing system in which customers register products using a customer terminal device and settle payments using a settlement device. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a transaction status monitoring device in a product sales data processing system that includes a customer terminal device used by customers to register products according to transaction units and a transaction status monitoring device that performs processing related to monitoring transactions, and the transaction status monitoring device is equipped with a display control means that displays ongoing transaction information that presents information related to transactions that are ongoing since the start of product registration by the customer terminal device, based on transaction information that reflects the results of product registration by transaction unit performed by the customer terminal device. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a diagram illustrating an example of the configuration of a shopping system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of installation of a settlement device according to the present embodiment. [Figure 3] 1 is a diagram showing an example of the appearance of a settlement device according to an embodiment of the present invention; [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a settlement device according to the present embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device according to the present embodiment. [Figure 6] 1 is a diagram illustrating an example of the configuration of a transaction management device according to an embodiment of the present invention. [Figure 7] 1 is a diagram illustrating an example of the configuration of a transaction status monitoring device according to an embodiment of the present invention. [Figure 8] 3A to 3C are diagrams illustrating examples of customer information, store information, and cart information according to the present embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of a definition of a reserved product in the present embodiment. [Figure 10] A sequence diagram showing an example of processing procedures executed by the customer terminal device, settlement device, and transaction management device in this embodiment in response to the accounting of one transaction in self-service operation. [Figure 11] FIG. 10 is a diagram showing an example of a screen of a shopping application in the present embodiment. [Figure 12]10A and 10B are diagrams showing an example of a registered product presentation screen and a screen displayed on the settlement device in this embodiment. [Figure 13] FIG. 10 is a diagram showing an example of an abnormal transaction list screen in this embodiment. [Figure 14] FIG. 10 is a diagram showing an example of a transaction details screen in the present embodiment. [Figure 15] 10A and 10B are diagrams illustrating an example of a transition of a product registration screen in response to release of a hold in the present embodiment. [Figure 16] FIG. 10 is a diagram showing an example of a hold release screen in the present embodiment. [Figure 17] 10 is a flowchart illustrating an example of a processing procedure executed by the transaction management device and the transaction status monitoring device in this embodiment in relation to displaying an ongoing transaction list screen. [Figure 18] 10 is a flowchart illustrating an example of a processing procedure executed by the transaction management device and the transaction status monitoring device in this embodiment in relation to the release of a hold at the registration stage. [Figure 19] FIG. 10 is a diagram showing an example of a registered product list screen displayed on the settlement device in this embodiment. [Figure 20] A figure showing an example of a settlement device operating status screen in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] <Embodiment> [Example of shopping system configuration] Fig. 1 shows an example of the configuration of a shopping system (an example of a product sales data processing system) according to this embodiment. The shopping system shown in Fig. 1 corresponds to a transaction (customer terminal-enabled transaction) in which, for example, a customer registers the product they are purchasing while taking it from a shelf using a customer terminal device 50, and then the same customer also pays for the registered product using a payment device 40. The transaction here refers to the procedure performed for one transaction, including product registration and payment for the registered product. The shopping system of this embodiment includes a management device 10, a transaction management device 60, a settlement device 40, a customer terminal device 50, a transaction status monitoring device 80, and a credit card settlement server 70.

[0009] The management device 10, settlement device 40, and transaction status monitoring device 80 are installed in the store and are connected to each other via a LAN 19 (which may be wired or wireless). The management device 10 is a business terminal used by store staff for store management, etc., and is capable of communicating with the transaction management device 60. The transaction status monitoring device 80 is a business terminal used in the store to monitor the transaction status of customers who register items using the customer terminal device 50. The transaction status monitoring function of the transaction status monitoring device 80 includes outputting information about the transaction status on the transaction status monitoring device 80 by displaying it, as well as controlling transactions, such as releasing the hold status of held items in response to a store staff member's operation, as described below. The transaction status monitoring device 80 is capable of communicating with the transaction management device 60, and is capable of realizing the transaction status monitoring function by exchanging data with the transaction management device 60. Although four payment terminals 40 are shown in FIG. 1, the number of payment terminals 40 within one store is not particularly limited.

[0010] The customer terminal device 50 is operated by a customer (such as a shopper who is a member of the store, hereinafter simply referred to as a customer). In addition to typical communication and imaging functions (camera), the customer terminal device 50 has a recognition function that scans barcodes attached to products to read product codes, i.e., recognizes barcodes attached to products. Note that the recognition function of the customer terminal device 50 is only required to be able to read product codes, and does not necessarily have to be able to recognize which product the read product code belongs to. In other words, the customer terminal device 50 is only required to be able to read a product code from a barcode when the barcode exists as an object in an image captured by the imaging function (an image acquired as a through image).

[0011] Such customer terminal device 50 may be a smartphone, tablet terminal, etc. owned by the customer. A shopping application having a function of registering products in accordance with the shopping system of this embodiment is installed on the smartphone, tablet terminal, etc. serving as customer terminal device 50.

[0012] Furthermore, customer terminal device 50 may be, for example, a terminal loaned to a customer by a store. An application having a function of registering products in accordance with the shopping system of this embodiment is also installed in customer terminal device 50 loaned to a customer by a store. Customer terminal device 50 loaned to a customer by a store may be one that is held by the customer or may be one that is attached to a shopping cart and used by the customer.

[0013] Furthermore, the customer terminal device 50 captures an image (e.g., releases the shutter) of the product (e.g., the surrounding area with the barcode attached) and generates the captured image (image data). The customer terminal device 50 may release the shutter in response to an operation by the customer who is the operator, but in this embodiment, it is preferable that the customer terminal device 50 releases the shutter at its own discretion.

[0014] Furthermore, the customer terminal device 50 may be equipped with an image recognition technology that extracts feature points from an image (through image, captured image) and recognizes the imaged subject (object, etc.). For example, the customer terminal device 50 may use the image recognition technology to identify (estimate) the captured product.

[0015] The settlement device 40 is a settlement device that can at least accept cash payments as a settlement method. The settlement device 40 is configured to be able to communicate with the transaction management device 60. Note that the settlement device 40 may be able to communicate with the transaction management device 60, for example, via a relay by the management device 10.

[0016] The transaction management device 60 manages transactions carried out in accordance with the shopping system of this embodiment.

[0017] The credit card payment server 70 executes payment processing corresponding to the credit card in response to a credit card payment request transmitted from the settlement device 40, the customer terminal device 50, etc.

[0018] [About the payment device] Figure 2 shows an example of the installation of the payment device 40. Figure 2(A) is a perspective view of the payment device 40 and other components as seen from the customer side. Figure 2(B) is a perspective view of the payment device 40 and other components as seen from the store clerk side. As shown in Figure 2(A), a counter is placed on the right side of the payment device 40 as seen from the customer side.

[0019] Figure 3 shows an example of the appearance of the settlement device 40. Figure 3(A) is a perspective view of the settlement device 40 as seen from the customer side. Figure 3(B) is a perspective view of the settlement device 40 as seen from the store clerk side. Fig. 4 is a diagram showing an example of the configuration of the settlement device 40. In Fig. 3 and Fig. 4, the same parts are given the same reference numerals.

[0020] An example configuration of settlement device 40 shown in Fig. 4 will be described below with reference to Fig. 3. Settlement device 40 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a customer display unit 405, a customer scanner unit 406, a card payment unit 408, a change dispenser 409, a store clerk display unit 410, a key operation unit 411, a store clerk scanner unit 412, a printing unit 413, an audio output unit 414, and a communication unit 415. These can communicate with each other via a bus.

[0021] The CPU 401 is a central processing unit that controls the operation of the settlement device 40 by reading and executing programs stored in the ROM 402 . The ROM 402 is a read-only memory that stores various types of information used by the CPU 401, including programs.

[0022] The RAM 403 is a read / write memory that stores various types of information, such as information read from the ROM 402 or the hard disk 404, information acquired from the outside, and information generated during processing.

[0023] The hard disk 404 stores various types of information. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Furthermore, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information obtained from the outside, information generated during processing, and the like.

[0024] The customer-side display unit 405 is a touch display for customers, which displays various information to customers and accepts various inputs from customers. Customer-side scanner unit 406 is a scanner unit for customers, and for example, scans a barcode attached to a product to read the product code. Customer-side scanner unit 406 may also scan a code (barcode, 2D code, etc.) printed on a receipt (registered trademark) to read the information required for payment. Customer-side scanner unit 406 may also scan a code (2D code, etc.) displayed on the display unit of customer terminal device 50 to read the information required for payment.

[0025] Although customer-side scanner unit 406 is used when a customer registers a product, the customer may register the product by other methods. For example, if a preset key (a button for ordering the product) corresponding to the product is displayed on customer-side display unit 405, the customer may operate (press) the preset key to register the product.

[0026] The card payment unit 408 is a payment mechanism that accepts various cards (credit cards, prepaid cards such as transportation cards, etc.). The card payment unit 408 of this embodiment includes a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient if it includes at least the card recognition unit. Note that the card recognition unit may also recognize various cards that are not directly used for payment (settlement) (for example, membership cards, point cards, etc.).

[0027] The change dispenser 409 (cash settlement unit) is a cash settlement mechanism that has an input port for banknotes and coins and an output port for banknotes and coins, calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and dispenses the change from the output port. The change dispenser 409 faces the customer and is operated by the customer. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, the number of coins by denomination, etc.).

[0028] That is, the change dispenser 409 is used when settling the price of registered products in cash (currency) in the settlement device 40. The change dispenser 409 has a banknote insertion slot for inserting banknotes, a coin insertion slot for inserting coins, a banknote discharge slot for discharging banknotes, a coin discharge slot for discharging coins, a counting unit for counting the inserted or discharged currency, a currency transport mechanism between the insertion slot or discharge slot and the storage unit, the above-mentioned sensor, etc. The banknote insertion slot and coin insertion slot are also referred to as deposit insertion slots. The banknote discharge slot and coin discharge slot are also referred to as change discharge slots. The banknote insertion slot and banknote discharge slot may be a common unit, and the coin insertion slot and coin discharge slot may be a common unit.

[0029] The change dispenser 409 also counts the coins replenished during the closing process and stores them in the storage unit. The change dispenser 409 also counts the coins to be dispensed during the closing process and discharges them from the change discharge port. The closing process is a process of adjusting the amount of money stored in the change dispenser 409 (cash on hand / cash on hand) to a reference amount after the store has closed or before it has opened.

[0030] The store clerk's display unit 410 is a touch display for the store clerk, and displays various information to the store clerk and receives various inputs from the store clerk. The key operation unit 411 is made up of various keys (buttons) and receives various inputs from the store clerk. The store clerk scanner unit 412 is a scanner unit for store clerks, and for example, scans barcodes attached to products to read product codes. The store clerk scanner unit 412 also scans barcodes attached to store clerk name tags to read store clerk codes.

[0031] Although the clerk-side scanner unit 412 is used when the clerk registers a product, the clerk may register the product by other methods. For example, if a key corresponding to a product (such as a key corresponding to a sports newspaper) is arranged on the key operation unit 411, the clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the clerk-side display unit 410, the clerk may operate that preset key to register the product.

[0032] The printing unit 413 prints and issues various media (receipts, bills, etc.). The printing unit 413 can be rotated to face from the store clerk side to the customer side, or from the customer side to the store clerk side (the direction of the media issuing port). The orientation of the printing unit 413 may be changed manually, or may be changed automatically (mechanically controlled, etc.) in response to, for example, a transition (switching) of the operating mode described below. The correct orientation of the printing unit 413 may be detected by a sensor or the like.

[0033] The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs audio guidance and the like. The communication unit 415 executes communication with other devices (other settlement devices 40 and management device 10).

[0034] In addition, the settlement device 40 of this embodiment can be switched between a total of four operating modes: a customer terminal-compatible settlement mode, which is set to process settlement based on customer terminal-compatible accounting, and three accounting modes (first to third accounting modes) corresponding to three different patterns of accounting (product registration, settlement). The first payment mode is an operating mode in which a store clerk performs product registration operations and operations corresponding to payment on the payment device 40. The second payment mode is an operating mode in which a store clerk performs product registration operations on the payment device 40, and a customer performs operations corresponding to payment on the same payment device 40. The third payment mode is an operating mode in which a customer performs product registration operations and operations corresponding to payment on the payment device 40. As a result, in a store that has introduced the shopping system of this embodiment, some of the multiple payment devices 40 can be set to customer terminal-compatible payment mode to enable customer terminal-compatible payment, and other payment devices 40 can be set to, for example, first or second payment mode so that a store clerk can handle the payment with the customer. Note that some of the other payment devices 40 may be set to third payment mode.

[0035] [Customer terminal device configuration example] 5 shows an example of the configuration of customer terminal device 50. Customer terminal device 50 in the figure includes a CPU 501, a storage unit 502, a RAM 503, a display unit 504, an operation unit 505, an imaging unit 506, and a network-compatible communication unit 507. The CPU 501 is a central processing unit that controls the operation of the customer terminal device 50 by reading and executing programs stored in the storage unit 502 . The storage unit 502 is an auxiliary storage device for the CPU 501, and stores various types of information used by the CPU 501, including programs. The RAM 503 is the main storage device of the CPU 501 . The display unit 504 displays images according to the display control of the CPU 501. The display unit 504 may be configured as a touch panel that allows operations to be performed on the screen. The operation unit 505 collectively indicates various operators provided on the customer terminal device 50 and various input devices connected to the customer terminal device 50 . The imaging unit 506 captures images under the control of the CPU 401. The imaging unit 506 of this embodiment can also function as a part that reads two-dimensional codes in a code reader that processes the two-dimensional codes. The network-compatible communication unit 507 is a unit that performs communication wirelessly via a network. The network-compatible communication unit 507 enables the customer terminal device 50 to communicate with the transaction management device 60.

[0036] [Example of transaction management device configuration] 6 shows an example of the configuration of transaction management device 60. Transaction management device 60 in the figure comprises a CPU 601, a storage unit 602, a RAM 603, and a network-compatible communication unit 604. The CPU 601 is a central processing unit that controls the operation of the transaction management device 60 by reading and executing programs stored in the storage unit 602 . The storage unit 602 is an auxiliary storage device for the CPU 601, and stores various types of information used by the CPU 601, including programs. The RAM 603 is the main storage device of the CPU 601 . The network-compatible communication unit 604 is a part that performs communication via a network.

[0037] The memory unit 602 of the transaction management device 60 stores customer information, store information, product information, and cart information.

[0038] [Example of configuration of transaction status monitoring device] 7 shows an example of the configuration of a transaction status monitoring device 80. The transaction status monitoring device 80 in the figure includes a CPU 801, a storage unit 802, a RAM 803, an in-store communication unit 804, a network-compatible communication unit 805, a display unit 806, and an operation unit 807. The CPU 801 is a central processing unit that controls the operation of the transaction status monitoring device 80 by reading and executing programs stored in the storage unit 802 . The storage unit 602 is an auxiliary storage device for the CPU 801, and stores various types of information used by the CPU 801, including programs. The RAM 803 is the main storage device of the CPU 801 . The in-store communication unit 804 communicates with terminals such as the settlement device 40 and management device 10 within the store via the LAN 19 . The network-compatible communication unit 805 is a component that communicates with the outside via a network. In the case of the transaction status monitoring device 80, the network-compatible communication unit 805 can communicate with the transaction management device 60 on the cloud. The display unit 806 displays an image under the control of the CPU 801. The display unit 806 may be configured as a touch panel. The operation unit 807 collectively indicates the operation keys provided in the transaction status monitoring device 80 and the input devices connected to the transaction status monitoring device 80 .

[0039] [Information stored in the transaction management device] The customer information stored in the memory unit 602 is information for managing individual customers. The transaction management device 60 generates customer information when a customer is registered (it may be considered that a customer has been registered when their customer information is stored). The transaction management device 60 also updates the customer information as appropriate based on cart information, etc. The transaction management device 60 may, for example, refer to the cart information at a predetermined time every day and update the customer information.

[0040] 8(A) shows an example of customer information stored in the memory unit 602 of the transaction management device 60. The customer information in this figure includes customer identification information, customer name, customer registration date, cancellation information, customer rank, number of points, etc. The customer identification information is identification information that uniquely identifies a customer. The customer identification information may be application identification information that is uniquely assigned to each installed shopping application when the shopping application of this embodiment is installed. The application identification information may be, for example, a number that is uniquely (e.g., sequentially) assigned to each installed shopping application. Alternatively, the application identification information may be terminal identification information that is unique to the customer terminal device 50 on which the shopping application is installed. The terminal identification information may be, for example, a telephone number assigned to a customer who is the user of the customer terminal device 50, or hardware identification information that is uniquely assigned to the hardware of the customer terminal device 50, such as a MAC (Media Access Control) address. The customer name is the customer's name or nickname, etc. The customer registration date is the date and time the customer was registered. The cancellation information is information regarding the cancellation of registered products after registration. The customer rank is a rank based on the customer's purchase history. When generating customer information for a new customer, the customer identification information, customer name, and customer registration date are generated, but since this is before the start of the actual transaction (product registration), other information (cancellation information, etc.) is not generated.

[0041] The transaction management device 60 generates and stores customer identification information, for example, when registering a customer (for example, when the customer terminal device 50 downloads or installs a shopping application from an external device (for example, a predetermined server that provides all applications, the transaction management device 60) to use the shopping service provided by the transaction management device 60).In addition, for example, when registering a customer, the transaction management device 60 acquires information entered in the name field of the registration form (input form) using the customer terminal device 50 and stores it as the customer name.In addition, for example, the transaction management device 60 acquires the current date and time when registering the customer and stores it as the customer registration date.

[0042] In addition, instead of or in addition to storing customer information in its own memory, the transaction management device 60 may store some or all of the customer information in another device (such as a file server accessible to the transaction management device 60).

[0043] 8(B) shows an example of store information stored in the memory unit 602 of the transaction management device 60. The store information in the figure includes store identification information, store name (branch name), store identification information 1, and store identification information 2. The store identification information is identification information that uniquely identifies a store. The store identification information shown in Fig. 8(B) is composed of a store (trade name) or company code and a branch code. The store name is the name of the store. The store name shown in Fig. 8(B) is composed of the store (trade name) or company and the branch name. The store identification information 1 is information on a two-dimensional code (QR code (registered trademark) or the like) for identifying a store where a transaction takes place (a store where a product is bought and sold). The store identification information 2 is store location information (GPS information) for identifying the store where the transaction is to be made. In the example shown in FIG. 8(B), the store identification information and the store specifying information 1 are different, but the store identification information and the store specifying information 1 may be the same.

[0044] The transaction management device 60 may acquire and store store information from an external source (such as a server (not shown) at a headquarters that oversees each store). The transaction management device 60 may also store some or all of the store information in another device (such as a file server accessible to the transaction management device 60) instead of or in addition to storing the store information in its own memory.

[0045] The product information is information acquired from, for example, the store management device 10, and is information about products sold in the store. The product information for one product includes information such as a product code (product identifier), product name, and price.

[0046] Cart information is information used to manage individual transactions. The transaction management device 60 generates cart information at the start of a transaction. The transaction management device 60 also updates the cart information as the transaction progresses (each time a product is registered) (it may be considered that a product has been registered when it is stored in the cart information).

[0047] FIG. 8(C) is an example of cart information stored in the memory unit 602 of the transaction management device 60. The cart information in the figure includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, reserved product information, cancellation information, and the like.

[0048] The cart identification information is identification information that uniquely identifies the cart information. For example, the cart identification information includes store identification information, a date, and a serial number (for example, a serial number for each store and date). The transaction start date and time is the date and time when the transaction started. The transaction start date and time may be, for example, the date and time when the cart information was created. The transaction start date and time may also be the date and time when the first item was registered (the date and time when the registered item information (registered item 1) in FIG. 8(C) was stored). The date and time when the cart information was created and the date and time when the first item was registered may both be stored separately.

[0049] The transaction end date and time is the end date and time of the transaction. For example, the transaction start date and time may be the settlement date and time. The customer identification information is customer identification information that identifies the customer of the transaction. When cart information is generated, cart identification information, transaction start date and time, and customer identification information are generated, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, etc.) is not generated. The settlement date and time may be the settlement start date and time or the settlement end date and time. Both the settlement start date and time and the settlement end date and time may be stored separately as the transaction end date and time.

[0050] Registered product information (total) is information that is updated each time a product is registered. Registered product information (total) includes the number of products (number of products), estimated subtotal amount (for example, the subtotal amount before discounts, etc. are reflected), subtotal amount, etc. Registered product information (registered product 1) is the registration information for one product item. Registered product information (registered product 2) is the registration information for two products. In the example shown in Figure 8 (C), registered product information (registered product 3) to registered product information (registered product 5) are omitted from the illustration. Registered product information (N; N is an integer) includes the product code, product name (product name), price, etc.

[0051] The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management device 60 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as information to determine whether or not to apply a special offer such as a limited time offer and the effect of applying the special offer.

[0052] The reserved product information (total) is information that is updated every time a reserved product is registered. A reserved product is a product that was not registered properly due to a specific reason and is registered in a temporarily reserved state. The reserved product information (total) includes the number of reserved products (number of products), the number of reserved products that are NO-FILE, and the number of reserved products that cannot be read (check for unauthorized operations).

[0053] NO-FILE refers to a product whose barcode or product code was successfully scanned (the product code was read) at the store, but the product code is not stored in the product information (a product whose product information is not registered).

[0054] A read NG refers to a failure to scan the product code at the store (the product code could not be read), or a product whose product code failed to be scanned at the store. In other words, a read NG refers to a timeout process when it is possible to determine that the barcode has not been recognized even after the product has been imaged for a certain period of time using image recognition technology, or a product that has been timed out. For example, if the barcode cannot be correctly acquired (recognized) even though the customer has performed the operation to read it due to wrinkles in the package, blurred or dirty barcode printing, or the barcode being printed on a transparent film, it will be determined that the barcode cannot be read.

[0055] Reserved Product Information (Reserved Product 1) is information on reserved product 1. Reserved Product Information (Reserved Product 2) is information on reserved product 2. Reserved Product Information (Reserved Product 3) is information on reserved product 3.

[0056] The reserved product information (reserved product N; N is an integer) includes the reserved product type (information indicating whether the reserved product is NO-FILE or cannot be read) and image data (image data captured when reading was NG). For example, if the Nth item is a reserved product due to NO-FILE, the reserved product information (reserved product N) includes the reserved product type "1 (NO-FILE)" and image data. Also, if the Nth item is a reserved product due to reading being NG, the reserved product information (reserved product N) includes the reserved product type "2 (Cannot be read)" and image data.

[0057] 9 shows an example of definition of reserved items corresponding to cart information in this embodiment. In this figure, an example is shown in which reserved items are classified into eight categories. Classification numbers "1" to "8" are assigned to each of the eight reserved item classifications. The classification of the reserved product with classification number 1 is "NO-FILE" as explained in FIG. The classification of the reserved product with classification number 2 is "reading not allowed" as explained in FIG.

[0058] The classification of the reserved product with classification number 3 is "pseudo scan input." A reserved product with "pseudo scan input" is a product for which the customer attempted to have the customer terminal device 50 read the product code, but the customer terminal device 50 was unable to read the code properly.

[0059] As a specific example, a "pseudo scan input" situation occurs when the product is brought into the imaging range of the imaging unit 506, but the product code is not included in the imaging range of the imaging unit 506. Furthermore, "pseudo scan insertion" corresponds to a situation in which the product is brought into the imaging range of the imaging unit 506, but an image of a part without a code is captured. Furthermore, "pseudo scan insertion" refers to a situation in which a product is placed within the imaging range of the imaging unit 506 with the code portion hidden by a finger or the like. In addition, a "pseudo scan input" situation occurs when the product code is captured by the imaging unit 506, but the product is passed through the imaging range of the imaging unit 506 at a speed that the customer terminal device 50 cannot read the code.

[0060] The classification of reserved items with classification number 4 is "non-scanned entry." Reserved items with "non-scanned entry" are items that were added to the shopping cart without performing an operation to position the item within the imaging range of imaging unit 506. This non-scanning insertion can occur, for example, when the customer terminal device 50 is fixedly attached to a shopping cart and is capable of capturing an image of the inside of a shopping basket placed in the shopping cart. For example, when the customer terminal device 50 determines, based on the captured image, that a product has been placed in the shopping cart even though the product code has not been scanned, it can determine that a non-scanning insertion has occurred.

[0061] The classification of reserved items with classification number 5 is "age verification items." "Age verification items" are items such as alcohol and tobacco that require a store clerk to verify the customer's age before selling them.

[0062] The classification of reserved goods with classification number 6 is "pharmaceuticals." "Pharmaceuticals" are goods that require a qualified person, such as a pharmacist, to ask the purchaser for confirmation.

[0063] The classification of reserved items with classification number 7 is "items with security tags." "items with security tags" are items that have security tags attached and therefore require a store clerk to remove the security tags from the items when they are sold.

[0064] The classification of reserved products with classification number 8 is "cancelled products." "Cancelled products" are products that were once registered but were canceled by a customer's cancellation operation on the customer terminal device 50. "Cancelled products" are taken from the customer by a store clerk, for example, at the time of payment.

[0065] Of the classification numbers 1 to 7, the three categories "NG Read," "Pseudo Scan," and "Non-Scan Insert" correspond to products for which the code was not read when the customer was registering on the customer terminal device 50.

[0066] In addition, instead of or in addition to storing the cart information in its own memory, the transaction management device 60 may store some or all of the cart information in another device (such as a file server accessible to the transaction management device 60).

[0067] [Example of basic processing procedure for self-operation] The sequence diagram in Figure 10 shows an example of the processing procedure executed by customer terminal device 50, settlement device 40, and transaction management device 60 in response to the accounting of one transaction in self-service operation. Specifically, the processing in Figure 10 shows an example of the processing of customer terminal device 50, settlement device 40, and transaction management device 60 from when a customer registers a product to be purchased from products displayed in the store until the payment for the registered product is completed.

[0068] Step S1: Customer terminal device 50 acquires information identifying the store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (for example, by outputting the two-dimensional code on a display screen or attaching a medium with the two-dimensional code printed on it), and a customer visiting the store may scan (read) the two-dimensional code with customer terminal device 50, thereby allowing customer terminal device 50 to acquire the store identification information. When a customer visiting the store launches a shopping application, a start-up screen may be displayed instructing the customer to scan the two-dimensional code. Alternatively, when a customer visiting the store scans the two-dimensional code with customer terminal device 50, the shopping application may be launched, and a start-up screen may be displayed informing the customer that the transaction management device 60 is currently connected.

[0069] Also, for example, since a store is identified by its location, a customer who visits the store may obtain location information (GPS information) at the store using the customer terminal device 50 (i.e., the store's location information may be obtained as store identification information). When a customer who visits the store starts a shopping application, the location information may be obtained, and a screen may be displayed as a startup screen informing the customer that the application is currently connected to the transaction management device 60. If multiple stores are detected from the location information and it is not possible to identify one, a selection screen may be displayed to allow the customer to make a selection. Alternatively, the application may be switched to a mode in which a two-dimensional code is forcibly obtained.

[0070] 11(A) shows an example of the start-up screen of the shopping application displayed on the display unit 504 of the customer terminal device 50. The start-up screen in the figure displays the store name. This store name is displayed based on the store-specific information acquired in step S1. When a customer wants to start registering a product for shopping, the customer operates a transaction start instruction button BT10 arranged on the start-up screen. In response to operation of the transaction start instruction button BT10, the customer terminal device 50 transmits a transaction start request including the acquired store identification information and customer identification information to the transaction management device 60. The transaction start request may be transmitted in response to a customer operation on the customer terminal device 50 as described above, or may be transmitted in response to the acquisition of store identification information without receiving any particular operation. Regarding customer identification information, the information entered in the name field of the registration form using the customer terminal device 50 during customer registration (when downloading or installing the shopping application on the customer terminal device 50) may be stored in the customer information of the transaction management device 60, but it may also be stored in the memory of the customer terminal device 50 in addition to the transaction management device 60. Note that when a store is identified (when the product registration initial screen described below is acquired), the store name, currently offered services (information on flyers being distributed that day), and available coupon information of the store may be displayed on a screen (the product registration initial screen or a screen separate from the product registration initial screen). Note that service and coupon information may be acquired from the transaction management device 60, for example, as screen information.

[0071] In addition, the destination information (address of the transaction management device 60) may also be obtained when registering the customer (when downloading or installing the shopping application to the customer terminal device 50) and stored in the memory of the customer terminal device 50. In addition, when scanning a two-dimensional code, the destination information may also be converted into a two-dimensional code in addition to the store identification information, and by scanning the two-dimensional code with the customer terminal device 50, the customer terminal device 50 may obtain the destination information along with the store identification information.

[0072] Step S2: The transaction management device 60, which has received the customer identification information and store identification information as a transaction start request from the customer terminal device 50, generates cart information for the transaction. Note that, in the initial state of the generated cart information, the cart identification information, transaction start date and time, and customer identification information are stored, but since the actual transaction (product registration) has not yet begun, other information (transaction end date and time, product information (registered product information, pending product information), etc.) is not stored.

[0073] As described above, the transaction management device 60 stores store information such as that shown in Figure 8(B), and therefore when it receives store identification information (although it also receives customer identification information) as a transaction start request from the customer terminal device 50, if the received store identification information is a two-dimensional code, it acquires the store identification information by referring to store identification information 1, and if the received store identification information is location information (GPS information), it acquires the store identification information by referring to store identification information 2. Note that if the store identification information received from the customer terminal device 50 is a two-dimensional code of the store identification information, the transaction management device 60 can simply acquire it as is.

[0074] In other words, when the transaction management device 60 receives customer identification information and store identification information from the customer terminal device 50 as a transaction start request, it acquires the store identification information from the store identification information received from the customer terminal device 50, acquires the current date, issues (assigns) a serial number, combines the store identification information with the current date and serial number, and stores the combined information as cart identification information in the cart information. Furthermore, when the transaction management device 60 receives store identification information and customer identification information from the customer terminal device 50 as a transaction start request, it acquires the current date and time and stores the current date and time as the transaction start date and time (generation date and time) in the cart information. Furthermore, when the transaction management device 60 receives store identification information and customer identification information from the customer terminal device 50 as a transaction start request, it stores the customer identification information received from the customer terminal device 50 as customer identification information in the cart information.

[0075] Step S3: The transaction management device 60, which has generated the cart information for the transaction, generates product registration initial screen information (screen information for the product registration screen, which is the initial screen) and transmits it to the customer terminal device 50. Specifically, the transaction management device 60, for example, generates product registration initial screen information and transmits the generated product registration initial screen information to the customer terminal device 50 together with cart identification information.

[0076] Step S4: The customer terminal device 50, which has received the cart identification information and the product registration initial screen information from the transaction management device 60, stores the cart identification information and displays the registration screen on the display unit. Specifically, the customer terminal device 50 displays the product registration initial screen, for example, as shown in Figure 11(B).

[0077] Step S5: In response to a customer's operation, the customer terminal device 50 scans the barcode attached to the product and reads the product code. In the figure, it is assumed that the barcode scan was successful. Steps S5 to S9 are repeatedly executed each time the barcode attached to the product is scanned.

[0078] The customer terminal device 50 that has acquired the barcode transmits to the transaction management device 60 the cart identification information and the product registration information including the product code obtained by scanning.

[0079] Step S6: Upon receiving product registration information (cart identification information and product code) from the customer terminal device 50, the transaction management device 60 identifies the cart information for the transaction from the cart identification information contained in the received product registration information.

[0080] Step S7: The transaction management device 60 updates the product data in the identified cart information. Specifically, if the received product registration information includes a product code for item N, the transaction management device 60 stores the product code as the product code of the registered product information (registered product N) in the identified cart information, obtains the product name and price corresponding to the product code from the product information, and stores them as the product and price of the registered product information (registered product N). The transaction management device 60 also updates the registered product information (total) in the identified cart information.

[0081] Step S8: After updating the product data in the cart information, the transaction management device 60 generates product registration update screen information (screen information of the product registration screen, which is the update screen to which the registered product has been added) and transmits it to the customer terminal device 50. Specifically, the transaction management device 60 generates product registration update screen information such that the customer terminal device 50 displays a product registration update screen to which the list item of the product currently registered in the registered product list has been added, as shown in Figure 11 (C), for example, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0082] The product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the customer terminal device 50 after "XX bread" has been registered as the third product item. In other words, when "XX yogurt" is stored in the cart information as the first item, the transaction management device 60 generates product registration update screen information such that "XX yogurt" is displayed on the customer terminal device 50 and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information; when "XX chocolate" is stored in the cart as the second item, the transaction management device 60 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed on the customer terminal device 50 and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information; and when "XX bread" is stored in the cart information as the third item, the transaction management device 60 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed on the customer terminal device 50 as shown in Figure 11 (C), and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0083] In response to the registration of one product, a registered product presentation screen WD1 may be displayed, presenting the currently registered product, as shown in Fig. 12(A), for example. Furthermore, the registered product presentation screen WD1 in the same figure shows an example in which, in response to the product being available for eating in, a "Yes" button BT1 and a "No" button BT2 are displayed to confirm with the customer whether or not they wish to eat in. In this case, the price of the product will be calculated so that the consumption tax rate for the product is different when the "Yes" button BT1 is operated and when the "No" button BT2 is operated.

[0084] Step S9: The customer terminal device 50, which has received the cart identification information and product registration update screen information from the transaction management device 60, adds the product to the registration screen. Specifically, the customer terminal device 50 displays a product registration update screen such as that shown in FIG. 11(C). As described above, the product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the customer terminal device 50 after "XX bread" has been registered as the third product item.

[0085] Step S10: The customer terminal device 50 accepts a payment instruction operation as an operation by the customer, for example, by touching the "Proceed to Checkout" button shown in FIG.

[0086] Step S11: The customer terminal device 50 that has accepted the payment transition instruction operation generates a two-dimensional code. That is, the customer terminal device 50 converts information (e.g., cart identification information) required to execute the payment process for the items purchased by the customer terminal device 50 into a two-dimensional code. The customer terminal device 50 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, a code display screen with a two-dimensional code arranged as shown in FIG. 11(D) is displayed on the display unit.

[0087] Step S12: The settlement device 40 scans (reads) the two-dimensional code displayed on the display unit of the customer terminal device 50. For example, the settlement device 40 scans the two-dimensional code displayed on the display unit of the customer terminal device 50 that is pointed by the customer within the recognition range of the customer-side scanner unit 406.

[0088] Step S13: The settlement device 40 reads the two-dimensional code displayed on the display unit of the customer terminal device 50 and requests the transaction management device 60 to calculate the subtotal. For example, the settlement device 40 sends a calculation request (subtotal calculation request information) to the transaction management device 60 requesting the calculation of the subtotal, together with the cart identification information obtained from the two-dimensional code.

[0089] Step S14: The transaction management device 60 receives the cart identification information and the sub-calculation request information from the customer terminal device 50 and identifies the cart information of the transaction from the cart identification information.

[0090] Step S15: After identifying the cart, transaction management device 60 calculates the subtotal amount using information such as prices in the registered product information included in the cart information corresponding to the identified cart information.

[0091] Step S16: After calculating the subtotal, the transaction management device 60 updates the cart information (storing the subtotal (calculated subtotal)) and sends the subtotal information indicating the calculated subtotal to the settlement device 40 together with the cart identification information.

[0092] Step S17: Upon receiving the cart identification information and subtotal information from the transaction management device 60, the settlement device 40 displays the subtotal amount on the customer side display unit 405, for example, as shown in FIG. 12(B).

[0093] Step S18: The settlement device 40, which has displayed the subtotal on the customer-side display unit 405, executes the payment (settlement). Specifically, the settlement device 40 accepts the selection of the payment type. In the case of cash, it accepts the deposit, calculates the amount of change, and, if there is change, dispenses the change and issues a receipt. Furthermore, when the settlement is complete, the settlement device 40 sends settlement completion information along with the cart information to the transaction management device 60, and the transaction management device 60 stores the transaction completion date and time (settlement date and time) for that cart.

[0094] After scanning a product, the customer terminal device 50 transmits the product code to the transaction management device 60 (S5). However, the customer terminal device 50 may be configured not to transmit product codes for products (e.g., products scanned at another store) other than those scanned within the store (the store where the customer visited and displayed the product registration initial screen). For example, the customer terminal device 50 acquires and stores location information (GPS information) when the customer visits the store (or when the product registration initial screen is displayed). The customer terminal device 50 also acquires location information when scanning each product and compares the location information acquired when the customer scanned the product with the location information acquired when the customer visited the store (or when the product registration initial screen is displayed). If the two information match (or approximately match), the customer terminal device 50 may permit the product code of the product to be transmitted to the transaction management device 60. If the two information do not match (or approximately match), the customer terminal device 50 may prohibit the product code of the product from being transmitted to the transaction management device 60. This makes it possible to prevent inappropriate product registration (for example, product registration to a cart created at another store, etc.).

[0095] When the payment terminal 40 prohibits the transmission of the product code as described above, after scanning the product, the payment terminal 40 may display an error message (e.g., "Registration is not possible because the product is not in the XX store") on the customer display unit 405. The payment terminal 40 may also display the above message on the clerk display unit 410 instead of or in addition to the message on the customer display unit 405.

[0096] Furthermore, after reading the two-dimensional code displayed on the display of the customer terminal device 50, the settlement device 40 requests the transaction management device 60 to calculate a subtotal (S13). However, the settlement device 40 may not request calculation of a subtotal for products other than those scanned in the store (e.g., products scanned at other stores). For example, the settlement device 40 references the store identification information of the store (it may store and reference the store identification information of the store in its own settlement device 40, or it may reference store identification information stored in another accessible device), and when it reads the two-dimensional code displayed on the display of the customer terminal device 50, it compares the cart identification information obtained from the two-dimensional code with the store identification information of the store. The settlement device 40 may then permit the request for calculation of a subtotal if the store identification information included in the cart identification information is configured to include the store identification information of the store, but may prohibit the request for calculation of a subtotal if it is not configured to include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payments for products registered at other stores, etc.).

[0097] When the payment settlement device 40 prohibits the request for the subtotal amount as described above, after reading the two-dimensional code, the payment settlement device 40 may display an error message (e.g., "Payment cannot be made because it includes products not from store X") on the customer-side display unit 405. The payment settlement device 40 may also display the above message on the clerk-side display unit 410 instead of or in addition to the message on the customer-side display unit 405.

[0098] In the example of the processing procedure in Figure 10, the transaction management device 60 calculates the subtotal. However, for example, the settlement device 40 may acquire cart information from the transaction management device 60 and calculate the subtotal based on the acquired cart information. Alternatively, the transaction management device 60 may send cart information to the management device 10 and request calculation of the subtotal, and the management device 10 may calculate the subtotal using the received cart information and send the calculated subtotal to the settlement device 40 via the transaction management device 60.

[0099] During the settlement process, the transaction management device 60 may check the cancellation status of the customer's products based on the customer information and cart information of the customer, and determine whether or not to issue a warning against fraud. If it is determined that a warning should be issued, the transaction management device 60 may, for example, cause the settlement device 40 to issue a warning notification.

[0100] Furthermore, during the checkout process, the transaction management device 60 may determine whether the product information included in the cart information includes any reserved items, and if so, may request the checkout device 40 to issue an instruction to correct the reserved items. Upon receiving the request to issue an instruction to correct the reserved items, the checkout device 40 displays a message indicating that there are reserved items, as shown in FIG. 12(C). Upon confirming the message, the store clerk may cancel (correct) the reserved items by entering the price corresponding to the reserved items or canceling the reserved items.

[0101] [About the transaction monitoring function of the transaction status monitoring device] In this embodiment, the transaction status monitor 80 is used to monitor ongoing transactions in a store. An ongoing transaction is a transaction that has reached a predetermined stage in the period from when a customer starts product registration using the customer terminal device 50 until the settlement is completed at the settlement device 40. Specifically, an ongoing transaction may be, for example, from the start of product registration in one transaction to the completion of settlement, or from the start of product registration in one transaction to the stage at which product registration is considered to be completed in response to a settlement transition instruction operation being performed. In the following explanation, an example will be given in which an ongoing transaction is defined as the period from the start of product registration in one transaction to the completion of settlement.

[0102] Ongoing transactions can be divided into normal transactions and abnormal transactions. A normal transaction is a transaction in which all product-specific registrations made using the customer terminal device 50 up to the present time have been made normally. An abnormal transaction is a transaction in which at least one product registration has been made abnormally among the product-specific registrations made using the customer terminal device 50 up to the present time. Product registrations that have not been made normally in abnormal transactions specifically include registrations that have been treated as pending products according to any of the classifications defined as shown in Figure 9. In other words, an abnormal transaction includes the registration of one or more pending products. Furthermore, abnormal transactions may include transactions (warning transactions) that are determined to be likely to be fraudulent by a customer when registering a product using the customer terminal device 50. Caution transactions may include, for example, transactions in which the number of times reserved products are registered due to false scan inputs or non-scan inputs exceeds a certain number. Caution transactions may also include, for example, transactions by members who have been designated as persons requiring caution because they have committed fraud in the past or are likely to have committed fraud.

[0103] The transaction status monitoring device 80 of this embodiment can display an ongoing transaction list screen showing a list of ongoing transactions on the display unit 806. In this embodiment, the transaction status monitoring device 80 can switch between three ongoing transaction list screens: an abnormal transaction list screen, an all transaction list screen, and a normal transaction list screen. The abnormal transaction list screen is a screen that shows a list of abnormal transactions among all ongoing transactions. The all transaction list screen is a screen that shows a list of all ongoing transactions. The normal transaction list screen is a screen that shows a list of normal transactions among ongoing transactions.

[0104] In this embodiment, of the three ongoing transaction list screens, the abnormal transaction list screen is treated as the main ongoing transaction list screen. For example, when the transaction status monitoring device 80 starts displaying the ongoing transaction list screen in response to an operation by a store clerk, the abnormal transaction list screen is displayed first as the initial screen.

[0105] 13 shows an example of an abnormal transaction list screen. The abnormal transaction list screen in the figure includes a transaction number area AR30 (AR30-1, AR30-2, AR30-3), display command buttons BT30 (BT30-1, BT30-2, BT30-3), and a transaction list area AR40.

[0106] The transaction number area AR30 is an area that indicates the number of corresponding ongoing transactions. The transaction number area AR30-1 indicates the number of all ongoing transactions. The transaction number area AR30-2 indicates the number of abnormal ongoing transactions among all ongoing transactions. The transaction number area AR30-3 indicates the number of normal ongoing transactions among all ongoing transactions. In this case, the transaction number area AR30-2 is highlighted in a predetermined manner (shown in a bold frame in the same figure), indicating that a list of abnormal ongoing transactions is displayed in the transaction list area AR40.

[0107] The display instruction buttons BT30 (BT30-1, BT30-2, BT30-3) are buttons operated to instruct switching to the display of the ongoing transaction list screen of the corresponding ongoing transaction. The display instruction button BT30-1 is a button that is operated to instruct switching to the display of the all transaction list screen. The display instruction button BT30-2 is a button that is operated to instruct switching to the display of the abnormal transaction list screen. In this case, since the abnormal transaction list screen is displayed, the display instruction button BT30-2 is grayed out, for example, to indicate that it is in an inoperable state. The display instruction button BT30-3 is a button that is operated to instruct switching to the display of the normal transaction list screen.

[0108] The transaction list area AR40 displays a list of ongoing transactions. In the case of the abnormal transaction list screen shown in the figure, the transaction list area AR40 displays a list of abnormal transactions. In this case, the transaction list area AR40 shows list items of abnormal transactions from 1 to 10, arranged in order of most recent transaction start time (registration start time), for example. If the number of abnormal transactions is 11 or more, the 12th and subsequent list items may be displayed by scrolling or page forwarding the transaction list area AR40.

[0109] Each list item in the transaction list area AR40 displays the transaction start time, membership number, number of registered products, current total amount for the registered products, and time elapsed since the transaction started. In addition, in the list item of an abnormal transaction as in the case of the same figure, information indicating the reason why the corresponding transaction is treated as an abnormal transaction (cause information) is presented. In the same figure, the cause information is represented by an icon. Specifically, the first list item displays an icon labeled "protected" and an icon labeled "year." For example, the icon labeled "protected" indicates that a reserved product has been registered, classified as either "NO-FILE" or "NG to read." The icon labeled "year" indicates that, among the previous product registrations, a reserved product has been registered as an "age verification product." In other words, the icon indicates the classification of the registered reserved product. The combination of the icon style and the reserved product classification is not particularly limited. For example, different icon styles may be prepared for each reserved product classification, or one icon style may be associated with multiple predetermined reserved product classifications.

[0110] Additionally, in the third list item, an icon indicating "cart abandonment" as the cause information is displayed. The "cart abandonment" icon indicates that the cause information includes a product registration result in which a customer may have engaged in fraudulent behavior known as cart abandonment. The "cart abandonment" icon may be displayed in response to the registration of a pending product classified as either "pseudo-scanned entry" or "non-scanned entry," for example.

[0111] Additionally, the fifth list item displays an icon labeled "Caution." The "Caution" icon indicates that the transaction is with a member who is registered as a suspicious person in the member information stored in the transaction management device 60, for example. Members who are suspected of being persons of concern include, for example, members who have previously committed fraudulent acts or who may have committed fraudulent acts, or members who have not committed fraudulent acts but are known to have difficulty operating the customer terminal device 50 or the checkout device 40 every time they shop. For such suspicious members, it is preferable that a store clerk, for example, be able to monitor the progress of ongoing transactions. Therefore, in this embodiment, not only transactions that include the registration of reserved items, but also ongoing transactions of suspicious members are treated as abnormal transactions.

[0112] Additionally, each list item in the transaction list area AR40 indicates the type of customer terminal device 50 that the customer is using to register the product in the corresponding transaction. "Customer-owned terminal" indicates that the type of customer terminal device 50 is a mobile terminal such as a smartphone owned by the customer. "Store terminal" indicates that the type of customer terminal device 50 is a terminal loaned to the customer by the store.

[0113] The order in which list items are arranged in the transaction list area AR40 is not limited to the order of transaction start time. For example, the list items in the transaction list area AR40 may be arranged in order according to the number of pending items included in the transaction. Furthermore, the list items in the transaction list area AR40 may be arranged in order according to the number of all pending items included in the transaction (including pending items and items other than the pending items). Furthermore, the list items in the transaction list area AR40 may be arranged in order based on the classification of the pending items included in the transaction. Furthermore, the list items in the transaction list area AR40 may be arranged in order based on the positional relationship between the corresponding customer terminal device 50 and the settlement device 40. The position of the customer terminal device 50 can be obtained by the transaction management device 60, etc., based on location information obtained by the customer terminal device 50 itself using a GPS function, etc., or, for example, the communication status between the customer terminal device 50 and a beacon installed at a predetermined location in the store. Specifically, the list items in the transaction list area AR40 may be arranged in order of the proximity of the corresponding customer terminal device 50 to the settlement device 40.

[0114] In response to an operation to select a list item in the transaction list area AR40, the transaction status monitoring device 80 can display a transaction details screen showing details of the transaction corresponding to the selected list item. The transaction details screen may be displayed by the same operation not only on the abnormal transaction list screen, but also on the all transaction list screen and the normal transaction list screen.

[0115] Figure 14 shows an example of a transaction details screen WD20 that is displayed in response to an operation to select one of the list items in the transaction list area AR40 of the abnormal transaction list screen of Figure 13. The transaction details screen WD20 in this figure is an example in the form of a window that is arranged so as to be superimposed on the abnormal transaction list screen of Figure 13.

[0116] The transaction details screen WD20 in the figure displays a list of products registered in the transaction, correlated with the time when the products were registered. This allows a store clerk looking at the transaction details screen WD20 to understand which products were registered at what time in the transaction.

[0117] Furthermore, among the product list items on the transaction details screen WD20, the list items of products classified as reserved products are highlighted in a predetermined manner EH, or a registration status display TR including an image (registration status image pic) obtained by capturing an image of the situation in which the registration operation for the corresponding product is being performed by the customer terminal device 50. Whether the reserved product is displayed as a highlight EH or a registration status display TR depends on the classification of the reserved product.

[0118] The registration status image pic may be a still image, a video, or a time-lapse image. In addition, if the registration status image pic is a still image, multiple images taken at different times may be displayed.

[0119] Specifically, in the figure, a highlight EH is attached to one reserved item classified as "NO-FILE." Also, in the same figure, the list item for the "alcohol" product is highlighted with EH in response to the classification of the product as a reserved product for "age verification."

[0120] The registration status display TR corresponds to products that have been registered as "cart abandonment." In other words, the registration status display TR is displayed to indicate pending products that have been registered as either "pseudo-scanned input" or "non-scanned input." "Pseudo-scanned input" and "non-scanned input" are likely to occur when a customer commits fraud by intentionally not allowing the code to be scanned.

[0121] The store clerk can close the transaction details screen WD20 by performing a predetermined operation. When the transaction details screen WD20 of Figure 14 is closed, the screen may return to the abnormal transaction list screen of Figure 13.

[0122] In addition, when the display instruction button BT30-1 is operated while the abnormal transaction list screen of Figure 13 is displayed, the transaction status monitoring device 80 switches the ongoing transaction list screen displayed on the display unit 806 from the abnormal transaction list screen to the all transaction list screen. The all transaction list screen may, for example, have a transaction count area AR30, a display command button BT30, and a transaction list area SR40, similar to that shown in Figure 13. Furthermore, the transaction list area SR40 on the all transaction list screen displays a list of all pending transactions, up to the number that can be displayed on one screen. In this case, too, the clerk can display the list items of the remaining pending transactions by scrolling or page-turning in the transaction list area SR40. When the display instruction button BT30-2 is operated while the all transaction list screen is displayed, the display transitions to the abnormal transaction list screen. Also, when the display instruction button BT30-3 is operated while the all transaction list screen is displayed, the display transitions to the normal transaction list screen.

[0123] The normal transaction list screen may have, for example, a transaction count area AR30, a display command button BT30, and a transaction list area SR40 arranged in the same manner as in Fig. 13. In addition, the transaction list area SR40 on the normal transaction list screen displays a list of the normal transactions that can be displayed on one screen. When the display command button BT30-1 is pressed while the normal transaction list screen is displayed, the display transitions to the all transaction list screen. Also, when the display command button BT30-2 is pressed while the normal transaction list screen is displayed, the display transitions to the abnormal transaction list screen.

[0124] In this embodiment, the number of ongoing transactions occurring in a store, the product registration results for ongoing transactions, and other conditions change over time. The content of the transactions presented in the transaction list area AR40 of the ongoing transaction list screen (abnormal transaction list screen, all transaction list screen, normal transaction list screen) also changes to reflect the changes in the situation over time as described above. For example, if no pending items were registered up to the second item in a certain ongoing transaction, but the third item is registered as a pending item, the ongoing transaction will be changed from a normal transaction to an abnormal transaction in response to the third item being registered as a pending item. At this time, if the abnormal transaction list screen is displayed, a list item for the ongoing transaction that has been changed to an abnormal transaction will be added to the transaction list area AR40. In addition, a list item displayed in the transaction list area AR40 of the ongoing transaction list screen may be deleted when the settlement of the corresponding ongoing transaction at the settlement device 40 is completed. Additionally, the list item displayed in the transaction list area AR40 of the ongoing transaction list screen may be updated to indicate that the corresponding ongoing transaction has transitioned to the settlement stage due to completion of the product registration stage. Alternatively, if the product registration stage is treated as an ongoing transaction, the list item displayed in the transaction list area AR40 may be deleted when the product registration stage is completed. Also, for example, when an ongoing transaction is interrupted by an operation on the customer terminal device 50 by the customer, the corresponding list item in the transaction list area AR40 may be deleted. Furthermore, the settlement of a transaction may be completed at the customer terminal device 50 without using the settlement device 40. In this case, even when the settlement is completed at the customer terminal device 50, the corresponding list item in the transaction list area AR40 may be deleted. Furthermore, information regarding transactions displayed as list items, etc. in the transaction list area AR40 may be buffered (stored) in the transaction status monitoring device 80 or transaction management device 60, etc., so that it can be displayed as past history, including information about list items that have been deleted once.

[0125] [About releasing reserved items at the registration stage] In the shopping system of this embodiment, if the registered products include reserved products, a store clerk can perform an operation to release the reserved products at the beginning of the stage when product registration is completed and the transaction moves to payment, as explained with reference to Fig. 12(C). This release of the reserved products at the stage when the transaction moves to payment is performed after product registration is completed by performing a payment transition instruction operation.

[0126] In the shopping system of this embodiment, the transaction status monitoring device 80 can display an abnormal transaction list screen, allowing a store clerk monitoring transactions using the transaction status monitoring device 80 to recognize an abnormal transaction involving a reserved item even during product registration before the transaction moves to the checkout stage. Therefore, the shopping system of this embodiment is configured so that a store clerk can release a reserved item included in a transaction at the product registration stage (registration-stage hold release) by operating the transaction status monitoring device 80. By performing this registration-stage hold release, the checkout device 40 does not need to release the reserved items, and this can be distributed between the checkout device 40 and the transaction status monitoring device 80. This reduces the total waiting time for the checkout device 40 to release the reserved items, improving the utilization efficiency of the checkout device 40.

[0127] If a customer who is currently registering merchandise includes a reserved item among the merchandise he or she has registered, the customer can go to the counter where the transaction status monitoring device 80 is installed and ask a store clerk as an operator of the transaction status monitoring device 80 to release the reserved item before performing a settlement transition instruction operation. If the registered items include a held item, the customer terminal device 50 may display information directing the customer to a location in the store where the held item can be released, such as the counter described above. For example, a display may be displayed directing the customer to a specific location in the store. Furthermore, if the transaction status monitoring device 80 is a portable device that is carried by a store clerk while working in the store, the customer can ask the clerk they find in the store to release the held item.

[0128] The store clerk who has been requested to release the hold will confirm, for example, the customer's membership number, and then identify the transaction in question from the list items on the abnormal transaction list screen displayed on the transaction status monitoring device 80. The transaction status monitoring device 8 may be configured to enable a search for the target transaction using, for example, the membership number as a search keyword. The following explanation will take as an example a case where a store clerk displays the transaction details screen WD20 (FIG. 14) for the abnormal transaction in question, and then operates the displayed transaction details screen WD20 to release the registration-stage hold. In this case, the store clerk operates to display the transaction details screen WD20 for the identified (or searched) transaction (abnormal transaction).

[0129] An example of the hold release operation on the transaction details screen WD20 will be described with reference to FIG. 14 again. In the example of the transaction details screen WD20 in the figure, there are four reserved items that can be released. Two of the four are the two reserved items "NO-FILE" and "Alcohol," which are highlighted with EH. The remaining two of the four are the two reserved items presented by the registration status display TR.

[0130] When releasing a reserved item marked "NO-FILE" on the transaction details screen WD20, the store clerk selects the list item "NO-FILE" on the transaction details screen WD20. In response to this operation, an operation screen (removal screen) for releasing a reserved item marked "NO-FILE" is displayed, although not shown in the figure.

[0131] 16(A) is an example of a hold release screen that is displayed when a "NO-FILE" held item is released from hold. The hold release screen in the figure has a product code input area AR61. This is the area where a store clerk inputs a product code by operating the operation unit 807 of the transaction status monitoring device 80.

[0132] Once the store clerk has identified the actual product registered as "NO-FILE," he or she performs an operation to input the product code of the identified product into the product code area AR41. The store clerk can input the product code by, for example, operating a keyboard provided as the operation unit 807 (or a software keyboard displayed on the screen). Alternatively, the store clerk may operate the search button BT43 to display a product search screen, enter, for example, the product name as a search condition to search for the relevant product, and input the product code of the searched product into the product code area AR41. After entering the product code as described above, the store clerk can re-register the product registered as "NO-FILE" as a normal product by operating the registration button BT41. This will release the reserved product registered as "NO-FILE" and it will be treated as a normally registered product. Furthermore, the hold release screen in the same figure has a cancel button BT42. The store clerk may cancel the registration of a held item in order to release the held item. In this case, the store clerk can cancel the registration of the held item by operating the cancel button BT42.

[0133] When a reserved product is registered during product registration, a display indicating that the reserved product is a reserved product is displayed in the list item of the reserved product in the registered product list on the product registration screen, as shown in Figure 15(A). The figure shows an example where the reserved product is "NO-FILE". In response to the store clerk performing the operation to release the "NO-FILE" held item as described above, the list item for the "NO-FILE" held item changes to a state in which information about the newly registered item (product name, quantity, price) is displayed, as shown in FIG. 15(B). Furthermore, the list item for the released item displays, as shown in the figure, a message indicating that the item has been released, such as "released." In other words, the customer terminal device 50 notifies the user that the held item has been released.

[0134] Furthermore, when canceling a reserved item of "alcohol" on the transaction details screen WD20, the store clerk performs an operation to select the list item of "alcohol" on the transaction details screen WD20. Since "alcohol" is a reserved item classified as an "age verification item," in response to this operation, an operation screen (removal screen) for canceling a reserved item of an "age verification item" is displayed.

[0135] FIG. 16(B) is an example of a hold release screen displayed in response to a case where a reserved product of "age verification product" is released from hold. The hold release screen in the figure displays a message to the store clerk urging them to confirm the customer's age and perform the confirmation operation, such as "Please press the button once you have confirmed the customer's age." Also, the hold release screen in the figure has a confirmation button BT50. If the store clerk can confirm that the customer is not a minor, he or she presses the confirmation button BT50 to confirm that the customer's age has been verified. This releases the hold on the "alcohol" product, and it is treated as a properly registered product.

[0136] It should be noted that age verification by operating the age verification button BT50 may be performed by the customer rather than the store clerk. In this case, a message urging the customer to operate the age verification button may be displayed on the hold release screen, such as "Please press the button to verify your age."

[0137] Furthermore, when canceling the reservation of a reserved product (pseudo-scanned or non-scanned) corresponding to the registration status display TR on the transaction details screen WD20, an operation is performed to select a list item as the registration status display TR. In response to this operation, a reservation release screen for canceling the reservation of the reserved product corresponding to the registration status display TR is displayed.

[0138] FIG. 16(C) is an example of a hold release screen displayed in response to the case where a reserved product corresponding to the registration status display TR is released from hold. The hold release screen in the figure displays a registration status image area AR60. In the registration status image area AR60, for example, enlarged registration status images epc (epc1 to epc3) corresponding to the registration status image pic displayed in the registration status display TR are displayed. The example in the figure displays three enlarged registration status images epc1 to epc3. The enlarged registration status images epc1 to epc3 are three images captured by the customer terminal device 50 at regular intervals during the registration operation for the target held item. For example, an enlarged registration status image epc2 is an enlarged version of the registration status image pic displayed in the registration status display TR, an image captured before the registration status image pic is displayed as the enlarged registration status image epc1, and an image captured after the registration status image pic is displayed as the enlarged registration status image epc3. By viewing these enlarged registration status images epc1 to epc3, the store clerk can more accurately understand how the customer performed the product code reading operation for the target held item than, for example, when a single registration status image pic is displayed. The number of enlarged registration status images epc arranged in the registration status image area AR60 is not particularly limited as long as it is equal to or greater than 1. The enlarged registration status images epc may be displayed as moving images.

[0139] The clerk identifies the target product shown in the registration status image (pic) on the hold release screen and checks the actual product in the customer's shopping cart. The clerk then confirms with the customer whether or not they wish to purchase the target product. If the customer confirms that they wish to purchase the target product, the clerk performs an operation on the hold release screen to re-register the target product. That is, the clerk can register the target product by entering the product code of the target product in the product code input area AR71 and operating the register button BT61. Furthermore, when entering the product code, the customer can also enter the product code in the product code area AR41 by operating the search button BT63 to display the product search screen. On the other hand, if the customer confirms that he or she will not purchase the target product, the store clerk operates the cancel button BT62 to cancel the registration of the target product as a reserved product. In this way, the reserved items sorted by pseudo-scan input or non-scan input are released from reservation.

[0140] [Example of processing procedure] An example of a processing procedure executed by the transaction management device 60 and the transaction status monitoring device 80 in relation to displaying the ongoing transaction list screen will be described with reference to the flowchart of FIG.

[0141] First, an example of a processing procedure executed by the transaction status monitor device 80 will be described. Step S101: To display the ongoing transaction list screen, a store clerk in charge of monitoring using the transaction status monitoring device 80 performs a predetermined display instruction operation on the operation unit 807. The transaction status monitoring device 80 accepts the display instruction operation performed by the store clerk.

[0142] Step S102: The abnormal transaction list screen is displayed as the initial screen among the ongoing transaction list screens. Therefore, in response to receiving the display instruction operation in step S101, the transaction status monitoring device 80 transmits a request for the abnormal transaction list screen to the transaction management device 60.

[0143] Step S103: In response to the request for the abnormal transaction list screen, the transaction management device 60 transmits the abnormal transaction list screen to the transaction status monitoring device 80. The transaction status monitoring device 80 displays the received abnormal transaction list screen on the display unit 806.

[0144] The ongoing transaction list screen may be in the form of, for example, an HTML file or an XML file, and the transaction status monitor device 80 may display the ongoing transaction list screen using, for example, a web browser function.

[0145] Step S104: After processing in step S103, the transaction status monitor device 80 determines whether or not it has received an operation to instruct switching to the all transaction list screen (all transaction list screen switching operation). The all transaction list screen switching operation is an operation performed on the display instruction button BT30-1 when the currently displayed ongoing transaction list screen is either the abnormal transaction list screen or the normal transaction list screen.

[0146] Step S105: When the transaction status monitor device 80 receives the operation to switch to the all transaction list screen, it sends a request for the all transaction list screen to the transaction management device 60.

[0147] Step S106: In response to the request for the all transaction list screen, the transaction management device 60 transmits the all transaction list screen to the transaction status monitoring device 80. The transaction status monitoring device 80 displays the received all transaction list screen on the display unit 806.

[0148] Step S107: After the processing of step S106, or if it is determined in step S104 that the all transaction list screen switching operation has not been performed, the transaction status monitor device 80 determines whether or not an operation to instruct switching to the normal transaction list screen (normal transaction list screen switching operation) has been received. The normal transaction list screen switching operation is an operation performed on the display instruction button BT30-3 when the currently displayed ongoing transaction list screen is either the all transaction list screen or the abnormal transaction list screen.

[0149] Step S108: When the normal transaction list screen switching operation is accepted, the transaction status monitor device 80 sends a normal transaction list screen request to the transaction management device 60.

[0150] Step S109: In response to the request for the normal transaction list screen, the transaction management device 60 transmits the normal transaction list screen to the transaction status monitoring device 80. The transaction status monitoring device 80 displays the received normal transaction list screen on the display unit 806.

[0151] Step S110: After the processing of step S109, or if it is determined in step S107 that the normal transaction list screen switching operation has not been performed, the transaction status monitor device 80 determines whether or not an operation to instruct switching to the abnormal transaction list screen (abnormal transaction list screen switching operation) has been received. The abnormal transaction list screen switching operation is an operation performed on the display instruction button BT30-2 when the currently displayed ongoing transaction list screen is either the all transaction list screen or the normal transaction list screen. If the operation to switch to the abnormal transaction list screen is accepted, the process returns to step S102, and the processes of steps S102 and S103 are executed, thereby switching the display to the abnormal transaction list screen.

[0152] Step S111: The transaction status monitor device 80 determines whether an update screen for updating the currently displayed ongoing transaction list screen has been received from the transaction management device 60.

[0153] Step S112: When an updated screen is received, the transaction status monitor device 80 updates the currently displayed ongoing transaction list screen with the received screen. As a result, new transactions and completed changes occurring in the corresponding ongoing transactions are reflected in the transaction list area AR40 of the currently displayed ongoing transaction list screen.

[0154] Step S113: After the processing of step S112, or if it is determined in step S111 that an updated screen has not been received, the transaction status monitor device 80 determines whether the display of the ongoing transaction list screen has ended. The display of the ongoing transaction list screen is ended, for example, in response to an operation by a store clerk to close the ongoing transaction list screen. If it is determined that the display of the ongoing transaction list screen has not ended, the process returns to step S104. If it is determined that the display of the ongoing transaction list screen has ended, the process in the same figure ends.

[0155] Next, an example of the processing procedure of the transaction management device 60 in the figure will be described. Step S201: The transaction management device 60 determines whether a request for an ongoing transaction list screen (either an abnormal transaction list screen, a all transaction list screen, or a normal transaction list screen) sent in any of steps S102, S105, or S108 has been received.

[0156] Step S202: When a request for an ongoing transaction list screen is received, the transaction management device 60 generates the requested ongoing transaction list screen. When a request for an abnormal transaction list screen is received as a request for an ongoing transaction list screen, the transaction management device 60 extracts cart information that includes pending items among the registered items from the cart information. Cart information that includes pending items corresponds to an abnormal transaction. The transaction management device 60 uses the extracted cart information to generate an abnormal transaction list screen that displays a list of abnormal transactions in the transaction list area AR40. When a request for an all transaction list screen is received as a request for an ongoing transaction list screen, the transaction management device 60 uses all currently stored cart information to generate an all transaction list screen that displays a list of ongoing transactions in the transaction list area AR40. When a request for a normal transaction list screen is received as a request for an ongoing transaction list screen, the transaction management device 60 extracts cart information from the cart information that does not include any pending items among the registered items.Cart information that does not include any pending items corresponds to a normal transaction.The transaction management device 60 uses the extracted cart information to generate a normal transaction list screen that displays a list of normal transactions in the transaction list area AR40.

[0157] Step S203: The transaction management device 60 transmits the ongoing transaction list screen generated in step S202 to the transaction status monitoring device 80.

[0158] Step S204: As shown in steps S5 to S7 of FIG. 10, each time a product is scanned by the customer terminal device 50, the transaction management device 60 registers the product according to the scan results and updates the cart information. After processing step S203, or if it is determined in step S201 that a request for the ongoing transaction list screen has not been received, the transaction management device 60 determines whether there has been an update to the cart information corresponding to the ongoing transaction that is being presented on the ongoing transaction list screen currently displayed on the transaction status monitoring device 80. Specifically, when the transaction status monitoring device 80 is displaying the abnormal transaction list screen as the ongoing transaction list screen, the transaction management device 60 determines that the corresponding cart information has been updated if an item is added, deleted, or the like to cart information that previously included a reserved item. The transaction management device 60 also determines that the corresponding cart information has been updated if cart information that previously did not include a reserved item in its registered items is changed to include a reserved item. The transaction management device 60 also determines that the corresponding cart information has been updated if at least one of the reserved items previously included in the registered items is released from reservation. The transaction management device 60 also determines that the corresponding cart information has been updated if a transaction is completed for cart information that previously included a reserved item in its registered items. In addition, when the all transaction list screen is being displayed as the ongoing transaction list screen, the transaction management device 60 determines that the corresponding cart information has been updated if an item is added or canceled for any of the cart information currently in progress, or if new cart information is generated in response to the start of a new transaction, or if a transaction for any of the stored cart information has ended. In addition, when the normal transaction list screen is being displayed as the ongoing transaction list screen, the transaction management device 60 determines that the corresponding cart information has been updated if an item is added, canceled, etc. to any of the cart information that does not currently include a pending item, or if new cart information is generated in response to the start of a new transaction, or if a transaction is completed for cart information that does not include a pending item. If it is determined that the cart information is not to be updated, the process returns to step S201.

[0159] Step S205: If it is determined in step S204 that the cart information has been updated, the transaction management device 60 generates an update screen that reflects the results of the cart information update. The update screen will be one of an abnormal transaction list screen, a total transaction list screen, or an abnormal transaction list screen, corresponding to the ongoing transaction list screen currently being displayed on the transaction status monitoring device 80, and the results of the current cart information update will be reflected in the transaction list area AR40.

[0160] Step S206: The transaction management device 60 transmits the updated screen generated in step S205 to the transaction status monitoring device 80.

[0161] Next, referring to the flowchart of Figure 18, we will explain an example of the processing procedure that the transaction status monitoring device 80 and the transaction management device 60 perform in relation to releasing the reservation of a reserved product (removing the reservation at the registration stage) before product registration is completed (before the settlement transition instruction operation is performed).

[0162] First, an example of a processing procedure executed by the transaction status monitor device 80 will be described. Step S301: While the transaction details screen D20 is displayed, the transaction status monitoring device 80 accepts an operation (target product designation operation) performed by a store clerk to designate a target product to be released from hold. The target product designation operation is an operation to select a list item in the highlighted display EH or a list item in the registration status display TR from among the list items of registered products displayed on the transaction details screen D20. In other words, the target product designation operation is an operation to select a list item of a reserved product.

[0163] Step S302: In response to receiving the target product designation operation, the transaction status monitoring device 80 displays a hold release screen for the reserved product designated by the target product designation operation.

[0164] Step S303: The store clerk performs an operation (hold release operation) on the displayed hold release screen in accordance with the hold release of the held product. The transaction status monitoring device 80 accepts the hold release operation.

[0165] Step S304: In response to receiving the hold release operation, the transaction status monitor device 80 transmits a hold release notice.

[0166] Next, an example of a processing procedure executed by the transaction management device 60 will be described. Step S401: The transaction management device 60 receives the hold release notice sent from the transaction status monitoring device 80 in step S304. Step S402: The received hold release notice includes cart identification information indicating the corresponding transaction and information specifying the held product information of the held product that has been released (product identification information). The transaction management device 60 updates the stored cart information for the cart information identified by the same cart identification information as that included in the hold release notice by changing the held product information specified by the product identification information to registered product information. Such update results are reflected on the abnormal transaction list screen displayed on the transaction status monitor device 80 by the processing of steps S204 to S206, S111, and S112 in FIG.

[0167] Step S403: The transaction management device 60 generates a product registration screen (updated product registration screen) that reflects the result of the release of the currently reserved product. The transaction management device 60 transmits the generated updated product registration screen to the customer terminal device 50.

[0168] Next, an example of a processing procedure executed by the customer terminal device 50 will be described. Step S501: The customer terminal device 50 receives the updated product registration screen sent from the transaction management device 60 in step S403. Step S502: The customer terminal device 50 changes the product registration screen displayed on the display unit 504 based on the received updated product registration screen. As a result, the list item that was indicated as a reserved product changes to a state that notifies the user that the product has been released from the reserved state, as shown by the transition from Fig. 15(A) to Fig. 15(B), for example.

[0169] In addition, when a transaction including a product for which the registration stage hold has been released moves to the settlement stage at the settlement device 40, it may be indicated that the product has been released from the registration stage hold on, for example, the registered product list screen displayed on the settlement device 40. Figure 19 shows an example of a registered product list screen displayed on the settlement device 40. In the registered product list in the figure, the listing for "XX Chocolate," which was a reserved product, has the word "Released." This "Released" indication indicates that the product "XX Chocolate" has been re-registered as a product by releasing the reservation at the registration stage. In addition, in the registered product list in the same figure, the item for "Chuhai" has been struck out with a double line. This indicates that the "Chuhai" product, which was registered as a reserved product, has been cancelled at the registration stage.

[0170] <Modification> Modifications of this embodiment will be described below. The modifications described below may be combined with the above embodiment and other modifications as appropriate.

[0171] [First Modification] The transaction status monitoring device 80 may be capable of displaying the operating status of the settlement device 40 in the store. 20 shows an example of how the transaction status monitoring device 80 displays the operating status of the settlement device 40. The figure shows an example of how the operating status of the settlement device 40 is displayed by displaying a settlement device operating status screen WD30 superimposed on an ongoing transaction list screen. In the example shown in the figure, there are arranged operation status areas AR50 (AR50-1, AR50-2, AR50-3) that indicate the operation status of each of three settlement devices 40, named settlement machines 1, 2, and 3. In the figure, each operation status area AR50 indicates that settlement machines 1 and 2 are in operation, and settlement machine 3 is stopped, as the operation status.

[0172] Furthermore, on the settlement device operation status screen WD30, operation operation buttons BT50 (BT50-1, BT50-2, BT50-3) are arranged corresponding to each operation status area AR50 (AR50-1, AR50-2, AR50-3). The operation operation buttons BT50 are buttons used to remotely control the operation of the corresponding settlement device 40 (payment machine). If the corresponding settlement device 40 is in operation, the corresponding settlement device 40 can be stopped by operating the operation operation button BT50. On the other hand, if the corresponding settlement device 40 is stopped, the corresponding settlement device 40 can be operated by operating the operation operation button BT50.

[0173] By viewing the ongoing transaction list screen displayed on the transaction status monitoring device 80, the store clerk can ascertain the number of currently registered product transactions. Furthermore, by viewing the settlement device operation status screen WD30, the store clerk can determine whether the number of currently operating settlement devices 40 is appropriate for the number of currently registered product transactions. If the store clerk determines that the number of currently operating settlement devices 40 is low, the store clerk can quickly activate the required number of inactive settlement devices 40 by operating the operation button BT50 on the settlement device operation status screen WD30. If the store clerk determines that the number of currently operating settlement devices 40 is high, the store clerk can quickly halt the required number of active settlement devices 40 by operating the operation button BT50 on the settlement device operation status screen WD30.

[0174] [Second Modification] It should be noted that fraudulent acts by customers may occur not only at the product registration stage but also at the checkout stage. In other words, fraudulent acts may occur while a customer is paying at the checkout device 40. Therefore, in this modified example, in response to a determination at the checkout device 40 that a customer may be committing fraudulent acts, the transaction status monitoring device 80 may display information about the checkout device 40 where a customer may be committing fraud.

[0175] One example of fraudulent activity committed at the payment device 40 is having the payment device 40 read a two-dimensional code stored in the customer terminal device 50 using the screenshot function. Specifically, for example, after registering one product using the customer terminal device 50, a customer performs a payment transition instruction operation to display a two-dimensional code on the code display screen. The customer then uses the screenshot function to store the displayed two-dimensional code as image data in the customer terminal device 50. The customer then places many products in a shopping cart without registering the products and proceeds to the payment device 40. The customer displays the image data of the stored two-dimensional codes on the customer terminal device 50 and has the payment device 40 read it. In this case, the customer can make it appear as if they have purchased many products placed in the shopping cart by performing payment for the one product they previously registered. Whether or not there is a possibility that such fraud has occurred can be determined, for example, by the transaction management device 60 by checking whether or not the interval between the time when the settlement transition instruction operation was performed and the time when the settlement device 40 was caused to read the two-dimensional code is equal to or greater than a certain value.

[0176] If the transaction management device 60 determines that fraud may have occurred at the settlement device 40, it sends a fraud notification to the transaction status monitoring device 80. The fraud notification includes information indicating the settlement device 40 where fraud may have occurred. The fraud notification may also include information indicating the content and type of fraud. In response to receiving a fraud notification, the transaction status monitoring device 80 displays a fraud notification screen based on the received fraud notification. The fraud notification screen indicates which settlement device 40 may be the site of fraud. Furthermore, the fraud notification screen may display information indicating the nature and type of fraud.

[0177] [Third Modification] In the above embodiment, the reserved item is released from the reserved state by operating the transaction status monitoring device 80. In addition to operating the transaction status monitoring device 80, the reserved item may also be released from the reserved state by, for example, having a store clerk stamp an electronic stamp on the screen displayed on the display unit of the customer terminal device 50.

[0178] In this case, if the registered products include a held item, the shopping application of the customer terminal device 50 can display an electronic stamp screen on which an electronic stamp is applied to release the held item. To release the held item, the customer operates the customer terminal device 50 to display the electronic stamp screen on the display unit 504. The electronic stamp screen may be for releasing a selected held item, for releasing all held items, or for releasing held items that fall into a predetermined category.

[0179] The store clerk presses the electronic stamp onto the display surface of the display unit 504 on which the electronic stamp screen is displayed. In response to the electronic stamp being stamped, customer terminal device 50 sends a notification (hold release notification) to transaction management device 60 that the reserved item in question has been released from hold. Transaction management device 60 updates the cart information to reflect the release of the reserved item notified by the hold release notification.

[0180] In this case, the transaction management device 60 may send an updated product registration screen to the customer terminal device 50 in the same manner as in step S403 of Figure 18. Furthermore, in this case, the transaction management device 60 also sends information indicating the result of the current hold release processing to the transaction status monitoring device 80. The transaction status monitoring device 80 changes the content of the list item for the relevant transaction on the ongoing transaction list screen so that the hold release processing result indicated by the received information is reflected.

[0181] [Fourth Modification] The product registration results of one transaction made using one customer terminal device 50 may be handed over to another customer terminal device 50, and the customer may then continue to register products for the same transaction using the other customer terminal device 50. For example, when a customer is registering a product using his / her own customer terminal device 50, the remaining battery charge of the customer terminal device 50 may become low, but the customer may not be able to charge it immediately, making it difficult to continue the product registration. Also, when a customer is registering a product using the customer terminal device 50, if the customer terminal device 50 malfunctions, it may become difficult to continue the product registration. In such a case, the customer can cancel the product registration results from the customer terminal device 50 that they have been using and redo the product registration from the beginning, for example, using another customer terminal device 50 provided by the store. However, redoing the product registration in this way is troublesome for the customer, and the progress of product registration in one transaction is inefficient. Therefore, if the product registration results of one customer terminal device 50 can be transferred to another customer terminal device 50 as described above, the customer can continue to perform product registration operations while maintaining the previous product registration results, without having to start the product registration operations over again.

[0182] The transfer of product registration results between the customer terminal devices 50 may be performed, for example, in accordance with the following operations. When a customer determines that the customer terminal device 50 that the customer has been using to register products can no longer be used, the customer may ask, for example, a store clerk at the store's service counter, to take over use of another customer terminal device 50. The clerk who receives the request may, for example, perform a predetermined operation on the customer terminal device 50 that the customer has been using so far, to display a takeover code on the customer terminal device 50 that is the takeover source. The takeover code includes cart identification information associated with the transaction. The customer may also perform the operation to display the transfer code. The code displayed by the payment transfer instruction operation may also be used as the transfer code. The store clerk has the customer terminal device 50 of the transfer destination, which may be a loaned store terminal prepared for transfer, read the code displayed on the customer terminal device 50 of the transfer source. The customer terminal device 50 of the transfer destination that has read the code transmits a transfer request to the transaction management device 60. The transmitted transfer request includes the cart identification information indicated by the read code. Upon receiving the takeover request, the transaction management device 60 transmits the product registration screen information of the cart information identified by the cart identification information included in the received takeover request to the customer terminal device 50 as the takeover destination. The customer terminal device 50 as the takeover destination displays the product registration screen based on the received product registration screen information, and becomes ready to execute processing according to subsequent product registration operations. In other words, the customer terminal device 50 as the takeover destination takes over the product registration results from the customer terminal device 50 as the takeover source, and is then able to execute processing according to subsequent product registrations. The store clerk takes over the product registration results as described above and hands the customer terminal device 50, which is the new device and ready for product registration, to the customer. As described above, the customer terminal device 50 to be handed over may take over the product registration results and become ready to register products, so that the customer may also perform an operation to read the code.

[0183] [Fifth Modification] The transaction list screen shown in FIG. 13 may be displayed on a device other than the transaction status monitoring device 80 that is installed in the store. That is, in correspondence with FIG. 1, the transaction list screen may be displayed on the management device 10, the settlement device 40, etc. Alternatively, the transaction list screen may be displayed on a mobile terminal carried by a store clerk while performing their duties. Alternatively, the transaction list screen may be displayed on an integrated management device installed in, for example, a headquarters or the like that is capable of managing the transaction status of multiple stores in an integrated manner. Such an integrated management device may be capable of displaying both a transaction list screen for each store and a transaction list screen that reflects the integrated status of transactions from multiple stores.

[0184] [Sixth Modification] The control for displaying the ongoing transaction list screen on the transaction status monitoring device 80 of the above embodiment may be realized by a plurality of predetermined devices, such as the transaction status monitoring device 80, the transaction management device 60, the customer terminal device 50, the management device 10, and even other servers on the network, each performing a part of the processing and coordinating with each other. Also, the functions of the transaction status monitoring device 80 of this embodiment may be shared by another device in the same store, such as the management device 10.

[0185] <Summary of the embodiment> [Technical field] The present invention relates to a product sales data processing system. [Background technology] BACKGROUND ART In a self-checkout system equipped with a plurality of self-checkout terminals, a technique is known in which an attendant terminal displays the operating status and error occurrence status of the self-checkout terminals (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2007-95026 A [Summary of the Invention] [Problem to be solved by the invention] A product sales data processing system is known in which, when shopping at a store, a customer registers products using their own smartphone or a customer terminal device loaned by the store, and then pays for the registered products using a payment device installed in the store. In such a merchandise sales data processing system, it is preferable that the store be able to monitor ongoing transactions after merchandise registration has begun by allowing the customer to use the customer terminal device. The present invention has been made in consideration of the above circumstances, and aims to enable a store to monitor ongoing transactions in a product sales data processing system in which customers use a customer terminal device to register products and use a payment device to settle payments.

[0186] [Means for solving the problem] (1) As described above, one aspect of this embodiment is a transaction status monitoring device in a product sales data processing system that includes a customer terminal device (50) used by customers to register products according to transaction units, and a transaction status monitoring device (80) that performs processing related to monitoring transactions, and that includes a display control means for displaying ongoing transaction information (e.g., an ongoing transaction list screen) that presents information about transactions that have been initiated in response to the initiation of product registration by the customer terminal device, based on transaction information that reflects the results of product registration by transaction unit performed by the customer terminal device.

[0187] According to the above configuration, in this embodiment, information about a transaction currently in progress (for example, an ongoing transaction list screen) can be output by the transaction status monitoring device 80 when the customer is currently registering a product using the customer terminal device 50. In other words, the store can grasp the status of ongoing transactions that are currently being carried out when the customer is registering a product using the customer terminal device 50.

[0188] (2) One aspect of this embodiment is a transaction status monitoring device as described in (1), wherein the display control means displays ongoing transaction information that presents transactions that meet specified conditions from among ongoing transactions.

[0189] According to the above configuration, the ongoing transactions presented on the ongoing transaction list screen can be limited to, for example, ongoing transactions that include pending products among their registered products, or ongoing transactions that are likely to have been fraudulently registered by customers.

[0190] (3) One aspect of this embodiment is a transaction status monitoring device as described in (1) or (2), wherein the display control means displays details of the transaction content for a transaction selected from among the ongoing transactions for which information is presented as ongoing transaction information.

[0191] According to the above configuration, the transaction status monitoring device 80 can display details of an ongoing transaction selected from the ongoing transactions presented on the ongoing transaction list screen, for example. As the transaction details, for example, the registered products can be displayed corresponding to the time, as shown on the transaction details screen WD20 in FIG. 14. Furthermore, for registered products that have been registered as pending products, the pending products can be distinguished from successfully registered products by changing the appearance of the product list item so that the pending product can be recognized, for example, by highlighting EH or displaying a registration status TR.

[0192] (4) One aspect of this embodiment is a transaction status monitoring device as described in (3), wherein the display control means displays, in the details of the transaction content, a registration status image obtained by capturing an image of the situation at the time of product registration using a customer terminal device.

[0193] According to the above configuration, a registration status image is displayed that shows the status of the product when it is registered in an ongoing transaction. By viewing this registration status image, the store clerk can accurately understand the actual status of the product that was registered as a reserved product and the reason for its registration as a reserved product.

[0194] (5) One aspect of this embodiment is a transaction status monitoring device described in any one of (1) to (4), which includes a hold release means for controlling the release of a reserved product that was not registered normally and was registered in a reserved state in a transaction presented by ongoing transaction information in response to an operation.

[0195] According to the above configuration, even if a customer has not yet completed the registration of all products to be purchased, a store clerk can operate the transaction status monitoring device 80 to release the reserved products included in the products that have been registered so far.

[0196] (6) One aspect of this embodiment is a transaction status monitoring device as described in (5), which is equipped with a notification control means for controlling the customer terminal device to be notified that the reserved product has been released from the reserved product.

[0197] According to the above configuration, it is possible to notify the customer that the reserved item has been released from the hold by the customer terminal device 50. This allows the customer to accurately understand that the reserved item has been released from the hold.

[0198] (7) One aspect of this embodiment is a transaction status monitoring device described in any one of (1) to (6), wherein the information regarding an ongoing transaction presented by the ongoing transaction information includes information indicating the type of customer terminal device used to register the product corresponding to the ongoing transaction.

[0199] When a customer registers an item at a store, there are cases where multiple types of customer terminal devices 50 are available, such as a mobile terminal that the customer owns or a terminal loaned to the customer by the store. In response to such cases, the above configuration makes it possible to indicate on the ongoing transaction list screen which type of customer terminal device 50 is being used for each ongoing transaction.

[0200] (8) One aspect of this embodiment is a transaction status monitoring device described in any one of (1) to (7), wherein the display control means displays the status of the operation of a settlement device that performs settlement processing using settlement information based on transaction information that reflects the results of product registration for each transaction unit performed by the customer terminal device.

[0201] According to the above configuration, the store clerk can monitor the status of ongoing transactions using the transaction status monitoring device 80, and can also monitor the operating status of the settlement devices 40. This allows the store clerk to obtain effective information for making decisions on the appropriate operation of the store, such as determining the number of settlement devices 40 to operate, based on the status of ongoing transactions and the operating status of the settlement devices 40.

[0202] In addition, a program for implementing the functions of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction status monitoring device 80, etc. described in each of the above embodiments may be recorded on a computer-readable recording medium, and the program may be loaded into a computer system and executed to perform the processing of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction status monitoring device 80, etc. Here, "loading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. The "computer system" may also include multiple computer devices connected via a network, including communication lines such as the Internet, a WAN, a LAN, and a dedicated line. The "computer-readable recording medium" refers to portable media such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and storage devices such as a hard disk built into a computer system. In this way, the recording medium storing the program may also be a non-transitory recording medium such as a CD-ROM. The term "recording medium" also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in a format executable by a terminal device. In other words, the format in which the program is stored on the distribution server is not important as long as it can be downloaded from the distribution server and installed in a format executable by a terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on a terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" also includes a medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be for implementing part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0203] 10 management device, 40 settlement device, 50 customer terminal device, 60 transaction management device, 70 credit card settlement server, 80 transaction status monitoring device

Claims

1. A transaction status monitoring device in a product sales data processing system, comprising a customer terminal device used by a customer to register products according to a transaction unit, and a transaction status monitoring device that performs processing related to monitoring of transactions, A display control means for displaying on the same screen, based on transaction information reflecting the results of product registrations made by the customer terminal devices, the number of customer terminal devices that require the assistance of a store clerk regarding the results of the product registrations, and a transaction list area at the bottom of the screen presenting list items that associate information identifying the customer terminal devices with the status of transactions corresponding to the product registrations made by the customer terminal devices. A transaction status monitoring device comprising:

2. The information for identifying the customer terminal device includes information indicating the type of the customer terminal device.

2. A transaction status monitoring device according to claim 1.

3. A computer as a transaction status monitoring device in a product sales data processing system including a customer terminal device used by a customer to register products according to a transaction unit and a transaction status monitoring device that performs processing related to monitoring of transactions, A display control means for displaying on the same screen, based on transaction information reflecting the results of product registrations made by the customer terminal devices, the number of customer terminal devices that require the assistance of a store clerk regarding the results of the product registrations, and a transaction list area at the bottom of the screen presenting list items that associate information identifying the customer terminal devices with the status of transactions corresponding to the product registrations made by the customer terminal devices. A program to function as a

4. The information for identifying the customer terminal device includes information indicating the type of the customer terminal device. The program according to claim 3.

Images