Portable registration terminal, product sales data processing system, and program

Abstract

To provide a product sales data processing system that allows a customer himself / herself to register a product by using a portable registration terminal, the system performing processing for a salesperson intervention requiring product in a manner not to disturb the advance of payment by other customers.SOLUTION: The portable registration terminal includes: registration means for registering products; and information generation means for generating payment shift information when a salesperson intervention requiring product required for salesperson intervention processing where a salesperson intervenes is not included in the products registered by the registration means, and generating salesperson intervention shift information on a shift to the salesperson intervention processing when the salesperson intervention requiring product is included in the products registered by the registration means.SELECTED DRAWING: Figure 14

Description

Technical Field

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

Background Art

[0002] A system in which customers register products by themselves 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 register products by themselves using a portable registration terminal, there may be a registration result that the intervention of a store clerk is required for the products registered by the portable registration terminal. For transactions including products that require the intervention of a store clerk (store clerk intervention products), after a store clerk performs a predetermined process corresponding to the store clerk intervention products, the process proceeds to settlement. It is preferable that the process corresponding to the store clerk intervention products is performed so as not to interfere with the accounting of other customers.

[0005] The present invention has been made in view of such circumstances, and an object of the present invention is to perform a process corresponding to a store clerk intervention product so as not to interfere with the progress of the accounting of other customers in a product sales data processing system in which customers register products by themselves using a portable registration terminal.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-mentioned problems is a portable registration terminal comprising: a registration means for registering products; and an information generation means for generating settlement transition information if the products registered by the registration means do not include products requiring staff intervention, and for generating staff intervention transition information regarding the transition to staff intervention if such products are included.

[0007] Furthermore, one aspect of the present invention is a terminal for store employees that, in response to the fact that the products registered by a portable registration terminal in a transaction include products requiring store employee intervention, edits transaction information containing the products requiring store employee intervention as part of the store employee intervention process.

[0008] Furthermore, one aspect of the present invention is a program that causes a computer as a portable registration terminal to function as a registration means for registering products, and as an information generation means for generating settlement transition information if the products registered by the registration means do not include products requiring staff intervention, and for generating staff intervention transition information regarding the transition to staff intervention if such products are included.

[0009] Furthermore, one aspect of the present invention is a product sales data processing system comprising a portable registration terminal and a server, wherein the server comprises registration means for registering products based on product identification information transmitted from the portable registration terminal, and information generation means for generating settlement transition information if the products registered by the registration means do not include products requiring staff intervention, and for generating staff intervention transition information regarding the transition to staff intervention if such products are included, and for outputting the generated settlement transition information or staff intervention transition information to the portable registration terminal. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of the configuration of the shopping system in the first embodiment. [Figure 2] This figure shows an example of the installation of the payment device in the first embodiment. [Figure 3] This figure shows an example of the appearance of the settlement device in the first embodiment. [Figure 4] This figure shows an example of the configuration of the settlement device in the first embodiment. [Figure 5] This figure shows an example of the configuration of a customer terminal device in the first embodiment. [Figure 6] This figure shows an example of the configuration of the transaction management device in the first embodiment. [Figure 7] This figure shows an example of the configuration of the transaction information management device in the first embodiment. [Figure 8] This figure shows an example of customer information, store information, and cart information in the first embodiment. [Figure 9] This figure shows an example of the definition of a reserved product in the first 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 the first embodiment in response to the accounting of a single transaction in self-service operation. [Figure 11] This figure shows an example screen of a shopping application in the first embodiment. [Figure 12] This figure shows an example of a registered product display screen, a product registration screen, and a guidance image in the first embodiment. [Figure 13] This figure shows an example of a settlement screen in the first embodiment. [Figure 14] This figure shows an example of the hold release transition code screen in the second embodiment. [Figure 15] This flowchart shows an example of a processing procedure executed by the customer terminal device in the second embodiment upon completion of product registration. [Modes for carrying out the invention]

[0011] <First Embodiment> [Example of a shopping system configuration] FIG. 1 shows a configuration example of a shopping system (an example of a product sales data processing system) according to the present embodiment. The shopping system in the figure is, for example, an accounting (customer terminal-corresponding accounting) in which a customer takes out a product to be purchased from a product shelf and registers the taken-out product using a customer terminal device 50, and the same customer uses a settlement device 40 to settle the registered product. The accounting here includes registration of a product and settlement of the registered product, and refers to a procedure performed corresponding to one transaction. The shopping system according to the present embodiment includes a management device 10, a transaction management device 60, a settlement device 40, a customer terminal device 50, a transaction information management device 80, and a credit card settlement server 70.

[0012] The management device 10, the settlement device 40, and the transaction information management 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. The transaction information management device 80 may be installed, for example, at a service counter or a backyard.

[0013] The transaction information management 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 in one store is not particularly limited.

[0014] The customer terminal device 50 is operated by the customer (a shopper who is a member of the store, etc., hereinafter also simply referred to as "customer"). In addition to general communication and imaging functions (camera), the customer terminal device 50 is equipped with a recognition function that scans the barcode attached to the product and reads the product code, that is, recognizes the barcode attached to the product. The recognition function of the customer terminal device 50 only needs to be able to read the product code, and does not need to be able to recognize which product the read product code belongs to. In other words, the customer terminal device 50 only needs to be able to read the product code from the barcode when the barcode exists as an object in the captured image (the image acquired as a through image) captured by the imaging function.

[0015] Such customer terminal devices 50 may be smartphones, tablet devices, etc., owned by the customer. A shopping application having the function of registering products in accordance with the shopping system of this embodiment is installed on the smartphone or tablet device, etc., which serves as the customer terminal device 50.

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

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

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

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

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

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

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

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

[0024] 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 storage unit 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.

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

[0026] RAM403 is a read / write memory that stores various types of information. For example, RAM403 stores information read from ROM402 and storage unit404, information acquired from external sources, and information generated during processing.

[0027] The memory unit 404 stores various types of information. For example, instead of the ROM 402, the memory unit 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 acquired from external sources, information generated during processing, etc. The memory unit 404 may be configured with, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), etc.

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

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

[0030] 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.).

[0031] 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.).

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

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

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

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

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

[0037] 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).

[0038] 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. Such mode switching may be performed, for example, according to a predetermined time period within the store's business hours. Furthermore, the payment device 40 in this embodiment may be configured as a dedicated device specialized for the above-mentioned customer terminal-compatible payment mode.

[0039] [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. In this embodiment, the display unit 504 is 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.

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

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

[0042] [Example of Transaction Information Management System Configuration] Figure 7 shows an example configuration of the transaction information management device 80. The transaction information management 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 transaction information management 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 transaction information management 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 operators provided by the transaction information management device 80 and the input devices connected to the transaction information management device 80.

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

[0044] 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).

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

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

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

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

[0049] 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).

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

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

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

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

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

[0055] 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).

[0056] 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).

[0057] "Reading Failed" refers to a situation where scanning a product code in a store fails (the product code could not be read), or it is one manifestation of a case where scanning a product code in a store fails. In other words, "Reading Failed" refers to a timeout process that occurs when, for example, image recognition technology detects a product for a certain period of time but fails to recognize the barcode, and it also refers to the event that results in a timeout. 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.

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

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

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

[0061] The classification of the held item with classification number 2 is "Unreadable" as explained in Figure 8. The customer terminal device 50 determines that a reading failure has occurred if, despite recognizing that the entire product barcode has been captured in the image obtained by the imaging unit 506, the barcode reading is not completed successfully after a certain period of time.

[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] "Simulated 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] Specifically, for example, the customer terminal device 50 determines that a pseudo-scan has occurred if, although the product is recognized in the captured image, the barcode cannot be recognized at all, and therefore the barcode reading process does not complete successfully. Alternatively, the customer terminal device 50 may determine that a pseudo-scan has occurred if the barcode reading is not completed successfully because only a portion of the product's barcode can be recognized in the captured image. Alternatively, the customer terminal device 50 may determine that a pseudo-scan has occurred even if the barcode of the product was recognized in the captured image, but the barcode reading could not be completed successfully because the product was moving too fast. When such pseudo-scans occur, it's possible that fraud is taking place where customers are merely pretending to scan product barcodes while secretly placing items in their shopping carts.

[0065] 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 in 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.

[0066] Specifically, for example, if the customer terminal device 50 is set in a shopping cart, it can capture images of the contents of the shopping basket placed in the shopping cart. The customer terminal device 50 determines that a non-scanned item has been added to the shopping basket if it detects in the captured image that a new item has been added, even though there is no indication that the barcode of the item is being scanned. 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 that do not require scanning, based on the captured image. Such instances of non-scanning may indicate fraudulent activity, such as customers placing items in their shopping carts without scanning the barcodes of the products using the customer terminal device 50.

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

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

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

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

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

[0072] For pending items classified as "NON-FILE" under classification number 1, the product code was obtained through a code scan in response to the product registration operation, but the product information associated with the obtained product code is not registered in the product master. Therefore, it is not possible to identify which of the products registered in the product master corresponds to the pending items classified as "NON-FILE" under classification number 1. 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.

[0073] Among classification numbers 1 to 7, pending items that fall under any of the four categories "NON-FILE," "Reading NG," "Pseudo-Scan Input," or "Non-Scan Input" (classification numbers 1 to 4) are considered unspecified items. Unspecified items are those for which the registration result was incomplete because, for example, it could not be determined which of the items registered in the product master it was (the corresponding product information could not be identified). Unspecified products are further divided into two categories: products with a code obtained through the product registration process, such as "NON-FILE" under classification number 1, and products without a code obtained through the product registration process, such as "Reading NG," "Pseudo-Scan Input," and "Non-Scan Input" under classification numbers 2-4.

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

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

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

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

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

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

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

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

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

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

[0084] 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).

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

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

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

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

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

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

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

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

[0093] 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).

[0094] Step S11: The customer terminal device 50, having received the payment transition instruction operation, generates a payment transition code CDP. In other words, the customer terminal device 50 generates a payment transition code CDP by 2D coding the information necessary to perform the payment process for the purchased items by the customer terminal device 50 (for example, cart identification information). The customer terminal device 50, having generated the payment transition code CDP, displays the generated payment transition code CDP on the display unit. For example, the customer terminal device 50 displays a payment transition code screen on the display unit, with the payment transition code CDP arranged as shown in Figure 11(D).

[0095] Step S12: The payment device 40 scans (reads) the payment transition code CDP displayed on the display unit of the customer terminal device 50. For example, the payment device 40 scans the payment transition code CDP 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.

[0096] Step S13: The settlement device 40, having read the settlement transition code CDP displayed on 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 settlement transition code CDP, requesting the calculation of the subtotal amount.

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

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

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

[0100] Step S17: The settlement device 40, having received cart identification information and subtotal information (settlement information) from the transaction management device 60, displays the subtotal amount on the customer-side display unit 405.

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

[0102] 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.).

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

[0104] Furthermore, after the settlement device 40 reads the settlement transition code CDP displayed on the customer terminal device 50, it 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 settlement device 40 refers to the store identification information of the store (it may store and refer to the store identification information of the store within the settlement device 40 itself, or it may refer to store identification information stored in another accessible device), and when it reads the settlement transition code CDP displayed on the customer terminal device 50, it compares the cart identification information obtained from the settlement transition code CDP with the store identification information of the store. The settlement device 40 then may permit the request to calculate the subtotal amount if the store identification information included in the cart identification information includes the store identification information of the store in question, and may 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).

[0105] 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 it includes items from stores other than XX") on the customer-side display unit 405 after reading the payment transition code CDP. 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.

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

[0107] In the shopping system of this embodiment, the customer terminal device 50 may not transmit product registration information each time a product is registered, as shown in Figure 10, but may instead transmit product registration information for all registered products at once when product registration for all products is complete.

[0108] [Regarding the operation of customer terminal devices when unspecified products are registered] In Figure 10, step S5 is the process that is performed when the product code has been successfully read and the product corresponding to the read product code has been identified. However, at the stage in step S5 when the customer terminal device 50 is performing the product code reading process, there is a possibility that the product registration result will be that the product has been registered as an unspecified product under one of the classification numbers 1 to 4 in Figure 9 (unspecified result).

[0109] As a concrete example, Figure 12(B) shows an example of what happens when the customer terminal device 50 determines that an unidentified result has occurred as a pseudo-scan for classification number 3, using an image captured from the product registration screen. The figure shows the product registration screen displayed on the customer terminal device 50. The product registration screen in the figure shows an image captured from the customer attempting to have the customer terminal device 50 read the product's barcode, with the barcode portion being obscured by the customer's finger. Furthermore, if a product is registered as an unspecified item or otherwise classified as a pending item, a button may be displayed that allows the user to call a store employee to have the pending item released.

[0110] In such a case, the customer terminal device 50 obtains a processing result indicating that it recognized the presence of a barcode from the captured image, but was unable to extract the code from the barcode. Since this processing result falls under one type of processing result in a pseudo-scan, the customer terminal device 50 detects that a pseudo-scan has occurred. In this case, the customer terminal device 50 transmits product registration information to the transaction management device 60 indicating that the pseudo-scan of classification number 3 was performed on an unspecified product.

[0111] Furthermore, when the customer terminal device 50 transmits product registration information in response to the occurrence of an unspecified result as described above, it transmits an image corresponding to the unspecified result. The transmitted image may be extracted from the image captured by the imaging unit 506 for reading the product code, after the image has been buffered for a certain period of time. The transmitted image may also be a predetermined number of still images, or a moving image for a predetermined period corresponding to the occurrence of an unspecified result.

[0112] Furthermore, if an unspecified result occurs as described above and the product to be registered is designated as an unspecified product, the customer terminal device 50 treats the unspecified product as a reserved product. In this case, when the customer terminal device 50 determines that an unspecified result has occurred, it may, as shown in Figure 12(C), designate the unspecified product as a reserved product and display a guidance image WD2 prompting the customer to place it in a reserved product bag. Specifically, the guidance image WD2 in the figure displays the message, "If the product cannot be scanned, please place it in the dedicated bag." The form of the guidance image WD2 is not particularly limited. The guidance image WD2 in the figure is displayed superimposed on the product registration screen. A confirmation button BT3 is placed in the guidance image WD2 in the figure. In this case, the guidance image WD2 is erased when an operation is performed on the confirmation button BT3. Alternatively, the guidance image WD2 may be erased after a certain period of time has elapsed since the start of display. After the guidance image WD2 is erased, the user may return to the product registration screen, for example, in Figure 11(B) or Figure 11(C).

[0113] Unspecified products are treated as pending products as described above. On the product registration screen, the registered product list is displayed as exemplified in Figure 11(C), but for pending products that are classified as unspecified products, the list item does not need to be displayed in the registered product list. Pending products that are not classified as unspecified products are displayed as list items in the registered product list. In addition, for unspecified products, a list item may be displayed in the registered product list to indicate that they are unspecified products.

[0114] Once the customer has finished registering all the items to be purchased, they perform a settlement transition instruction operation, causing the settlement transition code CDP displayed on the customer terminal device 50 to be read by the settlement device 40. Having read the settlement transition code CDP, the settlement device 40 requests the transaction management device 60 to calculate the subtotal amount, as shown as step S13 in Figure 9. In this embodiment, when requesting the calculation of the subtotal amount, the settlement device 40 requests settlement information to be used in the settlement process.

[0115] The transaction management device 60 identifies the relevant cart information in response to a request for settlement information and generates settlement information based on the identified cart information. The settlement information includes registered product information in the cart information and information such as the subtotal amount corresponding to the registered products. In addition, among the registered product information included in the settlement information, the registered product information corresponding to products that were not registered includes an image corresponding to the unidentified result. The transaction management device 60 transmits the generated settlement information to the settlement device 40. When the payment device 40 receives payment information, it displays a payment screen on the customer-side display unit 405 that reflects the contents of the received payment information.

[0116] Figure 13 shows an example of a payment screen displayed on the customer-side display unit 405 of the payment device 40. In the checkout screen shown in the figure, the registered product list area AR3 is located. The registered product list area AR3 is an area that displays a list of products registered by the customer terminal device 50.

[0117] In the following explanation, the product information (registered product information, pending product information) corresponding to each product list item in the registered product list area AR3 may also be referred to as a record. Furthermore, registered product information and pending product information corresponding to classifications such as age-verified products (classification number 5), pharmaceuticals (classification number 6), and security tag products (classification number 7) are also called product identification records because the products are identified. Among the product identification records, registered product information corresponds to products that have been successfully registered, not pending products, and is therefore also called successfully registered records. Among the pending product information, those corresponding to unidentified products (classification numbers 1-4) are also called unidentified records.

[0118] If the registered products include items on hold, the list items for the held products will be prioritized and placed at the top of the left column in the registered product list area AR3. In other words, the list items for the held products will be arranged sequentially from the beginning in the registered product list area AR3. In the example shown in the figure, since five pending items were included among the registered items, a pending item list area AR31 was formed in the registered item list area AR3, containing list items for the five pending items from the top left. The list items in the pending item list area AR31 are designed to differ from the list items of other items, for example, in terms of background color.

[0119] Furthermore, in the pending product list area AR31, the list items corresponding to the product identification records for which the product has been identified are arranged in order first, followed by the list items corresponding to the unidentified products for which the product has not been identified. In other words, the pending product list area AR31 is arranged in a way that separates the list items corresponding to the product identification records for which the product has been identified from the list items corresponding to the unidentified products for which the product has not been identified.

[0120] In the registered product list area AR3, the list items corresponding to successfully registered records are placed following the pending product list area AR31. The diagram shows an example where the list items corresponding to successfully registered records in the registered product list area AR3 are arranged in descending order of product price. In the list fields of the registered product list area AR3, the list field corresponding to the product identification record displays the product name, registered quantity, and price corresponding to the registered quantity of the identified product.

[0121] In the reserved item list area AR31, a reserved item release declaration button BT31 is placed in each reserved item's list item. The reserved item release declaration button BT31 is used to declare the release of the reserved item. However, the reserved item release declaration button BT31 cannot be operated on the settlement screen shown in the diagram, but it can be operated on the reserved item release processing screen described later. On the settlement screen, the reserved item release declaration button BT31 functions as an icon to indicate that the corresponding list item corresponds to a reserved item.

[0122] The BT31 button, which declares the release of a hold, displays the name of the category to which the corresponding product belongs as a held product. Specifically, for example, age-verification products (classification number 5), pharmaceuticals (classification number 6), security tag products (classification number 7), and cancellation products (classification number 8), the corresponding classification name will be displayed on the BT31 button for declaring the release of hold. In addition, unspecified products (classification numbers 1-4) will be collectively displayed as "Holding Products." The diagram shows an example of how the BT31 button for declaring the release of hold items displays. The first row of the list item is displayed as "Age Verification" because it is an age verification product (classification number 5), the second row of the list item is displayed as "Security Tag" because it is a security tag product (classification number 7), and the third row of the list item is displayed as "Pharmaceuticals" because it is a pharmaceutical product (classification number 6). The fourth and fifth rows of the list item are shown as "Hold Item," respectively. In the list items on the 4th and 5th rows, thumbnail images TN are placed. The thumbnail image TN is an image captured by the customer terminal device 50 when a product registration operation is being performed for the corresponding unspecified product. The thumbnail image TN may be a still image or a video. The presence or absence of a thumbnail image (TN) allows store staff to visually distinguish between list items for unspecified items and list items for identified items in the pending items list. Furthermore, the content displayed in the thumbnail image (TN) allows store staff to understand what the item actually was that was registered as unspecified. Furthermore, the display indicating the corresponding classification on the hold release declaration button BT31 may be an icon or other image representing the classification.

[0123] Among the list items for pending items, for specific items such as age verification products (classification number 5), pharmaceuticals (classification number 6), and security tag products (classification number 7), the product name, registered quantity, and price corresponding to the registered quantity of the specified product will be displayed. In contrast, the list item corresponding to the unspecified product will display content according to the classification of the corresponding pending product. Specifically, in the case of an unspecified product as NON-FILE (classification number 1), the list item on the 5th line of the figure may indicate that it is NON-FILE and show the read product code. Furthermore, in the case of unspecified products (products with no code) that are read NG (classification number 2), pseudo-scan input (classification number 3), and non-scan input (classification number 4), a message indicating that the product code could not be read may be displayed, as shown in the list item on the 4th line of the figure.

[0124] As shown in the figure, if a reserved product list area AR31 is formed in the registered product list area AR3 of the checkout screen, the store clerk needs to perform an operation to process the reserved product. When a checkout screen with a reserved product list area AR31 formed in this way is displayed, the checkout device 40 executes a store clerk call to prompt the store clerk to perform an operation to process the reserved product. As a store clerk call, the checkout device 40 may, for example, display a signpost or other indicator in a predetermined manner, or send a store clerk call notification to a terminal device held or monitored by the store clerk. Furthermore, as shown in the figure, when the payment screen is displayed in which the reserved product list area AR31 is formed because the registration results include reserved products, the payment device 40 is configured not to accept payment operations from the customer. Also, for example, in the area above the registered product list area AR3 on the payment screen in the figure, a message is displayed to the customer informing them that a store employee who has been called will come to the payment device 40.

[0125] When a store employee is called to the payment device 40, the employee goes to the payment device 40 and performs a login operation to log in as an employee. In this case, the login operation may be, for example, having the employee code (which may be in the form of a 2D code or barcode) printed on the employee ID card read by the scanner unit (customer-side scanner unit 406 or employee-side scanner unit 412). Alternatively, it may be an operation to input an employee number, etc., by, for example, placing an item.

[0126] In response to the store clerk logging in, the display on the customer-side display unit 405 transitions from the payment screen to the hold release processing screen (not shown). By performing operations on the hold release processing screen, the store clerk releases the hold status (releases the hold) for each item in the list of held items displayed in the registered product list area AR3 of the payment screen. The hold release processing screen may consist of multiple screens. In other words, when the hold release processing screen 1 is displayed, the system may transition to another hold release processing screen that accepts a predetermined operation in response to an operation performed by the store clerk.

[0127] When a store employee wants to release a held item that belongs to a category where the product can be identified (age verification items (category number 5), pharmaceuticals (category number 6), and security tag items (category number 7)), they perform the prescribed handling procedure according to the respective category and then perform a hold release declaration operation to release the held item. In response to the hold release declaration operation, the settlement device 40 sends a hold release request to the transaction management device 60. Upon receiving the hold release request, the transaction management device 60 manages the corresponding held item information as regular product information. As a result, the held status is released for held items of categories where the product can be identified.

[0128] Specifically, if the item to be released from hold is an age-recognition item, the store clerk will verify that the customer is an adult as part of their customer service procedure and then perform the action to release the hold. Furthermore, if the item to be released from the hold is a pharmaceutical product, the store clerk, as part of their customer service, will either explain the product themselves if they are a qualified pharmacist, or have another store clerk who is a qualified pharmacist explain it before performing the action to release the hold. Furthermore, if the item to be released from hold has a security tag, the store employee will remove the security tag attached to the item as part of the customer service procedure and then perform the operation to declare the item released from hold.

[0129] Furthermore, when a store employee releases a held item classified as an unspecified item (NON-FILE (classification number 1), read failure (classification number 2), simulated scan insertion (classification number 3), non-scanned insertion (classification number 4)), they will determine what the held item is, for example, from the actual item or the image captured at the time of registration displayed on the release processing screen. The store clerk confirms what the held item is and then performs an operation on the hold release processing screen to input the corresponding product information. The settlement device 40 sends a hold release request containing the entered product information to the transaction management device 60. Upon receiving the hold release request, the transaction management device 60 uses the product information contained in the received hold release request to manage the held item information for the held item classified as an unspecified item as regular product information. As a result, the held status for the held item classified as an unspecified item is released.

[0130] Additionally, store employees can remove the held item from their records by deleting the item's registration. Additionally, when a store employee releases a held item and registers it normally, they may, if necessary, enter the purchase quantity.

[0131] In this way, once the holding status of all held items in a transaction has been released, the settlement device 40 displays a settlement screen that does not include any held items. The customer can then perform the settlement by operating the settlement device 40, which displays the settlement screen in this manner.

[0132] Furthermore, the staff-side display unit 410 may also display a payment screen similar to that shown in Figure 13, and may allow the staff to perform payment-related operations on behalf of the customer. In addition, when the staff-side display unit 410 displays the payment screen, the system may transition from the payment screen to the hold release processing screen in response to the staff's login operation. Moreover, the staff may be able to operate on the hold release processing screen displayed on the staff-side display unit 410.

[0133] <Second Embodiment> Next, a second embodiment will be described. In the first embodiment described above, the process of releasing the hold is performed by having the settlement transition code CDP displayed on the customer terminal device 50 after the customer has finished registering the product, and then having the settlement device 40 read the CDP, and then having a store employee go to the settlement device 40 and perform the operation. However, with the above procedure for releasing held items, the store clerk has to perform the operation to release the held items at the payment machine 40, where the customer would normally perform the payment. As a result, customers waiting in line to pay for transactions that include held items will have to wait for the extra time required for the store clerk to release the held items. In other words, the progress of other customers' payments will be hindered. Note that "payment" here refers to the procedure that includes everything from registering the items in a transaction to settling the payment for those registered items.

[0134] For example, in the shopping system of this embodiment, when a customer registers an item using the customer terminal device 50, resulting in the item being registered as a pending item, a notification may be sent to the employee terminal. The employee terminal may be, for example, a transaction information management device 80, a management device 10, etc. Alternatively, the employee terminal may be a POS register installed in the store and operated by an employee. It may also be a personal computer installed in the store. Alternatively, it may be a mobile terminal for employees, such as a smartphone, tablet, or handheld terminal. For example, if the customer terminal device 50 is lent to the customer by the store in a manner such as being fixedly attached to a shopping cart, the customer terminal device 50 may also be made capable of functioning as an employee terminal. In this case, the store clerk who receives the notification can immediately attend to the customer and perform the hold release operation. This eliminates the need for the store clerk to perform the hold release operation at the payment device 40. However, in this case, the store clerk will become aware of the hold and respond to the hold release operation before the customer has completed product registration. For example, some customers may not like the fact that their product registration status is known even though they have not completed product registration.

[0135] Therefore, the shopping system of this embodiment is configured, as described below, to allow a store employee to release the hold before the customer goes to the payment device 40, in response to the customer completing product registration using the customer terminal device 50.

[0136] As mentioned above, once the customer has completed registering all the items they wish to purchase, they operate the "Proceed to Checkout" button located on the product registration screen displayed on the customer terminal device 50. In other words, the customer performs a checkout instruction operation upon completion of product registration. Note that in relation to the "Proceed to Checkout" button, "checkout" is used synonymously with "settlement." In this case, if the registered items do not include any items on hold, the customer terminal device 50 displays a settlement transition code screen with the settlement transition code CDP, as shown in Figure 11(D). In this case, the customer can proceed to the settlement device 40 and have the settlement device 40 read the settlement transition code CDP to complete the settlement.

[0137] In response to this, if the registered items include items on hold, the customer terminal device 50 displays a hold release transfer code screen instead of a settlement transfer code screen, in accordance with the settlement transfer instruction operation.

[0138] Figure 14 shows an example of the Hold Release Transition Code screen. In the Hold Release Transition Code screen shown in the figure, the Hold Release Transition Code CDH is displayed. The Hold Release Transition Code screen also displays a message instructing the customer to go to the service counter and present the Hold Release Transition Code CDH to a store employee, as the registered items include items on hold. The Hold Release Transition Code screen also features a Payment Transition Instruction Button BT41. The Payment Transition Instruction Button BT41 is a button used to proceed to payment after the held items have been released. The payment transition instruction button BT41 may be disabled until the payment is no longer possible, such as when the hold is released. If the payment transition instruction button BT41 is operated despite being disabled, the customer may not be aware of the current situation requiring the release of the hold. In such cases, a pop-up window or similar notification may be displayed to the customer instructing them to go to the service counter to have a staff member release the hold, so that the staff member can accurately understand the current situation. Alternatively, instead of the payment transition instruction button BT41, a button for calling a staff member or a button for returning to the product registration screen may be provided.

[0139] The information in the hold release transition code CDH, like the checkout transition code CDP, includes cart identification information that reflects the results of the customer's product registration. However, the information in the hold release transition code CDH includes read control information that can be read by the employee terminal but not accepted (cannot be read) by the checkout device 40.

[0140] Therefore, even if a customer goes to the payment device 40 and attempts to have the payment device 50 read the hold release transition code CDH displayed on the hold release transition code screen, the payment device 40 may not accept the reading of the hold release transition code CDH and may, for example, notify the customer that reading is not possible.

[0141] If the hold release transition code screen is displayed, the customer should go to the service counter and show the hold release transition code screen to the staff member. A transaction information management device 80 is installed at the service counter. The transaction information management device 80 is capable of performing processing corresponding to the release of a hold. In this case, the transaction information management device 80 is equipped with a code scanner. Note that the employee terminal installed at the service counter, for example, that is capable of performing processing corresponding to the release of a hold is not limited to the transaction information management device 80, but may also be a POS register or the like. The store clerk performs an operation to have the transaction information management device 80 read the hold release transition code CDH displayed on the hold release transition code screen presented by the customer. The transaction information management device 80 is capable of accepting the reading of the hold release transition code CDH. In other words, the transaction information management device 80 refers to the read control information indicated in the hold release transition code CDH, recognizes that it is a code that it can read, and performs the reading of the hold release transition code CDH. The transaction information management device 80 obtains the cart identification information indicated by the read hold release transition code CDH. The transaction information management device 80 obtains the cart information indicated by the cart identification information from the transaction management device 60. The transaction information management device 80 uses the acquired cart information to display a hold release processing screen. The hold release processing screen displayed by the transaction information management device 80 may be similar in form to, for example, the hold release processing screen displayed by the settlement device 40 in the first embodiment. The store clerk releases the hold status for each held item by operating on the hold release processing screen.

[0142] By releasing the hold status for all pending items included in the registered products, the products registered in the customer's transaction will no longer include pending items, and will be ready for settlement. The customer then operates the settlement transition instruction button BT41 displayed on the hold release transition code screen. In response to the operation of the settlement transition instruction button BT41, the customer terminal device 50 displays a settlement transition code screen similar to that shown in Figure 11(D). The customer then proceeds to the settlement device 40 and has the settlement device 40 read the settlement transition code CDP to complete the settlement.

[0143] By releasing the hold in this manner, it is possible to prevent the settlement device 40 from performing the hold release operation. In this case, the store will only become aware of the product registration details after the customer declares the completion of product registration by performing the settlement transition instruction operation. Therefore, customers will be more psychologically receptive to the store knowing the details of their product registration.

[0144] Furthermore, once the transaction information management device 80 has released the hold status of all held items, it may be configured to allow settlement processing to proceed according to the store clerk's instructions. The transaction information management device 80 may be equipped with a card reader that supports card media such as credit cards, cash cards, prepaid cards, and transportation cards. This enables the transaction information management device 80 to perform settlement processing corresponding to card media. In addition, by equipping the transaction information management device 80 with a change dispenser, settlement processing corresponding to cash payments can be performed.

[0145] Furthermore, depending on the time of day in the store and the operating status of the payment device 40, it may be permitted to release the hold at the payment device 40. For example, during times when there are fewer staff members on duty, such as early mornings or late nights, there are often no staff members at the service counter. Also, during early mornings and late nights, there are fewer customers. In this case, even if a staff member releases the hold at the payment device 40, it is unlikely to increase the waiting time for customers waiting in line to pay. Therefore, during times when there are fewer staff members and customers, such as early mornings or late nights, it may be possible to release the hold at the payment device 40. In this case, for example, the payment device 40 may disable the read control information included in the hold release transition code CDH during the relevant time period and process it as a normal payment transition code CDP. Furthermore, even if a store employee is performing a hold release operation on one of the payment devices 40 installed in the store, if the number of operational payment devices 40 exceeds a certain level, it is unlikely that the waiting time for customers waiting in line to pay will increase. Therefore, if the number of operational payment devices 40 exceeds a certain level, it may be possible to release the hold at the payment device 40.

[0146] Referring to the flowchart in Figure 15, an example of the processing procedure that the customer terminal device 50 of this embodiment executes upon completion of product registration will be described.

[0147] Step S101: Once the customer has completed product registration using the customer terminal device 50, they perform a payment transition instruction operation. The payment transition instruction operation is an operation on the "Proceed to Checkout" button on the product registration screen shown in Figure 11(B), etc. The customer terminal device 50, which is in the process of product registration, waits for the customer to perform the operation on the "Proceed to Checkout" button as a payment transition instruction operation.

[0148] Step S102: When the settlement transition instruction operation is performed, the customer terminal device 50 determines whether or not there are any pending items among the items registered up to that point for that transaction.

[0149] Step S103: If it is determined in step S102 that there are no items on hold, the customer terminal device 50 generates a settlement transition code screen as illustrated in Figure 11(D), and displays the generated settlement transition code screen on the display unit 504.

[0150] Step S104: If it is determined in step S103 that there are items on hold, the customer terminal device 50 generates a hold release code screen as illustrated in Figure 14 and displays the generated hold release code screen on the display unit 504.

[0151] In the above explanation, the example given was that the transaction information management device 80 of the service counter is capable of reading the hold release transition code CDH on the hold release transition code screen. Accordingly, the hold release transition code screen in Figure 14 displayed a message instructing the customer to go to the service counter. However, in addition to the transaction information management device 80, or in place of the transaction information management device 80, a mobile terminal for store employees, such as a tablet held by a store employee, may be used as a store employee terminal capable of releasing the hold. In this case, the hold release transition code screen may display a message instructing the customer to speak to a store employee if they see one in the store in order to release their hold. The customer can, for example, speak to the nearest store employee and show them the hold release transition code screen. The employee can then have the hold release transition code CDH on the hold release transition code screen read by their mobile terminal, which will display the hold release processing screen, allowing them to release the hold.

[0152] <Third Embodiment> Next, a third embodiment will be described. In the first embodiment, the hold release code screen displayed the hold release transition code CDH. The hold release transition code CDH could be read by the employee terminal, allowing the employee terminal to proceed with the hold release process, but it was a code that could not be read by the payment device 40.

[0153] In contrast, in the hold release transition code screen of this embodiment, the settlement transition prohibition control code is displayed instead of the hold release transition code CDH. The checkout transition prohibition control code includes cart identification information and a checkout transition prohibition flag. The checkout transition prohibition control code may be a two-dimensional code or a barcode, similar to the hold release transition code CDH. On the screen displaying the hold release transition code, which shows the control code to prevent transition to settlement, a message may be displayed instructing the customer to go to the settlement device 40 and have the control code to prevent transition to settlement read.

[0154] In this embodiment, the customer goes to the payment device 40 and performs an operation to cause the payment device 40 to read the payment transition prohibition control code. Upon reading the payment transition prohibition control code, the payment device 40 first recognizes that the payment transition prohibition flag is included in the read payment transition prohibition control code. If the payment transition prohibition flag is detected, the payment device 40 displays a message to the customer informing them, for example, that payment cannot be made at this time because the registered items include items on hold, and instructing them to go to the service counter and have a store employee release the hold.

[0155] The customer goes to the service counter and presents the hold release transfer code screen, which displays the settlement transfer prohibition control code, to the store clerk. The store clerk uses the code scanner installed in the transaction information management device 80 to read the settlement transfer prohibition control code displayed on the presented hold release transfer code screen.

[0156] In this embodiment, the transaction information management device 80 is configured to interpret the settlement transition prohibition control code as a hold release instruction. In other words, the transaction information management device 80 disables the settlement transition prohibition flag included in the settlement transition prohibition control code it reads. Then, the transaction information management device 80 obtains cart information from the transaction management device 60 that is associated with the cart information identification information indicated by the settlement transition code CDP included in the same settlement transition prohibition control code. The transaction information management device 80 uses the obtained cart information to display a hold release processing screen. The store clerk performs an operation to release the hold status for each held item by operating on the displayed hold release processing screen.

[0157] As described above, the store clerk's operation releases the hold status of all held items included in the registered product, making it possible to pay. The customer, as in the second embodiment, operates the payment transition instruction button BT41 on the hold release transition code screen to display the payment transition code screen similar to Figure 11(D). The customer then goes to the payment device 40 and has the payment device 40 read the payment transition code CDP to proceed with the payment. In this embodiment as well, once the transaction information management device 80 has completed releasing the hold status of all held items, it may be possible to continue processing the settlement in response to the store clerk's operation. In this embodiment as well, the employee's mobile terminal may be used as an employee terminal capable of releasing hold orders.

[0158] Furthermore, as a modification of this embodiment, the settlement device 40 may, upon reading the settlement transition prohibition control code, send a hold release permission notification to the transaction information management device 80 or to a staff terminal such as a staff member's mobile terminal.

[0159] The hold release permission notification is a notification that authorizes the employee's terminal to perform the hold release process. The hold release permission notification includes the cart identification information contained in the payment transition prohibition control code read by the payment device 40.

[0160] For example, when a store employee terminal receives a notice of permission to release a hold, it will display a list of transaction statuses showing the status of each transaction in the current store, and will indicate that the list item of the transaction indicated by the cart identification information included in the received notice of permission to release a hold can be released in a predetermined display manner.

[0161] When a store employee receives a request from a customer to release a hold, they verify that a transaction in a list item that indicates it is possible to release the hold matches the transaction the customer is dealing with. Then, the employee selects the list item that indicates it is possible to release the hold, which displays the hold release screen for the corresponding transaction on the employee terminal, and they proceed with the hold release operation. In this case, the employee does not need to have the employee terminal read the settlement transition prohibition control code.

[0162] <Fourth Embodiment> Next, a fourth embodiment will be described. In this embodiment, the hold release transition code screen does not include the display of codes such as the settlement transition code CDP or the hold release transition code CDH, and instead displays a message instructing the customer to go to the service counter or speak to a store employee to release the hold. Furthermore, the customer terminal device 50 of this embodiment displays the above-mentioned hold release transition code screen and generates a hold release permission notification, and transmits the generated hold release permission notification to a store employee terminal (transaction information management device 80, store employee mobile terminal, etc.) via, for example, the transaction information management device 80. From this point forward, similar to the modification of the third embodiment, a store employee who receives a request from a customer to release the hold can release the hold by operating the employee terminal.

[0163] <Fifth Embodiment> Next, a fifth embodiment will be described. In the hold release transition code screen of this embodiment, instead of displaying codes such as the settlement transition code CDP and the hold release transition code CDH, a button for calling a store employee to release the hold (employee call button) is displayed. Such a hold release transition code screen may display a message to the customer instructing them to operate the employee call button to have an employee release the hold. In this case, a message may also be displayed instructing the customer to move to a designated location other than the settlement device 40 in the store before operating the employee call button. Displaying such a message makes it easier for the employee who receives the call to find the customer who operated the employee call button.

[0164] In response to a customer pressing the staff call button, the customer terminal device 50 sends a hold release permission notification to the staff terminal, for example, via the transaction management device 60. In this embodiment, upon receiving the hold release permission notification, the customer terminal device 50 may display a message to the staff instructing them to go to the customer who pressed the staff call button to release the hold. Alternatively, instructions may be given to the staff via in-store announcements or other means in response to the operation of the staff call button. For example, if the above message is displayed on the staff terminal (e.g., staff mobile terminal) that the staff member is carrying, the staff member will be instructed to go to the customer with their mobile terminal. The hold release permission notification in this modified version includes cart identification information indicating the transaction to be released from hold. The employee terminal that receives the hold release permission notification may, for example, similar to the third embodiment, indicate in the transaction status list display that the hold release process is possible for the list item of the transaction (the transaction to be released from hold) indicated by the cart identification information included in the received hold release permission notification, in a predetermined display manner. The employee can then display the hold release processing screen for the transaction to be released from hold on their employee mobile terminal and perform the hold release operation.

[0165] <Sixth Embodiment> Next, the sixth embodiment will be described. In this embodiment, the hold release transition code screen displays a message to the customer instructing them to have a store employee release the hold, along with the settlement transition code CDP. Such a hold release transition code screen can be easily generated, for example, by displaying the above message on a settlement transition code screen where a settlement transition code CDP is placed, as shown in Figure 11(D).

[0166] In this case, the customer follows the message displayed on the hold release transition code screen and, for example, goes to the service counter or speaks to the nearest store employee to request that the hold be released. If a customer has the payment transition code CDP displayed on the hold release transition code screen read by the payment device 40, the payment device 40 will accept the reading of the payment transition code CDP and be able to obtain the cart information indicated by the read payment transition code CDP. However, in this case, a payment screen similar to the one shown in Figure 13 will be displayed. In this case, the customer cannot immediately make a payment using the payment device 40, and must first have a store employee operate the payment device 40 to release the hold. Typically, in this embodiment, the customer will follow the message displayed on the hold release transition code screen and request the store employee to release the hold. Alternatively, when a customer has the settlement device 40 read the settlement transition code CDP displayed on the hold release transition code screen, and the settlement device 40 transmits cart identification information to the transaction management device 60, the transaction management device 60 may determine whether the received cart identification information includes information indicating the registration of a hold item. If the cart identification information includes information indicating a hold item, the transaction management device 60 may not transmit the cart information to the settlement device 40, but instead send an error notification to the settlement device 40 indicating that settlement is not possible due to the registration of a hold item. Upon receiving the error notification, the settlement device 40 may display a message to the customer informing them that settlement is not possible due to a hold item and that they should ask a store employee to release the hold item.

[0167] When a store employee is asked to release a hold, they ask the customer to show them the hold release transition code screen, and then have the employee scan the settlement transition code CDP on the displayed hold release transition code screen using their own terminal. The employee terminal in this embodiment is capable of reading the settlement transition code CDP in response to the hold release process. Upon reading the settlement transition code CDP, the employee terminal obtains cart information associated with the cart identification information indicated by the settlement transition code CDP from the transaction management device 60. The employee terminal uses the obtained cart information to display the hold item processing screen. The employee operates the hold item processing screen to release the hold. In this embodiment as well, once the hold status of all held items has been released from the store clerk's terminal, the store clerk may then be able to proceed with the payment process according to their instructions.

[0168] As a modification of this embodiment, in accordance with the fifth embodiment, the hold release transition code screen may display a staff call button along with the settlement transition code CDP.

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

[0170] [First variation] Pharmaceuticals are included among the reserved items. As an example of this modification, for pharmaceuticals, the customer performs an operation to have the customer terminal device 50 read the product code, and then the customer terminal device 50 obtains, for example, the employee identification information of a pharmacist-qualified employee in charge of the sales area where the pharmaceuticals are displayed. The acquisition of employee identification information may be performed, for example, by having the customer terminal device 50 read the employee code attached to the employee ID card held by an employee who is a pharmacist, or the customer terminal device 50 may be configured to receive the information from the RFID tag on the employee ID card. The customer terminal device 50 transmits the product code of the pharmaceutical product, which is associated with the employee identification information of a pharmacist-qualified employee, to the transaction management device 60. The transaction management device 60 may register the product in the cart information as an item that has already been released from hold if the product code of the pharmaceutical product is associated with the employee identification information of a pharmacist-qualified employee.

[0171] Furthermore, currently, particularly Category 1 pharmaceuticals, they are displayed in specific locations that can only be accessed by store employees. Customers must request the desired medication from an employee, who then hands it over to them. In other words, for Category 1 pharmaceuticals, customers are limited to receiving them from store employees who are licensed pharmacists. Similar treatment may also apply to Category 2 and Category 3 pharmaceuticals.

[0172] Therefore, if pharmaceuticals are handed over to customers by a pharmacist-qualified employee at a specific location as described above, the store may register identification information (location-based identification information) corresponding to the location where the pharmaceuticals are sold, in association with the product code that the customer has read into the customer terminal device 50 as an item to be purchased. In this case, once the location-based identification information is associated with the product code of the pharmaceuticals, the store may treat it as if the pharmacist-qualified employee has explained the product and handed it over to the customer, and the hold has been released. Such location-based identification information may include, for example, employee identification information of a pharmacist-qualified employee in charge of the sales area where pharmaceuticals are displayed, or case identification information attached to the display cases of pharmaceuticals. The customer has the customer terminal device 50 read the product code of the medicine handed to them by the store clerk, and also has the customer terminal device 50 acquire store clerk identification information and case identification information as location-corresponding identification information. Store clerk identification information may be acquired by having the customer terminal device 50 read the store clerk code attached to the store clerk ID card held by the store clerk who is a pharmacist. Case identification information may be acquired by having the customer terminal device 50 read the case identification information provided on the case.

[0173] Furthermore, the same configuration as described in this modified example may be applied to valuables such as precious metals and watches.

[0174] [Second variation] In each of the embodiments described above, it is assumed that the customer using the shopping application is a registered member of the store. However, for example, to promote the use of the shopping application, it may be possible to register products for the first transaction without registering as a member. In such cases, if a customer who is not a registered member completes product registration using the shopping application in their first transaction, the customer terminal device 50 may, for example, display a screen instructing the customer to go to the service counter or call a nearby store employee before payment, instead of a payment transition code screen or a hold release transition code screen, to have a store employee complete the membership registration procedure. Furthermore, stores may conduct campaigns such as giving a commemorative gift to customers who have completed member registration and are using the shopping application for the first time. In this case, once the customer has completed product registration using the shopping application for the first time, the customer terminal device 50 may display a screen instructing the customer to go to the service counter or call a nearby store employee to receive the commemorative gift, instead of the payment transfer code screen or the hold release transfer code screen.

[0175] [Third variation] For example, there may have been issues in the previous transaction, such as a discrepancy in the selling price of a product, the purchase of a recalled product, or forgetting to take change. The history of such issues is stored in the transaction management device 60. Therefore, when the customer completes product registration in accordance with the current use of the shopping application, if the transaction management device 60 determines, based on the history stored, that an issue occurred in the previous transaction, the customer terminal device 50 may display an issue notification screen instead of the settlement transition code screen or the hold release transition code screen. The issue notification screen may include instructions for the customer to go to the service counter or call a nearby store employee before settlement to have an employee address the issue in the previous transaction.

[0176] [Fourth variation] In addition, in the above embodiments and modified examples, some of the processing performed by the customer terminal device 50 and the transaction information management device 80 may be performed by a higher-level device such as a transaction management device 60 connected to the customer terminal device 50 and the transaction information management device 80 via communication. Also, in the above embodiments and modified examples, some of the processing performed by the settlement device 40 may be performed by a higher-level device such as a transaction management device 60 connected to the settlement device 40 via communication. 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 may be configured as a thin client-compatible server (e.g., a cloud server), and the customer terminal device 50 and the transaction information management device 80 may function as thin clients. In this case, the thin client terminals, such as the customer terminal device 50 and the transaction information management device 80, transmit information such as commands and captured images corresponding to operations performed on them to the transaction information management device 80. The transaction information management device 80 responds to the information received from the thin client terminals by performing processes such as product registration and determining whether there are any pending items in the shopping cart information, and may transmit image data or web page data as a screen reflecting the processing results to the thin client terminals. The customer terminal device 50 and the transaction information management device 80, acting as thin client terminals, display the transmitted image data or web page data using an image viewer or web browser.

[0177] <Summary of Embodiments> [Technical field] The present invention relates to a portable registration terminal, a product sales data processing system, a terminal for store employees, and a program. [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. 2020-067947 [Overview of the prefecture] [Problems the invention aims to solve] In a product sales data processing system where customers register products themselves using a portable registration terminal, there may be cases where the registration result indicates that the product registered by the portable registration terminal requires the intervention of a store employee. For transactions that include products requiring the intervention of a store employee (employee-assisted products), the system ensures that the store employee performs the prescribed processing corresponding to the employee-assisted product before proceeding to settlement. It is preferable that the processing corresponding to employee-assisted products is performed in a manner that does not interfere with the payment of other customers. This invention has been made in view of these circumstances, and aims to provide a product sales data processing system in which customers register products themselves using a portable registration terminal, so as to enable processing for products requiring staff intervention without interfering with the checkout process for other customers.

[0178] [Means for solving the problem] (1) As described above, one aspect of this embodiment is a portable registration terminal (e.g., customer terminal device 50) comprising: registration means for registering products; and information generation means for generating settlement transition information (e.g., a settlement transition code screen including a settlement transition code CDP) if the products registered by the registration means do not include products requiring staff intervention (e.g., products on hold) (e.g., step S103); and generating staff intervention transition information (e.g., a settlement transition code CDP, a hold release transition code CDH, a staff call button, a message to the customer, etc., displayed on the hold release transition code screen) (e.g., step S104) regarding the transition to staff intervention processing (e.g., hold release processing) if the products requiring staff intervention are included (e.g., step S104).

[0179] According to the above configuration, the customer terminal device 50 can display a settlement transition code screen showing the settlement transition code CDP if the products registered by the customer using the customer terminal device 50 include reserved products, and can display a reserved product release transition code screen if there are no reserved products. In this case, if a reserved product is present and a reserved product release process is required, the settlement device 40 can be made to read the settlement transition code CDP on the settlement transition code screen, and the process can be made to release the reserved product. This makes it possible to perform processing for items requiring staff intervention in a shopping system (product sales data processing system) where customers register products themselves using the customer terminal device 50, without interfering with the checkout process for other customers.

[0180] (2) One aspect of this embodiment is a portable registration terminal as described in (1), which includes an information output means for outputting the employee-mediated transition information generated by the information generation means to a predetermined employee terminal (for example, a transaction information management device 80, an employee's mobile terminal, etc.). In this case, the staff-assisted transition information includes the hold release transition code CDH, the settlement transition code CDP, and the hold release permission notification in response to the operation of the staff call button, etc., which are displayed on the hold release transition code screen.

[0181] According to the above configuration, the customer terminal device 50 can cause a different employee terminal, distinct from the payment device 40, to acquire employee-mediated transition information.

[0182] (3) One aspect of this embodiment is a portable registration terminal as described in (2), wherein the employee-mediated transition information output to the employee terminal is information that enables the employee terminal to execute the employee-mediated processing (for example, settlement transition code CDP, hold release transition code CDH).

[0183] According to the above configuration, a staff terminal, separate from the payment device 40, can acquire staff-intervention transition information and execute a hold release process.

[0184] (4) One aspect of this embodiment is a portable registration terminal according to any one of (1) to (3), wherein the information generation means generates information of a screen that allows operations to call a store employee (for example, a hold release transition code screen on which a store employee call button is located) as store employee-assisted transition information.

[0185] According to the above configuration, customers can have a staff member release their hold by operating the staff call button displayed on the customer terminal device 50.

[0186] (5) One aspect of this embodiment is a product sales data processing system comprising a portable registration terminal and a store employee terminal, wherein the portable registration terminal comprises registration means for registering products, and information generation means for generating settlement transition information if the products registered by the registration means do not include products requiring store employee intervention, and for generating store employee intervention transition information regarding the transition to store employee intervention if such products are included, and the store employee terminal comprises editing means for editing transaction information (e.g., cart information) that includes the products requiring store employee intervention as part of the store employee intervention process.

[0187] Editing transaction information here refers, as a specific example, to the processing of information that removes the pending status of a product shown in the shopping cart information and registers it as a successfully registered product. Operations corresponding to such editing of transaction information include operations that instruct the release of the pending status for age-verified products, pharmaceuticals, anti-theft tag products, etc., and operations that input product information to release the pending status of unspecified products.

[0188] According to the above configuration, it becomes possible to process reserved items using a staff terminal other than the payment device 40.

[0189] (6) One aspect of this embodiment is the product sales data processing system described in (5), wherein the employee terminal is equipped with settlement means capable of performing settlement processing using the transaction information edited by the editing means.

[0190] With the above configuration, it becomes possible to process held items using the employee's terminal, release the hold, and then proceed to execute the payment process using the same employee's terminal.

[0191] (7) One aspect of this embodiment is a terminal for store employees that, in response to the fact that the products registered by a portable registration terminal in a transaction include products requiring store employee intervention, edits transaction information containing the products requiring store employee intervention as part of the store employee intervention process.

[0192] (8) One aspect of this embodiment is a program that causes a computer as a portable registration terminal to function as a registration means for registering products, and as an information generation means for generating settlement transition information if the products registered by the registration means do not include products that require staff intervention, and for generating staff intervention transition information regarding the transition to staff intervention if such products do include such products.

[0193] (9) One aspect of this embodiment is a product sales data processing system comprising a portable registration terminal and a server (e.g., a transaction management device 60), wherein the server comprises registration means for registering products based on product identification information transmitted from the portable registration terminal, and information generation means for generating settlement transition information if the products registered by the registration means do not include products requiring staff intervention, and for generating staff intervention transition information regarding the transition to staff intervention if such products are included, and for outputting the generated settlement transition information or staff intervention transition information to the portable registration terminal.

[0194] Furthermore, programs for realizing the functions of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction information management 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, transaction information management 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]

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

Claims

1. The registration method for registering products, Information generation means that, if the products registered by the registration means do not include products requiring staff intervention, generates settlement transition information, and if such products requiring staff intervention are included, does not generate settlement transition information but generates staff intervention transition information. A display means that displays the employee-assisted transition information generated by the information generation means and an operator that is disabled until the employee-assisted processing performed by the employee terminal upon acquisition of the employee-assisted transition information is completed. A portable registration terminal equipped with [a specific feature / feature].

2. A product sales data processing system comprising a portable registration terminal and a terminal for store staff, The aforementioned portable registration terminal is The registration method for registering products, Information generation means that, if the products registered by the registration means do not include products requiring staff intervention, generates settlement transition information, and if such products requiring staff intervention are included, does not generate settlement transition information but generates staff intervention transition information. A display means that displays the employee-assisted transition information generated by the information generation means and the operator that is not operable, Equipped with, The aforementioned terminal for store staff is The staff intervention process, which is performed by acquiring the staff intervention transition information displayed on the display means, includes an editing means for editing transaction information that includes the product requiring staff intervention. The display means disables the operation of the control until the employee intervention process is completed. Product sales data processing system.

3. A product sales data processing system comprising a portable registration terminal, a server, and a terminal for store staff, The aforementioned server, A registration means for registering products based on product identification information transmitted from a portable registration terminal, Information generation means that, if the products registered by the registration means do not include products requiring staff intervention, generates settlement transition information, and if such products requiring staff intervention are included, does not generate settlement transition information but generates staff intervention transition information. A display means for displaying the employee-assisted transition information generated by the information generation means and an operator that is disabled until the employee-assisted processing performed by the employee terminal upon acquisition of the employee-assisted transition information is completed, on the portable registration terminal, A product sales data processing system equipped with the following features.

4. The computer of the portable registration terminal A means of registering products, If the products registered by the registration means do not include products requiring staff intervention, the information generation means generates settlement transition information; if such products requiring staff intervention are included, the information generation means does not generate settlement transition information but generates staff intervention transition information. A display means that displays the employee-assisted transition information generated by the information generation means and an operator that is disabled until the employee-assisted processing performed by the employee terminal upon acquisition of the employee-assisted transition information is completed. A program that makes it function as such.

5. A program for causing a first computer to function as the portable registration terminal and a second computer to function as the store clerk terminal in a product sales data processing system comprising a portable registration terminal and a store clerk terminal, The first computer, A means of registering products, If the products registered by the registration means do not include products requiring staff intervention, the information generation means generates settlement transition information; if such products requiring staff intervention are included, the information generation means does not generate settlement transition information but generates staff intervention transition information. A display means that displays the employee-assisted transition information generated by the information generation means and the operator that is not operable. To make it function as, The second computer described above, As the staff intervention process performed by acquiring the staff intervention transition information displayed by the display means, the staff intervention means is configured to function as an editing means for editing transaction information that includes the product requiring staff intervention. The display means disables the operation of the control until the employee intervention process is completed. program.

6. A program for causing a computer to function as the server in a product sales data processing system comprising a portable registration terminal, a server, and a terminal for store employees, The aforementioned computer, A registration means for registering products based on product identification information transmitted from a portable registration terminal. If the products registered by the registration means do not include products requiring staff intervention, the information generation means generates settlement transition information; if such products requiring staff intervention are included, the information generation means does not generate settlement transition information but generates staff intervention transition information. A display means that displays the employee-assisted transition information generated by the information generation means and an operator that is disabled until the employee-assisted processing performed by the employee terminal upon acquisition of the employee-assisted transition information is completed, on the portable registration terminal. A program that makes it function as such.

Images