Program, portable terminal, system, server, and notification method

Abstract

To implement a system where customers register articles by themselves further effectively.SOLUTION: In a program for enabling a mobile terminal used for securing articles in a shopping cart at a sales counter to function as a computer, the computer functions as: operation acceptance means for accepting operations to register articles for purchase, change the quantity of the articles for purchase, or cancel the purchase of the articles; recognition means for recognizing the placement of the articles into a cart or the removal of the articles from the cart; and notification means to notify a user that the operation content accepted by the operation acceptance means does not match the recognition content recognized by the recognition means. The notification means does not notify the user of the mismatch between the operation content and the recognition content until a predetermined condition holds.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a program, a mobile terminal, a system, a server, and a notification method. [Background technology]

[0002] There is known a self-service terminal equipped with a scale that issues an error when an item is placed in a bag without being scanned (see, for example, Patent Document 1). Also, in a system in which customers register items themselves in a product display area using a shopping cart, a technology is known in which a scale is provided in the shopping cart to detect fraudulent placement of items in the shopping cart. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-238264 Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is room for improvement in the system where customers register their products themselves in the product display area.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technology that can more suitably implement a system in which customers themselves register products in the product display area. [Means for solving the problem]

[0006] One aspect of the program for solving the above-mentioned problems is a program for causing a mobile terminal operated when securing an item in a cart at a sales floor to function as a computer, and for causing the computer to function as an operation reception means for receiving operations to register an item to be purchased, an operation to change the quantity of an item to be purchased, or an operation to cancel the purchase of an item, a recognition means for recognizing when an item is added to or removed from the cart, and a notification means for notifying when there is a mismatch between the operation content received by the operation reception means and the recognition content recognized by the recognition means, wherein the notification means does not notify when there is a mismatch between the operation content and the recognition content until a predetermined condition is met. [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 an explanatory diagram illustrating a cart. [Figure 3] 10 is a display example of a mobile terminal. [Figure 4] 10 is a display example of a mobile terminal. [Figure 5] 10 is a display example of a mobile terminal. [Figure 6] 10 is a display example of a mobile terminal. [Figure 7] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 8] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 9] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 10] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 11] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 12] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 13] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 14] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 15] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 16] FIG. 10 is an explanatory diagram illustrating the relationship between various situations and fraud, etc. [Figure 17] 10 is a flowchart illustrating an example of an operation of the mobile terminal. DETAILED DESCRIPTION OF THE INVENTION

[0008] 1 is a conceptual diagram of a network for explaining a sales system 1 according to this embodiment. The sales system 1 shown in FIG. 1 includes a headquarters server 10, a cloud server 20, a store controller 30, a transaction status management device 40, a settlement device 50, and a mobile terminal 60.

[0009] The sales system 1 can be introduced into various business types (supermarkets, convenience stores, drug stores, home centers, electronics retailers, etc.). The store controller 30, transaction status management device 40, and payment device 50 are installed within the store (product display area, checkout area, backroom, office, etc.). These can communicate via a LAN 19 (which may be wired or wireless). The headquarters server 10 and cloud server 20 are installed outside the store (for example, at a headquarters or data center, etc.). The devices installed within the store (store controller 30, transaction status management device 40, payment device 50) can communicate (directly or via the store controller 30) with the devices installed outside the store (headquarters server 10, cloud server 20).

[0010] Also, within the store, there is a shopping cart (hereinafter simply referred to as a "cart") 70 prepared by the store. Also within the store, there is a mobile terminal 60 that is owned by a customer who visits the store. The mobile terminal 60 can be attached (set) to the cart 70. The mobile terminal 60 and the cart 70 can communicate with each other via wireless communication (for example, Bluetooth (registered trademark; the same applies below)). In FIG. 1, the mobile terminal 60 shown inside the cart 70 represents the mobile terminal 60 attached to the cart 70. The mobile terminal 60 and the cloud server 20 can communicate with each other (directly or via the store controller 30).

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

[0012] Note that the number of each device (terminal) in FIG. 1 is an example. For example, while "..." is illustrated to the right of the payment device 50 in FIG. 1, the number of payment devices 50 installed in a store may be one or more. Also, for example, while two mobile terminals 60 are illustrated in FIG. 1, the number of mobile terminals 60 present in the store is the number of customers who visit the store with their mobile terminals 60, and is not necessarily two. Also, for example, while two carts 70 are illustrated in FIG. 1, the number of carts 70 present in the store is the number prepared by the store based on the number of mobile terminals 60 expected to be present in the store at the same time, and may be, for example, 10 or more.

[0013] (Mobile terminal 60) The mobile terminal 60 is used by customers themselves when registering products in a store. Specifically, the mobile terminal 60 registers products based on the customer's operation (motion) while in a state where it can communicate with one cart 70. Note that, as long as the mobile terminal 60 is in a state where it can communicate with one cart 70, it can register products based on the customer's operation whether it is attached to the cart 70 or detached from the cart 70 (for example, while the customer is holding it and operating it).

[0014] Although not shown, the mobile terminal 60 includes, for example, a CPU, a storage unit, a display unit, an operation unit, an audio output unit (speaker), an audio input unit (microphone), an imaging unit (camera), a detection unit (sensor), and a communication unit. The mobile terminal 60 is, for example, a smartphone.

[0015] The CPU is a central processing unit that controls the entire mobile terminal 60 by reading and executing programs stored in the storage unit. The storage unit stores various information (for example, information referenced or generated by the CPU, information obtained from the outside, etc.). The storage unit is a general term for one or more various storage components (for example, memory or storage, such as RAM, ROM, hard disk, SSD (Solid State Drive), etc.).

[0016] For example, the mobile terminal 60 may acquire (receive) an application program (hereinafter, App A) for using Service A from an external source (which may be a predetermined server or cloud server 20) and store (install) it in a storage unit. The mobile terminal 60 may use App A to display various screens (e.g., see FIGS. 3 to 6) and execute various processes (e.g., see FIGS. 7 to 17) related to Service A. As described above, Service A is a self-service service in which the mobile terminal 60 is used for product registration and the settlement device 50 is used for payment, and App A is an application program that handles the mobile terminal 60 (product registration) portion of Service A.

[0017] The display unit is, for example, a liquid crystal display, and displays various information (including image information). The display unit is configured as a touch panel that can accept operations on the display screen. The operation unit accepts operations from an operator (customer). The operation unit is a collective term for one or more various operation members (various operators (hard buttons) provided on the housing. Note that, since the display unit is configured as a touch panel, it may be considered as part of the operation unit. The audio output unit outputs audio. The audio input unit inputs audio. The imaging unit acquires (generates) captured images (still images, moving images). The detection unit (measurement unit) detects or measures various events, etc. The detection unit is a collective term for, for example, one or more various detection members (GPS sensor, acceleration sensor, gyro sensor, etc.). Note that the operation unit, audio input unit, and imaging unit may also be considered as part of the detection unit. The communication unit transmits and receives various information. The communication unit is a collective term for one or more various communication members (various communication members such as 5G, wireless LAN, NFC (Near Field Communication), Bluetooth, etc.).

[0018] Needless to say, the mobile terminal 60 includes a timekeeping unit (timekeeping function). The timekeeping unit enables the mobile terminal 60 to manage the current time, the time elapsed from a certain point in time, and the time remaining until a certain point in time.

[0019] For example, the mobile terminal 60 can manage the time that has elapsed since a product was added to the basket or the time that has elapsed since a product was removed from the basket. The mobile terminal 60 can manage the time that has elapsed since a product was registered (scan registration (described later), button registration (described later)). The mobile terminal 60 can manage the time that has elapsed since a product was canceled using the product cancel button (described later). The mobile terminal 60 can manage the time that has elapsed since a quantity change operation (a quantity decrease operation using the minus button (described later), or a quantity increase operation using the plus button (described later)) was performed. The mobile terminal 60 can manage the time that has elapsed since a certain screen (including a small screen) was displayed (started to be displayed) or since a certain screen (including a small screen) was erased.

[0020] The mobile terminal 60 connects to one cart 70 via Bluetooth (Bluetooth connection). When connecting to one cart 70, the mobile terminal 60 needs device identification information (e.g., Bluetooth address) of the cart 70 as pairing information. The mobile terminal 60 can acquire the device identification information of each cart 70 from a beacon transmitted by each cart 70. In the following description, the device identification information of the cart 70 may be referred to as connection information with the cart 70 (or simply "connection information").

[0021] The mobile terminal 60 can obtain connection information for each cart 70 from the beacon transmitted by each cart 70, but can also obtain connection information for each cart 70 from a two-dimensional code 78 (described below) affixed to each cart 70.

[0022] The mobile terminal 60 acquires connection information for one cart 70 (the cart 70 that the customer intends to use) based on the customer's operation, connects to the cart 70 using the acquired connection information, and becomes capable of communication (Bluetooth communication) with the cart 70.

[0023] The mobile terminal 60 can display an image captured by the imaging unit as a so-called through image (live view image) on the display unit. When the mobile terminal 60 is attached to the holder unit 74 (described later) and an image is captured by the imaging unit, the mobile terminal 60 obtains an image captured in a direction looking down on the shopping basket from the position of the holder unit 74 and displays the image on the display unit as a through image. do.

[0024] The mobile terminal 60 may store the captured image in the storage unit instead of or in addition to displaying the captured image as a through image on the display unit. That is, the mobile terminal 60 may store the captured image in the storage unit without displaying it as a through image on the display unit, or may store the captured image as a through image on the display unit without storing it in the storage unit, or may store the captured image in the storage unit while displaying it as a through image on the display unit. The mobile terminal 60 may also transmit the captured image to the cloud server 20.

[0025] In other words, the mobile terminal 60 can capture images even when it is displaying a scan registration screen (described later) or a button registration screen (described later), and can store the captured images in a memory unit or in the cloud server 20.

[0026] The mobile terminal 60 may also store in the memory unit, for example, weighing information received from the cart 70 (the last received weighing value (the latest (previous) weighing value), the weight of the container (details will be described later) (the container weight), etc.).

[0027] The mobile terminal 60 has various image processing functions. For example, the mobile terminal 60 has an object recognition function that recognizes objects from a captured image. The mobile terminal 60 also reads product barcodes (code symbols attached to the products or displayed near the products) from the captured image. That is, the mobile terminal 60 has a barcode reading function that recognizes barcodes in the captured image using the object recognition function and reads the recognized barcodes to obtain product codes (e.g., JAN codes or in-store codes). The mobile terminal 60 also reads two-dimensional codes 78 (described below) attached to each cart 70. That is, the mobile terminal 60 has a two-dimensional code reading function that recognizes two-dimensional codes 78 in the captured image using the object recognition function and reads the recognized two-dimensional codes 78 to obtain connection information. The mobile terminal 60 may also have a scanning action detection function that detects a customer's scanning action (holding over) of a product from the captured image (for example, by detecting whether a human hand or barcode has newly appeared in the captured image).

[0028] The mobile terminal 60 can monitor for fraud or mistakes during shopping by image recognition of captured images. For example, the mobile terminal 60 can monitor whether an unregistered product (a product not registered by the customer) is added to the cart 70, whether a registered product (a product registered by the customer) is not added to the cart 70, whether an uncancelled product (a product not canceled by the customer) is removed from the cart 70, or whether a canceled product (a product canceled by the customer) is not removed from the cart 70.

[0029] If fraud or the like (fraud, mistake) occurs, the fraud or the like is reported. For example, the mobile terminal 60 may report fraud or the like on a registration screen. Furthermore, if fraud or the like occurs, information indicating that the transaction requires confirmation (for example, a confirmation required flag) may be set in the transaction information of the transaction in which fraud or the like occurred, and necessary measures may be taken (for example, in the settlement device 50) until the settlement of the transaction is completed.

[0030] It is also possible to store captured images (images captured from each direction) for each product as verification information, compare the scanned product verification image with the newly recognized object, and check by image recognition whether the registered product matches the added product or whether the canceled product matches the removed product (image check). In other words, it is possible to monitor whether a product different from the registered product has been added to the cart 70 or whether a product different from the canceled product has been removed from the cart 70.

[0031] (Scan registration, button registration) The mobile terminal 60 has two product registration methods (methods for acquiring product codes): scan registration and button registration. Scan registration is a product registration method based on scanning a barcode. Button registration is a product registration method based on operating (touching) a product button (a preset button for product registration that corresponds to each product displayed on the display).

[0032] (Cart 70) 2 is an explanatory diagram illustrating the cart 70. The cart 70 has a function of placing and transporting products (products registered by the mobile terminal 60) and other items, as well as a function of weighing the products and other items, a function of communicating with the mobile terminal 60, and the like.

[0033] As shown in FIG. 2, the cart 70 includes a placement section (placement base) 71, a board storage section (board box) 72, a cart charging section 73, a holder section 74, a mobile terminal charging section 75, and a battery 76 (not shown). The placement section 71 is a member on which a shopping basket or the like can be placed. The board storage section 72 stores one or more boards (details will be described later). The cart charging section 73 has a detachable contact terminal with a power supply cable (not shown), and the tip of the contact terminal is connected to the charging terminal of the battery 76. The battery 76 stores power to be supplied to the cart 70 (specifically, the boards in the board storage section 72). The battery 76 is a power supply section (power source) for the cart 70.

[0034] The holder section 74 is a member for setting the portable terminal 60. The holder section 74 has an opening (hole) at the position of the imaging section (lens) of the set portable terminal 60. The portable terminal charging section 75 stores power to be supplied to the portable terminal 60 set in the holder section 74. Note that the reference numeral 79 will be described later.

[0035] A two-dimensional code 78 is attached to the mobile terminal charging section 75. The two-dimensional code 78 is a two-dimensional code that is a representation of device identification information (connection information) of the cart 70 (the cart 70 to which the two-dimensional code 78 is attached).

[0036] 2, no shopping basket is placed on the placement section 71 and no mobile terminal 60 is attached to the holder section 74, but a customer who comes to the store with a mobile terminal 60 places the shopping basket on the placement section 71 and attaches the mobile terminal 60 to the holder section 74. If necessary, the customer may charge the mobile terminal 60 by connecting it to a cable (not shown) of the mobile terminal charging section 75.

[0037] The substrate accommodating unit 72 accommodates substrates (one substrate, separate substrates) that realize weighing and communication functions. In other words, the substrate accommodating unit 72 includes a weighing unit and a communication unit. In the following description, the communication unit included in the substrate accommodating unit 72 may be referred to as a cart communication unit.

[0038] The weighing unit weighs the weight of an item placed on the placement unit 71. For example, the weighing unit detects that an item has been placed on the placement unit 71 by an increase in weight. The cart communication unit, for example, transmits a beacon. The cart communication unit also transmits and receives various information to and from the mobile terminal 60. For example, the cart communication unit transmits a weighing result (described later) to the mobile terminal 60. The cart communication unit may also transmit a determination result (described later) to the mobile terminal 60.

[0039] Furthermore, the board housing section 72 may house a board that realizes a memory function (which may be the same board as the board that realizes the weighing function and communication function, or a different board). In other words, the board housing section 72 may further include a memory section. The memory section stores, for example, the weight of the container (container weight) and the measurement value before increase or decrease (before change) for calculating the weight increase or decrease (amount of change). The memory section may also store the amount of weight increase (weight of the item added to the shopping cart) and the amount of weight decrease (weight of the item removed from the shopping cart).

[0040] A container is an item placed on the placement section 71 in the initial state before shopping begins (more specifically, the state before one item is added). A container may include not only a shopping basket but also the customer's luggage (wallet, bag, etc.). For example, if an empty shopping basket is placed on placement section 71 in the initial state before shopping begins, the container is the shopping basket, and the container weight is the weight of the shopping basket. For example, if a shopping basket containing a wallet is placed on placement section 71 in the initial state before shopping begins, the container is the shopping basket and the wallet, and the container weight is the weight of the shopping basket plus the weight of the wallet. Note that since the weight of the shopping basket is known, the weight of the customer's luggage can be calculated.

[0041] (Tare) Furthermore, the cart 70 (cart communication unit) receives tare instruction information from the mobile terminal 60. When the cart 70 receives tare instruction information from the mobile terminal 60, it sets the weighed value at the time of reception as the tare weight. The cart 70 may notify the mobile terminal 60 of the weighed value (tare weight) at the time of reception of the tare instruction information, or may always notify the mobile terminal of 0 g regardless of the weighed value at the time of reception of the tare instruction information. For example, if the weighed value at the time of reception of the tare instruction information from the mobile terminal 60 is 3000 g, the cart 70 may notify the mobile terminal 60 of the weighed value, 3000 g, or may notify the mobile terminal 60 of 0 g, which is the weighed value minus the weighed value (i.e., 3000 g is treated as 0 g). In the former case, the mobile terminal 60 proceeds with processing using 3000 g as the reference weight at the start of shopping, and in the latter case, the mobile terminal 60 proceeds with processing using 0 g as the reference weight at the start of shopping.

[0042] The mobile terminal 60 transmits tare instruction information to the cart 70 before adding at least one product. For example, the mobile terminal 60 connects to the cart 70 using the two-dimensional code 78 and then transmits the tare instruction information to the cart 70. The mobile terminal 60 may transmit the tare instruction information to the cart 70 before registering the first product (for example, when the initial registration screen is displayed), or may transmit the tare instruction information to the cart 70 after registering the first product.

[0043] As described above, the mobile terminal 60 can monitor for fraudulent behavior during shopping by image recognition, but the mobile terminal 60 can also monitor for fraudulent behavior during shopping by linking (communicating) with the cart 70.

[0044] The cart 70 may also include a timing unit (timing function). That is, similar to the mobile terminal 60, the cart 70 may use the timing unit to manage the current time, the elapsed time from a certain point in time, and the remaining time until a certain point in time.

[0045] For example, the cart 70 may manage the time elapsed since a product was added to the basket or the time elapsed since a product was removed from the basket. The cart 70 may receive operation information on the mobile terminal 60 from the mobile terminal 60, and manage the time elapsed since an operation to register a product (scan registration, button registration) on the mobile terminal 60, the time elapsed since an operation to cancel a product, or the time elapsed since an operation to change a quantity. The cart 70 may receive control information on the screen of the mobile terminal 60 from the mobile terminal 60, and manage the time elapsed since a certain screen (including a small screen) on the mobile terminal 60 is displayed or erased.

[0046] (Decision on putting products into cart 70) The mobile terminal 60 determines whether a product or the like has been added to the cart 70 (monitors the addition of a product or the like to the cart 70). For example, the mobile terminal 60 determines whether a product or the like has been added to the cart 70 in the following manner. (1) The cart 70 always transmits the latest weight value currently detected to the mobile terminal 60. The cart 70 may transmit the latest (post-increase) weight value to the mobile terminal 60 each time it detects a weight increase. The cart 70 may transmit the amount of increase in the weight value (the cart 70 stores the weight value before the increase and calculates the amount of increase) to the mobile terminal 60 each time it detects a weight increase. The cart 70 may notify the mobile terminal 60 that a weight increase has occurred each time it detects a weight increase. In other words, the cart 70 transmits the above-mentioned information (the latest weight value, the increase in the weight value, and information that a weight increase has occurred) to the mobile terminal 60 as the weighing result of the weighing unit. (2) The mobile terminal 60 determines whether a product or the like has been added to the cart 70 based on the weighing result received from the cart 70. Specifically, the mobile terminal 60 determines that a product or the like has been added to the cart 70 when the weighing value received from the cart 70 has increased (or when the mobile terminal 60 receives an increase in the weighing value from the cart 70, or when the mobile terminal 60 receives a notification from the cart 70 that a weight increase has occurred).

[0047] In addition, the cart 70 may send the weight of all items including the tare weight to the mobile terminal 60 as the latest weighing value, or may send the weight value of all items excluding the tare weight (the tare weight is stored) to the mobile terminal 60.

[0048] The cart 70 may determine whether or not a product or the like has been inserted (or may monitor the insertion of a product or the like). Specifically, the cart 70 determines that a product or the like has been inserted when it detects an increase in weight. When the cart 70 determines that a product or the like has been inserted, it notifies the mobile terminal 60 of the determination result (information indicating that it has determined that a product or the like has been inserted).

[0049] (Decision on taking out products from cart 70) The mobile terminal 60 determines whether a product or the like has been removed from the cart 70 (monitors the removal of a product or the like from the cart 70). For example, the mobile terminal 60 determines whether a product or the like has been removed from the cart 70 in the following manner. (1) The cart 70 always transmits the latest weight value currently detected to the mobile terminal 60. The cart 70 may transmit the latest (post-reduction) weight value to the mobile terminal 60 each time it detects a weight loss. The cart 70 may transmit the amount of weight loss (the cart 70 stores the weight value before the loss and calculates the amount of loss) to the mobile terminal 60 each time it detects a weight loss. The cart 70 may notify the mobile terminal 60 that a weight loss has occurred each time it detects a weight loss. In other words, the cart 70 transmits the above-mentioned information (the latest weight value, the amount of loss in the weight value, and information that a weight loss has occurred) to the mobile terminal 60 as the weighing result of the weighing unit. (2) The mobile terminal 60 determines whether a product or the like has been removed from the cart 70 based on the weighing result received from the cart 70. Specifically, the mobile terminal 60 determines that a product or the like has been removed from the cart 70 when the weighing value received from the cart 70 has decreased (or when the mobile terminal 60 receives the amount of decrease in the weighing value from the cart 70, or when the mobile terminal 60 receives a notification from the cart 70 that a weight decrease has occurred).

[0050] In addition, the cart 70 may send the weight of all items including the tare weight to the mobile terminal 60 as the latest weighing value, or may send the weight value of all items excluding the tare weight (the tare weight is stored) to the mobile terminal 60.

[0051] The cart 70 may determine whether or not a product or the like has been removed (may monitor the removal of a product or the like). Specifically, the cart 70 determines that a product or the like has been removed when it detects a weight loss. When the cart 70 determines that a product or the like has been removed, it notifies the mobile terminal 60 of the determination result (information indicating that it has determined that a product or the like has been removed).

[0052] (Product not registered + product inserted (weight value increased)) The mobile terminal 60 determines whether an unregistered product has been added. For example, if the product is not registered (scan registered, button registered) and the product is added to the cart 70, the mobile terminal 60 determines that an unregistered product has been added to the cart 70. For example, if the mobile terminal 60 determines that a product has been added to the cart 70 based on the weighing result received from the cart 70 (the latest weighing value, the increase in the weighing value, and information indicating that a weight increase has occurred) but the product has not been registered, the mobile terminal 60 determines that an unregistered product has been added to the cart 70. Also, for example, if the mobile terminal 60 receives a determination result indicating that a product has been added from the cart 70 but the product has not been registered, the mobile terminal 60 determines that an unregistered product has been added to the cart 70.

[0053] When the mobile terminal 60 determines that an unregistered product has been added to the cart 70, it may notify the user of this (for example, by displaying a message on the screen or by voice). For example, the mobile terminal 60 may display "Weight NG", "Confirmation Required", or "Registration Forgotten" on the registration screen. Instead of or in addition to displaying "Weight NG", the mobile terminal 60 may display a message such as "Registration was not successful, please register again." Furthermore, when the mobile terminal 60 determines that an unregistered product has been added to the cart 70, it may set a confirmation required flag (which may be a confirmation required flag for confirming that registration was forgotten) in the transaction information of the transaction.

[0054] The cart 70 may determine whether an unregistered product has been added. In the case where the cart 70 makes the determination, the mobile terminal 60 notifies the cart 70 that a product has been registered each time the product is registered. For example, if the cart 70 detects an increase in weight and determines that a product has been added, but does not receive a notification from the mobile terminal 60 that the product has been registered, the cart 70 may determine whether an unregistered product has been added.

[0055] If the cart 70 determines that an unregistered product has been added, it notifies the mobile terminal 60 of the determination result (information indicating that an unregistered product has been added). If the mobile terminal 60 receives the above notification, it notifies the user that an unregistered product has been added to the cart 70 (for example, by displaying a notification on the screen or by voice). For example, the mobile terminal 60 may display "Weight NG" for the product on the registration screen, or may display "Confirmation Required," or "Registration Forgotten." Instead of or in addition to displaying "Weight NG," the mobile terminal 60 may display a message such as "Registration was not successful, please register again." Furthermore, if the mobile terminal 60 receives the above notification, it may set a confirmation required flag (which may be a confirmation required flag for confirming that registration was forgotten) in the transaction information for the transaction.

[0056] In addition, in relation to determining whether an unregistered product has been inserted or whether a registered product has been inserted (described later), weight information for each product may be stored as verification information, and a weight check may be performed to determine whether the registered product matches the inserted product.

[0057] The same applies to an increase in the quantity of a registered product. In other words, in the same way as determining whether an unregistered product has been added, it may be determined whether a product with an increased quantity has been added.

[0058] (Product registration + product not inserted (no increase in weight value)) The mobile terminal 60 determines whether a registered product has been added. For example, if a product has been registered (scan registration, button registration) and the product has not been added to the cart 70, the mobile terminal 60 determines that the registered product has not been added to the cart 70. For example, if a product has been registered but the mobile terminal 60 has not received a weighing result (the latest weighing value, the increase in the weighing value, and information indicating an increase in weight) from the cart 70 (i.e., if it has not determined that the product, etc. has been added to the cart 70), the mobile terminal 60 determines that the registered product has not been added to the cart 70. Furthermore, for example, if a product has been registered but the mobile terminal 60 has not received a determination result indicating that the product, etc. has been added from the cart 70, the mobile terminal 60 determines that the registered product has not been added to the cart 70.

[0059] If the mobile terminal 60 determines that a registered product has not been added to the cart 70, it may notify the user of this (for example, by displaying a notification on the screen or by voice). For example, the mobile terminal 60 may display "weight NG" for the product on the registration screen, or may display "confirmation required," or may display "forgot to add." Instead of or in addition to displaying "weight NG," the mobile terminal 60 may display a message such as "Please add the registered product to your shopping cart." Furthermore, if the mobile terminal 60 determines that a registered product has not been added to the cart 70, it may set a confirmation required flag (which may be a confirmation required flag for confirming that the product has not been added) in the transaction information for the transaction.

[0060] The cart 70 may determine whether a registered product has been added. In the case where the cart 70 makes the determination, the mobile terminal 60 notifies the cart 70 that a product has been registered each time a product is registered. For example, if the cart 70 receives a notification from the mobile terminal 60 that a product has been registered, but does not determine that a product has been added by detecting an increase in weight, the cart 70 may determine that a registered product has not been added.

[0061] If the cart 70 determines that a registered product has not been added, it notifies the mobile terminal 60 of the determination result (information indicating that it has determined that a registered product has not been added). When the mobile terminal 60 receives the above notification, it may notify the user that a registered product has not been added to the cart 70. For example, the mobile terminal 60 may display "weight NG," "confirmation required," or "forgot to add" for the product on the registration screen. Instead of or in addition to displaying "weight NG," the mobile terminal 60 may display a message such as "Please add the registered product to your shopping cart." Furthermore, when the mobile terminal 60 receives the above notification, it may set a confirmation required flag (which may be a confirmation required flag for confirming that an item has been left unadded) in the transaction information for the transaction.

[0062] The same applies to an increase in the quantity of a registered product. In other words, in the same way as determining whether a registered product has been added, it may be determined whether a product with an increased quantity has been added.

[0063] (Product cancelled + product not taken out (no decrease in weight)) The mobile terminal 60 determines whether a canceled product has been removed. For example, if a product has been canceled and the product has not been removed from the cart 70, the mobile terminal 60 determines that the canceled product has not been removed from the cart 70. For example, if a product has been canceled but the mobile terminal 60 has not received a weighing result (the latest weighing value, the amount of decrease in the weighing value, and information indicating that the weight has decreased) from the cart 70 (i.e., if it has not determined that the product, etc. has been removed from the cart 70), the mobile terminal 60 determines that the canceled product has not been removed from the cart 70. Furthermore, for example, if a product has been canceled but the mobile terminal 60 has not received a determination result indicating that the product, etc. has been removed from the cart 70, the mobile terminal 60 determines that the canceled product has not been removed from the cart 70.

[0064] If the mobile terminal 60 determines that the canceled product has not been removed from the cart 70, it may notify the user of this (for example, by displaying a message on the screen or by voice). For example, the mobile terminal 60 may display "Weight NG" for the product on the registration screen, or may display "Confirmation Required," or may display "Forgotten to Remove." Instead of or in addition to displaying "Weight NG," the mobile terminal 60 may display a message such as "Please return the canceled product to the shelf." Furthermore, if the mobile terminal 60 determines that the canceled product has not been removed from the cart 70, it may set a confirmation required flag (which may be a confirmation required flag for confirming that the product has been left behind) in the transaction information for the transaction.

[0065] The cart 70 may determine whether a canceled product has been removed. In the case where the cart 70 makes the determination, the mobile terminal 60 notifies the cart 70 that the product has been canceled each time the product is canceled. For example, if the cart 70 receives a notification from the mobile terminal 60 that a product has been canceled but does not detect a weight loss and determine that the product has been removed, the cart 70 may determine that the canceled product has not been removed.

[0066] If the cart 70 determines that the canceled product has not been removed, it notifies the mobile terminal 60 of the determination result (information indicating that it has determined that the canceled product has not been removed). When the mobile terminal 60 receives the above notification, it may notify that the canceled product has not been removed from the cart 70. For example, the mobile terminal 60 may display "weight NG," "confirmation required," or "forgot to remove" for the product on the registration screen. Instead of or in addition to displaying "weight NG," etc., the mobile terminal 60 may display a message such as "Please return the canceled product to the shelf." Furthermore, when the mobile terminal 60 receives the above notification, it may set a confirmation required flag (which may be a confirmation required flag for confirming that the product has been left behind) in the transaction information of the transaction.

[0067] In addition, in relation to determining whether a canceled product has been removed or whether an un-canceled product has been removed (described later), weight information for each product may be stored as verification information, and the weight may be checked to see if the canceled product matches the removed product.

[0068] The same applies to a decrease in the quantity of a registered product. That is, in the same way as determining whether a canceled product has been taken out, it may be determined whether a product with a decreased quantity has been taken out.

[0069] (Product not canceled + product removed (weighing value decreased)) The mobile terminal 60 determines whether an uncancelled product has been removed. For example, if no product has been canceled and a product has been removed from the cart 70, the mobile terminal 60 determines that an uncancelled product has been removed. For example, if the mobile terminal 60 determines that a product has been removed from the cart 70 based on the weighing results received from the cart 70 (the latest weighing value, the amount of decrease in the weighing value, and information indicating that a weight decrease has occurred), but no product has been canceled, the mobile terminal 60 determines that an uncancelled product has been removed from the cart 70. Also, for example, if the mobile terminal 60 receives a determination result indicating that a product has been removed from the cart 70, but no product has been canceled, the mobile terminal 60 determines that an uncancelled product has been removed from the cart 70.

[0070] When the mobile terminal 60 determines that an uncancelled product has been removed from the cart 70, it may notify the user of this (for example, by displaying a notification on the screen or by voice). For example, the mobile terminal 60 may display "Weight NG" for the product on the registration screen, or may display "Confirmation Required," or may display "Cancel Forgotten." Instead of or in addition to displaying "Weight NG," the mobile terminal 60 may display a message such as "Please cancel if you want to stop the purchase." Furthermore, when the mobile terminal 60 determines that an uncancelled product has been removed from the cart 70, it may set a confirmation required flag (which may be a confirmation required flag for confirming that cancellation has been forgotten) in the transaction information for the transaction.

[0071] The cart 70 may determine whether an uncancelled product has been removed. In the case where the cart 70 makes the determination, the mobile terminal 60 notifies the cart 70 that the product has been canceled each time the product is canceled. For example, if the cart 70 detects a weight loss and determines that a product has been removed, but does not receive a notification from the mobile terminal 60 that the product has been canceled, the cart 70 may determine that an uncancelled product has been removed.

[0072] If the cart 70 determines that an uncancelled item has been removed, it notifies the mobile terminal 60 of the determination result (information indicating that it has determined that an uncancelled item has been removed). When the mobile terminal 60 receives the notification, it may notify the user that an uncancelled item has been removed from the cart 70. For example, the mobile terminal 60 may display "weight NG," "confirmation required," or "cancellation forgotten" for the item on the registration screen. Instead of or in addition to displaying "weight NG," the mobile terminal 60 may display a message such as "Please cancel if you want to stop the purchase." Furthermore, when the mobile terminal 60 receives the notification, it may set a confirmation required flag (which may be a confirmation required flag for confirming that cancellation has been forgotten) in the transaction information for the transaction.

[0073] The same applies to a decrease in the quantity of a registered product. In other words, in the same way as determining whether an uncancelled product has been taken out, it may be determined whether an undecreased product has been taken out.

[0074] (Payment device 50) The settlement device 50 is used by a customer. Specifically, the settlement device 50 settles the purchase of products registered via the mobile terminal 60 based on the customer's operation. Although not shown in the figure, the settlement device 50 includes a CPU, a memory unit, a display unit, a scanner unit, a payment unit, a printer unit, an audio output unit, an imaging unit, a communication unit, and a sign pole. For example, the scanner unit scans various codes and reads each code. For example, the payment unit is a collective term for one or both of a cash payment unit (change dispenser) that settles with cash and a non-cash payment unit (card payment unit, code payment unit) that settles with non-cash (e.g., credit, electronic money, etc.). For example, the display unit displays a product list screen (not shown), etc. The settlement device 50 may further include a key operation unit consisting of one or more various operation members, a human presence sensor that detects (detects, recognizes) the presence of a person, etc.

[0075] (Headquarters Server 10) The headquarters server 10 is a server that manages the entire sales system 1. The headquarters server 10 stores, for example, various information (for example, a product master file (product master), a product button file, etc.). The product master is a file that stores product names, prices, etc. in association with product codes. The product button file stores, for example, in association with product button identification information that identifies the product button, the product code of the product designated (specified) by the product button, category identification information that identifies the category to which the product button belongs (i.e., category identification information that identifies the category to which the product designated by the product button belongs), an image (captured image, illustration, etc.) to be displayed on the product button, etc.

[0076] The headquarters server 10 also supplies various information (e.g., product master, product button file, etc.) to, for example, the cloud server 20 and the store controller 30. Although not shown in the figure, the headquarters server 10 includes at least a CPU, a memory unit, and a communication unit. The headquarters server 10 may be configured from multiple servers.

[0077] (Cloud Server 20) Cloud server 20 is a server that mainly supports service A. Cloud server 20 stores various information (e.g., product master, product button file, transaction information, etc.). Cloud server 20 also supplies various information to, for example, mobile terminal 60 and settlement device 50. Although not shown in the figure, cloud server 20 includes at least a CPU, a storage unit, and a communication unit. Cloud server 20 may be composed of multiple servers.

[0078] (Store Controller 30) The store controller 30 is a server that is mainly responsible for communicating information between devices installed inside the store (the transaction status management device 40, the settlement device 50) and devices installed outside the store (the headquarters server 10, the cloud server 20). Although not shown in the figure, the store controller 30 includes at least a CPU, a memory unit, and a communication unit.

[0079] (Transaction status management device 40) The transaction status management device 40 is, for example, a device (e.g., a personal computer) that manages (monitors, controls, etc.) the settlement device 50 and the mobile terminal 60. For example, the transaction status management device 40 monitors (displays) the processing status and operating status of the settlement device 50. The transaction status management device 40 may also monitor the processing status and operating status of the mobile terminal 60 (e.g., access the cloud server 20 and display or modify the product master, product button file, transaction information, etc.). The transaction status management device 40 may also monitor the status of the cart 70 (e.g., access the cloud server 20 and display the status of the cart 70's battery, etc. (battery 76, cart charging unit 73, mobile terminal charging unit 75) and various error information transmitted via the mobile terminal 60 and stored in the cloud server 20). The transaction status management device 40 may also access the headquarters server 10, etc., and perform maintenance (e.g., product settings) on the product master stored in the headquarters server 10, etc. Although not shown in the figures, the transaction status management device 40 includes at least a CPU, a memory unit, a display unit (which may be configured as a touch panel), an operation unit (keyboard, mouse, etc.), and a communication unit. The transaction status management device 40 can communicate with a printing device (not shown), and various information may be output from the printing device.

[0080] The sales system 1 may include devices other than those described above. For example, a registration and settlement device 51 (not shown) may be installed in a store to register products based on customer operations and settle payments based on customer operations. Although not shown, the registration and settlement device 51 includes a CPU, a memory unit, a display unit, a scanner unit, a settlement unit (one or both of a cash settlement unit and a non-cash settlement unit), a printer unit, an audio output unit, an imaging unit, a communication unit, and a sign pole. For example, the scanner unit scans and reads various codes (e.g., product codes, clerk codes attached to gift certificates, point cards, clerk name tags, etc.). For example, the display unit displays a registration screen (not shown) and a settlement screen (not shown). The registration and settlement device 51 may further include a key operation unit consisting of one or more various operating members, a human presence sensor, etc., to detect the presence of a person.

[0081] Furthermore, the sales system 1 may have a registration and settlement device 52 (not shown) installed in the store that has a clerk display unit, a scanner unit, etc. on one side (the clerk side) and a customer display unit and a settlement unit (either a cash settlement unit or a non-cash settlement unit, or both) on the other side (the customer side; the side opposite the clerk side), and that registers products based on clerk operation and settles payments based on customer operation. Also, a registration and settlement device 53 (not shown) may be installed in the store that has a clerk display unit, a clerk registration unit, etc. on one side and a customer display unit, a customer registration unit, and a settlement unit (either a cash settlement unit or a non-cash settlement unit, or both) on the other side, and that has operating modes of normal mode (similar to the registration and settlement device 52, in which products are registered based on clerk operation and settlement based on customer operation) and full self-service mode (similar to the registration and settlement device 51, in which products are registered based on customer operation and settlement based on customer operation). When registration and settlement device 51 (similar to registration and settlement device 52 and registration and settlement device 53) is installed inside a store, it is connected to LAN 19 so that it can communicate with devices installed inside or outside the store.

[0082] 3 to 6 are examples of displays on the mobile terminal 60. It is assumed that the mobile terminal 60 has already installed the application A.

[0083] 3(A) is the initial screen (standby screen, a screen in which application A and other applications are not running) of the mobile terminal 60. The initial screen in FIG. 3(A) displays the icon of application A (denoted by symbol A in the figure).

[0084] Fig. 3(B) is a menu screen (start screen) that is displayed immediately after launching app A. For example, when the icon for app A on the initial screen (Fig. 3(A)) is operated, mobile terminal 60 displays a menu screen such as that shown in Fig. 3(B). On the menu screen of Fig. 3(B), various buttons are displayed in an operable manner, such as a start shopping with cart use button BT610A that accepts an operation to start shopping using cart 70, and a start shopping without using cart button BT610B that accepts an operation to start shopping without using cart 70.

[0085] Fig. 3(C) shows the connection code reading instruction screen that is displayed after pressing the shopping cart use start button BT610A. The connection code reading instruction screen in Fig. 3(C) displays a message MS613 that instructs how to read the connection code (two-dimensional code 78) and an explanatory image GA612 that explains how to read the connection code.

[0086] After the connection with the cart 70 is completed by reading the two-dimensional code 78 (for example, immediately after the connection is completed), the mobile terminal 60 may transmit tare instruction information to the cart 70 and execute the tare. The mobile terminal 60 may display a small screen (not shown) on top of the menu screen of FIG. 3(B) with a message such as "Please set the shopping basket. When you're done, press the OK button" and an OK button, based on the operation of the cart use start button BT610A on the menu screen of FIG. 3(B). The mobile terminal 60 may then erase the small screen and display the connection code reading instruction screen of FIG. 3(C). In other words, the mobile terminal 60 may instruct the customer to set a tare before executing the tare (before the two-dimensional code 78 is read). The mobile terminal 60 may also display the small screen on top of the connection code reading instruction screen of FIG. 3(C) based on the operation of the cart use start shopping button BT610A on the menu screen of FIG. 3(B).

[0087] The small screen may be displayed after the connection with the cart 70 is completed by reading the two-dimensional code 78, and may be dismissed and the tare weight may be calculated by pressing the OK button. By prompting the user to set the shopping cart at least before the tare weight is calculated, it is possible to prevent the problem of the shopping cart being judged to contain unregistered items when it is set after the tare weight is calculated. Furthermore, the user may be prompted (e.g., displayed on the screen) to set their own bag or basket instead of or in addition to the store-provided shopping basket. When starting shopping using a store-provided shopping basket, the user must eventually (e.g., after paying) transfer the items (purchased items) from the basket into their own bag or basket. However, when starting shopping using a personal bag or basket, the transfer work described above is not required, allowing for hassle-free and efficient shopping.

[0088] FIG. 3(D) is a registration screen (initial registration screen) that is displayed after connection with the cart 70 (connection using device identification information acquired from the two-dimensional code 78) is completed. The registration screen in FIG. 3(D) is provided with a captured image display area HR620, a registration information display area HR630, etc. The captured image display area HR620 is an area that mainly displays a captured image. The registration information display area HR630 is an area that mainly displays product registration information (transaction details). The captured image display area HR620 (above the captured image display area HR620) is provided with a registration method selection button display area HR621, in which a recommendation button BT624 is displayed. The registration method selection button display area HR621 is an area that displays a registration method selection button.

[0089] The registration method selection button is a button that allows selection (switching) of the product registration method (scan registration / button registration). In the registration method selection button display area HR621, the scan registration button BT622 (a button displayed as "Scan" in this example) and the button registration button BT623 (a button displayed as "No barcode" in this example) are displayed as registration method selection buttons. The customer operates (touches) the scan registration button BT622 when switching the product registration method from button registration to scan registration, and operates the button registration button BT623 when switching the product registration method from scan registration to button registration.

[0090] When scan registration is selected, the portable terminal 60 displays the scan registration button BT622 in a display mode indicating a selected state (shown with a thick frame in the figure), and displays the button registration button BT623 in a display mode indicating a non-selected state (shown with a dashed line in the figure). When button registration is selected, the portable terminal 60 displays the button registration button BT623 in a display mode indicating a selected state, and displays the scan registration button BT622 in a display mode indicating a non-selected state. On the registration screen in Figure 3(D), the scan registration button BT622 is displayed with a thick frame, and the button registration button BT623 is displayed with a dashed line (scan registration is selected).

[0091] When the recommendation button BT624 is operated (touched), the mobile terminal 60 displays a recommended product screen (not shown) that presents recommended products. Note that the "12" in "★12" in this example indicates that there are 12 recommended products.

[0092] A registration screen on which scan registration is selected may be referred to as a scan registration screen, and a registration screen on which button registration is selected may be referred to as a button registration screen.

[0093] Fig. 3(E) is a display example of a scene following Fig. 3(D). When the barcode of the whitebait is being imaged by the customer's action, the mobile terminal 60 displays a registration screen (scan registration screen) as shown in Fig. 3(E).

[0094] FIG. 3(F) is an example display of a scene following FIG. 3(E). When the mobile terminal 60 acquires the product code for whitebait from the barcode, it displays a registration screen (scan registration screen) as shown in FIG. 3(F). The registration information display area HR630 on the registration screen (scan registration screen) in FIG. 3(F) displays the registration information of the scanned and registered product (whitebait). After registering the product (one item), the mobile terminal 60 displays an operable checkout instruction button BT631 (in this example, a button displaying "Proceed to Checkout") that accepts checkout instruction operations, as shown in FIG. 3(F). The quantity button BT632 displays the purchase quantity and is a button that is operated to change the purchase quantity or cancel the purchase.

[0095] FIG. 3(G) is a display example of a scene following FIG. 3(F). When the quantity button BT632 is operated, the mobile terminal 60 displays a small screen (pop-up screen) SG1 in front of the registration screen of FIG. 3(F), as shown in FIG. 3(G). The mobile terminal 60 tone-downs the back surface (except for the registration information portion of the product) to make the small screen SG1 on the front and the product stand out, but can accept a touch on any location on the back surface as an operation to clear the small screen SG1. In other words, while the small screen SG1 is displayed, the area behind the small screen SG1 is an area that accepts an operation to clear the small screen SG1.

[0096] The small screen SG1 displays the purchase quantity of the product (whitebait) (displayed as "xn") and the total price for the purchase quantity of the product, and also has a product cancellation button (in this example, a button displayed as "Cancel Product"), a minus button (in this example, a button displayed as "-"), and a plus button (in this example, a button displayed as "+").

[0097] The product cancellation button is a button that is operated when canceling the registration of the registered product (all items). The minus button is a button that is operated when decreasing the purchase quantity of the registered product. Operating the minus button once (quantity decrease operation) decreases the purchase quantity by one. In the example shown in Figure 3, the purchase quantity is "1", so the minus button cannot be operated. The plus button is a button that is operated when increasing the purchase quantity of the registered product. Operating the plus button once (quantity increase operation) increases the purchase quantity by one.

[0098] Fig. 3(H) is a display example of a scene following Fig. 3(G). When the plus button is operated twice, the mobile terminal 60 displays the small screen SG1 as shown in Fig. 3(H).

[0099] Fig. 4(A) is a display example of a scene following Fig. 3(H). When an operation is performed on an area other than the small screen SG1 (any area on the back), the mobile terminal 60 erases the small screen SG1 and displays a registration screen that reflects the operation to increase the quantity, as shown in Fig. 4(A).

[0100] In addition, if an operation is performed on an area other than small screen SG1 without any operation being performed on small screen SG1 (product cancellation operation using the product cancellation button, quantity decrease operation using the minus button, quantity increase operation using the plus button), the mobile terminal 60 will simply erase small screen SG1 (Figure 3(G) → Figure 3(F)).

[0101] In addition, a decision button to be operated when deciding (confirming) an operation (product cancellation operation, quantity decrease operation, quantity increase operation) or a cancel button to be operated when simply erasing the small screen SG1 may be arranged on the small screen SG1. When the decision button or the cancel button is arranged on the small screen SG1, the mobile terminal 60 may erase the small screen SG1 and display a registration screen that reflects the quantity increase operation, as shown in FIG. 4(A), when, for example, the plus button is operated twice and then the decision button is operated. When the decision button or the cancel button is arranged on the small screen SG1, the mobile terminal 60 may simply erase the small screen SG1 and display the registration screen of FIG. 3(F) when the cancel button is operated, regardless of whether the product cancellation button, minus button, or plus button is operated.

[0102] Fig. 4(B) is a display example of a scene following Fig. 4(A). When the button registration button BT623 is operated on the registration screen of Fig. 4(A), the mobile terminal 60 displays a registration screen (button registration screen) as shown in Fig. 4(B). The registration screen of Fig. 4(B) is provided with a registration method selection button display area HR621, a tab display area HR640, a registration information display area HR630, a product button display area HR660, etc. A search button BT625 is displayed to the right of the registration method selection button display area HR621.

[0103] On the registration screen of FIG. 4(B), the scan registration button BT622 is displayed in a dashed line, and the button registration button BT623 is displayed in a thick line (button registration is selected).

[0104] When the search button BT625 is operated, the mobile terminal 60 accepts character input for searching for a product button. For example, when the search button BT625 is operated, the mobile terminal 60 displays a character input area and accepts character input from the customer in the character input area.

[0105] The tab display area HR640 is an area that displays five selectable (switchable) tabs (all tab, fruit tab, vegetable tab, fresh fish tab, prepared food tab). The four tabs other than the all tab (fruit tab, vegetable tab, fresh fish tab, prepared food tab) correspond to the four categories (fruit, vegetable, fresh fish prepared food) in which products to be registered by button registration exist. The all tab corresponds to all of the above four categories. In the registration screen of Figure 4(B), the all tab is selected. The underline on the all tab indicates that the all tab is selected.

[0106] As described above, the registration information display area HR630 is an area that mainly displays the registration information of a product. The registration information display area HR630 on the registration screen (button registration screen) of Fig. 4(B) displays the registration information of the product (whitebait) that has been scanned and registered. When the whitebait quantity button BT632 is operated, the mobile terminal 60 displays the small screen SG1 on top of the registration screen of Fig. 4(B). In other words, like the scan registration screen, the small screen SG1 can also be displayed on top of the button registration screen.

[0107] The product button display area HR660 is an area that displays product buttons for products that belong to a category corresponding to the tab selected (touched) in the tab display area HR640. In the registration screen of FIG. 4(B), the "All" tab is selected, so all product buttons (product buttons for products belonging to fruits, vegetables, fresh fish, and prepared foods) are displayed in the product button display area HR660. In the example shown in FIG. 4(B), there are many product buttons to be displayed, so they are displayed by scrolling, but they may also be displayed across multiple pages. The size of the product buttons may also be reduced. The product button display area HR660 may be provided between the tab display area HR640 and the registration information display area HR630.

[0108] When a customer selects the Fruits tab in the tab display area HR640, the mobile terminal 60 displays in the tab display area HR640 an indication that the Fruits tab has been selected (by underlining in this example), and displays product buttons for products belonging to Fruits in the product button display area HR660. For example, when a customer selects the Fruits tab in the tab display area HR640, the mobile terminal 60 identifies the category (fruits) corresponding to the Fruits tab. Next, the mobile terminal 60 references the product button file stored in the cloud server 20, and displays product buttons corresponding to the category identification information that identifies fruits (i.e., product buttons for products belonging to Fruits) in the product button display area HR660. The same applies when a customer selects the Vegetables tab, Fresh Fish tab, or Prepared Food tab.

[0109] Furthermore, if a customer selects the All tab when a tab other than the All tab is selected (for example, the scene in Figure 4(C)), as shown in Figure 4(B), a message indicating that the All tab has been selected is displayed in the tab display area HR640, and the All product buttons are displayed in the product button display area HR660.

[0110] The mobile terminal 60 may acquire the product button file together with the app A when acquiring the app A, or may acquire the product button file as part of the app A when acquiring the app A and store it in the storage unit. In this case, the mobile terminal 60 refers to the product button file stored therein and displays the product button in the product button display area HR660.

[0111] Furthermore, when the mobile terminal 60 receives character input after operating the search button BT625, it displays in the tab display area HR640 a message indicating that the all tab has been selected, and displays the product buttons searched for by the character input in the product button display area HR660. When the search results fall within one category (for example, when all the search results are fruits), the mobile terminal 60 may display in the tab display area HR640 a message indicating that the tab for that category has been selected, and display the product buttons searched for by the character input in the product button display area HR660.

[0112] Figure 4(C) is a display example of a scene following Figure 4(B). When the fresh fish tab is selected on the registration screen of Figure 4(B), the mobile terminal 60 displays a registration screen such as that shown in Figure 4(C). Because the fresh fish tab is selected on the registration screen of Figure 4(C), product buttons for products belonging to fresh fish are displayed in the product button display area HR660.

[0113] Figure 4(D) is a display example of a scene following Figure 4(C). When the saury product button (saury button) is operated from the scene of Figure 4(C), the mobile terminal 60 displays a small screen (pop-up screen) SG2 in front of the registration screen of Figure 4(C), as shown in Figure 4(D).

[0114] The small screen SG2 displays the product name (saury), the unit price of the product, the purchase quantity of the product (displayed as "xn", default value is 1), the total amount for the purchase quantity of the product, and is also provided with a minus button (in this example, a button displaying "-"), a plus button (in this example, a button displaying "+"), a cancel button (in this example, a button displaying "Quit"), and a decision button.

[0115] The minus button is a button that is operated when decreasing the purchase quantity of the registered product. Operating the plus button once (quantity decrease operation) decreases the purchase quantity by one. In the example shown in Figure 3, the purchase quantity is "1", so the minus button cannot be operated. The plus button is a button that is operated when increasing the purchase quantity of the registered product. Operating the plus button once (quantity increase operation) increases the purchase quantity by one. The decision button is a button that is operated when deciding (confirming) an operation on the small screen SG2 (quantity decrease operation, quantity increase operation). The cancel button is a button that is operated when simply erasing the small screen SG2.

[0116] Fig. 4(E) is a display example of a scene following Fig. 4(D). When the enter button is operated from the scene of Fig. 4(D), the mobile terminal 60 displays a registration screen (button registration screen) as shown in Fig. 4(D). The registration information display area HR630 of the registration screen (button registration screen) of Fig. 4(E) displays the registration information of the product (whitebait) registered by scan and the registration information of the product (pacific saury) registered by button.

[0117] Fig. 4(F) is a display example of a scene following Fig. 4(E). When the scan registration button BT622 is operated from the scene of Fig. 4(E), the mobile terminal 60 displays a registration screen (scan registration screen) as shown in Fig. 4(F). The registration information display area HR630 of the registration screen (scan registration screen) of Fig. 4(F) displays the registration information of the product (whitebait) that was scanned and registered, and the registration information of the product (pacific saury) that was button-registered.

[0118] Fig. 4(G) is a display example of another scene following Fig. 4(D). When the plus button is operated twice from the scene of Fig. 4(D), the mobile terminal 60 displays the small screen SG2 as shown in Fig. 4(G).

[0119] Fig. 4(H) is a display example of a scene following Fig. 4(G). When the enter button is operated from the scene of Fig. 4(G), the mobile terminal 60 displays a registration screen (button registration screen) as shown in Fig. 4(H). The registration information display area HR630 of the registration screen (button registration screen) of Fig. 4(H) displays the registration information of the product (whitebait) registered by scan and the registration information of the product (pacific saury) registered by button.

[0120] Fig. 5(A) is a display example of a scene following Fig. 4(H). When the scan registration button BT622 is operated from the scene of Fig. 4(H), the mobile terminal 60 displays a registration screen (scan registration screen) as shown in Fig. 5(A). The registration information display area HR630 of the registration screen (scan registration screen) of Fig. 5(A) displays the registration information of the product (whitebait) that was scanned and registered, and the registration information of the product (pacific saury) that was button-registered.

[0121] Fig. 5(B) is a display example of a scene following Fig. 4(F). When the saury quantity button BT632 is operated, the mobile terminal 60 displays a small screen SG1 in front of the registration screen of Fig. 4(F), as shown in Fig. 5(B).

[0122] Fig. 5(C) is a display example of a scene following Fig. 5(B). When the plus button is operated once, the mobile terminal 60 displays the small screen SG1 as shown in Fig. 5(C).

[0123] Fig. 5(D) is a display example of a scene following Fig. 5(C). When an operation is performed on an area other than the small screen SG1 (any area on the back), the mobile terminal 60 erases the small screen SG1 and displays a registration screen that reflects the operation to increase the quantity, as shown in Fig. 5(D).

[0124] Fig. 5(E) is a display example of a scene following Fig. 5(A). When the Saury quantity button BT632 is operated, the mobile terminal 60 displays a small screen SG1 in front of the registration screen of Fig. 5(A), as shown in Fig. 5(E).

[0125] Fig. 5(F) is a display example of a scene following Fig. 5(E). When the minus button is operated once, the mobile terminal 60 displays the small screen SG1 as shown in Fig. 5(F).

[0126] Fig. 5(G) is a display example of a scene following Fig. 5(F). When an operation is performed on an area other than the small screen SG1 (any area on the back), the mobile terminal 60 erases the small screen SG1 and displays a registration screen that reflects the quantity reduction operation, as shown in Fig. 5(G).

[0127] When the enter button and the cancel button are arranged on the small screen SG1, the mobile terminal 60 displays the registration screen of FIG. 5(G) when the minus button is operated once and then the enter button is operated.

[0128] Fig. 5(H) is a display example of another scene following Fig. 5(E) or Fig. 5(F). When the product cancellation button is operated, the mobile terminal 60 erases the small screen SG1 and displays a registration screen that reflects the product cancellation operation, as shown in Fig. 5(H). Note that when the product cancellation button is operated, the mobile terminal 60 may display a small screen for confirming product cancellation (a small screen on which an OK button and a Cancel button are arranged; not shown) in place of the small screen SG1, and when an operation to cancel (operation of the OK button) is performed on the small screen for confirming product cancellation, the small screen for confirming product cancellation may be erased and the registration screen of Fig. 5(H) may be displayed.

[0129] When the enter button and the cancel button are arranged on the small screen SG1, the mobile terminal 60 displays the registration screen of FIG. 5(H) when the product cancellation button is operated and then the enter button is operated.

[0130] 3 to 5, the operation when the quantity button BT632 in the registration information display area HR630 of the scan registration screen is operated to display the small screen SG1 is explained, but the operation when the quantity button BT632 in the registration information display area HR630 of the button registration screen is operated to display the small screen SG1 is also the same.

[0131] (Reporting fraud, etc.) It has been explained that if there is any fraud (fraud, mistake), the mobile terminal 60 may notify the same on the registration screen, and the following is an example of such notification.

[0132] FIG. 6(A) shows a portion of the registration screen of FIG. 4(A). For example, if the whitebait whose purchase quantity has been increased (from 1 to 3) after scan registration has not been added to the cart, the mobile terminal 60 displays "weight NG" in the display area for the whitebait registration information, as shown in FIG. 6(A). Note that the mobile terminal 60 may display "confirmation required" or "forgot to add" instead of or in addition to "weight NG." Note that if the whitebait whose purchase weight is set to 1 has not been added to the cart, the mobile terminal 60 may display, for example, "weight NG" in the display area for the whitebait registration information on the registration screen of FIG. 3(F).

[0133] FIG. 6(B) shows a portion of the registration screen of FIG. 5(D). For example, if the saury whose purchase quantity has been increased (from 1 to 2) after button registration has not been added to the cart, the mobile terminal 60 displays "weight NG" in the display area for the saury registration information, as shown in FIG. 6(B). Note that the mobile terminal 60 may display "confirmation required" or "forgot to add" instead of or in addition to "weight NG." Note that if the saury whose purchase weight is set to 1 has not been added to the cart, the mobile terminal 60 may display, for example, "weight NG" in the display area for the saury registration information on the registration screen of FIG. 4(F).

[0134] Fig. 6(C) shows a part of the registration screen of Fig. 5(G). For example, if the saury whose purchase quantity has been reduced (from 3 to 2) after button registration has not been removed from the cart, the mobile terminal 60 displays "weight NG" in the display area for the saury's registration information, as shown in Fig. 6(C). Note that the mobile terminal 60 may display "confirmation required" or "forgot to remove" instead of or in addition to "weight NG".

[0135] Fig. 6(D) shows a part of the registration screen of Fig. 5(H). For example, if the saury whose purchase was canceled after the button registration has not been removed from the cart, the mobile terminal 60 displays "(Saury weight NG)" in the area that displayed the registration information for the saury, as shown in Fig. 6(D). Note that the mobile terminal 60 may display "Confirmation Required" or "Forgot to Remove" in place of or in addition to "Weight NG" in the "Weight NG" portion.

[0136] Note that when fraud or the like occurs in which the product cannot be identified (for example, when an unregistered product is inserted), the mobile terminal 60 notifies the user of the fraud or the like without associating it with the product name. When fraud or the like occurs in which the product cannot be identified, the mobile terminal 60 may store information indicating that fraud or the like has occurred (for example, a confirmation required flag) along with a captured image in which the fraud or the like can be confirmed. Even when fraud or the like occurs in which the product can be identified, the mobile terminal 60 may store information indicating that fraud or the like has occurred along with a captured image in which the fraud or the like can be confirmed.

[0137] 6(A) to 6(D) are all examples in which "weight NG" or the like is notified in the registration information display area HR630 of the scan registration screen, but when the mobile terminal 60 displays "weight NG" or the like for a certain product in the registration information display area HR630 of the scan registration screen, the mobile terminal 60 also displays "weight NG" or the like for that product in the registration information display area HR630 of the button registration screen displayed subsequently (the same applies to the scan registration screen displayed subsequently). For example, when the mobile terminal 60 displays "weight NG" for Shirasu as shown in FIG. 6(A) in the registration information display area HR630 of the scan registration screen of FIG. 4(A), the mobile terminal 60 also displays "weight NG" or the like for Shirasu as shown in FIG. 6(A) in the registration information display area HR630 of the button registration screen of FIG. 4(B), which is switched from FIG. 4(A).

[0138] When fraud or the like has occurred, the mobile terminal 60 notifies the user of the fact that fraud or the like has occurred as described above, but instead of or in addition to notifying the user of the fact that fraud or the like has occurred when fraud or the like has occurred, the mobile terminal 60 may also notify the user of the fact that no fraud or the like has occurred when fraud or the like has not occurred. For example, the mobile terminal 60 may display "weight OK" or "confirmed."

[0139] The mobile terminal 60 may notify of fraud or the like on a small screen instead of or in addition to the registration information display area HR630. The mobile terminal 60 may display a small screen displaying a different message depending on the type of fraud or the like. For example, if a registration is forgotten, the mobile terminal 60 may display a small screen displaying a message such as "No product was registered" (hereinafter, this may be referred to as a "forgotten registration notification small screen"). If an insertion is forgotten, the mobile terminal 60 may display a small screen displaying a message such as "No product was inserted" (hereinafter, this may be referred to as a "forgotten insertion notification small screen"). If a removal is forgotten, the mobile terminal 60 may display a small screen displaying a message such as "No product was removed" (hereinafter, this may be referred to as a "forgotten removal notification small screen"). If a cancellation is forgotten, the mobile terminal 60 may display a small screen displaying a message such as "No product was canceled" (hereinafter, this may be referred to as a "forgotten cancellation notification small screen"). The small screen for registration is forgotten and may have an OK button for clearing the small screen for registration. The same applies to the small screen for informing about forgotten insertion, the small screen for informing about forgotten removal, and the small screen for informing about forgotten cancellation. Note that when the small screen informing about fraud, etc. is erased (for example, when it is erased based on the operation of the OK button if an OK button is provided, or when it is erased based on the touch operation of any location on the back surface (scan registration screen) if an OK button is not provided, or when a predetermined time has passed), the mobile terminal 60 may further (following the notification by the small screen) notify about fraud, etc. in the registration information display area HR630 of the registration screen after the small screen is erased, as shown in FIG.

[0140] Furthermore, the mobile terminal 60 does not initiate a determination (judgment) of fraud, etc., at least during a period when there is room (possibility) for button registration, purchase quantity change, or purchase cancellation. More specifically, in addition to button registration, purchase quantity change, and purchase cancellation during the above-mentioned period, product insertion and product removal during the above-mentioned period are also subject to fraud, etc., but the timing of the judgment is after the end of the period. Specifically, the mobile terminal 60 does not initiate a determination of fraud, etc., during a period when the small screen SG1 is displayed regardless of whether the scan registration screen or the button registration screen is displayed on the back, or during a period when the button registration screen is displayed regardless of whether the small screen SG1 or the small screen SG2 is displayed on the front. Instead, the mobile terminal 60 initiates a determination of fraud, etc., after a period when the scan registration screen without the small screen SG1 is displayed on the front. Naturally, notification of fraud, etc., is made after a determination of fraud, etc., so the mobile terminal 60 does not notify of fraud, etc., while the small screen SG1 or the button registration screen is displayed.

[0141] 7 to 16 are explanatory diagrams that explain the relationship between various situations (display screen, product insertion, product removal, product registration, change in purchase quantity, purchase cancellation, etc.) and fraud, etc. In each of the figures (FIGS. 7(A) to 16(B)), the flow of time is indicated from left to right. Also, at the beginning of each figure, the mobile terminal 60 is assumed to be displaying the scan registration screen. FIGS. 7 to 10 show types that are disadvantageous to the store (forgetting to register, forgetting to remove). FIGS. 11 to 16 show types that are disadvantageous to the customer (forgetting to insert, forgetting to cancel).

[0142] Figure 7(A) shows whether or not a scan registration, or a button registration screen display (operation of button registration button BT623), or a small screen SG1 display (operation of quantity button BT632) occurs within a predetermined time (e.g., 10 seconds) after the product is inserted.

[0143] As described above, the mobile terminal 60 can manage the time elapsed since the product was added to the cart. Therefore, the mobile terminal 60 can determine whether a scan registration or the like has occurred within a predetermined time since the product was added. The cart 70 may receive operation information from the mobile terminal 60, determine whether a scan registration or the like has occurred within a predetermined time since the product was added, and notify the mobile terminal 60 of the determination result.

[0144] The timing at which the cart 70 receives operation information for the mobile terminal 60 from the mobile terminal 60 is the timing at which the operation is performed on the mobile terminal 60. In other words, the mobile terminal 60 transmits operation information to the cart 70 when an operation is performed. The timing at which the cart 70 receives control information for the screen on the mobile terminal 60 from the mobile terminal 60 is the timing at which the screen on the mobile terminal 60 is displayed / hidden. In other words, the mobile terminal 60 transmits screen control information to the cart 70 when the screen is switched between displayed and hidden. The same applies to the other figures (FIGS. 7(B) to 16(B)).

[0145] If the scan registration is made within the predetermined time, the mobile terminal 60 will not report any fraud (weight OK). This situation occurs when, after a product is inserted, the same product as the inserted product is scanned and registered. The case where the button registration screen is displayed within the predetermined time will be described later (FIG. 7(B)). The case where the small screen SG1 is displayed within a predetermined time will be described later (FIG. 7(C)). If there is no such thing, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user of forgotten registration. At least, the determination that nothing has happened (weight NG (forgotten to register)) is not made within the predetermined time (it is made after the predetermined time has elapsed).

[0146] FIG. 7(B) displays the button registration screen within a predetermined time after the product is inserted, and indicates whether or not there is any button registration while the button registration screen is displayed (between the operation of the button registration button BT623 and the operation of the scan registration button BT622).

[0147] The mobile terminal 60 determines whether or not a button has been registered while the button registration screen is displayed. Note that the cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, determine whether or not a button has been registered while the button registration screen is displayed, and notify the mobile terminal 60 of the determination result.

[0148] If a button is registered while the button registration screen is displayed, the mobile terminal 60 does not report any fraud or the like (weight OK). If no button is registered while the button registration screen is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user that registration has been forgotten. At least, the determination that there is no button registration (weight NG (registration forgotten) determination) is not made while the button registration screen is displayed (it is made after the scan registration button BT622 is operated or the scan registration screen is displayed).

[0149] FIG. 7(C) shows whether or not a quantity increase operation has been performed while the small screen SG1 is displayed within a predetermined time after the product has been inserted.

[0150] The mobile terminal 60 determines whether or not a quantity increase operation has been performed while the small screen SG1 is displayed. Note that the cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, determine whether or not a quantity increase operation has been performed while the small screen SG1 is displayed, and notify the mobile terminal 60 of the determination result.

[0151] If an operation to increase the quantity is performed while the small screen SG1 is displayed, the mobile terminal 60 does not report any fraud or the like (weight OK). If no operation to increase the quantity is performed while the small screen SG1 is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user that registration has been forgotten. At least, the determination that there has been no operation to increase the quantity (weight NG (forgotten to register) determination) is not made while the small screen SG1 is displayed (it is made after the small screen SG1 is erased).

[0152] FIG. 8(A) shows whether or not a product is removed while the small screen SG1 is being displayed when a product cancellation operation or a quantity reduction operation is performed on the small screen SG1.

[0153] When a product cancellation operation or a quantity reduction operation is performed on the small screen SG1, the mobile terminal 60 determines whether or not the product was removed while the small screen SG1 is displayed. Note that the cart 70 may receive from the mobile terminal 60 control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60, determine whether or not the product was removed while the small screen SG1 is displayed when a product cancellation operation or a quantity reduction operation is performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0154] If a product is removed while the small screen SG1 is displayed, the mobile terminal 60 does not report any fraud or the like (weight OK). If the product is not removed while the small screen SG1 is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten to remove)). For example, the mobile terminal 60 may display a small screen for notifying the user of the product being left behind. At least, the determination that the product has not been removed (weight NG (forgotten to remove) determination) is not made while the small screen SG1 is displayed.

[0155] The period for determining whether to remove a product may include a predetermined time (e.g., 5 seconds) before the small screen SG1 is displayed. The period for determining whether to remove a product may include a predetermined time (e.g., 5 seconds) after the small screen SG1 is hidden, instead of or in addition to the predetermined time before the small screen SG1 is displayed. In other words, the period for determining whether to remove a product may include one or both of the predetermined time before the small screen SG1 is displayed and the predetermined time after the small screen SG1 is hidden. Note that the predetermined time before display and the predetermined time after hiding do not have to be the same length.

[0156] Figure 8(B) shows whether or not a product is removed between a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased when a product cancellation operation or quantity reduction operation is performed on the small screen SG1.

[0157] As described above, the mobile terminal 60 can manage the elapsed time from when a product was removed from the cart. Therefore, the mobile terminal 60 can determine whether the small screen SG1 was displayed within a predetermined time from when the product was removed, whether the product was removed within the predetermined time (within the predetermined time before the small screen SG1 was displayed), and whether a product cancellation operation or a quantity reduction operation was performed on the small screen SG1. That is, when a product cancellation operation or a quantity reduction operation is performed on the small screen SG1, the mobile terminal 60 can determine whether the product was removed within the predetermined time before the small screen SG1 was displayed. The cart 70 may receive screen control information and operation information on the mobile terminal 60 from the mobile terminal 60, determine whether a product was removed within the predetermined time before the small screen SG1 was displayed when a product cancellation operation or a quantity reduction operation is performed on the small screen SG1, and notify the mobile terminal 60 of the determination result. Furthermore, as described above, the mobile terminal 60 can manage the elapsed time from when a certain screen (including a small screen) was cleared. Therefore, when a product cancellation operation or a quantity reduction operation is performed on the small screen SG1, the mobile terminal 60 can determine whether or not the product has been removed within a predetermined time after the small screen SG1 is cleared. Note that the cart 70 may receive from the mobile terminal 60 control information for the screen on the mobile terminal 60 and operation information for the mobile terminal 60, and may determine whether or not the product has been removed within a predetermined time after the small screen SG1 is cleared when a product cancellation operation or a quantity reduction operation is performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0158] If a product is removed during a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased, the mobile terminal 60 does not report any fraud or the like (weight OK). If the product is not removed during a predetermined time period from before the small screen SG1 is displayed to a predetermined time period after the small screen SG1 is removed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten to remove)). For example, the mobile terminal 60 may display a small screen for notifying the user of the product being left behind. It should be noted that at least the determination that the product has not been removed (weight NG (forgotten to remove) determination) is made after a predetermined time has elapsed since the small screen SG1 was erased.

[0159] FIG. 9(A) shows whether or not a product is inserted while the button registration screen is displayed in the case where no button registration is performed while the button registration screen is displayed (between the operation of the button registration button BT623 and the operation of the scan registration button BT622).

[0160] When no button registration is performed while the button registration screen is displayed, the mobile terminal 60 determines whether or not a product has been inserted while the button registration screen is displayed. Note that the cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, and when no button registration is performed while the button registration screen is displayed, determine whether or not a product has been inserted while the button registration screen is displayed, and notify the mobile terminal 60 of the determination result.

[0161] If a product is inserted while the button registration screen is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user that registration has been forgotten. If no product is inserted while the button registration screen is displayed, the mobile terminal 60 does not report any fraud or the like. At least, the determination that a product has been inserted (determination that the weight is NG (forgotten to register)) is not made while the button registration screen is displayed.

[0162] The period for determining whether to insert a product may include a predetermined time (e.g., 5 seconds) before the button registration screen is displayed. The period for determining whether to insert a product may include a predetermined time (e.g., 5 seconds) after the button registration screen is cleared (after the scan registration screen is displayed) instead of or in addition to the predetermined time before the button registration screen is displayed. In other words, the period for determining whether to insert a product may include one or both of the predetermined time before the button registration screen is displayed and the predetermined time after the button registration screen is cleared. Note that the predetermined time before display and the predetermined time after clearing do not have to be the same length.

[0163] Figure 9(B) shows whether or not a product is inserted between a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is deleted when no button registration is performed while the button registration screen is displayed.

[0164] As described above, the mobile terminal 60 can manage the elapsed time from when a product was added to the cart. Therefore, the mobile terminal 60 can determine whether the button registration screen was displayed within a predetermined time from when the product was added, whether a product was added within the predetermined time (within the predetermined time before the button registration screen was displayed), and whether a button was registered on the button registration screen. That is, the mobile terminal 60 can determine whether a product was added within the predetermined time before the button registration screen was displayed, even if no button registration was performed while the button registration screen was displayed. The cart 70 may receive screen control information and operation information from the mobile terminal 60, and determine whether a product was added within the predetermined time before the button registration screen was displayed, even if no button registration was performed while the button registration screen was displayed, and notify the mobile terminal 60 of the determination result. Furthermore, as described above, the mobile terminal 60 can manage the elapsed time from when a certain screen (including a small screen) was cleared. Therefore, when no button registration is performed while the button registration screen is displayed, the mobile terminal 60 can determine whether or not a product has been inserted within a predetermined time after the button registration screen is cleared. Note that the cart 70 may receive from the mobile terminal 60 control information for the screen on the mobile terminal 60 and operation information for the mobile terminal 60, and when no button registration is performed while the button registration screen is displayed, determine whether or not a product has been inserted within a predetermined time after the button registration screen is cleared, and notify the mobile terminal 60 of the determination result.

[0165] If a product is inserted between a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is deleted, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user of forgotten registration. If no product is inserted during the predetermined time before the button registration screen is displayed to the predetermined time after the button registration screen is deleted, the mobile terminal 60 does not report any fraud or the like. At least, the determination that a product has been inserted (determination that the weight is NG (forgotten to register)) is made after a predetermined time has elapsed since the button registration screen was cleared (the scan registration screen was displayed).

[0166] FIG. 10(A) shows whether or not a product is inserted while the small screen SG1 is displayed in a case where neither a product cancellation operation, a quantity decrease operation, nor a quantity increase operation is performed on the small screen SG1.

[0167] The mobile terminal 60 determines whether a product has been added while the small screen SG1 is displayed when no product cancellation operation, quantity decrease operation, or quantity increase operation has been performed on the small screen SG1. The cart 70 may receive control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60 from the mobile terminal 60, and determine whether a product has been added while the small screen SG1 is displayed when no product cancellation operation, quantity decrease operation, or quantity increase operation has been performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0168] If a product is inserted while the small screen SG1 is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user of forgotten registration. If no product is inserted while the small screen SG1 is displayed, the mobile terminal 60 does not report any fraud or the like. At least, the determination that a product has been inserted (determination that the weight is NG (forgotten to register)) is not made while the small screen SG1 is displayed.

[0169] The period for determining whether to insert a product may include a predetermined time (e.g., 5 seconds) before the small screen SG1 is displayed. The period for determining whether to remove a product may include a predetermined time (e.g., 5 seconds) after the small screen SG1 is hidden, instead of or in addition to the predetermined time before the small screen SG1 is displayed. In other words, the period for determining whether to insert a product may include one or both of the predetermined time before the small screen SG1 is displayed and the predetermined time after the small screen SG1 is hidden. Note that the predetermined time before display and the predetermined time after hiding do not have to be the same length.

[0170] Figure 10(B) shows whether or not a product is inserted between a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased, when no product cancellation operation, quantity decrease operation, or quantity increase operation is performed on the small screen SG1.

[0171] As described above, the mobile terminal 60 can manage the elapsed time from when a product was added to the cart. Therefore, the mobile terminal 60 can determine whether the small screen SG1 was displayed within a predetermined time after the product was added, whether the product was added within the predetermined time (within the predetermined time before the small screen SG1 was displayed), and whether a product cancellation operation, a quantity decrease operation, or a quantity increase operation was performed on the small screen SG1. That is, the mobile terminal 60 can determine whether a product was added within the predetermined time before the small screen SG1 was displayed when no product cancellation operation, quantity decrease operation, or quantity increase operation was performed on the small screen SG1. The cart 70 may receive control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60 from the mobile terminal 60, determine whether a product was added within the predetermined time before the small screen SG1 was displayed when no product cancellation operation, quantity decrease operation, or quantity increase operation was performed on the small screen SG1, and notify the mobile terminal 60 of the determination result. As described above, the mobile terminal 60 can manage the elapsed time from the timing of clearing a certain screen (including a small screen). Therefore, the mobile terminal 60 can determine whether a product has been added within a predetermined time after the small screen SG1 was cleared when no product cancellation operation, quantity decrease operation, or quantity increase operation has been performed on the small screen SG1. The cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, and determine whether a product has been added within a predetermined time after the small screen SG1 was cleared when no product cancellation operation, quantity decrease operation, or quantity increase operation has been performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0172] If a product is inserted between a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased, the mobile terminal 60 notifies the user of fraud (weight NG (forgotten registration)). For example, the mobile terminal 60 may display a small screen for notifying the user of forgotten registration. If no product is inserted during the predetermined time before the small screen SG1 is displayed and the predetermined time after the small screen SG1 is erased, the mobile terminal 60 does not report any fraud or the like. At least, the determination as to whether or not a product has been inserted (determination as to whether or not the weight is NG (forgotten to register)) is made after a predetermined time has elapsed since the small screen SG1 was erased.

[0173] In addition, in relation to the example shown in Figure 7(C) and the example shown in Figure 10, if a product cancellation operation or quantity reduction operation is performed on small screen SG1 and a product is inserted while small screen SG1 is displayed (which may be a period including a predetermined time before display or a predetermined time after deletion), the mobile terminal 60 will report fraud, etc. (weight NG (forgot to remove, forgot to register)).

[0174] FIG. 11 shows whether or not a product is inserted within a predetermined time (for example, 10 seconds) after scan registration.

[0175] As described above, the mobile terminal 60 can manage the elapsed time from the scan registration operation timing. Therefore, the mobile terminal 60 can determine whether or not a product has been inserted within a predetermined time from the scan registration. Alternatively, the cart 70 may receive operation information on the mobile terminal 60 from the mobile terminal 60, determine whether or not a product has been inserted within a predetermined time from the scan registration, and notify the mobile terminal 60 of the determination result.

[0176] If the product is inserted within the predetermined time, the mobile terminal 60 will not report any fraud or the like (weight OK). If the product is not inserted within a predetermined time, the mobile terminal 60 will notify the user of fraud, etc. (Important NG (forgotten insertion)). For example, the mobile terminal 60 may display a small screen for notifying the user that the product has been inserted. At least, a determination that the product has not been inserted (a determination that the product has been omitted) is not made within a predetermined time.

[0177] FIG. 12(A) shows whether or not a product is inserted while the button registration screen is displayed (between the operation of the button registration button BT623 and the operation of the scan registration button BT622) when button registration is performed on the button registration screen.

[0178] When button registration is performed on the button registration screen, the mobile terminal 60 determines whether or not a product has been inserted while the button registration screen is displayed. Note that the cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, and may determine whether or not a product has been inserted while the button registration screen is displayed when button registration is performed on the button registration screen, and notify the mobile terminal 60 of the determination result.

[0179] If a product is inserted while the button registration screen is displayed, the mobile terminal 60 will not report any fraud or the like (weight OK). If no product is inserted while the button registration screen is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten to insert)). For example, the mobile terminal 60 may display a small screen for notifying the user that a product has been inserted. At least, the determination that the product has not been inserted (determination that the weight is NG (forgotten to insert)) is not made while the button registration screen is displayed.

[0180] The period for determining whether to insert a product may include one or both of the predetermined time before the button registration screen is displayed and the predetermined time after the button registration screen is deleted. Note that the predetermined time before the display and the predetermined time after the deletion do not have to be the same length.

[0181] FIG. 12(B) shows whether or not a product is inserted during a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is deleted when button registration is performed on the button registration screen.

[0182] As described above, the mobile terminal 60 can manage the elapsed time from when a product was added to the cart. Therefore, the mobile terminal 60 can determine whether the button registration screen was displayed within a predetermined time from when a product was added, whether a product was added within the predetermined time (within the predetermined time before the button registration screen was displayed), and whether button registration was performed on the button registration screen. That is, when button registration was performed on the button registration screen, the mobile terminal 60 can determine whether a product was added within the predetermined time before the button registration screen was displayed. The cart 70 may receive screen control information and operation information for the mobile terminal 60 from the mobile terminal 60, determine whether a product was added within the predetermined time before the button registration screen was displayed, and notify the mobile terminal 60 of the determination result. Furthermore, as described above, the mobile terminal 60 can manage the elapsed time from when a certain screen (including a small screen) was cleared. Therefore, when button registration was performed on the button registration screen, the mobile terminal 60 can determine whether a product was added within the predetermined time after the button registration screen was cleared. In addition, the cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, and when button registration is performed on the button registration screen, determine whether or not a product has been inserted within a specified time after the button registration screen is deleted, and notify the mobile terminal 60 of the determination result.

[0183] If a product is inserted between a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is deleted, the mobile terminal 60 will not report any fraud or the like (weight OK). If no product is inserted during a predetermined time period from before the button registration screen is displayed to a predetermined time period after the button registration screen is deleted, the mobile terminal 60 notifies the user of fraud, etc. (forgotten insertion). For example, the mobile terminal 60 may display a small screen for notifying the user of forgotten insertion. At least, the determination that no product has been inserted (weight NG (forgotten to insert) determination) is made after a predetermined time has elapsed since the button registration screen was cleared (the scan registration screen was displayed).

[0184] FIG. 13(A) shows whether or not a product is inserted while the small screen SG1 is being displayed when a quantity increase operation is performed on the small screen SG1.

[0185] When a quantity increase operation is performed on the small screen SG1, the mobile terminal 60 determines whether or not a product has been added while the small screen SG1 is displayed. Note that the cart 70 may receive control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60 from the mobile terminal 60, determine whether or not a product has been added while the small screen SG1 is displayed when a quantity increase operation is performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0186] If a product is inserted while the small screen SG1 is displayed, the mobile terminal 60 does not report any fraud or the like (weight OK). If no product is inserted while the small screen SG1 is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (forgotten to insert)). For example, the mobile terminal 60 may display a small screen for notifying the user of forgotten to insert. At least, the determination that the product has not been inserted (weight NG (forgotten to insert) determination) is not made while the small screen SG1 is displayed.

[0187] The period for determining whether to insert a commodity may include one or both of a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is removed. Note that the predetermined time before the display and the predetermined time after the removal do not have to be the same length.

[0188] FIG. 13(B) shows whether or not a product is inserted during a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased when a quantity increase operation is performed on the small screen SG1.

[0189] As described above, the mobile terminal 60 can manage the elapsed time from when a product was added to the cart. Therefore, the mobile terminal 60 can determine whether the small screen SG1 was displayed within a predetermined time after the product was added, whether the product was added within the predetermined time (within the predetermined time before the small screen SG1 was displayed), and whether an operation to increase the quantity was performed on the small screen SG1. That is, when an operation to increase the quantity was performed on the small screen SG1, the mobile terminal 60 can determine whether the product was added within the predetermined time before the small screen SG1 was displayed. The cart 70 may receive control information about the screen of the mobile terminal 60 or operation information about the mobile terminal 60 from the mobile terminal 60, determine whether a product was added within the predetermined time before the small screen SG1 was displayed when an operation to increase the quantity was performed on the small screen SG1, and notify the mobile terminal 60 of the determination result. Furthermore, as described above, the mobile terminal 60 can manage the elapsed time from when a certain screen (including a small screen) was cleared. Therefore, when a quantity increase operation is performed on the small screen SG1, the mobile terminal 60 can determine whether or not a product has been added within a predetermined time after the small screen SG1 is cleared. Note that the cart 70 may receive control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60 from the mobile terminal 60, determine whether or not a product has been added within a predetermined time after the small screen SG1 is cleared when a quantity increase operation is performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0190] If a commodity is inserted between a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased, the mobile terminal 60 does not report any fraud or the like (weight OK). If no product is inserted during a predetermined time period from before the small screen SG1 is displayed to a predetermined time period after the small screen SG1 is removed, the mobile terminal 60 notifies the user of fraud (weight NG (forgotten to insert)). For example, the mobile terminal 60 may display a small screen for notifying the user of the forgotten to insert product. At least, the determination that no product has been inserted (weight NG (forgotten to insert) determination) is made after a predetermined time has elapsed since the small screen SG1 was erased.

[0191] FIG. 14(A) shows whether or not the small screen SG1 is displayed (the quantity button BT632 is operated) within a predetermined time (for example, 10 seconds) after the product is taken out.

[0192] As described above, the mobile terminal 60 can manage the elapsed time from when a product was removed from the cart. Therefore, the mobile terminal 60 can determine whether or not the small screen SG1 was displayed within a predetermined time from when the product was removed. The cart 70 may receive control information for the screen of the mobile terminal 60 from the mobile terminal 60, determine whether or not the small screen SG1 was displayed within a predetermined time from when the product was removed, and notify the mobile terminal 60 of the determination result.

[0193] The case where the small screen SG1 is displayed within a predetermined time will be described later (FIG. 14(B)). If the small screen SG1 is not displayed within a predetermined time, the mobile terminal 60 will notify the user of fraud or the like (weight NG (cancellation forgotten)). For example, the mobile terminal 60 may display a small screen for notifying the user of a forgotten cancellation. Note that, for convenience, it is assumed that the user has forgotten to cancel, but it is also possible that the same product has been registered multiple times and only some of the products have been removed, so it may actually be that the quantity has been forgotten to be reduced. At least, the determination that the small screen SG1 was not displayed (weight NG (cancellation forgotten) determination) is not made within a predetermined time.

[0194] FIG. 14(B) displays the small screen SG1 within a predetermined time after the product is taken out, and indicates whether or not a product cancellation operation or a quantity reduction operation is performed while the small screen SG1 is displayed.

[0195] The mobile terminal 60 determines whether a product cancellation operation or a quantity reduction operation has been performed while the small screen SG1 is displayed. Note that the cart 70 may receive from the mobile terminal 60 control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60, determine whether a product cancellation operation or a quantity reduction operation has been performed while the small screen SG1 is displayed, and notify the mobile terminal 60 of the determination result.

[0196] When a product cancellation operation or a quantity reduction operation is performed, the mobile terminal 60 does not report fraud or the like (weight OK). If there is no product cancellation operation or quantity reduction operation, the mobile terminal 60 will report fraud, etc. (weight NG (cancellation forgotten)). For example, the mobile terminal 60 may display a small screen for reporting a forgotten cancellation. Note that, for convenience, it is assumed that the same product has been registered multiple times and some of the products may have been removed, so it may actually be a forgotten quantity reduction. It should be noted that at least the determination that there has been no product cancellation operation or quantity reduction operation (weight NG (cancellation forgotten) determination) is not made while the small screen SG1 is displayed.

[0197] FIG. 15(A) shows whether or not a product is removed while the button registration screen is displayed in a case where no button registration is performed while the button registration screen is displayed.

[0198] When no button registration is performed while the button registration screen is displayed, the mobile terminal 60 determines whether or not a product has been removed while the button registration screen is displayed. Note that the cart 70 may receive from the mobile terminal 60 control information for the screen on the mobile terminal 60 and operation information for the mobile terminal 60, and when no button registration is performed while the button registration screen is displayed, determine whether or not a product has been removed while the button registration screen is displayed, and notify the mobile terminal 60 of the determination result.

[0199] If a product is removed while the button registration screen is displayed, the mobile terminal 60 will notify the user of fraud (weight NG (cancellation forgotten)). For example, the mobile terminal 60 may display a small screen for notifying the user of a forgotten cancellation. For convenience, the screen is set to "cancellation forgotten," but it is also possible that the same product was registered multiple times and some of the products were removed, so it may actually be "quantity reduction forgotten." If no product is taken out while the button registration screen is displayed, the mobile terminal 60 does not report any fraud or the like. At least, the determination that a product has been removed (determination that the weight is NG (forgotten to cancel)) is not made while the button registration screen is displayed.

[0200] The period for determining whether to remove the product may include one or both of a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is removed. Note that the predetermined time before the display and the predetermined time after the removal do not have to be the same length.

[0201] Figure 15(B) shows whether or not a product is removed between a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is deleted when no button registration is performed while the button registration screen is displayed.

[0202] As described above, the mobile terminal 60 can manage the elapsed time from when a product was removed from the cart. Therefore, the mobile terminal 60 can determine whether the button registration screen was displayed within a predetermined time from when the product was removed, whether the product was removed within the predetermined time (within the predetermined time before the button registration screen was displayed), and whether a button was registered on the button registration screen. In other words, the mobile terminal 60 can determine whether a product was removed within the predetermined time before the button registration screen was displayed, even if no button registration was performed while the button registration screen was displayed. The cart 70 may receive screen control information and operation information from the mobile terminal 60, and determine whether a product was removed within the predetermined time before the button registration screen was displayed, even if no button registration was performed while the button registration screen was displayed, and notify the mobile terminal 60 of the determination result. Furthermore, as described above, the mobile terminal 60 can manage the elapsed time from when a certain screen (including a small screen) was cleared. Therefore, when no button registration is performed while the button registration screen is displayed, the mobile terminal 60 can determine whether or not a product has been removed within a predetermined time after the button registration screen is cleared. Note that the cart 70 may receive control information for the screen on the mobile terminal 60 and operation information for the mobile terminal 60 from the mobile terminal 60, and may determine whether or not a product has been removed within a predetermined time after the button registration screen is cleared when no button registration is performed while the button registration screen is displayed, and notify the mobile terminal 60 of the determination result.

[0203] If a product is removed between a predetermined time before the button registration screen is displayed and a predetermined time after the button registration screen is deleted, the mobile terminal 60 will notify the user of fraud (weight NG (cancellation forgotten)). For example, the mobile terminal 60 may display a small screen for notifying the user of a forgotten cancellation. For convenience, the message is said to be a cancellation forgotten, but since the same product may have been registered multiple times and some of the product may have been removed, it may actually be a case of a quantity reduction forgotten. If no product is taken out during the predetermined time before the button registration screen is displayed to the predetermined time after the button registration screen is deleted, the mobile terminal 60 does not report any fraud or the like. At least, the determination that a product has been removed (determination that the weight is NG (forgotten to cancel)) is made after a predetermined time has elapsed since the button registration screen was cleared (the scan registration screen was displayed).

[0204] FIG. 16(A) shows whether or not a product is removed while the small screen SG1 is displayed when neither a product cancellation operation, a quantity decrease operation nor a quantity increase operation is performed on the small screen SG1.

[0205] The mobile terminal 60 determines whether or not a product was removed while the small screen SG1 was displayed when neither a product cancellation operation, quantity decrease operation, nor quantity increase operation was performed on the small screen SG1. The cart 70 may receive from the mobile terminal 60 control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60, and may determine whether or not a product was removed while the small screen SG1 was displayed when neither a product cancellation operation, quantity decrease operation, nor quantity increase operation was performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0206] If a product is removed while the small screen SG1 is displayed, the mobile terminal 60 notifies the user of fraud, etc. (weight NG (cancellation forgotten)). For example, the mobile terminal 60 may display a small screen for notifying the user of cancellation forgotten. For convenience, we have listed it as a forgotten cancellation, but it is possible that the same product was registered multiple times and only some of them were removed, so it may also be that the quantity was forgotten to be reduced. If no product is taken out while the small screen SG1 is displayed, the mobile terminal 60 does not report any fraud or the like. At least, the determination that a product has been removed (determination that the weight is NG (cancellation forgotten)) is not made while the small screen SG1 is displayed.

[0207] The period for determining whether to insert a commodity may include one or both of a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is removed. Note that the predetermined time before the display and the predetermined time after the removal do not have to be the same length.

[0208] Figure 16(B) shows whether or not a product is removed between a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased, when no product cancellation operation, quantity decrease operation, or quantity increase operation is performed on the small screen SG1.

[0209] As described above, the mobile terminal 60 can manage the elapsed time from when a product was removed from the cart. Therefore, the mobile terminal 60 can determine whether the small screen SG1 was displayed within a predetermined time from when the product was removed, whether the product was removed within the predetermined time (within the predetermined time before the small screen SG1 was displayed), and whether a product cancellation operation, a quantity decrease operation, or a quantity increase operation was performed on the small screen SG1. That is, the mobile terminal 60 can determine whether a product was removed within the predetermined time before the small screen SG1 was displayed when no product cancellation operation, quantity decrease operation, or quantity increase operation was performed on the small screen SG1. The cart 70 may receive control information for the screen of the mobile terminal 60 and operation information for the mobile terminal 60 from the mobile terminal 60, determine whether a product was removed within the predetermined time before the small screen SG1 was displayed when no product cancellation operation, quantity decrease operation, or quantity increase operation was performed on the small screen SG1, and notify the mobile terminal 60 of the determination result. As described above, the mobile terminal 60 can manage the elapsed time from the timing of clearing a certain screen (including a small screen). Therefore, the mobile terminal 60 can determine whether a product has been removed within a predetermined time after the small screen SG1 was cleared when no product cancellation operation, quantity decrease operation, or quantity increase operation has been performed on the small screen SG1. The cart 70 may receive control information for the screen on the mobile terminal 60 and operation information on the mobile terminal 60 from the mobile terminal 60, and determine whether a product has been removed within a predetermined time after the small screen SG1 was cleared when no product cancellation operation, quantity decrease operation, or quantity increase operation has been performed on the small screen SG1, and notify the mobile terminal 60 of the determination result.

[0210] If a product is removed between a predetermined time before the small screen SG1 is displayed and a predetermined time after the small screen SG1 is erased, the mobile terminal 60 will notify the user of fraud (weight NG (cancellation forgotten)). For example, the mobile terminal 60 may display a small screen for notifying the user of a forgotten cancellation. Note that, for convenience, this is considered a forgotten cancellation, but since the same product may have been registered multiple times and some of the products may have been removed, it may actually be a forgotten reduction in quantity. If no product is taken out during the predetermined time before the small screen SG1 is displayed and the predetermined time after the small screen SG1 is erased, the mobile terminal 60 does not report any fraud or the like. It should be noted that at least the determination that a product has been removed (weight NG (cancellation forgotten) determination) is made after a predetermined time has elapsed since the small screen SG1 was erased.

[0211] 8 and 10, if a product cancellation operation or a quantity reduction operation is performed on small screen SG1 and a product is inserted while small screen SG1 is displayed (which may be a period including a predetermined time before display or a predetermined time after deletion), the mobile terminal 60 will report fraud, etc. (weight NG (forgot to remove, forgot to register)). Also, if a quantity increase operation is performed on small screen SG1 and a product is removed while small screen SG1 is displayed (which may be a period including a predetermined time before display or a predetermined time after deletion), the mobile terminal 60 will report fraud, etc. (weight NG (forgot to insert, forgot to cancel)).

[0212] FIG. 17 is a flowchart illustrating an example of the operation of the mobile terminal. Specifically, the flowchart in FIG. 17 illustrates the operation shown in FIG. 7 as an example of the operation related to reporting fraud, etc. Explanation of the operations in FIGS. 8 to 15 using flowcharts will be omitted. The flowchart in FIG. 17(A) starts when a product is inserted. The flowcharts in FIG. 17(B) and FIG. 17(C) are continuations of the flowchart in FIG. 17(A). It is assumed that the mobile terminal 60 is displaying a scan registration screen when the flowchart in FIG. 17(A) is displayed.

[0213] (Flowchart in Figure 7(A)) Step S1: The mobile terminal 60 determines whether or not there has been scan registration. If there has been scan registration (Step S1: YES), the process (process related to reporting fraud, etc.) ends. If there has not been scan registration (Step S1: NO), the process proceeds to Step S2.

[0214] Step S2: The mobile terminal 60 determines whether or not the button registration screen has been displayed (that is, whether or not the button registration button BT623 has been operated). If the button registration screen has been displayed (step S2: YES), the process proceeds to step S11 in Fig. 7(B). If the button registration screen has not been displayed (step S2: NO), the process proceeds to step S3.

[0215] Step S3: The mobile terminal 60 determines whether or not the small screen SG1 is displayed (i.e., whether or not the quantity button BT632 is operated). If the small screen SG1 is displayed (step S3: YES), the process proceeds to step S21 in FIG. 7C. If the small screen SG1 is not displayed (step S3: NO), the process proceeds to step S4.

[0216] Step S4: The mobile terminal 60 determines whether a predetermined time has passed since the product was inserted. If the predetermined time has passed (Step S4: YES), the process proceeds to Step S5. If the predetermined time has not passed (Step S4: NO), the process returns to Step S1.

[0217] Step S5: The portable terminal 60 notifies the user that the weight is NG (registration forgotten), and then ends the process (processing related to notifying the user of fraud, etc.).

[0218] (Flowchart in Figure 7(B)) Step S11: The mobile terminal 60 determines whether the button registration screen has been erased (that is, whether the scan registration button BT622 has been operated). If the button registration screen has been erased (Step S11: YES), the mobile terminal 60 proceeds to Step S12. If the button registration screen has not been erased (Step S11: NO), the mobile terminal 60 returns to Step S11.

[0219] Step S12: The mobile terminal 60 determines whether or not a button has been registered on the previous button registration screen. If a button has been registered (Step S12: YES), the process (process related to reporting fraud, etc.) ends. If a button has not been registered (Step S12: NO), the process proceeds to Step S15.

[0220] Step S15: The portable terminal 60 notifies the user that the weight is NG (registration forgotten), and then ends the process (processing related to notifying the user of fraud, etc.).

[0221] (Flowchart in Figure 7(C)) Step S21: The mobile terminal 60 determines whether the small screen SG1 has been erased. If the small screen SG1 has been erased (step S21: YES), the process proceeds to step S22. If the small screen SG1 has not been erased (step S21: NO), the process returns to step S21.

[0222] Step S22: The mobile terminal 60 determines whether or not a quantity increase operation has been performed on the previous small screen SG1. If a quantity increase operation has been performed (Step S22: YES), the process (process related to reporting fraud, etc.) ends. If a quantity increase operation has not been performed (Step S22: NO), the process proceeds to Step S25.

[0223] Step S25: The portable terminal 60 notifies the user that the weight is NG (registration forgotten), and then ends the process (processing related to notifying the user of fraud, etc.).

[0224] 6 to 17, an example of monitoring fraud, etc., by communication with the cart 70 (i.e., weight values) has been described, but as mentioned above, the mobile terminal 60 can also monitor fraud, etc., by image recognition. The mobile terminal 60 may also monitor fraud, etc., by image recognition instead of or in addition to communication with the cart 70 (i.e., weight values). When monitoring fraud, etc., using image recognition, the determination of fraud, etc., and the control of notification of fraud, etc. (timing, etc.) can be implemented in the same way as when weight values ​​are used (FIGS. 7 to 17). When weight values ​​are not used, "weight OK / weight NG" etc. may be displayed as "image OK / image NG", etc.

[0225] The embodiment has been described above, but according to the sales system 1 of the embodiment, it is possible to more suitably implement a system in which customers themselves register products.

[0226] While fraud or operational errors by customers can result in losses for the store (e.g., forgetting to register or withdraw), systems can generally lead to cases where a fraud or operational error that would result in a loss for the store is mistakenly identified as not occurring, or where a fraud or operational error that would not result in a loss for the store is mistakenly identified as not occurring. In the former case, the store's loss remains, while in the latter case, the system leaves a bad impression on the customer and requires unnecessary confirmation work by store staff (store staff). Furthermore, customer operational errors can also result in losses for the customer (e.g., forgetting to insert or cancel). In these cases, a customer's loss can also be mistakenly identified as not occurring, or where a non-customer error that would result in a loss for the customer is mistakenly identified as not occurring. In the former case, the customer's loss remains (and may ultimately lead to a loss of service), while in the latter case, the system causes unnecessary confusion for the customer and requires unnecessary confirmation work by store staff (store staff). In other words, fraud and operational errors must be handled appropriately (captured as accurately as possible).

[0227] According to the sales system 1, fraud or operational errors that result in losses to the store can be handled appropriately, for example, as shown in Figures 7 to 10, and operational errors that result in losses to the customer can be handled appropriately, for example, as shown in Figures 11 to 16.

[0228] As an example, if the system is designed to notify a customer that a product has been forgotten to be registered if it has not been registered within a uniformly predetermined time after being added to the cart, and the customer takes time to select the product button after adding the product ("Pacific saury" in this example) to the cart and is unable to register the button within the predetermined time, the customer will be notified that the product has been forgotten to be registered. In other words, being notified that the customer has forgotten to register the product despite the customer's intention to register the product will be frustrating, and the store clerk will have to perform unnecessary confirmation work. In the case of sales system 1, if the button registration screen is displayed before the predetermined time has elapsed, the customer will not be notified that the product has been forgotten to be registered, and the above-mentioned problem will not occur (Figure 7(B)). The same applies to the operation to increase the quantity (Figure 7(C)).

[0229] As another example, if the system is designed to notify a customer that a product has been forgotten to be added to the cart if the product is not added within a uniformly predetermined time from product registration, the system will notify a customer that a product has been forgotten to be added if the product has not been added within the predetermined time from button registration or if the product was added before button registration. In other words, the system will notify a customer that a product has been added even though the product has been properly added, which will confuse customers and require unnecessary confirmation work from store staff. In the case of sales system 1, if a product is added before or after button registration, the system will not notify a customer that a product has been forgotten to be added, so the above-mentioned problem will not occur (Figures 12(A)(B)). The same applies to the operation to increase the quantity (Figures 13(A)(B)).

[0230] In other words, sales system 1 does not notify customers of fraud or operational errors during periods when there is room for button registration, changes to purchase quantity, or purchase cancellation (such as when small screen SG1 is displayed, or when the button registration screen is displayed), so sales system 1 makes it less likely that problems such as those described above (such as being notified that a product has been forgotten to be registered despite the intention to register the product) will occur, making it possible to more effectively implement a system in which customers can register products themselves.

[0231] (Variations, etc.) Although each embodiment has 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) to (15). In addition, the following (1) to (15) can be appropriately combined with each other.

[0232] (1) In the above embodiment (specifically, FIG. 9(A)), an example was described in which a weight NG (registration forgotten) was reported depending on whether a product was inserted while the button registration screen was displayed, but a weight NG (registration forgotten) may also be reported depending on whether a product was inserted while the small screen SG2 was displayed. That is, in the example of FIG. 9(A), if button registration was not performed, a weight NG (registration forgotten) was reported if a product was inserted while the small screen SG2 was not displayed in the foreground (for example, while the button registration screen of FIG. 4(C) or the button registration screen of FIG. 4(E) was displayed) or while the small screen SG2 was displayed in the foreground (for example, while the button registration screen of FIG. 4(D) was displayed). However, a weight NG (registration forgotten) may also be reported only when a product was inserted while the small screen SG2 was displayed in the foreground (for example, while the button registration screen of FIG. 4(D) was displayed). In other words, the example of Figure 9(B) is an example in which weight NG (registration forgotten) is more easily notified than the example of Figure 9(A), but weight NG (registration forgotten) may be less easily notified than in Figure 9(A).

[0233] (2) In the above embodiment (specifically, FIG. 12(A)), an example was described in which a weight NG (forgotten to insert) was reported depending on whether a product was inserted while the button registration screen was displayed, but a weight NG (forgotten to insert) may also be reported depending on whether a product was inserted while the small screen SG2 was displayed. That is, in the example of FIG. 12(A), if button registration was performed, a weight NG (forgotten to insert) was reported if a product was not inserted when the small screen SG2 was not displayed in the foreground (for example, while the button registration screen of FIG. 4(C) or the button registration screen of FIG. 4(E) was displayed) or when the small screen SG2 was displayed in the foreground (for example, while the button registration screen of FIG. 4(D) was displayed), but a weight NG (forgotten to insert) may also be reported if a product was not inserted when the small screen SG2 was displayed in the foreground (for example, while the button registration screen of FIG. 4(D) was displayed). In other words, the example of Figure 12(B) is an example in which weight NG (forgotten to put in) is less likely to be notified than the example of Figure 12(A), but it may also be an example in which weight NG (forgotten to put in) is more likely to be notified than in Figure 12(A).

[0234] (3) In the above embodiment (specifically, FIG. 15(A)), an example was described in which a weight NG (cancellation forgotten) was reported depending on whether a product was removed while the button registration screen was displayed. However, a weight NG (cancellation forgotten) may also be reported depending on whether a product was inserted while the small screen SG2 was displayed. That is, in the example of FIG. 15(A), if button registration was not performed, a weight NG (cancellation forgotten) was reported if a product was removed while the small screen SG2 was not displayed in the foreground (for example, while the button registration screen of FIG. 4(C) or the button registration screen of FIG. 4(E) was displayed) or while the small screen SG2 was displayed in the foreground (for example, while the button registration screen of FIG. 4(D) was displayed). However, a weight NG (cancellation forgotten) may also be reported only when a product was removed while the small screen SG2 was displayed in the foreground (for example, while the button registration screen of FIG. 4(D) was displayed). In other words, the example of Figure 15(B) is an example in which weight NG (cancellation forgotten) is more easily notified than the example of Figure 15(A), but weight NG (cancellation forgotten) may be less easily notified than in Figure 15(A).

[0235] (4) In the above embodiment, an example was described in which button registration was completed by operating the enter button on small screen SG2, but after operating the enter button on small screen SG2, a small screen for button registration (a small screen with an OK button and a Cancel button; not shown) may be displayed instead of small screen SG2, and when an operation to register (operation of the OK button) is performed on the small screen for button registration confirmation, the small screen for product cancellation confirmation may be erased, and button registration may be completed. For example, an operation of the enter button on small screen SG2 in front of the button registration screen of Fig. 4(D) → a small screen for button registration confirmation may be displayed in front of the button registration screen of Fig. 4(D) → an OK button on the small screen for button registration confirmation may be operated → the small screen for button registration confirmation may be erased, and the button registration screen of Fig. 4(E) may be displayed.

[0236] (5) In the above embodiment, an example in which the small screen SG2 is displayed (an example in which the purchase quantity can be specified when registering the button) has been described, but the small screen SG2 does not have to be displayed (a quantity increase operation may be performed after the button is registered). For example, an operation on the saury product button (saury button) on the button registration screen of FIG. 4(C) may lead to a transition to the button registration screen of FIG. 4(E). Also, an operation on the saury product button on the button registration screen of FIG. 4(C) may lead to a display of a small screen for confirming button registration in front of the button registration screen of FIG. 4(C) → an operation on the OK button on the small screen for confirming button registration → the small screen for confirming button registration is erased, and a transition to the button registration screen of FIG. 4(E) may be made.

[0237] (6) In the above embodiment, an example was described in which the button registration screen is maintained even after button registration is performed on the button registration screen. However, when button registration is performed on the button registration screen, a transition to a scan registration screen may also be performed. For example, a transition may be made to the scan registration screen of FIG. 4(F) by operating the saury product button (saury button) on the registration screen of FIG. 4(C). Alternatively, a transition may be made to the scan registration screen of FIG. 4(F) by operating the saury product button on the button registration screen of FIG. 4(C) by displaying a small button registration confirmation screen in front of the button registration screen of FIG. 4(C) by operating the OK button on the small button registration confirmation screen by clearing the small button registration confirmation screen and displaying the scan registration screen of FIG. 4(F).

[0238] (7) In the above embodiment, an example was described in which various small screens (for example, small screen SG1, small screen SG2, various small screens for notifications, etc.) were displayed, but the information displayed on the small screens may also be displayed on a normal-sized screen such as a registration screen. In other words, instead of displaying small screen b in front of a normal-sized screen A, screen A may be switched to screen B (a screen displaying information on small screen b).

[0239] (8) Although described in the above embodiment, the weight check may be carried out, for example, as follows.

[0240] (Weight check / Check method 1) In a mode in which the cart 70 transmits the weight of all products (weight excluding tare weight) to the mobile terminal 60, the mobile terminal 60 stores the weight previously received from the cart 70 (e.g., the weight of the XX loaf of bread), calculates the difference between the weight currently received from the cart 70 (e.g., the weight of the XX loaf of bread + the XX oolong tea), compares the difference weight (weight a) with the weight of the XX oolong tea (weight b), and displays the comparison result. For example, the mobile terminal 60 may determine whether the difference between weight a and weight b falls within a predetermined range recognized as an error, and if it falls within the predetermined range, it is considered normal, and if it does not fall within the predetermined range, it is considered abnormal. The same applies to check methods 2 and 3.

[0241] It is sufficient that the mobile terminal 60 is able to refer to the weight of each product (weight b for each product). For example, the mobile terminal 60 may obtain the weight of the product (the product just registered) by inquiring (sending the product code of the registered product) of another device (for example, the cloud server 20) that stores a product weight master (a file that associates product codes with weights; this may be part of the product master), or may store the product weight master in a memory unit of the mobile terminal and obtain the weight of the product by referring to the product weight master of the mobile terminal. The same applies to check methods 2 and 3.

[0242] Furthermore, the calculation of the differential weight and the comparison of weights may be performed by the cart 70. For example, the mobile terminal 60 may transmit the weight of the currently registered product (weight on the master) to the cart 70, and the cart 70 may compare the differential weight calculated by itself with the weight (of the currently registered product) received from the mobile terminal 60. The same applies to the calculation of the differential weight and the comparison of weights in check method 2 and the comparison of weights in check method 3.

[0243] (Weight check / check method 2) When the cart 70 is configured to transmit the weight of all items (weight including tare weight) to the mobile terminal 60, the mobile terminal 60 stores the weight previously received from the cart 70 (e.g., the weight of the tare weight + XX bread), calculates the difference between this and the weight currently received from the cart 70 (e.g., the weight of the tare weight + XX bread + XX oolong tea), compares the differential weight (weight a) with the weight of the XX oolong tea (weight b), and displays the comparison result.

[0244] (Weight check / check method 3) When the cart 70 is configured to transmit the weight gain or loss (the weight gain or loss of all products or the weight gain or loss of all items) to the mobile terminal 60, the mobile terminal 60 compares the weight (weight a) received this time from the cart 70 with the weight of the XX oolong tea (weight b) and displays the comparison result.

[0245] (9) As described above, the mobile terminal 60 is equipped with an acceleration sensor and a gyro sensor, and therefore may determine whether the mobile terminal 60 itself (the mobile terminal 60 set in the cart 70, i.e., the cart 70) is moving or stationary. Note that instead of or in addition to the mobile terminal 60, the cart 70 itself may be equipped with an acceleration sensor and a gyro sensor and determine whether it is moving or stationary. In other words, the sensing results of the acceleration sensor and gyro sensor may be used to determine whether the cart 70 is moving or stationary.

[0246] By determining whether cart 70 is moving (moving state) or stationary (stationary state), the accuracy (validity, reliability) of the determination can be improved, for example, by reducing the number of erroneous determinations of fraud when fraud is not actually occurring. For example, if vibrations increase due to sudden acceleration / deceleration (including starting and stopping of movement) or poor condition of the casters, even though no products have actually been added, the weight value of the weighing unit may change, leading to the determination that a product has been added to cart 70 (forgotten to be registered) or that a product has been removed from cart 70 (forgotten to cancel). In contrast, by using the above sensing results, it can be determined that cart 70 is moving, and the change in weight value can be determined to be due to vibrations caused by movement, and the change in weight value can be ignored (referred to as ignoring control).

[0247] To prevent the ignoring control from becoming a breeding ground for fraud, the weight value before the start of movement may be stored and compared with the weight value after the end of movement (when stationary), and the presence or absence of product insertions and removals during movement (between the start and end of movement) may be monitored. This monitoring may be performed by the mobile terminal 60 or the cart 70. If the weight value increases during movement, the mobile terminal 60 may display a message such as, "Was the product registered correctly?". If the weight value increases during movement and no product registration (or increase in quantity) occurred during movement, the mobile terminal 60 may display a message such as, "Registration was not performed correctly. Please register again." or may set a confirmation flag in the transaction information for the transaction. The mobile terminal 60 may also instruct the user to register products while stationary during movement. For example, the mobile terminal 60 may display a message such as, "The cart is moving. Please stop the cart before registering products." Furthermore, if the weight value decreases during movement, the mobile terminal 60 may display a message such as, "Did you successfully cancel the item?" Furthermore, if the weight value decreases during movement and there is no cancellation (or quantity decrease) during movement, the mobile terminal 60 may display a message such as, "The cancellation was not successful, please cancel again," or may set a confirmation required flag in the transaction information of the transaction. Furthermore, the mobile terminal 60 may instruct the user to cancel while stationary while moving. For example, the mobile terminal 60 may display a message such as, "The cart is moving. Please stop the cart before canceling the item" while moving.

[0248] (10) Related to (9) above, the weight value may also change when the contents of the shopping cart are being rearranged (such as by changing the position of each item in the cart) or checked (such as by checking whether or not a purchase has been made). To prevent rearranging the contents of the shopping cart from being judged as an insertion of a product, buttons related to rearranging the cart (such as a start cart rearrangement button and an end cart rearrangement button) may be provided on the screen of the mobile terminal 60 (for example, a registration screen), and the customer may be prompted to rearrange the cart while declaring that they are rearranging the cart (between the operation of the start cart rearrangement button and the end cart rearrangement button). The mobile terminal 60 executes ignore control while declaring that they are rearranging the cart. Also, as in the case of movement, the weight value before the start of rearranging the cart (when the start cart rearrangement button is operated) may be stored and compared with the weight value after the end of rearranging the cart (when the end cart rearrangement button is operated) to monitor for any unauthorized insertion of products while declaring that they are rearranging the cart.

[0249] (11) In the above embodiment, an example has been described in which the device identification information (e.g., Bluetooth address) of each cart 70 is obtained from a beacon, and an example has been described in which the device identification information of each cart 70 is obtained from a two-dimensional code 78 affixed to each cart 70. However, the device identification information of each cart 70 may be obtained by other methods. For example, an NFC tag (reference numeral 79 in FIG. 1 ) may be affixed to each cart, and the device identification information of each cart 70 may be obtained from the NFC tag 79. The NFC tag 79 includes a storage unit that stores the device identification information (connection information) of the cart 70 (the cart 70 to which the NFC tag 79 is affixed) and a communication unit that transmits the device identification information stored in the storage unit to an external device (specifically, the mobile terminal 60).

[0250] (12) The cart 70 may be connectable to a network (eg, LAN 19) via, for example, a wireless LAN.

[0251] (13) In the above embodiment, the mobile terminal 60 is described as being owned by the customer, but it may also be a terminal (rental terminal) provided by the store. The mobile terminal 60 that is a rental terminal is provided as a dedicated terminal in which only application A can be executed. When the mobile terminal 60 is a rental terminal, the menu screen (FIG. 3(B)) is displayed from the beginning.

[0252] Furthermore, the mobile terminal 60 serving as the rental terminal may not be separate from the cart 70, but may be part of the cart 70 (the cart 70 may be equipped with the mobile terminal 60). When the mobile terminal 60 serving as the rental terminal is part of the cart 70, the mobile terminal 60 and the cart 70 may be connected from the beginning.

[0253] (14) The state of establishing communication between the mobile terminal 60 and the cart 70 using Bluetooth has been expressed as pairing, but this is not limited to encrypted communication and may be unencrypted communication. It may also be so-called bonding, in which a key exchange protocol for encryption is executed and the key is stored for communication. In other words, in this application, pairing refers to a state in which Bluetooth communication is established, and the detailed form of this communication is not important.

[0254] (15) Some or all of the functions (input / output, storage, processing (including judgment)) of each device (e.g., transaction status management device 40, settlement device 50, registered settlement device 51, registered settlement device 52, registered settlement device 53, mobile terminal 60, etc.) may be realized by a device other than the device described as the entity that executes the function. For example, each device may function as a so-called thin client specialized for input / output interfaces, etc. As an example, a cloud server (which may be the same as cloud server 20 or another cloud server) may execute a program for controlling the operation of each device, and each device may display a screen using a browsing function, etc.

[0255] As an example, the cloud server 20 may control the display of the screen (FIGS. 3 to 7, etc.) and the operation (FIG. 17, etc.) of the mobile terminal 60. That is, a program (app A) that controls the operation of the mobile terminal 60 related to service A may run on the CPU of the mobile terminal 60 or on the CPU of the cloud server 20. In other words, the app A may be a web application used with a browser. The cloud server 20 (a program of the cloud server 20) may receive operation information on the mobile terminal 60 from the mobile terminal 60 and determine whether a scan registration or the like has occurred within a predetermined time since the product was inserted, as a determination (determination of fraud, etc.) related to the control (monitoring of fraud, etc.) of FIG. 7(A) (or may control a notification by the mobile terminal 60 depending on the determination result). The same applies to the determination, etc. related to each control of FIGS. 7(B) to 16(B).

[0256] In other words, the cloud server 20 includes an operation information receiving means for receiving operation information for a product registration operation, a product quantity change operation, or a product cancellation operation from the mobile terminal 60, a recognition information receiving means for receiving recognition information regarding putting a product into a basket or removing a product from the basket from the mobile terminal 60, a judgment means for judging whether the operation information received by the operation information receiving means is consistent with the recognition information received by the recognition information receiving means, and a notification control information sending means for sending notification control information to the mobile terminal 60 to notify the mobile terminal 60 of information corresponding to a mismatch between the operation information and the recognition information, and the notification control information sending means may send the notification control information to the mobile terminal 60 after a predetermined condition is met.

[0257] <Summary of the embodiment> [Technical field] The present invention relates to a program, a mobile terminal, a system, a server, and a notification method. [Background technology] There is known a self-service terminal equipped with a scale that issues an error when an item is placed in a bag without being scanned (see, for example, Patent Document 1). Also, in a system in which customers register items themselves in a product display area using a shopping cart, a technology is known in which a scale is provided in the shopping cart to detect fraudulent placement of items in the shopping cart. [Prior art document] [Patent documents] [Patent Document 1] JP 2010-238264 A [Summary of the Invention] [Problem to be solved by the invention] However, there is room for improvement in systems that allow customers to register products themselves in product display areas. The present invention has been made in consideration of these circumstances, and aims to provide technology that enables more suitable implementation of a system that allows customers to register products themselves in product display areas. [Means for solving the problem]

[0258] (1) One aspect of the solution to the above-mentioned problem is a program for causing a mobile terminal (e.g., mobile terminal 60) operated when securing an item in a shopping cart at a sales floor to function as a computer, the program including: an operation reception means for receiving an operation to register an item to be purchased, an operation to change the quantity of an item to be purchased, or an operation to cancel a purchase of an item; a recognition means for recognizing whether an item is being put into the shopping cart or taken out of the shopping cart (determining whether an item is being put into the shopping cart 70 or taken out of the shopping cart 70); a program for detecting inconsistencies between the operation content received by the operation reception means and the recognition content recognized by the recognition means (determining whether an item is being put into the shopping cart 70 or taken out of the shopping cart 70); For example, the program functions as a notification means for notifying (for example, notification on a small screen such as a small screen for notifying registration, small screen for notifying removal, small screen for notifying insertion, or small screen for notifying cancellation, notification in the registration information display area HR630, or notification by voice) about forgotten registration, forgotten take-out, forgotten insertion, or forgotten cancellation, and the notification means does not notify about a mismatch between the operation content and the recognition content until a predetermined condition is met (for example, until the small screen SG1 is erased while the small screen SG1 is displayed, or until the scan registration screen is displayed while the button registration screen is displayed). According to the program (1), the system for customers to register products themselves can be implemented more effectively. For example, while the small screen SG1, which allows for button registration, changing the purchase quantity, or canceling a purchase, or while the button registration screen is displayed, the system does not notify customers of fraud or operational errors. This makes it less likely that problems will occur, such as being notified that a customer has forgotten to register a product despite intending to do so, and allows the system for customers to register products themselves to be implemented more effectively.

[0259] Note that "the notification means does not notify that the operation content and the recognized content do not match until a predetermined condition is met" may be changed to "the notification means notifies that the operation content and the recognized content do not match after a predetermined condition is met." The same applies to the following (2), (3), (6), (7), (8), and (11).

[0260] (2) The program described in (1) is characterized in that the operation receiving means can receive the quantity change operation or the purchase cancellation operation through a specific screen displayed based on a predetermined operation (for example, a small screen SG1 displayed based on the operation of the quantity button BT632, or a small screen SG2 displayed based on the operation of a product button), and the notification means does not notify that the operation content of the quantity change operation or the purchase cancellation operation does not match the recognized content, at least while the screen is displayed. The program (2) can be used to more effectively implement a system in which customers can register products themselves. For example, it can also be used effectively in a system that accepts operations to change the quantity or cancel a purchase.

[0261] (3) The program described in (1) is characterized in that the operation receiving means can receive the registration operation by operating a product button located on a specific screen (for example, a button registration screen displayed based on the operation of button registration button BT623) displayed based on a predetermined operation, and the notification means does not notify that the operation content of the registration operation does not match the recognition content, at least while the screen is displayed. The program (3) can be used to more effectively implement a system in which customers can register products themselves. For example, it can be used effectively in a system in which products are registered by operating a product button.

[0262] (4) The program described in (1) functions as an acquisition means for acquiring weighing information from an external device (e.g., a cart 70) equipped with a weighing unit on which a basket is placed, and the recognition means recognizes the putting of a product into the basket or the removal of a product from the basket based on the weighing information acquired by the acquisition means. According to the program (4), a system in which customers themselves register products based on the weighing information can be more suitably implemented.

[0263] (5) The program described in (1) is characterized in that it functions as an imaging means for capturing images of the inside of a basket (for example, the inside of a shopping basket placed on the loading section 71 of the cart 70), and the recognition means recognizes the addition of a product to the basket or the removal of a product from the basket based on the image captured by the imaging means. According to the program (5), it is possible to more suitably implement a system in which customers themselves register products based on captured images (image recognition).

[0264] (6) One aspect for solving the above-mentioned problem is a mobile terminal (e.g., mobile terminal 60) that is operated when securing a product in a cart at a sales floor, and that is equipped with an operation reception means that receives an operation to register a product to be purchased, an operation to change the quantity of a product to be purchased, or an operation to cancel a product purchase, a recognition means that recognizes the addition of a product to the cart or the removal of a product from the cart, and a notification means that notifies when the operation content received by the operation reception means does not match the recognition content recognized by the recognition means, and is characterized in that the notification means does not notify when the operation content does not match the recognition content until a predetermined condition is met. The mobile terminal (6) can more effectively implement a system in which customers can register their own products, similar to the program (1).

[0265] (7) One aspect for solving the above-mentioned problem is a system (e.g., sales system 1) including a mobile terminal (e.g., mobile terminal 60) that is operated when securing a product in a cart at a sales floor, the system comprising: an operation reception unit that receives an operation to register a product to be purchased, an operation to change the quantity of a product to be purchased, or an operation to cancel a product purchase; a recognition unit that recognizes the addition of a product to the cart or the removal of a product from the cart; and a notification unit that notifies when the operation content received by the operation reception unit does not match the recognition content recognized by the recognition unit, and the notification unit does not notify when the operation content does not match the recognition content until a predetermined condition is met. According to the system (7), similar to the program (1), it is possible to more effectively implement a system in which customers themselves register their products.

[0266] (8) One aspect for solving the above-mentioned problem is a program for causing a system (e.g., sales system 1) including a mobile terminal (e.g., mobile terminal 60) operated when securing a product in a cart at a sales floor to function as a computer, the program causing the computer to function as an operation reception means for receiving an operation to register a product to be purchased, an operation to change the quantity of a product to be purchased, or an operation to cancel a product purchase, a recognition means for recognizing the addition of a product to the cart or the removal of a product from the cart, and a notification means for notifying when the operation content received by the operation reception means does not match the recognition content recognized by the recognition means, and the notification means does not notify when the operation content does not match the recognition content until a predetermined condition is met. According to the program (8), similar to the program (1), it is possible to more effectively implement a system in which customers themselves register their products.

[0267] (9) One aspect for solving the above-mentioned problem is a server (e.g., cloud server 20) capable of communicating with a mobile terminal (e.g., mobile terminal 60) operated when securing a product in a cart at a sales floor, the server comprising: operation information receiving means for receiving operation information for a product registration operation, a product quantity change operation, or a product cancellation operation from the mobile terminal; recognition information receiving means for receiving recognition information from the mobile terminal regarding putting a product into the cart or removing a product from the cart; judgment means for judging whether the operation information received by the operation information receiving means and the recognition information received by the recognition information receiving means are consistent; and notification control information sending means for sending notification control information to the mobile terminal to notify the mobile terminal of inconsistency between the operation information and the recognition information, wherein the notification control information sending means sends the notification control information to the mobile terminal after a predetermined condition is met. The server (9) can more effectively implement a system in which customers can register their own products, similar to the program (1).

[0268] (10) One aspect for solving the above-mentioned problem is a program for causing a server (e.g., cloud server 20) capable of communicating with a mobile terminal (e.g., mobile terminal 60) operated when securing a product in a cart at a sales floor to function as a computer, the program causing the computer to function as an operation information receiving means for receiving operation information for a product registration operation, a product quantity change operation, or a product cancellation operation from the mobile terminal, a recognition information receiving means for receiving recognition information from the mobile terminal regarding putting a product into the cart or removing a product from the cart, a judgment means for judging whether the operation information received by the operation information receiving means is consistent with the recognition information received by the recognition information receiving means, and a notification control information sending means for sending notification control information to the mobile terminal to notify the mobile terminal of inconsistency between the operation information and the recognition information, and the notification control information sending means sends the notification control information to the mobile terminal after a predetermined condition is met. According to the program (10), similar to the program (1), it is possible to more effectively implement a system in which customers themselves register their products.

[0269] (11) One aspect for solving the above-mentioned problem is a notification method using a mobile terminal operated when securing a product in a shopping cart at a sales floor, the notification method comprising an operation reception step for receiving an operation to register a product to be purchased, an operation to change the quantity of a product to be purchased, or an operation to cancel a product purchase, a recognition step for recognizing whether a product has been put into the shopping cart or removed from the shopping cart, and a notification step for notifying that the operation content received by the operation reception step does not match the recognition content recognized by the recognition step, wherein the notification step is characterized in that the notification method does not notify that the operation content does not match the recognition content until a predetermined condition is met. According to the notification method (11), similar to the program (1), it is possible to more suitably implement a system in which customers themselves register their products.

[0270] Note that a program for realizing the functions of each of the above-described devices (e.g., cloud server 20, transaction status management device 40, settlement device 50, registration and settlement device 51, registration and settlement device 52, registration and settlement device 53, mobile terminal 60, etc.) may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be loaded into a computer system and executed to perform processing of each of the above devices. 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 OS and peripheral devices. The term "computer system" may also include multiple computer devices connected via a network, including communication lines such as the Internet, WAN, LAN, and dedicated line. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. In this way, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The recording medium also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the recording medium of the distribution server may be different from the program code in a format executable by the terminal device. In other words, the format in which the program is stored on the distribution server is not important as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, each downloaded at a different time and then combined on the terminal device, or each part 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 for implementing 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]

[0271] 1...Sales system 10...Head office server 20...Cloud server 30...Store controller 40...Transaction status management device 50...Payment device 51...Registration and payment device 52...Registration and payment device 53...Registration and payment device 60...Mobile terminal 70...Cart

Claims

1. A program for causing a mobile terminal operated when securing an item in a shopping cart at a sales floor to function as a computer, The computer operation accepting means for accepting an operation to register a product to be purchased, an operation to change the quantity of the product to be purchased, or an operation to cancel the purchase of a product; recognition means for recognizing whether a commodity is put into the basket or whether a commodity is removed from the basket; a notification means for notifying that the operation content received by the operation receiving means does not match the recognition content recognized by the recognition means; It functions as The notification means A program that does not notify the user that the operation content and the recognized content do not match until a predetermined condition is met.

2. The operation receiving means The quantity change operation or the purchase cancellation operation can be accepted via a specific screen that is displayed based on a predetermined operation, The notification means 2. The program according to claim 1, wherein the program does not notify the user that the operation content of the quantity change operation or the purchase cancellation operation does not match the recognized content at least while the screen is displayed.

3. The operation receiving means The registration operation can be accepted by operating a product button arranged on a specific screen that is displayed based on a predetermined operation, The notification means 2. The program according to claim 1, wherein the program does not notify the user that the operation content of the registration operation does not match the recognized content at least while the screen is displayed.

4. An acquisition means for acquiring weighing information from an external device having a weighing unit on which a basket is placed. It functions as The recognition means 2. The program according to claim 1, wherein the program recognizes whether an item is being put into the basket or taken out of the basket based on the weighing information acquired by the acquisition means.

5. Imaging means for capturing images of the inside of the car It functions as The recognition means 2. The program according to claim 1, wherein the program recognizes whether an item is being put into the basket or taken out of the basket based on the image captured by the imaging means.

6. A mobile terminal that is operated when securing a product in a cart at a sales floor, an operation receiving means for receiving an operation to register a product to be purchased, an operation to change the quantity of a product to be purchased, or an operation to cancel a product purchase; recognition means for recognizing whether a commodity is put into the basket or whether a commodity is removed from the basket; a notification means for notifying that the operation content received by the operation receiving means does not match the recognition content recognized by the recognition means; Equipped with The notification means A portable terminal characterized in that it does not notify the fact that the operation content and the recognized content do not match until a predetermined condition is met.

7. A system including a mobile terminal operated when securing a product in a cart at a sales floor, an operation receiving unit that receives an operation to register a product to be purchased, an operation to change the quantity of a product to be purchased, or an operation to cancel a product purchase; a recognition unit that recognizes whether a product is put into a basket or taken out of the basket; a notification unit that notifies that the operation content accepted by the operation acceptance unit does not match the recognition content recognized by the recognition unit; Equipped with The notification unit A system characterized in that it does not notify the user that the operation content and the recognized content do not match until a predetermined condition is met.

8. A program for causing a system including a mobile terminal operated when securing an item in a cart at a sales floor to function as a computer, The computer operation accepting means for accepting an operation to register a product to be purchased, an operation to change the quantity of the product to be purchased, or an operation to cancel the purchase of a product; recognition means for recognizing whether a commodity is put into the basket or whether a commodity is removed from the basket; a notification means for notifying that the operation content received by the operation receiving means does not match the recognition content recognized by the recognition means; It functions as The notification means A program that does not notify the user that the operation content and the recognized content do not match until a predetermined condition is met.

9. A server capable of communicating with a mobile terminal operated when securing an item in a cart at a sales floor, an operation information receiving means for receiving operation information of a product registration operation, a product quantity change operation, or a product cancellation operation from the mobile terminal; recognition information receiving means for receiving, from the mobile terminal, recognition information relating to putting a commodity into the basket or removing a commodity from the basket; a determination means for determining whether the operation information received by the operation information receiving means and the recognition information received by the recognition information receiving means are consistent with each other; a notification control information transmitting means for transmitting notification control information to the mobile terminal for notifying the mobile terminal of information corresponding to a mismatch between the operation information and the recognition information; Equipped with The notification control information transmitting means A server that transmits the notification control information to the mobile terminal after a predetermined condition is met.

10. A program for causing a server capable of communicating with a mobile terminal operated when securing an item in a shopping cart at a sales floor to function as a computer, The computer operation information receiving means for receiving operation information of a product registration operation, a product quantity change operation, or a product cancellation operation from the mobile terminal; recognition information receiving means for receiving, from the mobile terminal, recognition information relating to putting a commodity into the basket or removing a commodity from the basket; a determination means for determining whether the operation information received by the operation information receiving means matches the recognition information received by the recognition information receiving means; a notification control information transmitting means for transmitting notification control information to the mobile terminal for notifying the mobile terminal of information corresponding to the inconsistency between the operation information and the recognition information; It functions as The notification control information transmitting means A program for transmitting the notification control information to the mobile terminal after a predetermined condition is met.

11. A notification method using a mobile terminal operated when securing a product in a cart at a sales floor, an operation receiving step of receiving an operation to register a product to be purchased, an operation to change the quantity of the product to be purchased, or an operation to cancel the purchase of the product; a recognition step of recognizing whether a product is put into a basket or removed from the basket; a notification step of notifying that the operation content received in the operation receiving step does not match the recognized content recognized in the recognition step; and The notification step includes: A notification method, characterized in that a notification is not given about the inconsistency between the operation content and the recognized content until a predetermined condition is met.

Images