JP7321498B2 - Label issuing device and program - Google Patents

Description

The present invention relates to a label issuing device and a program.

2. Description of the Related Art In stores, a sales system has been introduced in which a customer can operate a portable terminal device owned by the customer and register the product himself/herself (see, for example, Patent Document 1).

Japanese Patent No. 5056161

In selling products sold by weight, a weighing and pricing device corresponding to a sales format in which a salesclerk responds to customers face-to-face is used. In a sales floor using a weighing and pricing device in the sales system as described above, the procedure is such that a salesclerk sets a price for a product specified by a customer, and then registers the product on the customer's portable terminal device. is different from the procedure in the case of product registration by taking out the product from a product shelf or the like and having the portable terminal device read the code.
In addition, even if a store has introduced a sales system in which product registration is performed using a customer's mobile terminal device, it is possible to handle transactions by customers who do not use mobile terminal devices. Sometimes. Regarding sales of products sold by weight in such cases, it is preferable that the transactions are conducted efficiently regardless of whether or not the customer uses the mobile terminal device.

SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances. It is an object of the present invention to enable efficient transactions in selling commodities that are priced by a weighing and pricing device corresponding to .

According to one aspect of the present invention for solving the above-described problems, there are provided product designation means for designating a product to be registered, connection means for performing processing for communicably connecting another device to the own device, and at least one product. The label issuing apparatus comprises connection necessity confirmation means for confirming necessity of connection with the other device when the connection means is not connected with the other device before the registration is finalized.

According to one aspect of the present invention, a computer is provided with product designation means for designating a product to be registered, connection means for performing processing for communicably connecting another device to the own device, and registration of at least one product being confirmed. A program for functioning as connection necessity confirmation means for confirming necessity of connection with another device when the connection means is not connected to the other device.

INDUSTRIAL APPLICABILITY As described above, according to the present invention, in a sales system in which product registration can be performed using a mobile terminal device owned by a customer, both customers who use the mobile terminal device and customers who do not use the mobile terminal device can do so. It is possible to obtain the effect of being able to conduct transactions efficiently when selling products for which pricing is performed by the weighing and pricing device.

It is a figure which shows the example of an outline|summary of the shop where the weighing pricing apparatus in the sales system of 1st Embodiment is used. It is a figure which shows the structural example of the sales system in 1st Embodiment. It is a figure which shows the structural example of the weighing and pricing apparatus in 1st Embodiment. 1 is a perspective view showing an appearance example of a weighing and pricing device according to a first embodiment; FIG. It is a figure which shows the example of an external appearance of the payment|settlement apparatus in 1st Embodiment. It is a figure which shows the structural example of the settlement apparatus in 1st Embodiment. It is a figure which shows the structural example of the portable terminal device in 1st Embodiment. It is a figure which shows the structural example of the transaction management server in 1st Embodiment. It is a figure which shows the structural example of customer information, shop information, and basket information in 1st Embodiment. 4A and 4B are diagrams showing examples of modes of a startup screen, a nearby store guidance screen, and a store information screen in the first embodiment; FIG. It is a figure which shows the example of one aspect|mode of the advertisement screen in 1st Embodiment, a code scan screen, and a settlement guidance screen. 4 is a flow chart showing an example of a processing procedure executed by the weighing and pricing device, mobile terminal device, and transaction management server in the first embodiment in relation to product registration in one transaction; It is a figure which shows the example of a display mode of the connection information code screen in 1st Embodiment. It is a figure which shows the example of a one aspect|mode of the single item label in 1st Embodiment. FIG. 10 is a flow chart showing an example of a processing procedure executed by the weighing and pricing apparatus according to the second embodiment in response to pricing in one transaction; FIG. It is a figure which shows an example of the connection necessity confirmation screen in 2nd Embodiment. It is a figure which shows an example of the issue confirmation screen in 2nd Embodiment. FIG. 10 is a flow chart showing an example of a processing procedure executed by a weighing and pricing apparatus according to a third embodiment in response to pricing in one transaction; FIG. It is a figure which shows an example of the code information reading guidance screen in 3rd Embodiment. It is a figure which shows the example of one aspect|mode of the addition label in 4th Embodiment. It is a figure which shows the structural example of the sales system in 5th Embodiment. FIG. 21 is a sequence diagram showing an example of a processing procedure executed by a weighing pricing device, a mobile terminal device, a transaction management server, and a weighing sales management server according to the fifth embodiment in relation to product registration in one transaction; It is a figure which shows the example of a display mode of the salesclerk button in the 2nd modification of this embodiment. It is a figure which shows the example of a display aspect of the connection information code screen in the 2nd modification of this embodiment. FIG. 20 is a diagram showing a display mode example of a connection maintenance guidance message screen in a fourth modified example of the present embodiment; FIG. 22 is a diagram illustrating an example of a procedure for product registration at a pricing counter according to the sixth modification of the embodiment; FIG. 22 is a diagram illustrating an example of a procedure for product registration at a pricing counter according to the sixth modification of the embodiment; FIG. 22 is a diagram illustrating an example of a procedure for product registration at a pricing counter according to the sixth modification of the embodiment; FIG. 22 is a diagram illustrating an example of a procedure for product registration at a pricing counter according to the sixth modification of the embodiment;

<First embodiment>
FIG. 1 shows an outline of a store in which a weighing and pricing device is used in the sales system of this embodiment. An example of a store in this embodiment that sells food will be described.
In the display case shown in the figure, various foods are displayed as commodities.
Three weighing and pricing devices 10-1, 10-2 and 10-3 are installed on the display case. In the following description, the weighing and pricing devices 10-1, 10-2, and 10-3 will be referred to as the weighing and pricing device 10 unless otherwise distinguished. The weighing and pricing apparatus 10 includes a weighing table on which a product to be weighed (or mass) is placed. Weighing and pricing device 10 is an example of a label issuing device.

Also, although not shown, a checkout device is installed at a predetermined location away from the counter shown in the figure.
The number of weighing and pricing devices 10 installed and the number of settlement devices installed in a store are not particularly limited.

In this embodiment, although not shown in the figure, in the store, in addition to the sales floor where the weighing and pricing device 10 is arranged, the customer can put any product into the shopping basket from the product shelf. There is also a sales floor where you can

FIG. 2 shows a configuration example of a sales system in this embodiment. The sales system shown in FIG. A server 50 is provided.

The weighing and pricing apparatus 10 calculates the price of each product based on the measured weight of the product placed on the scale and the unit weight, and generates product pricing information for the product including the calculated price. The product pricing information is transmitted to the mobile terminal device 40 communicably connected to the weighing and pricing device 10 .
The customer instructs the store clerk on the item to be purchased and the weight (or amount) to be purchased. The store clerk performs an operation on the weighing and pricing device 10 to designate the product instructed by the customer as an object to be registered. After that, the store clerk causes the weighing and pricing apparatus 10 to measure the weight of the product to be registered (or the weight corresponding to the amount instructed by the customer). At this time, the store clerk weighs the product by placing it on the scale.
The weighing and pricing device 10 calculates the price of the product based on the measured weight and the unit weight per unit weight (for example, 100 g) set for the product, and calculates the price of the product and the product designated as a registration target. to price. As described above, the customer instructs the store clerk the weight of each product that the customer wants to purchase, and the store clerk measures the weight of the instructed product and sets the price of the product. The weighing and pricing device 10 transmits product pricing information reflecting the fixed price of the product to the communicatively connected portable terminal device 40 each time the price of the product is fixed.

The settlement device 20 uses the basket information (settlement information) acquired from the transaction management server 50 to execute the settlement process according to the customer's operation.

The management device 30 is a host device of the settlement device 20 in the store. A management device 30 in the figure is communicably connected to the settlement device 20 . For example, the management device 30 can manage transaction results at the store by acquiring track record information of settlement processing at the store from the settlement device 20 . Further, for example, the status of the settlement device 20 can be monitored, and when an abnormality occurs in the settlement device 20, notification can be given.
Note that the management device 30 may also be communicably connected to the weighing and pricing device 10 . In this case, for example, the management device 30 may store the product master information. The weighing and 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 owned by a customer. In this embodiment, the mobile terminal device 40 may be a smartphone, a tablet terminal, or the like owned by the customer. The mobile terminal device 40 is installed with application software (shopping application) that is used by customers for services related to shopping and the like, corresponding to the sales system of the present embodiment.

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 basket information for each transaction based on the received product registration information. The basket information indicates the product registration result in the corresponding transaction.
In response to the basket information request transmitted from the settlement device 20, the transaction management server 50 transmits to the settlement device 20 basket information associated with the transaction identifier specified by the basket information request.

A configuration example of the weighing and pricing device 10 according to the present embodiment will be described with reference to FIGS. 3 and 4. FIG. FIG. 3 is a block diagram showing a hardware configuration example of the weighing and pricing device 10. As shown in FIG. FIG. 4 is a perspective view showing an appearance example of the weighing and pricing device 10. As shown in FIG. FIG. 4A is a diagram of the weighing and pricing apparatus 10 viewed from the store clerk side, and FIG. 4B is a diagram of the weighing and pricing apparatus 10 viewed from the customer side.

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

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

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

The store clerk display unit 105 is arranged facing the store clerk as shown in FIG. 4(A). The store clerk display unit 105 is configured as a touch panel, and receives an operation by touching the displayed operation screen with an operating body such as a finger.

As shown in FIG. 4(B), the customer display unit 106 is arranged facing the customer side and performs display for the customer. The customer display unit 106 may be configured as a touch panel so as to be operable by the customer.

A hard disk 107 serves as an auxiliary storage device for the CPU 101 and stores various information necessary for the weighing and pricing apparatus 10 . The hard disk 107 may store product files, for example. The hard disk 107 may store a program for causing the CPU 101 to execute registration processing and the like. The hard disk 107 may also store various information generated by executing programs. Further, the hard disk 107 may store information about display by the store clerk display section 105 and the customer display section 106 and information about printing by the printing section 110 .
Note that, instead of the hard disk 107, another storage device such as an SSD (Solid State Drive) may be provided.

As shown in FIG. 4A, the key operation unit 108 includes various operation keys (number key, cancel key, tare key, addition key, product number key, execution key, etc.) for receiving various operations from the store clerk. ).

The weighing unit 109 measures the weight of the product or the like placed on the scale 109 a (the product and the tare containing the product) and outputs data indicating the weight value to the CPU 101 . It should be noted that the CPU 101 that has obtained the weighed value from the weighing unit 109 subtracts a predetermined weight (the weight of the tare) from the weighed value to calculate the product placed on the weighing table 109a. In addition, the CPU 101 temporarily stores the product weight calculated as described above in the RAM 103, and displays it on the display units (clerk display unit 105 and customer display unit 106).

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

The device-to-device correspondence communication unit 111 is provided for communication with another weighing and pricing device 10 via a predetermined communication network. The communication network supported by the inter-apparatus communication unit 111 may be wired or wireless. Note that the inter-device correspondence 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 system supported by the short-range communication unit 112 may be, for example, Bluetooth (registered trademark).

FIG. 5 is a perspective view showing the appearance of the settlement device 20. As shown in FIG. The settlement device 20 shown in the figure includes a scanner section 204, a customer display section 206, a change machine 260, and an issue port 210a.

The scanner unit 204 reads code information. The code information readable by the scanner unit 204 may be a bar code (one-dimensional code) or a two-dimensional code (eg, QR code (registered trademark)).
In this embodiment, the scanner unit 204 is used for reading code information displayed on the mobile terminal device 40 . Code information displayed on the mobile terminal device 40 includes code information for settlement, code information arranged on the membership card screen and indicating a member identifier and the like, code information including information as a coupon, and the like. Further, the settlement device 20 may be capable of executing product registration processing in response to the operation of a store clerk, for example. In this case, the scanner unit 204 may read code information as a product code. .
The scanner unit 204 shown in FIG. 2 is fixedly mounted on the pedestal of the customer display unit 206. However, for example, a handy scanner can be used and hung on a pedestal provided on the side of the housing. may be stopped.

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

The change machine 260 is an automatic change machine that accepts banknotes and coins inserted by a customer, performs deposit processing, and discharges change, refunds, or rejected banknotes and coins. The change dispenser 260 includes a banknote management unit 261 , a coin slot 264 , a coin outlet 265 and a reject slot 266 . A coin slot 264, a coin outlet 265, and a reject slot 266 are included in the coin management section. The banknote management unit 261 includes a banknote insertion port 262 and a banknote discharge port 263 . The banknote insertion slot 262 is a slot for taking in banknotes inserted by customers. The banknote discharge port 263 is a port for discharging banknotes and rejected banknotes. The banknote insertion port 262 and the banknote discharge port 263 are configured in two stages. For example, in the banknote management unit 261 , the banknote insertion port 262 is on the upper side and the banknote discharge port 263 is on the lower side.

The coin slot 264 is a slot for taking in coins inserted by customers. The coin ejection opening 265 is an opening for ejecting coins as change, coins that are unsuccessfully identified by the money identification unit provided in the change dispenser 260, and coins that are identified as counterfeit coins by the money identification unit. The reject port 266 is a port for ejecting coins when a cancel operation is performed after depositing. A banknote slot 262 and a coin slot 264 are deposit slots. A bill discharge port 263, a coin discharge port 265, and a reject port 266 are payout ports. The issue port 210a outputs various receipts from a receipt output port.

The change machine 260 and the issuing port 210a have a banknote insertion port 262, a banknote discharge port 263, a coin insertion port 264, a coin discharge port 265, a rejection port 266, and a receipt discharge port facing the customer side. It protrudes from the side of the counter table on the customer side. This arrangement reduces the risk of the customer's toes hitting the counter pedestal when the customer stands close to the change dispenser 260 . For example, the change dispenser 260 and the issuing port 210a are housed in an integrated housing, and this housing is protruded from the side of the counter table on the customer side.

FIG. 6 is a block diagram showing a configuration example of the settlement device 20. As shown in FIG. The settlement device 20 includes a CPU 201 , a ROM 202 , a RAM 203 , a scanner section 204 , a customer display section 206 , a hard disk 207 , a printing section 210 , an inter-device communication section 211 , and a change dispenser 260 . These are connected to each other via bus 219 . Note that the inter-device correspondence communication unit 211 is a part provided for communication with a salesclerk identification tag in the third embodiment described later, so it may be omitted in the present embodiment.

The CPU 201 executes various processes for realizing the functions of the settlement apparatus 20 by executing programs.
The ROM 202 stores various information. For example, the ROM 202 stores programs executed by the CPU 201 . In addition, the ROM 202 stores information (screen information, message information, etc.) regarding display by the customer display unit 206 . Also, the ROM 202 stores a device number for identifying its own device. The ROM 202 may also store information (print content, print format information, etc.) regarding printing by the printing unit 210 . The scanner unit 204 optically reads the coded information and stores the read information in the RAM 203 .
The RAM 203 is used as a working area when the CPU 201 executes processing and calculation.
A scanner unit 204 optically reads the coded information. The scanner unit 204 can read information such as a membership number printed as a barcode or the like on a membership card, for example.

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

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

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

A configuration example of the mobile terminal device 40 of the present embodiment will be described with reference to FIG. The mobile terminal device 40 shown in FIG. 409.

The CPU 401 implements various processes in the mobile terminal device 40 by executing programs.
A storage unit 402 is an auxiliary storage device for the CPU 401 and stores programs to be executed by the CPU 401 as well as various data.
A RAM 403 is a main storage device of the CPU 401 .

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

A display unit with a touch panel 406 is a display unit combined with a touch panel.
An operation unit 407 is other than the touch panel display unit 406 and collectively indicates keys and the like to be operated.

The imaging unit 408 performs imaging. The mobile terminal device 40 has a code information scanning function using the imaging unit 408 . In other words, the portable terminal device 40, as a code information scanning function, acquires code information from the captured image upon recognizing that the captured image captured by the imaging unit 408 contains code information.

Under the shopping application of this embodiment, the code information scanning function using the imaging unit 408 reads the code information attached to the product and reads the connection information code displayed on the weighing and pricing device 10. used for By reading the code information attached to the product, the product to be registered is specified by the product code included in the code information. Such identification of a product to be registered may be realized by, for example, general object recognition processing using a captured image obtained by capturing an image of the product by the imaging unit 408 . In this case, as a result of general object recognition processing, one product may be specified, or a plurality of candidates may be presented. When a plurality of candidates are presented, the product to be registered may be specified by the customer selecting one of the presented candidates.

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

A configuration example of the transaction management server 50 of the present embodiment will be described with reference to FIG. The transaction management server 50 in FIG.

The CPU 501 implements various processes in the transaction management server 50 by executing programs.
A storage unit 502 is an auxiliary storage device for the CPU 501 and stores programs to be executed by the CPU 501 as well as various data.
A RAM 503 is a main storage device of 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 section, an operation section, and the like so that the administrator can perform operations.

The transaction management server 50 stores, for example, customer information as shown in FIG. 9(A). The customer information shown in FIG. 9A includes customer identification information, customer name, customer registration date, cancellation information, customer rank, number of points, and the like. Customer identification information is identification information that uniquely identifies a customer. The customer name is the customer's name, nickname, or the like. The customer registration date is the date and time when the customer was registered. Cancellation information is information regarding cancellation of a registered product after registration. The customer rank is a rank according to the customer's purchase record. When generating customer information for a new customer, customer identification information, customer name, and customer registration date are generated, but since the actual transaction (product registration) has not yet started, other information (cancellation information, etc.) is not generated.

The transaction management server 50, for example, when registering a customer (for example, the mobile terminal device 40 uses the service provided by the transaction management server 50 from the outside (for example, a predetermined server that provides general applications, the transaction management server 50). Generate and store customer identification information when downloading or installing a shopping application). Further, the transaction management server 50 acquires information entered in the name column of the registration form (input form) using the mobile terminal device 40 at the time of customer registration, for example, and stores the information as the customer name. Also, the transaction management server 50 acquires, for example, the current date and time at the time of customer registration, and stores it as the customer registration date.

Transaction management server 50 stores part or all of the customer information in another device (such as a file server that transaction management server 50 can access) instead of or in addition to storing the customer information in its own storage unit. You can memorize all of them.

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

The transaction management server 50 stores, for example, shop information as shown in FIG. 9(B). The store information shown in FIG. 9B includes store identification information, store name (branch name), store identification information 1, and store identification information 2. FIG. The store identification information is identification information that uniquely identifies the store. The store identification information shown in FIG. 9B is composed of a store (store name) or company code and a branch code. The store name is the name of the store. The store name shown in FIG. 9B is composed of a store (store name) or company and a branch name. The shop identification information 1 is information of a two-dimensional code (for example, QR code (registered trademark), etc.) for identifying a trading shop (a shop where merchandise is bought and sold). The store identification information 2 is store location information (GPS information) for specifying the store to trade with. In the example shown in FIG. 9B, the store identification information and the store identification information 1 are different, but the store identification information and the store identification information 1 may be the same.

It should be noted that the transaction management server 50 may acquire and store store information and the like from an external source (such as a server (not shown) at the head office that supervises each store). In addition, transaction management server 50 stores part of or store information in another device (such as a file server that transaction management server 50 can access) instead of or in addition to storing store information in the storage section of its own device. You can memorize all of them.

The product information is obtained from the management device 30 of each store. That is, 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. Note that the transaction management server 50 may acquire and store product information from an external source (such as a server (not shown) at the headquarters that controls each store). In addition, transaction management server 50 stores part of or store information in another device (such as a file server that transaction management server 50 can access) instead of or in addition to storing store information in the storage section of its own device. You can memorize all of them.

Basket information is information for managing individual transactions. Transaction management server 50 generates basket information at the start of a transaction. In addition, the transaction management server 50 updates the basket information as the transaction progresses (each time a product is registered). can also be used).

The transaction management server 50 stores, for example, basket information as shown in FIG. 9(C). The basket information shown in FIG. 9C includes basket identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, pending product information, cancellation information, and the like. Basket identification information is identification information that uniquely identifies a basket (transaction). The basket identification information shown in FIG. 9C is composed of store identification information, dates, and serial numbers (for example, serial numbers by store and by date). The transaction start date and time is the date and time when the transaction started. The trading start date and time shown in FIG. 9 is the date and time when the basket information is generated. The transaction start date and time may be the registration date and time of one product (the date and time when the registered product information (registered product 1) in FIG. 9C is stored). Both the date and time of creation of basket information and the date and time of registration of one item of merchandise may be stored separately.

The transaction end date and time is the end date and time of the transaction. The trading start date and time shown in FIG. 9 is the settlement date and time. The customer identification information is customer identification information that identifies the customer of the transaction. When generating basket information, basket identification information, transaction start date and time, and customer identification information are generated, but other information (transaction end date and time, etc.) is generated before the actual transaction (product registration) starts. not. Note that the settlement date and time may be the settlement start date and time, or may be the settlement end date and time. Both the settlement start date and time and the settlement end date and time may be stored separately.

The registered product information (total) is information updated each time a product is registered. The registered product information (total) includes the number of products (number of products), approximate subtotal amount (approximate subtotal amount before price calculation by price determination logic), subtotal amount (subtotal amount after price calculation by price determination logic), and the like. Registered product information (1) is registered information of one item of product. Registered product information (2) is registered information of two items of products. Note that in the example shown in FIG. 9C, illustration of registered product information (3) to registered product information (5) is omitted. The registered product information (N; N is an integer) includes product code, product name (product name), price, and the like.

The registered product information (N) may include the registration date and time of the N item 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 be used as a criterion for determining the necessity of application of services such as time service (service based on selling price determination logic E) and the effect after application.

The pending product information (total) is information updated each time a pending product (described later) is registered. The reserved product information (total) includes the number of reserved products (number of products), the number of NON-FILE products among the reserved products, the number of read NG (unauthorized operation confirmation required) products among the reserved products, and the like.

NON-FILE means that although the barcode was successfully scanned at the store (although the product code could be read), the product code was not stored in the product information, or the product code was successfully scanned at the store. However, it is a product whose product code is not stored in the product information.

The reading NG means that the scanning of the product code failed at the store (the product code could not be read), or the product for which the scanning of the product code failed at the store. In other words, reading NG is time-out processing when it can be determined that the image of the product is captured for a certain period of time by image recognition technology, but the barcode recognition is not achieved, or the product has been time-out processed. For example, if the barcode cannot be correctly acquired (recognized) due to wrinkles on the package, blurred or dirty barcode printing, it is determined that reading is NG. Also, when an illegal operation of pretending to have read the bar code and throwing it into the basket is detected, it is determined that reading is NG. The mobile terminal device 40 includes a sensor (for example, a gyro sensor, an acceleration sensor, a distance sensor, or the like). It is possible to detect a situation in which the terminal device 40 is tilted and an article (product) exists at a certain distance ahead of the mobile terminal device 40 . When the barcode cannot be read within a predetermined time (when the barcode cannot be read even though the barcode reading continues for a predetermined time), timeout processing is performed and the product is held (reading NG).

Reserved product information (reserved product 1) is information on one item of reserved product. Reserved product information (reserved product 2) is information on two items of reserved products. The reserved product information (reserved product 3) is information of three reserved products.

Reserved product information (reserved product N; N is an integer) includes the reserved product type (information indicating whether the relevant reserved product is NON-FILE or read NG), and image data (image data captured when reading is NG). including. For example, if the N item product is a NON-FILE reserved product, the reserved product information (reserved product N) includes reserved product type “1 (NON-FILE)” and image data. Further, when the product of the N item is a pending product due to reading NG, the pending product information (reserved product N) includes the pending product type “2 (reading NG)” and image data.

Transaction management server 50 stores part or all of the basket information in another device (such as a file server accessible by transaction management server 50) in place of or in addition to storing the basket information in its own storage unit. You can memorize all of them.

Functions of the shopping application installed in the mobile terminal device 40 will be described with reference to FIGS. 10 and 11. FIG.
When the customer operates the mobile terminal device 40 to activate the shopping application, the mobile terminal device 40 running the shopping application first displays a startup screen on the touch panel display unit 406 as shown in FIG. 10(A). do. On the startup screen in the same figure, a "store information" button, a "notice" button, and a "advantageous information" button are arranged. In addition, a shopping start button showing characters "Start shopping" is arranged.

For example, when the customer performs an operation (tap operation) on the "store information" button, the display on the touch panel display unit 406 transitions to the nearby store guidance screen as shown in FIG. 10B. The nearby store guidance screen displays on a map stores that are within a certain range from the user's own position acquired by the position information acquisition unit 409 and where the shopping application can be used (available stores). The figure shows an example in which marks indicating three available shops are arranged on the map with reference to the current position of the mobile terminal device 40 .
In displaying such a nearby store guide screen, the mobile terminal device 40 may, for example, use a store information server (not shown) that manages information about available stores (available store information). (which may be shared), along with its own location information, transmits an available store search request. 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 the searched available store information to the mobile terminal device 40 . The mobile terminal device 40 uses the received information on available stores to display a nearby store guidance screen.

A shopping application may have the functionality of a shopping list, for example. A customer can perform an operation of registering a product that he or she intends to purchase in a shopping list.
When the shopping application has the function of a shopping list in this way, the mobile terminal device 40 also includes, for example, information on products registered in the shopping list in the available store search request. The store information server includes a list of product items 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 checks the presence or absence of products registered in the shopping list for each available store information searched as being within a certain range from the position of the mobile terminal device 40. The available store information is transmitted to the mobile terminal device 40 after including the information shown. In this case, the mobile terminal device 40 may display available stores on the map so that the presence or absence of products registered in the shopping list can be visually recognized. As a display mode of available stores that enables the presence or absence of products registered in the shopping list to be visually recognized, for example, the mark indicating the available stores can be used to indicate which stores have the products registered in the shopping list and which stores do not. Color coding and size may be changed according to available stores.

In addition, when the customer performs an operation (for example, a tap operation on the mark) to select the mark of an arbitrary store under the state where the surrounding store guidance screen is displayed as shown in FIG. As shown in 10(C), a store information screen showing information on the selected store is displayed.

As described above, the "Notice" button and the "Profit Information" button are arranged on the startup screen of FIG. 10(A). Also on the store information screen of FIG. 10C, a "notice" button and a "advantageous information" button are arranged.
When the customer operates the "notice" button while the startup screen or store information screen is being displayed, the corresponding available store is displayed as "notice", as shown in FIG. 11(A). An advertisement screen that provides information such as events and sale announcements prepared as is displayed.
Also, when the customer operates the "advantageous information" button, as shown in FIG. 11(B), an advertisement screen for providing information on services such as discounts for customers using the shopping application is displayed. be done.
These advertisement screens may be displayed based on the advertisement information included in the available store information transmitted from the store information server.

Further, when the shopping start button arranged on the startup screen of FIG. 10A is operated, the display unit with touch panel 406 transitions to the code scan screen as shown in FIG. 11C. The customer can use the mobile terminal device 40 on which the code scan screen is displayed to perform the product registration operation.
Here, as an example of basic product registration operation, instead of the sales floor where the weighing and pricing apparatus 10 is arranged, an example of product registration operation at a sales floor where product shelves are arranged will be described.
A customer takes out a product that he or she intends to purchase (a product to be purchased), for example, from a product shelf. The customer scans the code information of the code (a bar code, but it may be a two-dimensional code) attached to the product to be purchased by scanning the imaging unit of the mobile terminal device 40 with the code scan screen displayed. 408 performs the reading operation.
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 the basket information (settlement information) corresponding to one transaction. Moreover, the product registration information based on the read code information may be stored in the mobile terminal device 40 .
After completing the operation of registering all the products to be purchased, the customer performs a predetermined operation (completion of product registration) to the mobile terminal device 40 to instruct the 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 product registration completion. The transaction management server 50 that has received the product registration completion notification can manage the basket information of the corresponding transaction as if the product registration has been completed.

When the product registration completion operation is performed, the touch-panel display unit 406 of the mobile terminal device 40 displays a settlement guide screen as shown in FIG. 11(D). On the settlement guidance screen of FIG. 10, there are, for example, two pieces of information: a guidance message for the customer to go to the settlement device 20 for settlement, and transaction code information indicating the transaction corresponding to the current product registration. It is displayed as a dimension code. The transaction code information includes a transaction identifier that uniquely identifies the transaction. For example, the transaction identifier is issued by the transaction management server 50 in response to the first transmission of the product registration information in the corresponding transaction by the mobile terminal device 40, and is notified to the mobile terminal device 40. good.
The customer goes to the settlement device 20 and causes the scanner unit 204 of the settlement device 20 to read the two-dimensional code displayed on the settlement guidance screen. The settlement device 20 acquires basket 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 basket information to execute settlement processing according to the operation of the customer. The settlement device 20 includes one or more card readers corresponding to a predetermined card, for example, when a customer uses or uses cards such as a credit card, an electronic money card, and a point card for settlement. may be provided.
In this way, in this embodiment, a customer who has a shopping application installed on his/her own mobile terminal device 40 can perform product registration by operating his/her own mobile terminal device 40 . In addition, the settlement at the settlement device 20 is also performed by the customer's operation. In this embodiment, the store clerk does not need to perform the operation of product registration, the operation of the checkout device, or the like, because the customer performs product registration and payment in this way.

On the other hand, in a store, as illustrated in FIG. 1, there is a sales floor for face-to-face sale by weight where the weighing and pricing device 10 is arranged. In such sales floors for sale by weight, as described with reference to FIG. 1, a customer faces a store clerk who operates the weighing and pricing apparatus 10 and specifies the product and its weight, and the store clerk selects the specified product. The product is priced by weighing and pricing device 10 .
As for the sales floor where the weighing and pricing apparatus 10 corresponding to face-to-face sales is used, the operation related to product registration and the accompanying processing in the sales system are performed when the basic product registration operation described above is performed. will be different. This point will be described below.

An example of a processing procedure executed by the weighing and pricing device 10, the portable terminal device 40, and the transaction management server 50 in relation to product registration in one transaction will be described with reference to the flowchart of FIG. Also, with reference to the same figure, the operation of the store clerk and the customer when the customer makes a purchase at a sales floor that handles sales by weight will be described. In order to simplify the explanation, FIG. 1 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 and pricing device 10. .

First, an example of a processing procedure executed by the weighing and pricing apparatus 10 will be described.
Step S101: The weighing and pricing device 10 determines whether or not a pricing operation has been performed for one product in one transaction.
A customer who intends to purchase a product sold by weight informs the store clerk of the product he or she wishes to purchase and its weight. The store clerk takes out the notified product to be purchased from the display case. The store clerk inputs the item of the product to be purchased into the weighing and pricing device 10, and then places the product on the scale (weighing unit 109). For example, the weighing and pricing apparatus 10 may determine that the pricing operation for one product has been started in response to the input of the item of the product to be purchased.
In addition, the weighing and pricing apparatus 10 determines that product registration corresponding to one transaction has started in response to the start of the pricing operation for the first product in one transaction, and the transaction associated with the current transaction. Issue an identifier.

Step S102: The weighing and pricing device 10 executes pricing processing in response to the pricing operation being performed. The pricing process is a product registration process executed by the weighing and pricing apparatus 10 to register a product to be purchased.
As the pricing process, the weighing and pricing apparatus 10 receives input of product items by the store clerk and acquires the items of the product to be purchased. The weighing and pricing apparatus 10 uses the unit weight and the weight measured by the weighing unit 109 (for example, the weight measured when the product is placed on the weighing unit 109 and stabilized without fluctuation). , to calculate the price of the product. The weighing unit 109 displays the item of the product to be purchased, the measured weight, the price, etc., on the store clerk display unit 105 and the customer display unit 106, for example.
The store clerk confirms with the customer about the weight, etc., and when the customer's consent is obtained, performs an operation of instructing determination of the price of the product to be purchased.

Step S103: The weighing and pricing apparatus 10 displays the connection information code on the customer display section 106 when the pricing for one product to be purchased is determined as described above. The connection information code may be displayed as a two-dimensional code, for example. The connection information code is control information for connecting the mobile terminal device 40 running the shopping application to the weighing and pricing device 10 via, for example, Bluetooth. The connection information code includes a transaction identifier issued according to this transaction.
FIG. 13 shows an example of a connection information code screen displayed on the customer display unit 106. As shown in FIG. This figure shows an example of a mode in which the customer display section 106 has a vertically long display surface section and the notation on the screen is in English.
On the connection information code screen shown in FIG. 2, the connection information code is displayed as a two-dimensional code, and the image of the portable 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 .
In addition, on the connection information code screen, pricing-related information (Tare, Gross weight, Unit Price, and Total Price) for the product to be priced etc.) are shown. Also, a message ("OK with this weight?") prompting the customer to confirm whether or not the weighed weight can be registered is displayed.
After confirming the content of the pricing-related information displayed on the connection information code screen, the customer performs an operation to read the connection information code as a two-dimensional code displayed on the connection information code screen with the mobile terminal device 40. be made to do.
Note that display section 105 for salesclerk may display a message, a pop-up window, an icon, or the like for notifying the salesclerk that the connection information code is being displayed on display section 106 for customer.

Return the description to FIG.
Step S104: The weighing and pricing device 10 executes connection processing for establishing connection in response to a connection request from the mobile terminal device 40 that has read the connection information code.

Step S105: The weighing and pricing device 10 connected to the portable terminal device 40 by the connection processing in step S104 performs transaction identifier collation processing. That is, the weighing and pricing apparatus 10 determines whether or not the transaction identifier issued in response to the current transaction matches the transaction identifier notified from the connected mobile terminal device 40 .

Step S106: If the transaction identifier matching process in step S105 determines that the transaction identifiers match, the weighing and pricing device 10 selects the product to which the result of the pricing process in step S102 is reflected. Pricing information (an example of registration processing information) is transmitted to the connected mobile terminal device 40 .

Step S107: When the product pricing information transmitted in step S106 can be normally received by the mobile terminal device 40, the mobile terminal device 40 transmits a receipt confirmation notification to the weighing and pricing device 10. FIG. The weighing and pricing device 10 receives the transmitted acknowledgment of receipt.
Step S108: In response to receiving the reception confirmation notification, the weighing and pricing apparatus 10 causes the printing unit 110 to print a label (single item label) corresponding to the product for which pricing processing has been performed in this step S102. and issue a single item label.

FIG. 14 shows an example of a single item label. Information such as product name, processing date, expiry date, weight unit price, weight, and price is printed on such a single item label. In addition, information indicating, for example, the department to which the sale by weight is available may also be printed on the single-item label. In addition, a code (a bar code in the figure) containing at least part of the information printed in characters, etc., as described above, may be printed on the single item label. It is preferable to change the mode, such as the printing of "done" or the label format. The store clerk affixes the single-item label issued in this way to the item to be priced this time.

Return the description to FIG.
Step S109: When it is determined in step S101 that no pricing operation has been performed for one product, or after the process of step S108 is executed, the weighing and pricing device 10 performs one transaction. A determination is made as to whether or not the pricing of the product has been completed.
When the clerk confirms that pricing has been completed for all of the products specified by the customer in response to one transaction, the salesclerk performs an operation (pricing completion operation) to declare the completion of pricing corresponding to one transaction. 10. When the pricing completion operation is performed, the weighing and pricing device 10 determines that the pricing of the product corresponding to one transaction has been completed.
If it is determined that pricing for the product corresponding to one transaction has not been completed, the process returns to step S101.

Step S110: When it is determined that the pricing of the product corresponding to one transaction has been completed, the weighing and pricing device 10 transmits a pricing completion notice to the connected mobile terminal device 40 .
Step S<b>111 : The portable terminal device 40 that has received the pricing completion notification transmitted in step S<b>110 transmits a reception confirmation notification to the weighing and pricing device 10 . The reception confirmation notification transmitted in step S111 notifies that the pricing completion notification has been received normally. The weighing and pricing device 10 that has received the reception confirmation notice executes a process of disconnecting the communication with the portable terminal device 40 up to now.

Next, an example of a processing procedure executed by the weighing and pricing device 10 will be described.
Step S201: With the code scan screen displayed on the display unit 406 with touch panel, the portable terminal device 40 determines whether or not the code has been read.
Step S202: As described above, one product specified by the customer is priced by the weighing and pricing device 10 according to the operation of the store clerk. A connection information code is displayed at 106 . Therefore, the customer operates the mobile terminal device 40 with the code scan screen displayed to cause the mobile terminal device 40 to read the displayed connection information code. As a result, it is determined that the code has been read in step S201.
Since the code read in this case is the connection information code, the mobile terminal device 40 performs processing for communicably connecting to the connection destination weighing and pricing device 10 according to the connection procedure indicated by the connection information code. , with the weighing device 10 .

Step S203: The mobile terminal device 40 connected to the weighing and pricing device 10 in step S202 executes transaction identifier collation processing with the weighing and pricing device 10 to which it is connected. At this time, the portable terminal device 40 transmits the transaction identifier included in the connection information code read in response to step S201 to the weighing and pricing device 10 .

Step S204: As described above, the weighing and pricing apparatus 10 transmits product pricing information in step S106 when it is determined by the transaction identifier matching process that the transaction identifiers match. The mobile terminal device 40 receives the transmitted product pricing information.
Step S205: The mobile terminal device 40 transmits a reception confirmation notification to the weighing and pricing device 10, notifying that the product pricing information has been received.
Step S206: In addition, the portable terminal device 40 transmits to the transaction management server 50 product registration information for one product that reflects the contents of the product pricing information received in step S204. The product registration information transmitted in this manner includes a transaction identifier.

Step S207: The mobile terminal device 40 determines whether or not the weighing and pricing device 10 has received the pricing completion notification transmitted in step S110. 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 sends a receipt confirmation notification as notification of the reception of the pricing completion notification to the weighing and pricing device. Send to 10.
Step S209: Receipt of the pricing completion notification means that product registration corresponding to one transaction at a sales floor that supports sales by weight has been completed. Therefore, the mobile terminal device 40 transmits to the transaction management server 50 a product registration completion notice, which is a notification that the product registration corresponding to 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 by the mobile terminal device 40 in step S206 corresponding 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 basket information corresponding to the current transaction. As a result, the registration of one product (product type) in one transaction is confirmed. In step S302, which is executed first for one transaction, the transaction management server 50 generates new basket information, and then registers the received product registration information in the generated basket information. I do. When generating new basket information, the basket identification information to be stored in the basket 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 the product registration information has not been received, or after executing the processing in step S302, the transaction management server 50 receives the product registration completion notice transmitted by the mobile terminal device 40 in step S209. is received. If it is determined that the product registration completion notification has not been received, the process returns to step S301. When it is determined that the product registration completion notification has been received, the processing related to the generation of basket information corresponding to one transaction shown in the figure is ended. Registration of all products corresponding to one transaction is confirmed in response to the completion of the processing related to the generation of basket information corresponding to one transaction.

According to the process shown in the figure, the weighing and pricing apparatus 10 according to the present embodiment issues a single item label in response to receiving a receipt confirmation notification of product pricing information from the connected mobile terminal device 40. It is designed to In other words, although not specifically shown in the process of FIG. If not, the weigh pricing device 10 will not issue a single item label. At this time, for example, error notification is performed. As a result, the weighing and pricing apparatus 10 issues only the single item label of the item for which the item pricing information has been received by the portable terminal device 40 .
In this case, the store clerk and the customer can confirm that the portable terminal device 40 normally receives the pricing information necessary for registering the commodity sold by weight in response to the issuance of the single item label. In other words, the store clerk and the customer can accurately determine whether or not the product registration processing in the portable terminal device 40 has been executed normally.

<Second embodiment>
Next, a second embodiment will be described. In the first embodiment described above, a case where a customer who intends to purchase a product at a sales floor where the weighing and pricing device 10 is arranged uses the mobile terminal device 40 to register the product is taken as an example.

In some cases, the store can handle both customers who use the mobile terminal device 40 to register products and shop, and customers who do not use the mobile terminal device 40 to shop. .
When dealing with a customer who does not use the mobile terminal device 40 for shopping, a POS register operated by a salesclerk is arranged in the store for shopping at a sales floor where product shelves are arranged, and the customer can select from the product shelves. Bring the product taken out in step to the POS register. The store clerk who operates the POS register registers the merchandise brought by the customer and settles the account.
Alternatively, a registration device that performs product registration according to the operation of a store clerk may be arranged in the store. The customer brings the product selected from the product shelf to the registration device. The store clerk who operates the registration device performs an operation to register the merchandise brought by the customer. Settlement information reflecting the result of product registration processing by the registration device is acquired by the settlement device 20 in a predetermined manner. Specifically, the settlement information may be transmitted to the settlement device 20 directly from the registration device or via a host device.
Alternatively, an accounting ticket (registered trademark) is issued by the registration device, and the customer causes the checkout device 20 to read the code information printed on the checkout ticket. The attached settlement information may be obtained from a registration device, a higher-level device, or the like. Alternatively, the code information printed on the accounting ticket may include the settlement information. The customer can pay by operating the checkout device 20 that has acquired the checkout information.
Alternatively, a full self-service POS register may be arranged at the store. The customer may register the merchandise he or she has brought from the merchandise shelf at the full self-service POS register, and perform an operation to pay the bill.

On the other hand, in the sales system of the present embodiment, in the sales floor for products sold by weight where the weighing and pricing apparatus 10 is arranged, customers who shop using the mobile terminal device 40 and customers who do not use the mobile terminal device 40 It is configured to be able to respond as follows according to the customer who is shopping.

The flowchart of FIG. 15 shows an example of a processing procedure executed by the weighing and pricing apparatus 10 of this embodiment in response to pricing in one transaction.
In the following description, a case will be exemplified in which prices are set for specific fixed-price products in addition to the products sold by weight at the sales floor for the products sold by weight.
Also, the processing of the mobile terminal device 40 and the transaction management server 50 corresponding to the processing of the weighing and pricing device 10 in FIG. 12 may be the same as in FIG.

Step S1101: The weighing and pricing device 10 first executes product identification processing. The commodity specifying process is a process of specifying whether the commodity to be priced is a commodity sold by weight or a fixed price commodity. As the product identification process, the weighing and pricing apparatus 10 determines whether the type of the input product item indicated in the product master corresponds to whether the item is sold by weight or fixed price, depending on the item of the product input by the store clerk's operation, for example. You have to decide whether to
It should be noted that the operation of inputting the item of the product performed by the store clerk in the product specifying process corresponds to the specification of the product to be registered. That is, the weighing and pricing apparatus 10 designates a product to be registered according to an operation performed by a store clerk for inputting the item of the product.

Step S1102: The weighing and pricing apparatus 10 determines, as a result of the product identification processing in step S1101, whether the product to be priced is a sale-by-measure product or a fixed-price product.
Step S1103: If it is determined in step S1102 that the product is sold by weight, the weighing pricing device 10 executes weighing corresponding pricing processing. The metric-based pricing process may conform to step S102 in FIG. 12, for example.
Step S1104: If it is determined in step S1102 that the product is a fixed-price product, the weighing and pricing device 10 executes quantity-based pricing processing. That is, in this case, the store clerk inputs the number of fixed-price products to be registered into the weighing and pricing device 10 . The number input by the store clerk may be performed, for example, by manipulating the numbers. Alternatively, the input of the number of products by the store clerk may be an operation (work) of placing the products one by one on the scale table 109a. In this case, in the weighing and pricing apparatus 10, the weight measured by the weighing unit 109 changes step by step by a certain amount or more as the products are placed one by one on the weighing platform 109a. The number of times is counted as the number of products. Then, the weighing and pricing apparatus 10 calculates the price of the product using the input quantity and the weight unit price set for the item of the product to be registered.
The weighing and pricing apparatus 10 displays the item, quantity, price, etc. of the product to be purchased on, for example, the store clerk display section 105 and the customer display section 106 . The store clerk confirms with the customer about the number of items, etc., and when the customer's consent is obtained, performs an operation of instructing determination of the price of the purchase target product.

Step S1105: After the process of step S1103 or step S1104, the weighing and pricing apparatus 10 displays the connection information code on the display unit for customer 106 in response to the determination of the price of one product to be purchased as described above. display.

Step S1106: In this embodiment, not only customers who use the mobile terminal device 40 but also customers who do not use the mobile terminal device 40 receive pricing with the weighing and pricing device 10 . In this case, the customer using the mobile terminal device 40 performs an operation to cause the mobile terminal device 40 to 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 mobile terminal device 40 orders the next product or receives the product from the clerk without performing the operation of connecting the mobile terminal device 40 to the weighing and pricing apparatus 10 so as to be communicable. wait, etc.
Therefore, the weighing and pricing apparatus 10 determines whether or not a predetermined time has passed since the display of the connection information code was started in step S1105. The predetermined time here may be set in consideration of the standard time required from when the connection information code is displayed to when the customer completes the operation of having the mobile terminal device 40 read the connection information code.

Step S1107: While it is determined in step S1106 that the predetermined time has not elapsed, the weighing and pricing apparatus 10 further determines whether or not connection processing has started. As described above, when the customer corresponding to the current transaction is the customer who uses the mobile terminal device 40, the customer performs an operation to cause the mobile terminal device 40 to read the connection information code displayed in step S1105. Become. After reading the connection information code, the mobile terminal device 40 issues a connection request to the weighing and pricing device 10 (step S202 in FIG. 12), and establishes a connection between the mobile terminal device 40 and the weighing and pricing device 10. A connection process is started to After starting the connection process in response to the connection request from the portable terminal device 40 in this manner, the weighing and pricing apparatus 10 determines that the connection process has started in step S1107.
If it is determined in step S1107 that the connection process is not started, the process returns to step S1106. In this way, the weighing and pricing apparatus 10 determines whether or not the connection process is started within a predetermined time in the state where the connection information code is 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 apparatus 10 causes the store clerk display section 105 to display a connection necessity confirmation screen.
In response to the lapse of a predetermined time after the connection information code is displayed, the weighing and pricing device 10 determines that the corresponding customer is a customer who does not use the mobile terminal device 40, and prints the single item label on which the code information is printed. You may be made to issue. However, for example, the customer who intends to use the mobile terminal device 40 may be preoccupied with other things and forget to perform the operation to have the mobile terminal device 40 read the connection information code. There is a possibility that the predetermined time will pass due to taking time to handle 40.
Therefore, the weighing and pricing apparatus 10 of the present embodiment does not immediately issue a label when a predetermined time has elapsed since the connection information code was displayed on the customer display unit 106, but instead displays a connection necessity confirmation screen. By displaying it, the store clerk is asked to confirm whether or not the customer does not use the mobile terminal device 40 .

FIG. 16 shows an example of the connection necessity confirmation screen. The screen for confirming whether or not connection is necessary in FIG. 10 is, for example, in the form of a pop-up window, and is displayed so as to be superimposed on the screen that was displayed on the clerk-side display unit 26 until just before the label printing operation was performed. It can be.
A connection information code display button BT1 and a label issue button BT2 are arranged on the connection necessity confirmation screen in FIG. For example, the connection information code display button BT1 is a button operated when it is confirmed that the customer is using the mobile terminal device 40 and the store clerk determines that the mobile terminal device 40 should be connected. The label issue button BT2 is a button operated to issue a single item label when it is confirmed that the customer is not using the portable terminal device 40 and the clerk decides that the label can be issued as it is. be.
When the connection necessity confirmation screen is displayed, the store clerk confirms whether or not the customer uses the mobile terminal device 40 by looking at the customer's behavior or by asking the customer.

The description is returned to FIG.
Step S1109: The weighing and pricing apparatus 10 determines whether or not it has been confirmed that connection is not required while the connection necessity confirmation screen is displayed in step S1108.
When it is confirmed that the customer is a customer using the mobile terminal device 40, the salesclerk operates the connection information code display button BT1. When the connection information code display button BT1 is operated, the weighing and pricing device 10 determines that confirmation that connection is necessary has been obtained. In this case, the process returns to step S1106 after the connection necessity confirmation screen is erased. As a result, the display of the connection information code on the customer display unit 106 started in step S1105 is continued.
Note that if the connection information code displayed on the customer display unit 106 is to be erased in response to the label issuing operation, the process returns to step S1105, and the customer display unit At 106, the connection information code may be redisplayed.

Step S1110: When it is confirmed that the customer is not a customer using the mobile terminal device 40, the salesclerk operates the label issue button BT2 on the connection necessity confirmation screen. When the label issuing button BT2 is operated, the weighing and pricing apparatus 10 determines that it has been confirmed that connection is unnecessary.
In this case, the weighing and pricing apparatus 10 issues a single item label reflecting the result of the pricing process for the item to be registered this time for customers who do not use the mobile terminal device 40 . The store clerk affixes the single-item label issued in this way to the item to be priced this time.
As a single-item label for customers who do not use the mobile terminal device 40, as shown in FIG. 14, the result of the pricing process is printed in characters, and code information is printed. The code information of the single product label corresponding to the customer who does not use the portable terminal device 40 is read by a device capable of product registration processing, such as a POS register operated by a store clerk, a registration device, or a full self-service POS register. This includes the contents that can be used when executing the product registration process.
Such code information may include, for example, a product code, weight or quantity, unit price (unit price per weight or unit price per predetermined number), price, and the like. Thereby, a customer who does not use the portable terminal device 40 can receive the registration of the commodities priced at the sales floor (the sales counter corresponding to the pricing) where the weighing and pricing device 10 is installed, and can settle the account.

Step S<b>1111 : The mobile terminal device 40 executes the connection process started in response to step S<b>1107 to establish connection with the mobile terminal device 40 .
The processing of steps S1112 to S1116 is the same as steps S105 to S109 in FIG. However, in the case of S1115, a single item label is issued according to the label issuing operation. The label issuance 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. There may be. Also, the code information is not printed on the single item label to be issued. At this time, the weighing and pricing apparatus 10 may display a screen (for example, a pop-up window) on which the label issuing operation is performed in response to the reception confirmation notification from the mobile terminal device 40 in step S1114.

Further, when issuing a single-item label in step S1115, an issuance confirmation screen for confirming the issuance of the single-item label may be displayed on the clerk display unit 105. FIG.
FIG. 17 shows an example of the issue confirmation screen. On the issuance confirmation screen in the figure, a confirmation button BT3 is arranged along with a message announcing that a single item label will be issued in response to the completion of the transmission of the product pricing information transmitted in step S1113. there is
The store clerk operates the confirmation button BT3 arranged on the displayed issuance confirmation screen to cause the weighing and pricing apparatus 10 to issue a single item label. Alternatively, a single product label may be issued after receiving a reception completion notification of the product pricing information from the portable terminal.

The description is returned to FIG.
Step S1117: When it is determined in step S1116 that the pricing of the product corresponding to one transaction has been completed, the weighing and pricing device 10 determines whether or not it is currently connected to the mobile terminal device 40. do. If it is determined that the device is not connected to the mobile terminal device 40, the weighing and pricing device 10 may skip the processing of step S1119 and terminate the processing of FIG.

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

In the case of the processing procedure example as described above, in the present embodiment, it is possible to respond to a customer who is shopping at a price-based counter as follows. That is, in the case of a customer who does not use the portable terminal device 40, the single item label on which the code information is printed is attached to the priced item. As a result, even a customer who does not use the mobile terminal device 40 can receive product registration at a POS register or the like. On the other hand, the customer using the portable terminal device 40 does not need to register the product at a POS register or the like, so he/she attaches a single-item label on which code information is not printed to the priced product.
As described above, in the present embodiment, a single item label on which code information is printed is issued for customers who do not use the mobile terminal device 40, and the code information is not printed for customers who use the mobile terminal device 40. A single item label will be issued. As a result, it is possible to clearly distinguish between the customer who uses the portable terminal device 40 and the customer who does not use the priced product by the presence or absence of the code information on the single product label. As a result, it becomes possible to efficiently conduct transactions in selling the product for which the price is set by the weighing and pricing device 10 corresponding to both customers who use the portable terminal device 40 and customers who do not use it.
In addition, under the processing of FIG. 15, the store clerk performs operations according to the same procedure for customers who use the mobile terminal device 40 and customers who do not. Specifically, the store clerk performs a pricing operation that causes the weighing and pricing apparatus 10 to execute pricing processing corresponding to either step S1103 or step S1104, and then proceeds to step S1115 or step S1110. and perform an operation to instruct the issuance of a single-item label. In other words, when dealing with customers who use the mobile terminal device 40 and customers who do not use the mobile terminal device 40, the store clerk performs the operation of pricing, and then instructs the issuance of a single item label. The procedure will be the same, such as performing the operation to Therefore, the store clerk is less likely to be confused by the operation when dealing with both customers who use the mobile terminal device 40 and customers who do not use the mobile terminal device 40 . This makes trading more efficient.
In the description of FIG. 15, the label issuance operation corresponding to the single label on which the code information is printed is the operation of the label issuance button BT2 arranged on the connection necessity confirmation screen. The operation may be the same as in the case of issuing a single item label that is not printed.

15, the connection information code is displayed in step S1105 after the weight pricing process in step S1103 or step S1104 is completed and pricing is determined. .
However, the connection information code is not displayed until the product registration information is registered in the basket information (that is, the registration of the product is confirmed) in response to the transmission of the product pricing information in step S1113, for example. may be made available. As an example, the display of the connection information code may be performed at the timing when the product identification process is executed in step S1102.
15, the connection information code is displayed for each product so that the weighing and pricing device 10 and the portable terminal device 40 are connected for each product registered. It is However, the connection between the weighing pricing device 10 and the mobile terminal device 40 may be made once for a plurality of products to be registered in one transaction. As an example, the weighing and pricing apparatus 10 may display the connection information code corresponding to one transaction when an operation corresponding to completion of pricing for one transaction is performed. In this case, the weighing and pricing device 10 may transmit the commodity pricing information of all the commodities registered in the current transaction to the connected mobile terminal device 40 .

As a modified example of this embodiment, the processing of steps S1108 and S1109 may be omitted. That is, if a predetermined time has passed since the start of display of the connection information code in step S1106, it is determined that the customer does not use the mobile terminal device 40, and the code information is printed as it is without displaying the connection necessity confirmation screen. may be configured to issue a single-item label. In this case, the elapse of a predetermined time from the start of display of the connection information code may be used as a trigger to issue a single label on which the code information is printed, even if the label issuance operation is not performed. Also, as in the first embodiment, the single item label issuance in step S1115 is triggered by the reception confirmation notification in step S1114, and the code information is not printed even if the label issuance operation is not performed. A label may be issued.

As another modification of the present embodiment, for example, steps S1108 and S1109 may be omitted, and in step S1106, instead of determining whether or not a predetermined time has elapsed, a single label on which code information is printed may be printed. It may be determined whether or not a label issuance operation instructing the issuance of the label has been performed.
In this case, the clerk confirms whether or not the customer intends to use the mobile terminal device 40 by looking at the customer's appearance or by inquiring of the customer while the connection information code is displayed in step S1105. . Then, when it is confirmed that the customer does not intend to use the portable terminal device 40, the label issuance operation is performed. As a result, a single label on which code information is not printed is issued in step S1110.
On the other hand, when the clerk confirms that the customer intends to use the portable terminal device 40, the clerk should wait for the customer to make the portable terminal device 40 read the connection information code. Then, the processing from step S1111 onward may be executed in response to the customer causing the portable terminal device 40 to read the connection information code.

<Third Embodiment>
Next, a third embodiment will be described. As in the processing shown in FIG. 15, when a single label on which code information is printed is issued for a customer who does not use the mobile terminal device 40, the following situation may occur. There is
In other words, although an operation corresponding to no connection is performed on the connection necessity confirmation screen displayed in step S1108, after the single item label on which the code information is printed is issued, the customer corresponding to this transaction In some cases, the customer using the mobile terminal device 40 is confirmed again.
As a countermeasure for such a case, the store clerk performs an operation to re-price the same product, and asks the customer to connect the mobile terminal device 40 and the weighing and pricing device 10 so that they can communicate with each other. Product registration should be performed.
However, in the case of the above-mentioned countermeasures, by re-pricing, the store clerk has to repeat the operation procedure corresponding to the pricing for the same product twice, which makes it difficult to proceed with the transaction efficiently. It can be a hindrance. In particular, when a weighing operation for weighing the product is required, an operation of inputting the number of the tare subtraction or an operation of selecting the tare from the tare preset key is required. Normally, the product is weighed after weighing the container (tray) and then performing the tare operation, so in the case of re-pricing, for example, the product is removed from the container and weighed again. It also becomes a waste of man-hours.

In this embodiment, even after issuing a single product label on which code information is printed, product registration corresponding to the customer using the portable terminal device 40 can be performed without re-pricing. Configured.

The flowchart of FIG. 18 shows an example of a processing procedure executed by the weighing and pricing apparatus 10 of this embodiment in response to pricing in one transaction. In FIG. 15, the same reference numerals are assigned to steps that are the same as those in FIG. 15, and description thereof will be omitted as appropriate.

Step S1210: After issuing the single item label on which the code information is printed in step S1110, the weighing and pricing apparatus 10 executes the following process. In other words, the weighing and pricing apparatus 10 determines whether the label reissue instruction operation is performed before the operation of inputting the item for the next pricing target product is performed or until the pricing completion operation is performed. or not.
After the single-item label is issued, the store clerk performs label reissue instruction operation when confirming that the customer being served this time is the customer using the mobile terminal device 40.例文帳に追加The label reissue instruction operation may be, for example, an operation on a button arranged at a predetermined position on the store clerk display unit 105 . Alternatively, after a single item label on which code information is printed is issued, a dialog window for confirming label reissue instruction operation is displayed on display unit 105 for salesclerk, and then a predetermined button arranged in the dialog window is displayed. label reissue instruction operation may be performed by operating .

Step S1211: In response to the label reissue instruction operation, the weighing and pricing apparatus 10 enters a state in which code information can be input. Therefore, the store clerk performs an operation to cause the scanner unit 104 to read the code information of the single-item label issued in step S1110. The weighing and pricing device 10 acquires code information read by the scanner unit 104 . The single item label whose code information has been read is collected by the store clerk.
Instead of reading the code information by the scanner unit 104, the store clerk may perform an operation (input number) of inputting a numerical value corresponding to the code information.
Note that the weighing and pricing apparatus 10 guides the store clerk to perform an operation to read the code information of the issued single-item label in response to the label reissue instruction operation being performed. good. Such guidance may be provided by display on the clerk display unit 105, voice output, or the like.

FIG. 19 shows an example of a code information reading guide screen displayed on the clerk display section 105 as a guide for performing an operation of inputting code information of a single item label.
On the code information reading guidance screen shown in the same figure, a message is displayed to guide the store clerk to input the code information printed on the single item label (reading by the scanner unit 104 or entering a number), and a confirmation button BT3 is displayed. are placed. After operating the confirmation button BT3, the store clerk performs an operation of inputting the code information printed on the single item label.

Return the description to FIG.
Step S1222: The weighing and pricing apparatus 10 causes the customer display section 106 to display the connection information code. After the process of step S1222, the process proceeds to step S1111.
In this case, the customer performs an operation to read the connection information code displayed in step S1222 with his or her mobile terminal device 40. FIG. As a result, the mobile terminal device 40 executes connection processing for connecting to the weighing and pricing device 10 so as to be communicable. At this time, the weighing and pricing apparatus 10 executes the processes from steps S1111 to S1115. That is, the product corresponding to the single-item label on which the code information is printed is registered in the basket information by the transaction management server 50 by being transmitted again as product pricing information in step S1113. In other words, it is handled as a product registered in transactions using the mobile terminal device 40 .

If the code information of the single item label includes the transaction number, the weighing and pricing apparatus 10 reissues the single item label including the code information read in step S1211 and the product value including the transaction number. The attachment information may be transmitted to the mobile terminal device 40 .
On the other hand, for example, when the code information of a single product label contains the product number and price information but not the transaction number, the weighing and pricing device 10 determines the weight unit price of the product (for example, Alternatively, the store clerk may input it), and after calculating the weight from the amount included in the code information read in step S1211, the single item label may be reissued.
In addition, since settlement can be performed using, for example, the product number and price information, the weighing and pricing device 10 can transmit at least the corresponding product product number and price information to the portable terminal device 40. good.
Furthermore, the label issuance history may be stored in a predetermined device in the sales system of this embodiment. In this case, the weighing and pricing apparatus 10 searches for the corresponding label issuance history from the stored label issuance histories using, for example, predetermined information included in the code information read in step S1211 as a search key. You may transmit the label issuance history acquired as product pricing information.

<Fourth Embodiment>
Next, a fourth embodiment will be described.
In the first embodiment described above, the weighing and pricing apparatus 10 issues a single item label corresponding to one item each time the pricing of one item is determined in one transaction.
On the other hand, the weighing and pricing apparatus 10 according to the present embodiment provides an addition label printed with the content indicating the total amount of the product price-priced in one transaction in response to the completion of pricing for one transaction. to be issued.

FIG. 20 shows an example of an addition label. In the figure, the names of three commodities whose pricing is fixed in one transaction, the price of each commodity, the total price of each commodity, etc. are printed.
Also, code information (an example of a bar code is shown in the figure) is printed on the addition label in the figure. In this embodiment, the information printed on the bar code of the addition label is not particularly limited as long as it is information that can be obtained by the weighing and pricing apparatus 10 in response to the product pricing process in one transaction. As the simplest example, the code information of the addition label may indicate, for example, the department code corresponding to the sales floor where the weighing and pricing device 10 is arranged, and the total price information of the merchandise.
Further, the code information of the add-on label may include a transaction identifier and information for each product whose pricing is determined in one transaction. If the code information of such a premium label is used, for example, when correcting the transaction history after settlement processing such as returned goods, the code information of the premium label is read by the settlement device 20 or the like, and the transaction history is called up and corrected. can do In addition, it is possible to inspect the products sold by weight in one transaction by having the checkout device 20 or the like read the code information of the addition label.

A processing procedure example of the weighing and pricing apparatus 10 in this embodiment will be described with reference to FIG. 12 .
As for the processing procedure of the weighing and pricing apparatus 10 of this embodiment, first, step S108 in FIG. 12 may be omitted. In addition, a step of issuing an additional label is added after it is determined in step S109 that the pricing of the product corresponding to one transaction has been completed.

It should be noted that the weighing and pricing apparatus 10 may issue a single item label each time the pricing of a product is determined, and may issue an additional label upon completion of pricing for one transaction.
In this way, when issuing a single item label for each product whose pricing has been confirmed together with the addition label, the code information of the addition label includes the transaction identifier and the information for each product whose pricing has been confirmed in one transaction. In this case, the printing of the code information may be omitted for the single item label.

Moreover, when applying 4th Embodiment to 2nd Embodiment and 3rd Embodiment, you may be comprised as follows.
For example, based on the flowchart of FIG. 15 or 18, the processing of steps S1110 and S1115 is 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 corresponding to one transaction has been completed.
In this case, as the step of issuing the addition label, if the mobile terminal device 40 has not been connected to the weighing and pricing device 10 so far, the addition label on which the code information is printed is issued; may be adapted to issue additive labels on which code information is not printed.

<Fifth Embodiment>
Next, a fifth embodiment will be described.
FIG. 21 shows a configuration example of the sales system of this embodiment. In the figure, the same parts as those in FIG.
The sales system shown in the figure further includes a weighted sales management server 60 . The weighing sales management server 60 is communicably connected to each of the weighing pricing devices 10 . Also, the metered sales management server 60 is communicatively connected to the transaction management server 50 .
The weighing sales management server 60 manages product pricing information reflecting the result of the pricing process executed by the weighing pricing apparatus 10 .

Although illustration is omitted, the configuration of the metered sales management server 60 may be configured to include a CPU, a storage unit, a RAM, and a communication unit, similar to the transaction management server 50 of FIG.

With reference to the sequence diagram of FIG. 22, processing executed by the weighing and pricing apparatus 10, the mobile terminal device 40, the transaction management server 50, and the weighted sales management server 60 of the present embodiment in relation to product registration in one transaction. A procedure example will be described.
Step S1001: The weighing and pricing apparatus 10 executes pricing processing for one product according to the product pricing operation of the store clerk.
Step S1002: When the product pricing is determined in step S1001, the weighing and pricing apparatus 10 transmits to the weighing and selling management server 60 product pricing information indicating the result of the determined product pricing processing. The transmitted product pricing information includes a product pricing information identifier that uniquely identifies the product pricing information.
Step S1003: Upon receiving the product pricing information transmitted in step S1002, the metered sales management server 60 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 the execution of the pricing process in step S1001, the weighing and pricing apparatus 10 transmits the product pricing information in step S1002 and displays the connection information code on the customer display unit 106. FIG. The connection information code displayed here includes control information for communicably connecting the mobile terminal device 40 to 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 code scan screen and is ready to read the code. Therefore, the customer 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 connection processing with the transaction management server 50 according to the connection procedure based on the control information included in the connection information code read in step S1005.

Step S1007: When the connection with the transaction management server 50 is established by the connection processing in step S1006, the portable terminal device 40 passes the product pricing information identifier included in the connection information read in step S1005 to the transaction management server 50. Send to
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. FIG.
Step S1009: In response to receiving the merchandise registration information request, the weighted sales management server 60 selects the merchandise pricing information identifier included in the received merchandise registration information request from among the merchandise registration information stored by itself. Search for product registration information associated with . The metered sales management server 60 transmits the retrieved product registration information to the transaction management server 50 .
Step S1010: The transaction management server 50 registers the received product registration information in the basket information.

Step S1011: As the product registration information is registered in the basket information by the transaction management server 50 in step S1010, the product registration for the one product for which pricing processing was performed by the weighing and pricing apparatus 10 in step S1001 is completed. I did. Therefore, the transaction management server 50 transmits a registration completion notice to the mobile terminal device 40 .
Note that the mobile terminal device 40 that has received the registration completion notification confirms that, for example, the product registration for one product targeted for the pricing process executed by the weighing and pricing apparatus 10 corresponding to the connection information code read this time has been completed. You may perform the display etc. which alert|report to a visitor that it was completed.

Step S1012: The transaction management server 50 also transmits to the metered sales management server 60 a reception confirmation notification indicating that the merchandise registration information transmitted in step S1009 has been received normally. The acknowledgment notification includes a product pricing information identifier that identifies the corresponding product registration information.
Step S1013: In response to the reception confirmation notification transmitted in step S1012, the metered sales management server 60 selects the product indicated by the product pricing information identifier included in the reception confirmation notification among the product registration information stored therein. Manage registration information so that it is indicated that it has been sent.

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

The processing of steps S1001 to S1015 is referred to as "loop processing 1". It is executed repeatedly each time it is done to the object.

Step S1016: When the clerk confirms that pricing has been completed for all of the products specified by the customer for one transaction, the clerk weighs an operation for declaring completion of pricing for one transaction (pricing completion operation). This is done for the pricing device 10 . When the pricing completion operation is performed, the weighing and pricing device 10 determines that the pricing of the product corresponding to one transaction has been completed.
Step S<b>1017 : When it is determined that the pricing of the product corresponding to one transaction has been completed, the weighing and pricing apparatus 10 transmits a pricing completion notice to the weighing sales management server 60 . The pricing completion notification indicates that the pricing process for all products corresponding to one transaction has been completed.
Step S1018: In response to receiving the pricing completion notification transmitted in step S1017, the metered sales management server 60 transmits (or may forward) the pricing completion notification to the transaction management server 50. FIG.
Step S1019: In response to receiving the pricing completion notification transmitted in step S1018, the transaction management server 50 transmits (or may forward) the pricing completion notification to the mobile terminal device 40. FIG. The mobile terminal device 40 that has received the pricing completion notification may display, for example, the settlement guidance screen of FIG. 11(D). Further, in step S1019, in response to the receipt of the pricing completion notification by the mobile terminal device 40, for example, processing is executed to disconnect the connection between the mobile terminal device 40 and the transaction management server 50. good.

In this embodiment, the weighing pricing device 10 and the mobile terminal device 40 are not connected so as to be able to communicate directly, 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. In addition to being connected, the weighted sales management server 60 and the transaction management server 50 communicate with each other. As a result, through the process of FIG. 10, the weighing and pricing apparatus 10 receives a notification from the weighing and selling management server 60 that registration of the product registration information corresponding to the product pricing in the basket information has been completed (that is, in step S1014). A single item label can be issued in response to receipt of the transmitted registration completion notice. In this case as well, if the corresponding product registration information is not registered in the basket information in the transaction management server 50 even though the product pricing information has been sent from the weighing and pricing device 10, the weighing and pricing device 10 does not issue a single item label. As a result, in the weighing and pricing apparatus 10, only the single item label of the product to be valued whose corresponding product registration information is registered in the basket information is issued.
In this case, the clerk and the customer can confirm that the item to be subjected to the pricing process has been properly registered in the basket information by the issuance of the single-item label. In the case of this embodiment, the customer can access the basket information of the product targeted for the pricing process also by the notification performed by the mobile terminal device 40 in response to the reception of the registration completion notification (step S1011). You can confirm that the registration of has been performed successfully.

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

As a modification of the present embodiment, the second embodiment is applied, and when the pricing of one transaction is completed, the weighing and pricing device 10 changes the price of the product priced in one transaction. It is also possible to issue an addition label on which the content indicating the total amount is printed. Alternatively, the weighing and pricing apparatus 10 may issue a single item label each time the pricing of an item is determined, and an additional label upon completion of pricing for one transaction.

<Modification>
Modifications of this embodiment will be described below.
[First modification]
Under the process shown in FIG. 12, the weighing and pricing device 10 may not be able to receive the reception confirmation notification in step S107 for some reason.
Examples of cases where the reception confirmation notification cannot be received include the following cases. One is a case where the commodity pricing information to be transmitted by the weighing and pricing device 10 is not normally transmitted in step S106. Another possibility is that the product pricing information was transmitted in step S106, but the mobile terminal device 40 could not receive the product pricing information normally. Another is a case where the reception confirmation notification that should be sent by the mobile terminal device 40 could not be normally sent in step S205. In one case, the product pricing information was transmitted in step S205, but the weighing and pricing apparatus 10 could not normally receive the reception confirmation notification.

If the weighing and pricing apparatus 10 does not receive the reception confirmation notification within a certain period of time after executing the process of step S106 for transmitting the product pricing information and times out, an error occurs in the transmission and reception of the product pricing information. It is determined that When it is determined that an error has occurred in the transmission and reception of product pricing information, the weighing and pricing apparatus 10 notifies that the error in the transmission and reception of the product pricing information has occurred, for example, on the store clerk display unit 105. be. It should be noted that the customer display unit 106 may also notify that an error has occurred in the transmission and reception of product pricing information.

As a response to the notification of the occurrence of an error in the transmission and reception of product pricing information as described above, for example, the store clerk asks the customer to confirm whether or not the corresponding product has been properly registered. You may be told to ask for help. For example, by looking at the display on the mobile terminal device 40, the customer can determine whether or not the product registration information has been successfully transmitted/received to/from the transaction management server 50 corresponding to step S206. (whether or not the corresponding basket information has been registered normally).
If it can be confirmed that the product registration information has been sent and received normally, it means that only an error has occurred in the sending and receiving of the receipt confirmation notice, and the product has been registered normally. No corrective action is required. Alternatively, for example, the customer performs an operation to resend the reception confirmation notification from the mobile terminal device 40, and the weighing and pricing apparatus 10 receives the reception confirmation notification, thereby eliminating the transmission/reception error of the product pricing information. may be treated as if

In addition, as a response to the notification of the occurrence of an error in the transmission and reception of product pricing information, the weighing and pricing device 10 generates a pricing information code (bar code or double A label (re-registration label) printed with a dimension code may be issued.
When issuing the re-registration label, a dialog window for confirming whether or not the issue is necessary may be displayed on the salesclerk display unit 105 for the salesclerk. In this case, the clerk declares that it is not necessary to issue a re-registration label when it is confirmed that the product registration information has been successfully transmitted to and received from the transaction management server 50. to the dialog window. On the other hand, if the sales clerk confirms that the transmission and reception of the product registration information to and from the transaction management server 50 are not performed normally, the clerk instructs the issuance of the label for re-registration. against
When the re-registration label is issued, the store clerk passes the issued re-registration label to the customer. The customer causes the portable terminal device 40 to read the pricing information code printed on the handed over re-registration label. The mobile terminal device 40 transmits product pricing information indicated by the read pricing information code to the transaction management server 50 as product registration information. As a result, the basket information of the product corresponding to the transmission/reception error of the product pricing information is registered in the transaction management server 50 .

[Second modification]
In each of the embodiments described above, the connection information code is displayed each time the pricing process is performed for each product in one transaction. In this modified example, a connection information code is displayed corresponding to one transaction.
In this case, for example, the connection information code is displayed on the customer display unit 106 by the store clerk performing a predetermined operation on the weighing and pricing device 10 before the first price setting operation for the product sold by weight in one transaction. Alternatively, the connection information code may be included in a standby screen displayed on the customer display unit 106 in a state of waiting for the first pricing operation in one transaction, for example.

In this case, the customer causes the mobile terminal device 40 to read the connection information code displayed on the customer display unit 106 before the pricing of the first product is performed. The mobile terminal device 40 establishes a connection with the weighing and pricing device 10 according to the connection condition (connection procedure) indicated by the read connection information code.
When the communication is established, the weighing and pricing device 10 executes a process of associating the mobile terminal device 40, which is the communication partner, with the current transaction. For this purpose, the weighing and pricing device 10 acquires a terminal identifier from, for example, the mobile terminal device 40 with which it communicates. The terminal identifier may be, for example, an identifier such as a MAC address that is individually assigned to each piece of hardware as the mobile terminal device 40, or an application identifier that is assigned to a shopping application installed in the mobile terminal device 40. may be

Further, in response to establishment of communication and connection with the portable terminal device 40, the weighing and pricing device 10 performs an operation for associating the clerk in charge of the pricing operation with the current transaction. The store clerk designation screen may be displayed on the store clerk display unit 105 .
FIG. 23 shows an example of one aspect of the clerk designation screen. A salesclerk button is arranged on the salesclerk designation screen of FIG. The store clerk button indicates correspondence with the store clerk by displaying characters or the like indicating the corresponding store clerk. In the same figure, an example is shown in which three store clerk buttons are arranged, and "clerk A", "clerk B", and "clerk C" are indicated, respectively. The salesclerk button may indicate, for example, the salesclerk's name, position, and the like. The store clerk corresponding to the displayed store clerk button is the store clerk who is currently registered (logged in) as the store clerk in charge of the selling floor of the mass-market product. Note that the clerk button of the clerk who is currently serving other customers and is currently performing a pricing operation with another weighing and pricing apparatus 10 is arranged with diagonal lines as shown in FIG. ) indicates that the operation is disabled.
Then, the clerk operates the clerk button corresponding to him/her from among the displayed clerk buttons.
In addition, an "Add" button is arranged on the clerk designation screen. For example, a situation may arise in which a store clerk needs to serve a customer before logging in as the store clerk in charge of the department. In such a case, the salesclerk designation screen does not display the salesclerk button corresponding to the salesclerk who has not yet logged in. Therefore, in this case, the clerk can log in on the spot by operating the "Add" button and performing an operation to cause the weighing and pricing device 10 to read his/her own clerk identifier, for example. In response to the login, in addition to the previously displayed store clerk buttons, the store clerk button of the corresponding store clerk is further displayed on the store clerk designation screen.

The weighing and pricing device 10 associates the store clerk identifier of the store clerk indicated by the operated store clerk button with the terminal identifier acquired from the mobile terminal device 40 as the communication partner. In addition, the weighing and pricing apparatus 10 manages product pricing information for each product corresponding to the pricing operation performed under the corresponding transaction in association with the store clerk identifier. As a result, the transaction corresponding to the mobile terminal device 40 can be uniquely identified.

Instead of operating the clerk button, for example, the clerk identifier is acquired by having the scanner unit 104 of the weighing and pricing apparatus 10 read the code information of the clerk identifier attached to the clerk's ID card possessed by the clerk. you can The store clerk ID card is in the form of, for example, an IC (Integrated Circuit) card in which a store clerk identifier is stored. good too. Further, communication is performed when an RFID (Radio Frequency Identifier) card or the like as a store clerk identification card and the weighing and pricing apparatus 10 come within a mutual communication range by a predetermined short-range wireless communication. In this case, the weighing and pricing device 10 may acquire the stored salesclerk identifier from a communicationable salesclerk ID card. In this case, if there are a plurality of clerk ID cards with which communication is possible, the clerk identifier is acquired from the clerk ID card with the strongest reception strength (that is, the clerk ID card of the clerk closest to the weighing and pricing device 10), for example. may be made to do so.

Note that a transaction identifier (transaction number) may be further associated with the mobile identifier, store clerk identifier, and merchandise pricing information. Alternatively, a transaction identifier may be associated instead of the store clerk identifier. For example, in the case of an operation that does not perform management in which the store clerk and the transaction are associated with each other as described above, the store clerk identifier is not used. Correlation with transactions becomes possible.
As described above, when associating transaction identifiers, the weighing and pricing device 10 displays a plurality of transaction selection buttons each showing a mark such as a predetermined figure or a predetermined color in place of the store clerk button. Of the transaction selection buttons, the mark and color attached to the transaction selection button operated by the store clerk may be associated with the transaction.

When the connection information code is displayed corresponding to one transaction as in this modification, the weighing and pricing device 10 updates the product pricing information each time the pricing process is performed for each product. It may not be transmitted to the mobile terminal device 40 . In other words, the weighing and pricing apparatus 10 is configured to transmit the product pricing information for all the products that have been priced for each product to the mobile terminal device 40, for example, when the pricing processing for all products corresponding to one transaction is completed. may be made
Further, in the case where the connection information code is displayed corresponding to one transaction as in the present modification, as described above, by associating the transaction with the mobile terminal device 40, one measurement pricing can be performed. Between the start and completion of the pricing operation for one transaction on the device 10, the pricing operation for another transaction can be interrupted. In other words, it is possible for one weighing and pricing device 10 to perform pricing processing for multiple transactions in parallel.
As a result, for example, the previous customer was wondering which product to ask for the next price, or for some reason, the customer had to temporarily take actions other than facing the clerk on the spot. In such a case, the store clerk can store the details of previous customer's transactions (merchandise pricing information) and price the merchandise corresponding to the next customer.

In the above example, the connection information code is displayed in correspondence with one transaction by displaying the connection information code on the customer display unit 106 at the stage prior to the pricing operation of the first bulk product in one transaction. Therefore, the weighing and pricing device 10 and the portable terminal device 40 are connected at the stage before the pricing of the commodity corresponding to one transaction is started.
However, as a mode of displaying the connection information code corresponding to one transaction, the connection code information may be displayed at the stage when pricing of all products in one transaction is completed.
FIG. 24 shows an example of a connection information code screen displayed on the customer display section 106 when pricing of all products in one transaction is completed. This figure shows an example of a mode in which the customer display section 106 has a vertically long display surface section and the notation on the screen is in English.
As in FIG. 13, the connection information code screen in FIG. 13 displays a connection information code in the form of a two-dimensional code, and also displays an image of the mobile terminal device together with an arrow pointing to the two-dimensional code.
Also, on the connection information code screen in the same figure, pricing-related information (product name, measured weight, price, etc.) for each of one or more products for which pricing processing has been performed so far in the corresponding transaction is displayed. is displayed.
In this case as well, the store clerk display unit 105 displays a message, pop-up window, icon, or the like to inform the store clerk that the connection information code is being displayed on the customer display unit 106. you can

[Third modification]
“Product registration handover” may be enabled between a plurality of weighing and pricing devices 10 . Product registration handover means that after a store clerk registers a product for one transaction with one weighing and pricing device 10, the store clerk moves to another weighing and pricing device 10 to register the product for the same transaction. is to do In product registration handover, the product registration information corresponding to the registration of the product previously performed by the weighing and pricing device 10 is taken over by the next weighing and pricing device 10 in the same single transaction. The next weighing and pricing device 10 can add information about the product registered by its own product registration process to the inherited product registration information.

For example, a customer may designate a product that is displayed at a position distant from the weighing and pricing apparatus 10 currently being operated by a store clerk. By enabling "merchandise registration handover", the store clerk goes to the designated merchandise, takes out the merchandise, and registers the merchandise with another weighing and pricing device 10 installed at the nearest location. can continue.

In the "handover of product registration" in this modification, any one of the plurality of weighing and pricing devices 10 functions as a parent, and then the parent weighing and pricing device 10 communicates with the child weighing and pricing device 10. It is realized by being connected as possible.
The child weighing and pricing device 10 associates product pricing information for each product with a price with the salesclerk identifier of the salesclerk who performed the pricing operation (or with the transaction identifier instead of the salesclerk identifier). (or both the store clerk identifier and the transaction identifier may be associated) and is transmitted to the parent weighing and pricing device 10 . For example, every time the clerk starts operating one weighing and pricing device 10, the clerk causes the weighing and pricing device 10 to read the clerk identifier recorded on his or her clerk ID card, or operates a number or a predetermined button. By doing so, the weighing and pricing device 10 acquires the store clerk identifier of the user and logs in. The store clerk causes the weighing and pricing device 10 to acquire his/her own store clerk identifier each time the weighing and pricing device 10 that performs the pricing operation is changed in response to taking over the product registration.
The parent weighing and pricing device 10 stores integrated product pricing information obtained by integrating the received product pricing information for each same store clerk identifier each time product pricing information is received.

Then, when the clerk finishes pricing all the products in one transaction, the salesclerk performs a pricing completion operation. In response to the pricing completion operation, the weighing and pricing apparatus 10 displays the connection information code on the customer display section 106 .
When the customer causes the mobile terminal device 40 to read the displayed connection information code and the mobile terminal device 40 and the weighing and pricing device 10 are communicatively connected, the mobile terminal device 40 reads the connection information. The store clerk identifier included in the code is sent to the weighing and pricing device 10 . The weighing and pricing device 10 that has received the store clerk identifier selects the integrated product pricing information associated with the received store clerk identifier from among the integrated product pricing information stored in the parent weighing and pricing device 10. It is transmitted to the mobile terminal device 40 . The mobile terminal device 40 transmits the received integrated commodity pricing information to the transaction management server 50 as commodity registration information for all priced commodities. The transaction management server 50 registers information for each product indicated in the received product registration information as basket information.
Even when "merchandise registration transfer" is possible as in this modified example, the transaction and the mobile terminal device 40 may be associated with each other as in the second modified example.
The processing corresponding to the function of the parent weighing and pricing device may be executed by, for example, a higher-level management device or the transaction management server 50 or the like. Alternatively, each time the clerk moves the weighing and pricing device 10 and logs in by entering the clerk identifier, the product pricing information of the corresponding transaction stored in the weighing and pricing device 10 of the source of movement is transferred to the destination of the movement. , and the product pricing information obtained by the pricing process at the destination may be integrated with the product pricing information thus sent.

In addition, in the case where product registration can be handed over as described above, the connection information code may be displayed on the weighing and pricing device 10 each time the product pricing process is completed. After that, when the clerk moves the weighing and pricing device 10 that performs the pricing operation to take over the product registration, the weighing and pricing device 10 of the transfer source, although the pricing for one transaction has not been completed. and the connection with the mobile terminal device 40 is cut off.
The following modes are conceivable for disconnecting the connection between the weighing and pricing device 10 of the movement source and the mobile terminal device 40 .
One is that the store clerk, who has been performing pricing operations using the source weighing and pricing device 10, must move to the moving destination weighing and pricing device 10 for the same transaction and perform the pricing operation. When such a situation occurs, the weighing and pricing device 10 of the source of movement is operated to log out. In response to being logged out in response to the logout operation, the source weighing and pricing device 10 disconnects the current connection with the portable terminal device 40 .
Alternatively, when the clerk starts the pricing operation in the moving destination weighing and pricing device 10 by taking over the product registration, the moving destination weighing and pricing device 10 acquires his/her own clerk identifier. The original weighing and pricing device 10 may disconnect from the current portable terminal device 40 . In this case, the store clerk may move to the destination weighing and pricing device 10 without performing a logout operation on the moving source weighing and pricing device 10 .
In this case, the weighing and pricing apparatus 10 at the movement source logs in from the weighing and pricing apparatus 10 at the destination through communication with the weighing and pricing apparatus 10 at the destination. The current connection with the mobile terminal device 40 is cut off in response to receiving the notification of the fact that it has been done. In addition, even if another store clerk logs in at a timing before receiving the notification that the same store clerk has logged in from the move destination weigh and pricing device 10, the source weighing and pricing device 10 Disconnects the current connection with the mobile terminal device 40 .
In other words, in this case, the connection between the source weighing and pricing device 10 and the mobile terminal device 40 is disconnected at a predetermined timing until the login to the weighing and pricing device 10 at the move destination is performed. I wish I could.
Even if the connection between the source weighing pricing device 10 and the mobile terminal device 40 is disconnected in any of the above modes, the parent The weighing and pricing apparatus 10 associates and manages the store clerk identifier and the product pricing information for the same single transaction. As a result, even if the same store clerk performs the pricing operation with any of the weighing and pricing devices 10 for one transaction, the product pricing information for the same transaction is properly integrated.

Then, for example, the store clerk identifier of the operator (the store clerk logged into the weighing and pricing device 10) who performs the pricing operation corresponding to one transaction, and the mobile terminal device 40 connected to the logged-in weighing and pricing device 10 Connection correspondence information associated with terminal identification information (for example, information such as the device ID of the mobile terminal device 40 used for connection) may be stored in the weighing and pricing device 10 . The connection correspondence information may be stored by the logged-in weighing and pricing device 10 or by the parent weighing and pricing device 10 .
By storing the connection correspondence information in this way, for example, when the store clerk moves to another weighing and pricing apparatus 10 and logs in due to product registration takeover, the connection information code can be automatically used without using the connection information code. It becomes possible to connect the weighing and pricing device 10 and the mobile terminal device 40 .
That is, in response to the clerk moving to another weighing and pricing apparatus 10 and logging in, the logged in weighing and pricing apparatus 10 acquires the connection correspondence information including the same clerk identifier as that acquired by the login. . Then, the logged-in weight pricing device 10 may use the terminal identification information included in the acquired connection correspondence information to execute the process of connecting to the corresponding mobile terminal device 40 .

[Fourth Modification]
Further, for example, a beacon terminal may be provided in the weighing and pricing apparatus 10, and the short-range wireless communication unit 405 may also function as a beacon terminal.
In this case, for example, when the mobile terminal device 40 detects the weighing and pricing device 10 by transmitting/receiving a beacon signal to the weighing and pricing device 10, the message "Are you purchasing a showcase product?" Please scan the code displayed on the scale.", etc., to the customer asking for confirmation of purchase of the bulk item. When an operation to declare the purchase of a bulk product is performed, such as an operation on a "yes" button, for example, the portable terminal device 40 displays a code scan screen.
In the description so far, the connection information code is displayed on the customer display unit 106 of the weighing and pricing apparatus 10. The customer may read the connection information code printed on the sticker with the mobile terminal device 40 . When the weighing and pricing device 10 and the mobile terminal device 40 are communicably connected in response to the reading of the connection information code, notification of the connection is sent to the mobile terminal device 40 and the weighing and pricing device. It may be directed to the customer or store clerk by means of a display or the like on the device 10 . Furthermore, at that time, the weighing and pricing apparatus 10 may output a message such as "Welcome" to the customer by display or voice. In addition, in the weighing and pricing apparatus 10, such a notification may also be made in the clerk's display unit 105. In this case, the clerk's operation should not be used to notify the clerk. It may be possible to
Also in this modified example, similarly to the third modified example, by associating the transaction identifier corresponding to one transaction with the terminal identifier of the mobile terminal device 40, the mobile terminal device 40 can set the weight and price. When connected to the device 10, the weighing and pricing device 10 may be able to identify the transaction corresponding to the mobile terminal device 40 currently connected.

At this time, for example, if the customer who is carrying the mobile terminal device 40 carelessly leaves the place, the connection between the mobile terminal device 40 and the weighing and pricing apparatus 10 during pricing processing is interrupted. Therefore, it is troublesome to perform reconnection operation by redisplaying the connection information code or the like. Therefore, the mobile terminal device 40 outputs, for example, a connection maintenance guide message to the customer by display or voice so that the connection between the mobile terminal device 40 and the weighing and pricing apparatus 10 is not interrupted. You can do it.
FIG. 25 shows an example of a mode in which a connection maintenance guidance message is output by display on the mobile terminal device 40. As shown in FIG. On the connection maintenance guidance message screen shown in FIG. A state is shown in which a message is displayed to the effect that the user should not be further away than the communication distance with the device 10).
However, there are cases in which, for example, there is no choice but to leave the place due to, for example, a sudden phone call. However, in this case, since the customer has not yet received the product by weight, the mobile terminal device 40 cancels (interrupts) the processing corresponding to the registration of the product by weight and cancels (interrupts) the product registration corresponding to normal shopping. You may be made to return to a screen. In this case, the weighing and pricing device 10 stores the transaction information including the product pricing information of the product that is priced before leaving the sales floor in association with the terminal identifier of the mobile terminal device 40. . As a result, when the customer returns to the sales floor for bulk sales and connects the portable terminal device 40 to the weighing and pricing device 10 so as to be able to communicate with it, the weighing and pricing device 10 returns to the connected portable terminal. Transaction information associated with the same terminal identifier as device 40 can be called up. In this case, the weighing and pricing apparatus 10 can add product pricing information corresponding to the restarted product pricing process to the called transaction information. In other words, product pricing information before the customer leaves the sales floor and product pricing information after the customer returns to the sales floor can be integrated and processed as information for the same transaction.
Further, when the customer needs to leave the place where the customer is interacting with the store clerk as described above, an operation (registration interruption operation) requesting interruption of processing corresponding to registration of sold-by-measure products is performed on the mobile terminal device 40. It may be made possible. FIG. 25 shows an example in which the registration suspension operation is enabled by operating the registration suspension button displayed as "temporarily leave". When the registration suspension button is operated, the mobile terminal device 40 transmits a registration suspension request to the weighing and pricing device 10 . In response to the reception of the registration interruption request, the weighing and pricing apparatus 10 disconnects communication with the mobile terminal device 40, and stores the product pricing information about the corresponding transaction as the terminal identifier of the mobile terminal device 40. Store them in association with each other.

[Fifth Modification]
In the present embodiment, for example, if it is a stage before settlement is performed, by operating the mobile terminal device 40 on which the shopping application is running, an arbitrary item is selected from among the items for which basket information is registered, and the registration is canceled. can do.
After that, as in the second modified example, when the weighing and pricing device 10 completes pricing processing for all products corresponding to one transaction, product pricing information for all the products that have been priced is generated. If the mobile terminal device 40 is configured to transmit the product pricing information to the mobile terminal device 40, before the weighing and pricing device 10 completes pricing processing for all products corresponding to one transaction, the mobile terminal device 40 cannot be obtained. In other words, the customer in this case is registered by the pricing process until the portable terminal device 40 receives the product pricing information for all the products and the corresponding basket information is registered in the transaction management server 50. Items cannot be canceled. Therefore, for example, by operating the mobile terminal device 40, it may be possible to cancel even a product for which the basket information has not yet been registered. However, in this case, for example, the transaction management server 50 preferably treats the canceled product as a pending product so that the salesclerk can perform a clearing operation at the time of payment.

[Sixth Modification]
In the above-described first embodiment, designation of products to be purchased (designation of item and weight or number of products) from a customer to a store clerk at a sales floor for pricing is performed by the customer orally communicating to the store clerk. be done. Then, the store clerk operates the weighing and pricing device 10 to price the product specified by the customer, and the weighing and pricing device 10 transmits the product pricing information to the transaction management server 50, whereby one product is sold. was registered as a product. In such a product registration procedure, the customer himself/herself does not perform an operation to have the portable terminal device 40 read the code information of the product.

In the sales system of this modified example, products are registered in response to the customer's use of the mobile terminal device 40 to read the code information corresponding to the product to be purchased, even in the price-based sales floor. make it
In this case, the customer may operate the mobile terminal device 40 in the same procedure as in the sales floor where the product shelf is installed, even in the price-based sales floor. As a result, the customer is less likely to be confused by the operation of the mobile terminal device 40 at the pricing counter.

An example of the procedure for product registration at the price-setting counter according to this modification will be described below with reference to FIGS. 26 to 29. FIG. In the following explanation, an example will be given of a case in which three items of fixed-price apples, bulk-sale cherries, and fixed-price asparagus products are registered for one customer at a pricing counter. .
In this modification, product registration is divided into a first stage and a second stage. The product registration in the first stage is product registration performed by the customer having the mobile terminal device 40 read the code information corresponding to the product. In the second step product registration, the basket information is registered in the transaction management server 50 in response to the salesclerk operating the weighing and pricing device 10 to price the product registered in the first step product registration. Product registration.

In the price-based sales floor corresponding to this modification, for example, shelf labels are arranged for customers in correspondence with each product displayed in the showcase. The shelf labels may be arranged, for example, in the showcase so that the customer can see the correspondence with the corresponding product.
The shelf label indicates the item and unit price (weight unit price or unit price) of the corresponding product, as well as code information. The shelf label code information includes, for example, a product code indicating the item of the corresponding product.
Note that the shelf label of this modified example may be printed on a sheet of paper, resin, or the like, or a device such as an electronic shelf label may be used.

First, product registration in the first stage is performed as follows.
When the customer looks at the products displayed in the showcase and decides the product to be purchased (the product to be purchased), the customer sends the code information indicated on the shelf tag corresponding to the decided product to be purchased to the portable terminal device 40. Do the operation to read by.
Here, the customer first purchases two apples as the first product to be purchased. In this case, the customer sets the product registration mode for the mobile terminal device 40 on which the shopping application is running, and then causes the mobile terminal device 40 to read the code information indicated on the shelf label of the apple.

FIG. 26A shows an example of a product registration screen displayed on the touch panel display unit 406 in response to setting of the product registration mode. A scan image area AR1 and a registered product list area AR2 are arranged on the product registration screen.
The product registration mode set in this manner may be common to the product registration mode set when reading the code attached to the product displayed on the product shelf. In this case, the product registration screen displayed on the display unit 406 with touch panel according to the setting of the product registration mode is also displayed in the product registration mode set when reading the code attached to the product displayed on the product shelf. It may be the same aspect as the product registration screen.

In addition, the product registration screen in the figure shows an example of display contents before the product registration of apples is performed. In this case, the customer has not yet registered any products since entering the store, and the apple is the first product to be registered in this transaction. Therefore, the registered product list area AR2 of the product registration screen in FIG.

FIG. 26(B) shows an example of contents indicated by shelf labels provided corresponding to apples displayed in the showcase. The shelf label in the figure indicates that the product item is an apple, and the unit price per piece is $1.20. The apple in this case is a fixed-price product because the unit price per apple is set. Code information in the form of a two-dimensional code is arranged on the shelf label in FIG. The code information on the shelf label may be a one-dimensional code (bar code).

When the customer performs an operation to have the mobile terminal device 40 read the code information, an image captured by the camera (imaging unit 408) is displayed in the scan image area AR1 on the product registration screen of FIG. 26(A). . The customer performs an imaging operation so that the code information of the apple shelf label fits within the frame shown in the scan image area AR1. When the mobile terminal device 40 detects that the code information of the apple shelf label fits within the frame in the scan image area AR1, the mobile terminal device 40 executes processing for reading the code information.

For example, the code information includes the product code corresponding to apples, the product name, and the unit price per piece (number unit price). Therefore, the mobile terminal device 40 causes the touch panel display unit 406 to display a quantity designation screen based on the content of the read code information. In this case, the portable terminal device 40 determines that the corresponding product is a fixed-price product based on the fact that the unit price included in the code information is the unit price, and displays a quantity designation screen in a format corresponding to the fixed-price product. make it

It should be noted that a screen transmitted from the transaction management server 50 may be displayed as the display of the quantity designation screen. In this case, the mobile terminal device 40 transmits to the transaction management server 50 a quantity designation screen request containing the read code information. If the product indicated by the received code information is a fixed-price product, the transaction management server 50 generates a quantity designation screen in a format corresponding to the fixed-price product, and transmits the generated quantity designation screen to the mobile terminal device 40. do. Alternatively, if the product indicated by the received code information is a product sold by weight, the transaction management server 50 generates a quantity designation screen in a format corresponding to the product sold by weight, and sends the generated quantity designation screen to the portable terminal device 40. Send to
The mobile terminal device 40 causes the display unit 406 with the touch panel to display the received quantity designation screen.

FIG. 26C shows an example of a quantity designation screen displayed in response to reading code information corresponding to apples. In the quantity designation screen of FIG. 10, the product for which the quantity is to be designated is apples, and the unit price per piece is 1.20 dollars. In addition, on the quantity designation screen of FIG. 4, a message for guiding the user to designate (select) the quantity, a quantity designation area AR11, and a send button BT11 are arranged.

The customer can input the number of apples, which are the products to be registered, by operating the quantity designation area AR11. The customer, for example, touches the quantity designation area AR11 to display a pull-down menu of numerical values, and performs an operation of selecting an arbitrary numerical value from the numerical values presented in the displayed pull-down menu. By such an operation, the selected numerical value is displayed as the input result of the number of apples in the quantity designation area AR11.
The number input operation for the quantity designation area AR11 may be a numerical value input operation using a software keyboard superimposed and displayed on the quantity designation screen.

After inputting the number, the customer operates the send button BT11. In response to the transmission button BT11 being operated, the mobile terminal device 40 transmits the product registration information to the transaction management server 50. FIG. The product registration information includes a transaction identifier indicating the corresponding transaction, a product code, and information indicating the designated quantity (number).

The mobile terminal device 40 determines that the transmission of the product registration information has been completed by receiving the notification that the product registration information has been received from the transaction management server 50, and displays the product registration screen again on the display unit 406 with touch panel. Let As a result, the mobile terminal device 40 becomes ready to read the code information corresponding to the next product registration.
FIG. 26D shows an example of a product registration screen displayed on the display unit 406 with touch panel in response to the completion of transmission of the product registration information for the apple product. The product registration screen in this case has changed to a state in which the list items corresponding to the apple product are arranged in the registered product list area AR2. Depending on the list item corresponding to the product of apples, it is indicated that two apples were registered by the first product registration (first-stage product registration).

After completing product registration for apples as described above, the customer next purchased the cherries displayed in the showcase.
FIG. 27(A) shows an example of contents indicated by shelf labels provided corresponding to cherries displayed in the showcase. In the shelf label in the figure, the product item is cherry, and the unit price (unit weight) per kg is 10.00 dollars, and code information corresponding to the cherry is arranged. be done.
At this time, the display on the display unit 406 with the touch panel of the mobile terminal device 40 is in the state shown in FIG. Therefore, the customer uses the mobile terminal device 40 to read the code information placed on the shelf label corresponding to the cherry.
In response to reading the code information placed on the shelf label corresponding to the cherry, the mobile terminal device 40 causes the touch panel display unit 406 to display the quantity designation screen corresponding to the cherry.

FIG. 27B shows an example of the quantity designation screen displayed in response to reading code information corresponding to cherry. In the quantity designation screen of FIG. 10, it is indicated that the product for which the quantity is to be designated is cherries, and the weight unit price per 1 kg is 10.00 dollars. In addition, on the quantity designation screen of FIG. 4, a message for guiding the user to designate (select) the quantity, a quantity designation area AR11, and a send button BT11 are arranged.

In this case, the cherries are sold by weight. Therefore, the customer inputs the weight of the cherry by operating the quantity designation area AR11. The mode of operation for inputting the weight of cherries may conform to the aforementioned operation for inputting the number of apples.
For example, the customer touches the quantity designation area AR11, for example, to display a pull-down menu of numerical values indicating the weight in stages, and selects any numerical value from the numerical values presented in the displayed pull-down menu. may be configured to perform an operation to Alternatively, the weight input operation for the quantity designation area AR11 may be a numerical value input operation using a software keyboard superimposed and displayed on the quantity designation screen.
After inputting the weight, the customer operates the send button BT11. In response to the transmission button BT11 being operated, the mobile terminal device 40 transmits the product registration information to the transaction management server 50. FIG. The product registration information includes information indicating the product code and the specified quantity (weight).

Upon completion of the transmission of the product registration information, the mobile terminal device 40 causes the display unit 406 with the touch panel to display the product registration screen again.
FIG. 27C shows an example of a product registration screen displayed on the touch panel display unit 406 in response to the completion of transmission of the product registration information for the cherry product. In this case, the product registration screen has changed to a state in which list items corresponding to cherry products are further arranged in addition to the list items corresponding to apple products in the registered product list area AR2. The display of such listings indicates that the second product registration (first stage product registration) was registered for 500g of cherries.
In this case, the customer has completed the first-stage product registration for all the products that the customer wants to purchase at the pricing-enabled sales floor by completing the first-stage product registration for apples and cherries.

As described above, the mobile terminal device 40 transmits the product registration information of the product to be registered to the transaction management server 50 each time the product registration in the first stage is performed.
The transaction management server 50 collates the product code indicated in the received product registration information with the product master each time the product registration information is received. The product master of this modified example includes information indicating whether or not each product is to be sold at a sales floor for pricing.
In this case, the transaction management server 50, as a result of matching the product code with the product master, recognizes that the corresponding product is being sold at the pricing corresponding sales floor. Therefore, the transaction management server 50 transmits a pricing processing request including the received product registration information to the weighing and pricing device 10 .
At this time, when the transaction management server 50 transmits a pricing processing request in accordance with the product registration information of the first product, for example, among the plurality of weighing and pricing devices 10 installed in the sales floor, the A pricing device 10 may be selected to transmit the pricing processing request. Thereafter, the transaction management server 50 transmits pricing processing requests corresponding to the product registration information of the second and subsequent products to the weighing and pricing apparatus 10 of the same destination as the first product registration information.

Next, product registration in the second step is performed as follows.
The weighing and pricing apparatus 10 uses the product registration information included in the pricing processing request received from the mobile terminal device 40 to display a price product selection screen on the salesclerk display unit 105 .
FIG. 28A shows a mode example of a pricing product selection screen. 26 and 27, the pricing product selection screen in FIG. correspond to the state.
On the pricing product selection screen in the same figure, a pricing product button BT12-1 corresponding to apples and a pricing product button BT12-2 corresponding to cherries are arranged. In the following description, the pricing product buttons BT12-1 and BT12-2 will be referred to as the pricing product button BT12 unless otherwise distinguished.
First, when a pricing processing request corresponding to apples is first received, a pricing product selection screen on which only the pricing product button BT12-1 is arranged is displayed. A pricing product button BT12-2 is further arranged in response to the receipt of the processing request.

The pricing product button BT12 is a button for selecting a product to be subjected to pricing processing. When the pricing product buttons BT12-1 and BT-12 are arranged as in the pricing product selection screen in FIG. 1 or BT-12 can be operated first.
In this example, the sales clerk first operates the product button BT12-1 corresponding to apples, out of the price product buttons BT12-1 and BT-12. In response to the operation of the product button BT12-1, a product pricing screen corresponding to the apple product is displayed on display unit 105 for salesclerk.

FIG. 28B shows an example of a product pricing screen corresponding to apple products. A guide area AR21 and a pricing information area AR30 are arranged on the product pricing screen. The pricing information area AR30 includes a quantity area AR31, a unit price area AR32, and a price area AR33.

The guide area AR21 is an area in which the contents of guidance to the store clerk are displayed. Depending on the guide area AR21 in the figure, it is announced that the product currently being priced is apples.

The pricing information area AR30 is an area where information related to the pricing of the corresponding product is shown. Like an apple in this case, a quantity area AR31, a unit price area AR32, and a price area AR33 are arranged in the pricing information area AR30 corresponding to the fixed-price product.
The quantity area AR31 is an area in which the quantity of the product that is input by the store clerk for pricing is shown. Since the apple is a fixed-price product, the quantity area AR31 in FIG. In the quantity area AR31, the quantity specified by the customer (purchase quantity) is used as the denominator, and the quantity input according to the operation of the store clerk is displayed as the numerator.
The unit price area AR32 is an area in which the unit price of the item to be priced is indicated.
The price area AR33 is an area where a price corresponding to the current quantity of products is displayed.

By looking at the display of the product pricing screen shown in FIG. 28B, the store clerk could confirm that the apple should be priced. Also, the store clerk can understand from the display in the quantity area AR31 that the number of apples purchased is two. Therefore, the store clerk takes out two apples from the showcase and then performs an operation of inputting the number of purchases.
For example, as an operation for inputting the number of purchases, for example, the store clerk puts the products one by one on the weighing table 109a of the weighing and pricing apparatus 10 in order. The weighing and pricing device 10 counts the number of products one by one each time the weight measured by the weighing unit 109 increases step by step as the apples are placed one by one. The number of products counted in this manner is reflected as a change in the value of the numerator in the quantity area AR31. In addition, the display in the price area AR33 is also changed so that the price corresponds to the counted number of commodities.
When the store clerk confirms that the number of products counted by the weighing and pricing device 10 has reached the number of purchases by placing two apples on the weighing platform 109a, the store clerk performs a predetermined operation (value confirmation operation).

Instead of placing the products one by one on the weighing table 109a as described above, the number of products to be purchased may be input by manipulating the numbers.

In response to the pricing confirmation operation being performed, the weighing and pricing device 10 generates product pricing information (which is also product registration information in the case of this modification) reflecting the results of the fixed pricing process. Send to transaction management server 50 . The transaction management server 50 registers the received commodity pricing information in the basket information corresponding to the current transaction. In this way, the second-stage product registration for the apple product is performed.

Further, in response to the second step product registration being performed as described above, the weighing and pricing apparatus 10 of this modified example issues a single product label for the apple product. In addition, when applying this modification to 2nd Embodiment or 3rd Embodiment, it is not necessary to print code information on a single-item label.

In addition, the display of the guidance area AR21 on the product pricing screen changes as shown in FIG.
In the guidance area AR21 in the product pricing screen of FIG. 28C, a content is displayed to guide the store clerk to affix the issued single-item label to the container containing the product. The store clerk puts, for example, two apples in a container, and then sticks a single-item label on the container.
After attaching the label, the store clerk performs an operation (commodity pricing end operation) for the weighing and pricing apparatus 10 to end the pricing process corresponding to the item of one product.

In this case, among the products corresponding to the product pricing information received under the corresponding transaction, pricing processing has not yet been completed for Cherry's product. In this case, in response to the product pricing end operation corresponding to the apple, the display on the clerk display unit 105 of the weighing and pricing apparatus 10 changes to the pricing product selection screen shown in FIG. 29(A). Transition.
On the pricing product selection screen of FIG. 29A, the pricing product button BT12-1 corresponding to apples arranged in FIG. 28A is deleted, and the pricing product button BT12- corresponding to cherry 2 is placed. By viewing such a display, the store clerk can understand that the pricing operation for the apple product has been completed and the pricing operation for the cherry product has not yet been performed. In this case, the store clerk operates the pricing product button BT12-2 in order to set a price corresponding to the cherry product. In response to the operation of the pricing product button BT12-1, the salesclerk display unit 105 displays the product pricing screen corresponding to the cherry product.

FIG. 29B shows an example of a product pricing screen corresponding to cherry products. The same parts as those in FIG. 28(B) are denoted by the same reference numerals.
While apples were a fixed-price product, cherries are sold by weight. For this reason, the pricing information area AR30 on the product pricing screen corresponding to the cherry, which is sold by weight, differs from that shown in FIG. 28B corresponding to the fixed price product as follows.
In other words, in the pricing information area AR30 in the figure, the quantity area AR31 shows the measured weight of the item to be priced. Also, in the quantity area AR31 corresponding to the product sold by weight, the weight specified by the customer is used as the denominator, and the measured weight of the product is displayed as the numerator. In addition, in the unit price area AR32, the price per unit weight (weight unit price) of the item to be priced is displayed.

Further, in the pricing information area AR30 in the figure, in addition to the quantity area AR31, the unit price area AR32, and the price area AR33, a tare area AR34 and a weighing gauge area AR35 are arranged.
The tare area AR34 is an area where the weight of the tare is indicated.
The weighing gauge area AR35 is an area that displays the measured weight (measured weight) of the product in the form of a gauge. In the example shown in the figure, the scale range of the weighing gauge area AR35, for example, is based on the weight specified by the customer (specified weight), and is divided into a proper range, a range lighter than the proper range, and a range heavier than the proper range. It is divided into three ranges.

With the commodity pricing screen shown in FIG. The weighing and pricing device 10 measures the weight of the placed cherries. The weighing and pricing device 10 reflects the measured weight as the value of the numerator in the quantity area AR31. The weighing and pricing device 10 also reflects the measured weight in the weighing gauge area AR35. Also, in the price area AR33, a price corresponding to the measured weight is displayed.

The store clerk looks at the value of the numerator in the quantity area AR31 and the weighing gauge area AR35, and adjusts the quantity of cherries to be placed on the weighing platform 109a so that the measured weight falls within the appropriate range for the designated weight. When the measured weight falls within the appropriate range, the store clerk confirms with the customer whether the price corresponding to the current measured weight is acceptable, and if the customer's consent is obtained, the sales clerk confirms the price.
In response to the pricing confirmation operation being performed, the weighing and pricing device 10 sends product pricing information (which is also product registration information in the case of this modification) reflecting the results of the fixed pricing process. Send to transaction management server 50 . The transaction management server 50 registers the received commodity pricing information in the basket information corresponding to the current transaction. In this manner, the second-stage product registration for Cherry's product is performed.
In response to the second-stage product registration as described above, the weighing and pricing device 10 issues a single product label for the cherry product.

Along with the issuance of the single item label, although not shown, the display of the guide area AR21 on the item pricing screen displays the content that guides the store clerk to affix the issued single item label to the container containing the item. be. The store clerk puts the cherry placed on the weighing table 109a into a container, for example, and attaches a single item label to the container. The store clerk hands over the container containing the cherries to which the label was pasted this time and the container containing the apples to which the single item label was pasted earlier to the corresponding customer.
The store clerk performs the product pricing end operation in response to pasting the single item label this time. In this case, since there are no commodities to be subjected to pricing processing in the corresponding transaction, the weighing and pricing device 10 may shift to, for example, a standby state.

As described above, in this modification, the customer causes the mobile terminal device 40 to read the code information corresponding to the product to be purchased by the customer in the same manner as in the sales floor where the product shelves are arranged. Merchandise registration can be performed with an operation.

For example, in the case of product registration at the pricing-compatible sales floor, the portable terminal device 40 registers the product at the pricing-compatible sales floor in response to the completion of the registration of the products sold at the pricing-compatible sales floor. The customer may be required to perform an operation (registration end declaration operation) to declare that the registration operation has been completed. In this case, the portable terminal device 40 transmits the commodity pricing information of all the commodities registered corresponding to the pricing correspondence sales floor to the transaction management server 50 in response to the operation of declaring the end of registration. You can do it.
26 to 29, the product pricing information (product registration information) transmitted by the mobile terminal device 40 is received by the weighing and pricing device 10 via the transaction management server 50. is mentioned. However, for example, the product pricing information may be transmitted directly from the mobile terminal device 40 to the weight pricing device 10 without going through the transaction management server 50 .

[Seventh Modification]
Note that the label issuing device in each of the above-described embodiments is not limited to the configuration of the weighing and pricing device 10. For example, an automatic change dispenser or a drawer is provided, and the settlement corresponding to the registered product is performed. It may be configured to have a function as a POS register capable of processing. The label issuing device of this modified example can complete and execute product registration processing involving pricing of products and settlement processing according to the product registration processing. Alternatively, the label issuing device of each of the above-described embodiments may be configured as a pricing device that does not weigh the products, but counts the products and sets prices.

<Summary of embodiment>
(1) As described above, one aspect of the present embodiment includes product designation means for designating a product to be registered, and processing for communicably connecting another device (for example, the mobile terminal device 40) to its own device. and connection necessity confirmation means for confirming necessity of connection with another device if said connection means has not been connected with another device before the registration of at least one product is confirmed. is a label issuing device (eg, weighing and pricing device 10).
According to the above configuration, a label on which code information is printed is issued to, for example, customers who do not use the mobile terminal device 40 in response to product registration at the pricing counter. When issuing a label on which code information is not printed, it is possible to prevent a label on which code information is printed from being erroneously issued even though it is a response to a customer using a portable terminal device 40.例文帳に追加

(2) One aspect of the present embodiment is the label issuing device described above, and when the connection necessity confirmation means determines that the connection with the other device is unnecessary, the product to be used for product registration. and input means for inputting the product registration/use information printed by the printing means. In response, the other device performs processing for communicably connecting to its own device.
According to the above configuration, even if a label on which code information is printed is erroneously issued when dealing with a customer using the mobile terminal device 40, there is no need to re-register the corresponding product. By reading the code information on the issued label, it is possible to reissue a label on which the code information is not printed as merchandise registration using the mobile terminal device 40 .

(3) One aspect of the present embodiment is the above-described label issuing device, further comprising operator registration means for registering an operator who operates the device corresponding to one transaction, wherein the connection means At a predetermined timing until the operator is registered as an operator who operates another label issuing device corresponding to the same transaction, the connection between the own device and the other device is cut off.
According to the above configuration, the connection between the weighing and pricing device 10 and the mobile terminal device 40 can be appropriately disconnected in response to the change of the weighing and pricing device 10 operated by the store clerk when product registration is performed by taking over the product registration. It can be carried out.

(4) One aspect of the present embodiment includes a computer configured to: product designation means for designating a product to be registered; This is a program for functioning as connection necessity confirmation means for confirming necessity of connection with another device when the connection means has not been connected to the other device by the time is determined.

It should be noted that a computer-readable recording medium records a program for realizing the functions of the weighing pricing apparatus 10, the portable terminal device 40, the transaction management server 50, the weighing sales management server 60, and the like. By reading and executing the program recorded in the computer system, the processes of the weighing and pricing device 10, the mobile terminal device 40, the transaction management server 50, the weighing sales management server 60, etc. may be performed. Here, "loading and executing the program recorded on the recording medium into the computer system" includes installing the program in the computer system. The "computer system" here includes hardware such as an OS and peripheral devices. A "computer system" may also include a plurality of computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. Recording media also include internal or external recording media accessible from the distribution server for distributing the program. The program code stored in the recording medium of the distribution server may be different from the program code in a format executable by the terminal device. That is, as long as it can be downloaded from the distribution server and installed in a form that can be executed on the terminal device, the form stored in the distribution server does not matter. It should be noted that the program may be divided into a plurality of parts, and the divided programs may be downloaded at different timings and then merged in the terminal device, or the distribution servers that distribute the divided programs may be different. In addition, "computer-readable recording medium" is a volatile memory (RAM) inside a computer system that acts as a server or client when the program is transmitted via a network, and retains the program for a certain period of time. It shall also include things. Further, the program may be for realizing part of the functions described above. Further, it may be a so-called difference file (difference program) that can realize the above functions by combining with a program already recorded in the computer system.

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

Claims (5)

a product designation means for designating a product to be registered;
Weighing means for measuring the weight of the product designated as a registration target by the product designation means;
connection means for performing processing for connecting another device to its own device so as to be communicable;
a transmission means for transmitting product pricing information based on the weight weighed by the weighing means to another device connected to the own device by the connection means;
A label issuing device comprising: connection necessity confirmation means for confirming necessity of connection with another device when the connection means is not connected with the other device until registration of at least one product is confirmed. a printing means for printing product registration usage information used for product registration when the connection necessity confirmation means determines that the connection with the other device is unnecessary;
an input means for inputting the product registration usage information printed by the printing means,
2. The label issuing apparatus according to claim 1, wherein said connecting means performs processing for communicably connecting another apparatus to said own apparatus in response to said input means inputting product registration/utilization information. further comprising an operator registration means for registering an operator who operates the device corresponding to one transaction;
2. The connecting means disconnects the connection between the own device and the other device at a predetermined timing until the operator is registered as an operator who operates another label issuing device corresponding to the same transaction. Or the label issuing device according to 2. Receiving an operation on a screen for selecting either an operation for confirming that connection is necessary in response to the connection necessity confirmation means or an operation for instructing printing of product registration usage information used for product registration further comprising operation reception means
The label issuing device according to any one of claims 1 to 3. the computer,
Product designation means for designating products to be registered;
Weighing means for measuring the weight of the product designated as a registration target by the product designation means;
connection means for performing processing for connecting another device to its own device so as to be communicable;
Transmission means for transmitting product pricing information based on the weight weighed by the weighing means to another device connected to the own device by the connection means;
connection necessity confirmation means for confirming necessity of connection with another device when the connection means is not connected with the other device before the registration of at least one product is confirmed ;
A program to function as

Images