JP7672015B2 - Sales System - Google Patents

Description

The present invention relates to a sales system.

A sales system has been introduced in stores that allows customers to register products themselves by operating their own mobile terminal devices (see, for example, Patent Document 1).

Patent No. 5056161

A weighing device is used to sell products sold by weight. In a sales area that uses a weighing device in the above-mentioned sales system, the weighing device is used to price the product that the customer wishes to purchase, and the product is then registered on the customer's mobile terminal device. This is a different procedure from when a customer registers a product by taking it off a shelf, etc., and having the mobile terminal device read the code on the product.

The present invention was made in consideration of these circumstances, and aims to facilitate smooth product registration in a sales system in which product registration is performed using a mobile terminal device carried by a customer.

One aspect of the present invention that solves the above-mentioned problems is a sales system that includes a weighing and pricing device and a portable terminal device that customers use to register products, and that includes an output means that outputs connection information for connecting the weighing and pricing device and the portable terminal device so that they can communicate with each other, and a control means that, after outputting the connection information, ends the output of the connection information by the output means at a predetermined timing after the weighing and pricing device and the portable terminal device are connected so that they can communicate with each other.

Another aspect of the present invention is a sales system that includes a weighing and pricing device and a portable terminal device that customers use to register products, and that includes an output means that outputs connection information for connecting the weighing and pricing device and the portable terminal device so that they can communicate with each other, and a control means that causes the output means to output the connection information at a predetermined timing when the weighing and pricing device and the portable terminal device are not connected so that they can communicate with each other.

1 is a diagram showing an example of an outline of a store in which a weighing and pricing device in a sales system according to a first embodiment is used; 1 is a diagram illustrating an example of the configuration of a sales system according to a first embodiment. FIG. 1 is a diagram illustrating an example of the configuration of a weighing pricing device according to a first embodiment. 1 is a perspective view showing an example of the appearance of a weighing and pricing device according to a first embodiment; 1 is a diagram showing an example of the appearance of a settlement device according to a first embodiment; FIG. 2 is a diagram illustrating an example of the configuration of a settlement device according to the first embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a mobile terminal device according to the first embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a transaction management server according to the first embodiment. 4A to 4C are diagrams illustrating an example of customer information, store information, and cart information according to the first embodiment. 5A to 5C are diagrams illustrating examples of a start-up screen, a nearby store guide screen, and a store information screen according to the first embodiment. 5A to 5C are diagrams illustrating examples of an advertisement screen, a product registration screen, and a payment guidance screen according to the first embodiment. 4 is a flowchart showing an example of a processing procedure executed by the weighing and pricing device, the mobile terminal device, and the transaction management server according to the first embodiment in relation to product registration in one transaction. 13A and 13B are diagrams illustrating an example of a display form of a connection information code screen according to the first embodiment. FIG. 2 is a diagram showing an example of a single label according to the first embodiment. 10 is a flowchart showing an example of a processing procedure executed by the weighing pricing device according to the second embodiment in response to pricing in one transaction. FIG. 11 is a diagram showing an example of a connection necessity confirmation screen according to the second embodiment; FIG. 11 is a diagram showing an example of an issuance confirmation screen according to the second embodiment. 13 is a flowchart showing an example of a processing procedure executed by the weighing pricing device according to the third embodiment in response to pricing in one transaction. FIG. 13 is a diagram showing an example of a code information reading guide screen according to the third embodiment. FIG. 13 is a diagram showing an example of an additive label according to the fourth embodiment. FIG. 13 is a diagram illustrating an example of the configuration of a sales system according to a fifth embodiment. A sequence diagram showing an example of processing procedures executed by a weighing pricing device, a mobile terminal device, a transaction management server, and a weighing sales management server in the fifth embodiment in relation to product registration in one transaction. FIG. 13 is a diagram showing an example of a display form of a store clerk button according to a fourth modified example of the embodiment. FIG. 13 is a diagram showing an example of a display form of a connection information code screen according to a fourth modified example of the embodiment. A figure showing an example of how products sold by weight are displayed in a store related to the sixth embodiment. FIG. 13 is a diagram showing an example of the appearance of a weighing and pricing device according to a sixth embodiment, as viewed from the front. 23A to 23D are diagrams showing a procedure for reading a connection information code according to the sixth embodiment and an example of a pricing operation screen. FIG. 23 is a diagram illustrating an example of a procedure that a customer follows in response to a price determination for one product in the sixth embodiment. FIG. 23 is a diagram illustrating an example of a procedure that a customer follows in response to a price determination for one product in the sixth embodiment. 23A and 23B are diagrams showing examples of a pricing operation screen and a product registration screen according to the sixth embodiment. 13 is a flowchart showing an example of a processing procedure executed by a weighing pricing device, a mobile terminal device, and a transaction management server according to the sixth embodiment in relation to the registration of products sold by weight in one transaction. FIG. 23 is a diagram showing an example of a pricing operation screen according to a seventh modified example of the present embodiment. FIG. 23 is a diagram showing an example of a pricing operation screen according to a seventh modified example of the present embodiment. FIG. 23 is a diagram showing an example of a weighing result screen according to a seventh modified example of the present embodiment.

First Embodiment
1 shows an overview of a store in which a weighing and pricing device (one example of a weighing and pricing device) in the sales system of this embodiment is used. An example of a store in this embodiment is a store that sells food. In the store in which the weighing and pricing device is used in this embodiment, a face-to-face method is adopted in which a store clerk weighs and prices products using the weighing and pricing device in response to product designation by a customer.

In the display case shown in the figure, various foods are displayed as merchandise.
Three weighing pricing devices 10-1, 10-2, and 10-3 are installed on the display case. In the following description, when there is no need to distinguish between the weighing pricing devices 10-1, 10-2, and 10-3, they will be referred to as the weighing pricing device 10. The weighing pricing device 10 includes a weighing platform on which products to be weighed (or mass) are placed. The weighing pricing device 10 executes a pricing process for the weighed products.

Although not shown in the figure, a payment settlement device is installed at a predetermined location away from the sales floor shown in the figure.
The number of weighing and pricing devices 10 and the number of settlement devices installed in a store are not particularly limited.

In this embodiment, although not shown in the figure, the store also has a sales area where customers can place any product from the product shelves into their shopping cart, in addition to the sales area where the weighing and pricing device 10 is located.

Figure 2 shows an example of the configuration of a sales system in this embodiment. The sales system in the figure includes weighing and pricing devices 10 (10-1, 10-2, 10-3), settlement devices 20 (20-1, 20-2), a management device 30, a mobile terminal device 40, and a transaction management server 50.

The weighing pricing device 10 calculates the price of each product based on the weight measured for the product placed on the weighing platform and the unit price by weight, and generates product pricing information for the product including the calculated price. The product pricing information is transmitted to a mobile terminal device 40 connected to the weighing pricing device 10 so as to be able to communicate with the weighing pricing device 10.
A customer specifies the product to be purchased and its weight (or price) to the store clerk. The store clerk operates the weighing pricing device 10 to designate the product specified by the customer as a registration target. The store clerk then has the weighing pricing device 10 measure the weight of the product to be registered (or the weight corresponding to the price specified by the customer). At this time, the store clerk weighs the product by placing it on a weighing platform.
The weighing pricing device 10 calculates the price of the product based on the weighed weight and the weight unit price per unit weight (e.g., 100 g) set for the product, and prices the product designated as the registration target together with the product price. The customer indicates the weight of each product he or she wishes to purchase to the store clerk as described above, and the store clerk measures the weight of the indicated product and prices the product. Each time the price of a product is determined, the weighing pricing device 10 transmits product pricing information reflecting the determined product price to the mobile terminal device 40 that is communicably connected.

The settlement device 20 uses the cart information (settlement information) obtained from the transaction management server 50 to execute settlement processing in response to the customer's operations.

The management device 30 is a higher-level device of the settlement device 20 in the store. The management device 30 in the figure is communicably connected to the settlement device 20. The management device 30 can manage transaction records in the store, for example, by acquiring record information of settlement processing in the store from the settlement device 20. The management device 30 can also monitor the status of the settlement device 20, and issue a notification if an abnormality occurs in the settlement device 20.
The management device 30 may also be communicably connected to the weighing-pricing device 10. In this case, for example, product master information may be stored in the management device 30. The weighing-pricing device 10 can use the product master stored in the management device 30 to execute processing corresponding to product registration.

The mobile terminal device 40 is a terminal device that is owned by a customer. In this embodiment, the mobile terminal device 40 may be a smartphone, tablet terminal, or the like that is owned by the customer. Application software (shopping application) that corresponds to the sales system of this embodiment and that the customer uses for services related to shopping, etc. is installed on the mobile terminal device 40.

The transaction management server 50 manages transactions in the sales system. Specifically, the transaction management server 50 receives product registration information transmitted from the mobile terminal device 40 via the network, and generates cart information for each transaction based on the received product registration information. The cart information indicates the registration result of the product in the corresponding transaction.
In response to a cart information request sent from the settlement device 20, the transaction management server 50 sends to the settlement device 20 cart information associated with the transaction identifier specified by the cart information request.

An example of the configuration of the weighing pricing device 10 in this embodiment will be described with reference to Figures 3 and 4. Figure 3 is a block diagram showing an example of the hardware configuration of the weighing pricing device 10. Figure 4 is a perspective view showing an example of the appearance of the weighing pricing device 10. Figure 4(A) is a view of the weighing pricing device 10 from the store clerk's side, and Figure 4(B) is a view of the weighing pricing device 10 from the customer's side.

As shown in FIG. 3, the weighing and pricing device 10 comprises a CPU (Central Processing Unit) 101, a ROM 102, a RAM 103, a scanner unit 104, a clerk display unit 105, a customer display unit 106, a hard disk 107, a key operation unit 108, a weighing unit 109, a printing unit 110, an inter-device communication unit 111, and a short-range communication unit 112. These are connected to each other via a bus 119.

The CPU 101 executes various processes for implementing the functions of the weighing and pricing device 10 by executing a program.
ROM 102 stores various information. For example, it stores a program executed by CPU 101. ROM 102 also stores information (screen information, message information, etc.) related to display by clerk display unit 105 and customer display unit 106. ROM 102 also stores a device number (device identifier) for identifying the device itself. ROM 102 may also store information related to printing by printing unit 110 (printing contents, printing format information, etc.).
The RAM 103 is used as a working area when the CPU 101 executes processing and calculations.

The scanner unit 104 optically reads the coded information. For example, as shown in Figures 4(A) and 4(B), the scanner unit 104 is installed in a position that is difficult for customers to see.

As shown in FIG. 4(A), the store clerk display unit 105 is arranged facing the store clerk. The store clerk display unit 105 is configured as a touch panel and accepts operations when an operating object such as a finger touches the displayed operation screen.

As shown in FIG. 4(B), the customer display unit 106 is disposed facing the customer and displays information for the customer. The customer display unit 106 may be configured as a touch panel so that it can be operated by the customer.

The hard disk 107 serves as an auxiliary storage device for the CPU 101 and stores various types of information necessary for the weighing and pricing device 10. The hard disk 107 may store, for example, product files and the like. The hard disk 107 may store programs for causing the CPU 101 to execute registration processing and the like. The hard disk 107 may also store various types of information that are generated by executing the programs. The hard disk 107 may also store information related to displays by the clerk display unit 105 and the customer display unit 106, and information related to printing by the printing unit 110.
Instead of the hard disk 107, other storage devices such as a solid state drive (SSD) may be provided.

As shown in FIG. 4(A), the key operation unit 108 has various operation keys (number entry key, cancel key, tare key, add key, item number key, execute key, etc.) for accepting various operations from the store clerk.

The weighing unit 109 weighs the product (product and the container containing the product) placed on the scale platform 109a and outputs data indicating the weighing value to the CPU 101. After obtaining the weighing value from the weighing unit 109, the CPU 101 subtracts a predetermined weight (the container weight) from the weighing value to calculate the product placed on the scale platform 109a. The CPU 101 also temporarily stores the product weight calculated as described above in the RAM 103 and displays it on the display unit (store clerk display unit 105, customer display unit 106).

The printing unit 110 prints on a recording medium and issues (outputs) the data from an issuing port (see FIG. 4A). For example, the printing unit 110 can issue labels to be affixed to products.

The inter-device communication unit 111 is provided in order to communicate with other weighing-pricing devices 10 via a predetermined communication network. The communication network supported by the inter-device communication unit 111 may be wired or wireless. The inter-device communication unit 111 may be capable of communicating with the management device 30.
The short-range communication unit 112 communicates with the mobile terminal device 40 using a predetermined short-range wireless communication method. The short-range wireless communication method supported by the short-range communication unit 112 may be, for example, Bluetooth (registered trademark).

Figure 5 is a perspective view showing the exterior of the settlement device 20. The settlement device 20 in this figure includes a scanner unit 204, a customer display unit 206, a change dispenser 260, and an issuing port 210a.

The scanner unit 204 reads code information. The code information that the scanner unit 204 can read may be a barcode (one-dimensional code) or a two-dimensional code (e.g., QR Code (registered trademark)).
In this embodiment, the scanner unit 204 is used to read code information displayed on the mobile terminal device 40. Examples of code information displayed on the mobile terminal device 40 include code information for settlement, code information arranged on the membership card screen indicating a member identifier or the like, code information including information as a coupon, etc. Furthermore, the settlement device 20 may be capable of executing a product registration process in response to, for example, an operation by a store clerk, and in this case, the scanner unit 204 may be configured to read code information as a product code.
The scanner unit 204 in the figure is shown as being fixedly mounted on the base of the customer display unit 206, but it may also be, for example, a handheld scanner that is hooked onto a base provided on the side of the housing.

The customer display unit 206 displays information related to payment to customers. The customer display unit 206 may be configured as a display device equipped with a touch panel.

The change machine 260 is an automatic change machine that accepts banknotes and coins inserted by customers, processes the deposit, and ejects banknotes and coins when change, refunds, or rejects are given. The change machine 260 comprises a banknote management section 261, a coin insertion port 264, a coin ejection port 265, and a rejection port 266. The coin insertion port 264, the coin ejection port 265, and the rejection port 266 are included in the coin management section. The banknote management section 261 comprises a banknote insertion port 262 and a banknote ejection port 263. The banknote insertion port 262 is an opening that takes in banknotes inserted by customers. The banknote ejection port 263 is an opening that ejects banknotes and rejected banknotes. The banknote insertion port 262 and the banknote ejection port 263 are configured in two stages. For example, in the banknote management section 261, the upper stage is the banknote insertion port 262 and the lower stage is the banknote ejection port 263.

The coin slot 264 is an opening for taking in coins inserted by customers. The coin outlet 265 is an opening for ejecting coins as change, coins that the coin recognition unit of the change machine 260 has failed to recognize, and coins that the coin recognition unit has recognized as counterfeit coins. The rejection opening 266 is an opening for ejecting coins when a cancellation operation is performed after depositing. The banknote slot 262 and the coin slot 264 are deposit openings. The banknote outlet 263, the coin outlet 265, and the rejection opening 266 are withdrawal openings. The issuing opening 210a outputs various receipts from the receipt outlet.

The change machine 260 and issuing port 210a are protruding from the customer side of the counter table with the bill insertion port 262, bill ejection port 263, coin insertion port 264, coin ejection port 265, reject port 266, and receipt ejection port facing the customer. This arrangement reduces the risk of a customer's toes hitting the counter table when standing close to the change machine 260. For example, the change machine 260 and issuing port 210a are stored in a single housing, and this housing is protruding from the customer side of the counter table.

Figure 6 is a block diagram showing an example of the configuration of the settlement device 20. The settlement device 20 comprises a CPU 201, a ROM 202, a RAM 203, a scanner unit 204, a customer display unit 206, a hard disk 207, a printing unit 210, an inter-device communication unit 211, and a change dispenser 260. These are connected to each other via a bus 219. Note that the inter-device communication unit 211 is a part that is provided for communication with a store clerk identification tag in the third embodiment described below, and therefore may be omitted in this embodiment.

The CPU 201 executes various processes for implementing the functions of the settlement device 20 by executing a program.
ROM 202 stores various information. For example, ROM 202 stores a program executed by CPU 201. ROM 202 also stores information related to display by customer display unit 206 (screen information, message information, etc.). ROM 202 also stores an apparatus number for identifying its own apparatus. ROM 202 may also store information related to printing by printing unit 210 (printing contents, printing format information, etc.). Scanner unit 204 optically reads coded information and stores the read information in RAM 203.
The RAM 203 is used as a working area when the CPU 201 executes processing and calculations.
The scanner unit 204 optically reads the coded information, for example, a membership number printed as a barcode on a membership card.

The customer display unit 206 is configured as a touch panel, displays information for customers, and accepts operations by customers touching the screen.

The hard disk 207 serves as an auxiliary storage device for the CPU 201 and stores various information necessary for the settlement device 20. The hard disk 207 may store programs for causing the CPU 201 to execute settlement processing and the like. The hard disk 207 may also store various information generated by executing the programs. The hard disk 207 may also store information related to display by the customer display unit 206 and information related to printing by the printing unit 210.
The printing unit 210 prints receipts and the like on paper and ejects the receipts from an ejection port.

The inter-device communication unit 211 communicates with, for example, other settlement devices 20 and management devices 30.

An example of the configuration of the mobile terminal device 40 of this embodiment will be described with reference to FIG. 7. The mobile terminal device 40 in the figure includes a CPU 401, a storage unit 402, a RAM 403, a network-compatible communication unit 404, a short-range wireless-compatible communication unit 405, a display unit with a touch panel 406, an operation unit 407, an imaging unit 408, and a location information acquisition unit 409.

The CPU 401 executes programs to realize various processes in the mobile terminal device 40 .
The storage unit 402 is an auxiliary storage device for the CPU 401, and stores various types of data in addition to the programs executed by the CPU 401.
The RAM 403 is a main storage device for the CPU 401 .

A network-compatible communication unit 404 executes communication compatible with a network via a telephone line or a wireless LAN.
The short-distance wireless communication unit 405 performs short-distance wireless communication according to the Bluetooth standard, for example. That is, the short-distance wireless communication unit 405 performs short-distance wireless communication with the short-distance communication unit 112 in the weighing-pricing device 10. This enables communication between the mobile terminal device 40 and the weighing-pricing device 10.

The touch panel display unit 406 is a display unit combined with a touch panel.
An operation unit 407 collectively indicates keys and the like that are operated other than the touch panel display unit 406 .

The imaging unit 408 captures an image. The mobile terminal device 40 has a code information scanning function that utilizes the imaging unit 408. In other words, when the mobile terminal device 40 recognizes that code information is included in an image captured by the imaging unit 408, the code information scanning function acquires the code information from the captured image.

In the shopping application of this embodiment, the code information scanning function using the imaging unit 408 is used to read the code information attached to the product and to read the connection information code displayed on the weighing pricing device 10. By reading the code information attached to the product, the product to be registered is identified by the product code contained in the code information. Identification of the product to be registered in this manner may be achieved, for example, by a general object recognition process using an image obtained by imaging the product with the imaging unit 408. In this case, one product may be identified as a result of the general object recognition process, or multiple candidates may be presented. When multiple candidates are presented, the product to be registered may be identified by the customer selecting one of the multiple candidates presented.

The location information acquisition unit 409 measures its own location and acquires location information indicating the measured location. The location information acquisition unit 409 may be configured to include a positioning device compatible with, for example, GPS (Global Positioning System).

An example of the configuration of the transaction management server 50 of this embodiment will be described with reference to FIG. 8. The transaction management server 50 in the figure includes a CPU 501, a memory unit 502, a RAM 503, and a communication unit 504.

The CPU 501 executes programs to realize various processes in the transaction management server 50 .
The storage unit 502 is an auxiliary storage device for the CPU 501, and stores various types of data in addition to the programs executed by the CPU 501.
The RAM 503 is a main storage device for the CPU 501 .
The communication unit 504 communicates with the settlement device 20, the mobile terminal device 40, and the like.
The transaction management server 50 may also be provided with a display unit, an operation unit, etc., so that an administrator can perform operations, etc.

The transaction management server 50 stores customer information such as that shown in FIG. 9 (A). The customer information shown in FIG. 9 (A) includes customer identification information, customer name, customer registration date, cancellation information, customer rank, number of points, etc. Customer identification information is identification information that uniquely identifies a customer. Customer name is the customer's name or nickname, etc. Customer registration date is the date and time when the customer was registered. Cancellation information is information regarding the cancellation of registered products after registration. Customer rank is a rank according to the customer's purchase history. Note that when generating customer information for a new customer, customer identification information, customer name, and customer registration date are generated, but other information (cancellation information, etc.) is not generated because this is before the start of an actual transaction (product registration).

The transaction management server 50 generates and stores customer identification information, for example, when a customer is registered (for example, when the mobile terminal device 40 downloads or installs a shopping application from an external device (for example, a predetermined server that provides all apps, the transaction management server 50) to use a service provided by the transaction management server 50). In addition, the transaction management server 50 obtains information entered into the name field of a registration form (input form) using the mobile terminal device 40, for example, when a customer is registered, and stores it as the customer name. In addition, the transaction management server 50 obtains the current date and time when the customer is registered, and stores it as the customer registration date.

In addition, instead of or in addition to storing the customer information in a memory unit within its own device, the transaction management server 50 may store some or all of the customer information in another device (such as a file server accessible to the transaction management server 50).

The store information is obtained from the management device 30 of each store. In other words, the transaction management server 50 stores the store information by receiving the store information directly from the management device 30 of each store or indirectly via another device.

The transaction management server 50 stores store information such as that shown in FIG. 9(B). The store information shown in FIG. 9(B) includes store identification information, store name (branch name), store specific information 1, and store specific information 2. Store identification information is identification information that uniquely identifies a store. The store identification information shown in FIG. 9(B) is composed of a store (trade name) or company code and a branch code. The store name is the name of the store. The store name shown in FIG. 9(B) is composed of a store (trade name) or company and a branch name. Store specific information 1 is information on a two-dimensional code (e.g., QR code (registered trademark), etc.) for identifying the store in which the transaction takes place (the store where the product is bought and sold). Store specific information 2 is store location information (GPS information) for identifying the store in which the transaction takes place. Note that in the example shown in FIG. 9(B), the store identification information and the store specific information 1 are different, but the store identification information and the store specific information 1 may be the same.

The transaction management server 50 may obtain and store store information from an external source (such as a server (not shown) at a headquarters that oversees each store). The transaction management server 50 may also store some or all of the store information in another device (such as a file server accessible by the transaction management server 50) instead of or in addition to storing the store information in a memory unit within its own device.

The product information is obtained from the management device 30 of each store. In other words, the transaction management server 50 stores the product information by receiving the product information directly from the management device 30 of each store or indirectly via another device. The transaction management server 50 may obtain and store the product information from an external source (such as a server (not shown) at the headquarters that oversees each store). The transaction management server 50 may also store some or all of the store information in another device (such as a file server accessible by the transaction management server 50) instead of or in addition to storing the store information in the memory unit of its own device.

Cart information is information for managing individual transactions. The transaction management server 50 generates cart information at the start of a transaction. In addition, the transaction management server 50 updates the cart information as the transaction progresses (each time a product is registered) (the storage of a product in the cart information may be interpreted as the registration of that product).

The transaction management server 50 stores cart information such as that shown in FIG. 9(C), for example.
The cart information shown in FIG. 9(C) includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, pending product information, cancellation information, etc. The cart identification information is identification information that uniquely identifies a cart (transaction). The cart identification information shown in FIG. 9(C) is composed of store identification information, date, and serial number (e.g., a serial number specific to each store and date). The transaction start date and time is the start date and time of the transaction. The transaction start date and time shown in FIG. 9(C) is the creation date and time of the cart information. Note that the transaction start date and time may be the registration date and time of one product item (the date and time when the registered product information (registered product 1) in FIG. 9(C) is stored). The creation date and time of the cart information and the registration date and time of one product item may both be stored separately.

The transaction end date and time is the end date and time of the transaction. The transaction start date and time shown in Figure 9 (C) is the settlement date and time. The customer identification information is customer identification information that identifies the customer of the transaction. When cart information is generated, the cart identification information, transaction start date and time, and customer identification information are generated, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, etc.) is not generated. The settlement date and time may be the settlement start date and time or the settlement end date and time. The settlement start date and time and the settlement end date and time may both be stored separately.

Registered product information (total) is information that is updated each time a product is registered. Registered product information (total) includes the number of products (number of products), estimated subtotal amount (estimated subtotal amount before price calculation using price determination logic), subtotal amount (subtotal amount after price calculation using price determination logic), etc. Registered product information (1) is the registration information for one product item. Registered product information (2) is the registration information for two products. In the example shown in Figure 9 (C), registered product information (3) to registered product information (5) are omitted from the illustration. Registered product information (N; N is an integer) includes the product code, product name (product name), price, etc.

The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management server 50 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a basis for determining whether or not to apply a service such as a time service (a service based on selling price determination logic E) and the effect of applying the service.

Pending product information (total) is information that is updated each time a pending product (described below) is registered. Pending product information (total) includes the number of pending products (number of products), the number of pending products that are NON-FILE, the number of pending products that cannot be read (check for tampering), etc.

A NON-FILE is a product whose barcode was successfully scanned at the store (the product code was read) but the product code is not stored in the product information, or whose product code was successfully scanned at the store but the product code is not stored in the product information.

A read NG refers to a failure to scan the product code at the store (the product code could not be read), or a product whose product code has not been scanned at the store. In other words, a read NG refers to a timeout process when it is possible to determine that a product has been imaged for a certain period of time using image recognition technology but has not been recognized as a barcode, or a product that has been timed out. For example, a read NG is determined when the barcode cannot be correctly acquired (recognized) due to wrinkles on the package or smudges or dirt on the barcode print. A read NG is also determined when an unauthorized operation of pretending to read the barcode and putting it in the basket is detected. The mobile terminal device 40 is equipped with a sensor (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.) and can detect when the mobile terminal device 40 is reading a barcode (specifically, when the mobile terminal device 40 is tilted to read the barcode and an item (product) is present at a certain distance from the mobile terminal device 40). If the barcode cannot be read within the specified time (if the barcode continues to be read for a specified time but the barcode cannot be read), a timeout occurs and the product is marked as pending (unable to be read).

Pending product information (pending product 1) is information on pending product 1. Pending product information (pending product 2) is information on pending product 2. Pending product information (pending product 3) is information on pending product 3.

The reserved product information (reserved product N; N is an integer) includes the reserved product type (information indicating whether the reserved product is a NON-FILE or cannot be read) and image data (image data captured when reading was NG). For example, if the Nth item is a reserved product due to a NON-FILE, the reserved product information (reserved product N) includes the reserved product type "1 (NON-FILE)" and image data. Also, if the Nth item is a reserved product due to reading was NG, the reserved product information (reserved product N) includes the reserved product type "2 (cannot be read)" and image data.

In addition to or instead of storing the cart information in a memory unit within its own device, the transaction management server 50 may store some or all of the cart information in another device (such as a file server accessible to the transaction management server 50).

The functions of the shopping application installed on the mobile terminal device 40 will be described with reference to FIGS.
When a customer operates the mobile terminal device 40 to start up a shopping application, the mobile terminal device 40 on which the shopping application runs first displays a start-up screen on the touch panel display unit 406, as shown in Fig. 10(A). The start-up screen in the figure has a "Store Information" button, an "Announcement" button, and a "Discount Information" button. Also, a shopping start button with the words "Start Shopping" is also provided.

For example, when a customer operates (tap) the "Store Information" button, the display on the touch panel display unit 406 transitions to a nearby store guide screen as shown in Fig. 10(B) . The nearby store guide screen displays on a map stores that are within a certain range based on the customer's own position acquired by the position information acquisition unit 409 and that have a shopping application available (available stores). The figure shows an example in which marks indicating three available stores are placed on a map based on the current position of the mobile terminal device 40.
To display such a nearby store guide screen, the mobile terminal device 40 transmits an available store search request together with its own location information to a store information server (not shown; the transaction management server 50 or the like may also be used as the store information server) that manages information on available stores (available store information). In response to receiving the available store search request, the store information server searches for available stores located within a certain distance range based on the location information received together with the available store search request. The store information server transmits information on the searched available stores to the mobile terminal device 40. The mobile terminal device 40 uses the received information on available stores to display the nearby store guide screen.

The shopping application may have, for example, a shopping list function, whereby a customer can perform an operation to register products that the customer intends to purchase in the shopping list.
In this way, when the shopping application has a shopping list function, the mobile terminal device 40, for example, includes information on the products registered in the shopping list in the available store search request. The store information server includes a list of the items of products sold at the store in the available store information for each store. In response to receiving the available store search request, the store information server transmits the available store information to the mobile terminal device 40 after including information indicating the presence or absence of the products registered in the shopping list for each available store information searched for as being within a certain range from the position of the mobile terminal device 40. In this case, the mobile terminal device 40 may display the available stores on a map so that the presence or absence of the products registered in the shopping list can be visually confirmed. As a display mode of the available stores so that the presence or absence of the products registered in the shopping list can be visually confirmed, for example, the color or size of the mark indicating the available store may be changed depending on whether the available store has the products registered in the shopping list or not.

In addition, when the nearby store guide screen is displayed as in FIG. 10(B), if the customer performs an operation to select the mark of any store (e.g., by tapping on the mark), a store information screen showing information about the selected store will be displayed as shown in FIG. 10(C).

As described above, the "Notice" button and the "Discount Information" button are arranged on the start-up screen of Fig. 10(A). Also, the "Notice" button and the "Discount Information" button are arranged on the store information screen of Fig. 10(C).
When a customer operates the "Notice" button while the start-up screen or store information screen is displayed, an advertising screen is displayed providing information such as event and sale announcements prepared as "Notice" by the corresponding available store, as shown in FIG. 11 (A).
Furthermore, if a customer operates the "Special Offers" button, an advertising screen is displayed providing information on discounts and other services for customers using the shopping application, as shown in FIG. 11 (B).
These advertisement screens may be displayed based on advertisement information included in the available store information transmitted from the store information server.

When the shopping start button arranged on the start screen of Fig. 10 (A) is operated, the touch panel display unit 406 transitions to a product registration screen (code scan screen) as shown in Fig. 11 (C). The customer can use the mobile terminal device 40 on which the product registration screen is displayed to perform product registration operations.
Here, an example of product registration operation in a sales floor where product shelves are arranged will be described as an example of a basic product registration operation, rather than in a sales floor where a weighing and pricing device 10 is arranged.
A customer takes out a product that he or she wishes to purchase (a product to be purchased) from, for example, a product shelf. The customer performs an operation to have the imaging unit 408 of the mobile terminal device 40, which is displaying a product registration screen, read the code information of the code (which is a barcode but may also be a two-dimensional code) attached to the product to be purchased that he or she has taken out.
The code information thus read is transmitted from the mobile terminal device 40 to the transaction management server 50 as product registration information corresponding to one product. The transaction management server 50 includes the received product registration information in cart information (payment information) corresponding to one transaction. The product registration information based on the read code information may be stored in the mobile terminal device 40.
When the customer has completed the operation to register all products to be purchased, the customer performs a predetermined operation (product registration completion operation) on the mobile terminal device 40 to instruct completion of product registration. When the product registration completion operation is performed, the mobile terminal device 40 may notify the transaction management server 50 of the completion of product registration. Upon receiving the notification of the completion of product registration, the transaction management server 50 can manage the cart information of the corresponding transaction as if product registration had been completed.

When the product registration completion operation is performed, a payment guide screen is displayed on the touch panel display unit 406 of the mobile terminal device 40 as shown in Fig. 11 (D). The payment guide screen in the figure displays a message instructing the customer to go to the payment settlement device 20 to settle the payment, and transaction code information indicating the transaction corresponding to the current product registration is displayed, for example, as a two-dimensional code. The transaction code information includes a transaction identifier that uniquely identifies the transaction. This transaction identifier may be, for example, issued by the transaction management server 50 in response to the mobile terminal device 40 first transmitting product registration information in the corresponding transaction, and notified to the mobile terminal device 40.
The customer goes to the settlement device 20 and has the scanner unit 204 of the settlement device 20 read the two-dimensional code displayed on the settlement guidance screen. The settlement device 20 acquires cart information corresponding to the transaction identifier indicated by the read two-dimensional code from the transaction management server 50. The settlement device 20 uses the acquired cart information to execute settlement processing in response to the customer's operation. The settlement device 20 may be equipped with one or more card readers corresponding to predetermined cards, for example, in case a customer uses or combines cards such as a credit card, electronic money card, point card, etc. to settle the payment.
In this manner, in this embodiment, a customer who has installed a shopping application on his/her mobile terminal device 40 can register products by operating his/her mobile terminal device 40. Furthermore, the settlement at the payment device 20 is also performed by the customer. In this manner, since the customer performs product registration and settlement, in this embodiment, it is not necessary for a store clerk to perform product registration operations or operate the payment device.

On the other hand, some stores have sales areas where weighing devices 10 are installed and where sales by weight are available in a face-to-face manner, as shown in Fig. 1. In such sales areas where sales by weight are available, as explained in Fig. 1, a customer meets a store clerk who operates the weighing device 10 and specifies a product and its weight, and the store clerk uses the weighing device 10 to price the product based on the weight of the specified product.
In this way, in a sales area where the weighing and pricing device 10 for face-to-face sales is used, the operations related to product registration and the associated processing in the sales system differ from the case where the basic product registration operations described above are performed. This point will be explained below.

With reference to the flowchart in FIG. 12, an example of the processing procedure executed by the weighing pricing device 10, the mobile terminal device 40, and the transaction management server 50 in relation to product registration in one transaction will be described. Also, with reference to the same figure, the operations of the store clerk and the customer when the customer shops at a sales floor that supports bulk sales will be described. Note that, for simplicity of explanation, the same figure shows an example in which product registration corresponding to one transaction is completed by one or more product registration processes performed corresponding to one weighing pricing device 10.

First, an example of a processing procedure executed by the weighing and pricing device 10 will be described.
Step S101: The weighing pricing device 10 determines whether or not a pricing operation has been performed for one product in one transaction.
A customer who wishes to purchase a commodity sold by weight tells a store clerk the commodity he or she wishes to purchase and its weight. The store clerk takes out the commodity from the display case. The store clerk inputs the item name of the commodity to be purchased into the weighing pricing device 10 and places the commodity on the scale (weighing unit 109).

The item name of the product to be purchased is entered, for example, as follows. The clerk display unit 105 (touch panel) of the weighing pricing device 10 has keys (preset keys) corresponding to each product sold by weight. The clerk operates one of the preset keys that corresponds to the product to be purchased. This causes the item name of the product corresponding to the operated preset key to be entered as the item name of the product to be purchased.

For example, the weighing pricing device 10 may determine that a pricing operation for one product has begun in response to inputting the item name of the product to be purchased.
In addition, when a pricing operation for the first product in a transaction is started, the weighing pricing device 10 determines that product registration corresponding to the transaction has started, and issues a transaction identifier to be associated with the current transaction.

Step S102: In response to the pricing operation, the weighing pricing device 10 executes a pricing process. The pricing process is a product registration process executed by the weighing pricing device 10 to register a product to be purchased.
As a pricing process, the weighing pricing device 10 accepts the input of the item name of the product by the store clerk and obtains the item name of the product to be purchased. The weighing pricing device 10 calculates the price of the product using the weight unit price and the weight measured by the weighing unit 109 (for example, the weight measured when the product is stable without fluctuating after being placed on the weighing unit 109). The weighing unit 109 displays the item name, measured weight, price, etc. of the product to be purchased on the store clerk display unit 105 and the customer display unit 106, for example.
The store clerk confirms with the customer the weight etc., and when the customer gives consent, performs an operation to instruct the customer to finalize the pricing of the product to be purchased.

Step S103: When the weighing result by the weighing unit 109 is confirmed as described above and the pricing for one item to be purchased is confirmed (corresponding to confirmation of the weighing result), the weighing pricing device 10 displays a connection information code on the customer display unit 106. The connection information code may be displayed, for example, as a two-dimensional code. The connection information code is control information for connecting the mobile terminal device 40 on which the shopping application runs to the weighing pricing device 10, for example, via Bluetooth. The connection information code includes a transaction identifier issued in response to the current transaction.
13 shows an example of a connection information code screen displayed on the customer display unit 106. In this figure, an example of a connection information code screen is shown in which the customer display unit 106 has a vertically long display surface and the display screen is in English.
In the connection information code screen in the figure, the connection information code is displayed as a two-dimensional code, and an image of the mobile terminal device is displayed together with an arrow pointing to the two-dimensional code. This allows the customer to intuitively understand that the two-dimensional code should be read by the mobile terminal device 40.
The connection information code screen also displays pricing-related information for the item being priced (such as tare weight, gross weight, unit price by weight, and total price). In other words, the connection information code screen displays the results of the pricing process for the item being priced (confirmed weighing results). Also, a message ("OK with this weight?") is displayed to prompt the customer to confirm whether or not they wish to register the weighed weight.
After checking the contents of the pricing-related information displayed on the connection information code screen, the customer operates the mobile terminal device 40 to read the connection information code displayed on the connection information code screen as a two-dimensional code.
The store clerk display unit 105 may display a message, a pop-up window, an icon, or the like to inform the store clerk that the connection information code is being displayed on the customer display unit 106.

The display of the connection information code in step S103 may be performed at the following timing.
For example, the connection information code may be displayed when the fluctuation in the weighing value measured by the weighing unit 109 for the priced product falls below a certain level.
In addition, the connection information code may be displayed when the weighing value measured by the weighing unit 109 for the product to be priced becomes stable and the weighing value for price calculation is determined.
Furthermore, the connection information code may be displayed at the timing when the measurement value for price calculation is finalized and the price is calculated.
The connection information code may be displayed in response to an operation. For example, a store clerk may perform an operation to display the connection information code at any timing, such as when a transaction starts or when the price of a priced product is confirmed.
In this case, the operation for displaying the connection information code may be, for example, a touch operation on a button arranged on the screen displayed on the store clerk display unit 105 for instructing the display of the connection information code.
Furthermore, when the connection information code is displayed in response to an operation by a store clerk, the timing of displaying the price of the priced item and the connection information code on the customer display unit 106 may be as follows. For example, the weighing pricing device 10 displays the price of the item on the customer display unit 106 in response to the timing at which the price of the weighed priced item is determined. Thereafter, the weighing pricing device 10 may additionally display the connection information code on the same screen together with the price of the priced item in response to an operation to display the connection information code. Alternatively, the weighing pricing device 10 may not display the price of the item when the price of the priced item is determined by weighing, and may display the price of the priced item and the connection information code on the same screen in response to an operation to display the connection information code after the price of the priced item is determined.
In addition, the weighing pricing device 10 may display the connection information code at a timing before pricing by the pricing process in step S102 is completed, for example, in response to a determination in step S101 that a pricing operation has been started by inputting the item name of the product to be purchased.
Such modified examples of the display timing of the connection information code may be similarly applied to the second to fifth embodiments described later.

Returning to FIG.
Step S104: The weighing-pricing device 10 executes a connection process to establish a connection in response to a connection request from the portable terminal device 40 that has read the connection information code. When the connection is established, communication between the weighing-pricing device 10 and the portable terminal device 40 becomes possible.

Step S104-1: The weighing-pricing device 10 detects whether or not a connection has been established by the connection process of step S104. When the weighing-pricing device 10 detects that a connection with the mobile terminal device 40 has been established, it erases (ends) the display of the connection information code displayed in step S103.
For example, the connection information code may be constantly displayed on the weighing pricing device 10, or a plate on which the connection information code is displayed may be constantly installed near the weighing pricing device 10. However, in this case, for example, a customer who is not related to the target transaction may cause the portable terminal device 40 to read the connection information code, which may result in an unnecessary connection between the weighing pricing device 10 and the portable terminal device 40. Therefore, the weighing pricing device 10 controls the start and end of the display of the connection information code and limits the opportunities for connection with the portable terminal device 40, thereby making it possible to avoid unnecessary connection between the weighing pricing device 10 and the portable terminal device 40 as described above.

Step S105: The weighing-pricing device 10 connected to the portable terminal device 40 by the connection process of step S104 performs a transaction identifier matching process. That is, the weighing-pricing device 10 determines whether the transaction identifier issued in response to the current transaction matches the transaction identifier notified by the connected portable terminal device 40.
In addition, in consideration of the fact that it is unlikely that another customer who is not being served by a store clerk will have his/her mobile terminal device read the connection information code, the connection information code may not include the transaction identifier. In this case, the transaction identifier matching process in step S105 and step S203 described below may be omitted, and the subsequent processes may be executed.

Step S106: If the transaction identifiers are determined to match by the transaction identifier matching process in step S105, the weighing pricing device 10 transmits product pricing information (an example of registration processing information) reflecting the results of the current pricing process for one product in step S102 to the connected mobile terminal device 40.

Step S107: If the product pricing information transmitted in step S106 is normally received by the mobile terminal device 40, a reception confirmation notice is transmitted from the mobile terminal device 40 to the weighing-pricing device 10. The weighing-pricing device 10 receives the transmitted reception confirmation notice.
Step S108: In response to receiving the receipt confirmation notification, the weighing pricing device 10 issues an individual item label by having the printing unit 110 print a label (individual item label) corresponding to the product for which pricing processing has been performed in step S102.

Figure 14 shows an example of a single item label. Such single item labels are printed with information such as the product name, processing date, expiration date, price per weight, weight, and price. In addition, the single item label may also be printed with information indicating the department to which the sales floor that sells by weight corresponds. The single item label may also be printed with a code (a barcode in this figure) that includes at least a portion of the information printed in characters, etc., as described above, but it is preferable to change the format, such as printing "registered" or printing the label format, so as not to confuse it with labels for general customers. The store clerk attaches the single item label issued in this way to the product that is the subject of the current pricing.

Returning to FIG.
Step S109: If it is determined in step S101 that a pricing operation has not been performed for one item, or after the processing of step S108 has been executed, the weighing pricing device 10 determines whether pricing of all items corresponding to one transaction has been completed.
When the store clerk confirms that pricing has been completed for all products designated by the customer in one transaction, the store clerk performs an operation to declare the completion of pricing for one transaction (pricing completion operation) on the weighing pricing device 10. In response to the price completion operation being performed, the weighing pricing device 10 determines that pricing for all products in one transaction has been completed.
Alternatively, for example, if a store clerk has previously performed an operation to specify the items of products to be priced in one transaction, whether or not the pricing of all products corresponding to one transaction has been completed may be determined based on whether or not the pricing process for each product has been completed a number of times corresponding to the declared number. Here, the operation by the store clerk to previously specify the items of products to be priced in one transaction may be, for example, an operation on a preset key displayed on the store clerk display unit 105 of the weighing pricing device 10, or an operation on a tag device arranged toward the store clerk in correspondence with each displayed product. The preset key is a key arranged on the screen in correspondence with each product. The tag device is a device that transmits product information about the corresponding product to the weighing pricing device 10 by, for example, short-range wireless communication in response to a touch operation being performed.
If it is determined that the pricing of the product corresponding to one transaction has not been completed, the process returns to step S101.

Step S110: When it is determined that pricing of the product corresponding to one transaction is completed, the weighing pricing device 10 transmits a pricing completion notification to the connected mobile terminal device 40.
Step S111: The portable terminal device 40 that has received the pricing completion notification sent in step S110 sends a reception confirmation notification to the weighing pricing device 10. The reception confirmation notification sent in step S111 notifies that the pricing completion notification has been normally received. The weighing pricing device 10 that has received the reception confirmation notification executes a process to disconnect the communication connection with the portable terminal device 40.

The display of the connection information code may be erased, for example, when a single-item label is issued in step S108 (when pricing of one item is completed) instead of at the timing of step S104-1. Alternatively, the display of the connection information code may be erased, for example, at the timing corresponding to the disconnection of communication with the mobile terminal device 40 in step S111.

Next, an example of a process procedure executed by the mobile terminal device 40 will be described.
Step S201: With the product registration screen displayed on the touch panel display unit 406, the mobile terminal device 40 determines whether or not the code has been read.
Step S202: As described above, when one product designated by a customer is priced by the weighing pricing device 10 in response to the operation of the store clerk and the pricing is confirmed, a connection information code is displayed on the customer display unit 106 of the weighing pricing device 10. The customer then operates the mobile terminal device 40 with the product registration screen displayed, and causes the mobile terminal device 40 to read the displayed connection information code. As a result, it is determined in step S201 that the code has been read.
In this case, since the code read is a connection information code, the mobile terminal device 40 executes processing between the weighing and pricing device 10 to establish a communicative connection with the destination weighing and pricing device 10 in accordance with the connection procedure indicated by the connection information code.

Step S203: The portable terminal device 40 connected to the weighing-pricing device 10 in step S202 executes a transaction identifier matching process with the connected weighing-pricing device 10. At this time, the portable terminal device 40 transmits to the weighing-pricing device 10 the transaction identifier included in the connection information code read in response to step S201.
As described above, if the connection information code does not include a transaction identifier, the transaction identifier matching process in step S203 may be omitted along with step S105, and the subsequent processes may be executed.

Step S204: As described above, when the weighing pricing device 10 determines that the transaction identifiers match through the transaction identifier matching process, it transmits commodity pricing information in step S106. The portable terminal device 40 receives the transmitted commodity pricing information. In addition, in response to receiving the commodity pricing information, the portable terminal device 40 displays a pricing result that reflects the contents of the received commodity pricing information on the touch panel display unit 406. The pricing result displayed on the touch panel display unit 406 may be, for example, the product name, price, and an indication that the product is a product to be priced. The pricing result may include, for example, any of the information shown on the label in FIG. 14.
Step S205: The mobile terminal device 40 transmits a receipt confirmation notice to the weighing pricing device 10 notifying that the product pricing information has been received.
Step S206: The mobile terminal device 40 also transmits product registration information for one product, reflecting the contents of the product pricing information received in step S204, to the transaction management server 50. The product registration information thus transmitted includes a transaction identifier.

Step S207: The mobile terminal device 40 determines whether the pricing completion notification transmitted by the weighing pricing device 10 in step S110 has been received. If it is determined that the pricing completion notification has not been received, the process returns to step S201.

Step S208: When it is determined in step S207 that the pricing completion notification has been received, the mobile terminal device 40 transmits a reception confirmation notification to the weighing pricing device 10 as notification that the pricing completion notification has been received.
Step S209: The fact that the pricing completion notification has been received means that product registration for one transaction at the bulk sales counter has been completed. The mobile terminal device 40 then transmits a product registration completion notification to the transaction management server 50, which is a notification that product registration for one transaction has been completed.

Next, an example of a processing procedure executed by the transaction management server 50 will be described.
Step S301: The transaction management server 50 determines whether or not the product registration information transmitted from the mobile terminal device 40 in step S206 in response to one transaction has been received.
Step S302: When the product registration information is received in step S301, the transaction management server 50 registers (adds) the received product registration information to the cart information corresponding to the current transaction. This confirms the registration of one product (product type) in one transaction. In step S302, which is executed for the first time in one transaction, the transaction management server 50 generates new cart information and then registers the received product registration information to the generated cart information. When generating new cart information, the cart identification information to be stored in the cart information can be generated using the transaction identifier included in the product registration information transmitted in step S206.
Step S303: If it is determined in step S301 that product registration information has not been received, or after executing the processing of step S302, the transaction management server 50 determines whether or not the product registration completion notification sent by the mobile terminal device 40 in step S209 has been received. If it is determined that the product registration completion notification has not been received, the processing returns to step S301. If it is determined that the product registration completion notification has been received, the processing related to the generation of cart information corresponding to one transaction shown in the figure is terminated. In response to the processing related to the generation of cart information corresponding to one transaction being terminated, the registration of all products corresponding to one transaction is confirmed.

According to the process in the figure, the weighing pricing device 10 of this embodiment issues a single item label in response to receiving a receipt confirmation notice for the product pricing information from the connected mobile terminal device 40. In other words, although not specifically shown in the process in the figure, if the weighing pricing device 10 transmits product pricing information but does not receive a receipt confirmation notice from the connected mobile terminal device 40, the weighing pricing device 10 does not issue a single item label. In this case, for example, an error notification is issued. As a result, the weighing pricing device 10 issues only single item labels for products for which the mobile terminal device 40 has received product pricing information.
In this case, in response to the printing of the single item label, the store clerk and the customer can confirm that the pricing information required to register the product sold by weight has been properly received by the mobile terminal device 40. In other words, the store clerk and the customer can accurately determine whether or not the product registration process on the mobile terminal device 40 has been properly executed.

Second Embodiment
Next, a second embodiment will be described. The first embodiment described above is an example in which a customer who wishes to purchase a product at a sales floor where the weighing and pricing device 10 is installed uses a mobile terminal device 40 to register the product.

In some stores, the store is operated so as to be able to accommodate both customers who use the mobile terminal device 40 to register products and make purchases, and customers who make purchases without using the mobile terminal device 40.
In order to accommodate customers who do not use the mobile terminal device 40, for shopping in a sales floor with product shelves, a POS register operated by a store clerk is provided in the store, and the customer brings the product they have selected from the product shelves to the POS register. The clerk operating the POS register registers the product brought by the customer and then settles the payment.
Alternatively, a registration device that registers products in response to operation by a store clerk may be placed in the store. A customer brings a product that he or she has selected from the product shelf to the registration device. The store clerk who operates the registration device operates to register the product brought by the customer. Settlement information that reflects the results of the product registration process by the registration device is acquired by the settlement device 20 in a predetermined manner. Specifically, the settlement information may be sent to the settlement device 20 directly from the registration device or via a higher-level device.
Alternatively, a registration device may issue a receipt (registered trademark), and the customer may have the settlement device 20 read the code information printed on the receipt, so that the settlement device 20 obtains settlement information associated with the transaction identifier indicated by the code information from the registration device or a higher-level device, etc. Alternatively, the code information printed on the receipt may include the settlement information. The customer may then operate the settlement device 20 that has obtained the settlement information to make the settlement.
Alternatively, a fully self-service POS register may be provided in the store, where customers can register the products they have picked up from the shelves and make a payment.

On the other hand, in the sales system of this embodiment, in a sales area where merchandise sold by weight is sold and where the weighing pricing device 10 is installed, the following responses can be made depending on whether the customer is shopping using a mobile terminal device 40 or not.

The flowchart in FIG. 15 shows an example of a processing procedure that the weighing pricing device 10 of this embodiment executes in response to pricing in one transaction.
In the following description, an example will be given in which pricing is performed on specific fixed-price items in addition to items sold by weight in a sales area selling items sold by weight.
12. Furthermore, the processing of the mobile terminal device 40 and the transaction management server 50 corresponding to the processing of the weighing pricing device 10 in the figure may be similar to that in FIG.

Step S1101: The weighing pricing device 10 first executes a product identification process. The product identification process is a process for identifying whether the product to be priced is a product sold by weight or a fixed price product. As the product identification process, the weighing pricing device 10 may determine, for example, in response to an input of a product type by a store clerk, whether the type indicated in the product master of the input product type corresponds to a product sold by weight or a fixed price product.
The operation of inputting the item of the product performed by the store clerk in the product specification process corresponds to the designation of the product to be registered. That is, the weighing pricing device 10 designates the product to be registered in response to the operation of inputting the item of the product performed by the store clerk.

The product identification process of step S1101 may also include a process of acquiring information about the name and image of the product to be priced. The product identification process of step S1101 may also include a process of acquiring information about the price of the product to be priced, such as the amount per unit weight (price per weight) and the number of products to be priced per unit weight. The product identification process of step S1101 may also be performed in response to a store clerk operating a preset key displayed on the store clerk display unit 105 of the weighing pricing device 10. Alternatively, the product identification process of step S1101 may be performed in response to the weighing pricing device 10 receiving product information transmitted from a shelf tag in response to a store clerk or customer touching a shelf tag having a wireless function that is arranged corresponding to each product displayed in the showcase.

Step S1102: The weighing pricing device 10 determines, as a result of the product identification process in step S1101, whether the product to be priced is a product sold by weight or a fixed price product.
Step S1103: If it is determined in step S1102 that the product is a product sold by weight, the measurement-based pricing device 10 executes a measurement-based pricing process. The measurement-based pricing process may be similar to step S102 in FIG.
Step S1104: If it is determined in step S1102 that the product is a fixed-price product, the weighing pricing device 10 executes a quantity-based pricing process. That is, in this case, the store clerk inputs the number of the fixed-price product to be registered into the weighing pricing device 10. The input of the number by the store clerk may be performed, for example, by a number-setting operation. Alternatively, the input of the number by the store clerk may be an operation (task) of placing the products one by one on the weighing platform 109a. In this case, the weighing pricing device 10 counts the number of times that the weight measured by the weighing unit 109 changes stepwise by a certain amount or more as the number of products as the products are placed on the weighing platform 109a one by one. Then, the weighing pricing device 10 calculates the price of the product using the input number and the weight unit price set for the item of the product to be registered.
The weighing pricing device 10 displays, for example, the item, quantity, price, etc. of the product to be purchased on the clerk display unit 105 and the customer display unit 106. The clerk confirms the quantity, etc. with the customer, and when approval is obtained from the customer, performs an operation to instruct the confirmation of the pricing of the product to be purchased.

Step S1105: After processing of step S1103 or step S1104, the weighing pricing device 10 displays a connection information code on the customer display unit 106 in response to the pricing being finalized for one of the products to be purchased as described above.

Step S1106: In this embodiment, pricing is accepted by the weighing pricing device 10 not only from customers who use the portable terminal device 40, but also from customers who do not use the portable terminal device 40. In this case, a customer who uses the portable terminal device 40 performs an operation to have the portable terminal device 40 read the connection information code displayed on the customer display unit 106 in step S1105. On the other hand, a customer who does not use the portable terminal device 40 places an order for the next product or waits to receive the product from a store clerk, without performing an operation to connect the portable terminal device 40 to the weighing pricing device 10 so that it can communicate with the weighing pricing device 10.
Therefore, the weighing pricing device 10 judges whether a predetermined time has elapsed from the point in time when the display of the connection information code is started in step S1105. The predetermined time here may be set in consideration of a standard time required for a customer to complete the operation of having the portable terminal device 40 read the connection information code after the connection information code is displayed.

Step S1107: While it is determined in step S1106 that the predetermined time has not elapsed, the weighing pricing device 10 further determines whether or not the connection process has been started. As described above, if the customer corresponding to the current transaction is a customer using a mobile terminal device 40, the customer will perform an operation to have the mobile terminal device 40 read the connection information code displayed in step S1105. Then, the mobile terminal device 40 that has read the connection information code makes a connection request to the weighing pricing device 10 (step S202 in FIG. 12), and a connection process for establishing a connection between the mobile terminal device 40 and the weighing pricing device 10 is started. When the weighing pricing device 10 starts the connection process in response to the connection request from the mobile terminal device 40 in this way, it determines in step S1107 that the connection process has been started.
If it is determined in step S1107 that the connection process has not been started, the process returns to step S1106. In this manner, the weighing pricing device 10 determines whether or not the connection process will be started within a predetermined time in a state in which the connection information code has been displayed on the customer display unit 106 in step S1105.

Step S1108: If it is determined in step S1106 that the predetermined time has elapsed, the weighing and pricing device 10 causes the store clerk display unit 105 to display a connection necessity confirmation screen.
When a predetermined time has elapsed since the connection information code was displayed, the weighing pricing device 10 may issue a single-item label with the code information printed on it, assuming that the corresponding customer is a customer who does not use the mobile terminal device 40. However, for example, a customer who intends to use the mobile terminal device 40 may be distracted by something else and forget to operate the mobile terminal device 40 to read the connection information code, or may have difficulty in handling the mobile terminal device 40, causing the predetermined time to elapse.
Therefore, in the weighing pricing device 10 of this embodiment, when a predetermined time has elapsed since the connection information code was displayed on the customer display unit 106, instead of immediately issuing a label, a connection necessity confirmation screen is displayed, thereby prompting the store clerk to confirm whether or not the customer is not using the mobile terminal device 40.

16 shows an example of the connection necessity confirmation screen. The connection necessity confirmation screen in the figure may be displayed, for example, in a pop-up window format so as to be superimposed on the screen that was displayed on the store clerk's display unit 26 until immediately before the label printing operation is performed.
The connection necessity confirmation screen in the figure has a connection information code display button BT1 and a label issue button BT2 arranged thereon. For example, the connection information code display button BT1 is a button that is operated when it is confirmed that the customer is using the mobile terminal device 40 and the store clerk judges that the mobile terminal device 40 should be connected. The label issue button BT2 is a button that is operated to issue a single label when it is confirmed that the customer is not using the mobile terminal device 40 and the store clerk judges that a label may be issued as is.
When the connection necessity confirmation screen is displayed, the store clerk confirms whether or not the customer is going to use the mobile terminal device 40 by observing the customer's appearance or by asking the customer.

In the process shown in FIG. 11, when the pricing is confirmed in step S1103 or step S1104, the connection information code is first displayed on the customer display unit 106 in step S1105.
However, the weighing pricing device 10 may, for example, omit the processes of steps S1105 and S1106, and then display a connection necessity confirmation screen corresponding to step S1108 in response to the pricing being finalized in step S1103 or step S1104. In other words, in this case, in response to the pricing being finalized, the connection necessity confirmation screen is first displayed, and the store clerk determines whether or not the customer is using the mobile terminal device 40, and performs either an operation to display the connection information code or an operation to issue a label. In such a configuration, the store clerk can quickly issue a label when it is determined that the customer is clearly not using the mobile terminal device 40, for example.

Returning to the explanation of FIG.
Step S1109: The weighing and pricing device 10 determines whether or not a confirmation that a connection is not required has been obtained in the state in which the connection necessity confirmation screen has been displayed in step S1108.
If it is confirmed that the person is a customer using a mobile terminal device 40, the store clerk operates the connection information code display button BT1. When the connection information code display button BT1 is operated, the weighing pricing device 10 determines that confirmation that a connection is necessary has been obtained. In this case, the connection necessity confirmation screen is cleared, and processing returns to step S1106. This allows the display of the connection information code on the customer display unit 106, which was started in step S1105, to continue.
In addition, if the connection information code displayed on customer display unit 106 is to be erased in response to the label issuance operation, the process may be returned to step S1105, and the connection information code may be re-displayed on customer display unit 106.

Step S1110: If it is confirmed that the person using the mobile terminal device 40 is not a customer, the store clerk operates the label issuing button BT2 on the connection necessity confirmation screen. If the label issuing button BT2 is operated, the weighing and pricing device 10 determines that it has been confirmed that connection is not required.
In this case, the weighing pricing device 10 issues a single item label reflecting the result of the pricing process for the currently registered product in response to a customer who does not use the mobile terminal device 40. The store clerk attaches the single item label thus issued to the product that is the subject of the current pricing.
Furthermore, when the label issuing button BT2 is operated in this manner, the weighing-pricing device 10 does not need to connect to the mobile terminal device 40. Therefore, the weighing-pricing device 10 may be configured to erase the connection information code displayed in step S1105 at the timing when the label issuing button BT2 is operated.
As shown in Fig. 14, the result of the pricing process is printed as text on the single item label corresponding to a customer who does not use the mobile terminal device 40, and code information is also printed on the single item label corresponding to a customer who does not use the mobile terminal device 40. The code information on the single item label corresponding to a customer who does not use the mobile terminal device 40 includes information that can be read by a device capable of product registration process, such as a POS register operated by a store clerk, a registration device, or a fully self-service POS register, and can be used when executing product registration process.
Such code information may include, for example, a product code, weight or number, unit price (price per weight or unit price per specified number), price, etc. This allows customers who do not use the mobile terminal device 40 to register a priced product at a sales floor where the weighing pricing device 10 is installed (pricing-enabled sales floor) and make a payment.
The code information of the single item label may also be readable by the mobile terminal device 40. Even if a customer uses the mobile terminal device 40, there is a possibility that, for example, a store clerk may mistakenly issue a single item label with code information printed on it. In this case, the weighing pricing device 10 will not transmit the product pricing information to the mobile terminal device 40. Even if this occurs, the mobile terminal device 40 can obtain the product pricing information by reading the code information of the single item label with the mobile terminal device 40.
In this embodiment, even if the code information is printed on the single-item label issued in step S1115 for a customer using the mobile terminal device 40, this does not impede operations such as settlement. Furthermore, in this embodiment, in the case of a customer using the mobile terminal device 40, the mobile terminal device 40 can obtain product pricing information through communication with the weighing pricing device 10 without having to take the trouble of having the mobile terminal device 40 read the code information printed on the single-item label.

Step S1111: The weighing-pricing device 10 executes the connection process started in response to step S1107, and establishes a connection with the mobile terminal device 40.
Step S1111-1: When the weighing-pricing device 10 detects that a connection has been established by the connection process of step S1111, it erases the display of the connection information code displayed in step S1105.

The processing of steps S1112 to S1116 is the same as steps S105 to S109 in FIG. 12. However, in the case of S1115, a single-item label is issued in response to a label issuing operation. The label issuing operation in this case may be, for example, an operation of a predetermined key arranged on the key operation unit 108, or an operation of a predetermined key arranged on the operation screen displayed on the clerk display unit 105. Furthermore, no code information is printed on the issued single-item label. At this time, the weighing and pricing device 10 may display a screen (for example, a pop-up window) on which the label issuing operation is performed in response to receiving a receipt confirmation notification from the mobile terminal device 40 in step S1114.

When issuing the individual label in step S1115, an issuance confirmation screen for confirming whether or not to issue the individual label may be displayed on the store clerk display unit 105.
17 shows an example of the issuance confirmation screen. The issuance confirmation screen in the figure displays a message informing the user that a single-item label will be issued in response to the completion of the transmission of the product pricing information sent in step S1113, and also displays a confirmation button BT3.
The store clerk operates the confirmation button BT3 arranged on the displayed issuance confirmation screen to cause the weighing pricing device 10 to issue a single-item label. Alternatively, the single-item label may be issued after receiving a notification of completion of reception of the product pricing information from the mobile terminal.

Returning to the explanation of FIG.
Step S1117: When it is determined in step S1116 that the pricing of the product corresponding to one transaction is completed, the weighing pricing device 10 determines whether or not it is currently connected to the mobile terminal device 40. If it is determined that it is not connected to the mobile terminal device 40, the weighing pricing device 10 may skip the process of step S1119 and end the process in the figure.

On the other hand, if it is determined in step S1117 that the weighing pricing device 10 is connected, the weighing pricing device 10 executes the processes of steps S1118 and S1119. The processes of steps S1118 and S1119 are the same as steps S110 and S111 in FIG. 12.

The display of the connection information code may be erased, for example, when the single-item label is issued in step S1115, instead of at the timing of step S111-1. Alternatively, the display of the connection information code may be erased, for example, at the timing corresponding to the disconnection of communication with the mobile terminal device 40 in step S1119.

In the above-described exemplary processing procedure, in this embodiment, customers shopping at a sales floor that supports pricing can be served as follows. That is, in the case of customers who do not use a mobile terminal device 40, a single item label with printed code information is affixed to a priced item. This allows even customers who do not use a mobile terminal device 40 to register their items at a POS register or the like. On the other hand, in the case of customers who do use a mobile terminal device 40, there is no need to register items at a POS register or the like, so a single item label without printed code information is affixed to a priced item.
In this manner, in this embodiment, a single item label with code information printed thereon is issued to customers who do not use a mobile terminal device 40, and a single item label without code information printed thereon is issued to customers who do use a mobile terminal device 40. This makes it possible to clearly distinguish whether a priced product is for a customer who uses a mobile terminal device 40 or a customer who does not, based on the presence or absence of code information on the single item label. This allows efficient transactions when selling products priced by the weighing pricing device 10 to both customers who use a mobile terminal device 40 and customers who do not.
In addition, under the process of FIG. 15, the clerk performs the same operation procedure for customers who use the mobile terminal device 40 and customers who do not. Specifically, the clerk performs a pricing operation to cause the weighing pricing device 10 to execute a pricing process corresponding to either step S1103 or step S1104, and then performs an operation to instruct the issuance of a single item label corresponding to step S1115 or step S1110. In other words, the clerk performs the same operation procedure, that is, a pricing operation and then an operation to instruct the issuance of a single item label, whether the clerk is dealing with a customer who uses the mobile terminal device 40 or a customer who does not. Therefore, the clerk is less likely to be confused about the operation whether the clerk is dealing with a customer who uses the mobile terminal device 40 or a customer who does not. This allows for more efficient transactions.
In the explanation of FIG. 15, the label issuing operation corresponding to the single label on which code information is printed is an operation on the label issuing button BT2 located on the connection necessity confirmation screen, but it may be the same operation as in the case of issuing a single label on which code information is not printed in step S1115, for example.

In the example of the processing procedure in FIG. 15, after the metric pricing process in step S1103 or step S1104 is completed and the pricing is finalized, the connection information code is displayed in step S1105.
However, the connection information code may be displayed, for example, before the product registration information is registered in the cart information in response to the transmission of the product pricing information in step S1113 (i.e., the registration of the product is confirmed). As an example, the connection information code may be displayed in accordance with the timing at which the product identification process is executed in step S1102.
In addition, in the example of the processing procedure in FIG. 15, the connection information code is displayed for each product, so that the weighing pricing device 10 and the mobile terminal device 40 are connected for each product of the registered mode. However, the connection between the weighing pricing device 10 and the mobile terminal device 40 may be performed once for multiple products to be registered in one transaction. As an example, the weighing pricing device 10 may display the connection information code corresponding to one transaction at the stage where an operation corresponding to the completion of pricing for one transaction is performed. In this case, the weighing pricing device 10 may transmit product pricing information for all products registered in this one transaction to the connected mobile terminal device 40.

As a modified example of this embodiment, the processes of steps S1108 and S1109 may be omitted. In other words, if a predetermined time has elapsed since the start of displaying the connection information code in step S1106, it may be determined that the customer is not using the mobile terminal device 40, and the connection necessity confirmation screen may not be displayed, and a single label with printed code information may be issued. In this case, the elapse of a predetermined time from the start of displaying the connection information code may be used as a trigger to issue a single label with printed code information even if a label is not issued. In this case, the connection information code may be erased when the predetermined time has elapsed since the start of displaying the connection information code and it becomes time to issue a label. For example, as in the first embodiment, the issuance of a single label in step S1115 may also be triggered by the receipt of a reception confirmation notification in step S1114, and a single label without printed code information may be issued even if a label is not issued.

As another variation of this embodiment, for example, the processes of steps S1108 and S1109 may be omitted, and in step S1106, instead of determining whether a predetermined time has elapsed, it may be determined whether a label issuance operation has been performed to instruct the issuance of a single label on which code information is printed.
In this case, with the connection information code displayed in step S1105, the store clerk checks whether the customer intends to use the portable terminal device 40 by observing the customer's behavior or by asking the customer, etc. Then, if it is confirmed that the customer does not intend to use the portable terminal device 40, the store clerk performs a label issuing operation. As a result, a single label without code information printed thereon is issued in step S1110.
On the other hand, if the store clerk confirms that the customer intends to use the mobile terminal device 40, the store clerk may wait for the customer to perform an operation to have the mobile terminal device 40 read the connection information code. Then, in response to the customer having the mobile terminal device 40 read the connection information code, the processing from step S1111 onward may be executed.

The connection necessity confirmation screen may be in a form in which the connection information code display button BT1 is not arranged, but the label issue button BT2 is arranged. In this case, the weighing pricing device 10 displays the connection information code on the customer display unit 106 and displays the connection necessity confirmation screen on the store clerk display unit 105 at a predetermined timing after the price of the product to be registered is confirmed. In this case, if the customer uses the mobile terminal device 40, the customer has the mobile terminal device 40 read the displayed connection information code and connects the communication between the mobile terminal device 40 and the weighing pricing device 10. The weighing pricing device 10 may erase the connection necessity confirmation screen and the connection information code in response to the establishment of communication. On the other hand, if the customer does not use the mobile terminal device 40, the store clerk operates the label issue button BT2 arranged on the connection necessity confirmation screen. In response to the operation of the label issue button BT2, the weighing pricing device 10 issues a single item label reflecting the result of the pricing process of the product to be registered. In this case, the weighing pricing device 10 may erase the connection necessity confirmation screen and the connection information code in response to pressing the label issuing button BT2.

Third Embodiment
Next, a third embodiment will be described. When a single-item label on which code information is printed is issued for a customer who does not use a mobile terminal device 40 as in the process shown in FIG. 15, the following situation may occur.
In other words, even if an operation corresponding to no connection is performed on the connection necessity confirmation screen displayed in step S1108, after the single-item label with the code information printed on it has been issued, it may be confirmed again that the customer corresponding to the current transaction is the customer using the mobile terminal device 40.
In such a case, the store clerk can reprice the same item, and then have the customer connect the mobile terminal device 40 and the weighing pricing device 10 so that they can communicate with each other, and the item can be registered.
However, in the case of the above-mentioned measures, repricing requires the store clerk to repeat the operation procedure according to the pricing twice for the same product, which may hinder efficient transaction. In particular, when a weighing operation is required to weigh the product, an operation of inputting the tare weight or selecting the tare weight from the tare preset key is required. Usually, the container (tray) is weighed, the tare weight is subtracted, and then the product is weighed. Therefore, when repricing is required, for example, the product must be removed from the container and then weighed again, which is wasteful labor.

In this embodiment, the system is configured so that even after issuing a single-item label with printed code information, products can be registered for customers using the mobile terminal device 40 without repricing.

The flowchart in FIG. 18 shows an example of a processing procedure that the weighing pricing device 10 of this embodiment executes in response to pricing in one transaction. In the figure, steps that are the same as those in FIG. 15 are given the same reference numerals, and descriptions thereof are omitted as appropriate.

Step S1210: After issuing the single-item label on which the code information is printed in step S1110, the weighing pricing device 10 executes the following process. That is, the weighing pricing device 10 determines whether or not a label reissue instruction operation has been performed before the operation to input the item for the next commodity to be priced is performed or before the operation to complete pricing is performed.
After the single label has been issued, if the store clerk confirms that the customer he or she is currently serving is a customer using a mobile terminal device 40, the store clerk performs an operation to instruct the store clerk to reissue the label. The operation to instruct the store clerk to reissue the label may be, for example, an operation on a button arranged at a predetermined position on the store clerk display unit 105. Alternatively, after the single label on which the code information is printed has been issued, a dialogue window for confirming the operation to instruct the store clerk to reissue the label may be displayed on the store clerk display unit 105, and the operation to instruct the store clerk to reissue the label may be performed by operating a predetermined button arranged in the dialogue window.

Step S1211: In response to the label reissue instruction operation, the weighing pricing device 10 becomes ready to input code information. The store clerk then performs an operation to have the scanner unit 104 read the code information of the individual label issued in step S1110. The weighing pricing device 10 acquires the code information read by the scanner unit 104. The individual label whose code information has been read is collected by the store clerk.
It should be noted that the store clerk may perform an operation of inputting a numerical value (entry number) corresponding to the code information, instead of an operation of causing the scanner unit 104 to read the code information.
In response to the label reissue instruction operation, the weighing pricing device 10 may provide a guidance to the store clerk to perform an operation to read the code information of the issued single-item label. Such guidance may be provided by a display on the store clerk display unit 105, a voice output, or the like.

FIG. 19 shows an example of a code information reading guidance screen that is displayed on the store clerk display unit 105 as guidance for inputting the code information of the single item label.
The code information reading guidance screen in the figure displays a message instructing the store clerk on how to input the code information printed on the single item label (by reading it with the scanner unit 104 or by inputting the quantity), and also displays a confirmation button BT3. The store clerk operates the confirmation button BT3 and then performs an operation to input the code information printed on the single item label.

Returning to the explanation of FIG.
Step S1222: The weighing pricing device 10 displays the connection information code on the customer display unit 106. After the process of step S1222, the process proceeds to step S1111.
In this case, the customer performs an operation to have his/her mobile terminal device 40 read the connection information code displayed in step S1222. This causes the mobile terminal device 40 to execute a connection process to establish a communicable connection with the weighing-pricing device 10. At this time, the weighing-pricing device 10 executes the processes of steps S1111 to S1115 and onward. In other words, the product corresponding to the single item label on which the code information is printed is registered in the cart information in the transaction management server 50 by being sent again as product pricing information in step S1113. In other words, the product is treated as a registered product in the transaction using the mobile terminal device 40.

In addition, if the code information of the individual item label is configured to include a transaction number, the weighing pricing device 10 may reissue the individual item label including the code information read in step S1211, and transmit the product pricing information including the transaction number to the mobile terminal device 40.
On the other hand, for example, if the code information on the individual item label includes product number and amount information but does not include a transaction number, the weighing pricing device 10 may calculate the weight from the unit price by weight of the item (which may be obtained, for example, from the item master or entered by a store clerk) and the amount included in the code information read in step S1211, and then reissue the individual item label.
In addition, since settlement can be performed using information such as the product number and price of a product, the weighing pricing device 10 may transmit at least information such as the product number and price of the corresponding product to the mobile terminal device 40.
Furthermore, the label issuance history may be stored in a predetermined device in the sales system of this embodiment. In this case, the weighing pricing device 10 may use, for example, predetermined information included in the code information read in step S1211 as a search key to search for a corresponding label issuance history from among the stored label issuance history, and transmit the searched label issuance history as product pricing information.

Fourth Embodiment
Next, a fourth embodiment will be described.
In the first embodiment, the weighing and pricing device 10 issues a single-item label corresponding to one commodity every time the pricing of one commodity is determined in one transaction.
In contrast, the weighing pricing device 10 of this embodiment issues an addition label printed with information indicating the total price of the items priced in one transaction upon completion of pricing for one transaction.

20 shows an example of an addition label, in which the names of three items whose prices have been determined in one transaction, the prices of each item, and the total amount of the prices of each item are printed.
Also, the addition label in the figure has code information (an example of a barcode is shown in the figure) printed on it. In this embodiment, the information printed on the barcode of the addition label is not particularly limited as long as it is information that the weighing pricing device 10 can obtain in response to the pricing process of the product in one transaction. As the simplest example, the code information on the addition label may indicate, for example, the department code corresponding to the sales floor where the weighing pricing device 10 is located, and information on the total price of the product.
Furthermore, the code information of the accumulator label may include a transaction identifier and information for each product whose price has been determined in one transaction. With this type of accumulator label code information, when correcting the transaction record after a settlement process such as a return, for example, the settlement device 20 can read the code information of the accumulator label to call up the transaction record and make the correction. Also, inspection of products sold by weight in one transaction is possible by having the settlement device 20 read the code information of the accumulator label.

An example of a processing procedure of the weighing and pricing device 10 in this embodiment will be described with reference to FIG.
As a processing procedure of the weighing pricing device 10 of this embodiment, first, step S108 in Fig. 12 may be omitted. Then, after it is determined in step S109 that the pricing of the product according to one transaction is completed, a step of issuing an additional label is added.

The weighing pricing device 10 may be configured to issue a single-item label each time the pricing of an item is determined, and to issue an add-on label upon completion of pricing for one transaction.
In this way, when issuing individual labels for each item whose pricing has been determined in addition to the additive label, if the code information on the additive label includes a transaction identifier and information for each item whose pricing has been determined in a transaction, printing of the code information on the individual labels may be omitted.

Moreover, when the fourth embodiment is applied to the second or third embodiment, the following configuration may be adopted.
For example, when based on the flowchart of Figure 15 or Figure 18, the processes of steps S1110 and S1115 are omitted. In addition, a step of issuing an additional label is added after it is determined in step S1117 that the pricing of the product for one transaction has been completed.
In this case, the step of issuing the accumulator label may be such that if the portable terminal device 40 has not been connected to the weighing pricing device 10, an accumulator label with code information printed on it is issued, and if it has not been connected, an accumulator label without code information printed on it is issued.

Fifth Embodiment
Next, a fifth embodiment will be described.
Fig. 21 shows an example of the configuration of a sales system according to this embodiment. In this figure, the same parts as those in Fig. 1 are given the same reference numerals and the description thereof will be omitted.
The sales system in the figure further includes a metered sales management server 60. The metered sales management server 60 is communicatively connected to each of the metered pricing devices 10. The metered sales management server 60 is also communicatively connected to the transaction management server 50.
The metered sales management server 60 manages product pricing information that reflects the results of the pricing process executed by the metered pricing device 10 .

Although not shown in the figure, the configuration of the metered sales management server 60 may be configured to include a CPU, a memory unit, a RAM, and a communication unit, similar to the transaction management server 50 in FIG. 8.

Referring to the sequence diagram of Figure 22, an example of the processing procedure executed by the weighing pricing device 10, the mobile terminal device 40, the transaction management server 50, and the weighing sales management server 60 of this embodiment in relation to product registration in one transaction will be described.
Step S1001: The weighing pricing device 10 executes a pricing process for one product in response to a product pricing operation by a store clerk.
Step S1002: When the pricing of the product is confirmed in step S1001, the metered pricing device 10 transmits product pricing information indicating the result of the confirmed product pricing process to the metered sales management server 60. The transmitted product pricing information includes a product pricing information identifier that uniquely identifies the product pricing information.
Step S1003: When the metered sales management server 60 receives the product pricing information transmitted in step S1002, it stores product registration information reflecting the contents of the received product pricing information. The product registration information to be stored is associated with the product pricing information identifier of the received product pricing information.

Step S1004: In response to executing the pricing process in step S1001, the weighing pricing device 10 causes the customer display unit 106 to display a connection information code along with the transmission of the product pricing information in step S1002. The connection information code displayed here includes control information for the mobile terminal device 40 to connect to the transaction management server 50 so that it can communicate with the transaction management server 50. The connection information code also includes a product pricing information identifier that uniquely identifies the product pricing information transmitted in step S1002.

Step S1005: The mobile terminal device 40 displays the product registration screen and is in a state where the code can be read. The customer then operates the mobile terminal device 40 to cause the mobile terminal device 40 to read the connection information code displayed on the customer display unit 106.
Step S1006: The mobile terminal device 40 executes a connection process with the transaction management server 50 in accordance with a connection procedure based on the control information included in the connection information code read in step S1005.

Step S1007: When a connection with the transaction management server 50 is established by the connection process of step S1006, the mobile terminal device 40 transmits to the transaction management server 50 the product pricing information identifier included in the connection information read in step S1005.
Step S1008: The transaction management server 50 that has received the product pricing information identifier in step S1007 transmits a product registration information request including the received product pricing information identifier to the metered sales management server 60.
Step S1009: In response to receiving the product registration information request, the metered sales management server 60 searches for product registration information stored therein that corresponds to the product pricing information identifier included in the received product registration information request. The metered sales management server 60 transmits the searched product registration information to the transaction management server 50.
Step S1010: The transaction management server 50 registers the received product registration information in the cart information.

Step S1011: The transaction management server 50 registers the product registration information in the cart information in step S1010, completing the product registration for one product for which the weighing pricing device 10 performed the pricing process in step S1001. The transaction management server 50 then transmits a registration completion notification to the mobile terminal device 40.
In addition, the mobile terminal device 40 that receives the registration completion notification may, for example, display a message informing the customer that product registration has been completed for one product that was the subject of the pricing process executed by the weighing pricing device 10 in response to the connection information code read this time.

Step S1012: The transaction management server 50 also transmits a receipt confirmation notice indicating that the product registration information transmitted in step S1009 has been normally received to the metered sales management server 60. The receipt confirmation notice includes a product pricing information identifier that identifies the corresponding product registration information.
Step S1013: In response to receiving the receipt confirmation notification sent in step S1012, the metered sales management server 60 manages the product registration information stored therein, including the product registration information indicated by the product pricing information identifier included in the receipt confirmation notification, so that it indicates that it has been sent.

Step S1014: After the process of step S1013, the metered sales management server 60 transmits a registration completion notification to the metered pricing device 10 that transmitted the product pricing information in step S1002.
Step S1015: In response to receiving the registration completion notification sent in step S1014, the weighing pricing device 10 issues a single-item label reflecting the result of the pricing process in step S1001.

Step S1015-1: In response to receiving the registration completion notification sent in step S1014, the weighing pricing device 10 erases the connection information code displayed in step S1004.

The processing of steps S1001 to S1015 is referred to as "loop processing 1" and is executed repeatedly each time a product pricing operation is performed on the weighing pricing device 10 for each product in response to a customer's designation of a product sold by weight for purchase in a transaction.

Step S1016: When the store clerk confirms that pricing has been completed for all products designated by the customer in one transaction, the store clerk performs an operation to declare the completion of pricing for one transaction (pricing completion operation) on the weighing pricing device 10. In response to the price completion operation being performed, the weighing pricing device 10 determines that pricing of the products in one transaction has been completed.
Step S1017: When it is determined that the pricing of the products corresponding to one transaction is completed, the weighing pricing device 10 transmits a pricing completion notification to the weighing sales management server 60. The pricing completion notification indicates that the pricing process for all products corresponding to one transaction is completed.
Step S1018: In response to receiving the pricing completion notification sent in step S1017, the volumetric sales management server 60 sends (or may forward) a pricing completion notification to the transaction management server 50.
Step S1019: In response to receiving the bidding completion notification transmitted in step S1018, the transaction management server 50 transmits (or may forward) the bidding completion notification to the mobile terminal device 40. The mobile terminal device 40 that has received the bidding completion notification may display, for example, the settlement guide screen of Fig. 11D. In addition, in response to receiving the bidding completion notification at the mobile terminal device 40 in step S1019, a process may be executed such that the connection between the mobile terminal device 40 and the transaction management server 50 is disconnected.

In this embodiment, the connection information code may be erased, for example, in response to the transaction management server 50 establishing a connection with the mobile terminal device 40 by the connection process of step S1006. In this case, the connection information code includes weighing pricing device identification information that identifies the corresponding weighing pricing device 10. When the mobile terminal device 40 establishes communication with the transaction management server 50, it transmits the weighing pricing device identification information included in the connection information code to the transaction management server 50. The transaction management server 50 transmits a connection establishment notification to the weighing pricing device 10 identified by the received weighing pricing device identification information. In response to receiving the connection establishment notification, the weighing pricing device 10 erases the connection information code.
Alternatively, the connection information code may be deleted in response to the registration of the product in the cart information in step S1010. In this case, the connection information code also includes weighing-pricing device identification information for identifying the corresponding weighing-pricing device 10. When the mobile terminal device 40 establishes communication with the transaction management server 50, the mobile terminal device 40 transmits the weighing-pricing device identification information included in the connection information code to the transaction management server 50. The transaction management server 50 stores the received weighing-pricing device identification information. When the transaction management server 50 completes the registration of the product in the cart information in step S1010, the transaction management server 50 transmits a registration completion notification in step S1011 not only to the mobile terminal device 40 but also to the weighing-pricing device 10 indicated by the stored weighing-pricing device identification information. In response to receiving the registration completion notification, the weighing-pricing device 10 deletes the connection information code.
Alternatively, the weighing pricing device 10 may start displaying the connection information code in response to the pricing process of the first item in the pricing of a transaction, and then continue to display the code thereafter, until it is erased when the pricing of that transaction is completed.

In this embodiment, the weighing pricing device 10 and the mobile terminal device 40 are not directly connected to be able to communicate with each other, but the weighing pricing device 10 and the mobile terminal device 40 are connected to the weighing sales management server 60 and the transaction management server 50, respectively, and the weighing sales management server 60 and the transaction management server 50 communicate with each other. As a result, the weighing pricing device 10 can issue a single item label in response to receiving a notification from the weighing sales management server 60 that the registration of the product registration information corresponding to the product pricing in the cart information has been completed (i.e., the registration completion notification transmitted in step S1014) by the process in the figure. Even in this case, if the weighing pricing device 10 transmits the product pricing information but the transaction management server 50 does not register the corresponding product registration information in the cart information, the weighing pricing device 10 does not issue a single item label. As a result, the weighing pricing device 10 issues only the single item label of the product to be priced, the corresponding product registration information of which is registered in the cart information.
In this case, the store clerk and the customer can confirm that the registration of the product subject to the pricing process to the cart information has been successfully completed by issuing a single-item label. In this embodiment, the customer can also confirm that the registration of the product subject to the pricing process to the cart information has been successfully completed by the notification provided by the mobile terminal device 40 in response to receipt of the registration completion notification (step S1011).

The configurations of the second and third embodiments can also be applied to this embodiment. In this case, the weighing and pricing device 10 may execute the same process as the flowchart in FIG. 15 or FIG. 18.

As a variation of this embodiment, the second embodiment may be applied so that the weighing pricing device 10 issues an accumulating label printed with information indicating the total amount of the items priced in one transaction upon completion of pricing in one transaction. Alternatively, the weighing pricing device 10 may issue a single item label each time the pricing of an item is finalized, and issue an accumulating label upon completion of pricing in one transaction.

<Modification>
Modifications corresponding to the first to fifth embodiments will be described below.

[First Modification]
There are two types of products sold by weight: variable weight products and fixed weight products. Variable weight products have a set price per weight, and customers can purchase them by any weight (or number). The price of variable weight products is calculated by multiplying the measured weight of the product by the price per weight.
A fixed-price product is a product for which the weight and unit price per unit are set, and the customer decides the number of products to purchase.
In the above embodiments, the weighing pricing device 10 performs pricing processing for non-fixed-weight products, but may perform pricing processing for fixed-weight products. In the case of fixed-weight products, the weighing pricing device 10 calculates the number of items purchased by dividing the weight measured by the weighing unit 109 by the unit price by weight, and calculates the price by multiplying the calculated number of items by the unit price.

[Second Modification]
In each of the above embodiments, the item number of the commodity to be priced (registered) may be input by a method other than operating the preset keys on the store clerk display unit 105 of the weighing pricing device 10.
For example, the weighing pricing device 10 may be provided with an imaging unit that captures images of commodities to be priced, and the weighing pricing device 10 may be able to identify the item of the commodity to be priced based on the analysis results of the image captured by the imaging unit. Note that, for example, the transaction management server 50 may receive an image of the commodity from the weighing pricing device 10, identify the item of the commodity to be priced based on the analysis results of the received image, and notify the weighing pricing device 10 of the identified item of the commodity from the transaction management server 50.
In this case, the store clerk causes the imaging unit of the weighing pricing device 10 to capture an image of the product to be priced, and the weighing pricing device 10 inputs the item name of the product imaged by the imaging unit as the item name of the product to be priced.

Also, for example, a tag device may be placed at a position corresponding to each of the displayed bulk products on the store clerk side. The tag device is connected to the weighing and pricing device 10 so as to be able to communicate with the weighing and pricing device 10 via wired or wireless communication. The tag device also stores product information indicating the corresponding bulk product. The tag device is equipped with a touch sensor, so that it can detect contact by a touch operation.
In this case, the store clerk performs a touch operation on the tag device corresponding to the product that the customer has notified them of as a purchase target. The tag device that detects the touch operation transmits the product information stored therein to the weighing pricing device 10. The weighing pricing device 10 uses the received product information to input the item name of the product to be priced.
The tag devices may be provided at positions corresponding to the displayed bulk products so that the customer can perform a touch operation. In this case, the customer performs a touch operation on the tag device corresponding to the product to be purchased.

A motion sensor that detects motion may be provided on a lid, lever, or other part that moves when a product is removed from a display unit that stores products sold by weight. The motion sensor can detect motion using, for example, an acceleration sensor, and stores product information indicating the corresponding product sold by weight. In response to detecting motion, the motion sensor transmits the product information stored therein to the weighing pricing device 10.
In this case, for example, the store clerk takes out from among the displayed products the product that the customer has indicated as the product to be purchased. In response to the product being taken out, the motion sensor corresponding to the product to be purchased detects the motion. In response to the detection of the motion, the motion sensor transmits the product information stored therein to the weighing pricing device 10. The weighing pricing device 10 uses the received product information to input the item name of the product to be priced.
For example, in a store, products sold by weight may be displayed so that customers can take out the products. In this case, the customer takes out the product to be purchased from the display area and hands it over to a store clerk. In this case, when the customer takes out the product, product information is transmitted from the motion sensor, and the weighing pricing device 10 inputs the item of the product to be priced.

[Third Modification]
In the process shown in FIG. 12, there may be cases where the weighing and pricing device 10 is unable to receive the receipt confirmation notice in step S107 due to some cause.
Examples of cases in which the reception confirmation notice cannot be received include the following. One is a case in which the commodity pricing information that should be transmitted by the weighing pricing device 10 is not transmitted normally in step S106. Another is a case in which the commodity pricing information is transmitted in step S106, but the commodity pricing information is not received normally by the mobile terminal device 40. Another is a case in which the reception confirmation notice that should be transmitted by the mobile terminal device 40 in step S205 is not transmitted normally. Another is a case in which the commodity pricing information is transmitted in step S205, but the reception confirmation notice is not received normally by the weighing pricing device 10.

If the weighing pricing device 10 does not receive a receipt confirmation notification within a certain period of time after executing the process of step S106 to transmit the commodity pricing information and a timeout occurs, the weighing pricing device 10 determines that a commodity pricing information transmission/reception error has occurred. If it determines that a commodity pricing information transmission/reception error has occurred, the weighing pricing device 10 is configured to notify, for example, on the clerk display unit 105, that a commodity pricing information transmission/reception error has occurred. Note that the customer display unit 106 may also be configured to notify that a commodity pricing information transmission/reception error has occurred.

In response to the notification of the occurrence of an error in transmitting/receiving product pricing information as described above, for example, a store clerk may ask the customer to check whether the corresponding product has been registered properly. The customer can check, for example, by looking at a display on the mobile terminal device 40, whether the transmission and reception of product registration information with the transaction management server 50 corresponding to step S206 has been performed properly (whether the corresponding cart information has been registered properly on the transaction management server 50).
If it is confirmed that the product registration information is being sent and received normally, it means that the product registration was performed normally, but only that an error occurred in sending and receiving the reception confirmation notice, so no special action is required. Alternatively, for example, the customer may be asked to perform an operation to resend the reception confirmation notice from the mobile terminal device 40, and the weighing pricing device 10 may process the product pricing information transmission/reception error as having been resolved when the reception confirmation notice is received.

In addition, in response to a notification of an error in transmitting or receiving product pricing information, the weighing pricing device 10 may issue a label (re-registration label) on which a pricing information code (which may be a barcode or a two-dimensional code) reflecting the pricing information of the corresponding product is printed.
When issuing a re-registration label, a dialog window for asking the store clerk whether or not to issue a re-registration label may be displayed on the store clerk display unit 105. In this case, if the store clerk receives confirmation that the product registration information has been normally transmitted and received with the transaction management server 50, the store clerk performs an operation on the dialog window to declare that it is not necessary to issue a re-registration label. On the other hand, if the store clerk receives confirmation that the product registration information has not been normally transmitted and received with the transaction management server 50, the store clerk performs an operation on the dialog window to instruct the issuance of a re-registration label.
When a re-registration label has been issued, the store clerk hands it to the customer. The customer has the mobile terminal device 40 read the pricing information code printed on the re-registration label that was given to them. The mobile terminal device 40 transmits the product pricing information indicated by the read pricing information code to the transaction management server 50 as product registration information. This results in the registration of cart information to the transaction management server 50 for the product corresponding to the product pricing information transmission/reception error.

[Fourth Modification]
In the above-described embodiments, the connection information code is displayed each time a pricing process is performed for each product in one transaction. In this modified example, the connection information code is displayed in correspondence with one transaction.
In this case, for example, before the first pricing operation of a commodity sold by weight in one transaction, a store clerk performs a predetermined operation on the weighing pricing device 10, thereby causing the connection information code to be displayed on the customer display unit 106. Alternatively, the connection information code may be included in a standby screen displayed on the customer display unit 106 while waiting for the first pricing operation in one transaction, for example.

In this case, the customer has the mobile terminal device 40 read the connection information code displayed on the customer display unit 106 before the first product is priced. The mobile terminal device 40 establishes a connection with the weighing pricing device 10 according to the connection conditions (connection procedure) indicated by the read connection information code. In this case, the weighing pricing device 10 may erase the display of the connection information code in response to detecting the establishment of a connection with the mobile terminal device 40, for example.

When communication is established, the weighing and pricing device 10 executes a process of associating the current transaction with the mobile terminal device 40, which is the communication partner. To do this, the weighing and pricing device 10 acquires a terminal identifier from the mobile terminal device 40, which is the communication partner, for example. The terminal identifier may be an identifier that is assigned individually to each piece of hardware as the mobile terminal device 40, such as a MAC address, or it may be an application identifier that is assigned to a shopping application installed on the mobile terminal device 40.

In addition, when communication is established and a connection is made with the mobile terminal device 40, the weighing pricing device 10 may display a clerk designation screen on the clerk display unit 105, where an operation is performed to associate the clerk in charge of pricing operations for the current transaction.
Fig. 23 shows an example of a clerk designation screen. In the clerk designation screen in the figure, clerk buttons are arranged. Each clerk button is displayed with a character or the like indicating the corresponding clerk, thereby indicating the correspondence with the clerk. In the figure, three clerk buttons are arranged, and an example is shown in which they are indicated as "clerk A", "clerk B", and "clerk C".
The clerk button may display, for example, the name, title, etc. of the clerk. The clerk corresponding to the displayed clerk button is the clerk currently registered (logged in) as the clerk in charge of the sales floor for bulk products. Note that the clerk button of the clerk currently serving another customer and performing pricing operations on another weighing pricing device 10 is shown as inoperable by, for example, being arranged with a diagonal line as shown in the figure (or may be grayed out, etc.).
The store clerk then performs an operation on the store clerk button corresponding to him/her among the displayed store clerk buttons.
Also, an "Add" button is provided on the clerk designation screen. For example, there may be a situation where a clerk needs to deal with a customer before logging in as the clerk in charge of the sales floor. In such a case, the clerk button corresponding to the clerk who is not logged in is not displayed on the clerk designation screen. In this case, the clerk can operate the "Add" button and then log in on the spot by, for example, having the weighing pricing device 10 read his/her clerk identifier. In response to the login, the clerk designation screen further displays a clerk button for the corresponding clerk in addition to the clerk buttons that have been displayed up until now.

The weighing pricing device 10 associates the clerk identifier of the clerk indicated by the operated clerk button with the terminal identifier obtained from the mobile terminal device 40 with which it is communicating. The weighing pricing device 10 also manages the product pricing information for each product corresponding to the pricing operation performed under the corresponding transaction in association with the clerk identifier. This makes it possible to uniquely identify the transaction corresponding to the mobile terminal device 40.

In addition, instead of operating the clerk button, the clerk identifier may be obtained by, for example, having the scanner unit 104 of the weighing and pricing device 10 read the code information of the clerk identifier attached to the clerk ID card held by the clerk. The clerk ID may be in the form of an IC (Integrated Circuit) card on which the clerk identifier is stored, and the clerk identifier may be obtained from the IC card by a card reader provided in the weighing and pricing device 10. In addition, when communication is performed when an RFID (Radio Frequency Identifier) card or the like as the clerk ID and the weighing and pricing device 10 are within a communication range of each other by a predetermined short-distance wireless communication, the weighing and pricing device 10 may obtain the clerk identifier stored in the clerk ID with which it can communicate. In this case, when there are multiple clerk IDs with which it can communicate, the clerk identifier may be obtained from, for example, the clerk ID with the strongest reception strength (i.e., the clerk ID of the clerk located closest to the weighing and pricing device 10).

In addition, a transaction identifier (transaction number) may be further associated with the mobile identifier, clerk identifier, and product pricing information. Alternatively, the transaction identifier may be associated instead of the clerk identifier. For example, in an operation that does not manage the association between clerks and transactions as described above, the clerk identifier is not used, so by associating the transaction identifier instead of the clerk identifier, it becomes possible to associate the mobile terminal device 40 with the transaction.
As described above, when associating a transaction identifier, the weighing pricing device 10 may display a number of transaction selection buttons showing a predetermined mark such as a graphic or a predetermined color instead of the clerk button, and associate the mark and color attached to the transaction selection button operated by the clerk from among the displayed transaction selection buttons with the transaction.

When a connection information code is displayed corresponding to one transaction as in this modified example, the weighing pricing device 10 does not need to transmit commodity pricing information to the mobile terminal device 40 each time pricing processing is performed on a commodity basis. In other words, the weighing pricing device 10 may transmit commodity pricing information for all priced commodities to the mobile terminal device 40, for example, at the stage when pricing processing for all commodities corresponding to one transaction is completed.
Furthermore, in the case where a connection information code is displayed corresponding to one transaction as in this modified example, by associating the transaction with the mobile terminal device 40 as described above, it is possible to allow a pricing operation for another transaction to be inserted between the start and completion of a pricing operation for one transaction for one weighing pricing device 10. In other words, it becomes possible for one weighing pricing device 10 to perform pricing processing for a plurality of transactions in parallel.
This allows the clerk to merchandise the next item to be priced, for example, if the previous customer is unsure of which item to have priced next, or if for some reason the customer is forced to temporarily take an action other than meeting the clerk there and then, by storing the details of the previous customer's previous transactions (item pricing information), the clerk can price the item for the next customer.

In addition, in the above example, as a mode of displaying a connection information code corresponding to one transaction, the connection information code is displayed on the customer display unit 106 at a stage prior to the pricing operation of the first bulk product in one transaction, so that the weighing pricing device 10 and the mobile terminal device 40 are connected at a stage prior to the start of pricing of the product corresponding to one transaction.

However, as a mode for displaying the connection information code corresponding to one transaction, for example, the connection information code may be displayed at a timing corresponding to the first pricing of a commodity sold by weight in one transaction, similar to step S103 in FIG.
Alternatively, as a mode for displaying the connection information code corresponding to one transaction, the connection information code may be displayed at the stage where pricing of all products in one transaction is completed.

24 shows an example of a connection information code screen that is displayed on the customer display unit 106 when pricing for all products in one transaction is complete. This figure shows an example of a connection information code screen when the customer display unit 106 has a vertically long display surface and the display screen is written in English.
On the connection information code screen in the figure, similarly to FIG. 13, a connection information code in the form of a two-dimensional code is displayed, and an image of a mobile terminal device is also displayed together with an arrow pointing to the two-dimensional code.
The connection information code screen in the figure also displays pricing-related information (product name, measured weight, price, etc.) for one or more products for which pricing processing has been performed so far in the corresponding transaction.
In this case, too, the store clerk display unit 105 may be configured to display a message, pop-up window, icon, etc. to inform the store clerk that the connection information code is being displayed on the customer display unit 106.
In this way, even if the connection information code is displayed at the stage when pricing of all bulk items in a transaction has been completed, the weighing pricing device 10 may erase the display of the connection information code upon detecting the establishment of a connection with the mobile terminal device 40.

[Fifth Modification]
"Product registration handover" may be possible between multiple weighing pricing devices 10. Product registration handover means that after a store clerk registers products in one transaction at one weighing pricing device 10, the store clerk moves to another weighing pricing device 10 and registers products in the same transaction. In product registration handover, product registration information corresponding to product registration previously performed at a weighing pricing device 10 in the same transaction is handed over to the next weighing pricing device 10. The next weighing pricing device 10 can add information about products registered by its own product registration process to the handed over product registration information.

For example, a customer may specify a product that is displayed in a location far from the weighing and pricing device 10 that the store clerk is currently operating. By making "product registration handover" possible, the store clerk can go to the specified product, pick up the product, and continue registering the product using another weighing and pricing device 10 installed in the nearest location.

In this modified example, the "product registration handover" is realized by having one of the multiple weighing and pricing devices 10 function as a parent, and then the parent weighing and pricing device 10 and the child weighing and pricing device 10 being connected so that they can communicate with each other.
The child weighing pricing device 10 associates the commodity pricing information for each priced commodity with the clerk identifier of the clerk who performed the pricing operation (alternatively, a transaction identifier may be associated instead of the clerk identifier, or both the clerk identifier and the transaction identifier may be associated), and transmits it to the parent weighing pricing device 10. For example, every time a clerk starts operating one weighing pricing device 10, the clerk has the weighing pricing device 10 read the clerk identifier recorded on the clerk's clerk ID card, or operates the number of items placed or a specified button, thereby causing the weighing pricing device 10 to obtain the clerk identifier and log in. Every time a clerk changes the weighing pricing device 10 that performs the pricing operation in response to product registration handover, the clerk has the weighing pricing device 10 obtain the clerk identifier.
Each time product pricing information is received, the parent weighing pricing device 10 stores integrated product pricing information that integrates the received product pricing information for each of the same store clerk identifiers.

When the clerk has finished pricing all the products in one transaction, he or she performs a pricing completion operation. In response to the pricing completion operation being performed, the weighing pricing device 10 displays a connection information code on the customer display unit 106.
When the customer causes the portable terminal device 40 to read the displayed connection information code, and the portable terminal device 40 and the weighing-pricing device 10 are connected to each other so that they can communicate with each other, the portable terminal device 40 transmits the store clerk identifier included in the connection information code to the weighing-pricing device 10. The display of the connection information code may be erased in response to detecting that the weighing-pricing device 10 has been connected to the portable terminal device 40 so that they can communicate with each other.
The weighing pricing device 10 that has received the store clerk identifier transmits to the mobile terminal device 40 the integrated product pricing information associated with the received store clerk identifier from the integrated product pricing information stored in the parent weighing pricing device 10. The mobile terminal device 40 transmits the received integrated product pricing information to the transaction management server 50 as product registration information for all priced products. The transaction management server 50 registers information for each product indicated in the received product registration information as cart information.
Even when "product registration transfer" is possible as in this modified example, the transaction may be associated with the mobile terminal device 40 as in the second modified example.
The process corresponding to the function as the parent weighing pricing device may be executed by, for example, a higher-level management device or the transaction management server 50. Alternatively, each time a store clerk moves from one weighing pricing device 10 to another and logs in by inputting a store clerk identifier, the commodity pricing information of the corresponding transaction stored in the source weighing pricing device 10 is transmitted to the destination weighing pricing device 10, and the transmitted commodity pricing information is integrated with the commodity pricing information obtained by the pricing process at the destination.

In addition, in the case where product registration handover is possible as described above, each time the pricing process of a product is completed, the weighing pricing device 10 may display a connection information code on the customer display unit 106. In this case, too, the connection information code may be erased in response to each completion of the pricing process of a product, when the customer has the mobile terminal device 40 read the connection information code, and the weighing pricing device 10 and the mobile terminal device 40 are connected so as to be able to communicate with each other.
Then, when the store clerk moves the weighing pricing device 10 where the pricing operation is performed in order to take over the product registration, the connection between the weighing pricing device 10 from which the store clerk moved and the mobile terminal device 40 is disconnected, even though the pricing of one transaction is not completed.
The following manners are conceivable for disconnecting the connection between the source weighing and pricing device 10 and the portable terminal device 40.
First, when a store clerk who has been performing pricing operations using the source weighing pricing device 10 needs to move to the destination weighing pricing device 10 in response to the same transaction and perform pricing operations there, a logout operation is performed on the source weighing pricing device 10. In response to the logout operation, the source weighing pricing device 10 cuts off the connection with the current mobile terminal device 40 in response to the logout state being entered.
Alternatively, when the store clerk starts a pricing operation at the destination weighing pricing device 10 by taking over the product registration, the source weighing pricing device 10 may disconnect the connection to the current mobile terminal device 40 in response to the destination weighing pricing device 10 acquiring the store clerk's store clerk identifier. In this case, the store clerk may move to the destination weighing pricing device 10 without performing a logout operation on the source weighing pricing device 10.
In this case, the source metered pricing device 10 disconnects the connection with the current mobile terminal device 40 in response to receiving a notification from the destination metered pricing device 10 that the same store clerk as the one currently logged in has logged in through communication with the destination metered pricing device 10. Furthermore, the source metered pricing device 10 also disconnects the connection with the current mobile terminal device 40 if another store clerk logs in before receiving a notification from the destination metered pricing device 10 that the same store clerk has logged in.
In other words, in this case, the connection between the source weighing-pricing device 10 and the mobile terminal device 40 may be disconnected at a predetermined timing before logging in to the destination weighing-pricing device 10 .
Even if the connection between the source weighing pricing device 10 and the mobile terminal device 40 is cut off in any of the above-mentioned ways, the parent weighing pricing device 10 associates and manages the clerk identifier and the product pricing information for the same transaction until an operation to declare the completion of pricing for the transaction is performed. As a result, even if the same clerk performs pricing operations on any of the weighing pricing devices 10 in response to the same transaction, the product pricing information for the same transaction is properly integrated.

In addition, for example, connection correspondence information that associates the clerk identifier of the operator (the clerk who logged in to the weighing pricing device 10) who performs the pricing operation corresponding to one transaction with the terminal identification information of the mobile terminal device 40 connected to the logged-in weighing pricing device 10 (for example, information such as the device ID of the mobile terminal device 40 used for the connection) may be stored in the weighing pricing device 10. The connection correspondence information may be stored by the logged-in weighing pricing device 10 or may be stored by the parent weighing pricing device 10.
By storing the connection correspondence information in this manner, for example, when a store clerk moves to another weighing-pricing device 10 and logs in due to product registration handover, it becomes possible to automatically connect the weighing-pricing device 10 and the mobile terminal device 40 without using a connection information code.
In other words, in response to a store clerk moving to another weighing-pricing device 10 and logging in, the logged-in weighing-pricing device 10 acquires connection correspondence information including the same store clerk identifier acquired by the login. The logged-in weighing-pricing device 10 may then execute a process of connecting to the corresponding mobile terminal device 40 using the terminal identification information included in the acquired connection correspondence information.

Sixth Embodiment
Next, a sixth embodiment will be described. The first to fifth embodiments correspond to a face-to-face method in which a store clerk faces a customer to measure and price products sold by weight.
In contrast, the present embodiment corresponds to a self-service system in which a customer weighs and prices products sold by weight. In the case of the self-service system, a store clerk who operates a weighing and pricing device may not be present.

The configuration of the sales system corresponding to this embodiment may be the same as that of Fig. 2. However, the sales system in this embodiment is provided with a weighing pricing device 10A having a different configuration from the weighing pricing device 10. The configuration of the weighing pricing device 10A may be the same as that of Fig. 3, for example, but the clerk display unit 105 may be omitted.
In a store that is compatible with the sales system of this embodiment, customers can measure and price products sold by weight as described below.

When a customer wishes to purchase a product sold by weight, the customer first inputs the item name of the product to be purchased as follows.
25 shows an example of a display of products sold by weight in a store. In the example shown in the figure, lemons LM, apples AP, and oranges OG are displayed as products sold by weight. Also, product information panels 3000-LM, 3000-AP, and 3000-OG are installed corresponding to the displayed lemons LM, apples AP, and oranges OG. When no particular distinction is made between the product information panels 3000-LM, 3000-AP, and 3000-OG, they will be referred to as product information panel 3000.

The product information panel 3000 presents information on the corresponding product. In the figure, the product information panel 3000-LM is shown enlarged. Thus, the product information panel 3000-LM presents, as product information, that the product's item is lemon, the unit price per unit weight, and a product information code 3001. In the example shown in the figure, the product information code 3001 is a barcode (one-dimensional code). The product information code 3001 includes the product code of the product's item name as lemon.
Similarly, the other product information panels 3000 also present product information such as the product category, unit price per unit weight, and product information code.

The product information panel 3000 may be configured to present product information by displaying it on a display device, or may be configured to present product information by attaching a printed matter such as a poster to the product information panel 3000.
By presenting product information on a display device, it is possible to display at the appropriate time a price reduction that reflects time-limited special offers, etc. Also, by changing and displaying barcodes over time, it is possible to prevent fraudulent acts such as registering products sold by weight at different unit prices by having the mobile terminal device 40 read barcodes that have been photographed in advance by a camera.

When inputting the item of the product to be purchased, the customer displays the product registration screen on his/her mobile terminal device 40 and has the mobile terminal device 40 read the product information code displayed on the product information panel 3000 of the product to be purchased. The figure shows the customer reading the product information code 3001 corresponding to lemon LM. The scanned image area AR11 on the product registration screen of the mobile terminal device 40 shows the image of the product information code 3001.
When the product information code 3001 corresponding to lemon LM is thus code scanned, the mobile terminal device 40 acquires product information of lemon LM from the read product information code 3001. Using the acquired product information, the mobile terminal device 40 designates lemon LM as an item of merchandise sold by weight.

Furthermore, a product registration status area AR12 is arranged on the product registration screen. The product registration status area AR12 shows the current registration status of the product to be purchased. In the figure, a total area AR121 and registration list items AR122 (AR122-1, AR122-2, AR122-3) are arranged in the product registration status area AR12. The registration list items AR122 are list items that individually show registered products or products in a provisional registration state where item information has been input.
In the figure, as the registration list item AR122, registration list items AR122-1, AR122-2, and AR122-3 corresponding to yogurt, apples AP, and lemons LM are arranged.
In this case, yogurt is not a product sold by weight, so in the registration list item AR122-1 for yogurt, "x1" is displayed in the comment display CM, indicating that one unit has been registered, and the price is 160 yen.
In contrast, the items sold by weight, Apples AP and Lemons LM, are in a "provisionally registered" state (provisionally registered state) for the products to be purchased. A product in a provisionally registered state is a product for which the item has been entered but pricing has not yet been completed (it is also in a state of waiting to be weighed).
For this reason, in the registration list items of Apple AP and Lemon LM, for example, a comment display CM saying "Weighing required" indicates that pricing by weighing has not yet been done. Accordingly, in the registration list items of Apple AP and Lemon LM, a display of "?? yen" indicates that the price is not yet determined. Also, in the registration list items AR122-1 and AR122-2, a predetermined background color is set to indicate the provisional registration state.

In the example shown in the figure, the customer has provisionally registered lemons LM and apples AP as products sold by weight. In this case, the two products sold by weight that the customer specified as items to purchase were lemons LM and apples AP. In this case, the customer will weigh each of the lemons LM and apples AP. The customer will then remove the amount (number) of lemons LM and apples AP that he or she wishes to purchase from the lemons LM and apples AP on display. The customer then takes the removed lemons LM and apples AP with him or her to the weighing and pricing device 10A.

Figure 26 shows an example of the appearance of the weighing and pricing device 10A of this embodiment as seen from the front. As shown in the figure, the weighing and pricing device 10A is provided with a customer display unit 106, a scanner unit 104, a label discharge port 110a, and a weighing platform 109b of the weighing unit 109 facing the customer.

The weighing and pricing device 10A in the figure is in a standby state, with a standby screen displayed on the customer display unit 106. In the figure, the standby screen is shown in an enlarged manner.
In the standby screen of the figure, a code reading guide area AR21 and a measurement guide area AR22 are arranged.

The code reading guidance area AR21 displays information in response to guidance for a customer who is registering a product using the mobile terminal device 40. In the code reading guidance area AR21, for example, a connection information code CD using a two-dimensional code is displayed, and then a display is displayed instructing the customer to first have the mobile terminal device 40 read the connection information code CD when starting to register the product to be purchased (including weighing and pricing based on the weighing result).
The measurement guidance area AR22 displays information corresponding to guidance for customers who do not use the mobile terminal device 40 for shopping. In the measurement guidance area AR22, a display is displayed to guide the customer to place a product corresponding to one of the products to be purchased on the weighing platform 109b of the weighing unit 109 when starting to register products to be purchased.

In this case, the customer uses the mobile terminal device 40 to register the product. When starting to register the bulk product to be purchased, the customer operates the mobile terminal device 40 to read the connection information code CD displayed in the code reading guide area AR21. Figure 27 (A) shows an example of the appearance of the product registration screen on the touch panel display unit 406 when the mobile terminal device 40 is reading the connection information code CD.

In response to reading the connection information code CD as described above, the portable terminal device 40 establishes communication with the weighing and pricing device 10A. When the weighing and pricing device 10A and the portable terminal device 40 are connected in such a manner that they can communicate with each other, the weighing and pricing device 10A is placed in a state in which communication is exclusively held by the connected portable terminal device 40. In a state in which communication is exclusively held, the portable terminal device 40 does not connect to other portable terminal devices 40.

In addition, when a customer who is not using the mobile terminal device 40 for shopping starts weighing by, for example, placing an item on the weighing platform 109b, the weighing pricing device 10A may prohibit the establishment of mutual communication with the mobile terminal device 40 thereafter. If the establishment of mutual communication is not prohibited, any attempt to establish mutual communication will end in failure, but since it will take time until a timeout occurs, it will take some time from when the above declaration is detected until weighing can actually be performed. In contrast, if the establishment of mutual communication is prohibited, unnecessary time (the time until a timeout occurs) is saved and weighing can be performed immediately. Note that, for example, the prohibition may be lifted after the printing of the label is completed.

When communication with the weighing and pricing device 10A is established, the mobile terminal device 40 transmits information about the temporarily registered bulk products to the weighing and pricing device 10A. Specifically, the mobile terminal device 40 in this case transmits information about Lemon LM and Apple AP as information about the temporarily registered bulk products.

In addition, when communication with the weighing pricing device 10A is established, the mobile terminal device 40 causes the touch panel display unit 406 to display a pricing operation screen. Figure 27 (B) shows an example of the pricing operation screen displayed on the touch panel display unit 406 of the mobile terminal device 40.

In addition, the weighing pricing device 10A displays a pricing operation screen on the customer display unit 106 in response to the establishment of communication with the mobile terminal device 40.
FIG. 27(C) shows an example of a pricing operation screen displayed on the customer display unit 106 of the weighing pricing device 10A.
The pricing operation screen in the figure has commodity selection buttons BT11 (BT11-1, BT11-2) arranged thereon. The commodity selection buttons BT11 correspond to each commodity in a provisionally registered state, and are buttons for selecting a commodity to be registered (weighed and priced). In the figure, an example is shown in which, of the commodity selection buttons BT11, the commodity selection button BT11-1 corresponds to apples AP, and the commodity selection button BT11-2 corresponds to lemons LM.
The pricing operation screen also includes a registration result area AR31. The registration result area AR31 displays the unit price by weight of the bulk product to be registered, the measured weight, and the total price of the bulk products that have been registered.
The pricing operation screen also has a cancel button BT12 and a search button BT13. The cancel button BT12 is a button operated to stop weighing and pricing a provisionally registered bulk product. The search button BT13 is a button operated to search for other products when, for example, a provisional registration has not been made and therefore another product not shown by the product selection button BT11 is to be registered.
In addition, on the pricing operation screen, a message MS1 is displayed instructing the customer to operate the product selection button BT11 corresponding to the product to be registered and then place the product to be registered on the weighing platform 109b, such as "Please select a product and place it on the platform."

In the figure, a pricing operation screen similar to that displayed on the weighing and pricing device 10A is displayed on the mobile terminal device 40. This allows the customer to weigh, price, and register a provisionally registered commodity on either the mobile terminal device 40 or the weighing and pricing device 10A.
In addition, the mobile terminal device 40 may display a product registration screen or the like instead of displaying the pricing operation screen.
In the following description, an example will be given in which a customer performs registration by operating the pricing operation screen displayed on the weighing pricing device 10A.

Here, the customer decides to register Apple AP first, of the two products Apple AP and Lemon LM that are in a provisionally registered state. In this case, the customer operates the product selection button BT11-1 corresponding to Apple AP on the pricing operation screen. Figure 28 (A) shows the state in which the customer has operated the product selection button BT11-1 corresponding to Apple AP. The product selection button BT11-1 is highlighted in response to being touched by the operation. By operating the product selection button BT11-1 in this way, Apple AP is designated as the item to be registered.

In response to the apple AP being designated as a registration target, the display on the customer display unit 106 of the weighing and pricing device 10A transitions from the pricing operation screen to a weighing guide screen. FIG. 28(B) shows an example of the weighing guide screen. On the weighing guide screen, a weighing guide area AR32 is arranged. Also, on the weighing guide screen, a registration result area AR31, a cancel button BT12, and a search button BT13 are arranged continuously from the pricing operation screen.
In the weighing guidance area AR32, a message is displayed guiding the customer to place the apple AP on the weighing platform 109b. Specifically, in the weighing guidance area AR32 in the figure, a message MS2 saying "Please place the product", the word "apple" and a picture of an apple are displayed. In addition, a back button BT14 is arranged in the weighing guidance area AR32. The back button BT14 is a button for performing an operation to return to the previous screen.
In this case, the customer places the apple AP to be registered on the weighing platform 109b, as shown in FIG. 28(B).

When the apple AP to be registered is placed on the weighing platform 109b and weighed by the weighing section 109, the display on the customer display section 106 of the weighing pricing device 10A transitions from the weighing guide screen to the weighing result screen.
29A shows an example of the weighing result screen. The weighing result screen includes a label printing guide area AR33. The weighing result screen also includes a registration result area AR31, a cancel button BT12, and a search button BT13, which are displayed successively from the weighing guide screen.
In the registration result area AR31 of the weighing result screen, the measured weight of the Apple AP, the unit price by weight of the Apple AP, and the price of the Apple AP calculated based on the measured weight are displayed.
In the label issuance information area AR33, a message MS3 is displayed, such as "Please press the print button," which urges the customer to operate the label issuance button BT15 to issue a label (single item label) reflecting the pricing result of Ringo AP. In addition, in the label issuance information area AR33, the word "Apple" and a picture of an apple are displayed, which indicate that the product for which the label is to be issued this time is Ringo AP. The label issuance button BT15 is located in the label issuance information area AR33. In addition, in the label issuance information area AR33, a back button BT14 is located, which is used to return to the previous screen.

In this case, the customer operates the label printing button BT15 as shown in Fig. 29(A) . In response to the operation of the label printing button BT15, the weighing pricing device 10A issues a label (single item label) on which the contents reflecting the pricing result for the apple AP are printed.
In response to the operation of the label issuing button BT15, the display on the customer display unit 106 of the weighing and pricing device 10A transitions from the weighing result screen to a label application guide screen.
29(B) shows an example of the label attachment guide screen. In the label attachment guide screen, a label attachment guide area AR34 is arranged. In addition, in the label attachment guide screen, a registration result area AR31, a cancel button BT12, and a search button BT13 are arranged continuously from the measurement guide screen.
In the label attachment guidance area AR34, a picture is displayed guiding the user to attach the label issued by the weighing pricing device 10A to the bag containing the apples AP that have been priced this time. Note that in the label attachment guidance area AR34, a message guiding the user to attach the label, such as "Please attach the label to the bag of the product", may be displayed.

When the pricing results are obtained for the bulk products in the provisionally registered state as described above and a label is issued, the weighing pricing device 10A transmits the product registration information of the Apple AP reflecting the pricing results to the mobile terminal device 40.
The weighing and pricing device 10A may transmit the product registration information to the transaction management server 50 via a communication line.

In response to the issuance of the label for Apple AP as described above, the display on customer display unit 106 of weighing and pricing device 10A transitions from the label application guide screen to a pricing operation screen.
Fig. 30(A) shows an example of a pricing operation screen displayed in response to the printing of a label for Apple AP. In the pricing operation screen in Fig. 30, the product selection button BT11-1 for Apple AP displayed in the pricing operation screen in Fig. 27(C) has been deleted.
Note that instead of being deleted, the product selection button BT11-1 for the Apple AP may be displayed in a manner that indicates that it is not operable, for example, by being grayed out. In other words, the pricing operation screen is configured so that only operations for bulk products in a provisionally registered state can be performed.
When the pricing operation screen in the figure is displayed, a pricing operation screen that allows operations similar to those in the figure to be performed may also be displayed on the mobile terminal device 40 .

With the pricing operation screen of the same figure displayed, the customer operates the product selection button BT11-2 to register (weigh and price) lemon LM, which is still in a provisional registration state.
If the customer presses the cancel button BT12 at this time, the provisional registration of the lemon LM is cancelled, and only the apple AP is registered as a commodity sold by weight. In this case, the customer may return the lemon LM he or she brought from the display area to the display area, or may keep it as a reserved commodity and hand it over to the store clerk at the time of payment.

The customer operates the product selection button BT11-2 corresponding to the lemon LM, and then has the weighing and pricing device 10A weigh, price, and print a label for the lemon LM, following the same procedure as for the apple AP described above. With the label for the lemon LM printed, weighing and pricing (registration) for all products sold by weight that were provisionally registered is now complete.

When registration has been completed for all bulk items that were in a provisionally registered state, the display on the customer display unit 106 of the weighing and pricing device 10A will return to the standby screen (Figure 26).

In addition, once registration has been completed for all bulk products that were in a provisionally registered state, the product registration screen displayed on the touch panel display unit 406 of the mobile terminal device 40 will appear, for example, as shown in Figure 30 (B).
The product registration status area AR12 on the product registration screen in the figure has changed as follows, in comparison with FIG. 25. That is, the registration list items AR122-1 and AR122-2 corresponding to lemon LM and apple AP have changed from a state indicating provisional registration to a state indicating registered. Specifically, the background color of each of the registration list items AR122-1 and AR122-2 has changed from a color indicating a provisional registration state to a color indicating registered. In addition, the price determined by the pricing process is displayed in each of the registration list items AR122-1 and AR122-2. In addition, the comment display CM in each of the registration list items AR122-1 and AR122-2 has changed from "measurement required" to "measurement". The comment display CM of "measurement" indicates that the corresponding product is a product sold by weight and has been registered by the weighing and pricing process. Therefore, the comment display CM may display, for example, "weighed" or "registered" instead of "weighed."
In addition, for bulk items that have been weighed in the product registration status area AR12, information regarding the results of the pricing process, such as the weighed weight, price, unit price, etc., may be displayed.
Alternatively, the "measurement required" comment display CM itself may be deleted when the corresponding product has been registered. Even in such a case, it is preferable to change the background color or other aspect of the registration list item AR122 so that the product registration status area AR12 can visually distinguish between products sold by weight and products not sold by weight.

The product registration screen displayed on the mobile terminal device 40 may be configured to change to a state in which the registration list item AR122 of the product sold by weight for which registration has been completed indicates that it has been registered (weighed) each time the registration (weighing) of multiple products sold by weight that are provisionally registered is completed one by one.

With reference to the flowchart in Figure 31, an example of the processing procedure executed by the weighing pricing device 10A, the mobile terminal device 40, and the transaction management server 50 of this embodiment in relation to the registration of products sold by weight in one transaction will be described.

First, an example of a processing procedure of the mobile terminal device 40 in response to a case where a customer uses the mobile terminal device 40 to input the item of a commodity sold by weight to be purchased will be described.
Step S2201: The mobile terminal device 40 waits for the product information code 3001 (FIG. 25) to be read while the product registration screen is displayed on the touch panel display unit 406.

Step S2202: In response to reading the product information code 3001, the mobile terminal device 40 acquires product information from the read product information code. By acquiring the product information, the mobile terminal device 40 inputs the item name of the product to be purchased by the customer.

Step S2203: The mobile terminal device 40 adds a registration list item AR122 indicating the product of the product information acquired in step S2202 to the product registration status area AR12 of the product registration screen. In this way, the product of the product information acquired in response to reading the product information code 3001 is treated as a provisionally registered product. The registration list item AR122 of the provisionally registered product is set with a background color indicating provisional registration, as in the registration list items AR122-2 and AR122-3 in Fig. 25, and the comment display CM displays "measurement required" to indicate that pricing has not yet been performed.
After the process of step S2203, the process returns to step S2201.

Next, an example of a process procedure executed by the weighing pricing device 10A in response to pricing of provisionally registered products will be described.
Step S2101: The weighing and pricing device 10A is set to standby mode when no weighing or pricing operation is being performed by a customer. In standby mode, the weighing and pricing device 10A displays a standby screen on the customer display unit 106. On the standby screen, the connection information code CD is displayed as shown in FIG.

Step S2102: In a standby state, the weighing and pricing device 10A determines whether or not a connection process has been started with the mobile terminal device 40 that has read the connection information code CD.

Step S2103: If it is determined in step S2102 that the connection process has not been started, the weighing and pricing device 10A determines whether the weighing unit 109 has started weighing the product by the customer placing the product on the weighing platform 109b.

Step S2104: If it is determined in step S2103 that the weighing unit 109 has started weighing, the weighing pricing device 10A executes a pricing process for the weighed product corresponding to a transaction that does not use the mobile terminal device 40. After the process of step S2104, the process returns to step S2101. By returning the process to step S2101, the weighing pricing device 10A sets the standby mode and displays a standby screen including the connection information code CD.

As the pricing process of step S2014 corresponding to a transaction not using the mobile terminal device 40, the weighing pricing device 10 displays a product selection screen for performing an operation to specify (select) a product to be priced. The connection information code CD may be erased in response to the product selection screen being displayed. In other words, the connection information code CD may be erased in response to the weighing unit 109 performing weighing.
The product selection screen is a screen on which a preset key for each product classified as a product sold by weight is arranged, so that a product sold by weight can be selected. Products sold by weight may include products whose number is calculated according to the measured weight and whose price is calculated according to the calculated number and unit price.
The customer finds a preset key corresponding to the commodity placed on the weighing platform 109b on the commodity selection screen and operates the found preset key. The weighing pricing device 10 sets the commodity corresponding to the operated preset key as a target for pricing.
When the weighing pricing device 10 sets the commodity corresponding to the operated preset key as a commodity to be priced, the weighing pricing device 10 calculates the price of the commodity to be priced based on the weighing result of the weighing unit 109 .
Once the price has been calculated, the weighing pricing device 10 displays a weighing result screen in a manner similar to that shown in FIG. 29(A), which includes content to guide the customer through the label printing operation and on which a label printing button BT15 is located.
In response to the operation of the label issuing button BT15, the weighing pricing device 10 issues a label (single item label) reflecting the result of the pricing process for the current priced item. After this, the weighing pricing device 10 returns the process to step S2101 to enter standby mode and display the standby screen.

Alternatively, the weighing pricing device 10 may display, on the standby screen, a product selection screen on which preset keys for products sold by weight are arranged, together with the connection information code CD. A customer who does not use the mobile terminal device 40 can also start pricing by operating a preset key on the product selection screen displayed on the standby screen before placing the product to be priced on the weighing platform 109b. When a preset key on the product selection screen displayed on the standby screen is operated in this manner, the weighing pricing device 10 sets the product corresponding to the operated preset key as the product to be priced. Then, the weighing pricing device 10 displays a weighing guidance screen, for example, in a form similar to that shown in FIG. 28(A), and guides the customer to place the product set as the price target on the weighing platform 109b. The connection information code CD may be erased in response to the weighing guidance screen being displayed.
The weighing pricing device 10 that has displayed the above-mentioned weighing guidance screen calculates the price of the item to be priced based on the weighing result of the weighing unit 109 in response to the customer placing the item to be priced on the weighing platform 109b.
When the price is calculated, the weighing pricing device 10 displays the weighing result screen in a manner similar to that shown in Fig. 29(A). When the label issuing button BT15 arranged on the weighing result screen is operated, the weighing pricing device 10 issues a label (single item label), and returns the process to step S2101 to enter standby mode and display the standby screen.
In this way, a customer who does not use a mobile terminal device 40 can start pricing by placing the product to be priced on the weighing platform 109b, or by selecting the product to be priced by operating the product selection screen displayed on the standby screen.

Step S2105: If it is determined in step S2102 that the connection process has been started, the weighing and pricing device 10A executes the started connection process and establishes a connection with the mobile terminal device 40.

Step S2106: Once the connection is established, the mobile terminal device 40 transmits the provisionally registered product information. The weighing pricing device 10A acquires the transmitted provisionally registered product information. The provisionally registered product information is for products sold by weight, such as apples AP and lemons LM, whose items were input in response to the mobile terminal device 40 reading the product information code 3001.

Step S2107: Having acquired the provisionally registered product information, the weighing pricing device 10A displays a pricing operation screen (FIG. 27(C)) on the customer display unit 106. The pricing operation screen is a screen on which product selection buttons BT11 corresponding to each provisionally registered product indicated by the acquired provisionally registered product information are arranged, and the pricing operation involves selecting one provisionally registered product to be the subject of the pricing process from among the provisionally registered products.

Here, the weighing pricing device 10A erases the standby screen that was displayed until the connection process was started, in conjunction with the display of the initial pricing operation screen in step S2017 in response to the start of the connection process in step S2102. The erasure of the standby screen also erases the connection information code CD. In other words, the process of step S2107 erases the connection information code CD in response to the weighing pricing device 10A establishing a connection with the mobile terminal device 40.

Step S2108: After displaying the pricing operation screen, the weighing pricing device 10A executes pricing processing in response to the customer's pricing operation. That is, as explained in FIG. 28(A) and FIG. 28(B), the customer operates the product selection button BT11 on the pricing operation screen to specify the provisionally registered product to be priced. The customer places the provisionally registered product specified as the product to be priced on the weighing platform 109b and causes the weighing unit 109 to weigh it. The weighing pricing device 10A calculates the price using the weight measured by the weighing unit 109 and the unit price by weight indicated in the provisionally registered product information acquired in step S2106.

Step S2109: In response to the price being finalized by the pricing process in step S2108, the weighing pricing device 10A causes the customer display unit 106 to display the weighing result screen (FIG. 29(A)). The weighing pricing device 10A displays the weighed weight, the price per unit weight, and the calculated price in the registration result area AR31 of the weighing result screen.

Step S2110: A label issue button BT15 is located on the weighing result screen. The customer operates the label issue button BT15. In response to the operation of the label issue button BT15, the weighing pricing device 10A issues a label corresponding to the product priced by the current pricing process of step S2018.

The weighing pricing device 10A may issue a label as the process of step S2110, for example, when the pricing process in step S2108 is completed and the price is finalized. In this case, the display of the label issue button BT15 on the weighing result screen may be omitted.

Step S2111: In addition, the weighing pricing device 10A transmits product pricing information to the mobile terminal device 40 in response to the completion of the pricing process in step S2108 and the determination of the price. The product pricing information reflects the results of the pricing process for the product that was the subject of the current pricing process in step S2108.

Step S2112: After transmitting the commodity pricing information in step S2111, the weighing pricing device 10A determines whether or not the pricing process for all provisionally registered commodities has been completed.
If there are any products that have not yet been priced, the process returns to step S2107. In this case, the weighing pricing device 10A displays a pricing operation screen in which the product selection button BT11 of the provisionally registered product for which the pricing process has been completed is in an inoperable state, as shown in FIG.

Step S2113: If it is determined in step S2112 that the pricing process for all provisionally registered products has been completed, the weighing pricing device 10A disconnects the connection with the mobile terminal device 40 established in step S2105.
After disconnecting the connection with the portable terminal device 40, the process returns to step S2101. That is, a standby screen is displayed. By displaying the standby screen, the connection information code CD is displayed. That is, in response to disconnection of the connection with the portable terminal device 40, the weighing pricing device 10A displays the connection information code CD for connection with the next portable terminal device 40.

Next, an example of a process procedure executed by the mobile terminal device 40 in relation to pricing of provisionally registered products will be described.
Step S2211: The mobile terminal device 40 waits for the connection information code CD to be read while displaying the product registration screen.

Step S2212: When the customer operates the mobile terminal device 40 to read the connection information code CD, the mobile terminal device 40 reads the connection information code CD. In response to the reading of the connection information code CD, the mobile terminal device 40 executes a process between the mobile terminal device 40 and the weighing-pricing device 10A to establish a communicative connection with the weighing-pricing device 10A according to the connection procedure indicated by the read connection information code CD.

Step S2213: When a connection with the weighing pricing device 10A is established by the connection process of step S2212, the mobile terminal device 40 transmits provisionally registered product information to the weighing pricing device 10A. The provisionally registered product information is information about the weighing product whose item was entered by the processes of steps S2201 to S2203.

Step S2214: After processing of step S2213, the mobile terminal device 40 displays the pricing operation screen (Figure 27 (B)) on the touch panel display unit 406, instead of the previous product registration screen.

Step S2215: After displaying the pricing operation screen in step S2214, the mobile terminal device 40 waits to receive the commodity pricing information transmitted from the weighing pricing device 10A in step S2211. When the mobile terminal device 40 receives the commodity pricing information, it transmits commodity registration information reflecting the pricing processing results indicated by the received commodity pricing information to the transaction management server 50. In addition, in response to receiving the commodity pricing information, the mobile terminal device 40 determines that pricing has been completed for the provisionally registered commodity indicated by the commodity pricing information.

Step S2216: After the process of step S2215, the mobile terminal device 40 determines whether or not the pricing process has been completed for all provisionally registered products.
If there are any products that have not yet been priced, the process returns to step S2214. In this case, in step S2214, the mobile terminal device 40 updates the priced operation screen that has been displayed so far so that the product selection buttons for provisionally registered products for which priced processing has been completed are in an inoperable state.

Step S2217: If it is determined in step S2216 that the pricing process has been completed for all provisionally registered products, the mobile terminal device 40 displays a product registration screen on the touch panel display unit 406.

Next, an example of a processing procedure executed by the transaction management server 50 will be described.
Step S2301: The transaction management server 50 waits to receive the product registration information transmitted from the mobile terminal device 40 in step S2215.
Step S2302: When the product registration information is received, the transaction management server 50 registers (adds) the received product registration information to the cart information corresponding to the current transaction. At this time, the transaction management server 50 searches for cart information associated with the same cart identification information as that contained in the received product registration information, and registers the product registration information in the searched cart information. By performing the processing of step S2302, the provisional registration state for one product is canceled, and registration is completed. After the processing of step S2302, the processing returns to step S2301.

<Modification>
Below, a modification corresponding to the sixth embodiment will be described.

[Sixth Modification]
In the sixth embodiment, acquisition of product information (provisionally registered product information) of a product to be priced (provisionally registered product) by the weighing pricing device 10A is not limited to receiving the provisionally registered product information transmitted from the mobile terminal device 40.
For example, the weighing pricing device 10A may be capable of displaying a product selection screen on the customer display unit 106, in which preset keys corresponding to each product sold by weight are arranged. A customer can specify a product to be priced by the weighing pricing device 10A by operating a preset key arranged on the displayed product selection screen. The weighing pricing device 10A may be configured to obtain product information of the product corresponding to the operated preset key as provisionally registered product information.
In this case, it is not necessary to transmit the product information of the priced product from the mobile terminal device 40 to the weighing pricing device 10A. Therefore, the weighing pricing device 10A in this case may display the connection information code CD on the customer display unit 106 at a predetermined timing corresponding to, for example, a preset key operation, instead of displaying the connection information code CD on the standby screen. For example, the weighing pricing device 10A may display the connection information code CD at the timing when a product selection screen on which preset keys are arranged is displayed. Alternatively, the weighing pricing device 10A may display the connection information code CD at a predetermined timing from the operation of a preset key to select the first provisionally registered product to the operation of a preset key to select the last provisionally registered product. Alternatively, the weighing pricing device 10A may display the connection information code CD at the timing when the operation of the preset keys corresponding to all of the weighing products to be purchased is completed. Alternatively, the weighing pricing device 10A may display the connection information code CD at the timing when the pricing of at least one product is completed after the operation of the preset keys corresponding to all of the weighing products to be purchased is completed.

The portable terminal device 40 reads the connection information code CD and is communicatively connected to the weighing-pricing device 10A, so that the weighing-pricing device 10A can transmit provisionally registered product information to the portable terminal device 40. This allows the weighing-pricing device 10A and the portable terminal device 40 to share the provisionally registered product information.
In this case, the connection information code CD may be erased when the connection between the weighing pricing device 10A and the mobile terminal device 40 is established. Alternatively, the connection information code CD may be erased when the pricing of all provisionally registered products is completed.

Also, for example, the weighing pricing device 10A is provided with an imaging unit that captures images of the products to be priced, and the weighing pricing device 10A identifies the product type based on the analysis results of the image captured by the imaging unit of the product sold by weight to be purchased by the customer. The weighing pricing device 10A may acquire provisionally registered product information by acquiring product information corresponding to the identified product type from, for example, a product master. Note that, in this case as well, for example, the transaction management server 50 may receive an image of the product captured from the weighing pricing device 10A, analyze the received image, identify the product type of the product to be priced, and notify the identified product type from the transaction management server 50 to the weighing pricing device 10A.
In this case, the weighing pricing device 10A may display the connection information code CD at a predetermined timing between when the provisionally registered product information of the first product is acquired and when the provisionally registered product information of the last product is acquired, or when the provisionally registered product information corresponding to all of the products sold by weight to be purchased is acquired.
In this case, the connection information code CD may also be erased when the connection between the weighing pricing device 10A and the mobile terminal device 40 is established, or when pricing of all provisionally registered products is completed.

Also, for example, a tag device may be placed at a position corresponding to each of the displayed bulk products on the customer side. The tag device is connected to the weighing and pricing device 10A so as to be able to communicate with the weighing and pricing device 10A via wired or wireless communication. The tag device also stores product information indicating the corresponding bulk product. The tag device is equipped with a touch sensor, so that it can detect contact by a touch operation.
In this case, the customer performs a touch operation on the tag device corresponding to the product to be purchased. The tag device that detects the touch operation transmits the product information stored therein to the weighing pricing device 10A. The weighing pricing device 10A may acquire the received product information as provisionally registered product information.
In this case, the weighing pricing device 10A may display the connection information code CD, for example, at the timing when the provisionally registered product information of the first product is acquired.
In this case, the connection information code CD may also be erased when the connection between the weighing pricing device 10A and the mobile terminal device 40 is established, or when pricing of all provisionally registered products is completed.

A motion sensor that detects motion may be provided on a lid, lever, or other part that moves when a customer removes a commodity from a fixture that stores the commodity sold by weight. The motion sensor can detect motion using, for example, an acceleration sensor, and stores commodity information indicating the corresponding commodity sold by weight. In response to detecting motion, the motion sensor transmits the commodity information stored therein to the weighing pricing device 10A.
In this case, the customer removes the product to be purchased from the displayed products. In response to the removal of the product, the motion sensor corresponding to the product to be purchased detects the motion. In response to the detection of the motion, the motion sensor transmits the product information stored therein to the weighing pricing device 10A. The weighing pricing device 10A acquires the received product information as provisionally registered product information.
In this case, the weighing pricing device 10A may also display the connection information code CD, for example, at the timing when the provisionally registered product information of the first product is acquired.
In this case, the connection information code CD may also be erased when the connection between the weighing pricing device 10A and the mobile terminal device 40 is established, or when pricing of all provisionally registered products is completed.

[Seventh Modification]
As a modification of the sixth embodiment, the following procedure may be used to price products depending on whether the customer uses the mobile terminal device 40 or not.
In this modified example, the weighing pricing device 10 displays a standby screen in standby mode. The weighing pricing device 10 displays a plurality of standby screens, for example, by switching between them cyclically at predetermined time intervals. For example, one standby screen has a content that guides the customer to place the product on the weighing platform 109b in order to start pricing. Another standby screen has a content that guides the customer to read code information (e.g., a barcode) attached to the product. Another standby screen has a content that guides the customer to perform an operation to search for the product in order to start pricing. Another standby screen has a content that guides the customer to perform an operation to touch the standby screen in order to start pricing.

In this modification, the product information panel 3000 used in the sixth embodiment is not used at the product display location. Therefore, a customer using a mobile terminal device 40 does not perform provisional registration by reading the product information code 3001 on the product information panel 3000 in order to input the item of the product to be priced.
In this modification, the customer, regardless of whether or not the mobile terminal device 40 is used, inputs the item name of the product to be priced (pre-item input) by touching the tag device corresponding to the product to be purchased, or by taking the product to be purchased from a display location equipped with a motion sensor, as described in the sixth modification above. Alternatively, regardless of whether or not the mobile terminal device 40 is used, the customer first takes the product to be purchased from the display location, and then performs a product selection operation on the weighing pricing device 10, thereby inputting the item name of the product to be priced (screen operation item input).

The weighing and pricing device 10 of this modified example is set to standby mode when it is not operating in response to customer operation. In standby mode, the weighing and pricing device 10 displays the initial pricing operation screen on the customer display unit 106.

32 shows an example of an initial pricing operation screen displayed on the customer display unit 106. This figure shows an initial pricing operation screen that is displayed when no advance item input has been made.
The pricing operation screen in the figure has a weighing result area AR41. The weighing result area AR41 is an area in which the results of weighing the weighted product to be priced are displayed. The weighing result area AR41 includes a weight area AR41-1, a price per unit weight area AR41-2, and a total amount area AR41-3.
The weight area AR41-1 is an area in which the measured weight of the bulk product to be priced is shown.
The price per weight area AR41-2 is an area in which the price per weight of the commodity being priced is shown.

Note that some items sold by weight are sold by number, where the number of items is calculated based on the measured weight and unit weight, and the price is calculated based on the calculated number of items and the unit price per item. In the case of such items sold by weight, the weight area AR41-1 displays the number of items calculated based on the measured weight and unit weight, and the price per item may be displayed in the weight unit price area AR41-2.

The total amount area AR41-3 shows the total amount of the prices of the bulk items for which pricing has been completed so far in the same transaction.

The product selection area AR42 is an area in which the product to be priced can be selected. In the product selection area AR42 in the same figure, four tabs TB (TB-1 to TB-4) are arranged in the product selection area AR42. In the product selection area AR42, each tab TB is associated with a sheet on which product buttons are arranged. The tab TB can be selected by the customer's operation. The selected tab TB is highlighted relative to the other tabs TB, and in the product selection area AR42, the product button BT41 arranged on the sheet of the selected tab TB is displayed.

In the example shown in the figure, the sheet corresponding to the tab TB-1 has a product button BT41 for the product whose item type has been input in advance.
The sheet corresponding to tab TB-2 has product buttons BT41 (preset keys) arranged in a predetermined order for each product that has been classified as a product sold by weight and registered in advance in the product master.
The sheet corresponding to tab TB-3 has product buttons for products classified as fruits under the classification of bulk products in the product master.
The sheet corresponding to tab TB-4 is a tab corresponding to a sheet on which product buttons for products further classified as vegetables under the classification of bulk products in the product master are arranged.
In this case, a sheet for fruits and a sheet for vegetables are prepared in response to the fact that fruits and vegetables have a high purchase history among the bulk products.

As shown in the figure, the tab TB-2 is selected on the initial pricing operation screen, and as a result, in the product selection area AR42, product buttons BT41 (preset keys) of products included in the general products registered in the product master under the classification of products sold by weight are arranged on the sheet corresponding to the tab TB-2.
In this case, the order of arrangement of the product buttons BT41 on the sheet may be determined based on, for example, purchase history or a preset priority order. Also, 16 product buttons BT41 are arranged in the product selection area AR42 in the figure. In other words, 16 bulk products are presented as selection candidates. If there are 17 or more products registered in the bulk product category, the product buttons BT41 of other bulk products can be displayed by, for example, page forwarding or scrolling the sheet area.
In the same figure, the product information is simplified and displayed as "Item 1" and "Item 2" in the product button BT41, but for example, the product button BT41 may display the product name or picture indicating the corresponding product.
The sheet corresponding to tab TB-2 is an area for specifying (selecting) the product to be priced from among all the products classified as bulk products in the product master.

If the bulk product to be purchased is fruit, a customer who does not use the mobile terminal device 40 to register the product can operate the tab TB-3 to display a sheet on which product buttons BT41 for bulk products in the fruit category are arranged. The customer can operate the product button BT41 corresponding to the bulk product to be purchased from among the product buttons BT41 arranged on the displayed sheet, and designate it as the item of the product to be priced.
Furthermore, if the bulk product to be purchased is a vegetable, a customer who does not use the mobile terminal device 40 to register the product can operate the tab TB-4 to display a sheet on which product buttons BT41 for bulk products in the vegetable category are arranged. The customer can operate the product button BT41 corresponding to the bulk product to be purchased from among the product buttons BT41 arranged on the displayed sheet, and designate it as the item of the product to be priced.

In addition, a message area ARm is located above the product selection area AR42. The message area ARm is an area in which a message with a predetermined content according to the content of the current screen is displayed. In the message area ARm in the same figure, "Select The Item" is displayed. In other words, in this case, the message area ARm displays a message instructing the customer to operate the product button BT41 to specify the item of the product to be priced.

In addition, the pricing operation screen includes a search area AR43 where bulk products can be searched for by inputting characters. In the example shown in the figure, bulk products can be searched for by inputting the product name, etc., using a software keyboard provided in the search area AR43.
The search area AR43 does not have to be arranged on the pricing operation screen. In addition, the search area AR43 may be displayed in response to a predetermined operation being performed on the pricing operation screen, for example.

When the weighing pricing device 10 receives information on merchandise sold by weight in response to advance item input from a tag device or motion sensor in standby mode, it displays the pricing operation screen shown in FIG. 33 instead of the pricing operation screen in FIG. 32. In FIG. 33, the same parts as in FIG. 32 are given the same reference numerals and descriptions are omitted as appropriate.

In the pricing operation screen of FIG. 33, tab TB-1 is selected in product selection area AR42. Six product buttons BT41, Item 11 to Item 16, are arranged on the sheet corresponding to the selected tab TB-1. The bulk items corresponding to the six product buttons BT41 are items for which the item to be priced has been entered in advance by the customer through advance item input. In this case, the order in which the product buttons BT41 are arranged may correspond to the order in which the items were entered.

In addition, in the message area ARm of the same figure, a message is displayed instructing the customer to operate the product button BT41 to specify the item of the product to be priced.

In this way, in standby mode, the weighing pricing device 10 of this modified example arranges product buttons BT41 of products registered in the category of products sold by weight on the sheet with tab TB-2 selected in the product selection area AR42 by default. In this state, when a customer inputs an item in advance and information on a product sold by weight transmitted from outside the weighing device (a tag device or a motion sensor) is received, the weighing pricing device 10 changes the state from tab TB-2 to tab TB-1 being selected. The weighing pricing device 10 displays the sheet of the selected tab TB-1 with a product button BT41 arranged according to the received information on the product sold by weight. Then, when the customer subsequently inputs the next item in advance and information on another product sold by weight is received, the weighing pricing device 10 displays the sheet of tab TB-1 with an additional product button BT41 arranged according to the received information on the product sold by weight.

When a customer approaches the weighing pricing device 10 without having input items in advance, a pricing operation screen is displayed on the sheet of tab TB-2 with product button BT41 arranged as a preset key, as shown in FIG. 32. In this case, the customer can specify the product to be priced by operating the product button BT41 arranged on the sheet of tab TB-2 that is currently displayed. Alternatively, the customer can specify (select) the product to be priced by operating tabs TB-2 and TB-3, which correspond to products sold by weight, such as fruits and vegetables, to switch sheets and then operating the product button BT41.

On the other hand, when a customer goes to the weighing pricing device 10 after having previously input items, a pricing operation screen is displayed on the sheet of tab TB-1 on which a product button BT41 is arranged for each product whose items have been previously input, as shown in Fig. 33. In this case, the customer operates the product button BT41 arranged on the sheet of tab TB-1 that is currently displayed to specify (select) the product to be priced.
In this manner, the arrangement of the product button BT41 for the product whose item number has been pre-entered on the sheet of tab TB-1 is such that the product whose item number has been pre-entered is highlighted (given priority) among the products that have been pre-registered in the product master according to their classification as products sold by weight.

The manner in which the pre-entered items are displayed with emphasis (priority) is not limited to the example of switching sheets as described above.
For example, in the case where no item has been input in advance on sheet 1, the weighing pricing device 10 displays product buttons BT41 corresponding to all products sold by weight, as shown in FIG.
When the item information is input in advance, the weighing pricing device 10 may erase the item buttons BT41 of the items for which the items have not been input in advance among the item buttons BT41 corresponding to all bulk-sold items on the same sheet, and may display the item buttons BT41 of the items for which the items have been input in advance. At this time, the item buttons BT41 of the items for which the items have been input in advance may be rearranged so that they are positioned together.
Alternatively, when advance item input is performed, the weighing pricing device 10 may display the product button BT41 of the product for which advance item input has been performed in a larger size than the product button BT41 of the product for which advance item input has not been performed.
Alternatively, when advance item input is performed, the weighing pricing device 10 may display in the product selection area AR42 a separate area in which the product buttons BT41 of products for which advance item input has been performed are located and an area in which the product buttons BT41 of products for which advance item input has not been performed are located.
In addition, the manner in which the product buttons BT41 of products whose items have been input in advance on the same sheet are highlighted relative to the product buttons BT41 of products whose items have not been input in advance may be combined as appropriate.

When a customer operates the product button BT41 to designate (select) one product as a price target, the display on the customer display unit 106 in the weighing pricing device 10 transitions from a pricing operation screen to a weighing guidance screen. Although not shown in the figure, the weighing guidance screen shows the product designated as a price target by, for example, the product name or a picture representing the product, and also displays a message instructing the customer to place the product designated as a price target on the weighing platform 109b.
This display allows the customer to confirm whether the product button BT41 he or she has operated corresponds to the product he or she has specified as the target product for pricing. In addition, the customer can understand that the corresponding product should be placed on the weighing platform 109b.

When the weighing guide screen in this figure is displayed, the product to be priced has not yet been placed on the weighing platform 109b.
Thus, before the product to be priced is placed on the weighing platform 109b, the weighing result area AR41 on the pricing operation screen is displayed as follows. That is, the weight area AR41-1 indicates that the weight is zero since weighing has not yet been performed. The price per weight area AR41-2 indicates the price per weight of the product specified as the product to be priced. The price per weight displayed in this manner may be obtained, for example, from the product information in the product master. The total amount area AR41-3 indicates that the price is zero.

With the weighing guidance screen of the same figure displayed, the customer places the product to be priced on the weighing platform 109b.
When the product is placed on the weighing platform 109b, the weighing pricing device 10 executes a pricing process. That is, the weighing pricing device 10 determines the weight of the product when it is determined that the weight of the product measured by the weighing unit 109 has stabilized, and calculates the price based on the determined weight and the unit price by weight.

In response to the pricing process being executed in this manner, the display on the customer display unit 106 transitions from the weighing information screen to a weighing result screen.
Fig. 34 shows an example of a weighing result screen. In this figure, the same parts as in Fig. 33 are given the same reference numerals and the description will be omitted as appropriate.
In the weighing result screen shown in the same figure, the weighing result area AR41 changes to show the weight of the weighed product (in this case, the number calculated based on the weight and unit weight) in the weight area AR41-1, and the total amount area AR41-3 shows the total amount based on the calculated price of the product.

In addition, on the weighing result screen, the product name and design of the priced product are displayed in the product selection area AR42.

In addition, in the measurement information area AR46, a label issue button BT42 and a connection information code area AR44 are arranged.
The label issue button BT42 is a button operated to instruct the issuing of a label (single item label) reflecting the result of the pricing process for the item to be priced.
The connection information code area AR44 is an area in which the connection information code CD is displayed.
In the connection information code area AR44, a message is displayed for a customer using the portable terminal device 40, instructing the customer to have the portable terminal device 40 read the connection information code CD.

In addition, the message area ARm displays a message such as "PRINT LABEL OR READ CHORD" to guide the customer to either operate the label printing button BT42 or read the connection information code CD.

In this case, the customer who uses the portable terminal device 40 causes the portable terminal device 40 to read the connection information code CD. As a result, the portable terminal device 40 is connected to the weighing and pricing device 10.
The connection information code CD is erased when the portable terminal device 40 is connected to the weighing and pricing device 10 .
The weighing pricing device 10 transmits product pricing information reflecting the current pricing process result to the connected mobile terminal device 40. In addition, the weighing pricing device 10 issues a single-item label on which no code information is printed in response to completion of transmission of the product pricing information.

Customers who do not use the mobile terminal device 40 operate the label printing button BT42. In response to the operation of the label printing button BT42, the weighing pricing device 10 issues a single-item label on which code information reflecting the current pricing process result is printed.

In this modified example, when the pricing is finalized, the label issue button BT42 and the connection information code area AR44 are displayed on the same weighing result screen. In this case, the customer can decide whether to have the connection information code CD read or to operate the label issue button BT42, depending on whether or not he or she uses the weighing pricing device 10. In addition, in the case of this modified example, the procedure until the price is finalized by pricing is the same regardless of whether or not the mobile terminal device 40 is used, so that customers can easily become familiar with the procedure.

After the label has been issued, the weighing result screen may transition to a label application guide screen. The label application guide screen displays messages, pictures, and the like to guide the user to apply the label issued by the weighing pricing device 10 to the bag containing the currently priced product. The label application guide screen does not include the connection information code area AR44 that was displayed on the weighing result screen. In other words, the label application guide screen is displayed after the display of the connection information code has been completed.
The customer follows the instructions to lift the product from the weighing platform 109b and attaches the label taken out from the label outlet 110a to the bag containing the product.
The label application guidance screen is erased, for example, when a sensor provided at the label outlet 110a detects that a label has been removed. Instead of erasing the label application guidance screen, the customer display unit 106 transitions to displaying a pricing operation screen for specifying the next item to be priced.
In this case, if the current pricing process is performed in response to an operation on the pricing operation screen on which the preset keys of Fig. 32 are arranged, the next screen may also transition to the pricing operation screen of Fig. 32. On the other hand, if the current pricing process is performed in response to an operation on the pricing operation screen according to advance item input shown in Fig. 33, and there are still unpriced products among the products whose items have been advance input, the next screen may also transition to the pricing operation screen of Fig. 33.
If, for example, there is still some heavy object on the weighing platform 109b when the label is removed from the label discharge port 110a, a screen is displayed instructing the customer to remove the heavy object from the weighing platform 109b.

Note that among the modified examples (first modified example to fifth modified example) corresponding to the first to fifth embodiments described above, those that are applicable to the sixth embodiment may be appropriately applied to the sixth embodiment.

The predetermined processing that was executed by the mobile terminal device 40 in each of the above embodiments may be shared by a higher-level device such as the transaction management server 50 or configured to be executed in cooperation with the mobile terminal device 40. The predetermined processing executed by the weighing pricing devices 10, 10A may be shared by a higher-level device such as the transaction management server 50 or configured to be executed in cooperation with the mobile terminal device 40. The predetermined processing executed by the transaction management server 50 may be shared by the mobile terminal device 40 or the weighing pricing devices 10, 10A or configured to be executed in cooperation with the mobile terminal device 40 or the weighing pricing devices 10, 10A.

<Overview of the embodiment>
[Technical field]
The present invention relates to a sales system.
[Background Art]
2. Description of the Related Art Sales systems have been introduced in stores that allow customers to register products by themselves by operating their own mobile terminal devices (see, for example, Japanese Patent Application Laid-Open No. 2003-233634).
[Prior Art Literature]
[Patent Documents]
[Patent Document 1] Japanese Patent No. 5056161 [Summary of the Invention]
[Problem to be solved by the invention]
A weighing device is used to sell products sold by weight. In a sales area using a weighing device in the above-mentioned sales system, the weighing device is used to price the product to be purchased by the customer, and the product is then registered on the customer's mobile terminal device. This is different from the procedure when a customer registers a product by taking it off a shelf or the like and having the mobile terminal device read the code on the product.
The present invention has been made in consideration of the above circumstances, and aims to enable smooth product registration using a weighing and pricing device in a sales system in which product registration is performed using a portable terminal device carried by a customer.

[Means for solving the problems]
(1) As described above, one aspect of this embodiment is a sales system comprising a weighing and pricing device and a portable terminal device used by a customer to register products, the sales system comprising: an output means for outputting connection information for communicatively connecting the weighing and pricing device and the portable terminal device; and a control means for terminating the output of the connection information by the output means at a predetermined timing after the weighing and pricing device and the portable terminal device have been communicatively connected.

According to the above configuration, for product registration, the portable terminal device 40 and the weighing pricing device 10 (10A) are communicatively connected using the connection information code displayed (output) on the weighing pricing device 10. Then, the weighing pricing device 10 (10A) can erase the displayed connection information code at a predetermined timing after the portable terminal device 40 and the weighing pricing device 10 (10A) are communicatively connected.
This prevents a malfunction such as, for example, a customer unrelated to the transaction accidentally reading the connection information code CD with his/her mobile terminal device 40, causing the device to inadvertently connect to the weighing and pricing device 10 (10A), and allows product registration to be carried out smoothly.

(2) One aspect of this embodiment is the sales system described in (1), in which the control means causes the output means to terminate output of the connection information when the weighing unit of the weighing pricing device performs weighing or when an operation is performed on the operation unit.

According to the above configuration, after the weighing and pricing device and the mobile terminal device are connected so as to be able to communicate with each other, the connection information code can be erased when the weighing unit of the weighing and pricing device performs a weighing or when an operation is performed on the operation unit.

(3) One aspect of this embodiment is the sales system described in (1) or (2), which includes a label issuing means for issuing a label indicating the weighing result by the weighing and pricing device when the control means terminates the output of the connection information.

With the above configuration, the connection information code can be erased when a label corresponding to the pricing is issued.

(4) One aspect of this embodiment includes a display means for displaying a guide to attaching the label described in (3) to a product, and the display is performed by the display means after the output means has finished outputting the connection information.

With the above configuration, the connection information code can be hidden once the product price has been finalized and the label has been printed.

(5) One aspect of this embodiment is a sales system including a weighing and pricing device and a portable terminal device that a customer uses to register products, the sales system including an output means for outputting connection information for communicatively connecting the weighing and pricing device and the portable terminal device, and a control means for causing the output means to output the connection information at a predetermined timing when the weighing and pricing device and the portable terminal device are not communicatively connected.

According to the above configuration, for product registration, the portable terminal device 40 and the weighing pricing device 10 (10A) are communicatively connected using the connection information code displayed (output) on the weighing pricing device 10. Then, the weighing pricing device 10 (10A) can display the connection information code at a predetermined timing when the portable terminal device 40 and the weighing pricing device 10 (10A) are not communicatively connected.
This allows the display of the connection information code to be restricted at an appropriate timing in accordance with the situation where a customer who has participated in a transaction registers a commodity. As a result, for example, a customer who is not involved in the transaction may mistakenly have his/her mobile terminal device 40 read the connection information code CD, thereby preventing a malfunction in which the weighing and pricing device 10 (10A) is inadvertently connected to the weighing and pricing device 10, and commodity registration can be performed smoothly.

(6) One aspect of this embodiment is the sales system described in (5), in which the control means causes the output means to output connection information when the weighing result by the weighing pricing device is confirmed.

According to the above configuration, the connection information code is displayed when the pricing result is determined in conjunction with the determination of the weighing result, so that product pricing information can be sent from the weighing pricing device 10 to the mobile terminal device 40 immediately when communication is possible by reading the connection information code.

(7) One aspect of this embodiment is the sales system described in (5) or (6), in which the control means outputs the connection information (e.g., a connection information code screen) together with the weighing result by the weighing pricing device.

According to the above configuration, the customer can check the weighing results (pricing process results) of the products to be priced that are displayed on the customer display unit 106, while performing an operation to have the mobile terminal device 40 read the connection information code.

(8) One aspect of this embodiment is a sales system according to any one of (5) to (7), comprising a display means for displaying an operator (e.g., label printing button BT42) for printing the weighing result on a label in the weighing pricing device, and the control means outputs the connection information together with the operator displayed by the display means.

According to the above configuration, a customer using the mobile terminal device 40 can have the weighing pricing device 10 issue a label (without a barcode printed on it) after confirming the registration of the product by reading the connection information code arranged on the weighing result screen. On the other hand, a customer who does not use the mobile terminal device 40 can issue a label (with a barcode printed on it) by operating the label issue button BT42 arranged on the same weighing result screen. In other words, the weighing result screen is designed so that both customers who use the mobile terminal device 40 and customers who do not use the mobile terminal device 40 can operate to issue a label. In addition, the weighing pricing device 10 can issue labels (without a barcode printed on it) for customers who use the mobile terminal device 40 and labels (with a barcode printed on it) for customers who do not use the mobile terminal device 40, depending on whether the operation to issue the label is to read the connection information code or to operate the label issue button BT42.

(9) One aspect of this embodiment is a sales system according to any one of (1) to (8), comprising a reception means for receiving information on a product to be weighed by the weighing and pricing device from outside the weighing device (e.g., a tag device, a motion sensor), and a selection display means for selectively displaying pre-registered products (e.g., displaying a product button BT41), and when the reception means receives the product information, the selection display means displays the product corresponding to the product information received by the reception means in a highlighted manner (e.g., displaying a product button BT41 on a sheet of tab TB-1) for selection.

According to the above configuration, for example, in the initial pricing operation screen, when there is no advance item input, it is possible to display the product buttons BT41 (preset keys) corresponding to all bulk products on the sheet of tab TB-2. Then, in response to advance item input, it is possible to switch the display of the initial pricing operation screen to a mode in which the product buttons BT41 of the preset keys for the products for which advance item input has been made are arranged on the sheet of tab TB-1. This makes it easier to specify the products to be priced when advance item input has been made.

In addition, a program for realizing the functions of the above-mentioned weighing pricing device 10, mobile terminal device 40, transaction management server 50, and weighing sales management server 60 may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing as the above-mentioned weighing pricing device 10, mobile terminal device 40, transaction management server 50, and weighing sales management server 60. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. In addition, the "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium installed inside or outside the distribution server that can be accessed in order to distribute the program. The code of the program stored in the distribution server's recording medium may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a storage medium that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted over a network. The program may also be a storage medium for implementing part of the above-mentioned functions. Furthermore, the program may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

10 (10-1, 10-2, 10-3), 10A: weighing and pricing device, 20 (20-1, 20-2): settlement device, 30: management device, 40: mobile terminal device, 50: transaction management server, 60: weighing and sales management server

Claims (3)

A sales system including a weighing and pricing device and a mobile terminal device used by a customer to register products,
an output means for displaying a code for connecting the weighing and pricing device and the mobile terminal device so that they can communicate with each other;
a label issuing means for issuing a label indicating a weighing result by the weighing and pricing device;
and a control means for ending the display of the code by the output means at a predetermined timing after the weighing and pricing device and the mobile terminal device are communicatively connected after the code is displayed . The sales system according to claim 1 , wherein the control means causes the code to be displayed together with the weighing result by the weighing and pricing device. A sales system including a weighing and pricing device and a mobile terminal device used by a customer to register products, comprising:
an output means for displaying a code for connecting the weighing and pricing device and the mobile terminal device so that they can communicate with each other;
a label issuing means for issuing a label indicating a weighing result by the weighing and pricing device;
A program for causing the output means to function as a control means for terminating the display of the code at a predetermined timing after the weighing and pricing device and the mobile terminal device are communicatively connected after the code is displayed.

Images