Sales system

Abstract

To provide a more suitable system for customers to register products. [Solution] The sales system comprises a registration unit for registering products, a weighing unit for weighing products, and a display unit for displaying a registration screen that accepts product registration by the registration unit. The display unit displays a registration screen that accepts further product registration by the registration unit based on a partial weighing status where multiple products have been registered consecutively by the registration unit and some of the multiple products have been weighed by the weighing unit.

Description

Technical Field

[0001] The present invention relates to a sales system.

Background Art

[0002] A system in which a customer registers a product using a terminal attached to a shopping cart is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there is room for improvement in the system for customers to register products.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a more suitable system for customers to register products.

Means for Solving the Problems

[0006] One aspect for solving the above-described problems includes a registration unit for registering a product, a weighing unit for weighing the weight of the product, and a display unit for displaying a registration screen for accepting the registration of the product by the registration unit. The display unit is capable of displaying a registration screen that can accept further registration of products by the registration unit from a partial weighing situation in which a plurality of products are continuously registered by the registration unit and a part of the plurality of products is weighed by the weighing unit. A sales system characterized by that.

Brief Description of the Drawings

[0008] Figure 1 is a conceptual diagram of a network illustrating the sales system 1 of this embodiment (which may also be called a "sales data processing system," etc.). The sales system 1 shown in Figure 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 (which may also be called an "information processing terminal (device)," "information communication terminal (device)," "mobile communication terminal (device)," "mobile registration terminal (device)," "portable registration terminal (device)," etc.) 60.

[0009] Sales system 1 can be implemented in various types of businesses (supermarkets, convenience stores, drugstores, home centers, consumer electronics stores, etc.). The store controller 30, transaction status management device 40, and settlement device 50 are installed inside the store (product display area, checkout area, back room, office, etc.). These can communicate via LAN 19 (wired or wireless). The headquarters server 10 and cloud server 20 are installed outside the store (for example, at the head office or data center). The devices installed inside the store (store controller 30, transaction status management device 40, settlement device 50) and the devices installed outside the store (head office server 10, cloud server 20) can communicate (directly or via the store controller 30).

[0010] Furthermore, there are shopping carts (hereinafter simply referred to as "carts") 70 provided by the store. Also, there are mobile terminals 60 owned by customers who visit the store. The mobile terminals 60 can be attached (set up) to the carts 70. The mobile terminals 60 and the carts 70 can communicate wirelessly (for example, Bluetooth (registered trademark; the same applies hereinafter)). In Figure 1, the mobile terminal 60 shown inside the cart 70 represents the mobile terminal 60 attached to the cart 70. The mobile terminals 60 and the cloud server 20 can communicate (either directly or via the store controller 30).

[0011] Sales system 1 provides a self-service (hereinafter sometimes referred to as Service A) in which customers register products using a mobile terminal 60 and make payments using a payment device 50. In other words, Service A is a self-service in which customers register products and make payments themselves, but they use a mobile terminal 60 for product registration and a payment device 50 for payment.

[0012] In addition, in FIG. 1, the number of each device (terminal) is an illustration. For example, in FIG. 1, although "..." is illustrated on the right side of the settlement device 50, the number of settlement devices 50 installed in the store may be one or more. Also, for example, in FIG. 1, two mobile terminals 60 are illustrated, but the number of mobile terminals 60 present in the store is the number of customers who come to the store with mobile terminals 60, and is not necessarily two. Also, for example, in FIG. 1, two carts 70 are illustrated, but the number of carts 70 present in the store is the number prepared by the store side based on the number of mobile terminals 60 that can be 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 the store. Specifically, the mobile terminal 60 registers a product based on a customer's operation (action) while being in a communicable state with one cart 70. Note that the mobile terminal 60 can register a product based on a customer's operation whether it is attached to the cart 70 or removed from the cart 70 as long as it is in a communicable state with one cart 70. For example, the customer may remove the mobile terminal 60 from the cart 70 and read the barcode of the product printed on the shelf label (product label) attached to the display shelf of a certain product (if it is an electronic shelf label with a display, the barcode of the product displayed on the display) to register the product.

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

[0015] The CPU is a central processing unit that controls the entire mobile terminal 60 by reading and executing a program stored in the storage unit. The storage unit stores various information (for example, information that the CPU refers to or generates, information acquired from the outside, etc.). The storage unit is a general term for one or more various storage members (for example, those serving as 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 referred to as App A) for using Service A from the outside (which may be a predetermined server or cloud server 20) and store (install) it in the storage unit. The mobile terminal 60 may execute various processes related to Service A by App A and display a screen. Note that Service A is a self-service that uses the mobile terminal 60 for product registration and uses the settlement device 50 for settlement as described above, and App A is an application program that is responsible for the part of Service A related to the mobile terminal 60 (product registration).

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

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

[0019] The mobile terminal 60 can obtain connection information for each cart 70 from the beacons transmitted by each cart 70, and can also obtain connection information for each cart 70 from the 2D code 78 (described later) attached to each cart 70.

[0020] The mobile terminal 60 obtains 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 obtained connection information, and becomes capable of communicating with the cart 70 (Bluetooth communication).

[0021] The mobile terminal 60 can display images captured by the imaging unit as so-called through images (live view images) on the display unit. When the mobile terminal 60 is attached to the holder portion 76 (described later) of the cart 70 and imaging is performed by the imaging unit, it acquires an image of the shopping basket viewed from the position of the holder portion 76 and displays it on the display unit as a through image.

[0022] The mobile terminal 60 may store the captured image in a storage unit instead of displaying it on the display unit, or in addition to displaying the captured image on the display unit. In other words, the mobile terminal 60 may store the captured image in a storage unit without displaying it on the display unit, or store the captured image on the display unit without storing it in the storage unit, or store the captured image in the storage unit while displaying it on the display unit. The mobile terminal 60 may also transmit the captured image to the cloud server 20.

[0023] The mobile terminal 60 stores in its memory the weighing information received from the cart 70 (for example, the previously received weighing value, the tare weight, etc.). When the mobile terminal 60 receives a weighing value as weighing information from the cart 70, it determines that the weighing value from the cart 70 has increased if the current weighing value is greater than the weighing value stored in the memory (the previous weighing value), and determines that the weighing value from the cart 70 has decreased if the current weighing value is less than the weighing value stored in the memory.

[0024] The mobile terminal 60 is equipped with various image recognition functions (image processing functions). For example, the mobile terminal 60 is equipped with an object recognition function (object determination function) that recognizes objects in an captured image. In addition, the mobile terminal 60 is equipped with the following functions in relation to the object recognition function.

[0025] The mobile terminal 60 is equipped with a barcode reading function that recognizes barcodes in captured images and reads the recognized barcodes. The mobile terminal 60 uses the barcode reading function to read barcodes attached (printed) to products, for example, and obtain product codes (product identification information).

[0026] The mobile terminal 60 is equipped with a 2D code reading function that recognizes 2D codes in captured images and reads the recognized 2D codes. Using the 2D code reading function, the mobile terminal 60 reads, for example, the 2D codes 78 (described later) attached to each cart 70 and obtains connection information.

[0027] The mobile terminal 60 may be equipped with a scan action recognition function that recognizes a scanning action (holding motion) in which a customer scans a product (barcode) based on the captured image. The scan action recognition function may, for example, recognize whether something resembling a barcode (for example, an object with a predetermined pattern consisting of multiple line segments, etc.) has newly appeared in the barcode reading area (described later) (for example, by pattern matching).

[0028] Needless to say, the mobile terminal 60 is equipped with a timing function (timing unit). The mobile terminal 60 can manage the current time, the elapsed time from a certain point in time, and the remaining time until a certain point in time using its timing function.

[0029] For example, the mobile terminal 60 can manage the elapsed time since the product was registered. The mobile terminal 60 can also manage the remaining time of the timer set for the product registration (a timer that times out after a predetermined time has elapsed since registration). The same applies to the elapsed time since the product was canceled and the remaining time of the timer set for the product cancellation.

[0030] Furthermore, the mobile terminal 60 can manage the elapsed time from the start of display of the screen (including the small screen (pop-up screen)). The mobile terminal 60 can also manage the remaining period of the timer set at the start of display of the screen (including the small screen) (a timer that times out after a predetermined time has elapsed from the start of display). The same applies to the elapsed time from the time of erasing the screen (including the small screen) and the remaining period of the timer set at the time of erasing the screen (including the small screen).

[0031] Furthermore, the mobile terminal 60 can manage the elapsed time from the timing of removing the product from the shopping basket (the timing when it is determined that the weighed value has decreased, or the timing when it receives a weight decrease notification, etc. (described later) from the cart 70). The mobile terminal 60 can also manage the remaining time of the timer set for the timing of removing the product from the shopping basket (a timer that times out after a predetermined time has elapsed from the timing of removal). The mobile terminal 60 may also manage the elapsed time from the timing of placing the product into the shopping basket (the timing when it is determined that the weighed value has increased, or the timing when it receives a weight increase notification, etc. (described later) from the cart 70), and the remaining time of the timer set for the timing of placing the product into the shopping basket (a timer that times out after a predetermined time has elapsed from the timing of placement).

[0032] (Cart 70) Figure 2 is an explanatory diagram illustrating the cart 70. Figure 2(A) is a side view of the cart 70. Figure 2(B) is a perspective view of the cart 70. In addition to the function of carrying and transporting goods (goods registered by the mobile terminal 60), the cart 70 is equipped with a function for weighing goods, a function for communicating with the mobile terminal 60, and other functions.

[0033] As shown in Figures 2(A) and 2(B), the cart 70 comprises an upper mounting section (upper mounting platform) 71, a lower mounting section (lower mounting platform) 72, and a circuit board housing section (circuit board box) 73. The upper mounting section 71 and the lower mounting section 72 are components on which shopping baskets, etc., can be placed. In other words, the cart 70 can hold shopping baskets, etc., in two layers, upper and lower. Figures 2(A) and 2(B) show a state where no shopping baskets are placed on the upper mounting section 71 and the lower mounting section 72, but shopping baskets, etc., can be placed on both the upper mounting section 71 and the lower mounting section 72. In Figure 2(A), the symbol A indicates the position (space) of a shopping basket placed on the upper mounting section 71, and the symbol B indicates the position of a shopping basket placed on the lower mounting section 72.

[0034] The circuit board housing section 73 accommodates one or more circuit boards (details will be described later). A charging terminal 74 is provided on the left side of the circuit board housing section 73 (the left side when the cart 70 is facing forward). A power supply cable (not shown) is detachably connected to the charging terminal 74. Charging terminals 75 are provided on the front and rear sides of the circuit board housing section 73 (the front charging terminal 75 is not shown in Figure 2). The front charging terminal 75 is configured to contact (connect) with the rear charging terminal 75 of another cart 70 (in other words, the rear charging terminal 75 is configured to contact the front charging terminal 75 of another cart 70). For example, if multiple carts 70 are stored in a storage area (return / use waiting area) lined up front to back, the charging terminals 75 of the front and rear carts 70 will contact each other, allowing multiple carts 70 from the first cart 70 to the last cart 70 to be charged by a single power supply.

[0035] The holder portion 76 is a component for setting the mobile terminal 60. Figures 2(A) and 2(B) show the state when the mobile terminal 60 is not set in the holder portion 76. A customer who comes to the store with a mobile terminal 60 places a shopping basket or the like on the upper mounting portion 71, etc., and attaches the mobile terminal 60 to the holder portion 76. The holder portion 76 has an opening (hole) where the imaging part (lens) of the set mobile terminal 60 is located.

[0036] A two-dimensional code 78 is affixed to the holder portion 76. The two-dimensional code 78 is a two-dimensional representation of the device identification information (connection information) of the cart 70 (the cart 70 to which the two-dimensional code 78 is affixed). Since the two-dimensional code 78 is a code used to connect the cart 70 and the mobile terminal 60, it is also referred to as a connection code.

[0037] The circuit board housing section 73 houses circuit boards (one circuit board or separate circuit boards) that implement weighing and communication functions. In other words, the circuit board housing section 73 includes a weighing section (scale section) and a communication section. In the following description, the communication section provided in the circuit board housing section 73 may be referred to as the cart communication section.

[0038] The weighing unit weighs the weight of the items placed on the upper or lower mounting section 72. More specifically, the weighing unit weighs the total weight of the items placed on the upper or lower mounting section 72 together, without distinguishing between the weight of the items on the upper or lower mounting section 71 and the weight of the items on the lower mounting section 72. The common support member that supports the upper and lower mounting sections 71 is configured so that the total weight is applied to the weighing unit (i.e., it is configured so that the weight is not applied to other parts of the cart 70 (e.g., the bottom part, the back part, etc.)). However, as long as the total weight is applied to the weighing unit, the support member that supports the upper mounting section 71 and the support member that supports the lower mounting section 72 may be separate members, rather than a common support member.

[0039] The cart communication unit transmits, for example, beacons. The cart communication unit also sends and receives various information with the mobile terminal 60. For example, the cart communication unit transmits weighing information to the mobile terminal 60. The cart communication unit receives tare instruction information (described later) from the mobile terminal 60.

[0040] Furthermore, the circuit board housing section 73 may house a circuit board that implements a memory function (this may be the same circuit board as the one that implements the weighing function and communication function, or it may be a different circuit board). In other words, the circuit board housing section 73 may further include a memory unit. The memory unit may store, for example, the tare weight (tare weight) and the previous weighing value (weighing value before increase or decrease).

[0041] Furthermore, if the current weighing value is greater than the weighing value stored in the memory unit (the previous weighing value), the cart 70 may send a weight increase notification (or the amount of the weight increase) to the mobile terminal 60. If the current weighing value is less than the weighing value stored in the memory unit, the cart 70 may send a weight decrease notification (or the amount of the weight decrease) to the mobile terminal 60.

[0042] Furthermore, the cart 70 may be equipped with a timing function (timing unit). In other words, similar to the mobile terminal 60, the cart 70 may manage the current time, the elapsed time from a certain point in time, or the remaining time until a certain point in time using a timing function.

[0043] (Tare, tare deduction) The tare weight is the items placed on the upper and lower loading sections 71 and 72 in the initial state before shopping begins (more specifically, before the first item is placed in the machine). The tare weight may include the shopping basket as well as the customer's personal belongings (wallet, bag, etc.). Since the weight of the shopping basket is known, the weight of the customer's personal belongings can be calculated.

[0044] After connecting with the cart 70, the mobile terminal 60 transmits tare instruction information to the cart 70 before loading at least one item. When the cart 70 receives tare instruction information from the mobile terminal 60, it uses the measured value at the time of receipt as the tare weight. The cart 70 notifies the mobile terminal 60 of the measured value (tare weight) at the time of receiving the tare instruction information. For example, if the measured value when the cart 70 receives tare instruction information from the mobile terminal 60 is 3000g, it notifies the mobile terminal 60 of 3000g. The mobile terminal 60 proceeds with processing using 3000g as the tare weight. The cart 70 may also always notify the mobile terminal of 0g, regardless of the measured value at the time of receiving the tare instruction information. For example, if the cart 70 receives tare instruction information from the mobile terminal 60 and the measured value is 3000g, it may store 3000g and notify the mobile terminal 60 of 0g. The actual tare weight is 3000g, but the mobile device 60 can proceed with processing using 0g as the base weight at the start of the purchase.

[0045] (Monitoring for fraud, etc.) The mobile terminal 60 monitors for customer fraud (fraud or errors) based on the status of product registration and product loading. For example, the mobile terminal 60 monitors for unregistered and unregistered items.

[0046] (Monitoring of unregistered entries) "Not registered and not yet deployed" refers to a situation where a product has been registered (including an increase in quantity) but has not been deployed (the product was registered, but not deployed (the deployment was not recognized)). "Not registered and not yet deployed" results in a loss (disadvantage) for the customer because the product subject to settlement (the registered product) is not secured.

[0047] The mobile terminal 60 determines that an item has been "forgotten to enter" if the state of not having registered an item is not resolved within a predetermined time (for example, 30 seconds). In other words, the mobile terminal 60 determines that an item has been forgotten to enter if it is not entered within a predetermined time (for example, 30 seconds) after the item has been registered (or after the quantity has been increased). Since an item has not been entered, it may also be called an item that has not been confirmed to enter. A waiting list for entry and an item that has not been confirmed to enter are used to manage items that have been forgotten to enter (items that have not been confirmed to enter).

[0048] (Waiting list) The waiting list is a list for managing products awaiting input. Products awaiting input are products that have been registered and are waiting to be input. More specifically, products awaiting input are products that have been registered but have not yet been determined to have been input (products that have not yet been determined to have been input). The mobile terminal 60 adds the registered products to the waiting list as products awaiting input. Specifically, the mobile terminal 60 adds the following information to the waiting list for products awaiting input: the management number, the product code of the product awaiting input, the weight of the product awaiting input (the weight of the product in the product master), and the remaining time. The remaining time is a timer value and manages the predetermined time as described below. Note that the management number is optional.

[0049] Products awaiting input are removed from the input waiting list after being added to the input waiting list (after product registration) if it is determined that the product has been input, or if a predetermined time (e.g., 30 seconds) has elapsed without it being determined that the product has been input.

[0050] The waiting list is stored in a location accessible to the mobile terminal 60. For example, the mobile terminal 60 generates the waiting list in its own memory. The waiting list may be shared within the sales system 1, similar to the unconfirmed input list and unconfirmed registration list described later, so that it is possible to recognize which mobile terminal 60's unconfirmed input list it belongs to.

[0051] (List of items not yet confirmed to be added) The unconfirmed input list is a list for managing unconfirmed input items (also called forgotten input items). Unconfirmed input items are items whose input could not be confirmed within a specified time (e.g., 30 seconds) after registration. More specifically, unconfirmed input items are items that were registered but were not determined to have been input within a specified time after registration. In other words, unconfirmed input items are items that have been added to the waiting input list (waiting input items) but have not been determined to have been input and for which a specified time (e.g., 30 seconds) has elapsed. The mobile terminal 60 adds unconfirmed input items to the unconfirmed input list. Specifically, the mobile terminal 60 adds the following information to the unconfirmed input list as information about the unconfirmed input item: the management number, the time it became an unconfirmed input item (the time it was added to the unconfirmed input list), the product code of the unconfirmed input item, and the weight of the unconfirmed input item (the weight of the item in the product master). Note that the management number is optional.

[0052] The list of unconfirmed entries is stored in a location accessible to the mobile terminal 60. For example, the mobile terminal 60 generates the list of unconfirmed entries in its own storage.

[0053] Furthermore, the unconfirmed input list (the information contained in the unconfirmed input list) is shared within the sales system 1 in a way that allows it to recognize which mobile terminal 60 the unconfirmed input list belongs to. For example, a mobile terminal 60 sends an unconfirmed input list to a cloud server 20. When the cloud server 20 receives an unconfirmed input list from a mobile terminal 60, it stores the unconfirmed input list in association with the transaction information (cart information) of that mobile terminal 60. The unconfirmed input list stored in the cloud server 20 is then sent to other devices (for example, a settlement device 50). In addition, the unconfirmed input list stored in the cloud server 20 may be accessible by, for example, a transaction status management device 40.

[0054] The existence of unconfirmed items (unconfirmed item list) may be an event that requires staff intervention (staff call). For example, if an unconfirmed item is found during the product registration stage of a mobile terminal 60, the settlement device 50 that settles the items registered on the mobile terminal 60 may perform a staff call process. The staff call process includes one or more of the following: illumination of a light-emitting part in a manner indicating that a staff call is in progress; transmission of a staff call notification to a device used by a staff member (e.g., a transaction status management device 40, a mobile terminal used by a staff member (not shown)); and display on the staff call screen (not shown) that a staff call is in progress.

[0055] Furthermore, if the mobile terminal 60 determines that an item has been forgotten to be inserted (i.e., if an unconfirmed item is added to the unconfirmed item list, or has been added), it notifies the customer of the forgotten item (for example, via the screen or by voice). Specifically, if the mobile terminal 60 determines that an item has been forgotten to be inserted, it displays a small screen 660 indicating the forgotten item on the front of the registration screen 650, with or without voice (for example, Figure 3(F), Figure 9(A)). Also, if the mobile terminal 60 determines that an item has been forgotten to be inserted, it displays a message indicating that an item has been forgotten in the registration information display area 642 of the registration screen 650 (for example, Figure 10(A)).

[0056] (Monitoring unregistered entries) Unregistered input refers to a situation where product registration (including quantity increases) has not occurred, but product input has occurred (product input was recognized), but product registration has not taken place. Unregistered input results in a loss for the store because the secured product (input product) is not subject to settlement.

[0057] The mobile terminal 60 determines that an item has been "forgotten to register" if it is in an unregistered state. In other words, the mobile terminal 60 determines that an item has been "forgotten to register" if it is added without registering the item (or increasing the quantity). Since "forgotten to register" means that the registration has not been confirmed, it may also be called "unconfirmed registration." An unconfirmed registration list is used to manage "forgotten to register" (unconfirmed registration).

[0058] (Unconfirmed Registration List) The unconfirmed registration list is a list for managing unconfirmed registration items (also called forgotten registration items). Unconfirmed registration items are items that were put into storage without being registered. More specifically, unconfirmed registration items are items that were judged to have been put into storage despite not being registered (i.e., items that were put into storage but judged not to be items awaiting storage). The mobile terminal 60 adds unconfirmed registration items to the unconfirmed registration list. Specifically, the mobile terminal 60 adds the management number, the time the item became unconfirmed (the time it was added to the unconfirmed registration list), and the weight of the unconfirmed registration item (the increase in the weighed value) to the unconfirmed registration list as information about the unconfirmed registration item. Note that the management number is optional.

[0059] The unconfirmed registration list is stored in a location accessible to the mobile terminal 60. For example, the mobile terminal 60 generates the unconfirmed registration list in its own storage.

[0060] Furthermore, the unconfirmed registration list (the information contained within the unconfirmed registration list) is shared within the sales system 1 in a way that allows recognition of which mobile terminal 60 the unconfirmed registration list belongs to. For example, a mobile terminal 60 sends an unconfirmed registration list to a cloud server 20. When the cloud server 20 receives an unconfirmed registration list from a mobile terminal 60, it stores the unconfirmed registration list in association with the transaction information (cart information) of that mobile terminal 60. The unconfirmed registration list stored in the cloud server 20 is then sent to other devices (for example, a settlement device 50). In addition, the unconfirmed registration list stored in the cloud server 20 may be accessible by, for example, a transaction status management device 40.

[0061] The existence of unconfirmed registered items (unconfirmed registration list) is an event that requires staff intervention (calling a staff member). For example, if an unconfirmed registered item occurs during the product registration stage of a mobile terminal 60, the payment device 50 that settles the payment for the items registered on the mobile terminal 60 will execute a staff member call process.

[0062] Furthermore, if the mobile terminal 60 determines that registration has been forgotten (i.e., if it adds an unconfirmed product to the unconfirmed registration list or has added it), it notifies the customer of the occurrence of the forgotten registration (unconfirmed registration) (for example, notifying via the screen or by voice). Specifically, if the mobile terminal 60 determines that registration has been forgotten, it displays a small screen 670 indicating the forgotten registration on the front of the registration screen 650, with or without voice (for example, Figure 3(G), Figure 12(A)). Also, if the mobile terminal 60 determines that registration has been forgotten, it displays a message indicating that registration has been forgotten in the registration information display area 642 of the registration screen 650 (for example, Figure 13(A)).

[0063] If there are any unconfirmed items that have been inserted or unconfirmed items that have not been registered, the store clerk will be called to the payment device 50, where the clerk will check the unconfirmed items and unconfirmed items. For example, the clerk may display a clerk-only screen (for example, a maintenance screen) on the payment device 50, and through the clerk-only screen, check the unconfirmed items in the unconfirmed items list and the unconfirmed items in the unconfirmed items list.

[0064] (Continuous registration) The mobile terminal 60 operates on a basic set of one registration operation and one input operation, such as "register product → input product → register product →...", and does not accept the next registration operation until the pair (set) is completed. In addition to this general operating procedure (single registration procedure), it also allows for continuous registration procedures such as "register product → register product →..." (Figures 5 to 13). In other words, customers can input products one at a time as they register them, or they can register two or more products consecutively. As mentioned above, customers may remove the mobile terminal 60 from the cart 70 and scan the shelf labels on the display shelves. However, since scanning shelf labels can be done without holding products, customers' hands are not occupied after scanning, and they can easily register products continuously.

[0065] Furthermore, the mobile terminal 60 allows the user to register products even after some of the products registered through sequential registration have been entered. For example, the mobile terminal 60 displays a registration screen 650 that accepts the user to register products after some of the products registered through sequential registration have been entered (Figures 5 to 13). In other words, if a customer registers two or more products consecutively, they may perform the next registration operation after entering all of the consecutively registered products, or they may perform the next registration operation after entering some of the consecutively registered products.

[0066] (Payment device 50) The payment device 50 is used by the customer. Specifically, the payment device 50 settles the payment for products registered by the mobile terminal 60 based on the customer's operation. Although not shown in the diagram, the payment device 50 includes a CPU, a memory unit, a display unit, a scanner unit, a payment unit, a printing unit, an audio output unit, an imaging unit, a communication unit, and a sign pole (light-emitting unit). For example, the scanner unit scans various codes and reads each code. For example, the payment unit is a general term for either or both a cash payment unit (change machine) that settles with cash, or a non-cash payment unit (card payment unit, code payment unit) that settles with non-cash (e.g., credit, electronic money, etc.). For example, the display unit displays a product list screen (not shown), etc. The main function of the payment device 50 is the payment function, but it also has functions for registering products and canceling products. The payment device 50 may further include a key operation unit consisting of one or more various operating members, and a human presence sensor that detects (detects, recognizes) the presence of a person.

[0067] (Headquarters Server 10) The headquarters server 10 is the server that manages the entire sales system 1. The headquarters server 10 stores various types of information, such as product master data. The product master data is a file that stores product information (product name, price, weight, etc.) associated with product codes.

[0068] Furthermore, the headquarters server 10 supplies various information (e.g., product master data) to, for example, the cloud server 20 and the store controller 30. Although not shown in the diagram, the headquarters server 10 includes at least a CPU, a memory unit, and a communication unit. The headquarters server 10 may be composed of multiple servers.

[0069] (Cloud Server 20) Cloud server 20 is primarily a server that supports service A. Cloud server 20 stores various types of information. For example, cloud server 20 stores product master data, transaction information, unconfirmed input list, and unconfirmed registration list. Cloud server 20 may also store a waiting input list.

[0070] The transaction information for one mobile terminal 60 is generated, for example, at the start of a transaction with that mobile terminal 60, and stores the registration information of the products registered by that mobile terminal 60. The transaction information for each mobile terminal 60 may also store the status (processing progress) of each mobile terminal 60. The status stored in the transaction information includes the registration status, which indicates that the product has been registered, and the settlement declaration status, which indicates that a declaration has been made to proceed to settlement.

[0071] Furthermore, the cloud server 20 supplies various information to, for example, the mobile terminal 60, the settlement device 50, and the transaction status management device 40. Although not shown in the diagram, the cloud server 20 comprises at least a CPU, a memory unit, and a communication unit. The cloud server 20 may be composed of multiple servers.

[0072] (Store controller 30) The store controller 30 is a server primarily responsible for communicating information (e.g., product master data) between devices installed inside the store (transaction status management device 40, settlement device 50) and devices installed outside the store (headquarters server 10, cloud server 20). Although not shown in the diagram, the store controller 30 comprises at least a CPU, a memory unit, and a communication unit.

[0073] (Transaction status management device 40) The transaction status management device 40 is, for example, a device (e.g., a personal computer) that manages (monitors, controls, etc.) the settlement device 50 and the mobile terminal 60. For example, the transaction status management device 40 monitors (displays) the processing status and operation status of the settlement device 50. The transaction status management device 40 may also monitor (displays, corrects, etc.) the processing status and operation status of the mobile terminal 60. For example, the transaction status management device 40 may access transaction information stored in the cloud server 20 and monitor the transaction details (products, etc.) and status of each mobile terminal 60. For example, the transaction status management device 40 may access the unconfirmed registration list stored in the cloud server 20 and display whether unconfirmed registration items exist on each mobile terminal 60 or what unconfirmed registration items exist. For example, the transaction status management device 40 may access the unconfirmed input list stored in the cloud server 20 and display whether unconfirmed input items exist on each mobile terminal 60 or what unconfirmed input items exist.

[0074] Although not shown in the diagram, the transaction status management device 40 comprises at least a CPU, a memory unit, a display unit (which may be configured as a touch panel), an operation unit (keyboard, mouse, etc.), and a communication unit. The transaction status management device 40 can communicate with a printing device (not shown), and various information may be output from the printing device.

[0075] (Example display on mobile device 60) Figure 3 shows an example of the display on the mobile device 60. It is assumed that application A is already installed on the mobile device 60.

[0076] (Initial screen 610) Figure 3(A) shows the initial screen 610 of the mobile device 60. The initial screen 610 is the standby screen (a state in which no applications are running). The icon 611 of application A is displayed on the initial screen 610.

[0077] (Menu screen 620) Figure 3(B) shows the menu screen 620 (start screen) that appears after the operation (press) of icon 611 on the initial screen 610. The menu screen 620 displays various buttons, such as the "Start Shopping with Cart" button 621a, which accepts the operation to start shopping using the cart 70, and the "Start Shopping without Cart" button 621b, which accepts the operation to start shopping without using the cart 70. If the "Start Shopping with Cart" button 621a is pressed, the mobile terminal 60 displays the menu screen 620 (Figure 3(C)). If the "Start Shopping without Cart" button 621b is pressed, the mobile terminal 60 displays the initial registration screen 640 (Figure 3(D)).

[0078] (Connection instruction screen 630) Figure 3(C) shows the connection instruction screen 630 that appears after the user presses the "Start Shopping with Cart" button 621a on the menu screen 620. The connection instruction screen 630 displays a message 631 instructing the user to read the 2D code 78 (connection code), and an explanatory image 632 describing how to read the 2D code 78.

[0079] After the mobile terminal 60 has completed its connection with the cart 70 by reading the 2D code 78 (for example, immediately after the connection is completed), it may send tare instruction information to the cart 70 and perform tare. Based on the operation of the "Start Shopping with Cart" button 621a on the menu screen 620, the mobile terminal 60 may display an announcement screen (not shown) on the front of the menu screen 620 that guides the user on how to place the shopping basket. For example, the mobile terminal 60 may display an announcement screen (not shown) with a message such as "If you are using one basket, please set it on the upper side (upper placement section 71). If you are using two baskets, please also set one on the lower side (lower placement section 72). When you have set them, please press the OK button," and an OK button. Based on the operation of the OK button, the announcement screen (not shown) may be cleared, and the connection instruction screen 630 may be displayed instead of the menu screen 620. In other words, the mobile terminal 60 may instruct the customer to set the tare before performing the tare calculation (before the 2D code 78 is read).

[0080] Furthermore, the mobile terminal 60 may display the above-mentioned announcement screen (not shown) in front of the connection instruction screen 630 based on the operation of the shopping start button 621a with cart usage on the menu screen 620. In other words, the mobile terminal 60 may display the above-mentioned announcement screen (not shown) after switching from the menu screen 620 to the connection instruction screen 630.

[0081] After the connection with the cart 70 is completed by reading the 2D code 78, the above announcement screen (not shown) may be displayed, and the small screen may be dismissed based on the operation of the OK button, and tare may be performed. By prompting the user to set the shopping basket at least before tare is performed, it is possible to prevent the problem that if the shopping basket is set after tare has been performed, the system may determine that an unregistered item has been added to the shopping basket.

[0082] You can encourage customers to bring their own bags or baskets. When customers start shopping using a shopping basket provided by the store, they have to transfer the items in the basket (purchased items) to their own bag or basket at the end of the shopping trip (before leaving the store, for example, after paying). However, when customers start shopping using their own bags or baskets, this transfer process is not necessary, allowing them to shop efficiently and without hassle.

[0083] The system may include a detection function to determine if a shopping basket or similar item has been placed in the basket. This detection function may operate while the announcement screen (not shown) is displayed. If a detection function is included, the system may detect that a shopping basket or similar item has been placed, and after tare weighting is performed, it may transition to the initial registration screen (Figure 3(D)).

[0084] The above detection function may also be used to detect a shopping basket by pre-registering (memorizing) the weight of the shopping basket and detecting that the shopping basket has been set when the measured value increases by that weight. The above detection function may also be used to detect a shopping basket (or reusable shopping bag, etc.) by pre-registering the appearance of the shopping basket and detecting that the shopping basket has been set using the image recognition function (image processing function) of the mobile terminal 60.

[0085] (Initial registration screen 640) Figure 3(D) shows the initial registration screen 640 that is displayed after the connection between the mobile terminal 60 and the cart 70 is completed (or after the operation of the "Start Shopping Without Cart Use" button 621b on the menu screen 620). The initial registration screen 640 is provided with an image capture display area 641 and a registration information display area 642. The image capture display area 641 is mainly for displaying the captured image. The central part of the image capture display area 641 is a barcode reading area suitable for reading barcodes. The barcode reading area is a rectangular area where the message "Please hold the barcode over the device" is displayed. The registration information display area 642 is mainly for displaying product registration information (transaction details) and total information. An explanatory image 643 is displayed in front of the registration information display area 642. The explanatory image 643 is an image that explains how to register a product. Note that the explanatory image 643 may be set so that it is not displayed on subsequent visits.

[0086] Additionally, a cart image 644 is displayed at the top of the initial registration screen 640 (image display area 641). The cart image 644 indicates that a connection (communication possible) is established with the cart 70. The cart image 644 is always displayed as long as a connection with the cart 70 is established.

[0087] Furthermore, the image captured from the position of the holder 76, looking down at the shopping basket, includes the shopping basket and, after items have been placed in it, the items after they have been placed in the basket. However, for the sake of simplification, the shopping basket and the items after they have been placed in the basket are not shown in Figure 3.

[0088] (Registration screen 650) Figure 3(E) shows the registration screen 650 that appears after product registration. Specifically, the registration screen 650 in Figure 3(E) shows a scenario where XX bread has been registered as the first product item and XX oolong tea has been registered as the second product item. More specifically, the captured image display area 641 of the registration screen 650 in Figure 3(E) shows (captured) XX oolong tea. In other words, the registration screen 650 in Figure 3(E) shows the scene immediately after XX oolong tea has been registered (immediately after scanning) and before XX oolong tea is placed in the cart 70 (shopping basket).

[0089] The mobile terminal 60 obtains product information by querying the product information based on the product code obtained by scanning the product's barcode. The query for product information is directed to a device that stores the product master. The device that stores the product master may be another device (for example, the cloud server 20), or it may be the terminal itself if the product master is stored in the terminal's own memory.

[0090] As explained earlier, the product master is a file that stores product information (product name, price, weight, etc.) associated with product codes (product identification information). However, the product master can also manage weight data for in-store products (prepared in-store products) in addition to the weight data for manufacturer products (purchased products). The weight data for manufacturer products is, for example, the weight data provided by the manufacturer. The weight data for in-store products may be the weight data obtained from the equipment used in the weighing and pricing process (weighing and pricing process) after the product has been processed in the store (for example, a label printer with a weighing function, or a packaging machine with a packaging function).

[0091] The weight data for manufacturer products and the weight data for in-store products may be managed on different servers (different product masters). If the weight data for manufacturer products and the weight data for in-store products are managed on different servers, the mobile terminal 60 may switch the server to refer to based on the product code obtained by scanning, or it may refer to one server based on the product code obtained by scanning, and if it is not possible to obtain the product information for that product, it may refer to the other server.

[0092] Note that the product code for manufacturer products is, for example, a standardized code (JAN code). The product code for in-store products is a code that is valid within the store (in-store code). In-store codes are basically a different coding system from JAN codes. JAN codes include manufacturer identification information and product identification information (but do not include weight), whereas in-store codes do not include manufacturer identification information (they may include at least one of product name, price, or weight). In other words, although it was explained that the product master stores product information (product name, price, weight, etc.) associated with the product code (product identification information), in the case of in-store products, it may be possible to obtain at least one of product name, price, or weight from the product code (in-store code) itself.

[0093] The registration information display area 642 displays information about the registered product (product name, quantity, price) as registration information. In the example in Figure 3(E), the registration information display area 642 displays "XX Bread, x1, ¥220" as the first product item and "XX Oolong Tea, x1, ¥150" as the second product item. "x1" means a quantity of "1". The quantity is displayed as the quantity button 653. In addition, the registration information display area 642 displays "Estimated Total 2 items ¥370" as total information.

[0094] Furthermore, when the quantity button 653 is operated, the mobile terminal 60 displays a small quantity change screen (not shown) in front of the registration screen 650. The small quantity change screen displays buttons such as a cancel button, minus button, plus button, and cancel button. The customer can change (increase or decrease) the quantity to be purchased or cancel the purchase (cancel registration) on the small quantity change screen. For example, if the customer wants to increase the quantity of XX bread, they operate the quantity button 653 in the XX bread column and then operate the plus button on the small quantity change screen that appears after the operation. The same applies if they want to decrease the quantity or cancel the purchase.

[0095] In the registration information display area 642, the column for XX bread displays "Weight OK". "Weight OK" indicates that the weight check was successful. In other words, after registering a product, the mobile terminal 60 monitors whether the product has been placed in the shopping basket within a predetermined time. If there is an increase in the weight (increase in the measured value) of the product within the predetermined time, it displays "Weight OK" for that product. In the scene shown in Figure 3(E), XX oolong tea has not been placed in the shopping basket, so "Weight OK" is not displayed in the column for XX oolong tea.

[0096] The mobile terminal 60 can accept the operation to end product registration and proceed to checkout after registering one product item. The checkout start button 651 on the registration screen 650 is a button that accepts the start of checkout (end of product registration). Message 652 is a message that guides the user on how to proceed to checkout (operation of the checkout start button 651).

[0097] (Forgot to insert the data - small screen 660) Figure 3(F) shows the registration screen 650 and the small "forgotten item" screen 660 on the front of the registration screen 650. If the mobile terminal 60 determines that an item has been forgotten to be inserted (if the item is not inserted within a predetermined time after product registration (or after the quantity has been increased)), it displays the "forgotten item" screen 660 on the front of the registration screen 650, as shown in Figure 3(F). The "forgotten item" screen 660 displays that it is an error due to an item being forgotten to be inserted and that a store clerk may check it at checkout. The mobile terminal 60 displays the "forgotten item" screen 660 for a predetermined time (for example, 2 seconds). In other words, the mobile terminal 60 clears the "forgotten item" screen 660 after a predetermined time (for example, 2 seconds) has elapsed since the display of the "forgotten item" screen 660 began.

[0098] (Forgot to register? Mini-screen 670) Figure 3(G) shows the registration screen 650 and the registration forgetting screen 670 in front of the registration screen 650. If the mobile terminal 60 determines that registration has been forgotten (if an item is added without registering the item (or increasing the quantity)), it displays the registration forgetting screen 670 in front of the registration screen 650, as shown in Figure 3(G). The registration forgetting screen 670 displays that it is a registration forgetting error and that a store clerk may check it at checkout. The mobile terminal 60 displays the registration forgetting screen 670 for a predetermined time (for example, 2 seconds). In other words, the mobile terminal 60 erases the registration forgetting screen 670 after a predetermined time (for example, 2 seconds) has elapsed since the start of its display.

[0099] (Settlement code display screen 680) Figure 6(H) shows the payment code display screen 680 that appears after the payment start button 651 on the registration screen 650 is pressed. The payment code display screen 680 displays the payment code 681 (described later), a message 682 instructing the payment machine (payment device 50) to read the payment code 681, and an explanatory image 683 explaining how to read the payment code 681 on the payment machine. The payment code display screen 680 also displays a "return to shopping" button 684. When the "return to shopping" button 684 is pressed, the mobile terminal 60 displays the registration screen 650 that was displayed before the payment start button 651 was pressed.

[0100] The settlement code 681 is a two-dimensional code representing transaction identification information that identifies the transaction information of a particular transaction from among multiple transaction information (including information such as weight OK) stored in the cloud server 20. In other words, the settlement code 681 displayed by a mobile terminal 60 indicates information that can identify the transaction information of that mobile terminal 60 from among multiple transaction information stored in the cloud server 20. When the settlement device 50 reads the settlement code 681, it requests the cloud server 20 to transmit the transaction information including the transaction identification information, and obtains (receives) the transaction information of the mobile terminal 60 from the cloud server 20. Note that the settlement code 681 may also be a two-dimensional code representing the location information of the transaction information of the mobile terminal 60 (storage location within the sales system 1, such as a URI (Uniform Resource Identifier)).

[0101] Figure 4 is a flowchart illustrating an example of the operation of the mobile terminal 60. Specifically, the flowchart in Figure 4 shows the operation in the stages of product registration and loading. The flowchart in Figure 4 is executed repeatedly after connecting with the cart 70 (Bluetooth connection).

[0102] Step S1: The mobile terminal 60 determines whether a product has been scanned. If a product has been scanned (Step S1: YES), proceed to Step S2. If no product has been scanned (Step S1: NO), proceed to Step S4.

[0103] Step S2: The mobile terminal 60 registers the product (the scanned product). Then proceed to step S3. Step S3: The mobile terminal 60 stores the information of the item (scanned item) in the waiting list as an item awaiting input. Then proceed to step S4.

[0104] Step S4: The mobile terminal 60 determines whether the measured value has increased. For example, the mobile terminal 60 determines that the measured value has increased if the measured value received as weighing information from the cart 70 (the current measured value) is greater than the measured value stored in its memory unit (the previous measured value). The mobile terminal 60 may also determine that the measured value has increased if it receives a weight increase notification (or an increase in the measured value) from the cart 70. If it determines that the measured value has increased (Step S4: YES), proceed to Step S5. If it determines that the measured value has not increased (Step S4: NO), proceed to Step S12.

[0105] Step S5: The mobile terminal 60 determines whether there is a corresponding product awaiting input (a product awaiting input corresponding to the increase in the weighed value). The mobile terminal 60 determines that there is a corresponding product awaiting input if there is a product awaiting input corresponding to the increase in the weighed value (a product awaiting input where the difference between the weight of the product awaiting input and the increase in the weighed value is within a predetermined range that is acceptable as an error). On the other hand, if the mobile terminal 60 does not store the product awaiting input list (or if there is no product awaiting input stored in the product awaiting input list), or if it stores the product awaiting input list but there is no product awaiting input corresponding to the increase in the weighed value, it determines that there is no corresponding product awaiting input. Note that the determination that there is no corresponding product awaiting input is a determination that registration has been forgotten. If it is determined that there is a corresponding product awaiting input (Step S5: YES), proceed to Step S6. If it is determined that there is no corresponding product awaiting input (determined as registration forgotten) (Step S5: NO), proceed to Step S10.

[0106] Step S6: The mobile terminal 60 removes the product (the product awaiting input) from the input waiting list. Then proceed to step S12.

[0107] Step S10: The mobile terminal 60 notifies the customer about the forgotten registration. Specifically, the mobile terminal 60 displays a small screen 670 (Figure 3(G)) indicating the forgotten registration (with or without voice) in front of the registration screen 650 (initial registration screen 640 before registering one item). The mobile terminal 60 also displays "<Forgotten Registration>" and the increased weight (the measured value determined to have increased in step S4) in the registration information display area 642. The process then proceeds to step S11.

[0108] The mobile terminal 60 erases the registration forgetting screen 670 when a predetermined time (for example, 2 seconds) has elapsed since the start of display. If the timing of step S10 occurs while the registration forgetting screen 670 is being displayed (i.e., the timing of step S10 is before the already displayed registration forgetting screen 670 is erased), the mobile terminal 60 redisplays (erases, displays) the registration forgetting screen 670 and displays it for a predetermined time from the redisplay. In the above case, the mobile terminal 60 may simply continue displaying without redisplaying. If the display of the registration forgetting screen 670 is continued, the predetermined time until erasure may be cleared (i.e., a new erasure timing may be set from that timing), or the predetermined time until erasure may not be cleared (i.e., the already set erasure timing may be maintained). After erasing the registration forgetting screen 670, the mobile terminal 60 may display "<Registration Forgotten>" and the increased weight in the registration information display area 642 to indicate that registration was forgotten.

[0109] Step S11: The mobile terminal 60 stores the information of the product (the product that was put in) in the unregistered product list as an unregistered product. Then proceed to step S12.

[0110] Step S12: The mobile terminal 60 determines if there are any items waiting to be loaded that have timed out. If it determines that there are items waiting to be loaded that have timed out (Step S12: YES), proceed to Step S13. Note that determining that there are items waiting to be loaded that have timed out means that an item has been forgotten to be loaded. If it determines that there are no items waiting to be loaded that have timed out (Step S12: NO), this flowchart ends (i.e., return to Step S1).

[0111] Step S13: The mobile terminal 60 stores the information of the product (the product that timed out and was awaiting input) in the unconfirmed input list as an unconfirmed input product. The process then proceeds to step S14. Step S14: The mobile terminal 60 removes the item (the item that timed out and was waiting to be loaded) from the loading list. Then proceed to step S15.

[0112] Step S15: The mobile terminal 60 notifies the customer about the forgotten payment. Specifically, the mobile terminal 60 displays a small screen 660 (Figure 3(F)) indicating the forgotten payment, either with or without voice, in front of the registration screen 650. The mobile terminal 60 also displays "Forgotten Payment" in the registration information display area 642. Then, this flowchart ends (i.e., returns to step S1).

[0113] The mobile terminal 60 erases the forgotten payment screen 660 after a predetermined time (for example, 2 seconds) has elapsed since the start of display. If the timing of step S15 occurs while the forgotten payment screen 660 is being displayed, the mobile terminal 60 redisplays (erases, displays) the forgotten payment screen 660 and displays it for a predetermined time from the redisplay. In the above case, the mobile terminal 60 may simply continue displaying without redisplaying. If the display of the forgotten payment screen 660 is continued, the predetermined time until erasure may be cleared (i.e., a new erasure timing may be set from that timing), or the predetermined time until erasure may not be cleared (i.e., the already set erasure timing may be maintained).

[0114] (Supplementary Explanation of Steps S5 and S6) As described above, when there is an input-waiting product corresponding to the increase in the measured value (the input-waiting product whose difference between the weight of the input-waiting product and the increase in the measured value is within a predetermined range allowed as an error) in the input-waiting list in the mobile terminal 60, it is determined that there is a corresponding input-waiting product (step S5 (YES)), and the product (the corresponding input-waiting product) is deleted from the input-waiting list (step S6). However, in the following scenarios (1) to (3), it may operate as follows respectively.

[0115] In this supplementary explanation, assume that the weight of the input-waiting product a is "Wa", the weight of the input-waiting product b is "Wb", the weight of the input-waiting product c is "Wc", the increase in the measured value is "Wg", and the predetermined range allowed as an error is "Wth".

[0116] (1) When there are multiple input-waiting products whose difference between the weight of the input-waiting product and the increase in the measured value is within a predetermined range allowed as an error, delete the input-waiting product with the weight closest to the increase in the measured value (that is, the input-waiting product with the smallest difference as described above) from the input-waiting list.

[0117] For example, when the difference "Wda" between Wa and Wg is within Wth, and the difference "Wdb" between Wb and Wg is within Wth, if Wda < Wdb, delete the input-waiting product a from the input-waiting list; if Wdb < Wda, delete the input-waiting product b from the input-waiting list.

[0118] (2) When the difference between the total weight of two or more input-waiting products and the increase in the measured value is within a predetermined range allowed as an error, delete the two or more input-waiting products from the input-waiting list (except when it corresponds to the following (3)).

[0119] For example, if the difference between the total weight of Wa and Wb ("Wab") and Wg ("Wdab") is within Wth, then items a and b awaiting input will be removed from the input waiting list. Also, for example, if the difference between the sum of Wa, Wb, and Wc and Wg ("Wdabc") is within Wth, then items a, b, and c awaiting input will be removed from the input waiting list.

[0120] (3) If the difference between the total weight of two or more items awaiting input and the increase in the measured value is within a predetermined range that is permissible as an error, and the difference between the weight (or total weight) of one other item awaiting input and the increase in the measured value is within a predetermined range that is permissible as an error, the other item awaiting input is removed from the list of items awaiting input.

[0121] For example, if the difference between the total weight of Wa and Wb, "Wab," and Wg, "Wdab," is within Wth, and the difference between Wc and Wg, "Wdc," is also within Wth, meaning there is a possibility of simultaneous input of waiting product a and waiting product b, and a possibility of input of waiting product c, then waiting product c will be removed from the waiting list. This is to ensure that the system operates as correctly as possible, even if the products that are actually input and the products that are removed do not match. In other words, the policy of "deleting pending product a and pending product b" cannot accommodate the input of pending product a (or pending product b) after "inputting pending product c → deleting pending product a and pending product b," whereas the policy of "deleting pending product c" can accommodate the input of pending product c after "inputting pending product a and pending product b simultaneously → deleting pending product c." (As per (2) above), if there is a possibility of simultaneous input of pending product a and pending product b, and a possibility of input of pending product c, pending product c is deleted from the pending list, taking into consideration the possibility that pending product a (or pending product b) may be input later.

[0122] Figures 5 to 13 are explanatory diagrams illustrating the series of steps involved in registering and inputting products. In Figures 5 to 13, the left side (Figure 5(A), Figure 6(A), ..., Figure 13(A)) shows the display contents of the registration information display area 642 (excluding total information), while the right side (Figure 5(B), Figure 6(B), ..., Figure 13(B)) shows the stored contents of various lists.

[0123] In Figures 5 to 13, the customer is assumed to have scanned the product (obtained the product code for the product) or placed the product in the machine using the following operating procedure (steps 1 to 8). Step 1: Scan product A (product name "A"). Step 2: Scan product B (product name "B"). Step 3: Scan product C (product name "C"). Step 4: Add product B. Step 5: Add product A. Step 6: Scan product D (product name "D"). Step 7: Add product D. Step 8: Add product C.

[0124] The product master data is assumed to contain the following information for products A through D. Product code "49...1": Product name "A", price "¥250", weight "71 (grams)", etc. Product code "49...2": Product name "B", price "¥120", weight "35 (grams)", etc. Product code "49...3": Product name "C", price "¥460", weight "50 (grams)", etc. Product code "49...4": Product name "D", price "¥180", weight "64 (grams)", etc.

[0125] Figure 5(A) shows the display content of the registration information display area 642 at the point when steps 1 through 3 have been completed, specifically when the customer has scanned product code "45...1" for product A as the first item, scanned product code "45...2" for product B as the second item 10 seconds later, and scanned product code "45...3" for product C as the third item 4 seconds later. Figure 5(B) shows the contents of the waiting list at the point described above.

[0126] According to the flowchart in Figure 4, the mobile terminal 60 scans product code "45...1" for product A and stores information about product A in the waiting list as a product awaiting input (step S3). After scanning product code "45...2" for product B, it stores information about product B in the waiting list as a product awaiting input (step S3). After scanning product code "45...3" for product C, it stores information about product C in the waiting list as a product awaiting input (step S3). Note that the remaining time for products A and B (initial value 30 seconds timer) decreases as time passes. The same applies to the decrease in remaining time from Figure 6 onwards.

[0127] Figure 6(A) shows the display content of the registration information display area 642 at the point where step 4 has been completed, specifically, when the customer has inserted product B 5 seconds after the scene in Figure 5. Figure 6(B) shows the contents of the waiting list at the same point.

[0128] According to the flowchart in Figure 4, upon inputting product B, the mobile terminal 60 determines that the measured value has increased (step S4 (YES)), determines that product B is the relevant product (step S5 (YES)), and removes product B from the input waiting list (step S6).

[0129] Figure 7(A) shows the display content of the registration information display area 642 at the point when step 5 has been completed, specifically, when the customer has inserted product A 4 seconds after the scene in Figure 6. Figure 7(B) shows the contents of the waiting list at the same point.

[0130] According to the flowchart in Figure 4, upon inputting product A, the mobile terminal 60 determines that the measured value has increased (step S4 (YES)), determines that product A is the relevant product (step S5 (YES)), and removes product A from the input waiting list (step S6).

[0131] Figure 8(A) shows the display content of the registration information display area 642 at the point when steps 1 through 6 have been completed, specifically, when the customer has finished scanning product code "45...4" for product D as the fourth item, 8 seconds after the scene in Figure 7. Figure 8(B) shows the contents of the waiting list at the same point in the scene described above.

[0132] According to the flowchart in Figure 4, after scanning the product code "45...4" of product D, the mobile terminal 60 stores the information of product D in the waiting list as a product awaiting input (step S3).

[0133] Figure 9(A) shows the display content of the registration information display area 642 during the period between steps 6 and 7, specifically, 13 seconds after the scene in Figure 8, without any scanning or input. Figure 9(B) shows the contents of the input waiting list in the above scene.

[0134] According to the flowchart in Figure 4, the mobile terminal 60 determines that product C is a timed-out product waiting to be inserted (step S12 (YES)), stores product C's information in the unconfirmed insertion list as an unconfirmed insertion product (step S13), removes product C from the waiting list (step S14), and displays the forgotten insertion screen 660 as a notification of the forgotten insertion (step S15). The mobile terminal 60 also displays "Forgotten Insertion" in the registered information display area 642 to indicate that the product has been forgotten to be inserted (step S15). Note that in Figure 9(A), "Forgotten Insertion" is hidden by the front small screen 660.

[0135] Figure 10(A) shows the display content of the registration information display area 642 in the scene between steps 6 and 7, specifically, the scene 2 seconds after the scene in Figure 9 when no scanning or insertion has occurred. Figure 10(B) shows the contents of the waiting list in the above scene. In other words, the mobile terminal 60 clears the forgotten insertion screen 660 because 2 seconds have passed since the start of the forgotten insertion screen 660 display.

[0136] Figure 11(A) shows the display content of the registration information display area 642 at the point where steps 1 through 7 have been completed, specifically, when the customer inserts product D 6 seconds after the scene in Figure 10. Figure 11(B) shows the contents of the waiting list at the same point.

[0137] According to the flowchart in Figure 4, upon inputting product D, the mobile terminal 60 determines that the weighed value has increased (step S4 (YES)), identifies product D as the relevant product (step S5 (YES)), and removes product D from the waiting list (step S6). In the example in Figure 11, the waiting list itself is deleted because there are no more products waiting to be input, but it is also acceptable to retain an empty waiting list.

[0138] Figure 12(A) shows the display content of the registration information display area 642 at the point when steps 1 through 8 have been completed, specifically, when the customer has inserted product C X seconds after the scene in Figure 11. Figure 12(B) shows the contents of the waiting list at the same point.

[0139] According to the flowchart in Figure 4, upon inputting product C, the mobile terminal 60 determines that the weighed value has increased (step S4 (YES)) and determines that there is no corresponding product (step S5 (NO)). In other words, the mobile terminal 60 determines that there is no corresponding product because product C, which was input, is not on the input waiting list (step S5 (NO)). Next, the mobile terminal 60 displays a small screen 670 indicating that registration has been forgotten as a notification of the forgotten product (step S10), and stores the information of product C in the unconfirmed registration list as an unconfirmed registration product (step S11). The mobile terminal 60 also displays "<Forgotten Registration>" and the increased weight "50g" in the registration information display area 642 (step S10).

[0140] Figure 13(A) shows the display content of the registration information display area 642 in the scene after step 8, specifically, the scene 2 seconds after the scene in Figure 12 without scanning or input. Figure 13(B) shows the contents of the input waiting list in the above scene. In other words, the mobile terminal 60 clears the registration forgetfulness mini-screen 670 because 2 seconds have passed since the start of the registration forgetfulness mini-screen 670 display.

[0141] (Submitted after timeout) According to Figures 4 to 13, if an item is registered but then inserted after a timeout (i.e., an item is inserted after a predetermined amount of time has passed since registration), the mobile terminal 60 displays a small screen 670 indicating that an item has been forgotten to register, displays "<Registration Forgotten>" etc. in the registration information display area 642, and stores it in the unconfirmed registration list (Figures 12 and 13). In other words, if an item that has gone from being a pending item to an unconfirmed item due to a timeout is inserted, the mobile terminal 60 processes it as if it were an item that had been forgotten to register (unconfirmed registration), just as if the item had been inserted without registration.

[0142] (Another example of input after a timeout) As an alternative example, if registration is performed but the data is submitted after a timeout, the process may be carried out as follows. Specifically, the process may proceed from step S5 (NO) in Figure 4 to step S7 (not shown).

[0143] Step S7 (not shown): The mobile terminal 60 determines whether there is an unconfirmed product in the list of unconfirmed products that corresponds to the increase in the weighed value (an unconfirmed product whose difference between its weight and the increase in the weighed value is within a predetermined range that is allowed as an error). If there is an unconfirmed product that corresponds to the increase in the weighed value (Step S7: YES), proceed to Step S8 (not shown). If there is no unconfirmed product that corresponds to the increase in the weighed value (Step S7: NO), proceed to Step S10 in Figure 4 (the process proceeds as shown in Figure 4 thereafter).

[0144] Step S8 (not shown): The mobile terminal 60 determines whether a predetermined time (e.g., 10 seconds) has elapsed since the time the product (the unconfirmed product corresponding to the increase in the weighed value) became an unconfirmed product (the timeout time) (i.e., whether the product was added within the predetermined time after the timeout). If the predetermined time has not elapsed, i.e., the product was added within the predetermined time after the timeout (Step S8: YES), proceed to Step S9 (not shown). If the predetermined time has elapsed (Step S8: NO), proceed to Step S10 in Figure 4 (the process proceeds as shown in Figure 4 thereafter).

[0145] Step S9 (not shown): The mobile terminal 60 removes the product from the list of unconfirmed entries. The process then proceeds to step S12 in Figure 4 (the process continues as shown in Figure 4).

[0146] According to the above process (steps S7-S9), if an item that has become an unconfirmed item from the items awaiting input due to a timeout is input within a predetermined time after the timeout, it will be removed from the unconfirmed input list (step S7 (YES) → step S8 (YES) → step S9 → step S12). In other words, if an item that has become an unconfirmed item from the items awaiting input due to a timeout is input within a predetermined time after the timeout, that item will be removed from the unconfirmed input list (step S9). In other words, it will not be subject to staff intervention (calling a staff member). Note that this input will not be processed as a registration oversight (steps S10 and S11 will not be executed).

[0147] Alternatively, the step S8 judgment (determining whether the item was inserted within the specified time after the timeout) may be omitted, and the process may proceed directly to step S7 (YES) → step S9. In other words, items that have changed from items awaiting insertion to items not yet confirmed to be inserted due to a timeout may be excluded from staff intervention (calling a staff member) regardless of when they are inserted before proceeding to checkout (before pressing the checkout start button 651).

[0148] Furthermore, although it was explained that the process in step S9 involves removing the product in question (the product corresponding to the increase in the weighed value) from the list of unconfirmed inputs, it is also possible to add information indicating that the product is not subject to staff intervention (for example, an exclusion flag) instead of removing the product from the list of unconfirmed inputs. In other words, if a product that went from being a product waiting to be input to an unconfirmed input product due to a timeout is input within a predetermined time after the timeout, it may be excluded from the list of products subject to staff intervention, but a record of it being an unconfirmed input product may be kept.

[0149] (Cancellation (deletion) of items whose input has not been confirmed) As mentioned above, registered items can be canceled by operating the corresponding quantity button 653. The same applies to items that have been registered but not added to the shopping cart, i.e., unconfirmed items (items forgotten to be added).

[0150] If a customer cancels an item that has been successfully placed in the shopping cart (an item that has not been checked for placement), they remove the canceled item from the shopping cart and return it to the store (to its original display shelf) (or place it in a designated holding bag located in a place where it will not be weighed). If a cancellation operation is performed on an item that has been successfully placed in the shopping cart, and the item is not removed from the shopping cart within a predetermined time (for example, 10 seconds) from the cancellation operation (i.e., the weight of the item does not decrease), the mobile terminal 60 notifies the customer that the canceled item has not been removed.

[0151] On the other hand, if a customer cancels an unverified item, they do nothing because the item is no longer in their shopping basket. The mobile terminal 60 does not notify the customer that the canceled item has not been removed from their shopping basket, even if the item is not removed within a specified time after the cancellation operation.

[0152] For example, in the scenario shown in Figure 10(A), if the customer cancels product A (a product that was properly loaded) and it is not retrieved within a specified time, the mobile terminal 60 will notify the customer that the canceled product A has not been retrieved. However, in the scenario shown in Figure 10(A), if the customer cancels product C (a product that has not been loaded or verified), the mobile terminal 60 will not notify the customer that the canceled product C has not been retrieved, even if it is not retrieved within a specified time.

[0153] Furthermore, if an unconfirmed item is canceled, it may be deleted from the unconfirmed item list, or it may not be deleted, or a flag or other indication that a cancellation operation has been performed may be added instead of deleting it. For example, in the scenario shown in Figure 10(A), if the customer cancels item C, the information for item C may be deleted from the unconfirmed item list in Figure 10(B), or it may not be deleted, or a flag or other indication that a cancellation operation has been performed may be added to the information for item C.

[0154] (Sending and receiving information between the mobile terminal 60 and the cloud server 20, and storing information) The transmission and reception of information between the mobile terminal 60 and the cloud server 20, and the storage of information, may be implemented by any of the following methods (methods A to F), or by appropriately combining a part of one method with a part of another method.

[0155] <Mode A> Each time the mobile terminal 60 obtains a product code, it stores the product code in its memory and transmits the product code to the cloud server 20. Upon receiving the product code from the mobile terminal 60, the cloud server 20 refers to the product master, obtains the product information (product name, price, etc.) corresponding to the product code, and transmits (responds to) the obtained product information to the mobile terminal 60. When the cloud server 20 receives a product code from the mobile terminal 60 each time, as described above, it transmits the product information obtained from the product code to the mobile terminal 60, but does not store the product code or the product information obtained from the product code in the transaction information of the mobile terminal 60. The above part of A is the same as in Aspect B described below.

[0156] The mobile terminal 60, having received the product information from the cloud server 20 after sending the acquired product code to the cloud server 20, stores the product information in its memory as registration information for that product, associating it with the product code. When the mobile terminal 60 has finished registering (when the checkout start button 651 is pressed), it simultaneously sends the product codes of one or more products stored in its memory to the cloud server 20. The cloud server 20, having received the product codes of one or more products from the mobile terminal 60, refers to the product master, retrieves the product information corresponding to each product code, associates the retrieved product information with each product code, and stores it in the transaction information of the mobile terminal 60 as registration information for each product. In other words, the cloud server 20 does not store the mobile terminal 60's individual product registration information in its transaction information each time the mobile terminal 60 acquires an individual product code, but rather stores the registration information of one or more products from the mobile terminal 60 in its transaction information when the mobile terminal 60 has finished registering the products. According to the Aspect A (and similarly for the B, D, and E aspects), the cloud server 20 does not update the transaction information of each mobile terminal 60 each time each mobile terminal 60 acquires a product code (it does not add registration information, etc.), so there is no processing load on the cloud server 20 that would occur if the transaction information of each mobile terminal 60 were updated (for example, searching for target transaction information or writing information). Furthermore, because there is no processing load as described above each time each mobile terminal 60 acquires a product code, the response time when the mobile terminal 60 acquires a product code (updating the registration screen 650, etc.) is improved. In addition, even if the number of product codes acquired by the mobile terminal 60 by the time registration is completed is N (even if N products are registered in one transaction), the search process to search for the transaction information to be updated (pre-processing before updating) only needs to be done once (i.e., the total lead time for one transaction is compressed to one), making it efficient. Furthermore, according to embodiment A, compared to embodiment B, the amount of information transmitted and received between the mobile terminal 60 and the cloud server 20 after the mobile terminal 60 has completed registration can be reduced.

[0157] <Mode B> The mobile terminal 60, having received the acquired product code and sent it to the cloud server 20, stores the product information in its memory unit, associating it with the product code, as registration information for that product. When the mobile terminal 60 has finished registering, it simultaneously sends the registration information for one or more products (one or more product codes, and the product information corresponding to each product code) stored in its memory unit to the cloud server 20. In other words, in morphology A, the mobile terminal 60 simultaneously sends the product codes for one or more products to the cloud server 20 when it has finished registering, whereas in morphology B, the mobile terminal 60 simultaneously sends the registration information for one or more products to the cloud server 20 when it has finished registering. The cloud server 20, having received the registration information for one or more products from the mobile terminal 60, stores the received registration information in the transaction information of the mobile terminal 60. According to morphology B (and similarly in morphology E), the cloud server 20 obtains the product registration information from each mobile terminal 60 when each mobile terminal 60 has finished registering, so it does not need to refer to the product master when each mobile terminal 60 has finished registering. Therefore, in embodiment B, the cloud server 20 does not have to refer to the product master and retrieve product information for each product when each mobile terminal 60 has finished registering.

[0158] <Aspect C> Each time the mobile terminal 60 acquires a product code, it stores the product code in its memory and transmits the product code to the cloud server 20. Upon receiving the product code from the mobile terminal 60, the cloud server 20 refers to the product master, acquires the product information corresponding to the product code, transmits the acquired product information to the mobile terminal 60, and stores the registration information of the product in the transaction information of the mobile terminal 60. In other words, in modes A and B, the cloud server 20 does not update the transaction information of the mobile terminal 60 each time it acquires a product code from the mobile terminal 60, whereas in mode C, it updates the transaction information of the mobile terminal 60 each time it acquires a product code from the mobile terminal 60. According to mode C (and similarly in mode F), when the mobile terminal 60 has finished registering, it does not need to transmit the information stored in its memory (product codes for one or more products, registration information for one or more products) to the cloud server 20, thus reducing the amount of communication between the mobile terminal 60 and the cloud server 20 when the registration is completed. Furthermore, according to the C configuration (and the F configuration as well), when the mobile terminal 60 has finished registering, the cloud server 20 does not have the burden of referring to the product master based on the product code obtained from the mobile terminal 60 to obtain product information and storing the obtained product information in the transaction information (the burden in the A configuration), nor does it have the burden of storing the product information obtained from the mobile terminal 60 in the transaction information (the burden in the B configuration).

[0159] <Mode D> The mobile terminal 60 receives product master data from another device (for example, the cloud server 20) and stores it in its storage unit. Each time a product code is acquired, the mobile terminal 60 refers to the product master data stored in its storage unit to obtain product information for that product code, and stores the product information in its storage unit, associating it with the product code, as registration information for that product. The above part of Embodiment D is the same as Embodiment E described below.

[0160] When the mobile terminal 60 has finished registration, it simultaneously sends the product codes of one or more products stored in its memory unit to the cloud server 20 (hereinafter the same as in Mode A). In other words, in Mode A the cloud server 20 refers to the product master, while in Mode D the mobile terminal 60 refers to the product master. According to Mode D (and similarly in Mode E), the mobile terminal 60 does not need to send the product code to the cloud server 20 each time it obtains a product code. Also, according to Mode D (and similarly in Mode E), the cloud server 20 does not have the burden of referring to the product master to obtain product information and sending the obtained product information to the mobile terminal 60 each time the mobile terminal 60 obtains a product code.

[0161] <Mode E> When the mobile terminal 60 has finished registering, it simultaneously sends the registration information of one or more products stored in its memory unit to the cloud server 20 (hereinafter the same as in Mode B). In other words, the difference is that in Mode B the cloud server 20 refers to the product master, while in Mode E the mobile terminal 60 refers to the product master. Alternatively, in Mode D, when the mobile terminal 60 has finished registering, it simultaneously sends the product codes of one or more products to the cloud server 20, while in Mode E the mobile terminal 60 simultaneously sends the registration information of one or more products to the cloud server 20.

[0162] <Pattern F> The mobile terminal 60 receives product master data from another device and stores it in its memory. Each time the mobile terminal 60 obtains a product code, it refers to the product master data stored in its memory to obtain product information for that product code, stores the product information in its memory as registration information for that product and associates it with the product code, and also transmits the product information to the cloud server 20. The cloud server 20 stores the product information received from the mobile terminal 60 as registration information in the transaction information of the mobile terminal 60. In other words, the difference between mode C and mode F is that in mode C, the cloud server 20 refers to the product master data, while in mode F, the mobile terminal 60 refers to the product master data.

[0163] Although it was explained that the cloud server 20 may consist of multiple servers, for example, it may consist of a cloud server 20A that stores the product master and a cloud server 20B that stores the transaction information of each mobile terminal 60.

[0164] In the configuration consisting of cloud server 20A and cloud server 20B, in embodiments A to C, the mobile terminal 60 sends the product code to cloud server 20A each time it obtains a product code, and cloud server 20A, upon receiving the product code, obtains product information by referring to the product master. Alternatively, in embodiments A to C, the mobile terminal 60 may send the product code to cloud server 20B each time it obtains a product code, and cloud server 20B, upon receiving the product code, may query cloud server 20A for product information corresponding to that product code.

[0165] In the configuration consisting of cloud server 20A and cloud server 20B, in Mode A (and similarly in Mode D), the mobile terminal 60 that has completed registration simultaneously transmits the product codes of one or more products stored in its memory unit to the cloud server 20A. The cloud server 20A refers to the product master, obtains the product information for each product, and transmits (supplies) the product information along with the product code to the cloud server 20B. The cloud server 20B stores the registration information for each product in the transaction information of the mobile terminal 60. Alternatively, in Mode A (and similarly in Mode D), the mobile terminal 60 that has completed registration simultaneously transmits the product codes of one or more products stored in its memory unit to the cloud server 20B. The cloud server 20B may query the cloud server 20A for product information corresponding to each product code, and store the product information obtained from the query, along with the product code, in the transaction information of the mobile terminal 60 as the registration information for each product.

[0166] In the case where the system consists of cloud server 20A and cloud server 20B, in embodiment B (and the same applies to embodiment E), the mobile terminal 60 that has completed registration may simultaneously transmit the registration information of one or more products stored in its memory unit to the cloud server 20B, and the cloud server 20B may store this information in the transaction information of the mobile terminal 60. In embodiment B (and the same applies to embodiment E), the mobile terminal 60 that has completed registration may simultaneously transmit the registration information of one or more products stored in its memory unit to the cloud server 20A, the cloud server 20A may transmit (transfer) the registration information of the one or more products to the cloud server 20B, and the cloud server 20B may store this information in the transaction information of the mobile terminal 60.

[0167] When the system consists of cloud server 20A and cloud server 20B, in embodiments D to F, the mobile terminal 60 may receive product master data from cloud server 20A and store it in its storage unit.

[0168] In the configuration consisting of cloud server 20A and cloud server 20B, in embodiment F, each time a product code is acquired, the mobile terminal 60 refers to the product master stored in its memory to acquire product information for that product code, stores the product information in its memory as registration information for that product and associates it with the product code, and transmits the product information to cloud server 20B. In embodiment F, each time a product code is acquired, the mobile terminal 60 refers to the product master stored in its memory to acquire product information for that product code, stores the product information in its memory as registration information for that product and associates it with the product code, and transmits the product information to cloud server 20A, cloud server 20A transmits (transfers) the registration information for one or more products to cloud server 20B, and cloud server 20B may store it in the transaction information of the mobile terminal 60.

[0169] Even if the cloud server 20 stores the registration information for one or more products together when the mobile terminal 60 has finished registering the products (Modes A, Mode B, Mode D, Mode E), or if the cloud server 20 stores the registration information for each individual product each time the mobile terminal 60 obtains the product code for that product (Modes C, Mode F), after the mobile terminal 60 has finished registering the products, the cloud server 20 stores the registration information for all products of the mobile terminal 60 in the transaction information of the mobile terminal 60. Therefore, the settlement device 50 can receive the registration information for all products from the cloud server 20 by reading the settlement code 681 displayed after the settlement start button 651 is operated.

[0170] The above describes various modes of sending and receiving product codes, product information, and registration information, as well as storing registration information and transaction information. However, various modes are also possible for sending, receiving, and storing lists of unconfirmed input items and lists of unconfirmed registrations. For example, the mobile terminal 60 may send unconfirmed input items to the cloud server 20 each time an unconfirmed input item occurs, and the cloud server 20 may update the list of unconfirmed input items. Alternatively, the mobile terminal 60 may send the list of unconfirmed input items to the cloud server 20 when registration is complete. The same applies to lists of unconfirmed registrations.

[0171] (Status update) When the mobile terminal 60 completes product registration based on the operation of the settlement start button 651 and transitions from the registration screen 650 to the settlement code display screen 680, it sends information to the cloud server 20 indicating that the screen has transitioned from the registration screen 650 to the settlement code display screen 680, and the cloud server 20 updates the status in the transaction information of the mobile terminal 60 from the registration state to the settlement declaration state.

[0172] If the cloud server 20 stores the registration information for one or more products together when the mobile terminal 60 has finished registering a product, the mobile terminal 60 sends information to the cloud server 20 indicating that the screen has transitioned from the registration screen 650 to the settlement code display screen 680, along with the product codes (or registration information for one or more products) of one or more products. Upon receiving the above information, the cloud server 20 stores the registration information for one or more products together in the transaction information of the mobile terminal 60 and updates the status in the transaction information from the registration state to the settlement declaration state.

[0173] Furthermore, if the cloud server 20 stores the registration information for one or more products together when the mobile terminal 60 has finished registering a product, the cloud server 20 may update its status upon receiving the product code (or registration information for one or more products) of one or more products. In other words, if the cloud server 20 stores the registration information for one or more products together when the mobile terminal 60 has finished registering a product, the mobile terminal 60 does not need to send information to the cloud server 20 indicating that it has transitioned from the registration screen 650 to the payment code display screen 680 when it transitions from the registration screen 650 to the payment code display screen 680.

[0174] If the cloud server 20 stores the registration information for each product each time the mobile terminal 60 obtains the product code for an individual product, the mobile terminal 60 sends information to the cloud server 20 indicating that the screen has transitioned from the registration screen 650 to the settlement code display screen 680 when it transitions from the registration screen 650 to the settlement code display screen 680. Upon receiving the above information, the cloud server 20 updates the status in the transaction information of the mobile terminal 60 from the registration state to the settlement declaration state.

[0175] Even if the cloud server 20 stores the registration information for one or more products together when the mobile terminal 60 has finished registering a product, or even if the cloud server 20 stores the registration information for each individual product each time the mobile terminal 60 obtains the product code for that product, when the settlement device 50 reads the settlement code 681 of a certain mobile terminal 60, the cloud server 20 may check the status of the mobile terminal 60 and, if it is in the settlement declaration state, send the registration information for all products to the settlement device 50. Since the registration information is sent after checking the status, problems that may occur, for example, when a captured image of the settlement code 681 is read (such as sending registration information to the settlement device 50 while it is in the process of returning from the settlement declaration state to the registration state) will not occur.

[0176] Furthermore, when the mobile terminal 60 transitions from the settlement code display screen 680 to the registration screen 650 by, for example, pressing the "return to shopping" button 684, it sends information to the cloud server 20 indicating that the screen has transitioned from the settlement code display screen 680 to the registration screen 650. Upon receiving this information, the cloud server 20 updates the status in the transaction information of the mobile terminal 60 from the settlement declaration state to the registration state.

[0177] (Recognition of placing items into the upper and lower baskets) The mobile terminal 60 recognizes the placement of items into the shopping basket based on weighing information (increase in weighing value) from the cart 70. Furthermore, it may use the image captured by the imaging unit to recognize whether the items are being placed into the shopping basket (upper basket) placed on the upper mounting section 71 or into the shopping basket (lower basket) placed on the lower mounting section 72.

[0178] Specifically, the mobile terminal 60 may recognize that an item has been placed in the upper basket if the weighing value by the cart 70 increases and the image captured by the imaging unit changes (for example, if the number of objects in the captured image increases), and it may also recognize that an item has been placed in the lower basket if the weighing value by the cart 70 increases and the image captured by the imaging unit does not change.

[0179] (If the connection with Cart 70 is lost) The connection between the mobile device 60 and the cart 70 may be lost while the initial registration screen 640 or registration screen 650 is being displayed. This loss may occur, for example, when the mobile device 60 is removed from the cart 70 and moved a certain distance away. Other reasons for loss include deactivating Bluetooth in the settings of the mobile device 60, or if either the mobile device 60 or the cart 70 malfunctions or loses power. Even if the connection is lost, the mobile device 60 will attempt to reconnect in the background, and will reconnect when it is brought closer to the cart 70.

[0180] (Information regarding Cart 70) The mobile terminal 60 may transmit various information about the connected cart 70 to the cloud server 20. For example, the mobile terminal 60 may receive information such as the cart number (which cart it is) and battery status (remaining charge information, etc.) from the cart 70 and transmit it to the cloud server 20. The cart 70 itself may also transmit information to the cloud server 20. The battery status and other information of each cart 70 stored in the cloud server 20 can be accessed, for example, from the transaction status management device 40.

[0181] As described above, the embodiment of the sales system 1 provides a more suitable system (which improves customer convenience or reduces the workload on store staff) in which customers register products using a shopping cart and a terminal.

[0182] For example, the mobile terminal 60 displays a registration screen that allows for both individual and sequential registration (see, for example, Figures 5(A) and 5(B). In Figure 5(A), no error messages are displayed regarding sequential registration), thus increasing the freedom of operation and improving customer convenience. Furthermore, the mobile terminal 60 displays a registration screen that allows for the registration of the next product even after some of the sequentially registered products have been loaded (weighed) (see, for example, Figures 8(A) and 8(B). In Figure 8(A), no error messages are displayed regarding the registration of product D), thus enabling the next registration even before all sequentially registered products have been loaded, further increasing the freedom of operation and improving customer convenience.

[0183] Furthermore, the mobile terminal 60 manages items that have been forgotten to be inserted (items not confirmed to be inserted) and items that have been forgotten to be registered (items not confirmed to be registered) in a list (items not to be inserted are managed in the unconfirmed insertion list, and items not confirmed to be registered are managed in the unconfirmed registration list), making it easy to check when calling a store employee and reducing the workload on the employees.

[0184] (Variations, etc.) Although each embodiment has been described above, the configuration of the equipment, the data configuration, the processing flow, the display and output modes, etc., can be changed as appropriate, for example, as shown in the following Modifications 1 to 22. Furthermore, Modifications 1 to 22 can be combined as appropriate.

[0185] (Modification 1) In the above embodiment, an example was described in which an option is provided for whether or not to use the shopping cart 70 (Shopping Start Button 621a with Shopping Cart Use, Shopping Start Button 621b without Shopping Cart in Figure 3(B)), but it is not necessary to provide an option. In other words, in the above embodiment, the use of the shopping cart 70 is optional when shopping using the mobile terminal 60, but the use of the shopping cart 70 may be made mandatory. That is, it may be made so that products cannot be registered unless a connection to the shopping cart 70 is made.

[0186] In a configuration where the use of the shopping cart 70 is mandatory, the menu screen 620 in Figure 3(B) may display a shopping start button 622 (not shown) instead of the shopping start button 621a with shopping cart use and the shopping start button 621b without shopping cart use, and the user may proceed to the connection instruction screen 630 in Figure 3(C) after operating the shopping start button 622. Alternatively, the menu screen 620 in Figure 3(B) may maintain the display of the shopping start button 621a with shopping cart use and hide the shopping start button 621b without shopping cart use (it may also be displayed in a way that makes it impossible to operate).

[0187] Whether the use of Cart 70 is optional or mandatory can be set for each store, and may be operated flexibly according to the operational policies of each store. As described in this embodiment, using Cart 70 makes it possible to effectively monitor unregistered and unregistered entries, thus greatly contributing to the prevention and deterrence of fraud. Therefore, it is preferable to make the use of Cart 70 mandatory for stores that place a greater emphasis on preventing and deterring fraud.

[0188] (Modification 2) In the above embodiment, an example was described in which the mobile terminal 60 displays a cart image 644 indicating that it is connected when it is connected to the cart 70 (in a state where communication is possible). However, it is also possible not to display an indication that it is connected when it is connected. In other words, it is possible to avoid making the customer aware of the connection with the cart 70 as much as possible. In this regard, there is a risk of giving the customer unnecessary questions or anxieties, and there is also a policy that there is no need to actively disclose to the customer mechanisms related to preventing or deterring fraud. For the same reason, "Weight OK" and indications related to fraud, etc. ("Forgot to put in", "<Forgot to register>", etc.) in the registration information display area 642 may also be hidden. The display / hide of the indication that it is connected, the display / hide of "Weight OK", the display / hide of indications related to fraud, etc. may each be set on a store-by-store basis.

[0189] (Modification 3) In the above embodiment, an example was described in which the mobile terminal 60 displays a pop-up small screen (small screen 660 for forgotten insertion) when it is determined that an insertion has been forgotten (Figure 3(F)). However, instead of displaying a pop-up small screen, a similar message may be displayed on the registration screen 650. The same applies when it is determined that registration has been forgotten.

[0190] (Modification 4) In the above embodiment, it was explained that items on the unconfirmed input list (i.e., items with "Forgotten to Input" displayed in the registration information display area 642) are subject to staff intervention (calling a staff member) at the payment device 50. However, if the item is input before proceeding to the payment device 50 (before the payment start button 651 is operated), it may be excluded from staff intervention. In order to exclude it from staff intervention, it is deleted from the unconfirmed input list (or an exclusion flag is added), but the display indicating that it was forgotten to input ("Forgotten to Input") does not have to be deleted (but may be deleted). Note that the contents of this Modification 4 have already been partially explained in "Another Example of Input After Timeout" of the above embodiment.

[0191] (Modification 5) In the above embodiment, it was explained that unconfirmed registered items on the unconfirmed registration list (i.e., items with "<Forgotten Registration>" or weight displayed in the registration information display area 642) are subject to staff intervention (calling a staff member) at the checkout device 50. However, if the item is registered before proceeding to the checkout device 50 (before the checkout start button 651 is operated), it may be excluded from staff intervention. In order to exclude it from staff intervention, it is deleted from the unconfirmed registration list (or an exclusion flag is added), but the indication that it was forgotten to register ("<Forgotten Registration>", weight) does not have to be deleted (but may be deleted).

[0192] (Modification 6) In the above embodiment, an example was described in which the mobile terminal 60 manages items awaiting input (list of items awaiting input) and items not yet confirmed for input (list of items not yet confirmed for input). However, other devices (for example, the cloud server 20) may manage items awaiting input and items not yet confirmed for input. For example, they may be managed as follows.

[0193] When a product is scanned, the mobile terminal 60 sends the product code to the cloud server 20. When the cloud server 20 receives the product code from the mobile terminal 60, it stores the product with that product code in the waiting list as a product awaiting input. When the weighed value increases, the mobile terminal 60 sends the increased weighed value to the cloud server 20. When the cloud server 20 receives the weighed value from the mobile terminal 60, it refers to the waiting list and, if there is a product awaiting input, removes the product from the waiting list.

[0194] The cloud server 20 refers to the input waiting list (remaining time) it has stored, removes the timed-out input waiting items from the input waiting list, and stores the timed-out input waiting items as unconfirmed input items in the unconfirmed input list.

[0195] (Modification 7) In the above embodiment, an example was described in which the mobile terminal 60 manages the unverified registered products (unverified registered products list), but other devices (for example, the cloud server 20) may manage the unverified registered products. For example, they may be managed as follows.

[0196] (In relation to the above modification 6, when the cloud server 20 manages products awaiting input, etc.) If the weighed value increases, the mobile terminal 60 sends the increased weighed value to the cloud server 20. When the cloud server 20 receives the weighed value from the mobile terminal 60, it refers to the waiting list for input, and if there are no corresponding waiting items, it stores the item in the unconfirmed list as an unconfirmed registered item. If there are no corresponding waiting items, the cloud server 20 also sends information to the mobile terminal 60 to notify it about the forgotten input, and the mobile terminal 60, upon receiving this notification, notifies it about the forgotten input.

[0197] (When the mobile terminal 60 manages products awaiting shipment, etc.) If the weighed value increases, the mobile terminal 60 refers to the waiting list for input. If there are no corresponding items waiting for input, it notifies the user about the forgotten input and sends the increased weighed value to the cloud server 20. When the cloud server 20 receives the weighed value from the mobile terminal 60, it stores it in the unconfirmed list as an unregistered item.

[0198] (Modification 8) In the above embodiment, an example was described in which the mobile terminal 60 obtains a product code by scanning a barcode and registers the product, but products may be registered by other methods. For example, product buttons (preset buttons) associated with product codes may be displayed on the registration screen 650 (the same applies to the initial registration screen 640), and the product code may be obtained and the product registered by accepting operation of the product buttons.

[0199] (Modification 9) As described above, since the mobile terminal 60 is equipped with an accelerometer and a gyroscope, it may determine whether the mobile terminal 60 (the mobile terminal 60 set in the cart 70, i.e., the cart 70) is moving or stationary. Alternatively, the cart 70 itself may be equipped with an accelerometer and a gyroscope to determine whether it is moving or stationary. In other words, the sensing results of the accelerometer and gyroscope may be used to determine whether the cart 70 is moving or stationary.

[0200] The mobile terminal 60 may ignore changes in the weighed value while the cart 70 is moving, assuming that the change is due to vibrations during movement (this is called ignore control). According to ignore control, changes in the weighed value due to movement will not be misinterpreted as product loading, thus improving the accuracy of product loading decisions.

[0201] In ignore control, product loading during movement (from start to finish) is not monitored, so it could be argued that ignore control could actually become a breeding ground for fraud. To address this, the mobile terminal 60 may acquire the weighed value from the cart 70 after the end of movement (for example, the weighed value after a predetermined time (3 seconds) has elapsed since coming to a stop) and monitor whether the weighed value after the end of movement has changed from the weighed value before the start of movement (the previous weighed value stored in the memory unit) (i.e., whether or not products were loaded during movement (from start to finish)).

[0202] (Modification 10) As is related to Modification 9 above, the weighing unit of the cart 70 is used in an environment where vibrations are likely to occur due to the operation and movement of the cart 70. Therefore, if the detection of an increase in the weighed value is made strictly, there is a risk that simple vibration of the weighing unit may be mistaken for product loading and judged as an unregistered loading. To resolve this problem, a filter may be applied that judges a small increase in the weighed value as being due to vibration, and an increase in the weighed value of more than a predetermined threshold (e.g., 10g) may be recognized as product loading, while an increase in the weighed value of less than the predetermined threshold may not be recognized as product loading. The filter (predetermined threshold) can be set for each store. Since the condition of the wheels differs for each cart 70, it may also be possible to set it for each cart 70. Also, since the usage situation differs for each customer (whether they operate it carefully or not, etc.), it may also be possible to set it for each customer. The filter processing may be performed on the cart 70 side or on the mobile terminal 60 side.

[0203] (Modification 11) As with Modification 9 above, the measured value may also change when the contents of the shopping basket are being rearranged (e.g., changing the position of items) or checked (e.g., checking whether an item has been purchased). To prevent the system from mistakenly determining that an item has been added simply by rearranging the contents of the shopping basket, declaration buttons related to rearranging the shopping basket (a shopping basket rearrangement start button and a shopping basket rearrangement end button) may be placed on the screen of the mobile terminal 60 (for example, the registration screen), and the customer may be instructed to rearrange the basket during the declaration period (between the operation of the shopping basket rearrangement start button and the operation of the shopping basket rearrangement end button). The mobile terminal 60 will perform ignore control during the declaration period. In addition, the mobile terminal 60 may acquire the measured value after the rearrangement is completed (after the shopping basket rearrangement end button is operated), as in the case of movement, and monitor whether the measured value after the rearrangement is completed has changed from the measured value before the rearrangement was started (the previous measured value stored in the memory unit) (i.e., whether an item was added during the declaration).

[0204] (Modification 12) In the above embodiment, examples were given of obtaining device identification information (e.g., Bluetooth address) for each cart 70 from a beacon and obtaining device identification information for each cart 70 from a two-dimensional code 78 attached to each cart 70. However, device identification information for each cart 70 may be obtained by other methods. For example, an NFC tag (not shown) may be attached to each cart, and device identification information for each cart 70 may be obtained from the NFC tag. The NFC tag includes a storage unit that stores device identification information (connection information) for the cart 70 (the cart 70 to which the NFC tag is attached), and a communication unit that transmits the device identification information stored in the storage unit to an external party (specifically, a mobile terminal 60).

[0205] When obtaining connection identification information from a beacon, it may be possible to obtain multiple connection identification pieces (connection identification pieces from multiple carts 70 in the vicinity). If multiple connection identification pieces are obtained, information about each cart 70 from which connection identification information was obtained will be displayed on the screen, and the customer will be allowed to select one cart 70 to use. The information about the cart 70 may be one or more of the following (A) to (C): (A) Unit number information for each cart 70. Unit number information will be attached to each cart 70. The customer can visually confirm which cart 70 is displayed on the screen (confirmed by the unit number information) and easily select the cart 70 to use on the screen. The unit number information may be numbers such as "Unit 1" or "Unit 2", letters such as "Unit A" or "Unit B", or plant names or animal names. (B) Characteristic information of each cart 70 (color, shape, etc.). Similar to the unit number information, customers can visually confirm (by using characteristic information) which cart 70 each cart 70 displayed on the screen is which cart 70, and easily select the cart 70 they want to use on the screen. (C) Distance information from the customer. Information such as "closest" and "second closest" may be displayed for each cart 70 on the screen. Alternatively, they may be displayed in order of proximity.

[0206] (Modification 13) In the above embodiment, the state in which communication is established between the mobile terminal 60 using Bluetooth and the cart 70 is expressed as pairing, but this is not limited to encrypted communication, and communication may be unencrypted. Furthermore, 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, as used in this application, pairing refers to the state in which Bluetooth communication is established, and the detailed form of this is not specified.

[0207] (Modification 14) In the above embodiment, the cart 70 was described as connecting to the mobile terminal 60 via BT, but instead of or in addition to connecting to the mobile terminal 60 via BT, it may connect to the LAN 19 by, for example, wireless LAN and communicate with the cloud server 20.

[0208] (Modification 15) In the above embodiment, the mobile terminal 60 communicates with the cloud server 20 in addition to the BT connection with the cart 70. However, it may also connect to the LAN 19 by wireless LAN and communicate with the cloud server 20, or it may communicate with the cloud server 20 without connecting to the LAN 19 (for example, by 5G).

[0209] (Modification 16) In the above embodiment, the mobile terminal 60 was described as being owned by the customer, but it may also be a terminal provided by the store (a rental terminal). The mobile terminal 60, which is a rental terminal, is provided as a dedicated terminal in a state where only application A can be executed. If the mobile terminal 60 is a rental terminal, the menu screen 620 (Figure 3(B)) is displayed from the beginning.

[0210] (Modification 17) Related to Modification 16 above, if the mobile terminal 60 is a rental terminal, the mobile terminal 60 and the cart 70 may be separate, or the mobile terminal 60 (or each component of the mobile terminal 60) and the cart 70 may be integrally formed. If the mobile terminal 60, which is a rental terminal, and the cart 70 are separate, the customer borrows the rental terminal after entering the store and sets it in the cart 70.

[0211] The phrase "integrally formed" means that the mobile terminal 60 (or its components) and the cart 70 include not only a configuration in which the cart 70 comprises the entire mobile terminal 60, but also a configuration in which the cart 70 separately comprises components (display unit, imaging unit, etc.) corresponding to each component (display unit, imaging device, etc.) of the mobile terminal 60. In other words, one part of the cart 70 may represent the entire mobile terminal 60, or two or more parts of the cart 70 may each represent a component corresponding to one or more components of the mobile terminal 60. A cart 70 comprising the mobile terminal 60 (or its components) may be called an integrated cart (or dedicated cart).

[0212] In other words, the type of cart 70 in sales system 1 and the manner in which cart 70 is used may be either (A) or (B) below. (A) A cart 70 into which a separate mobile terminal 60 (the customer's mobile terminal 60, or a mobile terminal 60 provided by the store) is set. Each time the customer uses the cart 70, they connect the mobile terminal 60 to the cart via Bluetooth (BT connection). (B) A cart 70 of the type integrally formed with the mobile terminal 60 (or each component of the mobile terminal 60) (integrated cart). Because it is integrally formed, there is no connection equivalent to connecting separate parts, and no special operation is required for connection. For example, when the power is turned on, one component of the integrated cart (e.g., weighing unit) and another component (e.g., display operation unit) should be able to communicate automatically. One component of the integrated cart and the other components may communicate by wire or by wireless.

[0213] (Modification 18) In the above embodiment, an example was described in which the cart 70 comprises an upper loading section 71 and a lower loading section 72 arranged vertically. However, the cart 70 may also comprise a front loading section and a rear loading section arranged front to back. Just as articles placed on the upper loading section 71 and articles placed on the lower loading section 72 are weighed by a single common weighing unit, articles placed on the front loading section and articles placed on the rear loading section are weighed by a single common weighing unit.

[0214] (Modification 19) In the above embodiment, an example was described in which the cart 70 has two mounting sections (upper mounting section 71, lower mounting section 72), but the cart 70 may have three mounting sections. Any article placed on any of the three mounting sections is weighed by a single common weighing unit. The arrangement of the three mounting sections is not particularly limited. For example, they may be arranged in the vertical direction as upper, middle, and lower mounting sections, or in the front-to-back direction as front mounting section (rear mounting section), middle mounting section, and rear mounting section (front mounting section). Alternatively, they may be arranged in two tiers, with one on the upper tier and two on the lower tier (front and rear), or two on the upper tier (front and rear) and one on the lower tier. The same applies when the cart 70 has four or more mounting sections and a single common weighing unit. In other words, there should be one fewer imaging unit than the number of mounting sections.

[0215] (Modification 20) In the above embodiment, an example was described in which the cart 70 has two mounting sections, but it may also have one mounting section. In other words, only one shopping basket may be placed on the cart 70.

[0216] (Modification 21) In the above embodiment, an example was described in which a mobile terminal 60 communicating with the cart 70 manages for forgotten items to be inserted or registered. However, other devices may also manage for forgotten items to be inserted or registered. For example, a stationary device in which customers register products and pay for them (a so-called fully self-service registration and payment device; referred to as the registration and payment device 51) may manage for forgotten items to be inserted or registered.

[0217] For example, in a configuration comprising a registration and settlement device 51 and a weighing device capable of communicating with the registration and settlement device 51, the registration and settlement device 51 may operate as shown in the flowchart of Figure 4. Alternatively, the registration and settlement device 51, which includes a weighing unit, may operate as shown in the flowchart of Figure 4.

[0218] (Modification 22) Some or all of the functions (input / output, storage, processing (including judgment)) in each device (for example, the transaction status management device 40, the settlement device 50, the registration settlement device 51, the mobile terminal 60, the cart 70, etc.) may be implemented in a device other than the device described as the entity that executes the function. For example, each device may function as a so-called thin client specializing in input / output interfaces, etc. As an example, a cloud server (which may be the same as cloud server 20 or a different cloud server) may execute a program to control the operation of each device, and each device may display a screen, etc., using a browsing function.

[0219] For example, the cloud server 20 may control the display of the mobile terminal 60 screen (Figures 3, 5 to 13), or, as is related to the above modifications 6 and 7, the cloud server 20 may control the operation of the mobile terminal 60. In other words, the program (app A) that controls the operation of service A of the mobile terminal 60 may run on the CPU of the mobile terminal 60 or on the CPU of the cloud server 20. To put it another way, app A may be a web application used with a browser. The screen displayed on the display unit of the mobile terminal 60 (for example, Figures 3(A) to 3(H), 5(A), 6(A), ..., 13(A)) may be a web screen provided by the cloud server 20.

[0220] <Summary of Embodiments> [Technical field] This invention relates to a sales system. [Background technology] A system is known in which customers register products using a terminal attached to a shopping cart (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2018-147252 [Overview of the prefecture] [Problems the invention aims to solve] However, there is room for improvement in the system for customers to register products. This invention has been made in view of these circumstances and aims to provide a more suitable system for customers to register products. [Means for solving the problem]

[0221] (1) One embodiment for solving the above-mentioned problems is a sales system comprising a registration unit for registering products, a weighing unit for weighing products, and a display unit for displaying a registration screen that accepts product registration by the registration unit, wherein the display unit displays a registration screen (see, for example, Figures 7 and 8) that accepts further product registration by the registration unit based on a partial weighing status where multiple products have been registered consecutively by the registration unit and some of the multiple products have been weighed by the weighing unit. According to the configuration of (1), a more suitable system can be provided in which customers register products using a shopping cart (cart 70) and a terminal (mobile terminal 60). For example, customer convenience can be improved.

[0222] (2) The sales system according to (1), characterized in that the display unit displays that an unregistered product has been added if the increase in the measured value by the weighing unit is not the weight corresponding to the weight of an unmeasured product in the partial weighing situation, and is not the weight corresponding to an item further registered by the registration unit from the partial weighing situation (see, for example, step S10 in Figure 4), and does not display that an unregistered product has been added if the increase in the measured value by the weighing unit is the weight corresponding to an unmeasured product in the partial weighing situation, or the weight corresponding to an item further registered by the registration unit from the partial weighing situation. According to the configuration of (2), for example, a more suitable system can be provided in which customers register products using a shopping cart and a terminal.

[0223] (3) The sales system according to (1) or (2), characterized in that if the increase in the measured value by the weighing unit corresponds to the weight of an unweighed item among a plurality of items continuously registered by the registration unit, the display unit does not display that an unregistered item has been added, regardless of the registration order of the plurality of items continuously registered (that is, as shown in Figure 6 for example, even if an item is added, if the added item is one of the items on the waiting list, the display unit does not display that an unregistered item has been added). According to the configuration of (3), for example, a more suitable system can be provided in which customers register products using a shopping cart and a terminal.

[0224] Furthermore, the processing of each of the above-described devices (for example, the cloud server 20, the transaction status management device 40, the settlement device 50, the registration settlement device 51, the mobile terminal 60, the cart 70, etc.) may be performed by recording the program for realizing the functions of each device on a computer-readable recording medium, loading the program recorded on this recording medium into a computer system, and executing it. Here, "loading the program recorded on the recording medium into a computer system and executing it" includes installing the program into the computer system. Here, "computer system" includes hardware such as the OS and peripheral devices. Also, "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Thus, the recording medium storing the program may also be a non-transient recording medium such as a CD-ROM. Also, the recording medium includes internal or external recording media that can be accessed from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in an executable format on the terminal device. In other words, as long as it can be downloaded from the distribution server and installed in an executable format on the terminal device, the format in which it is stored on the distribution server is irrelevant. Furthermore, the program may be divided into multiple parts, downloaded at different times and then combined on the terminal device, and each of the divided programs may be distributed by a different distribution server. In addition, "computer-readable recording medium" includes volatile memory (RAM) within computer systems that act as servers or clients when a program is transmitted over a network, which retains the program for a certain period of time. Moreover, the above program may be intended to implement only a part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [Explanation of symbols]

[0225] 1…Sales system 10…Headquarters server 20…Cloud server 30…Store controller 40…Transaction status management device 50…Settlement device 51…Registration and settlement device 60…Mobile terminal 70…Cart

Claims

1. The registration section for registering products, A weighing unit for measuring the weight of the product, A display unit that displays a registration screen for accepting product registrations by the aforementioned registration unit. Equipped with, The aforementioned display unit is The registration unit registers multiple products in succession, and a registration screen is displayed that accepts further product registration from the registration unit based on the partial weighing status, where some of the products have been weighed by the weighing unit. A sales system characterized by the following features.

2. The aforementioned display unit is The increase in the measured value by the aforementioned measuring unit, If the weight measured in the aforementioned partial weighing situation does not correspond to the weight of the unweighed product, and also does not correspond to the weight of the product further registered by the registration unit based on the aforementioned partial weighing situation, then a message indicating that an unregistered product has been entered will be displayed. If the weight corresponds to the weight of an unweighed item in the aforementioned partial weighing situation, or to the weight of an item further registered by the registration unit based on the aforementioned partial weighing situation, the system will not display that an unregistered item has been added. The sales system according to feature 1.

3. The aforementioned display unit is If the increase in the measured value by the weighing unit corresponds to the weight of an unweighed item among multiple items that have been continuously registered by the registration unit, the system will not display a message indicating that an unregistered item has been added, regardless of the registration order of the multiple items that have been continuously registered. The sales system according to claim 1 or 2.

Images