Program

Abstract

To make a system, which allows a customer himself or herself to register an article, suitably operate.SOLUTION: There is provided a program that allows a portable terminal usable to register an article to function as a computer, wherein the computer is caused to function as registration means for registering an article and acquisition means for acquiring connection information for connection with a shopping cart, and the registration means can register an article after the acquisition means acquires the connection information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a program. [Background technology]

[0002] There is known an information communication terminal that reads the MAC address of a device from an NFC tag attached to the device and transmits data to an IP address corresponding to the read MAC address (see, for example, Patent Document 1). There is also known a system in which customers themselves register products in a product display area using a shopping cart. [Prior art documents] [Patent documents]

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

[0004] However, there is room for improvement in the system in which customers themselves register products in the product display area using a shopping cart.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique that enables a system in which customers themselves register products to be more suitably implemented. [Means for solving the problem]

[0006] A program according to one aspect for solving the above-mentioned problems includes: This is a program for causing a mobile terminal that can be used to register products to function as a computer, causing the computer to function as a registration means for registering products and an acquisition means for acquiring connection information for connecting to a shopping cart, the program being characterized in that the registration means enables product registration after the connection information is acquired by the acquisition means. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram of a network for explaining a sales system. [Diagram 2] FIG. 2 is an explanatory diagram illustrating a cart. [Diagram 3] 13 is a display example of a mobile terminal. [Figure 4] 13 is a display example of a mobile terminal. [Diagram 5] 13 is a display example of a payment device, etc. [Figure 6] 10 is a flowchart illustrating an example of an operation of the mobile terminal. [Figure 7] 10 is a flowchart illustrating an example of an operation of the mobile terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] 1 is a conceptual diagram of a network for explaining a sales system 1 of 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 in various business formats (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.). The store controller 30, transaction status management device 40, and settlement device 50 are installed in the store (product display area, accounting area, back yard, etc.). These can communicate with each other 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, a head office or a data center, etc.). The devices installed in the store (store controller 30, transaction status management device 40, settlement device 50) and the devices installed outside the store (headquarters server 10, cloud server 20) can communicate with each other (directly or via the store controller 30).

[0010] In addition, a shopping cart (hereinafter simply referred to as a "cart") 70 prepared by the store is present in the store. In addition, a mobile terminal 60 that is owned by a customer who visits the store is present in 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 by wireless communication (for example, NFC (Near Field Communication) such as RFID (Radio frequency identification), 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 uses a mobile terminal 60 to register a product and uses a settlement device 50 to settle the payment. In other words, service A is a self-service in which a customer registers a product and settles the payment by himself / herself, using mobile terminal 60 for product registration and using settlement device 50 for settlement.

[0012] Note that the number of each device (terminal) in FIG. 1 is an example. For example, "..." is illustrated to the right of the settlement device 50 in FIG. 1, but the number of settlement devices 50 installed in the store may be one or more. Also, for example, two mobile terminals 60 are illustrated in FIG. 1, but the number of mobile terminals 60 present in the store is the number of customers who come to the store with their mobile terminals 60, and is not necessarily two. Also, for example, two carts 70 are illustrated in FIG. 1, but 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 when a customer registers a product in a store. Specifically, the mobile terminal 60 registers a product based on the customer's operation (motion) when it is 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 a product based on the customer's operation even if it is attached to the cart 70 or detached from the cart 70 (for example, a state where the customer is holding it in his / her hand and operating it).

[0014] Although not shown in the figure, the mobile terminal 60 includes, for example, a CPU, a storage unit, a display unit, an operation unit, a sound output unit (speaker), a sound 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, and controls the entire mobile terminal 60 by reading and executing programs stored in the storage unit. The storage unit stores various information (e.g., information referenced or generated by the CPU, information acquired from the outside, etc.). The storage unit is a collective term for one or more various storage members (e.g., 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 the service A from the outside (which may be a predetermined server, the cloud server 20) and store (install) it in the storage unit. The mobile terminal 60 may execute various screens (e.g., see Figs. 3(B) to 3(H), 4(C) to 4(H), and 5(C)(D)) and various processes (e.g., see Figs. 6 and 7) related to the service A by the app A. As described above, the service A is a self-service in which the mobile terminal 60 is used for product registration and the settlement device 50 is used for payment, and the app A is an application program that handles the mobile terminal 60 (product registration) portion of the 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 capable of accepting operations on the display screen. The operation unit accepts operations by 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) an imaged image (still image, moving image). The detection unit (measurement unit) detects or measures various events, etc. The detection unit is, for example, a collective term for one or more various detection members (GPS sensor, acceleration sensor, gyro sensor, etc.). Note that, the operation unit, the audio input unit, and the 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, Bluetooth, etc.).

[0018] 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 of the cart 70 (e.g., Bluetooth address) 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 information for connecting to the cart 70 (or simply "connection information").

[0019] 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 later) affixed to each cart 70, or from an NFC tag 79 (described later) affixed to each cart 70.

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

[0021] The mobile terminal 60 can display the captured image by the imaging unit as a so-called through image (live view image) on the display unit. Instead of or in addition to displaying the captured image as a through image on the display unit, the mobile terminal 60 may store the captured image in the storage 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, may store the captured image in the display unit as a through image without storing it in the storage unit, or may store the captured image in the display unit as a through image 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.

[0022] Furthermore, 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 container weight (the container weight), etc.).

[0023] The mobile terminal 60 has various image processing functions. For example, the mobile terminal 60 has an object recognition function for recognizing an object from a captured image. The mobile terminal 60 also reads a barcode (code symbol) attached to a product from the captured image. That is, the mobile terminal 60 has a barcode reading function for recognizing a barcode in a captured image by using an object recognition function, and reading the recognized barcode to obtain a product code (e.g., a JAN code, etc.). The mobile terminal 60 also reads a two-dimensional code 78 (described later) attached to each cart 70. That is, the mobile terminal 60 has a two-dimensional code reading function for recognizing a two-dimensional code 78 in a captured image by using an object recognition function, and reading the recognized two-dimensional code 78 to obtain connection information. The mobile terminal 60 may also have a scan operation detection function for detecting a scanning operation (holding operation) of a product by a customer from a captured image (for example, detecting whether a human hand or a barcode has newly appeared in the captured image).

[0024] The mobile terminal 60 acquires (receives) connection information from an NFC tag 79 (described later) attached to each cart 70. For example, when a customer sets the mobile terminal 60 in the cart 70 (holder unit 74 (described later)), the mobile terminal 60 receives connection information for the cart 70 (set cart 70) from the NFC tag 79 (IC tag communication unit (described later)) attached to the cart 70 (holder unit 74).

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

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

[0027] The holder section 74 is a member for setting the mobile terminal 60. The holder section 74 has an opening (hole) at the position of the imaging section (lens) of the set mobile terminal 60. The mobile terminal charging section 75 stores power to be supplied to the mobile terminal 60 set in the holder section 74.

[0028] 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 represents device identification information (connection information) of the cart 70 (the cart 70 to which the two-dimensional code 78 is attached).

[0029] An NFC tag (IC tag) 79 is attached to the holder unit 74. The NFC tag 79 includes a storage unit that stores device identification information (connection information) of the cart 70 (the cart 70 to which the NFC tag 79 is attached) and a communication unit that transmits the device identification information stored in the storage unit to an outside (specifically, the mobile terminal 60). In the following description, the communication unit included in the NFC tag 79 may be referred to as an IC tag communication unit.

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

[0031] When the imaging unit of the mobile terminal 60 captures an image while attached to the holder unit 74, the mobile terminal 60 obtains an image looking down toward the shopping basket from the position of the holder unit 74. By image recognition of the captured image, the mobile terminal 60 can detect (monitor) whether an unscanned product has been put into the cart 70 or a scanned product has not been put into the cart 70, that is, whether there has been any fraud or operational error during shopping.

[0032] For transactions that are determined to be fraudulent (fraud, operational error), the details of the fraud in the transaction may be confirmed (confirmed in the presence of a store clerk) and necessary measures may be taken (for example, registering products that were added to the cart 70 without being scanned). For example, for transactions (transaction information) that are determined to be fraudulent, information indicating that the transaction has been determined to be fraudulent or that the transaction requires confirmation (for example, a confirmation required flag) may be set, and the details of the fraud in the transaction may be confirmed and necessary measures may be taken until the settlement of the transaction is completed (for example, in the settlement device 50).

[0033] Note that captured images (images captured from each direction) for each product may be stored as verification information, and the verification image of the scanned product may be compared with a newly recognized object to detect that a product different from the scanned product has been added to the cart 70. In other words, it may be checked by image recognition whether the registered product and the added product match (image check).

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

[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 may be a different board). That is, 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 product added to the shopping basket) and the amount of weight decrease (weight of the product removed from the shopping basket).

[0037] The container is an item placed on the placement section 71 in the initial state before shopping begins (more specifically, the state before one item of merchandise is inserted). The container weight is a weighing value by the weighing section in the initial state before shopping begins. The container may include the customer's baggage (wallet, bag, etc.) in addition to the shopping basket. For example, when an empty shopping basket is placed on the placement section 71 in the initial state before shopping begins (i.e., when only a shopping basket is placed), the container is the shopping basket, and the container weight is the weight of the shopping basket. For example, when a shopping basket with a wallet in it is placed on the placement section 71 in the initial state before shopping begins (i.e., when the shopping basket and the wallet are placed), 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.

[0038] (Tare) Furthermore, the cart 70 (cart communication unit) receives tare instruction information from the mobile terminal 60. When the cart 70 receives tare instruction information from the mobile terminal 60, it determines the weighing value at the time of reception as the weighing value (initial weight) in the initial state before shopping begins (the state before one item of merchandise is inserted). For example, if the weighing value in an unloaded state is 0 g and the weight of the shopping basket is 500 g (known), and the weighing value when the tare instruction information is received is 500 g, the tare weight is 500 g (the tare is only the shopping basket). Also, for example, in the above case, if the weighing value when the tare instruction information is received is 3000 g, the tare weight is 3000 g (the tare is the shopping basket + the customer's baggage).

[0039] That is, the cart 70 stores the weighing value in an unloaded state, and after the shopping basket or the customer's baggage is placed on the cart 70 from the unloaded state and the cart 70 receives the tare instruction information, the weighing value when the shopping basket or the customer's baggage is placed on the cart 70 is set as the weighing value at the start of shopping. For example, when the cart 70 receives an instruction to subtract a tare from the mobile terminal 60 while the weighing unit is measuring 3000g, the cart 70 changes the "3000g" to "0g" and notifies the mobile terminal of "0g". Note that when the cart 70 receives an instruction to subtract a tare from the mobile terminal 60 while the weighing unit is measuring 3000g, the cart 70 may notify the mobile terminal 60 of the "3000g". In the former case, the mobile terminal 60 may proceed with the process assuming that the reference weight at the start of shopping is 0g, and in the latter case, the mobile terminal 60 may proceed with the process assuming that the reference weight at the start of shopping is 3000g.

[0040] In addition, since the weight of the shopping basket is known, it is possible to calculate the weight of the customer's baggage. For example, if the weighing value in an unloaded state is 0g, the weight of the shopping basket is 500g (known), and the weighing value when the tare instruction information is received is 3000g, the weight of the baggage is 2500g.

[0041] The mobile terminal 60 transmits tare instruction information to the cart 70 before inserting at least one item of merchandise. For example, when connecting to the cart 70 using the two-dimensional code 78 (see FIGS. 3 and 6), the mobile terminal 60 transmits tare instruction information to the cart 70 (step S7 in FIG. 6) after connecting to the cart 70 using the two-dimensional code 78 (after step S6 in FIG. 6). For example, when connecting to the cart 70 using the NFC tag 79 (see FIGS. 4 and 7), the mobile terminal 60 transmits tare instruction information to the cart 70 (step S38 in FIG. 7) after accepting a shopping start operation (after step S37 in FIG. 7).

[0042] The mobile terminal 60 may send the tare weight instruction information to the cart 70 before the first item is registered (for example, when the initial registration screen is displayed), or after the first item is registered; however, the closer the tare weight is executed to the time just before the item is inserted (the closer the timing to insert the item), the lower the risk of an incorrect determination of fraud when in fact it is not, so it is preferable to send the information to the cart 70 after the first item is registered. In other words, if the timing of sending the tare instruction information is earlier than the timing of placing the shopping basket on the placement unit 71 (if the order is sending the tare instruction information → placing the shopping basket on the placement unit 71), it will be determined to be fraudulent (putting an unscanned item into the cart 70) when the shopping basket is placed on the placement unit 71, so it is preferable to send the tare instruction information to the cart 70 as late as possible (immediately after the first item is registered, which is immediately before the first item is added. If the timing of placing the shopping basket is earlier than the timing of sending the tare instruction information (if the order is placing the shopping basket on the placement unit 71 → sending the tare instruction information), it will not be determined to be fraudulent when the shopping basket is placed on the placement unit 71. Note that if it is mistakenly determined to be fraudulent when it is not, it leaves a bad impression on the customer and requires unnecessary confirmation work by store staff (store).

[0043] As described above, the mobile terminal 60 can obtain the device identification information of each cart 70 from the beacon transmitted by each cart 70 (cart communication unit), but can also obtain the device identification information of each cart 70 from the two-dimensional code 78 affixed to each cart 70 (mobile terminal charging unit 75) and from the NFC tag 79 (IC tag communication unit) affixed to each cart 70 (holder unit 74).

[0044] In the following description, it is assumed that the mobile terminal 60 acquires device identification information of the cart 70 from the two-dimensional code 78 or the NFC tag 79. In other words, it is assumed that the mobile terminal 60 acquires device identification information of one cart 70 (the cart 70 that the customer is going to use) from the two-dimensional code 78 or the NFC tag 79 affixed to the cart 70 based on the customer's actions, connects to the cart 70 (cart communication unit) using the acquired device identification information, and becomes capable of communicating with the cart 70 (cart communication unit).

[0045] As described above, the mobile terminal 60 can monitor for fraudulent behavior during shopping (can determine whether or not fraudulent behavior has occurred) through image recognition, but can also monitor for fraudulent behavior during shopping (can determine whether or not fraudulent behavior has occurred) through collaboration (communication) with the cart 70.

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

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

[0048] The cart 70 may determine whether a product or the like has been inserted (may monitor the insertion of a product or the like). Specifically, when the cart 70 detects an increase in weight, it determines that a product or the like has been inserted. 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 been determined that a product or the like has been inserted).

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

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

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

[0052] (Adding unscanned items to cart 70) The mobile terminal 60 determines whether an unscanned product has been added to the cart 70 (monitors the addition of unscanned products to the cart 70). For example, the mobile terminal 60 receives a weighing result (the latest weighing value, the increase in the weighing value, and information indicating that there has been an increase in weight) from the cart 70 and determines that a product or the like has been added to the cart 70 based on the weighing result, but if the product was not registered prior to the reception (for example, within a predetermined time prior to the reception), the mobile terminal 60 may determine that the product has been added to the cart 70 without being scanned.

[0053] When the mobile terminal 60 determines that an item has been added to the cart 70 without being scanned, it may notify the user that an item has been added to the cart 70 without being scanned (for example, by displaying a message on the screen or by voice). For example, the mobile terminal 60 may display a message such as "Registration was not successful. Please scan the barcode again." Furthermore, when the mobile terminal 60 determines that an item has been added to the cart 70 without being scanned, it may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that an unscanned item has been added) in the transaction information of the transaction.

[0054] The cart 70 may determine whether an item has been inserted without being scanned (or may monitor the insertion of an unscanned item). In the case where the cart 70 determines whether an item has been inserted without being scanned, the mobile terminal 60 notifies the cart 70 that an item has been registered each time the item is registered. For example, if the cart 70 detects an increase in weight and determines that an item has been inserted, but does not receive a notification from the mobile terminal 60 that the item has been registered prior to the detection of the weight increase (for example, within a predetermined time prior to the detection), the cart 70 may determine that the item has been inserted without being scanned.

[0055] When the cart 70 determines that an item has been added without being scanned, it may notify the mobile terminal 60 of the determination result (information indicating that it has been determined that the item has been added without being scanned). When the mobile terminal 60 receives the notification, it may notify that an item has been added to the cart 70 without being scanned. For example, the mobile terminal 60 may display a message such as "Registration was not successful, please scan the barcode again." Furthermore, when the mobile terminal 60 receives the notification, it may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that an unscanned item has been added) in the transaction information of the transaction.

[0056] Examples of actions in which an item is added without being scanned include, for example, adding an item to cart 70 (more specifically, a shopping basket placed on mounting section 71 (described below)) without performing a scanning operation (putting an item from the display shelf into a shopping basket without making any sign of scanning), adding an item to cart 70 by intentionally performing an insufficient (inappropriate) scanning operation so that the item's barcode is not read (putting an item from the display shelf into a shopping basket while faking a scanning operation), adding a set item to cart 70 by unintentionally or intentionally reading the barcode of a single item (for example, a can of beer) rather than the barcode of a set item (for example, a six-pack of canned beer), and adding an item to cart 70 after an unintentional failed scanning operation without realizing it (a simple scanning error).

[0057] Note that weight information for each product may be stored as verification information, and a check may be performed based on the weight to see if the scanned product matches the inserted product (weight check).

[0058] (Scanned item not added to cart 70) The mobile terminal 60 determines whether the scanned product has been added to the cart 70 (monitors whether the scanned product has not been added to the cart 70). For example, if the mobile terminal 60 registers a product, but does not receive a weighing result (the latest weighing value, the amount of increase in the weighing value, and information indicating that there has been an increase in weight) from the cart 70 after the product is registered (for example, within a predetermined time from the time of product registration) and determines that the product, etc. has been added to the cart 70 based on the weighing result, the mobile terminal 60 may determine that the scanned product has not been added to the cart 70.

[0059] When the mobile terminal 60 determines that the scanned product has not been added to the cart 70, the mobile terminal 60 may notify the user that the scanned product has not been added to the cart 70. For example, the mobile terminal 60 may display "weight NG", "confirmation required", or "confirmation required (not added)" for the scanned product in the transaction details. Instead of or in addition to displaying "weight NG" or the like for the scanned product, the mobile terminal 60 may display a message such as "Please add the registered product to the shopping cart." Furthermore, when the mobile terminal 60 determines that the scanned product has not been added to the cart 70, the mobile terminal 60 may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the scanned product has not been added) in the transaction information for the transaction.

[0060] The cart 70 may determine whether the scanned product has been inserted (or may monitor whether the scanned product has not been inserted). In the case where the cart 70 determines whether the scanned product has been inserted, the mobile terminal 60 notifies the cart 70 that the product has been registered each time the product is registered. For example, if the cart 70 receives a notification from the mobile terminal 60 that the product has been registered, but does not determine that the product has been inserted after receiving the notification (for example, within a predetermined time from the time of reception) (i.e., if it does not detect an increase in weight), it may determine that the scanned product has not been inserted.

[0061] When the cart 70 determines that the scanned product has not been inserted, the cart 70 may notify the mobile terminal 60 of the determination result (information indicating that the scanned product has not been inserted). When the mobile terminal 60 receives the notification, the mobile terminal 60 may notify that the scanned product has not been inserted into the cart 70. For example, the mobile terminal 60 may display "weight NG", "confirmation required", or "confirmation required (not inserted)" for the scanned product in the transaction details. Instead of or in addition to displaying "weight NG" or the like for the scanned product, the mobile terminal 60 may display a message such as "Please put the registered product in the shopping cart." Furthermore, when the mobile terminal 60 receives the notification, the mobile terminal 60 may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the scanned product has not been inserted) in the transaction information of the transaction.

[0062] As described above, weight information for each product may be stored as verification information, and a weight check may be performed to determine whether the scanned product matches the inserted product.

[0063] (Cancelled item not removed from cart 70) The mobile terminal 60 determines whether the canceled product (product canceled by a cancellation scan or a screen operation) has been removed from the cart 70 (monitors whether the canceled product has not been removed from the cart 70). For example, if the mobile terminal 60 cancels a product, but does not receive a weighing result (the latest weighing value, the amount of decrease in the weighing value, and information indicating that there has been a weight decrease) from the cart 70 after the product is canceled (for example, within a predetermined time from the time the product was canceled) and determines based on the weighing result that the product has not been removed from the cart 70, the mobile terminal 60 may determine that the canceled product has not been removed from the cart 70.

[0064] When the mobile terminal 60 determines that the canceled item has not been removed from the cart 70, the mobile terminal 60 may notify the user that the canceled item has not been removed from the cart 70. For example, the mobile terminal 60 may display "weight NG", "confirmation required", or "confirmation required (not removed)" for the canceled item in the transaction details. Instead of or in addition to displaying "weight NG" or the like for the scanned item, the mobile terminal 60 may display a message such as "Please return the canceled item to the shelf." Furthermore, when the mobile terminal 60 determines that the canceled item has not been removed from the cart 70, the mobile terminal 60 may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the canceled item has not been removed) in the transaction information for the transaction.

[0065] The cart 70 may determine whether the canceled product has been removed (or may monitor whether the canceled product has not been removed). In the case where the cart 70 determines whether the canceled product has been removed, the mobile terminal 60 notifies the cart 70 that the product has been canceled each time the product is canceled. For example, if the cart 70 receives a notification from the mobile terminal 60 that the product has been canceled, but does not determine that the product has not been removed after receiving the notification (for example, within a predetermined time from the time of reception) (i.e., if it does not detect a decrease in weight), it may determine that the canceled product has not been removed.

[0066] When the cart 70 determines that the canceled product has not been removed, the cart 70 may notify the mobile terminal 60 of the determination result (information indicating that the canceled product has not been removed). When the mobile terminal 60 receives the notification, the mobile terminal 60 may notify that the canceled product has not been removed from the cart 70. For example, the mobile terminal 60 may display "weight NG", "confirmation required", or "confirmation required (not removed)" for the canceled product in the transaction details. Instead of or in addition to displaying "weight NG" or the like for the scanned product, the mobile terminal 60 may display a message such as "Please return the canceled product to the shelf." Furthermore, when the mobile terminal 60 determines that the canceled product has not been removed from the cart 70, the mobile terminal 60 may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the canceled product has not been removed) in the transaction information of the transaction.

[0067] Note that weight information for each product may be stored as verification information, and a weight check may be performed to determine whether the canceled product matches the removed product.

[0068] (Items removed from cart 70 not yet cancelled) The mobile terminal 60 judges whether or not a taken-out product (a product taken out of the cart 70) has been cancelled (monitors whether a taken-out product has not been taken out of the cart 70). For example, the mobile terminal 60 receives a weighing result (the latest weighing value, the amount of reduction in the weighing value, and information indicating that a weight reduction has occurred) from the cart 70 and judges that a product or the like has been taken out of the cart 70 based on the weighing result, but if the product was not cancelled before receiving the weighing result (for example, within a predetermined time prior to the time of reception), the mobile terminal 60 may determine that the taken-out product has not been cancelled.

[0069] When the mobile terminal 60 determines that the taken-out product has not been canceled, the mobile terminal 60 may notify the user that the taken-out product has not been canceled. For example, the mobile terminal 60 may display a message such as "Please cancel the order if you return the product to the shelf (if you want to stop the purchase)." Furthermore, when the mobile terminal 60 determines that the taken-out product has not been canceled, the mobile terminal 60 may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the taken-out product has not been canceled) in the transaction information of the transaction.

[0070] The cart 70 may determine whether a taken-out product has been canceled (or may monitor whether a taken-out product has not been canceled). In the case where the cart 70 determines whether a taken-out product has been canceled, 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 taken out, but does not receive a notification from the mobile terminal 60 that the product has been canceled before the weight loss is detected (for example, within a predetermined time prior to the detection), the cart 70 may determine that the taken-out product has not been canceled.

[0071] When the cart 70 determines that the taken-out product has not been canceled, it may notify the mobile terminal 60 of the determination result (information indicating that the taken-out product has not been canceled). When the mobile terminal 60 receives the notification, it may display a message such as "Please cancel if you return the product to the shelf (if you want to stop the purchase)." Furthermore, when the mobile terminal 60 determines that the taken-out product has not been canceled, it may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the taken-out product has not been canceled) in the transaction information of the transaction.

[0072] Note that weight information for each product may be stored as verification information, and a weight check may be performed to determine whether the removed product matches the canceled product.

[0073] Incidentally, although this includes the contents already explained, control may be performed as in A to F below. A: Product not registered + weight increase If an item is added to the shopping cart (if an increase in the weighing value is detected) even though it has not been registered (by scanning or operating the screen), it is determined that it has been forgotten to be registered. For example, if an item is not registered → item is added to the shopping cart → it is determined that it has been forgotten to be registered → an error (forgotten to register) is reported. If an item is registered → item is added to the shopping cart within 5 seconds → it is determined that it has not been forgotten to be registered → no error is reported. This control prevents the store from suffering disadvantages (losses).

[0074] The error notification may be, for example, a message display such as "Registration was not completed correctly, please scan the barcode again." If it is determined that registration was forgotten, instead of or in addition to the error notification, a confirmation required flag (which may be a dedicated confirmation required flag indicating that the scanned product has not been inserted) may be set in the transaction information of the transaction, and, for example, a store clerk may be called during the settlement process at the settlement device 50.

[0075] This control corresponds to the above-mentioned "putting unscanned products into the cart 70". As explained in "putting unscanned products into the cart 70", it may be determined whether the mobile terminal 60 has forgotten to register, or it may be determined whether the cart 70 has forgotten to register.

[0076] B: Product registration + no change in weight value If a product has been registered but is not added to the shopping cart (if no increase in the weighing value is detected), it is determined that the product has been forgotten to be added. For example, if a product is registered → product is not added to the shopping cart within 5 seconds → it is determined that the product has been forgotten to be added → an error (forgotten to be added) is notified. If a product is registered → product is added to the shopping cart within 5 seconds → it is determined that the product has not been forgotten to be added → no error is not notified. This control prevents customers from suffering any disadvantages.

[0077] The error notification may, for example, display "weight NG", "verification required", or "verification required (not inserted)" for the scanned item, or may display a message such as "Please put the registered item in the shopping cart." Furthermore, if it is determined that an item has been forgotten to be inserted, a confirmation required flag (which may be a dedicated confirmation required flag indicating that the scanned item has not been inserted) may be set in the transaction information of the transaction instead of or in addition to the error notification, and, for example, a store clerk may be called during the settlement process at the settlement device 50. Note that, because forgetting to insert an item is not fraud (fraud that causes a disadvantage to the store), it is not necessary to set a confirmation required flag in the transaction information of the transaction.

[0078] This control corresponds to the above-mentioned "scanned product not being put into the cart 70". As explained in "scanned product not being put into the cart 70", the mobile terminal 60 may determine whether or not the product has been put into the cart 70, or the cart 70 may determine whether or not the product has been put into the cart 70.

[0079] C: Product cancelled + no change in weight If an item is cancelled (screen operation) but the item is not removed from the shopping cart (if no decrease in weight value is detected), it is determined that the cancelled item was forgotten to be removed. For example, if an item is cancelled → item is not removed from the shopping cart within 5 seconds → it is determined that the cancelled item was forgotten to be removed → an error (cancelled item forgotten to be removed) is reported. If an item is cancelled → item is removed from the shopping cart within 5 seconds → it is determined that the cancelled item was not forgotten to be removed → no error is reported. This control prevents the store from suffering any disadvantages.

[0080] The error notification may be, for example, a message such as "Weight NG", "Confirmation required", or "Confirmation required (not removed)" for the scanned product, or a message such as "Please return the canceled product to the shelf." Furthermore, if it is determined that the canceled product was forgotten to be removed, a confirmation required flag (which may be a dedicated confirmation required flag indicating that the canceled product has not been removed) may be set in the transaction information for the transaction instead of or in addition to the error notification, and, for example, a store clerk may be called during the settlement process at the settlement device 50.

[0081] This control corresponds to the above-mentioned "cancelled product not removed from cart 70." As explained in "cancelled product not removed from cart 70," the mobile terminal 60 may determine whether the canceled product was left behind, or the cart 70 may determine whether the canceled product was left behind.

[0082] D: No product cancellation + weight reduction If an item is removed from the shopping basket even though no item was cancelled (if a decrease in the weighing value is detected), it is determined that the removed item was forgotten to be cancelled. For example, if an item is removed from the shopping basket → the item is not cancelled within 10 seconds → it is determined that the removed item was forgotten to be cancelled → an error (removed item forgotten to be cancelled) is reported. If an item is removed from the shopping basket → the item is cancelled within 10 seconds → it is determined that the removed item was not forgotten to be cancelled → no error is reported. This control prevents customers from suffering any disadvantages.

[0083] The error notification may be, for example, a message display such as "If you return the product to the shelf (if you want to stop the purchase), please cancel." Furthermore, if it is determined that the taken-out product has been forgotten to be canceled, instead of or in addition to the error notification, a confirmation required flag (which may be a dedicated confirmation required flag indicating that the taken-out product has not been canceled) may be set in the transaction information of the transaction, and, for example, a store clerk may be called during the settlement process at the settlement device 50. Note that, since forgetting to insert money is not fraud (fraud that causes a disadvantage to the store), it is not necessary to set a confirmation required flag in the transaction information of the transaction.

[0084] This control corresponds to the above-mentioned "non-cancellation of a product taken out of the cart 70." As explained in "non-cancellation of a product taken out of the cart 70," the mobile terminal 60 may determine whether or not a product to be taken out has been forgotten to be canceled, or the cart 70 may determine whether or not a product to be taken out has been forgotten to be canceled.

[0085] Also, in relation to the tare weight, for example, if the weighing value in an unloaded state is 0g and the weight of the shopping basket is 500g (known), and the weighing value when the tare instruction information is received is 3000g, the tare weight is 3000g (the tare weight is the shopping basket + the customer's baggage), but the weight of the baggage, 2500g, may be stored. In this way, even if the weighing value decreases by 2500g during shopping, it can be determined that baggage has been removed, and it may not be determined that the removed item has been forgotten to be canceled.

[0086] In addition, the control of calling a store clerk (setting the confirmation required flag) in the above A to D may be configurable for each store and for each time (time period). This allows for flexible handling of fraud and the like according to the store's policy and circumstances. For example, in cases where a product is not registered + weight value increase (A) or a product is not registered + product detected in an image or product canceled + no change in weight value (C), that is, when a product is inserted without being scanned or when a necessary product is not canceled, one efficient setting is to set the confirmation required flag and only notify an error for other events. With this setting, it is possible to reduce sales losses in the store due to non-scanning, etc., while reducing the burden on store clerks because a store clerk is not called in the case of other errors.

[0087] E: Activate the weight loss cancellation mode As also related to D above, when a decrease in the weighing value is detected, the control may be performed so as to automatically prompt the user to cancel the product. For example, when a product is removed from the shopping basket, the mobile terminal 60 displays transaction details (a list of registered products) in a selectable manner, and the selected product is determined to be the product removed from the shopping basket, and the product is canceled (deleted from transaction details, etc.). Alternatively, when a product is removed from the shopping basket, the mobile terminal 60 is switched from a registration scan mode (a normal scan mode for identifying the product to be registered) to a cancellation scan mode (a scan mode for identifying the product to be canceled), and the product whose barcode is scanned is determined to be the product removed from the shopping basket, and the product is canceled (deleted from transaction details, etc.). Note that the display of transaction details in which the product to be canceled can be selected as described above or the switching to the cancellation scan mode may be referred to as a cancellation mode (product cancellation mode). In other words, when a decrease in the weighing value is detected, the control may be automatically performed to switch to the cancellation mode. The above judgment and control may be performed by the mobile terminal 60 itself, or by the cart 70.

[0088] F: Cancel Cancel mode Removal of product from shopping basket (detection of decrease in weighing value) → storing weight of removed product (decreased weight) → control to cancel mode (display transaction details or switch to cancel scan mode) → putting product into shopping basket (detection of increase in weighing value) → the decreased weight matches the increased weight → it is determined that the product has been returned to the shopping basket → end of cancel mode (delete transaction details or switch to registration scan mode). The above judgments and controls may be performed by the mobile terminal 60 itself or by the cart 70.

[0089] The above control is such that if the weight loss and the weight increase match, it is determined that the product has been returned to the shopping cart, but if the weight increases after the weight loss, it may be determined that the product has been returned to the shopping cart. In other words, the control may be such that if the product is removed from the shopping cart (a decrease in the weight value is detected) → the control goes to the cancel mode → the product is put into the shopping cart (an increase in the weight value is detected) → it is determined that the product has been returned to the shopping cart → the cancel mode ends. In this case, it is not necessary to store the weight value.

[0090] According to the control of E and F above, the registration mode and the cancellation mode are automatically transitioned, so that, for example, the name of the mode may be displayed on the screen so that the customer can recognize it at a glance, or the screen background, etc. may be made different.

[0091] (Payment device 50) The settlement device 50 is used by a customer. Specifically, the settlement device 50 settles the items registered by 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 settlement unit, a printing unit, an audio output unit, an imaging unit, a communication unit, and a sign pole. For example, the scanner unit scans various codes (for example, a settlement code GA631 (described later), a product code, a clerk code attached to gift certificates, point cards, clerk name tags, etc.) and reads each code. For example, the settlement unit is a collective term for one or both of a cash settlement unit (change machine) that settles with cash and a non-cash settlement unit (card settlement unit, code settlement unit) that settles with non-cash (for example, credit, electronic money, etc.). For example, the display unit displays a product list screen (see FIG. 5(A)(B)(E)), etc. The settlement device 50 may further include a key operation unit consisting of one or more various operation members, a human presence sensor that detects (senses, recognizes) the presence of a person, and the like.

[0092] (Headquarters Server 10) The headquarters server 10 is a server that manages the entire sales system 1. The headquarters server 10 stores, for example, various information (for example, a product master file (product master) and the like). The product master is a file that stores product names, prices, and the like in association with product codes. The headquarters server 10 also supplies various information (for example, the product master and the like) 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 composed of multiple servers.

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

[0094] (Store Controller 30) The store controller 30 is a server that is mainly responsible for communication of information between devices installed in the store (the transaction status management device 40, the settlement device 50) and devices installed outside the store (the head office 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.

[0095] (Transaction status management device 40) The transaction status management device 40 is, for example, a device (for example, 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 operation status of the settlement device 50. The transaction status management device 40 may also monitor the processing status and operation status of the mobile terminal 60 (for example, access the cloud server 20 and display or modify the transaction information, etc. stored in the cloud server 20). The transaction status management device 40 may also monitor the status of the cart 70 (for example, access the cloud server 20 and display the status of the battery, etc. (battery 76, cart charging unit 73, mobile terminal charging unit 75) of the cart 70 transmitted via the mobile terminal 60 and stored in the cloud server 20, and various error information). The transaction status management device 40 may also access the headquarters server 10, etc., and perform maintenance (such as setting of products) of 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 storage 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 may output various information from the printing device.

[0096] The sales system 1 may include devices other than the above-mentioned devices. For example, a registration and settlement device 51 (not shown) may be installed in a store to register products based on the customer's operation and settle the payment based on the customer's operation. Although not shown, the registration and settlement device 51 includes a CPU, a memory unit, a display unit, a scanner unit, a settlement unit (one or both of a cash settlement unit and a non-cash settlement unit), a printing unit, a voice output unit, an imaging unit, a communication unit, and a sign pole. For example, the scanner unit scans various codes (for example, product codes, clerk codes attached to gift certificates, point cards, clerk name tags, etc.) and reads each code. For example, the display unit displays a registration screen (not shown) and a settlement screen (not shown). The registration and settlement device 51 may further include a key operation unit consisting of one or more various operation members, a human presence sensor that detects the presence of a person, etc.

[0097] The sales system 1 may also be provided with a registration and settlement device 52 (not shown) in a store that has a clerk display unit, a scanner unit, etc. on one side (clerk side) and a customer display unit and a settlement unit (one or both of a cash settlement unit and a non-cash settlement unit) on the other side (customer side; opposite to the clerk side), registering products based on the operation of a clerk and settling based on the operation of a customer. The store may also be provided with a registration and settlement device 53 (not shown) in a store that has a clerk display unit, a clerk registration unit, etc. on one side and a customer display unit, a customer registration unit and a settlement unit (one or both of a cash settlement unit and a non-cash settlement unit) on the other side, and has a normal mode (similar to the registration and settlement device 52, in which products are registered based on the operation of a clerk and settlement is based on the operation of a customer) and a full self-service mode (similar to the registration and settlement device 51, in which products are registered based on the operation of a customer and settlement is based on the operation of the customer). When registration and settlement device 51 (as well as registration and settlement device 52 and registration and settlement device 53) is installed within a store, it is connected to LAN 19 so as to be able to communicate with devices installed within or outside the store.

[0098] Fig. 3 is a display example of the mobile terminal 60. Specifically, Fig. 3 is a display example when the mobile terminal 60 connects to the cart 70 using a two-dimensional code 78. It is assumed that the application A has already been installed in the mobile terminal 60.

[0099] Fig. 3(A) is an initial screen (standby screen, a screen in which application A and other applications are not being executed) of the mobile terminal 60. On the initial screen of Fig. 3(A), an icon of application A (designated A in the figure) is displayed in a normal state.

[0100] Fig. 3(B) is a menu screen (start screen) displayed immediately after the application A is started. For example, when the icon of the application A on the initial screen (Fig. 3(A)) is operated, the mobile terminal 60 displays a menu screen as shown in Fig. 3(B). On the menu screen shown in Fig. 3(B), various buttons are displayed in an operable manner, for example, a start shopping with cart use button BT610A that accepts an operation to start shopping using the cart 70, and a start shopping without cart use button BT610B that accepts an operation to start shopping without using the cart 70. At the bottom of the menu screen, a related information display area HR601 that displays related information is provided.

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

[0102] FIG. 3(D) is a registration screen (initial registration screen) that is displayed after the connection to the cart 70 (connection using device identification information acquired from the two-dimensional code 78) is completed. The upper part of the registration screen is a captured image display area HR621 that mainly displays a captured image. The center of the captured image display area HR621 is a barcode reading area suitable for reading a barcode (a rectangular area with a message "Please hold the barcode over the screen" displayed in the center). The lower part of the registration screen is a registration information display area HR622 that mainly displays product registration information and total information. In addition, an explanatory image GA624 that explains how to register a product is displayed on the initial registration screen shown in FIG. 3(D). Note that the explanatory image GA624 may be set not to be displayed on the initial registration screen from the next time onwards.

[0103] The initial registration screen shown in Fig. 3(D) is a screen that is displayed after the connection with the cart 70 is completed, and therefore displays a cart image GA625 indicating that the cart 70 is currently connected (communication is possible). The same is true for other screens (registration screens in Figs. 3(E) to 3(G)) during the connection with the cart 70.

[0104] After the cart use no shopping start button BT610B is operated, the mobile terminal 60 displays an initial registration screen (not shown) instead of displaying the connection code reading instruction screen (FIG. 3(C)). The initial registration screen (not shown) displayed after the cart use no shopping start button BT610B is operated, and other screens (not shown) transitioning from the initial screen are not screens displayed while connected to the cart 70, so the cart image GA625 is not displayed.

[0105] In addition, in the image captured looking down towards the shopping basket from the position of the holder portion 74, when a scanning operation is not being performed, the shopping basket and items already added to the shopping basket are captured, and when a scanning operation is being performed, the item that is the target of the scanning operation and the shopping basket and items already added to the shopping basket behind the target item are captured. However, in Figure 3(D) (as well as Figures 3(E) to 3(G), Figures 4(D) to 4(G), Figures 5(C) and Figure 5(D)), for the sake of simplicity, items other than the item that is the target of the scanning operation (the shopping basket and items already added to the shopping basket, etc.) are not shown.

[0106] Fig. 3(E) is a registration screen after registering products. Specifically, when registering XX bread as the first product and XX oolong tea as the second product, the mobile terminal 60 displays the registration screen as shown in Fig. 3(E).

[0107] In the captured image display area HR621 of the registration screen in Fig. 3(E), XX Oolong Tea is displayed (captured). That is, Fig. 3(E) shows a scene immediately after XX Oolong Tea is registered (immediately after the barcode of XX Oolong Tea is scanned), that is, a scene before XX Oolong Tea is put into the cart 70 (more specifically, a shopping basket or the like placed on the placement section 71).

[0108] The registration information display area HR622 of the registration screen in Fig. 3(E) displays information about the registered product (product name, quantity, price). Specifically, "XX bread, 1 piece, 220 yen" is displayed as the first product, and "XX oolong tea, 1 piece, 150 yen" is displayed as the second product. The mobile terminal 60 may register the product by inquiring (sending a product code acquired by scanning a barcode) to another device (e.g., cloud server 20) that stores the product master, or may store the product master in a storage unit of the mobile terminal and register the product by referring to the product master of the mobile terminal.

[0109] In the registration information display area HR622 on the registration screen, the "Weight OK" is displayed in the "XX Bread" field. Since the "XX Oolong Tea" has not been added to cart 70, the "Weight OK" is not displayed in the "XX Oolong Tea" field.

[0110] After registering one item of merchandise, the mobile terminal 60 can accept an operation to proceed to checkout (payment) (i.e., to end shopping (product registration)). Therefore, on the registration screen (captured image display area HR621) shown in Fig. 3(E), a Proceed to Checkout button BT626 that accepts an operation to proceed to checkout is displayed in an operable manner, and an explanation image GA627 that explains the Proceed to Checkout button BT626 is displayed.

[0111] Fig. 3(F) is a display example in the case where XX Oolong Tea is put into the cart 70 from the scene in Fig. 3(E) and a weighing result (weight value, etc.) is received from the cart 70. When the weighing result is received from the cart 70, the mobile terminal 60 displays "Weight OK" in the column for XX Oolong Tea in the registration information display area HR622, as shown in Fig. 3(F).

[0112] Fig. 3(G) is a display example in the case where XX Oolong Tea has not been put into the cart 70 from the scene in Fig. 3(E). If the mobile terminal 60 does not receive the weighing result from the cart 70 (within a predetermined time), it displays "Weight NG" in the column for XX Oolong Tea in the registration information display area HR622, as shown in Fig. 3(G).

[0113] The mobile terminal 60 displays "Weight OK" when it receives the weighing result from the cart 70, and displays "Weight NG" when it does not receive the weighing result from the cart 70, so "Weight OK" and "Weight NG" are information on the weighing result (information based on whether or not the weighing result has been received, information according to the weighing of the cart 70). The cart image GA625 is also one piece of information on the weighing result.

[0114] Fig. 3(H) is a settlement code display screen that is displayed after the Proceed to Checkout button BT626 is operated. The settlement code display screen shown in Fig. 3(H) displays a settlement code GA631 (described later), a message MS632 that instructs the settlement machine (settlement device 50) to read the settlement code GA631, and an explanatory image GA633 that explains how to read the settlement code GA631 in the settlement machine. In addition, the settlement code display screen shown in Fig. 3(H) displays a Return to Shopping button BT639 that can be operated. When the Return to Shopping button BT639 is operated, the registration screen before the Proceed to Checkout button BT626 was operated is displayed.

[0115] The settlement code GA631 is a two-dimensional code of transaction identification information for identifying transaction information of the transaction from among a plurality of pieces of transaction information (including weight OK / weight NG information) stored in the cloud server 20. In other words, the settlement code GA631 displayed by a certain mobile terminal 60 is information for identifying the transaction information of the mobile terminal 60 (transaction information of a commodity registered by the mobile terminal 60) from among a plurality of pieces of transaction information stored in the cloud server 20. The settlement device 50 that reads the settlement code GA631 displayed by a certain mobile terminal 60 acquires (receives) the transaction information of the mobile terminal 60 from the cloud server 20. The settlement code GA631 may be a two-dimensional code of location information of the transaction information of the mobile terminal 60 (a storage location in the sales system 1, such as a Uniform Resource Identifier (URI)).

[0116] Fig. 4 is a display example of the mobile terminal 60. Specifically, Fig. 4 is a display example when the mobile terminal 60 connects to the cart 70 using the NFC tag 79. It is assumed that the application A has already been installed in the mobile terminal 60.

[0117] Fig. 4(A) is an initial screen of the mobile terminal 60. The initial screen shown in Fig. 4(A) is similar to the initial screen shown in Fig. 3(A), and therefore a description thereof will be omitted.

[0118] FIG. 4(B) is a connection completion screen that is displayed after the connection with the cart 70 (connection using device identification information acquired from the NFC tag 79) is completed. As shown in FIG. 4(B), the connection completion screen displays (places) a launch reception section (launch reception area; reference symbol B in the figure) instead of the icon of app A. The launch reception section is an area where app A is launched by operation, similar to the icon of app A. The launch reception section is larger in size than the icon of app A.

[0119] In FIG. 4B, an example in which the start reception section is displayed instead of the icon of the app A has been described, but the icon of the app A may be made inoperable by displaying the start reception section at a position where the icon of the app A is not visible (in front of the icon of the app A). ​​Alternatively, the start reception section (symbol B) may be an enlarged display of the icon of the app A (symbol A). In other words, when the mobile terminal 60 completes the connection with the cart 70, the icon of the app A may change from the normal state (symbol A) to the enlarged state (symbol B). In addition, the start reception section (symbol B) may be displayed at a position where the icon of the app A is visible, separately from the icon of the app A (symbol A), so that the icon of the app A may remain operable even after the start reception section is displayed.

[0120] FIG. 4(C) is a menu screen (start screen) displayed immediately after the application A is started. For example, when the start reception part of the connection completion screen (FIG. 4(B)) is operated (for example, tapped, etc.), the mobile terminal 60 displays a menu screen as shown in FIG. 4(C). On the menu screen shown in FIG. 4(C), a cart image GA625 is displayed indicating that the cart 70 is connected (communication is possible). This is the same for other screens (registration screens in FIG. 4(D) to FIG. 4(G)) in the state of connection with the cart 70. Also, on the menu screen shown in FIG. 4(C), various buttons, for example, a shopping start button BT610 that receives an operation to start shopping, are displayed in an operable manner. At the bottom of the menu screen, a related information display area HR601 that displays related information is provided.

[0121] Fig. 4(D) is a registration screen (initial registration screen before registering one item) that is displayed after operating the shopping start button BT610. The initial registration screen shown in Fig. 4(D) is the same as the initial registration screen shown in Fig. 3(D), so a description thereof will be omitted.

[0122] If connection to the cart 70 is not possible, the icon (symbol A) of app A in FIG. 4(A) is operated, and the menu screen (FIG. 4(C)) is displayed (however, the cart image GA625 is not displayed). After the shopping start button BT610 is operated, the mobile terminal 60 may display, for example, a message such as "Do you want to shop using the cart?" and a button to accept an operation to shop using the cart 70, and if an operation to shop using the cart 70 is accepted, the mobile terminal 60 may retry connection to the cart 70.

[0123] Fig. 4(E) is a registration screen after registering products. Specifically, when registering XX bread as the first product and XX oolong tea as the second product, the mobile terminal 60 displays a registration screen as shown in Fig. 4(E). The registration screen shown in Fig. 4(E) is similar to the registration screen shown in Fig. 3(E), and therefore a description thereof will be omitted.

[0124] Fig. 4(F) is a display example when XX Oolong Tea is added to cart 70 from the scene of Fig. 4(E) and a weighing result (weighing value, etc.) is received from cart 70. Fig. 4(G) is a display example when XX Oolong Tea is not added to cart 70 from the scene of Fig. 4(E). The registration screens shown in Figs. 4(F) and (G) are similar to the registration screens shown in Figs. 3(F) and (G), respectively, and therefore description thereof will be omitted.

[0125] Fig. 4(H) is the settlement code display screen that is displayed after pressing the Proceed to Checkout button BT626. The settlement code display screen shown in Fig. 4(H) is the same as the settlement code display screen shown in Fig. 3(H), so a description thereof will be omitted.

[0126] FIG. 5 is a display example of the settlement device 50, etc. FIG. 5(A) is a product list screen proceeded to from the scene of FIG. 3(F) (or FIG. 4(F)) (when both the weight of the XX bread and the XX oolong tea are OK). FIG. 5(B) is a product list screen proceeded to from the scene of FIG. 3(G) (or FIG. 4(G)) (when the weight of the XX bread is OK and the weight of the XX oolong tea is NG). In other words, when a customer operates the button BT626 to proceed to checkout from the scene of FIG. 3(F) (or FIG. 4(F)) and has the settlement device 50 (scanner unit of the settlement device 50) read the settlement code GA631 displayed on the mobile terminal 60 by this operation, the settlement device 50 displays the product list screen as shown in FIG. 5(A). Furthermore, when a customer operates the button BT626 to proceed to checkout from the scene of Figure 3(G) (or Figure 4(G)) and has the settlement code GA631 displayed on the mobile terminal 60 by this operation read by the settlement device 50 (the scanner unit of the settlement device 50), the settlement device 50 will display a product list screen such as that shown in Figure 5(B).

[0127] The settlement device 50 may determine whether the transaction information (transaction information received from the cloud server 20) includes a confirmation required flag, and if the confirmation required flag is included, may notify the transaction status management device 40 that the transaction requires confirmation along with the device identification information of the settlement device 50. The store clerk operating the transaction status management device 40 visits the settlement device 50, confirms the details of the fraud, etc. in the transaction, and takes necessary measures (for example, registering unscanned products on a maintenance screen for store clerks or a screen transitioning from the maintenance screen). The cloud server 20, instead of the settlement device 50, may determine whether the transaction information (transaction information sent to the settlement device 50) includes a confirmation required flag, and if the confirmation required flag is included, may notify the transaction status management device 40 that the transaction requires confirmation along with the device identification information of the settlement device 50.

[0128] If the transaction information includes a confirmation required flag, the settlement device 50 may not complete the settlement process until the necessary processing is performed (until the cause of the fraud or other fraud is identified and the fraud or other situation is resolved). For example, the settlement device 50 may not accept the operation of the checkout button.

[0129] Furthermore, when identifying the cause of fraud or resolving the situation, the store clerk checks information such as "weight NG", and may also display images captured for a certain period of time when the confirmation required flag was set as information to assist the store clerk. For example, the settlement device 50 may display three still images (or a moving image including the timing of product insertion) of an unscanned product before, during, and after it is inserted into the cart on a maintenance screen or the like. The settlement device 50 may also display two still images (or a moving image including the timing of product cancellation) of an unscanned product before and after it is canceled (five seconds after the product is canceled) on a maintenance screen or the like. This allows the store clerk to easily find the relevant product (for example, an unscanned product to be registered, or a canceled product to be removed) from the customer's shopping cart. Furthermore, the store clerk may compare the number of items with the number of items registered in the transaction details, and if there is a mismatch, register (increase quantity) or cancel (decrease quantity) the item, thereby matching the contents of the transaction details with the contents of the shopping cart and resolving any fraudulent situations. Note that the still images and moving images described above are captured images (one piece of verification information) captured by the mobile terminal 60, and the mobile terminal 60 transmits the captured images to the cloud server 20, which then transmits them to the settlement device 50.

[0130] 5(C) and 5(D) are examples of other registration screens displayed by the mobile terminal 60, which will be described in detail later. FIG. 5(E) is an example of another product list screen displayed by the settlement device 50, which will be described in detail later.

[0131] The flow from reading the payment code GA631 to displaying the product list screen is, for example, as follows. (1) The settlement device 50 reads the settlement code GA631 displayed on the mobile terminal 60 and transmits request information to the cloud server 20, including transaction identification information obtained from the settlement code GA631 (transaction identification information that identifies the transaction information of the mobile terminal 60). (2) The cloud server 20, which has received the request information from the settlement device 50, generates a product list screen reflecting the contents of the transaction information identified by the transaction identification information included in the request information (i.e., a product list screen that displays a list of information about the products registered by the mobile terminal 60 (including information about the weighing results ("Weight OK" or "Weight NG"))) and transmits the screen information of the product list screen to the settlement device 50. (3) The settlement device 50 receives the screen information from the cloud server 20 and displays a product list screen on the display unit based on the screen information.

[0132] At the time when the settlement device 50 reads the settlement code GA631 of a certain mobile terminal 60 and transmits request information to the cloud server 20, the cloud server 20 only needs to store transaction information regarding all of the products registered by that mobile terminal 60. In other words, there is no particular limit to the timing at which the cloud server 20 starts to store the transaction information of the mobile terminal 60. In other words, the mobile terminal 60 may transmit information regarding each product (including information regarding the weighing result) to the cloud server 20 each time the mobile terminal 60 registers the product, or may transmit information regarding all of the products registered up to that point together to the cloud server 20 based on the operation of the Proceed to Checkout button BT626 (when the settlement code GA631 is displayed).

[0133] Fig. 6 is a flowchart explaining an example of the operation of the mobile terminal 60. Specifically, the flowchart in Fig. 6 shows the flow from when a customer comes to the store with the mobile terminal 60 and the mobile terminal 60 connects to the cart 70 using the two-dimensional code 78 until the settlement code display screen (Fig. 3(H)) is displayed. Note that when this flowchart is started (when the customer comes to the store), the mobile terminal 60 is assumed to be displaying the initial screen (Fig. 3(A)).

[0134] Step S1: The mobile terminal 60 accepts an operation to start up the application A. For example, the mobile terminal 60 accepts an operation on the application icon (symbol A) of the application A on the initial screen (FIG. 3(A)). Step S2: The mobile terminal 60 displays the menu screen (FIG. 3(B)). Step S3: The mobile terminal 60 accepts an operation to start shopping using the cart 70. For example, the mobile terminal 60 accepts an operation of the shopping start with cart button BT610A on the menu screen (FIG. 3(B)). Step S4: The portable terminal 60 displays a connection code reading instruction screen (FIG. 3(C)).

[0135] Step S5: The mobile terminal 60 determines whether or not connection information (device identification information of the cart 70) for connecting to the cart 70 has been acquired. For example, if the mobile terminal 60 reads the two-dimensional code 78 affixed to the cart 70 based on the customer's operation, the mobile terminal 60 acquires connection information for the cart 70 from the two-dimensional code 78. If connection information has been acquired (step S5: YES), the process proceeds to step S6. If connection information has not been acquired (step S5: NO), step S5 is repeated.

[0136] Step S6: The mobile terminal 60 pairs with and connects to the cart 70. Step S7: The mobile terminal 60 transmits tare subtraction instruction information to the cart 70. Step S8: The mobile terminal 60 transmits information about the cart 70 to the cloud server 20. For example, the mobile terminal 60 receives information about the cart 70 from the cart 70, such as the cart number of the cart 70, the status of the battery, and various error information, and transmits it to the cloud server 20. This enables the administrator to monitor the information about the cart 70, for example, in the transaction status management device 40, and perform necessary maintenance on the cart 70 as appropriate. Step S9: The mobile terminal 60 displays the initial registration screen (FIG. 3(D)).

[0137] In step S8 (similar to step S33 in FIG. 7), the information about the cart 70 received from the cart 70 is transmitted to the cloud server 20, so the cart 70 itself does not need to have the function of communicating with the cloud server 20, and the cart 70 can be realized at low cost.

[0138] Furthermore, when the mobile terminal 60 acquires the connection information from the cart (step S5: YES) but fails to connect to the cart 70 for some reason, the cart 70 can be uniquely identified from the connection information, so that the mobile terminal 60 may transmit connection failure information to the cloud server 20 as information related to the cart 70. This allows the information on the connection relationship (cart communication unit) to be provided to the administrator, and maintenance can be performed. Furthermore, when the mobile terminal 60 fails to connect to the cart 70 for some reason, instead of or in addition to transmitting the connection failure information to the cloud server 20, the mobile terminal 60 may output (screen display, voice output) a message such as, for example, "The cart may be out of order. Please use another cart." The same applies to the case of connecting to the cart 70 using the NFC tag 79 (also in the flowchart of FIG. 7).

[0139] The order of steps S7 to S9 is not particularly limited. In other words, the mobile terminal 60 only needs to transmit tare instruction information to the cart 70 based on the connection with the cart 70, transmit information related to the cart 70 to the cloud server 20, and display the initial registration screen, and the order is not particularly limited.

[0140] Step S10: The mobile terminal 60 judges whether the barcode of the product has been read by the customer's scanning operation. If it has been read (Step S10: YES), the process proceeds to Step S11. If it has not been read (Step S10: NO), the process repeats Step S10.

[0141] Step S11: The mobile terminal 60 registers the product (the product whose barcode was read in step S10). The mobile terminal 60 displays (adds) the information about the product (product name, quantity, price) in the registration information display area HR622 of the registration screen, and updates the total information. Step S12: The mobile terminal 60 receives the weighing result (weighing value) from the cart 70. That is, the product (the product registered in step S11) is added to the cart 70, weighed by the cart 70, and the weighing result is transmitted from the cart 70 to the mobile terminal 60. Step S13: The mobile terminal 60 displays information about the weighing result (for example, "Weight OK") in the registration information display area HR622 (the field for the relevant product) on the registration screen.

[0142] Step S14: The mobile terminal 60 judges whether or not the barcode of the product has been read by the customer's scanning operation. If it has been read (Step S14: YES), the process returns to Step S11. If it has not been read (Step S14: NO), the process proceeds to Step S15. Step S15: The mobile terminal 60 judges whether or not to end the registration. For example, if the "Proceed to Checkout" button BT626 is operated, the mobile terminal 60 judges to end the registration. If the registration is to be ended (Step S15: YES), the mobile terminal 60 proceeds to Step S16. If the registration is not to be ended (Step S15: NO), the mobile terminal 60 returns to Step S14.

[0143] Step S16: The mobile terminal 60 cuts off the connection with the cart 70 and cancels the pairing. Step S17: The mobile terminal 60 displays the settlement code display screen (FIG. 3(H)).

[0144] In this flowchart, the mobile terminal 60 receives the weighing result (weighing value) from the cart 70 within a predetermined time from product registration (step S12) and displays "Weight OK" as information related to the weighing result (information based on whether or not the weighing result has been received) in step S13. However, if the mobile terminal 60 does not receive the weighing result from the cart 70 within a predetermined time from product registration, it displays "Weight NG" as information related to the weighing result in step S13.

[0145] Furthermore, in this flowchart, the flow of receiving the weighing result (weighing value) from the cart 70 (step S12) has been described, but the mobile terminal 60 may also receive a judgment result (information indicating that it has been determined that a product or the like has been inserted) from the cart 70. In other words, if the mobile terminal 60 receives the above judgment result from the cart 70 within a predetermined time from product registration in step S12, it may display "weight OK" in step S13 as information on the judgment result (information based on whether or not the judgment result has been received), and if the mobile terminal 60 does not receive the above judgment result from the cart 70 within a predetermined time from product registration, it may display "weight NG" in step S13 as information on the judgment result.

[0146] Fig. 7 is a flowchart for explaining an example of the operation of the mobile terminal 60. Specifically, the flowchart in Fig. 7 shows the flow from when a customer comes to the store with the mobile terminal 60 and the mobile terminal 60 connects to the cart 70 using the NFC tag 79 until the settlement code display screen (Fig. 4(H)) is displayed. It is assumed that when this flowchart is started (when the customer comes to the store), the mobile terminal 60 is displaying the initial screen (Fig. 4(A)).

[0147] Step S31: The mobile terminal 60 determines whether or not it has received connection information (device identification information of the cart 70) for connecting to the cart 70. For example, when a customer sets the mobile terminal 60 in the cart 70 (holder unit 74), it receives connection information for the cart 70 (set cart 70) from the NFC tag 79 (IC tag communication unit) affixed to the cart 70 (holder unit 74). If it has received connection information (step S31: YES), it proceeds to step S32. If it has not received connection information (step S31: NO), it repeats step S31.

[0148] Step S32: The mobile terminal 60 pairs with and connects to the cart 70. Step S33: The mobile terminal 60 transmits information about the cart 70 to the cloud server 20. This enables the administrator to monitor the information about the cart 70, for example, in the transaction status management device 40, and perform necessary maintenance on the cart 70 as appropriate.

[0149] Note that, if the mobile terminal 60 receives connection information from the cart (step S31: YES) but fails to connect to the cart 70, the cart 70 can be uniquely identified from the connection information, so connection failure information may be transmitted to the cloud server 20 as information related to the cart 70. Information on the connection relationship (cart communication unit) can also be provided to the administrator so that maintenance can be performed.

[0150] Step S34: The mobile terminal 60 displays a connection completion screen (FIG. 4(B)). Step S35: The mobile terminal 60 accepts an operation to start the application A. For example, the mobile terminal 60 accepts an operation on the start acceptance section (reference B) of the connection completion screen (FIG. 4(B)). Step S36: The mobile terminal 60 displays the menu screen (FIG. 4(C)). Step S37: The mobile terminal 60 accepts a shopping start operation. For example, the mobile terminal 60 accepts an operation of the shopping start button BT610 on the menu screen (FIG. 4(C)). Step S38: The mobile terminal 60 transmits tare subtraction instruction information to the cart 70. Step S39: The mobile terminal 60 displays the initial registration screen (FIG. 4(D)).

[0151] Hereinafter, steps S40 to S47 in FIG. 7 are similar to steps S10 to S17 in FIG. 6, and therefore the description will be omitted.

[0152] (If the connection to Cart 70 is lost during product registration) During product registration (after operating the Start Shopping button BT610 and before operating the Proceed to Checkout button BT626), the connection with the cart 70 may be disconnected. The connection will be disconnected when the mobile terminal 60 is removed from the cart 70 and moved some distance away from the cart 70 (note that if Bluetooth is set to inactive in the settings on the mobile terminal 60, the connection will also be disconnected if the mobile terminal 60 or cart 70 malfunctions or is turned off). When the connection is disconnected, an attempt is made to reconnect in the background, so it will be reconnected if the distance becomes shorter.

[0153] If the mobile terminal 60 is disconnected from the cart 70 during product registration, the mobile terminal 60 can continue to register the product. For example, even if the connection to the cart 70 is disconnected after the registration of the first item, XX bread, the second item, XX oolong tea, can be registered as shown in Fig. 5(C) and Fig. 5(D). Note that Fig. 4(C) shows a scene immediately after the registration of XX oolong tea (immediately after the barcode of XX oolong tea is scanned) (a scene before XX oolong tea is added to the cart 70), and Fig. 5(D) shows a scene after XX oolong tea is added to the cart 70.

[0154] The registration screens shown in Fig. 5(C) and Fig. 5(D) do not display a cart image GA625 indicating that the cart 70 is connected. In addition, the column for XX Oolong Tea displays a message indicating that the cart 70 is not connected (message "Not connected"). Note that the mobile terminal 60 may display a message indicating that there has been no weighing check (e.g., messages "No weight confirmation" or "No check") instead of or in addition to a message indicating that there is no connection to the cart 70.

[0155] Similar to the information on the weighing result (weight OK, weight NG) when connected to the cart 70 shown in Figures 3(F)(G) and 4(F)(G), information on the disconnection (not connected, weight not confirmed, no check) is also sent as transaction information to the cloud server 20 and the settlement device 50. Figure 5(E) is a product list screen proceeding from the scene in Figure 5(D). "Not connected" is displayed in the column for XX Oolong Tea on the product list screen shown in Figure 5(E).

[0156] The embodiment has been described above. According to the embodiment, a system in which customers themselves register products can be more suitably implemented.

[0157] For example, a customer using a shopping cart can register products using his / her own mobile terminal 60. Also, the store does not need to provide the shopping cart with a scanner function, a detail display function, etc., and can allow the customer to register products using the mobile terminal 60.

[0158] Connection with a shopping cart is also easy. In other words, in the case of a method of pairing based on a beacon, the shopping carts before use are all placed in one place, so that the connection information of multiple available shopping carts is displayed on the screen of the mobile terminal, and it is difficult to know which is the connection information of a specific (desired) shopping cart, making connection troublesome, but in the case of the embodiment, if the two-dimensional code 78 of a specific shopping cart is read using the mobile terminal 60, the connection information of the cart 70 is obtained from the two-dimensional code 78 and automatically connected, or if the mobile terminal 60 is set in a specific shopping cart, the connection information of the cart 70 is obtained from the NFC tag 79 and automatically connected, so there is no hassle.

[0159] Information on the connection status with the shopping cart and the weighing result (for example, cart image GA625, not connected, weight not confirmed, no check, weight OK, weight NG) is notified, so it can be easily recognized. In other words, it is possible to appropriately monitor for fraud, etc.

[0160] (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, for example, the following (1) to (24). In addition, the following (1) to (24) may be appropriately combined with each other.

[0161] (1) In the above embodiment, an example of registering a product by reading a barcode with an imaging unit has been described, but the method of product registration is not limited to this. For example, a button (product preset button) corresponding to each product may be displayed on a registration screen (including an initial registration screen), and the product may be registered by operating the product preset button. Note that the number of already registered products (products registered by reading a barcode, products registered by operating a product preset button) can be increased via the registration screen (for example, by operating the "x1" part shown in FIG. 3(F) etc.), but this addition can also be considered as product registration of the same product.

[0162] As the concept of product registration expands, for example, "adding an unscanned product to cart 70" is redefined as "adding an unregistered product to cart 70." However, if a product has been registered using a product preset button or by adding a quantity, adding a product after that will not be considered as "adding an unregistered product to cart 70," just as in the case of registering a product by reading a barcode.

[0163] (2) In the above embodiment, the cart image GA625 indicating that the cart 70 is connected (communicable) is displayed in the captured image display area HR621. However, the cart image GA625 may be displayed in a position that does not interfere with the display of the captured image (through image) (visual recognition of the captured image). For example, the cart image GA625 may be displayed in the related information display area HR601 at the bottom of the screen.

[0164] (3) In the above embodiment, an example has been described in which the cart image GA625 actively notifies the customer that the cart 70 is currently connected (an example in which the customer can recognize that the cart 70 is currently connected by looking at the cart image GA625), but it is not necessary to actively notify the customer. For example, the customer may be notified that the cart 70 is currently connected by changing the display color (background color, etc.) of part or all of the related information display area HR601. In other words, the customer may not be made aware of whether or not the cart 70 is currently connected.

[0165] (4) In the above embodiment, an example has been described in which the two-dimensional code 78 is affixed to the mobile terminal charging unit 75. However, the two-dimensional code 78 may be affixed to a location other than the mobile terminal charging unit 75. One or more two-dimensional codes 78 may be affixed to a location other than the mobile terminal charging unit 75 of the cart 70. The two-dimensional code 78 may be affixed on the NFC tag 79 (i.e., overlapping the NFC tag 79).

[0166] (5) In the above embodiment, an example was described in which one NFC tag 79 was affixed to holder unit 74. However, two or more NFC tags 79 may be affixed to holder unit 74, and instead of or in addition to affixing one or more NFC tags 79 to holder unit 74, one or more NFC tags 79 may be affixed to a location other than holder unit 74 of cart 70.

[0167] This is also related to (4) and (5) above, but if the mobile terminal 60 connects to the cart 70 using the two-dimensional code 78 but does not connect to the cart 70 using the NFC tag 79, it is not necessary to affix the NFC tag 79 to the cart 70. Also, if the mobile terminal 60 connects to the cart 70 using the NFC tag 79 but does not connect to the cart 70 using the two-dimensional code 78, it is not necessary to affix the two-dimensional code 78 to the cart 70.

[0168] (6) In the above embodiment, it was explained that operating the icon of app A transitions to the menu screen (Figure 3 (B)). However, when app A is launched, it may compare the location information (GPS information) of its own mobile terminal 60 with the location information of the target store (the store being visited) (the location information of the target store among the location information of each store monitored by sales system 1) to determine whether it is within the store entry range, and display the menu screen if it determines that it is within the store entry range. App A may also determine that it is within the store entry range when it receives a beacon (wireless LAN, etc.) of the target store (the store being visited).

[0169] (7) In the above embodiment, as a display example when connecting to the cart 70 using the NFC tag 79, an example of transition from the initial screen (FIG. 4(A)) to the connection completion screen (FIG. 4(B)) to the menu screen (FIG. 4(C)) has been described, but the transition may be from the initial screen (FIG. 4(A)) to the menu screen (FIG. 4(C)). In other words, the mobile terminal 60 may launch the app A by connecting to the cart 70 and display the menu screen.

[0170] (8) In the above embodiment, an example was described in which the registration screen of the mobile terminal 60 and the product list screen of the settlement device 50 displayed information on the weighing result (e.g., "weight OK", "weight NG", "weight not confirmed", "not checked", etc.) and information on the connection to the cart 70 at the time of registration (e.g., "not connected"), but the settlement device 50 may issue a receipt on which the information on the weighing result and the information on the connection to the cart 70 at the time of registration are printed, or may generate electronic receipt information including the information. The information on the weighing result and the information on the connection to the cart 70 at the time of registration may be recorded in the transaction history (log) or electronic journal. Furthermore, the judgment result based on the captured image (e.g., the judgment result of putting an unscanned product that may be fraudulent into the cart 70 or not canceling a product removed from the cart 70, and further the judgment result of not removing a canceled product that is not fraudulent from the cart 70 or not putting a scanned product into the cart 70) may also be stored as the transaction history or electronic journal. Fraud detection based on measurements and fraud detection based on images can be compiled in various ways, such as by customer type, day, month, year, or store, and can also be used as an indicator for store management.

[0171] (9) In the above embodiment, an example was described in which information on the weighing result and the connection status with the cart 70 at the time of registering the products were notified for each product, but information on the connection status with the cart 70 at the time of registering the products was notified for each transaction. For example, when the number of the "specific products" described below is equal to or greater than a predetermined number, a message indicating that the number of specific products is equal to or greater than a predetermined number may be displayed in a predetermined location (e.g., the upper part) of a predetermined screen (e.g., the registration screen of the mobile terminal 60, the settlement code display screen of the mobile terminal 60, or the product list screen of the settlement device 50). The specific products are products that require confirmation (products with a confirmation flag set) such as unscanned inserted products and uncancelled removed products, or products that are "unconnected (weight not confirmed, not checked)". The specific products may be limited to products that may cause a disadvantage (loss) to the store (i.e., for example, products that are forgotten to be inserted after product registration and products that are forgotten to be removed after product cancellation may be excluded from the "specific products"). The fact that the number of specific products is equal to or greater than a predetermined number (the same applies to the fact that the total amount of specific products is equal to or greater than a predetermined amount, as described below) may be recorded in the transaction history or electronic journal.

[0172] If the total price of specific products is equal to or greater than a predetermined amount, a message indicating that the total price of the specific products is equal to or greater than a predetermined amount may be displayed in a predetermined location on a predetermined screen. If the ratio of specific products to all products (the ratio of the number of products or the ratio of the price) is equal to or greater than a predetermined ratio, a message indicating that the total price of the specific products is equal to or greater than a predetermined amount may be displayed in a predetermined location on a predetermined screen.

[0173] If the number of specific items is equal to or greater than a predetermined number (or if the total amount of the specific items is equal to or greater than a predetermined amount, or if the ratio of the specific items to the total items (proportion of the number or proportion of the amount) is equal to or greater than a predetermined ratio), the settlement device 50 may light up a sign pole to notify this fact, or may transmit information to notify this fact to the transaction status management device 40 or the store clerk's mobile terminal.

[0174] The settlement device 50 may issue a receipt printed with information indicating that the number of specific items was a predetermined number or more (or that the total amount of the specific items was a predetermined amount or more, or that the ratio of the specific items to the total items (proportion of number or proportion of amount) was a predetermined ratio or more), or may generate electronic receipt information including that information.

[0175] An exit gate device is installed in the store, and when the number of specific items is equal to or exceeds a predetermined number (or when the total amount of the specific items is equal to or exceeds a predetermined amount, or when the ratio of the specific items to the total items (ratio of number or ratio of amount) is equal to or exceeds a predetermined ratio), the exit gate device may notify this fact with sound or light, or may restrict passage. Note that a system may be set up in which a customer leaves the store after completing payment by having the exit gate device read a barcode or two-dimensional code (exit code) printed on a medium (e.g., a receipt), and by reading the exit code, the exit gate device may recognize that the number of specific items is equal to or exceeds a predetermined number. The exit code may be displayed on the mobile terminal 60.

[0176] Whether or not to issue an alert (display on the screen of the mobile terminal 60 or the settlement device 50, light up a sign pole, send information to the transaction status management device 40 or a store clerk's mobile terminal, alert at the exit gate device, etc.) as described above when the number of specific items is equal to or exceeds a predetermined number (or when the total amount of the specific items is equal to or exceeds a predetermined amount, or when the ratio of the specific items to the total items (ratio of number or ratio of amount) is equal to or exceeds a predetermined ratio) may be managed and controlled for each time period and for each customer.

[0177] (10) Although described in the above embodiment, the weight check may be performed, for example, as follows.

[0178] (Weight check / check method 1) In the case where the cart 70 transmits the weight of all products (weight not 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 XX bread), calculates the difference between the weight currently received from the cart 70 (e.g., the weight of XX bread + XX oolong tea), compares the difference weight (weight a) with the weight of XX oolong tea (weight b), and displays the comparison result. For example, the mobile terminal 60 may determine whether the difference between weight a and weight b falls within a predetermined range recognized as an error, and if it falls within the predetermined range, it is normal, and if it does not fall within the predetermined range, it is abnormal. The same applies to check methods 2 and 3.

[0179] 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 inquire (send the product code obtained by scanning a barcode) of another device (e.g., 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) to obtain the weight of the product (the product currently registered), or may store the product weight master in a storage 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.

[0180] Furthermore, the calculation of the differential weight and the comparison of the 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.

[0181] (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 weight of the XX loaf of bread), calculates the difference between this and the weight currently received from the cart 70 (e.g., the weight of the tare weight + the XX loaf of bread + the XX oolong tea), compares the differential weight (weight a) with the weight of the XX oolong tea (weight b), and displays the comparison result.

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

[0183] (11) In the above embodiment, the connection between the mobile terminal 60 and the cart 70 is disconnected based on the operation of the Proceed to Checkout button BT626. However, the condition for disconnection is not limited to this. For example, any of the following conditions a to e may be satisfied. a: Based on the fact that the settlement device 50 has read the settlement code GA631, the connection between the mobile terminal 60 and the cart 70 is disconnected. Note that the fact that the settlement device 50 has read the settlement code GA631 may be transmitted from the settlement device 50 → cloud server 20 → mobile terminal 60. For example, when the settlement device 50 reads the settlement code GA631, it transmits request information to the cloud server 20, and the cloud server 20, having received the request information, notifies the mobile terminal 60 that the settlement device 50 has read the settlement code GA631. b: Based on the completion of settlement at the settlement device 50, the connection between the mobile terminal 60 and the cart 70 is disconnected. Note that the completion of settlement at the settlement device 50 may be transmitted from the settlement device 50 → cloud server 20 → mobile terminal 60. For example, after completing settlement, the settlement device 50 transmits settlement information to the cloud server 20, and the cloud server 20 that receives the settlement information notifies the mobile terminal 60 that settlement has been completed. c: An exit gate device is installed in the store, and when a customer passes through the exit gate device, the connection between the mobile terminal 60 and the cart 70 is disconnected. The fact that a customer has passed through the exit gate device may be transmitted from the exit gate device to the cloud server 20 to the mobile terminal 60. The exit gate device may recognize that each customer has passed through, for example, by reading a barcode printed on the medium described in (9) above. d: When the cart 70 is returned to the cart collection point, the connection between the mobile terminal 60 and the cart 70 is cut off. Note that the mobile terminal 60 itself may determine that the cart 70 has been returned to the cart collection point (for example, from a GPS or a beacon), or the cart 70 (the cart 70 itself determines that the cart 70 has been returned from the start of charging at the cart collection point) may notify the mobile terminal 60. e: Based on the fact that the user has left the store, the connection between the mobile terminal 60 and the cart 70 is severed. The fact that the user has left the store is determined by the mobile terminal 60 itself (for example, by a GPS or a beacon).

[0184] When the connection with the cart 70 is cut off (when a BT disconnection is executed) by operating the Proceed to Checkout button BT626 or by the above-mentioned a to e, the retry control of connection with the cart 70 is stopped. In other words, until the control of cutting off the connection (BT connection) with the cart 70 is executed by operating the Proceed to Checkout button BT626 or by the above-mentioned a to e (until it is cut off based on a declaration, etc.), the status is one in which a BT connection is required, and for example, if the connection is cut off by removing the device from the cart 70 and reading a barcode on the shelf label, etc., the connection with the cart 70 is retried (reconnection with the cart 70 is executed using connection information already acquired from the two-dimensional code 78 or NFC tag 79).

[0185] Since retry control generally consumes a lot of power, it is necessary to limit its execution as much as possible. However, according to the above, the timing when BT connection is not required (the timing when the Proceed to Checkout button BT626 is operated, and the timings a to e described above) are made clear (the execution conditions of retry control are appropriately set), unnecessary retry control is suppressed, and battery consumption (battery 76) can be reduced.

[0186] (12) In the above embodiment, if connection to the cart 70 fails, a message such as "The cart may be out of order. Please use another cart" is output. However, as is related to (11) above and (13) below, it is also possible to allow the user to use the cart 70 that has failed to connect.

[0187] One of the purposes of using the weighing function of the cart 70 (connection to the cart 70 equipped with a weighing unit) is to improve security (detection of fraud, etc.), but using the weighing function of the cart 70 (connection of the mobile terminal 60 to the cart 70) does not have to be an absolute condition (it may be operated flexibly). For example, even if it is determined that the connection is not possible (if the connection is not established) as a result of repeated connection requests for the connection between the cart 70 and the mobile terminal 60, the customer may be able to use the cart 70. For example, even if the connection is not possible, the initial registration screen may be displayed. However, the app A may continue to periodically retry the connection request in the background. Since it is an operation in the background, there is no difference in the external behavior from the case of connection establishment. In other words, even if the connection to the cart 70 fails (i.e., even if the weighing function of the cart 70 cannot be used), the customer is not forced to perform any special operation.

[0188] (13) In the above embodiment, the mobile terminal 60 starts registering a product after connecting to the cart 70 (i.e., product registration is prohibited before connecting to the cart 70), while it has been described that the mobile terminal 60 can continue registering a product after starting the product registration (i.e., if the connection to the cart 70 is disconnected during the product registration), but this is not limiting.

[0189] The mobile terminal 60 may be configured to start registering products even when not connected to the cart 70. For example, when the mobile terminal 60 fails to connect to the cart 70, the mobile terminal 60 may display a small screen with a "Do not connect" button on the front of the registration initial screen (FIG. 3(A)), and when the "Do not connect" button is operated, the mobile terminal 60 may be configured to start registering products even when not connected to the cart 70. When the mobile terminal 60 fails to connect to the cart 70, the mobile terminal 60 may be configured to start registering products without displaying the small screen as described above. Depending on the date and time (time period), it may be controlled whether to display the small screen and start registering products based on the operation of the "Do not connect" button, or to start registering products without displaying the small screen. Depending on the store's settings, when the connection to the cart 70 fails, it may be controlled whether (a) product registration is prohibited, (b) a small screen is displayed and product registration is started based on the operation of the "Do not connect" button, or (c) product registration is started without displaying the small screen. The above (a) to (c) may be set for each date and time (time period) or for each customer.

[0190] When the connection with the cart 70 is cut off during product registration, the mobile terminal 60 may prohibit the registration of the product (or may prohibit the putting of the product into the cart 70). Depending on the store's settings, when the connection with the cart 70 is cut off during product registration, control may be performed as follows: (a) the product registration is allowed to continue, (b) the product registration is prohibited, or (c) the putting of the product into the cart 70 is prohibited. The above (a) to (c) may be set for each date and time (time period), or may be set for each customer.

[0191] In (9) above, it was explained that an alert (display on the screen of the mobile terminal 60 or the settlement device 50, light up the sign pole, send to the transaction status management device 40 or the mobile terminal of the store clerk, alert at the exit gate device, etc.) is given when the number of specific items is a predetermined number or more (or when the total amount of the specific items is a predetermined amount or more, or when the ratio of the specific items to the total items (ratio of number or ratio of amount) is a predetermined ratio or more), but an alert may also be given when the time without connection is a predetermined time or more, or when the ratio of the time without connection to the total shopping time is a predetermined ratio or more, or when registration is started without connection. Whether or not to give an alert may be managed (set) and controlled for each time period and for each customer.

[0192] (14) In the above embodiment, the mobile terminal 60 transitions to the initial registration screen (= a state in which a product can be registered) in Fig. 3(D) when the connection to the cart 70 is completed (or not connected), but the mobile terminal 60 may transition to the initial registration screen in Fig. 3(D) on the condition that the connection code (two-dimensional code 78) is read (at the time when the connection code is read). This can shorten the time until the initial registration screen is displayed.

[0193] The mobile terminal 60 (application A) issues a connection request to the cart 70, but if a connection to the cart 70 is not established in one request, the request is retried, and if the connection is completed in one retry within a retry period in which multiple retries are made, or if it is determined that a connection cannot be established after the retry period has ended, then in a specification in which a registration screen is displayed, the registration screen will be displayed after the retry period has elapsed, which can cause a problem that product registration cannot be started quickly, resulting in poor operability and inconvenience. Therefore, rather than waiting for an actual connection to be established after the connection code is read, if the condition is that the connection code is read, there is an advantage in that the registration screen can be displayed immediately and product registration can be started quickly.

[0194] There are cases where a connection to the cart 70 cannot be established because the cart 70 is in an abnormal state (for example, a breakdown in the cart communication unit, the power is off, etc.). If the conditions are that a connection is established or that a connection is not possible after the end of a retry period, and the cart 70 that a customer wishes to use (the cart 70 from which the connection code was read) is in an abnormal state, the customer must wait to register a product until it is determined that a connection is not possible after the retry period. On the other hand, if the conditions are that a connection code is read, there is no need to waste time waiting until it is determined that a connection is not possible after the retry period.

[0195] The cart 70 is more expensive than a typical shopping cart because it is composed of a scale unit (weighing unit), a communication unit (cart communication unit) with the application A, a power unit, a control unit, etc. Many supermarkets need to prepare a large number of shopping carts for their sales floors so that they can be used even when there are many customers, and it is a heavy burden to equip all the shopping carts with scale units. Therefore, it is possible that shopping carts equipped with scale units (hereinafter sometimes referred to as carts with scales) and shopping carts not equipped with scale units (hereinafter sometimes referred to as carts without scales) are mixed. In a sales floor where shopping carts equipped with scale units and shopping carts not equipped with scale units are mixed, the method of starting to operate the mobile terminal 60 will be different.

[0196] Unless the connection code is read, app A cannot advance the status (for example, it cannot transition between screens), and therefore the cart without scales cannot be used with that app. One method would be to make the appearance of carts with scales and carts without scales different so that they can be distinguished from each other, allowing the customer to determine which cart they are using and have app A accept the selection operation, but this is inconvenient and difficult to allow from an operational standpoint. One way to solve this is to affix a two-dimensional code, similar to that of carts with scales, to carts without scales, and make the reading of the two-dimensional code a condition for starting use. This would allow them to be operated in the same way as carts with scales.

[0197] The two-dimensional code affixed to a cart with a scale is a connection code, but the two-dimensional code affixed to a cart without a scale is not a connection code but an encoded disconnection code. When app A reads the disconnection code from the two-dimensional code affixed to a cart without a scale while it is not connected to a cart with a scale, it transitions to a registration screen and becomes available for shopping. In this way, when a shopping cart without a scale is present, it is preferable to allow registration before retrying and waiting for a decision that connection is not possible.

[0198] Also, when app A reads a disconnection code from a two-dimensional code attached to a cart without scales while connected to a cart with scales, it may perform a process to end (disconnect) the connection with the cart with scales and maintain the shopping available state. By allowing app A to read a two-dimensional code while connected to a cart with scales, it is possible to conveniently accommodate customers who change shopping carts in the middle of shopping. For example, if the casters or handle of a shopping cart are not in good condition and the cart cannot be transported (moved), a customer may change shopping carts (to a cart without scales) and replace the basket even in the middle of shopping, and various problems may arise if the connection with the cart with scales before the change is maintained, so the disconnection process is run.

[0199] Similarly, on condition that the mobile terminal 60 has acquired a connection code from the NFC tag 79, the mobile terminal 60 may display the startup reception section (startup reception area; reference symbol B in the figure) in FIG.

[0200] (15) In relation to (14) above, the operation of app A (operation of mobile terminal 60) may be changed based on whether or not a cart with scales (cart 70) exists in the target store (visited store). For example, when a start-up operation (icon operation) is performed, app A may inquire of cloud server 20 whether or not a cart with scales exists in the target store, and if a cart with scales exists in the target store, display a menu screen (for example, the menu screen of FIG. 3(B)) that allows the user to select a connection with the cart with scales, and if a cart with scales does not exist in the target store, display a menu screen (not shown) that does not allow the user to select a connection with the cart with scales. Alternatively, app A may determine whether or not the user is within the entry range of the target store after the start-up operation ((6) above), and if the user is within the entry range of the target store and a cart with scales exists in the target store, display a menu screen that allows the user to select a connection with the cart with scales, and if the user is within the entry range of the target store and a cart with scales exists in the target store, display a menu screen that does not allow the user to select a connection with the cart with scales, and if the user is within the entry range of the target store and a cart with scales does not exist in the target store, display a menu screen that does not allow the user to select a connection with the cart with scales. When application A displays a menu screen in which connection to a cart equipped with a scale cannot be selected, application A thereafter does not perform control (Bluetooth control) or the like relating to connection to a cart equipped with a scale.

[0201] (16) As described above, the mobile terminal 60 is equipped with an acceleration sensor and a gyro sensor, and therefore may determine whether its own mobile terminal 60 (its own 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 the gyro sensor may be used to determine whether the cart 70 is moving or stationary.

[0202] By determining whether the 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 that fraud is occurring when fraud is not occurring. For example, if vibrations increase due to sudden acceleration / deceleration (including starting and stopping movement) or poor condition of the casters, even though no product has actually been inserted, the weight value of the weighing unit may change, and it may be determined that a product has been inserted into the cart 70 (i.e., it may be determined that an unscanned product has been inserted into the cart 70). In contrast, by using the above sensing results, it is possible to determine that the cart 70 is moving, and that the change in the weight value is due to the vibration caused by the movement, and the change in the weight value can be ignored (referred to as ignoring control).

[0203] In order to prevent the ignoring control from becoming a breeding ground for fraud, the weighing value before the start of movement may be stored and compared with the weighing value after the end of the movement (when stationary) to monitor whether or not there is any fraudulent insertion during the movement (between the start of the movement and the end of the movement). The monitoring may be performed by the mobile terminal 60 or the cart 70. If the weighing value increases during the movement, the mobile terminal 60 may display a message such as "Did you register the product correctly? If you could not register it correctly, please read the barcode again." If the weighing value increases during the movement and no product was registered during the movement, the mobile terminal 60 may display a message such as "Since registration was not correctly performed, please read the barcode again." or may set a confirmation required flag (which may be a dedicated confirmation required flag indicating that the scanned product has not been inserted) in the transaction information of the transaction. The mobile terminal 60 may also instruct the registration of a product while stationary during the movement. For example, the mobile terminal 60 may display a message such as "The cart is moving. Please stop the cart before registering the product" during the movement.

[0204] (17) This is related to (16) above, but the weight value may also change when the contents of the shopping basket are rearranged (e.g., changing the position of each item in the basket) or checked (e.g., checking whether or not the item has been purchased). In order to prevent rearrangement of the contents of the shopping basket from being determined as insertion of scanned products into the cart 70, buttons related to rearrangement of the basket (start rearrangement of basket button, end rearrangement of basket button) may be provided on the screen of the mobile terminal 60 (e.g., registration screen), and the customer may be made to rearrange the basket while declaring rearrangement of the basket (between the operation of the start rearrangement of basket button and the operation of the end rearrangement of basket button). The mobile terminal 60 executes ignore control while declaring rearrangement of the basket. Also, as in the case of movement, the weight value before the start of rearrangement of the basket (when the start rearrangement of basket button is operated) may be stored and compared with the weight value after the end of rearrangement of the basket (when the end rearrangement of basket button is operated) to monitor for the presence or absence of unauthorized insertion while declaring rearrangement of the basket.

[0205] (18) When a product is registered using the cart 70, payment without using the in-store settlement machine (payment device 50) (for example, so-called air payment with a credit card, etc.) may be permitted, and when a product is registered without using the cart 70, only payment using the in-store settlement machine may be permitted. Whether or not to permit payment without using the in-store settlement machine may be determined depending on the number or percentage of the specific products in (9) above, the time of disconnection, and whether or not registration was started without being connected.

[0206] If the customer does not use the cart 70, the customer may operate the icon of application A (symbol A in the figure) from the initial screen (FIG. 3(A)). When the icon of application A on the initial screen is operated, the mobile terminal 60 displays a menu screen (FIG. 3(C)). Note that when the icon of application A is operated from the initial screen, the cart 70 is not basically connected, so the cart image GA625 is not displayed on the menu screen that is displayed by operating the icon of application A from the initial screen (the same applies to the registration screen transitioned to from the menu screen).

[0207] (19) The cart 70 may be used as a scale in a so-called fully self-service cash register (for example, the registration and settlement device 51, the registration and settlement device 53 in the fully self-service mode). In an embodiment in which the cart 70 is used as a so-called fully self-service cash register, the cart 70 is not connected to the mobile terminal 60 (in fact, the mobile terminal 60 is not used in this embodiment).

[0208] (20) The cart 70 may not have a weighing unit (the cart 70 may be the scale-less cart described in (14) above). The cart 70 may also have a display unit. That is, the cart 70 may have a display unit instead of or in addition to the weighing unit. The display unit of the cart 70 may display information about the product registered by the connected mobile terminal 60 (additional information about the registered product, recommended product information related to the registered product, etc.), information according to the location of the connected mobile terminal 60 (recommended product information in the product display area), etc. That is, the details of the scanned and registered product may be displayed (notified) on the mobile terminal 60 (app A), and supplementary information and advertising information may be displayed (provided) on a display mounted on the cart 70. The display unit of the cart 70 may also display information (e.g., an image, etc.) indicating that the mobile terminal 60 is currently connected.

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

[0210] (22) In the above embodiment, the mobile terminal 60 is described as belonging to the customer, but it may be a terminal (rented terminal) prepared by the store. The mobile terminal 60, which is a rented terminal, is prepared as a dedicated terminal in which only application A can be executed. In a configuration in which the mobile terminal 60 is connected to the cart 70 using the two-dimensional code 78, if the mobile terminal 60 is owned by the customer, the menu screen is displayed by operating the icon of application A (symbol A in the figure) (FIG. 3(A) → FIG. 3(B)), but if the mobile terminal 60 is a rented terminal, the menu screen is displayed from the beginning.

[0211] Furthermore, the mobile terminal 60, which is the rental terminal, may not be separate from the cart 70, but may be part of the cart 70 (the cart 70 may be equipped with the mobile terminal 60). When the mobile terminal 60 is separate from the cart 70, the operation after connection (for example, monitoring for fraud, etc.) is the same as when the mobile terminal 60 is part of the cart 70 (when connected from the beginning). In other words, although the parts related to BT control (BT connection, BT communication) are different, other parts are common whether the mobile terminal 60 is set in the cart 70 (when they are separate) or the cart 70 is equipped with the mobile terminal 60.

[0212] (23) Although the state of establishing communication between the portable terminal 60 and the cart 70 using Bluetooth has been expressed as pairing, this is not limited to encrypted communication, and may be unencrypted communication. Also, it may 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 is not important.

[0213] (24) A part or all of each function (input / output, storage, processing (including judgment)) of each device (e.g., the transaction status management device 40, the settlement device 50, the registered settlement device 51, the registered settlement device 52, the registered settlement device 53, the mobile terminal 60, etc.) may be realized by a device other than the device described as the executing subject of the function. For example, each device may function as a so-called thin client specialized for an input / output interface, etc. As an example, a cloud server (which may be the same as the cloud server 20 or may be another cloud server) executes a program for controlling the operation of each device, and each device may display a screen by a browsing function. As an example, the cloud server 20 may control the display of the screen (FIGS. 3, 4, etc.) and the operation (FIGS. 6, 7, etc.) of the mobile terminal 60. In other words, the program (app A) for controlling the operation related to the service A of the mobile terminal 60 may run on the CPU of the mobile terminal 60 or may run on the CPU of the cloud server 20. In other words, the app A may be a Web application used using a browser.

[0214] <Overview of the embodiment> [Technical field] The present invention relates to a program. [Background technology] There is known an information communication terminal that reads the MAC address of a device from an NFC tag attached to the device and transmits data to an IP address corresponding to the read MAC address (see, for example, Patent Document 1). There is also known a system in which customers themselves register products in a product display area using a shopping cart. [Prior art document] [Patent documents] [Patent Document 1] Patent No. 6375732 [Summary of the invention] [Problem to be solved by the invention] However, there is room for improvement in a system in which customers themselves register products in a product display area using a shopping cart. The present invention has been made in consideration of such circumstances, and has an object to provide a technology that can more suitably implement a system in which customers themselves register products. [Means for solving the problem]

[0215] (1) One aspect for solving the above-mentioned problem is a program (e.g., app A) for causing a mobile terminal (e.g., mobile terminal 60) that can be used for registering products to function as a computer, the program causing the computer to function as a registration means for registering products and an acquisition means for acquiring (from a two-dimensional code 78, an NFC tag 79, or a beacon) connection information (e.g., device identification information of the shopping cart to be connected) for connecting to a shopping cart (e.g., cart 70), the registration means being characterized in that it enables product registration after the acquisition means has acquired the connection information. According to the program (1), a system in which customers themselves can register products can be more effectively implemented. For example, a customer can register products by connecting the mobile terminal 60 to a shopping cart, and can also register products by acquiring connection information.

[0216] (2) The shopping cart is provided with a weighing unit, and functions as a receiving means for receiving the weighing result by the weighing unit and a tare subtraction means for performing a tare subtraction by the weighing unit, and the tare subtraction means performs a tare subtraction when an item of product is registered by the registration means (e.g., before at least one item of product is added to the cart 70).This is the program described in (1). According to the program (2), it is possible to preferably carry out a tare subtraction. If the shopping basket is placed on the cart 70 after a tare subtraction has been carried out, it will be erroneously determined that an act is fraudulent when it is not, but since the first item is generally registered after the shopping basket is placed on the cart 70, if a tare subtraction is carried out when the first item is registered, the tare subtraction will be carried out while the shopping basket is placed on the cart 70 (that is, a situation in which the shopping basket is placed on the cart 70 after a tare subtraction has been carried out will not occur), and this will reduce the number of cases in which an act is erroneously determined to be fraudulent when it is not.

[0217] (3) The program described in (2) functions as a fraud detection means capable of detecting the fraudulent addition of products to the shopping cart, and the fraud detection means determines that a fraudulent addition has occurred when it is determined from the weighing result that there has been an increase in the weighing value of the weighing unit but no product has been registered by the registration means. According to the program (3), it is possible to effectively monitor for fraud (eg, the insertion of unregistered products).

[0218] (4) The program described in (3) functions as a change means for changing the number of purchased items of the product registered by the registration means, and the fraud determination means does not determine that fraudulent insertion of products has occurred when the change means increases the number of purchased items. According to the program in (4), for example, when changing the quantity, cases in which an actual act is mistakenly determined to be fraudulent are reduced.

[0219] (5) A program described in any of (1) to (4) which functions as a connection means for connecting to the shopping cart by communication using the connection information, and a declaration means for accepting a declaration to terminate product registration by the registration means (e.g., operation of the Proceed to Checkout button BT626), and which terminates the connection with the shopping cart when the declaration means accepts the declaration (see flowcharts in Figures 6 and 7). According to the program (5), the connection can be terminated appropriately (provided that there is no more product to be inserted).

[0220] (6) The program described in (5) is characterized in that the registration means is capable of continuing to register the product if the connection to the shopping cart is disconnected after starting to register the product and before the connection means terminates the connection to the shopping cart based on the declaration (see, for example, Figures 5(C), 5(D), and 5(E)). Program (6) can increase customer convenience.

[0221] (7) The program described in (5) is characterized in that it functions as a transmission means (see the flowcharts of Figures 6 and 7) for transmitting information regarding the shopping cart connected by the connection means (e.g., the machine number, the status of the battery, etc., various error information). According to the program (7), the necessary maintenance of the shopping cart can be performed as needed.

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

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

Claims

1. A program for causing a mobile terminal that can be used to register a product to function as a computer, The computer, A registration means for registering the product; A means for acquiring connection information for connecting to a shopping cart Function as a The registration means includes: A program that enables registration of a product after the connection information is acquired by the acquisition means.

2. The shopping cart includes a weighing unit, A receiving means for receiving a weighing result by the weighing unit; Tare subtraction means for subtracting the tare weight from the weighing unit Function as a The tare subtraction means is 2. The program according to claim 1, further comprising a step of subtracting a tare weight when said registration means registers one item of merchandise.

3. A fraud determination means for determining whether or not an item has been fraudulently added to the shopping cart. Function as a The fraud determination means includes:

3. The program according to claim 2, further comprising a step of determining that an illegal insertion has occurred when an increase in the weighing value of the weighing unit is detected from the weighing result but the product is not registered by the registration means.

4. A change means for changing the purchase quantity of the product registered by the registration means. Function as a 4. The program according to claim 3, wherein said fraud determination means does not determine that fraudulent insertion of products has occurred when said change means increases the number of purchased items.

5. a connection means for connecting to the shopping cart by communication using the connection information; A declaration means for accepting a declaration that the registration of the product by the registration means is to be terminated. Function as a The connection means is 5. The program according to claim 1, wherein when the declaration is accepted by the declaration means, a connection with the shopping cart is terminated.

6. The registration means includes: The program according to claim 5, characterized in that if the connection to the shopping cart is disconnected after product registration has begun and before the connection means terminates the connection to the shopping cart based on the declaration, the product registration can be continued.

7. A transmission means for transmitting information regarding the shopping cart connected by the connection means.

6. The program according to claim 5, wherein the program causes the program to function as follows:

Images