Product sales data processing system and program

Abstract

To enable an item sales data processing system in which customers themselves register items using mobile terminals to efficiently resolve inadequate item registration results.SOLUTION: An item sales data processing system for registering items based on item registration operation by a customer using a portable terminal device includes: acquisition control means for allowing a monitoring device used by a clerk to acquire registration defective item information concerning a defective item for which the registration result is defective when the registration result of the item based on the item registration operation is defective; display control means for displaying on the monitoring device a screen based on the registration defective item information acquired by the acquisition control means; and normal registration means for registering the registration defective item as a normal item in response to an input of registration complementary information to the displayed screen.SELECTED DRAWING: Figure 14

Description

Technical Field

[0001] The present invention relates to a product sales data processing system, and and a program.

Background Art

[0002] A system in which customers themselves register products using a mobile terminal is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a product sales data processing system in which customers themselves register products using a mobile terminal, the registration result of a product may be incomplete. For a product with an incomplete registration result, for example, the incomplete state of the registration result is eliminated by the operation of a store clerk. It is preferable that such elimination of the incomplete state of the registration result is performed efficiently.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to enable the elimination of an incomplete state of a product registration result to be performed efficiently in a product sales data processing system in which customers themselves register products using a mobile terminal.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-mentioned problems is a product sales data processing system in which a customer registers a product based on a product registration operation using a mobile terminal device, comprising: an acquisition control means that causes a monitoring device used by a store employee to acquire information on a product that was not properly registered when the product registration result based on the product registration operation is incomplete; a display control means that causes the monitoring device to display a screen based on the product information that was not properly registered acquired by the acquisition control means; and a normal registration means that performs a normal registration in which the product that was not properly registered is registered as a normal product when registration supplementation information is input to the displayed screen.

[0007] Furthermore, one aspect of the present invention is a program that causes a computer in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device to function as an acquisition control means that causes a monitoring device used by a store employee to acquire information about products that were not properly registered when the product registration result based on the product registration operation was incomplete; a display control means that causes the monitoring device to display a screen based on the information about products that were not properly registered acquired by the acquisition control means; and a normal registration means that performs a normal registration in which the products that were not properly registered are registered as normal products in response to the input of registration completion information on the displayed screen.

[0008] Furthermore, one aspect of the present invention is a monitoring device used by a store employee in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device, the monitoring device comprising: an acquisition means for acquiring incomplete product information relating to a product whose registration result was incomplete when the product registration result based on the product registration operation was incomplete; a display control means for displaying a screen based on the incomplete product information acquired by the acquisition means; and a normal registration means for performing a normal registration in which the incomplete product is registered as a normal product in response to the input of registration supplementation information to the displayed screen.

[0009] Furthermore, one aspect of the present invention is a program that causes a computer used as a monitoring device by a store employee in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device to function as an acquisition means for acquiring incomplete product information regarding incompletely registered products when the product registration result based on the product registration operation is incomplete; a display control means for displaying a screen based on the incompletely registered product information acquired by the acquisition means; and a normal registration means for performing normal registration in which the incompletely registered product is registered as a normal product in response to the input of registration supplementation information to the displayed screen.

[0010] Furthermore, one aspect of the present invention is a server device provided in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device, the server device comprising: an acquisition control means that causes a monitoring device used by a store employee to acquire information on products with incomplete registration results when the product registration result based on the product registration operation is incomplete; a display control means that displays a screen based on the incomplete registration information acquired by the acquisition control means on a monitoring device operated by a store employee; and a normal registration means that performs normal registration in which the incomplete registration product is registered as a normal product in response to the input of registration supplementation information on the screen displayed on the monitoring device. [Brief explanation of the drawing]

[0011] [Figure 1] This is a diagram showing an example of the configuration of the shopping system in this embodiment. [Figure 2] This figure shows an example of the installation of the payment device in this embodiment. [Figure 3] This figure shows an example of the appearance of the settlement device in this embodiment. [Figure 4] This figure shows an example of the configuration of the settlement device in this embodiment. [Figure 5] This figure shows an example of the configuration of the customer terminal device in this embodiment. [Figure 6]This figure shows an example of the configuration of the transaction management device in this embodiment. [Figure 7] This figure shows an example of the configuration of the monitoring device in this embodiment. [Figure 8] This figure shows an example of customer information, store information, and shopping cart information in this embodiment. [Figure 9] This figure shows an example of the definition of a reserved product in this embodiment. [Figure 10] This sequence diagram shows an example of a processing procedure executed by the customer terminal device, settlement device, and transaction management device in this embodiment in response to the accounting of a single transaction in self-service operation. [Figure 11] This figure shows an example screen of the shopping application in this embodiment. [Figure 12] This figure shows an example of the screen displayed on the registered product presentation screen and the payment device in this embodiment. [Figure 13] This figure shows examples of the hold release guidance screen, hold release waiting screen, hold release confirmation screen, and product registration screen in this embodiment. [Figure 14] This figure shows an example of a product information input screen in this embodiment. [Figure 15] This flowchart shows an example of the processing procedure performed by the customer terminal device, transaction management device, and monitoring device in this embodiment in relation to the release of unspecified products from the hold. [Modes for carrying out the invention]

[0012] <Embodiment> [Example of a shopping system configuration] Figure 1 shows an example configuration of the shopping system (an example of a product sales data processing system) of this embodiment. The shopping system in the figure corresponds to an accounting system (customer terminal-based accounting) in which, for example, a customer registers the items they intend to purchase by taking them from the shelves using a customer terminal device 50, and the same customer also settles the payment for the registered items using a payment device 40. Accounting here refers to a procedure that includes the registration of items and the settlement of the registered items, and is performed in accordance with one transaction. 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 monitoring device 80, and a credit card payment server 70.

[0013] The management device 10, the settlement device 40, and the monitoring device 80 are installed in the store and are communicably connected 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 communicable with the transaction management device 60.

[0014] The monitoring device 80 is a business terminal that monitors the status of transactions performed by customers using the customer terminal device 50 in the store, and is communicable with the transaction management device 60. In FIG. 1, four settlement devices 40 are illustrated, but the number of settlement devices 40 within one store is not particularly limited.

[0015] The customer terminal device 50 is operated by a customer (such as a shopper who is a member of the store, hereinafter simply referred to as a customer). In addition to a general communication function and imaging function (camera), the customer terminal device 50 has a recognition function for scanning a barcode attached to a product to read the product code, that is, for recognizing the barcode attached to the product. Note that the recognition function provided in the customer terminal device 50 only needs to be able to read the product code, and does not necessarily need to be able to recognize which product the read product code belongs to. That is, as long as the customer terminal device 50 can read the product code from the barcode when the barcode exists as an object within the captured image (the image acquired as a through image) captured by the imaging function, it is sufficient.

[0016] Such a customer terminal device 50 may be a smartphone, a tablet terminal, or the like owned by the customer. A shopping application having a function of performing product registration corresponding to the shopping system of this embodiment is installed in a smartphone, a tablet terminal, or the like as the customer terminal device 50.

[0017] Furthermore, the customer terminal device 50 may be, for example, a terminal lent to the customer by the store. The customer terminal device 50 lent to the customer by the store will also have an application installed that has the function of registering products in accordance with the shopping system of this embodiment. The customer terminal device 50 lent to the customer by the store may be in a form that the customer holds in their hand, or it may be in a form that the customer uses while attached to a shopping cart, for example.

[0018] Furthermore, the customer terminal device 50 captures an image of the product (for example, the surrounding area with a barcode) (for example, by taking a picture) and generates an image (image data). The customer terminal device 50 may take the image by taking a picture according to the operation of the customer, who is the operator, but in this embodiment, it is preferable that the customer terminal device 50 takes the image by taking a picture based on its own judgment.

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

[0020] The settlement device 40 is a settlement device that allows payment by at least cash as a settlement method. The settlement device 40 is configured to communicate with the transaction management device 60. The settlement device 40 may also be configured to communicate with the transaction management device 60, for example, via a relay of the management device 10.

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

[0022] The credit card payment server 70 executes payment processing corresponding to the credit card in response to credit card payment requests sent from the settlement device 40, customer terminal device 50, etc.

[0023] [Regarding the payment system] Figure 2 shows an example of the installation of the payment device 40. Figure 2(A) is a perspective view of the payment device 40 etc. as seen from the customer's side. Figure 2(B) is a perspective view of the payment device 40 etc. as seen from the employee's side. As shown in Figure 2(A), the counter is placed to the right of the payment device 40 as seen from the customer's side.

[0024] Figure 3 shows an example of the appearance of the payment device 40. Figure 3(A) is a perspective view of the payment device 40 from the customer's side. Figure 3(B) is a perspective view of the payment device 40 from the employee's side. Figure 4 shows an example of the configuration of the payment device 40. In Figures 3 and 4, the same parts are denoted by the same reference numerals.

[0025] The following describes an example configuration of the payment device 40 shown in Figure 4, with reference to Figure 3. The payment device 40 comprises a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a customer-side display unit 405, a customer-side scanner unit 406, a card payment unit 408, a change dispenser 409, a staff-side display unit 410, a key operation unit 411, a staff-side scanner unit 412, a printing unit 413, an audio output unit 414, and a communication unit 415. These units can communicate with each other via a bus.

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

[0027] RAM403 is a read / write memory that stores various types of information. For example, RAM403 stores information read from ROM402 and hard disk 404, information obtained from external sources, and information generated during processing.

[0028] The hard disk 404 stores various types of information. For example, instead of the ROM 402, the hard disk 404 may store programs executed by the CPU 401. Alternatively, instead of the RAM 403, it may store information read from the ROM 402, information obtained from external sources, information generated during processing, etc.

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

[0030] The customer-side scanner unit 406 is used when the customer registers products, but the customer may register products by other means. For example, if a preset key (a button to order a product) corresponding to a product is displayed on the customer-side display unit 405, the customer may register the product by operating (pressing) the preset key.

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

[0032] The change dispenser 409 (cash settlement unit) is a cash settlement mechanism that has an input slot for banknotes and coins, and an output slot for banknotes and coins. It calculates the amount to be inserted into the input slot, calculates the change amount which is the difference between the inserted amount and the purchase amount, and dispenses the change from the output slot. The change dispenser 409 is facing the customer and is operated by the customer. When banknotes or coins are inserted into the input slot, it is detected by a sensor (detection of the insertion, detection of the number of coins of each denomination, etc.).

[0033] In other words, the change dispenser 409 is used in the settlement device 40 when settling the price of registered goods in cash (currency). The change dispenser 409 has a banknote slot for inserting banknotes, a coin slot for inserting coins, a banknote outlet for dispensing banknotes, a coin outlet for dispensing coins, a counting unit for counting the currency being inserted or dispensed, a currency transport mechanism between the insertion or dispensing slot and the storage unit, and the aforementioned sensors. The banknote slot and coin slot are also referred to as deposit slots. The banknote outlet and coin outlet are also referred to as change dispensers. The banknote slot and banknote outlet may be the same, and the coin slot and coin outlet may be the same.

[0034] Furthermore, the change dispenser 409 counts the money replenished during closing procedures and stores it in the storage compartment. Also, the change dispenser 409 counts the money to be dispensed during closing procedures and dispenses it from the change dispenser. Closing procedures refer to the process of adjusting the amount of money stored in the change dispenser 409 (cash balance / cash balance) to a base amount after closing or before opening.

[0035] The employee-side display unit 410 is a touch display for employees, which displays various information to employees and accepts various inputs from them. The key operation unit 411 consists of various keys (buttons) and accepts various inputs from store staff. The employee-side scanner unit 412 is a scanner unit for employees, and for example, it scans barcodes attached to products to read product codes. The employee-side scanner unit 412 also scans barcodes attached to employee name tags to read employee codes.

[0036] The employee-side scanner unit 412 is used when an employee registers a product, but the employee may register a product by other means. For example, if the key operation unit 411 has keys corresponding to products (for example, a key corresponding to a sports newspaper), the employee may register the product by operating (pressing) those keys. Also, if the employee-side display unit 410 displays preset keys corresponding to products, the employee may register the product by operating those preset keys.

[0037] The printing unit 413 prints and issues various media (receipts, payment slips, etc.). The printing unit 413 can rotate freely to change its orientation (direction of the media issuing slot) from the employee side to the customer side and from the customer side to the employee side. The orientation of the printing unit 413 may be changed manually, or it may be changed automatically (mechanically controlled, etc.) in accordance with the transition (switching) of the operation mode described later. The correctness of the orientation of the printing unit 413 may be detected by a sensor or other means.

[0038] The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs voice guidance, etc. The communication unit 415 performs communication with other devices (other settlement devices 40 and management devices 10).

[0039] Furthermore, the settlement device 40 of this embodiment can switch between a total of four operating modes: a customer terminal-compatible settlement mode, which is set to perform settlement processing under customer terminal-compatible accounting, and three accounting modes (1st to 3rd accounting modes), each corresponding to three different accounting patterns (product registration and settlement). The first checkout mode is an operating mode in which a store employee performs operations corresponding to product registration and operations corresponding to payment on the payment device 40. The second checkout mode is an operating mode in which a store employee performs operations corresponding to product registration on the payment device 40, and a customer performs operations corresponding to payment on the same payment device 40. The third checkout mode is an operating mode in which a customer performs operations corresponding to product registration and operations corresponding to payment on the payment device 40. As a result, in stores that have introduced the shopping system of this embodiment, some of the payment devices 40 can be configured to support customer terminal-based payment by setting a customer terminal-compatible payment mode, while the other payment devices 40 can be configured, for example, to be configured to a first payment mode or a second payment mode, so that store staff can interact with customers and handle the payment. It should be noted that some of the other payment devices 40 may be configured to be configured to a third payment mode.

[0040] [Example of customer terminal system configuration] Figure 5 shows an example configuration of a customer terminal device 50. The customer terminal device 50 in the figure comprises a CPU 501, a storage unit 502, a RAM 503, a display unit 504, an operation unit 505, an imaging unit 506, and a network-compatible communication unit 507. The CPU 501 is a central processing unit that controls the operation of the customer terminal device 50 by reading and executing programs stored in the memory unit 502. The memory unit 502 is an auxiliary storage device for the CPU 501, and stores various types of information used by the CPU 501, including programs. RAM503 is the main memory of CPU501. The display unit 504 displays an image in accordance with the display control of the CPU 501. The display unit 504 may be configured as a touch panel that allows operation of the screen. The operation unit 505 collectively refers to the various controls provided on the customer terminal device 50 and the various input devices connected to the customer terminal device 50. The imaging unit 506 performs imaging in accordance with the control of the CPU 401. Furthermore, the imaging unit 506 in this embodiment can also function as the part that reads the 2D code in a code reader that processes 2D codes. The network-enabled communication unit 507 is a component that communicates wirelessly over a network. The network-enabled communication unit 507 enables the customer terminal device 50 to communicate with the transaction management device 60.

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

[0042] The storage unit 602 of the transaction management device 60 stores customer information, store information, product master (product information), and cart information.

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

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

[0045] Figure 8(A) shows an example of customer information stored in the storage 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, points, etc. Customer identification information is identification information that uniquely identifies a customer. The customer identification information may also be application identification information, which is uniquely assigned to each installed shopping application when the shopping application of this embodiment is installed. The application identification information may be a number uniquely assigned (for example, sequentially) to each installed shopping application. Alternatively, the application identification information may be terminal identification information unique to the customer terminal device 50 on which the shopping application is installed. The terminal identification information may be hardware identification information unique to the hardware of the customer terminal device 50, such as a telephone number assigned to the customer who is a user of the customer terminal device 50, or a MAC (Media Access Control) address. The customer name is the customer's name or nickname. The customer registration date is the date and time the customer registered. Cancellation information is information regarding the cancellation of registered products after registration. The customer rank is a rank based on the customer's purchase history. When generating customer information for a new customer, customer identification information, customer name, and customer registration date are generated, but other information (such as cancellation information) is not generated because it is before the start of actual transactions (product registration).

[0046] The transaction management device 60 generates and stores customer identification information, for example, when a customer registers (for example, when the customer terminal device 50 downloads or installs a shopping application from an external source (for example, a predetermined server providing the application in general, or the transaction management device 60) to use the shopping service provided by the transaction management device 60). The transaction management device 60 also retrieves information entered in the name field of the registration form (input form) using the customer terminal device 50 during customer registration and stores it as the customer name. The transaction management device 60 also retrieves the current date and time at the time of customer registration and stores it as the customer registration date.

[0047] In addition, 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) instead of storing the customer information in its own internal storage unit.

[0048] Figure 8(B) shows an example of store information stored in the storage unit 602 of the transaction management device 60. The store information in this figure includes store identification information, store name (branch name), store specific information 1, and store specific information 2. Store identification information is identification information that uniquely identifies a store. The store identification information shown in Figure 8(B) consists 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 Figure 8(B) consists of the store (business name) or company name and the branch name. Store identification information 1 is information about a two-dimensional code (such as a QR code (registered trademark)) used to identify the store where the transaction takes place (the store where the goods are bought and sold). Store identification information 2 is the location information (GPS information) of the store where the transaction will take place, used to identify the store. Note that in the example shown in Figure 8(B), the store identification information and store specific information 1 are different, but the store identification information and store specific information 1 may be the same.

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

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

[0051] Figure 8(C) shows an example of cart information stored in the storage unit 602 of the transaction management device 60. The cart information in the diagram includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, cart product information (registered product information, pending product information), cancellation information, etc.

[0052] Cart identification information is identification information that uniquely identifies the cart information. For example, cart identification information includes store identification information, date, and serial number (e.g., a store-specific serial number for each date). The transaction start date and time is the date and time when the transaction begins. For example, the transaction start date and time may be the date and time when the shopping cart information was generated. Alternatively, the transaction start date and time may be the date and time when the first item was registered (the date and time when the registered item information (registered item 1) in Figure 8(C) was stored). The shopping cart information generation date and time and the registration date and time of the first item may be stored separately.

[0053] The transaction end date and time is the date and time when the transaction ends. For example, the transaction end date and time may be the settlement date and time. The customer identification information is the customer identification information that identifies the customer for the transaction. Note that when cart information is generated, cart identification information, transaction start date and time, and customer identification information are generated, but other information (such as the transaction end date and time) is not generated because it is before the actual transaction (product registration) has started. 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.

[0054] The Registered Product Information (Total) is updated each time a product is registered. It includes the number of items, the estimated subtotal amount (e.g., the subtotal amount before any discounts are reflected), and the total subtotal amount. Registered Product Information (Registered Product 1) is the registration information for one product. Registered Product Information (Registered Product 2) is the registration information for two products. Note that in the example shown in Figure 8(C), the illustrations for Registered Product Information (Registered Product 3) to Registered Product Information (Registered Product 5) are omitted. Registered Product Information (N; N is an integer) includes the product code, product name, price, etc.

[0055] The registered product information (N) may include the registration date and time of the N product. In other words, the transaction management device 60 may store the registration date and time of the registered product as 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-limited service is applicable and the effect after its application.

[0056] The "Holding Product Information (Total)" is updated each time a holding product is registered. A pending product is a product that was temporarily placed on hold because it could not be registered properly due to certain factors. The total pending product information includes the number of pending products (number of items), the number of non-file pending products, and the number of pending products that cannot be read (requires verification of fraudulent operation).

[0057] NON-FILE refers to products where the barcode or product code was successfully scanned in the store (the product code could be read), but the product code is not stored in the product master's product information (products with unregistered product information).

[0058] "Reading Failed" refers to a situation where the product code scan failed at the store (the product code could not be read), or a product for which the product code scan failed at the store. In other words, "Reading Failed" means that, for example, image recognition technology detects that a product has been imaged for a certain period of time but barcode recognition has not been achieved, and a timeout is triggered when this occurs; the product is one that has been timed out. For example, if the barcode cannot be properly acquired (recognized) despite the customer attempting to scan it, due to reasons such as wrinkles on the packaging, smudges or dirt on the barcode print, or the barcode being printed on a transparent film, the scan will be deemed unsuccessful.

[0059] The information for held items (held item 1) is for item 1. The information for held items (held item 2) is for item 2. The information for held items (held item 3) is for item 3.

[0060] The held product information (held product N; N is an integer) includes the held product type (information indicating whether the held product is NON-FILE or unreadable) and image data (image data captured when the product was unreadable). For example, if N items are held products due to being NON-FILE, the held product information (held product N) includes the held product type "1 (NON-FILE)", the product code, and the image data. Also, if N items are held products due to being unreadable, the held product information (held product N) includes the held product type "2 (unreadable)" and the image data.

[0061] Figure 9 shows an example of defining held items corresponding to cart information in this embodiment. In this figure, an example is shown in which held items are classified into eight categories. Each of the eight categories of held items is assigned a classification number from "1" to "8". The classification of the held product with classification number 1 is "NON-FILE," as explained in Figure 8. The classification of the held item with classification number 2 is "Unreadable" as explained in Figure 8.

[0062] The classification for held items with classification number 3 is "pseudo-scan input". Held items classified as "pseudo-scan input" are items in which the customer attempted to have the customer terminal device 50 read the product code, but the customer terminal device 50 was unable to read the code properly.

[0063] As a concrete example, "pseudo-scan input" refers to a situation where the product is placed within the imaging range of the imaging unit 506, but the product code is not included within the imaging range of the imaging unit 506. Furthermore, "pseudo-scan input" refers to a situation where the product was placed within the imaging range of the imaging unit 506, but the image was taken only in areas without a code. Furthermore, "simulated scan input" refers to a situation where the cord portion is hidden by a finger or the like, while the product is placed within the imaging range of the imaging unit 506. Furthermore, "pseudo-scan input" includes situations such as when the product code is captured by the imaging unit 506, but the product is passed through the imaging range of the imaging unit 506 at a speed that prevents the customer terminal device 50 from reading the code.

[0064] The classification for held items with classification number 4 is "non-scanned." "Non-scanned" held items are items that have been placed in the shopping cart without performing any operation to position the item within the imaging range of the imaging unit 506. This non-scanned insertion can occur, for example, when the customer terminal device 50 is fixedly attached to the shopping cart and is capable of imaging the contents of the shopping basket placed on the shopping cart. For example, if the customer terminal device 50 determines, based on the captured image, that an item has been placed in the shopping cart even though the item's code has not been scanned, it can determine that a non-scanned insertion has occurred.

[0065] The classification of the reserved item with classification number 5 is "age-verified product." "Age-verified product" is a product that requires the store clerk to verify the customer's age before sale, such as alcohol or tobacco.

[0066] The classification of the held item with classification number 6 is "pharmaceuticals." "Pharmaceuticals" are products that require confirmation from the purchaser by someone with a qualification such as a pharmacist.

[0067] The classification of item number 7 is "Anti-theft tagged item." An "Anti-theft tagged item" is an item that has an anti-theft tag attached, and therefore requires the store clerk to remove the anti-theft tag from the item before sale.

[0068] The classification of the held item with classification number 8 is "cancelled item." A "cancelled item" is an item that was initially registered but was canceled by a customer's cancellation operation on the customer terminal device 50. Canceled items are, for example, collected by a store employee from the customer at the time of settlement.

[0069] In this embodiment, pending products that fall under any of the four classifications "NON-FILE," "Reading NG," "Pseudo-Scan Input," or "Non-Scan Input" (classification numbers 1-4) among classification numbers 1-7 are unspecified products. Unspecified products are products whose registration result was incomplete because, for example, it could not be determined which of the products registered in the product master it was.

[0070] The product master is stored, for example, by the management device 10. The product master stores product information for each product sold at the store. The product information corresponding to one product includes a predetermined number of information items, including the product code and product name. The transaction management device 60 stores the product master data obtained from the management device 10. The transaction management device 60 uses the stored product master data for processing related to product registration, etc.

[0071] For held items corresponding to classification number 1, "NON-FILE," the product code has been obtained through a code scan in response to the product registration operation, but the product information associated with the obtained product code has not been registered in the product master. Therefore, it is not possible to identify which of the products registered in the product master corresponds to the held items corresponding to classification number 1, "NON-FILE." Specifically, the customer terminal device 50 transmits the product code obtained by the code scan to the transaction management device 60, and the transaction management device 60 may compare the transmitted product code with the product code of a product registered in the product master it stores. If the transaction management device 60 determines, as a result of the comparison, that a product code identical to the transmitted product code does not exist in the product master, it may treat the item as a held item corresponding to classification number 1, "NON-FILE," and notify the customer terminal device 50 accordingly. For pending items that fall under one of the three categories of classification numbers 2-4—"Reading Failed," "Pseudo-Scan Input," or "Non-Scan Input"—the acquisition of the product code failed as a result of the code scan performed in response to the product registration operation. Therefore, it is not possible to identify which of the products registered in the product master corresponds to a pending item that falls under one of the three categories of classification numbers 2-4. Such unspecified items can be released from their "holding" status (holding state) and registered normally by a store employee operating the monitoring device 80, as described later.

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

[0073] [Example of basic processing procedures for self-service operation] The sequence diagram in Figure 10 shows an example of the processing procedure performed by the customer terminal device 50, the settlement device 40, and the transaction management device 60 in response to the accounting of a single transaction in self-service operation. Specifically, the processing shown in the figure is an example of the processing performed by the customer terminal device 50, the settlement device 40, and the transaction management device 60 from the time a customer registers the items they wish to purchase from among the goods displayed in the store, until the settlement of the registered items is completed.

[0074] Step S1: The customer terminal device 50 acquires information that identifies the store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (outputting the two-dimensional code on a display screen, attaching a printed medium with the two-dimensional code, etc.), and when a customer enters the store, the customer terminal device 50 scans (reads) the two-dimensional code, thereby acquiring the store identification information. Alternatively, when a customer enters the store and launches the shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as the launch screen, or when a customer enters the store and scans the two-dimensional code with the customer terminal device 50, the shopping application may be launched and a screen informing the customer that it is connecting to the transaction management device 60 may be displayed as the launch screen.

[0075] For example, since stores are identified by their location, customers who visit a store may acquire location information (GPS information) using the customer terminal device 50 at the store (i.e., the location information of the store may be acquired as store identification information). When a customer who visits a store launches the shopping application, the system may acquire location information and display a screen as the launch screen informing the customer that it is connecting to the transaction management device 60. If multiple stores are detected from the location information and it is not possible to identify one, a selection screen may be displayed for the customer to make a selection. Alternatively, the system may switch to a mode that forces the acquisition of a 2D code.

[0076] Figure 11(A) shows an example of the startup screen of a shopping application displayed on the display unit 504 of the customer terminal device 50. In the startup screen shown in the figure, the store name is displayed. This store name is displayed based on the store identification information obtained in step S1. When a customer wants to start registering items for purchase, they operate the transaction start instruction button BT10 located on the startup screen. In response to the operation of the transaction start instruction button BT10, the customer terminal device 50 transmits a transaction start request to the transaction management device 60, which includes the acquired store identification information and customer identification information. The transaction start request may be transmitted in response to the customer's operation on the customer terminal device 50 as described above, or it may be transmitted in response to the acquisition of store identification information without any specific operation being received. Regarding customer identification information, when a customer registers (when downloading or installing the shopping application on the customer terminal device 50), the information entered in the name field of the registration form using the customer terminal device 50 may be stored in the customer information of the transaction management device 60. However, it may also be stored in the memory unit of the customer terminal device 50 in addition to the transaction management device 60. Furthermore, when a store is identified (when the initial product registration screen described later is obtained), the store name, services being offered (information from flyers distributed on that day), and available coupon information may be displayed on the screen (the initial product registration screen or a screen other than the initial product registration screen). Information on services and coupons may also be obtained from the transaction management device 60 as screen information, for example.

[0077] Furthermore, the recipient information (the address of the transaction management device 60) may also be obtained during customer registration (when downloading or installing the shopping application on the customer terminal device 50) and stored in the memory of the customer terminal device 50. In the case of scanning a 2D code, the recipient information may also be encoded in a 2D code in addition to the store identification information, and by scanning the 2D code with the customer terminal device 50, the customer terminal device 50 may obtain the recipient information along with the store identification information.

[0078] Step S2: The transaction management device 60, having received customer identification information and store identification information as a transaction start request from the customer terminal device 50, generates cart information for that transaction. In its initial state, the generated cart information stores cart identification information, transaction start date and time, and customer identification information, but does not store other information (transaction end date and time, product information (registered product information, pending product information), etc.) because the actual transaction (product registration) has not yet started.

[0079] As described above, the transaction management device 60 stores store information as shown in Figure 8(B). Therefore, when it receives store identification information (and customer identification information) from the customer terminal device 50 as a transaction start request, if the received store identification information is a two-dimensional code, it obtains the store identification information by referring to store identification information 1. If the received store identification information is location information (GPS information), it obtains the store identification information by referring to store identification information 2. In addition, if the store identification information received from the customer terminal device 50 is a two-dimensional code of the store identification information, the transaction management device 60 can simply obtain it as is.

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

[0081] Step S3: The transaction management device 60 that generated the cart information for the transaction generates initial product registration screen information (screen information of the initial product registration screen) and transmits it to the customer terminal device 50. Specifically, the transaction management device 60 generates, for example, initial product registration screen information and transmits the generated initial product registration screen information to the customer terminal device 50 along with the cart identification information.

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

[0083] Step S5: Upon customer operation, the customer terminal device 50 scans the barcode attached to the product and reads the product code. In this diagram, it is assumed that the barcode scan was successful. Steps S5 to S9 are repeated each time the barcode attached to the product is scanned.

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

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

[0086] Step S7: The transaction management device 60 updates the product data in the identified cart information. Specifically, if the received product registration information includes a product code as item N, the transaction management device 60 stores the product code as the product code of the registered product information (registered product N) in the identified cart information, retrieves 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.

[0087] Step S8: The transaction management device 60, having updated the product data in the cart information, generates product registration update screen information (screen information for the product registration screen, which is an update screen in 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 in the registered product list with the list item of the product that was just registered added, as shown in Figure 11(C), and transmits the generated product registration update screen information to the customer terminal device 50 along with the cart identification information.

[0088] The product registration screen (product registration update screen) shown in Figure 11(C) is displayed on the customer terminal device 50 after "XX Bread" has been registered as the third product item. In other words, when the transaction management device 60 stores "XX Yogurt" as the first item in the cart information, it generates product registration update screen information that displays "XX Yogurt" on the customer terminal device 50, and transmits the generated product registration update screen information to the customer terminal device 50 along with the cart identification information. When "XX Chocolate" is stored in the cart as the second item, it generates product registration update screen information that displays both "XX Yogurt" and "XX Chocolate" on the customer terminal device 50, and transmits the generated product registration update screen information to the customer terminal device 50 along with the cart identification information. When "XX Bread" is stored in the cart information as the third item, as shown in Figure 11(C), it generates product registration update screen information that displays "XX Yogurt," "XX Chocolate," and "XX Bread" on the customer terminal device 50, and transmits the generated product registration update screen information to the customer terminal device 50 along with the cart identification information.

[0089] Furthermore, once product 1 is registered, a registered product display screen WD1, which presents the newly registered product, may be displayed, for example, as shown in Figure 12(A). In addition, the registered product display screen WD1 in the same figure shows an example where a "Yes" button BT1 and a "No" button BT2 are placed to confirm with the customer whether or not they will eat in, depending on whether the product supports eat-in. In this case, the price of the product will be calculated so that the consumption tax rate applied to the product differs depending on whether the "Yes" button BT1 or the "No" button BT2 is pressed.

[0090] Step S9: The customer terminal device 50, having received 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, for example, as shown in Figure 11(C). As mentioned above, the product registration screen (product registration update screen) shown in Figure 11(C) is displayed to the customer terminal device 50 after "○○ Bread" has been registered as the third product item.

[0091] Step S10: The customer terminal device 50 accepts a payment transition instruction operation as a customer operation. For example, it accepts a touch of the "Proceed to Payment" button shown in Figure 11(C).

[0092] Step S11: The customer terminal device 50, having received the payment transition instruction operation, generates a two-dimensional code. In other words, the customer terminal device 50 encodes the information necessary to perform the payment process for the purchased items (e.g., cart identification information) into a two-dimensional code. The customer terminal device 50, having generated the two-dimensional code, displays the generated two-dimensional code on its display unit. For example, it displays a code display screen on its display unit with the two-dimensional code arranged as shown in Figure 11(D).

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

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

[0095] Step S14: The transaction management device 60, having received cart identification information and sub-calculation request information from the customer terminal device 50, identifies the cart information for the transaction from the cart identification information.

[0096] Step S15: The transaction management device 60, having identified the cart, calculates the subtotal amount using the price and other information in the registered product information included in the cart information corresponding to the identified cart information.

[0097] Step S16: The transaction management device 60, having calculated the subtotal amount, updates the cart information (stores the subtotal amount (calculated subtotal amount)) and transmits the subtotal information showing the calculated subtotal amount, along with the cart identification information, to the settlement device 40.

[0098] Step S17: The settlement device 40, having received cart identification information and subtotal information from the transaction management device 60, displays the subtotal amount on the customer-side display unit 405, for example, as shown in Figure 12(B).

[0099] Step S18: The settlement device 40, which has displayed the subtotal amount on the customer-side display unit 405, executes the payment (settlement). Specifically, the settlement device 40 accepts the selection of the payment type. In the case of cash, it accepts the deposit, calculates the amount of change, and if there is change, dispenses the change and issues a receipt. Furthermore, when the settlement is completed, the settlement device 40 transmits settlement completion information along 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) of the cart.

[0100] The customer terminal device 50 transmits the product code to the transaction management device 60 after scanning the product (S5), but it may choose not to transmit the product code for products other than those scanned within the store (the store where the customer visited and displayed the initial product registration screen) (for example, products scanned at another store). For example, the customer terminal device 50 acquires and stores location information (GPS information) when the customer visits the store (or when the initial product registration screen is displayed). The customer terminal device 50 also acquires location information when scanning individual products and compares the location information acquired when scanning the product with the location information acquired when the customer visited the store (or when the initial product registration screen is displayed). The customer terminal device 50 may then permit the transmission of the product code to the transaction management device 60 if the two match (or nearly match), and prohibit the transmission of the product code to the transaction management device 60 if they do not match (or nearly match). This prevents inappropriate product registration (for example, registering products in shopping carts created at other stores, etc.).

[0101] If the payment device 40 prohibits the transmission of product codes as described above, it may display an error message (for example, "Registration is not possible because you are not in the XX store") on the customer-side display unit 405 after scanning the product. Alternatively, the payment device 40 may display the above message on the employee-side display unit 410 instead of or in addition to the customer-side display unit 405.

[0102] Furthermore, the payment device 40 reads the two-dimensional code displayed on the display unit of the customer terminal device 50 and then requests the transaction management device 60 to calculate the subtotal amount (S13). However, it may choose not to request the calculation of the subtotal amount for items other than those scanned within the store (for example, items scanned at other stores). For example, the payment device 40 may refer to the store identification information of the store (it may store and refer to the store identification information of the store within the payment device 40 itself, or it may refer to store identification information stored in another accessible device), and when it reads the two-dimensional code displayed on the display unit 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 payment device 40 may then 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 in question, and prohibit the request to calculate the subtotal amount if it does not include the store identification information of the store in question. This prevents inappropriate transactions (for example, transactions for products registered at other stores).

[0103] If the payment device 40 prohibits the request for a subtotal amount as described above, it may display an error message (for example, "Payment cannot be processed because the order includes items from stores other than XX") on the customer-side display unit 405 after reading the 2D code. Alternatively, the payment device 40 may display the above message on the employee-side display unit 410 instead of, or in addition to, the customer-side display unit 405.

[0104] In the example processing procedure shown in Figure 10, the transaction management device 60 is configured to calculate the subtotal amount. However, for example, the settlement device 40 may obtain cart information from the transaction management device 60 and calculate the subtotal amount based on the obtained cart information. Alternatively, the transaction management device 60 may send cart information to the management device 10 to request the calculation of the subtotal amount, the management device 10 may use the received cart information to calculate the subtotal amount, and the calculated subtotal amount may be sent to the settlement device 40 via the transaction management device 60.

[0105] Furthermore, during settlement processing, the transaction management device 60 may check the customer's past cancellation history based on customer information and cart information, and determine whether or not to issue a warning about fraud. If it determines that a warning should be issued, the transaction management device 60 may, for example, cause the settlement device 40 to send a warning notification.

[0106] Furthermore, during the settlement process, the transaction management device 60 determines whether or not there are any reserved items among the product information included in the cart information, and if there are reserved items, it may request the settlement device 40 to correct the reserved items. Upon receiving the request for correction of reserved items, the settlement device 40 displays a notification that there are reserved items, as shown in Figure 12(C). Upon confirming the notification, the store clerk performs operations such as entering the price corresponding to the reserved items or canceling the reserved items as a way to release (correct) the reserved items.

[0107] [Regarding remote operation to release hold] The holding status of a held item is released (hold release) by a store employee operating the payment device 40, which displays an indication that there is a held item, as shown in Figure 12(C). However, in this case, the store employee needs to go to the payment device 40 that is displaying the indication that there is a held item each time. Therefore, in the shopping system of this embodiment, it is possible for a store employee to release unspecified items included in the reserved items registered in an abnormal transaction by operating the monitoring device 80. In other words, in this embodiment, even if a store employee does not go to the payment device 40, it is possible to remotely release the hold status of an unspecified item (remote hold release operation) using the monitoring device 80. By enabling remote release of held items in this manner, it becomes unnecessary to release held items that fall under the category of unspecified items at the settlement device 40. This allows for the release of held items at a stage prior to settlement at the settlement device 40, thus enabling more efficient release of held items. Furthermore, since the release operation can be distributed between the settlement device 40 and the monitoring device 80, the total waiting time for release at the settlement device 40 can be reduced, thereby improving the utilization efficiency of the settlement device 40.

[0108] The following describes the flow of remote operation to release hold in this embodiment. In the following description, the operation in which a customer scans (reads) a code (e.g., a barcode) attached to a product using the customer terminal device 50 in order to register the product will also be referred to as the product registration operation. The customer terminal device 50 has a code scanning function that extracts a code from an image captured by the imaging unit 506 and acquires code information. The customer terminal device 50 can acquire a product code by scanning the code attached to the product.

[0109] Customers register products by scanning the code attached to the product they intend to purchase at the store's sales floor using the customer terminal device 50. Once a product is registered, the product registration screen is updated, as shown in Figure 11(C), by adding a list item for the newly registered product to the registered product list.

[0110] Furthermore, if the customer terminal device 50 of this embodiment determines that a product registration operation has been performed for a certain product, and that the product is an unspecified product among the held products, it displays a hold release guidance screen. The hold release guidance screen informs the customer that the product targeted in this product registration operation has been treated as an unspecified product, and allows the customer to specify (select) whether or not to request a remote hold release operation to release the unspecified product from the hold.

[0111] Below, we will first explain an example where, as a result of the product registration operation, the product to be registered is determined to be an unspecified product corresponding to classification number 1, "NON-FILE".

[0112] Figure 13(A) shows an example of the hold release guidance screen WD51. In this figure, the hold release guidance screen WD51 is displayed as a window that is superimposed on the product registration screen. In the WD51 hold release guidance screen shown in the diagram, a message is displayed informing the customer that the product targeted in this product registration operation has been registered as an unspecified product in the hold list, and that it is possible to request a remote release of the hold. Furthermore, the hold release guidance screen WD51 includes an operation request button BT51 and an operation no-go button BT52. The operation request button BT51 is for customers to press if they wish to request remote release of the hold at that moment. The operation no-go button BT52 is for customers to press if they do not wish to request remote release of the hold at that moment, but instead want the store clerk to release the hold when they make a payment at the payment device 40.

[0113] Furthermore, the product registration screen displayed in the background of the hold release guidance screen WD51 in the same figure has been updated to reflect the results of this product registration operation. In other words, the product list item at the bottom of the product registration screen displays "Hold Product: NON-FILE". This display of the list item indicates that, as a result of this product registration operation, the product has been registered as a held product corresponding to classification number 1, "NON-FILE". Also, in the case of a held product corresponding to classification number 1, "NON-FILE", product information associated with the acquired product code has not been acquired, and therefore price information has not been acquired either. For this reason, the price is not displayed in the product list item at the bottom of the product registration screen.

[0114] In this case, the customer decided to request remote release of the hold at this point, and therefore operated the operation request button BT51. In response to the operation request button BT51 being operated, the customer terminal device 50 transmits the operation request information to the transaction management device 60. The operation request information includes cart identification information and pending product reference information. If the product targeted in this product registration operation is an unspecified product classified as "NON-FILE" with classification number 1, the pending product reference information includes the product code obtained by the customer terminal device 50 through code scanning and the image captured by the imaging unit 506 while the code scanning is being performed. If the product being registered in this operation is determined to be an unspecified product with classification numbers 2-4, specifically one of the following: "Reading Failed," "Simulated Scan Input," or "Non-Scan Input," the pending product reference information will include the image captured by the imaging unit 506 when the code scan is being performed, but will not include the product code.

[0115] The transaction management device 60 forwards the received operation request information to the monitoring device 80. At this time, the transaction management device 60 includes the product information registered as an unspecified product in response to the product registration operation in the operation request information and sends it to the monitoring device 80.

[0116] When the customer terminal device 50 transmits operation request information to the monitoring device 80 via the transaction management device 60 as described above, it displays the hold release waiting screen WD52 instead of the hold release guidance screen WD51. Figure 13(B) shows an example of the hold release waiting screen WD52. The hold release waiting screen WD52 in this figure is an example of a window format that is superimposed on the product registration screen, similar to the hold release guidance screen WD51. In the WD52 hold release waiting screen shown in the diagram, a message is displayed informing the customer that a hold release operation is currently underway and asking them to wait until the hold release operation for the unspecified items is complete.

[0117] Furthermore, upon receiving the operation request information, the monitoring device 80 displays the product information input screen on the display unit 806. The store employee in charge of monitoring using the monitoring device 80 can understand that a customer has requested a remote operation to release the hold by seeing the product information input screen.

[0118] Furthermore, prior to displaying the product information input screen, the monitoring device 80 may display a hold release operation confirmation screen on the display unit 806, which notifies the customer that a request for hold release remote operation has been received and allows the user to declare whether or not to perform the hold release remote operation in response to the request. The declaration operation of whether or not to perform the hold release remote operation may be an operation on either a button to declare that the hold release remote operation will be performed or a button to declare that the hold release remote operation will not be performed. If a store employee declares that they will perform a remote operation to release the hold on the hold confirmation screen, the display on the display unit 806 changes to the product information input screen. If a store employee declares that they will not perform a remote operation to release the hold on the hold confirmation screen, the display on the display unit 806 returns to the predetermined screen that was displayed before the hold release confirmation screen appeared.

[0119] Figure 14(A) shows an example of a product information input screen displayed on the display unit 806. The product information input screen in this figure includes a product code input area AR30-1, a search button BT31, a product name input area AR30-2, a selling price input area AR30-3, a product type input area AR30-4, a warning type input area AR30-5, a confirmation button BT32, a delete button BT33, and a scan status image area AR31.

[0120] Furthermore, unless otherwise specified, the product code input area AR30-1, product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5 should be referred to simply as input area AR30.

[0121] Product code input area AR30-1 is an input area where the product code of an unspecified product that has been designated for release from the hold is entered. The search button BT31 is used when entering a product code into the product code input area AR30-1 and searching for products registered in the product master. Product name input area AR30-2 is the input area where the product name is entered. The selling price input area AR30-3 is the input area where the selling price is entered. Product type input area AR30-4 is the input area where the product type is entered. Warning type input area AR30-5 is an input area where the warning type is entered. The confirmation button BT32 is used to instruct the display of an input information confirmation screen, which confirms the contents of the information entered in each of the input areas AR30 mentioned above, in order to release the hold. The delete button BT33 is used to remove the registration of an unspecified product that was designated as a pending product, as part of the "release from pending" process.

[0122] The scan status image area AR31 is the area where the scan status image is displayed. The scan status image is an image captured by the imaging unit 506 when the customer terminal device 50 is scanning the code of an unspecified product that has been designated for release from hold in response to the customer's product registration operation. The content of such a scan status image indicates the status of the unspecified product that has been designated for release from hold when the customer terminal device 50 is scanning the product code. Furthermore, in the scan status image area AR31, multiple scan status images may be displayed, for example, with different capture timings. The scan status images may also be moving images or time-lapse images composed of still images captured at regular intervals.

[0123] If the unspecified product is classified as "NON-FILE" with classification number 1, the product code is successfully obtained as a result of scanning the code in response to the product registration operation. However, the product information associated with the obtained product code has not been retrieved. Therefore, in the initial display state of the product information input screen, the product code input area AR30-1 is pre-filled with the product code, but the remaining product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5 are all empty.

[0124] Therefore, the store clerk performs the operation of entering information corresponding to the unspecified product that has been designated for release into each of the above input areas AR30, where information has not yet been entered. At this time, the store clerk can look at the scan information image displayed in the scan status image area AR31 and determine what kind of product the unspecified product that has been designated for release is. This allows the store clerk to determine what kind of information should be entered into each of the following input areas AR30-2, AR30-3, AR30-4, and AR30-5. When determining the information to be entered into each of the above input areas AR30, the store clerk may refer to, for example, a product book containing information on products that can be handled at the store. The store clerk is then instructed to input the specified information into the product name input area AR30-2, the selling price input area AR30-3, the product type input area AR30-4, and the warning type input area AR30-5. As a result, as shown in Figure 14(A), all input areas—product code input area AR30-1, product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5—are filled with information about the unspecified product that was subject to release from hold.

[0125] Once information has been entered into all input areas AR30 as described above, the store clerk operates the confirmation button BT32. In response to the operation of the confirmation button BT32, the display unit 806 displays an input information confirmation screen (though this is not shown in the diagram). The input information confirmation screen shows the contents of the information entered into each input area AR30 on the product information input screen, and also includes an execution button to instruct the user to release the hold. The store clerk confirms the information displayed on the product information input screen and then operates the execute button. In response to the operation of the execute button, the monitoring device 80 sends a request to release the hold, which includes the information (simplified product information) entered in the input area AR30, to the transaction management device 60.

[0126] When the transaction management device 60 receives a request to release a hold, it replaces the hold item information of the hold item targeted for release in the cart information with the registered item information, including the simplified item information included in the received request to release a hold. As a result, the hold item, which was previously unspecified, is released from its hold status and treated as if it has been successfully registered.

[0127] When the transaction management device 60 releases the pending status of an unspecified product as described above and registers it as a normal product (normal registration), it sends a notification of completion of release of hold to the customer terminal device 50. The notification of completion of release of hold includes information on the product registration update screen, which has been changed to indicate that the relevant list item that indicated it was a pending product has now been successfully registered as a result of this release of hold.

[0128] When the customer terminal device 50 receives a notification that the hold has been released, it first displays the hold release confirmation screen WD53 instead of the hold release waiting screen WD52 that it had been displaying. Figure 13(C) shows an example of the hold release confirmation screen WD53. In the hold release confirmation screen WD53 shown in this figure, a message informing the customer that the hold release remote operation has been completed and the hold has been released, and a confirmation button BT53 are provided. The customer can see the displayed hold release confirmation screen WD53 to understand that the hold on the unspecified item has been successfully released. The customer then operates the confirmation button BT53 to confirm that the hold has been released.

[0129] In response to the operation of the confirmation button BT53, the customer terminal device 50 clears the hold release confirmation screen WD53. The customer terminal device 50 also updates the display of the product registration screen using the product registration update screen information included in the hold release completion notification.

[0130] Figure 13(D) shows the updated product registration screen after the hold release confirmation screen WD53 has been cleared. In the product registration screen shown in this figure, the bottom list item, which was shown as "Holding Product: NON-FILE" in the product registration screens of Figures 13(A) to 13(D), has changed to display the product name, such as "○○ Bread," along with the price (selling price). Furthermore, in the bottom list item of the product registration screen shown in this figure, for example, "Hold Released" is displayed, indicating that the product corresponding to that list item has been successfully registered after the hold release was completed.

[0131] Furthermore, in the configuration shown in Figure 13(B), where the hold release waiting screen WD52 is displayed, the hold release waiting screen WD52, once displayed, will not disappear until the hold release remote operation is completed. In this case, even if the customer still has items they wish to register, they cannot perform the item registration operation while the hold release waiting screen WD52 is displayed and must wait. Therefore, in response to the operation request button BT51 (Figure 13A)) on the hold release guidance screen WD51 being operated, the customer terminal device 50 may transition to the following display instead of displaying the hold release waiting screen WD52. In other words, the customer terminal device 50 may operate the hold release guidance screen WD51 in response to the operation request button BT51 being operated and return to the product registration screen. Then, on the product registration screen, the list item of the held product that is the subject of the hold release remote operation request will be displayed in a predetermined manner to indicate that it is waiting for the hold release remote operation to be completed. Then, in response to the completion of the hold release remote operation, the product registration screen will display a notification in a predetermined manner that the hold release remote operation has been completed and the held product has been released. The notification that the hold has been released may be displayed as a pop-up window with a message indicating that the hold has been released, for example, in accordance with Figure 13(C). In addition, the notification that the hold has been released may be accompanied by sound output or vibration in addition to the display. By displaying the product registration screen after the operation request button BT51 is pressed, it becomes possible for the customer to perform product registration even while the hold release remote operation is in progress.

[0132] Furthermore, when the customer is paying at the payment device 40 while the hold release guidance screen WD51 is displayed as shown in Figure 13(A), they are instructed to release the hold. If it is determined at this stage that the customer does not want to request remote hold release, the "no operation required" button BT52 is operated. If the "No Operation Required" button BT52 is pressed, the customer terminal device 50 clears the hold release guidance screen WD51 and returns to the state where the product registration screen is displayed. In this case, the customer terminal device 50 does not send any operation request information to the transaction management device 60. Also, in this case, the list item of the relevant held product on the product registration screen displayed after the hold release guidance screen WD51 is cleared will maintain the indication that it was a held product before the "No Operation Required" button BT52 was pressed.

[0133] Furthermore, if a store employee using the monitoring device 80 determines that they should release the hold by deleting the registration of the hold item as an unspecified item, they will operate the delete button BT33 on the product information input screen. When the delete button BT33 is pressed, the monitoring device 80 sends a release request to the transaction management device 60 instructing it to delete the registration of the item as a held item. In this case, the transaction management device 60, upon receiving the release request, deletes the held item information of the item to be released from the cart information. As a result, the held item, which was previously an unspecified item, is treated as if its registration had been deleted, and the release is completed. In this case, the transaction management device 60 includes information from the product registration update screen, in the notice of completion of hold release that it sends to the customer terminal device 50 in response to the release of the hold, showing that the relevant list item indicating that the product was on hold has been deleted.

[0134] Furthermore, customers may want to release held items by deleting their registration. For example, a customer might have mistakenly scanned the code of an item they did not intend to purchase using the customer terminal device 50, and then returned the item to the shelf. Therefore, the deletion of a pending item as an unspecified item may be specified, for example, when a customer requests a remote operation to release the pending item. In this case, for example, the pending item release guidance screen WD51 may allow the customer to select either changing the item to a normal registration or deleting the registration as the release option, and then request a remote operation to release the pending item.

[0135] Next, we will explain an example where, as a result of a customer performing a product registration operation using the customer terminal device 50, the product to be registered is determined to be an unspecified product falling under one of the following classification numbers: "Reading Failed," "Simulated Scan Input," or "Non-Scan Input." In this case as well, the customer terminal device 50 displays the hold release guidance screen WD51 as shown in Figure 13(A). However, in this case, the product registration screen displayed in the background of the hold release guidance screen WD51 will display a message indicating that the reading of the product code during the product registration operation failed, such as "Holded Product: Code Unreadable" instead of "Holded Product: NON-FILE". In this case as well, when the hold release guidance screen WD51 is displayed, the customer operates either the operation request button BT51 or the operation no-go declaration button BT52, depending on their own judgment as to whether or not to request remote hold release. If the operation request button BT51 is operated, the display on the display unit 504 of the customer terminal device 50 changes in accordance with the remote hold release operation performed by the store clerk via the monitoring device 80, as shown in Figures 13(B) and 13(C). Then, in response to the customer operating the confirmation button BT53 on the hold release confirmation screen WD53 displayed as shown in Figure 13(C), the product registration screen reflecting this hold release is displayed, as shown in Figure 13(D).

[0136] In this case, the product information input screen displayed by the monitoring device 80 in response to a request for remote operation to release the hold may be the same as in Figure 14(A). However, if the unspecified product falls under any of the following categories with classification numbers 2-4: "Reading NG," "Simulated Scan Input," or "Non-Scan Input," the product code has not been obtained through the product registration operation. Therefore, in the initial display state of the product information input screen, information is not entered in the product name input area AR30-2, the selling price input area AR30-3, the product type input area AR30-4, the warning type input area AR30-5, and also in the product code input area AR30-1.

[0137] In this case, if the store clerk wishes to release the hold remotely and register the item successfully, they will be instructed to enter information into each input area AR30 on the product information input screen. In this case as well, the store clerk can determine what kind of product it is by looking at the scan status image displayed in the scan status image area AR31. After entering the information into each of the input areas AR30, the store clerk will operate the confirmation button BT32 to display the input information confirmation screen and then instruct the store clerk to release the hold on the displayed input information confirmation screen. As a result, the hold on the unspecified item will be released and the item will be successfully registered. If an unspecified product falls under any of the following categories with classification numbers 2-4: "Reading NG," "Simulated Scan Input," or "Non-Scan Input," the store clerk may input the product name or other information obtained from the scan status image displayed in the scan status image area AR31 as a search key (search condition), and then perform a search by, for example, operating the search button BT31. In this case, the monitoring device 80 accesses the product master stored in, for example, the transaction management device 60 or the management device 10, and searches for products that match the entered search key. The store clerk then identifies the relevant product from the search results. The monitoring device 80 can obtain the product information of the identified product from the product master and use the obtained product information to input information into each input area AR30.

[0138] Furthermore, even if an unspecified product falls under classification number 1, "NON-FILE," it may be possible to search for the product for successful registration. However, the determination that an unspecified product falls under "NON-FILE" is due to the fact that there is no corresponding product information in the product master stored in the transaction management device 60. Therefore, if an unspecified product falls under "NON-FILE," there is no point in accessing the product master of the transaction management device 60 to search for the product, as is the case with unspecified products that are "Read NG," "Simulated Scan Input," or "Non-Scan Input." However, for example, the corresponding product information may be registered in the product master of the store controller (for example, the management device 10) or in a product master database located outside the store, such as at the headquarters of a chain of stores, but this product information may not be reflected in the product master of the transaction management device 60. Therefore, if an unspecified product falls under the category of "NON-FILE," the monitoring device 80 may, in response to the operation of the search button BT31, access the product master stored in the store controller or an external product master database to search for product information corresponding to the entered search key.

[0139] Furthermore, if a store employee wishes to cancel the registration of an unspecified product as a remote release of the hold, they will operate the delete button BT33 on the product information input screen.

[0140] Next, with reference to Figure 14(B), another example of the product information input screen displayed on the monitoring device 80 will be described. In the product information input screen shown in the diagram, the input area AR40 (product code input area AR40-1, product type input area AR40-2, warning type input area AR40-3, product name input area AR40-4, selling price input area AR40-5, quantity unit input area AR40-6, tax exemption flag input area AR40-7, special sale setting input area AR40-8, tax information input area AR40-9), scan status image area AR41, search button BT41, confirmation button BT42, and delete button BT43 are arranged. In this type of product information input screen, each input area AR40 is set up to input basic product information, including product code, product type, warning type, product name, selling price, quantity unit, tax exemption flag, special sale settings, and tax information. In the product information input screen shown in Figure 14(B), information such as tax exemption, consumption tax, and special offers can be entered as simplified product information. Therefore, when releasing the hold on unspecified products and registering them normally, settings for tax exemption, consumption tax, and special offers can be made in advance.

[0141] When an item is registered in the shopping cart as a "holding item," it is in an incomplete state that prevents the process from proceeding to the checkout stage. This state must be resolved by changing the registration to a normal one or deleting the item before proceeding to checkout. In this embodiment, remote operation of the hold release is possible using the monitoring device 80, allowing the registration of a held item to be released even before settlement is performed by the settlement device 40. Furthermore, it becomes possible to distribute the release of held items between, for example, the monitoring device 80 and the settlement device 40. This allows for the release of held items to be performed more efficiently.

[0142] Furthermore, the information items used as simplified product information to be entered on the product information input screen during remote release of hold are considered to be only a portion of the information items included in the product information stored in the product master. The information items included in the product master include product code, product name, selling price, product type, warning type, unit of quantity, tax exemption flag, special sale settings, and tax information, corresponding to input area AR30 in Figure 14(A) and input area AR40 in Figure 14(B). In addition, other items include, for example, medium category, minor category, cost, standard retail price, size, weight, specifications, net weight, registration date and time, and update date and time. For example, medium category and minor category may be necessary for product management in stores, but this information is not necessarily required in transactions. In other words, some of the information items included in the product master are information that does not necessarily need to be used in transactions.

[0143] Therefore, in this embodiment, the information items to be entered into input areas AR30 and AR40 on the product information input screen where the hold release remote operation is performed are limited to the information items necessary to enable the transaction. This eliminates the need for store employees to input an excessive number of information items when remotely releasing held items, thus improving the efficiency of releasing unspecified items from hold.

[0144] Furthermore, it is not mandatory to input information items corresponding to all input areas (AR30, AR40) on the product information input screen. Also, on the product information input screen, when information items that can identify the product classification, such as product name or product type, are entered, the appearance of the corresponding input areas may be changed to indicate that the information items that are no longer mandatory or cannot be entered under the corresponding classification are now not required.

[0145] [Example of processing procedure] Referring to the flowchart in Figure 15, an example of the processing procedure performed by the customer terminal device 50, the transaction management device 60, and the monitoring device 80 in relation to the release of unspecified products will be explained. The processing in the same figure corresponds to Figure 9, and shows the processing steps S5 to S11 in more detail, including the processing corresponding to unspecified products.

[0146] First, we will explain an example of a processing procedure performed by the customer terminal device 50. Step S101: The customer terminal device 50, with the product registration screen displayed, waits for a code scan to be performed in accordance with the product registration operation, and determines whether the reading of the product code (acquisition of the product code) by the code scan has been successfully completed in accordance with the product registration operation.

[0147] Step S102: If the customer terminal device 50 has successfully read the product code, it transmits product registration information, including the read product code and cart identification information, to the transaction management device 60.

[0148] Step S103: The customer terminal device 50 receives a registration completion notice sent from the transaction management device 60 in response to the transmission of product registration information in step S102. The customer terminal device 50 uses the information of the product registration update screen included in the received registration completion notice to update the product registration screen, for example, as illustrated in Figure 11(C).

[0149] In response to the registration completion notification received in step S103, the products registered by the transaction management device 60 include not only products that were successfully registered based on the reading of the product code, but also products held as pending products, including "NON-FILE" with classification number 1, "Age Verification Products" with classification numbers 5-7, "Pharmaceuticals," and "Anti-theft Tag Products." If the product selected for registration this time was a pending product (unspecified product) with classification number 1, "NON-FILE", then the product registration screen after the update in step S103 will have an added product list indicating that it is a pending product as "NON-FILE".

[0150] Step S104: The customer terminal device 50 determines whether the registration result corresponding to this product registration operation is registered as a reserved product of classification number 1, "NON-FILE". If it is determined that the item is registered as a pending item of classification number 1, "NON-FILE", the process proceeds to step S108. If it is determined that the item is not registered as a pending item of classification number 1, "NON-FILE", the process proceeds to step S114.

[0151] Step S105: If the reading of the product code was not completed successfully in Step S101, the product targeted for registration in this product registration operation will be an unspecified product due to one of the following classification numbers: "Reading Failed," "Pseudo-Scan Input," or "Non-Scan Input." In this case, the customer terminal device 50 will perform a classification determination to determine which of the following classifications—"Reading Failed," "Pseudo-Scan Input," or "Non-Scan Input"—corresponds to classification numbers 2 to 4.

[0152] The customer terminal device 50 is configured to detect product code reading failures based on the captured image obtained by causing the imaging unit 506 to perform imaging when reading the product code in step S101. If a product code reading failure is detected, it is determined that the reading of the product code in step S101 was not completed successfully.

[0153] Furthermore, the customer terminal device 50 makes a determination in step S105 according to the detected product code reading failure state. First, the customer terminal device 50 determines that if it recognizes that the entire barcode of the product has been captured in the image, but a certain amount of time has passed without the barcode reading being completed successfully, it will be classified as "Reading Failed" under classification number 2.

[0154] Furthermore, if the customer terminal device 50 detects a product code reading failure, where the product was recognized in the captured image but the barcode could not be recognized at all and therefore barcode reading could not be completed successfully, it will be classified as "pseudo-scan input" under classification number 3. Alternatively, if the customer terminal device 50 detects a product code reading failure, where only a portion of the product's barcode is recognized in the captured image and therefore the barcode reading was not completed successfully, it will also be classified as "pseudo-scan input" under classification number 3. Alternatively, if the customer terminal device 50 detects a product code reading failure, where the barcode of the product was recognized in the captured image but the barcode reading was not completed properly because the product was moving too fast, it will also be classified as "pseudo-scan input" under classification number 3.

[0155] Furthermore, if a product code reading failure occurs, which falls under classification number 3, "pseudo-scan input," it may indicate that fraud is taking place, such as when a customer pretends to scan a product's barcode but actually places the product in their shopping cart.

[0156] Furthermore, if the customer terminal device 50 is attached to a shopping cart and is configured to image the inside of the shopping basket, it can image the contents of the shopping basket placed on the shopping cart. If the customer terminal device 50 detects a product code reading failure in the captured image, indicating that a new product has been added to the shopping basket even though no attempt to scan the product barcode is recognized, it will classify it as "non-scanned entry" under classification number 4.

[0157] For example, a customer may move already registered items within their shopping basket to organize its contents. The customer terminal device 50 may be configured to distinguish between such item movements and the addition of new items corresponding to product code reading failures as "non-scanned entries," based on the captured image. When a product code reading failure occurs, which is classified as "non-scanned input," it is possible that fraud is occurring, such as when a customer places an item in their shopping cart without having the customer terminal device 50 scan the product's barcode.

[0158] Step S106: The customer terminal device 50 transmits product registration information corresponding to the classification determined in step S105 to the transaction management device 60. The product registration information transmitted in step S106 does not include a product code. The product registration information transmitted in step S106 may also include information indicating the classification determined in step S105.

[0159] Step S107: The customer terminal device 50 receives a registration completion notice sent from the transaction management device 60 in response to the transmission of product registration information in step S106. The customer terminal device 50 updates the product registration screen using the information on the product registration update screen included in the received registration completion notice. In the updated product registration screen, a product list is added that indicates, for example, that the product is a pending product (unspecified product) that falls under one of classification numbers 2 to 4.

[0160] Step S108: After processing in step S107, or if it is determined in step S104 that the item is registered as a "NON-FILE" item with classification number 1, the customer terminal device 50 displays the hold release guidance screen WD51 (Figure 13(A)) on the display unit 504.

[0161] Step S109: The customer terminal device 50 determines whether or not the operation request button BT51 located on the hold release guidance screen WD51 has been operated.

[0162] Step S110: When the operation request button BT51 is pressed, the customer terminal device 50 transmits the operation request information to the transaction management device 60. Step S111: The customer terminal device 50 also displays the hold release waiting screen WD52 instead of the hold release guidance screen WD51.

[0163] Step S112: While the hold release waiting screen WD52 is displayed, the customer terminal device 50 waits for the hold release completion notification sent from the transaction management device 60 to be received. When the hold release completion notification is received, the customer terminal device 50 displays the hold release confirmation screen WD53 instead of the hold release waiting screen WD52.

[0164] Step S113: The hold release confirmation screen WD53 displayed in step S112 is cleared when the customer presses the confirmation button BT53. When the hold release waiting screen WD52 is cleared, the customer terminal device 50 updates the product registration screen using the product registration update screen information included in the hold release completion notification received in step S112. If the pending item is successfully registered, the updated product registration screen will show the item's product list, which was previously indicated as pending, as having been successfully registered. Similarly, if the pending item is deleted, the updated product registration screen will show the item's product list as deleted.

[0165] Step S114: After processing in step S113, or if it is determined in step S104 that the item is not registered as a pending item of classification number 1 "NON-FILE", or if it is determined in step S109 that the "no operation required" button BT52 on the pending release guidance screen WD51 has been operated, the customer terminal device 50, while displaying the item registration screen, determines whether or not a settlement transition instruction operation has been performed. If the settlement transition instruction operation is not performed, the process returns to step S101.

[0166] Step S115: When the payment transition instruction operation is performed, the customer terminal device 50, for example, converts the cart identification information into a two-dimensional code and displays the generated two-dimensional code on the display unit 504 using a code display screen as exemplified in Figure 11(D).

[0167] Next, an example of a processing procedure executed by the transaction management device 60 will be described. Step S201: The transaction management device 60 determines whether or not it has received the product registration information transmitted from the customer terminal device 50 in step S102.

[0168] Step S202: When the transaction management device 60 receives product registration information, it identifies the cart information indicated by the cart identification information contained in the received product registration information. Step S203: The transaction management device 60 updates the cart information identified in step S202. That is, the transaction management device 60 adds the cart product information (registered product information or pending product information) based on the product code included in the product registration information received in response to step S201 to the identified cart information. As a result, the product is registered in the cart information.

[0169] Step S202 updates the cart information, registering not only the successfully registered items but also the pending items that do not fall under classification numbers 2-4 ("Reading Failed," "Pseudo-Scan Input," "Non-Scan Input"). In other words, step S202 updates the cart information, including the registration of pending items whose product codes have been successfully read. The pending items whose product codes have been successfully read are classification number 1 "NON-FILE," classification number 5 "Age Verification Items," classification number 6 "Pharmaceuticals," and classification number 7 "Anti-Theft Tag Items." Furthermore, although classification number 8 "Cancelled Items" are not reflected in the process shown in the diagram, when a cancellation operation is performed on the customer terminal device 50, the transaction management device 60 updates the pending item information for the item in the cart information so that the item is managed as a cancelled item.

[0170] Step S204: After processing in step S203, the transaction management device 60 sends a registration completion notification to the customer terminal device 50.

[0171] Step S205: After processing in step S204, or if it is determined in step S201 that product registration information has not been received, the transaction management device 60 determines in step S106 whether or not product registration information for a pending product (unspecified product) corresponding to one of classification numbers 2 to 4 ("Reading NG", "Pseudo-scan input", "Non-scan input") has been received from the customer terminal device 50. If product registration information has not been received, the process returns to step S201.

[0172] Step S206: When the transaction management device 60 receives product registration information, it identifies the cart information indicated by the cart identification information contained in the received product registration information. Step S207: The transaction management device 60 updates the cart information identified in step S206. In this case, the transaction management device 60 adds the reserved product information, including the classification number contained in the product registration information received in response to step S205, to the identified cart information. As a result, one reserved product is registered in the cart information that corresponds to a reserved product (unspecified product) that corresponds to one of the classification numbers 2 to 4 ("Reading NG", "Pseudo-scan input", "Non-scan input"). Step S208: After processing in step S207, the transaction management device 60 sends a registration completion notification to the customer terminal device 50.

[0173] Step S209: After processing in step S208, the transaction management device 60 determines whether or not it has received the operation request information transmitted from the customer terminal device 50 in step S110. If it is determined that the operation request information has not been received, the process returns to step S201.

[0174] Step S210: When it is determined in step S209 that an operation request has been received, the transaction management device 60 forwards the received operation request information to the monitoring device 80. At this time, the transaction management device 60 includes the pending product information that was added to the cart information when updating the cart information in step S207 in the operation request information.

[0175] Step S211: In response to the operation request information transmitted in step S210, the monitoring device 80 sends a hold release request (cart information update request) indicating the completion of the hold release remote operation. The transaction management device 60 updates the cart information upon receiving the hold release request. In other words, if the transaction management device 60 includes simplified product information in the hold release request, it uses the simplified product information to generate registered product information. The transaction management device 60 replaces the hold product information added when the cart information was updated in step S207 with the generated registered product information. As a result, the hold product, which was previously unspecified, is released from the hold in a way that allows it to be registered successfully. Furthermore, if the transaction management device 60 receives a request to release the hold, it instructs the deletion of the registration of the corresponding hold item, and deletes the hold item information that was added when the cart information was updated in step S207 from the cart information. As a result, the hold item, which is an unspecified item, is released from the hold by canceling its registration.

[0176] Step S212: The transaction management device 60 sends a notification to the customer terminal device 50 indicating that the hold has been released due to the update of the cart information in step S211.

[0177] Next, an example of a processing procedure performed by the monitoring device 80 will be described. Step S301: The monitoring device 80 waits for the operation request information transmitted from the transaction management device 60 in step S210 to be received.

[0178] Step S302: When operation request information is received, the monitoring device 80 displays the product information input screen on the display unit 806.

[0179] Step S303: The store clerk performs a normal registration operation or a registration deletion operation as a remote operation to release the hold on the displayed product information input screen. A normal registration operation involves entering information into input area AR30 (AR40), operating the confirmation button BT32 (BT42) to display the input information confirmation screen, and then instructing the system to release the hold. A registration deletion operation is performed using the delete button BT33 (BT43). The monitoring device 80 accepts the remote operation to release the hold as described above.

[0180] Step S304: The monitoring device 80 transmits a hold release request to the transaction management device 60 upon completion of the hold release remote operation. If a successful registration operation is performed as a hold release remote operation, the hold release request includes simplified product information based on the information entered in the input area AR30 (AR40). If a registration deletion operation is performed as a hold release remote operation, the hold release request also includes instructions to delete the registration of the corresponding hold product.

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

[0182] [First variation] In the above embodiment, the held items subject to remote release are defined as items that fall under one of four categories as unspecified items: "NON-FILE," "Reading NG," "Pseudo-Scan Insertion," and "Non-Scan Insertion." As a variation of this design, it may be possible to remotely release held items that fall under categories other than the four categories mentioned above. For example, in the case of "age verification items," the hold may be released and the item may be registered normally once the store clerk has confirmed that the customer is of an age to purchase the item, for example, by using the customer's membership information or a facial image of the customer transmitted from the customer terminal device 50.

[0183] [Second variation] In the above embodiment, when an operation request information is transmitted from the customer terminal device 50, the product information input screen is displayed on the monitoring device 80, and the store clerk remotely performs the hold release operation. However, there are cases where, for example, operation request information is transmitted from multiple different customer terminal devices 50 almost simultaneously. Therefore, the monitoring device 80 may be configured to display a list of customers (operation request list) corresponding to each customer terminal device 50 that has sent operation request information. The store clerk may select one list item from among the list items presented in the operation request list and perform a remote operation to release the hold according to the operation request information corresponding to the selected list item. Furthermore, the list items in the operation request list may be sortable according to predetermined sorting criteria. For example, the list items in the operation request list may be sortable based on the order in which the operation request information was received, the number of registered pending items among the registered products, or the like.

[0184] [Third variation] Furthermore, the monitoring device 80 may be configured to display a list of customers corresponding to transactions in which reserved products are registered (list of customers holding reserved products). In this case, for example, based on past transaction history, the list items for customers who frequently register reserved products may be displayed in a different manner from other list items so that this can be easily identified. Furthermore, the list items in the list of customers holding pending items may be sortable according to a predetermined sorting criterion. For example, the list items in the list of customers holding pending items may be sortable according to the current number of registered items. Furthermore, the list items in the list of customers holding reserved items may be sorted according to the distance between the current location of the customer corresponding to each list item and the settlement device 40. The customer's current location is obtained by acquiring the current location of the customer terminal device 50. The monitoring device 80 can acquire location information obtained by the customer terminal device 50 using its own GPS or similar positioning function, for example, via the transaction management device 60. Alternatively, the monitoring device 80 can also acquire the location information of the customer terminal device 50 by, for example, installing beacons at predetermined locations in the store that communicate with the customer terminal device 50 to acquire terminal identification information, and associating the location information received from the beacons with the location of the beacon that transmitted the location information. Furthermore, the list items in the list of customers holding pending products may be sortable according to the credit level of the customer corresponding to each list item. For example, the transaction management device 60 stores credit level information, setting a credit level for each customer based on the customer's past transaction history. The monitoring device 80 can obtain the credit level of the customer corresponding to each list item from the credit level information stored by the transaction management device 60.

[0185] [Fourth variation] In the above embodiment, when a customer performs an operation to request a remote release of a held item from the customer terminal device 50 (an operation on the operation request button BT51), the monitoring device 80 displays a product information input screen for the normal registration of the held item. In other words, in the above embodiment, when a customer performs an operation to request a remote release of a held item, the store clerk is able to perform a remote release of the held item. However, it is acceptable for store employees to be able to remotely release held items without the customer having to perform an action to request the release of held items. For example, the registration of a reserved item as "NON-FILE" may result from a store error, such as the product information not being registered in the product master. Therefore, if a reserved item is registered as "NON-FILE," the customer terminal device 50 may send operation request information to the transaction management device 60 even if the customer does not perform an operation to request remote release of the reserved item. The transaction management device 60 can display a product information input screen corresponding to a held product registered as "NON-FILE" in response to the receipt of operation request information. As a result, when a held product is registered as "NON-FILE," the store clerk can operate the monitoring device 80 to perform normal registration without the customer having to perform an operation to request remote release of the hold (a request for normal registration). In this case, the customer does not have to go to the trouble of performing an operation to request normal registration even though it is the store's fault, so the customer is less likely to feel dissatisfied.

[0186] Furthermore, if a store employee can remotely release a held item without a request from the customer, the customer terminal device 50 does not need to display the hold release guidance screen WD51 and the hold release waiting screen WD52, as shown in Figures 13(A) and 13(B), even if it transmits operation request information. However, in this case, if the hold release confirmation screen WD53, as illustrated in Figure 13(C), is displayed when the hold release is completed by a store employee's remote operation, the customer will be suddenly notified that the hold release is complete, which could easily cause confusion. Therefore, in this case, it is preferable to display a message on the hold release confirmation screen WD53 that allows the customer to understand that the hold was released remotely by a store employee without the customer's request, for example, "The previous item was not registered successfully, so a store employee has taken care of it remotely."

[0187] [Fifth variation] The monitoring device 80 in the above embodiment may be, for example, a terminal installed in the back room of a store, or a portable terminal carried by a store employee.

[0188] [Sixth variation] In the above embodiment, the monitoring device 80 receives the operation request information transmitted by the customer terminal device 50 via the transaction management device 60, thereby acquiring the product information contained in the operation request information. In other words, the monitoring device 80 in the above embodiment passively acquires product information. However, the monitoring device 80 may be configured to actively acquire product information by querying the transaction management device 60 for product information at predetermined timings, such as at regular intervals. In this case, the transaction management device 60 may, in response to an inquiry from the monitoring device 80, transmit the product information it has received and stored from the customer terminal device 50 to the monitoring device. Alternatively, the transaction management device 60 may, in response to an inquiry from the monitoring device 80, cause the customer terminal device 50 to transmit the product information, and then forward the received product information to the monitoring device. Alternatively, product information may be transmitted and received between the customer terminal device 50 and the monitoring device 80 without the transaction management device 60 acting as an intermediary.

[0189] [7th variation] In the above embodiment, some of the processing performed by the customer terminal device 50 may be performed by, for example, the transaction management device 60, the monitoring device 80, the settlement device 40, the management device 10, other higher-level devices within the store, or server devices on the cloud. Similarly, some of the processing performed by each of the transaction management device 60, the monitoring device 80, the settlement device 40, the management device 10, etc., may be performed by other devices. As one of the embodiments described above, the shopping system of this embodiment may be configured as a thin client system. For example, the transaction management device 60 or another server may be configured as a thin client-compatible server (for example, a cloud server), and the customer terminal device 50, monitoring device 80, etc. may be configured to function as thin clients. Furthermore, the transaction management device 60, monitoring device 80, management device 10, etc., may be configured to be distributed across multiple computer devices or servers.

[0190] <Summary of Embodiments> [Technical field] This invention relates to a product sales data processing system. [Background technology] A system is known in which customers register products themselves using a mobile device (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2018-147252 [Overview of the prefecture] [Problems the invention aims to solve] In a product sales data processing system where customers register products themselves using mobile devices, product registration results may be incomplete. For products with incomplete registration results, the incomplete state is resolved, for example, through the actions of a store employee. It is desirable that such resolution of incomplete registration results be carried out efficiently. This invention has been made in view of these circumstances, and aims to efficiently resolve the issue of incomplete product registration results in a product sales data processing system in which customers register products themselves using a mobile terminal.

[0191] [Means for solving the problem] (1) As described above, one aspect of this embodiment is a product sales data processing system in which a customer registers a product based on a product registration operation using a mobile terminal device (e.g., customer terminal device 50), and comprises: an acquisition control means that causes a monitoring device used by a store employee (e.g., monitoring device 80) to acquire information about the product that failed to register (e.g., the product that failed to register)

[0192] With the above configuration, if a reserved item is registered as a result of the product registration operation, the store clerk can remotely release the reserved item using the monitoring device 80. This allows the reserved item to be released even before settlement is performed at the settlement device 40. Furthermore, it becomes possible to distribute the release of reserved items between the monitoring device 80 and the settlement device 40, for example. This allows for the efficient release of reserved items (an example of resolving a state where the product registration result is incomplete).

[0193] (2) One aspect of this embodiment is the product sales data processing system described in (1), wherein the unregistered product is a product whose product information, associated with the product code acquired by the mobile terminal device in response to the product registration operation, does not exist in the product information database (e.g., product master) used for managing products at the store (e.g., a reserved product classified as "NON-FILE"), the display control means displays the screen which presents a predetermined portion of the information items included in the product information as input items for the registration supplement information (e.g., input area AR30 (AR40)), and the normal registration means performs normal registration of the unregistered product based on the product code and the information entered in the input items.

[0194] According to the above configuration, for pending items classified as "NON-FILE," remote release of the pending item is possible by entering specified information items other than the product code obtained through the product registration operation into the product information input screen. This completes the information necessary for product registration, allowing for the release of the pending item as a successful registration.

[0195] (3) One aspect of this embodiment is the product sales data processing system described in (1) or (2), wherein the unregistered product is a product for which the product code could not be obtained when the mobile terminal device failed to obtain the product code from the captured image as a result of the product registration operation in which the mobile terminal device captures the product code, the display control means presents the captured image as an image to show the user (e.g., a store employee) the products that are the target of normal registration, and displays the screen which presents a predetermined portion of the information items included in the product information stored in the product information database used for product management at the store as input items for the registration supplement information, and the normal registration means performs normal registration of the unregistered product based on the information entered in the input items.

[0196] According to the above configuration, for held items classified as "reading failed," "pseudo-scanned input," or "non-scanned input," remote operation to release the hold is performed by entering predetermined information items into the product information input screen. This completes the information necessary for product registration, enabling the release of the hold as a normal registration.

[0197] (4) One aspect of this embodiment is a product sales data processing system according to any one of (1) to (3), wherein the display control means controls the monitoring device to display a list of customers whose registered products include the incompletely registered products based on the product registration operation.

[0198] According to the above configuration, store employees can use the monitoring device 80 to understand the status of customers who have registered items to be held in the store.

[0199] (5) One aspect of this embodiment is a product sales data processing system according to any one of (1) to (4), comprising notification control means that controls the portable terminal device to display a message to inform the customer that the incomplete registration result based on the product registration operation is correctable by an operation of the store clerk to the monitoring device when the product registration result is incomplete.

[0200] According to the above configuration, customers can be informed that remote release of the hold is possible, and then have a store employee perform the remote release of the hold for them.

[0201] (6) One aspect of this embodiment is a product sales data processing system according to any one of (1) to (5), wherein the acquisition control means, when the product registration result based on the product registration operation is incomplete, causes the store clerk to acquire the incomplete product information without accepting a customer's request for normal registration (for example, an operation on the operation request button BT51).

[0202] With the above configuration, store staff can release items that have been registered as held items without the customer having to perform an operation to request normal registration. This configuration is effective, for example, in cases where an item is registered as held due to a store error, such as with "NON-FILE," because it allows for normal registration without requiring the customer to perform an operation to request normal registration.

[0203] (7) One aspect of this embodiment is a program that causes a computer in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device to function as an acquisition control means that causes a monitoring device used by a store employee to acquire information about products that were not properly registered when the product registration result based on the product registration operation was incomplete, a display control means that causes the monitoring device to display a screen based on the information about products that were not properly registered acquired by the acquisition control means, and a normal registration means that performs normal registration in which the products that were not properly registered are registered as normal products in response to the input of registration completion information on the displayed screen.

[0204] (8) One aspect of this embodiment is a monitoring device used by a store employee in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device, and the monitoring device comprises: an acquisition means for acquiring incomplete product information relating to a product whose registration result was incomplete when the product registration result based on the product registration operation was incomplete; a display control means for displaying a screen based on the incomplete product information acquired by the acquisition means; and a normal registration means for performing a normal registration in which the incomplete product is registered as a normal product in response to the input of registration supplementation information to the displayed screen.

[0205] (9) One aspect of this embodiment is a program that causes a computer used by a store employee as a monitoring device in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device to function as an acquisition means for acquiring incomplete product information regarding incompletely registered products when the product registration result based on the product registration operation is incomplete; a display control means for displaying a screen based on the incompletely registered product information acquired by the acquisition means; and a normal registration means for performing normal registration in which the incompletely registered product is registered as a normal product in response to the input of registration supplement information to the displayed screen.

[0206] (10) One aspect of this embodiment is a server device (for example, a transaction management device 60) provided in a product sales data processing system in which a customer registers products based on a product registration operation using a mobile terminal device, and the server device comprises: an acquisition control means that causes a monitoring device used by a store employee to acquire information on products for which the registration result based on the product registration operation was incomplete; a display control means that causes a screen based on the information on products for which registration was incomplete, acquired by the acquisition control means, to be displayed on a monitoring device operated by a store employee; and a normal registration means that performs a normal registration in which the products for which registration was incomplete are registered as normal products in response to the input of registration completion information on the screen displayed on the monitoring device.

[0207] Furthermore, programs for realizing the functions of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, monitoring device 80, etc., as described above in each embodiment may be recorded on a computer-readable recording medium, and the programs recorded on this recording medium may be loaded into a computer system and executed to perform the processing of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, monitoring device 80, etc. Here, "loading the programs recorded on the recording medium into a computer system and executing them" includes installing the programs into the computer system. Here, "computer system" includes hardware such as the OS and peripheral devices. Also, "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Thus, the recording medium on which the program is stored may be a non-transient recording medium such as a CD-ROM. Furthermore, the recording medium includes internal or external recording media accessible from the distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in an executable format for the terminal device. In other words, the format in which it is stored on the distribution server is irrelevant as long as it can be downloaded from the distribution server and installed in an executable format for the terminal device. It is also acceptable for the program to be divided into multiple parts, downloaded at different times, and then combined on the terminal device, and for each of the divided programs to be distributed by a different distribution server. Moreover, "computer-readable recording medium" includes volatile memory (RAM) within computer systems that act as servers or clients when a program is transmitted over a network, which retains the program for a certain period of time. Furthermore, the program may be intended to implement only a part of the functions described above.Furthermore, the above-mentioned functions may be implemented in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [Explanation of Symbols]

[0208] 10 Management devices, 40 Settlement devices, 50 Customer terminal devices, 60 Transaction management devices, 70 Credit card payment servers, 80 Monitoring devices

Claims

1. A product registration means for customers who are browsing the sales floor to register products based on product registration operations using a terminal device, A notification means for notifying store employees about products whose registration results were incomplete using the aforementioned product registration means, A display control means that displays a screen relating to the incompletely registered product after the notification by the notification means, The system includes a normal registration means that, in response to the input of registration supplement information, performs normal registration to register the incompletely registered product as a normal product, The aforementioned incompletely registered products include products for which product information associated with the product code obtained by the terminal device in response to the product registration operation does not exist in the product information database used for product management at the store. The display control means, on the screen relating to the unregistered product, displays a text input field or an operator to delete the unregistered product as the normal registration means. Product sales data processing system.

2. The display control means displays the screen that presents at least the selling price information item among the information items included in the product information as an input item for the registration supplement information. The normal registration means performs normal registration of the unregistered product based on the product code and the information entered in the input fields. Product sales data processing system according to claim 1.

3. The aforementioned unregistered products include products for which the product code could not be obtained when the terminal device failed to acquire the product code from the captured image as a result of the product registration operation in which the terminal device was made to capture the product code. The display control means presents the captured image as an image to show the user the product to be successfully registered, and displays the screen which presents at least the selling price information item, from among the information items included in the product information stored in the product information database used for product management at the store, as an input item for the registration supplement information. The normal registration means performs normal registration of the unregistered product based on the information entered in the input fields. Product sales data processing system according to claim 1 or 2.

4. The terminal device further includes a notification control means that controls the terminal to display a message informing the customer that if the product registration result based on the aforementioned product registration operation is incomplete, the incomplete registration result can be resolved by a store employee. A product sales data processing system according to any one of claims 1 to 3.

5. The computer in the product sales data processing system A product registration means in which customers register products based on product registration operations using a terminal device while browsing the sales floor. A notification means for notifying store employees about products whose registration results were incomplete using the aforementioned product registration means. Display control means that, after the notification by the notification means, displays a screen relating to the incompletely registered product. A normal registration means that, upon input of registration supplementary information, registers the incompletely registered product as a normal product. It is a program designed to function as such. The aforementioned incompletely registered products include products for which product information associated with the product code obtained by the terminal device in response to the product registration operation does not exist in the product information database used for product management at the store. The display control means, on the screen relating to the unregistered product, displays a text input field or an operator to delete the unregistered product as the normal registration means. program.

Images