Product sales data processing system, program and mobile terminal

Abstract

To provide technology for controlling misidentification of a total price.SOLUTION: An item sales data processing system for registering items by means of a portable terminal operated by a customer of a store includes: registration means for registering the items secured by a customer, and display means for displaying a total price of the items registered by the registration means. The registering means registers the items whose prices are unknown as the items with no known price. The display means displays the total price in different manners between when the items with no known price are registered by the registration means and when the items with no known price are not registered by the registration means.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] The present invention relates to a product sales data processing system. , P Program and mobile devices Regarding. [Background technology]

[0002] There is a known system in which customers can register products themselves using a mobile terminal equipped with a camera (see, for example, Patent Document 1). This system has a function in which the mobile terminal displays the total price at that point in time even while the customer is in the middle of shopping. This function has been well received by customers, and improves customer convenience. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6242444 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, even if the price of a registered product is unknown, a total price is displayed that does not reflect the fact that a product with an unknown price has been registered, which may lead to customers misunderstanding the total price or misinterpreting the total price.

[0005] The present invention has been made in consideration of the above circumstances, and has an object to provide a technique for suppressing erroneous recognition of the total amount. [Means for solving the problem]

[0006] One aspect of the present invention that solves the above-mentioned problems is a product sales data processing system that registers products using a mobile terminal operated by a customer of a store, the product sales data processing system comprising: a registration means that registers products reserved by the customer; and a display means that displays a total price of the products registered by the registration means, wherein the registration means registers products whose prices are unknown as products with unknown prices, and the display means displays the total price in different manners depending on whether a product with an unknown price has been registered by the registration means or not. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of a product sales data processing system according to an embodiment of the present invention. [Diagram 2] 1 is a diagram showing an example of the state near the entrance of a store in which a product sales data processing system according to an embodiment of the present invention has been introduced. [Diagram 3] 1A to 1C are diagrams illustrating examples of how a mobile terminal is set in a shopping cart according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram illustrating a settlement device according to the present embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a mobile terminal according to the present embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a transaction management device according to the present embodiment. [Figure 7] 4A to 4C are diagrams illustrating an example of customer information, store information, and cart information according to the embodiment. [Figure 8] FIG. 2 is an explanatory diagram illustrating classification of reserved products according to the embodiment. [Figure 9] A sequence diagram showing an example of processing procedures executed by a mobile terminal, a settlement device, and a transaction management device according to this embodiment in response to the accounting of one transaction in self-service operation. [Figure 10] 11A to 11C are diagrams showing examples of a start-up screen, a product registration initial screen, a product registration update screen, and a code display screen according to the present embodiment. [Figure 11]11A to 11C are diagrams illustrating an example of a registered product presentation screen, a product registration screen, and a guide image according to the embodiment. [Figure 12] FIG. 13 is a diagram showing a display mode when a product with an unknown price is registered according to the embodiment. [Figure 13] 6 is a flowchart illustrating an example of an operation of the mobile terminal according to the embodiment. [Figure 14] 6 is a flowchart illustrating an example of an operation of the mobile terminal according to the embodiment. [Figure 15] 6 is a flowchart illustrating an example of an operation of the mobile terminal according to the embodiment. [Figure 16] 5 is a flowchart showing an example of the operation of the transaction management device according to the present embodiment. [Figure 17] 11A and 11B are diagrams showing an example of a re-read instruction screen and a preset key screen according to the embodiment; [Figure 18] 11A and 11B are diagrams showing an example of a re-read instruction screen and a preset key screen according to the embodiment; [Figure 19] FIG. 13 is a diagram showing an example of a settlement screen according to the embodiment. [Figure 20] FIG. 13 is a diagram showing an example of a reserved product processing screen according to the embodiment; [Figure 21] FIG. 13 is a diagram showing an example of a reserved product processing screen according to the embodiment; [Figure 22] 1 is a diagram showing an example of an enlarged captured image area according to the embodiment; [Figure 23] FIG. 13 is a diagram showing an example of a reserved product processing screen according to the embodiment; [Figure 24] 1 is a diagram showing an example of an enlarged captured image area according to the embodiment; [Diagram 25] 13 is a flowchart showing an example of a processing procedure executed by the settlement device according to the embodiment in relation to displaying a reserved product processing screen. [Figure 26] FIG. 11 is a diagram showing an example of a captured image area according to a first modified example of the present embodiment. [Figure 27] FIG. 11 is a diagram showing an example of a settlement screen according to a second modified example of the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] <Embodiment> [Example of overall configuration of product sales data processing system] FIG. 1 shows an example of the overall configuration of a product sales data processing system 1 according to this embodiment. The product sales data processing system 1 in the figure includes a store controller 10, a transaction management device 20 (cloud server), a registration settlement device 30, a settlement device 40, a transaction status management device 50 (for example, a personal computer, etc.), and a mobile terminal 60. The product sales data processing system 1 in the figure can be introduced in various stores, etc. (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).

[0009] Although one registered settlement device 30 is illustrated in the figure, the number of registered settlement devices 30 installed in one store may be two or more. Although two settlement devices 40 are illustrated in the figure, the number of settlement devices 40 in one store may be one or three or more. Although one transaction status management device 50 is illustrated in the figure, the number of transaction status management devices 50 in one store may be two or more. Furthermore, two or more store controllers 10 may be provided in one store.

[0010] The product sales data processing system 1 in the figure is capable of handling both a store clerk-assisted operation in which a store clerk uses a registration and settlement device 30 to register products, and a self-service operation in which a customer registers products using a mobile terminal 60 and then uses a settlement device 40 to settle the payment. In the following explanation, self-operation will be mainly described.

[0011] The store controller 10, the registration and settlement device 30, the settlement device 40, and the transaction status management device 50 are installed in a store. The store controller 10, the registration and settlement device 30, the settlement device 40, and the transaction status management device 50 are communicatively connected via a LAN 19 (which may be wired or wireless). The store controller 10 is communicable with the transaction management device 20.

[0012] The store controller 10 is a device that mainly manages various devices installed in a store. For example, the store controller 10 has a communication function with an external device, and receives a product file (product master) from an external device (e.g., a head office server not shown, which may be the transaction management device 20) and supplies it to the registered settlement device 30, etc., and receives transaction information from the settlement device 40, etc. and transmits it to the external device (e.g., the transaction management device 20, etc.).

[0013] The transaction management device 20 is a server that provides various services. For example, the transaction management device 20 manages various information (e.g., transaction information (cart information), etc.) corresponding to self-service operation.

[0014] The registration and settlement device 30 is a device that executes registration processing and settlement processing. The registration and settlement device 30 is used by a store clerk (the registration and settlement processing are executed by the operation of the store clerk).

[0015] The settlement device 40 is a device that executes settlement processing. The settlement device 40 is used by a customer. That is, the settlement device 40 executes settlement processing in response to operations by the customer. In addition, when the payment includes items whose processing is temporarily suspended for confirmation by a store clerk (hereinafter referred to as "pending items"; details will be described later), a store clerk will be called and the clerk (or the customer) will operate the payment device 40 to confirm the pending items.

[0016] The transaction status management device 50 is a device that mainly manages (or monitors) various devices within the LAN 19. The transaction status management device 50 manages the operating status of other devices (e.g., the registered settlement device 30, the settlement device 40, etc.), displays various information on the other devices, and outputs various commands to the other devices.

[0017] The mobile terminal 60 is a terminal used by a customer in a self-service environment. In this embodiment, the mobile terminal 60 is used in a state where it is attached to a shopping cart 70 in a self-service environment.

[0018] The mobile terminal 60 has a recognition function for recognizing various codes (barcodes, two-dimensional codes, etc.) in addition to a communication function and an imaging function (camera). For example, the mobile terminal 60 recognizes a barcode attached to a product. In other words, the mobile terminal 60 reads product identification information (product code). The mobile terminal 60 may extract feature points in an image captured by the imaging function (an image acquired as a through image) and recognize an object (various codes).

[0019] The mobile terminal 60 is a smartphone or the like owned by the customer. The mobile terminal 60 may be owned by the store and lent to the customer when shopping. Although two mobile terminals 60 are shown in the figure, the number of mobile terminals 60 used for product registration in the store varies depending on the number of customers.

[0020] A shopping application having a function for registering products in accordance with the self-service operation of this embodiment is installed on the mobile terminal 60.

[0021] Fig. 2 shows an example of the state near the entrance of a store in which the product sales data processing system 1 of this embodiment has been installed. As shown in Fig. 2, near the entrance (or the entrance if the entrance and exit are separate), a rental shopping cart 70, a rental shopping basket 80, and a sale shopping bag 90 are prepared. When a customer visits the store, they place the shopping basket 80 in the shopping cart 70, place the shopping bag 90 in the shopping basket 80, etc., and proceed into the store. At this time, if the customer wishes to do their own shopping, they place the mobile terminal 60 in the shopping cart 70.

[0022] The customer may bring the shopping bag 90 that he or she has just purchased as his or her own bag the next time he or she visits the store, or may bring a different bag from the shopping bag 90 as his or her own bag. Also, the customer may purchase a plastic bag.

[0023] Although not shown in the figure, a bag for reserved items (described later) is attached to the shopping cart 70 in addition to the shopping basket 80 for storing reserved items.

[0024] [Example of how a mobile device is placed in a shopping cart] An example of how the mobile terminal 60 is set in the shopping cart 70 will be described with reference to Fig. 3. Fig. 3(A) is a side view of the part of the shopping cart 70 where the mobile terminal 60 is set. Fig. 3(B) is a top view of the shopping cart 70.

[0025] As shown in Fig. 3(A), a holder 71 for setting a mobile terminal 60 is attached to shopping cart 70. A customer sets mobile terminal 60 in holder 71. Mobile terminal 60 set in holder 71 is in a state in which an image of shopping bag 90 or the entire personal bag can be captured by imaging unit 606 (see Fig. 4(B)) as shown in Fig. 3(B).

[0026] [About the payment device] FIG. 4 is a diagram for explaining the settlement device 40. FIG. 4(A) is a diagram showing an example of the appearance of the settlement device 40 (front view seen from the customer side). FIG. 4(B) is a diagram showing an example of the configuration of the settlement device 40. In FIG. 4(A) and FIG. 4(B), the same parts are given the same reference numerals.

[0027] An example of the configuration of settlement device 40 shown in Fig. 4(B) will be described below with reference to Fig. 4(A). Settlement device 40 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a display unit 405, a scanner unit 406, a card settlement unit 408, a change dispenser 409, a printing unit 413, an audio output unit 414, a communication unit 415, and an imaging unit 416 (camera). These can communicate with each other via a bus. Settlement device 40 may further include a key operation unit and an alarm unit (for example, a lamp on a sign pole, etc.).

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

[0029] The RAM 403 is a read / write memory, and stores various information as a main storage device. For example, the RAM 403 stores information read from the ROM 402 or the hard disk 404, information acquired from the outside, information generated during processing, and the like.

[0030] The hard disk 404 stores various information as an auxiliary storage device. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information acquired from the outside, information generated in processing, etc. Note that instead of the hard disk 404, a storage device such as an SSD (Solid State Drive) may be provided.

[0031] The display unit 405 is a touch display that displays various information and accepts various inputs.

[0032] The scanner unit 406 optically reads various information. For example, the scanner unit 406 scans a code (such as a barcode or a two-dimensional code) displayed on the display unit of the mobile terminal 60 and reads information necessary for the settlement process. The scanner unit 406 may also scan a code printed on a receipt (registered trademark) issued by another device (for example, a registered settlement device 30) and read information necessary for the settlement process. The scanner unit 406 may also scan a code attached to a product and read the product code. The scanner unit 406 may also scan a code attached to a store clerk's name tag and read the store clerk code.

[0033] The card payment unit 408 is a payment mechanism that uses various cards (credit cards, prepaid cards such as transportation cards, cash cards for debit payments, point cards for point payments, etc.). The card payment unit 408 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 recognize various cards (e.g., point cards, membership cards, stockholder cards, etc.) for the purpose of providing benefits, discounts, etc.

[0034] The change machine 409 (cash settlement unit) is a mechanism for settlement with cash, and 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 amount of change, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. When banknotes or coins are inserted into the input port, they are detected by a sensor (detection of the fact that they have been inserted, detection of the number of coins by denomination, etc.).

[0035] The printing unit 413 prints and issues various media (receipts, bills, etc.). The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs audio guidance and the like. The communication unit 415 transmits and receives information to and from other devices (the store controller 10, the registered settlement device 30, the other settlement devices 40, the transaction status management device 50, etc.).

[0036] The imaging unit 416 is provided to capture an image of, for example, the hands of a customer operating the change machine.

[0037] [Registered payment device] The registration and settlement device 30 may be configured to have a display unit and a scanner unit on each side (clerk side, customer side) and a settlement unit (card settlement unit, cash settlement unit) on one side (customer side). The registration and settlement device 30 configured in this way may be a device that can be switched to any of a plurality of operation modes (a mode in which a registration process is executed by a clerk's operation and a settlement process is executed by a customer's operation, a mode in which a registration process is executed by a clerk's operation and a settlement process is executed by a customer's operation, etc.) depending on, for example, the operating status. Also, if the registration and settlement device 30 is configured to execute the settlement process by the customer's operation, it can be used for self-operation. That is, a customer can make a transaction by having the mobile terminal 60 execute the registration process and have the registration and settlement device 30 execute the settlement process. However, in the following description, an example will be given in which the settlement device 40 is used for self-service operation.

[0038] [Example of mobile device configuration] 5 shows an example of the configuration of a mobile terminal 60. The mobile terminal 60 in the figure includes a CPU 601, a storage unit 602, a RAM 603, a display unit 604, an operation unit 605, an imaging unit 606, and a network-compatible communication unit 607.

[0039] The CPU 601 is a central processing unit, and controls the operation of the mobile terminal 60 by reading and executing programs stored in the storage unit 602 . The storage unit 602 is an auxiliary storage device for the CPU 601, and stores various types of information used by the CPU 601, including programs. The RAM 603 is a main storage device for the CPU 601 .

[0040] The display unit 604 displays images according to display control by the CPU 601. The display unit 604 may be configured as a touch panel that allows operations to be performed on the screen. The operation unit 605 collectively indicates various operators provided on the mobile terminal 60 and various input devices connected to the mobile terminal 60.

[0041] The imaging unit 606 captures images under the control of the CPU 401. The imaging unit 606 of this embodiment can also function as a part that reads two-dimensional codes in a code reader that processes the two-dimensional codes.

[0042] The network-compatible communication unit 607 is a unit that wirelessly communicates via a network. The network-compatible communication unit 607 enables the mobile terminal 60 to communicate with the transaction management device 20.

[0043] [Example of transaction management device configuration] 6 shows an example of the configuration of transaction management device 20. Transaction management device 20 in the figure includes a CPU 201, a storage unit 202, a RAM 203, and a network-compatible communication unit 204. CPU 201 is a central processing unit that controls the operation of transaction management device 20 by reading and executing programs stored in memory unit 202 . The storage unit 202 is an auxiliary storage device for the CPU 201, and stores various types of information used by the CPU 201, including programs. The RAM 203 is a main storage device for the CPU 201 . The network compatible communication unit 204 is a part that performs communication via a network.

[0044] The memory unit 202 of the transaction management device 20 stores customer information, store information, and cart information.

[0045] [Information stored in the transaction management device] The customer information stored in the memory unit 202 is information for managing individual customers. The transaction management device 20 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 20 also updates the customer information as appropriate based on cart information, etc. The transaction management device 20 may update the customer information, for example, by referring to the cart information at a specified time every day.

[0046] 7(A) shows an example of customer information stored in the memory unit 202 of the transaction management device 20. The customer information in this figure includes customer identification information, customer name, customer registration date, product cancellation information, customer rank, number of points, etc. The customer identification information is identification information that uniquely identifies a customer. As the customer identification information (or instead of the customer identification information), for example, application identification information that is uniquely (e.g., sequentially) assigned to each installed shopping application may be used. Also, as the customer identification information (or instead of the customer identification information), terminal identification information unique to the mobile terminal 60 in which the shopping application is installed may be used. The terminal identification information may be hardware identification information uniquely assigned to the hardware of the mobile terminal 60, such as a telephone number assigned to a customer who is a user of the mobile terminal 60, or 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. Product cancellation information is information regarding cancellation of a product after it has been registered. 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 the actual transaction (product registration), other information (product cancellation information, etc.) is not generated.

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

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

[0049] 7(B) shows an example of store information stored in the memory unit 202 of the transaction management device 20. 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. 7(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. 7B 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. 7(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.

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

[0051] Cart information is information for managing individual transactions. The transaction management device 20 generates the cart information at the start of a transaction. In addition, the transaction management device 20 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).

[0052] FIG. 7(C) is an example of cart information stored in memory unit 202 of transaction management device 20. The cart information in FIG. 1 includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, and reserved product information.

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

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

[0055] 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 7 (C), registered product information (registered product 3) to registered product information (registered product 5) are omitted from the illustration. Registered product information (registered product N; N is an integer) includes the product code, product name (product name), price, etc.

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

[0057] The reserved product information (total) is information that is updated each time a reserved product is registered. The reserved product information (total) includes the number of reserved products (items) of all types and the number of reserved products (items) of each type. In this embodiment, the reserved products are classified into a plurality of types, and each classification is managed by classification number (reserved major classification number, reserved minor classification number) (details are explained in FIG. 8). In the example of FIG. 7(C), "Total number of items: 3" in the reserved product information (total) indicates that the number of items of all types (total of reserved products with reserved major classification numbers "1" to "4") is 3, "NON-FILE: 2" indicates that the number of reserved products classified as NON-FILE (total of reserved products with reserved major classification number "1") is 2, and "Read NG: 1" indicates that the number of reserved products classified as read NG (total of reserved products with reserved major classification number "2") is 1.

[0058] NON-FILE means that the barcode or product code was successfully scanned at the store (the product code was read), but the product code has not been stored (registered) in the product file. In other words, a reserved product classified as NON-FILE is a reserved product whose product code was successfully scanned, but whose product code has not been stored in the product file.

[0059] A "no read" means that the reading (scanning) of the product code at the store was not successful. In other words, a reserved product classified as a "no read" is a reserved product whose product code was not successfully read.

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

[0061] The reserved product information (reserved product N; N is an integer) includes a reserved major category number (described later). For example, if the Nth item of product is a reserved product classified as NON-FILE with a reserved major category number of "1", the reserved product information (reserved product N) includes the reserved major category number "1 (NON-FILE)" and a product code. Also, if the Nth item of product is a reserved product classified as read-NG with a reserved major category number of "2", the reserved product information (reserved product N) includes the reserved major category number "2 (read-NG)" and image data (image captured by the mobile terminal 60). Note that the reserved product information for reserved products classified as NON-FILE may include image data in addition to the reserved major category number "1 (NON-FILE)" and a product code.

[0062] 7 is an example of information stored in transaction management device 20, and transaction management device 20 may store other information (e.g., a product file). Information about one product in a product file may include, for example, a product code (product identifier), a product name, a price, and the like.

[0063] Fig. 8 is an explanatory diagram for explaining classification of reserved products according to this embodiment. As shown in Fig. 8, in this embodiment, reserved products are classified into major categories (classification by reserved major category numbers) and minor categories (classification by reserved minor category numbers). Note that the devices in the product sales data processing system 1 may be able to refer to information such as that shown in Fig. 8 (such as a file showing the relationship between reserved major category numbers and reserved minor category numbers).

[0064] As shown in FIG. 8, in this embodiment, reserved products are classified into four major categories, with reserved major category numbers "1" to "4."

[0065] Reserved items classified under reserve category number "1" are NON-FILE reserved items. As described above, NON-FILE reserved items are reserved items whose product code has been successfully scanned but the product code is not stored in the product file. In other words, if a product code has been successfully scanned but the product code has not been stored in the product file, the reserved item is classified under reserve category number "1." Reserved items classified under reserve category number "1" have an unknown price, so confirmation by a store clerk is required at the time of payment.

[0066] In Figure 8, "NON-FILE" in "1 (NON-FILE)" is the classification name of the reserved item (major classification name of the reserved item). The same applies to "Read NG" in "2 (Read NG)", "Specific item" in "3 (Specific item)", and "Cancelled item" in "4 (Cancelled item)" described later.

[0067] In this embodiment, there is a reserved minor category number "11" as a subordinate (lower) minor category of the major category of reserved major category number "1". Since there is only one reserved minor category under the major category of reserved major category number "1", the reserved minor category number "11", all reserved products classified under reserved major category number "1" are classified under reserved minor category number "11".

[0068] In FIG. 8, "NON-FILE" in "11 (NON-FILE)" is the category name of the reserved product (reserved minor category name). The same applies to "pseudo scan (coating, etc.)" in "21 (pseudo scan (coating, etc.)" and "pseudo scan (short time)" in "22 (pseudo scan (short time)" described later.

[0069] In addition, in Figure 8, a read operation "Yes" indicates that a read operation was performed, a read operation "No" indicates that a read operation was not performed, a read success / failure "Success" indicates that the read operation was successful, a read success / failure "Failure" indicates that the read operation failed, and a read success / failure "-" indicates that the read operation was not performed, and therefore the problem is unrelated to the success or failure of the read.

[0070] Reserved items classified under reserve category number "2" are reserved items that could not be read. As described above, reserved items that could not be read are reserved items whose product codes could not be read successfully. In other words, when a reserved item is placed on hold because the product code could not be read successfully, the reserved item is classified under reserve category number "2." Reserved items classified under reserve category number "2" have an unknown price and are also susceptible to fraudulent manipulation, so they require confirmation by a store clerk at the time of payment.

[0071] In this embodiment, reserved minor category numbers "21," "22," "23," and "24" exist as minor categories under the major category of reserved major category number "2." Reserve minor category number "21" is reserved product with "pseudo scan (coated, etc.)." Reserve minor category number "22" is reserved product with "pseudo scan (short time)." Reserve minor category number "23" is reserved product with "bad barcode." Reserve minor category number "23" is reserved product with "non-scanned input."

[0072] A reserved item with reserved subcategory number "21" (pseudo scan (covered, etc.)) is, for example, a reserved item for which a reading operation has been performed (the item has been held over), that is, the item has been placed within the imaging range of the imaging unit 606 (more specifically, the readable range of the barcode), but the barcode of the item has not been captured (captured within the readable range) (because only parts of the item other than the barcode are captured within the readable range), so the item cannot be read; a reserved item for which the barcode of the item has been captured but part of the barcode is covered, for example by a finger, so the item cannot be read; or a reserved item for which the barcode of the item has been captured but the imaging angle of the barcode is inappropriate, so the item cannot be read.

[0073] A reserved item with reserved subcategory number "22" (pseudo scan (short time)) is, for example, a reserved item whose barcode was photographed but could not be read because the barcode moved (including passing by) too quickly to be read.

[0074] A reserved product with the reserved category number "23" (defective barcode) is, for example, a reserved product whose barcode has been photographed but cannot be read due to wrinkles, smudges, dirt, reflections, etc. in the printed portion of the barcode.

[0075] A reserved item (non-scanned) with the reserved major category number "24" is, for example, a reserved item that could not be read because it was placed in shopping cart 80 without the product being scanned (without being held over the card).

[0076] Reserved products with reserved subcategory numbers "21" to "24" (i.e. reserved products with reserved major category number "2") may be referred to as unreadable products. Also, a situation that results in reserved products with reserved subcategory numbers "21" to "24" may be referred to as a unreadable situation (or simply "unreadable").

[0077] In addition, the reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)), the reserved items with reserved subcategory number "22" (pseudo scan (short time)), and the reserved items with reserved major category number "23" (bad barcode) have in common that they are all reserved items for which a reading operation was performed but the reading was unsuccessful. However, the reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)) and the reserved items with reserved subcategory number "22" (pseudo scan (short time)) are considered to have less of an intention to successfully read the item than the reserved items with reserved major category number "23" (bad barcode). In other words, the reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)) and the reserved items with reserved subcategory number "22" (pseudo scan (short time)) can also be said to be pseudo reading operations (fake reading operations), and are therefore referred to as reserved items with pseudo scans (fake scans).

[0078] Reserved items classified under reserve category number "3" are reserved items that are specific items (described below). Reserved items that are specific items are reserved items that have been successfully registered, but because they are specific items, they require the assistance of a store clerk when checking out. In other words, when an item becomes reserved because it is a specific item, the item is classified under reserve category number "3." Reserved items classified under reserve category number "3" are specific items, and therefore require the assistance of a store clerk when checking out.

[0079] In this embodiment, reserved minor category numbers "31," "32," and "33" exist as minor categories under the reserved major category number "3." Reserve minor category number "31" is a reserved product for "age verification products." Reserve minor category number "32" is a reserved product for "pharmaceuticals." Reserve minor category number "33" is a reserved product for "anti-theft tags."

[0080] Reserved items with the reserved subcategory number "31" (age verification items) are reserved items such as alcohol and tobacco that require a store clerk to verify the customer's age before selling them.

[0081] A reserved product with reservation subcategory number "32" (pharmaceutical products) is, for example, a reserved product that requires a licensed person such as a pharmacist to explain the product to the customer.

[0082] A reserved product with reservation subcategory number "33" (anti-theft tag product) is, for example, a reserved product that has a security tag attached and therefore requires a store clerk to remove the security tag from the product when it is sold.

[0083] Reserved goods classified under the reserve category number "4" are canceled reserved goods. Cancelled reserved goods are reserved goods that were successfully registered but whose registration was cancelled after registration. In other words, if a product becomes reserved because its registration was cancelled after it was registered, the reserved goods are classified under the reserve category number "4". Reserved goods classified under the reserve category number "4" are cancelled goods (i.e. goods that will not be purchased) and will not be taken out of the store, so they require confirmation by a store clerk when making the payment.

[0084] In this embodiment, there is a reserved minor category number "41" as a minor category under the major category of reserved major category number "4". Since there is only one reserved minor category under the major category of reserved major category number "4", reserved minor category number "41", all reserved products classified under reserved major category number "4" are classified under reserved minor category number "41".

[0085] In the above explanation, it is assumed that the reading operation has been performed for reserved items with reserved subcategory number "31" (age verification items), but if the reading operation has not been performed, the reserved items will be classified as reserved items with reserved subcategory number "24" (non-scanned input). The same applies to reserved items with reserved subcategory number "32" (medicines), reserved items with reserved subcategory number "33" (anti-theft tag items), and reserved items with reserved subcategory number "41" (cancelled items).

[0086] Also, in the above explanation, it is assumed that a reading operation is performed and the reading is successful for reserved items with reserved subcategory number "31" (age verification items), but if a reading operation is performed and the reading fails, the reserved items will be classified as reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)), reserved items with reserved subcategory number "22" (pseudo scan (short time)), or reserved items with reserved subcategory number "23" (bad barcode). The same applies to reserved items with reserved subcategory number "32" (pharmaceuticals), reserved items with reserved subcategory number "33" (anti-theft tag items), and reserved items with reserved subcategory number "41" (cancelled items).

[0087] As shown in Fig. 8, the reserved major category number and the reserved minor category number are in a higher-ranking relationship, but one or both may be used depending on the situation. For example, in the cart information shown in Fig. 7(C), an example in which the reserved major category number is stored in the reserved product information has been described, but the reserved minor category number may be stored instead of or in addition to the reserved major category number.

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

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

[0090] Step S1: The mobile terminal 60 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 mobile terminal 60, thereby allowing the mobile terminal 60 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 mobile terminal 60, the shopping application may be started, and a screen informing the customer that the transaction management device 20 is currently connected may be displayed as a start-up screen.

[0091] Fig. 10(A) shows an example of a start-up screen of a shopping application displayed on the display unit 604 of the mobile terminal 60. The start-up screen in this figure displays the store name. This store name is displayed based on the store-specific information acquired in step S1. When a customer wants to start registering products for shopping, the customer operates a transaction start button BT10 arranged on the start-up screen.

[0092] In response to the operation of transaction start instruction button BT10, mobile terminal 60 transmits a transaction start request including the acquired store specific information and customer identification information to transaction management device 20. Destination information (address of transaction management device 20) may be acquired at the time of customer registration (when a shopping application is downloaded or installed on mobile terminal 60) and stored in a memory unit of mobile terminal 60. In addition, when a two-dimensional code is scanned, destination information may be converted into a two-dimensional code in addition to the store specific information, and mobile terminal 60 may acquire the destination information together with the store specific information by scanning the two-dimensional code with mobile terminal 60.

[0093] Step S2: The transaction management device 20 receives the customer identification information and store identification information as a transaction start request from the mobile terminal 60, and generates cart information for the transaction. For example, the transaction management device 20 acquires the store identification information from the store identification information received from the mobile terminal 60, and further acquires the current date, issues (assigns) a serial number, combines the store identification information, the current date, and the serial number, and stores the combined information as cart identification information in the cart information. The transaction management device 20 also stores the current date and time as the transaction start date and time (generation date and time) in the cart information. The transaction management device 20 also stores the customer identification information received from the mobile terminal 60 as customer identification information in the cart information.

[0094] Step S3: The transaction management device 20, 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 mobile terminal 60. Specifically, the transaction management device 20 generates, for example, the product registration initial screen information, and transmits the generated product registration initial screen information to the mobile terminal 60 together with the cart identification information.

[0095] Step S4: The mobile terminal 60 receives the cart identification information and the product registration initial screen information from the transaction management device 20, stores the cart identification information, and displays the registration screen on the display unit. Specifically, the mobile terminal 60 displays the product registration initial screen as shown in FIG. 10(B), for example.

[0096] Step S5: The customer operates the mobile terminal 60 to scan the barcode attached to the product and read 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.

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

[0098] Step S6: Upon receiving the product registration information (cart identification information and product code) from mobile terminal 60, transaction management device 20 identifies the cart information of the transaction from the cart identification information included in the received product registration information.

[0099] Step S7: The transaction management device 20 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 20 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 20 also updates the registered product information (total) in the identified cart information.

[0100] Step S8: After updating the product data in the cart information, transaction management device 20 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 mobile terminal 60. Specifically, transaction management device 20 generates product registration update screen information such that a product registration update screen is displayed on mobile terminal 60, in which a list item of the currently registered product has been added to the registered product list, as shown in Fig. 10(C), for example, and transmits the generated product registration update screen information to mobile terminal 60 together with the cart identification information.

[0101] FIG. 10(C) shows an estimated total field AT indicating the number of registered items, and a total price field AF for the registered items. The estimated total field AT shows that the estimated total is three items (one item of XX yogurt, one item of XX chocolate, and one item of XX bread, for a total of three items). The total price field AF shows that the total price is 830 yen (= 260 yen + 350 yen + 220 yen). By displaying the current total price in this way, customers can know the current total price. The current total price is very useful information, especially for customers who are on a budget.

[0102] The product registration screen (product registration update screen) shown in Fig. 10(C) is displayed on the mobile terminal 60 after "XX bread" is registered as the third product. That is, when "XX yogurt" is stored in the cart information as the first product, the transaction management device 20 generates product registration update screen information such that "XX yogurt" is displayed on the mobile terminal 60 and transmits the generated product registration update screen information to the mobile terminal 60 together with the cart identification information, when "XX chocolate" is stored in the cart as the second product, the transaction management device 20 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed on the mobile terminal 60 and transmits the generated product registration update screen information to the mobile terminal 60 together with the cart identification information, and when "XX bread" is stored in the cart information as the third product, the transaction management device 20 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed on the mobile terminal 60 as shown in Fig. 10(C) and transmits the generated product registration update screen information to the mobile terminal 60 together with the cart identification information.

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

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

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

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

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

[0108] Step S13: The settlement device 40 reads the two-dimensional code displayed on the display of the mobile terminal 60 and requests the calculation of the subtotal amount from the transaction management device 20. For example, the settlement device 40 transmits a calculation request (subtotal amount calculation request information) to the transaction management device 20, together with the cart identification information obtained from the two-dimensional code, to request the calculation of the subtotal amount.

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

[0110] Step S15: After identifying the cart, the transaction management device 20 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.

[0111] Step S16: After calculating the subtotal, the transaction management device 20 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.

[0112] Step S17: The settlement device 40, which has received the cart identification information and the subtotal information from the transaction management device 20, displays the subtotal amount on the display unit 405 (a settlement screen including the subtotal amount).

[0113] Step S18: The settlement device 40, which has displayed the subtotal on the 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 20, and the transaction management device 20 stores the transaction end date and time (settlement date and time) for that cart.

[0114] [About reading failure situations] 9 shows a process corresponding to the case where the reading of the product code is successful in step S5. However, at the stage of the product code reading process corresponding to step S5, a situation (reading failure situation) may occur in which the mobile terminal 60 fails to read any of the reserved classification numbers "21" to "24" in FIG. 8.

[0115] As a specific example, Fig. 11(B) shows a scene where a reserved product with reserved subcategory number "21" (pseudo scan (covered, etc.)) may occur, using a captured image of the product registration screen. The figure shows the product registration screen displayed on the mobile terminal 60. The product registration screen in the figure shows a state where a captured image is displayed of a customer attempting to have the mobile terminal 60 read the barcode of a product with the barcode portion covered by their finger.

[0116] 11B, the portable terminal 60 recognizes the presence of a barcode from the captured image, but fails to read the barcode (cannot extract the code). In this case, the portable terminal 60 executes a read failure process (described later) to deal with the read failure situation.

[0117] Although details will be described later, in the reading failure process, a retry (reading) is performed on the product that has become a reading failure status, and if the reading failure status is not resolved by the retry, a preset key is displayed. The product that has become a reading failure status can be registered via the preset key. In other words, the reading failure status can be resolved by a retry or a preset key. In many cases, the reading failure status can be resolved by a retry or a preset key, but if the reading failure status is not resolved, the product becomes a reserved product.

[0118] If the unreadable state is not resolved (i.e., if the product becomes a pending product), for example, as shown in FIG. 11(C), a guide image WD2 may be displayed to encourage the user to place the pending product in a bag for pending products. Specifically, the guide image WD2 in the figure displays a message saying, "If you cannot scan the product, please place it in a special bag." Note that the form of the guide image WD2 is not particularly limited. The message displayed in the guide image WD2 may be, for example, "Scanning has failed" or "The product has been determined to be unreadable." 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. 10(B) or FIG. 10(C), for example.

[0119] Furthermore, when the mobile terminal 60 sets the unreadable product as a reserved product, the mobile terminal 60 may transmit captured images corresponding to the unreadable state to the transaction management device 20. 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 606 for reading the product code for a certain period of time. Furthermore, the captured images to be transmitted may be, for example, a predetermined number of still images, or may be moving images for a predetermined period of time according to the occurrence of the unreadable state.

[0120] In addition, the product registration screen displays a registered product list as shown in FIG. 10(C), but the mobile terminal 60 may display the products as list items regardless of the type of reserved product (i.e., all reserved products in the subcategory). When displaying the reserved products, information indicating that the products are reserved products (icon or button indicating that the products are reserved products, classification number (one or both of the reserved major classification number and the reserved minor classification number), classification name (one or both of the reserved major classification name and the reserved minor classification name) etc.) may be displayed. When displaying the reserved products, information indicating the type of the reserved products (classification number (one or both of the reserved major classification number and the reserved minor classification number), classification name (one or both of the reserved major classification name and the reserved minor classification name), icon or button according to the classification number or classification name etc.) may be displayed. In addition, the mobile terminal 60 may not display some reserved products (reserved products with a specific reserved minor classification number) as list items, and may display other reserved products as list items.

[0121] Next, we will explain how to display the total amount in different ways depending on whether an item with an unknown price is registered or not. Here, the items with unknown prices are the items with the above-mentioned reserved classification numbers "1" and "2".

[0122] Fig. 12 is a diagram showing the display mode when a product with an unknown price is registered. Fig. 12(A) and Fig. 12(B) show an estimated total field AT indicating the number of registered products, a total amount field AF of the registered products, and a reserved product display field AH. In Fig. 12(A), the estimated total field AT shows that the estimated total is three items (one item of OO yogurt, one item of OO chocolate, and one reserved product, for a total of three items). The total amount field AF shows that the total amount is 610 yen (= 260 yen + 350 yen) + α. Furthermore, the reserved product display field AH shows that the item is a reserved item and indicates that the item is a reserved item, and urges the user to add the item to the reserved basket.

[0123] In Fig. 12(B), the estimated total field AT shows that the estimated total is 2 items + 1 reserved item (1 item of XX yogurt and 1 item of XX chocolate, for a total of 2 items + 1 reserved item). Also, like Fig. 12(A), the total amount field AF shows that the total amount is 610 yen (= 260 yen + 350 yen) + α. Furthermore, like Fig. 12(A), the reserved item display field AH shows that the items are reserved and encourages the customer to add the items to their reserved basket.

[0124] In this manner, in this embodiment, as shown in FIG. 12, by adding "+α", the total amount is displayed which reflects that an item with an unknown price has been registered.

[0125] The display mode of the total amount field AF in FIG. 10(C) described above is different from that of the total amount field AF in FIG. 12(A) and FIG. 12(B). In addition, the display mode of the estimated total field AT in FIG. 10(C) is different from that of the estimated total field AT in FIG. 12(B). The display mode of FIG. 10(C) is a display mode when no products with unknown prices are registered. Therefore, the mobile terminal 60 displays the total amount in a different manner when a product with unknown prices is registered and when no products with unknown prices are registered. In addition, the mobile terminal 60 displays the number of products (estimated total) in a different manner when a product with unknown prices is registered and when no products with unknown prices are registered. Furthermore, when an item with an unknown price is registered, the total amount is displayed in a manner that includes the total amount of items whose price is known ("¥640" in Figures 12(A) and 12(B)) and information indicating that an item with an unknown price has been registered ("+α" in Figures 12(A) and 12(B). Note that the information indicating that an item with an unknown price has been registered is not limited to "+α" and may be a symbol such as "!" or language such as "¥640 + price of unknown item" or "over ¥640."

[0126] If, as in the past, the price of a registered product with an unknown price was not displayed in a different manner from the price of a registered product with an unknown price, various problems would arise, such as the customer misunderstanding the total amount, which would result in the customer being unable to pay at the time of payment, or the customer feeling uncomfortable when the total amount changes at the time of payment.

[0127] Therefore, by displaying the items in a different manner, it is possible to draw the customer's attention, and as a result, the customer can recognize that the total amount changes depending on the item whose price is unknown.

[0128] It is also possible for the customer to input a shopping budget in advance. In this case, it is possible to always determine whether the customer will exceed the budget by displaying whether the total amount exceeds the budget inputted by the customer. Similarly, it is also possible to always determine whether the customer will exceed the budget by displaying whether the total amount exceeds the balance of electronic money or the balance of points that can be paid in lieu of payment. In this way, not only can misrecognition of the total amount be suppressed, but it is also possible to easily determine whether the customer will exceed the budget, thereby improving convenience.

[0129] Furthermore, when a customer touches information indicating that a product with an unknown price has been registered (such as +α or !), or "￥640 + price of unknown product", the mobile terminal 6 may perform the following processes A, B, and C. In the following explanation, information indicating that a product with an unknown price has been registered is also referred to as unknown price information.

[0130] Process A is a process that accepts the input of a provisional amount by a customer. When there is a price tag showing the price of an item whose price is unknown on the mobile terminal 6, the customer can recognize the price. Therefore, when the unknown price information is touched, the mobile terminal 6 accepts the input of the price by the customer. The customer inputs the price into the mobile terminal 6, for example, by inputting a value. Although the input price is only provisional, the mobile terminal 6 can display a provisional but more accurate total amount (the sum of the total amount of items whose prices are not unknown and the input provisional price) compared to the case where the provisional price is not input. In addition, the customer can more accurately determine whether or not the budget is exceeded. As a display mode at this time, the total amount may be displayed in a different manner from the case where the item whose price is unknown is not registered, such as by changing the color of the total amount. Also, the input provisional price may be displayed by replacing it with "α" in FIG. 12. Specifically, if the total amount of items whose prices are not unknown is 610 yen and the input provisional price is 100 yen, it may be displayed as "￥640+￥100". Since the input provisional price is merely a provisional price, a store clerk will check it at the time of payment.

[0131] Process B is a process in which the mobile terminal 6 reads the price tag. When the unknown price information is touched, the mobile terminal 6 performs OCR (Optical Character Recognition) processing on the price tag read by the imaging unit 416 to obtain the price. The obtained price is only provisional, but compared to the case where the provisional price is not obtained, the mobile terminal 6 can display a provisional but more accurate total amount (total amount of products whose prices are not unknown + the obtained provisional price). In addition, the customer can more accurately determine whether or not the budget is exceeded. As a display mode at this time, the total amount may be displayed in a different manner from the case where the product whose price is not registered, such as by changing the color of the total amount. In addition, the obtained provisional price may be displayed by replacing it with "α" in FIG. 12. Specifically, if the total amount of products whose prices are not unknown is 610 yen and the obtained provisional price is 100 yen, "￥640+￥100" may be displayed. Note that since the obtained provisional price is only a provisional price, a store clerk checks it at the time of payment.

[0132] In the above processes A and B, the price entered by the customer or obtained by OCR processing was only provisional, but it may be treated as the correct price. In this case, the price in the product master may be updated to the price entered by the customer or obtained by OCR processing. If the price entered by the customer or obtained by OCR processing is treated as the correct price, the total amount will be displayed in the same manner as when the total amount of products whose prices are known is displayed, and there will be no need for a store clerk to check the price at the time of payment.

[0133] Process C is a process in which the store clerk inputs the price. The input by the store clerk can be a process in which the store clerk directly inputs the price into the mobile terminal 6, or a process in which the store clerk inputs the price from a higher-level device. In the former case, when the unknown price information is touched, the store clerk is authenticated and then the price input is accepted. In this case, the product that was put on hold because the price was unknown is no longer a put on hold product, and the total amount is displayed in the same manner as when the total amount of products whose prices are known is displayed, and furthermore, there is no need for the store clerk to check the payment at the time of settlement.

[0134] When inputting from a higher-level device, first, when the price unknown information is touched, the mobile terminal 6 transmits at least one captured image when the barcode of the product whose price is unknown is read to the higher-level device. Alternatively, when the price unknown information is touched, the mobile terminal 6 transmits a captured video when the barcode of the product whose price is unknown is read to the higher-level device. When the captured image or video is received in the higher-level device, a store clerk visually checks the captured image or video. After checking the captured image or video, the store clerk transmits the price and other product information as necessary to the mobile terminal 6. The mobile terminal 6 regards the price received from the higher-level device as the price input by the store clerk, and the price of the product whose price is unknown as the input price. In this case, the product that was set as a reserved product because the price was unknown is no longer a reserved product, and the display mode of the total amount is the same as when the total amount of the product whose price is not unknown is displayed, and furthermore, check by the store clerk at the time of payment is not required.

[0135] 13 to 15 are flowcharts showing an example of the operation of the mobile terminal 60 according to this embodiment. FIG. 16 is a flowchart showing an example of the operation of the transaction management device 20 according to this embodiment. The flowcharts in FIG. 13 to 16 correspond to the processing of steps S5 to S9 in FIG. 9. Note that the flowcharts in FIG. 13 to 16 omit processing related to reserved items (specific items) classified under reserved major classification number "3" and reserved items (cancelled items) classified under reserved major classification number "4".

[0136] Although not shown in the flowcharts of FIGS. 13 to 15, the mobile terminal 60 constantly captures images using the imaging unit 606 in order to read barcodes and recognize the insertion of products into the shopping cart 80.

[0137] [Explanation of the flow chart in Figure 13] Step S100: The mobile terminal 60 judges whether or not the customer has started to read a barcode. For example, when the mobile terminal 60 recognizes an object resembling a barcode in the captured image (through image), it judges that the customer has started to read a barcode. Note that several images of objects resembling a barcode may be stored as comparison images in the storage unit 602 of the mobile terminal 60 (or in another device that the mobile terminal 60 can refer to, for example, the storage unit 202 of the transaction management device 20), and when the mobile terminal 60 recognizes an image similar to any of the comparison images in the captured image, it may judge that it has recognized an object resembling a barcode (i.e., it may judge that the customer has started to read a barcode). If the reading operation has started (step S100: YES), the process proceeds to step S101. If the reading operation has not started (step S100: NO), the process proceeds to step S104.

[0138] Step S101: The mobile terminal 60 determines whether or not the reading of the barcode has been completed (successful). That is, the mobile terminal 60 determines whether or not the product code has been acquired from the barcode. If the reading has been completed (Step S101: YES), proceed to Step S110. If the reading has not been completed (Step S101: NO), proceed to Step S102.

[0139] Step S102: The mobile terminal 60 judges whether or not the insertion of an item into the shopping basket 80 has been detected. That is, the mobile terminal 60 set in the manner illustrated in Fig. 3 captures an image of the contents of the shopping basket 80 placed in the shopping cart 70, and is able to detect the insertion of an item into the shopping basket 80 from a change in the captured image. If the insertion of an item is detected (Step S102: YES), the process proceeds to Step S120. If the insertion of an item is not detected (Step S102: NO), the process proceeds to Step S103.

[0140] Step S103: The mobile terminal 60 judges whether or not a predetermined time has elapsed since the start of the reading operation. If the predetermined time has elapsed (Step S103: YES), the process proceeds to Step S120. If the predetermined time has not elapsed (Step S103: NO), the process returns to Step S101.

[0141] Step S104: As in step S102, the mobile terminal 60 determines whether or not it has detected the insertion of a product into the shopping cart 80. If it has detected the insertion of a product (step S104: YES), it proceeds to step S120. If it has not detected the insertion of a product (step S104: NO), this flow chart ends.

[0142] Step S110: Following step S101 (YES), the mobile terminal 60 executes a product registration process (described later), and then this flow chart ends.

[0143] Step S120: Following step S102 (YES), step S103 (YES), and step S104 (YES), the portable terminal 60 executes a reading failure process (described later), and then this flowchart ends.

[0144] [Explanation of the flow chart in Figure 14] The flowchart in FIG. 14 is an example of the product registration process (S110) in FIG. Step S111: The mobile terminal 60 transmits the product registration information to the transaction management device 20. The product registration information includes the product code obtained from the barcode read in step S101 and the cart identification information. Then, the process proceeds to step S112.

[0145] Step S112: Mobile terminal 60 receives the registration completion notification transmitted from transaction management device 20 in response to the transmission of the product registration information in step S111. Then, the process proceeds to step S113.

[0146] Step S113: The mobile terminal 60 updates the product registration screen, for example, as shown in FIG. 10(C).

[0147] [Explanation of the flow chart in Figure 15] The flowchart in FIG. 15 is an example of the read failure process (S120) in FIG. Step S121: The portable terminal 60 judges whether the value of the reread operation instruction flag is "1". The reread operation instruction flag is information indicating whether a reread operation (a re-read operation) has been instructed. The value "0" of the reread operation instruction flag indicates that a reread operation has not yet been instructed in the transaction, and the value "1" of the reread operation instruction flag indicates that a reread operation has already been instructed in the transaction. If the value of the reread operation instruction flag is "1", that is, if a reread operation has already been instructed in the transaction (step S121 (YES)), proceed to step S124. If the value of the reread operation instruction flag is "0", that is, if a reread operation has not yet been instructed in the transaction (step S121 (NO)), proceed to step S122. The re-read operation instruction completed flag may be stored in the memory unit 602 of the mobile terminal 60 (or in another device that can be accessed by the mobile terminal 60, for example, the memory unit 202 of the transaction management device 20). When the re-read operation instruction completed flag is stored in another device, the re-read operation instruction completed flag for each mobile terminal 60 (or customer) may be stored in the other device so that each can be identified.

[0148] Step S122: The portable terminal 60 sets the value of the re-read operation instruction completion flag to “1.” Then, the process proceeds to step S123.

[0149] Step S123: The portable terminal 60 displays a message prompting the user to perform a reading operation, and then the process returns to step S100 in FIG.

[0150] Step S124: The portable terminal 60 sets the value of the re-read operation instruction completion flag to “0.” Then, the process proceeds to step S125.

[0151] Step S125: The mobile terminal 60 displays the preset keys on the display unit 604. The customer can operate the preset keys to register the products. The details of the preset keys will be described later. Then, the process proceeds to step S126.

[0152] Step S126: The mobile terminal 60 judges whether or not a preset key has been operated. In other words, the mobile terminal 60 judges whether or not an operation to register a product has been performed using a preset key has been performed. If a preset key has been operated (step S126: YES), the process returns to step S110 (product registration process) in Fig. 13 and Fig. 14. If a preset key has not been operated (step S126: NO), the process proceeds to step S127.

[0153] Step S127: The mobile terminal 60 judges whether or not a predetermined time has elapsed since the display (display start) of the preset keys in step S125. If the predetermined time has elapsed (step S127: YES), the mobile terminal 60 proceeds to step S130. If the predetermined time has not elapsed (step S127: NO), the mobile terminal 60 returns to step S126.

[0154] Step S130: The mobile terminal 60 determines a classification number (for example, a reserved sub-classification number) of the reserved product. For example, the mobile terminal 60 may determine the reserved sub-classification number as follows.

[0155] [Determination of reserved product classification number (reserved sub-classification number)] (1) When the process transitions from step S102 (YES) in FIG. 13 to the reading failure process (step S120), the reserved subcategory number is determined to be "22." In other words, since the insertion of a product was detected before the predetermined time elapsed, the reserved product is determined to be a reserved product with reserved subcategory number "22" (pseudo scan (short time)). (2) When the process transitions from step S103 (YES) in Fig. 13 to the reading failure process (step S120) and it is determined that the operation is a pseudo scan, the reserved subcategory number is determined to be "21." In other words, the reading operation is permitted until a predetermined time has elapsed, and if it is determined that the operation is a pseudo scan, the reserved product is determined to be a reserved product with reserved subcategory number "21" (pseudo scan (coated, etc.)). (3) When the process transitions from step S103 (YES) in Fig. 13 to the reading failure process (step S120) and it is not determined to be a pseudo scan, the reserved subcategory number is determined to be "23." In other words, the reading operation is permitted until a predetermined time has elapsed, and if it is determined that the operation is not a pseudo scan, the reserved product is determined to be a reserved product with reserved subcategory number "23" (bad barcode). (4) When the process transitions from step S104 (YES) in Fig. 13 to the reading failure process (step S120), the reserved subcategory number is determined to be "24." In other words, since the insertion of a product was detected without recognizing the start of the reading operation, the reserved product is determined to be a reserved product (non-scan-inserted) with the reserved subcategory number "24."

[0156] Further explanation will be given regarding the reserved item with reserved subcategory number "21" (pseudo scan (covered, etc.)) and the reserved item with reserved subcategory number "23" (defective barcode). Depending on whether or not the customer's reading operation until a predetermined time has elapsed is a pseudo scan (specifically, a pseudo scan of covering, etc.), the mobile terminal 60 decides whether or not the reserved item is a pseudo scan with reserved subcategory number "21" (pseudo scan (covered, etc.)) or a reserved item with reserved subcategory number "23" (defective barcode), but whether or not it is a pseudo scan may be determined, for example, as follows.

[0157] The mobile terminal 60 may determine whether or not the scan is a pseudo scan based on a plurality of captured images taken until a predetermined time has elapsed (until step S103 (YES) is reached). (Judgment method 1) The mobile terminal 60 determines that a pseudo-scan has occurred if at least a portion of the barcode is not captured in multiple captured images taken over a specified period of time (for example, if a portion is covered by a finger or the like), or if the barcode is within the imaging range of the imaging unit 606 but at an inappropriate angle, and determines that a pseudo-scan has not occurred if the entire barcode is captured and the angle of the barcode is appropriate. (Judgment method 2) Instead of determination method 1, the mobile terminal 60 may determine that it is a pseudo scan if the object has not changed (for example, the angle or position of the object has changed by more than a predetermined amount) in the multiple captured images taken until a predetermined time has elapsed (i.e., there is no evidence of any attempt to read it) even if the entire barcode is captured in the multiple captured images and the angle of the barcode is appropriate (i.e., there is no evidence of any attempt to read it). In other words, the mobile terminal 60 may determine that it is not a pseudo scan if the entire barcode is captured in the multiple captured images taken until a predetermined time has elapsed, the angle of the barcode is appropriate, and the object has changed in the multiple captured images (i.e., there is evidence of any attempt to read it), and may determine that it is a pseudo scan if not.

[0158] The portable terminal 60 may determine (distinguish) how the process has transitioned to the read failure processing in the process of step S130 (i.e., whether the process has transitioned to the read failure processing from step S102 (YES) in FIG. 13, whether the process has transitioned to the read failure processing from step S103 (YES) in FIG. 13, or whether the process has transitioned to the read failure processing from step S104 (YES) in FIG. 13) as follows. As an example, the portable terminal 60 may set a different flag (with a value of 1) for each of the cases of step S102 (YES) in FIG. 13, step S103 (YES) in FIG. 13, and step S104 (YES) in FIG. 13, and may determine how the process has transitioned to the read failure processing based on which flag is set in the process of step S130.

[0159] In addition, the process for determining the reserved sub-category number when transitioning to read failure processing from step S102 (YES) in Figure 13, the process for determining the reserved sub-category number when transitioning to read failure processing from step S103 (YES) in Figure 13, and the process for determining the reserved sub-category number when transitioning to read failure processing from step S104 (YES) in Figure 13 may each be made into different processes (i.e., by branching the processing flow), and the corresponding reserved sub-category number may be determined (assigned) in each process. In other words, in the process for determining the reserved sub-category number when transitioning to reading failure processing from step S102 (YES) in Figure 13 (classification number determination process A), the reserved sub-category number may be determined to be "22," in the process for determining the reserved sub-category number when transitioning to reading failure processing from step S103 (YES) in Figure 13 (classification number determination process B), the reserved sub-category number may be determined to be "23" or "21," and in the process for determining the reserved sub-category number when transitioning to reading failure processing from step S104 (YES) in Figure 13 (classification number determination process C), the reserved sub-category number may be determined to be "24."

[0160] It is also possible that the transition to the read failure processing before (first time) step S123 in FIG. 15 is different from the transition to the read failure processing after (second time) step S123 in FIG. 15. If the transition to the read failure processing for the first time is different from the transition to the read failure processing for the second time, the second transition (i.e., the newer one) may be adopted to determine the reserved sub-classification number. As an example, in a case where the first transition is from step S104 (YES) in FIG. 13 to the read failure processing and the second transition is from step S102 (YES) in FIG. 13 to the read failure processing (the first time is non-scanning and the second time is short), the second transition (the transition from step S102 (YES) in FIG. 13 to the read failure processing) may be adopted and the reserved sub-classification number may be determined to be "22".

[0161] Step S131: Following step S130, the mobile terminal 60 acquires (extracts) a captured image corresponding to the currently occurring reading failure situation from among the captured images captured by the imaging unit 606. Then, the process proceeds to step S132.

[0162] The captured images acquired by the portable terminal 60 in step S131 will be described. The captured images acquired by the portable terminal 60 are intended to allow the store clerk to visually recognize the reading failure situation that has occurred. For this reason, the format (video, still image) of the captured images acquired by the portable terminal 60, the number of captured images, the time and period for which the captured images are to be acquired, etc. may differ depending on the reading failure situation.

[0163] [Images taken for reserved items with reserved classification numbers "21" to "23"] In the case of reserved products with reserved subcategory numbers "21" to "23" (i.e., when a barcode reading operation has been performed), the mobile terminal 60 acquires captured images that allow recognition of the barcode reading status. In other words, the mobile terminal 60 always captures images using the imaging unit 606 in order to recognize the barcode reading operation and the insertion of the product into the shopping cart 80 as described above, and temporarily stores these images, and extracts captured images that allow recognition of the barcode reading status in step S131. Note that, in the case of reserved products with reserved subcategory numbers "21" to "23" (i.e., when a barcode reading operation has been performed), the mobile terminal 60 may acquire (extract) captured images that allow recognition of the insertion of the product into the shopping cart 80 (images before and after insertion, etc.) in addition to the captured images that allow recognition of the barcode reading status in the case of reserved products with reserved subcategory numbers "21" to "23" (i.e., when a barcode reading operation has been performed).

[0164] [Image captured for reserved items with reserved classification number "24"] In the case of a reserved item with reserved subcategory number "24" (i.e., when the barcode has not been read), the mobile terminal 60 obtains captured images (images before and after insertion, etc.) that enable recognition of the insertion of the item into the shopping basket 80. That is, the mobile terminal 60 always captures images using the imaging unit 606 in order to recognize the barcode reading operation and the insertion of the item into the shopping basket 80 as described above, and temporarily stores these images, and in step S131 extracts captured images (images before and after insertion, etc.) that enable recognition of the insertion of the item into the shopping basket 80.

[0165] Step S132: The portable terminal 60 transmits the unreadable information to the transaction management device 20. The unreadable information includes the captured image acquired in step S131, the reserved sub-category number determined in step S130, and the cart identification information. Then, the process proceeds to step S133.

[0166] Step S133: The portable terminal 60 receives the registration completion notification transmitted from the transaction management device 20 in response to the transmission of the unsuccessful reading information in step S132. Then, the process proceeds to step S134.

[0167] Step S134: The mobile terminal 60 may, for example, update the product registration screen and display the guide image WD2 in a superimposed manner as shown in Fig. 11(C) Then, this flow chart ends.

[0168] As shown in Figures 13 to 15, after displaying a message prompting the user to perform another read operation, if the mobile terminal 60 recognizes the barcode read operation but does not complete the barcode reading normally (succeed) (step S102 (YES), step S103 (YES)), it displays a preset key (step S125) in the read failure process (step S120), and if the product is not registered using the preset key within a predetermined time (step S127 (YES)), it processes the product as a reserved product with reserved subcategory number "21" to "23".

[0169] Furthermore, as shown in Figures 13 to 15, if the mobile terminal 60 detects the insertion of a product without recognizing the barcode reading operation after displaying a message prompting another reading operation (step S104 (YES)), it displays a preset key (step S125) in the reading failure processing (step S120), and if the product is not registered using the preset key within a predetermined time (step S127 (YES)), it processes the product as a reserved product with reserved subcategory number "24".

[0170] In the flow chart shown in Fig. 15, if the first reading is unsuccessful, a second (again) reading is performed, and if the second reading is also unsuccessful, a preset key is displayed, but if the first reading is unsuccessful, a preset key may be displayed without a second reading. For example, whether or not a second reading is performed may be determined depending on the reserved subcategory number. As an example, in the case of a non-scan input with the reserved subcategory number "24", a preset key may be displayed immediately without a second (again) reading, based on or independent of operation.

[0171] [Explanation of the flow chart in Figure 16] Step S201: Transaction management device 20 judges whether or not it has received the product registration information transmitted by mobile terminal 60 in step S111 of Fig. 14. If it has received the product registration information (step S201: YES), it proceeds to step S202. If it has not received the product registration information (step S201: NO), it proceeds to step S211.

[0172] Step S202: The transaction management device 20 judges whether or not the product has been identified. In other words, the transaction management device 20 judges whether or not the product code included in the product registration information is stored in the product file (product master). If the product has been identified (step S202: YES), proceed to step S203. If the product has not been identified (step S202: NO), proceed to step S213.

[0173] Step S203: The transaction management device 20 identifies the cart information. That is, the transaction management device 20 identifies the cart information that corresponds to the cart identification information included in the product registration information. Then, the process proceeds to step S204.

[0174] Step S204: The transaction management device 20 updates the cart information identified in step S203. That is, the transaction management device 20 updates the registered product information (total, registered product N) in the cart information. As a result, one product is registered in the cart information. Then, the process proceeds to step S205.

[0175] Step S205: The transaction management device 20 transmits a registration completion notification to the mobile terminal 60. The mobile terminal 60 receives the registration completion notification in step S112 of Fig. 14. Then, this flow chart ends.

[0176] Step S211: The transaction management device 20 judges whether or not it has received the read failure information transmitted by the portable terminal 60 in step S132 of Fig. 15. If it has received the read failure information (step S211: YES), it proceeds to step S213. If it has not received the read failure information (step S211: NO), this flow chart ends.

[0177] Step S213: The transaction management device 20 identifies the cart information. That is, the transaction management device 20 identifies the cart information that corresponds to the cart identification information included in the unread information. Then, the process proceeds to step S214.

[0178] Step S214: The transaction management device 20 updates the cart information identified in step S213. That is, the transaction management device 20 updates the reserved item information (total, N reserved items) in the cart information. As a result, one item (reserved item) is registered in the cart information. Then, the process proceeds to step S215. The transaction management device 20 can refer to information showing the relationship between the reserved major category number and the reserved minor category number (for example, information such as that shown in FIG. 8), and recognizes the reserved major category number that is higher than the reserved minor category number included in the unreadable information.

[0179] Step S215: The transaction management device 20 transmits a registration completion notification to the mobile terminal 60. The mobile terminal 60 receives the registration completion notification in step S133 of Fig. 15. Then, this flow chart ends.

[0180] If the transaction management device 20 is unable to identify the product (step S202: NO), it registers a reserved product (NON-FILE) with reserved major classification number "1" when updating the cart information (step S214).

[0181] Furthermore, when updating the cart information, the transaction management device 20 also registers reserved products (specific products) classified under reservation major category number "3", i.e., reserved products with reservation minor category number "31" (age verification products), reserved products with reservation minor category number "32" (medicines), and reserved products with reservation minor category number "33" (anti-theft tag products). For example, the mobile terminal 60 may transmit product registration information for age verification products (medicines and anti-theft tag products as well) in the same way as other products that do not fall under the category of specific products (step S111 in FIG. 14), and the transaction management device 20 may register the reserved products (specific products) in the processing of step S204 (or in the processing of step S214).

[0182] Furthermore, when updating the cart information, transaction management device 20 similarly registers reserved items (cancelled items) classified as reserved major classification number "4." For example, mobile terminal 60 may transmit item registration information (item registration information including information indicating cancellation, also referred to as registration cancellation information) in a cancellation process (cancellation process, not shown), and transaction management device 20 may register the reserved item (cancelled item) in the process of step S204 (or in the process of step S214).

[0183] 17 and 18 are diagrams showing an example of a re-read instruction screen and a preset key screen (preset key small screen) according to this embodiment. Display of the preset keys and the like will be described with reference to FIGS.

[0184] FIG. 17 shows a scene in which a customer K has purchased one "XX potato" and two "XX tea" and then purchases one "XX chocolate."

[0185] FIG. 17(A) shows a scene where one "XX potato" and two "XX tea" are registered (all successfully read). In FIG. 17(A), the mobile terminal 60 captures the inside of the shopping basket 80. In the captured image of FIG. 17(A), there are an object of "XX potato" (symbol a) and an object of "XX tea" (symbol b). From the scene of FIG. 17(A), if the customer K performs an operation to read the barcode of "XX chocolate" and puts the "XX chocolate" into the shopping basket 80 without successfully reading it (if step S102 (YES) in FIG. 13 is reached, or if step S103 (YES) is reached), the captured image immediately after the insertion will be as shown in FIG. 17(B). In the captured image of FIG. 17(B), there are an object of "XX potato" (symbol a), an object of "XX tea" (symbol b), and an object of "XX chocolate" (symbol c).

[0186] Next, the mobile terminal 60 displays a re-read instruction screen WD31 as shown in Fig. 17(C) (step S123 in Fig. 15). The re-read instruction screen WD31 in Fig. 17(C) displays a message (symbol e) urging the user to perform a read operation, indicating that registration has failed (symbol d). The re-read instruction screen WD31 in Fig. 17(C) also displays an OK button BT51 to be operated when performing a read operation again in accordance with the message, and a "No purchase" button BT53 to be operated when canceling the purchase of the product (XX chocolate).

[0187] When the OK button BT51 is operated on the reread instruction screen WD31, the reread instruction screen WD31 is cleared, and the process returns to step S100 in FIG. 13 as shown in the flowchart in FIG.

[0188] If the “Do not purchase” button BT53 is operated on the re-read instruction screen WD31, the re-read instruction screen WD31 is cleared, and although this is omitted in the flowchart shown in FIG. 15, a cancellation process (cancellation process, not shown) is executed for the product, and the process ends.

[0189] In the second reading operation, if reading is unsuccessful as in the first reading operation, the mobile terminal 60 displays the preset key screen WD41 as shown in FIG. 17(D) (step S125 in FIG. 15).

[0190] The preset key screen WD41 in Fig. 17(D) displays a message (symbol d) indicating that registration (reading) has failed and a message (symbol f) prompting the user to select a product using a button (preset key). In addition, the preset key screen WD41 in Fig. 17(D) has a plurality of preset keys BT60 and a preset key display switching button BT61 (a button for displaying the next plurality of preset keys BT60 and a button for displaying the previous plurality of preset keys BT60. Either one is used in the case of the first or last). In addition, the preset key screen WD41 in Fig. 17(D) has a button BT62 for selecting the product (XX chocolate) using a preset key that is operated when the user intends to purchase the product (XX chocolate) but is unable to find a preset key corresponding to the product (XX chocolate), and a button BT63 for not purchasing the product (XX chocolate) that is operated to cancel the purchase of the product (XX chocolate).

[0191] When any of the preset keys BT60 is operated on the preset key screen WD41, the preset key screen WD41 is cleared, and the process returns to step S110 (product registration process) in FIG. 13 and FIG. 14, as shown in the flow chart in FIG. 15. This causes the product corresponding to the operated preset key BT60 to be registered. Specifically, in this example, the preset key BT60 corresponding to XX chocolate is operated on the preset key screen WD41. The mobile terminal 60 acquires the product code of XX chocolate based on the operation of the preset key BT60 corresponding to XX chocolate. When the mobile terminal 60 acquires the product code of XX chocolate based on the operation of the preset key BT60 corresponding to XX chocolate, the mobile terminal 60 executes the product registration process (step S110) and registers XX chocolate, in the same manner as when the reading of the barcode attached to XX chocolate is successful (i.e., when the product code of XX chocolate is acquired by reading the barcode).

[0192] When the display switch button BT61 is operated on the preset key screen WD41, the preset keys BT60 displayed on the preset key screen WD41 are switched. That is, the mobile terminal 60 switches the preset keys BT60 displayed on the preset key screen WD41 based on the operation of the display switch button BT61.

[0193] When the button BT62 that cannot be selected on the preset key screen WD41 is operated, the preset key screen WD41 is cleared, and the process proceeds to step S130, which is omitted in the flowchart shown in Fig. 15. In other words, the product (XX chocolate) is processed as a reserved product, just like when a predetermined time has elapsed (step S127 (YES)).

[0194] When the "Do not purchase" button BT63 is operated on the preset key screen WD41, the preset key screen WD41 is cleared, and although this is omitted in the flowchart shown in FIG. 15, a cancellation process (cancellation process, not shown) is executed for the product, and the process ends.

[0195] Figure 18 shows a scene where a customer K has secured one "XXX potato" and two "XX tea" and then purchases one "apple." Note that the "apple" does not have a barcode.

[0196] Like FIG. 17(A), FIG. 18(A) shows a scene in which one "XX potato" and two bottles of "XX tea" have been registered (all successfully read). If customer K adds an "apple" to shopping basket 80 from the scene in FIG. 18(A) (if step S104 (YES) in FIG. 13 is selected), the captured image immediately after the addition will be as shown in FIG. 18(B). In the captured image in FIG. 18(B), there are an "XX potato" object (symbol a), a "XX tea" object (symbol b), and an "apple" object (symbol g).

[0197] Next, the mobile terminal 60 displays a re-read instruction screen WD32 as shown in FIG. 18(C) (step S123 in FIG. 15). The re-read instruction screen WD32 in FIG. 18(C) displays a message indicating that registration has failed (symbol d) and a message prompting a reading operation (symbol e). In the case of loose products such as fruits and vegetables, a label with a barcode may be placed on the display stand, and the number of items may be input in the app by scanning the label. When the label is placed, a message prompting a reading operation of the barcode on the label may be displayed. In addition, the re-read instruction screen WD32 in FIG. 18(C) includes an OK button BT51 to be operated when performing a reading operation according to the message, a NO BARCODE button BT52 to be operated when the product (apple) does not have a barcode, and a DON'T PURCHASE button BT53 to be operated when the purchase of the product (apple) is canceled.

[0198] Comparing the reread instruction screen WD31 in FIG. 17(C) with the reread instruction screen WD32 in FIG. 18(C), FIG. 17 shows a scene where the barcode reading has failed (although the presence of the barcode was confirmed), so the no barcode button BT52 present on the reread instruction screen WD32 in FIG. 18(C) is not located on the reread instruction screen WD31 in FIG. 17(C).

[0199] When the OK button BT51 is operated on the reread instruction screen WD32, the reread instruction screen WD32 is cleared, and the process returns to step S100 in Fig. 13, as shown in the flowchart in Fig. 15. In the example of Fig. 18, since the apple does not have a barcode attached, customer K does not operate the OK button BT51. However, if the apple had a barcode attached, customer K might operate the OK button BT51.

[0200] When the no barcode button BT52 is operated on the reread instruction screen WD32, the reread instruction screen WD32 is cleared, and although this is omitted in the flowchart shown in Fig. 15, the process proceeds to step S124 in Fig. 15. In other words, if the product does not have a barcode, even if the process returns to step S100 in Fig. 13 and a reading operation is performed, the reading will not be successful, so the process simply proceeds to step S124 in Fig. 15.

[0201] If the “Do not purchase” button BT53 is operated on the re-read instruction screen WD32, the re-read instruction screen WD32 is cleared, and although this is omitted in the flowchart shown in FIG. 15, a cancellation process (cancellation process, not shown) is executed for the product, and the process ends.

[0202] Based on the operation of the no barcode button BT52, the mobile terminal 60 displays the preset key screen WD42 as shown in Fig. 18(D) (step S125 in Fig. 15). Note that, even if the OK button BT51 is operated in a case where the apple has a barcode attached thereto, and the re-reading operation produces the same result as the first time, the mobile terminal 60 displays the preset key screen WD42 as shown in Fig. 18(D) (step S125 in Fig. 15).

[0203] The preset key screen WD42 in Fig. 18(D) displays a message (symbol d) indicating that registration (reading) has failed, and a message (symbol f) prompting the user to select a product using a button (preset key). In addition, the preset key screen WD42 in Fig. 18(D) has a plurality of preset keys BT60 (preset key BT60a corresponding to apples, preset key BT60b corresponding to pears) and a preset key display switching button BT61. In addition, the preset key screen WD42 in Fig. 18(D) has a "cannot select" button BT62 that is operated when the user intends to purchase the product (apples) but is unable to select the product (apples) using a preset key for reasons such as not being able to find a preset key corresponding to the product (apples), and a "do not purchase" button BT63 that is operated when the user wishes to cancel the purchase of the product (apples).

[0204] For example, when the preset key BT60a corresponding to apple is operated on the preset key screen WD42, the preset key screen WD42 is cleared, and the process returns to step S110 (product registration process) in Fig. 13 and Fig. 14 as shown in the flowchart in Fig. 15. As a result, apple corresponding to the operated preset key BT60a is registered.

[0205] When the display switch button BT61 is operated on the preset key screen WD42, the preset keys BT60 displayed on the preset key screen WD42 are switched. That is, the mobile terminal 60 switches the preset keys BT60 displayed on the preset key screen WD42 based on the operation of the display switch button BT61.

[0206] When the button BT62 that cannot be selected on the preset key screen WD42 is operated, the preset key screen WD42 is cleared, and although omitted in the flowchart shown in Fig. 15, the process proceeds to step S130. In other words, the product (apple) is processed as a reserved product, similar to the case when the predetermined time has elapsed (step S127 (YES)).

[0207] When the "Do not purchase" button BT63 is operated on the preset key screen WD42, the preset key screen WD42 is cleared, and although this is omitted in the flowchart shown in FIG. 15, a cancellation process (cancellation process, not shown) is executed for the product, and the process ends.

[0208] [Preset keys to display] The preset keys displayed on the preset key screen WD41 (WD42) will be described below. The mobile terminal 60 may display the preset keys in any one of the following display modes 1 to 4, for example.

[0209] (Display mode 1) For example, the mobile terminal 60 displays preset keys for all the products. Specifically, as shown in the preset key screen WD41 of Fig. 17(D) , the mobile terminal 60 displays preset keys for some of the products, and displays other preset keys in response to the operation of the display switching button BT61. In the display mode 1, the number of preset keys to be displayed is very large. Therefore, there is a possibility that the customer cannot select a preset corresponding to the product to be purchased. In such a case, the customer may operate, for example, the button BT62 that cannot be selected in order to proceed with the process.

[0210] (Display mode 2) The mobile terminal 60 displays a preset key for a specific product. Specifically, as shown in the preset key screen WD42 of FIG. 18(D), the mobile terminal 60 displays a preset key for a specific product and does not display a preset key for other products. The specific product may be a product sold individually, such as fruits and vegetables (whether or not a barcode is attached). In other words, the specific product may be a product sold in a predetermined manner (e.g., sold individually). The specific product may also be a product not equipped with a barcode (whether or not a product sold individually). In the display mode 2, the preset key displayed is the preset corresponding to the specific product whether the specific product is registered or not. That is, when the specific product is registered, the preset key corresponding to the product to be purchased (specific product) is displayed, but when the product other than the specific product is registered, the preset key corresponding to the product to be purchased (product other than the specific product) is not displayed. Therefore, in the latter case, the customer operates, for example, the unselectable button BT62. Note that a button for displaying preset keys for products other than the specific product may be provided, and in the latter case, the preset key for the product other than the specific product may be displayed by operating the button for displaying preset keys for products other than the specific product.

[0211] (Display mode 3) The mobile terminal 60 displays a preset key according to a position in the store (the position of the mobile terminal 60, or the position of the customer using the mobile terminal 60). Specifically, the mobile terminal 60 captures (specifies, estimates) the position of each customer (mobile terminal 60) in the store using GPS, wireless LAN, wireless tag, beacon, etc., and displays a preset key according to the captured position. For example, if the captured position is the alcohol section, a preset key related to alcohol may be displayed, and if the captured position is the daily necessities section, a preset key related to daily necessities may be displayed. Note that the preset key according to the captured position may be preferentially displayed (the preset key according to the captured position may be displayed on the first page, and other preset keys may be displayed depending on the operation).

[0212] (Display mode 4) The mobile terminal 60 may determine the preset key to be displayed based on image recognition. In other words, the mobile terminal 60 may display a preset key narrowed down from a large number of preset keys based on image recognition. For example, if the product is round and red, an apple or the like may be displayed as shown in the preset key screen WD42 of FIG. 18(D).

[0213] The display modes 1 to 4 may be appropriately combined. Also, which of the display modes 1 to 3 is adopted may be changed depending on the customer.

[0214] [After payment transfer instructions] When the customer has finished registering all the products to be purchased, he or she performs a settlement instruction operation and has the settlement device 40 read the two-dimensional code displayed on the mobile terminal 60. After reading the two-dimensional code, the settlement device 40 requests the transaction management device 20 to calculate the subtotal amount, as shown as step S13 in Fig. 9. Here, when requesting calculation of the subtotal amount, the settlement device 40 of this embodiment requests settlement information to be used in the settlement process using the settlement screen.

[0215] In response to a request for settlement information, the transaction management device 20 identifies the corresponding cart information and generates settlement information based on the identified cart information. The settlement information includes various information in the cart information (e.g., some or all of registered product information, pending product information, cancellation information, etc.). For example, the settlement information includes image data (captured image) related to the pending product information. The transaction management device 20 transmits the generated settlement information to the settlement device 40. Upon receiving the settlement information, the settlement device 40 displays a settlement screen reflecting the contents of the received settlement information on the display unit 405.

[0216] FIG. 19 shows an example of a settlement screen displayed on the display unit 405 of the settlement device 40. The checkout screen in the figure includes a registered product list area AR3. The registered product list area AR3 is an area that presents a list of products registered by the mobile terminal 60.

[0217] 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 example shown in the figure, since the registered products include six reserved products, a reserved product list area AR31 including list items of the six 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 arranged to differ from the list items of other products, for example in terms of background color, etc.

[0218] The list items in the registered product list area AR3 show the product name of the corresponding product, the registered quantity, the price according to the registered quantity, etc. In addition, for example, the list items corresponding to the reserved product may show the classification number (reserved major classification number, reserved minor classification number, or both) and classification name (reserved major classification name, reserved minor classification name, or both) of the reserved product.

[0219] A call button BT31 is arranged in each list item of the reserved product in the reserved product list area AR31. Each call button BT31 shows the reserved subcategory name to which the corresponding product falls.

[0220] Furthermore, a customer monitor area AR32 is arranged on the settlement screen. The customer monitor area AR32 is an area in which an image captured by the imaging unit 416 is displayed as a monitor image in real time. In the customer monitor area AR32, the state of the customer's hands as he or she operates the settlement device 40 for settlement is displayed in real time. By the settlement device 40 displaying such an image in the customer monitor area AR32, the customer becomes aware that his or her state is being imaged, which has the effect of preventing fraudulent acts by the customer when making a payment. The settlement device 40 may be configured to store (save) the image used for display in the customer monitor area AR32.

[0221] Here, as shown in the figure, when the reserved item list area AR31 is formed in the registered item list area AR3 on the checkout screen, the clerk needs to perform an operation to process the reserved items. When the checkout screen with the reserved item list area AR31 formed in this way is displayed, the checkout device 40 executes a call to the clerk to have the clerk perform an operation to process the reserved items. As a call to the clerk, for example, the checkout device 40 may display a display such as a sign pole in a predetermined manner, or send a notice of the call to the clerk to a terminal device carried or monitored by the clerk. The clerk who goes to the checkout device 40 in response to the call to the clerk performs an operation to process the reserved items corresponding to each list item shown in the reserved item list area AR31 of the displayed checkout screen.

[0222] When processing the reserved item No. 1, the store clerk operates the call button BT31 in the list item of the reserved item to be processed. In this case, the store clerk operates the call button BT31 of the list item in the first row corresponding to canned beer in the reserved item list area AR31. In response to the operation of the call button BT31, a reserved item processing screen for processing the reserved item corresponding to the list item including the operated call button BT31 is displayed on the checkout screen. Note that the entire list item of the reserved item to be processed may be touch operable.

[0223] For example, when the store clerk operates the call button BT31 of the list item in the first row corresponding to a can of beer which is an age verification product, a reserved product processing screen for the can of beer is displayed on the checkout screen.

[0224] 20 is an example of a reserved product processing screen AR4 for a canned beer, which is an age verification product. On the reserved product processing screen AR4, a product information area AR41, an input operation area AR42, a register button BT41, and a cancel button BT42 are arranged.

[0225] The product information area AR41 is an area that shows information about the corresponding reserved product. The product information area AR41 in the figure shows the product name, product code, price, registered quantity, etc. In the case of an age verification product, the content displayed in the product information area AR41 reflects the information of the corresponding product (reserved product information) included in the payment information.

[0226] The input operation area AR42 is an area where a software keyboard for inputting product information in the product information area AR41 is arranged. The input operation area AR42 is capable of switching between a keyboard with a key arrangement corresponding to numeric input and a keyboard with a key arrangement corresponding to character input, depending on the operation. In addition, a preset call key, for example, labeled "preset", is arranged in the input operation area AR42. By operating the preset call key, a preset key screen is displayed on which preset keys corresponding to each product are arranged. By operating a preset key arranged in the preset key screen (preset key area), the store clerk can input product information corresponding to the operated preset key into the product information area AR41.

[0227] The REGISTER button BT41 is a button for canceling the pending registration of the corresponding product and registering it as a purchase target for the customer. The CANCEL button BT42 is a button for canceling the registration of a product whose registration is in a pending state.

[0228] For example, the store clerk checks the customer's age, and if there are no problems, presses the registration button BT41 to confirm the registration of the canned beer. This causes the settlement device 40 to cancel the pending registration state of the canned beer and process it to include it in the registered products. Alternatively, if the store clerk determines that the canned beer should not be registered, he or she presses the cancel button BT42 to cancel the registration of the canned beer and collects the canned beer product.

[0229] In addition, for an unreadable product, the call button BT31 in the list item of the reserved product list area AR31 displays, for example, "Non-scan." When the store clerk processes the unreadable product, he or she operates the call button BT31 that displays "Non-scan" in the list item of the unreadable product.

[0230] For example, in the case of a reserved item classified as "NON-FILE," in the initial display state of the reserved item processing screen AR4, no item information is shown in the item information area AR41. In this case, the store clerk can register the item by inputting a numeric string as the item code or a character string as the item name in the item information area AR41 by performing a numeric input operation or a character input operation in the input operation area AR42. The item information registered in this manner is transmitted to the transaction management device 20. The transaction management device 20 synchronizes the cart information by updating the information of the corresponding item in the cart information (reserved item information) from the "NON-FILE" state so that the information entered in the item information area AR41 is reflected.

[0231] In addition, the reserved product processing screen may display the classification number (reserved major classification number, reserved minor classification number, or both) and the classification name (reserved major classification name, reserved minor classification name, or both).

[0232] 21 is an example of a reserved product processing screen AR4 for processing an unreadable product, which is displayed in response to operating the call button BT31 displaying "Non-scan." In the initial display state of the reserved product processing screen AR4 corresponding to an unreadable product, no information about the product has been acquired yet, so no information about the product is presented in the product information area AR41, as shown in the figure.

[0233] Further, the reserved product processing screen AR4 corresponding to the unsuccessfully read product has a captured image area AR43 arranged in addition to a product information area AR41, an input operation area AR42, a registration button BT41, and a cancel button BT42.

[0234] A captured image corresponding to the occurrence of the corresponding reading failure state is displayed in the captured image area AR43. This captured image is acquired by the mobile terminal 60 in step S131 of FIG.

[0235] Specifically, the captured image in the captured image area AR43 in the figure shows a reading failure state classified as a non-scan insertion. In the captured image area AR43 in the figure, two captured images G11 and G12 are arranged. The captured image G11 is a captured image showing a state before an additional product is added to the shopping basket 80. The captured image G12 is an image showing a state after the captured image G11 when an additional product is added to the shopping basket 80.

[0236] By looking at the captured image in captured image area AR43 in the figure, the store clerk can understand that the unreadable product to be processed was added to the shopping cart 80 without having its barcode read. Furthermore, in captured image G12, a frame FL is placed in the area of ​​the added product. This allows the store clerk to easily identify what the added product is without being registered. The identification of the added product and the placement of the frame FL may be performed by either the mobile terminal 60 or the settlement device 40.

[0237] Furthermore, if the store clerk wants to check the captured image in the captured image area AR43 in more detail, the store clerk can perform a captured image enlargement operation, for example, by tapping on any position in the captured image area AR43. In response to the captured image enlargement operation being performed, the settlement device 40 places an enlarged captured image area AR431 on the reserved product processing screen AR4, as shown in Fig. 22. The enlarged captured image area AR431 can be erased (closed) in response to a predetermined operation.

[0238] Returning to Fig. 21 for explanation, the store clerk confirms with the customer whether or not they wish to purchase the corresponding unreadable product. If the customer does not wish to purchase the product, the store clerk operates the cancel button BT42 and collects the corresponding unreadable product. If the customer wishes to purchase the product, the store clerk operates the input operation area AR42 to input product information into the product information area AR41, and then operates the register button BT41 to register the product.

[0239] Moreover, the pending product processing screen AR4 in FIG. 23 shows an example of a case where the unsuccessfully read product is classified as a "pseudo scan." In the captured image area AR43 in the same figure, one captured image is displayed. The captured image in the captured image area AR43 displayed in this way shows that when the unsuccessfully read situation occurred, the image was captured with part of the barcode hidden by a finger. By looking at the captured image in the captured image area AR43, the store clerk can understand that the unsuccessfully read product to be processed is classified as a pseudo scan.

[0240] Also in this case, by performing an operation on the captured image area AR43, as shown in FIG. 24, it is possible to display an enlarged captured image area AR431 on the reserved product processing screen AR4.

[0241] In this case, the store clerk will also confirm with the customer whether or not he / she wishes to purchase the corresponding unreadable product, and will register or cancel the product depending on whether or not the customer wishes to purchase it.

[0242] The pseudo scan also includes a situation where the barcode is not included in the imaging range of the imaging unit 606 even when the product is held over the imaging range of the imaging unit 606. In this case, the captured image area AR43 may be configured to display a captured image in which part of the product is included in the imaging range but the barcode is not included in the imaging range.

[0243] The pseudo scan also includes a situation where a product passes through the imaging range of the imaging unit 606 at a speed that makes it impossible to read the product code. In this case, the captured image area AR43 may display a still image captured when the product passes through the imaging range, or a moving image captured when the product passes through the imaging range.

[0244] An example of a processing procedure executed by the settlement device 40 in relation to displaying the reserved item processing screen will be described with reference to the flowchart of Fig. 25. It is assumed that the settlement device 40 is displaying the settlement screen (Fig. 19) at the start of the flowchart of Fig. 25.

[0245] Step S301: While the settlement screen is displayed, the settlement device 40 judges whether or not an operation to specify a reserved product to be processed (reserved product specification operation) has been performed. If a reserved product specification operation has been performed (step S301: YES), the process proceeds to step S302. If a reserved product specification operation has not been performed (step S301: NO), the process returns to step S301.

[0246] Step S302: The settlement device 40 judges whether the reserved product designated by the reserved product designation operation is an incompletely read product (reserved product with reserved subcategory number "21" to "24"). If it is an incompletely read product (step S302: YES), proceed to step S303. If it is not an incompletely read product (step S302: NO), proceed to step S304.

[0247] Step S303: The settlement device 40 generates a reserved item processing screen including a captured image area AR43 for the reserved item designated as the processing target (reserved items with reserved subcategory numbers "21" to "24" corresponding to the unreadable item). The settlement device 40 may obtain the captured image of the captured image area AR43 from the reserved item information of the corresponding item in the settlement information. The settlement device 40 displays the generated reserved item processing screen. Then, this flowchart ends.

[0248] Step S304: The settlement device 40 generates a reserved product processing screen that does not include the captured image area AR43 for the reserved products designated as the processing target (reserved products with reserved subcategory numbers "11", "31" to "33", and "41" that do not correspond to unreadable products). The settlement device 40 displays the generated reserved product processing screen. Then, this flowchart ends.

[0249] <Modification> A modification of this embodiment will now be described.

[0250] [First Modification] In the above embodiment, an example is given in which one or two captured images (FIGS. 21 and 23) are presented in the captured image area AR43 when the reserved product is an insufficiently read product. However, the number of captured images presented in the captured image area AR43 may be three or more.

[0251] 26 shows an example in which three captured images G11, G12, and G13 are arranged in the captured image area AR43 of the reserved product processing screen AR4. The reserved product processing screen AR4 in the same figure shows an example in which the unreadable product to be processed is classified as a non-scanned input.

[0252] The captured images G11, G12, and G13 in the figure show the following state. In the captured image area AR43, the captured images G11, G12, and G13 are arranged in this order from left to right. The arrangement order of the captured images G11, G12, and G13 corresponds to the time lapse in which the images were captured. The first captured image G11 is an image of the inside of the shopping cart 80 before the target unreadable product is added. The second captured image G12 is an image of the process in which the captured image G11 changes to the next third captured image G13. The third captured image G13 is an image of the state in which the target unreadable product is added to the shopping cart 80. The second captured image G12 may be extracted from the captured images including the product to be added, for example, or may be an image captured at a time determined to be exactly halfway between the times when the captured images G11 and G13 are captured. Also in the captured image G13, a frame FL is placed on the part of the product that has been added to the shopping cart 80.

[0253] [Second modified example] In the above embodiment, the display surface of the display unit 405 of the settlement device 40 is horizontally long. However, the display surface of the display unit 405 of the settlement device 40 may be vertically long.

[0254] FIG. 27(A) shows an example of a checkout screen displayed on display unit 405 with a vertically long display screen corresponding to this modified example. In the figure, the same parts as in FIG. 19 are given the same reference numerals. As can be seen by comparing the figure with FIG. 19, the information presented as the checkout screen is similar, but the layout of the information presented on the checkout screen is different in accordance with the fact that the size of the display screen is vertically long. However, the checkout screen in FIG. 27(A) also has a pending product list area AR31 including list items of pending products in the upper left corner of the registered product list area AR3, and the background color, etc. is different from the list items other than the pending products, similar to the checkout screen in FIG. 19.

[0255] In this modification, for example, the reserved item list area AR31 in Fig. 27(A) can be enlarged to be displayed as an enlarged reserved item list area AR311 as shown in Fig. 27(B). The operation to display the enlarged reserved item list area AR311 may be an operation of touching any position within the reserved item list area AR31. Alternatively, it may be an operation of touching the reserved item count area AR33 arranged on the checkout screen in Fig. 27(A).

[0256] By displaying the enlarged pending product list area AR311 in this manner, the store clerk can easily see the list items of the pending products and can easily understand what pending products are available. Also, for example, depending on the arrangement position of the display unit 405 in the settlement device 40, the position of the display unit 405 may be high, and particularly when the display surface of the display unit 405 is vertically long, it may be difficult to operate the upper side of the display surface of the display unit 405. Therefore, in the example of FIG. 27(B), the enlarged pending product list area AR311 is arranged on the lower side of the display surface. This makes it easier for the store clerk to operate the enlarged pending product list area AR311.

[0257] When the store clerk performs processing for a reserved item, the clerk operates the call button BT31 arranged on the list item of the reserved item to be processed among the list items in the enlarged reserved item list area AR311 displayed as in Fig. 27(B). In response to the operation of the call button BT31, a reserved item processing screen AR4 is displayed in place of the enlarged reserved item list area AR311 as shown in Fig. 27(C). The reserved item processing screen AR4 displayed in this way is for processing the reserved item indicated by the list item of the operated call button BT31.

[0258] Furthermore, if the reserved product to be processed is an unreadable product, the settlement device 40 displays the captured image area AR43 on the same screen as the reserved product processing screen AR4, as shown in Fig. 27(C). Note that the figure shows an example in which one image is displayed in the captured image area AR43. However, even in the case of such a vertically long screen, a predetermined number of captured images may be displayed in the captured image area AR43 according to the unreadable status (according to the reserved minor classification number), as shown in Figs. 21 and 26.

[0259] Also, in the example of FIG. 21 etc., the captured image area AR43 was arranged in the reserved item processing screen AR4. In contrast, in FIG. 27(C), the captured image area AR43 is not included in the reserved item processing screen AR4 in accordance with the vertically long display surface of the display unit 405. This allows the captured image area AR43 to be enlarged and arranged to a larger size than when arranged in the reserved item processing screen AR4, making it easier to see the captured image. Also, as shown in FIG. 27(C), on the vertically long display surface, the captured image area AR43 is arranged on the upper side, and the reserved item processing screen AR4 is arranged on the lower side. This makes it easier for the store clerk to operate the reserved item processing screen AR4.

[0260] [Third Modification] In the above embodiment, the captured image area AR43 is arranged on the pending product processing screen for processing pending products that have not been read correctly, and the captured image area AR43 is not arranged on the pending product processing screen for pending products that have not been read correctly. However, in this modified example, the captured image area AR43 may be arranged on the pending product processing screen for pending products that have not been read correctly. In this case, the mobile terminal 60 may transmit product registration information including the captured image for registered products whose barcodes have been successfully read.

[0261] [Fourth Variation] The captured image area AR43 may be displayed as an independent screen different from the reserved item processing screen, for example, in response to an operation of the settlement device 40 by a store clerk.

[0262] [Fifth Modification] In addition, when the transaction start instruction button BT10 arranged on the start screen of FIG. 10(A) is operated to start product registration, the mobile terminal 60 may display a warning screen informing the customer in advance that "images at the time of product registration may be displayed on the settlement device". By displaying such a warning screen, for example, fraudulent product registration can be deterred. Alternatively, instead of the warning screen, the mobile terminal may display a consent screen to confirm the customer's consent to "images at the time of product registration may be displayed on the settlement device". In the consent screen, buttons for accepting an operation to confirm intention, such as a "Yes" button and a "No" button, are arranged. If the "Yes" button is operated, the customer may be treated as a customer who does not commit fraud, and the cancellation may be confirmed as it is without registering the canceled product as a reserved product.

[0263] [Sixth Modification] In the above embodiment, a reading failure situation where the barcode is not successfully read is treated as a product registration error. In this modified example, in addition to a reading failure situation where the barcode is not successfully read, for example, a situation where the barcode is successfully read but the target product cannot be added to the shopping cart 80 may also be treated as a product registration error. Note that, for example, rice over a certain weight or canned drinks in units of six are often placed at the bottom of the cart. Therefore, for such products, even if it is detected that they cannot be added to the shopping cart 80, they may not be treated as a product registration error.

[0264] [Seventh Variation] For example, due to a communication error or a communication speed limit set on the mobile terminal 60, when the unreadable information is sent in step S132 of FIG. 15, the captured image may not be sent to the transaction management device 20. In such a case, the transaction management device 20 may receive the unreadable information including the reserved subcategory number but not the captured image. Alternatively, the mobile terminal 60 may resend the unreadable information not including the captured image, so that the transaction management device 20 can receive the unreadable information including the reserved subcategory number but not the captured image. In this way, even in the case of a communication error or a communication speed limit set on the mobile terminal 60, the transaction management device 20 may register at least the reserved subcategory number of the unreadable product in the cart information as much as possible. As a result, the settlement device 40, by using settlement information based on the cart information, can display a pending product processing screen for the unreadable product as shown in Fig. 21, for example, although no captured image is displayed in the captured image area AR43. In this case, a message that can inform the store clerk that the unreadable product is a product, such as "Are there any products that were not scanned?", may be displayed in the blank area of ​​the pending product processing screen where the captured image area AR43 is not displayed.

[0265] [Eighth Modification] The occurrence of the reading failure may be displayed on a terminal (store operating terminal) operating in the store other than the settlement device 40, such as the transaction status management device 50. For example, the transaction status management device 50, which is one of the store operating terminals, can manage the status of each transaction in the store by communicating with the transaction management device 20, for example. Thus, when a pending product is registered, the transaction status management device 50 may acquire information identifying the customer to whom the pending product corresponds, product information of the target product, amount information, etc. at the time of registration of the pending product, and display the acquired information. Then, for example, when a store clerk performing management work using the transaction status management device 50 confirms that there is no problem with the displayed product, the store clerk may perform an operation such as canceling the registration as a pending product and re-registering it as a normal product.

[0266] [Ninth Variation] The imaging device used for product registration is not particularly limited as long as it is capable of reading the barcode of the product, is capable of capturing an image of the contents of the shopping basket 80 or the like, and is capable of outputting the captured image to the mobile terminal 60 or the like. For example, such an imaging device may be capable of capturing an image of the inside of a customer's own bag, instead of the shopping basket 80 provided by the store.

[0267] [Tenth Modification] The mobile terminal 60 may be held by the customer to register the product without being set in the shopping cart 70. In this case, it is sufficient that the insertion of the product into the shopping cart 70 is detected. For example, a device (terminal) equipped with an imaging means capable of detecting the insertion of the product into the shopping basket 80 (shopping bag 90) may be installed, or a device equipped with a weighing means capable of detecting the insertion of the product into the shopping basket 80 (shopping bag 90) may be installed. Even in a mode in which the insertion of the product into the shopping cart 70 is not detected (a mode in which no device other than the mobile terminal 60 is used), the mobile terminal 60 cannot execute the transition to the reading failure process from step S102 (YES) in FIG. 13 related to the insertion of the product, but can execute the transition to the reading failure process from step S103 (YES) in FIG. 13 not related to the insertion of the product. That is, at least the reserved product with the reserved subcategory number "21" (pseudo scan (covered, etc.)) and the reserved product with the reserved subcategory number "23" (bad barcode) can be recognized.

[0268] [Eleventh Modification] In the above embodiment, the preset key is not displayed in the first reading failure state, and is displayed in the second reading failure state (FIG. 15), but the preset key may be displayed in the first reading failure state. For example, the processes of steps S121 to S124 in FIG. 15 may not be performed. Alternatively, the preset key may not be displayed in the Nth reading failure state (N is an integer of 2 or more), and may be displayed in the (N+1)th reading failure state. In this case, instead of a flag (re-read operation instruction completion flag) indicating whether or not reading has been performed after the reading failure state, a counter that counts the number of times reading has been performed after the reading failure state may be used. The number of times (0 or more) until the preset key is displayed may be different depending on the customer. For example, the past purchase history and the number of times the reading failure state has occurred may be stored for each customer, and the number of times (0 or more) until the preset key is displayed may be different depending on the past purchase history and the number of times the reading failure state has occurred. Also, instead of or in addition to the customer, the number of times (0 or more) until the preset key is displayed may be varied depending on the type of product.

[0269] [Twelfth Modification] In the above embodiment, the products registered by reading the barcode and the products registered using the preset key are not particularly distinguished, but the products registered by reading the barcode and the products registered using the preset key may be stored and output (displayed, etc.) so as to be distinguishable from each other. For example, in the cart information (registered products N), the products registered by reading the barcode and the products registered using the preset key may be stored so as to be distinguishable from each other. For example, information indicating that the products registered using the preset key are the products registered using the preset key may be stored. In the cart information (registered product information (total)), the products registered by reading the barcode and the products registered using the preset key may be stored so as to be distinguishable from each other. For example, the breakdown (number of items, estimated subtotal amount, etc.) of the products registered using the preset key may be stored. In addition, the mobile terminal 60 may display the products registered by reading the barcode and the products registered using the preset key in a registered product list such as that shown in FIG. 10(C), so as to be distinguishable from each other. For example, the mobile terminal 60 may display, in the registered product list, information indicating that a product registered using a preset key is a product registered using a preset key. The settlement device 40 may also display, in a settlement screen such as that shown in Fig. 19, products registered by reading a barcode and products registered using a preset key in a distinguishable manner. For example, the settlement device 40 may display, in the settlement screen, information indicating that a product registered using a preset key is a product registered using a preset key.

[0270] [13th Variation] In the above embodiment, the mobile terminal 60 detects a reading failure state indicating that a product whose product code has not been read has been secured (put into the shopping basket 80 (shopping bag 90)) by a customer. However, instead of the mobile terminal 60, another device (e.g., the transaction status management device 50, the store controller 10, the transaction management device 20, etc.) may detect the reading failure state. The transaction status management device 50 (similar to the store controller 10 and the transaction management device 20) may detect the reading failure state, for example, as follows. The mobile terminal 60 notifies the transaction status management device 50 at each timing that the product code has been read and that the product has been put into the shopping basket 80. When the transaction status management device 50 receives a notification from the mobile terminal 60 that the product code has been read but receives a notification that the product has been put into the shopping basket 80, the transaction status management device 50 determines that a reading failure state has occurred (i.e., detects a reading failure state). When the transaction status management device 50 (same for the store controller 10 and transaction management device 20) detects a reading failure, it notifies the mobile terminal 60 that a reading failure has occurred. When the mobile terminal 60 is notified by the transaction status management device 50 (same for the store controller 10 and transaction management device 20) that a reading failure has occurred, it executes a reading failure process (FIG. 15).

[0271] [14th Variation] In the above embodiment, the imaging unit 606 of the mobile terminal 60 is used to read the product code and to determine whether a product has been inserted, but it is not necessary to use the imaging unit 606 for both. For example, a device equipped with an imaging means capable of detecting the insertion of a product into the shopping basket 80 (shopping bag 90) may be installed (for example, installed on each shopping cart 70, installed on the ceiling of the store, etc.). In other words, the imaging unit 606 of the mobile terminal 60 may be used to read the product code, and the insertion of the product may be detected using a device installed on the shopping cart 70 or on the ceiling of the store, etc.

[0272] [15th Variation] In the above embodiment, the insertion of a commodity is determined by the imaging unit 606 (captured image), but it does not have to be determined by the captured image. For example, instead of or in addition to the imaging means, a weighing device (for example, installed in each shopping cart 70) capable of detecting the insertion of a commodity into the shopping basket 80 (shopping bag 90) may be used.

[0273] [16th Variation] In the above embodiment, in the case of a reading failure, a message prompting the user to read is displayed regardless of the classification of the reserved subcategory numbers "21" to "24", and a preset key is displayed when the reading failure occurs again. However, the control may be different depending on the classification. For example, in the case of a certain reserved subcategory number (e.g., reserved subcategory number "24"), a preset key may be displayed without displaying a message prompting the user to read, and in the case of other reserved subcategory numbers (e.g., reserved subcategory numbers "21" to "23"), a message prompting the user to read may be displayed and then the preset key may be displayed. Also, for example, in the case of a certain reserved subcategory number (e.g., reserved subcategory number "24"), a preset key may be displayed (a message prompting the user to read may be displayed or not), and in the case of other reserved subcategory numbers (e.g., reserved subcategory numbers "21" to "23"), the product may be reserved without displaying the preset key (a message prompting the user to read may be displayed or not). This allows a process to be executed according to the situation (reading failure situation). In the above embodiment (where different processes are used for each classification of reserved items), the process of determining the reserved subcategory number of the reserved item (step S130 in FIG. 15) may be executed earlier (for example, at the beginning of the reading failure process (S120)). Although the "certain reserved subcategory number" is reserved subcategory number "24" and the "other reserved subcategory numbers" are reserved subcategory numbers "21" to "23", the combination of the "certain reserved subcategory number" and the "other reserved subcategory numbers" is not limited to this. Also, instead of the two combinations of "certain reserved subcategory number" and "other reserved subcategory numbers", there may be three to five combinations.

[0274] [17th Variation] In the above embodiment, the mobile terminal 60 displays the preset keys (candidate products). However, instead of or in addition to the mobile terminal 60, other devices (e.g., the settlement device 40, the registered settlement device 30, etc.) may display the preset keys (candidate products). For example, the mobile terminal 60 may not display the preset keys, and the settlement device 40 may display the preset keys (candidate products) for each of the reserved products (reserved products with reserved subcategory numbers "21" to "24"). Also, for example, the mobile terminal 60 may display the preset keys (candidate products), and when registration is not made using the preset keys (i.e., when the product becomes a reserved product), the settlement device 40 may display the preset keys (candidate products) for each of the reserved products (reserved products with reserved subcategory numbers "21" to "24").

[0275] [18th Variation] In addition, all or part of each function (input / output, storage, processing (including judgment)) of each device (store controller 10, transaction management device 20, registration settlement device 30, settlement device 40, transaction status management device 50, mobile terminal 60, etc.) described above may be realized by other devices different from the device described as the execution subject of the function. For example, as the processing of the mobile terminal 60, at least part of the processing described using the left column of the sequence diagram of FIG. 9 and at least part of the processing described using the flowcharts of FIG. 13 to FIG. 16 may be executed by the transaction management device 20, the store controller 10, or the settlement device 40 instead of the mobile terminal 60. In addition, as the processing of the settlement device 40, at least part of the processing described using the middle column of the sequence diagram of FIG. 9 may be executed by the transaction management device 20, the store controller 10, or the mobile terminal 60 instead of the settlement device 40. In relation to the above, the mobile terminal 60 may function as a so-called thin client specialized in an input / output interface with respect to the present shopping service (such as the product registration described in the sequence diagram of FIG. 9 and the flowcharts of FIG. 13 to FIG. 16). For example, instead of the mobile terminal 60 executing the shopping application (no need to install it on the mobile terminal 60), an external device (which may be the transaction management device 20 or another cloud server) may execute the shopping application. That is, the mobile terminal 60 may accept various inputs (customer operations, detection by a device such as a camera), transmit input information (operation information, image information, etc.) to an external device, receive the processing results of the external device based on the input information (update screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device). Instead of or in addition to the mobile terminal 60, another device (such as the settlement device 40) may also function as a thin client.

[0276] <Summary of the embodiment> [Technical field] The present invention relates to a product sales data processing system and a program. [Background technology] There is a known system in which customers can register products themselves using a mobile terminal equipped with a camera (see, for example, Patent Document 1). This system has a function in which the mobile terminal displays the total price at that point in time even while the customer is in the middle of shopping. This function has been well received by customers, and improves customer convenience. [Prior art document] [Patent documents] [Patent Document 1] Patent No. 6242444 [Summary of the invention] [Problem to be solved by the invention] However, in the conventional technology, even if the price of a registered product is unknown, a total price is displayed that does not reflect the fact that a product with an unknown price has been registered, which may lead to customers misunderstanding the total price or misinterpreting the total price. The present invention has been made in consideration of the above circumstances, and has an object to provide a technique for suppressing erroneous recognition of the total amount.

[0277] [Means for solving the problem] (A1) One aspect of this embodiment that solves the above-mentioned problems is a product sales data processing system that registers products using a mobile terminal operated by a customer of a store, the product sales data processing system comprising: a registration means that registers products reserved by the customer; and a display means that displays the number of products registered by the registration means or the total price of the registered products, wherein the registration means registers products whose prices are unknown as products with unknown prices, and the display means displays the total price in different manners depending on whether a product with an unknown price has been registered by the registration means or a product with an unknown price has not been registered by the registration means.

[0278] The above configuration can prevent customers from misunderstanding the total amount. As described above, the function of the mobile device displaying the total amount at that time even while shopping is in progress is a function that is well received by customers, so it is better to eliminate the possibility of causing misunderstanding. Therefore, by displaying it in a different form, it is possible to draw the customer's attention, and as a result, the customer can recognize that the total amount changes depending on the product whose price is unknown.

[0279] (A2) One aspect of this embodiment is the product sales data processing system described in (A1), wherein the display means displays the number of registered products.

[0280] (A3) One aspect of this embodiment is the product sales data processing system described in (A2), wherein the display means displays the number of products in a different manner depending on whether a product with an unknown price has been registered by the registration means or whether a product with an unknown price has not been registered by the registration means.

[0281] According to the above configuration, the number of products is displayed in different ways, which can attract the customer's attention, and as a result, the customer can recognize that the total price changes depending on the number of products.

[0282] (A4) One aspect of this embodiment is a product sales data processing system as described in any of (A1) to (A3), in which the display manner of the total amount when a product with an unknown price is registered by the registration means includes the total amount of products whose price is not unknown and information indicating that a product with an unknown price has been registered.

[0283] (A5) One aspect of this embodiment is a program for causing a mobile terminal operated by a store customer to function as a computer, the program causing the computer to function as a display means for displaying the number of items that have been registered as a result of being reserved by the customer or the total price of the registered items, the display means displaying the total price in a different manner depending on whether an item with an unknown price has been registered or not.

[0284] According to the above configuration, the same effect as (A1) can be obtained.

[0285] In addition, the programs for implementing the functions of the above-mentioned store controller 10, transaction management device 20, registration settlement device 30, settlement device 40, transaction status management device 50, mobile terminal 60, etc. may be recorded on a computer-readable recording medium, and the programs recorded on the recording medium may be read into a computer system and executed to perform processing of the above-mentioned devices. 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 the Internet, a WAN, a LAN, a dedicated line, and other communication lines. 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, 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. In addition, the recording medium also includes a recording medium provided inside or outside and accessible from a distribution server to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on 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 a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network. The above program may also 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]

[0286] 1 Product sales data processing system, 10 Store controller, 20 Transaction management device, 40 Payment device, 50 Transaction status management device, 60 Mobile terminal, 70 Shopping cart, 80 Shopping basket

Claims

1. A product sales data processing system for registering products using a mobile terminal operated by a customer of a store, The mobile terminal includes: a registration means for registering goods reserved by a customer; a display means for displaying the total price of the products registered by the registration means in a predetermined total price field; Equipped with The registration means includes: Register products with unknown prices as products with unknown prices, The display means is When the products registered by the registration means include a product with an unknown price, the total price of the products registered by the registration means other than the product with an unknown price and information indicating that the total price of the products registered by the registration means is the amount exceeding the total price of the products other than the product with an unknown price are displayed in the total price column. Product sales data processing system.

2. The display means is Displaying the total number of products registered by the registration means in a predetermined total product column; When the products registered by the registration means include products whose prices are unknown, the number of products registered by the registration means and the number of products whose prices are unknown among the products registered by the registration means are displayed in the total product column.

2. The product sales data processing system according to claim 1.

3. A program for causing a mobile terminal operated by a customer of a store to function as a computer, The computer, a registration means for registering the goods reserved by the customer; A display means for displaying the total amount of the products registered by the registration means in a predetermined total amount column. Functioning as a The registration means includes: Register products with unknown prices as products with unknown prices, The display means is When the products registered by the registration means include a product with an unknown price, the total price of the products registered by the registration means other than the product with an unknown price and information indicating that the total price of the products registered by the registration means is the amount exceeding the total price of the products other than the product with an unknown price are displayed in the total price column. A program characterized by:

4. A mobile terminal operated by a customer of a store, a registration means for registering goods reserved by a customer; a display means for displaying the total price of the products registered by the registration means in a predetermined total price field; Equipped with The registration means includes: Register products with unknown prices as products with unknown prices, The display means is When the products registered by the registration means include a product with an unknown price, the total price of the products registered by the registration means other than the product with an unknown price and information indicating that the total price of the products registered by the registration means is the amount exceeding the total price of the products other than the product with an unknown price are displayed in the total price column. Mobile device.

Images