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

The system integrates customer and clerk processes by using a portable registration terminal to generate appropriate transition information, ensuring smooth handling of staff-mediated products without interfering with other customers' transactions.

JP2024166336AActive Publication Date: 2024-11-28TERAOKA SEIKO CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024160080
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-09-17
Publication Date
2024-11-28
Estimated Expiration
2040-10-14

AI Technical Summary

Technical Problem

In product sales data processing systems where customers register products using portable terminals, transactions involving staff-mediated products require store clerk intervention, which can interfere with other customers' checkout processes.

Method used

A system that includes a portable registration terminal capable of generating checkout transition information if no staff intervention is needed and clerk intervention transition information if required, along with a clerk terminal for editing transaction information, ensuring seamless integration of customer and clerk processes without interference.

Benefits of technology

Enables efficient processing of staff-mediated products without disrupting other customers' checkout, allowing store clerks to intervene only when necessary, thus optimizing the checkout experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166336000001_ABST
    Figure 2024166336000001_ABST
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] 2. Description of the Related Art A system is known in which customers themselves register products using mobile terminals (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-067947 A Summary of the Invention [Problem to be solved by the invention]

[0004] In a product sales data processing system in which customers themselves use a portable registration terminal to register products, the registration result may indicate that a store clerk's intervention is required for a product registered by the portable registration terminal. For a transaction that includes a product that requires a store clerk's intervention (a store clerk-intervention product), the store clerk performs a predetermined process corresponding to the store clerk-intervention product before moving on to settlement. It is preferable that the process corresponding to the store clerk-intervention product is performed in a manner that does not interfere with the transaction of other customers.

[0005] The present invention has been made in consideration of the above circumstances, and aims to provide a product sales data processing system in which customers themselves register products using a portable registration terminal, whereby processing corresponding to products requiring clerk intervention is performed without interfering with the transaction progress of other customers. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a portable registration terminal that includes a registration means for registering products, and an information generation means for generating checkout transition information if the products registered by the registration means do not include a product requiring store clerk intervention that requires store clerk intervention, and for generating store clerk intervention transition information regarding a transition to store clerk intervention if the products requiring store clerk intervention are included.

[0007] Another aspect of the present invention is a store clerk terminal that is equipped with an editing means for editing transaction information including a store clerk-required product as a store clerk-mediated processing when the products registered by the portable registration terminal in response to a transaction include a store clerk-required product that requires store clerk-mediated processing.

[0008] Another aspect of the present invention is a program for causing a computer serving 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 store clerk intervention that require store clerk intervention, and for generating store clerk intervention transition information regarding the transition to store clerk intervention if the products requiring store clerk intervention are included.

[0009] Another aspect of the present invention is a product sales data processing system comprising a portable registration terminal and a server, the server comprising: a registration means for registering products based on product identification information transmitted from the portable registration terminal; and an information generation means for generating settlement transition information if the products registered by the registration means do not include a product requiring clerk intervention that requires clerk intervention, and for generating clerk intervention transition information regarding the transition to clerk intervention processing if the product requiring clerk intervention is included, and for causing the generated settlement transition information or clerk intervention transition information to be output on the portable registration terminal. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a shopping system in a first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of installation of a settlement device in the first embodiment. [Diagram 3] 1 is a diagram showing an example of the appearance of a settlement device in a first embodiment. FIG. [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a settlement device in the first embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device in the first embodiment. [Figure 6] 1 is a diagram illustrating an example of the configuration of a transaction management device in a first embodiment. [Figure 7] 1 is a diagram illustrating an example of the configuration of a transaction information management device in a first embodiment. [Figure 8] 3A to 3C are diagrams illustrating an example of customer information, store information, and cart information according to the first embodiment. [Figure 9] FIG. 11 is a diagram showing an example of a definition of a reserved product in the first embodiment. [Figure 10] A sequence diagram showing an example of processing procedures executed by a customer terminal device, a settlement device, and a transaction management device in the first embodiment in response to the accounting of one transaction in self-service operation. [Figure 11] FIG. 2 is a diagram showing an example of a screen of a shopping application in the first embodiment. [Figure 12] 4A to 4C are diagrams showing examples of a registered product presentation screen, a product registration screen, and a guide image in the first embodiment. [Figure 13] FIG. 2 is a diagram showing an example of a settlement screen in the first embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a call-on-hold transition code screen in the second embodiment. [Figure 15] 13 is a flowchart showing an example of a processing procedure executed by a customer terminal device in response to completion of product registration in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] The management device 10, settlement device 40, and transaction information management device 80 are installed in a store and are communicatively connected via a LAN 19 (which may be wired or wireless). The management device 10 is a business terminal used by store staff for store management and the like, and is capable of communicating with the transaction management device 60. The transaction information management device 80 may be installed, for example, at a service counter or in a back yard.

[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 capable of communicating with the transaction management device 60. Although four settlement devices 40 are illustrated in FIG. 1, the number of settlement devices 40 within one store is not particularly limited.

[0014] The customer terminal device 50 is operated by a customer (such as a shopper who is a member of the store, hereinafter also referred to simply as a customer). In addition to typical communication and imaging functions (camera), the customer terminal device 50 has a recognition function that scans the barcode attached to a product to read the product code, that is, recognizes the barcode attached to the product. Note that 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 an image captured by the imaging function (an image acquired as a through image).

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

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

[0017] The customer terminal device 50 also captures an image (e.g., releases the shutter) of the product (e.g., the peripheral portion with a barcode attached) and generates a captured image (image data). The customer terminal device 50 may capture an image by releasing the shutter in response to an operation by the customer who is the operator, but in this embodiment, it is preferable that the customer terminal device 50 captures an image by releasing the shutter at its own discretion.

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

[0019] The settlement device 40 is a settlement device capable of at least cash payment as a settlement method. The settlement device 40 is configured to be able to communicate with the transaction management device 60. The settlement device 40 may be configured to be able to communicate with the transaction management device 60, for example, via the management device 10.

[0020] The transaction management device 60 manages transactions 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 a credit card payment request transmitted from the settlement device 40, the customer terminal device 50, etc.

[0022] [About the payment device] Fig. 2 is a diagram showing an example of the installation of the settlement device 40. Fig. 2(A) is a perspective view of the settlement device 40 etc. as seen from the customer side. Fig. 2(B) is a perspective view of the settlement device 40 etc. as seen from the store clerk side. As shown in Fig. 2(A), a counter is placed on the right side of the settlement device 40 as seen from the customer side.

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

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

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

[0026] The RAM 403 is a read / write memory and stores various information, such as information read from the ROM 402 or the storage unit 404, information acquired from the outside, and information generated during processing.

[0027] The storage unit 404 stores various information. For example, the storage unit 404 may store a program executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the storage unit 404 may store information read from the ROM 402, information acquired from the outside, information generated in processing, etc. The storage unit 404 may be configured to include, for example, a hard disk drive (HDD), a solid state drive (SSD), 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. Customer-side scanner unit 406 is a scanner unit for customers, and for example, scans a code (for example, a code other than a barcode, such as a barcode or a two-dimensional code) attached to a product and reads the product code. Customer-side scanner unit 406 may also scan a code (barcode, two-dimensional code, etc.) printed on a bill (registered trademark) and read information required for settlement. Customer-side scanner unit 406 may also scan a code (two-dimensional code, barcode, etc.) displayed on the display unit of customer terminal device 50 and read information required for settlement.

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

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

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

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

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

[0034] The store clerk's display unit 410 is a touch display for the store clerk, which displays various information to the store clerk and receives various inputs from the store clerk. The key operation unit 411 is made up of various keys (buttons) and receives various inputs from the store clerk. The store clerk scanner unit 412 is a scanner unit for store clerks, and for example, scans a barcode attached to a product and reads the product code. The store clerk scanner unit 412 also scans a barcode attached to the name tag of the store clerk and reads the store clerk code.

[0035] Although the store clerk's scanner unit 412 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper) is arranged on the key operation unit 411, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 410, the store clerk may operate that preset key to register the product.

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

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

[0038] In addition, the settlement device 40 of this embodiment can be switched between a total of four operating modes: a customer terminal-responsive settlement mode, which is set to perform settlement processing under customer terminal-responsive accounting, and three accounting modes (first to third accounting modes) corresponding to three different patterns of accounting (product registration, settlement). The first payment mode is an operating mode in which the store clerk performs operations on the payment device 40 corresponding to product registration and operations corresponding to payment. The second payment mode is an operating mode in which the store clerk performs operations on the payment device 40 corresponding to product registration, and the customer performs operations on the same payment device 40 corresponding to payment. The third payment mode is an operating mode in which the customer performs operations on the payment device 40 corresponding to product registration and operations corresponding to payment. As a result, in a store that has introduced the shopping system of this embodiment, some of the multiple payment devices 40 can be set to customer terminal compatible payment mode to support customer terminal compatible payment, and the other payment devices 40 can be set to, for example, the first or second payment mode so that a store clerk can handle payments in consultation with customers. Note that the other payment devices 40 may also include those set to the third payment mode. Such mode switching may be performed, for example, according to a predetermined time period during the opening hours of the store. In addition, the settlement device 40 of this embodiment may be configured as a dedicated device specialized for the above-mentioned customer terminal compatible settlement mode.

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

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

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

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

[0043] [Information stored in the transaction management device] The customer information stored in the memory unit 602 is information for managing individual customers. The transaction management device 60 generates customer information when a customer is registered (a customer's registration may be considered to have been completed when the customer information of that customer is stored). The transaction management device 60 also updates the customer information as appropriate based on cart information, etc. The transaction management device 60 may update the customer information, for example, by referring to the cart information at a specified time every day.

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

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

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

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

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

[0049] Cart information is information for managing individual transactions. The transaction management device 60 generates the cart information at the start of a transaction. In addition, the transaction management device 60 updates the cart information as the transaction progresses (each time a product is registered) (the storage of a product in the cart information may be interpreted as the registration of that product).

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

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

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

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

[0054] The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management device 60 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a basis for determining whether or not a service such as a time service should be applied and the effect of the application.

[0055] The reserved product information (total) is updated each time a reserved product is registered. A reserved product is a product that was not registered properly due to a certain reason and is registered in a temporarily reserved state. The reserved product information (total) includes the number of reserved products (number of products), the number of non-file reserved products, the number of unreadable reserved products (requiring confirmation of unauthorized operation), and the like.

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

[0057] A read NG is when a product code scan at a store fails (when the product code cannot be read), or is one aspect of a case where a product code scan at a store fails. In other words, a read NG refers to a timeout process when it is possible to determine that a product has been imaged for a certain period of time using image recognition technology but has not been recognized as a barcode, or an event where a timeout process has been performed. For example, if the barcode cannot be correctly acquired (recognized) despite the customer performing an operation to have the barcode read due to wrinkles in the package, smudges or dirt on the barcode print, or the barcode being printed on a transparent film, it will be determined that the barcode cannot be read.

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

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

[0060] 9 shows an example of reserved product definition corresponding to cart information in this embodiment. In the figure, an example is shown in which reserved products are classified into eight categories. Classification numbers "1" to "8" are assigned to each of the eight reserved product classifications. The classification of the reserved product with classification number 1 is “NON-FILE” as explained in FIG.

[0061] The classification of the reserved product with classification number 2 is “reading not allowed” as explained in FIG. The customer terminal device 50 determines that a reading NG has occurred when, in the image captured by the imaging unit 506, it is recognized that the entire barcode of the product has been captured, but the reading of the barcode is not completed successfully (successful) after a certain period of time has elapsed.

[0062] The classification of the reserved product with classification number 3 is "pseudo scan input." A reserved product with "pseudo scan input" is a product for which the customer has attempted to have the customer terminal device 50 read the product's code, but the customer terminal device 50 has not been able to read the code properly.

[0063] The "pseudo scan input" corresponds to a situation where the product is brought into the imaging range of the imaging unit 506, but the product code is not brought into the imaging range of the imaging unit 506. Additionally, a "pseudo scan insertion" situation corresponds to a situation in which the product is brought into the imaging range of the imaging unit 506, but an image of a part that does not have a code is captured. Additionally, "pseudo scan insertion" refers to a situation in which a product is brought into the imaging range of imaging unit 506 with the code portion hidden by a finger or the like. In addition, a "pseudo scan input" situation occurs when the code on a product is captured by the imaging unit 506, but the product is passed through the imaging range of the imaging unit 506 at a speed that prevents the customer terminal device 50 from reading the code.

[0064] Specifically, for example, the customer terminal device 50 determines that a pseudo scan has occurred when a product is recognized in a captured image, but the barcode cannot be recognized at all and therefore reading of the barcode is not completed normally. Alternatively, the customer terminal device 50 may also determine that a pseudo scan has occurred if reading of the barcode of a product is not completed normally because only a portion of the barcode of the product can be recognized in the captured image. Alternatively, the customer terminal device 50 may determine that a pseudo scan has occurred if the barcode of a product is recognized in the captured image, but the barcode reading is not completed successfully because the product is moving too quickly. When such false scans occur, it is possible that fraud is taking place, with customers simply pretending to have the barcode of a product scanned, but actually placing the item in their shopping cart.

[0065] The classification of the reserved product with classification number 4 is “non-scan-inserted.” A reserved product with the “non-scan-inserted” classification is a product that was added to the shopping cart without performing an operation to position the product within the imaging range of imaging unit 506. This non-scan insertion may occur, for example, when the customer terminal device 50 is fixedly attached to a shopping cart and is configured to be able to capture an image of the inside of a shopping basket placed in the shopping cart. For example, when the customer terminal device 50 determines based on the captured image that a product has been placed in the shopping cart even though the product's code has not been scanned, it can determine that a non-scan insertion has occurred.

[0066] Specifically, for example, when the customer terminal device 50 is set in a shopping cart, it can capture an image of the contents of the shopping basket placed in the shopping cart. The customer terminal device 50 determines that a non-scan input has occurred when it detects that a new product has been added to the shopping basket, even if no attempt to read the barcode of the product is recognized in the captured image. For example, a customer may move an already registered product within the shopping cart in order to organize the contents of the shopping cart. The customer terminal device 50 may be configured to distinguish between such a movement of a product and the additional insertion of a new product corresponding to a non-scan insertion based on the captured image. Such non-scan insertion may indicate fraud, such as a customer simply putting an item into the shopping cart without having the customer terminal device 50 read the product's bar code.

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

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

[0069] The classification of reserved items with classification number 7 is "anti-theft tag items." "Anti-theft tag items" are items that have anti-theft tags attached and require a store clerk to remove the anti-theft tag from the item when it is sold.

[0070] The classification of the reserved product with classification number 8 is a "cancelled product." A "cancelled product" is a product that was once registered but was cancelled by a customer's cancellation operation on the customer terminal device 50. A "cancelled product" is taken from the customer by a store clerk at the time of payment, for example.

[0071] The product master is stored, for example, in the management device 10. The product master stores product information for each product sold in the store. The product information for one product includes a number of predetermined information items, including a product code and a product name. Transaction management device 60 stores the product master data acquired from management device 10. Transaction management device 60 uses the stored product master data for processes related to product registration, etc.

[0072] For reserved items that fall under "NON-FILE" in classification number 1, the product code was obtained by code scanning in response to the product registration operation, but the product information associated with the obtained product code was not registered in the product master. Therefore, it has not been determined which of the products registered in the product master the reserved items that fall under "NON-FILE" in classification number 1 are. For pending products that fall into one of the three categories of classification numbers 2 to 4, "Read NG", "Pseudo scan input", and "Non-scan input", the product code has failed to be acquired as a result of the code scan in response to the product registration operation. Therefore, it is not possible to identify which of the products registered in the product master the pending products that fall into one of the three categories of classification numbers 2 to 4, "Read NG", "Pseudo scan input", and "Non-scan input", are.

[0073] An unspecified product is a pending product that falls into any of the four categories of "NON-FILE", "Read NG", "Pseudo-scan input", and "Non-scan input" in the classification numbers 1 to 4 out of the classification numbers 1 to 7. An unspecified product is a product whose registration result is incomplete because, for example, it was not possible to identify which of the products registered in the product master it is (the corresponding product information was not identified). Unidentified products are further divided into code-acquired products, whose product codes have been acquired through product registration operations, such as classification number 1 "NON-FILE," and code-unacquired products, whose product codes have not been acquired through product registration operations, such as classification numbers 2 to 4 "Read NG," "Pseudo scan input," and "Non-scan input."

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

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

[0076] Step S1: The customer terminal device 50 acquires information for identifying a store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (the two-dimensional code may be output on a display screen, a medium on which the two-dimensional code is printed may be attached, etc.), and a customer who visits the store may scan (read) the two-dimensional code with the customer terminal device 50, thereby allowing the customer terminal device 50 to acquire the store identification information. When a customer who visits the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer who visits the store scans the two-dimensional code with the customer terminal device 50, the shopping application may be started, and a screen informing the customer that the transaction management device 60 is currently connected may be displayed as a start-up screen.

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

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

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

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

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

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

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

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

[0085] Step S5: The customer terminal device 50 scans the barcode attached to the product by the customer's operation, and reads the product code. In the figure, it is assumed that the barcode has been successfully scanned. Steps S5 to S9 are repeatedly executed every time the barcode attached to the product is scanned.

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

[0087] Step S6: The transaction management device 60 receives the product registration information (cart identification information and product code) from the customer terminal device 50 and identifies the cart information of the transaction from the cart identification information included in the received product registration information.

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

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

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

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

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

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

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

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

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

[0097] Step S14: The transaction management device 60, which has received the cart identification information and the sub-calculation output request information from the customer terminal device 50, identifies the cart information of the transaction from the cart identification information.

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

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

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

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

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

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

[0104] The settlement device 40 reads the settlement transition code CDP displayed on the display unit of the customer terminal device 50 and then requests the transaction management device 60 to calculate the subtotal amount (S13), but may not request the calculation of the subtotal amount for products other than the products scanned in the store (for example, products scanned in other stores). For example, the settlement device 40 refers to the store identification information of the store (it may store and refer to the store identification information of the store in its own settlement device 40, or may refer to the store identification information stored in another accessible device), and when it reads the settlement transition code CDP displayed on the display unit of 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. Then, the settlement device 40 may permit the request to calculate the subtotal amount if the store identification information included in the cart identification information includes the store identification information of the store, and may prohibit the request to calculate the subtotal amount if the store identification information does not include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payments for products that are registered at other stores, etc.).

[0105] When the settlement device 40 prohibits the request for the subtotal amount as described above, after reading the settlement transition code CDP, the settlement device 40 may display an error message (e.g., "Settlement cannot be completed because the transaction includes products not from the XX store") on the customer-side display unit 405. The settlement device 40 may also display the above message on the store clerk-side display unit 410 instead of or in addition to the message on the customer-side display unit 405.

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

[0107] In the shopping system of this embodiment, the customer terminal device 50 may transmit product registration information for all registered products at once upon completion of product registration for all products, rather than transmitting product registration information each time a product is registered as in FIG. 10.

[0108] [About the behavior of customer terminal devices when an unspecified product is registered] In FIG. 10, step S5 is a process corresponding to the case where the reading of the product code is successful and the product corresponding to the read product code is identified. However, when the customer terminal device 50 performs the product code reading process in response to step S5, the product registration result may indicate that the product has been registered as an unidentified product under any of classification numbers 1 to 4 in Figure 9 (unidentified result).

[0109] 12(B) shows, by way of a captured image of a product registration screen, an example corresponding to a case where the customer terminal device 50 has determined that an unidentified result has occurred as a pseudo scan of classification number 3. The figure shows the product registration screen displayed on the customer terminal device 50. The product registration screen in the figure shows a state in which a captured image is displayed of a customer attempting to have the customer terminal device 50 read the barcode of a product with the barcode portion covered by his or her finger. In addition, if the registration result corresponds to a reserved item, including an item that has become unidentified, a button may be displayed that allows the user to call a store clerk to have the reserved status of the reserved item released.

[0110] In such a case, the customer terminal device 50 obtains a processing result indicating that the presence of a barcode was recognized from the captured image, but the code could not be extracted from the barcode. Since such a processing result is included in 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 to the transaction management device 60 product registration information indicating that the product is an unspecified product for which a pseudo scan of classification number 3 has been performed.

[0111] Furthermore, when transmitting product registration information in response to the occurrence of an unidentified result as described above, the customer terminal device 50 transmits captured images corresponding to the generated unidentified result. The captured images to be transmitted may be extracted from the buffered captured images, for example, by buffering the captured images captured by the imaging unit 506 for a certain period of time in order to read the product code. Furthermore, the captured images to be transmitted may be, for example, a predetermined number of still images, or may be a moving image for a predetermined period of time in response to the occurrence of an unidentified result.

[0112] Furthermore, when the product to be registered is designated as an unspecified product due to the occurrence of an unspecified result as described above, the customer terminal device 50 treats the unspecified product as a reserved product. In this case, the customer terminal device 50 may, at the timing when it is determined that an unspecified result has occurred, display a guide image WD2 that marks the unspecified product as a reserved product and encourages the customer to place the product in a bag for reserved products, as shown in FIG. 12(C). Specifically, the guide image WD2 in the figure displays a message saying, "If you cannot scan the product, please place the product in a special bag." Note that the form of the guide image WD2 is not particularly limited. The guide image WD2 in the figure is displayed so as to be superimposed on the product registration screen. A confirmation button BT3 is arranged in the guide image WD2 in the figure. In this case, the guide image WD2 is erased in response to an operation on the confirmation button BT3. Alternatively, the guide image WD2 may be erased in response to a certain time having elapsed since the start of display. After the guide image WD2 is erased, the display may return to the product registration screen of FIG. 11(B) or FIG. 11(C), for example.

[0113] Unspecified products are treated as reserved products as described above. On the product registration screen, a registered product list is displayed as shown in FIG. 11(C), but for reserved products classified as unspecified products, list items do not need to be displayed in the registered product list. Reserved products that are not classified as unspecified products are displayed as list items in the registered product list. Note that unspecified products may also have list items displayed in the registered product list to indicate that they are unspecified products.

[0114] When the customer has finished registering all the products to be purchased, the customer performs a payment transition instruction operation and has the payment transition code CDP displayed on the customer terminal device 50 read by the payment device 40. Having read the payment transition code CDP, the payment device 40 requests the transaction management device 60 to calculate the subtotal amount, as shown as step S13 in Fig. 9. Here, in this embodiment, when requesting calculation of the subtotal amount, the payment device 40 requests payment information to be used in the payment process.

[0115] In response to a request for settlement information, the transaction management device 60 identifies the corresponding cart 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 a subtotal amount according to the registered products. In addition, among the registered product information included in the settlement information, the registered product information corresponding to the insufficiently registered product includes a captured image corresponding to the unidentified result. The transaction management device 60 transmits the generated settlement information to the settlement device 40. When the settlement device 40 receives the settlement information, it displays a settlement screen on the customer side display unit 405 that reflects the contents of the received settlement information.

[0116] FIG. 13 shows an example of a settlement screen displayed on the customer side display unit 405 of the settlement device 40. The checkout screen in the figure includes a registered product list area AR3, which displays a list of products registered by the customer terminal device 50.

[0117] In the following description, the product information (registered product information, reserved product information) corresponding to each product list item in the registered product list area AR3 may also be referred to as a record. Additionally, registered product information and reserved product information corresponding to classifications such as age verification products (classification number 5), medicines (classification number 6), and security tag products (classification number 7) are also referred to as product identification records, since the products are identified. Of the product identification records, registered product information is also referred to as normal registration records, since it corresponds to products that have been properly registered, not reserved products. Of the reserved product information, that which corresponds to unspecified products (classification numbers 1 to 4) is also referred to as unspecified records.

[0118] If the registered products include reserved products, the list items of the reserved products are given priority and arranged from the top of the left column in the registered product list area AR3. In other words, the list items of the reserved products are arranged in order from the top in the registered product list area AR3. In the example shown in the figure, five reserved products are included in the registered products, so a reserved product list area AR31 including list items of the five reserved products from the top left is formed in the registered product list area AR3. The list items in the reserved product list area AR31 are made to differ from the list items of other products, for example in terms of background color, etc.

[0119] In addition, in the reserved item list area AR31, first, list items corresponding to the reserved item identification records in which the item is identified are arranged in order, followed by list items corresponding to the unspecified items in which the item is not identified. In other words, in the reserved item list area AR31, the list items corresponding to the reserved item identification records in which the item is identified and list items corresponding to the unspecified items in which the item is not identified are arranged separately.

[0120] In the registered product list area AR3, list items corresponding to normal registration records are arranged following the pending product list area AR31. In the same figure, an example is shown in which the list items corresponding to normal registration records are arranged in the registered product list area AR3 in descending order of product price. Among the list items in the registered product list area AR3, the list item corresponding to the product specification record shows the product name, registered quantity, price according to the registered quantity, etc. of the specified product.

[0121] A Hold Release Declaration Button BT31 is located in the list item for each held item in the held item list area AR31. The Hold Release Declaration Button BT31 is a button that declares the release of the held item for the corresponding item. However, the Hold Release Declaration Button BT31 cannot be operated on the checkout screen in the figure, and can be operated on the hold release processing screen described below. On the checkout screen, the Hold Release Declaration Button BT31 functions as an icon that indicates that the corresponding list item corresponds to a held item.

[0122] The reserved item release declaration button BT31 indicates the name of the reserved item classification to which the corresponding item falls. Specifically, for example, for age verification products (classification number 5), medicines (classification number 6), security tag products (classification number 7), and canceled products (classification number 8), the name indicating the corresponding classification is displayed on the hold release declaration button BT31. Also, for unspecified products (classification numbers 1 to 4), the name "hold product" is displayed collectively. In the figure, the display of the hold release declaration button BT31 shows an example in which the list item on the first line is displayed as "age verification" since it is an age verification product (classification number 5), the list item on the second line is displayed as "security tag" since it is a security tag product (classification number 7), and the list item on the third line is displayed as "pharmaceuticals" since it is a pharmaceutical product (classification number 6). Also, the list items on the fourth and fifth lines are each displayed as "hold product". In the list items in the fourth and fifth rows, thumbnail images TN are arranged. The thumbnail images TN are images captured by the customer terminal device 50 when a product registration operation is being performed for the corresponding unspecified product. The thumbnail images TN may be still images or moving images. Depending on whether or not a thumbnail image TN is present, the store clerk can visually distinguish between list items corresponding to unspecified products and list items corresponding to specified reserved products. Also, the store clerk can understand what the product registered as an unspecified product actually was based on the content displayed in the thumbnail image TN. In addition, the display indicating the corresponding classification on the hold release declaration button BT31 may be a picture such as an icon indicating the classification.

[0123] Among the list items of reserved goods, in the list items corresponding to identified goods such as age verification goods (classification number 5), pharmaceuticals (classification number 6), security tag goods (classification number 7), etc., the product name, registered quantity, price according to the registered quantity, etc. of the identified goods are displayed. In contrast, in the list item corresponding to an unidentified product, content according to the classification of the corresponding reserved product is displayed. Specifically, in the case of an unidentified product classified as NON-FILE (classification number 1), the read product code may be displayed together with an indication that it is NON-FILE, as in the list item in the fifth line of the figure. In addition, in the case of unidentified products (products for which a code has not been obtained) that are NG for reading (classification number 2), pseudo-scan input (classification number 3), and non-scan input (classification number 4), a message may be displayed indicating that the product code could not be read, as in the list item in the fourth line of the figure.

[0124] As shown in the figure, when the pending item list area AR31 is formed in the registered item list area AR3 on the checkout screen, a store clerk needs to perform an operation to process the pending items. When the checkout screen with the pending item list area AR31 formed in this way is displayed, the checkout device 40 executes a store clerk call to have the store clerk perform an operation to process the pending items. To call a store clerk, the checkout device 40 may, for example, cause a display such as a sign pole to be displayed in a predetermined manner, or send a notice of a store clerk call to a terminal device carried or monitored by the store clerk. As shown in the figure, when the checkout screen in which the reserved item list area AR31 is formed is displayed because the reserved item is included in the registration result, the checkout device 40 does not accept any operations related to checkout by the customer. Also, for example, in the area above the registered item list area AR3 on the checkout screen in the figure, a message is displayed to inform the customer that a store clerk who has been called will come to the checkout device 40.

[0125] The store clerk who goes to the settlement device 40 in response to the store clerk call performs a login operation to log in to the settlement device 40 as a store clerk. The login operation in this case may be, for example, an operation of having a scanner unit (customer-side scanner unit 406 or store clerk-side scanner unit 412) read a store clerk code (which may be in the form of a two-dimensional code or a barcode) printed on the store clerk ID. Alternatively, it may be an operation of inputting a store clerk number or the like by, for example, entering a number.

[0126] When the store clerk logs in, the display on the customer side display unit 405 transitions from the checkout screen to a hold release processing screen (not shown). The store clerk performs operations on the hold release processing screen to release the hold status (hold release) of the held items corresponding to each list item of the held items displayed in the registered item list area AR3 on the checkout screen. The on-hold call release processing screen may be composed of multiple screens. In other words, when one on-hold call release processing screen is displayed, in response to an operation by a store clerk, the screen may transition to another on-hold call release processing screen that accepts a specific operation.

[0127] When a store clerk wishes to release a held item of a category for which the item can be identified (age verification items (classification number 5), medicines (classification number 6), security tag items (classification number 7), the clerk performs the prescribed response procedure according to each category and then performs a hold release declaration operation to release the held item in question. In response to the hold release declaration operation being performed, 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 is configured to manage the corresponding held item information as normal product information. This releases the held state of held items of a category for which the item can be identified.

[0128] Specifically, when the product to be released from the hold is an age verification product, the store clerk confirms that the customer is an adult as a customer service task and performs a hold release announcement operation. In addition, if the product to be released from hold is a medicine, the store clerk will, as a handling procedure, either explain the situation themselves if they are a licensed pharmacist, or have another store clerk who is a licensed pharmacist explain the situation before declaring the release of the hold. Furthermore, if the product to be released from the hold is a product with a security tag, the store clerk will, as a service of the store, remove the security tag attached to the product and perform the operation to declare the hold release.

[0129] In addition, when a store clerk releases a pending item classified as an unidentified item (NON-FILE (classification number 1), NG to read (classification number 2), pseudo-scan input (classification number 3), non-scan input (classification number 4)), the store clerk will determine, for example, what the pending item is from the actual item or the image captured at the time of registration that is displayed on the hold release processing screen. When the store clerk confirms what the subject held item is, the clerk performs an operation to input item information corresponding to the confirmed item on the hold release processing screen. The settlement device 40 transmits a hold release request including the input item information to the transaction management device 60. Upon receiving the hold release request, the transaction management device 60 uses the item information included in the received hold release request to manage the held item information for the held item classified as an unspecified item as normal item information. This releases the hold state for the held item classified as an unspecified item.

[0130] The store clerk can also cancel the reserved state by performing an operation to delete the registration of the reserved item. Furthermore, when the store clerk releases the reserved status of the reserved product and returns it to a normally registered status, the store clerk may perform an operation to input the purchase quantity as necessary.

[0131] When the release of the reserved state of all reserved items in one transaction is completed in this way, the settlement device 40 displays a settlement screen that does not include the reserved items. The customer can operate the settlement device 40 with the settlement screen displayed in this way to settle the payment.

[0132] 13 may be displayed on the clerk display unit 410, and the clerk may be able to perform operations related to payment on behalf of the customer. In addition, in response to a login operation by the clerk while the payment screen is displayed on the clerk display unit 410, the payment screen may be transitioned to a hold release processing screen. Furthermore, the clerk may be able to operate the hold release processing screen displayed on the clerk display unit 410.

[0133] <Second embodiment> Next, a second embodiment will be described. In the first embodiment, the process of canceling the hold is performed by having the settlement device 40 read the settlement transition code CDP displayed on the customer terminal device 50 after the customer has completed product registration, and then having the store clerk go to the settlement device 40 and perform the operation. However, in the above-mentioned procedure for releasing the hold, the store clerk must perform the operation to release the hold at the settlement device 40 where the customer would normally settle the payment. As a result, customers who are waiting in line to settle the payment behind a customer who is settling a transaction in which the registered products include a reserved product must wait the extra time it takes for the store clerk to perform the operation to release the hold. In other words, the progress of the payment for other customers is impeded. Note that "payment" here refers to the procedure including the registration of products in one transaction to the settlement of the registered products.

[0134] For example, in the shopping system of the present embodiment, when a customer registers a product using the customer terminal device 50 and the product is registered as a pending product, a notification may be sent to the store clerk terminal. The store clerk terminal may be, for example, the transaction information management device 80, the management device 10, or the like. The store clerk terminal may be a POS register or the like installed in a store and operated by a store clerk. It may also be a personal computer installed in the store. It may also be a store clerk mobile terminal such as a smartphone, tablet terminal, or handheld terminal carried by a store clerk. For example, in the case where the customer terminal device 50 is lent to a customer by the store in such a manner that it is fixedly attached to a shopping cart, the customer terminal device 50 may also be made to function as a store clerk terminal. In this case, the store clerk who receives the notification can immediately assist the customer and perform the operation to release the hold. This eliminates the need for the store clerk to perform the operation to release the hold at the settlement device 40. However, in this case, the store clerk will become aware of the occurrence of a held item before the customer has completed product registration, and will assist in releasing the hold. For example, some customers may not like their product registration status being known even when product registration has not been completed.

[0135] Therefore, in the shopping system of this embodiment, as described below, when a customer has completed product registration using the customer terminal device 50, a store clerk can respond by releasing the hold before the customer goes to the payment terminal 40.

[0136] As mentioned above, when the customer has completed the registration of all products to be purchased, the customer operates the "Proceed to Checkout" button located on the product registration screen displayed on the customer terminal device 50. In other words, the customer performs an operation to instruct the customer to proceed to checkout upon completion of product registration. Note that with regard to the "Proceed to Checkout" button, "checkout" is used synonymously with checkout. In this case, if the registered products do not include reserved products, the customer terminal device 50 displays a payment transition code screen with the payment transition code CDP arranged thereon, as shown in Fig. 11(D). In this case, the customer can go directly to the payment settlement device 40 and have the payment settlement device 40 read the payment transition code CDP to settle the payment.

[0137] On the other hand, if the registered products include a reserved product, the customer terminal device 50 displays a hold release transition code screen instead of the settlement transition code screen in response to a settlement transition instruction operation being performed.

[0138] FIG. 14 shows an example of the hold release transition code screen. The hold release transition code screen in the figure displays the hold release transition code CDH. In addition, since the registered products include a held product, the hold release transition code screen displays a message instructing the customer to go to the service counter and present the hold release transition code CDH to a store clerk. In addition, the hold release transition code screen displays a payment transition instruction button BT41. The payment transition instruction button BT41 is a button that is operated to transition to payment after the hold product is released. The settlement transition instruction button BT41 may be made inoperable until the pending state is resolved by completing the release of the hold, etc. If the settlement transition instruction button BT41 is operated even though the operation is inoperable, there is a possibility that the customer does not understand the current situation that requires the hold to be released. In such a case, a pop-up window or the like may be displayed to the customer informing them to go to the service counter to have the store clerk release the hold, so that the store clerk can accurately understand the current situation. Instead of the settlement transition instruction button BT41, for example, a button for calling a store clerk or a button for returning to the product registration screen may be provided.

[0139] The information of the hold release transition code CDH, like the settlement transition code CDP, includes cart identification information that indicates cart information that reflects the result of the customer's product registration. However, the information of the hold release transition code CDH includes read control information that allows the settlement device 40 to not accept (cannot read) the read, although the store clerk terminal can read it.

[0140] Therefore, even if a customer goes to the settlement device 40 and performs an operation to read the hold release transition code CDH on the hold release transition code screen displayed on the customer terminal device 50, the settlement device 40 will not accept the reading of the hold release transition code CDH and may, for example, notify the customer that it cannot be read.

[0141] When the on-hold release transition code screen is displayed, the customer goes to the service counter and presents the on-hold release transition code screen to the store clerk. A transaction information management device 80 is installed at the service counter. The transaction information management device 80 is capable of executing a process corresponding to the hold release. In this case, a code scanner is provided in the transaction information management device 80. Note that the store clerk terminal installed at the service counter, for example, and capable of executing a process corresponding to the hold release is not limited to the transaction information management device 80, and may be, for example, a POS register or the like. The store clerk performs an operation to have the transaction information management device 80 read the on-hold release transition code CDH displayed on the on-hold release transition code screen presented by the customer. The transaction information management device 80 is capable of accepting the reading of the on-hold release transition code CDH. In other words, the transaction information management device 80 refers to the read control information indicated in the on-hold release transition code CDH, recognizes that it is a code that it can read, and executes the reading of the on-hold release transition code CDH. The transaction information management device 80 acquires the cart identification information indicated in the read hold release transition code CDH. The transaction information management device 80 acquires 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 on the transaction information management device 80 may be, for example, similar to the hold release processing screen displayed on the settlement device 40 of the first embodiment. The store clerk releases the hold state for each held item by operating the hold release processing screen.

[0142] By releasing the reserved status for all reserved items included in the registered items, the reserved items are no longer included in the registered items in the customer's transaction, and settlement becomes possible. Then, the customer 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 Fig. 11(D). The customer goes to the settlement device 40 and has the settlement device 40 read the settlement transition code CDP to perform settlement.

[0143] By canceling 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 registered product details after the customer declares the completion of product registration by performing the settlement transition instruction operation. For this reason, customers will be more likely to psychologically accept that their registered product details will be known by the store.

[0144] In addition, once the transaction information management device 80 has completed the release of the reserved state of all reserved items, it may be possible to continue to perform settlement processing in response to an operation by a store clerk. The transaction information management device 80 may be provided with a card reader compatible with card media such as credit cards, cash cards, prepaid cards, and transportation cards. This allows the transaction information management device 80 to perform settlement processing compatible with card media. Furthermore, providing a change dispenser in the transaction information management device 80 allows settlement processing compatible with cash payments.

[0145] For example, the settlement device 40 may be allowed to release the hold depending on the time of day in the store and the operating status of the settlement device 40. For example, in times when there are few store staff, such as early morning or late night, there are often no store staff at the service counter. In addition, in times when there are few customers in the early morning or late night. In this case, even if a store staff member releases the hold at the settlement device 40, it is unlikely that the waiting time of customers waiting for payment will be long. Therefore, in times when there are few store staff and customers, such as early morning or late night, the settlement device 40 may be allowed to release the hold. In this case, for example, the settlement device 40 may be configured to invalidate the read control information included in the hold release transition code CDH during the relevant time period and to process it as a normal settlement transition code CDP. Furthermore, even if the number of operating settlement devices 40 among those installed in the store is equal to or greater than a certain number, a situation in which customers waiting their turn to pay are forced to wait for a long time is unlikely to occur even if a store clerk performs an operation to release a held payment at a certain settlement device 40. Therefore, when the number of operating settlement devices 40 is equal to or greater than a certain number, it may be possible to allow a held payment to be released at any settlement device 40.

[0146] An example of a process procedure executed by the customer terminal device 50 of this embodiment in response to completion of product registration will be described with reference to the flowchart of FIG.

[0147] Step S101: When the customer completes product registration using the customer terminal device 50, the customer performs a checkout instruction operation. The checkout instruction operation is an operation on the "Proceed to checkout" button on the product registration screen shown in Fig. 11(B) etc. During the product registration process, the customer terminal device 50 waits for the "Proceed to checkout" button to be operated as a checkout instruction operation.

[0148] Step S102: When a payment transition instruction operation is performed, the customer terminal device 50 judges whether or not there is a reserved product among the products registered so far in accordance with one transaction.

[0149] Step S103: If it is determined in step S102 that there are no reserved products, the customer terminal device 50 generates a payment transition code screen as exemplified in FIG. 11(D) and causes the display unit 504 to display the generated payment transition code screen.

[0150] Step S104: If it is determined in step S103 that there is a reserved product, the customer terminal device 50 generates a hold release code screen as exemplified in FIG.

[0151] In the above explanation, an example was given in which the transaction information management device 80 at the service counter was capable of reading the on-hold release transition code CDH on the on-hold release transition code screen. In response to this, a message was displayed on the on-hold release transition code screen in Fig. 14 instructing the customer to go to the service counter. However, in addition to or instead of the transaction information management device 80, a store clerk's portable terminal, such as a tablet carried by the store clerk, may be used as the store clerk terminal capable of performing the hold release process. In this case, the on-hold release transition code screen may display a message instructing the customer to call a store clerk in the store if they see one to release the call on hold. The customer, for example, calls out to the nearest store clerk and shows the on-hold release transition code screen. The store clerk can have the store clerk's mobile terminal read the on-hold release transition code CDH on the on-hold release transition code screen, display a on-hold release processing screen on the store clerk's mobile terminal, and perform the on-hold release operation.

[0152] <Third embodiment> Next, a third embodiment will be described. In the first embodiment, the on-hold release code screen displayed the on-hold release transition code CDH. The on-hold release transition code CDH is a code that can be read by the store clerk terminal so that the store clerk terminal can transition to the on-hold release process, but cannot be read by the settlement device 40.

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

[0154] In this embodiment, the customer goes to the settlement device 40 and performs an operation to have the settlement device 40 read the settlement transition prohibition control code. In response to reading the settlement transition prohibition control code, the settlement device 40 first recognizes that there is a settlement transition prohibition flag included in the read settlement transition prohibition control code. When the settlement device 40 recognizes that there is a settlement transfer prohibition flag, it notifies the customer that, for example, the registered items include reserved items and therefore settlement cannot be performed at the present stage, and displays a message instructing the customer to go to the service counter and have a store clerk release the reserved items.

[0155] The customer goes to the service counter and shows the hold release transition code screen on which the payment transition prohibition control code is displayed to the store clerk. The store clerk operates the code scanner provided in the transaction information management device 80 to read the payment transition prohibition control code displayed on the presented hold release transition code screen.

[0156] The transaction information management device 80 of this embodiment is adapted to interpret the checkout transition prohibition control code as a hold release instruction. In other words, the transaction information management device 80 disables the checkout transition prohibition flag included in the read checkout transition prohibition control code. Then, the transaction information management device 80 acquires cart information associated with the cart information identification information indicated by the checkout transition code CDP included in the same checkout transition prohibition control code 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 store clerk performs an operation on the displayed hold release processing screen to release the hold state for each held item.

[0157] As a result of the store clerk performing the above operation, the reserved state of all reserved items included in the registered items is released, and payment becomes possible. As in the second embodiment, the customer operates the payment transition instruction button BT41 on the hold release transition code screen to display a payment transition code screen similar to that shown in Fig. 11(D). The customer goes to the payment device 40 and has the payment device 40 read the payment transition code CDP to perform payment. In this embodiment as well, once the transaction information management device 80 has completed the release of the reserved status for all reserved items, the payment process may then be made possible in response to operations by the store clerk. In this embodiment, the store clerk mobile terminal may also be used as a store clerk terminal capable of canceling a call on hold.

[0158] In addition, as a modified example of this embodiment, the settlement device 40 may send a hold release permission notification to the transaction information management device 80 or a store clerk terminal such as a store clerk mobile terminal in response to reading the settlement transition prohibition control code.

[0159] The hold release permission notification is a notification that allows the store clerk terminal to execute the hold release process. The hold release permission notification includes the cart identification information that was included in the payment transition prohibition control code that the settlement device 40 read.

[0160] For example, when a store clerk terminal receives a hold release permission notification, it will display a transaction status list showing the current status of each transaction in the store, and will indicate in a predetermined display manner that hold release processing is possible for the list item of the transaction indicated by the cart identification information included in the received hold release permission notification.

[0161] When the clerk receives a request from the corresponding customer to release the hold, the clerk confirms that the transaction in the list item for which the hold release process is possible matches the transaction corresponding to the customer. Then, the clerk performs an operation to select the list item for which the hold release process is possible, displays a hold release process screen for the corresponding transaction on the clerk terminal, and performs an operation to release the hold. In this case, the clerk does not need to have the clerk terminal read the settlement transfer prohibition control code.

[0162] <Fourth embodiment> Next, a fourth embodiment will be described. The on-hold release transition code screen of this embodiment does not include the display of codes such as the settlement transition code CDP and the on-hold release transition code CDH, and displays a message to the customer to go to the service counter or to speak to a store clerk to release the on-hold call. Then, 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 clerk terminal (transaction information management device 80, clerk mobile terminal, etc.) via, for example, the transaction information management device 80. Thereafter, similarly to the modified example of the third embodiment, the store clerk who receives the request from the customer to release the held call can operate the store clerk terminal to release the held call.

[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 clerk to release the hold (a store clerk call button) is displayed. On such a hold release transition code screen, a message may be displayed for the customer to guide the customer to operate the store clerk call button to have the store clerk release the hold. In this case, a message may be displayed to guide the customer to move to a predetermined location other than the settlement device 40 in the store and then operate the store clerk call button. By displaying such a message, the store clerk who is called can easily find the customer who operated the store clerk call button.

[0164] In response to the customer operating the clerk call button, the customer terminal device 50 transmits a hold release permission notice to the clerk terminal via, for example, the transaction management device 60. In this embodiment, the customer terminal device 50 that receives the hold release permission notice may, for example, display a message to the clerk instructing the clerk to go to the customer who operated the clerk call button to release the hold. Also, in response to the operation of the clerk call button, instructions may be given to the clerk by an in-store announcement or the like. For example, when the above message is displayed on the clerk terminal (for example, a clerk mobile terminal) that the clerk carries with him / her, the clerk is made to go to the customer carrying the clerk mobile terminal. The hold release permission notice of this modified example includes cart identification information indicating the transaction to be released from hold. As in the third embodiment, the store clerk terminal that receives the hold release permission notice may indicate that the hold release process is possible in a predetermined display mode 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 notice in the transaction status list display. The store clerk can display the hold release process screen for the transaction to be released from hold on the store clerk mobile terminal and then perform the hold release operation.

[0165] Sixth embodiment Next, a sixth embodiment will be described. The on-hold release transition code screen of this embodiment displays, together with the settlement transition code CDP, a message to guide the customer to have a store clerk release the on-hold call. Such a hold release transition code screen can be easily generated by displaying the above message on a settlement transition code screen on which a settlement transition code CDP is placed, as shown in FIG. 11(D), for example.

[0166] In this case, the customer follows the message displayed on the on-hold release transition code screen and, for example, goes to a service counter or speaks to the nearest store clerk to request the call be released from on-hold. If the customer allows the settlement device 40 to read the settlement transition code CDP displayed on the hold release transition code screen, the settlement device 40 can accept the reading of the settlement transition code CDP and obtain the cart information indicated by the read settlement transition code CDP. In this case, however, a settlement screen similar to that shown in FIG. 13 is displayed. In this case, the customer cannot immediately settle the payment at the settlement device 40, and must first have a store clerk operate the settlement device 40 to release the hold. In the case of this embodiment, the customer usually takes action to request the store clerk to release the hold in accordance with the message displayed on the hold release transition code screen. Alternatively, when the settlement device 40 transmits cart identification information to the transaction management device 60 in response to the customer having the settlement device 40 read the settlement transition code CDP displayed on the hold release transition code screen, the transaction management device 60 may determine whether or not the received cart identification information includes reserved item information indicating the registration of a reserved item. If the cart identification information includes reserved item information, the transaction management device 60 may transmit an error notification to the settlement device 40 indicating that settlement is not possible due to the registration of a reserved item, without transmitting the cart information to the settlement device 40. The settlement device 40 that receives the error notification may display a message to the customer informing them that settlement is not possible due to the presence of a reserved item, and guiding them to have a store clerk release the hold.

[0167] The store clerk who is requested to release the call on hold has the customer present the on-hold release transition code screen, and has the store clerk read the settlement transition code CDP on the presented on-hold release transition code screen into the store clerk terminal that he or she uses. The clerk terminal of this embodiment is capable of reading the settlement transition code CDP in response to the hold release process. In response to reading the settlement transition code CDP, the clerk terminal acquires cart information associated with the cart identification information indicated by the settlement transition code CDP from the transaction management device 60. The clerk terminal uses the acquired cart information to display a held item processing screen. The clerk operates the held item processing screen to perform a hold release operation. In this embodiment as well, once the on-hold status of all reserved items has been released, the store clerk may be able to continue with the settlement process in response to an operation by the store clerk at the store clerk terminal.

[0168] As a modification of this embodiment, a store clerk call button may be displayed on the hold release transition code screen together with the settlement transition code CDP, in accordance with the fifth embodiment.

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

[0170] [First Modification] The reserved goods include medicines. In this modified example, for example, for medicines, the customer performs an operation to have the customer terminal device 50 read the product code, and then the customer terminal device 50 acquires, for example, the salesperson identification information of a salesperson with a pharmacist license who is in charge of the sales floor where the medicines are displayed. The store clerk identification information may be obtained, for example, by having the customer terminal device 50 read the store clerk code attached to the store clerk ID card held by a store clerk who is a qualified pharmacist, or the customer terminal device 50 may receive the information from the RFID tag on the store clerk ID card. The customer terminal device 50 transmits the product code of the medicine associated with the clerk identification information of the clerk who is a licensed pharmacist to the transaction management device 60. When the clerk identification information of the clerk who is a licensed pharmacist is associated with the product code of the medicine, the transaction management device 60 may register the product in the cart information as a product that has already been released from hold.

[0171] Currently, Category 1 medicines are displayed in specific locations where only store clerks can take them out, and customers are required to ask a store clerk for the medicine they want and have the clerk hand it over to them. In other words, there are limited locations where customers can pick up Category 1 medicines from store clerks who are qualified pharmacists. Category 2 and Category 3 medicines may also be treated in the same way.

[0172] Therefore, when a pharmaceutical product is handed over to a customer by a salesperson with a pharmacist license at a specific location as described above, the product code that the customer has read into the customer terminal device 50 as a purchase item may be registered in association with identification information (location-corresponding identification information) corresponding to the location (location) where the pharmaceutical product is sold. In this case, by associating the location-corresponding identification information with the pharmaceutical product code, the pharmaceutical product may be treated as having been handed over to the customer by a salesperson with a pharmacist license after explanation, and may be treated as having been released from hold. Such location-corresponding identification information may be, for example, clerk identification information of a clerk with a pharmacist's license who is in charge of the sales floor where the medicines are displayed, or case identification information attached to the case in which the medicines are displayed. The customer has the customer terminal device 50 read the product code of the medicine handed over by the clerk, and has the customer terminal device 50 acquire the clerk identification information and case identification information as location-corresponding identification information. The clerk identification information may be acquired by having the customer terminal device 50 read the clerk code attached to a clerk ID card held by a clerk who is a qualified pharmacist. The case identification information may be acquired by having the customer terminal device 50 read the case identification information provided on the case.

[0173] Note that a configuration similar to that of this modified example may also be applied to valuables such as precious metals and watches.

[0174] [Second modified example] In each of the above embodiments, it is assumed that a customer using the shopping application is a person who has registered as a member of the store. However, for example, in order to popularize the shopping application, it may be possible to register a product for the first transaction without registering as a member. In this way, when a customer who is not registered as a member completes product registration using the shopping application for the first transaction, for example, the customer terminal device 50 may display a screen instructing the customer to go to the service counter or call a nearby store clerk before settlement, so that a store clerk can complete the member registration procedure, instead of the checkout transition code screen or the hold release transition code screen. In addition, the store may conduct a campaign to present a commemorative gift to a customer who uses the shopping application for the first time after completing the member registration. In this case, when the customer uses the shopping application for the first time to complete product registration, the customer terminal device 50 may display a screen instructing the customer to go to the service counter or call a nearby store clerk before payment to receive the commemorative gift, instead of the payment transition code screen or the hold release transition code screen.

[0175] [Third Modification] For example, there may be cases where a defect such as a difference in selling price of a product, purchase of a recalled product, or forgetting to take change occurred in the previous transaction. Such a defect history is stored in the transaction management device 60. When the customer completes product registration in accordance with the use of the current shopping application, if it is determined based on the history stored in the transaction management device 60 that a defect occurred in the previous transaction, the customer terminal device 50 may display a defect notification screen instead of the settlement transition code screen or the hold release transition code screen. The defect notification screen includes content that, for example, guides the customer to go to the service counter or call a nearby store clerk before settlement so that the store clerk can handle the defect in the previous transaction.

[0176] [Fourth Variation] In the above embodiment and modified examples, part of the processing executed by the customer terminal device 50, the transaction information management device 80, etc. may be executed by a higher-level device such as a transaction management device 60 connected via communication to the customer terminal device 50 and the transaction information management device 80. In the above embodiment and modified examples, part of the processing executed by the settlement device 40 may be executed by a higher-level device such as a transaction management device 60 connected via communication to the settlement device 40. As one of the above aspects, the shopping system of this embodiment may be provided with the configuration of a thin client system. As an 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, the transaction information management device 80, etc. 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 the thin client terminals. In response to information received from the thin client terminals, the transaction information management device 80 may execute processes such as product registration and determination of the presence or absence of reserved products in the cart information, and transmit image data or web page data as a screen reflecting the processing results to the thin client terminals. The customer terminal device 50, the transaction information management device 80, etc. as thin client terminals display the transmitted image data or web page data by an image viewer or a web browser.

[0177] <Summary of the embodiment> [Technical field] The present invention relates to a portable registration terminal, a product sales data processing system, a store clerk terminal, and a program. [Background technology] 2. Description of the Related Art A system is known in which customers themselves register products using mobile terminals (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2020-067947 A [Summary of the Invention] [Problem to be solved by the invention] In a product sales data processing system in which customers themselves use a portable registration terminal to register products, the registration result may indicate that a store clerk's intervention is required for a product registered by the portable registration terminal. For a transaction that includes a product that requires a store clerk's intervention (a store clerk-intervention product), the store clerk performs a predetermined process corresponding to the store clerk-intervention product before moving on to settlement. It is preferable that the process corresponding to the store clerk-intervention product is performed in a manner that does not interfere with the transaction of other customers. The present invention has been made in consideration of the above circumstances, and aims to provide a product sales data processing system in which customers themselves register products using a portable registration terminal, whereby processing corresponding to products requiring clerk intervention is performed without interfering with the transaction progress of 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) that includes a registration means for registering products, and an information generation means for generating settlement transition information (e.g., a settlement transition code screen including a settlement transition code CDP) (e.g., step S103) if the products registered by the registration means do not include a clerk-intervention product (e.g., an on-hold product) that requires clerk-intervention processing, and for generating clerk-intervention transition information regarding transition to clerk-intervention processing (e.g., hold release processing) (e.g., settlement transition code CDP, on-hold release transition code CDH, a clerk call button, a message for the customer, etc. displayed on the on-hold release transition code screen) (e.g., step S104) if the products registered by the registration means include a clerk-intervention product.

[0179] According to the above configuration, the customer terminal device 50 can display a settlement transition code screen showing the settlement transition code CDP when a held item is included among the items registered by the customer using the customer terminal device 50, and can display a hold release transition code screen when a held item is not included. In this case, when the hold release process is required due to the presence of a held item, it is possible to transition to the hold release process without having the settlement device 40 read the settlement transition code CDP on the settlement transition code screen. This allows, in a shopping system (product sales data processing system) in which customers themselves register products using the customer terminal device 50, processing corresponding to products requiring clerk intervention can be performed so as not to interfere with the transaction progress of other customers.

[0180] (2) One aspect of this embodiment is the portable registration terminal described in (1), which is equipped with an information output means for outputting the store clerk intervention transition information generated by the information generation means to a specified store clerk terminal (e.g., the transaction information management device 80, a store clerk mobile terminal, etc.). In this case, the store clerk intervention transition information includes the on-hold release transition code CDH displayed on the on-hold release transition code screen, the settlement transition code CDP, and a on-hold release permission notification in response to operation of the store clerk call button.

[0181] According to the above configuration, the customer terminal device 50 can cause a store clerk terminal different from the settlement device 40 to obtain store clerk intervention transition information.

[0182] (3) One aspect of this embodiment is the portable registration terminal described in (2), wherein the clerk intervention transition information output to the clerk terminal is information that enables the clerk intervention process to be executed on the clerk terminal (e.g., a settlement transition code CDP, a hold release transition code CDH).

[0183] According to the above configuration, a store clerk terminal separate from the settlement device 40 can obtain the store clerk intervention transition information and execute the on-hold release process.

[0184] (4) One aspect of this embodiment is a portable registration terminal as described in any one of (1) to (3), wherein the information generation means generates, as the store clerk-intervention transition information, information of a screen on which an operation can be performed to call a store clerk (for example, a hold release transition code screen on which a store clerk call button is located).

[0185] According to the above configuration, the customer can operate the store clerk call button displayed on the customer terminal device 50 to have the store clerk who responds to the call take the call back from the held state.

[0186] (5) One aspect of this embodiment is a product sales data processing system comprising a portable registration terminal and a store clerk terminal, wherein the portable registration terminal comprises a registration means for registering products, and an information generating means for generating settlement transition information when the products registered by the registration means do not include a store clerk-required product that requires store clerk-mediated processing, and for generating store clerk-mediated transition information regarding the transition to store clerk-mediated processing when the products registered by the registration means include the store clerk-required product, and the store clerk terminal comprises an editing means for editing transaction information (e.g., cart information) including the store clerk-required product as the store clerk-mediated processing.

[0187] Here, editing of transaction information refers to, as a specific example, the processing of information to release the reserved status of reserved items shown in the cart information and register them as normally registered items. Operations corresponding to such editing of transaction information include an operation to instruct release of reserved status for age verification items, medicines, security tag items, etc., an operation to input product information to release the reserved status of unspecified items, etc.

[0188] According to the above configuration, the reserved product processing can be performed by a store clerk terminal other than the settlement device 40.

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

[0190] According to the above configuration, after the reserved item is processed and released from the reserved item process using the store clerk terminal, the payment process can be continued using the same store clerk terminal.

[0191] (7) One aspect of this embodiment is a store clerk terminal that is equipped with an editing means for editing transaction information including a store clerk-mediated product that requires store clerk-mediated processing when the products registered by the portable registration terminal in response to a transaction include a store clerk-mediated product that requires store clerk-mediated processing.

[0192] (8) One aspect of this embodiment is a program for causing a computer serving 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 a product requiring clerk intervention that requires clerk intervention, and for generating clerk-mediated transition information regarding the transition to clerk-mediated processing if the products registered by the registration means include such a product requiring clerk intervention.

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

[0194] In addition, a program for realizing the functions of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction information management device 80, etc. described above in each of the above embodiments may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing as the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction information management device 80, etc. described above. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside the distribution server and accessible from the distribution server in order to distribute the program. The code of the program stored in the distribution server's recording medium may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. Note that the program may be divided into multiple parts, downloaded at different times, and then combined in the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds the program for a certain period of time, such as a volatile memory (RAM) in a computer system that becomes a server or a client when the program is transmitted via a network. The above program may be for realizing part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0195] 10 Management device, 40 Settlement device, 50 Customer terminal device, 60 Transaction management device, 70 Credit card settlement server, 80 Transaction information management device

Claims

1. A registration means for registering a product; an information generating means for generating payment transition information when the products registered by the registration means do not include a product requiring clerk intervention, and for generating screen information on a screen on which an operation can be performed to call a clerk as clerk intervention transition information regarding transition to clerk intervention when the products requiring clerk intervention are included; A portable registration terminal comprising:

2. The information output means outputs the store clerk intervention transition information generated by the information generation means to a predetermined store clerk terminal. The portable registration terminal of claim 1.

3. The store clerk intervention transition information output to the store clerk terminal is information that enables the store clerk intervention process to be executed on the store clerk terminal. The portable registration terminal of claim 2.

4. A product sales data processing system including a portable registration terminal and a store clerk terminal, The portable registration terminal includes: A registration means for registering a product; an information generating means for generating settlement transition information when the products registered by the registration means do not include a product requiring clerk intervention that requires clerk intervention, and for generating screen information on a screen on which a user can operate to call a clerk as clerk intervention transition information regarding a transition to clerk intervention when the products requiring clerk intervention are included, The store clerk terminal includes: As the store clerk intervention processing, an editing means is provided for editing transaction information including the store clerk intervention required product. Product sales data processing system.

5. The store clerk terminal includes a settlement unit capable of executing a settlement process using the transaction information edited by the editing unit.

5. The product sales data processing system according to claim 4.

6. A computer as a portable registration terminal, a registration means for registering the product; an information generating means for generating settlement transition information when the products registered by the registration means do not include a product requiring clerk intervention, and for generating screen information on an operation for calling a clerk as clerk intervention transition information regarding transition to clerk intervention when the product requiring clerk intervention is included; A program to function as a

7. A product sales data processing system including a portable registration terminal and a server, The server, A registration means for registering a product based on product identification information transmitted from a portable registration terminal; and an information generating means for generating settlement transition information when the products registered by the registration means do not include a product requiring clerk intervention that requires clerk intervention, and for generating screen information on which an operation can be performed to call a clerk as clerk intervention transition information regarding transition to clerk intervention processing when the products registered by the registration means include the clerk intervention transition information, and for outputting the generated settlement transition information or clerk intervention transition information on the portable registration terminal. Product sales data processing system.

Citation Information

Patent Citations

  • Monitoring device, monitor supporting device, and program thereof

    JP2019153074A

  • Commodity selling data processing device and program

    JP2020160930A

  • Shopping cart

    JP2020067947A