Sales management system, mobile terminals, and programs

Abstract

To provide an environment that facilitates shopping at a shop utilizing a portable terminal.SOLUTION: There is provided a portable terminal including: position specifying means for specifying a current position; and shop specifying means for specifying a predetermined shop that performs adjustment of a registered commodity. The shop specifying means specifies the predetermined shop based on the position, or when the predetermined shop cannot be specified based on the position, prompts a customer to input shop information, thereby specifying the predetermined shop by using the shop information as input.SELECTED DRAWING: Figure 31

Description

Technical Field

[0001] The present invention relates to a sales data processing system and program for identifying and managing product information.

Background Art

[0002] Conventionally, self-service POS systems for customers to perform registration processing of purchased products have become widespread. Furthermore, there is a portable registration device that can register products simultaneously when placing them in a shopping basket or the like. In recent years, a sales data processing system is known in which a shopping application is downloaded to a portable terminal such as a smartphone owned by a customer and used as a registration device for the customer to perform their own product registration at a store.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] A sales data processing system using a portable terminal such as a smartphone can register products with a portable terminal such as a smartphone that the customer is familiar with, thus saving the time required for registration processing at the cash register.

[0005] However, when using a portable terminal, it is necessary to identify the store where shopping is being done. In this case, procedures such as inputting the store into the portable terminal or identifying the store are required for the customer, forcing the customer to perform time-consuming tasks when shopping.

[0006] Furthermore, when customers use mobile devices to process credit card payments themselves, it can be difficult for the store to confirm whether the payment process using electronic payment methods such as credit cards has been successfully completed.

[0007] This invention was made in view of the above circumstances and aims to provide an environment that facilitates shopping at stores using mobile devices. [Means for solving the problem]

[0008] According to one embodiment, a sales management system including a mobile terminal includes a location identification means for identifying the current location of the mobile terminal, Based on the current location of the mobile terminal identified by the aforementioned location identification means A store identification means that identifies a designated store where the settlement of registered goods will be carried out, and after the designated store has been identified by the store identification means An acquisition means that obtains product information by reading a barcode at the store, and based on the product information obtained by the acquisition means The system includes a product registration means for performing product registration processing. The store identification means, when multiple stores are detected as candidates based on the current location of the identified mobile terminal, displays an option to select one of the multiple stores as the predetermined store. A sales management system with the following features is provided. [Effects of the Invention]

[0009] The sales data processing device of this embodiment provides a sales processing system that facilitates shopping at stores using a mobile terminal. [Brief explanation of the drawing]

[0010] [Figure 1] This is an example of a schematic diagram showing the overall configuration of a sales data processing system according to one embodiment. [Figure 2] This is a diagram showing an example of a POS terminal in a sales data processing system according to one embodiment. [Figure 3] This figure shows data from a sales data processing system according to one embodiment. [Figure 4] This is an example of a store employing a sales data processing system of one embodiment. [Figure 5] This is an example of an implementation example of a sales data processing system according to one embodiment. [Figure 6] This is an example of an implementation example of a sales data processing system according to one embodiment. [Figure 7] This is an example of the introduction of a sales data processing system according to an embodiment. [Figure 8] This is an example of the introduction of a sales data processing system according to an embodiment. [Figure 9] This is an example of the processing flow in a mobile terminal of a sales data processing system according to an embodiment. [Figure 10] This is an example of the processing flow in a POS terminal of a sales data processing system according to an embodiment. [Figure 11] This is an example of the functional block diagram of a sales data processing system according to an embodiment. [Figure 12] This is an example of the screen of a mobile terminal of a sales data processing system according to an embodiment. [Figure 13] This is an example of the screen of a mobile terminal of a sales data processing system according to an embodiment. [Figure 14] This is an example of the screen of a mobile terminal of a sales data processing system according to an embodiment. [Figure 15] This is an example of the screen of a mobile terminal of a sales data processing system according to an embodiment. [Figure 16] This is an example of the screen of a mobile terminal of a sales data processing system according to an embodiment. [Figure 17] This is an example of the screen of a mobile terminal of a sales data processing system according to an embodiment. [Figure 18] This is an example of the screen of a POS terminal of a sales data processing system according to an embodiment. [Figure 19] This is an example of the screen of a POS terminal of a sales data processing system according to an embodiment. [Figure 20] This is an example of the screen of a POS terminal of a sales data processing system according to an embodiment. [Figure 21] This is an example of the screen of a POS terminal of a sales data processing system according to an embodiment. [Figure 22] This is an example of the screen of a POS terminal of a sales data processing system according to an embodiment. [Figure 23] This is an example of the screen of a POS terminal of a sales data processing system according to an embodiment. [Figure 24] This is an example of a POS terminal screen for a sales data processing system according to one embodiment. [Figure 25] This is an example of a block diagram of a sales data processing system according to one embodiment. [Figure 26] This is an example of the image display processing flow on a mobile terminal of a sales data processing system according to one embodiment. [Figure 27] This is an example of the screen of a mobile terminal for a sales data processing system according to one embodiment. [Figure 28] This figure shows an example of data from a sales data processing system according to one embodiment. [Figure 29] This is an example of the image display processing flow on a mobile terminal of a sales data processing system according to one embodiment. [Figure 30] This is an example of a functional block diagram of a sales data processing system according to one embodiment. [Figure 31] This diagram shows the identification of a store in one embodiment. [Figure 32] This diagram shows an example of allowing members to choose their payment method. [Figure 33] This figure shows an example of customer monitoring in a sales data processing system according to one embodiment. [Figure 34] This is an example of a specific store processing flow on a mobile terminal of a sales data processing system according to one embodiment. [Figure 35] This is an example of a settlement processing flow on a mobile terminal of a sales data processing system according to one embodiment. [Figure 36] This is an example of a processing flow related to customer monitoring on a mobile terminal of a sales data processing system according to one embodiment. [Figure 37] This diagram illustrates an example of using a mobile device to obtain the type of bulk product that a member wishes to purchase. [Figure 38] This figure shows an example of a weighing device. [Figure 39] This is a diagram showing the configuration of interconnection between a mobile terminal and a weighing device. [Figure 40]This diagram shows how to obtain the weighed value of products sold by weight. [Figure 41] This is a diagram showing the weighing process. [Figure 42] This diagram shows the display information of the weighing device after the measurement value has been acquired, and how to operate it. [Figure 43] This diagram shows the display information on the weighing device and mobile terminal when weighing is stopped or terminated. [Figure 44] This diagram illustrates the process for canceling registrations of products that are measured by weight. [Figure 45] This diagram illustrates the situation when a settlement process is instructed for items for which weighing data has not been obtained. [Figure 46] This is a flowchart showing the coordinated operation between a mobile device and a weighing device. [Figure 47] This flowchart shows the actions taken when there are registered products for which no weighing data has been obtained. [Figure 48] This flowchart shows the operation of displaying and changing registration information on a mobile device. [Figure 49] This is a flowchart illustrating the manual operation of a weighing device. [Figure 50] This is a flowchart of the operation of a POS terminal. [Modes for carrying out the invention]

[0011] The sales data processing system of this embodiment will be described with reference to the drawings. -Overall configuration of the sales data processing system- One embodiment of the sales data processing system 1, as shown in Figure 1, includes a host device 10 equipped with storage means for storing product master 110, store master 120, member master 130, shopping file 140, etc., and a mobile terminal 20 connected to the host device 10 via the internet or the like.

[0012] The higher-level device 10, for example, uses a cloud server and is linked to a store controller (management device) 60 that builds the store's product sales system 6 via the internet, etc. The product master 110 etc stored in the higher-level device 10 are updated as appropriate, for example, at predetermined intervals, based on the information in the store controller 60.

[0013] The mobile terminal 20 is, for example, a smartphone personally owned by the customer. The mobile terminal 20 is equipped with a camera (input unit) 260 for taking images and a display unit (display input unit) 250 such as a touch panel. The mobile terminal 20 may also be a dedicated mobile terminal for store rentals. The mobile device (smartphone) 20 has the function of a registration device that performs the process of registering products to be purchased when shopping at a store, by installing a dedicated application.

[0014] The mobile terminal 20 can exchange information as needed with the product master 110, store master 120, shopping file 140, etc., stored in the host device 10. It also outputs registered information to a payment device such as a POS terminal 70.

[0015] The store's product sales system 6 includes a store controller 60 and multiple POS terminals (registration and settlement devices) 70, and the POS terminals 70 can register and settle the products purchased by customers.

[0016] The store controller 60 is an information processing device that manages the entire store's product sales system 6, including POS terminals 70 and other devices, as well as various types of information such as product master data and member master data. The store controller 60 retrieves and stores the product master data, which reflects the latest product information, from an external source (for example, a server at headquarters or a removable storage medium). A product master is a file in which product information such as product name (product name, item name), sales price, and discount information is linked to the product identification information (e.g., JAN code) assigned to each product.

[0017] The POS terminal 70 is a device that processes the registration and settlement of products purchased by customers, and has an input unit 760 such as a barcode reader, preset keys, and a CCD camera for reading information about the products purchased by the customer, a display unit 750 such as a touch panel for displaying the information about the products that have been read, and a printing unit 770 for printing receipts, etc. Furthermore, the POS terminal 70 can refer to the shopping file, etc., on the host device 10 as needed, such as when shopping identification information is entered from the mobile terminal 20.

[0018] An example of a POS terminal 70 is a POS terminal dedicated to payment. In this embodiment, customers can register products at the store using their own smartphone (mobile device) 20. Then, by performing the payment process using the POS terminal dedicated to payment, customers can complete the transaction without the intervention of store staff.

[0019] Furthermore, the POS terminal 70 is not limited to a POS terminal solely for payment; it may also be a semi-self-service POS system where a store employee registers the items purchased by the customer, and the customer then performs the payment process themselves. In the case of a semi-self-service POS system, the registration device and the payment device are separate, and the registration information processed by the registration device is output to the payment device, where the customer performs the payment process themselves. Alternatively, it may be a face-to-face POS system with a screen for the store employee to perform the registration process, a screen for the customer to perform the payment process, and a cash processing unit. Furthermore, the POS terminal 70 may be a fully self-service POS system in which customers register and pay for the items they purchase themselves, meaning no store staff are involved.

[0020] Furthermore, the POS terminal 70 may be a switchable POS system that can be switched depending on the congestion level, the number of staff, etc., to switch between a semi-self-service POS where the customer processes the payment themselves, a face-to-face semi-self-service POS, and a fully self-service POS. An example of a switchable POS terminal 70 is shown in Figure 2. The example of the POS terminal 70 shown in Figure 2 includes a table 70a. Furthermore, it may be a standard POS register where a store employee registers and processes the payment for items purchased by a customer, and is not limited in any way as long as it is a device capable of processing payments.

[0021] Furthermore, the sales data processing system 1 of this embodiment can be retrofitted (added on) to, for example, a store's product sales system 6 equipped with a store controller 60 and multiple POS terminals 70, thereby creating a sales data processing system that allows customers to register products using their smartphones at the store.

[0022] The above describes the general configuration of the sales data processing system of this embodiment; however, we will now explain further with some examples. Generally, when a customer purchases goods in a store, they take the items to the cashier, who enters the price of each item into the register. The total price of all items is then calculated, determining the final selling price for the transaction. Furthermore, when determining selling prices in stores, various discounts and other measures are applied to lower prices in an attempt to attract customers.

[0023] Figure 4 shows a system used by supermarkets and other businesses with multiple stores. Typically, in systems for supermarkets and similar businesses, a central system (server) 50 is installed to manage all stores, and this central system 50 manages common product master data, store master data, store-specific product master data, common special sale plan master data, store-specific special sale plan master data, and member master data.

[0024] Each store is equipped with a POS terminal 70 and a store controller 60 that manages the POS terminal 70, thus establishing a POS system. Each store's store controller 60 receives common product master data, store master data, store-specific product master data, common special offer master data, and store-specific special offer master data from the headquarters system 50, and also inputs (registers) this data at the store. Regarding the member master data, it may be received from the headquarters system 50 like the other master data, but the store controller does not need to hold it; instead, it may query the headquarters system each time member information needs to be retrieved.

[0025] Each store's POS system has its own pricing logic. The pricing logic includes several methods for calculating the selling price of a product purchased by a shopper, and also includes a function to determine which logic to apply when calculating the selling price of a product. For example, if a product is eligible for both an individual discount and a set-match discount, the set-match discount, which results in a lower price, will be applied. The choice of which discount logic to use is determined by the system settings.

[0026] Here, we will illustrate and explain several pricing logics used to determine the selling price of a product. First, we will define the standard pricing logic as "Basic Pricing Logic." Additionally, we will define the pricing logic unique to each company or store as "Company / Store Pricing Logic." The basic pricing logic includes features such as subtotal calculation, subtotal discounts, individual item discounts, bundle / mix-match discounts, and set-match discounts. The pricing logic (for businesses and stores) includes, for example, the above-mentioned subtotal (calculation of the total amount), subtotal discounts, individual item discounts, bundle / mix-match discounts, and set-match discounts, as well as discounts for special services for members and discounts for each payment method used. Furthermore, the pricing logic (for businesses and stores) has unique functions, such as determining which discount condition takes priority when multiple discount conditions compete simultaneously. In addition, the pricing logic (for businesses and stores) may also have its own logic for subtotal (calculation of the total amount), subtotal discounts, individual item discounts, bundle / mix-match discounts, and set-match discounts.

[0027] Referring to Figure 3(a), the logic behind the above price determination logic will be explained. The subtotal (Logic A) is the logic used to determine the selling price of the items to be purchased. It calculates the total amount by summing the prices of the latest product information for each item. Subtotal discount (Logic B) is a process that applies a predetermined discount amount or a predetermined percentage discount to the subtotal amount (total amount). Single item discounts (Logic C) are processes that apply special discounts or reductions to specific individual products.

[0028] Bundle mix-and-match discounts (Logic D) are a process that applies a discount or reduction when purchasing several items together from a specific group of products. Set Match Discount (Logic E) is a process that applies a discount or reduction when purchasing a specific combination of products.

[0029] Payment type discount (Logic F) is a process that applies a discount or reduction depending on the payment type used by the member at the time of payment. Membership-based discounts (Logic G) are a process that applies a discount or reduction to specific products or subtotal amounts based on the customer's membership status. The lowest price calculation logic (Logic H) is a process that determines which discount to apply to calculate the lowest price when a product meets multiple discount conditions (multiple logics are applicable).

[0030] Then, at each store, in accordance with the measures requested by the store operator, such as a company, a combination of several logics A through H above is used to set the pricing logic for that store and determine the selling price. It goes without saying that the logic for determining the selling price can be set by the store operator as appropriate, in addition to the logic described above (for example, setting which discount to choose when multiple discounts overlap), and that logic other than logic A through H may be included.

[0031] Next, we will describe the implementation model of the sales data processing system of this embodiment.

[0032] - An example of introducing a new sales data processing system equipped with a basic pricing logic - Figure 5 shows an outline of a model for introducing a sales data processing system that has an independent pricing logic (basic) and is unrelated to the existing pricing logic, such as when opening a new store. In the example shown in Figure 5, the higher-level device 10 of the sales data processing system is configured by the store's store controller, and the mobile terminal 20 communicates directly with the store controller, which is the higher-level device 10. The product master 110 and store master 120 stored in the higher-level device 10 can be created by directly inputting product information and store information using a web browser or the like.

[0033] In this example, the sales decision logic to be adopted at the new store is set in the store controller, allowing for the smooth construction of the sales data processing system. Below is a brief explanation of an example of the processing flow in this case. The numbers in parentheses in the explanation indicate the processing shown in Figure 5.

[0034] In the sales data processing system of this example, (1) when a member carrying a mobile terminal 20 launches an application on the mobile terminal 20, the application acquires GPS information from the mobile terminal 20 and transmits the acquired location information to the host device 10. If location information cannot be acquired, the application may display a QR code (registered trademark) installed at the entrance of the store, etc., on the display unit 250 for the mobile terminal 20 to read, and when the QR code (registered trademark) is read, information for identifying the store that has been converted into a QR code (registered trademark) may be transmitted to the host device 10. Note that the means for acquiring location information is not limited to GPS.

[0035] (2) When the higher-level device 10 receives location information (or information for identifying a store) from the mobile terminal 20, it transmits store information for one or more stores closest to the location of the mobile terminal 20 to the mobile terminal 20, based on the received location information and the information stored in the store master 120. Furthermore, when the higher-level device 10 transmits store information to the mobile terminal 20, it may also transmit customer information (such as the number of points earned and membership rank). Furthermore, the higher-level device 10 may also transmit to the mobile terminal 20 special sale information of the stores used by the member (such as the store name, information on sales and special offers being held at the store, and flyer information containing the store information).

[0036] The mobile terminal 20, upon receiving the store information, displays the received store information on the display unit 250. Alternatively, the system can display multiple received store listings in a selectable format. Members identify the store where they will make their purchase by checking the store displayed on the mobile device 20 and selecting the store if multiple stores are displayed. Once a store is identified, the higher-level device 10 associates the product master data of the identified store with the mobile terminal 20 and generates a shopping file (basket data).

[0037] (3) When a member reads the symbol code information of the product to be purchased at a designated store using the mobile terminal 20, the mobile terminal 20 transmits the read symbol code information (product identification information) to the host device 10. The product identification information includes all methods that can identify the product and be obtained as an image, such as barcodes, object recognition using image features, and character recognition. (4) The host device 10, upon receiving the product identification information, extracts product information from the product master 110 based on the received product identification information and transmits it to the mobile terminal 20. The mobile terminal 20 registers the received product information as a product to be purchased by the member.

[0038] (5) The product information registered by the mobile terminal 20 is transmitted to the host device 10 as registered product information, and the host device 10 stores the received registered product information in a shopping file (basket data). (6) The host device 10 calculates a subtotal for the registered product information stored in the shopping file using the selling price determination logic, and (7) transmits the calculated total amount to the mobile terminal 20. This allows members to view the current total amount (or an estimated amount, in some cases) while shopping.

[0039] (8) When a member finishes shopping, the mobile terminal 20 outputs the shopping identification information to the POS terminal 70 by displaying symbol code information such as a QR code (registered trademark) containing shopping identification information on the display unit 250 and having the input unit 760 of the POS terminal 70 read it. (9) The POS terminal 70 that has entered the shopping identification information requests the host device 10 to provide the shopping information (registered product information, etc.) associated with the shopping identification information.

[0040] (10) The host device 10, having received shopping identification information from the POS terminal 70, extracts the calculated shopping information linked to the shopping identification information from the basket data and transmits it to the POS terminal 70. (11) The POS terminal 70, having received the calculated shopping information, displays a payment screen based on the received shopping information. The member completes a transaction using the mobile terminal 20 by making a payment according to the payment screen. The above explains the processing flow in this example.

[0041] Furthermore, the subtotal calculation using the price determination logic may be performed by the POS terminal 70. In this case, the host device 10 may send (10) uncalculated shopping information related to the shopping identification information to the POS terminal 70 in response to (9) the shopping information request from the POS terminal 70. In addition, the subtotal calculation using the price determination logic may be performed by the mobile terminal 20.

[0042] -An example of introducing a sales data processing system to an existing store (Part 1)- This example demonstrates how, for an existing store shown in Figure 4, accounting can be performed using the pricing logic provided by the sales data processing system, without using the store's own pricing logic. This example illustrates how a sales data processing system equipped with the basic pricing logic can be added to an existing store where the configured pricing logic is the basic pricing logic.

[0043] The example shown in Figure 6 can be constructed by providing a sales data processing system via a cloud service to an existing store as shown in Figure 4, and by having the mobile terminal 20 communicate with a higher-level device 10 located on the cloud service.

[0044] In this example, the price determination logic (basic) set in the higher-level device 10 of the sales data processing system is the same as the selling price determination logic (basic) set in the existing store. Therefore, when determining the selling price based on the registered product information registered by the mobile terminal 20, it is not necessary to use the selling price determination logic of the existing store. Furthermore, the pricing logic set up in existing stores and the pricing logic provided by the sales data processing system are not limited to the basic pricing logic.

[0045] In this example, in order to use the sales data processing system, product information (such as product master data and special sale plan master data) and store information are periodically transmitted via the internet or other means from the existing headquarters system 50 or store controllers located in the stores to the higher-level device 10 provided by the cloud service. It is preferable that only information that is valid on the day is transmitted for the product master data and special sale plan master data.

[0046] Because the higher-level device 10, provided by the cloud service, acquires and stores product information (such as product master data and special sale plan master data) and store information, a sales data processing system can be built simply by adding a POS terminal 70 that performs settlement processing based on the registered information registered by the mobile terminal 20.

[0047] Furthermore, the shopping information in the shopping file 140 located in the cloud service may be periodically transmitted via the internet to the headquarters system 50 or the store controller 60 of the store, or transmitted via the in-store network to the store controller 60, and the transaction history performed by the mobile terminal 20 may be stored.

[0048] The processing flow in this example is the same as that of the newly installed sales data processing system shown in Figure 5, except that the higher-level device 10 is located on a cloud service instead of a store controller and acquires information from the headquarters system 50 or the store controller 60. Therefore, a description of the processing flow will be omitted. Similarly, in the example shown in Figure 6, the subtotal calculation based on the selling price determination logic may also be made executable by the POS terminal 70 or the mobile terminal 20 application. Alternatively, the solution can be implemented by modifying the application of existing POS terminals (payment devices) 70, without adding new POS terminals 70.

[0049] -An example of introducing a sales data processing system to an existing store (Part 2)- The example shown in Figure 7 is an example in which, for example, an existing store as shown in Figure 4 is used to determine the selling price and perform accounting using the selling price determination logic of the store's POS terminal 70, while utilizing the selling price determination logic provided by the sales data processing system. In this example, the settlement amount is determined using the pricing logic (company / store) set up in an existing store. In contrast, the pricing logic (basic) of the sales data processing system can provide an estimated amount to the mobile device during the shopping process.

[0050] In this example, a sales data processing system is provided to an existing store as shown in Figure 4 via a cloud service, and the mobile terminal 20 communicates with a higher-level device 10 located on the cloud service. Furthermore, by modifying the existing point-of-sale (POS) terminal 70 to enable communication with the higher-level device 10 of the sales data processing system, and by introducing an application that supports QR code (registered trademark) reading on the mobile terminal 20, a sales data processing system that supports product registration processing by the mobile terminal 20 can be constructed.

[0051] In the example shown in Figure 7, the price determination logic (basic) set in the higher-level device 10 of the sales data processing system does not correspond to the selling price determination logic (company / store) set in the existing store. Therefore, the mobile terminal 20 cannot display the exact total amount. However, an estimated amount calculated by the price determination logic (basic) set in the higher-level device 10 can be displayed on the display unit 250 of the mobile terminal 20, which can be used as a guide for shopping.

[0052] Furthermore, the pricing logic set up in existing stores and the pricing logic provided by the sales data processing system are not limited to the pricing logic (company / store) and pricing logic (basic).

[0053] The processing flow in this example is the same as the newly installed sales data processing system shown in Figure 4 above, except that in (6), the price determination logic that calculates the subtotal is different from the store's price determination logic, the total amount transmitted in (7) is an estimated amount, and the POS terminal 70 in (8), (9), (10), and (11) is an existing POS terminal located in a store. Therefore, the explanation of the processing flow is omitted.

[0054] -An example of introducing a sales data processing system to an existing store (Part 3)- The example shown in Figure 8 is an example in which, for example, an existing store as shown in Figure 4 has a subtotal service that determines the selling price based on the store's selling price determination logic (company / store), while accounting is performed using a newly installed POS terminal 70 instead of the existing POS terminal. According to this example, for instance, when a different POS terminal is delivered from the POS terminal 70 that settles the transaction using the pricing logic (company / store) set up in an existing store, it becomes unnecessary to retrieve the program from that POS terminal.

[0055] In this example, a sales data processing system is provided to an existing store as shown in Figure 3 via a cloud service, and the mobile terminal 20 communicates with a higher-level device 10 located on the cloud service. Furthermore, by providing the higher-level device (cloud service) 10 with a basket linkage function that transfers shopping information stored in the shopping file to subtotal services such as the headquarters system (server) and store controller, as well as a function that updates the information in the shopping file based on the results calculated by the subtotal service, a sales data processing system that supports product registration processing by the mobile terminal 20 can be constructed. In addition, a function to perform data conversion when transferring information can be added as needed.

[0056] In the example shown in Figure 8, subtotal calculation is performed by a subtotal service such as the existing store's headquarters system, eliminating the need to determine the selling price using the existing POS terminal 70's pricing logic. This allows for accounting using the new POS terminal 70 even without a network connection to the existing POS terminal 70. Furthermore, sales performance data can be managed by transmitting it to the headquarters system (server) 50, the store controller 60, and the higher-level device (cloud service) 10.

[0057] In this example as well, the price determination logic (basic) set in the higher-level device 10 of the sales data processing system does not correspond to the selling price determination logic (company / store) set in the existing store. Therefore, the mobile terminal 20 cannot display the exact total amount. However, an estimated amount calculated by the price determination logic (basic) set in the higher-level device 10 can be displayed on the display unit 250 of the mobile terminal 20, which can be used as a guide for shopping.

[0058] Furthermore, the pricing logic set up in existing stores and the pricing logic provided by the sales data processing system are not limited to the pricing logic (company / store) and pricing logic (basic).

[0059] Below is a brief explanation of an example of the processing flow in this case. The numbers in parentheses in the explanation indicate the processing shown in Figure 8.

[0060] In the sales data processing system of this example, steps (1) to (5) are the same as those shown in Figure 4 (1) to (5), so they are omitted.

[0061] (6) The host device 10 performs an approximate calculation based on the registered product information stored in the shopping file using the basic selling price determination logic, and (7) transmits the calculated approximate amount to the mobile terminal 20. This allows members to view the current estimated total amount while shopping.

[0062] (8) When a member finishes shopping, the mobile terminal 20 outputs the shopping information to the POS terminal 70 by displaying symbol code information such as a QR code (registered trademark) containing shopping identification information on the display unit 250 and having the input unit 760 of the POS terminal 70 read it. (9) The POS terminal 70 that has entered the shopping identification information transmits the shopping identification information to the host device 10 and requests the shopping information (registered product information, etc.) associated with the shopping identification information.

[0063] (10) The host device 10, having received the shopping identification information from the POS terminal 70, passes the shopping information linked to the shopping identification information to a subtotal service such as the headquarters system 50. (11) The headquarters system 50, upon receiving the shopping information, calculates the total amount using the subtotal service and transmits the calculated shopping information (subtotal information) to the host device 10.

[0064] Upon receiving the calculated shopping information (subtotal information), the host device 10 updates the shopping information stored in the shopping file with the calculated shopping information and transmits the calculated shopping information to the POS terminal 70. (13) The POS terminal 70, having received the calculated shopping information, displays a payment screen based on the received shopping information. The member completes a transaction using the mobile terminal 20 by making a payment according to the payment screen. The above explains the processing flow in this example.

[0065] As described above, the form of the sales data processing system in the present invention is not limited in any way. That is, a system consisting of a higher-level device 10 and a mobile terminal 20 that can be later linked to a store's product sales system, an overall system in which the higher-level device 10 and the mobile terminal 20 are linked to a store's product sales system, a system in which the higher-level device 10 is configured as a store controller 60 of the store's product sales system and the mobile terminal 20 is directly linked to the store controller 60 or an in-store POS terminal 70, etc., a system that conducts product transactions based on product information registered by the mobile terminal 20 can be the sales data processing system in the present invention.

[0066] Furthermore, the following description describes an embodiment in which product registration processing is performed using the mobile terminal 20. This is just one example, and the mobile terminal 20 may function merely as an interface for product registration processing, with other processing being performed by a higher-level system such as the higher-level device 10. In other words, which devices constituting the sales data processing system perform which processing can be set as appropriate.

[0067] -Higher-level device 10- The host device 10 of the sales data processing system 1 in this embodiment is equipped with storage means for storing product master 110, store master 120, member master 130, shopping file 140, etc. The product master 110, store master 120, etc. in the host device 10 are updated based on the information of each master stored in the store controller 60 of the store.

[0068] The product master 110 stores product information, store identification information, etc., linked to product identification information unique to each product. For example, the information stored in the product master can be used to identify product information from product identification information, or to identify product information handled at a store from store identification information. Note that the information stored in the product master 110 is not limited to the above-mentioned product information and store identification information.

[0069] Furthermore, in the sales data processing system of this embodiment, the product master 110 stores product identification information linked to sales conditions (specification numbers), for example, as shown in Figure 28(a). Furthermore, as shown in Figure 28(b), the product master 110 stores a special sale table that links the sales conditions (standard number) with discount type information, the identification number of the target product, the conditions for the discount to be valid, and the discount value when the conditions are met. Sales conditions are those set for each product, and include, for example, bulk discount information such as a discount price applied when purchasing multiple loose items of vegetables together, quantity limit information such as a set number of items per customer, and information indicating that the contents and price vary from pack to pack, such as packaged meat with a set price per gram. Note that the above bulk discount information is not limited to loose items of vegetables, but can also be set for products such as canned goods and instant noodles. Furthermore, the information stored in the product master 110 is not limited to the above-mentioned product information, store identification information, and sales conditions.

[0070] As shown in Figure 3(b), the store master 120 stores store identification information, store name, location information such as GPS information of the store, and QR code (registered trademark) information that identifies the store, all linked together. Based on the information stored in the store master 120, it is possible to identify nearby stores, for example, from location information.

[0071] As shown in Figure 3(c), the member master 130 stores member identification information and member information such as member name (name, address, credit card number, etc.) linked together. Based on the information stored in the member master 130, it is possible to identify, for example, the store information and credit card information used by a member from the member identification information.

[0072] Furthermore, the member master 130 may store information such as the number of times a member has previously used the mobile terminal 20 to register products, the number of times they have deleted (canceled) registered products during product registration, and other error operations, linked to the member identification information. It may also store the member's level, which is determined by the frequency (number of uses) and frequency (number of errors). For example, the higher-level device 10 sets member levels ranging from beginner level (L1) to premium member (L5), and tracks the frequency (number of times) of product registration and the frequency of errors using the mobile terminal 20. The member level may be determined based on (number of times used), etc., and stored in the member master 130.

[0073] As shown in Figure 3(d), the shopping file 140 is a file that stores registration information registered by the member using the mobile terminal 20 when making a purchase. It stores shopping information linked to shopping identification information that identifies the member's purchase and registered product information (barcode information, product name, price, etc.) registered for that purchase. The shopping identification information may consist of, for example, a combination of store identification information, date, and serial number.

[0074] Furthermore, the shopping file 140 may store shopping identification information linked to pending product information for products that could not be registered using the mobile terminal 20 during the shopping process, and may also store information related to cancellation operations performed by the member during the product registration process.

[0075] The shopping information stored in the shopping file 140 is synchronized with the product registration information on the mobile terminal 20. When a member changes or deletes the quantity of registered information registered on the mobile terminal 20 while shopping, the shopping information in the shopping file 140 is also changed or deleted accordingly. Furthermore, at the time of settlement, the member outputs shopping identification information from the mobile terminal 20 to the POS terminal 70, and the POS terminal 70 requests the registration information, etc., associated with the shopping identification information from the shopping file 140 of the host device 10. The higher-level device 10, upon receiving a request for registration information, outputs product information linked to the shopping identification information to the POS terminal 70.

[0076] When the settlement process for a transaction is completed, the host device 10 stores the shopping information for that transaction as settled shopping information in the shopping file 140. Members can access the shopping file 140 using their mobile terminal 20 to refer to their past shopping history. Furthermore, the shopping file 140 is synchronized with the shopping file stored in the store controller 60 of the store, and may also store shopping information made by members without using the mobile terminal 20. In this way, members can refer to their entire past shopping history at the store.

[0077] Additionally, the shopping file 140 may store past history and currently registered files in separate memory areas. It may also be configured so that when a current purchase is confirmed, it is added to the past history file.

[0078] Furthermore, the higher-level device 10 supplies an application program (shopping app) that runs on the mobile terminal 20. The shopping app may also be provided from an internet site that provides applications for the mobile terminal 20.

[0079] -Mobile device 20- The mobile terminal 20 of the sales data processing system 1 of this embodiment will be explained with reference to the flowchart shown in Figure 10 and the screen display examples shown in Figures 12 to 15. For the mobile terminal 20, we will explain using as an example a smartphone personally owned by the customer with a dedicated application supplied by the higher-level device 10 installed.

[0080] (Preparation) In order for a customer to use their smartphone as a mobile terminal 20 capable of processing store registrations, the customer must register as a member (hereinafter referred to as "member") who can process registrations using their smartphone.

[0081] When registering a new member, it is preferable to register information that can verify the member's identity, such as their name, address, telephone number, and email address, as well as their credit card information. The registration procedure can be done online or offline. For example, the member may enter the necessary information on a registration form or tablet at a store, and a download URL will be sent to the registered email address to download a dedicated app. Alternatively, the member may download and install a dedicated app from the host device 10, then access the member registration screen to complete the registration process. The application may also be provided from a website on the internet that offers applications for the mobile terminal 20.

[0082] Furthermore, if a customer is already a cardholder of the store, the registration process may be completed by simply adding, for example, their credit card information. Please note that the information to be registered is not limited to the information listed above. For example, if a store is part of a chain, it may register information about the store that is regularly used so that information specific to that store is delivered. The higher-level device 10 stores the registered member information in the member master 130.

[0083] Furthermore, the operation history data from member master 130 may be used at stores other than the one in question. In other words, the conditions and thresholds for displaying the confirmation screen by the store clerk at the payment terminal, based on the member's usage level as determined by their operation history, can be used at stores other than the one in question. Furthermore, considering that the mechanism of the higher-level device 10 may be used by multiple companies, it is preferable to utilize it by multiple companies beyond the company group in question, provided that its use is limited to security aspects related to operation history. Regarding security levels, each company group and each store can set their own levels, and the ranking settings for member levels and operation levels, as well as the conditions for triggering employee verification events, can be freely configured. These conditions can also be stored on the payment device side, received when acquiring the shopping file (basket data), and the payment device can control the triggering of employee verification events.

[0084] (Store identification processing) When a member launches a dedicated application on the mobile terminal 20, the mobile terminal 20 performs a process to identify the store in order to function as a registration device at the store (S201).

[0085] For example, when a member launches a dedicated app on the mobile terminal 20, the mobile terminal 20 may identify a store based on location information obtained from the mobile terminal 20's GPS, etc. Specifically, the mobile terminal 20 can transmit location information to the host device 10, and the host device 10, upon receiving the location information, can identify the store where the member will make a purchase by transmitting information about the nearest store to the mobile terminal 20 based on the store master 120. If there are multiple stores that meet the criteria, a selection screen may be displayed on the display unit 250 so that members can choose from among the multiple stores.

[0086] Alternatively, a QR code (registered trademark) containing QR code (registered trademark) information stored in the store master 120 may be attached to the entrance of the store, and when a member reads the QR code (registered trademark) with the input unit 260 of the mobile terminal 20, the mobile terminal 20 may identify the store. This method is effective when location information cannot be obtained, and when location information cannot be obtained, the display screen of the mobile terminal 20 may display a message such as "Please scan the store's QR code (registered trademark)." Alternatively, when a member enters the store, the store may be identified using in-store Wi-Fi, Bluetooth (registered trademark), beacons, or other short-range wireless communication. In other words, the means of identifying location information are not limited in any way.

[0087] Once a store is identified, the higher-level device 10 grants the mobile terminal 20 access to the store's product master data and generates basket data (shopping file) linked to the mobile terminal 20.

[0088] Alternatively, the mobile terminal 20 may display a selection screen on its display unit 250 for selecting a store, and the member may select a store from the selection screen, thereby identifying the selected store as the store where they will make their purchase. The mobile terminal 20 may also notify members of information such as "special sale information," "related / alternative products," "new products," and "out-of-stock information" at the store when they enter the store. Furthermore, if the specified store is closed for a regular holiday or other reason, this may be displayed on the display unit 250. In addition, if the store is closed, transitioning to the registration screen may be prohibited. Registration via the app may be prohibited for a predetermined time before closing, and customers who are in the process of registering may be notified of the closing time. However, customers who are in the process of registering may continue shopping, and registration does not have to be prohibited even when closing time arrives. Continued shopping is permitted within the range of the store's location. Notifications prompting payment in stages may also be provided.

[0089] When the mobile terminal 20 identifies a store, it displays a start screen 800 (Figure 12(a)) on the display unit 250 to begin shopping. The start screen 800 contains keys linked to member point information 800a, store information 800b for a specified store, special sale information and other notifications 800c, coupon information 800d, etc., as well as a "start" key 800e that declares the start of product registration at the store.

[0090] Then, when the member operates the "Start" key 800e on the start screen 800, the mobile terminal 20 displays the registration screen 810 shown in Figure 12(b). Furthermore, the mobile terminal 20 may immediately display the registration screen 810 without displaying the start screen 800 by identifying a store.

[0091] The registration screen 810 shown in Figure 12(b) is divided into two areas, upper and lower. The upper area of ​​the registration screen 810 is set as a first display area 811 that displays the image data captured by the camera (input unit) 260 of the mobile terminal 20. The mobile terminal 20 displays the message "Please scan the product barcode" 811a in the first display area 811 of the registration screen 810, and also displays a visible indicator 811b that shows the reading range for recognizing the barcode (product identification information), thereby completing the preparation for product registration.

[0092] (Read operation detection process and product information acquisition process) When a member performs an operation to read the code information attached to the product (S202), the mobile terminal 20 obtains product identification information from the read code information, etc. (S203). In step S202, the mobile terminal 20 detects that a reading operation has been performed by a customer or the like to read the code information.

[0093] When a member takes an item from the display shelf and places it in a shopping basket, the input unit 260 of the mobile terminal 20 captures an image of the item. As shown in Figure 13(a), by placing the barcode (code information) attached to the item within the marker 811b displayed in the first display area 811 of the registration screen 810, the mobile terminal 20 automatically recognizes that it is a barcode (item identification information) and retrieves the item identification information stored in the code information.

[0094] In this case, if the mobile terminal 20 is equipped with a distance sensor or the like, it can detect when the input unit 260 of the mobile terminal 20 has been close to an item for a certain period of time, thereby detecting that a member has performed a code information reading operation. Alternatively, if the mobile terminal 20 is constantly and automatically repeating barcode recognition and is not equipped with a distance sensor or the like, it may be possible to detect when a member has performed a code information reading operation by detecting, for example, that the same image has been captured for a predetermined period of time. Similarly, if these detections are made for a certain period of time, a timeout process may be executed, and a notification such as "Product registration failed. Do you want to purchase it? (Yes / No)" may be issued, prompting the user to place the item on hold. Purchase confirmation can also be performed.

[0095] Furthermore, the mobile terminal 20 may not automatically recognize barcodes or other code information, but instead read product identification information from code information captured by shutter operation or other means while the app is running. In this case, the operation to acquire code information can be detected by detecting that the shutter operation has been performed on the app screen. Alternatively, the system may use a gyroscope or similar sensor to monitor the tilt and other states of the mobile device, and determine that a reading operation is being performed. Specifically, detection can be performed by combining a predetermined distance and tilt relative to the product.

[0096] If the product's barcode (product identification information) cannot be recognized during the initial scanning, the member may set that product aside as a pending item and proceed with registering the next product. In this case, the member should simply scan the pending item and save the image. By allowing members to save images of items they have put on hold, it becomes easier to identify the items during the subsequent checkout process, and it also makes it easier for store staff to correct the product registration information. Specifically, there may be cases where the process prompting the customer to mark an item as "hold" is not executed, similar to the timeout process described above. In such cases, the customer will have to keep trying to register the item, which is inconvenient. In such cases, it may be possible to allow the customer to register the item as "hold" rather than registering it normally. In this case, for example, a "Hold Item Registration" button could be displayed on the registration screen or settings screen, and pressing this button would switch to a manual shutter capture mode. In this capture mode, the customer could take a picture of the front of the package of the item that could not be registered, its barcode, or the price tag on the shelf at their own timing, and then count it as a hold item. In other words, it may be possible to switch to manual shutter capture mode at the customer's discretion.

[0097] Furthermore, there are no particular limitations on the method for detecting the operation of reading product identification information.

[0098] If, in step S202, the mobile terminal 20 detects a reading operation by a member, but in step S203, it fails to obtain product identification information, it determines that the registration of product information has failed (resulting in "no" in S204).

[0099] For example, some products may have barcodes that are damaged or distorted due to packaging, making it impossible to read some or all of the information recorded on the barcode (unreadable products). Additionally, members may sometimes photograph parts of the product that do not have a barcode. In such cases, product identification information cannot be obtained by reading the code. Consequently, product registration becomes impossible. Step S204 detects cases where product registration is not possible due to the inability to read the above code information.

[0100] Furthermore, if the mobile terminal 20 detects a reading operation by the customer in step S202 and obtains product identification information in step S203, it checks whether the product identification information exists in the product master 110. If the read product identification information does not exist in the product master, it determines that the registration of product information has failed (no in S205).

[0101] For example, if product identification information recorded in the code information is acquired and sent to the higher-level device 10, but the acquired product identification information is not stored in the product master 110 (non-file product), or if there is a problem connecting to the higher-level device 10, then product information cannot be acquired from the higher-level device 10. As a result, the product cannot be registered. Step S205 detects cases where product registration is not possible due to the product being a Non-file product or similar.

[0102] Furthermore, if the mobile terminal 20 is constantly and automatically repeating barcode recognition and does not have a function to detect reading operations such as a distance sensor, the steps S202 and S204 for detecting the member's reading operation, i.e., the detection process for when product registration is not possible due to the inability to read the code information, may be omitted.

[0103] (Product registration process, product cancellation process) In step S205, if the acquired product identification information exists in the product master and product information linked to the product identification information can be obtained, the mobile terminal 20 registers it as registered product information for the product to be purchased by the customer. The registered product information registered on the mobile terminal 20 is also stored in the shopping file 140 (S206). Furthermore, while product information can be obtained by referring to the product master 110 stored in the higher-level device 10, if the mobile terminal 20 downloads the product master after identifying a store, it is also possible to obtain product information and register the product using only the mobile terminal 20. Alternatively, the product master to be referenced may be the product master stored in the store controller 60 or the POS terminal 70.

[0104] (Display processing) When the mobile terminal 20 registers a product, as shown in Figure 13(a), a second display area 812 that displays the registered product information and a third display area 813 that displays the current registration status are displayed in the lower area of ​​the registration screen 810 (S209).

[0105] The mobile terminal 20 displays product information such as the product name 812a, the purchase quantity (operator) 812b, and the price of the product 812c in the second display area 812, and displays the current number of registered items 813a, the estimated total 813b, and the "accounting" key 813c for proceeding with accounting processing based on the registered information in the third display area 813.

[0106] Furthermore, the mobile terminal 20 positions the third display area 813 above the second display area 812, that is, between the first display area 811 and the second display area 812. This allows members to easily see the changes in the estimated total when registering products. Furthermore, as shown in Figure 12(b), the mobile terminal 20 may display the third display area 813 with the registration points set to 0 and the estimated total to 0 yen prior to product registration.

[0107] The third display area 813 may be arranged independently of the first display area 811 and the second display area 812, or it may be arranged within the range of the second display area 812. Furthermore, while it is preferable that the estimated total displayed in the third display area 813 shows the exact total amount of the current sales prices of the products, in cases such as when a sales data processing system is introduced to an existing store with a complex pricing logic, accurate subtotal calculations cannot be performed by the store's pricing logic unless the registered product information is output to the existing POS terminal or other settlement device 70. In such cases, an estimated total calculated by summing the list prices of each product may be displayed in the third display area 813 of the mobile terminal 20. By displaying a third display area 813 on the registration screen 810 of the mobile terminal 20, members can keep track of the current number of items purchased and the estimated total while registering products. In this embodiment, the mobile terminal 20 displays a third display area 813 above the second display area 812, that is, between the first display area 811 and the second display area 812. This allows members to easily see the changes in the estimated total when registering products.

[0108] Furthermore, members can change the purchase quantity 812b of the product displayed in the second display area 812, or delete the registered product information for the product. For example, when a member touches the purchase quantity 812b portion displayed in the second display area 812, the mobile terminal 20 displays a quantity change screen (pop-up) 820 to change the quantity of the product, as shown in Figure 14(a).

[0109] The quantity change screen 820 displays the current number of items purchased and the price, and includes "+" keys 820a and "-" keys 820b to change the quantity of an item, as well as a "cancel item" key 820c to delete registered item information. Furthermore, if the registered product is a clearance item or a product with a limited quantity or variable weight, the mobile terminal 20 may display a pop-up 821 without the "+" key 820a and "-" key 820b for changing the quantity of the product, as shown in Figure 14(b).

[0110] Then, if a member changes the quantity or other information of the registered product displayed on the registration screen 810 by operating the "+" key 820a or "-" key 820b, the mobile terminal 20 changes the purchase quantity 812b of the product displayed on the registration screen 810. The mobile terminal 20 then outputs the changed registered product information to the host device 10, and the host device 10 updates the registration information stored in the shopping file 140 with the entered registered product information.

[0111] Furthermore, if a member deletes the registered product information displayed on the registration screen 810 by operating the "cancel product" key 820c, the mobile terminal 20 cancels the registration of the registered product information displayed on the registration screen 810. The mobile terminal 20 then outputs the deleted registered product information to the host device 10, and the host device 10 updates the registration information stored in the shopping file 140.

[0112] Furthermore, if a member cancels their registered product information, we may notify them to return the product to the display shelf or similar location. Furthermore, if the member's location within the store can be identified, the system may detect whether the product whose registration information has been canceled is more than a certain distance away from the shelf where it should be returned, and display a screen allowing the member to choose between returning the product to the shelf or moving it to the holding basket.

[0113] Furthermore, if a member cancels the registration of a product, the mobile terminal 20 may store the product information of the deleted product as canceled product information, linked to information indicating that a cancellation operation was performed. In particular, it is preferable to store the canceled product information when a product whose registration information has been canceled is moved to the pending cart.

[0114] Furthermore, the mobile terminal 20 may delete the registered product information that has been canceled so that it is not displayed on the registration screen 810, or it may display on the registration screen 810 such that it is clear that the product has been canceled, such as by drawing a strikethrough line through it or by adding a note that it is a canceled product.

[0115] Furthermore, the mobile terminal 20 may output information to the host device 10 indicating that a cancellation operation has been performed by the member, and the host device 10 may store this cancellation operation information in the shopping file 140. Furthermore, the higher-level device 10 may store in the member master 130 the number of times the member canceled registered product information during the purchase after the settlement process for the purchase has been completed.

[0116] (Notification processing) If, in step S204, it is determined that the product cannot be registered because it is an unreadable product, or if, in step S205, it is determined that the product cannot be registered because it is a non-file product or the like, the mobile terminal 20 notifies the member that the product cannot be registered (S207).

[0117] For example, the mobile terminal 20 displays a notification (pop-up) 830 on its display unit 250 indicating that items that cannot be registered will be put on hold, as shown in Figure 13(b). At this time, the terminal may also display a notification 830a prompting the user to place items that were successfully registered and items that could not be registered into separate baskets (or specific areas within the baskets), indicating that the two items will be handled differently. Notification that the above-mentioned product cannot be registered is not limited to pop-up messages or other notifications.

[0118] Furthermore, if the reserved item is an unreadable item and the item's code information is displayed on the shelf where the item is displayed, the mobile terminal 20 may notify the user to read the code information attached to the shelf.

[0119] (Generating information on reserved items) The mobile terminal 20 generates pending product information for products that cannot be registered (S208). The pending product information includes, for example, member identification information, shopping identification information, reading time, etc. Preferably, it also stores information on whether the pending product is a non-file product or an unreadable product, and it may also store the image data when the code information was captured.

[0120] (Display processing) The mobile terminal 20 that generated the reserved product information stores the generated reserved product information and, as shown in Figure 15(a), displays reserved product information 812e in the second display area 812 of the registration screen 810, indicating that there are reserved products in addition to the registered product information 812d (S209). Furthermore, it is preferable that the pending product information 812e displayed in the second display area 812 be displayed in a different format than the registered product information 812d. In the example shown in Figure 15(a), the mobile terminal 20 displays two registered product information items 812d together with the pending product information item 812e, and the background color of the pending product information item 812e is different from the background color of the other registered product information item 812d.

[0121] Furthermore, the mobile terminal 20 may display the number of reserved items in the display field 812g in the second display area 812, and also display a message 812f in the reserved item information 812e prompting the member to perform a different procedure than for regular registered items, such as "Please put it in the dedicated basket," thereby informing the member that reserved items exist and that reserved items will be handled differently. Furthermore, when displaying the information, it is preferable to also indicate whether the reserved item is a "non-file item" or an "unreadable item." This display allows store staff to provide customers with more prompt service.

[0122] Furthermore, it is preferable that the reserved product information 812e displayed in the second display area 812 can be modified in the same way as regular products, including changing the quantity or deleting it. For example, if a member repeatedly attempts to read code information for a product that cannot be registered, multiple pending product information entries 812e may be generated. In such cases, the mobile terminal 20 may delete the pending product information entries 812e in response to the member's actions. Furthermore, the mobile terminal 20 may output information regarding reserved items and information regarding the cancellation of reserved items to the host device 10, similar to the registered item information. The higher-level device 10 may also store the entered pending product information, etc., in the shopping file 140.

[0123] (Output of registration information) The mobile terminal 20 displaying the registration information proceeds to step S210 to detect whether the member has given instructions to proceed to checkout. If the member has given instructions to proceed to checkout (Yes in S210), it outputs the instructions to proceed to checkout or the registration information along with the instructions to proceed to checkout (S211), and completes the process. Here, the registration information output by the mobile terminal 20 may also be shopping identification information. Furthermore, the registration information may include registered product information for products that have been successfully registered, pending product information for products that could not be registered, and may also include canceled product information for products whose registration has been cancelled.

[0124] Specifically, the mobile terminal 20 detects when the member has operated the "Checkout" key 813c displayed on the registration screen 810 of the display unit 250. When it is detected that the "Checkout" key 813c has been operated, the mobile terminal 20 displays (outputs) a QR code (registered trademark) 840a, for example, generated based on shopping identification information, on the output screen 840, as shown in Figure 15(b) (S211). The mobile terminal 20 may also display (output) a QR code (registered trademark) 840a, generated based on registration information stored in the shopping file, on the output screen 840.

[0125] By having the member scan the QR code (registered trademark) 840a displayed on the display unit 250 of the mobile terminal 20 with the input unit 760 of the POS terminal 70, the POS terminal 70 can obtain registration information linked to the shopping identification information from the host device 10.

[0126] Furthermore, while symbol code information such as QR codes (registered trademarks) may store registration information including registered product information and owned product information, it may also store shopping identification information linked to the registration information including the registered product information and owned product information. For example, shopping identification information may be path information such as a URL stored in the shopping file, or it may be a combination of information such as a store identifier, member identifier, date and time, or it may be identifiable by a sequence number, etc., as long as the search destination of the shopping information is known on the payment device side.

[0127] Alternatively, instead of outputting symbol code information containing the registered information, the mobile terminal 20 may select a POS terminal 70 so that the selected POS terminal 70 can retrieve the registered information stored in a location other than the mobile terminal 20. For example, a member may have their mobile device 20 read a QR code (registered trademark) that identifies a specific POS terminal 70, which is generated on the screen of the POS terminal 70. The mobile device 20 then transmits payment instructions along with shopping identification information to the specific POS terminal 70. The POS terminal 70, upon receiving the payment instructions, may then retrieve registration information linked to the shopping identification information. Alternatively, you can obtain registration information using an IC reader by setting the Felica® or NFC identifier on your mobile device in advance.

[0128] On the other hand, if the customer does not instruct the system to proceed to checkout (No in S210) and performs operations such as reading code information for other products, the product registration process from steps S202 to S208 is repeated until the customer instructs the system to proceed to checkout. The above explains the processing flow in the mobile device 20.

[0129] -POS terminal 70- Next, the POS terminal (payment device) 70 of the sales data processing system 1 of this embodiment will be explained with reference to the flowchart shown in Figure 8 and the display examples shown in Figures 18 to 24.

[0130] (Input processing) The POS terminal (payment device) 70 receives the registration information (shopping identification information, etc.) output by the mobile terminal 20, etc. (S701).

[0131] For example, when a member displays (outputs) a QR code (registered trademark) 840a on the display unit 250 of the mobile terminal 20, and the input unit 760 of the POS terminal 70 reads it, the POS terminal 70 inputs the registration information (shopping identification information, etc.) stored in the QR code (registered trademark) 840a.

[0132] (Notification processing) The POS terminal 70, which has entered registration information (such as shopping identification information), requests shopping information linked to the shopping identification information from the host device 10, and determines whether the shopping information (registration information) sent from the host device 10 contains information about reserved items or canceled items (S702). If the POS terminal 70 determines that the registration information contains information about reserved items, it sends a notification to call a store employee (S703).

[0133] For example, the POS terminal 70 will notify the customer to call a store employee by flashing a light (Patlite® registered trademark) or the like, which provides visual notification from the POS terminal. The notification method is not limited to Patlite®, but may be any method, such as in-store announcements, notifications to POS registers where store employees are stationed or to monitoring devices that monitor the status of all POSs, notifications to management devices located in the back room, notifications to handheld devices carried by store employees, etc. Then, as shown in Figure 18, the POS terminal 70 displays a pop-up 910 on the display unit 750 indicating that there is a reserved item among the registered items and that a store employee is being called.

[0134] Furthermore, the POS terminal 70 may also issue a notification to call a store employee if it determines that the registration information includes information about canceled products (S703). In other words, in step S702 above, if the POS terminal 70 has reserved product information or canceled product information stored in the registration information, it may notify the store staff to call. It goes without saying that the notification system for calling a store employee may be controlled based on the detection of any of the above.

[0135] (Settlement process) On the other hand, if the POS terminal 70 determines in step S702 that the registration information does not include pending product information or canceled product information, it proceeds to the settlement process. Specifically, the POS terminal 70 displays the registration confirmation screen 900 on the display unit 750, as shown in Figure 19 (S709).

[0136] The registration confirmation screen 900 shown in Figure 19 displays a list of registered product information 900a, and an arrow 900c is displayed at a designated location on the registration confirmation screen 900. Members can scroll through the display of the list of registered product information 900a by operating the arrow 900c. Furthermore, above the registration confirmation screen 900, there is a total display field that shows the number of items purchased and the total amount for that purchase, and the "Checkout" key 900b is also displayed.

[0137] Furthermore, below the registration confirmation screen 900, there is a price range registration quantity display 900d that shows the number of registered items for each price range. In the example shown in Figure 19, the numbers "3", "4", "9", and "12" are displayed for the price ranges of "1,000 yen or more", "500 yen to 999 yen", "300 yen to 499 yen", and "300 yen or less", respectively, which represent the number of items for each range. By displaying the registered quantity for each price range, store staff can get an overview of the products that members have purchased. Furthermore, when high-value items are purchased, the store may notify the light (Patlite®), other devices (monitoring devices), service manager, etc., and store staff may assist with packaging high-value items.

[0138] Then, when the member operates the "Checkout" key 900b displayed on the registration confirmation screen 900, the POS terminal 70 executes the settlement process based on the registration information displayed on the registration confirmation screen 900 (S709), and completes the transaction.

[0139] (Display processing of registered product information and pending product information) Meanwhile, when the member presses the "OK" key 910a on the pop-up 910 of the POS terminal 70 that performed the notification process in step S703, the terminal displays a registration confirmation screen 920 on the display unit 750, which shows a list of the entered registration information (registered product information and held product information) (S704).

[0140] In the example of the registration confirmation screen 920 shown in Figure 20, a list of registered product information 920a is displayed, along with the pending product information 920b and 920c for two items that could not be registered, and the canceled product information 920d for one item whose registration was canceled. At this time, the POS terminal 70 displays the registration confirmation screen 920, which includes the registered product information 920a, the held product information 920b, 920c, and the canceled product information 920d shown in Figure 20, in a different display format than the registration confirmation screen 900, which is displayed using only the registered product information shown in Figure 19. For example, the background color or other screen colors of the registration confirmation screen 920, which includes the held product information 920b, 920c, and the canceled product information 920d, may be changed, or the text color or font may be changed.

[0141] Furthermore, it is preferable that the POS terminal 70 places the pending product information 920b, 920c and the canceled product information 920d at the beginning of the list of registered information 920a. Note that the display of the held product information 920b, 920c and the canceled product information 920d is not limited to the example shown in Figure 20. For example, the POS terminal 70 may display the held product information 920b, 920c and the canceled product information 920d in the left area of ​​the registration confirmation screen 920, and the registered product information 920a in the right area. These displays allow members or store staff to easily identify any reserved or canceled items among the products displayed in the list.

[0142] In addition, the POS terminal 70 displays a price range registration count display 900d at the bottom of the screen, which shows the number of registered items by price range, as well as a field 920e that displays the number of items on hold (including canceled items). In the example shown in Figure 20, "3" is displayed as the number of items on hold. Furthermore, for alcoholic beverages requiring age verification and Category 2 pharmaceuticals requiring explanation by a registered salesperson or pharmacist, including reserved items, the quantity may be displayed, or a separate display area may be provided. In this case, the display method may be changed for the target products, such as background color, font, and size, or marks may be added.

[0143] (Prohibition) If the POS terminal 70 has entered registration information that includes held item information 920b, 920c and canceled item information 920d, it will, following step S704, prohibit settlement processing using the registration information that includes held item information 920b, 920c and canceled item information 920d (S705).

[0144] For example, as shown in Figure 20, the POS terminal 70 prohibits the execution of the settlement process by not displaying the "Checkout" key 900b, which is normally displayed on the registration confirmation screen 900, on the registration confirmation screen 920 that includes pending product information 920b, 920c or canceled product information 920d.

[0145] (Editing process) POS terminal 70, which has been prohibited from executing the settlement process, modifies the held product information in response to the store clerk's modification operation (S706).

[0146] For example, when a store employee touches the reserved product information 920b on the registration confirmation screen 920 displayed on the display unit 750 of the POS terminal 70, an editing screen 930 for editing the reserved product information 920b is displayed on the display unit 750, as shown in Figure 21. Note that the editing screen 930 is not limited to the example shown in Figure 21. Alternatively, the editing screen 930 may be displayed as a pop-up, appearing in a portion of the registration confirmation screen 920 (for example, the left portion).

[0147] The editing screen 930 has a scan button 930a located in a designated position. When a store employee operates the scan button 930a, the POS terminal 70 displays the image data obtained when reading the product code information. The store staff can check the held items by looking at the displayed image data, and can then go to the display shelf to check the price of the items and obtain the correct product information. Editing on the editing screen 930 can be done in any way appropriate.

[0148] Furthermore, if all pending items are displayed in a list on the editing screen 930, the number of times users need to switch between the registration confirmation screen 920 and the editing screen 930 can be reduced. Alternatively, if pending items are displayed on half of the area of ​​the registration confirmation screen 920 (for example, only the left side), the editing screen 930 can be overlaid on or replaced with the registered item information on the other half (right side), thereby reducing the effort required for screen transitions.

[0149] The POS terminal 70 may also reflect the reserved product information modified by the store clerk on the editing screen 930 into the product master, etc. For example, when introducing a new product, a product from a new business partner, or when barcodes are not updated, scanning the barcode attached to the sale item may result in it not existing in the product master, leading to it being classified as a "Non-File" product. In such cases, the corrections made to the held product information on the POS terminal 70 can be reflected in the product master, preventing the product from being held again in the future. The product information editing process here only needs to include the items necessary for product registration and settlement processing. For example, this includes product name, unit price, barcode (product identification information), and tax category (reduced tax rate, inclusive tax, exclusive tax, tax-exempt, etc.).

[0150] Furthermore, for items where the price or other details are not clear, the POS terminal 70 may be configured to allow temporary corrections by editing the department and amount.

[0151] Then, when the store clerk edits and updates the reserved product information 920b on the editing screen 930 into registerable product information, the POS terminal 70 modifies and displays the reserved product information 920b on the registration confirmation screen 920, as shown in Figure 22. The POS terminal 70 may display the modified reserved product information 920b at the top of the list of registered product information without moving its display position, or it may move it to the display order of the other registered product information 920a after the modification and display it. Furthermore, if the pending product information 920b, 920c and the canceled product information 920d are placed in the left area of ​​the registration confirmation screen 920, the modified pending product information 920b may be moved to the right area for display.

[0152] Then, the POS terminal 70 changes the number of reserved items 920e, which is displayed at the bottom of the registration confirmation screen 920, to "2".

[0153] The POS terminal 70 that has modified the pending product information 920b determines whether pending product information (including canceled product information) exists in the registration information, that is, whether all pending product information has been modified (S707). If it determines that all pending product information has been modified, it releases the prohibition on settlement processing (S708) and displays the registration confirmation screen 920 showing that all pending product information has been modified, as shown in Figure 23 (S709).

[0154] In the registration confirmation screen 920 shown in Figure 23, the correct product information is entered and registered for the two pending product information items 920b and 920c that could not be registered, and the cancellation of the one canceled product information item 920d that was canceled during registration is confirmed. Once all of the pending product information 920b, 920c and the canceled product information 920d have been corrected or confirmed, the POS terminal 70 displays "0" in the quantity of pending products 920e, which is displayed at the bottom of the registration confirmation screen 920. Furthermore, the POS terminal 70 changes the background color of the registration confirmation screen 920 to the normal background color and displays the "OK" key 920f above the registration confirmation screen 920. When a member or store employee operates the "Confirm" key 920f, the POS terminal 70 completes the product registration and modification process and proceeds to the payment screen shown in Figure 24.

[0155] On the other hand, if the POS terminal 70 determines that all pending product information has not been corrected, it returns to step S706 and repeats the correction process until all pending product information has been corrected. In other words, in the example shown in Figure 22, the POS terminal 70 prohibits the execution of settlement processing until the pending product information 920c and the canceled product information 920d are corrected.

[0156] The settlement screen 950 shown in Figure 24 displays a "cash" key 950a and a "credit card" key 950b for selecting the payment amount and payment method. The member executes the settlement process (S710) by operating either key, and the transaction is completed. The above explains the processing flow in POS terminal 70.

[0157] -Functional Block Diagram- Figure 9 shows an example of a functional block diagram of the sales data processing system of this embodiment. The portable terminal 20 of the sales data processing system in this embodiment includes a control unit 200, a display unit 250 such as a touch panel, and an input unit 260 such as a camera.

[0158] The control unit 200 includes a control means 201 for overall control of the mobile terminal 20, a store identification means 202 for identifying the store where shopping is to be done, an acquisition means 203 for acquiring product identification information of the product to be purchased, a detection means 204 for detecting an operation to acquire product identification information, a product registration means 205 for identifying and registering product information based on the acquired product identification information, a pending product registration means 206 for generating and storing information about products for which product information cannot be registered, a display means 207 for displaying registered product information registered by the product registration means 205 and pending product information generated by the pending product registration means 206 on the display unit 250, a notification means 208 for notifying that product information cannot be registered, an output means 209 for outputting registered information and pending product information, and a registered product cancellation means 210 for canceling a member's registered product information, etc.

[0159] The control means 201 controls the mobile terminal 20 comprehensively, for example, by storing the input (acquired) or detected information in a memory or other storage device as appropriate, reading the information from the storage device and displaying it on the display unit 250, and exchanging information with other devices. Furthermore, the control means 201 performs various decision-making processes and the like.

[0160] The store identification means 202 performs store identification processing. For example, the store identification means 202 outputs location information of the mobile terminal 20 to the host device 10, and identifies the store where the purchase is made by inputting information of the store from the store master of the host device 10.

[0161] The acquisition means 203 executes the product information acquisition process. For example, the acquisition means 203 acquires product identification information of a product based on code information attached to the product, which is captured using the input unit 260 of the mobile terminal 20. In the sales data processing system of the above embodiment, an example is used in which product identification information is acquired by reading a barcode attached to the product, but the method of acquiring product identification information by the acquisition means is not limited to reading a barcode.

[0162] For example, product identification information can be obtained by a mobile terminal 20 using contactless detection with RFID tags or by scanning a QR code. Furthermore, image recognition technology can be used to identify products based on their appearance (shape, color, material, etc.). Furthermore, the recognition rate of the image recognition may be improved by storing images taken by customers when registering products on a server and performing AI learning on those images.

[0163] The detection means 204 performs a read operation detection process. For example, the detection means 204 detects that the input unit 260 of the mobile terminal 20 has performed an operation to capture image of code information attached to the product.

[0164] The product registration means 205 executes the product registration process. For example, the product registration means 205 identifies a product based on the product identification information obtained through the acquisition process and the information stored in the product master, acquires product information, and registers it as registered product information. The pending product registration means 206 executes the pending product information generation process. For example, the pending product registration means 206 generates and stores information about a product as pending product information if product identification information cannot be obtained through the acquisition process or if product identification information obtained through the acquisition process is not stored in the product master.

[0165] The display means 207 performs a display process. For example, the display means 207 displays registered product information registered by the product registration means 205 and reserved product information generated by the reserved product registration means 206 on the display unit 250. The notification means 208 performs notification processing. For example, the notification means 208 notifies the member via the display unit 250 or the like if there are products that cannot be registered through the member's product registration operation. The output means 209 outputs registered product information registered by the product registration means 205 and reserved product information generated by the reserved product registration means 206, etc.

[0166] The aforementioned registered product cancellation means 210 executes the registered product cancellation process. For example, the registered product cancellation means 210 detects that a member has canceled a product registration, creates registration deletion information, and outputs to the higher-level device 10 that the registered product information has been canceled.

[0167] The POS terminal 70 of the sales data processing system in this embodiment includes a control unit 700, a display unit 750 such as a touch panel, an input unit 760 such as a camera, a printing unit 770 such as a printer, and the like.

[0168] The control unit 700 includes a control means 701 for overall control of the POS terminal 70, an input means 702 for inputting product registration information, a display means 703 for displaying the input registration information on the display unit 750, a settlement means 704 for settling the payment for the products based on the registration information, a notification means 705 for notifying store staff, etc., when reserved product information is entered, an editing means 706 for correcting reserved product information, and a prohibition means 707 for prohibiting settlement processing by the settlement means 704 if the product information includes reserved product information.

[0169] The control means 701 controls the POS terminal 70 in an overall manner, for example, by storing the input (acquired) or detected information in a memory or other storage device as appropriate, reading the information from the storage device and displaying it on the display unit 750, and exchanging information with other devices. Furthermore, the control means 701 performs various decision-making processes. For example, in step S702 of the flow shown in Figure 8, it is determined whether or not there is pending product information in the registration information, and in step S707, it is determined whether or not there is pending product information that has not been modified.

[0170] The input means 702 performs input processing. For example, the input means 702 receives the registration information output by the output means 209 of the mobile terminal 20. The display means 703 performs the process of displaying the registered information. For example, the display means 703 displays the entered registration information (registration information and reserved items) on the display unit 750. Furthermore, it displays the registered information (registration information and reserved items) in a different format as needed.

[0171] The settlement means 704 executes the settlement process. For example, the settlement means 704 performs settlement processing for goods based on the registered information. It also obtains the accounting method used by the customer for settlement prior to the settlement processing. The notification means 705 performs notification processing. For example, if the input registration information includes information on reserved or canceled items, the notification means 705 displays on the display unit 750 that reserved items (cancelled items) exist and executes a calling process to summon a store employee to the POS terminal 70. It also executes a calling process to summon a store employee as needed, such as based on the member's status.

[0172] The editing means 706 performs the editing process. For example, the editing means 706 displays an editing screen for modifying the reserved product information entered by the input means 702. A store employee or other staff member can modify the reserved product information into registered product information by editing the reserved product information on the editing screen. The editing screen may also be displayed by entering a store employee code or the like. The prohibition means 707 executes the prohibition process. For example, if the registration information includes reserved product information or reserved product information, the prohibition means 707 prohibits settlement processing until the reserved product information is modified by the editing means 706 and registered as registered product information.

[0173] The following provides further explanation of the functions provided by the mobile terminal 20 of this embodiment. —How to display the registration details list— Next, we will provide further explanation regarding the screen display on the mobile device 20 during product registration. (Normal registration procedure) While shopping, the display unit 250 of the mobile terminal 20 displays the registration screen 810 shown in Figure 16(a). When a member reads information such as a barcode attached to a product using the mobile terminal 20, the mobile terminal 20 displays the most recently registered products in order in a second display area 812 located in the lower area of ​​the registration screen 810 shown in Figure 16(a), with the most recently registered products positioned in the upper part of the second display area 812.

[0174] As members register more products, the second display area 812 will eventually be filled with registered product information, and the barcodes of registered products that have already been read will no longer be displayed in the second display area 812.

[0175] Members can check the products they have registered by looking at the second display area 812. However, when purchasing many products, checking the information of previously registered products requires scrolling through the list displayed in the second display area 812 many times, making the process cumbersome. In this embodiment, the mobile terminal 20 allows for easier confirmation of registered products by expanding the second display area 812 of the display unit 250 as needed.

[0176] Specifically, if the registration of multiple products by a member causes all of the product information registered in the second display area 812 to become unusable, the mobile terminal 20 will display the "extension" key (operator) 813d in the third display area 813. Then, when a member operates the "Expand" key 813d, the mobile terminal 20 expands the second display area 812, as shown in Figure 16(b), and displays the second display area 812 and the third display area 813 using the entire area of ​​the display unit 250. Furthermore, as the second display area 812 is expanded, a "shrink" key (operator) 813e that shrinks the second display area 812 back to its original size before expansion may be displayed in the third display area 813.

[0177] Furthermore, if all products cannot be displayed even when the entire area of ​​the display unit 250 is used to display the second display area 812 and the third display area 813, it goes without saying that they can be displayed by scrolling. Furthermore, operations to expand the second display area 812 are not limited to those performed using the "Expand" key 813d located in the third display area 813.

[0178] Furthermore, it is preferable that the mobile terminal 20 hides the first display area 811 by using the entire area of ​​the display unit 250 to display the second display area 812 and the third display area 813, and in conjunction with this, disables the acquisition of image data by the input unit 260 of the mobile terminal 20.

[0179] Furthermore, the second display area 812 and the third display area 813 do not necessarily have to be expanded to cover the entire area of ​​the display unit 250 by operating the "Expand" key 813d. The expansion range may be changed by the member's operation, or it may be expanded to a state where all products can be viewed depending on the number of products. In this case, the acquisition of image data by the input unit 260 of the mobile terminal 20 may be disabled immediately when the second display area 812 is changed to include the first display area 811, or the acquisition of image data by the input unit 260 of the mobile terminal 20 may be disabled when the second display area 812 expands to the reading range that is visibly displayed in the first display area 811. As described above, when it becomes impossible to check the image data using the first display area 811, the imaging means by the input unit 260 is disabled, thereby reducing unnecessary power consumption.

[0180] Furthermore, the second display area 812 may be sequentially expanded as a member registers a product. In this case, the second display area 812 may be automatically expanded while the first display area 811 is secured by setting the maximum expanded state of the second display area 812.

[0181] Furthermore, if a barcode (product identification information) is not recognized within the reading range of the second display area 812 for a predetermined period of time, the mobile terminal 20 may disable the imaging means by the input unit 260 in order to save power.

[0182] The placement of the first display area 811 at the top of the screen ensures excellent operability, as it aligns with the camera position of the mobile device when the user operates the device, and the object being photographed is viewed from above the top edge of the device. The placement of the second display area 812 at the bottom of the screen allows users to view the screen when checking purchased items. If more items than the predetermined number of display lines are registered, the third display area 813 located in the center of the screen can be displayed in full using the expansion key. If the full display is insufficient, all items can be viewed by scrolling. Furthermore, since the operator checks the number of items purchased and the purchase amount while the image processing is in progress, positioning the third display area 813 between the first display area 811 and the second display area 812, which display the image capture screen, is excellent because it does not burden the operator's eye movement. In addition, the aforementioned extended keys can be easily operated.

[0183] Furthermore, the display position of the controls on the screen may be switched based on member information or at any time. Specifically, since the controls are arranged with right-handed operation in mind, they may be inconvenient for left-handed users or those using their left hand. In this case, as shown in Figure 27(a), the "Checkout" key 813c may be placed at approximately the same distance from the center line of the screen, and the purchase quantity 812b, etc., may be moved similarly, as shown in Figure 27(b), or placed at the beginning of the product name display. In other words, the system should memorize the optimal placement of controls for right-handed and left-handed operation, and automatically switch between them based on switching instructions or member information. Furthermore, the "Accounting" key 813c could even be placed in a deliberately inconvenient location, such as on the opposite side.

[0184] Figure 26 shows the processing flow for displaying the above registration details list. This flow corresponds to the subroutine of step S209 in the flow shown in Figure 7. In step S401, the mobile terminal 20 displays the first display area 811 and the second display area 812 on the display unit 212. The mobile terminal 20 then detects that the member has performed an expansion operation on the second display area 812 (S402), and upon detecting that the expansion operation has been performed, executes the expansion process for the second display area 812 (S403).

[0185] Then, it is determined whether the expanded second display area 812 has reached a predetermined range (S404). The predetermined range in step S404 may be, for example, a range that includes even a small part of the first display area 811, or a range that includes the reading range in which the barcode can be recognized. Alternatively, it may be a range that includes the entirety of the first display area 811.

[0186] If the mobile terminal 20 determines in step S404 that the second display area 812 has reached a predetermined range, it proceeds to step S406 and disables the acquisition means 203. Specifically, it turns off the camera's imaging function. (Imaging means by input unit 260)

[0187] On the other hand, if it is not detected in step S402 that an extension operation has been performed by a member, the process proceeds to step S405, where it is detected that the barcode is not recognized within the reading range of the second display area 812 for a predetermined period of time. If it is determined that the barcode is not recognized for the predetermined period of time, the mobile terminal 20 proceeds to step S406 to disable the acquisition means.

[0188] If the barcode is recognized in step S405, return to step S402 and continue displaying the registration information. The above explains the process for displaying the product registration screen.

[0189] -Multiple purchases of the same item- When registering products using the mobile terminal 20 of this embodiment, if you wish to purchase multiple identical products, you may do so by changing the quantity displayed in the registered product information 812d on the registration screen 810, or you may capture the code information of the same product multiple times.

[0190] However, if the code information for the same product is scanned multiple times consecutively or with a time interval between scans, the mobile terminal 20 will display a message asking whether it is okay to purchase the same product multiple times, or it will change the confirmation sound or vibration pattern when acquiring product identification information. For example, it may display a message such as "The same product has been scanned twice, is the registration correct?" to inform the customer whether the operation was correct or incorrect. This allows members to recognize that the registration process for the product they are currently working on is the second or subsequent acquisition of code information.

[0191] Specifically, if the same product is photographed and confirmed, a message such as "You have registered the same product. Do you want to purchase it?" with a yes / no option could be displayed for confirmation. Furthermore, during this confirmation, the screen could also display options for adjusting the quantity. This method is efficient when registering the same product consecutively, as there is a possibility of further additions. The same verification process will be performed when registering the same product again after registering other products in between. Furthermore, to prevent fraud, when purchasing multiple items, the system may read the data the same number of times as the number of items purchased. Similarly, when deleting items, the system may read the data the same number of times as the number of items being deleted. The operation of purchasing multiple identical items can be done either way, or both methods can be adopted. Furthermore, the operation method may be changed depending on the user's skill level.

[0192] Furthermore, if a member registers the same product through multiple imaging attempts, the mobile terminal 20 sets the purchase quantity of the registered product information for that product to "multiple attempts" and displays it in the latest row of the list display. Needless to say, registrations of the same product through multiple imaging attempts may also be displayed on multiple rows.

[0193] - Registration operation for loose-sale products - For products that are not suitable for attaching barcodes, such as fresh produce like cucumbers or loose-sale products like fish, the product registration process can be carried out by, for example, imaging the barcode attached to the shelf or container where the product is displayed. Needless to say, if a barcode is directly attached to the product, that barcode may be imaged.

[0194] In addition, the mobile terminal 20 may identify the product by imaging a product that is not suitable for barcode attachment and performing object recognition. Also, a registration process may be performed by voice or the like, or a registration process may be performed by displaying preset keys on the display unit and having the member select them.

[0195] Also, when selling loose-sale products, etc., a discount may be applied for bulk (multiple) purchases. When the member reads the barcode information of the product for which the discount for bulk purchase is applied, the mobile terminal 20 displays a popup 850 as shown in Fig. 17(a), in which the number of items that becomes cheaper by bulk purchase is set as the initial value of the number of purchases. In the popup 850, for the loose-sale product, the product name 850a, the price per unit 850b, the number of purchases 850c, and the selling price 850d are displayed, and a "+" key 850e and a "-" key 850f for instructing a change in the number of purchases, a "Cancel Product" key 850g, and a "Confirm" key 850h are arranged.

[0196] In the example shown in Fig. 17(a), a popup 850 in which a product with the product name "Hokkaido-grown corn" is registered is displayed, indicating that it is advantageous to buy 3 units of the product priced at 1,200 yen each for a total of 60 yen. The number of purchases 850c is set to "3", which is the number of items for bulk purchase, as the initial value. The member can know through the popup 850 that it is a discounted product for bulk purchase, and by operating the "Confirm" key 850h, the product registration for bulk purchase can be easily set.

[0197] In addition, members can change the quantity purchased by using the "+" key 850e and the "-" key 850f, and they can also cancel the registration of a product by using the "Cancel Product" key 850g, just as with normal product registration.

[0198] When a member changes the number of items to be purchased by operating the "-" key 850f, the mobile terminal 20 changes the display of the pop-up 850 as shown in Figure 17(b). In Figure 17(b), the pop-up 850 displays the purchase quantity 850c as "1," shows the regular price (120 yen) without the discount, and indicates that a 60 yen discount is available for purchasing three items. The content and timing of the display encouraging bulk purchases are not particularly limited; the mobile device 20 may also display that the bulk purchase discount will no longer apply when the member changes the quantity they are purchasing.

[0199] Then, when the member operates the "Confirm" key 850h (confirmation operation), the mobile terminal 20 registers the registration information according to the quantity set in Purchase Quantity 850c. In this way, members can learn about discounted items through the pop-up 850, and by operating the "Confirm" key 850h, they can easily set up a bulk purchase. Even for products eligible for bulk purchase discounts, the initial value can be set to "1".

[0200] Furthermore, this registration process also applies to regular single-item sales. In other words, by setting sales conditions such as bundle sales or bulk purchases, the same registration process can be performed. The sales conditions are set using product master data and special offer master data, and are generated as information that mobile devices can use to identify products. Moreover, special offers that are not available to general customers but are only available to members can also be applied.

[0201] Additionally, for items with sales quantity restrictions, such as a limit of XX items per person, you may disable or hide the "+" symbol for the maximum quantity. Furthermore, the "+" key may be counted up in units of quantity set in the sales conditions, and the addition / subtraction keys may be displayed and functioned in a different manner in units of "sales condition quantity". Furthermore, when the quantity is reduced from the "sales condition quantity," the system may notify that the sales condition has not been met and may also change the format of the explanation of the sales condition. Also, when the quantity is increased by "1" from the "sales condition quantity," the system may switch to displaying the next sales condition-fulfilled quantity and the total discount amount. This encourages members to purchase the specified quantity.

[0202] Figure 29 shows an example of the processing flow for registering the individual items sold as described above. Mobile device 20 inputs product information for items purchased by the member (S501). Specifically, the input unit 260 of the mobile terminal 20 reads the barcode (product identification information) attached to the product to obtain product identification information, and then obtains (inputs) product information from the product master 110 based on the product identification information.

[0203] Next, the mobile terminal 20 detects whether or not special sales conditions are set for the sales conditions of the entered product information (S502). For example, in the table shown in Figure 28(a), it detects whether sales conditions (specification number) exist for the product with the entered product identification number. The special sales conditions referred to here are any sales conditions that impose some kind of restriction on the number of items sold, such as products that are sold in bundles or a limit on the number of items that can be purchased per person. Furthermore, if the customer has previously memorized the number of items to purchase using a shopping list or similar method, this quantity may also be included in the sales conditions. Additionally, it may indicate that the item is frequently purchased by the customer (i.e., that the customer has a purchase history of that item).

[0204] If it is detected in step S502 that special sales conditions are set for the product information, then information on the number of units that must be sold, as set for the sales conditions, is obtained by, for example, referring to the product master special sale data shown in Figure 28(b). Then, the mobile terminal 20 determines the number of units to be purchased by the member based on the acquired information on the number of units sold, i.e., the detected sales conditions (S503).

[0205] For example, if the acquired product identification information is 0001 (corn), it is detected that this is a product eligible for the bulk discount set for promotion number 1. It is then determined that the number of units required to meet the sales conditions for promotion number 1 is 3, and the bulk quantity eligible for the discount, "3," is determined as the quantity. In addition, for limited-quantity products with sales conditions such as a limit of two per person, the limited quantity can be used as the quantity. Also, for products that customers frequently purchase (products they have purchased in the past), the number of units purchased last time can be used.

[0206] The mobile terminal 20, having determined the quantity, displays a confirmation screen on its display unit 250 for deciding to register the product, with the quantity to be purchased already set (S504). Normally, when a member scans a product's barcode (product identification information), the mobile terminal 20 sets the purchase quantity to "1" and registers the product. However, if the product obtained by scanning the barcode (product identification information) has special sales conditions set, for example, if it is a product eligible for a bulk discount, a confirmation screen is displayed with the bulk quantity set as the purchase quantity, as shown in Figure 17(a).

[0207] In step S504, the mobile terminal 20, which displays the confirmation screen, waits for the "OK" key 850h located on the confirmation screen to be pressed. Furthermore, if the quantity to be purchased is changed on the confirmation screen, the quantity will be changed accordingly.

[0208] In step S506, when it is detected that the "Decision" key 850h has been operated by the member, the mobile terminal 20 registers the product according to the number of purchases at the time when the "Decision" key 850h is operated, and completes the process.

[0209] On the other hand, in step S502, when it is detected that no special sales conditions are set for the product information, the process proceeds to step S505, the number of purchases is set to "1", and without displaying the confirmation screen, the process proceeds to step S507, the product is registered, and the process is completed. The above describes the process related to the registration operation of loose-sale products.

[0210] -Registration operation of non-fixed-weight products- When registering products sold by weight such as meat and prepared dishes, a value-added label on which product information is recorded is printed by a weighing instrument that weighs the weighed products, and the mobile terminal 20 performs the product registration process by reading the barcode printed on the value-added label. By connecting the weighing instrument to the store controller, the product information recorded on the issued value-added label can be added to the product master. Note that for non-fixed-weight products, it may be possible to prevent the change of the number of purchases by operating the list display on the registration screen 810.

[0211] Also, when the weighing instrument is network-connected, after connecting the weighing instrument and the mobile terminal 20 by short-range wireless communication or the like, the barcode of the product to be weighed is read by the mobile terminal 20, and the product to be weighed is specified by operating the key for specifying the product. By weighing the product with the weighing instrument, the information of the weighed product may be registered in the mobile terminal 20. In that case, the label issued by the weighing instrument may be a label that indicates only information such as the expiration date and is attached to the product. Furthermore, if member information, app user ID, etc. can be recognized by an IC or the like, shopping data can be generated even from a bulk-only weighing instrument and uploaded as the customer's shopping data, and it is also possible to prevent fraud by collating the two data. If only the product is specified and the weight, and therefore the purchase price, has not been determined, the item may be treated as a pending item.

[0212] -Register coupon information- The mobile device 20 can register coupon information from paper coupons. For example, by scanning the barcode printed on the coupon, it can retrieve the recorded discount information and reflect it in the registered product information. Furthermore, if the recorded coupon information is unique, the coupon information can be invalidated by reading it. Additionally, if coupons need to be collected, customers can either call a staff member during their shopping to enter the information, or the POS terminal 70 used for payment processing can be designated as a manned POS system.

[0213] The mobile terminal 20 may also automatically calculate the maximum discount condition based on the scanned coupon information, reflect it in the product price, and output the registration information. Furthermore, the mobile terminal 20 may record the scanned coupon information in code information such as a QR code (registered trademark) in accordance with the product registration information and output it, and the POS terminal 70 or the like may perform discount processing. In this case as well, the code information such as a QR code (registered trademark) output by the mobile terminal 20 may record shopping identification information and coupon identification information, and the POS terminal 70 that acquires the identification information may acquire the registration information and coupon information from the host device 10 based on the respective identification information.

[0214] - Using a shopping list - Members can use their mobile device 20 to identify a store and download all or part of the store's product master data, thereby creating a list of items they intend to purchase (hereinafter referred to as the "shopping list") using their mobile device 20. For example, when a member selects and registers products they intend to purchase from a list of product information displayed on the display unit 250 of the mobile terminal 20, the mobile terminal 20 creates a shopping list. Alternatively, the mobile terminal 20 may automatically register products that are purchased regularly as planned purchase items when creating a shopping list.

[0215] Members can use the shopping list displayed on the display unit 250 of the mobile terminal 20 when registering products at the store. The order of items you plan to purchase in the displayed shopping list can be arranged by store aisle order, department order, or any other order you wish to set and change. Furthermore, by voice input such as "vegetables" or "seika," the mobile terminal 20 may display only the relevant category, or it may display it in the upper part of the display area.

[0216] Then, when a member registers an item, the mobile device 20 changes the displayed item information on the shopping list and removes items from the shopping list. This allows the member to know that the item they intend to purchase has been registered. Furthermore, the mobile terminal 20 may be configured to notify the planned purchase quantity of items to be purchased multiple times, and to perform checkout or similar actions once the planned quantity is registered.

[0217] Furthermore, the mobile device 20 may be configured so that the product registration process cannot be executed until the member has specified the products to be registered from their shopping list. This ensures that the intended purchase is made and helps to curb excessive impulse purchases, such as buying products other than those intended.

[0218] Furthermore, if a member selects a product and then takes a picture of something other than that product, the mobile terminal 20 may display an error message or other notification. In addition, the mobile terminal 20 may also display an error message or other notification if the member takes a picture of any other product registered in the shopping list.

[0219] Furthermore, the mobile terminal 20 allows the registration of items that are not on the shopping list, but in such cases, it is preferable to notify the user that the item is not on the shopping list and to display a screen to confirm the purchase. Furthermore, the mobile terminal 20 may display the registered information in a way that allows for the distinction between products that are present in the shopping list and those that are not.

[0220] Furthermore, the mobile terminal 20 may allow members to complete product registration by clicking on the product name displayed in their shopping list. Members do not need to scan the product's barcode, allowing for smoother product registration. Also, by registering products using the shopping list, the registration process for products without barcodes can be easily handled. Alternatively, it may be limited to functioning as a preset key for products without barcodes. There is no need to scan barcodes on price tags, etc. Operation buttons may also be provided to display alternative products such as the place of origin (manufacturer), specifications, and capacity.

[0221] Furthermore, the mobile device 20 may be configured to automatically add regularly purchased items to a shopping list based on past purchase history, or to create a "shopping list" by scanning barcodes on empty containers or other items at home. Furthermore, if there are items registered on the shopping list but no registration information, the mobile terminal 20 may notify the member that they have forgotten to buy something by displaying a message on the registration screen or elsewhere, and may also ask the member whether or not they want to purchase the forgotten items.

[0222] - Processing of registered information output - Further explanation will be provided regarding the output process of registration information during settlement. The output of registration information is basically done by converting the shopping identification information into a QR code (registered trademark), displaying it on the mobile terminal 20, and having the POS terminal 70 read it. The POS terminal 70, upon reading the QR code (registered trademark), requests shopping information from the host device 10 based on the acquired shopping identification information. The host device 10, upon receiving the request from the POS terminal 70, performs a subtotal calculation based on the shopping information linked to the shopping information and transmits the calculated shopping information back to the POS terminal 70.

[0223] Alternatively, a QR code (registered trademark) encoding the shopping information may be displayed on the screen of the mobile terminal 20 and output to the POS terminal 70. In this case, the code information (QR code (registered trademark) 840a) displayed on the output screen 830 of the mobile terminal 20 is read by the input unit 760 of the POS terminal 70 to output the registered information and perform the settlement process. However, if there is a large amount of registered information and one code is insufficient, multiple code information can be displayed consecutively and read consecutively by the input unit 760 of the POS terminal 70 to output all the registered information. In this case, it is preferable to display the total number of code information and the number of the currently displayed code information on the output screen 830.

[0224] Furthermore, instead of reading the registered product information using a QR code (registered trademark), the information may be obtained and received by displaying the information in the storage area of ​​the shopping file and acquiring the "shopping file" using the information in that storage area. In addition, not limited to QR codes (registered trademark), any one-dimensional code that can identify member information, such as the NFC identification code of a mobile device, can be used, and the shopping file can be easily identified by setting such an identifier in the shopping file.

[0225] As described above, when the output process for registration information is performed by displaying code information (QR code (registered trademark) 840a) on the output screen 830 of the mobile terminal 20, the mobile terminal 20 will not stop displaying the code information until the POS terminal 70 has finished processing the input of the registration information.

[0226] For example, the POS terminal 70 may communicate to the mobile terminal 20 that it has finished reading the code information (QR code (registered trademark) 840a), and upon completion of inputting the code information in the POS terminal 70, display a message such as "Product registration is complete. Further operations will be performed at the payment device" on the display unit 250 of the mobile terminal 20, and then end the display of the code information.

[0227] This allows members to know that the product registration process using the mobile terminal 20 has been completed, and to concentrate on the settlement process using the POS terminal 70. Once the product registration process is complete, the mobile device 20, such as a smartphone, exits the output screen 830 displayed on the display unit 250 and returns to the start screen 800.

[0228] Furthermore, the output of registration information from the mobile terminal 20 to the POS terminal 70 is not limited to the display of code information. For example, the customer may complete the registration process using the mobile terminal 20 and select a POS terminal 70 to perform the settlement process. The mobile terminal 20 may then identify the POS terminal 70 and output the registration information to the POS terminal 70 via the network.

[0229] Furthermore, the input unit 260 of the mobile terminal 20 may read the identification information of the POS terminal 70 attached to (or displayed on) the POS terminal 70, and the registered information of the read identification information may be output to the POS terminal 70 via the network. In this case, the output of the registered information may not be directly output to the POS terminal 70 selected by the mobile terminal 20, but may be done via a higher-level system such as the host device 10 or the store controller 60. In other words, the mobile terminal 20 may output shopping identification information to the selected POS terminal 70, and the POS terminal 70 that has received the shopping identification information may request and obtain corresponding registration information from a higher-level system based on the shopping identification information.

[0230] Alternatively, the mobile terminal 20 may receive status information from the POS terminal 70 and display the status buttons of the POS terminal 70 on the display unit 250, so that when a member selects a POS terminal 70, the mobile terminal 20 outputs the registration information to the selected POS terminal 70. Furthermore, based on the status information transmitted from the POS terminal 70 to the mobile terminal 20, the mobile terminal 20 may automatically select and output to the POS terminal 70 that outputs registration information or purchase identification information. The output of registration information from the mobile terminal 20 to the POS terminal 70 is not particularly limited and can be done in any appropriate manner.

[0231] In addition, during shopping, a customer may remember that they have forgotten to buy an item when the checkout process is underway. In such cases, the customer may operate the cancel button or the like displayed on the display unit of the POS terminal 70 during the checkout process. The POS terminal 70 will then display a notification screen on its display unit 730 such as "Checkout will be canceled; subsequent operations will be performed on your smartphone," and the registration screen 810 will be displayed again on the display unit 250 of the mobile terminal 20, allowing the customer to continue registering the item.

[0232] -Settlement Processing- On the checkout screen 950, members select a payment method to process the payment for their goods. However, if a payment method has been registered in advance during member registration, the POS terminal 70 does not need to display a screen for selecting a payment method. It is preferable that the payment method can be changed even if it has been registered. Furthermore, for products requiring age verification, such as alcoholic beverages, a store employee must be called, similar to reserved items. In addition, for pharmaceuticals, explanations from a pharmacist or registered salesperson are mandatory for Category 2 pharmaceuticals, so a store employee may be called in a different manner than for reserved items. Furthermore, these items should be treated similarly to reserved items, stored as reserved item information, and, at the time of settlement, a store employee should be called by a notification device. It is also preferable that, similar to reserved item information, the payment should be prohibited by a prohibition device unless editing (confirmation processing) is performed on the screen of the POS terminal 70. Furthermore, it is permissible to prohibit purchases by notifying customers that a pharmacist or registered salesperson is not present.

[0233] The payment process allows for payment using gift certificates and points earned by loyalty program members. Discount coupons and other vouchers can also be used, and the payment process, including change distribution and receipt issuance, is the same as a regular payment system. Furthermore, if staff intervention is required, such as for collecting gift certificates, an automated system will call a staff member. Alternatively, the display may show instructions directing customers to a service counter or a manned POS system.

[0234] Furthermore, it is preferable that the system be controlled so that settlement processing is not performed based on registered product information registered at a store different from the store specified by the member. In other words, the basket data (shopping file) generated by identifying a store contains store identification information, and if another store is identified and the mobile terminal 20 outputs the registration information that has been registered, and attempts are made to process the payment using the POS terminal 70, the display unit 750 of the POS terminal 70 may display an error message such as "This is not a purchase from this store," and may also call a store employee. Furthermore, if the mobile device 20 identifies another store and attempts to register products, the mobile device 20's display screen may show messages such as "The payment at the other store is not yet complete. Do you want to create a basket for our store?" or "You are logged into another store. You cannot log in," thereby preventing the user from making purchases at the other store.

[0235] Furthermore, it is preferable to have store staff perform checks as needed during the payment process. Note that the check by the store staff may be performed during the store staff call process in step S703 of the flow in Figure 11, but it may also be performed at other times. Furthermore, while checks of payment processing by store staff may be conducted randomly and without prior notice, it is preferable to do so in accordance with the usage status of the member's mobile device 20.

[0236] For example, a staff member could perform a check on members whose membership level is the lowest level, L1, as recorded in the customer file. This would ensure that first-time users receive a check and support from a staff member. On the other hand, for high-level L5 members who have gone through the registration process using the mobile device 20 multiple times and have few errors using the mobile device 20, store staff checks and support will be omitted, thereby reducing the burden on the store.

[0237] Furthermore, as shown in the staff call process in step S703 in Figure 11, it is preferable for staff to perform checks and provide support when there are pending items whose code information cannot be read during the member's registration operation, or when the member attempts to cancel registered item information.

[0238] For example, the mobile terminal 20 or POS terminal 70 may refer to the member file to obtain the number of past cancellations and have a store employee check members whose past cancellation count exceeds a predetermined number, or it may refer to the shopping file and have a store employee check members who have performed registration deletion (cancellation) operations more than a predetermined number of times in the relevant purchase.

[0239] Specifically, the POS terminal 70 may be configured to call a store employee if the customer cancels the registration of an item multiple times (for example, three times) during the transaction. Furthermore, when calling a store employee based on a registration cancellation operation, the customer's past shopping history may be taken into consideration. For example, if the total number of registration cancellation operations (this time, last time, and the time before that) is five or more, the system may be set to call a store employee.

[0240] This allows store staff to check, for example, customers who scan areas of a product where there is no barcode and pretend to register the product, or customers who delete registration information without returning the product.

[0241] Furthermore, by setting whether or not to require staff intervention during the payment process based on the operation history of the mobile device 20 during the member registration process, it is possible to enhance service quality, efficiency, and security by actively involving staff members, focusing on members who frequently cancel their registration or make mistakes, or those who are likely to be unfamiliar with the registration process using the mobile device 20. In addition, it may be possible to issue a notice prohibiting the use of the app.

[0242] Furthermore, the intervention of store staff based on the operation history of the mobile terminal 20 during the member registration process is not limited to the payment process, but may also occur upon entry or product registration. For first-time members, intervention upon entry rather than at payment can facilitate a smoother product registration process.

[0243] -Preventing forgetting to settle payments- If a member leaves the store without completing the payment process for their purchased items, the mobile device 20 will notify the member that the payment process for the items is incomplete. Specifically, the location of the mobile device 20 is determined using GPS location information, and if the mobile device 20 moves outside the store premises without completing the payment process, it notifies the registered customer via email or the app screen.

[0244] Furthermore, if a product is registered using the app, the app may be prevented from being forcibly closed until the payment process is complete, or the user may be prohibited from launching other apps, informing the customer of this. Alternatively, automatic payment can be made using a pre-registered payment method such as a credit card, and notification can be sent via email. Furthermore, it is also acceptable to operate without performing settlement processing at a payment terminal by registering credit cards, electronic money, or bank account withdrawals. However, since members can shop with peace of mind if they can confirm their purchase details, it is also acceptable for members to decide at their discretion whether or not to confirm the details at a payment terminal or a device with similar functionality. In addition, if there are no items on hold, or depending on the member's skill level, and there is no need to handle cash payments, gift certificates, or coupons, that is, if there is no need to use a payment terminal such as online payment or bank account withdrawal, it may be possible to inform the member that they can skip operating the payment terminal when displaying the registration information or purchase identification information as a QR code (registered trademark) during the registration completion operation, or a message such as "No operation at the payment terminal is required" may be displayed instead of the screen.

[0245] Next, an example of a block diagram of the mobile terminal 20 of the sales data processing system will be explained using Figure 25(a). The sales data processing system of this embodiment includes a CPU 21, ROM 22, RAM 23, memory 24, network I / F 25, input I / F 26, display I / F 27, and the like as a control unit.

[0246] The CPU 21 configures the computer and executes instructions for software programs. The ROM 22 pre-stores programs and other data necessary for the CPU 21 to operate. Alternatively, these programs may be stored on a portable storage medium such as a CD-ROM and read by an external device such as a CD-ROM drive.

[0247] RAM23 is used as a work memory area for storing programs and for software to operate. Memory 24 consists of a hard disk drive and stores information such as product master data. Network I / F25 is a circuit for exchanging data with devices connected on the network. Input I / F26 is a circuit for input and output with input 260. The display interface 27 is a circuit for input and output with the display unit 250, such as a touch panel.

[0248] Next, an example of a block diagram of 70 POS terminals in a sales data processing system will be explained using Figure 25(b). The sales data processing system of this embodiment includes, as a control unit, a CPU 71, a ROM 72, a RAM 73, a memory 74, a network I / F 75, an input I / F 76, a display I / F 77, a printing I / F 78, and the like.

[0249] The CPU 71 configures the computer and executes instructions for software programs. The ROM 72 pre-stores programs and other data necessary for the CPU 71 to operate. Alternatively, these programs may be stored on a portable storage medium such as a CD-ROM and read by an external device such as a CD-ROM drive.

[0250] RAM73 is used as a work memory area for storing programs and for software to operate. Memory 74 consists of a hard disk drive and stores information such as product master data. Network I / F75 is a circuit for exchanging data with devices connected on a network. Input I / F 76 is a circuit for input and output with input 760. The display interface 77 is a circuit for input and output with the display unit 750, such as a touch panel. The Printer I / F 78 is a circuit for input and output with the Printer I / F 770, such as a printer.

[0251] As described above, in the sales data processing system of this embodiment, when registering products using a customer's smartphone, the display area of ​​the registered product on the mobile terminal's display is minimized during product registration, thereby facilitating the confirmation of image data. Furthermore, the list screen of registered products can be expanded as needed, making it easy to check registered products on a larger screen and reducing the amount of scrolling required.

[0252] Furthermore, if the image data of a product becomes unviewable due to viewing the registered product on a larger screen, disabling the camera or other input devices can save power and prevent the terminal device from overheating.

[0253] It goes without saying that the above embodiments are not intended to limit the invention described in the claims, but are to be treated as examples only. For example, in this embodiment, when the registration information includes reserved product information, the POS terminal 70 displays the registration information and reserved product information together in a list, but it may also display only the reserved product information in a list. The POS terminal 70 may also display a list of product information when a store employee corrects all the reserved product information.

[0254] Furthermore, various additional functions can be provided to the mobile terminal 20. For example, members could launch a dedicated app to detect and notify them of things like their smartphone's battery level and signal strength. If the battery level is low, the system may display a message such as "The battery may run out at ____ hours and ____ minutes" or "The battery may run out due to the ____ point reading process" to notify the member.

[0255] Additionally, if the system switches to offline mode due to poor signal conditions, a message such as "Only barcode information will be displayed. The price will not be displayed." may be displayed to notify the user. By acquiring (inputting) only barcode information and quantity offline, the data can be updated by referencing the product master when the system returns online. Alternatively, product information can be acquired and registered by connecting to the product master via a wired LAN or other communication medium during checkout.

[0256] The shopping files from the host device 10 are sent to the product sales system 6 (headquarters system or store controller) as the member's sales record, allowing the product sales system 6 to centrally manage the member's sales record from devices other than the host device 10. In other words, both sales records from in-store purchases and sales records from mobile devices can be managed together. The host system 10 can also be linked with an electronic receipt server (not shown). If a member requests an electronic receipt, the host system 10 may provide the member with an electronic receipt based solely on its sales data. Alternatively, the product sales system may be linked with the electronic receipt server. In this case, all purchase records can be viewed and downloaded as electronic receipts. Sales data is transmitted from the host device 10 to the product sales system 6 at predetermined intervals. Furthermore, members using the host device 10's cloud service may also be able to view and download purchase records from other companies and stores as electronic receipts. As a result, members will find it convenient even if the same sales data processing system is adopted at other stores of the same company, and if they have experience using the system at other companies and stores, they will be more likely to accept the sales data processing system.

[0257] Furthermore, even in cases where sales data is not transmitted from the POS terminal to the product sales system 6, such as in examples (1) and (3) of introducing a sales data processing system, and only sales data is received from the higher-level device 10, it is still possible to grasp the sales performance, sales reports, and inventory status of the store in question.

[0258] Additionally, the purchase history may be displayed in the app installed on the mobile device 20. If you want to create an electronic receipt for tax purposes, you can specify the product from the purchase history and instruct the system to generate an electronic receipt. If medical expense deductions and self-medication eligibility flags are managed, it would be possible to output a list of these items (in CSV or PDF format) and use it for medical expense deductions, etc. Other tax deductions can also be aggregated, and this aggregated information can be provided to members. If the eligible products differ for the same type of tax deduction, or if the tax deduction conditions differ, both can be compared and output, displayed, printed, or converted into electronic receipts. Members can also choose the tax deduction that is most advantageous to them.

[0259] Additionally, the purchase history may be displayed in the app installed on the mobile device 20. For purchase history intended for tax processing, electronic receipts can be generated by specifying the purchased items. If the self-medication flag is managed, the system can output a list of these items (in CSV or PDF format), which can then be used for medical expense deductions.

[0260] Furthermore, in the above embodiment, the mobile terminal 20 may obtain product information by referring to a product master such as that of a higher-level device 10, but it may also download the product master to the mobile terminal 20 so that it can obtain product information on the mobile terminal 20. Furthermore, while the mobile terminal 20 acquires product identification information from the captured image data, the mobile terminal 20 may only acquire the image data, and the subsequent steps of acquiring product identification information from the obtained image data may be performed by a higher-level system.

[0261] In other words, each step performed in this embodiment may be performed in any of the host device 10, mobile terminal 20, store controller 60, POS terminal 70, etc., and is not limited to any particular device as long as it does not create a contradiction.

[0262] The camera used to capture barcodes and other information attached to the product may be the camera built into the smartphone, or a separate camera connected via Bluetooth® or similar means may be used.

[0263] -Implementation of store identification- When a member purchases goods at a specific store, the store where the purchase will be made is identified. The following is a detailed explanation of how to identify a store, with reference to the diagram.

[0264] In Figure 30, the mobile terminal 20 is equipped with a location acquisition means 213 that acquires the location of the mobile terminal 20. For example, when a member launches a dedicated application on the mobile terminal 20, the location acquisition means 213 acquires the location from the mobile terminal 20's GPS, the signal strength from multiple base stations of the mobile phone network, etc. Alternatively, the location acquisition means 213 may acquire location information using short-range wireless communication. For example, the location acquisition means 213 can also directly acquire store information by interconnecting with the store's Wi-Fi or NFC installed at the store's entrance.

[0265] The location of a mobile device can be estimated using the signal strength of short-range wireless communication or triangulation based on signal strength. Other short-range wireless communication standards besides Wi-Fi include BLE (Bluetooth Low Energy), EnOcean®, Wi-SUN, and Zigbee®. BLE is one of the extensions of the short-range wireless communication technology Bluetooth. iBeacon® is a communication system that uses BLE, developed by Apple Inc. (Apple is a registered trademark). In iBeacon®, a fixed transmitter (beacon) continuously transmits unique ID information to nearby BLE-enabled smartphones and other devices. The receiving device can monitor the BLE signal and recognize the ID information and the propagation strength of the beacon. iBeacon® allows you to set the range in which the ID is transmitted from three types: "Immediate," "Near," and "Far."

[0266] It goes without saying that those skilled in the art can choose the appropriate short-range wireless communication method to estimate the location of a mobile device. Furthermore, the location acquisition means 213 can also be used to acquire location information, such as the exact location of the mobile device 20 within a store.

[0267] In Figure 30, the store identification means 202 identifies stores located within a predetermined range based on the location information of the mobile terminal 20 obtained from the location acquisition means 213. If multiple stores are located within the predetermined range, the multiple stores may be displayed on the mobile terminal 20, prompting the member to identify one of the stores.

[0268] By using location information, it becomes easy to identify the store where a customer enters and makes a purchase.

[0269] If it is not possible to identify the designated store based on location information, the member may be prompted to enter store information.

[0270] The POS terminal 70 has a control means 701 that compares a predetermined store (the store entered) identified by the mobile terminal 20 with the store where the POS terminal is installed, and if the comparison does not match, it performs control to prohibit the settlement process.

[0271] The weighing device 30 has a control means 335 that compares a predetermined store (the store entered) identified by the mobile terminal with the store where the weighing device is installed, and if the comparison does not match, it performs control to prohibit interconnection with the mobile terminal 20.

[0272] Figure 31(A) shows an example where the mobile terminal 20 detects and displays two nearby stores, A and B, based on location information. Because there are multiple nearby stores, a screen is displayed prompting the customer to select which store to enter. If the store to enter is store A (pqr store), the customer can select the store to enter by touching its button.

[0273] Figure 31(B) shows an example of entering store information. It shows an example where a symbol code 1312 identifying the store is displayed on a display screen 1310 installed at the store entrance. By photographing the symbol code 1312 with the camera of a member's mobile device 20, the app on the mobile device 20 recognizes the symbol code 1312. The captured symbol code 1322 is displayed on the display screen of the mobile device 20. By recognizing the symbol code 1312, the app can obtain the store information to be entered. Note that the symbol code may be printed on a poster or similar and displayed at the store entrance instead of being displayed on the display 20. Members can enter the store information without having to perform cumbersome operations such as key input. Furthermore, by appropriately changing the symbol code 1312 displayed on the display 20 over time, members can take a picture of a copy of the symbol code at a location away from the store, such as their home, to enter the store. This prevents fraudulent activities such as entering the name of a store.

[0274] Figure 31(C) shows an example in which the symbol code 1324 displayed on the mobile terminal 20 is read by the camera 1332 of the imaging device 1330 installed at the entrance of the store. By having the imaging device 1330 read the symbol code 1324 displayed on the mobile terminal 20, the application on the mobile terminal 20 can obtain store information through other networks. Furthermore, by appropriately changing the symbol code 1324 displayed on the mobile terminal 20 over time, it is possible to prevent fraudulent operations such as having a copy of the symbol code displayed on the mobile terminal 20 read by the imaging device 1330.

[0275] By reading the symbol code displayed as described above, it becomes easy to identify the information of the store you are entering. Alternatively, stores that members frequently shop at can be displayed on the mobile device 20, and members can be asked to select a store to identify it.

[0276] In Figure 30, the product registration means 205 may be configured to prevent the process from proceeding to product registration until a store is identified by the store identification means 202. This is because, if the store where the product will be purchased is not determined, then, for example, the store where the registered product will be settled will not be determined. This prevents the settlement process from being performed at the wrong store. For example, in cases where multiple tenants (stores) coexist in the same building, it is important to identify the store before starting the product registration process.

[0277] Furthermore, it is desirable to perform a check during the settlement process to verify which store registered the product. This will prevent fraud, for example, such as receiving a discount service when registering at one store and then settling the payment at the discounted price at another store.

[0278] Figure 32 shows an example in which the display means 207 displays a screen 1400 on the mobile terminal 20 that allows the member to select a payment method.

[0279] Screen 1400 displays buttons such as a cash button 1402, a credit card button 1404, and an electronic money button 1406. If a member selects the cash button 1402, the member can use the mobile terminal 20 to pay in cash using a cash-handling payment processing device (such as a POS terminal 70). Methods for linking the cash-handling payment processing device and the mobile terminal 20 include having the payment processing device read a symbol code displayed on the mobile terminal 20, having the mobile terminal 20 read a symbol code displayed on the payment processing device, or bringing the mobile terminal 20 close to the payment processing device using NFC (Near Field Communication). By using such methods, the mobile terminal 20 and the payment processing device can be linked, and the member can then use the payment processing device to pay for the registered product.

[0280] If a member selects electronic payment by pressing the credit card button 1404, the electronic money button 1406, etc., the following process will be performed, for example.

[0281] The settlement means 211 in Figure 30 may operate to limit the locations where electronic payment can be made using the mobile terminal 20 to predetermined locations.

[0282] The settlement means 211 preferably obtains current location information from the location acquisition means 213 and enables the processing of electronic payments such as credit cards and electronic money only when the location of the mobile terminal 20 is a predetermined location under the supervision of a store employee. The display means 207 may control the credit card button 1404 and the electronic money button 1406 so that they can only be pressed at predetermined locations. When processing of electronic payments such as credit cards and electronic money is performed on the mobile terminal 20, it is desirable for a store employee or the store's monitoring system (not shown) to confirm whether or not the settlement has been completed. As the monitoring system, for example, confirmation may be made using the screen of the POS terminal shown in Figure 2, or the confirmation screens shown in Figures 18 and 19. Note that the screens in Figures 18 and 19 may be displayed on a simple display terminal without a settlement function. The settlement may only become possible after the store employee has confirmed that the settlement has been completed and has detected the employee's action of completing confirmation, such as pressing a button. In this case, it is preferable that the display device is a touch panel, but a (physical) keyboard mainly operated by the store employee may also be connected. The display means 207 may display a screen as shown in the pop-up 1402 of Figure 32(C), allowing the store clerk to visually confirm the completion of the electronic payment. In this way, the store clerk can reliably confirm that payment has been made before the member leaves the store with their purchased items.

[0283] If a member selects electronic payment by pressing a credit card button 1404, an electronic money button 1406, etc., the settlement means 211 obtains location information from the location acquisition means 213 and confirms that the mobile terminal 20 is in a predetermined area. If the mobile terminal 20 is not in the predetermined area, a message is displayed prompting the member to move into the predetermined area.

[0284] The pop-up 1410 in Figure 32(B) shows an example of a screen that prompts the member to move to a designated area (for example, near the credit card payment counter). At the credit card payment counter, for example, a store employee is stationed to monitor whether the payment has been successfully processed using electronic payment methods such as credit cards. The employee may also perform checks, such as matching the purchased items held by the member with the items that have been paid for. Performing these checks on a sample basis reduces the burden on the employee, and allows the member to complete the payment process quickly and leave the store.

[0285] Figure 33 shows an example of customer monitoring in a sales data processing system according to one embodiment.

[0286] The control means 201 monitors and controls location information from the location acquisition means 213 to monitor and control whether the mobile terminal 20 has left the store, for example, even though the payment for the registered products has not been completed. The control means 201 then displays a pop-up 1512 via the display means 207, as shown in Figure 33(A), prompting the member to return to the store because "payment has not been completed." Alternatively, the display means 207 may display on the mobile terminal 20 that the member has left the store and should pay using a payment method such as a credit card or electronic money.

[0287] Furthermore, as shown in Figure 33(B), the mobile terminal 20 may communicate with the POS terminal 70 operated by the store clerk, and via the display means 703 of the POS terminal 70, it may display information (1522) of members who have left the store without completing payment on the screen 1520 of the POS terminal 70 on the display unit 750 of the POS terminal 70. Alternatively, the mobile terminal 20 may display screen 1520 on another management screen (not shown) of the store. Alternatively, the host device 10 may monitor the mobile terminal 20 and display screen 1520 on the display screen (not shown) of the host device 10.

[0288] It is desirable that the member information (1522) include at least one of the following: whether payment is incomplete, the time the member left the store, the member's name (customer name), member number, a list of registered items for which payment is incomplete, the member's telephone number, and the current location of the member's mobile device 20.

[0289] -Processing flow for implementations related to store identification- Figure 34 shows an example of a specific store processing flow on a mobile terminal of a sales data processing system according to one embodiment. The following describes each step in the mobile device 20. Figure 34(A) shows the processing flow for entering a store using a mobile device.

[0290] [S1002] The current location is determined. Then, the process moves to step S1004. GPS or the like is used to obtain location information. As already explained, there are various methods other than GPS for determining the current location of the mobile terminal 20.

[0291] As already mentioned, a symbol code displayed on a mobile device can be recognized by a reader installed at the entrance of the store, thereby linking the mobile device and the reader. This linking allows the mobile device to acquire store information. Other near-field wireless communication methods, such as NFC, may also be used to identify the store.

[0292] [S1004] Based on the store's location information and the identified current location, a process is performed to identify the store. The process then moves to step S1006. [S1006] Based on the current location information, it is checked whether the store can be identified. If this check is positive (yes), the process moves to step S1014. If this check is negative (no), the process moves to step S1008.

[0293] [S1008] The system checks whether multiple stores exist as candidates based on the current location information. If this check is positive (yes), the process moves to step S1010. If this check is negative (no), the process moves to step S1012.

[0294] [S1010] Since there are multiple store options, the user (member) is prompted to select a store, and the user's selection is accepted. The process then moves to step S1014.

[0295] [S1012] The mobile terminal 20 reads, for example, a symbol code located at the entrance of a store. The symbol code contains information including store information. Based on this store information, the store can be identified. Note that the process of making the mobile terminal 20 recognize a store is not limited to this process. As already mentioned, stores can be identified by various methods at the instruction of the member. The process then moves to step S1014. [S1014] The previously blocked transition to product registration processing is released. From this point onward, members can register purchased products using their mobile terminal 20 within the store. It is desirable that a shopping basket for the member be generated in the store's system when the member enters the store. Products registered by the member should be added to the shopping basket.

[0296] Figure 34(B) shows the processing flow when a mobile device is used for payment or when purchasing goods sold by weight. [S1022] This process is executed via interrupt when the system transitions to settlement processing or when interconnection with the weighing device is instructed. Further details regarding the interconnection between the mobile terminal and the weighing device will be described later. The process proceeds to step S1024. [S1024] In this case, a determination is made as to whether the store information held by the payment device or weighing device matches the store entry information on the mobile terminal. If this determination is affirmative (yes), the stores match, and the process is complete. If this judgment is negative (no), the process proceeds to step S1026. [S1026] Normally, members with mobile devices would pay at the store they enter. Furthermore, they will likely use the weighing equipment provided by the store they enter.

[0297] However, it is conceivable that a member might leave a store and enter another store to make a payment or use the weighing equipment at another store. In this case, the payment at another store and the purchase of weighed goods at another store would require complex processing at the store, as it would involve adjusting sales calculations and inventory management between stores during the payment process.

[0298] Therefore, a simple solution would be to uniformly prohibit customers from making payments at a different store than the one they entered, or from using weighing devices at other stores. As mentioned above, it would be desirable to not allow payments at other stores and not allow interconnection between weighing devices and mobile terminals. This would prohibit members from making payments at other stores, or prevent them from using weighing devices. This measure would avoid the inconveniences described above.

[0299] An example of "exception handling" is to process the payment as if the item were handled by the store where the current payment device is installed, regardless of location information. Alternatively, the mobile terminal and the weighing device may be interconnected, and the item may be registered on the mobile terminal as a product of the store linked to the weighing device. The payment device may then process the payment as if the item were a product of the store linked to the weighing device. In the case of the above exceptions, it is desirable to perform a process for each store to adjust for the discrepancy between theoretical and actual inventory levels between inventory and sales figures.

[0300] Figure 35 shows an example of the settlement processing flow on a mobile terminal of a sales data processing system according to one embodiment. The processing flow is described below.

[0301] [S1102] The member makes a declaration that settlement will be made by electronic payment using the mobile terminal 20. Examples of electronic payment include, but are not limited to, credit card payments and electronic money payments. The process proceeds to step S1104.

[0302] [S1104] The current location is identified. This current location is the location of the mobile device 20, which is the current location of the member. The process proceeds to step S1106.

[0303] [S1106] It is checked whether the current location is within the first area. Examples of the first area include the vicinity of the counter where a store employee is present, and the vicinity of the credit card payment desk where a store employee is present. In these locations, store employees can monitor the electronic payment of members using the mobile terminal 20. In addition, store employees can easily verify the purchased items. If this check is positive (yes), the process moves to step S1110. If this check is negative (no), the process moves to step S1108.

[0304] [S1108] Since the member possessing the mobile terminal 20 is outside the first area, for example, the display screen of the mobile terminal 20 will prompt the member to enter the first area. The display may also show the route within the store to the first area to guide the member (not shown). The process returns to step S1104. [S1110] Since the member is located within the first area, electronic payment processing is performed using the mobile terminal 20.

[0305] Figure 36 shows an example of a processing flow related to customer monitoring on a mobile terminal of a sales data processing system according to one embodiment. The details of the processing flow are described below. The following processes should ideally be initiated via interrupt handling or similar methods.

[0306] [S1200] This process is initiated periodically by an interrupt, or when a "specific process on the mobile terminal" is performed. Here, "specific process on the mobile terminal" refers to the following processes, for example. (1) Process to display a payment QR code on a mobile device for scanning at a POS terminal to process payment. (2) Processing when an instruction to proceed to the subplanning area is given, in cases where the system has the function to display the subplanning area. (3) Proceed to payment by credit card, electronic money, etc. Processing when an indication is made (4) Processing when an instruction is given to cancel all registered products. (5) Processing when an instruction is given to establish mutual communication with a weighing device, etc. When the above process is performed, it is a crucial moment in the shopping process, so it is advisable to perform the following steps. [S1202] The current location of the mobile terminal 20 is determined. The process proceeds to step S1204.

[0307] [S1204] It is checked whether the current location of the mobile terminal 20 is outside the second area (for example, outside the store). If this check is positive (yes), the process moves to step S1206. If this check is negative (no), the process ends.

[0308] [S1206] The mobile terminal 20 checks whether the payment for the registered items has been completed. If this check is positive (yes), the process ends. If this check is negative (no), the process moves to step S1208.

[0309] [S1208] It is discovered that the member carrying the mobile terminal 20 has left the store even though the payment has not been completed. Therefore, information about the member is displayed to the store staff. An example of what is displayed is as previously explained. The member is also notified (displayed) on the screen of the mobile terminal 20, for example, to return to the store. An example of this notification (display) is as previously explained. Alternatively, based on the acquired location information, the store can be identified again, and if it is found that the mobile terminal is in a different store, the member's current store can be re-registered. In this case, a new shopping basket for the re-registered store can be created, and the previously created shopping basket can be put on hold. Alternatively, since the member is outside the store, the system can return to the initial screen for identifying the store. This process will make it easier to properly address the needs of members whose settlements have not yet been completed. The process is now complete.

[0310] -An embodiment relating to the linkage between a weighing device and a mobile terminal-

[0311] Returning to Figure 30, the product type acquisition means 203a in Figure 30 acquires the type of bulk product that a member intends to purchase, for example, via a mobile terminal or the like. The weighing value acquisition means 203b acquires the weighing value of the acquired bulk product from the weighing device 30.

[0312] For products that need to be weighed, a unit price (price per kg, price per item, etc.) is pre-set for each product type. If a member knows the product type and weight of the weighed product they are purchasing, the price of that product can be calculated by using the unit price for that product type. To register a product and calculate its price, the product type and its weight are retrieved. The product registration means 205 can register products sold by weight using the product type and its weighed value.

[0313] It is desirable that the display means 207 display the product type in a manner that indicates that a weighing value has not been acquired until the weighing value acquisition means 203b acquires a weighing value corresponding to the product type. Alternatively, it may notify the user to weigh the product of the product type.

[0314] Furthermore, it is desirable that the settlement means 211 of the mobile terminal 20 prohibits proceeding to settlement processing once the type of weighed product is acquired, and lifts the prohibition on proceeding to settlement processing once the corresponding weighed value is acquired. This is because it is desirable not to proceed to settlement processing until the weighed value is acquired, as the price of the weighed product cannot be determined until then.

[0315] Figure 37 shows an example of using a mobile terminal 20 to obtain the type of bulk product that a member wishes to purchase. In Figure 37, lemons 3002, apples 3004, and oranges 3006 are displayed, and signs 3012, 3014, and 3016, each with a display, are placed behind each bulk product.

[0316] For example, sign 3012 displays the word "lemon," the unit price is per kilogram, and the unit price is nn yen. A barcode 3013a is also displayed so that the mobile terminal 20 can optically read this information. These displays may also be displayed printed on paper or other materials. Furthermore, using a display allows for quick adjustment of discounts, such as those offered during limited-time sales. Additionally, by changing the barcode at predetermined intervals, it is possible to prevent fraud, such as registering bulk products at different unit prices, by having the mobile terminal 20 read barcodes that have been previously photographed with a camera.

[0317] Figure 37 shows that the mobile terminal 20 is equipped with a camera, and the detection means 204 has read the barcode 3013b of the lemon 3002. In the second display area, one yogurt priced at 160 yen is already registered 3050. Also, an apple has been read 3040, and a "weighing required" indication 3041 and a price of ?? yen 3042 are displayed.

[0318] Similarly, lemons have been read, with the value 3030, the indication that weighing is required 3031, and the price of ?? yen 3042 displayed. The subtotal column 3020 shows that there is one officially registered item, its estimated total is 160 yen, and a button to proceed to checkout is displayed. Since the weighing values ​​for lemons and apples have not been obtained, the indications that weighing is required 3041 and 3031 are displayed, prompting the member to weigh them. Also, since weighing has not been performed, the price of ?? yen is displayed. Furthermore, the columns 3030 and 3040 for weighed items that have not been weighed are shaded, making it clear to the member that weighing values ​​have not been performed. Returning to Figure 30, the weighing device 30 has an instruction receiving means 331 that also serves as a display function and a communication means 333, both of which are controlled by a control means 335.

[0319] The communication means 333 communicates with the communication means 215 of the mobile terminal 20. The instruction receiving means 331 may be, for example, a display device having a touch panel. The instruction receiving means 331 displays symbol codes, messages, buttons, etc., and can receive various instructions by touching the screen. Although not shown in the weighing values ​​in Figure 30, it is desirable that the weighing device be equipped with a printer, a short-range wireless device (Bluetooth, NFC, etc.), a weighing function, a platform for placing the items to be weighed, and a reader for reading symbol codes.

[0320] The symbol code displayed on the weighing device 30 is read by the mobile terminal 20, thereby linking it to the mobile terminal. Alternatively, the weighing device 30 and the mobile terminal 20 may be linked when the reader on the weighing device 30 reads the symbol code displayed on the mobile terminal 20. Once linked, the mobile terminal 20 and the weighing device 30 can exclusively communicate with each other using short-range wireless communication such as Bluetooth, and exchange information.

[0321] Furthermore, the communication means 215 of the mobile terminal 20 may be configured to control the weighing device 30 via the communication means 333 using established mutual communication such as Bluetooth.

[0322] Furthermore, the instruction receiving means 331 of the weighing device 30 may, when it detects that a customer who is not using a mobile terminal 20 has declared their intention to use the weighing device 30, or when goods are placed on the platform, prohibit the establishment of communication with the mobile terminal 20, so that weighing can be carried out smoothly, and then, for example, when label printing is finished, it may operate to release this prohibition.

[0323] Figure 38 shows the weighing device 30. The display area shows the initial screen 4053a of the weighing device. The initial screen 4053b is an enlarged view of this screen. The initial screen 4053b displays a display area 4055 showing the symbol code used to establish communication with a mobile terminal, and an area 4057 which serves as both an explanatory screen and a touch area for when the weighing device is used without a mobile terminal. If a customer wishes to use the weighing device without using a mobile device, they can either touch the display area 4057 or place the product on the weighing platform 4062. The weighing device 30 includes a printed label output port 4060 and a symbol code reading unit 4061. The reading unit 4061 can, for example, read symbol codes displayed on a mobile device. Figure 39 shows the configuration of interconnection between the mobile terminal 20 and the weighing device 30.

[0324] Figure 39(A) shows how the camera of the mobile terminal 20 reads the symbol code 4056a displayed on the weighing device 30. The captured symbol code 4056b is displayed on the screen of the mobile terminal 20.

[0325] The detection means 204 of the mobile terminal 20 analyzes the symbol code and obtains the information necessary for mutual communication. Using this information, the communication means 215 of the mobile terminal 20 and the communication means 333 of the weighing device 30 can establish mutual communication using short-range wireless communication such as Bluetooth. Alternatively, mutual communication may be established by the reading unit 4061 of the weighing device 30 reading the symbol code displayed on the mobile terminal 20, or by obtaining the information necessary for mutual communication using NFC. After mutual communication is established, in addition to short-range wireless communication such as Bluetooth, other wireless communication such as Wi-Fi, optical communication, and wide-area communication networks of mobile phones may be used in combination.

[0326] Figure 39(B) shows the situation when mutual communication is established and the information of the weighed goods registered by the mobile terminal 20 is transferred to the weighing device. It goes without saying that the information of the weighed goods registered by the mobile terminal 20 may be transmitted directly from the mobile terminal 20 to the weighing device 30 via mutual communication, but it may also be transmitted to the weighing device 30 via other devices such as the communication-connected POS terminal 70, the host device 10, or a server device (not shown).

[0327] In Figure 39(C), the display information 4060a of the weighing device 30 is shown prominently in the display information 4060b. As shown in Figure 39(B), the same display information 4060c may also be displayed on the screen of the mobile terminal 20. By displaying the display information 4060c of the weighing device 30 on the mobile terminal 20 in this way, members can give instructions to the weighing device 30 from the mobile terminal 20. Needless to say, the mobile terminal 20 may also display the product registration screen instead of showing such a screen.

[0328] As shown in the display information 4060b in Figure 39(C), buttons 4063 for apples and 4065 for lemons, which are weighed products for which weighed values ​​have not yet been obtained, are displayed. The reason these two weighed products are displayed is that, in Figure 37, the barcodes of the apples and lemons were read, and the product types were obtained by the camera of the mobile terminal 20. To encourage the member to select products and weigh the apples and lemons they have, the message "Please select products and place them on the table" is displayed.

[0329] Additionally, a button 4066 to cancel weighing and a button 4067 to search for items sold by weight, which can be used if you want to weigh items that are not currently displayed, are also shown.

[0330] Figure 40 shows the process of obtaining the weighed value of a product sold by weight. In Figure 40(A), the member first touches the apple button 4063 on the display information 4060d. The apple button 4063 on the weighing device screen is highlighted because the member's finger 3100 touches it. This operation causes the instruction receiving means 331 of the weighing device 30 to detect that an apple is being weighed. The display information then shows that the unit price of the apple is 360.00 yen / kg. This unit price can be obtained in advance by the weighing device, for example, from the store's product master, or it can be obtained from the product master in response to the member selecting apples as a product sold by weight and then displayed.

[0331] Figure 40(B) shows the display information 4070a of the weighing device 30. The enlarged display information 4070b shows the message "Please place the product" 4073, prompting the member to place the apple on the platform 4062. An image of an apple 4075 is also displayed for the member's understanding. The back button 4077 is a command button that returns to the previous screen and displays the previous display information. In response to this indication, the member is attempting to place apple 3080 onto platform 4062 using finger 3100.

[0332] Figure 41 shows the weighing process. In Figure 41a, apple 3080a is placed on the platform 4062, so the display information 4090a (4090b) shows that the weighed weight is 1.2006 kg, the unit price is 360.00 yen, and based on the weighed weight and unit price, the total price of the apples is 432 yen. The total price can be calculated by rounding down the decimal part, for example.

[0333] Display information 4090b shows the label print command button 4093. It is desirable that the print command button 4093 only be displayed when the product is placed on the scale and the weighing value stabilizes. Alternatively, the print command button 4093 may be dimmed until the weighing value stabilizes, and pressing it will not print. Once the weighing value stabilizes, it may light up and printing will occur when pressed. In addition, a message "Please press the print button" is displayed. After confirming that their operation is correct, the member touches the print command button 4093 with their finger 3100.

[0334] Figure 41(B) shows the display information 4095 after the print command button 4093 is touched. The display information 4095 provides a notification prompting the user to attach the label 4097 to the product bag 4081 once it has been printed from the weighing device 30a. Note that the label may not be printed. Also, the label may not have a symbol code containing information about the weighed value printed on it. It is desirable that the product type and weighed value be transferred from the communication means 333 of the weighing device 30 to the mobile terminal 30 via the communication means 215 of the mobile terminal using two-way communication. Alternatively, the weighing device 30 may transmit the product type and weighed value via a communication line so that it is stored in the member's basket on another higher-level device in the store.

[0335] Figure 42 shows the display information 4060e of the weighing device 30 after the weighing value has been acquired and its operation. As shown in Figure 42(A), the apple display has disappeared from area 4063a. This is because the weighing value of the apple has already been acquired and the label has been printed out, so there is no need to display the apple.

[0336] Figure 42(B) shows an example where the member's finger 3100 touches the button 4066 to cancel weighing. The display information 4060f still shows lemon 4065a, so the member is required to weigh the lemons, but even in this situation, the member can cancel the weighing at their own discretion. Figure 43 shows the display information of the weighing device 30 and the portable terminal 20 when weighing is stopped or completed.

[0337] As shown in Figure 43(A), the screen of the weighing device 30 displays the initial display information 4053c. This allows other members to interconnect with their mobile terminals 20. It also allows customers without mobile phones to use the weighing device 30.

[0338] Figure 43(B) shows the display on the mobile terminal 20. Since the weighing of the apples has been completed and the mobile terminal 20 has acquired the weighed value of the apples, the apple display field 3040a has changed from a shaded display to a normal display. Also, the display at position 3041a, where the number is normally displayed, has changed from "Requires weighing" to "Weighed". This display indicates that apples are an item that needs to be weighed. This change in display allows the member to confirm that the apples they intend to purchase have been successfully registered. In contrast, the lemon display field 3030 has not changed because it has not been weighed. Since it is still shaded, it can be seen that it is being treated the same as the pending item mentioned earlier. In this embodiment, items for which the weighed value has not been acquired can be treated the same as pending items. In the estimated total field 3020, the price of the apples, 432 yen, has been added to 160 yen, and the amount 3021a has changed to 592 yen.

[0339] Return to Figure 30. The registration means 205 of the mobile terminal 20 may be configured to only accept changes to the number of items to be weighed, i.e., to set the number to zero (i.e., equivalent to canceling the registration), when an instruction is given to change the number of items to be weighed. This is because it is not assumed that there will be multiple items of the same weight when receiving and weighing items.

[0340] Furthermore, there are products sold by the piece, such as apples, where the weighing device calculates the number of apples based on their total weight. In some cases, the weighing device may register apples at 150 yen for one apple and 450 yen for three apples, and then issue a label. In this case, it may be possible to change the quantity to two or more. (In the case of such products, it may be possible to register apples by having the member read the product type code for apples using a mobile terminal, as shown in Figure 37, and then inputting the quantity (the weighing device 30 may not be used at all). In this case as well, the weighing device 30 may calculate the number of apples, print a label, and transmit the quantity based on the weighed value to the mobile terminal 20 or a higher-level device.

[0341] Furthermore, if there are elements of a counting scale, for example, if candy is sold individually at 5 yen per piece and it's common to buy 20 or 30 pieces, it would be very difficult for members to actually count them. Therefore, the number of pieces is calculated from the unit weight of the candy and the weighed value. In the case of such products, it may be made mandatory to use the weighing device 30. In this case, it is desirable that this number cannot be changed and can only be canceled. Alternatively, the quantity can only be changed within an upper and lower limit (for example, an error of ±1 piece per 20 pieces), and registered products can only be canceled.

[0342] Figure 44 shows the process for canceling the registration of products to be weighed. Figure 44(A) shows a member's finger 3100 touching the button 3041b labeled "Weigh" in order to change the quantity of apples.

[0343] Figure 44(B) shows the subsequent pop-up display 3043 and notification display 3110. The pop-up display 3043 displays the product cancellation button 3044. If the quantity of the product can be changed, buttons 820a and 820b for instructing to increase or decrease the quantity will be displayed, as shown in Figure 11(a). Figure 44(B) is a display similar to the pop-up display 821 in Figure 11(b). In Figure 44(B), the product cancellation button is touched by the member's finger 3100. When this operation is performed, the notification display 3110 is displayed. This display prompts the member to put the apple into the hold basket. The cancellation operation can be canceled by pressing the back button 3114. The OK button 3112 is a button that informs the mobile terminal 20 that the member has accepted this action. The member puts the apple into the hold basket. Note that the hold basket is just an example and should be distinguishable from other registered products. Alternatively, a notification could be issued instructing customers to return the products to their shelves.

[0344] Figure 44(C) shows the display on the mobile terminal 20 after the member touches the OK button 3112. Since the registration of the apple has been canceled, a strikethrough line 3045 is displayed, and the price of the apple has changed to 0 yen 3042a. The estimated total amount 3021a has also changed to 160 yen, reflecting the cancellation of the apple. Note that the strikethrough line 3042a is just one example to make it clear that the cancellation has taken place, and the display field for the apple itself may be erased. Alternatively, the mobile terminal 20 may not perform the cancellation, but instead indicate that an instruction to cancel has been given. In this case as well, the item may continue to be treated as a pending item, and a display regarding pending items 3110 may be shown to prompt the member to add the item to the pending basket. Figure 45 illustrates the situation when a customer is instructed to proceed with settlement (accounting) when there are items for which the weighing value has not been obtained.

[0345] Figure 45(A) shows what happens when the member presses the button 3108 to proceed to checkout when there are items for which the weighing value has not yet been obtained. In response to this instruction, the mobile terminal 20 displays a message 3110 regarding the held items. It then prompts the member to place the lemons, for which the weighing value has not yet been obtained, into the held basket. The member then touches the OK button 3110a. Note that if the weighing values ​​for all types of items to be weighed have been obtained, the message 3110a regarding the held items will not be displayed. In this case, the prohibition on proceeding to checkout is lifted, and the member can proceed to checkout.

[0346] Figure 45(B) shows the display screen of the mobile terminal 20 after the OK button 3110a is touched. A strikethrough line 3035 is displayed for the lemon, for which no measurement value has been acquired.

[0347] Products with a strikethrough like this can be treated the same way as reserved products as previously explained. Furthermore, when displaying reserved products (3110), a notification to call a store employee may also be issued. Alternatively, a notification to call a store employee may be issued without displaying reserved products (3110).

[0348] Figure 46 is a flowchart illustrating the coordinated operation between the mobile terminal 20 and the weighing device 30. The details of this flowchart are explained below. [S2002] The mobile terminal 30 reads the symbol code of the weighed product. Through this operation, the mobile terminal obtains the type of the weighed product. The obtained product type is registered in the mobile terminal and displayed on the screen. At this stage, the weighed value of the weighed product has not been obtained, so proceeding to the settlement process is prohibited. However, the member operating the mobile terminal may be allowed to press the button to proceed to checkout. In this case, as explained earlier, the member should be prompted to put the product for which the weighed value has not been obtained into the holding basket. Also, as shown in Figure 39, it is desirable to notify the member to obtain the weighed value by issuing a "Weighing Required" notification. The process then moves to step S2004.

[0349] [S2004] The system checks whether the process of obtaining the type has been completed. This check results in a positive judgment (yes) for example, if the button to proceed to accounting is pressed. In this case, the system proceeds to step S2006. Otherwise, a negative judgment (no) is automatically made, and the system returns to step S2002.

[0350] [S2006] Information for mutual communication with the weighing device is acquired. That is, the symbol code of the weighing device is read by the mobile terminal 20. Alternatively, the mobile terminal may acquire connection information by connecting via NFC, or by the weighing device reading the symbol code displayed on the mobile terminal. The process then moves to step S2008.

[0351] [S2008] Mutual communication is established between the weighing device and the mobile terminal 20. Short-range wireless communication such as Bluetooth is monopolized by the mobile terminal 20 and the weighing device 30. The process moves to step S2010.

[0352] [S2010] The customer operates the weighing device and the weighed value is obtained. Alternatively, the weighing device may obtain the weighed value in response to an operation by the customer using the mobile terminal 20, using a mobile terminal with which two-way communication has been established. The mobile terminal 20 obtains the weighed value from the weighing device 30 and registers it. The mobile terminal 20 may change the display of the column for the product for which the weighed value has been obtained so that it is clear that the weighed value has been obtained. It may also calculate the price from the weighed value and the unit price and display the price. The process moves to step S2012.

[0353] [S2012] It is checked whether the weighed values ​​for all product types to be weighed have been obtained. If this check is negative (no), the process returns to step S2010. If this check is positive (yes), the process moves to step S2014. [S2014] The ban on transitioning to settlement processing is lifted. Communication between the two parties is then disconnected. This completes the coordinated operation between the weighing device 30 and the mobile terminal 30.

[0354] Figure 47 is a flowchart showing the operation when there are registered products for which weighing values ​​have not been obtained. Figure 47(A) shows the process that is started by interruption when an instruction is received to proceed to accounting, or when an instruction is received to cancel the weighing of a product.

[0355] [S2102] Settlement is requested (the button to proceed to accounting is pressed), and the mobile terminal 20 determines whether all weighing values ​​corresponding to the type of goods acquired have been obtained. If this determination is positive (yes), the process proceeds to step S2106. If this determination is negative (no), the process proceeds to step S2104.

[0356] [S2104] The mobile terminal notifies the user to place items for which the weighing value has not been obtained into the hold basket. Since the "Proceed to Checkout" button has been pressed, the terminal notifies the user to place all items for which the weighing value has not been obtained into the hold basket. The process proceeds to step S2106.

[0357] [S2106] It is determined whether there was an instruction to cancel the weighing of the goods. If this determination is affirmative (yes), the process proceeds to step S2108. If this determination is negative (no), the process ends.

[0358] [S2108] Notification (A) is issued prompting the user to add the item that has been instructed to be canceled to the hold basket. The processing of notification (A) is carried out as shown in Figure 47(B). Figure 47(B) shows that the process is initiated by an interrupt when the above notification (A) is given.

[0359] [S2112] The mobile terminal 20 determines whether the OK button has been pressed. The OK button is, for example, the OK button 3110 in Figure 44(B), and is pressed when the member agrees to place items for which the weighing value has not been obtained into the holding basket. If this determination is positive (yes), the process moves to step S2114. If this determination is negative (no), the process moves to step S2116.

[0360] [S2114] The mobile terminal 20 cancels the notification and makes changes to the display, such as by striking through it. Then, it sets the price of the canceled item to 0, recalculates the total amount, and updates the display.

[0361] [S2116] For example, if no operation is performed after a certain period of time, it is desirable to notify a store employee. This notification is transmitted from the mobile terminal to a higher-level device, such as a POS terminal, and calls a store employee. The called employee then performs the verification. The above describes the operation flow of the mobile terminal 20 when the acquisition of measured values ​​is not yet complete. Figure 48 is a flowchart showing the operation of displaying registration information and the operation of changing registration information on the mobile terminal 20.

[0362] Figure 48(A) is a flowchart showing the operation of displaying registration information on the mobile terminal 20. [S2202] The mobile terminal determines whether the registered product is a product whose price varies by weight or a product sold by weight. If this determination is positive (yes), the process moves to step S2206. If this determination is negative (no), the process moves to step S2204. [S2204] Mobile terminal 20 displays the quantity in the quantity display field based on the member's instructions. Processing is completed. [S2206] Because the registered product information indicates that the price varies depending on the weight, or that the product is sold by weight, the mobile device displays information other than the quantity in the quantity display field. Figure 48(B) is a flowchart showing the operation for changing the registration information of the mobile terminal 20.

[0363] [S2210] The mobile terminal determines whether the registered product information indicates that the price varies by weight or that the product is sold by weight. If this determination is positive (yes), the process moves to step S2214. If this determination is negative (no), the process moves to step S2212. [S2212] The mobile terminal 20 displays the change in quantity according to the instruction to change the quantity and processes the change to reflect it.

[0364] [S2214] Because the registered product information indicates that the price varies depending on the weight, or that the product is sold by weight, the mobile terminal 20 only accepts instructions to change the quantity to zero, i.e., a deletion instruction. The process proceeds to step S2216.

[0365] [S2216] In the case of a deletion instruction, the mobile device will display a message indicating that the item has been deleted, prompt the user to place the deleted item in a specific location, and notify the user to call a store employee if necessary. The process will then be completed. Figure 49 is a flowchart showing the operation of the weighing device in manual mode, that is, when the customer uses the weighing device without using the mobile terminal 20.

[0366] [S2302] The weighing device determines whether a product has been placed on the weighing device's platform or whether it has detected a declaration from the customer that they will use the weighing device without a mobile terminal. An example of such a declaration is when the device detects that the customer has touched the display area 4057 in Figure 38. If this determination is positive (yes), the process moves to step S2304. If this determination is negative (no), the process ends.

[0367] [S2304] The weighing device prohibits the mobile terminal from establishing mutual communication with the weighing device. This is because if the mobile terminal 20 attempts to connect with the weighing device 30 while the customer is operating the weighing device, it may interfere with the customer's operation. An example of how this mutual communication is prohibited is to prevent the display of symbol code 4056 in Figure 38. The process proceeds to step S2306.

[0368] [S2306] The weighing device determines whether the customer has finished using the weighing device. If this determination is positive (yes), the process moves to step S2308. If this determination is negative (no), this step S2306 is repeated. [S2308] Since the customer has finished using the weighing device, the prohibition on establishing mutual communication is lifted for the weighing device.

[0369] Figure 50 is a flowchart of the operation of a POS terminal. The POS terminal can be of any type, such as a self-service POS terminal operated by the member themselves or a POS terminal operated by a store employee. As described in step S2400, the POS terminal can perform the following operations. In other words, a POS terminal (payment device) is, • Registered but unweighed products sold by weight • Products whose registration as bulk-sold items has been cancelled. • Products whose prices vary by weight have been removed from the listing. These items will be handled in the same way as reserved items. The handling of pending items has already been described in detail.

[0370] For registered but unweighed items sold by weight, the weighing device connected to the POS terminal should be used to obtain the weighed value.

[0371] The steps of each processing flow in this embodiment may be performed in any order, as long as they do not conflict, and may also be performed simultaneously, as long as they do not conflict. Furthermore, the embodiments described herein are not mutually exclusive, and parts or all of one embodiment can be appropriately combined with other embodiments. [Explanation of symbols]

[0372] 10: Higher-level device 20: Mobile devices 201: Control means 202: Store Identification Methods 203 :Acquisition means 204: Detection means 205: Product Registration Method 206: Method for registering reserved items 207:Display means 208: Notification methods 209: Output means 210: Method for canceling registered products 211: Payment method 213: Location acquisition means 215: Means of communication 331: Instruction receiving means 333: Means of communication 335: Control means 60: Store Controller 70: POS terminal 700: Control Unit 701: Control means 702: Input means 703:Display means 704: Payment method 705: Notification methods 706: Editing methods 707: Prohibited means 750:Display section 760: Input section 770: Printing Department

Claims

1. A sales management system including mobile devices, A location tracking method for determining the current location of a mobile device, A store identification means that identifies a predetermined store for settling registered goods based on the current location of the mobile terminal identified by the location identification means, After the predetermined store is identified by the store identification means, an acquisition means is provided to acquire product information by reading a barcode at the store. A product registration means that performs a product registration process based on the product information obtained by the acquisition means, Equipped with, The store identification means, when multiple stores are detected as candidates based on the current location of the identified mobile terminal, displays an option to select one of the multiple stores as the predetermined store. A sales management system characterized by the following features.

2. A sales management system including a mobile terminal, A location tracking method for determining the current location of a mobile device, A store identification means that identifies a predetermined store for settling registered goods based on the current location of the mobile terminal identified by the location identification means, After the predetermined store is identified by the store identification means, an acquisition means is provided to acquire product information by reading a barcode at the store. A product registration means that performs a product registration process based on the product information obtained by the acquisition means, Equipped with, The store identification means, when multiple stores are detected as candidates based on the current location of the identified mobile terminal, prompts the user to identify one of the multiple stores as the predetermined store, and when the predetermined store cannot be identified based on the current location of the identified mobile terminal, prompts the user to read code information for identifying the store. A sales management system characterized by the following features.

3. A means for determining the current position of the device, A store identification means that identifies a predetermined store for settling the payment for registered goods based on the current location of the device identified by the location identification means, After the predetermined store is identified by the store identification means, an acquisition means is provided to acquire product information by reading a barcode at the store. A product registration means that performs a product registration process based on the product information obtained by the acquisition means, Equipped with, If the store identification means detects multiple stores as candidates based on the current location of the identified device, it will display options for selecting one of the multiple stores as the predetermined store. A mobile device characterized by the following features.

4. A positioning means for determining the current position of the device, A store identification means that identifies a predetermined store for settling the payment for registered goods based on the current location of the device identified by the location identification means, After the predetermined store is identified by the store identification means, an acquisition means is provided to acquire product information by reading a barcode at the store. A product registration means that performs a product registration process based on the product information obtained by the acquisition means, Equipped with, The store identification means, when multiple stores are detected as candidates based on the current location of the identified device, prompts the user to identify one of the multiple stores as the predetermined store, and when the predetermined store cannot be identified based on the current location of the identified device, prompts the user to read code information for identifying the store. A mobile device characterized by the following features.

5. A program that controls a mobile device, A computer on a mobile device, A means for determining the current position of the device itself. A store identification means that identifies a predetermined store for settling the payment for registered goods based on the current location of the device identified by the location identification means. After the predetermined store has been identified by the store identification means, an acquisition means obtains product information by reading a barcode at the store. Product registration means that performs product registration processing based on the product information obtained by the acquisition means, To make it function as, If the store identification means detects multiple stores as candidates based on the current location of the identified device, it will display options for selecting one of the multiple stores as the predetermined store. A program characterized by the following features.

6. A program for controlling a mobile terminal, A computer on a mobile device, A means for determining the current position of the device itself. A store identification means that identifies a predetermined store for settling the payment for registered goods based on the current location of the device identified by the location identification means. After the predetermined store has been identified by the store identification means, an acquisition means obtains product information by reading a barcode at the store. Product registration means that performs product registration processing based on the product information obtained by the acquisition means, To make it function as, The store identification means, when multiple stores are detected as candidates based on the current location of the identified device, prompts the user to identify one of the multiple stores as the predetermined store, and when the predetermined store cannot be identified based on the current location of the identified device, prompts the user to read code information for identifying the store. A program characterized by the following features.

7. Furthermore, the computer on the mobile device, A display means for displaying code information for settling the payment for products registered by the aforementioned product registration means. The program according to claim 5 or 6, characterized in that it functions as such.

Images