Program, portable terminal, system, server and notification method

Abstract

To more preferably implement a system allowing a customer himself / herself to register a commodity.SOLUTION: A program for allowing a portable terminal operated in putting a commodity in a basket in a selling area to function as a computer, allows the computer to function as display means for displaying a commodity registration screen, registration means for registering a commodity, and notification means for notifying of fraudulent putting of the commodity into the basket. The display means can display another screen different from the commodity registration screen, and the notification means notifies of the fraudulent putting when the display means displays another screen in place of the commodity registration screen, and then displays the commodity registration screen in place of another screen.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 aims 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 problem is a program for causing a mobile terminal operated when adding products to a cart in a sales area to function as a computer, and for causing the computer to function as a display means for displaying a product registration screen, a registration means for registering products, and a notification means for notifying of the fraudulent addition of products to the cart, wherein the display means is capable of displaying a screen different from the product registration screen, and the notification means notifies of the fraudulent addition after the display means changes from a state in which it has displayed the other screen instead of the product registration screen to a state in which it displays the product registration screen instead of the other screen. [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. 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, such as the cloud server 20) and store (install) it in a storage unit. The mobile terminal 60 may use App A to display various screens and execute various processes 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 is equipped with 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. For example, the mobile terminal 60 can manage the time elapsed from the timing of displaying (starting displaying) a certain screen (including a small screen), the time elapsed from the timing of erasing a certain screen (including a small screen), and the timing of an operation to register a product. The mobile terminal 60 can also manage the time elapsed from a timing based on information received from the cart 70 (for example, the timing of adding a product to the shopping cart, or the timing of removing a product from the shopping cart).

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

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

[0021] 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 actions, connects to the cart 70 using the acquired connection information, and becomes capable of communication (Bluetooth communication) with the cart 70.

[0022] 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) of the cart 70, the mobile terminal 60 acquires an image captured by the imaging unit 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.

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

[0024] The mobile terminal 60 may store, in the storage unit, for example, the weighing information received from the cart 70 (the last received weighing value (the most recent (previous) weighing value), the weight of the container (the container weight), etc.).

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

[0026] The mobile terminal 60 can monitor for fraud or mistakes during shopping (can determine whether fraud or mistakes have occurred) by image recognition of captured images. For example, the mobile terminal 60 can monitor whether an unregistered product has been added to the cart 70 or whether a registered product has not been added to the cart 70.

[0027] If fraud or the like (fraud, mistake) occurs, the mobile terminal 60 notifies the user of the fraud or the like. Furthermore, if fraud or the like occurs, the mobile terminal 60 may set information indicating that the transaction requires confirmation (for example, a confirmation flag) in the transaction information of the transaction in which fraud or the like occurred, and may take necessary measures (for example, product registration, cancellation, etc.) until the settlement of the transaction is completed (for example, in the settlement device 50).

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

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

[0030] 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 device 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 is a contact terminal and is detachable from a power supply cable (not shown) or an adjacent cart 70 (for example, by connecting the carts 70 in order starting with the leading cart 70 connected to a single power supply unit, multiple carts 70 from the leading cart 70 to the rearmost cart 70 can be charged by a single power supply unit). 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, to the boards in the board storage section 72). The battery 76 is a power supply section (power source) for the cart 70.

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

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

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

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

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

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

[0037] The cart 70 may also include a timing unit (timing function). That is, like the mobile terminal 60, the cart 70 may use the timing unit to manage the current time, the amount of time elapsed since a certain point in time, and the amount of time remaining until a certain point in time. For example, the cart 70 may manage the amount of time elapsed since a product was added to the shopping cart or the amount of time elapsed since a product was removed from the shopping cart. The cart 70 may also manage the amount of time elapsed since a timing based on information received from the mobile terminal 60 (for example, the timing of display (start of display) or erasure of a certain screen (including a small screen), or the timing of an operation on the mobile terminal 60).

[0038] (Tare, tare) 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.

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

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

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

[0042] (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 that a product or the like has been added to the cart 70 when the weight value received from the cart 70 has increased (or when the mobile terminal 60 receives an increase in the weight value from the cart 70, or when the mobile terminal 60 receives a notification from the cart 70 that a weight has increased).

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

[0044] (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 that a product or the like has been removed from the cart 70 when the weight value received from the cart 70 has decreased (or when the mobile terminal 60 receives the amount of decrease in the weight value from the cart 70, or when the mobile terminal 60 receives a notification from the cart 70 that a weight decrease has occurred).

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

[0046] (Product not registered + product inserted (weight value increased)) The mobile terminal 60 determines whether an unregistered product has been added. For example, if no product is registered and a 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 a 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.

[0047] When the mobile terminal 60 determines that an unregistered product has been added to the cart 70, it may notify the user (for example, by displaying a message on the screen or by voice) that an unregistered product has been added to the cart 70. For example, the mobile terminal 60 may display a message such as "Have you forgotten to register the product?" or a message such as "Please register the product you have added to your shopping cart." Furthermore, the mobile terminal 60 may display (pop-up display) a small screen (for example, a small screen SG1 (described later) or a small screen SG2 (described later)) that notifies the user that the product has been forgotten to be registered.

[0048] 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 to check if registration has been forgotten) in the transaction information for the transaction, instead of or in addition to the notification described above.

[0049] 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. 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 it has determined that an unregistered product has been added).

[0050] It is also possible to store weight information for each product as verification information, and check whether the registered product matches the inserted product based on its weight (weight check).

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

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

[0053] When the mobile terminal 60 determines that a registered product has not been added to the cart 70, the mobile terminal 60 may notify the user (for example, by displaying a message on the screen or by voice) that the registered product has not been added to the cart 70. For example, the mobile terminal 60 may display a message such as "Did you forget to add a product to your shopping cart?" or "Please add the registered product to your shopping cart." The mobile terminal 60 may also display a small screen (pop-up display) notifying the user that a product has been forgotten to be added.

[0054] 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 to check if the product has been forgotten to be added) in the transaction information for the transaction, instead of or in addition to the notification described above.

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

[0056] It is also possible to store weight information for each product as verification information, and check whether the registered product matches the inserted product based on its weight (weight check).

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

[0058] (Product cancelled + product not taken out (no decrease in weight)) The mobile terminal 60 determines whether the 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.

[0059] When the mobile terminal 60 determines that the canceled item has not been removed from the cart 70, it may notify the user (for example, by displaying a message on the screen or by voice) that the canceled item has not been removed from the cart 70. For example, the mobile terminal 60 may display a message such as "Did you forget to remove the item from the shopping cart?" or "Please return the canceled item to the shelf." The mobile terminal 60 may also display a small screen (pop-up display) notifying the user that the item has been forgotten to be removed.

[0060] If the mobile terminal 60 determines that the canceled item has not been removed from the cart 70, it may set a confirmation required flag (which may be a confirmation required flag to confirm that the item has not been removed) in the transaction information for the transaction, instead of or in addition to the notification described above.

[0061] 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 an item is canceled. For example, if the cart 70 receives a notification from the mobile terminal 60 that an item has been canceled, but does not detect a weight loss and determine that the item has been removed, the cart 70 may determine that the canceled product has not been removed. 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).

[0062] It is also possible to store weight information for each product as verification information, and check whether the canceled product matches the removed product based on its weight (weight check).

[0063] The same applies to a decrease in the quantity of a registered product. In other words, in the same way as determining whether a canceled product has been taken out, it may be determined whether a product whose quantity has been decreased has been taken out.

[0064] (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 result 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 whether 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 whether an uncancelled product has been removed from the cart 70.

[0065] When the mobile terminal 60 determines that an uncancelled product has been removed from the cart 70, it may notify the user (for example, by displaying a message on the screen or by voice) that the uncancelled product has been removed from the cart 70. For example, the mobile terminal 60 may display a message such as "Did you forget to cancel the product?" or "Please cancel if you want to stop the purchase." The mobile terminal 60 may also display (pop up) a small screen (for example, a small screen SG3 (described later) or a small screen SG4 (described later)) that notifies the user that the product has been forgotten to be canceled.

[0066] When the mobile terminal 60 determines that an uncancelled item has been removed from the cart 70, it may set a confirmation required flag (which may be a confirmation required flag for confirming that the item has been forgotten to be canceled) in the transaction information for the transaction, instead of or in addition to the notification described above.

[0067] 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. If the cart 70 determines that an uncancelled product has been removed, it notifies the mobile terminal 60 of the determination result (information indicating that it has determined that an uncancelled product has been removed).

[0068] It is also possible to store weight information for each product as verification information, and check whether the canceled product matches the removed product based on its weight (weight check).

[0069] The same applies to a decrease in the quantity of a registered product. In other words, in the same way as determining whether a product that has not been canceled has been taken out, it may be determined whether a product whose quantity has not been decreased has been taken out.

[0070] (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 either 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). Note that the main function of the settlement device 50 is settlement, but it also has functions to register products and cancel products. 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.

[0071] (Headquarters Server 10) The head office server 10 is a server that manages the entire sales system 1. The head office server 10 stores, for example, various information (for example, a product master file (product master) and the like).

[0072] The headquarters server 10 also supplies various information (e.g., product master data) 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 storage unit, and a communication unit. The headquarters server 10 may be configured from multiple servers.

[0073] (Cloud Server 20) The cloud server 20 is a server that mainly supports service A. The cloud server 20 stores various information. For example, the cloud server 20 stores a product master. The cloud server 20 also stores transaction information for each mobile terminal 60. The transaction information for a certain mobile terminal 60 is generated when the mobile terminal 60 starts a transaction, and stores registration information for products registered by the mobile terminal 60. The transaction information for a certain mobile terminal 60 may also store the status (processing progress status) of the mobile terminal 60. The status stored in the transaction information includes a registration status (registration status) indicating that product registration is being performed, a settlement declaration status (settlement declaration status) indicating that settlement will proceed, and the like. The cloud server 20 also supplies various information to, for example, the mobile terminal 60 and the settlement device 50. Although not shown in the figure, the cloud server 20 includes at least a CPU, a memory unit, and a communication unit. The cloud server 20 may be composed of multiple servers.

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

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

[0076] (Example of display on mobile terminal 60) 3 to 5 are examples of displays on the mobile terminal 60. Fig. 3(A) to Fig. 3(H) show basic examples of displays from the start of application A to the display of a settlement code display screen (described later). It is assumed that application A is already installed on the mobile terminal 60.

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

[0078] Fig. 3(B) is a menu screen (start screen) that is displayed after application A is launched. For example, when the icon for application A on the initial screen (Fig. 3(A)) is operated, mobile terminal 60 displays a menu screen as 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.

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

[0080] FIG. 3(D) shows a product registration screen (hereinafter simply referred to as the "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 that is displayed first (the registration screen before the registration of one product item) may be referred to as the initial registration screen. The registration screen (initial registration screen) in FIG. 3(D) has a captured image display area HR620 and a registration information display area HR630. 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).

[0081] Fig. 3(E) is a registration screen when the mobile terminal 60 captures the barcode of the first product (whitebait). Fig. 3(F) is a registration screen when the mobile terminal 60 acquires the product code of whitebait from the barcode of Fig. 3(E) and registers whitebait.

[0082] The registration information display area HR630 on the registration screen in Figure 3 (F) displays the registration information for the registered product (whitebait). The quantity button BT632 displays the purchase quantity and is a button that can be operated to change the purchase quantity or cancel the purchase. After registering a product (one item of product), the mobile terminal 60 operably displays a checkout instruction button BT631 (in this example, a button that displays "Proceed to Checkout") that accepts a checkout instruction operation to complete registration and proceed to checkout (payment), and also displays an explanatory image GA637 that explains the checkout instruction button BT631.

[0083] FIG. 3(G) shows a registration screen when the mobile terminal 60 acquires the product code of the second product (oolong tea) from the barcode of the product (oolong tea) and registers the oolong tea.

[0084] Figure 3(H) is the settlement code display screen that is displayed after the checkout instruction button BT631 is pressed. The settlement code display screen in Figure 3(H) displays the settlement code GA641 (described below), a message MS642 that instructs the settlement machine (settlement device 50) to read the settlement code GA641, and an explanatory image GA643 that explains how to read the settlement code GA641 on the settlement machine. The settlement code display screen in Figure 3(H) also displays an operable Return to Shopping button BT649. When the Return to Shopping button BT649 is pressed, the registration screen that was displayed before the checkout instruction button BT631 was pressed is displayed.

[0085] The settlement code GA641 is a two-dimensional code of transaction identification information that identifies the transaction information of the transaction. In other words, the settlement code GA641 displayed by a certain mobile terminal 60 is information for identifying the transaction information of the certain mobile terminal 60 (transaction information of the product registered by the certain mobile terminal 60) from among multiple pieces of transaction information stored in the cloud server 20. The settlement device 50 that reads the settlement code GA641 displayed by a certain mobile terminal 60 acquires (receives) the transaction information of the certain mobile terminal 60 from the cloud server 20. The settlement code GA641 may also be a two-dimensional code of location information (a storage location within the sales system 1, such as a URI (Uniform Resource Identifier)) of the transaction information of the certain mobile terminal 60.

[0086] 4(A) to 4(D) show examples of the display when an incoming call occurs while the registration screen is displayed.

[0087] For example, when there is an incoming call on the registration screen of Fig. 3(F), as shown in Fig. 4(A), the mobile terminal 60 displays an incoming call notification area HR700 on top of the registration screen of Fig. 3(F) and notifies the user of the incoming call in the incoming call notification area HR700. The incoming call notification area HR700 displays "Japan" to indicate that it is a domestic call, the phone number of the incoming call, and displays an accept / reject button BT701 and an answer button BT702 in an operable manner.

[0088] When the Accept / Reject button BT701 is operated in the scene of FIG. 4(A) (or when the call for the incoming call ends without the operation of the Answer button BT702), the mobile terminal 60 erases the incoming call notification area HR700 and displays the registration screen of FIG. 3(F).

[0089] When the answer button BT702 is operated in the scene of Fig. 4(A), the mobile terminal 60 displays a call screen (telephone screen) as shown in Fig. 4(B) instead of the registration screen of Fig. 4(A). In other words, the mobile terminal 60 interrupts the product registration due to the interruption of the call.

[0090] When the call ends from the scene in Fig. 4(B) and no product is added to the cart 70 while the call screen in Fig. 4(B) is displayed (when it is determined that no product is added), the mobile terminal 60 displays the registration screen in Fig. 3(F) instead of the call screen in Fig. 4(B). When the call ends from the scene in Fig. 4(B) and a product is added to the cart 70 while the call screen in Fig. 4(B) is displayed (when it is determined that a product is added), the mobile terminal 60 displays (pops up) a small screen SG1 in front of the registration screen in Fig. 3(F), as shown in Fig. 4(C).

[0091] That is, the mobile terminal 60 can interrupt the display of the registration screen to display a call screen, and if a product is inserted while the call screen is being displayed, the small screen SG1 is displayed on the registration screen after returning from the call screen. Although not related to the call (call screen), the mobile terminal 60 also displays the small screen SG1 on the registration screen even if a product is inserted without being registered while the registration screen is being displayed.

[0092] The small screen SG1 displays a message MS101 for confirming whether the product has been placed in the shopping basket (cart 70), and a Yes button BT102 and a No button BT103 are displayed so that they can be operated.

[0093] It has been explained that the mobile terminal 60 notifies the user of fraud or the like if fraud or the like occurs, and the small screens SG1 and SG2 (described later), message MS710 (described later), and product insertion notification area HR720 (described later) are specific examples of notification of fraud. Also, the small screens SG3 (described later), SG4 (described later), message MS711 (described later), and product insertion notification area HR721 (described later) are specific examples of notification of mistakes.

[0094] When the NO button BT103 on the small screen SG1 is operated in the scene of FIG. 4(C), the mobile terminal 60 erases the small screen SG1 and displays the registration screen of FIG. 3(F).

[0095] When the Yes button BT102 on the small screen SG1 is operated in the scene of Fig. 4(C), the mobile terminal 60 displays a small screen SG2 in place of the small screen SG1 in front of the registration screen of Fig. 3(F), as shown in Fig. 4(D). A message MS201 instructing the user to register the products added to the shopping basket (cart 70) is displayed on the small screen SG2, and the OK button BT202 is displayed so that it can be operated.

[0096] When the OK button BT202 on small screen SG2 is operated in the scene of Fig. 4(D), the mobile terminal 60 clears the small screen SG2 and displays the registration screen of Fig. 3(F). The customer registers the products that they added to the shopping cart during the call on the registration screen (registration screen of Fig. 3(F)) that is displayed after operating the OK button BT202 on small screen SG2. If no products are registered within a predetermined time (for example, 10 seconds) after operating the OK button BT202 (after the registration screen is displayed), the mobile terminal 60 displays small screen SG1 (or small screen SG2) in front of the registration screen.

[0097] As described above, when the mobile terminal 60 is interrupted by a call screen from the registration screen and a product is inserted while the call screen is being displayed (when it is determined that a product has been inserted), it will notify the user of the fraudulent insertion on the registration screen after the call ends (after the call returns).

[0098] In addition, when a product is added while the call screen interrupted by the registration screen is being displayed, the mobile terminal 60 may display the small screen SG2 instead of the small screen SG1 on the registration screen after returning from the call screen. For example, when a product is added to the cart 70 while the call screen of FIG. 4(B) is being displayed (when it is determined that a product has been added), the mobile terminal 60 may display the small screen SG2 instead of the small screen SG1. Subsequently, when the OK button BT202 on the small screen SG2 is operated, the mobile terminal 60 erases the small screen SG2 and displays the registration screen of FIG. 3(F). When a predetermined time (for example, 10 seconds) has elapsed after the OK button BT202 is operated (after the registration screen is displayed), the mobile terminal 60 displays the small screen SG2 (or the small screen SG1). In other words, when a product is added to the cart 70 while the call screen is being displayed, the mobile terminal 60 may display: small screen SG1 (Yes button BT102) → small screen SG2 → registration screen, no product registered within a specified time → small screen SG1 (or small screen SG2), or may display: small screen SG2 → registration screen, no product registered within a specified time → small screen SG2 (or small screen SG1).

[0099] Although not related to calls (call screen), the mobile terminal 60 may display small screen SG2 instead of small screen SG1 on the registration screen, as described above, even if an unregistered product is inserted while the registration screen is displayed.

[0100] Furthermore, the mobile terminal 60 may display a small screen SG5 (described later) in a position (for example, a registration information display area HR630) that does not overlap the captured image display area HR620 of the registration screen, instead of the small screen SG1 or small screen SG2. The small screen SG5 displays a message MS201 similar to that of the small screen SG2, and displays an operable product button (button registration button) without a barcode. In other words, the small screen SG5 is a small screen on which the product button without a barcode is arranged instead of the OK button BT202 of the small screen SG2.

[0101] With the small screen SG5 displayed in the foreground, the mobile terminal 60 can register a product by holding the barcode of the product over the captured image display area HR620, and when the product is registered by holding the barcode over it, the mobile terminal 60 erases the small screen SG5. When the no-barcode product button on the small screen SG5 is operated with the small screen SG5 displayed in the foreground, the mobile terminal 60 displays a small screen SG6 (a small screen that displays operably product buttons (preset buttons) for products without barcodes (for example, vegetables, fruits, fresh fish, prepared foods, etc.)) in front of the captured image display area HR620, and when the product is registered by operating the product button on the small screen SG6, the mobile terminal erases the small screens SG5 and SG6. In addition, when the small screen SG5 is displayed in the foreground and the barcode-less product button on the small screen SG5 is operated, the mobile terminal 60 may display a product button registration area in which the product buttons of each barcode-less product are displayed in an operable manner instead of the captured image display area HR620, and may erase the small screen SG5 when a product is registered by operating the product button in the product button registration area (the product button registration area may be returned to the captured image display area HR620 when the small screen SG5 is erased).

[0102] In other words, rather than simply leaving it up to the customer to operate the OK button BT202 as on the small screen SG2, it is possible to continue to display message MS201 (small screen SG5) (by not accepting any operations other than product registration) until the product is actually registered using the barcode or product button, thereby urging the customer to ensure that the product is registered.

[0103] Although not related to a call (call screen), a no-barcode product button may be displayed in an operable manner on the registration screen so that a product without a barcode can be registered even when there is no call. For example, the no-barcode product button may be displayed in a part (top) of the captured image display area HR620 on the registration screen. When the no-barcode product button on the registration screen is operated, the mobile terminal 60 may display a small screen SG6 in front of the captured image display area HR620, and when a product is registered by operating a product button on the small screen SG6, the small screen SG6 may be erased. Furthermore, when the no-barcode product button on the registration screen is operated, the mobile terminal 60 may display a product button registration area instead of the captured image display area HR620, and when a product is registered by operating a product button in the product button registration area, the mobile terminal 60 may return from the product button registration area to the captured image display area HR620 (a scan button may be displayed on the registration screen together with the no-barcode product button, and when the scan button is operated, the product button registration area may be returned to the captured image display area HR620).

[0104] 4(E) to 4(H) show examples of the display when an incoming call occurs while the settlement code display screen is displayed.

[0105] For example, when a call comes in on the settlement code display screen of Figure 3(H), the mobile terminal 60 displays an incoming call notification area HR700 in front of the settlement code display screen of Figure 3(H), as shown in Figure 4(E), and notifies the user of the incoming call in the incoming call notification area HR700.

[0106] When the Accept / Reject button BT701 is operated in the scene of Figure 4(E) (or when the call for the incoming call ends without the operation of the Answer button BT702), the mobile terminal 60 erases the incoming call notification area HR700 and displays the settlement code display screen of Figure 3(H).

[0107] When the answer button BT702 is operated in the scene of Fig. 4(E), the mobile terminal 60 displays a call screen as shown in Fig. 4(B) instead of the settlement code display screen of Fig. 4(E). In other words, the mobile terminal 60 interrupts the display of the settlement code GA641 due to the interruption of the call.

[0108] When the call ends from the scene in Fig. 4(B) and no product is added to the cart 70 while the call screen in Fig. 4(B) is displayed (when it is determined that no product is added), the mobile terminal 60 displays the payment code display screen in Fig. 3(H) instead of the call screen in Fig. 4(B). When the call ends from the scene in Fig. 4(B) and a product is added to the cart 70 while the call screen in Fig. 4(B) is displayed (when it is determined that a product is added), the mobile terminal 60 displays a small screen SG1 in front of the payment code display screen in Fig. 3(H), as shown in Fig. 4(F).

[0109] In other words, the mobile terminal 60 can interrupt the display of the settlement code display screen to display a call screen, and if a product is inserted while the call screen is being displayed, a small screen SG1 is displayed on the settlement code display screen after returning from the call screen.

[0110] When the No button BT103 on the small screen SG1 is operated in the scene of FIG. 4(F), the mobile terminal 60 clears the small screen SG1 and displays the settlement code display screen of FIG. 3(H).

[0111] When the Yes button BT102 on the small screen SG1 is operated in the scene of Figure 4(F), the mobile terminal 60 displays the small screen SG2 in front of the registration screen of Figure 3(G) (the registration screen before the operation of the checkout instruction button BT631), as shown in Figure 4(G).

[0112] When the OK button BT202 on small screen SG2 is operated in the scene of Fig. 4(G), the mobile terminal 60 clears the small screen SG2 and displays the registration screen of Fig. 3(G). The customer registers the products that they added to the shopping cart during the call on the registration screen (registration screen of Fig. 3(G)) that is displayed after operating the OK button BT202 on small screen SG2. If no products are registered within a predetermined time (for example, 10 seconds) after operating the OK button BT202 (after the registration screen is displayed), the mobile terminal 60 displays small screen SG1 (or small screen SG2) in front of the registration screen.

[0113] As described above, when the mobile terminal 60 is interrupted by a call screen from the settlement code display screen and a product is inserted while the call screen is being displayed (when it is determined that a product has been inserted), it will notify the user of the fraudulent insertion on the settlement code display screen (or registration screen) after the call ends (returns).

[0114] Note that, when a product is inserted while the call screen interrupted by the checkout code display screen is being displayed, the mobile terminal 60 may display the small screen SG1 on the registration screen instead of the checkout code display screen. For example, when a product is inserted into the cart 70 while the call screen of Fig. 4(B) is being displayed (when it is determined that a product has been inserted), the mobile terminal 60 may display the small screen SG1 in front of the registration screen (the registration screen of Fig. 3(G)) as shown in Fig. 5(D).

[0115] Furthermore, the mobile terminal 60 may display a small screen SG2 in place of the small screen SG1 on the registration screen (or the payment code display screen) when a product is inserted while a call screen interrupted by the payment code display screen is being displayed. For example, when a product is inserted into the cart 70 while the call screen of FIG. 4(B) is being displayed (when it is determined that a product has been inserted), the mobile terminal 60 may display the small screen SG2 in front of the registration screen (the registration screen of FIG. 3(G)) as shown in FIG. 4(G) (or display the small screen SG2 in front of the payment code display screen as shown in FIG. 4(H)). Subsequently, when the OK button BT202 on the small screen SG2 is operated, the mobile terminal 60 erases the small screen SG2 and displays the registration screen of FIG. 3(G). If no product is registered within a predetermined time (for example, 10 seconds) after the OK button BT202 is operated (after the registration screen is displayed), the mobile terminal 60 may display the small screen SG2 (or the small screen SG1) in front of the registration screen.

[0116] Figures 5(A) to 5(D) show other display examples. When the mobile terminal 60 detects that a product has been added to the shopping basket (cart 70) while the call screen is being displayed, it may display a message MS710 (for example, a caption) on the call screen to indicate that the product has been added, as shown in Figure 5(A). After the call ends, the customer operates the small screen SG1 (or small screen SG2) that is displayed in front of the registration screen or the payment code display screen.

[0117] Although not related to the call (call screen), if a product is added to the cart 70 while the payment code display screen of Figure 3(H) is displayed (as with the call screen, product registration is not possible on the payment code display screen, so the product is added without being registered), the mobile terminal 60 will also display a message MS710 (for example, a caption) on the payment code display screen to indicate that the addition of the product has been detected, as shown in Figure 5(B).

[0118] That is, as described above, the mobile terminal 60 displays the small screen SG1 (or small screen SG2) if an unregistered product is inserted while the registration screen is displayed, but displays the message MS710 if an unregistered product is inserted while the payment code display screen is displayed. After checking the message MS710, the customer operates the Return to Shopping button BT649 to register the product.

[0119] Alternatively, when a product is added to the cart 70 while the checkout code display screen of Figure 3(H) is being displayed, the mobile terminal 60 may not display the message MS710, but may instead display a product addition notification area HR720 in front of the checkout code display screen, as shown in Figure 5(C), which can accept operations.

[0120] When product insertion notification area HR720 is operated in the scene of Fig. 5(C), mobile terminal 60 displays small screen SG1 or small screen SG2. For example, when product insertion notification area HR720 is operated, mobile terminal 60 may display small screen SG1 in front of the settlement code display screen as shown in Fig. 4(F), or may display small screen SG1 in front of the registration screen (the registration screen before the checkout instruction button BT631 is operated) as shown in Fig. 5(D), or may display small screen SG2 in front of the settlement code display screen as shown in Fig. 4(H), or may display small screen SG2 in front of the registration screen (the registration screen before the checkout instruction button BT631 is operated) as shown in Fig. 4(G).

[0121] Alternatively, when a product is added to the cart 70 while the payment code display screen of FIG. 3(H) is displayed, the mobile terminal 60 may display the small screen SG1 or the small screen SG2 without displaying the message MS710 or the product addition notification area HR720. For example, when a product is added to the cart 70 while the payment code display screen of FIG. 3(H) is displayed, the mobile terminal 60 may display the small screen SG1 in front of the payment code display screen as shown in FIG. 4(F), or may display the small screen SG2 in front of the payment code display screen as shown in FIG. 4(H), or may display the small screen SG1 in front of the registration screen (the registration screen before the checkout instruction button BT631 is operated) as shown in FIG. 5(D), or may display the small screen SG2 in front of the registration screen (the registration screen before the checkout instruction button BT631 is operated) as shown in FIG. 4(G). FIGS. 5(E) to 5(H) will be described later.

[0122] (Example of control related to reporting fraud, etc.) As an example, we will explain control examples (control example 1A, control example 1B, control example 2A, control example 2B, control example 3A, control example 3B, control example 4B) that notify of fraudulent insertion (insertion of product while the call screen is displayed) on the registration screen after returning from the call screen.

[0123] (Control Example 1A) In control example 1A, the cart 70 transmits the increased weight value to the mobile terminal 60 whether the mobile terminal 60 is displaying the registration screen or the call screen. The cart 70 is not concerned with whether the mobile terminal 60 is displaying the registration screen. The mobile terminal 60 receives and stores the weight value transmitted from the cart 70 whether the registration screen or the call screen is being displayed. In control example 1A, the mobile terminal 60 manages (stores) an unauthorized insertion flag. Note that control example 1A does not assume a weight decrease (product removal) while the call screen is being displayed.

[0124] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) If the fraudulent insertion flag has not been cleared, the mobile terminal 60 clears it (sets it to "0" which is the OFF state). (3) If there is an increase in weight (item insertion) while the call screen is displayed, the cart 70 transmits the weight value after the increase to the mobile terminal 60. If there is an increase in weight multiple times while the call screen is displayed, the cart 70 transmits the weight value after the increase to the mobile terminal 60 each time there is an increase in weight. (4) When the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed, the mobile terminal 60 stores (overwrites) the weight value as the current weight value. When the mobile terminal 60 receives a weight value multiple times while the call screen is displayed, the mobile terminal 60 stores (overwrites) each received weight value as the current weight value. (5) Furthermore, when the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed, the mobile terminal 60 sets the fraudulent insertion flag (sets it to "1", which is the on state). If the fraudulent insertion flag has already been set (when the mobile terminal 60 receives another weight value while the call screen is displayed), the mobile terminal 60 maintains the set state. (6) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (7) The mobile terminal 60 determines whether or not an unauthorized insertion has occurred. Specifically, the mobile terminal 60 determines that an unauthorized insertion has not occurred if the unauthorized insertion flag is not set (if there is no increase in weight while the call screen is displayed), and determines that an unauthorized insertion has occurred if the unauthorized insertion flag is set (if there is an increase in weight while the call screen is displayed). (8) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion. (9) The mobile terminal 60 clears the fraudulent insertion flag.

[0125] The mobile terminal 60 may determine whether or not an unauthorized insertion has occurred before returning to the registration screen (while the call screen is being displayed). For example, when the mobile terminal 60 receives a weight value from the cart 70 for the first time while the call screen is being displayed, the mobile terminal 60 may store (overwrite) the weight value as the current weight value and determine whether or not an unauthorized insertion has occurred (determine that an unauthorized insertion has occurred). In this case, the unauthorized insertion flag may not be provided.

[0126] (Control Example 1B) In Control Example 1A, weight loss (product removal) is not assumed, but in Control Example 1B, weight loss (product removal) is assumed.

[0127] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) The mobile terminal 60 stores (saves) the current measurement value (the measurement value immediately before switching to the call screen) as the "reference measurement value." (3) If there is an increase or decrease in weight (item insertion / removal) while the call screen is displayed, the cart 70 transmits the measured value after the increase or decrease to the mobile terminal 60. If there is an increase or decrease in weight multiple times while the call screen is displayed, the cart 70 transmits the measured value after the increase or decrease to the mobile terminal 60 each time there is an increase or decrease in weight. (4) When the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed, the mobile terminal 60 stores (overwrites) the weight value as the current weight value. When the mobile terminal 60 receives a weight value multiple times while the call screen is displayed, the mobile terminal 60 stores (overwrites) each received weight value as the current weight value. (5) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (6) The mobile terminal 60 determines whether or not an unauthorized insertion has occurred. Specifically, the mobile terminal 60 determines that no unauthorized insertion has occurred if the "reference weight value" is not less than the "current weight value" (if the weight has not increased compared to before the call screen was displayed), and determines that an unauthorized insertion has occurred if the "reference weight value" is less than the "current weight value" (if the weight has increased compared to before the call screen was displayed). (7) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion.

[0128] The mobile terminal 60 may determine whether or not fraudulent insertion has occurred based on whether or not the difference between the "reference weight value" and the "current weight value" is equal to or greater than a threshold value.

[0129] Furthermore, if the "reference weight value" is greater than the "current weight value," the mobile terminal 60 may notify the user about removing the product. In other words, in addition to determining and notifying the user that a product added to the shopping cart while the call screen is displayed has been forgotten to be registered, the mobile terminal 60 may also determine and notify the user that a product removed from the shopping cart while the call screen is displayed has been forgotten to be canceled. The same applies to other controls that use the reference weight value (Control Example 2B, Control Example 3B, Control Example 4B).

[0130] For example, if a product is added to the cart 70 while the call screen of Figure 4(B) is displayed (if it is determined that a product has been added), the mobile terminal 60 will display the small screen SG1 in front of the registration screen of Figure 3(F) as shown in Figure 4(C) (or display the small screen SG2 in front of the registration screen of Figure 3(F) as shown in Figure 4(D)) after the call ends, but if a product is removed from the cart 70 while the call screen of Figure 4(B) is displayed (if it is determined that a product has been removed), the mobile terminal 60 will display the small screen SG3 in front of the registration screen of Figure 3(F) as shown in Figure 5(E) (or display the small screen SG4 in front of the registration screen of Figure 3(F) as shown in Figure 5(F)) after the call ends.

[0131] The small screen SG3 in Fig. 5(E) displays a message MS301 confirming whether the product has been removed from the shopping cart, and the Yes button BT302 and No button BT303 are displayed so that they can be operated. When the No button BT303 on the small screen SG3 is operated in the scene of Fig. 5(E), the mobile terminal 60 erases the small screen SG3 and displays the registration screen of Fig. 3(F). When the Yes button BT302 on the small screen SG3 is operated in the scene of Fig. 5(E), the mobile terminal 60 displays a small screen SG4 in place of the small screen SG3 in front of the registration screen of Fig. 3(F), as shown in Fig. 5(F).

[0132] The small screen SG4 in Fig. 5(F) displays a message MS401 instructing the customer to cancel the product removed from the shopping cart, and the OK button BT402 is displayed so that it can be operated. When the OK button BT402 on the small screen SG4 is operated in the scene in Fig. 5(F), the mobile terminal 60 clears the small screen SG4 and displays the registration screen in Fig. 3(F). The customer can cancel the product removed from the shopping cart during a call on the registration screen (registration screen in Fig. 3(F)) that is displayed after operating the OK button BT402 on the small screen SG4.

[0133] If a product is added to cart 70 while the checkout code display screen of FIG. 3(H) is displayed, mobile terminal 60 displays message MS710 indicating that the product has been added, as shown in FIG. 5(B) (or product addition notification area HR720, as shown in FIG. 5(C)), but if a product is removed from cart 70 while the checkout code display screen of FIG. 3(H) is displayed, mobile terminal 60 displays message MS711 indicating that the product has been removed, as shown in FIG. 5(G) (or product addition notification area HR721, as shown in FIG. 5(H)). If product addition notification area HR721 is operated in the scene of FIG. 5(H), mobile terminal 60 displays small screen SG3 or small screen SG4.

[0134] (Control Example 2A) In control example 2A, the cart 70 transmits the increased weight value to the mobile terminal 60 whether the mobile terminal 60 is displaying the registration screen or the call screen. The cart 70 is not aware of whether the mobile terminal 60 is displaying the registration screen. The mobile terminal 60 accepts the weight value transmitted from the cart 70 while the registration screen is displayed, but does not accept the weight value transmitted from the cart 70 while the call screen is displayed. In control example 2A, the mobile terminal 60 manages (stores) an unauthorized insertion flag. Note that control example 2A does not assume a weight decrease (product removal) while the call screen is displayed.

[0135] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) The mobile terminal 60 clears the fraudulent insertion flag if it has not been cleared. (3) If the weight increases while the call screen is displayed, the cart 70 transmits the weight value after the increase to the mobile terminal 60. (4) The mobile terminal 60 accepts the weight values ​​sent from the cart 70 while the registration screen is displayed (it sends a receipt confirmation notification to the cart 70, receives the weight values ​​sent from the cart 70, and stores (overwrites) them as the current weight values), but does not accept the weight values ​​while the call screen is displayed (it does not send a receipt confirmation notification to the cart 70, and does not receive the weight values ​​sent from the cart 70). (5) When the cart 70 sends a measurement value to the mobile terminal 60 displaying the registration screen, the cart 70 receives a receipt confirmation notification from the mobile terminal 60 and does not resend the measurement value. However, when the cart 70 sends a measurement value to the mobile terminal 60 displaying the call screen, the cart 70 does not receive a receipt confirmation notification from the mobile terminal 60 and therefore resends the measurement value after a predetermined time (e.g., 3 seconds) has elapsed. (6) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (7) If there is a measurement value to be resent (if the measurement value was sent while the call screen was displayed), the cart 70 transmits (resends) the measurement value to the mobile terminal 60. (8) When the mobile terminal 60 receives a weighing value from the cart 70, it accepts the weighing value (sends a receipt confirmation notification to the cart 70, receives the weighing value sent from the cart 70, and stores (overwrites) it as the current weighing value). (9) Furthermore, when the portable terminal 60 receives a weight value from the cart 70, it sets an unauthorized insertion flag. (10) The mobile terminal 60 determines whether or not a fraudulent insertion has occurred. Specifically, the mobile terminal 60 determines that no fraudulent insertion has occurred if the fraudulent insertion flag is not set, and determines that a fraudulent insertion has occurred if the fraudulent insertion flag is set. (11) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion. (12) The mobile terminal 60 clears the fraudulent insertion flag.

[0136] (Control Example 2B) In Control Example 2A, weight loss (product removal) is not assumed, but in Control Example 2B, weight loss (product removal) is assumed.

[0137] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) The mobile terminal 60 stores (backs up) the current weight value as a "reference weight value." (3) If there is an increase or decrease in weight (item insertion / removal) while the call screen is displayed, the cart 70 transmits the measured value after the increase or decrease to the mobile terminal 60. If there is an increase or decrease in weight multiple times while the call screen is displayed, the cart 70 transmits the measured value after the increase or decrease to the mobile terminal 60 each time there is an increase or decrease in weight. (4) The mobile terminal 60 accepts the weight values ​​sent from the cart 70 while the registration screen is displayed (it sends a receipt confirmation notification to the cart 70, receives the weight values ​​sent from the cart 70, and stores (overwrites) them as the current weight values), but does not accept the weight values ​​while the call screen is displayed (it does not send a receipt confirmation notification to the cart 70, and does not receive the weight values ​​sent from the cart 70). (5) When the cart 70 sends a weight value to the mobile terminal 60 displaying the registration screen, the cart 70 receives a receipt confirmation notice from the mobile terminal 60 and does not resend the weight value. However, when the cart 70 sends a weight value to the mobile terminal 60 displaying the call screen, the cart 70 does not receive a receipt confirmation notice from the mobile terminal 60 and resends the weight value after a predetermined time (e.g., 3 seconds) has elapsed. If there is another weight increase or decrease after the cart 70 sent a weight value to the mobile terminal 60 displaying the call screen, the cart 70 sends the weight value after the weight increase or decrease to the mobile terminal 60 instead of the weight value to be resent (i.e., the latest weight value is the one to be resent). (6) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (7) If there is a measurement value to be resent (if the measurement value was sent while the call screen was displayed), the cart 70 transmits (resends) the measurement value to the mobile terminal 60. (8) When the mobile terminal 60 receives a weighing value from the cart 70, it accepts the weighing value (sends a receipt confirmation notification to the cart 70, receives the weighing value sent from the cart 70, and stores (overwrites) it as the current weighing value). (9) The mobile terminal 60 determines whether or not there has been any fraudulent insertion. Specifically, the mobile terminal 60 determines that there has been no fraudulent insertion if the "reference weight value" is not less than the "current weight value," and determines that there has been fraudulent insertion if the "reference weight value" is less than the "current weight value." (10) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion.

[0138] (Control Example 3A) In control example 3A, when the mobile terminal 60 is displaying a registration screen, the changed (increased) weight value is sent to the mobile terminal 60, but when the call screen is displayed, the changed (increased) weight value is not sent to the mobile terminal 60. In control example 3A, the mobile terminal 60 manages (stores) an unauthorized insertion flag. In control example 3A, the cart 70 manages (stores) a weight increase flag. Note that control example 3A does not anticipate a weight decrease (product removal) while the call screen is displayed.

[0139] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) The mobile terminal 60 clears the fraudulent insertion flag if it has not been cleared. (3) The mobile terminal 60 transmits a screen switching notification from the registration screen to the call screen to the cart 70. The screen switching notification can also be said to be weight value transmission control information that controls the transmission of weight values ​​in the cart 70. (4) When the cart 70 receives a screen change notification from the registration screen to the call screen (i.e., when the display on the mobile terminal 60 changes from the registration screen to the call screen), it clears the weight increase flag if it has not been cleared. (5) The cart 70 sets a weight increase flag if there is an increase in weight while the call screen is displayed (between receiving a notification of screen switching from the registration screen to the call screen and receiving a notification of screen switching from the call screen to the registration screen). If the weight increase flag has already been set (if there is another weight increase while the call screen is displayed), the cart 70 maintains the set state. (6) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (7) The mobile terminal 60 transmits a screen change notification from the call screen to the registration screen to the cart 70. (8) When the cart 70 receives a screen change notification from the call screen to the registration screen (i.e., when the display on the mobile terminal 60 changes from the call screen to the registration screen), if the weight increase flag is set, the cart 70 sends the current weighing value to the mobile terminal 60. (9) The cart 70 clears the weight increase flag. (10) When the mobile terminal 60 receives a weight value from the cart 70, it stores (overwrites) the weight value as the current weight value. (11) Furthermore, when the portable terminal 60 receives a weight value from the cart 70, it sets an unauthorized insertion flag. (12) The mobile terminal 60 determines whether or not a fraudulent insertion has occurred. Specifically, the mobile terminal 60 determines that no fraudulent insertion has occurred if the fraudulent insertion flag is not set, and determines that fraudulent insertion has occurred if the fraudulent insertion flag is set. (13) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion. (14) The mobile terminal 60 clears the fraudulent insertion flag.

[0140] If the mobile terminal 60 receives a weight value after returning to the registration screen, the mobile terminal 60 may store (overwrite) the weight value as the current weight value and determine that an unauthorized insertion has occurred. In this case, the unauthorized insertion flag does not need to be set.

[0141] (Control example 3B) In Control Example 3A, weight loss (product removal) is not assumed, but in Control Example 3B, weight loss (product removal) is assumed.

[0142] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) The mobile terminal 60 stores (backs up) the current weight value as a "reference weight value." (3) The mobile terminal 60 transmits a screen change notification from the registration screen to the call screen to the cart 70. (4) When the cart 70 receives a notification of screen switching from the registration screen to the call screen, the cart 70 clears the weight increase flag if it has not been cleared. (5) If there is a weight increase or decrease while the call screen is displayed, the cart 70 sets the weight increase or decrease flag. If the weight increase or decrease flag has already been set (if there is another weight increase or decrease while the call screen is displayed), the cart 70 maintains the set state. (6) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (7) The mobile terminal 60 transmits a screen change notification from the call screen to the registration screen to the cart 70. (8) When the cart 70 receives a screen change notification from the call screen to the registration screen, if the weight gain / loss flag is set, the cart 70 transmits the current weight value to the mobile terminal 60. (9) The cart 70 clears the weight increase / decrease flag. (10) When the mobile terminal 60 receives a weight value from the cart 70, it stores (overwrites) the weight value as the current weight value. (11) The mobile terminal 60 determines whether or not there has been any fraudulent insertion. Specifically, the mobile terminal 60 determines that there has been no fraudulent insertion if the "reference weight value" is not less than the "current weight value," and determines that there has been fraudulent insertion if the "reference weight value" is less than the "current weight value." (12) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion.

[0143] (Control Example 4B) In control example 3B, the cart 70 transmits the weight value after returning to the registration screen only if the weight value changes (increases or decreases) while the call screen is displayed, but in control example 4B, the cart 70 transmits the weight value after returning to the registration screen even if the weight value does not change while the call screen is displayed. Note that in a configuration in which the current weight value is always transmitted after returning to the registration screen, a flag is not necessary, and therefore there is no control example equivalent to control example 4A.

[0144] (1) The mobile terminal 60 switches from the registration screen to the call screen. (2) The mobile terminal 60 stores (backs up) the current weight value as a "reference weight value." (3) The mobile terminal 60 transmits a screen change notification from the registration screen to the call screen to the cart 70. (4) The cart 70 does not transmit the weight value to the mobile terminal 60 even if the weight increases or decreases while the call screen is displayed. (5) The mobile terminal 60 switches from the call screen to the registration screen (returns to the registration screen). (6) The mobile terminal 60 transmits a screen change notification from the call screen to the registration screen to the cart 70. (7) When the cart 70 receives a screen switching notification from the call screen to the registration screen, the cart 70 transmits the current weight value to the mobile terminal 60. In other words, the cart 70 transmits the weight value to the mobile terminal 60 after returning to the registration screen, regardless of whether the weight value has changed while the call screen is displayed. (8) When the mobile terminal 60 receives a weight value from the cart 70, it stores (overwrites) the weight value as the current weight value. (9) The mobile terminal 60 determines whether or not there has been any fraudulent insertion. Specifically, the mobile terminal 60 determines that there has been no fraudulent insertion if the "reference weight value" is not less than the "current weight value," and determines that there has been fraudulent insertion if the "reference weight value" is less than the "current weight value." (10) If the mobile terminal 60 determines that an illegal insertion has occurred, it notifies the user of the illegal insertion.

[0145] In Control Example 1A to Control Example 4B, we have explained the control when a measurement value changes on a call screen in response to an incoming call that was received while the registration screen was being displayed, but the control is similar when a measurement value changes on a call screen in response to an incoming call that was received while the settlement code display screen was being displayed.

[0146] In addition, the mobile terminal 60 immediately reports if the measurement value changes on the settlement code display screen (for example, Figures 5(B) and 5(C)), but if the measurement value changes on the settlement code display screen, the mobile terminal 60 can immediately receive the measurement value, determine whether or not an unauthorized insertion has occurred, and report the same, as in configuration example 1A and configuration example 1B, for example.

[0147] In the above "Example of control related to reporting fraud, etc.", an example using a measurement value was explained, but the same applies to cases using captured images (image recognition). Also, while the example explained was a case of forgetting to register (inserting without registration), the same applies to cases of forgetting to remove (cancelled but not removed), forgetting to cancel (uncancelled but removed), and forgetting to insert (not registered but inserted).

[0148] (Control by other devices, etc.) The cloud server 20 or the cart 70 may store the weight value. The cloud server 20 or the cart 70 may determine whether or not an unauthorized insertion has occurred. In a configuration in which the cloud server 20 stores the weight value, the mobile terminal 60 transmits the weight value received from the cart 70 to the cloud server 20 each time it receives a weight value from the cart 70, and the cloud server 20 stores the weight value received from the mobile terminal 60 in a memory unit each time it receives a weight value from the mobile terminal 60.

[0149] (Cloud server 20 stores the measured value, and mobile terminal 60 determines whether or not there is any fraudulent input.) In the case of the configuration using the unauthorized input flag (control example 1A, control example 2A, control example 3A), for example, the following may be performed. (1) When switching from the registration screen to the call screen, the mobile terminal 60 clears the fraudulent input flag if it has not been cleared. (2) When the mobile terminal 60 receives a weighing value from the cart 70 while the call screen is displayed (control example 1A) or after returning to the registration screen (control example 2A, control example 3A), the mobile terminal 60 transmits the weighing value to the cloud server 20, and the cloud server 20 stores (overwrites) the weighing value received from the mobile terminal 60 as the current weighing value. (3) Furthermore, when the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed or after returning to the registration screen, the mobile terminal 60 sets an unauthorized insertion flag. (4) When switching from the call screen to the registration screen, if the fraudulent insertion flag is not set, the mobile terminal 60 determines that no fraudulent insertion has occurred, and if the fraudulent insertion flag is set, it determines that a fraudulent insertion has occurred.

[0150] In the case of the configuration example 1A, the mobile terminal 60 may determine whether or not an unauthorized insertion has occurred before returning to the registration screen. In this case, the unauthorized insertion flag does not need to be provided.

[0151] In the case of a configuration using a reference measurement value (control example 1B, control example 2B, control example 3B, control example B), for example, the following may be performed. (1) When switching from the registration screen to the call screen, the mobile terminal 60 instructs the cloud server 20 to save the "reference measurement value." Based on the instruction, the cloud server 20 stores (saves) the current measurement value (the measurement value immediately before switching to the call screen) as the "reference measurement value." (2) When the mobile terminal 60 receives a measurement value from the cart 70 while the call screen is displayed (Configuration Example 1B) or after returning to the registration screen (Configuration Example 2B, Configuration Example 3B, Configuration Example 4B), the mobile terminal 60 transmits the measurement value to the cloud server 20, and the cloud server 20 stores (overwrites) the measurement value received from the mobile terminal 60 as the current measurement value. (3) When switching from the call screen to the registration screen, the mobile terminal 60 receives the “reference measurement value” and the “current measurement value” from the cloud server 20, and determines that no fraudulent input has occurred if the “reference measurement value” is not less than the “current measurement value,” and determines that fraudulent input has occurred if the “reference measurement value” is less than the “current measurement value.”

[0152] (Cloud server 20 stores the measured value and determines whether or not there has been any fraudulent input.) In the case of the configuration using the unauthorized input flag (control example 1A, control example 2A, control example 3A), for example, the following may be performed: The cloud server 20 manages the unauthorized input flag. (1) When switching from the registration screen to the call screen, the mobile terminal 60 instructs the cloud server 20 to clear the fraudulent insertion flag. Based on the instruction, the cloud server 20 clears the fraudulent insertion flag if it has not been cleared. (2) When the mobile terminal 60 receives a weighing value from the cart 70 while the call screen is displayed (control example 1A) or after returning to the registration screen (control example 2A, control example 3A), the mobile terminal 60 transmits the weighing value to the cloud server 20, and the cloud server 20 stores (overwrites) the weighing value received from the mobile terminal 60 as the current weighing value. (3) Furthermore, when the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed or after returning to the registration screen, the mobile terminal 60 instructs the cloud server 20 to set an unauthorized insertion flag. The cloud server 20 sets the unauthorized insertion flag based on the instruction. (4) When switching from the call screen to the registration screen, the mobile terminal 60 instructs the cloud server 20 to determine whether or not an unauthorized insertion has occurred. Based on this instruction, the cloud server 20 determines that no unauthorized insertion has occurred if the unauthorized insertion flag is not set, and determines that an unauthorized insertion has occurred if the unauthorized insertion flag is set. If the cloud server 20 determines that an unauthorized insertion has occurred, it notifies the mobile terminal 60 that an unauthorized insertion has occurred (or instructs the mobile terminal 60 to notify the mobile terminal 60 of the unauthorized insertion).

[0153] In the case of configuration example 1A, mobile terminal 60 may instruct cloud server 20 to determine whether or not there has been an unauthorized insertion before returning to the registration screen, and cloud server 20 may determine whether or not there has been an unauthorized insertion before returning to the registration screen. In this case, the unauthorized insertion flag may not be provided.

[0154] In the case of a configuration using a reference measurement value (control example 1B, control example 2B, control example 3B, control example B), for example, the following may be performed. (1) When switching from the registration screen to the call screen, the mobile terminal 60 instructs the cloud server 20 to save the "reference measurement value." Based on the instruction, the cloud server 20 stores (saves) the current measurement value (the measurement value immediately before switching to the call screen) as the "reference measurement value." (2) When the mobile terminal 60 receives a measurement value from the cart 70 while the call screen is displayed (Configuration Example 1B) or after returning to the registration screen (Configuration Example 2B, Configuration Example 3B, Configuration Example 4B), the mobile terminal 60 transmits the measurement value to the cloud server 20, and the cloud server 20 stores (overwrites) the measurement value received from the mobile terminal 60 as the current measurement value. (3) When switching from the call screen to the registration screen, the mobile terminal instructs the cloud server 20 to determine whether or not there has been an unauthorized insertion. Based on this instruction, the cloud server 20 determines that there has been no unauthorized insertion if the "reference measurement value" < "current measurement value" is not true, and determines that there has been an unauthorized insertion if the "reference measurement value" < "current measurement value." If the cloud server 20 determines that there has been an unauthorized insertion, it notifies the mobile terminal 60 that an unauthorized insertion has occurred (or instructs the mobile terminal 60 to notify the mobile terminal 60 of the unauthorized insertion).

[0155] (The cart 70 stores the weighed value, and the mobile terminal 60 determines whether or not there is any fraudulent insertion.) In the case of the configuration using the unauthorized input flag (control example 1A, control example 2A, control example 3A), for example, the following may be performed. (1) When switching from the registration screen to the call screen, the mobile terminal 60 clears the fraudulent input flag if it has not been cleared. (2) When the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed (control example 1A) or after returning to the registration screen (control example 2A, control example 3A), the mobile terminal 60 sets an unauthorized insertion flag. (3) When switching from the call screen to the registration screen, if the fraudulent insertion flag is not set, the mobile terminal 60 determines that no fraudulent insertion has occurred, and if the fraudulent insertion flag is set, it determines that a fraudulent insertion has occurred.

[0156] In the case of the configuration example 1A, the mobile terminal 60 may determine whether or not an unauthorized insertion has occurred before returning to the registration screen. In this case, the unauthorized insertion flag does not need to be provided.

[0157] In the case of a configuration using a reference measurement value (control example 1B, control example 2B, control example 3B, control example B), for example, the following may be performed. (1) When switching from the registration screen to the call screen, the mobile terminal 60 instructs the cart 70 to save the "reference weight value." Based on this instruction, the cart 70 stores (saves) the current weight value (the weight value immediately before switching to the call screen) as the "reference weight value." (2) When switching from the call screen to the registration screen, the mobile terminal 60 receives the “reference weight value” and the “current weight value” from the cart 70, and determines that no fraudulent input has occurred if the “reference weight value” is not less than the “current weight value,” and determines that fraudulent input has occurred if the “reference weight value” is less than the “current weight value.”

[0158] (Cart 70 stores the weighed value and determines whether or not there is any fraudulent input.) In the case of the configuration using the improper insertion flag (control example 1A, control example 2A, control example 3A), for example, the following may be performed: The cart 70 manages the improper insertion flag. (1) When switching from the registration screen to the call screen, the mobile terminal 60 instructs the cart 70 to clear the fraudulent insertion flag. Based on the instruction, the cart 70 clears the fraudulent insertion flag if it has not been cleared. (2) When the mobile terminal 60 receives a weight value from the cart 70 while the call screen is displayed (1-1A) or after returning to the registration screen (1-2A, 1-3A), it instructs the cart 70 to set the fraudulent insertion flag. The cart 70 sets the fraudulent insertion flag based on the instruction. Note that, since the use of the screen switching notification allows the cart 70 to recognize whether the call screen is being displayed or not, the cart 70 may set the fraudulent insertion flag without transmitting the weight value to the mobile terminal 60 (i.e., without following an instruction from the mobile terminal 60). (3) When switching from the call screen to the registration screen, the mobile terminal 60 instructs the cart 70 to determine whether or not a fraudulent insertion has occurred. Based on this instruction, the cart 70 determines that no fraudulent insertion has occurred if the fraudulent insertion flag is not set, and determines that a fraudulent insertion has occurred if the fraudulent insertion flag is set. If the cart 70 determines that a fraudulent insertion has occurred, it notifies the mobile terminal 60 that a fraudulent insertion has occurred (or instructs the mobile terminal 60 to notify the fraudulent insertion).

[0159] In the case of configuration example 1A, the mobile terminal 60 may instruct the cart 70 to determine whether or not there has been any fraudulent insertion before returning to the registration screen, and the cart 70 may determine whether or not there has been any fraudulent insertion before returning to the registration screen. In this case, the fraudulent insertion flag may not be provided.

[0160] In the case of a configuration using a reference measurement value (control example 1B, control example 2B, control example 3B, control example B), for example, the following may be performed. (1) When switching from the registration screen to the call screen, the mobile terminal 60 instructs the cart 70 to save the "reference weight value." Based on this instruction, the cart 70 stores (saves) the current weight value (the weight value immediately before switching to the call screen) as the "reference weight value." (2) When switching from the call screen to the registration screen, the mobile terminal 60 instructs the cart 70 to determine whether or not an unauthorized insertion has occurred. Based on this instruction, the cart 70 determines that no unauthorized insertion has occurred if the "reference weight value" is not less than the "current weight value," and determines that an unauthorized insertion has occurred if the "reference weight value" is less than the "current weight value." If the cart 70 determines that an unauthorized insertion has occurred, it notifies the mobile terminal 60 that an unauthorized insertion has occurred (or instructs the mobile terminal 60 to notify the unauthorized insertion).

[0161] In the above "Control by other devices, etc.", an example using measurement values ​​was explained, but the same applies to cases using captured images (image recognition). Also, while the example of a forgotten registration (unregistered insertion) was explained, the same applies to forgotten removal (cancelled but not removed), forgotten cancellation (uncancelled removal), and forgotten insertion (unregistered insertion).

[0162] (Communication status with Cart 70) If a product is inserted (such as an increase in a weighing value) while the call screen is displayed, the mobile terminal 60 will alert the user after the call to any fraudulent activity that occurred while the call screen was displayed (such as the insertion of an unregistered product).Similarly, if a product is inserted when the mobile terminal 60 is unable to communicate with the cart 70 (a communication-disabled state), the mobile terminal 60 will alert the user after it becomes able to communicate with the cart 70 (a communication-enabled state) to any fraudulent activity that occurred while the communication screen was displayed (such as the insertion of an unregistered product).

[0163] For example, when the mobile terminal 60 changes from a communication-enabled state to a communication-disabled state, it clears the fraudulent insertion flag (or stores the "reference weight value"). After the communication-disabled state changes to a communication-enabled state, if the fraudulent insertion flag is not set (or if the "reference weight value" is not < the "current weight value"), the mobile terminal 60 determines that no fraudulent insertion has occurred, and if the fraudulent insertion flag is set (or if the "reference weight value" is < the "current weight value"), it determines that fraudulent insertion has occurred. Note that, since the mobile terminal 60 does not receive weight values ​​from the cart 70 when it is in a communication-disabled state, control example 1A and control example 1B are not suitable, but other control examples are applicable.

[0164] As with the notification of fraud etc. while the call screen is displayed, for notification of fraud etc. while communication is unavailable, cloud server 20 or cart 70 may store a measurement value and determine whether or not a deposit has been made. The same applies to notification of fraud etc. while app A is not running and notification of fraud etc. while mobile terminal 60 is not running (described later).

[0165] (App A execution (startup) state) If a product is inserted while app A is not running (app A non-executing state), the mobile terminal 60 will notify the user of any fraud that occurred during the non-executing state (such as the insertion of an unregistered product) after app A is running (app A execution state).

[0166] For example, the mobile terminal 60 clears the fraudulent insertion flag (or stores the "reference weight value") when the execution state of application A changes from the execution state of application A due to application killing or the like. After the execution state of application A changes from the execution state of application A, if the fraudulent insertion flag is not set (or if the "reference weight value" is not < the "current weight value"), the mobile terminal 60 determines that no fraudulent insertion has occurred, and if the fraudulent insertion flag is set (or if the "reference weight value" is < the "current weight value"), the mobile terminal 60 determines that fraudulent insertion has occurred.

[0167] (Mobile terminal 60 startup (power-on) state) If a product is inserted while the mobile terminal 60 is in an inactive state (the mobile terminal 60 is in an inactive state), the mobile terminal 60 will alert the user of any fraud that occurred while the mobile terminal 60 was in an inactive state (such as the insertion of an unregistered product) after the mobile terminal 60 becomes active (the mobile terminal 60 is in an active state).

[0168] For example, when the mobile terminal 60 changes from an activated state to an inactivated state, it clears the fraudulent insertion flag (or stores the "reference weight value"). After the mobile terminal 60 changes from an inactivated state to an activated state (app A is also running), if the fraudulent insertion flag is not set (or if the "reference weight value" is not < the "current weight value"), it determines that no fraudulent insertion has occurred, and if the fraudulent insertion flag is set (or if the "reference weight value" is < the "current weight value"), it determines that fraudulent insertion has occurred. Note that since the mobile terminal 60 does not receive weight values ​​from the cart 70 when in an inactivated state, control example 1A and control example 1B are not suitable, but other control examples are applicable.

[0169] Although examples using weighing values ​​have been described above in the "state of communication with cart 70," "state of application A execution (startup)," and "state of mobile terminal 60 startup (power-on)," the same applies to cases using captured images (image recognition). Also, while the example described is of a situation where registration is forgotten (unregistered insertion), the same applies to situations where removal is forgotten (cancelled but not removed), cancellation is forgotten (uncancelled removal), and insertion is forgotten (registered but not inserted).

[0170] (Transmission and reception of information between the mobile terminal 60 and the cloud server 20, and storage of information) The transmission and reception of information between the mobile terminal 60 and the cloud server 20, and the storage of information may be realized by any of the following aspects (Aspects A to F), or by appropriately combining part of one aspect with part of another aspect.

[0171] <Aspect A> Each time the mobile terminal 60 acquires a product code (each time the product barcode is read or the product button is operated), it stores the product code in its storage unit and transmits the product code to the cloud server 20. Upon receiving the product code from the mobile terminal 60, the cloud server 20 references the product master, acquires product information (product name, price, etc.) corresponding to the product code, and transmits (responds to) the acquired product information to the mobile terminal 60. As described above, upon receiving each product code from the mobile terminal 60, the cloud server 20 transmits the product information acquired from the product code to the mobile terminal 60, but does not store the product code and the product information acquired from the product code in the transaction information of the mobile terminal 60. The above-mentioned portion of Aspect A also applies to Aspect B described below.

[0172] The mobile terminal 60 transmits the acquired product code to the cloud server 20 and receives product information from the cloud server 20. The mobile terminal 60 stores the product information in its storage unit in association with the product code as registration information for the product. When the mobile terminal 60 completes registration (when the checkout instruction button BT631 is operated), it simultaneously transmits the product codes of one or more products stored in its storage unit to the cloud server 20. When the cloud server 20 receives the product codes of one or more products from the mobile terminal 60, it references the product master, acquires product information corresponding to each product code, associates the product information acquired from each product code with each product code, and stores this as registration information for each product in the transaction information of the mobile terminal 60. In other words, the cloud server 20 does not store the registration information for each product of the mobile terminal 60 in the transaction information of the mobile terminal 60 each time the mobile terminal 60 acquires an individual product code. Instead, when the mobile terminal 60 completes product registration, it collectively stores the registration information for one or more products of the mobile terminal 60 in the transaction information of the mobile terminal 60. According to Aspect A (the same applies to Aspects B, D, and E), the cloud server 20 does not update the transaction information of each mobile terminal 60 (because registration information is not added, etc.) each time the mobile terminal 60 acquires a product code. This eliminates the processing load on the cloud server 20 (e.g., search processing for the target transaction information, writing information, etc.) that would be incurred if the transaction information of each mobile terminal 60 were updated. Furthermore, because there is no processing load as described above each time the mobile terminal 60 acquires a product code, the response (updating the registration screen, etc.) when the mobile terminal 60 acquires a product code is improved. Furthermore, even if the number of product codes acquired by the mobile terminal 60 by the time registration is completed is N (even if N products are registered in one transaction), only one search process (pre-processing before updating) is required to search for transaction information to be updated (i.e., the total lead time for one transaction is reduced to one time), which is efficient. In addition, according to the aspect A, compared to the aspect B, the amount of information transmitted and received between the mobile terminal 60 and the cloud server 20 after the mobile terminal 60 has completed registration can be reduced.

[0173] <Mode B> The mobile terminal 60 transmits the acquired product code to the cloud server 20 and receives product information from the cloud server 20. The mobile terminal 60 stores the product information in a storage unit in association with the product code as registration information for the product. When the mobile terminal 60 completes registration, the mobile terminal 60 simultaneously transmits the registration information for one or more products (one or more product codes, product information corresponding to each product code) stored in the storage unit to the cloud server 20. That is, in Aspect A, the mobile terminal 60 simultaneously transmits the product codes for one or more products to the cloud server 20 when it completes registration, whereas in Aspect B, the mobile terminal 60 simultaneously transmits the registration information for one or more products to the cloud server 20 when it completes registration. The cloud server 20, which receives the registration information for one or more products from the mobile terminal 60, stores the received registration information in the transaction information of the mobile terminal 60. According to Aspect B (similar to Aspect E), the cloud server 20 acquires the product registration information from each mobile terminal 60 when it completes registration, and therefore does not need to refer to the product master when each mobile terminal 60 completes registration. Therefore, in the aspect B, the load of the cloud server 20 referencing the product master and acquiring product information of each product when each mobile terminal 60 has completed registration is eliminated.

[0174] <Aspect C> Each time the mobile terminal 60 acquires a product code, it stores the product code in its storage unit and transmits the product code to the cloud server 20. Upon receiving the product code from the mobile terminal 60, the cloud server 20 references the product master, acquires product information corresponding to the product code, transmits the acquired product information to the mobile terminal 60, and stores registration information for the product in the transaction information of the mobile terminal 60. That is, in Aspects A and B, the cloud server 20 does not update the transaction information of the mobile terminal 60 each time a product code is acquired from the mobile terminal 60, but in Aspect C, the cloud server 20 updates the transaction information of the mobile terminal 60 each time a product code is acquired from the mobile terminal 60. According to Aspect C (and Aspect F as well), the mobile terminal 60 does not need to transmit the information stored in its storage unit (product codes of one or more products, registration information for one or more products) to the cloud server 20 when registration is completed, thereby reducing the amount of communication between the mobile terminal 60 and the cloud server 20 when registration is completed. Furthermore, according to aspect C (similarly to aspect F), when the mobile terminal 60 has completed registration, the cloud server 20 does not incur the load of referencing the product master based on the product code acquired from the mobile terminal 60 to acquire product information and storing the acquired product information in the transaction information (the load in the case of aspect A), nor the load of storing the product information acquired from the mobile terminal 60 in the transaction information (the load in the case of aspect B).

[0175] <Mode D> The mobile terminal 60 receives the product master from another device (for example, the cloud server 20) and stores it in the storage unit. Every time the mobile terminal 60 acquires a product code, it references the product master stored in the storage unit to acquire product information for the product code, and stores the product information in the storage unit in association with the product code as registration information for the product. The above-mentioned part of aspect D also applies to aspect E below.

[0176] When the mobile terminal 60 has completed registration, it transmits the product codes of one or more products stored in the storage unit to the cloud server 20 all at once (hereinafter, the same as in aspect A). That is, in aspect A, the cloud server 20 references the product master, but in aspect D, the mobile terminal 60 references the product master, which is different. According to aspect D (as well as aspect E), the mobile terminal 60 does not need to transmit a product code to the cloud server 20 every time it acquires a product code. Furthermore, according to aspect D (as well as aspect E), the cloud server 20 references the product master to acquire product information every time the mobile terminal 60 acquires a product code, and there is no burden of transmitting the acquired product information to the mobile terminal 60.

[0177] <Aspect E> When the mobile terminal 60 has completed registration, it transmits the registration information of one or more products stored in the storage unit to the cloud server 20 all at once (hereinafter, the same as in aspect B). That is, in aspect B, the cloud server 20 references the product master, but in aspect E, the mobile terminal 60 references the product master. Alternatively, in aspect D, the mobile terminal 60 transmits the product codes of one or more products all at once to the cloud server 20 when it has completed registration, but in aspect E, the mobile terminal 60 transmits the registration information of one or more products all at once to the cloud server 20 when it has completed registration.

[0178] <Aspect F> The mobile terminal 60 receives the product master from another device and stores it in the storage unit. Every time the mobile terminal 60 acquires a product code, it references the product master stored in the storage unit to acquire product information for the product code, stores the product information in the storage unit in association with the product code as registration information for the product, and transmits the product information to the cloud server 20. The cloud server 20 stores the product information received from the mobile terminal 60 as registration information in the transaction information of the mobile terminal 60. In other words, the difference is that in aspect C, the cloud server 20 references the product master, but in aspect F, the mobile terminal 60 references the product master.

[0179] It has been explained that cloud server 20 may be composed of multiple servers, but it may also be composed of, for example, cloud server 20A that stores product master data and cloud server 20B that stores transaction information for each mobile terminal 60.

[0180] In the case of the cloud server 20A and the cloud server 20B, in aspects A to C, each time the mobile terminal 60 acquires a product code, it transmits the product code to the cloud server 20A, and the cloud server 20A, having received the product code, acquires product information by referring to the product master. Note that in aspects A to C, each time the mobile terminal 60 acquires a product code, it may transmit the product code to the cloud server 20B, and the cloud server 20B, having received the product code, may inquire of the cloud server 20A about product information corresponding to the product code.

[0181] In the case of the cloud server 20A and the cloud server 20B, in aspect A (similar to aspect D), the mobile terminal 60 that has completed registration simultaneously transmits the product codes of one or more products stored in the storage unit to the cloud server 20A, the cloud server 20A acquires product information for each product by referring to the product master and transmits (supplies) each product information together with each product code to the cloud server 20B, and the cloud server 20B stores the product information as registration information for each product in the transaction information of the mobile terminal 60. Note that in aspect A (similar to aspect D), the mobile terminal 60 that has completed registration simultaneously transmits the product codes of one or more products stored in the storage unit to the cloud server 20B, and the cloud server 20B may inquire of the cloud server 20A about product information corresponding to each product code, and store the product information for each product acquired by inquiring of the cloud server 20A together with each product code in the transaction information of the mobile terminal 60 as registration information for each product.

[0182] In the case of the cloud server 20A and the cloud server 20B, in aspect B (similar to aspect E), the mobile terminal 60 that has completed registration may simultaneously transmit the registration information of one or more products stored in the storage unit to the cloud server 20B, and the cloud server 20B may store it in the transaction information of the mobile terminal 60. Note that in aspect B (similar to aspect E), the mobile terminal 60 that has completed registration may simultaneously transmit the registration information of one or more products stored in the storage unit to the cloud server 20A, and the cloud server 20A may transmit (transfer) the registration information of the one or more products to the cloud server 20B, and the cloud server 20B may store it in the transaction information of the mobile terminal 60.

[0183] In the case where the system is configured with cloud server 20A and cloud server 20B, in aspects D to F, mobile terminal 60 may receive the product master from cloud server 20A and store it in the storage unit.

[0184] In the case of the cloud server 20A and the cloud server 20B, in aspect F, each time a product code is acquired, the mobile terminal 60 refers to the product master stored in the storage unit to acquire product information for the product code, stores the product information in the storage unit in association with the product code as registration information for the product, and transmits the product information to the cloud server 20B. Note that in aspect F, each time a product code is acquired, the mobile terminal 60 refers to the product master stored in the storage unit to acquire product information for the product code, stores the product information in the storage unit in association with the product code as registration information for the product, and transmits the product information to the cloud server 20A, and the cloud server 20A transmits (transfers) the registration information for the one or more products to the cloud server 20B, and the cloud server 20B may store the registration information in the transaction information of the mobile terminal 60.

[0185] In addition, even in the case of an embodiment (Aspect A, Aspect B, Aspect D, Aspect E) in which the cloud server 20 collectively stores the registration information of one or more products when the mobile terminal 60 finishes registering the products, or an embodiment (Aspect C, Aspect F) in which the cloud server 20 stores the registration information of an individual product each time the mobile terminal 60 acquires the product code of that product, after the mobile terminal 60 finishes registering the products, the cloud server 20 stores the registration information of all products of that mobile terminal 60 in the transaction information of that mobile terminal 60, so the settlement device 50 can receive the registration information of all products from the cloud server 20 by reading the settlement code GA641 displayed after operating the accounting instruction button BT631.

[0186] (Status Update) When the mobile terminal 60 completes the product registration based on the operation of the settlement code GA641 and transitions the screen from the registration screen to the settlement code display screen, it sends information to the cloud server 20 that the screen has transitioned from the registration screen to the settlement code display screen, and the cloud server 20 updates the status in the transaction information of the mobile terminal 60 from the registration state to the settlement declaration state.

[0187] In a mode in which cloud server 20 collectively stores registration information for one or more products at the time when mobile terminal 60 finishes registering products, when mobile terminal 60 transitions the screen from the registration screen to the settlement code display screen, it transmits to cloud server 20 information indicating that the screen has transitioned from the registration screen to the settlement code display screen, along with the product codes of one or more products (or registration information for one or more products). Upon receiving the information, cloud server 20 collectively stores the registration information for one or more products in the transaction information of mobile terminal 60, and updates the status in the transaction information from a registration state to a settlement declaration state.

[0188] In addition, in a case where cloud server 20 collectively stores registration information for one or more products when mobile terminal 60 finishes registering the products, cloud server 20 may update the status by receiving product codes for one or more products (or registration information for one or more products). In other words, in a case where cloud server 20 collectively stores registration information for one or more products when mobile terminal 60 finishes registering the products, when mobile terminal 60 transitions the screen from the registration screen to the settlement code display screen, mobile terminal 60 does not need to transmit information to cloud server 20 that the screen has transitioned from the registration screen to the settlement code display screen.

[0189] In a mode in which cloud server 20 stores the registration information of an individual product each time mobile terminal 60 acquires the product code of that product, when mobile terminal 60 transitions the screen from the registration screen to the settlement code display screen, mobile terminal 60 transmits information to cloud server 20 that the screen has transitioned from the registration screen to the settlement code display screen. Upon receiving the information, cloud server 20 updates the status in the transaction information of mobile terminal 60 from the registration state to the settlement declaration state.

[0190] Whether the cloud server 20 collectively stores the registration information for one or more products when the mobile terminal 60 finishes registering the products, or whether the cloud server 20 stores the registration information for each product each time the mobile terminal 60 acquires the product code of that product, when the settlement device 50 reads the settlement code GA641 of a certain mobile terminal 60, the cloud server 20 may check the status of that mobile terminal 60 and, if it is in a settlement declaration state, send the registration information for all products to the settlement device 50. In order to check the status, problems that can arise, for example, when a captured image of the settlement code GA641 is read (such as sending registration information to the settlement device 50 when the state is in the process of returning from a settlement declaration state to a registration state) will no longer occur.

[0191] When the mobile terminal 60 transitions the screen from the settlement code display screen to the registration screen, for example, from Figure 4 (F) to Figure 3 (G), it sends information to the cloud server 20 that the screen has transitioned from the settlement code display screen to the registration screen, and the cloud server 20, having received the above information, updates the status in the transaction information of the mobile terminal 60 from the settlement declaration status to the registration status.

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

[0193] If a customer puts an item into the shopping basket (cart 70) while the call screen is displayed (if the weight value increases), the item was not registered while the call screen was displayed, and if left as is, a loss will occur to the store (forgetting to register). In the above embodiment, after the call screen display ends (on the screen returned from the call screen), a message is displayed (small screen SG1, small screen SG2) indicating that the item has been put in (the need to register the item), so the customer will register the item according to the display, and the store will not incur a loss.

[0194] If a customer removes an item from the shopping cart while the call screen is displayed (if the weight value decreases), the item was not canceled while the call screen was displayed, and if left as is, the customer will incur a loss (forgetting to cancel). In the above embodiment, after the call screen display ends (on the screen returned from the call screen), a message is displayed (small screen SG3, small screen SG4) indicating that the item has been removed (the need to cancel the item), so the customer will cancel the item according to the display, and no loss will be incurred by the customer.

[0195] If a customer adds an item to the shopping cart (if the weight increases) or removes an item from the shopping cart (if the weight decreases) while the payment code display screen is displayed, the necessary action (such as registering or canceling the item) can be taken immediately (because the payment code display screen can be immediately switched from the registration screen to the registration screen). Therefore, if a customer adds an item to the shopping cart or removes an item from the shopping cart while the payment code display screen is displayed, a notification is sent immediately. On the other hand, if a customer adds an item to the shopping cart or removes an item from the shopping cart while the call screen is displayed, it is difficult to take immediate action (because the call screen cannot be switched from the registration screen as long as the call is ongoing). Therefore, if a customer adds an item to the shopping cart or removes an item from the shopping cart while the call screen is displayed, a notification is sent after the call screen has finished displaying. Specifically, the notification is sent at an appropriate time (immediately after the call screen has finished displaying, without any delay), so the customer can easily recognize the situation (forgetting to register or cancel) and it is possible to prevent the customer from forgetting to take the necessary action.

[0196] In addition, if an item is inserted when communication with the cart 70 is not possible, if an item is inserted when app A is not running, or if an item is inserted when the mobile terminal 60 is not running, similar notifications will be issued, so even in such cases, no loss will be incurred by the store or the customer.

[0197] (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 (13). In addition, the following (1) to (13) can be appropriately combined with each other.

[0198] (1) In the above embodiment, the mobile terminal 60 displays (for example, displays small screens SG1 to SG4) information about adding a product to the shopping cart (the need to register the product) or removing the product (the need to cancel the product), but audio may be output instead of or in addition to the display.

[0199] The mobile terminal 60 may display an operable store clerk call button on the small screen SG1. The same applies to the small screens SG2 to SG4. When the store clerk call button is operated, the mobile terminal 60 may send a call notification to a device operated by the store clerk (the transaction status management device 40, the store clerk's mobile terminal) via the cloud server 20, for example.

[0200] (2) In the above embodiment, when a customer adds an item to the shopping cart or removes an item from the shopping cart while the call screen is displayed, the mobile terminal 60 notifies the customer that the item has been added (need to register the item) or removed (need to cancel the item) immediately after the call screen display ends. However, the notification may be made if the necessary action is not taken within a predetermined time (e.g., 10 seconds) from the end of the call screen display (i.e., if the necessary action is not taken within the predetermined time after it becomes possible). As mentioned above, it is easier for the customer to recognize and understand the situation (forgetting to register or forgetting to cancel) if the notification is made immediately after the call screen display ends without any delay.

[0201] (3) In the above embodiment, an example has been described in which, in a situation where an incoming call is received while the registration screen is being displayed and a call screen is displayed instead of the registration screen (when the registration screen switches from the call screen to the call screen), if a product is inserted (such as an increase in a weight value) while the call screen is being displayed, a notification of fraud (such as the insertion of an unregistered product) while the call screen is being displayed is given after the call screen has ended (on the registration screen when the call screen has been restored). Also, in a situation where an incoming call is received while the settlement code display screen is being displayed and a call screen is displayed instead of the settlement code display screen (when the settlement code display screen switches from the call screen to the call screen), if a product is inserted (such as an increase in a weight value) while the call screen is being displayed, a notification of fraud (such as the insertion of an unregistered product) while the call screen is being displayed is given after the call screen has ended (on the settlement code display screen when the call screen has been restored, or on the registration screen). However, the screen that is the subject of a notification when a product is inserted (such as an increase in a weight value) while the screen is being displayed is not limited to the call screen.

[0202] The target screens may be, for example, various SNS (Social Networking Service) screens, email screens, web browser screens, tool screens such as calculators, calendar or schedule screens, video viewing screens, game screens, etc. For example, when switching from a registration screen to an SNS screen, if a product is inserted while the SNS screen is displayed, the mobile terminal 60 may notify the user of any fraud that occurred while the SNS screen was displayed after the SNS screen display has ended (on the registration screen returned from the SNS screen).

[0203] (4) In the above embodiment, when the registration screen switches to the call screen, or when the settlement code display screen switches to the call screen, if an item is inserted while the call screen is displayed, a notification of fraud, etc. that occurred while the call screen was displayed is described after the call screen has ended. However, the screen before the call screen that notifies of fraud, etc. is not limited to the registration screen or the settlement code display screen.

[0204] The screen displayed before the call screen, which notifies of fraud, etc., may be, for example, a purchase history screen displayed from a purchase history button at the bottom of the registration screen, or a usage guide screen (guidance screen) displayed from a usage guide button at the bottom of the registration screen. For example, when switching from the registration screen to the purchase history screen, if a product is inserted while the purchase history screen is displayed, the mobile terminal 60 may notify of fraud, etc., that occurred while the purchase history screen was displayed after the purchase history screen has ended (on the registration screen returned from the purchase history screen).

[0205] (5) In the above embodiment, an example was described in which if a product is inserted while the settlement code display screen is displayed, an alert is immediately issued regarding fraud, etc. However, the screen that immediately alerts the user to fraud, etc. when a product is inserted, etc. is not limited to the settlement code display screen.

[0206] The screen that immediately notifies of fraud, etc. when a product is inserted, etc. may be, for example, a purchase history screen or a usage guide screen (guidance screen). For example, the mobile terminal 60 may immediately notify of fraud, etc. when a product is inserted, etc. while the purchase history screen is being displayed. That is, in (4) above, it was explained that the mobile terminal 60 may notify of fraud, etc. after the display of the purchase history screen ends when a product is inserted, etc. while the purchase history screen is being displayed. However, if a product is inserted, etc. while the purchase history screen is being displayed, the mobile terminal 60 may notify of fraud, etc. on the purchase history screen.

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

[0208] (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 whitebait), calculates the difference in weight (weight a) between the weight currently received from the cart 70 (e.g., the weight of the whitebait + oolong tea), and compares the difference in weight (weight a) with the weight (weight b) of the product currently registered (oolong tea). 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.

[0209] 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 currently registered product by inquiring (sending the product code of the registered product) with 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.

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

[0211] (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 + the shirasu), calculates the differential weight (weight a) between this and the weight currently received from the cart 70 (e.g., the weight of the tare weight + the shirasu + the oolong tea), and compares the differential weight (weight a) with the weight (weight b) of the product (oolong tea) registered this time.

[0212] (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 (weight b) of the product (oolong tea) registered this time.

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

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

[0215] 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."

[0216] (8) Related to (7) 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 operating 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 starting to rearrange the cart (when the start cart rearrangement button is operated) may be stored and compared with the weight value after completing the cart rearrangement (when the end cart rearrangement button is operated) to monitor for any unauthorized insertion of products while declaring that they are rearranging the cart.

[0217] (9) 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).

[0218] When connection identification information is acquired from a beacon, multiple pieces of connection identification information (respective connection identification information from multiple carts 70 present in the vicinity) may be acquired. When multiple pieces of connection identification information are acquired, information about each cart 70 for which connection identification information is acquired is displayed on the screen, and the customer is prompted to select one cart 70 to use. The information about the cart 70 may be, for example, one or more of the following (1) to (3). (1) Car number information of each cart 70. The cart number information is affixed to each cart 70. The customer can visually confirm (by checking the cart number information) which cart 70 (available cart 70) displayed on the screen is, and easily select the cart 70 to use on the screen. The cart number information may be numbers such as "Cart No. 1" or "Cart No. 2," letters such as "Cart No. A" or "Cart No. B," or the name of a plant or animal. (2) Characteristic information about each cart 70 (color, shape, etc.). As with the car number information, the customer can visually check which cart 70 is displayed on the screen (by checking the characteristic information) and easily select the cart 70 to use on the screen. (3) Distance information from the customer. Information such as "closest" or "second closest" may be displayed on the screen for each cart 70. The carts may also be displayed in order of proximity.

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

[0220] (11) 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.

[0221] 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, or the cart 70 may be equipped with a display operation unit equivalent to 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 (for example, automatically connected when the power is turned on).

[0222] That is, the cart 70 in the sales system 1 or the usage mode of the cart 70 may be any of the following (A) to (C). (A) A type that is used by BT connection (Bluetooth connection) with the customer's mobile terminal 60. A BT connection is made with the customer's mobile terminal 60 each time (when the cart 70 is used). (B) Type used by connecting via BT to the mobile terminal 60, which is a rental terminal at the store. Each time (when using the cart 70), a BT connection is made to the mobile terminal 60, which is a rental terminal. (C) Type in which the cart 70 is equipped with a mobile terminal 60 (or a display operation unit equivalent to the mobile terminal 60). The mobile terminal 60 (display operation unit) and the weighing unit may be connected by wire or by BT connection. The mobile terminal 60 (or a display operation unit equivalent to the mobile terminal 60) and the cart 70 (weighing unit) have a fixed one-to-one relationship, and no special operation is required to connect them (for example, they may be connected automatically when the power is turned on).

[0223] (12) 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.

[0224] (13) 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, 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.

[0225] As an example, cloud server 20 may control the display on the screen of mobile terminal 60 (e.g., FIGS. 3 to 5), or, as has already been partially explained (determining whether or not unauthorized input has occurred), cloud server 20 may control the operation of mobile terminal 60. In other words, a program (app A) that controls the operation of service A on mobile terminal 60 may run on the CPU of mobile terminal 60, or may run on the CPU of cloud server 20. In other words, app A may be a web application used using a browser.

[0226] For example, the cloud server 20 includes a display control means for displaying a product registration screen on the mobile terminal 60, and a notification control means for notifying the mobile terminal 60 of an unauthorized addition of a product to the cart by a customer. The mobile terminal 60 is capable of displaying a screen different from the product registration screen. The cloud server 20 (notification control means) notifies the mobile terminal 60 of the unauthorized addition after the mobile terminal 60 changes from a state in which the other screen is displayed in place of the product registration screen to a state in which the product registration screen is displayed in place of the other screen.

[0227] <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]

[0228] (1) One aspect for solving the above-mentioned problem is a program for causing a mobile terminal (e.g., mobile terminal 60) operated when putting products into a cart at a sales floor to function as a computer, and causing the computer to function as a display means for displaying a product registration screen, a registration means for registering products, and a notification means for notifying about the fraudulent putting of products into the cart (e.g., putting an unregistered product into the cart), wherein the display means is capable of displaying a screen different from the product registration screen (e.g., a call screen, a screen for various SNSs, an email screen, etc.), and the notification means is characterized by notifying about the fraudulent putting of products (e.g., notification by small screen SG1 in Figure 4(C) or small screen SG2 in Figure 4(D)) after the display means changes from a state in which it has displayed a screen different from the product registration screen to a state in which it displays the product registration screen instead of the screen different from the product registration screen. According to the program (1), it is possible to more effectively implement a system in which customers themselves register products in the product display area. For example, according to the program (1), after the display of the other screen has finished (on the screen returned from the other screen), a notice of fraudulent insertion (i.e., the need to register products) is displayed, so that customers will register the products in accordance with the notice, and the store will not incur any losses.

[0229] (2) One aspect for solving the above-mentioned problem is a program for causing a mobile terminal (e.g., mobile terminal 60) operated when putting an item into a cart at a sales floor to function as a computer, the program causing the computer to function as a display means for displaying a product registration screen, a registration means for registering products, and a notification means for notifying about the fraudulent putting of an item into the cart (e.g., putting an unregistered item into the cart), the display means being capable of displaying a screen different from the product registration screen (e.g., a call screen, a settlement code display screen, etc.), and the notification means, when the display means is in a state where it is displaying a screen different from the notification mode given on the product registration screen (e.g., small screen SG1 in Figure 4(C), small screen SG2 in Figure 4(D), etc.), notifying about the fraudulent putting of an item into the cart (e.g., message MS710 in Figure 5(A), message MS710 in Figure 5(B), product putting notification area HR720 in Figure 5(C), etc.). According to the program (2), a system in which customers themselves register products in the product display area can be more effectively implemented. For example, according to the program (2), a notification of fraudulent insertion can be preferably displayed on a separate screen in a notification mode suitable for the separate screen.

[0230] (3) A program as described in (1) or (2) that functions as a judgment means for determining whether the insertion has been fraudulent, and that the judgment means judges that the insertion has been fraudulent if the weight value of the basket increases when the display means is displaying another screen instead of the product registration screen. According to the program (3), it is possible to appropriately determine whether or not a bill has been inserted fraudulently using the weight value. As described in the embodiment, it is also possible to monitor (determine) and notify fraudulent insertion by image recognition.

[0231] (4) A program as described in (1) or (2), characterized in that the program functions as a communication means for communicating with an external weighing unit, and the notification means does not notify of the fraudulent insertion when the communication means is unable to communicate with the weighing unit, but notifies of the fraudulent insertion after the communication means is able to communicate with the weighing unit. According to program (4), after communication is enabled, the customer is notified of the fraudulent entry (i.e., the need to register the product), so that the customer will register the product in accordance with the notification, and the store will not incur any losses.

[0232] (5) A program as described in (4) that functions as a judgment means for determining whether the insertion has been fraudulent, and that the judgment means judges that the insertion has been fraudulent if the weighing value of the basket increases when communication with the weighing unit via the communication means is not possible. According to the program (5), it is possible to appropriately determine whether or not a meter has been inserted fraudulently using the measured value.

[0233] (6) One aspect for solving the above-mentioned problem is a mobile terminal that is operated when putting a product into a cart at a sales floor, and that is equipped with a display means for displaying a product registration screen, a registration means for registering the product, and a notification means for notifying about the fraudulent putting of a product into the cart, wherein the display means is capable of displaying a screen different from the product registration screen, and the notification means is characterized in that it notifies about the fraudulent putting of a product after the display means changes from a state in which it has displayed the other screen instead of the product registration screen to a state in which it has displayed the product registration screen instead of the other screen. The mobile terminal of (6) can more suitably implement a system in which customers themselves register products in the product display area, similar to the above (1).

[0234] (7) One aspect for solving the above-mentioned problem is a system including a mobile terminal that is operated when putting products into a cart at a sales floor, the system comprising a display unit that displays a product registration screen, a registration unit that registers products, and an alarm unit that alerts about the fraudulent putting of products into the cart, the display unit being capable of displaying a screen different from the product registration screen, and the alarm unit alerting about the fraudulent putting of products into the cart after the display unit changes from a state in which it has displayed the other screen instead of the product registration screen to a state in which it has displayed the product registration screen instead of the other screen. According to the system (7), similar to the system (1) above, it is possible to more suitably implement a system in which customers themselves register products in the product display area.

[0235] (8) One aspect for solving the above-mentioned problem is a server capable of communicating with a mobile terminal operated by a customer at a sales floor when putting an item into a cart, the server comprising a display control means for causing the mobile terminal to display a product registration screen, and a notification control means for causing the mobile terminal to notify the customer of an unauthorized addition of an item to the cart, the mobile terminal being capable of displaying a screen different from the product registration screen, and the notification control means for causing the mobile terminal to notify the customer of the unauthorized addition of an item after the mobile terminal has changed from a state in which it was displaying the other screen instead of the product registration screen to a state in which it is displaying the product registration screen instead of the other screen. According to the system (8), similar to the system (1) above, it is possible to more suitably implement a system in which customers themselves register products in the product display area.

[0236] (9) One aspect for solving the above-mentioned problem is a notification method for notifying a customer of the fraudulent insertion of a product into a cart by using a mobile terminal operated by the customer at a sales floor when inserting the product into the cart, the notification method comprising: a display step for displaying a product registration screen on the mobile terminal; and a notification step for notifying the mobile terminal of the fraudulent insertion, wherein the mobile terminal is capable of displaying a screen different from the product registration screen, and the notification step is characterized in that the notification of the fraudulent insertion occurs after the mobile terminal changes from a state in which the other screen is displayed in place of the product registration screen to a state in which the product registration screen is displayed in place of the other screen. According to the notification method (9), similar to the above (1), it is possible to more suitably implement a system in which customers themselves register products in the product display area.

[0237] Note that a program for implementing the functions of each of the above-described devices (e.g., cloud server 20, transaction status management device 40, settlement device 50, 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. Thus, a recording medium storing a program may be a non-transitory recording medium such as a CD-ROM. The term "recording medium" also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in a format executable by a terminal device. In other words, the format in which the program is stored on the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a form that is executable on the terminal device. The program may be divided into multiple parts, each of which may be downloaded at different times and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" also includes a storage medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be one that realizes part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0238] 1...Sales system 10...Head office server 20...Cloud server 30...Store controller 40...Transaction status management device 50...Payment device 60...Mobile terminal 70...Cart

Claims

1. A program for causing a mobile terminal operated when putting an item into a shopping cart at a sales floor to function as a computer, The computer a display means for displaying a product registration screen; a registration means for registering the product; Notification means for notifying fraudulent addition of products to a cart It functions as The display means It is possible to display a separate screen from the product registration screen, The notification means The display means changes from a state in which another screen is displayed instead of the product registration screen to a state in which the product registration screen is displayed instead of the other screen, and then notifies the user of the fraudulent insertion. A program characterized by:

2. A program for causing a mobile terminal operated when putting an item into a shopping cart at a sales floor to function as a computer, The computer a display means for displaying a product registration screen; a registration means for registering the product; Notification means for notifying fraudulent addition of products to a cart It functions as The display means It is possible to display a separate screen from the product registration screen, The notification means When the display means is displaying another screen, the unauthorized insertion is notified in a different manner from the manner of notification given on the product registration screen. A program characterized by:

3. The determination means for determining whether the input is fraudulent It functions as The determination means When the display means is displaying another screen instead of the product registration screen and the weight value of the basket increases, it is determined that the item has been fraudulently inserted.

3. The program according to claim 1 or 2.

4. Communication means for communicating with an external weighing unit It functions as The notification means When the communication means is unable to communicate with the weighing unit, the improper insertion is not notified, and the improper insertion is notified after the communication means is able to communicate with the weighing unit.

3. The program according to claim 1 or 2.

5. The determination means for determining whether the input is fraudulent It functions as The determination means If the weighing value of the basket increases when communication with the weighing unit via the communication means is not possible, it is determined that the item has been inserted fraudulently.

5. The program according to claim 4.

6. A mobile terminal that is operated when putting products into a cart at a sales floor, a display means for displaying a product registration screen; a registration means for registering a product; a notification means for notifying fraudulent addition of a product to a shopping cart; Equipped with The display means It is possible to display a separate screen from the product registration screen, The notification means The display means changes from a state in which another screen is displayed instead of the product registration screen to a state in which the product registration screen is displayed instead of the other screen, and then notifies the user of the fraudulent insertion. A mobile terminal characterized by:

7. A system including a mobile terminal operated when putting products into a cart at a sales floor, a display unit that displays a product registration screen; a registration section for registering products; a notification unit that notifies of fraudulent addition of products to a shopping cart; Equipped with The display unit It is possible to display a separate screen from the product registration screen, The notification unit The display unit changes from a state in which another screen is displayed instead of the product registration screen to a state in which the product registration screen is displayed instead of the other screen, and then notifies the user of the fraudulent insertion. A system characterized by:

8. A server capable of communicating with a mobile terminal operated by a customer at a sales floor when placing an item in a cart, a display control means for displaying a product registration screen on the mobile terminal; a notification control means for causing the mobile terminal to notify the customer of any unauthorized addition of an item to the basket; Equipped with The mobile terminal It is possible to display a separate screen from the product registration screen, The notification control means The mobile terminal changes from a state in which another screen is displayed instead of the product registration screen to a state in which the product registration screen is displayed instead of the other screen, and then notifies the user of the fraudulent insertion. A server characterized by:

9. A method for notifying a customer of fraudulent addition of a commodity to a basket at a sales floor using a mobile terminal operated by the customer when the customer adds a commodity to the basket, comprising: a display step of displaying a product registration screen on the mobile terminal; a notification step of causing the mobile terminal to notify the unauthorized insertion; Equipped with The mobile terminal It is possible to display a separate screen from the product registration screen, The notification step includes: The unauthorized insertion is notified after the mobile terminal changes from a state in which another screen is displayed instead of the product registration screen to a state in which the product registration screen is displayed instead of the other screen. A notification method characterized by:

Images