Sales system

Abstract

We provide a sales system that allows customers to smoothly proceed with their purchases, regardless of the settings or operating status of their customer terminals. [Solution] A sales system 1 comprising a cart 70 equipped with a weighing function and an application 60 installed on a customer's mobile terminal 50, the sales system 1 comprising: a connection unit 603 that establishes communication with the cart 70 if the application 60 is already installed on the mobile terminal 50 when connection information including at least device identification information for connecting to the cart 70 is obtained; and a display / operation unit 503 that displays a screen for installing the application if the application 60 is not already installed on the mobile terminal 50 when connection information including at least device identification information for connecting to the cart 70 is obtained.

Description

Technical Field

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

Background Art

[0002] There is known an information communication terminal that reads the MAC address of a device from an NFC tag attached to the device and transmits data with the IP address corresponding to the read MAC address as the destination (see, for example, Patent Document 1). Also, there is known a system in which a customer registers products by himself / herself in a product display area using a shopping cart.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In this regard, in operating a system that uses a customer's terminal (customer terminal) for product registration, it is preferable to provide a dedicated application program for the customer terminal. However, when a customer starts shopping at a store using the customer terminal, the installation status and execution status of the application program vary depending on the customer. Therefore, there is a demand for a system that allows a customer to smoothly proceed with shopping regardless of the settings and operation status of the customer terminal.

[0005] Therefore, one object of the present invention is to provide a sales system that allows a customer to smoothly proceed with shopping regardless of the settings and operation status of the customer terminal.

Means for Solving the Problems

[0006] To achieve the above objective, the sales system according to the present invention is a sales system comprising a shopping cart equipped with a weighing function and a shopping application program installed on a customer's mobile terminal, comprising: connection means for establishing communication with the shopping cart when connection information including at least device identification information for connecting to the shopping cart is obtained, and the application program is already installed on the mobile terminal; and display means for displaying a screen for installing the application program when connection information including at least device identification information for connecting to the shopping cart is obtained, and the application program is not already installed on the mobile terminal. [Brief explanation of the drawing]

[0007] [Figure 1] This is a conceptual diagram showing the network configuration of a sales system according to an embodiment of the present invention. [Figure 2] This is a functional block diagram showing the functions of the mobile terminal used in the above sales system. [Figure 3] This is a perspective view showing the shopping cart used in the sales system described above. [Figure 4] This is an example of a screen displayed on a mobile device used in the above sales system. [Figure 5] This is an example of a screen displayed on a mobile device used in the above sales system. [Figure 6] This is a flowchart illustrating an example of operation on the above-mentioned mobile device. [Figure 7] This is a flowchart illustrating an example of operation on the above-mentioned mobile device. [Figure 8] This is a flowchart illustrating an example of operation on the above-mentioned mobile device. [Figure 9] This is a flowchart illustrating an example of operation on the above-mentioned mobile device. [Figure 10] This is a sequence diagram illustrating an example of operation in the sales system described above. [Modes for carrying out the invention]

[0008] ● Overview and configuration of the sales system The sales system according to an embodiment of the present invention will be described below with reference to the figures. Figure 1 is a conceptual diagram of the network illustrating the sales system 1 of this embodiment. Sales System 1 is a system that can be introduced into various types of businesses such as supermarkets, convenience stores, drugstores, home centers, and consumer electronics retailers. This sales system 1 mainly includes a shopping cart equipped with a weighing function (hereinafter referred to as "cart 70"), a customer's mobile terminal 50, and a shopping application program (hereinafter referred to as "app 60") installed on the mobile terminal 50, as well as a headquarters server 10, a cloud server 20, a store controller 30, a transaction status management device 40, and a settlement device 80.

[0009] Of the elements that make up sales system 1, the store controller 30, transaction status management device 40, and settlement device 80 are installed in the store, such as in the product display area, checkout area, and back room. These are configured to communicate via a network NW1, such as a LAN or dedicated line (which can be wired or wireless). Furthermore, the headquarters server 10 and the cloud server 20 are installed outside the stores, such as at the head office or data center. The devices installed inside the store (store controller 30, transaction status management device 40, settlement device 80) and the devices installed outside the store (headquarters server 10, cloud server 20) are configured to communicate with each other via a network NW2 such as the internet (either directly or via the store controller 30).

[0010] Furthermore, within the store, there is a cart 70 provided by the store and a mobile terminal 50 owned by the customer. The mobile terminal 50 can be attached (set) to the cart 70. The mobile terminal 50 and the cart 70 can communicate with each other via a short-range wireless communication network NW3 such as Bluetooth (registered trademark; the same applies hereinafter). As described later, the mobile terminal 50 and the cart 70 may also use wireless communication such as NFC (Near Field Communication) or wired communication when pairing. In Figure 1, the mobile terminal 50 shown inside the cart 70 represents the mobile terminal 50 attached to the cart 70. The mobile terminal 50 and the cloud server 20 can communicate (either directly or via the store controller 30).

[0011] The store provides a self-service system (hereinafter sometimes referred to as "this service") in which customers register products themselves using a mobile terminal 50 and pay using a payment device 80, through the sales system 1.

[0012] Note that the number of each device (terminal) in Figure 1 is illustrative. For example, the number of payment devices 80 installed in the store only needs to be one or more. Also, the number of mobile terminals 50 present in the store is the number of customers who came to the store with a mobile terminal 50, and is not necessarily two as shown in the figure. Similarly, the number of carts 70 present in the store is the number prepared by the store based on the number of mobile terminals 50 that are expected to be present in the store at the same time, and could be, for example, 10 or more.

[0013] <Headquarters Server 10> The headquarters server 10 is the server that manages the entire sales system 1. The headquarters server 10 stores various information, such as the product master. The product master is a file that stores product names, prices, etc., associated with product codes. The headquarters server 10 also supplies various information, such as the product master, to the cloud server 20 and the store controller 30. The head office server 10 includes at least a CPU, a storage unit, and a communication unit. Note that the head office server 10 may be composed of multiple servers.

[0014] <Cloud server 20> The cloud server 20 is mainly a server that supports this service. The cloud server 20 stores various information such as product masters and transaction information. In addition, the cloud server 20 supplies various information to, for example, the mobile terminal 50 and the payment device 80. The cloud server 20 includes at least a CPU, a storage unit, and a communication unit. Note that the cloud server 20 may be composed of multiple servers.

[0015] <Store controller 30> The store controller 30 is mainly a server responsible for information communication between devices installed inside the store (transaction status management device 40, payment device 80) and devices installed outside the store (head office server 10, cloud server 20). The store controller 30 includes at least a CPU, a storage unit, and a communication unit.

[0016] <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 mobile terminal 50 and the settlement device 80. For example, the transaction status management device 40 monitors (displays) the processing status and operation status of the settlement device 80. The transaction status management device 40 may also monitor the processing status and operation status of the mobile terminal 50 (for example, by accessing the cloud server 20 and displaying or modifying transaction information etc. stored in the cloud server 20). The transaction status management device 40 may also monitor the status of the cart 70 (for example, by accessing the cloud server 20 and displaying the status of the cart 70's battery etc. (other examples include the cart charging unit 73 and the mobile terminal charging unit 75), various error information, and the cart 70's program version information, which are stored in the cloud server 20 and transmitted via the mobile terminal 50 or transmitted directly without going through the mobile terminal 50). The transaction status management device 40 may also access the headquarters server 10 etc. and maintain the product master stored in the headquarters server 10 etc. (product settings etc.). 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 is configured to communicate with a printing device and may output various information from the printing device.

[0017] <Mobile device 50> The mobile terminal 50 is used by customers to register products themselves within the store. Specifically, the mobile terminal 50 registers products based on the customer's operation (action) while in a state where it can communicate with a shopping cart 70. The mobile terminal 50 may be attached to a shopping cart 70, or it may be detached from the shopping cart 70, for example, held in the customer's hand and operated, as long as it is in a state where it can communicate with the shopping cart 70. In either state, it is possible to register products based on the customer's operation.

[0018] The mobile terminal 50 is implemented, for example, by a smartphone, and as shown in Figure 2, it includes functions that a smartphone generally has, such as a CPU 501, an information storage unit 502, a display / operation unit 503, an audio output unit 504, an audio input unit 505, an imaging unit 506, a detection unit 507, and a communication unit 508.

[0019] The CPU 501 is a central processing unit that controls the entire mobile terminal 50 and executes programs and instructions according to programs and instructions obtained from external sources, in addition to programs stored in the information storage unit 502.

[0020] The information storage unit 502 stores various types of information (for example, information referenced or generated by the CPU, information acquired from external sources, etc.). The information storage unit 502 is implemented by memory or storage such as RAM, ROM, hard disk, or SSD (Solid State Drive).

[0021] The mobile terminal 50 obtains (receives) an application 60 (details of which will be described later) from an external source (a designated server, or a cloud server 20) in order to use this service, and installs it in the information storage unit 502. The mobile terminal 50 executes processes related to this service using the application 60. As mentioned above, this service is a self-service system that uses the mobile terminal 50 for product registration and the payment device 80 for payment, but the application 60 is the application program that handles the mobile terminal 50 (product registration) part of this service.

[0022] The display and operation unit 503 is implemented, for example, by a touch panel display, and displays various information and accepts information input operations. The display and operation unit 503 does not necessarily have to consist of a display unit for displaying information and an operation unit for accepting input operations; it may consist of a liquid crystal display or the like for the display unit and hard buttons or the like for the operation unit. The audio output unit 504 is implemented by a speaker or the like and outputs sound. The audio input unit 505 is implemented using a microphone or the like, and inputs audio. The imaging unit 506 is implemented by a CMOS camera or the like, and acquires (generates) captured images (still images, moving images). The detection unit 507 is implemented using GPS sensors, acceleration sensors, gyro sensors, etc., and detects or measures various events. The display / operation unit 503, the voice input unit 505, or the imaging unit 506 may also be considered as part of the detection unit 507. The communications unit 508 performs the transmission and reception of information based on various communication protocols with wired terminals and devices, as well as with public communication networks such as 5G, local area networking networks such as Wi-Fi, and wireless communication such as NFC and Bluetooth.

[0023] <App 60> App 60 is a dedicated application program provided to the mobile device 50 for customers to use this service. This application 60 includes a functional unit for realizing this service, consisting of an information storage unit 601, a connection information acquisition unit 602, a connection unit 603, a registration unit 604, a display / operation processing unit 605, a code generation processing unit 606, and a communication processing unit 607.

[0024] The information storage unit 601 is an information storage area provided within the application 60. This information storage unit 601 stores, for example, registration data related to products registered by customers, and weighing data such as the weighed value and tare weight of products received from the cart 70. In addition, the product master may be obtained from the cloud server 20 and stored in the information storage unit 601.

[0025] The connection information acquisition unit 602 acquires connection information for connecting the cart 70 and the mobile terminal 50 so that they can communicate via the network NW3. The connection information includes at least device identification information that can identify a single cart 70 to which the mobile terminal 50 will connect. For example, when the cart 70 and the mobile terminal 50 connect wirelessly via Bluetooth, the connection information includes a Bluetooth address (pairing information, serial number, MAC address, etc.) as device identification information that can identify a single cart 70, thereby connecting (pairing) the mobile terminal 50 and the cart 70. Furthermore, the connection information acquisition unit 602 constitutes the connection information acquisition means according to the present invention in that it acquires device identification information of the cart 70 included in the connection information by acquiring the connection information.

[0026] Connection information can be obtained, for example, by following the first to third examples below. In the first example, the connection information acquisition unit 602 controls the imaging unit 506 to acquire coded connection information for each cart 70 from the two-dimensional code 76 (see Figure 3) attached to the cart 70. In the second example, the connection information acquisition unit 602 controls the communication unit 508 to acquire connection information via wireless communication from an NFC tag 77 (see Figure 3) or beacon transmitter attached to or mounted on the cart 70. In the third example, the connection information acquisition unit 602 controls the communication unit 508 to acquire connection information from the cart 70 connected to the mobile terminal 50 by wire, or from a predetermined device attached to the cart 70.

[0027] Furthermore, regarding the acquisition of connection information according to the first example described above, the 2D code 76 may be provided by means other than attaching it to the cart 70. For example, a display may be installed in a cart storage area where the carts 70 are kept. The carts 70 are then stored in the cart storage area so that they can be taken out in order from the front, and the 2D code 76 encoding the connection information of the cart 70 in front is displayed on the display. The customer takes out the cart 70 in front of them from the cart storage area and reads the 2D code 76 displayed on the display to obtain the connection information for that cart 70. Furthermore, if connection information is output via a beacon or a display installed in the cart storage area as described above, the system may be configured to output connection information, such as by transmitting a beacon or displaying a 2D code 76, when the cart 70 is removed from the cart storage area. The fact that the cart 70 has been removed from the cart storage area can be determined, for example, based on the charging status of the cart 70. That is, the charging status can be determined according to the connection status between the cart charging equipment installed in the cart storage area and the cart charging unit 73 (see Figure 3) of the cart 70.

[0028] In addition to device identification information, the connection information may include additional information necessary to enable the customer to receive the service when the application 60 is not running on the mobile terminal 50 or when the application 60 is not installed on the mobile terminal 50, as well as command information that commands the mobile terminal 50 to perform actions. The connection information in the first example may include, as command information, a startup command that commands the startup of application 60 when the connection information is obtained by a function of the mobile terminal 50 that is not provided by application 60 (i.e., when the connection information is obtained without starting application 60). The connection information in the second example may include, as additional information and command information, the address (URL) of the download site for the application 60, and information that commands the mobile terminal 50 to connect to the download site when the connection information is obtained by a function of the mobile terminal 50 that is not provided by the application 60 (when the connection information is obtained without launching the application 60). The connection information in the third example may include, as additional information, the URL of a predetermined landing page. This predetermined landing page contains predetermined information in HTML format for determining the next action, and a browser that navigates to the page according to the landing page URL will execute an action according to the predetermined information by loading the HTML. The predetermined information consists of, for example, a URL for transitioning to the download site of app 60, information to load that URL, and information to command the page transition to the download site, or information to search for whether app 60 is installed on the device and, if installed, command to launch app 60.

[0029] Furthermore, the connection information may be a combination of the additional information and command information from the first and second examples. Therefore, the connection information may include the address (URL) of the download site as additional information, and as command information, if the connection information is obtained by a function provided by the mobile terminal 50 (if the connection information is obtained without launching the application 60), it may include information that commands the launch of application 60 on the condition that application 60 is installed, while if application 60 is not installed, it may include information that commands a connection to the download site.

[0030] In this type of connection information, device identification information, additional information, and command information are configured to be identifiable. For example, device identification information, additional information, and command information are combined using a predetermined identifier such as a symbol. This identifier is information that the operating system (OS) or application 60 of the mobile terminal 50 can recognize in advance as information to be combined. As a result, when the OS or application 60 acquires the connection information, it can identify the device identification information, additional information, and command information and perform appropriate processing.

[0031] Notwithstanding the above example, if an application 60 installed on the mobile terminal 50 is launched and connection information is obtained through operations on the application 60, the application 60 can pair with the cart 70 according to the device identification information if the connection information contains only device identification information. Furthermore, even if additional information is included, such as in the connection information related to the first or second example described above, if the connection information is obtained through an operation on the app 60, the app 60 may ignore the additional information and pair with the cart 70 according to the device identification information. Furthermore, multiple pieces of connection information, including device identification information for a predetermined cart 70, may be prepared according to the status of the mobile terminal 50. For example, a two-dimensional code encoding the device identification information may be prepared for customers who have installed the app 60 on their mobile terminal 50, while connection information consisting of the device identification information and additional information including the URL of the download site may be prepared for customers who have not installed the app 60.

[0032] When the connection unit 603 obtains connection information from the connection information acquisition unit 602, it communicates with the cart 70 identified by the device identification information contained in the connection information and establishes a connection. For example, if the Bluetooth address of the cart 70 is obtained as the device identification information, pairing (connection) is performed, thereby establishing communication (Bluetooth communication) between the mobile terminal 50 and the cart 70.

[0033] The registration unit 604 performs the product registration process. This registration unit 604 controls, for example, the imaging unit 506 to photograph the symbol code (barcode or 2D code) attached to the product, and recognizes and reads the symbol code in the captured image. By doing so, it obtains the product code (for example, a JAN code) that was encoded in the symbol code, and registers the product identified by that product code as a product to be purchased. Furthermore, regardless of whether or not a product has a symbol code, the system may accept the customer's specification of the product to be purchased based on the product master stored in the information storage unit 601, and register the product accordingly. For example, buttons corresponding to individual products (product preset buttons) may be displayed on the registration screen (including the initial registration screen), and products may be registered by operating the product preset buttons. Furthermore, the product registration data is transmitted to the cloud server 20 along with transaction identification information that can uniquely identify the product, for example, as transaction information, and is referenced during settlement processing by the settlement device 80.

[0034] The display and operation processing unit 605 controls the display and operation unit 503 to display information and accept information input operations in accordance with the execution of the application 60's functions.

[0035] The code generation processing unit 606 generates a symbol code (refer to Figure 4 and later referred to as "settlement code G151") for settlement purposes, such as a barcode or a two-dimensional code, for the products registered by the registration unit 604. In one example, transaction identification information is encoded in the symbol code, and the settlement device 80 can obtain the transaction identification information from the symbol code and the transaction information associated with the transaction identification information from the cloud server 20.

[0036] The communication processing unit 607 controls the communication unit 508 to send and receive information between the cart 70 and the cloud server 20 in accordance with the execution of the application 60's functions. This communication processing unit 607 can, for example, receive weighing information from the cart 70 or send product registration data to the cloud server 20.

[0037] <Cart 70> In addition to its function of carrying and transporting goods (goods registered by the mobile terminal 50), the cart 70 also has a function for weighing goods and a function for communicating with the mobile terminal 50. Figure 3 shows an example of the external configuration of such a cart 70, which includes a loading section 71, a circuit board housing section 72, a cart charging section 73, a holder section 74, and a mobile terminal charging section 75, and is also equipped with a two-dimensional code 76 and an NFC tag 77. In addition, the cart 70 may also be equipped with a battery as a power source to supply power to the cart 70 (specifically, the circuit board in the circuit board housing section 72).

[0038] The mounting section 71 is a mounting platform on which shopping baskets and the like can be placed. A weighing unit 703 (see Figure 2) is connected to this mounting unit 71 for weighing the weight of the placed item.

[0039] The substrate housing section 72 houses substrates that realize various functional parts.

[0040] The cart charging unit 73 has a power supply cable (not shown) and detachable contact terminals, the ends of which are connected to the battery charging terminals.

[0041] The holder portion 74 is a component for setting the mobile terminal 50. The holder portion 74 has an opening that corresponds to the position of the imaging unit 506 of the set mobile terminal 50.

[0042] The mobile terminal charging unit 75 stores power to be supplied to the mobile terminal 50 set in the holder unit 74.

[0043] The two-dimensional code 76 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 76 is attached). In the illustrated example, the two-dimensional code 76 is attached to the mobile terminal charging unit 75 so that it is easily visible to the customer who places the mobile terminal 50 on the mounting unit 71, but it may be attached to another location. This two-dimensional code 76 constitutes one of the connection information providing means that provides connection information to the mobile terminal 50. Furthermore, in an operation where the mobile terminal 50 connects to the cart 70 using the NFC tag 77 described later, and does not connect to the cart 70 using the 2D code 76, it is not necessary to attach the 2D code 76 to the cart 70.

[0044] The NFC tag 77 comprises a storage unit that stores connection information for the cart 70 to which the NFC tag 77 is attached, and a communication unit that transmits the connection information stored in the storage unit to an external device, specifically the mobile terminal 50. In the illustrated example, the NFC tag 77 is attached to the holder unit 74, ensuring reliable NFC communication when the mobile terminal 50 is placed on the holder unit 74. The NFC tag 77 constitutes one of the connection information providing means for providing connection information to the mobile terminal 50. Furthermore, in an operation where the mobile terminal 50 connects to the cart 70 using a 2D code 76 and does not connect to the cart 70 using an NFC tag 77, it is not necessary to attach an NFC tag 77 to the cart 70.

[0045] In the example shown in Figure 3, the shopping basket is not placed on the mounting section 71, and the mobile terminal 50 is not attached to the holder section 74. However, a customer who comes to the store with a mobile terminal 50 will place the shopping basket on the mounting section 71 and attach the mobile terminal 50 to the holder section 74. The customer may also charge the mobile terminal 50 by connecting it to the cable (not shown) of the mobile terminal charging section 75, if necessary.

[0046] Furthermore, when the mobile terminal 50 is attached to the holder unit 74 and imaging is performed by the imaging unit 506, it acquires an image taken from the position of the holder unit 74, looking down towards the shopping cart. The mobile terminal 50 can detect (monitor) whether an item has been placed in the cart 70 without being scanned or whether a scanned item has not been placed in the cart 70 by recognizing the image of the captured image, thus determining whether there is any fraud or operational error during shopping.

[0047] Furthermore, as shown in Figure 2, the cart 70 includes at least a CPU 701, an information storage unit 702, a weighing unit 703, and a communication unit 704 as functional units that perform information processing related to the provision of this service.

[0048] The CPU 701 is a central processing unit that controls the entire cart 70 according to programs stored in the information storage unit 702, as well as programs and instructions obtained from external sources, and executes those programs and instructions.

[0049] The information storage unit 702 stores, for example, the tare weight and the pre-increase / decrease (pre-change) weighing values ​​for calculating the increase / decrease in weight (amount of change). The storage unit may also store the increase in weight (weight of items placed in the shopping basket) and the decrease in weight (weight of items removed from the shopping basket).

[0050] The weighing unit 703 is a functional unit that weighs the weight of the product on the placement unit 71. It detects when a product is placed on or removed from the placement unit 71 by weight fluctuations, weighs the product, and outputs the product weight (measured value). This weighing unit 703 constitutes the scale function of the present invention.

[0051] The tare weight is the weight of the items placed on the loading unit 71 in the initial state before shopping begins (more specifically, before an item is placed in the machine). The tare weight is the weight measured by the weighing unit 703 in the initial state before shopping begins. The tare weight may include not only the shopping basket but also the customer's personal belongings (wallet, bag, etc.). For example, if an empty shopping basket is placed on the loading unit 71 in the initial state before shopping begins (i.e., only the shopping basket is placed), the tare weight is the shopping basket, and the tare weight is the weight of the shopping basket. Also, for example, if a shopping basket containing a wallet is placed on the loading unit 71 in the initial state before shopping begins (i.e., both the shopping basket and the wallet are placed), the tare weight is the shopping basket and the wallet, and the tare weight is the weight of the shopping basket plus the weight of the wallet.

[0052] Furthermore, the cart 70 receives tare instruction information from the mobile terminal 50. When the cart 70 receives tare instruction information from the mobile terminal 50, it determines the measured value at the time of receipt as the measured value (initial weight) in the initial state before shopping begins (before the first item is placed in the cart). For example, if the measured value in an unloaded state is 0g and the weight of the shopping basket is 500g (known), then if the measured value when the tare instruction information is received is 500g, the tare weight is 500g (the tare is the shopping basket only). Alternatively, in the same case, if the measured value when the tare instruction information is received is 3000g, then the tare weight is 3000g (the tare is the shopping basket + the customer's luggage).

[0053] In other words, the cart 70 stores the weighed value in the unloaded state, and after a shopping basket or customer's luggage is placed on it from the unloaded state and tare instruction information is received, the weighed value with the shopping basket or customer's luggage on it is used as the weighed value at the start of shopping. For example, if the cart 70 is measuring 3000g with the weighing unit 703 and receives a tare instruction from the mobile terminal 50, it notifies the mobile terminal 50 that "3000g" has been changed to "0g". Alternatively, if the cart 70 is measuring 3000g with the weighing unit 703 and receives a tare instruction from the mobile terminal 50, it may notify the mobile terminal 50 that "3000g" has been changed to "3000g". In the former case, the mobile terminal 50 proceeds with processing assuming that the base weight at the start of shopping is 0g, and in the latter case, the mobile terminal 50 proceeds with processing assuming that the base weight at the start of shopping is 3000g.

[0054] Furthermore, since the weight of the shopping basket is known, it is possible to calculate the weight of the customer's luggage. For example, if the weight measured in an unloaded state is 0g, the weight of the shopping basket is 500g (known), and the weight measured when the tare instruction information is received is 3000g, then the weight of the luggage is 2500g.

[0055] The communications unit 704 sends and receives various information with the mobile terminal 50. The communication unit 704 communicates with the mobile terminal 50, which is connected via Bluetooth through pairing, for example, and transmits the weighing result from the weighing unit 703 to the mobile terminal 50.

[0056] The communication unit 704 may also transmit a beacon containing connection information as a signal to the mobile terminal 50 before pairing. When the communication unit 704 transmits the above-mentioned beacon to the mobile terminal 50, it constitutes one of the connection information providing means for providing connection information to the mobile terminal 50. Furthermore, the communication unit 704 may achieve wired communication with the mobile terminal 50 not only through wireless communication but also through cables and terminals for transmitting data. When transmitting connection information to the mobile terminal 50 via wired communication, the communication unit 704 also constitutes one of the means for providing connection information to the mobile terminal 50. Furthermore, the communication unit 704 may also have the function of sending and receiving various types of data not only to the mobile terminal 50, but also to the headquarters server 10, cloud server 20, or store controller 30 via the network NW1 and 2, in accordance with the communication protocols of the network NW1 and 2.

[0057] In this embodiment, the cart 70 is equipped with a weighing unit 703 as a weighing function. However, regardless of this, the cart 70 may be equipped with the following functions 1-5 individually or in appropriate combinations in place of the weighing function, or in addition to the weighing function. <Function 1: Sensor> Sensors such as optical sensors may be provided around the frame of the mounting section 71 or on the bottom surface of the mounting section 71. These sensors can detect when an item is placed in or removed from the cart 70. <Function 2: Camera Module> Similar to function 1, a camera module may be provided around the frame of the mounting section 71 or on the bottom surface of the mounting section 71. This camera module can detect when an item is placed in or removed from the cart 70, and can also implement a function to register the item by scanning its barcode. <Function 3: Vibration Sensor> A vibration sensor may be provided to detect vibrations in the loading section 71. Even without detecting an increase or decrease in weight on the loading section 71, as in the weighing section 703, it is possible to detect that an item has been placed in the cart 70 by vibration. As a result, if only vibration is detected without an item scan, it can be determined that an unauthorized item has been placed in the cart. <Function 4: Gyro Sensor> The cart 70 may be equipped with a gyro sensor to detect whether it is stopped or moving. This allows the usage status of each cart 70 being used in the store to be monitored. <Function 5: GPS> The carts 70 may be equipped with GPS to acquire their location information. This allows the store to track the location of each cart 70 being used.

[0058] <Payment device 80> The settlement device 80 is a device that settles the payment for registered products. In this embodiment, the settlement device 80 settles the payment for products registered by the mobile terminal 50 based on the customer's operation. The settlement device 80 includes, for example, a CPU, a memory unit, a display unit, a scanner unit, a settlement unit, a printing unit, an audio output unit, an imaging unit, a communication unit, and a signpost.

[0059] The scanner unit scans various codes (for example, the payment code G151, which will be described later in Figure 4, product codes, and employee codes attached to vouchers, point cards, employee name tags, etc.) and reads each code. The payment section is a general term encompassing either the cash payment section (change dispenser) that handles cash payments, or the non-cash payment section (card payment section, code payment section) that handles non-cash payments (e.g., credit cards, electronic money, etc.), or both. The display unit shows the product list screen, etc. The payment device 80 may further include a key operation section consisting of one or more various operating members, a human presence sensor for detecting (detecting, recognizing) the presence of a person, and so on.

[0060] The sales system 1 may include devices other than those described above. For example, a first registration and settlement device may be installed in the store that registers products based on customer operations and settles payments based on customer operations. The first registration and settlement device comprises a CPU, a memory unit, a display unit, a scanner unit, a settlement unit (either a cash settlement unit or a non-cash settlement unit or both), a printing unit, an audio output unit, an imaging unit, a communication unit, and a signpost. For example, the scanner unit scans various codes (e.g., product codes, employee codes attached to vouchers, point cards, employee name tags, etc.) and reads each code. Also, for example, the display unit displays the registration image and the payment screen. The registration and payment device may further include a key operation unit consisting of one or more various operating members, and a human presence sensor that detects the presence of a person.

[0061] Furthermore, the sales system 1 may also include a second registration and settlement device installed within the store, which has a display unit for staff, a scanner unit, etc. on one side (staff side), and a customer display unit and a settlement unit (either a cash settlement unit or a non-cash settlement unit, or both) on the other side (customer side, opposite to the staff side), registering products based on staff operations and settling payments based on customer operations. Furthermore, a third registration and settlement device may be installed in the store, which has a display unit and registration unit for store staff on one side, and a display unit, registration unit and settlement unit (either a cash settlement unit or a non-cash settlement unit or both) for customers on the other side, and has operating modes such as a normal mode (similar to the second registration and settlement device, it registers products based on the store staff's operation and settles the payment based on the customer's operation) and a full self-service mode (similar to the first registration and settlement device, it registers products based on the customer's operation and settles the payment based on the customer's operation). When installing the first registration and payment device (and the second and third registration and payment devices) within the store, it shall be connected to networks NW2 and NW3, enabling communication with devices installed inside or outside the store.

[0062] ●Screen example Figure 4 shows an example of the display on the mobile terminal 50. Specifically, Figure 4 shows an example of the display when the mobile terminal 50 connects to the cart 70 using a 2D code 76. In this example, it is assumed that the application 60 is already installed on the mobile terminal 50.

[0063] Figure 4(A) shows the initial screen of the mobile terminal 50 (standby screen; a screen in which app 60 and other apps are not running). On the initial screen of Figure 4(A), the icon G101 of app 60 is displayed in its normal state.

[0064] Figure 4(B) shows the menu screen (start screen) that appears immediately after launching the application 60. For example, when the icon G101 of the application 60 on the initial screen (Figure 4(A)) is operated, the mobile terminal 50 displays the menu screen shown in Figure 4(B). The menu screen shown in Figure 4(B) displays various buttons that can be operated, such as the "Start Shopping with Cart" button G111, which accepts the operation to start shopping using the cart 70, and the "Start Shopping without Cart" button G112, which accepts the operation to start shopping without using the cart 70. At the bottom of the menu screen, there is a related information display area G113 that displays related information.

[0065] Figure 4(C) shows the screen for reading connection information that appears after pressing the "Start Shopping with Cart" button G111. The screen for reading connection code shown in Figure 4(C) displays a message G121 instructing the user to read the connection information (2D code 76), and an explanatory image G122 explaining how to read the connection information.

[0066] After this, once the mobile terminal 50 and the cart 70 are connected, the tare function will be performed. Therefore, customers need to place their shopping basket on the placement unit 71 before the connection between the mobile terminal 50 and the cart 70 is made. To this end, at least before the connection between the mobile terminal 50 and the cart 70 is made, for example, on a separate screen provided during the transition from the screen shown in Figure 4(B) to the screen shown in Figure 4(C), or on the screen shown in Figure 4(C), a message prompting the customer to place the shopping basket, such as "Please place your shopping basket," may be displayed. Alternatively, on these screens, along with the message, a button may be provided for the customer to confirm the placement of the shopping basket, and pressing this button may transition to the next screen or process.

[0067] Figure 4(D) shows the registration screen (initial registration screen) that appears after the connection with the cart 70 (connection using device identification information obtained from the 2D code 76) is completed. The upper part of the registration screen is the image display area G131, which mainly displays the captured image. The central part of the image display area G131 is the barcode reading area (a rectangular area in the center with the message "Please hold the barcode over the scanner") suitable for reading barcodes. The lower part of the registration screen is the registration information display area G132, which mainly displays product registration information and total information. In addition, the initial registration screen shown in Figure 4(D) displays an explanatory image G133 that explains how to register products. Note that the explanatory image G133 may be disabled in subsequent initial registration screens depending on the settings.

[0068] The initial registration screen shown in Figure 4(D) is displayed after the connection with Cart 70 is complete, and therefore the cart image G134 is displayed to indicate that a connection (communication is possible) with Cart 70 is in progress. The same applies to other screens while connected to Cart 70 (registration screens in Figures 4(E) to 4(G)).

[0069] Furthermore, after the user presses the "Start Shopping Without Cart" button G112, the mobile terminal 50 does not display the connection code reading instruction screen (Figure 4(C)), but instead displays the initial registration screen (not shown). The initial registration screen (not shown) displayed after pressing the "Start Shopping Without Cart" button G112, and other screens (not shown) to which the user transitions from this initial screen, are not screens displayed while connected to the cart 70, and therefore the cart image G134 is not displayed.

[0070] In addition, when the holder portion 74 is positioned and looking down towards the shopping basket, the image captured will show the shopping basket and items already placed in the shopping basket when no scanning operation is being performed, and when a scanning operation is being performed, the target product of the scanning operation and the shopping basket and items already placed in the shopping basket behind it will be captured. However, in Figure 4(D) (and similarly in Figures 4(E) to 4(G) and Figures 5(D) to 5(G)), for simplification, items other than the target product of the scanning operation (such as the shopping basket and items already placed in the shopping basket) are omitted from the illustration.

[0071] Figure 4(E) shows the registration screen after registering products. Specifically, if the mobile terminal 50 registers XX bread as the first product and XX oolong tea as the second product, it will display a registration screen like the one shown in Figure 4(E).

[0072] In Figure 4(E), the captured image display area G131 of the registration screen shows (imaged) "XX Oolong Tea". In other words, Figure 4(E) shows the scene immediately after "XX Oolong Tea" is registered (immediately after scanning the barcode of "XX Oolong Tea"), that is, the scene before "XX Oolong Tea" is placed in the cart 70 (more specifically, the shopping basket placed on the mounting unit 71).

[0073] In the registration information display area G132 of the registration screen in Figure 4(E), information about the registered product (product name, quantity, price) is displayed. Specifically, "XX Bread, 1 piece, ¥220" is displayed as the first product item, and "XX Oolong Tea, 1 piece, ¥150" is displayed as the second product item. The mobile terminal 50 may register a product by querying another device that stores the product master (for example, the cloud server 20) (by sending the product code obtained by scanning the barcode), or it may store the product master in the information storage unit 601 of its own terminal and register a product by referring to the product master of its own terminal.

[0074] In the registration information display area G132 of the registration screen, the column for "XX Bread" shows "Weight OK". Since "XX Oolong Tea" has not been added to cart 70, the column for "XX Oolong Tea" does not show "Weight OK".

[0075] Furthermore, after registering one product item, the mobile terminal 50 can accept an operation to proceed to checkout (settlement) (i.e., to finish shopping (product registration)). Accordingly, the registration screen (image display area G131) shown in Figure 4(E) displays an operable "Proceed to Checkout" button G141, which accepts the operation to proceed to checkout, and an explanatory image G142 describing the "Proceed to Checkout" button G141 is displayed.

[0076] Figure 4(F) shows an example of the display when XX Oolong Tea is placed into cart 70 from the scene in Figure 4(E), and the weighing result (weighing value, etc.) is received from cart 70. When the mobile terminal 50 receives the weighing result from cart 70, it displays "Weight OK" in the XX Oolong Tea field of the registered information display area G132, as shown in Figure 4(F).

[0077] Figure 4(G) shows an example of the display when XX Oolong Tea is not placed in cart 70 from the scene in Figure 4(E). If the mobile terminal 50 does not receive the weighing result from cart 70 (received within a predetermined time), it displays "Weight NG" in the XX Oolong Tea column of the registration information display area G132, as shown in Figure 4(G).

[0078] The mobile terminal 50 displays "Weight OK" if it receives the weighing result from the cart 70, and "Weight NG" if it does not receive the weighing result from the cart 70. Therefore, "Weight OK" and "Weight NG" are information related to the weighing result (information based on whether or not the weighing result was received, information corresponding to the weighing of the cart 70). The cart image G134 is also one of the pieces of information related to the weighing result. Notwithstanding the illustrated examples, it is not necessary to display indications such as "Weight OK" or "Weight NG" when implementing the present invention.

[0079] Figure 4(H) shows the payment code display screen that appears after pressing the "Proceed to Checkout" button G141. The payment code display screen shown in Figure 4(H) displays the payment code G151 (described later), a message G152 instructing the payment device 80 ("payment machine" in the figure) to read the payment code G151, and an explanatory image G153 explaining how to read the payment code G151 at the payment machine. In addition, the payment code display screen shown in Figure 4(H) displays the "Return to Shopping" button G154, which is operable. If the "Return to Shopping" button G154 is pressed, the registration screen that was displayed before pressing the "Proceed to Checkout" button G141 is shown.

[0080] The settlement code G151 is a two-dimensional code representing transaction identification information that identifies the transaction information of a particular transaction from among multiple transaction information (including weight OK / weight NG information) stored in the cloud server 20. In other words, the settlement code G151 displayed by a mobile terminal 50 is information for identifying the transaction information of that mobile terminal 50 (transaction information of the product registered by that mobile terminal 50) from among multiple transaction information stored in the cloud server 20. The settlement device 80, upon reading the settlement code G151 displayed by a mobile terminal 50, obtains (receives) the transaction information of that mobile terminal 50 from the cloud server 20. Note that the settlement code G151 may also be a two-dimensional code representing the location information of the transaction information of the mobile terminal 50 (storage location within the sales system 1, such as a URI (Uniform Resource Identifier)).

[0081] Figure 5 shows an example of the display on the mobile terminal 50. Specifically, Figure 5 shows an example of the display when the mobile terminal 50 connects to the cart 70 using the NFC tag 77. It is assumed that the application 60 is already installed on the mobile terminal 50.

[0082] Figure 5(A) shows the initial screen of the mobile terminal 50. The initial screen shown in Figure 5(A) is the same as the initial screen shown in Figure 4(A), so no explanation is provided.

[0083] Figure 5(B) shows the connection completion screen displayed after the connection with the cart 70 (connection using device identification information obtained from the NFC tag 77) is completed. As shown in Figure 5(B), the connection completion screen displays (places) the launch reception unit G211 instead of the app 60 icon G201. The launch reception unit G211 is an area where the app 60 is launched by operation, similar to the app 60 icon G201. The launch reception unit G211 is larger in size than the app 60 icon G201.

[0084] In Figure 5(B), an example is shown in which the launch reception unit G211 is displayed instead of the app icon G201. However, the app icon G201 may be made inoperable by displaying the launch reception unit G211 in a position where it is not visible (in front of the app icon G201). Alternatively, the launch reception unit G211 may be an enlarged display of the app icon G201. In other words, when the mobile terminal 50 has completed the connection with the cart 70, the app icon G201 may be changed from its normal form to an enlarged form. In addition, the launch reception unit G211 may be displayed separately from the app icon G201 in a position where the app icon G201 is visible, and the app icon G201 may remain operable even after the launch reception unit G211 is displayed.

[0085] Figure 5(C) shows the menu screen (start screen) displayed immediately after launching the application 60. For example, when the launch reception unit G211 on the connection completion screen (Figure 5(B)) is operated (e.g., tapped), the mobile terminal 50 displays the menu screen shown in Figure 5(C). The menu screen shown in Figure 5(C) displays a cart image G134 indicating that it is connected to (communicating with) the cart 70. The same applies to other screens while connected to the cart 70 (registration screens in Figures 5(D) to 5(G)). In addition, the menu screen shown in Figure 5(C) displays various buttons, such as a shopping start button G221 that accepts the operation to start shopping, which can be operated. A related information display area G113 is provided at the bottom of the menu screen to display related information. Furthermore, the mobile terminal 50 may launch the application 60 and display the menu screen without transitioning to the connection completion screen shown in Figure 5(B) upon connecting with the cart 70.

[0086] Figure 5(D) shows the registration screen displayed after pressing the shopping start button G221 (the initial registration screen before registering the first product). The initial registration screen shown in Figure 5(D) is the same as the initial registration screen shown in Figure 4(D), so no explanation is provided.

[0087] If a connection to cart 70 cannot be established, the user will proceed to operate the app icon G201 in Figure 5(A) → display the menu screen (Figure 5(C)) (however, the cart image G134 will not be displayed). After the user operates the start shopping button G221, the mobile terminal 50 may display a message such as "Do you want to shop using a cart?" and a button to accept the user's request to shop using cart 70. If the user's request to shop using cart 70 is accepted, the mobile terminal 50 may retry connecting to cart 70.

[0088] Figure 5(E) shows the registration screen after registering products. Specifically, if the mobile terminal 50 registers XX bread as product item 1 and XX oolong tea as product item 2, it will display a registration screen like the one shown in Figure 5(E). The registration screen shown in Figure 5(E) is the same as the registration screen shown in Figure 4(E), so no explanation is provided.

[0089] Figure 5(F) shows an example of the display when XX Oolong Tea is placed into cart 70 from the scene in Figure 5(E) and the weighing result (weighing value, etc.) is received from cart 70. Figure 5(G) shows an example of the display when XX Oolong Tea is not placed into cart 70 from the scene in Figure 5(E). The registration screens shown in Figures 5(F) and 5(G) are the same as the registration screens shown in Figures 4(F) and 4(G), respectively, so their explanation is omitted.

[0090] Figure 5(H) shows the payment code display screen that appears after pressing the G141 button to proceed to checkout. The payment code display screen shown in Figure 5(H) is the same as the payment code display screen shown in Figure 4(H), so no further explanation is provided.

[0091] From this point onward, the customer has the settlement code G151 displayed on the mobile terminal 50 read by the settlement device 80 (the scanner unit of the settlement device 80) to receive payment. Specifically, when the settlement device 80 reads the settlement code G151 displayed on the mobile terminal 50, it obtains the content of the transaction information identified by the transaction identification information (information about the product registered by the mobile terminal 50) from the cloud server 20 based on the transaction identification information obtained from the settlement code G151 (transaction identification information that identifies the transaction information of the mobile terminal 50). Then, based on this transaction information, it performs the settlement using the payment method desired by the customer.

[0092] ● Processing Flow (When obtaining connection information by executing the functions of app 60, connection is made using a 1 / 2 QR code 76.) Figure 6 is a flowchart illustrating an example of the operation of the mobile terminal 50. This flowchart in Figure 6 shows a series of operations performed by a customer visiting a store using the mobile terminal 50, and is an example of the process when connection information is obtained from a 2D code 76 using an application 60 already installed on the mobile terminal 50. It should be assumed that when this flowchart is displayed (upon arrival at the store), the mobile terminal 50 is displaying the initial screen (Figure 4(A)).

[0093] Step S101: The mobile terminal 50 accepts an operation to launch the application 60. For example, the mobile terminal 50 accepts an operation to the application 60 icon G101 on the initial screen (Figure 4(A)). Step S102: The mobile terminal 50 displays the menu screen (Figure 4(B)). Step S103: The mobile terminal 50 accepts the operation to start shopping using the cart 70. For example, the mobile terminal 50 accepts the operation of the "Start Shopping with Cart" button G111 on the menu screen (Figure 4(B)). Step S104: The mobile terminal 50 displays a screen for reading connection information (Figure 4(C)).

[0094] Step S105: The mobile terminal 50 determines whether it has obtained connection information (device identification information of the cart 70) for connecting with the cart 70. For example, if the mobile terminal 50 reads a 2D code 76 attached to the cart 70 based on customer operation, it obtains the connection information of the cart 70 from the 2D code 76. If the connection information has been obtained (Step S105: YES), the process proceeds to Step S106. If the connection information has not been obtained (Step S105: NO), the process is repeated in Step S105.

[0095] Step S106: The mobile terminal 50 pairs with the cart 70 and connects. Step S107: The mobile terminal 50 transmits tare instruction information to the cart 70. Step S108: The mobile terminal 50 transmits information about the cart 70 to the cloud server 20. For example, the mobile terminal 50 receives information about the cart 70 from the cart 70, such as the cart's serial number (which cart it is), battery status, and various error information, and transmits it to the cloud server 20. This allows the administrator to monitor the information about the cart 70 in, for example, the transaction status management device 40, and perform necessary maintenance on the cart 70 as appropriate. Step S109: The mobile terminal 50 displays the initial registration screen (Figure 4(D)).

[0096] Furthermore, in step S108 (and similarly in step S203 in Figure 7), information about the cart 70 received from the cart 70 is sent to the cloud server 20. Therefore, the cart 70 itself does not need to have a function to communicate with the cloud server 20, and the cart 70 can be implemented at a low cost.

[0097] Furthermore, if the mobile terminal 50 obtains connection information from the cart 70 (step S105: YES) but fails to connect to the cart 70 for any reason, the mobile terminal 50 may send connection failure information to the cloud server 20 as information about the cart 70, since the cart 70 can be uniquely identified from the connection information. This also provides the administrator with information on the connection relationship (communication unit 704) so ​​that maintenance can be performed. In addition, if the mobile terminal 50 fails to connect to the cart 70 for any reason, instead of sending connection failure information to the cloud server 20, it may output a message (screen display, audio output) such as, for example, "The cart may be malfunctioning. Please use another cart." The same applies when connecting to the cart 70 using the NFC tag 77 (as shown in the flowchart in Figure 7).

[0098] The order of steps S107 to S109 is not particularly limited. In other words, the mobile terminal 50 only needs to send tare instruction information to the cart 70 based on its connection to the cart 70, send information about the cart 70 to the cloud server 20, and display the initial registration screen, and the order is not particularly limited.

[0099] Step S110: The mobile terminal 50 determines whether or not it has read the product's barcode based on the customer's scanning action. If it has read it (Step S110: YES), proceed to Step S111. If it has not read it (Step S110: NO), repeat Step S110.

[0100] Step S111: The mobile terminal 50 registers the product (the product whose barcode was read in step S110). The mobile terminal 50 displays (adds) the product's information (product name, quantity, price) to the registration information display area G132 of the registration screen, and updates the total information. Step S112: The mobile terminal 50 receives the weighing result (weighed value) from the cart 70. In other words, the product (the product registered in step S111) is placed in the cart 70, weighed by the cart 70, and the weighing result is transmitted from the cart 70 to the mobile terminal 50. Step S113: The mobile terminal 50 displays information regarding the weighing result (for example, "Weight OK") in the registration information display area G132 (the field for the relevant product) on the registration screen.

[0101] Step S114: The mobile terminal 50 determines whether or not it has read the product's barcode based on the customer's scanning action. If it has read it (Step S114: YES), return to Step S111. If it has not read it (Step S114: NO), proceed to Step S115. Step S115: The mobile terminal 50 determines whether to terminate registration or not. For example, if the user presses the button G141 to proceed to checkout, the mobile terminal 50 determines to terminate registration. If registration is terminated (Step S115: YES), the user proceeds to Step S116. If registration is not terminated (Step S115: NO), the user returns to Step S114.

[0102] Step S116: The mobile device 50 disconnects from the cart 70 and cancels the pairing. Step S117: The mobile terminal 50 displays the payment code display screen (Figure 4(H)).

[0103] In this flowchart, the mobile terminal 50 receives the weighing result (weighing value) from the cart 70 within a predetermined time after product registration (step S112), and displays "Weight OK" in step S113 as information regarding the weighing result (information based on whether or not the weighing result was received). However, if the mobile terminal 50 does not receive the weighing result from the cart 70 within a predetermined time after product registration, it displays "Weight NG" in step S113 as information regarding the weighing result.

[0104] Furthermore, although this flowchart describes the process of receiving the weighing result (weighing value) from the cart 70 (step S112), the mobile terminal 50 may also receive a judgment result (information indicating that it has been determined that goods have been placed in the cart). In other words, if the mobile terminal 50 receives the judgment result from the cart 70 within a predetermined time from product registration in step S112, it may display "Weight OK" in step S113 as information regarding the judgment result (information based on whether or not the judgment result has been received, etc.). If the mobile terminal 50 does not receive the judgment result from the cart 70 within a predetermined time from product registration, it may display "Weight NG" in step S113 as information regarding the judgment result.

[0105] (When obtaining connection information by executing the function of app 60, 2 / connection via NFC tag 77) Figure 7 is a flowchart illustrating an example of the operation of the mobile terminal 50. This flowchart in Figure 7 shows a series of operations performed by a customer visiting a store using the mobile terminal 50, and is an example of the process when the application 60 is already installed on the mobile terminal 50 and connection information is obtained from the NFC tag 77. It should be assumed that when this flowchart is displayed (upon arrival at the store), the mobile terminal 50 is displaying the initial screen (Figure 5(A)).

[0106] Step S201: The mobile terminal 50 determines whether or not it has received connection information (device identification information of the cart 70) for connecting with the cart 70. For example, when a customer places the mobile terminal 50 in the holder portion 74 of the cart 70, it receives the connection information of the cart 70 from the NFC tag 77 attached to the holder portion 74 of the cart 70. If the connection information is received (Step S201: YES), proceed to Step S202. If the connection information is not received (Step S201: NO), repeat Step S201.

[0107] Step S202: The mobile terminal 50 pairs with the cart 70 and connects. Step S203: The mobile terminal 50 transmits information about the cart 70 to the cloud server 20. This allows the administrator to monitor the information about the cart 70, for example, in the transaction status management device 40, and perform necessary maintenance on the cart 70 as needed.

[0108] Furthermore, if the mobile terminal 50 receives connection information from the cart 70 (step S201: YES) but fails to connect with the cart 70, the connection information can be used to uniquely identify the cart 70. Therefore, connection failure information can be sent to the cloud server 20 as information about the cart 70. Connection relationship information (communication unit 704) can also be provided to the administrator for maintenance.

[0109] Step S204: The mobile terminal 50 displays a connection completion screen (Figure 5(B)). Step S205: The mobile terminal 50 accepts an operation to launch the application 60. For example, the mobile terminal 50 accepts an operation to the launch acceptance unit G211 on the connection completion screen (Figure 5(B)). Step S206: The mobile terminal 50 displays the menu screen (Figure 5(C)). Step S207: The mobile terminal 50 accepts the operation to start shopping. For example, the mobile terminal 50 accepts the operation of the "Start Shopping" button G221 on the menu screen (Figure 5(C)). Step S208: The mobile terminal 50 transmits tare instruction information to the cart 70. Step S209: The mobile terminal 50 displays the initial registration screen (Figure 5(D)).

[0110] The following steps S210 to S217 in Figure 7 are the same as steps S110 to S117 in Figure 6, so their explanation will be omitted.

[0111] (If you want to obtain connection information without going through app 60, see option 1) Figure 8 is a flowchart illustrating an example of the operation of the mobile terminal 50. Specifically, the flowchart in Figure 8 shows the process when a customer visiting a store obtains connection information through an application program or terminal function different from the application 60 for this service, without launching the application 60. In this example, the connection information includes not only the device identification information of the cart 70, but also additional information such as the address (URL) of the download site for the application 60. Furthermore, the command information includes instructions to launch the application 60 if the application 60 is installed on the mobile terminal 50, and to access the download site for the application 60 if the application 60 is not installed.

[0112] Step S301: The mobile terminal 50 obtains connection information (device identification information of the cart 70) for connecting with the cart 70. For example, the mobile terminal 50 obtains connection information from a two-dimensional code 76 attached to the cart 70. However, in this example, the two-dimensional code 76 is read by an application program different from the app 60 (an application program that reads two-dimensional codes, which is either independently installed by the mobile terminal 50 or installed by the customer, etc., independently of the app 60), and the connection information of the cart 70 is obtained from the two-dimensional code 76.

[0113] Step S302: If app 60 is installed on mobile device 50 (Step S302: YES), proceed to step S303. If app 60 is not installed on mobile device 50 (Step S302: NO), proceed to step S304.

[0114] Step S303: If app 60 is installed on the mobile terminal 50 (Step S302: YES), the OS of the mobile terminal 50 receives the app launch command included in the connection information and launches app 60 without accessing the download site. After the application 60 is launched, in one example, the process proceeds to step S102 described above, and the mobile terminal 50 displays the menu screen (Figure 4(B)). Subsequently, the process from step S103 onwards is executed. In another example, the connection information or the device identification information among the connection information acquired in step S301 is retained even after the application 60 is launched, and the process proceeds to step S106, where the mobile terminal 50 is paired with the cart 70 by the connection unit 603 based on the retained device identification information. Subsequently, the process from step S107 onwards is executed, and the mobile terminal 50 displays the initial registration screen (Figure 4(D)), skipping the menu screen (Figure 4(B)). In other words, the process from when the mobile terminal 50 has not launched the application 60 to the initial registration screen (Figure (D)) can be completed in a single operation.

[0115] Step S304: The OS of the mobile terminal 50 accesses the download site via the communication unit 508 based on the URL of the download site included as additional information in the connection information and the command to connect to the said download site included as command information.

[0116] Step S305: If app 60 is not installed on mobile device 50 (Step S302: NO), the download site allows the user to choose, for example, to install app 60 or cancel the operation. If app 60 is to be installed on mobile device 50 (Step S304: YES), app 60 is installed on mobile device 50 and the process proceeds to step S303. If app 60 is not to be installed on mobile device 50 (Step S304: NO), the process ends.

[0117] In this example, we demonstrated how to obtain connection information from a 2D code 76, but the same process is followed when obtaining connection information via an NFC tag 77, beacon, or wired connection.

[0118] (If you want to obtain connection information without going through app 60, see option 2) Figure 9 is a flowchart illustrating an example of the operation of the mobile terminal 50. Similar to the example explained with reference to Figure 8, this example shows the process when a customer visiting a store obtains connection information without launching the app 60. However, in this example, the connection information includes not only the device identification information of the cart 70, but also the address (URL) of the download site for the application 60 as additional information, and the command information includes information that commands access to the download site for the application 60.

[0119] In this example, if app 60 is launched and connection information is obtained from app 60, for example, depending on the settings of app 60, it is possible to ignore the command to access the download site and connect to cart 70 using the device identification information of cart 70.

[0120] Step S401: The mobile terminal 50 obtains connection information (device identification information of the cart 70) for connecting with the cart 70. For example, the mobile terminal 50 obtains connection information from a two-dimensional code 76 attached to the cart 70. However, in this example as well, the two-dimensional code 76 is read by an application program different from the app 60 (an application program that reads two-dimensional codes, which is either independently installed by the mobile terminal 50 or installed by the customer, etc., independently of the app 60), and the connection information of the cart 70 is obtained from the two-dimensional code 76.

[0121] Step S402: The OS of the mobile terminal 50 accesses the download site via the communication unit 508 based on the URL of the download site included in the connection information and the connection command that instructs the connection to the said download site.

[0122] Step S403: On the download site, you can make selections based on the installation status of app 60. Step S404: If app 60 is installed (Step S403: YES), you can choose to launch or uninstall app 60 on the download site.

[0123] Step S405: If launching app 60 is selected (Step S404: YES), app 60 is launched. After app 60 is launched, in one example, the process proceeds to step S102 as described above, and the mobile terminal 50 displays the menu screen (Figure 4(B)). Subsequently, the process following step S103 is executed. In another example, the connection information or device identification information obtained in step S401 is retained even after launching app 60, and the process proceeds to step S106, where the mobile terminal 50 pairs with the cart 70 based on the retained device identification information via the connection unit 603 and connects. Subsequently, the process following step S107 is executed, and the mobile terminal 50 displays the initial registration screen (Figure 4(D)), skipping the menu screen (Figure 4(B)).

[0124] Step S406: If uninstalling app 60 is selected (Step S404: NO), app 60 will be uninstalled and the process will terminate.

[0125] Step S407: If app 60 is not installed (Step S403: NO), the download site allows you to choose to install app 60 or cancel the operation. If you choose to install app 60 on the mobile device 50 (Step S407: YES), app 60 will be installed on the mobile device 50 and the process will proceed to Step S405. If you do not choose to install app 60 on the mobile device 50 (Step S407: NO), the process will terminate.

[0126] In this example, we have shown how to obtain connection information from a 2D code 76, but the same process is followed when obtaining connection information via an NFC tag 77, a beacon, or a wired connection.

[0127] As described above, this embodiment allows the customer to proceed smoothly with shopping, regardless of the settings or operating status of the customer's mobile terminal 50, as the process of installing the application 60, launching the application 60, or displaying the product registration screen proceeds in response to the acquisition of connection information. Furthermore, customers using the cart 70 can register items using their own mobile device 50. On the other hand, stores do not need to equip the cart 70 with scanner functions or item display functions, as customers can register items using their mobile devices 50. Furthermore, connecting the mobile terminal 50 and the cart 70 is easy. That is, once connection information is provided by reading the 2D code 76, NFC communication, or beacon, the customer can connect the mobile terminal 50 and the cart 70 without being required to perform any complex operations.

[0128] ● 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 below. Furthermore, the following items may be combined as appropriate.

[0129] In the above embodiment, an example was described in which a two-dimensional code 76 is attached to the mobile terminal charging unit 75, but the two-dimensional code 76 may be attached to a location other than the mobile terminal charging unit 75. One or more two-dimensional codes 76 may be attached to a location other than the mobile terminal charging unit 75 of the cart 70. The two-dimensional code 76 may also be attached on top of the NFC tag 77 (i.e., superimposed on the NFC tag 77).

[0130] In the above embodiment, an example was described in which one NFC tag 77 is attached to the holder portion 74. However, two or more NFC tags 77 may be attached to the holder portion 74, or one or more NFC tags 77 may be attached to locations other than the holder portion 74 of the cart 70 instead of, or in addition to, attaching one or more NFC tags 77 to the holder portion 74.

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

[0132] In the above embodiment, the connection with the cart 70 may be lost during product registration (after operating the Start Shopping button G221 but before operating the Proceed to Checkout button G141). The connection is lost when the mobile terminal 50 is removed from the cart 70 and moved a certain distance away from it (however, if Bluetooth is deactivated in the settings of the mobile terminal 50, the connection will also be lost if the mobile terminal 50 or cart 70 malfunctions or loses power). When the connection is lost, an attempt is made to reconnect in the background, and the connection will be re-established when the distance is reduced. Furthermore, if the mobile terminal 50 loses connection with the shopping cart 70 during product registration, it may continue product registration.

[0133] In the above embodiment, an example was described in which the connection between the mobile terminal 50 and the cart 70 is disconnected based on the operation of the button G141 to proceed to checkout, but the conditions for disconnection are not limited to this. For example, any of the following a to e may be used. a: Based on the fact that the settlement device 80 has read the settlement code G151, the connection between the mobile terminal 50 and the cart 70 is disconnected. Note that the fact that the settlement device 80 has read the settlement code G151 can be communicated, for example, from the settlement device 80 to the mobile terminal 50 via the cloud server 20. That is, when the settlement device 80 reads the settlement code G151, it requests transaction information from the cloud server 20, and the cloud server 20, upon receiving the request, may notify the mobile terminal 50 that the settlement device 80 has read the settlement code G151. b: Based on the completion of payment at the payment device 80, the connection between the mobile terminal 50 and the cart 70 is disconnected. The completion of payment at the payment device 80 can be communicated, for example, from the payment device 80 to the mobile terminal 50 via the cloud server 20. That is, the payment device 80 sends payment information to the cloud server 20 after payment is completed, and the cloud server 20, upon receiving the payment information, may notify the mobile terminal 50 that payment has been completed. c: An exit gate device is installed inside the store, and the connection between the mobile terminal 50 and the cart 70 is disconnected based on the customer passing through the exit gate device. The fact that a customer has passed through the exit gate device can be communicated to the mobile terminal 50 via the cloud server 20, for example. That is, the exit gate device may recognize that each customer has passed through by reading a predetermined barcode displayed on the mobile terminal 50 after payment is completed, or printed on a predetermined medium. d: Based on the fact that cart 70 has been returned to the cart storage area, the connection between the mobile terminal 50 and cart 70 is disconnected. Note that the mobile terminal 50 may determine that cart 70 has been returned to the cart storage area itself using GPS or beacons, or cart 70 (which determines the return from the start of charging at the cart storage area) may notify the mobile terminal 50. e: Based on the fact that the customer has left the store, the connection between the mobile device 50 and the cart 70 is disconnected. The mobile device 50 itself may determine that the customer has left the store using GPS or beacons.

[0134] Cart 70 may be able to connect to network NW1, for example, via wireless LAN.

[0135] In the above embodiment, the mobile terminal 50 was described as being owned by the customer, but a terminal provided by the store (a rental terminal) may also be used. The rental mobile terminal 50 is provided as a dedicated terminal in a state where only the application 60 can be executed. In a configuration that connects to the cart 70 using a 2D code 76, if the mobile terminal 50 is a rental terminal, the menu screen is displayed from the beginning.

[0136] The state in which communication is established between the mobile terminal 50 using Bluetooth and the cart 70 is described as "pairing," but this is not limited to encrypted communication; it may also be unencrypted communication. Furthermore, it may also be so-called bonding, which involves executing a key exchange protocol for encryption, storing the key, and then communicating. In other words, as used in this application, pairing refers to the state in which Bluetooth communication is established, and the specific details of this state are not specified.

[0137] In the above embodiment, the mobile terminal 50 and the cart 70 are connected by the connection unit 603. However, the weighing value from the weighing unit 703 may be used as a key to link the cart 70 with the transaction, making it appear as if the cart 70 and the mobile terminal 50 are connected. When the weight of the product registered through operations on the app 60 matches the weighing value of the product weighed by the cart 70 at the same time, the two are considered to constitute a single transaction, and the transaction (product registration) by the mobile terminal 50 (app 60) and the cart 70 are automatically associated.

[0138] Figure 10 shows an example of processing according to this embodiment. In this example, the shopping cart 70 and the mobile terminal 50 (app 60) are configured to communicate with the cloud server 20, and the cloud server 20 performs the association between the transaction (product registration) by the mobile terminal 50 (app 60) and the shopping cart 70.

[0139] First, when a product is registered on the mobile terminal 50 via the application 60 (S501), product registration information, including at least information that can identify the mobile terminal 50 or the application 60, and information relating to the registered product, is transmitted to the cloud server 20 (S502). Meanwhile, in the cart 70, when a registered product is placed on the placement unit 71, the weighing unit 703 weighs the product (S503), and weighing information including at least information that can identify the cart 70 and information related to the weighed value of the product is transmitted to the cloud server 20 (S504).

[0140] When the cloud server 20 receives product registration information and weighing information at the same time (S505), it determines whether the product weight and weighing value match (S506). It should be noted that the term "same timing" here does not necessarily mean the exact same time; it does not need to be the exact same time, but rather any timing within a reasonable range of time required from the time the customer registers the product until they add it to their cart 70. Furthermore, the product weight is based on, for example, the weight value for each product that is stored in a predetermined table. This predetermined table may be stored by the cloud server 20 or by the application 60, and if the application 60 stores it, the product weight information may be transmitted from the application 60 to the cloud server 20 as part of the product information.

[0141] The cloud server 20 associates the transaction made by the mobile terminal 50 (app 60) that registered the product with the shopping cart 70 when the product weight and the measured value match. For example, if the weight data of a product registered through an operation on app 60 is 200g, and there is a shopping cart 70 that has measured an increase of 200g at the same time, the cloud server 20 considers both to constitute a single transaction and performs the association. As a result, transactions and carts 70 are linked without the customer being aware of it, so customers do not need to perform the operation to obtain connection information as described above, and can simply launch the smartphone app 60 and register the product as before. Furthermore, if the product weight and the measured value do not match during processing in S506, error processing is performed (S507). In error processing, for example, if it is determined that the customer may have fraudulently placed a product different from the registered product into the cart 70, the store staff will be notified of the situation via the transaction status management device 40 or the like. Alternatively, the customer may be notified via the mobile terminal 50 (app 60) to invalidate or redo the product registration.

[0142] In this example, the cloud server 20 associates transactions with carts 70. However, when the cloud server 20 identifies the transactions and carts 70 to be associated, it may also send a message to the mobile terminal 50 (app 60) requesting a connection to the identified carts 70.

[0143] In this embodiment, 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 80, the first registration settlement device, the second registration settlement device, the third registration settlement device, the mobile terminal 50, etc.) may be implemented in other devices different from the device described as the entity executing those functions. For example, each device may function as a so-called thin client specialized 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 using a browsing function, etc. As an example, cloud server 20 may control the display of the screen (Figures 4, 5, etc.) and the operation (Figures 6, 7, etc.) of the mobile terminal 50. In other words, the program (app 60) that controls the operation of the mobile terminal 50 related to this service may run on the CPU of the mobile terminal 50 or on the CPU of cloud server 20. Also, app 60 may be a web application used with a browser.

[0144] Furthermore, in this embodiment, each functional unit or means can be combined as appropriate to the extent that it does not create a contradiction, or each functional unit or means can be provided on terminals or devices different from those in this example. Also, the order of processing performed by each functional unit or means can be changed to the extent that it does not create a contradiction.

[0145] ●Summary of Embodiments This invention relates to a sales system.

[0146] Information and communication terminals are known that read the MAC address of a device from an NFC tag attached to the device and transmit data to the IP address corresponding to the read MAC address (see, for example, Japanese Patent No. 6375732). In addition, a system is known in which customers register products themselves in a product display area using a shopping cart.

[0147] In this regard, when operating a system that uses customer terminals for product registration, it is preferable to provide a dedicated application program for those customer terminals. However, when customers begin shopping in a store using their customer terminals, the installation status and execution status of the application program will vary from customer to customer. Therefore, there is a need for a system that allows customers to proceed with shopping smoothly regardless of the settings or operation status of their customer terminals.

[0148] Therefore, one of the objectives of the present invention is to provide a sales system that allows customers to proceed with shopping smoothly, regardless of the settings or operating status of the customer terminal.

[0149] To achieve the above objective, the sales system according to the present invention is a sales system comprising a shopping cart equipped with a weighing function and a shopping application program installed on a customer's mobile terminal, comprising: connection means for establishing communication with the shopping cart when connection information including at least device identification information for connecting to the shopping cart is obtained, and the application program is already installed on the mobile terminal; and display means for displaying a screen for installing the application program when connection information including at least device identification information for connecting to the shopping cart is obtained, and the application program is not already installed on the mobile terminal.

[0150] The system may also include a startup means for starting the application program if, upon obtaining connection information including at least device identification information for connecting to the shopping cart, the application program is already installed on the mobile terminal but is not running.

[0151] The system further includes a registration means for registering products by reading product codes, and the display means may, upon obtaining connection information including at least device identification information for connecting to the shopping cart, and if the application program is already installed, display a registration screen for registering products using the registration means while communication with the shopping cart is established by the connection means.

[0152] The connection information may include device identification information for connecting to the shopping cart and address information for the application program download site.

[0153] The connection means may, upon obtaining connection information including at least device identification information for connecting to the shopping cart, establish communication with the shopping cart based on the device identification information for connecting to the shopping cart, without accessing a download site, if the application program is already installed on the mobile terminal.

[0154] The aforementioned connection information may include instruction information.

[0155] Furthermore, the above-mentioned sales system and the computer programs that cause the devices and terminals constituting the above-mentioned sales system to execute predetermined processes may be provided by download via a network such as the Internet, or by recording them on various computer-readable recording media such as CD-ROMs.

[0156] According to the sales system of this embodiment described above, regardless of the settings or operating status of the customer's mobile terminal, the process proceeds from obtaining connection information to installing the application program, launching the application program, or displaying the product registration screen, allowing the customer to proceed with shopping smoothly. [Explanation of symbols]

[0157] 1: Sales System 2: Cloud Server 10: Headquarters Server 20: Cloud Server 30: Store Controller 40: Transaction status management device 50: Mobile devices 501:CPU 502: Information storage section 503:Operation unit 504: Audio output section 505: Voice input section 506: Imaging Unit 507: Detection unit 508: Communications Department 60: App 601: Information storage section 602: Connection Information Acquisition Unit 603: Connection part 604: Registration Department 605: Operation Processing Unit 606: Code generation processing unit 607: Communication Processing Unit 70: Cart 701: CPU 702: Information storage section 703:Measuring section 704: Communications Department 80:Payment device

Claims

1. A sales system comprising a shopping cart equipped with a weighing function and a shopping application program installed on the customer's mobile device, When connection information, including at least device identification information for connecting to the shopping cart, is obtained, and the application program is installed on the mobile terminal, a connection means for establishing communication with the shopping cart is provided. The system includes, when connection information, including at least device identification information for connecting to the shopping cart, is obtained, and if the application program is not already installed on the mobile terminal, a display means for displaying a screen for installing the application program, Sales system.

2. The system includes, upon obtaining connection information including at least device identification information for connecting to the shopping cart, and if the application program is already installed on the mobile terminal but the application program is not running, a startup means for starting the application program. The sales system according to claim 1.

3. It also includes a registration method for registering products by reading the product code, When the display means obtains connection information, which includes at least device identification information for connecting to the shopping cart, and the application program is already installed, it will display a registration screen for registering products using the registration means, with communication established with the shopping cart by the connection means. The sales system according to claim 1 or 2.

4. The connection information includes device identification information for connecting to the shopping cart and address information for the application program download site. The sales system according to claim 1 or 2.

5. When the connection means obtains connection information, which includes at least device identification information for connecting to the shopping cart, and the application program is already installed on the mobile terminal, it establishes communication with the shopping cart based on the device identification information for connecting to the shopping cart without accessing the download site. The sales system according to claim 4.

6. The aforementioned connection information includes instruction information, The sales system according to claim 1 or 2.

Images