Transaction state monitoring device
Patent Information
- Application Number
- JP2024092199
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-06-06
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2040-06-19
AI Technical Summary
Existing self-checkout systems lack the ability for stores to monitor and manage ongoing transactions effectively, particularly when customers use their own devices for product registration and payment, making it difficult to grasp the status of transactions in real-time.
A customer terminal device and a transaction status monitoring device are integrated into a product sales data processing system, allowing real-time monitoring and display of transaction information, including abnormal transactions, to facilitate better management and resolution of pending products.
Enables stores to efficiently manage ongoing transactions, reduce waiting times by releasing holds at the registration stage, and detect potential fraudulent activities, thereby improving operational efficiency and customer service.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a transaction status monitoring device. [Background technology]
[0002] 2. Description of the Related 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] JP 2007-95026 A Summary of the Invention [Problem to be solved by the invention]
[0004] There is known a product sales data processing system in which, when shopping at a store, a customer registers products using his or her own smartphone or a customer terminal device loaned to him or her by the store, and then settles the payment for the registered products using a settlement device installed in the store. In such a product sales data processing system, it is preferable that the store be able to grasp the status of ongoing transactions after product registration has started, by allowing the customer to use the customer terminal device.
[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 which includes a customer terminal device used by customers to register products according to transaction units and a transaction status monitoring device which performs processing related to monitoring transactions, and which includes a display control means for displaying ongoing transaction information which presents information related to transactions which are ongoing since the transaction information was started in response to the start of product registration by the customer terminal device, based on transaction information which reflects the results of product registration on a transaction unit basis performed by the customer terminal device. [Brief description of the drawings]
[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a shopping system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of installation of a settlement device in this embodiment. [Diagram 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 in the present embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device in the present embodiment. [Figure 6] 1 is a diagram illustrating an example of the configuration of a transaction management device in this embodiment. [Figure 7] FIG. 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 an example of customer information, store information, and cart information according to the present embodiment. [Figure 9] FIG. 13 is a diagram showing 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 a customer terminal device, a settlement device, and a transaction management device in this embodiment in response to the accounting of one transaction in self-service operation. [Figure 11] FIG. 2 is a diagram showing an example of a screen of a shopping application in the present embodiment. [Figure 12]13A to 13C are diagrams showing an example of a registered product presentation screen and a screen displayed on a settlement device in this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of an abnormal transaction list screen in this embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a transaction details screen in this embodiment. [Figure 15] 13A and 13B 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. 13 is a diagram showing an example of a hold release screen in the present embodiment. [Figure 17] 11 is a flowchart showing 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] 11 is a flowchart showing an example of a processing procedure executed by the transaction management device and the transaction status monitoring device in the present embodiment in relation to releasing a hold at the registration stage. [Figure 19] 13 is a diagram showing an example of a registered product list screen displayed on the settlement device in this embodiment. FIG. [Figure 20] A figure showing an example of a settlement device operation status screen in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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 in the figure corresponds to accounting (customer terminal-compatible accounting) in which, for example, a customer uses a customer terminal device 50 to register the product to be purchased while taking it from a product shelf, and the same customer also uses a payment device 40 to settle the payment for the registered product. The accounting here refers to a procedure carried out in response to one transaction, including the registration of the product and the settlement of 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, the settlement device 40, and the transaction status monitoring device 80 are installed in a store and are connected to each other so as to be able to communicate with each other via a LAN 19 (which may be wired or wireless). The management device 10 is a business terminal used by a store clerk for store management and the like, and is capable of communicating with the transaction management device 60. The transaction status monitoring device 80 is a business terminal used in a store to monitor the transaction status of a customer who registers a commodity using a customer terminal device 50. The transaction status monitoring function of the transaction status monitoring device 80 includes output by displaying information on the transaction status in the transaction status monitoring device 80, as well as control of transactions, such as releasing the reserved state of a reserved commodity in response to an operation by a store clerk, which will be described later. 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 sending and receiving data to and from the transaction management device 60. Although four settlement devices 40 are illustrated in FIG. 1, the number of settlement devices 40 within one store is not particularly limited.
[0010] The customer terminal device 50 is operated by customers (such as shoppers who are members of the store, hereinafter also referred to simply as customers). 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, that is, recognizes barcodes attached to products. Note that the recognition function of the customer terminal device 50 only needs to be able to read product codes, and does not need to be able to recognize which product the read product code belongs to. In other words, the customer terminal device 50 only needs to be able to read a product code from a barcode that exists as an object in an image captured by the imaging function (an image acquired as a through image).
[0011] Such a customer terminal device 50 may be a smartphone, a tablet terminal, or the like owned by a customer. A shopping application having a function of registering products in accordance with the shopping system of this embodiment is installed in the smartphone, tablet terminal, or the like serving as the customer terminal device 50.
[0012] Furthermore, the customer terminal device 50 may be, for example, a terminal loaned from a store to a customer. An application having a function of registering products in accordance with the shopping system of this embodiment is also installed in the customer terminal device 50 loaned from the store to a customer. The customer terminal device 50 loaned from the store to a customer 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] The customer terminal device 50 also captures an image (e.g., releases the shutter) of the product (e.g., the peripheral portion with a barcode attached) and generates a captured image (image data). The customer terminal device 50 may capture an image by releasing 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 captures an image by releasing the shutter at its own discretion.
[0014] In addition, 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 an imaged subject (object, etc.). For example, the customer terminal device 50 may use the image recognition technology to identify (estimate) an imaged product.
[0015] The settlement device 40 is a settlement device capable of at least cash payment as a settlement method. The settlement device 40 is configured to be able to communicate with the transaction management device 60. The settlement device 40 may be configured to be able to communicate with the transaction management device 60, for example, via 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] Fig. 2 is a diagram showing an example of the installation of the settlement device 40. Fig. 2(A) is a perspective view of the settlement device 40 etc. as seen from the customer side. Fig. 2(B) is a perspective view of the settlement device 40 etc. as seen from the store clerk side. As shown in Fig. 2(A), a counter is placed on the right side of the settlement device 40 as seen from the customer side.
[0019] Fig. 3 is a diagram showing an example of the appearance of the settlement device 40. Fig. 3(A) is a perspective view of the settlement device 40 as seen from the customer side. Fig. 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 of the 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 machine 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, and 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, and stores various types of information used by the CPU 401, including programs.
[0022] The RAM 403 is a read / write memory and stores various 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 information. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information acquired 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 and reads the product code. Customer-side scanner unit 406 may also scan a code (barcode, two-dimensional code, etc.) printed on a bill (registered trademark) and read information required for payment. Customer-side scanner unit 406 may also scan a code (two-dimensional code, etc.) displayed on the display unit of customer terminal device 50 and read information required for payment.
[0025] Although the 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 the 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 uses 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 that the card payment unit 408 includes at least the card recognition unit. The card recognition unit may also recognize various cards (e.g., membership cards, point cards, etc.) that are not directly used for payment (settlement).
[0027] The change machine 409 (cash settlement unit) is a cash settlement mechanism, which 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 outputs the change from the output port. The change machine 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, detecting the number of coins by denomination, etc.).
[0028] That is, the change machine 409 is used when the price of registered products is settled with cash (money) in the settlement device 40. The change machine 409 has a banknote insertion port for inserting banknotes, a coin insertion port for inserting coins, a banknote discharge port for discharging banknotes, a coin discharge port for discharging coins, a counting unit for counting the inserted or discharged money, a money transport mechanism between the insertion port or discharge port and the storage unit, the above-mentioned sensor, etc. The banknote insertion port and the coin insertion port are also referred to as deposit insertion ports. The banknote discharge port and the coin discharge port are also referred to as change discharge ports. The banknote insertion port and the banknote discharge port may be a common port, and the coin insertion port and the coin discharge port may be a common port.
[0029] The change machine 409 also counts the coins replenished during the closing process and stores them in a storage unit. The change machine 409 also counts the coins to be dispensed during the closing process and discharges them from a change discharge port. The closing process is a process of adjusting the amount of money stored in the change machine 409 (cash on hand / cash on hand) to a reference amount after the store is closed or before the store is opened.
[0030] The store clerk's display unit 410 is a touch display for the store clerk, which 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 a barcode attached to a product and reads the product code. The store clerk scanner unit 412 also scans a barcode attached to the name tag of the store clerk and reads the store clerk code.
[0031] Although the store clerk's scanner unit 412 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper) is arranged on the key operation unit 411, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 410, the store 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 freely rotate to change its orientation (direction of the media issuing port) from the clerk side to the customer side and from the customer side to the clerk side. 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 operation mode described below. The correctness of the 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 the 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-responsive settlement mode, which is set to perform settlement processing under customer terminal-responsive 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 operation mode in which the store clerk performs product registration operations and operations corresponding to payment on the payment device 40. The second payment mode is an operation mode in which the store clerk performs product registration operations on the payment device 40, and the customer performs operations corresponding to payment on the same payment device 40. The third payment mode is an operation mode in which the 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 support customer terminal compatible payment, and the other payment devices 40 can be set to, for example, the first or second payment mode so that a store clerk can handle payments in consultation with customers. Note that the other payment devices 40 may also include those set to the third payment mode.
[0035] [Example of customer terminal device configuration] 5 shows an example of the configuration of the customer terminal device 50. The 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, and 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 a main storage device for the CPU 501 . The display unit 504 displays an image 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. Furthermore, 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 wirelessly communicates 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, and controls the operation of the transaction management device 60 by reading and executing programs stored in the memory 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 501, including programs. The RAM 603 is a main storage device for 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 transaction status monitoring device configuration] 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 compatible 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, and 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 within the store, such as the settlement device 40 and the management device 10, via the LAN 19. The network-compatible communication unit 805 is a unit 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 images 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 operators 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 (a customer's registration may be considered to have been completed when the customer information of that customer 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 update the customer information, for example, by referring to the cart information at a specified time every day.
[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 (for example, 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 in 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 when the customer was registered. Cancellation information is information regarding the cancellation of registered products after registration. The customer rank is a rank according to the customer's purchasing 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 actual trading (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 to use a shopping service provided by the transaction management device 60 from an external device (for example, a specified server that provides all applications, the transaction management device 60 itself)). In addition, for example, when registering a customer, the transaction management device 60 acquires information entered into the name field of a registration form (input form) using the customer terminal device 50, and stores it as the customer name. In addition, the transaction management device 60 acquires, for example, 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 the customer information in its own memory unit, 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 carried out. 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 obtain and store store information from an external source (such as a server (not shown) at a headquarters that manages each store). The transaction management device 60 may store some or all of the store information in another device (such as a file server accessible by the transaction management device 60) instead of or in addition to storing the store information in its own memory.
[0045] The product information is, for example, information acquired from 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 for managing individual transactions. The transaction management device 60 generates the cart information at the start of a transaction. In addition, the transaction management device 60 updates the cart information as the transaction progresses (each time a product is registered) (the storage of a product in the cart information may be interpreted as the registration of that product).
[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 each date). The transaction start date and time is the date and time when the transaction starts. The transaction start date and time may be, for example, the date and time when the cart information is generated. The transaction start date and time may be the date and time when the first item of product is registered (the date and time when the registered product information (registered product 1) in FIG. 8(C) is stored). The date and time when the cart information is generated and the date and time when the first item of product is 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 the cart information is generated, the 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 (e.g., 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 a basis for determining whether or not a service such as a time service should be applied and the effect of the application.
[0052] The reserved product information (total) is updated each time a reserved product is registered. A reserved product is a product that was not registered properly due to a certain 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, the number of reserved products that cannot be read (check for unauthorized operations), and the like.
[0053] NO-FILE refers to a product whose barcode or product code was successfully scanned (the product code was successfully read) at the store, but whose 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 has not been scanned at the store. In other words, a read NG refers to a timeout process when it is possible to determine that a product has been imaged for a certain period of time using image recognition technology but has not been able to be recognized as a barcode, or a product that has been timed out. For example, if the barcode cannot be correctly acquired (recognized) despite the customer performing an operation to have the barcode read due to wrinkles in the package, smudges or dirt on the barcode print, 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 reserved product definition corresponding to cart information in this embodiment. In the figure, an example is shown in which reserved products are classified into eight categories. Classification numbers "1" to "8" are assigned to each of the eight reserved product 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 has attempted to have the customer terminal device 50 read the product's code, but the customer terminal device 50 has not been able to read the code properly.
[0059] As a specific example, an example of a "pseudo scan input" corresponds to a situation in which the product is brought into the imaging range of the imaging unit 506, but the product code is not brought into the imaging range of the imaging unit 506. Additionally, a "pseudo scan insertion" situation 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 that does not have a code is captured. Additionally, "pseudo scan insertion" refers to a situation in which a product is brought into the imaging range of imaging unit 506 with the code portion hidden by a finger or the like. In addition, a "pseudo scan input" situation occurs when the code on a product 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 prevents the customer terminal device 50 from reading the code.
[0060] The classification of the reserved product with classification number 4 is “non-scan-inserted.” A reserved product with the “non-scan-inserted” classification is a product that was added to the shopping cart without performing an operation to position the product 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 configured to be able to capture 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's 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 licensed person, such as a pharmacist, to ask the purchaser for confirmation.
[0063] The classification of reserved items with classification number 7 is "anti-theft tag items." "Anti-theft tag items" are items that have anti-theft tags attached and require a store clerk to remove the anti-theft tag from the item when it is sold.
[0064] The classification of the reserved product with classification number 8 is a "cancelled product." A "cancelled product" is a product that was once registered but was cancelled by a customer's cancellation operation on the customer terminal device 50. A "cancelled product" is taken from the customer by a store clerk at the time of payment, for example.
[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 by the transaction management device 60).
[0067] [Example of basic processing procedure for self-operation] The sequence diagram in Fig. 10 shows an example of a processing procedure executed by the customer terminal device 50, the settlement device 40, and the transaction management device 60 in response to the accounting of one transaction in a self-service operation. Specifically, the processing in Fig. 10 shows an example of the processing of the customer terminal device 50, the settlement device 40, and the transaction management device 60 from when a customer registers a product to be purchased from among products displayed in the store, until the settlement of the registered product is completed.
[0068] Step S1: The customer terminal device 50 acquires information for identifying a store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (the two-dimensional code may be output on a display screen, a medium on which the two-dimensional code is printed may be attached, etc.), and a customer who visits the store may scan (read) the two-dimensional code with the customer terminal device 50, thereby allowing the customer terminal device 50 to acquire the store identification information. When a customer who visits the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer who visits the store scans the two-dimensional code with the customer terminal device 50, the shopping application may be started, and a screen informing the customer that the transaction management device 60 is currently connected may be displayed as a start-up screen.
[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, location information may be obtained and a screen may be displayed as a start-up 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 one cannot be identified, a selection screen may be displayed to allow the customer to select. Alternatively, a mode may be switched to forcefully obtain a two-dimensional code.
[0070] 11(A) shows an example of a start-up screen of a 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 wishes to start registering a product for shopping, the customer operates a transaction start button BT10 arranged on the start-up screen. In response to the operation of the transaction start instruction button BT10, the customer terminal device 50 transmits a transaction start request including the acquired store specific information and customer identification information to the transaction management device 60. The transaction start request may be transmitted in response to the customer's operation on the customer terminal device 50 as described above, or may be transmitted in response to the acquisition of store specific information without receiving any particular operation. Regarding the 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 a shopping application on the customer terminal device 50) may be stored in the customer information of the transaction management device 60, but may also be stored in the memory of the customer terminal device 50 in addition to the transaction management device 60. When a store is identified (when the product registration initial screen described below is acquired), the store name, the services being offered (flyer information distributed on that day), and available coupon information may be displayed on a screen (the product registration initial screen or a screen other than the product registration initial screen). The service and coupon information may be acquired from the transaction management device 60 as screen information, for example.
[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 to the store-specific information, the destination information may also be converted into a two-dimensional code, 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-specific 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 in which the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are stored, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, product information (registered product information, reserved 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), so when it receives store identification information (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 store identification information converted into a two-dimensional code, the transaction management device 60 need only 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, and further 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. Also, 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. Also, 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 of 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 the 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 as shown in FIG. 11(B), for example.
[0077] Step S5: The customer terminal device 50 scans the barcode attached to the product by the customer's operation, and reads the product code. In the figure, it is assumed that the barcode has been successfully scanned. Steps S5 to S9 are repeatedly executed every 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 product registration information including the product code obtained by scanning.
[0079] Step S6: The transaction management device 60 receives the product registration information (cart identification information and product code) from the customer terminal device 50 and identifies the cart information of the transaction from the cart identification information included 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 contains a product code for the Nth item, 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 an 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 a list item of the currently registered product has been added to the registered product list, as shown in Fig. 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" is 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 FIG. 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 display screen WD1 may be displayed to display the currently registered product, as shown in Fig. 12(A), for example. In addition, in the registered product display screen WD1 shown in the same figure, in response to the target 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 would like to eat in. In this case, the price of the product is calculated so that the consumption tax rate for the target 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" is 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, a touch of the "Proceed to Checkout" button shown in FIG.
[0086] Step S11: The customer terminal device 50 that has accepted the settlement transition instruction operation generates a two-dimensional code. That is, the customer terminal device 50 converts information required for executing the settlement process for the items purchased by the customer terminal device 50 (e.g., cart identification information) 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 directed by the customer within the recognition range of the customer-side scanner unit 406.
[0088] Step S13: The settlement device 40, which has read the two-dimensional code displayed on the display unit of the customer terminal device 50, requests the calculation of the subtotal amount from the transaction management device 60. For example, the settlement device 40 transmits a calculation request (subtotal calculation request information) requesting the calculation of the subtotal amount to the transaction management device 60 together with the cart identification information obtained from the two-dimensional code.
[0089] Step S14: The transaction management device 60, which has received the cart identification information and the sub-calculation output request information from the customer terminal device 50, identifies the cart information of the transaction from the cart identification information.
[0090] Step S15: After identifying the cart, the transaction management device 60 calculates the subtotal amount using information such as the price 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 transmits the subtotal information indicating the calculated subtotal to the settlement device 40 together with the cart identification information.
[0092] Step S17: The settlement device 40, which has received the cart identification information and the subtotal information from the transaction management device 60, 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 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. In addition, when the settlement is completed, the settlement device 40 sends settlement completion information together with the cart information to the transaction management device 60, and the transaction management device 60 stores the transaction end 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 after moving to another store) other than those scanned in the store (the store when the customer visited the store 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 visits the store (or when the product registration initial screen is displayed). If the two match (or approximately match), the customer terminal device 50 may permit the transmission of the product code of the product to the transaction management device 60, and if they do not match (or approximately match), the customer terminal device 50 may prohibit the transmission of the product code of the product to the transaction management device 60. This makes it possible to prevent inappropriate product registration (for example, registering a product to a cart created in another store, etc.).
[0095] When the settlement device 40 prohibits the transmission of the product code as described above, it may display an error message (e.g., "Registration is not possible because it is not in the XX store") on the customer side display unit 405 after scanning the product. Furthermore, the settlement device 40 may display the above message on the store clerk side display unit 410 instead of or in addition to the message on the customer side display unit 405.
[0096] The settlement device 40 reads the two-dimensional code displayed on the display of the customer terminal device 50 and then requests the transaction management device 60 to calculate the subtotal amount (S13), but may not request calculation of the subtotal amount for products other than the product scanned in the store (for example, products scanned in other stores). For example, the settlement device 40 refers to the store identification information of the store (it may store and refer to the store identification information of the store in its own settlement device 40, or may refer to the 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 permit the request to calculate the subtotal amount if the store identification information included in the cart identification information includes the store identification information of the store, and may prohibit the request to calculate the subtotal amount if the store identification information does not include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payment for products registered at other stores, etc.).
[0097] When the settlement device 40 prohibits the request for the subtotal amount as described above, after reading the two-dimensional code, the settlement device 40 may display an error message (e.g., "Settlement cannot be completed because the transaction includes products not from the XXX store") on the customer-side display unit 405. The settlement device 40 may also display the above message on the store 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 Fig. 10, the transaction management device 60 calculates the subtotal amount. However, for example, the settlement device 40 may acquire cart information from the transaction management device 60 and calculate the subtotal amount based on the acquired cart information. Alternatively, the transaction management device 60 may transmit cart information to the management device 10 and request calculation of the subtotal amount, the management device 10 may calculate the subtotal amount using the received cart information, and the calculated subtotal amount may be transmitted 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 checkout processing, the transaction management device 60 may determine whether or not the product information included in the cart information includes any reserved products, and if so, may request the checkout device 40 to provide instructions to correct the reserved products. Upon receiving a request to provide instructions to correct the reserved products, the checkout device 40 displays a message to notify the user that there are reserved products, as shown in Fig. 12(C). Upon confirming the message, the store clerk may perform an operation to release (correct) the reserved products, such as entering a price corresponding to the reserved products or canceling the reserved products.
[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 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 made using the customer terminal device 50 up to the present time has been made normally. 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 FIG. 9. In other words, an abnormal transaction includes the registration of one or more pending products. Furthermore, an abnormal transaction may include a transaction (a transaction requiring caution) that is determined to be possibly fraudulent by a customer when registering a product using the customer terminal device 50. A transaction requiring caution may include, for example, a transaction in which the number of times that a reserved product is registered due to pseudo-scan input or non-scan input exceeds a certain number. A transaction requiring caution may also include, for example, a transaction by a member designated as a person requiring caution because he or she has committed fraud in the past or may 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 addition, 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 monitor 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), a display command button 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 ongoing transactions that are being handled. 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 out of all ongoing transactions. In this case, the transaction count area AR30-2 is highlighted in a predetermined manner (shown with a bold border in the figure), thereby indicating that a list of ongoing abnormal transactions is being 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 an ongoing transaction list screen of the corresponding ongoing transaction. The display command button BT30-1 is a button that is operated to command a change 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. Since what is displayed in this case is the abnormal transaction list screen, the display instruction button BT30-2 is shown to be in an inoperable state by, for example, being grayed out. The display instruction button BT30-3 is a button 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 that are being handled. In the case of the abnormal transaction list screen in the same figure, a list of abnormal transactions is displayed in the transaction list area AR40. In this case, the transaction list area AR40 shows list items of abnormal transactions from 1st to 10th, 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 performing operations such as scrolling or page forwarding on the transaction list area AR40.
[0109] Each list item in the transaction list area AR40 displays the transaction start time, member number, number of registered products, current total amount for the registered products, and time elapsed since the transaction started. In addition, in the case of a list item of an abnormal transaction as in the case of the same figure, information (cause information) indicating the cause of treating the corresponding transaction as an abnormal transaction 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 with a classification of either "NO-FILE" or "unreadable." The icon labeled "year" indicates that, among the products registered thus far, a reserved product has been registered with a classification of "age verification product." In other words, the classification of the registered reserved product is indicated by the icon. The combination of the icon appearance and the reserved product classification is not particularly limited. For example, an icon having a different appearance may be prepared for each reserved product classification, or a single icon having a certain appearance may be associated with a plurality of reserved product classifications.
[0110] In addition, in the third list item, an icon showing cause information as "basket missing" is displayed. The "basket missing" icon indicates that the cause information includes a product registration result in which a fraudulent act called "basket missing" may have been committed by a customer. The "basket missing" icon may be displayed in response to the registration of a reserved product classified as either "pseudo-scan input" or "non-scan input", for example.
[0111] In addition, an icon marked "Caution" is displayed in the fifth list item. The "Caution" icon indicates that the transaction is made by a member who is registered as a person requiring attention in the member information stored in the transaction management device 60, for example. A member who is suspected of being a person is, for example, a member who has committed fraud in the past or who may have committed fraud, or a member who has not committed fraud but is known to have difficulty operating the customer terminal device 50 or the settlement device 40 every time he or she makes a purchase. For such members who are suspect, 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 products, but also ongoing transactions of members who are suspect 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 of arrangement of the list items 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 an order according to the number of reserved items included in the transaction. The list items in the transaction list area AR40 may be arranged in an order according to the number of all items (including reserved items and items other than reserved items) included in the transaction. The list items in the transaction list area AR40 may be arranged in an order based on the classification of the reserved items included in the transaction. The list items in the transaction list area AR40 may be arranged in an 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 or the like based on location information obtained by the customer terminal device 50 itself measuring its position using a GPS function or the like, or, for example, the communication status between the customer terminal device 50 and a beacon installed at a predetermined position in the store. Specifically, the list items in the transaction list area AR40 may be arranged in order of proximity of the location of the corresponding customer terminal device 50 to the settlement device 40.
[0114] In response to an operation of selecting a list item in the transaction list area AR40, the transaction status monitor device 80 can display a transaction details screen showing details of the transaction corresponding to the selected list item. In addition, 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] Fig. 14 shows an example of a transaction details screen WD20 that is displayed in response to an operation of selecting one of the list items in the transaction list area AR40 of the abnormal transaction list screen of Fig. 13. The transaction details screen WD20 in Fig. 14 is an example in the form of a window that is arranged so as to be superimposed on the abnormal transaction list screen of Fig. 13.
[0116] In the transaction details screen WD20 in the figure, a list of products registered in the target transaction is displayed in association with the time when the products were registered. This allows a store clerk looking at the transaction details screen WD20 to know which products were registered at what time in the target transaction.
[0117] Furthermore, among the product list items on the transaction details screen WD20, the product list items 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 of the corresponding product is being performed by the customer terminal device 50 is displayed. Whether the reserved product is displayed as the highlighting EH or the registration status display TR is determined by 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 this figure, a highlighting EH is provided corresponding to a reserved item classified as "NO-FILE." In addition, in the same figure, the list item for the product "alcohol" is given a highlighting mark EH in response to the classification of the product as a pending product as an "age verification product."
[0120] The registration status display TR corresponds to products that are registered as falling under the category of "cart abandonment." In other words, the registration status display TR is displayed to indicate pending products that are registered as either "pseudo-scan-inserted" or "non-scan-inserted." "Pseudo-scan-inserted" and "non-scan-inserted" are likely to occur when a customer commits fraud by intentionally not allowing the code to be read.
[0121] The store clerk can close the transaction details screen WD20 by performing a predetermined operation. When the transaction details screen WD20 of Fig. 14 is closed, the screen may be configured to return to the state in which the abnormal transaction list screen of Fig. 13 is displayed.
[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 arranged in the same manner as in Fig. 13. Furthermore, the transaction list area SR40 on the all transaction list screen displays a list of all ongoing transactions, the number of which can be displayed on one screen. In this case, too, the clerk can display the list items of the remaining ongoing transactions by scrolling or page-turning the transaction list area SR40. When the display command 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 command 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 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 button BT30-1 is operated while the normal transaction list screen is displayed, the display transitions to the all transaction list screen. Also, when the Display button BT30-2 is operated 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, 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 situation over time as described above. For example, if no pending products were registered up to the second product for a certain ongoing transaction, but the third product is registered as a pending product, then in response to the third product being registered as a pending product, the ongoing transaction is changed from a normal transaction to an abnormal transaction. At this time, if the abnormal transaction list screen is displayed, the ongoing transaction that has been changed to an abnormal transaction is displayed in the transaction list area AR40 with an added list item. In addition, a list item displayed in the transaction list area AR40 of the ongoing transaction list screen may be deleted when settlement of the corresponding ongoing transaction at the settlement device 40 is completed. In addition, 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 as a result of completing 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 in response to the completion of the product registration stage. 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 summary area AR40 may be deleted. In addition, 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 summary 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 the 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, when the registered products include reserved products, the store clerk can perform an operation to release the reserved products at the beginning of the stage where the product registration is completed and the transaction moves to the checkout, as explained with reference to Fig. 12(C). The release of the reserved products at the stage where the transaction moves to the checkout is performed after the product registration is completed by performing the checkout transition instruction operation.
[0126] In the shopping system of this embodiment, since the transaction status monitoring device 80 can display an abnormal transaction list screen, a store clerk monitoring a transaction using the transaction status monitoring device 80 can know that there is an abnormal transaction including a reserved item even when the transaction is in the stage of product registration before moving to the settlement 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 stage of product registration (registration stage release of hold) by operating the transaction status monitoring device 80. By performing the registration stage release of hold in this manner, it becomes unnecessary to release the hold of the reserved item at the settlement device 40, and it becomes possible to distribute the release between the settlement device 40 and the transaction status monitoring device 80. This makes it possible to shorten the total waiting time for release of hold at the settlement device 40, and improve the utilization efficiency of the settlement device 40.
[0127] When a customer who is registering merchandise has 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, who is an operator of the transaction status monitoring device 80, to release the reserved item before performing a payment transition instruction operation. Here, if the registered products include a held product, the customer terminal device 50 may display information directing the customer to a location in the store where the held product can be released, such as the counter described above. For example, a display may be displayed directing the customer to a location in the store where the customer should go. In addition, for example, if the transaction status monitoring device 80 is a portable device and a store clerk carries it while working in the store, the customer can ask the store clerk he or she finds in the store to release the held product.
[0128] The store clerk who has been requested to release the hold confirms, for example, the membership number from the customer and then identifies the relevant transaction from among 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 make it possible to search for the target transaction using, for example, the membership number as a search keyword. In the following explanation, we will use as an example a case where the store clerk displays the transaction details screen WD20 (FIG. 14) for the target abnormal transaction, and then allows the registration stage hold to be released by operating the displayed transaction details screen WD20. 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 again to FIG. 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" that 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 (reservation release screen) for releasing the 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 area is where the store clerk inputs the product code by operating the operation unit 807 of the transaction status monitoring device 80.
[0132] When the store clerk identifies the actual product registered as "NO-FILE", he or she performs an operation to input the product code of the identified product in the product code area AR41. The store clerk can input the product code, for example, by 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 in the product code area AR41. When the product code is entered as above, the store clerk can operate the registration button BT41 to re-register the product registered as "NO-FILE" as a normal product. This will release the reserved product registered as "NO-FILE" and it will be treated as a normally registered product. Also, on the hold release screen in the figure, a cancel button BT42 is arranged. The store clerk may cancel the registration of the held item as a way 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). This 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 of the "NO-FILE" held item changes to a state in which the newly registered information about the item (item name, quantity, price) is displayed, as shown in FIG. 15(B). Furthermore, the list item of the released item displays, as shown in the figure, an indication that the item has been released, such as "released." In other words, the customer terminal device 50 is notified 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," this operation causes an operation screen (reservation release screen) for canceling the reserved item of the "age verification item" to be displayed.
[0135] FIG. 16B is an example of a hold release screen that is displayed in response to the case where a held product of "age verification product" is released from hold. The hold release screen in the figure displays a message to the store clerk urging him or her 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 arranged thereon. If the store clerk is able to confirm that the customer is not a minor, he or she presses the Confirm button BT50 to confirm that the age has been verified. This releases the hold on the "alcohol" product, and it is treated as a properly registered product.
[0136] The age verification by operating the age verification button BT50 may be performed by the customer, not by 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] In addition, when canceling the reservation of a reserved product (pseudo-scan input or non-scan input) 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 the 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 reserved item release screen displayed in response to a case where a reserved item corresponding to the registration status display TR is released from reserved item. In the hold release screen in the figure, a registration status image area AR60 is arranged. 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. In the example in the figure, an example in which three enlarged registration status images epc1 to epc3 are arranged is shown. 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 of the target held product. For example, an enlarged registration status image epc2 is arranged by enlarging the registration status image pic displayed in the registration status display TR, an image captured before the registration status image pic is arranged as the enlarged registration status image epc1, and an image captured after the registration status image pic is arranged as the enlarged registration status image epc3. By looking at such enlarged registration status images epc1 to epc3, the store clerk can accurately grasp how the customer performed the operation of reading the product code of the target held product, compared to the case in which, for example, one registration status image pic is arranged. 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 target product from the customer's shopping cart. The clerk then confirms with the customer whether or not to purchase the target product. If the customer confirms that they will 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 inputting the product code of the target product in the product code input area AR71 and operating the registration button BT61. In addition, when inputting the product code, the customer can also input the product code in the product code area AR41 by operating the search button BT63 to display a 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 manner, 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 process performed by the transaction management device 60 and the transaction status monitor 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: 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 to display an ongoing transaction list screen. 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. 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 causes the display unit 806 to display the received abnormal transaction list screen.
[0144] The ongoing transaction list screen may be in a format such as 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 the processing of step S103, the transaction status monitor device 80 judges whether or not an operation to instruct switching to the all transaction list screen (all transaction list screen switching operation) has been received. The all transaction list screen switching operation is an operation performed on the display instruction button BT30-1 when the ongoing transaction list screen currently being displayed is either the abnormal transaction list screen or the normal transaction list screen.
[0146] Step S105: When the operation to switch to the all-transaction list screen is accepted, the transaction status monitor device 80 transmits 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 causes the display unit 806 to display the received all-transaction list screen.
[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 is not performed, the transaction status monitoring device 80 determines whether or not an operation instructing 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 ongoing transaction list screen currently being displayed 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 monitoring device 80 sends a request for the normal transaction list screen 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 causes the display unit 806 to display the received normal transaction list screen.
[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 instructing switching to an abnormal transaction list screen (abnormal transaction list screen switching operation) has been accepted. The abnormal transaction list screen switching operation is an operation performed on the display instruction button BT30-2 when the ongoing transaction list screen currently being displayed is either the all transaction list screen or the normal transaction list screen. If an 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 judges whether or not 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 update screen is received, the transaction status monitor 80 updates the currently displayed ongoing transaction list screen with the received screen. As a result, the transaction list area AR40 of the currently on-sale ongoing transaction list screen reflects the new occurrence or completion changes that occur for the corresponding ongoing transaction.
[0154] Step S113: After the process of step S112, or if it is determined in step S111 that the updated screen has not been received, the transaction status monitor device 80 determines whether the display of the ongoing transaction list screen has been terminated. The display of the ongoing transaction list screen is terminated, 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 FIG.
[0155] Next, an example of a 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 shows 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 that does not include any pending items among the registered items from the cart information. 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 as steps S5 to S7 in FIG. 10, each time a product is scanned by the customer terminal device 50, the transaction management device 60 updates the cart information by registering the product according to the scan result. After processing of 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 or not 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 being displayed on the transaction status monitoring device 80. Specifically, when the abnormal transaction list screen is being displayed as the ongoing transaction list screen on the transaction status monitoring device 80, the transaction management device 60 determines that the corresponding cart information has been updated when a product is added, deleted, etc. to cart information that previously included a reserved product. The transaction management device 60 also determines that the corresponding cart information has been updated when cart information that previously did not include a reserved product in its registered products is changed to include a reserved product. The transaction management device 60 also determines that the corresponding cart information has been updated when at least one of the reserved products that was previously included in the registered products is released from reservation. The transaction management device 60 also determines that the corresponding cart information has been updated when a transaction is completed for cart information that previously included a reserved product in its registered products. 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 when an item is added, canceled, etc. to any of the cart information currently in an ongoing transaction, when new cart information is generated in response to the start of a new transaction, or when a transaction is completed for any of the stored cart information. 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 when an item is added, canceled, etc. to any of the cart information that does not currently include any pending items, when new cart information is generated in response to the start of a new transaction, or when a transaction is completed for cart information that does not include any pending items. 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 is one of an abnormal transaction list screen, a all 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 are 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, an example of the processing procedure executed by the transaction status monitoring device 80 and the transaction management device 60 in relation to releasing a reserved product (release of a reserved product at the registration stage) before product registration is completed (before the settlement transition instruction operation is performed) will be described.
[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 being displayed, the transaction status monitoring device 80 accepts an operation performed by a store clerk to specify a target product to be released from hold (target product specification operation). The target product specification operation is an operation to select a list item of the highlighted display EH or a list item of the registered status display TR among the list items of the registered products displayed on the transaction details screen D20. In other words, the target product specification operation is an operation to select a list item of the held product.
[0163] Step S302: In response to receiving the target product designation operation, the transaction status monitoring device 80 displays a reservation release screen for the reserved product designated by the target product designation operation.
[0164] Step S303: The store clerk performs an operation (a hold release operation) corresponding to the hold release of the held item on the displayed hold release screen. 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 identifying the held product information of the held product that has been released from hold (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 identified by the product identification information to the registered product information. Such update results are reflected on the abnormal transaction list screen displayed on the transaction status monitor 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 process 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 shown as a reserved product changes to a state in which the product has been released from reservation, 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 hold at the registration stage 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 hold at the registration stage 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 this figure, the display "Released" has been added to the list item for "XX Chocolate", which was a reserved product. This display "Released" indicates that the product "XX Chocolate" has been reregistered as a product by releasing the reservation at the registration stage. In addition, in the registered product list in the figure, the item "Chu-hai" is crossed out with a double line. This indicates that the "Chu-hai" product, which was registered as a reserved product, has been cancelled at the registration stage to release the reserved item.
[0170] <Modification> Modifications of the present 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 a display mode of the operating status of the settlement device 40 in the transaction status monitoring device 80. The figure shows an example of displaying the operating status of the settlement device 40 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 (settlement machine). When 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, when the corresponding settlement device 40 is stopped, the corresponding settlement device 40 can be operated by operating the operation operation button BT50.
[0173] The clerk can see how many transactions are currently being registered by looking at the ongoing transaction list screen displayed on the transaction status monitoring device 80. The clerk can also determine whether the number of settlement devices 40 currently in operation is appropriate for the number of transactions currently being registered by looking at the settlement device operation status screen WD30. Here, when the clerk determines that the number of settlement devices 40 currently in operation is small, the clerk can quickly operate the required number of settlement devices 40 that are currently stopped by operating the operation operation button BT50 on the settlement device operation status screen WD30. When the clerk determines that the number of settlement devices 40 currently in operation is large, the clerk can quickly stop the required number of settlement devices 40 that are currently in operation by operating the operation operation button BT50 on the settlement device operation status screen WD30.
[0174] [Second modified example] Incidentally, fraudulent acts by customers may occur not only at the product registration stage but also at the settlement stage. In other words, there is a possibility that fraudulent acts may be committed by a customer while the customer is making a settlement at the settlement device 40. Thus, in this modified example, in response to a determination that there is a possibility that a customer is committing fraud at the settlement device 40, the transaction status monitoring device 80 may display information regarding the settlement device 40 where there is a possibility that a customer is committing fraud.
[0175] One fraudulent act performed by the settlement device 40 is to have the settlement device 40 read a two-dimensional code stored in the customer terminal device 50 by the screenshot function. Specifically, for example, when a customer registers one product using the customer terminal device 50, the customer performs a settlement transition instruction operation to display a two-dimensional code on the code display screen. The customer 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 goes to the settlement device 40. The customer displays the stored image data of the two-dimensional code on the customer terminal device 50 and has the settlement device 40 read it. In this case, the customer can make it appear as if he or she has purchased many products placed in the shopping cart by performing settlement corresponding to one product 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 based on whether or not the interval between the time when the settlement transition instruction operation is performed and the time when the settlement device 40 is caused to read the two-dimensional code is equal to or greater than a certain value.
[0176] When the transaction management device 60 determines that fraud may have occurred at the settlement device 40, it transmits a fraud occurrence notification to the transaction status monitoring device 80. The fraud occurrence notification includes information indicating the settlement device 40 where fraud may have occurred. The fraud occurrence notification may also include information indicating the content and type of fraud. In response to receiving the fraudulent occurrence notification, the transaction status monitoring device 80 displays a fraudulent occurrence notification screen based on the received fraudulent occurrence notification. The fraudulent occurrence notification screen indicates which settlement device 40 may be the one in which fraud has possibly been committed. Furthermore, the fraudulent occurrence notification screen may display information indicating the content and type of fraud.
[0177] [Third Modification] In the above embodiment, the reserved product is released from the reserved state by operating the transaction status monitoring device 80. The reserved product may be released from the reserved state by, for example, a store clerk pressing an electronic stamp on the screen displayed on the display unit of the customer terminal device 50, in addition to operating the transaction status monitoring device 80.
[0178] In this case, the shopping application of the customer terminal device 50 is capable of displaying an electronic stamp screen on which an electronic stamp is pressed to release the held item when the registered items include a 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 one selected held item, for releasing all held items, or for releasing held items that fall into a predetermined classification.
[0179] The store clerk presses the electronic stamp on the display surface of display unit 504 on which the electronic stamp screen is displayed. In response to the electronic stamp being pressed, the customer terminal device 50 transmits a notification (hold release notification) to the transaction management device 60 that the subject held item has been released from hold. The transaction management device 60 updates the cart information to reflect the release of the held 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 of the corresponding transaction on the ongoing transaction list screen so that the hold release processing result indicated by the received information is reflected.
[0181] [Fourth Variation] The product registration results of a transaction carried out using one customer terminal device 50 may be handed over to another customer terminal device 50, allowing the customer to continue to register products for the same transaction using the other customer terminal device 50. For example, when a customer is using his / her own customer terminal device 50 to register a product, the customer terminal device 50 may run out of battery power, but since it is not possible to charge it immediately, it may become difficult to continue the product registration. Also, when a customer is using the customer terminal device 50 to register a product, 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 result by the customer terminal device 50 that he / she has been using and redo the product registration from the beginning, for example, by using another customer terminal device 50 lent 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 not efficient. Therefore, by transferring the product registration results of one customer terminal device 50 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 from the beginning.
[0182] The handover of the 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 has been used for product registration can no longer be used, the customer requests, for example, a clerk at the store's service counter, to take over use of another customer terminal device 50. The clerk who receives the request causes a takeover code to be displayed on the original customer terminal device 50, for example, by performing a predetermined operation on the original customer terminal device 50 that the customer has been using up until now. 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 makes the customer terminal device 50 of the transfer destination, which is, for example, a store terminal for loan 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. The transaction management device 60 that has received the takeover request 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 of the takeover destination. The customer terminal device 50 of the takeover destination displays the product registration screen based on the received product registration screen information, and becomes capable of executing processing according to subsequent product registration operations. In other words, the customer terminal device 50 of the takeover destination takes over the product registration results from the customer terminal device 50 of the takeover source, and is capable of executing processing according to subsequent product registrations. The store clerk takes over the product registration results as described above and hands the customer the customer terminal device 50 which is ready for product registration. In addition, as described above, in order for the next customer terminal device 50 to take over the product registration results and become capable of registering products, the customer may also be allowed to perform an operation to read the code.
[0183] [Fifth Modification] The transaction list screen as shown in FIG. 13 may be displayed, for example, on a device other than the transaction status monitoring device 80 and installed in a 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. Also, for example, it may be displayed on a mobile terminal carried by a store clerk while performing his / her duties. Also, it may be displayed on an integrated management device provided, for example, at a headquarters or the like, 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 reflecting the integrated status of transactions of 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, for example, 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 of which is responsible for a part of the processing and working together. 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] <Overview of the embodiment> [Technical field] The present invention relates to a product sales data processing system. [Background technology] 2. Description of the Related 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] There is known a product sales data processing system in which, when shopping at a store, a customer registers products using his or her own smartphone or a customer terminal device loaned to him or her by the store, and then settles the payment for the registered products using a settlement 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 has an object 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 including a customer terminal device (50) used by a customer to register products according to a transaction unit, and a transaction status monitoring device (80) for performing processing related to monitoring of transactions, the transaction status monitoring device including a display control means for displaying ongoing transaction information (e.g., an ongoing transaction list screen) 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.
[0187] According to the above configuration, in this embodiment, information about a transaction currently in progress (e.g., an ongoing transaction list screen) can be output by the transaction status monitoring device 80 when the customer currently uses the customer terminal device 50 to register a product. In other words, the store can grasp the status of ongoing transactions performed by the customer using the customer terminal device 50 to register a product.
[0188] (2) One aspect of this embodiment is the transaction status monitoring device 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 items among their registered items, 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 the transaction content of an ongoing transaction selected from the ongoing transactions presented on the ongoing transaction list screen, for example. As the details of the transaction content, for example, registered products can be displayed corresponding to the time, as shown on the transaction details screen WD20 of Fig. 14. Furthermore, for registered products that have been registered as pending products, the pending products may be displayed in a distinguished manner from normally registered products, for example, by changing the state of the list item of the relevant product so that the fact of being pending can be understood by highlighting EH, registering status display TR, etc.
[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 by a customer terminal device.
[0193] According to the above configuration, a registration status image showing the status when a product is registered in an ongoing transaction is displayed. By looking at such a registration status image, the store clerk can accurately understand what the product actually was that was registered as a reserved product and the reason why it was registered as a reserved product.
[0194] (5) One aspect of this embodiment is a transaction status monitoring device as described in any one of (1) to (4), comprising a hold release means for controlling the release of a hold of a reserved item that was not properly registered and was registered in a held 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 item has been released from reservation.
[0197] According to the above configuration, it is possible to notify the customer that the reserved item has been released from the reserved item by the customer terminal device 50. This allows the customer to accurately understand that the reserved item has been released from the reserved item.
[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 the ongoing transaction presented by the ongoing transaction information includes information indicating the type of customer terminal device being used to register the product corresponding to the ongoing transaction.
[0199] When a customer registers a product at a store, the customer may use either a mobile terminal that the customer has or a terminal that the store lends to the customer, and there may be cases where multiple types of customer terminal devices 50 are available. According to the above configuration, in such cases, it is possible to show which type of customer terminal device 50 is being used for each ongoing transaction on the ongoing transaction list screen.
[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 regarding the operation of a settlement device that performs settlement processing using settlement information based on transaction information that reflects the results of product registration on a transaction basis 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 operation status of the settlement devices 40. This allows the store clerk to obtain effective information for appropriately operating the store, such as determining the number of settlement devices 40 to operate, based on the status of ongoing transactions and the operation status of the settlement devices 40.
[0202] In addition, a program for realizing 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 above in each of the above embodiments may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing as the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction status monitoring device 80, etc. described above. Here, "reading 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. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside the distribution server and accessible to distribute the program. The code of the program stored in the distribution server's recording medium may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined in the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds the program for a certain period of time, such as a volatile memory (RAM) in a computer system that becomes a server or a client when the program is transmitted via a network. The program may be for realizing part of the above-mentioned functions.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 for performing processing related to monitoring of transactions, A display control means for displaying on the same screen the number of customer terminal devices requiring the assistance of a store clerk regarding the result of the product registration based on transaction information reflecting the result of the product registration for each transaction performed by the customer terminal device, and a transaction list area presenting a list item in which information identifying the customer terminal device is associated with the status of the transaction corresponding to the product registration performed by the customer terminal device at the bottom of the screen. A transaction status monitoring device comprising:
2. The information for identifying the customer terminal device includes information indicating a 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 for performing processing related to monitoring of transactions, A display control means for displaying on the same screen the number of customer terminal devices requiring the assistance of a store clerk regarding the result of the product registration based on transaction information reflecting the result of the product registration for each transaction performed by the customer terminal device, and a transaction list area presenting a list item in which information identifying the customer terminal device is associated with the status of the transaction corresponding to the product registration performed by the customer terminal device at the bottom of the screen. A program to function as a
4. The information for identifying the customer terminal device includes information indicating a type of the customer terminal device. The program according to claim 3.
