Commodity sales data processing system, adjustment device, and program

The product sales data processing system addresses issues in customer-driven product registration and payment by using a portable device for automatic product registration and transparent payment updates, enhancing efficiency and reducing staff intervention.

JP2024163155AActive Publication Date: 2024-11-21TERAOKA SEIKO CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024148273
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-08-30
Publication Date
2024-11-21
Estimated Expiration
2040-12-02

AI Technical Summary

Technical Problem

Existing systems face issues during product registration and payment when customers use mobile terminals, leading to problems such as incomplete product information retrieval and manual intervention by store clerks for resolving non-registered products.

Method used

A product sales data processing system that includes a portable registration device for customers to register products, a payment unit to execute payments, and a notification unit to inform customers of automatic product registration, utilizing a network of servers and devices to retrieve and update product information.

Benefits of technology

Automatically registers non-registered products and updates payment information, reducing staff burden and checkout time while ensuring transparent and anxiety-free transactions for customers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024163155000001_ABST
    Figure 2024163155000001_ABST
Patent Text Reader

Abstract

To provide a system for a customer himself / herself to register a commodity using a portable terminal, in which various problems in the scene of adjustment are solved.SOLUTION: Provided is a commodity sales data processing system for registering a commodity with a portable registration device to be operated by a customer himself / herself, including: registration means for acquiring commodity information corresponding to a specified commodity code from a first commodity information database and executing registration processing of registering the commodity; adjustment means for executing adjustment processing referring to the commodity information after the registration processing performed by the registration means finishes; and notification means for notifying a customer. The adjustment means is capable of further executing automatic registration processing of, in a case in which the commodity information corresponding to the commodity code fails to be acquired from the first commodity information database even if the commodity code is specified, acquiring the commodity information corresponding to the commodity code from a second commodity information database without performing an operation and registering the commodity. The notification means notifies the customer of the presence of an automatically-registered commodity in a case in which the automatic registration processing is executed.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a merchandise sales data processing system and a payment device. [Background technology]

[0002] A system has been proposed in which customers themselves register products using mobile terminals (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, various problems may arise when paying for a product after it has been registered.

[0005] The present invention has been made in consideration of the above circumstances, and aims to provide technology for solving various problems that occur at the checkout stage in a system in which customers themselves register products using their mobile terminals. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a product sales data processing system in which products are registered using a portable registration device operated by the customer themselves, comprising: a registration means for executing a registration process to obtain product information corresponding to an identified product code from a first product information database and register the product; a settlement means for executing a settlement process by referring to the product information after the registration process by the registration means has been completed; and a notification means for notifying the customer; wherein, if a product code has been identified but product information corresponding to the product code cannot be obtained from the first product information database, the settlement means is further capable of executing an automatic registration process to obtain product information corresponding to the product code from a second product information database without any operation and register the product; and wherein, when the automatic registration process has been executed, the notification means automatically notifies the customer that a product has been registered. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram of a network for explaining a sales system. [Figure 2] FIG. 2 is a diagram illustrating a settlement device. [Figure 3] 10 is an example of a file related to a sales system. [Figure 4] 10 is an example of a file related to a sales system. [Figure 5] 10 is a display example of a mobile terminal. [Figure 6] 10 shows an example of a display on a mobile terminal. [Figure 7] 10 is a display example of a mobile terminal. [Figure 8] 10 is a display example of a mobile terminal. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of processing by a mobile terminal and a cloud server. [Figure 10] 10 is a display example of a payment device. [Figure 11] 10 is a display example of a payment device. [Figure 12] 10 is a display example of a payment device. [Figure 13]10 is a display example of a payment device. [Figure 14] 10 is a display example of a payment device. [Figure 15] 10 is a display example of a payment device. [Figure 16] 10 is a display example of a payment device. [Figure 17] 10 is a display example of a payment device. [Figure 18] FIG. 10 is a sequence diagram showing an example of processing by the settlement device and the cloud server. [Figure 19] FIG. 10 is a sequence diagram showing an example of processing by a payment device, a store controller, a headquarters server, a cloud server, and a mobile terminal. [Figure 20] 10 is a display example of a payment device. [Figure 21] 10 is a display example of a payment device. [Figure 22] 10 is a display example of a payment device. DETAILED DESCRIPTION OF THE INVENTION

[0008] Fig. 1 is a conceptual diagram of a network for explaining a sales system 1. The sales system 1 shown in Fig. 1 includes a headquarters server 10, a cloud server 20, a store controller 30 (e.g., a server), a settlement device 40, a transaction status management device 50 (e.g., a personal computer), and a mobile terminal 60 (e.g., a smartphone). The sales system 1 can be introduced in various stores (supermarkets, convenience stores, drugstores, home centers, electronics retailers, other specialty stores, etc.).

[0009] Sales system 1 provides a self-service mode (hereinafter, sometimes referred to as service A) in which a customer uses a mobile terminal 60 to register a product and then uses a payment settlement device 40 to settle the payment. In other words, service A is a self-service mode in which a customer registers a product and settles the payment themselves, using mobile terminal 60 for product registration and using payment settlement device 40 for settlement.

[0010] Sales system 1 may provide other services in addition to service A. For example, as the other services, sales system 1 may provide one or more of the following: a service in which a customer uses registration and settlement device 41 (not shown) to register products and settle the payment; a service in which a store clerk uses registration and settlement device 42 (not shown) to register products and settle the payment; or a service in which a store clerk registers products using registration and settlement device 42 (not shown) or registration device 43 (not shown), and the customer settles the payment using settlement device 40 or settlement device 44 (not shown).

[0011] The headquarters server 10 is installed outside the store (for example, at a headquarters or data center) and is a server that manages the entire sales system 1. The headquarters server 10 stores, for example, various information necessary for the operation of service A (for example, a product master, a sale file, etc.) and performance information of service A in the store (for example, sales performance information, product sales performance information, etc.). The headquarters server 10 communicates with other devices, etc. (for example, a cloud server 20, a store controller 30, a product ordering system (not shown), etc.). The headquarters server 10 may be composed of multiple servers.

[0012] Cloud server 20 is a server installed outside the store (e.g., in a data center, etc.) that provides service A. Cloud server 20 stores, for example, various information (e.g., product master, transaction information, etc.) necessary for the operation of service A. Cloud server 20 communicates with other devices, etc. (e.g., headquarters server 10, store controller 30, mobile terminal 60, etc.). Note that cloud server 20 may be configured from multiple servers.

[0013] The store controller 30, settlement device 40, and transaction status management device 50 are installed in a store and are communicatively connected to each other via a LAN 19 (which may be wired or wireless). Note that the number of devices shown in FIG. 1 is an example. For example, while two settlement devices 40 are shown in FIG. 1, the number of settlement devices 40 in one store may be one or three or more. Furthermore, while one transaction status management device 50 is shown in FIG. 1, the number of transaction status management devices 50 in one store may be two or more.

[0014] Mobile terminals 60 may also be present in the store. The number of mobile terminals 60 in the store varies depending on the number of users (customers) of service A at the store. In FIG. 1, two mobile terminals 60 are shown as an example of a device that can be used by multiple people at the same time. Note that the mobile terminals 60 are assumed to be owned by the individual customer (or corporation) using service A, but may also be loaned by the store.

[0015] The mobile terminal 60 is a terminal used when registering a product in service A. That is, the customer uses the mobile terminal 60 when registering a product in service A. The mobile terminal 60 has a communication function, an imaging function (camera), and also a recognition function for recognizing various codes (barcodes, two-dimensional codes, etc.). For example, the mobile terminal 60 recognizes a barcode attached to a product. For example, the mobile terminal 60 may extract feature points in an image captured by the imaging function (an image acquired as a through image (live view)) and recognize an object (various codes).

[0016] The settlement device 40 is a device used when settling payments for service A. That is, a customer uses the settlement device 40 when settling payments for products registered using the mobile terminal 60. The configuration of the settlement device 40 will be described later.

[0017] The store controller 30 is a device that controls the part of the sales system 1 that is related to the store. The store controller 30 communicates with other devices outside the LAN 19 (e.g., the headquarters server 10, the cloud server 20, etc.). For example, the store controller 30 receives a product master and a sale file from the headquarters server 10 and provides them to the checkout device 40.

[0018] The transaction status management device 50 is a device that mainly manages various devices within the LAN 19. For example, the transaction status management device 50 monitors the operating status of the settlement device 40, etc.

[0019] FIG. 2 is a diagram illustrating the settlement device 40. FIG. 2(A) is a diagram illustrating an example of the appearance of the settlement device 40 (a front view seen from the customer side). FIG. 2(B) is a diagram illustrating an example of the configuration of the settlement device 40. In FIG. 2(A) and FIG. 2(B), the same parts are given the same reference numerals.

[0020] An example configuration of the settlement device 40 shown in Figure 2(B) will be described below with reference to Figure 2(A). The 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 payment unit 408, a change dispenser 409, a printer unit 413, an audio output unit 414, a communication unit 415, an imaging unit 416 (camera), and a sign pole 417. These can communicate with each other via a bus. The settlement device 40 may further include a key operation unit consisting of various keys (buttons), a sensor for detecting the presence of a person (such as a human presence sensor), etc.

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

[0022] The RAM 403 is a read / write memory that stores various types of information as a main storage device, such as information read from the ROM 402 or the hard disk 404, information acquired from the outside, and information generated during processing.

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

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

[0025] The scanner unit 406 optically reads various information. Specifically, the scanner unit 406 scans a code (a two-dimensional code 605 for payment (described later)) displayed on the display unit of the mobile terminal 60, and reads information necessary for payment processing. The scanner unit 406 may also scan a code attached to a store clerk's name tag or the like to read a store clerk code. The scanner unit 406 may also scan codes attached to gift certificates (gift certificates, coupons, complimentary coupons) and various cards (e.g., membership cards, point cards, etc.) to read the respective information.

[0026] In addition to the above, the scanner unit 406 may scan a code attached to a product to read the product code (JAN code, etc.). The scanner unit 406 may also scan a code printed on a receipt (registered trademark) printed and issued by another device (for example, a registration and settlement device 42 (not shown) or a registration device 43 (not shown)) to read information necessary for the settlement process.

[0027] The card payment unit 408 is a payment mechanism that accepts 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 if it includes at least the card recognition unit. The card recognition unit may also recognize various cards (for example, point cards, membership cards, stockholder cards, etc.) for the purpose of granting benefits, discounts, etc.

[0028] The change dispenser 409 (cash settlement unit) is a cash settlement mechanism, 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 change amount, 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 (detecting that they have been inserted, detecting the number of coins by denomination, etc.).

[0029] The printing unit 413 prints and issues various media (receipts, etc.). The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs a confirmation sound, a warning sound, audio guidance, and the like.

[0030] The communication unit 415 transmits and receives information to and from other devices (for example, the store controller 30). The imaging unit 416, for example, captures an image of the customer. The settlement device 40 may be equipped with two or more imaging units 416, and may simultaneously capture an image of the customer's face and their hands (near the insertion slot and ejection slot of the change dispenser 409). The sign pole 417 has a light emitting part at the tip, and notifies various information (such as calling a store clerk, operating status, etc.) depending on the light emitting mode of the light emitting part.

[0031] Figure 3 shows an example of a file related to the sales system 1. Figure 3(A) shows an example of a product master (referred to as a checkout product master) stored by the headquarters server 10. Figure 3(B) shows an example of a bargain file stored by the headquarters server 10. In addition to the headquarters server 10, the store controller 30 and the checkout device 40 also store a checkout product master and bargain files (details will be described later).

[0032] The checkout product master may be referenced when checking out using service A (checkout using the checkout device 40). Specifically, the checkout product master is referenced when the products being purchased at checkout include products whose product codes are not stored in the registration product master (i.e., products that are not registered in the registration product master; also referred to as non-file products).

[0033] The checkout product master stores information such as a product code (product identification information) that identifies a product, a product name (product name), and a price (sales price). In the example of FIG. 3(A), the checkout product master stores the product name and price in association with the product code. Note that the product codes such as "S0123" and "S0135" shown in FIG. 3(A) are examples given for the sake of convenience, and may be JAN codes or the like. Hereinafter, either or both of the product name and price may be referred to as product information. The product code may also be referred to as product information.

[0034] The sale file is referenced when settlement is made by service A. The sale file stores a sale code (sale identification information) that identifies the sale, sale conditions (target product), and sale details (discount amount). In the example of Figure 3 (B), the sale file stores the sale conditions and sale details in association with the sale code. Hereinafter, either or both of the sale conditions and sale details may be referred to as sale information. The sale code may also be referred to as sale information.

[0035] Fig. 4 shows an example of a file related to the sales system 1. Fig. 4(A) shows an example of a product master (referred to as a product master for registration) stored in the cloud server 20. Fig. 4(B) shows an example of a provisional product file stored in the cloud server 20.

[0036] The product master for registration is referenced when registering a product using service A (registering a product using mobile terminal 60). Similar to the product master for checkout, the product master for registration stores information such as product code, product name, and price. In the example of Fig. 4(A), the product master for registration stores product name and price in association with the product code.

[0037] The provisional product file may be referenced when a product is registered by service A. Specifically, the provisional product file is referenced when the product code transmitted from the mobile terminal 60 is not stored in the registration product master when registering a product. The provisional product file may always be referenced when a product is registered by service A. That is, the reference order may be the registration product master → provisional product file, or the provisional product file → registration product master. In the latter case, the provisional product file is always referenced when a product is registered by service A. In the latter case, the registration product master may not be referenced (if the product code transmitted from the mobile terminal 60 is stored in the provisional product file that is referenced first, the registration product master is not referenced).

[0038] The provisional product file stores information such as product code, product name, and price, similar to the product master for registration. In the example of Fig. 4(B), the provisional product file stores product name and price in association with the product code. Note that if the product master for registration is updated, for example, and the information in the provisional product file is reflected in the product master for registration, the information in the provisional product file may be deleted.

[0039] The headquarters server 10 transmits the checkout product master to the store controller 30. The store controller 30 stores the checkout product master received from the headquarters server 10 in its own device and transmits it to each checkout device 40. The checkout device 40 stores the checkout product master received from the store controller 30 in its own device. In other words, in addition to the headquarters server 10, the store controller 30 and the checkout device 40 also store the checkout product master.

[0040] Furthermore, the head office server 10 transmits the checkout product master to the cloud server 20 in addition to the store controller 30. The cloud server 20 stores the checkout product master received from the head office server 10 as a registration product master.

[0041] The information stored in the registration product master at a certain point in time may differ from the information stored in the checkout product master at that point in time. Specifically, both the registration product master stored in the cloud server 20 and the checkout product master stored in, for example, the checkout device 40 originate from the checkout product master stored in the headquarters server 10. However, because of differences in the frequency of transmission and reception (update frequency), the contents of the former may be older than the contents of the latter. For example, in the example shown in FIGS. 3(A) and 4(A), the checkout product master (FIG. 3(A)) stores the product with product code "S0274" (XX gum) and the product with product code "S0275" (XX snack) as new sales products, whereas the registration product master (FIG. 4(A)) does not store the product with product code "S0274" (XX gum) or the product with product code "S0275" (XX snack).

[0042] In this example, the headquarters server 10 transmits the checkout product master data to the store controller 30 at least once a day, the store controller 30 immediately stores the received checkout product master data, and transmits the checkout product master data to the checkout device 40 at least once a day, and the checkout device 40 immediately stores the received checkout product master data. In this example, the headquarters server 10 transmits the checkout product master data to the cloud server 20 several times a week or a month, and the cloud server 20 immediately stores the received checkout product master data as a registration product master data. In other words, in this example, the checkout product master data is updated at least once a day, and the registration product master data is updated several times a week or a month. In other words, the registration product master data is considered to be older than the checkout product master data, for example, because information reflected in the checkout product master data may not be reflected in the registration product master data.

[0043] The headquarters server 10 also transmits the sale file to the store controller 30. The store controller 30 stores the sale file received from the headquarters server 10 in its own device and transmits it to each settlement device 40. The settlement devices 40 store the sale file received from the store controller 30 in their own device. In other words, in addition to the headquarters server 10, the store controller 30 and the settlement devices 40 also store the sale file.

[0044] The cloud server 20 generates and updates a provisional product file based on the received NON-FILE resolution information (described later) including the product code, product name, and price.

[0045] The NON-FILE resolution information is information indicating that a NON-FILE has been resolved (that the NON-FILE has been resolved), and is generated and transmitted by the settlement device 40. The settlement device 40 may generate and transmit the NON-FILE resolution information when settling a bill for service A (settlement by the settlement device 40). Specifically, the settlement device 40 generates and transmits the NON-FILE resolution information after the NON-FILE has been resolved if, at the time of settlement, the purchased products include a NON-FILE product (a product not registered in the product master for registration) and the product code of the NON-FILE product is stored in the product master for settlement (i.e., when the NON-FILE can be resolved). The cloud server 20 receives the NON-FILE resolution information transmitted from the settlement device 40 via another device or directly from the settlement device 40. In addition, resolving NON-FILE means resolving the problem caused by NON-FILE (a situation where prices, etc. have not been obtained) that occurred when registering a product on the mobile terminal 60 at the settlement device 40 (obtaining prices, etc. that had not been obtained).

[0046] (Display example of mobile terminal 60 (transaction example (purchase example) 1)) FIG. 5 is a display example of the mobile terminal 60. FIG. 6 is a display example of the mobile terminal 60. FIGS. 5(A) and 5(B) are display examples of a scene before registering a product. FIGS. 5(C) to 6(B) are display examples of a scene in which items 1 to 3 are registered as transaction example 1 (item 3 is registered as a NON-FILE product). FIG. 6(C) is a display example of a two-dimensional code display screen corresponding to transaction example 1. FIGS. 5 and 6 transition as follows: FIG. 5(A) → FIG. 5(B) → FIG. 5(C) → FIG. 5(D) → FIG. 6(A) → FIG. 6(B) → FIG. 6(C).

[0047] FIG. 5(A) is the start screen (menu screen) of service A. When using service A, mobile terminal 60 displays the start screen as shown in FIG. 5(A). Various buttons are arranged on the start screen. For example, the start screen has a start shopping button BT600 that accepts a command to start shopping. When a customer wants to start shopping, they operate the start shopping button BT600.

[0048] Fig. 5(B) is a registration screen (initial registration screen; registration screen before registering one product) that is displayed after the shopping start button BT600 is operated on the start screen of Fig. 5(A). The upper side of the registration screen is a captured image display area HR601 that mainly displays captured images. The lower side of the registration screen is a registration information display area HR602 that mainly displays product registration information.

[0049] Figure 5(C) is the registration screen when capturing an image of the barcode attached to one item on the registration screen of Figure 5(B). That is, when a customer registers a desired item (item to be purchased), the barcode attached to the item is read as shown in Figure 5(C). It should be noted that the barcode attached to the one item is a barcode obtained by encoding the product code "S0204."

[0050] FIG. 5(D) shows a registration screen (registration screen after product registration) after the registration of one product item is completed. Specifically, the mobile terminal 60 transmits the product code "S0204" obtained from the barcode (a barcode obtained by encoding the product code "S0204") to the cloud server 20. The cloud server 20 references the product master for registration (FIG. 4(A)) and obtains the product name "XXX bread" and the price "¥220" based on the product code "S0204." The cloud server 20 stores the product information (product code "S0204," product name "XXX bread," quantity "1," price "¥220," etc.) as transaction information (cart information) for the transaction, and transmits the product information (product name "XXX bread," price "¥220," etc.) to the mobile terminal 60. Upon receiving the product information from the cloud server 20, the mobile terminal 60 reflects the product information for the one product item in the registration information display area HR602. Specifically, as shown in Fig. 5(D), the mobile terminal 60 displays the registered information of the product (product name "XXX bread", quantity "1", price "220 yen") (symbol a), and displays the total information (estimated total "1 item 220 yen") (symbol b). The mobile terminal 60 displays part of the registered information (quantity) as a quantity button BT603. The quantity button BT603 is a button for changing the quantity.

[0051] After registering a product (one item), the mobile terminal 60 displays an operable Proceed to Checkout button BT604 for accepting payment instructions, as shown in Figure 5(D). When the customer wishes to proceed to checkout (to complete product registration), the customer operates the Proceed to Checkout button BT604.

[0052] FIG. 6(A) shows a registration screen following the scene in FIG. 5(D) after the registration of the second product has been completed. Specifically, the mobile terminal 60 captures an image of the barcode attached to the second product. The barcode attached to the second product is assumed to be a barcode obtained by encoding the product code "S0245." The mobile terminal 60 transmits the product code "S0245" acquired from the barcode to the cloud server 20. The cloud server 20 references the product master for registration (FIG. 4(A)) and acquires the product name "XX Oolong Tea" and the price "150 yen" based on the product code "S0245." The cloud server 20 stores the product information (product code "S0245", product name "XX Oolong Tea", quantity "1", price "¥150", etc.) as transaction information for the transaction, and transmits the product information (product name "XX Oolong Tea", price "¥150", etc.) to the mobile terminal 60. Having received the product information from the cloud server 20, the mobile terminal 60 reflects the product information for the two items in the registered information display area HR602. Specifically, as shown in FIG. 6(A), the mobile terminal 60 displays (adds) the registered information for the products (product name "XX Oolong Tea", quantity "1", price "¥150") and displays (updates) the total information (estimated total "2 items ¥370").

[0053] FIG. 6(B) shows a registration screen following the scene in FIG. 6(A) after the registration of the three products has been completed (registration as unregistered products has been completed). Specifically, the mobile terminal 60 captures an image of the barcode attached to the three products. It is assumed that the barcode attached to the three products is a barcode obtained by encoding the product code "S0275." The mobile terminal 60 transmits the product code "S0275" acquired from the barcode to the cloud server 20. The cloud server 20 references the product master for registration (FIG. 4(A)) and recognizes (determines) that the product code "S0275" is not stored in the product master for registration. Furthermore, the cloud server 20 references the provisional product file (FIG. 4(B)) and recognizes that the product code "S0275" is not stored in the provisional product file either. The cloud server 20 stores the product information (product code "S0275", NON-FILE, quantity "1", etc.) as transaction information for the transaction, and transmits the product information (information indicating that the product is NON-FILE, etc.) to the mobile terminal 60. The mobile terminal 60, which has received the product information from the cloud server 20, reflects the product information for the three items in the registered information display area HR602. Specifically, as shown in FIG. 6(B), the mobile terminal 60 displays (adds) the registered information for the products ("unregistered product" indicating that the product is NON-FILE, quantity "1"), and displays (updates) the total information (estimated total "3 items 370 yen").

[0054] FIG. 6(C) shows a two-dimensional code display screen that is displayed after the Proceed to Checkout button BT604 is operated, following the scene in FIG. 6(B). The two-dimensional code display screen displays a two-dimensional code 605 for checkout. The two-dimensional code 605 is a two-dimensional code that contains information required for executing the checkout process. For example, the two-dimensional code 605 is a two-dimensional code that contains transaction identification information (cart identification information) that identifies the transaction information of the transaction from among multiple pieces of transaction information stored in the cloud server 20. Note that the information that is two-dimensionally coded does not have to be transaction identification information, as long as the transaction information of the transaction can be obtained after reading. For example, the two-dimensional code 605 may be a two-dimensional code that contains location information of the transaction information of the transaction (a storage location within the sales system 1, such as a Uniform Resource Identifier (URI)).

[0055] The two-dimensional code display screen also has an estimated total display area HR606 and a back button BT607. In the example of FIG. 6(C), the estimated total display area HR606 displays the estimated total "3 items for 370 yen," and also displays the message "Unregistered item (1 item) not included." This message notifies the user that the price of the unregistered item (1 item) is not reflected in the estimated total. The back button BT607 is a button for returning to shopping (restarting shopping). When the back button BT607 is operated, the mobile terminal 60 displays a registration screen (the registration screen displayed immediately before the Proceed to Checkout button BT604 was operated) instead of the two-dimensional code display screen.

[0056] Figure 6(D) shows how the settlement device 40 reads the two-dimensional settlement code 605. After completing product registration, the customer has the settlement device 40 read the two-dimensional settlement code 605 displayed on the mobile terminal 60, as shown in Figure 6(D).

[0057] (Display example of mobile terminal 60 (transaction example 2)) FIG. 7 is a display example of the mobile terminal 60. FIGS. 7(A) to 7(C) are display examples of a scene in which, as Transaction Example 2, products different from those in Transaction Example 1 (products 1 to 3) are registered. FIG. 7(D) is a display example of a two-dimensional code display screen corresponding to Transaction Example 2. Note that FIG. 7(A) is a continuation of FIG. 5(B), and the transitions are as follows: FIG. 5(A) → FIG. 5(B) → FIG. 7(A) → FIG. 7(B) → FIG. 7(C) → FIG. 7(D).

[0058] Fig. 7(A) shows the registration screen after the registration of one item has been completed, following the scene in Fig. 5(B). Specifically, the mobile terminal 60 shows the registration screen after the registration of XX Gyoza (product code "S0123") has been completed. As shown in Fig. 7(A), the mobile terminal 60 displays the registration information for the product (product name "XX Gyoza", quantity "1", price "¥290") and total information (estimated total "1 item ¥290").

[0059] Figure 7(B) shows the registration screen after the registration of two items has been completed, following the scene in Figure 7(A). Specifically, the mobile terminal 60 shows the registration screen after the registration of XX stir-fry (product code "S0144") has been completed. As shown in Figure 7(B), the mobile terminal 60 displays the registration information for the product (product name "XX stir-fry", quantity "1", price "¥420") and total information (estimated total "2 items ¥710").

[0060] Figure 7(C) shows the registration screen after the registration of three items and the change in quantity, following the scene in Figure 7(B). Specifically, the mobile terminal 60 shows the registration screen after the registration of XX socks (product code "S0597") is completed and the quantity is changed to three by operating the quantity button BT603. As shown in Figure 7(C), the mobile terminal 60 displays the registration information for the product (product name "XX socks", quantity "3", price "900 yen") and total information (estimated total "5 items 1610 yen").

[0061] Figure 7(D) shows the 2D code display screen that appears after the Proceed to Checkout button BT604 is pressed, following the scene in Figure 7(C). In the example of Figure 7(D), the estimated total display area HR606 displays the estimated total "5 items ¥1610."

[0062] (Display example of mobile terminal 60 (transaction example 3)) FIG. 8 is a display example of the mobile terminal 60. FIGS. 8(A) to 8(C) are display examples of a scene in which, as transaction example 3, products different from those in transaction examples 1 and 2 (products 1 to 3) are registered. FIG. 8(D) is a display example of a two-dimensional code display screen corresponding to transaction example 3. Note that FIG. 8(A) is a continuation of FIG. 5(B), and the transitions are as follows: FIG. 5(A) → FIG. 5(B) → FIG. 8(A) → FIG. 8(B) → FIG. 8(C) → FIG. 8(D).

[0063] Fig. 8(A) shows the registration screen after the registration of one product item has been completed, following the scene in Fig. 5(B). Specifically, the mobile terminal 60 shows the registration screen after the registration of XX bento (product code "S0175") has been completed. As shown in Fig. 8(A), the mobile terminal 60 displays the registration information for the product (product name "XX bento", quantity "1", price "620 yen") and total information (estimated total "1 item 620 yen").

[0064] Figure 8(B) shows the registration screen after the registration of two items has been completed, following the scene in Figure 8(A). Specifically, the mobile terminal 60 shows the registration screen after the registration of XX Green Tea (product code "S0215") has been completed. As shown in Figure 8(B), the mobile terminal 60 displays (adds) the registration information for the product (product name "XX Green Tea, quantity "1", price "¥130") and total information (estimated total "2 items ¥750").

[0065] Figure 8(C) shows the registration screen after the registration of three items and the change in quantity, following the scene in Figure 8(B). Specifically, the mobile terminal 60 shows the registration screen after the registration of XX salad (product code "S0170") is completed. As shown in Figure 8(C), the mobile terminal 60 displays (adds) the registration information for the product (product name "XX salad", quantity "1", price "¥280") and displays total information (estimated total "3 items ¥1030").

[0066] Figure 8(D) shows the 2D code display screen that appears after the Proceed to Checkout button BT604 is pressed, following the scene in Figure 8(C). In the example of Figure 8(D), the estimated total display area HR606 displays the estimated total "3 items ¥1030."

[0067] Fig. 9 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, the sequence diagram of Fig. 9 shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when one product item is registered on the mobile terminal 60 until the two-dimensional code for payment 605 is displayed. The left side of Fig. 9 shows the processing of the mobile terminal 60, and the right side shows the processing of the cloud server 20. It is assumed that at the start of the sequence diagram of Fig. 9 (the start of the processing of step S1 for the first time), the mobile terminal 60 is displaying an initial registration screen such as that shown in Fig. 5(B).

[0068] Step S1: The mobile terminal 60 reads the barcode attached to the product in response to a reading operation by the customer. That is, the mobile terminal 60 acquires the product code from the barcode attached to the product in response to a reading operation by the customer. Step S2: The mobile terminal 60 transmits to the cloud server 20 transaction identification information that identifies the transaction information of the transaction, and the product code acquired in step S1.

[0069] Step S3: The cloud server 20 receives the transaction identification information and the product code. Step S4: Cloud server 20 updates the transaction information for the transaction. That is, cloud server 20 updates the transaction information corresponding to the transaction identification information received in step S3 based on the product code received in step S3.

[0070] The processing of step S4 will be described in detail. If the product code is stored in the registration product master or the provisional product file, the cloud server 20 acquires (extracts) information corresponding to the product code (product name, price) from the registration product master or the provisional product file, and stores the product code, product name, quantity, price, etc. in the transaction information corresponding to the transaction identification information. On the other hand, if the product code is not stored in either the registration product master or the provisional product file, the cloud server 20 stores the product code, information indicating that it is a NON-FILE product, quantity, etc. in the transaction information corresponding to the transaction identification information.

[0071] By processing step S4, if the product whose product code was obtained in step S1 (the product whose barcode was read) is not a NON-FILE product (if the product code of the product is stored in the product master for registration, etc.), the product code, product name, quantity, price, etc. are stored in the transaction information of the transaction. On the other hand, if the product whose product code was obtained in step S1 is a NON-FILE product (if the product code of the product is not stored in the product master for registration, etc.), the product code, information indicating that it is a NON-FILE product, quantity, etc. are stored in the transaction information of the transaction.

[0072] Step S5: The cloud server 20 transmits product information for the product code (such as the product name and price, or information indicating that the product is non-file). For example, the cloud server 20 generates screen information that reflects the contents of the updated transaction information and transmits it to the mobile terminal 60.

[0073] The processing of step S5 will be described in detail. If the product whose product code was acquired in step S1 is not a non-file product, the cloud server 20 transmits the product name, price, etc. as product information for the product code to the mobile terminal 60. On the other hand, if the product whose product code was acquired in step S1 is a non-file product, the cloud server 20 transmits information indicating that the product is a non-file to the mobile terminal 60 as product information for the product code. Note that in step S4, if the product whose product code was acquired in step S1 is not a non-file product, the product code, product name, quantity, price, etc. are stored in the transaction information for the transaction, and if the product whose product code was acquired in step S1 is a non-file product, the product code, information indicating that the product is a non-file product, quantity, etc. are stored in the transaction information for the transaction. Therefore, in the processing of step S5, the cloud server 20 may simply generate screen information reflecting the contents of the updated transaction information and transmit it to the mobile terminal 60.

[0074] By the processing of step S5, if the product whose product code was obtained in step S1 is not a NON-FILE product, the product name and price of the product (for example, screen information reflecting the product name and price of the product) are sent to the mobile terminal 60. On the other hand, if the product whose product code was obtained in step S1 is a NON-FILE product, information indicating that it is a NON-FILE product (for example, screen information reflecting information indicating that it is a NON-FILE product) is sent to the mobile terminal 60.

[0075] Step S6: The mobile terminal 60 receives the product information (screen information) of the product code. Step S7: The mobile terminal 60 updates the registration screen based on the information (screen information) received in step S6. By the processing of step S7, if the product whose product code was obtained in step S1 is not a non-file product, the product name, price, etc. of the product are displayed on the registration screen. On the other hand, if the product whose product code was obtained in step S1 is a non-file product, information indicating that it is a non-file product is displayed on the registration screen. Steps S1 to S7 are repeatedly executed by reading the barcode attached to the product.

[0076] Step S8: The mobile terminal 60 generates a two-dimensional code 605 for payment based on the customer's payment instructions (operation of the Proceed to Payment button BT604) and displays it on the two-dimensional code display screen. Then, the sequence diagram in Fig. 9 ends.

[0077] 10 to 17 are examples of displays on the settlement device 40. FIG. 10 shows the initial screen GM01. As shown in FIG. 10, the initial screen GM01 displays a message and a guide map instructing the user to read the two-dimensional settlement code 605 (shown as a QR code (registered trademark) in the figure) displayed on the mobile terminal 60. The initial screen GM01 also has a store clerk call button BT401, a balance inquiry button BT402, and language switch buttons BT403 to BT405. The store clerk call button BT401 is a button for calling a store clerk. The balance inquiry button BT402 is a button for inquiring about the balances of various cards. The language switch button BT403 is a button for switching the display (text) on the initial screen GM01 from Japanese to English. The language switch button BT404 is a button for switching to Chinese. The language switch button BT405 is a button for switching to Korean.

[0078] After completing product registration, the customer follows the instructions on the initial screen GM01 to have the settlement device 40 read the two-dimensional settlement code 605 displayed on the mobile terminal 60. When the settlement device 40 reads the two-dimensional settlement code 605, it obtains from the cloud server 20 the transaction information of the transaction identified by the two-dimensional settlement code 605.

[0079] (Operation of settlement device 40 after acquiring transaction information) After acquiring the transaction information from the cloud server 20, the settlement device 40 performs, for example, the following two processes related to the product in the transaction information (processing related to the non-file product and processing related to the sale price).

[0080] (Processing for non-file products) The settlement device 40 determines whether or not the transaction information obtained from the cloud server 20 includes any NON-FILE products (products that the mobile terminal 60 has displayed as "unregistered products" (Figure 6(B))). If the transaction information does not include any NON-FILE products, the operation ends. In other words, since there are no NON-FILE products in the transaction information obtained from the cloud server 20, the processing ends.

[0081] If a non-file product is included in the transaction information obtained from the cloud server 20, the settlement device 40 refers to the settlement product master (FIG. 3(A)) and determines whether the product code of the non-file product is stored in the settlement product master (FIG. 3(A)). If the product code is stored in the settlement product master, it becomes possible to resolve the non-file status for the product with that product code.

[0082] If the product code of the non-file product is stored in the checkout product master, the checkout device 40 obtains the product name, price, etc. of the non-file product from the checkout product master, recalculates the total amount, and reflects this in the transaction information. In other words, the checkout device 40 eliminates the non-file status for the product. Specifically, the checkout device 40 additionally stores the product name, price, etc. obtained from the checkout product master into the transaction information without erasing (overwriting) the information indicating that the product is a non-file product, and additionally stores the recalculated total amount without erasing the total amount before the recalculation.

[0083] On the other hand, if the product code of the non-file product is not stored in the checkout product master, the checkout device 40, for example, causes the sign pole 417 to light up in a predetermined light-emitting manner indicating that a store clerk should be called (or, more specifically, a predetermined light-emitting manner indicating that the non-file cannot be resolved). The store clerk called by the checkout device 40 enters the product information of the non-file (such as the product price) and proceeds with the checkout. Note that the manner of calling a store clerk when the product code of the non-file product is not stored in the checkout product master is not limited to this. For example, instead of or in addition to lighting up the sign pole 417, the checkout device 40 may send a call notification to a device operated by the store clerk (such as the transaction status management device 50 or a mobile terminal carried by the store clerk).

[0084] In other words, for a product (a non-file product) for which the product code was not stored in the registration product master (FIG. 4(A)) at the time the product code was acquired by the mobile terminal 60 and therefore the product name, price, etc. could not be obtained from the registration product master, the checkout device 40 references the checkout product master, which is different from the registration product master, and if the product code is stored in the checkout product master, obtains the product name, price, etc. from the checkout product master, recalculates the total amount, and reflects this in the transaction information (resolves the non-file). On the other hand, if the product code is not stored in the checkout product master, a store clerk will handle the matter. Note that if there are multiple non-file products, a store clerk may be called if the non-file status has not been resolved for at least some of them (a store clerk may not be called if the non-file status has been resolved for all of them).

[0085] (Referenced product master for checkout) As described above, the checkout product master is transmitted from the headquarters server 10 to the store controller 30 to the checkout device 40, and is stored in each device (the headquarters server 10, the store controller 30, and the checkout device 40). Therefore, the checkout product master referenced when a non-file product is included in the transaction information obtained from the cloud server 20 may basically be the checkout product master stored in any device.

[0086] As an example, if the transaction information obtained from the cloud server 20 includes a non-file product, the product master for checkout in the checkout device 40 may be referenced in stages, as shown below: → product master for checkout in the store controller 30 → product master for checkout in the headquarters server 10.

[0087] (1) The settlement device 40 refers to the settlement product master stored in the device. If the NON-FILE is not resolved, the settlement device 40 inquires about the NON-FILE to the store controller 30 (for example, by sending NON-FILE inquiry information including the product code). (2) Upon receiving the NON-FILE inquiry information, the store controller 30 refers to the checkout product master stored in its own device. If the NON-FILE is resolved, the store controller 30 responds to the checkout device 40 to inform it of the resolution (for example, by sending the product name, price, etc.). On the other hand, if the NON-FILE is not resolved, the store controller 30 inquires about the NON-FILE to the headquarters server 10 (by sending the NON-FILE inquiry information). (3) Upon receiving the NON-FILE inquiry information, the headquarters server 10 refers to the checkout product master stored in its own device. If the NON-FILE is resolved, the headquarters server 10 responds to the store controller 30 that the issue has been resolved (by sending the product name, price, etc.). The store controller 30, having received the notification that the issue has been resolved, responds to the checkout device 40 that the issue has been resolved. On the other hand, if the NON-FILE is not resolved, the headquarters server 10 responds to the store controller 30 that the issue will not be resolved (by sending information that the issue will not be resolved). The store controller 30, having received the notification that the issue will not be resolved, responds to the checkout device 40 that the issue will not be resolved.

[0088] Furthermore, if there is a time lag in the process of transmitting the checkout product master (headquarters server 10 → store controller 30 → checkout device 40), there are cases where NON-FILE is resolved in the checkout product master in the store controller 30 even if it is not resolved in the checkout product master in the checkout device 40, and there are also cases where NON-FILE is resolved in the checkout product master in the headquarter server 10 even if it is not resolved in the checkout product master in the store controller 30.

[0089] Due to the time lag in the process of transmitting the checkout product master data (from the headquarters server 10 to the store controller 30 to the checkout device 40), the checkout product master data in the headquarters server 10 or the store controller 30 may always be referenced without referencing the checkout product master data in the checkout device 40, or the checkout product master data in the headquarters server 10 may always be referenced without referencing the checkout product master data in the checkout device 40 or the store controller 30. In the former case (when the checkout product master data in the checkout device 40 is not referenced), the store controller 30 does not transmit the checkout product master data to the checkout device 40 (i.e., the checkout device 40 does not store the checkout product master data therein). In the latter case, the headquarters server 10 does not transmit the checkout product master data to the store controller 30 (i.e., the store controller 30 and the checkout device 40 do not store the checkout product master data therein).

[0090] (Processing regarding special sale prices) The settlement device 40 refers to the sale file (FIG. 3(B)) and determines whether the products included in the transaction information acquired from the cloud server 20 (if the product names, prices, etc. of NON-FILE products are reflected, the transaction information after reflection) meet the sale conditions (i.e., whether the sale (discount, discount, etc.) is applied). If the sale conditions are not met, the operation ends. If the sale conditions are met, the settlement device 40 acquires the sale details (sale price, etc.) from the sale file, recalculates the total amount, and reflects it in the transaction information. Specifically, the settlement device 40 additionally stores the sale price, etc. acquired from the sale file without erasing (overwriting) the product prices, etc. before the sale price was applied, and additionally stores the recalculated total amount without erasing the total amount before the recalculation.

[0091] In other words, the settlement device 40 refers to the sale file that was not referenced when the product was registered on the mobile terminal 60, and if the conditions for applying the sale price (sale) are met, it obtains the applicable sale price etc. from the sale file, recalculates the total amount, and reflects it in the transaction information.

[0092] (referenced special offer file) Like the checkout product master, the sale file is transmitted from the headquarters server 10 to the store controller 30 to the checkout device 40, and is stored in each device (the headquarters server 10, the store controller 30, and the checkout device 40). Therefore, the sale file referenced may basically be a sale file stored in any device. For example, like the checkout product master, the sale file may be referenced in stages in the order of the sale file in the checkout device 40 → the sale file in the store controller 30 → the sale file in the headquarters server 10. Also, like the checkout product master, the sale file in the headquarters server 10 or the store controller 30 may always be referenced without referencing the sale file in the checkout device 40, or the sale file in the headquarters server 10 may always be referenced without referencing the sale file in the checkout device 40 or the store controller 30.

[0093] As described above, the settlement device 40 automatically reflects necessary information in the transaction information when settling (adds and updates necessary information to the transaction information). That is, if there are non-file products, the settlement device 40 additionally stores the prices of the non-file products and the recalculated total amount, etc. in the transaction information, and if a special sale applies, the settlement device 40 additionally stores the special sale price and the recalculated total amount, etc. in the transaction information.

[0094] (Example of operation of settlement device 40 (in case of transaction example 1)) For example, if a customer has the settlement device 40 read the settlement two-dimensional code 605 (the settlement two-dimensional code 605 shown in Figure 6(C)) displayed on the mobile terminal 60 after registering the product in Transaction Example 1 (Figures 5(C) to 6(B)), the settlement device 40 will obtain transaction information from the cloud server 20, including the following product: XX bread (product code "S0204", product name "XX bread", 1 item, ¥220) as the first product; XX oolong tea (product code "S0245", product name "XX oolong tea", 1 item, ¥150) as the second product; and a non-file product (product code "S0275", information indicating that it is a non-file product, 1 item) as the third product.

[0095] Because the transaction information includes a non-file product, the settlement device 40 references the settlement product master (Fig. 3(A)) and determines whether the product code "S0275" of the non-file product is stored in the settlement product master (Fig. 3(A)). Because the product code "S0275" of the non-file product is stored in the settlement product master, the settlement device 40 obtains the product name of the non-file product, "XX Snack", the price "¥160", etc., from the settlement product master, and recalculates the total amount to "¥530". Then, the settlement device 40 stores the product name "XX Snack" and the price "¥160" in the transaction information for the product with product code "S0275" without erasing the information that the product was a NON-FILE product, and stores the total amount after recalculation "¥530" without erasing the total amount before recalculation "¥370".

[0096] Next, the settlement device 40 refers to the sale file (FIG. 3(B)) and determines whether the product included in the transaction information (the transaction information updated as described above in connection with the NON-FILE) meets the sale conditions. The settlement device 40 determines that the product does not meet the sale conditions. In other words, the settlement device 40 does not update the transaction information related to the sale.

[0097] (Display example of settlement device 40 (transaction example 1)) Figure 11 is an example of the display on the settlement device 40 when the two-dimensional settlement code 605 shown in Figure 6(C) is read on the initial screen GM01 of Figure 10. When the settlement device 40 reads the two-dimensional settlement code 605 of Figure 6(C), it displays a product list screen GM02 as shown in Figure 11, and further displays a small screen SG10 in front of the product list screen GM02. The product list screen GM02 will be described later.

[0098] The small screen SG10 displays a message saying, "Product information was found, so some products have been automatically registered." This message notifies the user that a non-file product has been automatically registered (i.e., that the non-file has been automatically canceled). In other words, when the settlement device 40 automatically registers a non-file product, it uses the small screen SG10 to notify the user that the non-file product has been automatically registered. The settlement device 40 also uses the icon ICN415 (described below) on the product list screen GM02 to notify the user that the automatically registered product is an automatically registered product. The small screen SG10 has an OK button. The OK button is used to confirm the message on the small screen SG10 and to close the small screen SG10.

[0099] Fig. 12 is a display example of the settlement device 40 when the OK button is operated on the small screen SG10 of Fig. 11. When the OK button is operated, the settlement device 40 clears the small screen SG10 (i.e., simply displays the product list screen GM02) as shown in Fig. 12.

[0100] The product list screen GM02 has a product list display area HR410, a product quantity by price range display area HR411, and a total display area HR412. The product list screen GM02 also has a store clerk call button BT401 and a checkout button BT409. The checkout button BT409 is a button for confirming that there are no problems with the content displayed on the product list screen GM02 and for proceeding with the process.

[0101] The product list display area HR410 is an area for displaying a list of products to be settled (purchased). The settlement device 40 displays a list of products (product name, quantity, price) included in the transaction information acquired by reading the settlement two-dimensional code 605 (or the updated transaction information if the settlement device 40 has updated the content) in the product list display area HR410.

[0102] In the example of FIG. 12, the settlement device 40 displays XX bread, XX oolong tea, and XX snack in the product list display area HR410. XX bread is the first product in transaction example 1 (FIG. 5(D)). XX oolong tea is the second product in transaction example 1 (FIG. 6(A)). XX snack is the third product in transaction example 1 (FIG. 6(B)), and is a product that was automatically registered by the settlement device 40. In addition, the icon ICN415 displayed in association with XX snack indicates that it is a product that was automatically registered by the settlement device 40.

[0103] The price range product quantity display area HR411 is an area for displaying the quantity of products to be paid for (purchased) by price range (over 1,000 yen, between 500 yen and 1,000 yen, between 200 yen and 500 yen, and under 200 yen).

[0104] The total display area HR412 is an area for displaying the total of the transaction. In the example of FIG. 12, the settlement device 40 displays in the total display area HR412 a total number of items of 3 ("Total 3 items" in the figure), an estimated total amount of 370 yen ("Estimated total (amount displayed on smartphone) 370 yen" in the figure), and a final total amount of 530 yen ("Final total (payment amount) 530 yen" in the figure). The estimated total amount of 370 yen is the total amount displayed on the mobile terminal 60 (the total amount excluding the price of "XX snack" (160 yen) automatically registered by the settlement device 40; the total amount before recalculation). The final total amount of 530 yen is the total amount recalculated by the settlement device 40 (the total amount including the price of "XX snack" (160 yen) automatically registered by the settlement device 40).

[0105] In this example, the product code "S0275" for the XX snacks is not stored in the product master for registration (the price, etc., of the product with the product code "S0275" cannot be obtained when registering using the mobile terminal 60), but if the product code "S0275" for the XX snacks were stored in the product master for registration (the mobile terminal 60 could obtain the price, etc., of the product with the product code "S0275"), both the estimated total amount and the final total amount would be 530 yen. In other words, if the settlement device 40 does not recalculate the total amount, it displays the total amount displayed by the mobile terminal 60 as the estimated total amount and the final total amount in the total display area HR412. If the settlement device 40 recalculates the total amount, it displays the total amount displayed by the mobile terminal 60 (the total amount before recalculation) as the estimated total amount in the total display area HR412, and the total amount after recalculation as the final total amount.

[0106] Also, in this example, the product code "S0275" of the XX snack is stored in the product master for checkout (the price etc. of the product with product code "S0275" can be obtained at the time of checkout using the checkout device 40), but if the product code "S0275" of the XX snack is not stored in the product master for checkout (if the price etc. of the product with product code "S0275" cannot be obtained at the time of checkout using the checkout device 40, in other words, if the NON-FILE cannot be resolved), the store clerk will enter the price etc. at the checkout device 40.

[0107] Figure 13 is an example of the display on the settlement device 40 when the checkout button BT409 is operated on the product list screen GM02 in Figure 12. When the checkout button BT409 is operated, the settlement device 40 displays a payment type selection screen GM03, as shown in Figure 13.

[0108] The payment type selection screen GM03 has a payment type selection area SR420 and a captured image display area HR421. The payment type selection screen GM03 also has a store clerk call button BT401, a balance inquiry button BT402, language switch buttons BT403 to BT405, and a back button BT419. The back button BT419 is a button for returning to the product list screen GM02.

[0109] The payment type selection area SR420 is an area for selecting a payment type (payment method). In the payment type selection area SR420, buttons corresponding to various payment types such as cash, credit card, etc. are arranged.

[0110] The captured image display area HR421 is an area for displaying a captured image of the customer. For example, the settlement device 40 may capture an image of the area around the change machine 409 (i.e., the customer's hands operating the change machine 409) using its own camera (imaging unit 416) and display the captured image in the captured image display area HR421, or may display an image captured by an external camera (a camera installed in a position where it can capture an image of the area around the change machine 409) in the captured image display area HR421. The captured image displayed in the captured image display area HR421 may be a real-time output of the current situation (live view / through image), or may be a temporarily stored image played back. The captured image may be a video or a still image (for example, a continuously displayed still image).

[0111] When a payment type is selected on the payment type selection screen (when a button corresponding to a payment type is operated in the payment type selection area SR420), the settlement device 40 displays a payment screen corresponding to the selected payment type and executes the payment according to the selected payment type. For example, when the cash button (cash payment) is operated in the payment type selection area SR420, the settlement device 40 sequentially displays payment screens (payment screens appropriately displaying the confirmed total amount, the amount deposited (amount deposited), the amount shortfall, the amount of change, various messages, etc.) according to the progress of the customer's actions related to the cash payment (button operation, cash insertion, etc.), executes the payment process based on the confirmation operation on the payment screen (operation to execute the payment process), dispenses the change if any, and prints and issues a receipt. For example, when the credit button (an example of non-cash payment) is operated in the payment type selection area SR420, the settlement device 40 sequentially displays payment screens (payment screens appropriately displaying the finalized total amount, number of payments, PIN number, various messages, etc.) according to the progress of the customer's actions (button operation, card insertion, etc.) related to the non-cash payment by the card payment unit 408, and based on the confirmation operation on the payment screen, causes the card payment unit 408 to execute the payment process (or the settlement device 40 itself executes the payment process), and prints and issues a receipt.

[0112] (Example of operation of settlement device 40 (in case of transaction example 2)) For example, if a customer has the settlement device 40 read the two-dimensional settlement code 605 (two-dimensional settlement code 605 shown in Figure 7(D)) displayed on the mobile terminal 60 after registering the product in transaction example 2 (Figures 7(A) to 7(C)), the settlement device 40 will obtain transaction information from the cloud server 20, including the following product: XX Gyoza (product code "S0123", product name "XX Gyoza", 1 item, ¥290) as the first product, XX Stir Fry (product code "S0144", product name "XX Stir Fry", 1 item, ¥420) as the second product, and XX Socks (product code "S0597", product name "XX Socks", 3 items, ¥900) as the third product.

[0113] Since the transaction information does not include any non-file products, the settlement device 40 does not update the transaction information related to the non-file products.

[0114] Next, the settlement device 40 refers to the sale file (FIG. 3(B)) and determines whether the product included in the transaction information matches the sale conditions. The settlement device 40 determines that the sale conditions are met (specifically, the sale conditions for sale code "T003"), obtains the sale details (sale price "¥800" for sale code "T003") from the sale file, and recalculates the total amount "¥1510". The settlement device 40 then stores the sale price of the target product ("¥800" for three pairs of XX socks) in the transaction information without deleting the price of the target product before the sale price was applied ("¥900" for three pairs of XX socks), and stores the recalculated total amount "¥1510" without deleting the total amount before the recalculation ("¥1610").

[0115] (Example of display on settlement device 40 (transaction example 2)) Figure 14 is an example of the display on the settlement device 40 when the two-dimensional settlement code 605 shown in Figure 7(D) is read on the initial screen GM01 of Figure 10. When the settlement device 40 reads the two-dimensional settlement code 605 of Figure 7(D), it displays a product list screen GM02 as shown in Figure 14.

[0116] In the example of Figure 14, the settlement device 40 displays XX dumplings, XX stir fry, and XX socks in the product list display area HR410. XX dumplings are the first item in transaction example 2 (Figure 7(A)). XX stir fry is the second item in transaction example 2 (Figure 7(B)). XX socks are the third item in transaction example 2 (Figure 7(C)). In addition, the icon ICN417 displayed in association with XX socks indicates that the product is on sale.

[0117] In the example of FIG. 14, the settlement device 40 displays in the total display area HR412 the total points as 5 (shown as "5 points total" in the figure), the estimated total amount as 1,610 yen (shown as "Estimated total (amount displayed on smartphone) ¥1,610" in the figure), the final total amount as 1,510 yen (shown as "Final total (payment amount) ¥1,510" in the figure), and the difference between the estimated total amount and the final total amount, in this example, -100 yen (shown as "-¥100" in the figure) as the difference obtained by subtracting the estimated total amount from the final total amount. The estimated total amount of 1,610 yen is the total amount displayed on the mobile terminal 60 (the total amount before recalculation). The final total amount of 1,510 yen is the total amount recalculated by the settlement device 40.

[0118] The settlement device 40 can display the details of the sale applied to a product to which a special sale price has been applied (such socks in Transaction Example 2). For example, the settlement device 40 displays the details of the sale applied to a product to which a special sale price has been applied based on an operation.

[0119] Figure 15 is an example of the display on the checkout device 40 when the area for the XX socks to which a special sale price has been applied is operated in the product list display area HR410 of the product list screen GM02 in Figure 14 (for example, when the icon ICN417 is operated).

[0120] When the area of ​​the XX socks to which a sale price has been applied is operated, the settlement device 40 enlarges the area as shown in Fig. 15, makes the sale content display area HR418 appear within the enlarged area, and displays the details of the sale applied to the XX socks (in this example, "100 yen off every three XX socks (¥900 → ¥800)") in the sale content display area HR418. When the close button located in the sale content display area HR418 is operated, the settlement device 40 reduces the area of ​​the XX socks to the original display (deletes the sale content display area HR418) (Fig. 15 → Fig. 14).

[0121] Note that the payment type selection screen GM03 that is displayed when the checkout button BT409 is operated on the product list screen GM02 of FIG. 14 or FIG. 15 has the same configuration as the payment type selection screen GM03 (FIG. 13) that is displayed when the checkout button BT409 is operated on the product list screen GM02 of FIG. 12, so illustrations and explanations are omitted.

[0122] (Example of operation of settlement device 40 (in case of transaction example 3)) For example, if a customer has the settlement device 40 read the two-dimensional settlement code 605 (two-dimensional settlement code 605 shown in FIG. 8(D)) displayed on the mobile terminal 60 after registering the product in Transaction Example 3 (FIGS. 8(A) to 8(C)), the settlement device 40 acquires transaction information from the cloud server 20, including the following product: XX bento (product code "S0175", product name "XX bento", 1 item, 620 yen) as the first product; XX green tea (product code "S0215", product name "XX green tea", 1 item, 130 yen) as the second product; and XX salad (product code "S0170", product name "XX salad", 1 item, 280 yen) as the third product. It is assumed that the time is after 8:00 PM.

[0123] Since the transaction information does not include any non-file products, the settlement device 40 does not update the transaction information related to the non-file products.

[0124] Next, the settlement device 40 refers to the sale file (FIG. 3(B)) and determines whether the product included in the transaction information matches the sale conditions. The settlement device 40 determines that the product matches the sale conditions (specifically, matches the sale conditions for sale code "T002" and sale code "T004"), obtains the sale details from the sale file (the sale price "30 yen off" for sale code "T002", the 30 yen off and 50 yen off for sale code "T0004"), and recalculates the total amount to "920 yen." Then, the settlement device 40 stores the sale prices of the target products ("¥555" for the XX bento, "¥115" for the XX green tea, and "¥250" for the XX salad) in the transaction information without erasing the prices of the target products before the sale prices were applied ("¥620" for the XX bento, "¥130" for the XX green tea, and "¥280" for the XX salad), and stores the total amount after the recalculation ("¥920") without erasing the total amount before the recalculation ("¥1030").

[0125] (Example of display on settlement device 40 (transaction example 3)) Figure 16 is an example of the display on the settlement device 40 when the two-dimensional settlement code 605 shown in Figure 8(D) is read on the initial screen GM01 of Figure 10. When the settlement device 40 reads the two-dimensional settlement code 605 of Figure 8(D), it displays a product list screen GM02 as shown in Figure 16.

[0126] The settlement device 40 obtains the transaction information of the transaction (the transaction in which the mobile terminal 60 registered the product of Transaction Example 3) from the cloud server 20 by reading the settlement two-dimensional code 605 of FIG. 8(D).

[0127] In the example of FIG. 16, the settlement device 40 displays XX bento, XX green tea, and XX salad in the product list display area HR410. XX bento is the first product in transaction example 3 (FIG. 8(A)). XX green tea is the second product in transaction example 3 (FIG. 8(B)). XX salad is the third product in transaction example 3 (FIG. 8(C)). Icons ICN417 displayed in association with each of XX bento, XX green tea, and XX salad indicate that a special sale price has been applied to the product.

[0128] In the example of FIG. 16, the settlement device 40 displays in the total display area HR412 a total of 3 points (shown as "Total 3 points" in the figure), an estimated total of 1,030 yen (shown as "Estimated total (amount displayed on smartphone) ¥1,030" in the figure), a confirmed total of 920 yen (shown as "Confirmed total (amount to be paid) ¥920" in the figure), and a difference of -110 yen (shown as "-¥110" in the figure) obtained by subtracting the estimated total from the confirmed total. The estimated total of 1,030 yen is the total amount displayed on the mobile terminal 60. The confirmed total of 920 yen is the total amount recalculated by the settlement device 40.

[0129] Figure 17 is an example of the display on the settlement device 40 when the areas for XX bento, XX green tea, and XX salad, to which a sale price has been applied, are all operated in the product list display area HR410 of the product list screen GM02 in Figure 16. As shown in Figure 17, the settlement device 40 displays the details of the sale applied to the XX bento when the XX bento area is operated, displays the details of the sale applied to the XX green tea when the XX green tea area is operated, and displays the details of the sale applied to the XX salad when the XX salad area is operated.

[0130] Note that the payment type selection screen GM03 that is displayed when the checkout button BT409 is operated on the product list screen GM02 of FIG. 16 or FIG. 17 has the same configuration as the payment type selection screen GM03 (FIG. 13) that is displayed when the checkout button BT409 is operated on the product list screen GM02 of FIG. 12, so illustrations and explanations are omitted.

[0131] Figure 18 is a sequence diagram showing an example of the processing of the settlement device 40 and cloud server 20. Specifically, the sequence diagram of Figure 18 shows an example of the processing of the settlement device 40 and cloud server 20 from when the settlement two-dimensional code 605 is read by the settlement device 40 until the payment type selection screen GM03 is displayed. The left side of Figure 18 shows the processing of the settlement device 40, and the right side shows the processing of the cloud server 20. It is assumed that at the start of the sequence diagram of Figure 18, the settlement device 40 is displaying the initial screen GM01 as shown in Figure 10.

[0132] Step S11: In response to a reading operation by the customer, the settlement device 40 reads the settlement two-dimensional code 605 displayed on the mobile terminal 60. In other words, the settlement device 40 obtains transaction identification information that identifies the transaction information of the transaction. Step S12: The settlement device 40 requests transaction information of the transaction from the cloud server 20. For example, the settlement device 40 transmits request information (transaction information acquisition request information) including transaction identification information that identifies the transaction information of the transaction to the cloud server 20.

[0133] Step S13: The cloud server 20 receives the request (transaction information acquisition request information). Step S14: In response to the request, the cloud server 20 transmits the transaction information of the transaction to the settlement device 40. For example, the cloud server 20 transmits to the settlement device 40 the transaction information corresponding to the transaction identification information included in the transaction information acquisition request information received in step S13.

[0134] Step S15: The settlement device 40 receives and stores the transaction information of the transaction. Step S16: If a non-file product is included, the settlement device 40 refers to the settlement product master, and if the product code is stored in the settlement product master, obtains the product name, price, etc. of the product, recalculates the total amount, and reflects it in the transaction information (additionally stores it). The details of step S16 have already been explained in "Processing for non-file products," so they will be omitted here.

[0135] Step S17: The settlement device 40 refers to the sale file, and if the sale conditions are met, acquires the details of the sale (sale price, etc.), recalculates the total amount, and reflects it in the transaction information (additionally stores it). The details of step S17 have already been explained in "Processing related to sale prices," so they will be omitted here.

[0136] Step S18: The settlement device 40 displays the product list screen GM02 based on the transaction information. For example, in transaction example 1, the settlement device 40 displays the product list screen GM02 as shown in FIG. 11, in transaction example 2, the product list screen GM02 as shown in FIG. 14, and in transaction example 3, the product list screen GM02 as shown in FIG. 16. Note that since FIG. 11 shows a scene after the processing of step S19 (described below), the small screen SG10 displayed in step S19 is displayed in front of the product list screen GM02 displayed in step S18. Step S19: When the NON-FILE is resolved, the settlement device 40 notifies the user that the NON-FILE has been automatically resolved (that the NON-FILE product has been automatically registered). For example, the settlement device 40 displays a small screen SG10 as shown in FIG. 11 in front of the product list screen GM02.

[0137] Step S20: The settlement device 40 displays the payment type selection screen GM03 based on the customer's confirmation operation (operation of the checkout button BT409 on the product list screen GM02), and the sequence diagram in Fig. 18 ends.

[0138] FIG. 19 is a sequence diagram showing an example of processing by the settlement device 40, store controller 30, headquarters server 10, cloud server 20, and mobile terminal 60. Specifically, the sequence diagram of FIG. 19 shows an example of processing by the settlement device 40, store controller 30, headquarters server 10, cloud server 20, and mobile terminal 60 after the settlement device 40 displays the payment type selection screen GM03. The leftmost part of FIG. 19 shows processing by the settlement device 40, the second from the left shows processing by the store controller 30, the third from the left (middle) shows processing by the headquarters server 10, the fourth from the left (second from the right) shows processing by the cloud server 20, and the rightmost part shows processing by the mobile terminal 60. It is assumed that at the start of the sequence diagram of FIG. 19, the settlement device 40 displays the payment type selection screen GM03 as shown in FIG. 13.

[0139] Step S31: The settlement device 40 executes the settlement process based on the customer's operation (confirmation operation on the settlement screen). That is, the settlement device 40 displays the settlement screen according to the payment type selected on the payment type selection screen GM03, and executes the settlement process based on the confirmation operation on the settlement screen.

[0140] Step S32: The settlement device 40 transmits payment information (transaction result information) to the store controller 30. Furthermore, if the NON-FILE has been resolved, the settlement device 40 transmits NON-FILE resolution information to the store controller 30 in addition to the payment information. The payment information includes, for example, transaction identification information, detailed information (product code, quantity), payment method, payment amount, etc. The NON-FILE resolution information is information indicating that the NON-FILE has been resolved (that the NON-FILE has been resolved), and includes, for example, the product code, product name, price, etc. The settlement device 40 may transmit the NON-FILE resolution information to the store controller 30 as part of the payment information.

[0141] Step S33: In the case of cash payment, the settlement device 40 dispenses change if there is any. Step S34: The settlement device 40 prints and issues a receipt. The settlement device 40 may be equipped with a sensor that can detect the removal of change, and may print and issue a receipt after detecting the removal of the dispensed change when the change has been dispensed. Step S35: The settlement device 40 displays the initial screen GM01. The settlement device 40 may be equipped with a sensor that can detect the removal of a receipt, and may display the initial screen GM01 after detecting the removal of an issued receipt.

[0142] Step S36: The store controller 30 receives the payment information. In addition to the payment information, the store controller 30 may also receive NON-FILE resolution information. Step S37: The store controller 30 transmits the payment information to the head office server 10. If the store controller 30 has also received the NON-FILE resolution information, it also transmits the NON-FILE resolution information to the head office server 10.

[0143] Step S38: The head office server 10 receives the payment information. In addition to the payment information, the head office server 10 may also receive NON-FILE resolution information. Step S39: The head office server 10 transmits the payment information to the cloud server 20. If the head office server 10 has also received the NON-FILE resolution information, it transmits the NON-FILE resolution information to the cloud server 20 as well. Step S40: The headquarters server 10 records the results. For example, the headquarters server 10 updates the results information (sales results information, etc.) based on the payment amount, etc. included in the payment information. The headquarters server 10 also updates the results information (product sales results information, etc.) based on the detailed information, etc. included in the payment information. This results information may be aggregated and used, for example, for accounting (financial accounting, management accounting), ordering, product development, etc.

[0144] Step S41: The cloud server 20 receives payment information. In addition to the payment information, the cloud server 20 may also receive NON-FILE resolution information. Step S42: Cloud server 20 updates the transaction information for the transaction (storing information related to settlement completion). For example, cloud server 20 identifies the transaction information for the transaction based on the transaction identification information included in the payment information. Cloud server 20 additionally stores information (information related to the payment method, payment amount) based on the payment method, payment amount, etc. included in the payment information within the transaction information for the transaction. Note that while it is possible to determine whether a payment (transaction) is incomplete or complete based on whether the payment amount, etc. is stored, cloud server 20 may additionally store information indicating payment completion (transaction completion) within the transaction information for the transaction. (Note that if the transaction information includes a processing status classification (status) as a data item, the processing status classification may be updated to a classification (status) indicating payment completion (transaction completion) rather than additionally storing the information.)

[0145] Step S43: The cloud server 20 transmits payment completion information to the mobile terminal 60 indicating that the payment (transaction) has been completed. Step S44: If the cloud server 20 has received the NON-FILE resolution information, it updates the provisional product file. For example, the cloud server 20 adds the product code, product name, price, etc. included in the NON-FILE resolution information to the provisional product file.

[0146] Step S45: The mobile terminal 60 receives the payment completion information. Step S46: The mobile terminal 60 displays a transaction completion screen (not shown). That is, upon receiving the payment completion information, the mobile terminal 60 switches the display from the two-dimensional code display screen to the transaction completion screen. The transaction completion screen may be provided with, for example, an OK button, and the mobile terminal 60 may erase the transaction completion screen upon operation of the OK button.

[0147] If the estimated total amount differs from the confirmed total amount, information relating to this may be displayed on the transaction completion screen displayed by the mobile terminal 60 in step S46. For example, the mobile terminal 60 may display the estimated total amount and the confirmed total amount on the transaction completion screen, or may display the estimated total amount, the confirmed total amount, and the difference (the difference obtained by subtracting the estimated total amount from the confirmed total amount), or may display the confirmed total amount and the difference. Furthermore, if a special sale price has been applied, the mobile terminal 60 may display, instead of or in addition to the above amounts, etc., on the transaction completion screen, a message that the special sale price has been applied, the products to which the special sale price has been applied, details of the sale, etc.

[0148] As described above, the sales system 1 solves (eliminates or reduces) some of the various problems that occur during payment.

[0149] (1) According to the sales system 1, the information required for payment is automatically added (or supplemented) at the time of payment. This reduces the burden on store clerks and shortens payment time.

[0150] For example, at checkout, if a non-file product is not automatically registered, a store clerk is called and the called store clerk must register the non-file product. However, in the sales system 1, the checkout device 40 references the checkout product master and, if it is possible to register a non-file product, automatically registers the non-file product. This eliminates the burden on the store clerk. As long as there are at least situations where non-file products are automatically registered (as long as there are fewer situations where non-file products are not automatically registered), this will at least contribute to reducing the burden on the store clerk. Furthermore, checkout time will be reduced compared to when a store clerk registers a non-file product. As long as there are at least situations where non-file products are automatically registered, this will at least contribute to reducing the checkout time.

[0151] (2) According to the sales system 1, when the information necessary for the settlement is automatically replenished, the customer is notified of the replenishment. In other words, even when the information necessary for the settlement is automatically replenished, the accounting details are clear, so that the customer does not feel uneasy or misunderstood.

[0152] For example, when a non-file product is automatically registered, the settlement device 40 notifies the customer that the non-file product has been automatically registered (FIG. 11). Therefore, when a non-file product is automatically registered, the customer can easily recognize (understand) that the non-file product has been automatically registered. This prevents (or at least makes it less likely to cause) anxiety or misunderstanding that could arise if the customer did not recognize the information.

[0153] Furthermore, for example, when a non-file product is automatically registered or a special sale price is reflected, the settlement device 40 notifies the customer of which product is the target product (the product automatically registered or the product to which the special sale price is applied) (FIGS. 12, 14, 15, 16, and 17). Therefore, when a non-file product is automatically registered or a special sale price is reflected, the customer can easily recognize the target product. This prevents (or at least makes it less likely to cause) anxiety or misunderstanding that could arise if the product were not recognized.

[0154] Furthermore, for example, when the sale price is reflected, the settlement device 40 notifies the customer of the details of the sale (FIGS. 15 and 17). Therefore, when the sale price is reflected, the customer can easily recognize the details of the sale. This prevents (or at least makes it less likely to cause) anxiety or misunderstanding that may arise if the customer does not recognize the details.

[0155] Furthermore, for example, when a non-file product is automatically registered or a sale price is reflected, the settlement device 40 displays the total amount after the non-file product is registered or after the sale price is reflected, along with the total amount before the non-file product is registered or before the sale price is reflected (FIGS. 12, 14, 15, 16, and 17). Therefore, when a non-file product is automatically registered or a sale price is reflected, the customer can easily recognize that the total amount has increased or decreased and the extent of the increase or decrease. This prevents (or at least makes it less likely to cause) anxiety or misunderstanding that could arise if the customer were not aware of this.

[0156] In the above embodiment, transaction example 1 (FIGS. 6, 11, 12, etc.) for non-file products and transaction example 2 (FIGS. 7, 14, 15, etc.) and transaction example 3 (FIGS. 8, 16, 17, etc.) for products to which a special sale price is applied are used for explanations, but when non-file products and products to which a special sale price are applied are mixed in a single transaction, each product is processed in the same way. For example, when the settlement device 40 reads the settlement two-dimensional code 605 for a transaction in which non-file products and products to which a special sale price are applied are mixed in a single transaction, if the non-file is resolved, the small screen SG10 is displayed, and if the special sale price is applied, the total amount after the non-file is resolved and the special sale price is applied is recalculated on the product list screen GM02. In addition, the settlement device 40 displays the recalculated total amount (confirmed total amount) together with the estimated total amount, etc. in the total display area HR412 of the product list screen GM02, and adds the icon ICN415 to products for which the NON-FILE status has been resolved (i.e., products that have been automatically registered) and the icon ICN417 to products for which a special sale price has been applied, in the product list display area HR410 of the product list screen GM02.

[0157] (Variations, etc.) Although the embodiments have been described above, the device configuration, data configuration, processing flow, display and output modes, etc. can be appropriately changed as shown in the following (1), (2), etc. In addition, the following (1), (2), etc. can be appropriately combined.

[0158] (1) For example, in the above embodiment, the settlement device 40 was described as automatically reflecting necessary information in the transaction information at the time of settlement (adding and updating necessary information to the transaction information), but the necessary information may also be automatically reflected in the transaction information after a customer confirmation operation. For example, when the settlement device 40 reads the settlement two-dimensional code 605 for a transaction including a non-file product (for example, the settlement two-dimensional code 605 in FIG. 6(C)), it may display a small screen with a confirmation button (which may display a message indicating that there is a non-file product and that registration will be attempted again), and based on the operation of the confirmation button, it may refer to the settlement product master, and if the non-file is resolved, it may display a small screen SG10 indicating that the non-file product has been automatically registered (that the non-file has been automatically resolved).

[0159] (2) In the above embodiment, when a non-file product is automatically registered, the small screen SG10 notifies the user that the non-file product has been automatically registered (Figure 11), but the manner of notification is not limited to this.

[0160] For example, the automatic registration of a non-file product may be notified on the same full screen (entire screen) as the product list screen GM02. Specifically, when the two-dimensional checkout code 605 shown in FIG. 6(C) is read, the checkout device 40 may display a full screen (automatic product registration notification screen) notifying the user that a non-file product has been automatically registered. The automatic product registration notification screen may also be provided with an OK button, and when the OK button is operated, the checkout device 40 may display the product list screen GM02 (FIG. 12) instead of the automatic product registration notification screen. Regarding timing, the notification example using the small screen SG10 is an example in which the display of the small screen SG10 is started while the product list screen GM02 is being displayed (after the display starts) (steps S18 and S19 in FIG. 18), but the notification example using the automatic product registration notification screen is an example in which the display of the automatic product registration notification screen is started before the display of the product list screen GM02 starts.

[0161] Also, for example, it is not necessary to provide a dedicated screen (small screen SG10, automatic product registration notification screen) for notifying that a non-file product has been automatically registered. Specifically, when the settlement two-dimensional code 605 shown in Fig. 6(C) is read, the settlement device 40 may display a product list screen GM02 displaying a message or the like to the effect that a non-file product has been automatically registered (a product list screen GM02 in Fig. 12 that displays the above message or the like).

[0162] (3) In the above embodiment, when a non-file product is automatically registered, a notification is given that the non-file product has been automatically registered (FIG. 11). However, even when a non-file product is automatically registered, there may be cases where the notification is not given that the non-file product has been automatically registered. For example, when there are multiple non-file products, if all of the non-file products are automatically registered (if all of the non-files are resolved), a notification is given that the non-file products have been automatically registered, and if some of the non-file products are automatically registered (if some of the non-files are not resolved), a notification is not given that the non-file products have been automatically registered.

[0163] (4) When there are multiple non-file products and at least some of the non-file products are automatically registered (when some or all of the non-file products are resolved), the number of products automatically registered (number of resolved products) may be notified. Also, when there are multiple non-file products and at least some of the non-file products are not automatically registered (when some or all of the non-file products are not resolved), the number of products that were not automatically registered (number of products not resolved) may be notified.

[0164] (5) In the above embodiment, when a non-file product is automatically registered, the automatically registered product is notified using icon ICN415 (indicating which product is the automatically registered product) (FIG. 12), but the notification method is not limited to this. Instead of or in addition to icon ICN415, the automatically registered product may be notified using the size of the product name, the color of the product name, the blinking of the product name, the background of the product name, etc. The same applies when a special sale price is applied. That is, in the above embodiment, the product to which a special sale price is applied is notified using icon ICN417, but instead of or in addition to icon ICN417, the product to which a special sale price is applied may be notified using the size of the product name, the color of the product name, the blinking of the product name, the background of the product name, etc.

[0165] (6) In the above embodiment, when a non-file product is automatically registered, the estimated total amount and the finalized total amount are displayed, and the difference obtained by subtracting the estimated total amount from the finalized total amount is not displayed (FIG. 12). However, the display of the total amount when a non-file product is automatically registered is not limited to this. For example, the estimated total amount, the finalized total amount, and the difference may be displayed. Alternatively, the finalized total amount may be displayed, and the estimated total amount and the difference may not be displayed.

[0166] (7) In the above embodiment, when a sale price is reflected, the estimated total amount, the finalized total amount, and the difference obtained by subtracting the estimated total amount from the finalized total amount are displayed (e.g., FIG. 14 ). However, the display of the total amount when a sale price is reflected is not limited to this. For example, the estimated total amount and the finalized total amount may be displayed, without displaying the difference. Alternatively, the finalized total amount may be displayed, without displaying the estimated total amount and the difference.

[0167] (8) In relation to (6) and (7) above, the display of the total amount etc. is not limited to the display format shown in the above embodiment (FIGS. 12, 14, 16, etc.).

[0168] FIG. 20 is an example of a display on the settlement device 40. Each of FIGS. 20(A) to 20(D) shows a portion (lower portion) of the product list screen GM02. The settlement device 40 may display, for example, a product list screen GM02 as shown in FIG. 20(A), 20(B), 20(C), or 20(D) instead of the product list screen GM02 of transaction example 2 (the product list screen GM02 of FIG. 14).

[0169] In each example shown in Figures 20(A) to 20(D), the settlement device 40 displays "Smartphone Display Amount" instead of "Estimated Total Amount." Furthermore, in each example shown in Figures 20(C) and 20(D), the settlement device 40 displays "Payment Amount" instead of "Confirmed Total Amount." Furthermore, in each example shown in Figures 20(A) and 20(B), the settlement device 40 does not display either "Confirmed Total Amount" or "Payment Amount." Furthermore, for example, in each example shown in Figures 20(A), 20(B), and 20(C), the settlement device 40 displays the confirmed total amount (¥1510) larger than the estimated total amount (¥1610). Note that instead of or in addition to size, the confirmed total amount may be displayed more prominently than the estimated total amount by using text color, flashing, background, or the like. 20(C) and 20(D), a speech bubble (or the outer portion of the total display area HR412) is used to emphasize the fact that the price has become cheaper. It is also possible to emphasize the fact that the price has become cheaper by using animation or the like. In the examples shown in FIGS. 20(B) and 20(D), the amount of the discount (100 yen) is displayed in large letters. Instead of or in addition to the size, the amount of the discount may be emphasized by using text color, blinking, background, or the like. In the example shown in FIG. 20(C), the reason for the discount (discount) is displayed. The manner of notifying the reason for the discount is not limited to this. For example, the total display area HR412 may simply display words such as "Discount" or "Discount Applied," or a mark, design, icon, or the like indicating the discount may be displayed. While FIG. 20 shows a sale, the same applies to non-file items.

[0170] (9) In the above embodiment, the product list screen GM02 displays the details of the sale applied to a product based on an operation on the area of ​​the product to which a sale price has been applied (e.g., icon ICN417) (FIGS. 15 and 17). However, the operation of displaying the details of the sale is not limited to this. For example, a difference button (a button displaying the difference) may be placed in the total display area HR412 (i.e., the difference display may be made into a button), and the details of the sale applied to each product may be displayed based on the operation of the difference button. In the example of FIG. 14, a difference button displaying "-¥100" may be placed in the total display area HR412, and when the difference button is operated, the details of the sale for "XX Socks" may be displayed as shown in FIG. 15. In the example of FIG. 16, a difference button displaying "-¥110" may be placed in the total display area HR412, and when the difference button is operated, the details of the sale for "XX Lunch Box," "XX Green Tea," and "XX Salad" may be displayed as shown in FIG. 17. In addition, the operation of the area of ​​the product to which the special sale price is applied and the operation of the price difference button may coexist.

[0171] (10) In the above embodiment, the product list screen GM02 does not have the language switch buttons BT403 to BT405, but the product list screen GM02 may have the language switch buttons BT403 to BT405. The same applies to the balance inquiry button BT402 and the captured image display area HR421.

[0172] (11) In the above embodiment, the flow of information transmission and reception after the settlement process at the settlement device 40 is described as the flow from settlement device 40 → store controller 30 → headquarters server 10 → cloud server 20 → mobile terminal 60 in Fig. 19, but the flow of transmission and reception is not limited to this. For example, NON-FILE resolution information may be transmitted from settlement device 40 → store controller 30 → cloud server 20 (finally transmitted to cloud server 20 without passing through headquarters server 10), or from settlement device 40 → cloud server 20 (transmitted directly to cloud server 20 without passing through store controller 30 and headquarters server 10).

[0173] (12) In the above embodiment, when product information corresponding to a product code read by the mobile terminal 60 is not stored in the registration product master ( FIG. 4(A)), the settlement device 40 automatically registers the product information corresponding to the product code by referring to the registration product master ( FIG. 3(A)). However, the situation in which automatic registration is performed is not limited to this. For example, when product information corresponding to a product code read by the mobile terminal 60 is stored in the registration product master ( FIG. 4(A)), but the product information cannot be obtained from the registration product master at the time of product registration (e.g., due to a communication problem, processing capacity problem, or software or hardware malfunction), the settlement device 40 may automatically register the product information corresponding to the product code by referring to the registration product master ( FIG. 3(A)). In other words, this method is applicable to all situations in which a product code is obtained at the time of product registration but product information corresponding to the product code cannot be obtained.

[0174] Note that a product for which product information corresponding to the product code read by the mobile terminal 60 is not stored in the product master for registration and therefore the product information cannot be acquired from the product master for registration at the stage of product registration (here, referred to as a type 1 unregistered product), and a product for which product information corresponding to the product code read by the mobile terminal 60 is stored in the product master for registration but the product information cannot be acquired from the product master for registration at the stage of product registration (here, referred to as a type 2 unregistered product), may be collectively referred to as an unregistered product. Also, in the above embodiment, the type 1 unregistered product is referred to as a "NON-FILE product," and the mobile terminal 60 displays the type 1 unregistered product (NON-FILE product) as an "unregistered product" (FIGS. 6(B)(C)), but the mobile terminal 60 may also display the type 2 unregistered product as an "unregistered product" in the same way as the type 1 unregistered product. That is, at least for the customer, it is not necessary to distinguish between unregistered products of type 1 and unregistered products of type 2. Alternatively, the mobile terminal 60 may distinguish between the two by displaying unregistered products of type 1 as "unregistered products (not registered in master)" and unregistered products of type 2 as "unregistered products (XX abnormality)."

[0175] (13) In the above embodiment, the types of sales in the sales file shown in Figure 3(B) were exemplified as mix match (sale code "T001"), set match (sale code "T002"), bundle (sale code "T003"), and limited time special price (sale code "T004"), but the types of sales are not limited to these. For example, the types of sales may be a discount on a specific product (a fixed or specified product each time) on a specific date (e.g., a specified date each month), a discount based on the total amount, or a discount based on past purchasing history (accumulated (total) purchase amount, etc.).

[0176] (14) In the above embodiment, an example was described in which all types of special sales are referenced for the first time at the time of settlement by the settlement device 40 (an example in which no special sales are referenced at all when registering products by the mobile terminal 60). However, an embodiment in which at least some types of special sales are referenced for the first time at the time of settlement by the settlement device 40 (an embodiment in which some types of special sales are referenced when registering products by the mobile terminal 60) may also be adopted. As an example, a special sales file (sale file A) related to bundles (sale code "T003") and time-limited special prices (sale code "T004") may be stored in the cloud server 20 for use at the time of registration, and a special sales file (sale file B) related to mix matches (sale code "T001") and set matches (sale code "T002") may be stored in the settlement device 40, etc., so that bundles, etc. are reflected when products are registered by the mobile terminal 60, and mix matches, etc. are reflected when settlement by the settlement device 40. In addition, discounts, etc. according to the total amount described above may be reflected at the time of settlement.

[0177] 21 and 22 are examples of displays on the settlement device 40. The settlement device 40 is capable of displaying, for example, a product list screen GM02 as shown in FIG. 21, in relation to (13) and (15) above.

[0178] The example shown in FIG. 21 is an example in which a special discount has been applied to the example shown in FIG. 14. The special discount is an example of the discount based on the total amount or the discount based on past purchase history (i.e., a special sale) described above. In this example, if the cumulative purchase amount of each transaction up to the previous month (e.g., the cumulative total of the confirmed totals of each transaction since a certain date) has not reached a predetermined amount (e.g., ¥10,000), but the cumulative purchase amount including the total amount of the current transaction reaches the predetermined amount, a special discount of ¥100 is applied. The predetermined amount may be set in any number of stages (e.g., ¥10,000, ¥20,000, ¥30,000, etc.) (the discount amount may differ for each stage). Furthermore, the special discount may be a discount for the entire transaction rather than a discount for a specific product (or a specific group of products). For example, the special discount may be applied to the first transaction (regardless of transaction amount) of the current month if the cumulative purchase amount for the previous month was equal to or greater than a predetermined amount (e.g., ¥50,000).

[0179] Since the special discount is not a discount on a specific product (or a specific group of products) but a discount on the entire transaction, the settlement device 40 displays the special discount separately from the display of the products (XX dumplings, XX stir-fry, XX socks) in the product list display area HR410. In the example shown in Figure 21, the settlement device 40 displays the special discount with a space of one line (for one product).

[0180] When determining whether the cumulative shopping amount, including the total amount of the current transaction, reaches a predetermined amount, the total amount to be added should be the final total, not the estimated total. Furthermore, when determining whether a transaction is the first transaction of the current month if the cumulative shopping amount for the previous month was equal to or greater than a predetermined amount, the conclusion of the transaction (determination of whether it is a transaction) should be based at least on the stage of proceeding to checkout (the stage after the checkout two-dimensional code 605 is read). Furthermore, the same applies to the total amount and the conclusion of the transaction when a special discount is granted simply based on the total amount of the current transaction. For these reasons, special discounts are not notified at the registration stage but are notified at the checkout stage (reflected in the final total, not the estimated total). Without notification at the registration stage, the store may be concerned that the special discount granted will not be recognized by the customer, which may lead to customer concerns (especially those who are aware that the discount will be offered) about whether it will be properly granted. Therefore, the checkout device 40 prominently displays the special discount. In the example shown in Fig. 21, the settlement device 40 displays the special discount prominently with a one-line spacing. Note that instead of or in addition to the display position (setting the one-line spacing), the special discount may be displayed prominently by using the display size, color, blinking, background, etc.

[0181] The settlement device 40 may display the product list screen GM02 shown in Figures 22(A) and 22(B) instead of the product list screen GM02 shown in Figure 21. Note that Figures 22(A) and 22(B) each show a portion of the product list screen GM02 (product list display area HR410). The product list screen GM02 shown in Figure 22(A) differs from the product list screen GM02 shown in Figure 21 in that it displays an icon ICN417 associated with a special discount. When the special discount area is operated in the product list display area HR410 of the product list screen GM02 shown in Figure 22(A) (for example, when the icon ICN417 corresponding to the special discount is operated), the settlement device 40 displays the details of the special discount (in this example, the amount (-¥100) is already displayed in the product list display area HR410, so the condition is "total shopping amount since XX / XX / XX reaches 10,000 yen") as shown in Figure 22(B).

[0182] In addition, in a mode in which the settlement device 40 does not display the icon ICN417 associated with the service discount as shown in Figure 21, when the service discount area is operated, the settlement device 40 may display the details of the service discount as shown in Figure 22 (B) (however, the icon ICN417 is not displayed).

[0183] (15) In the example shown in Fig. 15, the details of the sale (100 yen off every three pairs of XX socks (¥900 → ¥800)) are displayed in the product list display area HR410 based on an operation (such as an operation of icon ICN417), but the details of the sale may also be displayed on a small screen based on an operation. The same applies to the examples shown in Figs. 17 and 22(B).

[0184] (16) In the example shown in FIG. 14 (similarly in FIG. 16 and FIG. 22(A)), it was explained that the details of the sale are displayed by operating the icon ICN417, etc. However, it can also be said that the icon ICN417 notifies that the product is at a sale price and at the same time suggests that it can be operated. However, just as the icon ICN415 related to automatic registration shown in FIG. 12 simply indicates that a non-file product has been automatically registered (and does not suggest that it can be operated), there is a risk that the icon ICN417 may also be perceived as simply indicating that the product is at a sale price. Therefore, when a sale (including a special discount) is applied, the product list screen GM02 may display a message indicating that the details of the sale can be confirmed by operation (for example, touch the discount application icon to confirm details).

[0185] (17) In the above embodiment, an example was described in which the settlement device 40 notifies a store clerk (by calling a store clerk by illuminating the sign pole 417 and sending a call notification to a device operated by the store clerk) when the NON-FILE is not resolved, but the situation in which the settlement device 40 notifies a store clerk is not limited to this. For example, the settlement device 40 may notify a store clerk when the confirmed total amount is higher than the estimated total amount (when the difference between the confirmed total amount and the estimated total amount is positive). (a) For example, if the final total amount (excluding the prices of items for which a non-file error occurred at the time of registration and the non-file error was resolved) is higher than the estimated total amount, i.e., if the final total amount for items other than the non-file item is higher than the estimated total amount for items other than the non-file item, the checkout device 40 may notify the store clerk (e.g., by sending a notification to a device operated by the store clerk that the final total amount is higher than the estimated total amount). Normally, the difference would not be positive for reasons other than non-file errors. However, if the difference is positive for reasons other than non-file errors, it is possible that some problem has occurred (e.g., a problem such as improper updating of the product master or sale file, or an incorrect price or the like in the product master or sale file). Furthermore, it is difficult (in terms of cost, operation, and technology) to constantly monitor the consistency and validity of information such as prices between servers (e.g., cloud server 20, headquarters server 10). Therefore, if the difference becomes positive for reasons other than NON-FILE, the store clerk may be notified and prompted to take appropriate action (such as checking or performing necessary maintenance). (b) For example, when a NON-FILE is resolved, the checkout device 40 may notify a store clerk (by sending a NON-FILE resolution notice including the name of the relevant product to a device operated by the store clerk). This allows the store clerk to understand that a NON-FILE has occurred (and the relevant product) and that it has been resolved, and the store can grasp the circumstances surrounding the occurrence of a NON-FILE. This allows the store clerk to consider whether improvements are necessary, for example, regarding the frequency and timing of updates to the registration product master in the cloud server 20 (the frequency and timing at which the cloud server 20 receives the checkout product master and stores it as the registration product master).

[0186] (18) The product master for registration shown in Figure 4(A) is a product master for registration in which the product code, product name, and price are stored as a set in all records (rows), but a product master for registration that includes records in which the product code is stored but the product name and price are not may also be used. In other words, the product master for registration shown in Figure 4(A) is such that if a product code is stored, product information corresponding to that product code can always be obtained, but a product master for registration in which product information corresponding to that product code may not be obtained even if a product code is stored may also be used. The same applies to the provisional product file in Figure 4(B) and the product master for checkout in Figure 3(A).

[0187] 4(A) and the provisional product file in FIG. 4(B), the settlement device 40 may determine whether or not the file is a non-file based on whether or not the product code read by the mobile terminal 60 is stored, or may determine whether or not the file is a non-file based on whether or not the product information corresponding to the product code read by the mobile terminal 60 is stored. On the other hand, when the settlement device 40 uses a registration product master or provisional product file that includes records in which the product code is stored but the product name and price are not stored, the settlement device 40 determines whether or not the file is a non-file based on whether or not the product code read by the mobile terminal 60 is stored.

[0188] (19) In the above embodiment, it was explained that the registration product master is older than the checkout product master because information reflected in the registration product master may not be reflected in the registration product master. However, the registration product master does not have to be older than the checkout product master. Specifically, the registration product master and the checkout product master may be the same. Even if the registration product master and the checkout product master are the same, depending on the timing (the timing of reading the product code, updating the product master, and starting checkout), a NON-FILE may occur when a product is registered and be resolved at checkout, just as when the registration product master is older than the checkout product master.

[0189] For example, in the following timings (time 1 to time 3; time 2 is later than time 1, and time 3 is later than time 2), even if the product master for registration and the product master for checkout are the same, NON-FILE occurs when the product is registered and is resolved at checkout. At time 2, both product masters (product master for registration, product master for checkout) are updated, and new product information for product A is added to both product masters. (Time 1) Based on a reading operation by a certain customer K, the mobile terminal 60 reads the product code attached to the product A. The product master for registration is referenced, and the product A becomes a non-file product. (Time 2) Product information for Product A is added to both product masters. At Time 2, Customer K is selecting a product in the store. (Time 3) Based on the reading operation of customer K, the settlement device 40 reads the settlement two-dimensional code 605 for the transaction including non-file product A. The settlement product master is referenced, and the non-file status for product A is resolved.

[0190] (20) In the above embodiment, when the automatic registration process is executed (when NON-FILE is resolved), the settlement device 40 sends NON-FILE resolution information and the provisional product file is updated (FIG. 19). However, the registration product master may be updated without providing a provisional product file. In other words, if a product becomes NON-FILE when registered by the mobile terminal 60 and the NON-FILE status of the product is resolved during settlement by the settlement device 40, the resolution of the status may be reflected in the master or file referenced during product registration by the mobile terminal 60 so that the product does not become NON-FILE when subsequently registered by the mobile terminal 60.

[0191] (21) In the above embodiment, an example was described in which a product was identified from a barcode attached to the product (i.e., by image recognition of a captured image of the barcode portion), but the method of identifying a product is not limited to this. For example, a product may be identified from its appearance (i.e., by image recognition of a captured image of the product's appearance). Also, a product may be identified from an electronic tag attached to the product (or a display shelf) by, for example, equipping the mobile terminal 60 with an electronic tag recognition unit that recognizes information on the electronic tag.

[0192] (Identifying a product from its appearance) There are several possible configurations for identifying a product from its appearance, depending on, for example, where image recognition of the captured image of the product's appearance is performed and what is obtained as a result of the image recognition. (Configuration a) Configuration a is a configuration in which the mobile terminal 60 performs image recognition and acquires a product code (JAN code, etc.) as a result of the image recognition. In the case of configuration a, for example, information indicating the correspondence between the image recognition result (or information to be compared with the image recognition result; the same applies below) and the product code is stored in a device that the mobile terminal 60 can refer to (for example, an individual mobile terminal 60). The mobile terminal 60 captures an image of the exterior of the product, performs image recognition on the captured image, and acquires the product code based on the image recognition result (i.e., identifies the product). (Configuration b) In configuration b, the mobile terminal 60 performs image recognition and acquires, as a result of the image recognition, identification information of a different system from the product code (identification information from which one product code can be acquired from one piece of identification information). In the case of configuration b, for example, information indicating the correspondence between the image recognition results and the identification information is stored in a device that the mobile terminal 60 can refer to (for example, each mobile terminal 60), and information indicating the correspondence between the identification information and the product code is stored in the cloud server 20. The mobile terminal 60 captures an image of the exterior of the product, performs image recognition on the captured image, acquires the identification information based on the image recognition result, and transmits the acquired identification information to the cloud server 20. The cloud server 20 acquires the product code from the identification information acquired from the mobile terminal 60 (i.e., identifies the product). (Configuration c) Configuration c is a configuration in which the cloud server 20 performs image recognition and acquires a product code as a result of the image recognition. In the case of configuration c, for example, information indicating the correspondence between the image recognition result and the product code is stored in the cloud server 20. The mobile terminal 60 captures an image of the exterior of the product and transmits the captured image to the cloud server 20. The cloud server 20 performs image recognition on the captured image acquired from the mobile terminal 60 and acquires a product code based on the image recognition result (i.e., identifies the product).

[0193] For the purpose of payment, information indicating the correspondence described above may also be stored in devices that the payment terminal 40 can refer to (for example, each payment terminal 40, the store controller 30, the headquarters server 10, etc.). The same applies to the aspect of identifying a product from an electronic tag.

[0194] (Identifying products using electronic tags) There are several possible configurations for identifying a product from an electronic tag, depending on what is acquired from the electronic tag (what information the electronic tag stores). (Configuration a) Configuration a is a configuration in which a product code (JAN code, etc.) is acquired from an electronic tag. In the case of configuration a, the product code is stored in the electronic tag. The mobile terminal 60 acquires the product code from the electronic tag (i.e., identifies the product). (Configuration b) Configuration b is a configuration in which identification information of a different system from the product code (identification information from which one product code can be obtained from one piece of identification information) is obtained from the electronic tag. In configuration b, the identification information is stored in the electronic tag. Configuration b is classified into a configuration (configuration b1) in which the mobile terminal 60 stores information indicating the correspondence between the identification information and the product code, and a configuration (configuration b2) in which the cloud server 20 stores information indicating the correspondence. In the former (configuration b1), the mobile terminal 60 obtains the identification information from the electronic tag and obtains the product code from the obtained identification information (i.e., identifies the product). In the latter (configuration b2), the mobile terminal 60 obtains the identification information from the electronic tag and transmits the obtained identification information to the cloud server 20. The cloud server 20 obtains the product code from the identification information obtained from the mobile terminal 60 (i.e., identifies the product).

[0195] (22) In the above embodiment, an example was described in which the product master (product master for registration) stored in the cloud server 20 is referenced when registering a product, and the product master (product master for checkout) stored in the checkout device 40, store controller 30, or headquarters server 10 is referenced as necessary when checkout. However, the mobile terminal 60 may store the product master for registration (the mobile terminal 60 may store the product master for registration instead of or in addition to the cloud server 20), and the mobile terminal 60 may reference the product master for registration in its own device when registering a product, and a product for which product information cannot be obtained from the product master for registration in its own device may be treated as a NON-FILE product.

[0196] As an example, in the aspect (21) of identifying a product from its appearance (e.g., configuration a), the mobile terminal 60 stores a product master for registration instead of or in addition to the cloud server 20, and after image recognition, the mobile terminal 60 refers to its own image recognition database (information indicating the correspondence, the product master for registration). If product information cannot be obtained from the image recognition database within the mobile terminal 60, the mobile terminal 60 may treat the product as a non-file product. Note that if product information cannot be obtained from the image recognition database within the mobile terminal 60, the mobile terminal 60 may refer to the image recognition database stored in the cloud server 20. Whether or not to refer to the image recognition database stored in the cloud server 20 when product information cannot be obtained from the image recognition database within the mobile terminal 60 may be determined taking into consideration response time (time is already required for image recognition, etc.), the possibility of obtaining product information from the image recognition database stored in the cloud server 20, and the like.

[0197] (23) In the above embodiment, an example was described in which a customer registers a product using a mobile terminal 60. However, any mobile (portable) device capable of registering products at the product display location may be used instead of a mobile terminal 60. For example, products may be registered using a tablet terminal provided to customers by the store, or a shopping cart equipped with a display unit (or a display device detachable from the shopping cart). The shopping cart may be equipped with an electronic tag recognition unit that recognizes information from an electronic tag.

[0198] (24) Some or all of the functions (input / output, storage, and processing (including judgment)) of the settlement device 40 in the above embodiment may be implemented by a device other than the device described as the entity executing the function. For example, at least some of the processes described using the sequence diagrams of FIGS. 18 and 19 as processes of the settlement device 40 may be executed by the store controller 30 or the cloud server 20 instead of the settlement device 40. In relation to the above, the settlement device 40 may function as a so-called thin client specialized for input / output interfaces, etc. For example, the settlement device 40 may accept various inputs (customer operations, detection by a device such as a scanner) and transmit the input information (operation information, image information, etc.) to the cloud server 20. The cloud server 20 may then execute processing according to the information received from the settlement device 40 and transmit the processing results (updated screen information, etc.) to the settlement device 40. The settlement device 40 may then execute an operation (display on a display, etc.) according to the information received from the cloud server 20. In other words, the cloud server 20 may execute a program for controlling the operation of the settlement device 40.

[0199] <Summary of the embodiment> [Technical field] The present invention relates to a merchandise sales data processing system and a payment device. [Background technology] A system has been proposed in which customers themselves register products using mobile terminals (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2018-055700 A [Summary of the Invention] [Problem to be solved by the invention] However, various problems may arise during checkout after product registration (for example, burden on store clerks, anxiety of customers, etc.) The present invention was made in consideration of these circumstances, and aims to provide technology for resolving various problems during checkout in a system in which customers themselves register products using a mobile terminal. [Means for solving the problem] (A1) A merchandise sales data processing system for registering merchandise using a portable registration device (e.g., a mobile terminal 60) operated by a customer himself / herself, the system comprising: registration means (e.g., registration by the mobile terminal 60) for executing a registration process for registering a merchandise by acquiring merchandise information corresponding to an identified merchandise code (e.g., a merchandise code identified from a barcode, a merchandise code identified from the appearance of a merchandise, a merchandise code identified from an electronic tag, etc.) from a first merchandise information database (e.g., a merchandise master for registration in FIG. 4(A)) and registering the merchandise; settlement means (e.g., settlement process by the settlement device 40) for executing a settlement process by referring to the merchandise information after the registration process by the registration means has been completed (e.g., after the Proceed to Checkout button BT604 has been operated); and notification means for notifying the customer; When a product code is identified but product information corresponding to the product code cannot be obtained from the first product information database (for example, when there is a non-file product), the means can further execute an automatic registration process (for example, the process of step S16 in Figure 18) to obtain product information corresponding to the product code from a second product information database (for example, the product master for checkout in Figure 3(A)) and register the product without any operation (for example, without the need for a store clerk to enter product information), and the notification means is a product sales data processing system characterized in that when the automatic registration process is executed, the notification means automatically notifies that a product has been registered (for example, by displaying the small screen SG10 in Figure 11 or displaying icon ICN415 in Figure 12). According to the configuration (A1), the information required for the settlement is automatically replenished (or supplemented), which reduces the burden on store clerks and shortens the settlement time.

[0200] (A2) The product sales data processing system described in (A1) is characterized in that when the automatic registration process is executed, the notification means begins to notify that there are products that have been automatically registered before a list screen (e.g., product list screen GM02) for checking the products to be settled is displayed, or while the list screen is displayed. According to the configuration (A2), it is possible to preferably notify the user that there is a registered product automatically.

[0201] (A3) A product sales data processing system as described in (A1) or (A2), characterized in that when the automatic registration process is executed, the notification means notifies which products have been automatically registered on a list screen for checking the products to be settled (for example, by icon ICN415 as shown in Figure 12). According to the configuration of (A3), it is possible to preferably notify which products are automatically registered products.

[0202] (A4) A product sales data processing system described in any of (A1) to (A3), characterized in that when the automatic registration process is executed, the notification means notifies the payment amount, which is at least the total amount of the products registered in the registration process by the registration means plus the amount of the products registered in the automatic registration process by the settlement means (for example, by displaying a "confirmed total (payment amount)" as shown in Figure 12). According to the configuration of (A4), even if the information required for settlement is automatically filled in, the details of the accounting (final payment amount) are clear, so that unnecessary anxiety and misunderstandings are not caused to the customer.

[0203] (A5) A product sales data processing system as described in any of (A1) to (A4) is provided with a store clerk call means capable of executing a store clerk call process to call a store clerk if, after the registration process by the registration means has been completed, there is a product whose product code has been identified but product information corresponding to that product code cannot be obtained from the first product information database, and the store clerk call means does not execute the store clerk call process if the automatic registration process has been executed for all of the products when the automatic registration process has not been executed for at least some of the products. The configuration of (A5) makes it possible to conveniently call a store clerk. The latter part of (A5) (i.e., "If there are any products whose product codes have been identified but whose product information corresponding to the product codes cannot be obtained from the first product information database at the time when the registration process by the registration means has ended, the store clerk call means does not execute the store clerk call process if the automatic registration process has been performed for all of the products, and executes the store clerk call process if the automatic registration process has not been performed for at least some of the products") collectively describes the cases where there is one product that could not be obtained and the cases where there are multiple products that could not be obtained. That is, the latter part indicates that (a) when there are multiple products that could not be obtained, the store clerk call process is not executed if the automatic registration process has been performed for all of the multiple products, and the store clerk call process is executed if the automatic registration process has not been performed for at least some of the multiple products, and (b) when there is one product that could not be obtained, the store clerk call process is not executed if the automatic registration process has been performed for the product, and the store clerk call process is executed if the automatic registration process has not been performed for the product.

[0204] (A6) A product sales data processing system described in any of (A1) to (A5), characterized in that when the automatic registration process is executed, the notification means separately notifies the estimated total amount, which is the total amount of the products registered in the registration process by the registration means, and the payment amount, which is the estimated total amount plus the amount of the products registered in the automatic registration process by the settlement means (for example, by displaying an ``estimated total (amount displayed on smartphone)'' and a ``final total (amount paid)'' as shown in Figure 12). According to the configuration of (A6), even if the information required for settlement is automatically filled in, the details of the transaction (total amount at the time of registration, final payment amount) are clear, so that unnecessary anxiety and misunderstandings are not caused to the customer.

[0205] (A7) A product sales data processing system described in any of (A1) to (A6), characterized in that when the automatic registration process is executed, the settlement means transmits product information of the product registered in the automatic registration process (for example, a product whose NON-FILE status has been resolved) to be stored in the first product information database. According to the configuration of (A7), the product will not be marked as non-file from the next time onwards, which reduces the burden on store clerks and shortens checkout time. Also, the product will not be marked as an unregistered product when registered on the mobile terminal 60 from the next time onwards, which is easy for customers to understand.

[0206] (A8) A product sales data processing system for registering products using a portable registration device (e.g., a mobile terminal 60) operated by a customer, the system comprising: a first registration means (e.g., registration processing by the mobile terminal 60) for executing a registration process to acquire product information corresponding to an identified product code (e.g., a product code identified from a barcode, a product code identified from the appearance of a product, a product code identified from an electronic tag, etc.) from a first product information database (e.g., a product master for registration in FIG. 4(A)) and register the product; a settlement means (e.g., settlement processing by the settlement device 40) for executing a settlement process by referring to the product information after the registration process by the first registration means is completed (e.g., after the “Proceed to checkout” button BT604 is operated); and a second product information database (e.g., settlement processing by the settlement device 40) for acquiring product information corresponding to the identified product code after the registration process by the first registration means is completed and before the settlement process by the settlement means begins. This product sales data processing system comprises a second registration means (e.g., registration processing by a checkout device 40) that executes a registration process to obtain product information from a product information database (e.g., the product master for checkout in Figure 3(A)) and register the product, and a notification means that notifies the customer, wherein the second registration means is capable of executing an automatic registration process (e.g., processing of step S16 in Figure 18) to obtain product information corresponding to the product code from the second product information database and automatically register the product when a product code has been identified but the product could not be registered by the first registration means (e.g., a non-file product) without any operation (e.g., without the need for a store clerk to input product information), and the notification means, when the automatic registration process has been executed, notifies the customer that a product has been automatically registered (e.g., displays the small screen SG10 in Figure 11 or displays the icon ICN415 in Figure 12). According to the configuration of (A8), the information required for the settlement is automatically replenished (or supplemented), which reduces the burden on the store clerk and shortens the settlement time.

[0207] (A9) A settlement device that settles for goods registered by a portable registration device that executes a registration process to obtain product information corresponding to an identified product code from a first product information database and register the product, comprising: a settlement means that executes the settlement process by referring to the product information after the registration process by the portable registration device is completed; and a notification means that notifies the customer; wherein, if a product code is identified but product information corresponding to the product code cannot be obtained from the first product information database, the settlement means is further capable of executing an automatic registration process to obtain product information corresponding to the product code from a second product information database and register the product without any operation; and wherein, when the automatic registration process is executed, the notification means automatically notifies that a product has been registered. According to the configuration of (A9), the information required for the settlement is automatically replenished (or supplemented), which reduces the burden on the store clerk and shortens the settlement time.

[0208] (A10) A settlement device that settles payments for goods registered by a portable registration device that obtains product information corresponding to an identified product code from a first product information database and registers the product, comprising: a settlement means that executes a settlement process by referring to the product information after the registration of the product by the portable registration device is completed; a registration means that obtains product information corresponding to the identified product code from a second product information database and registers the product after the registration of the product by the portable registration device is completed and before the settlement process by the settlement means begins; and a notification means that notifies a customer; wherein, when there is a product whose product code has been identified but which could not be registered in the portable registration device, the registration means is capable of executing an automatic registration process that obtains product information corresponding to the product code from the second product information database and automatically registers the product without any operation; and the notification means, when the automatic registration process is executed, automatically notifies that there is a product that has been registered. According to the configuration of (A10), the information required for the settlement is automatically replenished (or supplemented), which reduces the burden on the store clerk and shortens the settlement time.

[0209] (B1) A merchandise sales data processing system including a portable registration device (e.g., a mobile terminal 60) that registers merchandise through customer operation, and a settlement device (e.g., a settlement device 40) that settles the payments for the registered merchandise, wherein the portable registration device has a registration means that executes a registration process to register merchandise information including price information for identified merchandise (e.g., merchandise identified from a barcode, a merchandise identified from its appearance, a merchandise identified from an electronic tag, etc.), and the settlement device has a settlement means that settles the payment based on the merchandise information and a display means that displays information related to the settlement, and the display means displays (in a total display area HR412 as shown in Figures 14, 16, and 20) an estimated total amount based on the merchandise information at the time the registration process by the registration means is completed, and a final total amount that is the amount to be settled by the settlement means. According to the configuration of (B1), even if the product information is changed, the details of the transaction (total amount at the time of registration, final payment amount) are clear, so that the customer does not get unnecessarily anxious or misunderstood.

[0210] (B2) In a product sales data processing system including a portable registration device (e.g., a mobile terminal 60) that registers products through customer operation and a checkout device (e.g., a checkout device 40) that settles the payment for the registered products, the portable registration device includes a registration means that executes a registration process to register product information including price information of a specified product, and the checkout device includes an acquisition means that acquires the product information after the registration process by the registration means is completed (e.g., after the user operates the Proceed to Checkout button BT604), and an acquisition means that acquires the product information based on the product information after the registration process by the registration means is completed. a change means (for example, the processing of step S17 in FIG. 18) that can change the product information (for example, change it to a sale price) before the settlement by the settlement means; and a display means that displays information related to the settlement, wherein when the product information is changed by the change means, the display means displays (in total display area HR412 as shown in FIG. 14, FIG. 16, or FIG. 20) an estimated total amount based on the product information before the change and a final total amount based on the product information after the change. According to the configuration of (B2), even if the product information is changed, the details of the transaction (total amount at the time of registration, final payment amount) are clear, so that the customer does not get unnecessarily anxious or misunderstood.

[0211] (B3) The product sales data processing system described in (B1) or (B2) is characterized in that the display means displays the difference between the estimated total amount and the final total amount (for example, the discount amount due to a special sale as shown in Figures 14 and 16). According to the structure of (B3), the difference can be directly recognized.

[0212] (B4) A product sales data processing system as described in any one of (B1) to (B3), characterized in that the display means displays the reason for the difference between the estimated total amount and the final total amount (for example, as shown in Figure 15, Figure 17, or Figure 20(C)). The structure of (B4) prevents unnecessary anxiety and misunderstandings from being caused to customers.

[0213] (B5) A product sales data processing system described in any of (B1) to (B4), characterized in that the display means displays products that have resulted in a difference between the estimated total amount and the final total amount in a display manner different from that of other products (for example, notifying them by icon ICN417 as shown in Figures 14 and 16). According to the configuration of (B5), it is possible to preferably notify which product is the product that caused the price difference (the product to which the special sale was applied).

[0214] (B6) A settlement device that settles the accounts of registered products in a portable registration device that registers product information including price information of identified products, comprising a settlement means that settles the accounts based on the product information and a display means that displays information related to the settlement, wherein the display means displays an estimated total amount based on the product information at the time of completion of registration by the portable registration device and a final total amount that is the amount to be settled by the settlement means. According to the configuration of (B6), even if the product information is changed, the details of the transaction (total amount at the time of registration, final payment amount) are clear, so that the customer does not get unnecessarily anxious or misunderstood.

[0215] (B7) A program that causes a computer to function as a settlement device that settles the accounts of registered products in a portable registration device that registers product information including price information of identified products, the program causing the computer to function as a settlement means that settles the accounts based on the product information and a display means that displays information related to the settlement, the display means displaying an estimated total amount based on the product information at the time of completion of registration by the portable registration device and a final total amount that is the amount to be settled by the settlement means. According to the configuration of (B7), even if the product information is changed, the details of the transaction (total amount at the time of registration, final payment amount) are clear, so that the customer does not get unnecessarily anxious or misunderstood.

[0216] Note that programs for implementing the functions of each of the above-described devices (e.g., the headquarters server 10, the store controller 30, the checkout terminal 40, the transaction status management device 50, and the mobile terminal 60) may be recorded on a computer-readable recording medium, and the programs may be loaded into a computer system and executed to perform the processing of each device. Here, "loading a program recorded on a recording medium into a computer system and executing it" includes installing the program on a computer system. The term "computer system" here includes hardware such as an operating system and peripheral devices. The term "computer system" may also include multiple computer devices connected via a network, including the Internet, a WAN, a LAN, a dedicated line, and other communication lines. The term "computer-readable recording medium" refers to portable media such as floppy disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. Thus, a recording medium storing a program may be a non-transitory recording medium such as a CD-ROM. The term "recording medium" also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code executable on a terminal device. In other words, the format in which the program is stored on the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a form that is executable on the terminal device. The program may be divided into multiple parts, each of which may be 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 term "computer-readable recording medium" also includes a storage medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be one that realizes part of the functions described above.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]

[0217] 1...Sales system 10...Head office server 20...Cloud server 30...Store controller 40...Payment device 50...Transaction status management device 60...Mobile terminal 401...CPU 402...ROM 403...RAM 404...Hard disk 405...Display unit 406...Scanner unit 408...Card payment unit 409...Change dispenser 413...Printing unit 414...Audio output unit 415...Communication unit 416...Imaging unit 417...Sign pole

Claims

1. A product sales data processing system for registering products using a portable registration device operated by a customer, comprising: a registration means for executing a registration process for acquiring product information corresponding to the identified product code from a first product information database and registering the product; a payment means for executing a payment process by referring to the product information after the registration process by the registration means is completed; A notification means for notifying a customer; Equipped with The settlement means is If a product code is identified but product information corresponding to the product code cannot be obtained from the first product information database, an automatic registration process can be further executed to obtain product information corresponding to the product code from a second product information database and register the product without requiring any operation; The notification means includes: When the automatic registration process is executed, the user is notified that there is an automatically registered product. A product sales data processing system comprising:

2. The notification means includes: When the automatic registration process is executed, before a list screen for confirming products to be settled is displayed, or while the list screen is being displayed, a notification that there are products that have been automatically registered is started.

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

3. The notification means includes: When the automatic registration process is executed, a list screen for confirming the products to be checked out is displayed to inform the customer which products have been automatically registered.

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

4. The notification means includes: When the automatic registration process is executed, a payment amount obtained by adding the amount of the product registered in the automatic registration process by the settlement means to the total amount of the product registered in the registration process by the registration means is notified.

4. The product sales data processing system according to claim 1, wherein:

5. a store clerk calling means for executing a store clerk calling process for calling a store clerk when a product code is identified but product information corresponding to the product code cannot be obtained from the first product information database after the registration process by the registration means is completed; Equipped with The store clerk calling means includes: When the registration process by the registration means is completed, if there is a product whose product code has been specified but whose product information corresponding to the product code cannot be obtained from the first product information database, the store clerk call process is not executed if the automatic registration process has been executed for all of the product, and the store clerk call process is executed if the automatic registration process has not been executed for at least a part of the product.

5. The product sales data processing system according to claim 1,

6. The settlement means is When the automatic registration process is executed, product information of the product registered in the automatic registration process is transmitted to be stored in the first product information database.

6. The product sales data processing system according to claim 1,

7. A settlement device that settles for a commodity registered by a portable registration device that executes a registration process of acquiring commodity information corresponding to a specified commodity code from a first commodity information database and registering the commodity, a payment means for executing a payment process by referring to the product information after the registration process by the portable registration device is completed; A notification means for notifying a customer; Equipped with The settlement means is If a product code is identified but product information corresponding to the product code cannot be obtained from the first product information database, an automatic registration process can be further executed to obtain product information corresponding to the product code from a second product information database and register the product without requiring any operation; The notification means includes: When the automatic registration process is executed, the user is notified that there is an automatically registered product. A settlement device characterized by:

Citation Information

Patent Citations

  • Pos system provided with self-retrieving function

    JP1995065239A

  • Method of self-settlement of accounts by using portable device

    JP2018055700A