Weighing sales support device, mobile terminal, and program

Abstract

To provide a selling-by-measure support device which can reduce labor of a procedure for continuously purchasing a plurality of measured commercial products.SOLUTION: A server device (selling-by-measure support device) includes: a transaction start unit which, on the condition that a measuring device for measuring a commercial product sold by measure has acquired transaction start notice transmitted to the measuring device, establishes communication with the measuring device and starts processing concerning one transaction of the measured commercial product; a commercial product information acquisition unit which acquires commercial product information identifying the commercial product and a weight of the commercial product from the measuring device; a registration processing unit which registers the information acquired by the commercial product information acquisition unit; a registration information output unit which transmits a result of the registration by the registration processing unit to a portable terminal associated with a customer who purchases the commercial product; and a transaction completion unit which, on the condition that transaction completion notice showing completion of the processing concerning the one transaction of the measured commercial product has been outputted to the measuring device, completes the processing concerning the one transaction of the measured commercial product.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] Embodiments of the present invention relate to a weighing sales support device.

Background Art

[0002] Conventionally, a weighing device for face-to-face sales of weighed sales products (hereinafter referred to as weighing products) such as meat, whose price varies according to the weight to be purchased, is known (for example, Patent Document 1).

[0003] In such a conventional weighing device, communication between the weighing instrument and the transaction management server was established for each weighing product to be purchased. Therefore, when purchasing a plurality of weighing products continuously, it was necessary to repeat the connection and disconnection of communication between the weighing instrument and the transaction management server for each product, resulting in a problem that the transaction was troublesome.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a weighing sales support device that can reduce the labor of procedures when continuously purchasing a plurality of weighing products.

Means for Solving the Problems

[0005] The weighing sales support device according to the embodiment includes a transaction start unit, a product information acquisition unit, a registration processing unit, a registration information output unit, and a transaction end unit. The transaction start unit establishes communication with the weighing instrument on the condition that the weighing instrument for weighing the weighed product has acquired a transaction start notification transmitted to the weighing instrument, and starts processing related to one transaction of the weighed product. The product information acquisition unit acquires product information for identifying the weighed product and the weight of the weighed product from the weighing instrument. The registration processing unit registers the information acquired by the product information acquisition unit. The registration information output unit outputs the registration result by the registration processing unit to a mobile terminal associated with a customer who purchases the weighed product. The transaction end unit ends the processing related to one transaction of the weighed product on the condition that a transaction end notification indicating that the processing related to one transaction of the weighed product has been completed has been output to the weighing instrument.

Brief Description of Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8A

Figure 8B

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

[0007] (First Embodiment) An embodiment in which the present invention is applied to the measured product sales system 1 will be described with reference to the drawings.

[0008] (System Configuration of Weighed-Product Sales System) Using FIG. 1, the system configuration of the weighed-product sales system 1 will be described. FIG. 1 is a system block diagram showing an example of the system configuration of the weighed-product sales system according to the first embodiment.

[0009] The weighed-product sales system 1 is a system that performs product registration processing and settlement processing when selling weighed products. The weighed-product sales system 1 includes a server device 20, a weighing scale 40, a cash register 50, and a mobile terminal 80. Note that the weighed-product sales system 1 can perform product registration processing and settlement processing even when weighed products and products that do not require weighing (hereinafter referred to as non-weighed products) are mixed.

[0010] The server device 20 is connected to be communicable bidirectionally via a network N with a weighing scale 40 that weighs weighed products. The server device 20 instructs the weighing scale 40 to start processing related to a single transaction of the weighed product to be sold by sending a transaction start notification to the weighing scale 40. Then, the server device 20 starts processing related to the transaction of the weighed product (hereinafter referred to as weighed-product registration processing). When starting the weighed-product registration processing, the server device 20 acquires product information that identifies the weighed product and the weight of the weighed product from the weighing scale 40. Further, the server device 20 registers the product information and the weight acquired from the weighing scale 40 and transmits the registration result to the mobile terminal 80 associated with the customer who purchases the weighed product. When information on all weighed products has been acquired, the server device 20 terminates the weighed-product registration processing by sending a transaction end notification to the weighing scale 40. Note that the server device 20 is an example of the weighing sales support device in the present disclosure.

[0011] In addition, the mobile terminal 80 held by the customer receives an accounting code, which is transaction identification information associated with the product registration information, sent from the server device 20. The customer causes the accounting code to be displayed on the display unit of the mobile terminal 80 and allows the payment machine 50 to read it. The payment machine 50 acquires the product registration information corresponding to the read accounting code from the server device 20. Then, the payment machine 50 performs a settlement process using the settlement method (such as cash settlement, electronic money settlement, credit card settlement, etc.) specified by the customer. Note that the product registration information does not only register the measured products purchased by the customer, but also registers the product information of the non-measured products purchased by the same customer. In this embodiment, the settlement process is described as being performed by the payment machine 50, but the server device 20 may also perform the settlement process together.

[0012] The measuring instrument 40 identifies the measured product, measures the weight of the measured product, and calculates the purchase price. In addition, the measuring instrument 40 receives a transaction start notification from the server device 20, establishes communication with the server device 20, and starts the process related to one transaction of the measured product. Further, the measuring instrument 40 receives a transaction end notification from the server device 20 and ends the process related to one transaction of the measured product. Also, the measuring instrument 40 outputs information that uniquely identifies the measured product and the weight of the measured product to be purchased to the server device 20. Note that a code symbol Q (identification code) including identification information that uniquely identifies the measuring instrument 40 is attached to each measuring instrument 40. In addition, a plurality of measuring instruments 40 are provided, and the customer purchases the measured product using an available measuring instrument 40 (a measuring instrument 40 that has not established communication with the server device 20). Since the server device 20 is connected to the measuring instruments 40 of a plurality of stores, it is assumed that the code symbol Q also includes identification information (such as a store code, etc.) that can identify the measuring instrument 40 including the store where the measuring instrument 40 is installed.

[0013] The mobile terminal 80 is held by a customer, and at a weighing scale 40 where the customer purchases a weighed product, the mobile terminal 80 reads a code symbol Q (identification code) that uniquely identifies the weighing scale 40. The code symbol Q is, for example, a barcode or a two-dimensional code affixed to the housing of the weighing scale 40 and containing identification information that uniquely identifies the weighing scale 40. Further, the mobile terminal 80 outputs the identification information included in the read code symbol Q to the server device 20. Also, the mobile terminal 80 acquires registered product information from the server device 20. Further, the mobile terminal 80 requests the server device 20 to output an accounting code that is uniquely associated with the product registration information in which the product to be purchased is registered. Also, the mobile terminal 80 acquires the accounting code from the server device 20.

[0014] The cash register 50 acquires transaction identification information included in the accounting code by reading the accounting code displayed on the mobile terminal. Then, the cash register 50 acquires a product registration file corresponding to the transaction identification information from the server device 20. Also, the cash register 50 performs settlement processing using the settlement method instructed by the customer.

[0015] The server device 20 communicates with the weighing scale 40 and the cash register 50 via the in-store network 29 and the network N.

[0016] The mobile terminal 80 communicates with the server device 20 via an access point 60 provided in the store, the in-store network 29, and the network N.

[0017] (Hardware Configuration of Server Device) Using FIG. 2, the hardware configuration of the server device 20 will be described. FIG. 2 is a hardware block diagram showing an example of the hardware configuration of a server device included in a weighed product sales system according to the first embodiment.

[0018] The server device 20 includes a control unit 21 for controlling each part of the server device 20. The control unit 21 includes a CPU (Central Processing Unit) 22, a ROM (Read Only Memory) 23, and a RAM (Random Access Memory) 24. The CPU 22 is connected to the ROM 23 and the RAM 24 via an internal bus Ba such as an address bus and a data bus. The CPU 22 expands various programs stored in the ROM 23 and the storage unit 25 into the RAM 24. The CPU 22 controls the server device 20 by operating according to the various programs expanded in the RAM 24. That is, the control unit 21 has the configuration of a general computer.

[0019] The control unit 21 is connected to the storage unit 25, the display device 31, the operation device 32, and the communication interface 33 via the internal bus Ba.

[0020] The storage unit 25 is a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). Further, the storage unit 25 may be a non-volatile memory such as a flash memory in which stored information is retained even when the power is turned off. The storage unit 25 stores a control program Pa, a member master Ma, a product master Mb, a product registration file Md, and a meter identification information Ia.

[0021] The control program Pa is a program for controlling the overall operation of the server device 20.

[0022] The member master Ma stores the email address of the mobile terminal 80 that uniquely identifies the mobile terminal 80 of a member who has registered for use of a so-called smartphone POS that can purchase products using the mobile terminal 80, and attribute information such as the user's gender, age group, and member code registered for service improvement at the time of registration for use of the smartphone POS.

[0023] The merchandise master file Mb is a master file that stores merchandise information for weighed merchandise, i.e., merchandise code, merchandise name, unit price per gram, etc. Note that the weighed merchandise sales system 1 can perform settlement processing even when weighed merchandise and non-weighed merchandise are mixed. Therefore, the merchandise master file Mb stores merchandise information regardless of whether it is weighed merchandise or non-weighed merchandise.

[0024] The merchandise registration file Md is a file that consolidates the merchandise information registered by the server device 20 for each transaction. The merchandise registration file Md is registered regardless of whether it is weighed merchandise or non-weighed merchandise. In the case of weighed merchandise, the merchandise code, product name, gram unit price, weight, scale code used for weighing, price, etc. are registered in the merchandise registration file Md. Also, in the case of non-weighed merchandise, the merchandise code, product name, quantity, unit price, price, etc. are registered. Note that the merchandise registration file Md will be described in detail later (see Fig. 8B).

[0025] The server device 20 acquires the code information such as barcodes attached to the purchased goods (non-weighted goods) read by the customer using the mobile terminal 80. Then, the server device 20 acquires the product code included in the acquired code information. Also, the server device 20 collates the acquired product code with the product codes registered in the product master Mb, and registers the products purchased by the customer in the product registration file Md. Further, the server device 20 acquires from the weighing instrument 40 the weighed product registration file Mc (see FIG. 3) in which the weighed products purchased by the customer are registered. Then, the server device 20 updates the product registration file Md by merging the weighed product registration file Mc acquired from the weighing instrument 40 with the product registration file Md in which the purchased products of the same customer have already been registered, or by adding the information of the weighed product registration file Mc to the product registration file Md. Note that the server device 20 determines that the purchased items are related to the same customer's transaction, for example, by the identification codes assigned to the product registration file Md and the weighed product registration file Mc matching. As the identification code, for example, a transaction ID, a membership code, etc. are used. The transaction ID is an identification code issued by the server device 20 for each transaction, and includes a date, a store code, a serial number, etc. The membership code is as described above. Note that the details of the contents of the weighed product registration file Mc and the product registration file Md will be described later (see FIGS. 8A and 8B).

[0026] The weighing instrument identification information Ia is identification information assigned to each weighing instrument 40 that uniquely identifies the weighing instrument 40. The weighing instrument identification information Ia includes, for example, the manufacturing number of the weighing instrument 40. Since the server device 20 is connected to the weighing instruments 40 of a plurality of stores, the weighing instrument identification information Ia may further include a store code or the like that can uniquely identify the store where the weighing instrument 40 is installed.

[0027] The display device 31 displays the screen generated according to the instruction of the control unit 21. The display device 31 is composed of, for example, a device such as an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence).

[0028] The operation device 32 acquires the input operation of the operator and transmits it to the control unit 21. The operation device 32 is composed of devices such as a touch panel or a keyboard.

[0029] The communication interface 33 is an interface for communicating with the measuring instrument 40 and the mobile terminal 80 via wireless communication such as a wireless LAN or wired communication such as a wired LAN.

[0030] (Hardware Configuration of the Measuring Instrument) Using FIG. 3, the hardware configuration of the measuring instrument 40 will be described. FIG. 3 is a hardware block diagram showing an example of the hardware configuration of the measuring instrument included in the weighing merchandise sales system according to the first embodiment.

[0031] The measuring instrument 40 includes a control unit 41 for controlling each part. The control unit 41 includes a CPU 42, a ROM 43, and a RAM 44. The CPU 42 is connected to the ROM 43 and the RAM 44 via an internal bus Bb such as an address bus and a data bus. The CPU 42 expands various programs stored in the ROM 43 and the storage unit 45 into the RAM 44. The CPU 42 controls the measuring instrument 40 by operating according to various programs expanded in the RAM 44. That is, the control unit 41 has the configuration of a general computer.

[0032] The control unit 41 is connected to the storage unit 45, the display device 51 for store clerks, the display device 52 for customers, the operation device 53, the scanner 54, the weight sensor 55, and the communication interface 56 via the internal bus Bb.

[0033] The storage unit 45 is a storage device such as an HDD or an SSD. Further, the storage unit 45 may be a non-volatile memory such as a flash memory that retains stored information even when the power is turned off. The storage unit 45 stores a control program Pb, a product master Mb, a weighed product registration file Mc, and weighing instrument identification information Ib.

[0034] The control program Pb is a program for controlling the overall operation of the measuring instrument 40.

[0035] The product master Mb is a master file that stores product information of measured products. Since the content of the product master Mb is updated at any time, the measuring instrument 40 acquires the latest product master Mb from, for example, the server device 20.

[0036] The measured product registration file Mc is a file that stores product information measured by the measuring instrument 40. Details of the measured product registration file Mc will be described later (see FIG. 8A).

[0037] The measuring instrument identification information Ib is identification information that uniquely identifies the measuring instrument 40.

[0038] The clerk display device 51 displays, for the clerk, a screen generated according to an instruction from the control unit 41. The clerk display device 51 is composed of, for example, a device such as an LCD or an organic EL.

[0039] The customer display device 52 displays, for the customer, a screen generated according to an instruction from the control unit 41. The customer display device 52 is composed of, for example, a device such as an LCD or an organic EL.

[0040] The operation device 53 acquires an input operation of an operator and transmits it to the control unit 41. The operation device 53 is composed of, for example, a device such as a keyboard or a touch panel. Note that the operation device 53 may be provided on both the clerk side and the customer side.

[0041] When registering a measured product purchased by a customer, the scanner 54 reads an identification code (for example, a barcode) corresponding to the product specified by the customer.

[0042] The weight sensor 55 measures the weight of the measured product. The weight sensor 55 is, for example, a load cell.

[0043] The communication interface 56 is an interface for communicating with the server device 20 via wireless communication such as a wireless LAN or wired communication such as a wired LAN.

[0044] (Hardware Configuration of Mobile Terminal) Using FIG. 4, the hardware configuration of the mobile terminal 80 will be described. FIG. 4 is a hardware block diagram showing an example of the hardware configuration of the mobile terminal included in the metered product sales system according to the first embodiment.

[0045] The mobile terminal 80 includes a control unit 81 for controlling each part. The control unit 81 includes a CPU 82, a ROM 83, and a RAM 84. The CPU 82 is connected to the ROM 83 and the RAM 84 via an internal bus Bc such as an address bus and a data bus. The CPU 82 expands various programs stored in the ROM 83 and the storage unit 85 into the RAM 84. The CPU 82 controls the mobile terminal 80 by operating according to various programs expanded in the RAM 84. That is, the control unit 81 has the configuration of a general computer.

[0046] The control unit 81 is connected to the storage unit 85, the display device 91, the operation device 92, the camera 93, and the communication interface 94 via the internal bus Bc.

[0047] The storage unit 85 is a storage device such as an HDD or an SSD. Further, the storage unit 85 may be a non-volatile memory such as a flash memory in which stored information is retained even when the power is turned off. The storage unit 85 stores a control program Pc, member information Me, and product registration information Eb.

[0048] The control program Pc is a program for controlling the overall operation of the mobile terminal 80.

[0049] The member information Me is a file storing registration information such as an email address registered when registering for the use of the smartphone POS and a member code issued at the time of registration.

[0050] The display device 91 displays a screen generated according to an instruction from the control unit 81. The display device 91 is composed of a device such as an LCD or an organic EL, for example.

[0051] The operation device 92 acquires the input operations of the operator and transmits them to the control unit 81. The operation device 92 is composed of devices such as a touch panel and a keyboard, for example.

[0052] The camera 93 is built into the mobile terminal 80 and images, for example, the code symbol Q attached to the measuring instrument 40.

[0053] The communication interface 94 is an interface for communicating with the server device 20 via wireless communication such as a wireless LAN.

[0054] Note that the cash register 50 has, for example, the same computer structure as the server device 20. Further, the cash register 50 includes a card reader that reads the customer's credit card when performing credit card settlement and reads the customer's electronic money card when performing electronic money settlement. Further, the cash register 50 includes a camera or a scanner that reads the accounting code displayed on the display device 91 of the mobile terminal 80 by the customer. Further, the cash register 50 includes a receipt printer that outputs the result of the settlement.

[0055] (Functional Configuration of Server Device) The functional configuration of the server device 20 will be described with reference to FIG. 5. FIG. 5 is a functional block diagram showing an example of the functional configuration of the server device included in the weighing commodity sales system according to the first embodiment.

[0056] The control unit 21 of the server device 20 realizes, as functional units, the identification information acquisition unit 9, the member information acquisition unit 10, the transaction start unit 11, the commodity information acquisition unit 12, the registration processing unit 13, the registration information output unit 14, the accounting code generation unit 15, the transaction end unit 16, and the accounting code output unit 17 shown in FIG. 5 by expanding and operating the control program Pa in the RAM 24.

[0057] The identification information acquisition unit 9 acquires, from the mobile terminal 80, the identification information that uniquely identifies the measuring instrument 40 that measures the commodity to be sold by weight.

[0058] The member information acquisition unit 10 acquires the member code of the user necessary for using the smartphone POS from the mobile terminal 80.

[0059] The transaction start unit 11 instructs the weighing instrument 40 having the identification information acquired by the identification information acquisition unit 9 to start a transaction. More specifically, the transaction start unit 11 outputs a transaction start notification to the weighing instrument 40 having the identification information acquired by the identification information acquisition unit 9. Then, on the condition that the weighing instrument 40 has acquired the transaction start notification, the process related to one transaction of the weighed merchandise is started between the weighing instrument 40 and the server device 20 (hereinafter, also referred to as the establishment of communication). Also, when communication is established between the server device 20 and the weighing instrument 40, if the identification information of the same weighing instrument 40 is acquired from another mobile terminal, the transaction start unit 11 transmits information indicating that connection is unavailable to the other mobile terminal.

[0060] The merchandise information acquisition unit 12 acquires merchandise information for identifying the merchandise to be sold by weight and the weight of the merchandise from the weighing instrument 40 for which communication has been established.

[0061] The registration processing unit 13 performs a registration process for registering the information acquired by the merchandise information acquisition unit 12. More specifically, when the registration processing unit 13 reads code information such as a barcode attached to a non-weighed merchandise by the customer using the mobile terminal 80, the registration processing unit 13 acquires the merchandise code registered in the read code information. Then, the registration processing unit 13 registers the merchandise information corresponding to the acquired merchandise code in the merchandise registration file Md. Also, the registration processing unit 13 acquires the weighed merchandise registration file Mc corresponding to the weighed merchandise purchased by the customer possessing the mobile terminal 80 from the weighing instrument 40, and registers the contents of the weighed merchandise registration file Mc in the merchandise registration file Md by merging, or registers the information of the weighed merchandise registration file Mc in the merchandise registration file Md by adding it, thereby registering the merchandise. Note that the fact that the merchandise is the weighed merchandise purchased by the customer possessing the mobile terminal 80 is identified by identification information such as the member code of the user possessing the mobile terminal 80 and the transaction ID output by the server device 20 to the weighing instrument 40 when communication is established between the server device 20 and the weighing instrument 40.

[0062] The registration information output unit 14 outputs the product registration information for which the registration processing unit 13 has performed the registration processing to the customer's mobile terminal 80.

[0063] The accounting code generation unit 15 generates an accounting code that uniquely corresponds to the product registration file Md for which product registration has been completed in response to a request from the customer's mobile terminal 80.

[0064] The transaction end unit 16 instructs the weighing instrument 40 to end the weighed product registration process. More specifically, the transaction end unit 16 ends the weighed product registration process on the condition that a transaction end notification has been output to the weighing instrument 40 that is performing the weighed product registration process as one transaction.

[0065] The accounting code output unit 17 outputs the accounting code generated by the accounting code generation unit 15 to the customer's mobile terminal 80.

[0066] (Functional configuration of the weighing instrument) The functional configuration of the weighing instrument 40 will be described with reference to FIG. 6. FIG. 6 is a functional block diagram showing an example of the functional configuration of the weighing instrument included in the weighed product sales system according to the first embodiment.

[0067] The control unit 41 of the weighing instrument 40 realizes, by expanding and operating the control program Pb in the RAM 44, the transaction start unit 61, the weighed product identification unit 62, the weight measurement unit 63, the weighed product information registration unit 64, the weighed product information output unit 65, the transaction end unit 66, the display control unit 67, and the operation control unit 68 shown in FIG. 6 as functional units.

[0068] The transaction start unit 61 receives a transaction start notification from the server device 20 and establishes communication with the server device 20.

[0069] The weighed product identification unit 62 uniquely identifies the weighed product to be purchased by the customer. Specifically, the product is identified by reading an identification code such as a barcode for identifying the product to be purchased by the customer with the scanner 54.

[0070] The weight measurement unit 63 measures the weight of the weighed products purchased by customers.

[0071] The weighed product information registration unit 64 generates a weighed product registration file Mc in which the product information of the weighed products purchased by customers, the purchased weight, the purchase price, and the information uniquely identifying the weighing instrument 40 used for weighing are registered.

[0072] The weighed product information output unit 65 outputs the content of the weighed product registration file Mc to the server device 20 with which communication has been established.

[0073] Upon receiving the transaction completion notification from the server device 20, the transaction completion unit 66 terminates the weighed product registration process as one transaction.

[0074] The display control unit 67 generates a display screen to be displayed on the clerk display device 51 or the customer display device 52 of the weighing instrument 40. Further, the display control unit 67 outputs the generated display screen to the clerk display device 51 or the customer display device 52.

[0075] The operation control unit 68 acquires the operation information made on the operation device 53 of the weighing instrument 40 and passes it to the control unit 41. The control unit 41 causes the weighing instrument 40 to perform control according to the acquired operation information.

[0076] (Functional configuration of the mobile terminal) The functional configuration of the mobile terminal 80 will be described with reference to FIG. 7. FIG. 7 is a functional block diagram showing an example of the functional configuration of the mobile terminal included in the weighed product sales system according to the first embodiment.

[0077] The control unit 81 of the mobile terminal 80 realizes, by expanding and operating the control program Pc in the RAM 84, the identification information acquisition unit 71, the identification information output unit 72, the member information output unit 73, the registration information acquisition unit 74, the accounting code request unit 75, the accounting code acquisition unit 76, the display control unit 77, and the operation control unit 78 shown in FIG. 7 as functional units.

[0078] The identification information acquisition unit 71 acquires identification information that uniquely identifies the measuring instrument 40 from the measuring instrument 40. Specifically, the identification information acquisition unit 71 images the code symbol Q (see FIG. 1) affixed to the measuring instrument 40 with the camera 93 (see FIG. 4) provided in the mobile terminal 80, and acquires the identification information that uniquely identifies the measuring instrument 40 from the imaged code symbol Q.

[0079] The identification information output unit 72 outputs the identification information that uniquely identifies the measuring instrument 40, which is acquired by the identification information acquisition unit 71, to the server device 20.

[0080] The member information output unit 73 outputs the identification information that uniquely identifies the mobile terminal 80, which is necessary when using the smartphone POS. The identification information may be, for example, the email address of the mobile terminal 80, or may be an identification code or the like issued when registering the application of the smartphone POS.

[0081] The registration information acquisition unit 74 acquires product registration information from the server device 20.

[0082] The accounting code request unit 75 requests the server device 20 to output an accounting code.

[0083] The accounting code acquisition unit 76 acquires an accounting code from the server device 20.

[0084] The display control unit 77 generates a display screen to be displayed on the display device 91 of the mobile terminal 80. Further, the display control unit 77 outputs the generated display screen to the display device 91.

[0085] The operation control unit 78 acquires operation information made on the operation device 92 of the mobile terminal 80 and passes it to the control unit 81. The control unit 81 causes the mobile terminal 80 to perform control according to the acquired operation information.

[0086] Note that the payment machine 50 reads the accounting code displayed on the display device 91 by the mobile terminal 80. Further, the payment machine 50 transmits the read accounting code to the server device 20, and acquires the product registration information corresponding to the accounting code from the server device 20. Further, the payment machine 50 performs a settlement process on the acquired product registration information in a method designated by the customer. In the present embodiment, in order to focus on the method for realizing the reduction of the labor of the procedure when purchasing a weighed product, which is a feature of the present disclosure, the description of the functional configuration of the payment machine 50 is omitted.

[0087] (Configuration of Weighed Product Registration File) Using FIG. 8A, the configuration of the weighed product registration file Mc generated by the weighing instrument 40 will be described. FIG. 8A is a diagram showing an example of the configuration of the weighed product registration file generated by the weighing instrument.

[0088] The weighed product registration file Mc includes, as header information, a weighing instrument code 34 and a member code 30. Further, the weighed product registration file Mc includes, as registration information, a product code 35, a product name 36, a gram unit price 37, a weight 38, and a price 39.

[0089] The weighing instrument code 34 is identification information that uniquely identifies the weighing instrument 40. The weighing instrument code 34 may include, for example, the manufacturing number of the weighing instrument 40. Further, the weighing instrument code may include information that uniquely identifies the store where the weighing instrument 40 is installed. Note that the weighing instrument code 34 is stored in the storage unit 45 of the weighing instrument 40 as weighing instrument identification information Ib (see FIG. 3).

[0090] The member code 30 is identification information that is uniquely associated with the mobile terminal 80 that has registered for using the smartphone POS. The weighing instrument 40 acquires, for example, the member code 30 of the user who holds the mobile terminal 80 from the server device 20 when acquiring a transaction start notification from the server device 20 or when starting the weighed product registration process.

[0091] The product code 35 is identification information that uniquely identifies the product sold by weight by the weighing instrument 40.

[0092] Product name 36 is the product name corresponding to product code 35.

[0093] Gram unit price 37 is the unit price per gram of the product corresponding to product code 35.

[0094] Weight 38 is the weight of the product corresponding to product code 35 measured by the measuring instrument 40.

[0095] Price 39 is the integrated value of gram unit price 37 and weight 38.

[0096] (Configuration of Product Registration File) Using FIG. 8B, the configuration of the product registration file Md generated by the server device 20 will be described. FIG. 8B is a diagram showing an example of the configuration of the product registration file generated by the server device.

[0097] The product registration file Md includes, as header information, member code 30, transaction ID 18, date 19, and store code 27. Further, the product registration file Md includes, as registration information, item number 57, product code 35, product name 36, quantity 58, unit price 59, gram unit price 37, mass 38, measuring instrument code 34, and price 39.

[0098] Member code 30 is as described above.

[0099] Transaction ID 18 is identification information assigned by the server device 20 to uniquely identify the generated product transaction.

[0100] Date 19 is the date and time when the product registration file Md was created. Date 19 is given the time acquired from the CPU 22 when the product registration file Md is created or updated by the server device 20.

[0101] Store code 27 is identification information that uniquely identifies the store where the product transaction related to the product registration file Md was conducted.

[0102] Item number 57 is a sequential number assigned to each product, and the sequential number is assigned in the order of product registration. In the example of FIG. 8B, the products with item numbers "3" and "4" are weighed products, and the products with item numbers "1" and "2" are non - weighed products. For weighed products, the product code 35, product name 36, gram unit price 37, mass 38, and price 39, as described in the weighed product registration file Mc (FIG. 8A), are stored respectively. Also, for weighed products, the weighing instrument code 34 is stored.

[0103] On the other hand, for non - weighed products, the product code 35, product name 36, quantity 58, unit price 59, and price 39 are stored.

[0104] Note that whether the product registration file Md and the weighed product registration file Mc belong to the same transaction is determined by the header information of each file. In the cases of FIGS. 8A and 8B, it can be determined that they belong to the same transaction because the member code 30 is equal. Note that the server device 20 may send the transaction ID 18 to the weighing instrument 40, register the transaction ID 18 in the header information of the weighed product registration file Mc, and determine that the product registration file Md and the weighed product registration file Mc belong to the same transaction based on the transaction ID 18. In this case, the server device 20 acquires the identification information that uniquely identifies the weighing instrument 40 for weighing the products sold by weight from the portable terminal 80, and acquires the transaction ID that identifies the transaction in which the product registration is performed by the user via the portable terminal 80, and sends a transaction start notification to the weighing instrument 40 and also sends the transaction ID.

[0105] Also, one transaction performed by the weighing instrument 40 is started by the transaction start notification sent from the server device 20 and continues until the transaction ends. Therefore, the weighed product registration file Mc acquired by the server device 20 from the weighing instrument 40 may be merged or added to the product registration file Md associated with the member code (transaction ID) received by the server device 20 from the portable terminal 80.

[0106] (Flow of processing performed by the weighed product sales system) Using FIG. 9, the flow of processing performed by the weighed product sales system 1 will be described. FIG. 9 is a flowchart showing an example of the flow of processing performed by the weighed product sales system according to the first embodiment.

[0107] For the sake of simplicity of explanation, here, the flow of processing from when the registration process of the weighed product to be purchased by the customer is performed until the mobile terminal 80 held by the customer acquires accounting data from the server device 20 will be described. And regarding the subsequent settlement processing flow, it will be described only in text. Also, in the flowchart of FIG. 9, it is assumed that the server device 20 has already completed the registration process of non-weighed products.

[0108] (Flow of processing performed by the weighing scale) The transaction start unit 61 determines whether it has acquired a transaction start notification from the server device 20 (step S11). If it is determined that a transaction start notification has been acquired from the server device 20 (step S11: Yes), the process proceeds to step S12. On the other hand, if it is determined that a transaction start notification has not been acquired from the server device 20 (step S11: No), step S11 is repeated.

[0109] In step S11, when it is determined that a transaction start notification has been acquired from the server device 20, the transaction start unit 61 establishes communication with the server device 20 (step S12). Note that when the weighing scale 40 establishes communication with the server device 20, it receives identification information such as a member code 30 that can uniquely identify the transaction from the server device 20.

[0110] The weighed product identification unit 62 identifies the weighed product (step S13).

[0111] The weight measurement unit 63 weighs the product (step S14).

[0112] The weighed product information registration unit 64 generates a weighed product registration file Mc (step S15).

[0113] The operation control unit 68 determines whether information indicating the completion of the transaction of the weighed commodity has been input by the store clerk (step S16). If it is determined that the information indicating the completion of the transaction of the weighed commodity has been input (step S16: Yes), the process proceeds to step S17. On the other hand, if it is determined that the information indicating the completion of the transaction of the weighed commodity has not been input (step S16: No), the process returns to step S13 and repeats the registration of the next weighed commodity.

[0114] In step S16, if it is determined that the information indicating the completion of the transaction of the weighed commodity has been input, the weighed commodity information output unit 65 outputs the weighed commodity registration file Mc to the server device 20 (step S17).

[0115] The transaction completion unit 66 determines whether a transaction completion notification has been acquired from the server device 20 (step S18). If it is determined that the transaction completion notification has been acquired (step S18: Yes), the process proceeds to step S19. On the other hand, if it is determined that the transaction completion notification has not been acquired (step S18: No), step S18 is repeated.

[0116] In step S18, if it is determined that the transaction completion notification has been acquired, the transaction completion unit 66 ends the weighed commodity registration process. Thereby, the transaction established with the server device 20 is ended (step S19). After that, the weighing instrument 40 ends the process of FIG. 9.

[0117] (Flow of processing performed by the mobile terminal) The identification information acquisition unit 71 acquires the identification information of the weighing instrument 40 by decoding the code symbol Q of the weighing instrument 40 imaged by the camera 93 (step S21).

[0118] The identification information output unit 72 outputs the identification information of the weighing instrument 40 acquired by the identification information acquisition unit 71 to the server device 20. Further, the member information output unit 73 outputs the member information Me to the server device 20 (step S22).

[0119] The registration information acquisition unit 74 acquires the commodity registration information from the server device 20 (step S23).

[0120] The accounting code request unit 75 requests the server device 20 to output an accounting code (step S24).

[0121] The accounting code acquisition unit 76 acquires an accounting code from the server device 20 (step S25). Then, the mobile terminal 80 ends the process of FIG. 9.

[0122] Although not shown in the flowchart of FIG. 9, thereafter, the customer goes to the cash register 50. Then, the cash register 50 reads the accounting code displayed on the display device 91 of the mobile terminal 80. The cash register 50 acquires the product registration file Md corresponding to the read accounting code from the server device 20. Then, the cash register 50 performs a settlement process by the settlement method (cash settlement, electronic money settlement, credit card settlement, etc.) specified by the customer. After the settlement process is completed, the cash register 50 issues a receipt indicating the result of the settlement process. In addition, the cash register 50 outputs information indicating that the settlement corresponding to the acquired accounting code has been completed to the server device 20. The server device 20 acquires the information indicating that the settlement process has been completed and sets the product registration file Md corresponding to the accounting code as settled.

[0123] (Flow of processing performed by the server device) Next, the flow of processing performed by the server device 20 will be described. It is assumed that non-measured products have already been registered in the product registration file Md stored in the storage unit 25 of the server device 20. The registration of non-measured products is performed, for example, as follows. First, the camera 93 of the mobile terminal 80 held by the customer captures code information such as a barcode to which a product code is registered, which is attached to the non-measured product to be purchased, and decodes the captured code information to obtain the product code. Then, the mobile terminal 80 outputs the obtained product code and the member information Me of the customer who holds the mobile terminal 80 to the server device 20. The server device 20 acquires the product code and the member information Me and performs product registration by registering the acquired information in the product registration file Md.

[0124] The identification information acquisition unit 9 of the server device 20 acquires the identification information of the measuring instrument 40 from the mobile terminal 80. Further, the member information acquisition unit 10 acquires, for example, member information Me from the mobile terminal 80 (step S31).

[0125] The transaction start unit 11 outputs a transaction start notification to the measuring instrument 40 corresponding to the identification information acquired in step S31 (step S32). Although not explicitly shown in FIG. 9, when the server device 20 establishes communication with the measuring instrument 40, the server device 20 transmits identification information such as a member code 30 that can uniquely identify the transaction to the measuring instrument 40.

[0126] The identification information acquisition unit 9 determines whether it has acquired the identification information of the same measuring instrument 40 as the measuring instrument 40 with which communication is currently established (step S33). If it is determined that the identification information of the same measuring instrument 40 as the measuring instrument 40 with which communication is currently established has been acquired (step S33: Yes), the process proceeds to step S34. On the other hand, if it is determined that the identification information of the same measuring instrument 40 as the measuring instrument 40 with which communication is currently established has not been acquired (step S33: No), the process proceeds to step S35.

[0127] In step S33, if it is determined that the identification information of the same measuring instrument 40 as the measuring instrument 40 with which communication is currently established has been acquired, the transaction start unit 11 notifies the mobile terminal 80 that acquired the identification information in step S33 that connection is impossible (step S34).

[0128] The commodity information acquisition unit 12 determines whether it has acquired the measured commodity registration file Mc from the measuring instrument 40 (step S35). If it is determined that the measured commodity registration file Mc has been acquired from the measuring instrument 40 (step S35: Yes), the process proceeds to step S36. On the other hand, if it is determined that the measured commodity registration file Mc has not been acquired from the measuring instrument 40 (step S35: No), the process returns to step S33.

[0129] In step S35, if it is determined that the measured commodity registration file Mc has been acquired from the measuring instrument 40, the transaction end unit 16 outputs a transaction end notification to the measuring instrument 40 (step S36).

[0130] The registration processing unit 13 performs product registration processing by merging or adding the registration contents of the measured product registration file Mc obtained from the measuring instrument 40 into the product registration file Md already stored in the server device 20 (step S37).

[0131] As described above, in this flowchart, the case where the registration of measured products is performed after the registration of non-measured products is explained, but the purchase order of measured products and non-measured products does not matter. When a measured product is purchased, the measured product registration file Mc generated by the measuring instrument 40 is output to the server device 20. The server device 20 performs the registration processing of the measured product by merging or adding the contents of the obtained measured product registration file Mc into the product registration file Md. On the other hand, when a non-measured product is purchased, for each product purchase, the customer reads the code information of the product with the mobile terminal 80. The mobile terminal 80 transmits the read code information or the product code obtained by decoding the code information to the server device 20. The server device 20 performs the registration processing of the non-measured product by identifying the purchased product based on the code information or the product code obtained from the mobile terminal 80 and registering the identified product information in the product registration file Md.

[0132] The registration information output unit 14 outputs product registration information to the customer's mobile terminal 80 (step S38). Here, the reason for outputting the product registration information is to notify the customer that the product registration has been completed and to have the customer confirm the content. Since it is desirable to perform this confirmation operation each time a product is registered, the product registration information output in step S38 is, for example, only the registration information related to the measured product registered last. Of course, the confirmation of the product registration information may be performed collectively after all shopping is completed.

[0133] The accounting code generation unit 15 determines whether there is a request to output an accounting code from the mobile terminal 80 (step S39). If it is determined that there is a request to output an accounting code (step S39: Yes), the process proceeds to step S40. On the other hand, if it is determined that there is no request to output an accounting code (step S39: No), step S39 is repeated.

[0134] In step S39, when it is determined that there is a request to output an accounting code, the accounting code generation unit 15 generates an accounting code (step S40).

[0135] The accounting code output unit outputs the accounting code to the mobile terminal 80 (step S41). Thereafter, the server device 20 ends the process of FIG. 9.

[0136] As described above, the server device 20 (retail sales support device) of the first embodiment establishes communication with the weighing instrument 40 on the condition that the weighing instrument 40 that weighs the merchandise to be retailed has acquired a transaction start notification transmitted to the weighing instrument 40, and starts the process related to one transaction of the weighed merchandise. A transaction start unit 11, a merchandise information acquisition unit 12 that acquires merchandise information for identifying the merchandise and the weight of the merchandise from the weighing instrument 40, a registration processing unit 13 that registers the information acquired by the merchandise information acquisition unit 12, and a registration result by the registration processing unit 13 are transmitted to the mobile terminal 80 associated with the customer who purchases the merchandise (registration information output unit), and on the condition that a transaction end notification indicating that the process related to one transaction of the weighed merchandise has been completed is output to the weighing instrument 40, a transaction end unit 16 that ends the process related to one transaction of the weighed merchandise. Therefore, when continuously purchasing a plurality of weighed merchandise, it is only necessary to establish communication between the weighing instrument 40 and the server device 20 once, and there is no need to read the code symbol Q for identifying the weighing instrument 40 for each merchandise as in the prior art. Also, the customer does not need to read the barcode of each weighed merchandise with the mobile terminal 80. As a result, the labor of the procedure when continuously purchasing a plurality of weighed merchandise can be reduced.

[0137] Further, the server device 20 (retail sales support device) of the first embodiment further includes an identification information acquisition unit 9 that acquires identification information uniquely identifying a weighing instrument 40 that weighs merchandise to be retailed. The transaction start unit 11 establishes communication with the weighing instrument 40 specified by the identification information acquired by the identification information acquisition unit 9 from the mobile terminal 80. Therefore, the server device 20 can acquire the identification information of the weighing instrument 40 via the customer's mobile terminal 80. This can enhance the compatibility with a so-called smartphone POS system that conducts transaction settlement by communicating between the mobile terminal 80 and the transaction management server.

[0138] Also, in the server device 20 (retail sales support device) of the first embodiment, when communication is established between the server device 20 (retail sales support device) and the weighing instrument 40, and when a request for establishing communication is received from another mobile terminal 80, the transaction start unit 11 transmits information indicating that communication cannot be established to the other mobile terminal 80. Therefore, even when another customer transmits the identification information of the weighing instrument 40 acquired by their own mobile terminal 80 to the server device 20 when the server device 20 and the weighing instrument 40 have already established communication, it will not affect the already established communication. Also, it is possible to notify another customer that communication cannot be established because communication has already been established.

[0139] (Modification Example of the First Embodiment) Next, a modification example of the weighed merchandise sales system 1 of the first embodiment will be described with reference to FIG. 10. FIG. 10 is a flowchart showing an example of the processing flow performed by the weighed merchandise sales system according to the modification example of the first embodiment.

[0140] In the weighing product sales system which is a modification of the first embodiment, when the weighing scale 40 registers a weighing product, every time a weighing product is registered as a single item, the weighing product registration file Mc of the weighing product is transmitted to the server device 20. Specifically, when the first weighing product is registered by the weighing scale 40, the information of the weighing product is immediately output to the server device 20. Then, in the server device 20, it is registered in the customer's product registration file Md. And when the second weighing product is registered by the weighing scale 40, the information of the weighing product is immediately output to the server device 20. Then, in the server device 20, it is registered in the customer's product registration file Md. After the customer first reads the code symbol Q of the weighing scale 40 with the mobile terminal 80, the customer can conduct a transaction for the weighing product without operating the mobile terminal 80 just by instructing the store clerk about the desired weighing product.

[0141] Note that since the weighing product sales system of the modification of the first embodiment has the same hardware configuration as the weighing product sales system 1, the names and symbols used in the first embodiment are used as they are.

[0142] Also, the functional configurations and the contents of the functions of the server device 20, the cash register 50, and the mobile terminal 80 are the same as those described in the first embodiment.

[0143] In addition to the functions described in the first embodiment, the transaction end unit 66 provided in the weighing scale 40 further has a function of outputting transaction end information indicating that the processing related to a single transaction of the weighing product has ended to the server device 20 when the transaction of the weighing product is completed. Note that the weighing scale 40 detects that the transaction of the weighing product is completed when a store clerk who has asked the customer to end the transaction presses a transaction end button (not shown) displayed on the store clerk display device 51 of the weighing scale 40.

[0144] In the weighing merchandise sales system according to the first embodiment, every time a weighed merchandise is registered by the weighing scale 40, the server device 20 acquires a weighed merchandise registration file Mc in which the weighed merchandise is registered. Then, the server device 20 performs a merchandise registration process of merging or adding the registered contents of the acquired weighed merchandise registration file Mc to the merchandise registration file Md. At this time, as described in the first embodiment, the server device 20 determines that the weighed merchandise registration file Mc and the merchandise registration file Md are information related to the transactions of the same customer based on the fact that the identification information (such as the email address of the mobile terminal 80 or the identification code issued when registering the application of the smartphone POS) that uniquely identifies the mobile terminal 80 registered in the header information of the weighed merchandise registration file Mc and the header information of the merchandise registration file Md is equal.

[0145] Note that in addition to the functions described in the first embodiment, the transaction end unit 16 provided in the server device 20 has a function of acquiring, from the weighing scale 40, transaction end information indicating that the process related to one transaction of the weighed merchandise has ended.

[0146] After the server device 20 acquires the transaction end information from the weighing scale 40, the mobile terminal 80 acquires merchandise registration information from the server device 20. The merchandise registration information includes the total number of registered items and the purchase amount. The mobile terminal 80 displays the acquired merchandise registration information and the registration completion key on the display device 91 of the mobile terminal 80. The customer checks the merchandise registration information displayed on the display device 91. Then, if there is no problem with the registered contents, the customer presses the registration completion key displayed on the display device 91. The mobile terminal 80 detects that the registration completion key has been pressed and requests the server device 20 to issue an accounting code. After that, the mobile terminal 80 acquires the accounting code issued by the server device 20.

[0147] After that, the customer causes the payment machine 50 to read the accounting code and performs a settlement process. The method of the settlement process is as described in the first embodiment.

[0148] Hereinafter, with reference to FIG. 10, the flow of the process performed by the weighing merchandise sales system will be described.

[0149] (Flow of processing performed by the measuring device) The flow of processing (steps S131, S132) from when the transaction start section 61 of the measuring device 40 acquires a transaction start notification from the server device 20 until communication with the server device 20 is established is the same as the processing of steps S11 and S12 described in FIG. 9.

[0150] Subsequent to step S132, the measured product identification section 62 identifies the measured product (step S133).

[0151] The weighing section 63 weighs the product (step S134).

[0152] The measured product information registration section 64 generates a measured product registration file Mc (step S135).

[0153] The measured product information output section 65 outputs the measured product registration file Mc to the server device 20 (step S136).

[0154] The operation control section 68 determines whether information indicating the end of the transaction of the measured product has been input by the store clerk (step S137). If it is determined that information indicating the end of the transaction has been input (step S137: Yes), the process proceeds to step S138. On the other hand, if it is not determined that information indicating the end of the transaction has been input (step S137: No), the process returns to step S133 and the registration of the next measured product is repeated.

[0155] In step S137, when it is determined that information indicating the end of the transaction of the measured product has been input, the transaction end section 66 outputs transaction end information indicating that the processing related to one transaction of the measured product has ended to the server device 20 (step S138).

[0156] The transaction end section 66 determines whether it has acquired a transaction end notification from the server device 20 (step S139). If it is determined that the transaction end notification has been acquired (step S139: Yes), the process proceeds to step S140. On the other hand, if it is determined that the transaction end notification has not been acquired (step S139: No), step S139 is repeated.

[0157] In step S139, when it is determined that the transaction end notification has been acquired, the transaction end section 66 ends the metered commodity registration process. Thereby, the transaction established with the server device 20 is ended (step S140). Thereafter, the meter 40 ends the process of FIG. 10.

[0158] (Flow of processing performed by the mobile terminal) The identification information acquisition section 71 acquires the identification information of the meter 40 by decoding the code symbol Q of the meter 40 imaged by the camera 93 (step S151).

[0159] The identification information output section 72 outputs the identification information of the meter 40 acquired by the identification information acquisition section 71 to the server device 20. Also, the member information output section 73 outputs the member information Me to the server device 20 (step S152).

[0160] Note that the member information Me output here is added to the commodity registration file Md generated by the server device 20 as described above. Also, the member information Me is further output from the server device 20 to the meter 40 and added to the metered commodity registration file Mc generated by the meter 40. Thereby, it is confirmed that the metered commodity registration file Mc output to the server device 20 each time a metered commodity is registered from the meter 40 and the commodity registration file Md held by the server device 20 belong to the same transaction, and the metered commodity registration file Mc is merged or added to the commodity registration file Md.

[0161] The registration information acquisition section 74 acquires commodity registration information from the server device 20 (step S153).

[0162] The display control unit 77 displays on the display device 91 the product registration information acquired in step S153 and the registration completion key for notifying the server device 20 that the product registration has been completed (step S154).

[0163] The operation control unit 78 detects whether the registration completion key has been pressed (step S155). If it is determined that the registration completion key has been pressed (step S155: Yes), the process proceeds to step S156. On the other hand, if it is determined that the registration completion key has not been pressed (step S155: No), step S155 is repeated.

[0164] In step S155, when it is determined that the registration completion key has been pressed, the accounting code request unit 75 requests the server device 20 to output an accounting code (step S156).

[0165] The accounting code acquisition unit 76 acquires the accounting code from the server device 20 (step S157). Thereafter, the mobile terminal 80 ends the process of FIG. 10. As a further modification example of the process of FIG. 10, the mobile terminal 80 may use the request for the accounting code output in step S156 instead of the output of the transaction end information of the metered product output by the meter 40 in step S138. In this case, the server device 20 outputs a transaction end notification to the meter 40 on the condition that it has acquired the transaction end information from the mobile terminal 80. Then, the meter 40 ends the process related to one transaction of the metered product on the condition that it has acquired the transaction end notification from the server device 20.

[0166] (Flow of processing performed by the server device) The identification information acquisition unit 9 acquires the identification information of the meter 40 from the mobile terminal 80. Also, the member information acquisition unit 10 acquires, for example, the member information Me from the mobile terminal 80 (step S161).

[0167] The transaction start unit 11 outputs a transaction start notification to the meter 40 corresponding to the identification information acquired in step S31 (step S162).

[0168] The identification information acquisition unit 9 determines whether it has acquired the identification information of the same measuring instrument 40 as the measuring instrument 40 for which the current communication has been established (step S163). If it is determined that the identification information of the same measuring instrument 40 as the measuring instrument 40 for which the current communication has been established has been acquired (step S163: Yes), the process proceeds to step S164. On the other hand, if it is not determined that the identification information of the same measuring instrument 40 as the measuring instrument 40 for which the current communication has been established has been acquired (step S163: No), the process proceeds to step S165.

[0169] In step S163, if it is determined that the identification information of the same measuring instrument 40 as the measuring instrument 40 for which the current communication has been established has been acquired, the transaction start unit 11 notifies the mobile terminal 80 that acquired the identification information in step S163 that connection is not possible (step S164).

[0170] The commodity information acquisition unit 12 determines whether it has acquired the measured commodity registration file Mc from the measuring instrument 40 (step S165). If it is determined that the measured commodity registration file Mc has been acquired from the measuring instrument 40 (step S165: Yes), the process proceeds to step S166. On the other hand, if it is not determined that the measured commodity registration file Mc has been acquired from the measuring instrument 40 (step S165: No), the process returns to step S163.

[0171] In step S165, if it is determined that the measured commodity registration file Mc has been acquired from the measuring instrument 40, the registration processing unit 13 performs commodity registration processing by merging or adding the registration contents of the measured commodity registration file Mc acquired from the measuring instrument 40 to the commodity registration file Md already stored in the server device 20 (step S166).

[0172] The transaction end unit 16 determines whether it has acquired transaction end information from the measuring instrument 40 (step S167). If it is determined that the transaction end information has been acquired from the measuring instrument 40 (step S167: Yes), the process proceeds to step S168. On the other hand, if it is not determined that the transaction end information has been acquired from the measuring instrument 40 (step S167: No), the process returns to step S163.

[0173] In step S167, when it is determined that transaction end information has been acquired from the weighing scale 40, the transaction end unit 16 outputs a transaction end notification to the weighing scale 40 (step S168).

[0174] The registration information output unit 14 outputs product registration information to the customer's mobile terminal 80 (step S169).

[0175] The accounting code generation unit 15 determines whether there is a request to output an accounting code from the mobile terminal 80 (step S170). If it is determined that there is a request to output an accounting code (step S170: Yes), the process proceeds to step S171. On the other hand, if it is determined that there is no request to output an accounting code (step S170: No), step S170 is repeated.

[0176] In step S170, when it is determined that there is a request to output an accounting code, the accounting code generation unit 15 generates an accounting code (step S171).

[0177] The accounting code output unit outputs an accounting code to the mobile terminal 80 (step S172). Thereafter, the server device 20 ends the process of FIG. 10.

[0178] (Second Embodiment) An embodiment in which the present invention is applied to the weighed product sales system 2 will be described with reference to the drawings.

[0179] (System Configuration of the Weighed Product Sales System) The system configuration of the weighed product sales system 2 will be described with reference to FIG. 11. FIG. 11 is a system block diagram showing an example of the system configuration of the weighed product sales system according to the second embodiment.

[0180] The weighed product sales system 2 is a system that performs product registration processing and settlement processing when selling weighed products such as meat whose price varies according to the purchased weight. The weighed product sales system 2 includes a server device 20, a weighing scale 46, a cash register 50, and a mobile terminal 80.

[0181] The server device 20, the cash register 50, and the mobile terminal 80 have the same hardware configuration and functional configuration as the server device 20, the cash register 50, and the mobile terminal 80 included in the metered product sales system 1 described in the first embodiment. In the following description, the hardware components and functional components of the server device 20, the cash register 50, and the mobile terminal 80 will be described using the same names and reference numerals as those used in the description of the first embodiment.

[0182] The weighing device 46 is provided with a function of outputting a code symbol Q (code information) including identification information that uniquely identifies the weighing device 46, in addition to the weighing device 40 described in the first embodiment. The output code symbol Q is displayed on the customer display device 52 connected to the weighing device 46. Since the weighing device 46 has the same hardware configuration as the weighing device 40, in the following description, the hardware components of the weighing device 46 will be described using the same names and reference numerals as the hardware components of the weighing device 40.

[0183] The server device 20 communicates with the weighing device 46 and the cash register 50 via the in-store network 29 and the network N.

[0184] The mobile terminal 80 communicates with the server device 20 via the access point 60 provided in the store, the in-store network 29, and the network N.

[0185] (Functional configuration of the weighing device) The functional configuration of the weighing device 46 will be described with reference to FIG. 12. FIG. 12 is a functional block diagram showing an example of the functional configuration of the weighing device included in the metered product sales system according to the second embodiment.

[0186] The control unit 41 of the weighing device 46 realizes, by expanding and operating the control program Pb in the RAM 44, a transaction start unit 61, a metered product identification unit 62, a weight measurement unit 63, a metered product information registration unit 64, a metered product information output unit 65, a transaction end unit 66, a display control unit 67, an operation control unit 68, and an identification information display unit 69 shown in FIG. 12 as functional units.

[0187] The functions of the transaction start section 61, the weighed product identification section 62, the weighing section 63, the weighed product information registration section 64, the weighed product information output section 65, the transaction end section 66, the display control section 67, and the operation control section 68 are as described in the first embodiment.

[0188] The identification information display section 69 generates screen information indicating a code symbol Q including identification information that uniquely identifies the weighing instrument 46. Further, the identification information display section 69 causes the display control section 67 to display the generated screen information on the customer display device 52 (see FIG. 3). Further, upon receiving an instruction to erase the screen information indicating the code symbol Q, the identification information display section 69 causes the display control section 67 to erase the screen information.

[0189] The flow of processing performed by the weighed product sales system 2 will be described with reference to FIG. 13. FIG. 13 is a flowchart showing an example of the flow of processing performed by the weighed product sales system according to the second embodiment.

[0190] (Flow of processing performed by the weighing instrument) The identification information display section 69 generates screen information indicating a code symbol Q including identification information that uniquely identifies the weighing instrument 46, and causes the display control section 67 to display the generated screen information on the customer display device 52 (see FIG. 3) (step S51).

[0191] The identification information display section 69 determines whether an instruction to erase the code symbol Q has been given by the store clerk (step S52). If it is determined that an instruction to erase the code symbol Q has been given by the store clerk (step S52: Yes), the process proceeds to step S53. On the other hand, if it is determined that an instruction to erase the code symbol Q has not been given by the store clerk (step S52: No), step S52 is repeated. Note that when the store clerk confirms that the customer has photographed the code symbol Q displayed on the customer display device 52 with the camera 93 of the portable terminal 80, the store clerk operates the operation device 53 to instruct the weighing instrument 46 to erase the code symbol Q.

[0192] In step S52, when it is determined that an instruction to erase the code symbol Q has been given by the store clerk, the identification information display unit 69 causes the display control unit 67 to erase the code symbol Q displayed on the customer display device 52.

[0193] Hereinafter, the flow of the process performed in steps S54 to S62 is the same as the flow of the process performed by the weighing instrument 40 described in the first embodiment (the flow of the process performed in steps S11 to S19 in FIG. 9), and thus the description thereof is omitted.

[0194] (Flow of processing performed by the mobile terminal) The flow of the process performed by the mobile terminal 80 is the same as the flow of the process performed by the mobile terminal 80 described in the first embodiment (the flow of the process performed in steps S21 to S25 in FIG. 9), and thus the description thereof is omitted.

[0195] (Flow of processing performed by the server device) The flow of the process performed by the server device 20 is substantially the same as the flow of the process performed by the server device 20 described in the first embodiment, and thus the description thereof is omitted.

[0196] What is different from the process performed by the server device 20 in the first embodiment is that the processes corresponding to steps S33 and S34 in FIG. 9 are not required. That is, in the weighing commodity sales system 2 of the present embodiment, the code symbol Q including the identification information uniquely identifying the weighing instrument 46 is displayed on the customer display device 52 only when instructed by the identification information display unit 69 of the weighing instrument 46. Then, after the customer photographs the code symbol Q with the mobile terminal 80, the code symbol Q is erased.

[0197] Therefore, since a plurality of customers do not read the code symbol Q, there is no request to establish communication between the weighing instrument 46 and the server device 20 from customers other than those conducting transactions. Therefore, the server device 20 of the present embodiment does not need to perform the processes corresponding to steps S33 and S34 in FIG. 9.

[0198] (Operational effects of the second embodiment) As described above, in the server device 20 (retail sales support device) of the second embodiment, the weighing scale 46 that has established communication with the server device 20 receives a display instruction and displays a code symbol Q (code information) including identification information that uniquely identifies the weighing scale 46 to a customer who purchases a product to be sold by weight. The weighing scale 46 also includes an identification information display unit 69 that receives an erasure instruction and erases the code symbol Q. Therefore, since the code information necessary for establishing communication between the server device 20 and the weighing scale 46 is displayed only while the customer reads the code symbol Q, it is possible to prevent a plurality of customers from simultaneously requesting the server device 20 to establish communication with the same weighing scale 46.

[0199] (Third Embodiment) An embodiment in which the present invention is applied to a weighed product sales system 3 will be described with reference to the drawings.

[0200] (System Configuration of Weighed Product Sales System) The system configuration of the weighed product sales system 2 will be described with reference to FIG. 14. FIG. 14 is a system block diagram showing an example of the system configuration of the weighed product sales system according to the third embodiment.

[0201] The weighed product sales system 3 is a system that performs product registration processing and settlement processing when selling weighed products such as meat whose price varies according to the purchased weight. The weighed product sales system 3 includes a server device 26, a weighing scale 47, a cash register 50, and a mobile terminal 86.

[0202] The server device 26, the weighing scale 47, the cash register 50, and the mobile terminal 86 have the same hardware configurations as the server device 20, the weighing scale 40, the cash register 50, and the mobile terminal 80 included in the weighed product sales system 1 described in the first embodiment. In the following description, the hardware components of the server device 26, the weighing scale 47, the cash register 50, and the mobile terminal 86 will be described using the same names and reference numerals as those used in the description of the first embodiment.

[0203] The server device 26 acquires, from the customer's mobile terminal 86, information declaring the purchase of a weighed commodity and the current position of the mobile terminal 86. Further, the server device 26 searches for a weighing instrument 47 that is near the current position of the mobile terminal 86 and is currently available, and sends a transaction start notification to the searched weighing instrument 47, thereby instructing the start of processing related to a single transaction of the weighed commodity for the weighing instrument 47. Then, the server device 26 starts the weighed commodity registration process. The functions exerted by the server device 26 when performing the weighed commodity registration process and after the completion of the weighed commodity registration process are the same as those of the server device 20 described in the first embodiment, and thus the description thereof is omitted. Note that the server device 26 is an example of the weighing sales support device in the present disclosure.

[0204] The weighing instrument 47 identifies the weighed commodity, measures the weight of the weighed commodity, and calculates the purchase price. Further, the weighing instrument 47 establishes communication with the server device 26 upon receiving a transaction start notification from the server device 26. Further, the weighing instrument 47 ends the processing related to a single transaction of the weighed commodity on the condition that it has acquired a transaction end notification from the server device 26 indicating that the processing related to a single transaction of the weighed commodity has been completed. Further, the weighing instrument 47 outputs to the server device 26 information uniquely identifying the weighed commodity, the weight of the weighed commodity to be purchased.

[0205] The mobile terminal 86 is held by the customer, and upon receiving the operation of the customer, outputs to the server device 26 information indicating the intention to purchase a weighed commodity and the current position of the mobile terminal 86. Further, the mobile terminal 86 acquires registered commodity information from the server device 26. Further, the mobile terminal 86 requests the server device 26 to output an accounting code uniquely associated with the commodity registration information in which the commodity to be purchased is registered. Further, the mobile terminal 80 acquires the accounting code from the server device 26.

[0206] Note that the server device 26 communicates with the weighing instrument 47 and the cash register 50 via the in-store network 29 and the network N.

[0207] Further, the mobile terminal 86 communicates with the server device 26 via the access point 60 provided in the store, the in-store network 29, and the network N.

[0208] (Functional Configuration of Server Device) The functional configuration of the server device 26 will be described with reference to FIG. 15. FIG. 15 is a functional block diagram showing an example of the functional configuration of the server device included in the metered product sales system according to the third embodiment.

[0209] By expanding and operating the control program Pa in the RAM 24, the control unit 21 of the server device 26 realizes, as functional units, a metered product purchase declaration acquisition unit 87, a member information acquisition unit 10, a mobile terminal position acquisition unit 88, a weighing instrument search unit 89, a transaction start unit 11, a weighing instrument information output unit 90, a product information acquisition unit 12, a registration processing unit 13, a registration information output unit 14, an accounting code generation unit 15, a transaction end unit 16, and an accounting code output unit 17 shown in FIG. 15.

[0210] Among these, the member information acquisition unit 10, the transaction start unit 11, the product information acquisition unit 12, the registration processing unit 13, the registration information output unit 14, the accounting code generation unit 15, the transaction end unit 16, and the accounting code output unit 17 are as described in the first embodiment, and thus the repeated description will be omitted.

[0211] The metered product purchase declaration acquisition unit 87 acquires information declaring the purchase of a metered product from the mobile terminal 86. Note that the metered product purchase declaration acquisition unit 87 is an example of the acquisition unit in the present disclosure.

[0212] The mobile terminal position acquisition unit 88 acquires the current position of the mobile terminal 86 that has output information declaring the purchase of a metered product from the mobile terminal 86. Note that the mobile terminal position acquisition unit 88 is an example of the acquisition unit in the present disclosure.

[0213] The weighing scale search unit 89 searches for a weighing scale 47 that is near the current position of the mobile terminal 86 which has output information declaring the purchase of a weighed product and is in a weighable state, that is, a weighing scale 47 that has not established communication with the server device 26.

[0214] The weighing scale information output unit 90 outputs information indicating the position of the weighing scale 47 that has established communication with the server device 26 to the mobile terminal 86. The information indicating the position of the weighing scale 47 is output, for example, in the form of map information indicating the position of the weighing scale 47 in the store. Note that the weighing scale information output unit 90 is an example of the output unit in the present disclosure. Also, the information indicating the position of the weighing scale 47 is registered in advance in the weighing scale identification information Ia stored in the server device 26.

[0215] (Function configuration of the mobile terminal) The functional configuration of the mobile terminal 86 will be described with reference to FIG. 16. FIG. 16 is a functional block diagram showing an example of the functional configuration of the mobile terminal included in the weighed product sales system according to the third embodiment.

[0216] The control unit 81 of the mobile terminal 86 realizes, by expanding and operating the control program Pc in the RAM 84, a weighed product purchase declaration output unit 95, a member information output unit 73, a registration information acquisition unit 74, an accounting code request unit 75, a current position information output unit 96, a weighing scale information acquisition unit 97, a weighing scale information display unit 98, an accounting code acquisition unit 76, a display control unit 77, and an operation control unit 78 as functional units.

[0217] Among these, the member information output unit 73, the registration information acquisition unit 74, the accounting code request unit 75, the accounting code acquisition unit 76, the display control unit 77, and the operation control unit 78 are as described in the first embodiment, and thus repeated description will be omitted.

[0218] The metered product purchase declaration output unit 95 acquires a customer's declaration to declare the purchase of a metered product. Specifically, it is assumed that the purchase of a metered product is declared by detecting that, for example, a metered product purchase button displayed on the display device 91 is pressed. Further, the metered product purchase declaration output unit 95 outputs information indicating the declaration of the purchase of a metered product to the server device 26.

[0219] The current position information output unit 96 outputs the current position of the mobile terminal 86 to the server device 26. Note that the mobile terminal 86 is provided with a GPS receiver (not shown in FIG. 4), and the mobile terminal 86 identifies its own current position by analyzing the GPS signal received by the GPS receiver.

[0220] The weighing instrument information acquisition unit 97 acquires, from the server device 26, information indicating the position of the weighing instrument 47 with which the server device 26 has established communication.

[0221] The weighing instrument information display unit 98 displays, on the display device 91, the information indicating the position of the weighing instrument 47 acquired by the weighing instrument information acquisition unit 97.

[0222] (Flow of processing performed by the metered product sales system) Using FIG. 17, the flow of processing performed by the metered product sales system 3 will be described. FIG. 17 is a flowchart showing an example of the flow of processing performed by the metered product sales system according to the third embodiment.

[0223] (Flow of processing performed by the weighing instrument) The flow of processing performed by the weighing instrument 47 (from step S101 to step S109) is the same as the flow of processing performed by the weighing instrument 40 in the first embodiment (steps S11 to S19 in FIG. 9), and thus the description thereof will be omitted.

[0224] (Flow of processing performed by the mobile terminal) The metered product purchase declaration output unit 95 of the mobile terminal 86 acquires a customer's declaration to declare the purchase of a metered product (step S111). Specifically, the metered product purchase declaration output unit 95 determines that a customer who declares the purchase of a metered product has declared the purchase of the metered product by detecting that the customer has pressed, for example, a metered product purchase button displayed on the display device 91 of the mobile terminal 86.

[0225] The metered product purchase declaration output unit 95 outputs information indicating the declaration of the purchase of a metered product to the server device 26. Also, the member information output unit 73 outputs the member information Me to the server device 26. Further, the current position information output unit 96 outputs the current position of the mobile terminal 86 to the server device 26 (step S112).

[0226] The weighing instrument information acquisition unit 97 acquires information indicating the position of the weighing instrument 47 with which the server device 26 has established communication from the server device 26 (step S113).

[0227] The weighing instrument information display unit 98 displays the information indicating the position of the weighing instrument 47 acquired by the weighing instrument information acquisition unit 97 on the display device 91 (step S114). Note that the customer who holds the mobile terminal 86 checks the information indicating the position of the weighing instrument 47 displayed on the display device 91, goes to the designated weighing instrument 47, and purchases the metered product.

[0228] The registration information acquisition unit 74 acquires product registration information from the server device 26 (step S115).

[0229] The accounting code request unit 75 requests the server device 26 to output an accounting code (step S116).

[0230] The accounting code acquisition unit 76 acquires an accounting code from the server device 26 (step S117). Thereafter, the mobile terminal 80 ends the process of FIG. 17. Although not described in the flowchart of FIG. 17, thereafter, as described in the first embodiment, the customer performs a settlement process at the cash register 50.

[0231] (Flow of processing performed by the server device) The metered product purchase declaration acquisition unit 87 of the server device 26 acquires a declaration indicating the purchase of a metered product from the mobile terminal 86. Also, the member information acquisition unit 10 acquires member information Me from the mobile terminal 86. Further, the mobile terminal position acquisition unit 88 acquires the current position of the mobile terminal 86 from the mobile terminal 86 (step S121).

[0232] When the metering device search unit 89 acquires information declaring the purchase of a metered product, it searches for a metering device 47 that is in the vicinity of the mobile terminal 86 and has not established communication with the server device 26, that is, an unconnected metering device (step S122).

[0233] The metering device search unit 89 determines whether there is a metering device 47 in the vicinity of the mobile terminal 86 that has not established communication (step S123). If it is determined that there is a metering device 47 in the vicinity of the mobile terminal 86 that has not established communication (step S123: Yes), the process proceeds to step S124. On the other hand, if it is determined that there is no metering device 47 in the vicinity of the mobile terminal 86 that has not established communication (step S123: No), step S123 is repeated.

[0234] In step S123, if it is determined that there is a metering device 47 in the vicinity of the mobile terminal 86 that has not established communication, the transaction start unit 11 outputs a transaction start notification to the metering device 47 (step S124).

[0235] Hereinafter, the flow of processing performed from step S125 to step S132 is the same as the processing performed by the server device 20 from step S35 to step S42 in the first embodiment (see FIG. 9), and thus the description is omitted.

[0236] (Operational effects of the third embodiment) As described above, the server device 26 (retail sales support device) of the third embodiment includes a weighed product purchase declaration acquisition unit 87 (acquisition unit) that acquires information declaring the purchase of a weighed product from the customer's mobile terminal 86, and when the weighed product purchase declaration acquisition unit 87 acquires information declaring the purchase of a weighed product to be sold by weight, it searches for a weighing instrument 47 that is near the current position of the mobile terminal 86 and is in a weighable state, that is, a state where communication has not been established, and when the weighing instrument 47 has acquired the transaction start notification transmitted to the searched weighing instrument 47, it establishes communication with the weighing instrument 47 and starts the processing related to one transaction of the weighed product. A transaction start unit 11, a weighing instrument information output unit 90 (output unit) that transmits information indicating the position of the weighing instrument 47 with which communication has been established to the mobile terminal 86, a product information acquisition unit 12 that acquires product information identifying the weighed product and the weight of the weighed product from the weighing instrument 47, a registration processing unit 13 that registers the information acquired by the product information acquisition unit 12, and a registration information output unit that outputs the registration result by the registration processing unit 13 to the mobile terminal 86 associated with the customer who purchases the weighed product. And a transaction end unit 16 that ends the processing related to one transaction of the weighed product on the condition that a transaction end notification indicating that the processing related to one transaction of the weighed product has been completed is output to the weighing instrument 47. Therefore, since the customer does not need to read the code symbol Q including the identification information that uniquely identifies the weighing instrument 47, the trouble in the case of continuously purchasing a plurality of weighed products is further reduced.

[0237] As described above, the embodiments of the present invention have been described. However, these embodiments are examples and are not intended to limit the scope of the invention. This novel embodiment can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalent scope thereof.

Explanation of Reference Numerals

[0238] 1, 2, 3 Weighed product sales system 9, 71 Identification information acquisition unit 10 Member information acquisition unit 11,61 Transaction start section 12 Commodity information acquisition section 13 Registration processing section 14 Registered information output section 15 Accounting code generation section 16,66 Transaction end section 17 Accounting code output section 20,26 Server device (weight-selling support device) 40,46,47 Weighing scale 50 Cash register 62 Weighed commodity identification section 63 Weight measurement section 64 Weighed commodity information registration section 65 Weighed commodity information output section 67,77 Display control section 68,78 Operation control section 72 Identification information output section 73 Member information output section 74 Registered information acquisition section 75 Accounting code request section 76 Accounting code acquisition section 80,86 Mobile terminal 87 Weighed commodity purchase declaration acquisition section (acquisition section) 88 Mobile terminal position acquisition section 89 Weighing scale search section 90 Weighing scale information output section (output section) 95 Weighed commodity purchase declaration output section 96 Current position information output section 97 Weighing scale information acquisition section 98 Weighing scale information display section Mc Weighed commodity registration file Md Commodity registration file Q Code symbol

Prior art documents

Patent documents

[0239]

Patent Document 1

Claims

1. For a weighing instrument that weighs weighed merchandise, from the time a transaction start notification is output until a transaction end notification is output to the weighing instrument, a merchandise information acquisition unit that acquires merchandise information identifying the weighed merchandise and the weight of the weighed merchandise from the weighing instrument; A merchandise information output unit that outputs the merchandise information and the weight to a mobile terminal associated with a customer who purchases the weighed merchandise, A weighed merchandise sales support device.

2. Transmitting the transaction start notification and the transaction end notification to a weighing instrument corresponding to identification information that uniquely identifies the weighing instrument acquired from the mobile terminal. The weighed merchandise sales support device according to Claim 1.

3. When communication is established between the weighed merchandise sales support device and the weighing instrument, when a connection request for communication is received from another mobile terminal, transmitting information indicating that connection is not possible to the other mobile terminal. The weighed merchandise sales support device according to Claim 1 or Claim 2.

4. The weighing instrument Comprises an identification information display unit that causes a display device provided therein to display the identification information or to erase the identification information. The weighed merchandise sales support device according to Claim 2.

5. An acquisition unit that acquires the current position of a mobile terminal of a customer who has declared the purchase of weighed merchandise; An output unit that searches for a weighable weighing instrument near the current position of the mobile terminal and transmits information indicating the position of the searched weighing instrument to the mobile terminal, The weighed merchandise sales support device according to Claim 1.

6. A mobile terminal associated with a customer who purchases the weighed merchandise using a weighing instrument that weighs the weighed merchandise, An identification information acquisition unit that reads identification information that uniquely identifies the weighing instrument; An identification information output unit that outputs the identification information and the customer's membership information to a server device; An accounting code acquisition unit that acquires an accounting code associated with registration information including merchandise information identifying the weighed merchandise and the weight of the weighed merchandise from the server device, A mobile terminal.

7. Further comprising a registration information acquisition unit that acquires the registration information from the server device. The mobile terminal according to Claim 6.

8. A mobile terminal associated with a customer who purchases the weighed merchandise using a weighing instrument that weighs the weighed merchandise, An identification information acquisition unit that reads identification information that uniquely identifies the weighing instrument An identification information output unit that outputs the identification information and the customer's membership information to a server device; An accounting code acquisition unit that operates to acquire, from the server device, an accounting code associated with registration information including product information for specifying the weighed product and the weight of the weighed product; A program.

Images