Product sales data processing system

The product sales data processing system uses a mobile terminal with reading failure detection and display mechanisms to enhance the accuracy of fraudulent activity determination during product registration, reducing false positives and improving system integrity.

JP7580744B2Active Publication Date: 2024-11-12TERAOKA SEIKO CO LTD

Patent Information

Application Number
JP2020152041
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-09-10
Publication Date
2024-11-12
Estimated Expiration
2040-09-10

AI Technical Summary

Technical Problem

Existing systems struggle to accurately determine fraudulent product registration acts by customers using mobile terminals, often misclassifying legitimate registrations as fraudulent.

Method used

A product sales data processing system that includes a mobile terminal with a reading means, detection means for reading failures, and display means to inform customers of reading failures, along with invalidation control to prevent fraudulent registrations.

Benefits of technology

Enhances the accuracy of determining fraudulent activities during product registration by identifying and addressing reading failures, thereby reducing false positives and improving system integrity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007580744000001
    Figure 0007580744000001
  • Figure 0007580744000002
    Figure 0007580744000002
  • Figure 0007580744000003
    Figure 0007580744000003
Patent Text Reader

Abstract

To enable misconduct to be appropriately assessed in accordance with a customer's situation in commodity registration.SOLUTION: A commodity sales data processing system for registering commodities by a portable terminal operated by store customers is constituted by: read means for reading codes; detection means for detecting a read failure state indicating that a commodity whose commodity code among the codes has not been read by the read means is secured by a customer; display means for displaying information that pertains to the read failure state detected by the detection means; and disable means for exercising disable control that causes the detection of read failure states corresponding to the occurrence of the read failure state to be disabled, on the basis of the timing at which a prescribed code is read by the read means.SELECTED DRAWING: Figure 21
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a product sales data processing system. [Background technology]

[0002] 2. Description of the Related Art A system is known in which a customer registers an item by himself / herself using a mobile terminal equipped with a camera (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-147252 A Summary of the Invention [Problem to be solved by the invention]

[0004] In a system in which customers themselves register products using mobile terminals as described above, it is preferable to be able to detect fraudulent behavior by customers when registering products. However, depending on the circumstances of product registration, there are cases in which a customer's registration is determined to be fraudulent even though the customer has performed the registration work in accordance with the proper procedures.

[0005] The present invention has been made in consideration of the above circumstances, and has an object to enable appropriate fraudulent activity determination to be made depending on the customer's circumstances during product registration. [Means for solving the problem]

[0006] One aspect of the present invention that solves the above-mentioned problems is a product sales data processing system that registers products using a mobile terminal operated by a customer in a store, the product sales data processing system comprising: a reading means for reading a code; a detection means for detecting the occurrence of a read failure situation in which a customer secures a product whose product code has not been read by the reading means; a display means for displaying information regarding the read failure situation detected by the detection means; and an invalidation means for performing invalidation control that results in the detection of the read failure situation in response to the occurrence of the read failure situation being invalidated based on the timing at which a specified code is read by the reading means. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram showing an example of the configuration of a sales system according to a first embodiment and an example of how a mobile terminal device is set in a shopping cart. [Diagram 2] FIG. 1 is a diagram illustrating an example of the configuration of a weighing pricing device according to a first embodiment. [Diagram 3] 1 is a perspective view showing an example of the appearance of a weighing and pricing device according to a first embodiment. FIG. [Figure 4] 1 is a diagram showing an example of the appearance of a settlement device according to a first embodiment; [Diagram 5] 1 is a diagram illustrating an example of the configuration of a settlement device according to a first embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a mobile terminal device according to the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of a transaction management server according to the first embodiment. [Figure 8] 3A to 3C are diagrams illustrating an example of customer information, store information, and cart information according to the first embodiment. [Figure 9] FIG. 2 is a diagram showing an example of a definition of a reserved product according to the first embodiment. [Figure 10] A sequence diagram showing an example of processing procedures executed by the mobile terminal device, settlement device, and transaction management server in the first embodiment in response to a transaction in self-service operation. [Figure 11]FIG. 2 is a diagram showing an example of a screen of a shopping application in the first embodiment. [Figure 12] 4A to 4C are diagrams showing an example of a registered product presentation screen and a screen displayed on a settlement device in the first embodiment. [Figure 13] 11 is a flowchart showing an example of a processing procedure executed by the mobile terminal and the transaction management device according to the first embodiment in relation to product registration, including processing for dealing with a reading failure situation. [Figure 14] FIG. 2 is a diagram showing an example of how products sold by weight are displayed in a store according to the first embodiment. [Figure 15] 1 is a diagram showing an example of the external appearance of a weighing and pricing device according to a first embodiment, as viewed from the front. FIG. [Figure 16] 5A to 5C are diagrams illustrating a procedure for reading a connection information code according to the first embodiment and an example of a pricing operation screen. [Figure 17] 1A to 1C are diagrams illustrating an example of a procedure that a customer follows in response to a price determination for one product according to the first embodiment. [Figure 18] 1A to 1C are diagrams illustrating an example of a procedure that a customer follows in response to a price determination for one product according to the first embodiment. [Figure 19] 13A to 13C are diagrams showing examples of a pricing operation screen and a product registration screen according to the first embodiment. [Figure 20] 4 is a flowchart showing an example of a processing procedure executed by the weighing pricing device, the mobile terminal device, and the transaction management server according to the first embodiment in relation to the registration of products sold by weight in one transaction. [Figure 21] FIG. 4 is a diagram illustrating an example of setting an invalidation period according to the first embodiment. [Figure 22] 10 is a flowchart showing an example of a processing procedure executed by the mobile terminal device according to the first embodiment in relation to setting an invalidation period. [Figure 23] 10 is a flowchart illustrating an example of a processing procedure executed by the mobile terminal device according to the first embodiment in response to detection of the occurrence of a reading failure state. [Figure 24]13 is a flowchart illustrating an example of a processing procedure in which the mobile terminal device according to the first embodiment invalidates detection of an occurrence of a reading failure state before a time that is a reference time for the invalidation period. [Diagram 25] FIG. 11 is a diagram showing an example of a pricing operation screen according to the second embodiment. [Figure 26] FIG. 11 is a diagram showing an example of a weighing result screen according to the second embodiment. [Figure 27] FIG. 11 is a diagram illustrating an example of setting an invalidation period according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] First Embodiment 1A shows an example of the configuration of a sales system according to this embodiment. The sales system in this figure includes weighing and pricing devices 10 (10-1, 10-2, 10-3), settlement devices 20 (20-1, 20-2), a management device 30, a mobile terminal device 40, and a transaction management server 50. In the sales system of this embodiment, a customer registers an item using a mobile terminal device 40 and also operates a payment device 20 to make a payment.

[0009] The weighing pricing device 10 calculates the price of each product based on the weight measured for the product placed on the weighing platform and the unit price by weight, and generates product pricing information for the product including the calculated price. The product pricing information is transmitted to a mobile terminal device 40 communicably connected to the weighing pricing device 10.

[0010] The settlement device 20 uses the cart information (settlement information) acquired from the transaction management server 50 to execute settlement processing in response to the customer's operation.

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

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

[0013] The mobile terminal device 40 has a network communication function, for example, a short-range wireless communication function using Bluetooth (registered trademark) or the like. The mobile terminal device 40 also has a camera (imaging unit). By being equipped with a camera, the mobile terminal device 40 has a code scanning function that reads codes such as barcodes and two-dimensional codes.

[0014] The mobile terminal device 40 may be owned by the store and lent to the customer when shopping. Although one mobile terminal device 40 is shown in the figure, the number of mobile terminal devices 40 used for product registration in the store varies depending on the number of customers.

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

[0016] The mobile terminal device 40 of this embodiment is used in a state where it is attached to a shopping cart prepared in a store when registering a product. Figures 1(B) and 1(C) show examples of how to attach a mobile terminal device 40 to a shopping cart. Figure 1(B) is a side view of the shopping cart where the mobile terminal device 40 is set. Figure 1(C) is a top view of the shopping cart.

[0017] 1(B) shows a portion of holder 71 attached to a shopping cart. A customer places mobile terminal device 40 in holder 71. Mobile terminal device 40 placed in holder 71 is in a state where it can capture an image of the entire inside of shopping cart 80 with a camera (imaging unit), as shown in FIG. 1(C).

[0018] An example of the configuration of the weighing pricing device 10 in this embodiment will be described with reference to Fig. 2 and Fig. 3. Fig. 2 is a block diagram showing an example of the hardware configuration of the weighing pricing device 10. Fig. 3 is a diagram showing an example of the appearance of the weighing pricing device 10, showing an example of the appearance of the weighing pricing device 10 as viewed from the front.

[0019] 2, the weighing and pricing device 10 includes a CPU (Central Processing Unit) 101, a ROM 102, a RAM 103, a scanner unit 104, a customer display unit 106, a hard disk 107, a weighing unit 109, a printing unit 110, an inter-device communication unit 111, and a short-range communication unit 112. These are connected to each other via a bus 119.

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

[0021] The scanner unit 104 optically reads the coded information.

[0022] 3, the customer display unit 106 is disposed on the front side facing the customer side and displays information for the customer. Note that the customer display unit 106 may be configured as a touch panel so that it can be operated by the customer.

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

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

[0025] The printing unit 110 prints on paper media and issues (outputs) the labels from a label outlet 110a (FIG. 3). For example, the printing unit 110 can issue labels to be attached to products.

[0026] The inter-device communication unit 111 is provided to correspond to a case where communication is performed with another weighing-pricing device 10 via a predetermined communication network. The communication network that the inter-device communication unit 111 corresponds to may be a wired or wireless network. The inter-device communication unit 111 may be capable of communicating with the management device 30. The short-range communication unit 112 communicates with the mobile terminal device 40 by a predetermined short-range wireless communication method. The short-range wireless communication method supported by the short-range communication unit 112 may be, for example, Bluetooth.

[0027] 4 is a perspective view showing an example of the exterior of the settlement device 20. The settlement device 20 in the figure includes a scanner unit 204, a customer display unit 206, a change machine 260, and an issuing port 210a.

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

[0029] Information related to payment is displayed to customers on the customer display unit 206. The customer display unit 206 may be configured as a display device equipped with a touch panel.

[0030] The change machine 260 is an automatic change machine that accepts currency (banknotes and coins) inserted by customers, performs a deposit process, and gives change, refunds, or ejects rejected currency. The change machine 260 comprises a banknote management section 261, a coin insertion port 264, a coin ejection port 265, and a rejection port 266. The coin insertion port 264, the coin ejection port 265, and the rejection port 266 are included in the coin management section. The banknote management section 261 comprises a banknote insertion port 262 and a banknote ejection port 263. The banknote insertion port 262 is an opening that takes in banknotes inserted by customers. The banknote ejection port 263 is an opening that ejects banknotes and rejected banknotes. The banknote insertion port 262 and the banknote ejection port 263 are configured in two stages. For example, in the banknote management unit 261, the upper stage is a banknote input port 262 and the lower stage is a banknote output port 263.

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

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

[0033] 5 is a block diagram showing an example of the configuration of settlement device 20. Settlement device 20 includes a CPU 201, a ROM 202, a RAM 203, a scanner unit 204, a customer display unit 206, a hard disk 207, a printer unit 210, an inter-device communication unit 211, and a change dispenser 260. These are connected to each other via a bus 219. Note that inter-device communication unit 211 may be omitted in this embodiment, since it is a part that is provided for communication with a store clerk identification tag in the third embodiment described later.

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

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

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

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

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

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

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

[0041] The touch panel display unit 406 is a display unit combined with a touch panel. An operation unit 407 collectively indicates keys and the like used for operations other than the touch panel display unit 406 .

[0042] Imaging unit 408 captures an image. Mobile terminal device 40 has a code scan function that utilizes imaging unit 408. That is, when mobile terminal device 40 recognizes that a code is included in a captured image captured by imaging unit 408, it acquires the code from the captured image as the code scan function.

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

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

[0045] An example of the configuration of the transaction management server 50 of this embodiment will be described with reference to Fig. 7. The transaction management server 50 in Fig. 7 includes a CPU 501, a storage unit 502, a RAM 503, and a communication unit 504.

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

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

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

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

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

[0051] The transaction management server 50 stores, for example, store information as shown in FIG. 8(B). The store information shown in FIG. 8(B) includes store identification information, store name (branch name), store specification information 1, and store specification information 2. The store identification information is identification information that uniquely identifies a store. The store identification information shown in FIG. 8(B) is composed of a store (trade name) or company code and a branch code. The store name is the name of the store. The store name shown in FIG. 8(B) is composed of a store (trade name) or company and a branch name. The store specification information 1 is two-dimensional code information for identifying the store where the transaction is made (the store where the product is bought and sold). The store specification information 2 is store location information (GPS information) for identifying the store where the transaction is made. Note that in the example shown in FIG. 8(B), the store identification information and the store specification information 1 are different, but the store identification information and the store specification information 1 may be the same.

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

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

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

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

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

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

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

[0059] The reserved product information (total) is information that is updated each time a reserved product (described later) is registered. The reserved product information (total) includes the number of reserved products (number of products), the number of non-file reserved products, the number of unreadable reserved products (check for unauthorized operation), etc.

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

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

[0062] Reserved Product Information (Reserved Product 1) is information on reserved product 1. Reserved Product Information (Reserved Product 2) is information on reserved product 2. Reserved Product Information (Reserved Product 3) is information on reserved product 3.

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

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

[0065] 9 shows an example of reserved product definition corresponding to cart information in this embodiment. In the figure, an example is shown in which reserved products are classified into eight categories. Classification numbers "1" to "8" are assigned to each of the eight reserved product classifications. The classification of the reserved product with classification number 1 is “NON-FILE” as explained in FIG. The classification of the reserved product with classification number 2 is “reading not allowed” as explained in FIG.

[0066] The classification of the reserved product with classification number 3 is "pseudo-scan." A "pseudo-scan" reserved product is a product for which the customer attempted to have the mobile terminal device 40 read the product's code, but the mobile terminal device 40 was unable to read the code properly.

[0067] As a specific example, a "pseudo scan" corresponds to a situation in which the product is brought within the imaging range of the imaging unit 408, but the product code is not brought within the imaging range of the imaging unit 408. Additionally, a "pseudo scan" corresponds to a situation in which the product is brought within the imaging range of imaging unit 408, but an image of a portion that does not have a code is captured. Additionally, a "pseudo scan" corresponds to a situation in which the product is brought into the imaging range of imaging unit 408 while the code portion is covered by a finger or the like. Additionally, a "pseudo scan" refers to a situation in which the image capture unit 408 captures an image of the code on a product, but the product is passed through the imaging range of the imaging unit 408 at a speed that makes it impossible for the mobile terminal device 40 to read the code.

[0068] The classification of reserved products with classification number 4 is “non-scan-inserted.” Reserved products with the “non-scan-inserted” classification are products that have been added to shopping cart 80 without performing an operation to position the product’s code within the imaging range of imaging unit 408.

[0069] The classification of reserved items with classification number 5 is "age verification items." "Age verification items" are items such as alcohol and tobacco that require a store clerk to verify the customer's age before selling them.

[0070] The classification of reserved goods with classification number 6 is "pharmaceuticals." "Pharmaceuticals" are goods that require a qualified person, such as a pharmacist, to confirm with the purchaser.

[0071] The classification of reserved items with classification number 7 is "anti-theft tag items." "Anti-theft tag items" are items that have anti-theft tags attached and require a store clerk to remove the anti-theft tag from the item when it is sold.

[0072] The classification of the reserved product with classification number 8 is a "cancelled product." A "cancelled product" is a product that was once registered but was cancelled by a customer's cancellation operation on the mobile terminal device 40. A "cancelled product" is taken from the customer by a store clerk at the time of payment, for example.

[0073] Among the classification numbers 1 to 8, the three categories "NG to read", "pseudo scan", and "inserted without scanning" correspond to products whose codes were not read when the customer was registering the product on the mobile terminal device 40. Hereinafter, such a situation in which the code is not read during registration and the product is registered as a reserved product in the cart information is referred to as a "read failure situation". Products that fall into one of the three categories of "NG to read", "pseudo scan", and "inserted without scanning" may also be referred to as "read failure products".

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

[0075] [Example of basic processing procedure for self-operation] The sequence diagram in Fig. 10 shows an example of a processing procedure executed by the mobile terminal device 40, the settlement device 20, and the transaction management server 50 in response to a transaction in a self-service operation. Specifically, the processing in Fig. 10 shows an example of the processing of the mobile terminal device 40, the settlement device 20, and the transaction management server 50 from when a customer registers a product to be purchased from among products displayed in the store, until the settlement for the registered product is completed.

[0076] Step S1: The mobile terminal device 40 acquires information for identifying a store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (the two-dimensional code may be output on a display screen, a medium on which the two-dimensional code is printed may be attached, etc.), and a customer who visits the store may scan (read) the two-dimensional code with the mobile terminal device 40, thereby allowing the mobile terminal device 40 to acquire the store identification information. When a customer who visits the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer who visits the store scans the two-dimensional code with the mobile terminal device 40, the shopping application may be started, and a screen informing the customer that the transaction management server 50 is currently connected may be displayed as a start-up screen.

[0077] Also, for example, since a store is identified by its location, a customer who visits the store may obtain location information (GPS information) at the store using the mobile terminal device 40 (i.e., the store's location information may be obtained as store identification information). When a customer who visits the store starts up a shopping application, the location information may be obtained, and a screen may be displayed as a start-up screen informing the customer that the application is currently connected to the transaction management server 50. If multiple stores are detected from the location information and it is not possible to identify one, a selection screen may be displayed to allow the customer to select. Alternatively, a mode may be switched to forcefully obtain a two-dimensional code.

[0078] 11(A) shows an example of a shopping application start-up screen displayed on touch panel display unit 406 of mobile terminal device 40. The start-up screen in the figure displays the store name. This store name is displayed based on the store identification information acquired in step S1. When a customer wishes to start registering a product for shopping, the customer operates a transaction start button BT10 arranged on the start-up screen. In response to the operation of the transaction start instruction button BT10, the mobile terminal device 40 transmits a transaction start request including the acquired store specific information and customer identification information to the transaction management server 50. The transaction start request may be transmitted in response to the customer's operation on the mobile terminal device 40 as described above, or may be transmitted in response to the acquisition of store specific information without receiving any particular operation. Regarding the customer identification information, the information entered in the name field of the registration form using the mobile terminal device 40 during customer registration (when downloading or installing a shopping application to the mobile terminal device 40) may be stored in the customer information of the transaction management server 50, but may also be stored in the memory of the mobile terminal device 40 in addition to the transaction management server 50. When a store is identified (when an initial product registration screen, described below, is acquired), the store name, ongoing services (flyer information distributed on that day), and available coupon information of the store may be displayed on a screen (the initial product registration screen or a screen other than the initial product registration screen). The service and coupon information may be acquired from the transaction management server 50 as screen information, for example.

[0079] The destination information (address of the transaction management server 50) may also be obtained at the time of customer registration (when a shopping application is downloaded or installed on the mobile terminal device 40) and stored in the memory of the mobile terminal device 40. When scanning a two-dimensional code, the destination information may be converted into a two-dimensional code in addition to the store-specific information, and the mobile terminal device 40 may scan the two-dimensional code to obtain the destination information together with the store-specific information.

[0080] Step S2: The transaction management server 50, which has received the customer identification information and store identification information as a transaction start request from the mobile terminal device 40, generates cart information for the transaction. Note that in the initial state in which the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are stored, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, product information (registered product information, pending product information), etc.) is not stored.

[0081] As described above, the transaction management server 50 stores store information such as that shown in Figure 8(B), so when it receives store identification information (it also receives customer identification information) as a transaction start request from the mobile terminal device 40, if the received store identification information is a two-dimensional code, it acquires the store identification information by referring to store identification information 1, and if the received store identification information is location information (GPS information), it acquires the store identification information by referring to store identification information 2. Note that if the store identification information received from the mobile terminal device 40 is store identification information converted into a two-dimensional code, the transaction management server 50 need only acquire it as is.

[0082] In other words, the transaction management server 50, which receives customer identification information and store identification information from the mobile terminal device 40 as a transaction start request, acquires the store identification information from the store identification information received from the mobile terminal device 40, and further acquires the current date, issues (assigns) a serial number, combines the store identification information with the current date and serial number, and stores the combined information as cart identification information in the cart information. Also, the transaction management server 50, which receives store identification information and customer identification information from the mobile terminal device 40 as a transaction start request, acquires the current date and time, and stores the current date and time as the transaction start date and time (generation date and time) in the cart information. Also, the transaction management server 50, which receives store identification information and customer identification information from the mobile terminal device 40 as a transaction start request, stores the customer identification information received from the mobile terminal device 40 as customer identification information in the cart information.

[0083] Step S3: The transaction management server 50, which has generated the cart information for the transaction, generates product registration initial screen information (screen information of the product registration screen, which is the initial screen), and transmits it to the mobile terminal device 40. Specifically, the transaction management server 50 generates, for example, the product registration initial screen information, and transmits the generated product registration initial screen information to the mobile terminal device 40 together with the cart identification information.

[0084] Step S4: The mobile terminal device 40, which has received the cart identification information and the product registration initial screen information from the transaction management server 50, stores the cart identification information and displays the registration screen on the display unit. Specifically, the mobile terminal device 40 displays the product registration initial screen as shown in FIG. 11(B), for example.

[0085] Step S5: The customer operates the mobile terminal device 40 to scan the barcode attached to the product and read the product code. In the figure, it is assumed that the barcode has been successfully scanned. Steps S5 to S9 are repeatedly executed every time the barcode attached to the product is scanned.

[0086] The mobile terminal device 40 that has acquired the barcode transmits to the transaction management server 50 the cart identification information and product registration information including the product code acquired by scanning.

[0087] Step S6: The transaction management server 50 receives the product registration information (cart identification information and product code) from the mobile terminal device 40 and identifies the cart information of the transaction from the cart identification information included in the received product registration information.

[0088] Step S7: The transaction management server 50 updates the product data in the identified cart information. Specifically, if the received product registration information contains a product code for item N, the transaction management server 50 stores the product code as the product code of the registered product information (registered product N) in the identified cart information, obtains the product name and price corresponding to the product code from the product information, and stores them as the product and price of the registered product information (registered product N). The transaction management server 50 also updates the registered product information (total) in the identified cart information.

[0089] Step S8: After updating the product data in the cart information, the transaction management server 50 generates product registration update screen information (screen information of the product registration screen, which is an update screen to which the registered product has been added) and transmits it to the mobile terminal device 40. Specifically, the transaction management server 50 generates product registration update screen information such that the mobile terminal device 40 displays a product registration update screen to which a list item of the currently registered product has been added to the registered product list, as shown in Fig. 11(C), for example, and transmits the generated product registration update screen information to the mobile terminal device 40 together with the cart identification information.

[0090] The product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the mobile terminal device 40 after "XX bread" is registered as the third product item. In other words, when "XX yogurt" is stored in the cart information as the first item, the transaction management server 50 generates product registration update screen information such that "XX yogurt" is displayed on the mobile terminal device 40 and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal device 40; when "XX chocolate" is stored in the cart as the second item, the transaction management server 50 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed on the mobile terminal device 40 and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal device 40; and when "XX bread" is stored in the cart information as the third item, the transaction management server 50 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed on the mobile terminal device 40 as shown in FIG. 11(C), and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal device 40.

[0091] In response to the registration of one product, a registered product display screen WD1 may be displayed to display the currently registered product, as shown in Fig. 12(A), for example. In addition, in the registered product display screen WD1 shown in the same figure, in response to the target product being available for eating in, a "Yes" button BT1 and a "No" button BT2 are displayed to confirm with the customer whether or not they would like to eat in. In this case, the price of the product is calculated so that the consumption tax rate for the target product is different when the "Yes" button BT1 is operated and when the "No" button BT2 is operated.

[0092] Step S9: The mobile terminal device 40, which has received the cart identification information and the product registration update screen information from the transaction management server 50, adds the product to the registration screen. Specifically, the mobile terminal device 40 displays a product registration update screen as shown in Fig. 11(C), for example. As described above, the product registration screen (product registration update screen) shown in Fig. 11(C) is displayed on the mobile terminal device 40 after "XX bread" is registered as the third product item.

[0093] Step S10: The mobile terminal device 40 accepts a payment instruction operation as an operation by the customer, for example, a touch of the "Proceed to Checkout" button shown in FIG.

[0094] Step S11: The mobile terminal device 40 that has accepted the settlement transition instruction operation generates a two-dimensional code. That is, the mobile terminal device 40 converts information (e.g., cart identification information) required for executing the settlement process for the products purchased by the mobile terminal device 40 into a two-dimensional code. The mobile terminal device 40 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, a code display screen on which a two-dimensional code is arranged as shown in FIG. 11(D) is displayed on the display unit.

[0095] Step S12: The settlement device 20 scans (reads) the two-dimensional code displayed on the display unit of the mobile terminal device 40. For example, the settlement device 20 scans the two-dimensional code displayed on the display unit of the mobile terminal device 40 that is pointed by the customer within the recognition range of the scanner unit 204.

[0096] Step S13: The settlement device 20 reads the two-dimensional code displayed on the display of the mobile terminal device 40 and requests the calculation of the subtotal amount from the transaction management server 50. For example, the settlement device 20 sends a calculation request (subtotal amount calculation request information) to the transaction management server 50, together with the cart identification information obtained from the two-dimensional code, to request the calculation of the subtotal amount.

[0097] Step S14: The transaction management server 50, which has received the cart identification information and the sub-calculation output request information from the mobile terminal device 40, identifies the cart information of the transaction from the cart identification information.

[0098] Step S15: Having identified the cart, the transaction management server 50 calculates the subtotal amount using information such as prices in the registered product information included in the cart information corresponding to the identified cart information.

[0099] Step S16: After calculating the subtotal, the transaction management server 50 updates the cart information (stores the subtotal (calculated subtotal)) and transmits the subtotal information indicating the calculated subtotal to the settlement device 20 together with the cart identification information.

[0100] Step S17: The settlement device 20, which has received the cart identification information and the subtotal information from the transaction management server 50, displays the subtotal amount on the customer display unit 206, for example, as shown in FIG. 12(B).

[0101] Step S18: The settlement device 20, which has displayed the subtotal on the customer display unit 206, executes the payment (settlement). Specifically, the settlement device 20 accepts the selection of the payment type. In the case of cash, it accepts the deposit, calculates the amount of change, and, if there is change, dispenses the change and issues a receipt. Furthermore, when the settlement is completed, the settlement device 20 sends settlement completion information together with the cart information to the transaction management server 50, and the transaction management server 50 stores the transaction end date and time (settlement date and time) for that cart.

[0102] The mobile terminal device 40 transmits the product code to the transaction management server 50 after scanning the product (S5), but may not transmit product codes for products (e.g., products scanned at another store, etc.) other than those scanned in the store (the store when the customer visited the store and displayed the product registration initial screen). For example, the mobile terminal device 40 acquires and stores location information (GPS information) when the customer visits the store (or when the product registration initial screen is displayed). The mobile terminal device 40 also acquires location information when each product is scanned, and compares the location information acquired when the customer visited the store (or when the product registration initial screen is displayed). If the two information match (or approximately match), the mobile terminal device 40 may permit the transmission of the product code of the product to the transaction management server 50, and if the two information do not match (or approximately match), the mobile terminal device 40 may prohibit the transmission of the product code of the product to the transaction management server 50. This makes it possible to prevent inappropriate product registration (for example, registering a product to a cart created in another store, etc.).

[0103] When the settlement device 20 prohibits the transmission of the product code as described above, after scanning the product, the settlement device 20 may display an error message (e.g., "Registration is not possible because the product is not in the XX store") on the customer display unit 206. Furthermore, the settlement device 20 may display the above message on the store clerk display unit 410 instead of or in addition to the message on the customer display unit 206.

[0104] The settlement device 20 reads the two-dimensional code displayed on the display of the mobile terminal device 40 and then requests the transaction management server 50 to calculate the subtotal amount (S13), but may not request calculation of the subtotal amount for products other than the product scanned in the store (for example, products scanned in other stores). For example, the settlement device 20 refers to the store identification information of the store (it may store and refer to the store identification information of the store in its own settlement device 20, or may refer to the store identification information stored in another accessible device), and when it reads the two-dimensional code displayed on the display of the mobile terminal device 40, it compares the cart identification information obtained from the two-dimensional code with the store identification information of the store. The settlement device 20 may permit the request to calculate the subtotal amount if the store identification information included in the cart identification information includes the store identification information of the store, and may prohibit the request to calculate the subtotal amount if the store identification information does not include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payment for products registered at other stores, etc.).

[0105] When the settlement device 20 prohibits the request for the subtotal amount as described above, after reading the two-dimensional code, the settlement device 20 may display an error message (e.g., "Settlement cannot be completed because the transaction includes products not from the XXX store") on the customer display unit 206. Furthermore, the settlement device 20 may display the above message on the store clerk display unit 410 instead of or in addition to the message on the customer display unit 206.

[0106] In the example of the processing procedure in Fig. 10, the transaction management server 50 calculates the subtotal amount. However, for example, the settlement device 20 may acquire cart information from the transaction management server 50 and calculate the subtotal amount based on the acquired cart information. Alternatively, the transaction management server 50 may transmit cart information to the management device 30 and request calculation of the subtotal amount, the management device 30 may calculate the subtotal amount using the received cart information, and the calculated subtotal amount may be transmitted to the settlement device 20 via the transaction management server 50.

[0107] During the settlement process, the transaction management server 50 may check the cancellation status of the customer's products based on the customer information and cart information of the customer, and determine whether or not to issue a warning against fraud. If it is determined that a warning should be issued, the transaction management server 50 may, for example, cause the settlement device 20 to issue a warning notification.

[0108] Furthermore, during the settlement process, the transaction management server 50 may determine whether or not the product information included in the cart information includes any reserved products, and if so, may request the settlement device 20 to provide instructions to correct the reserved products. Upon receiving the request to provide instructions to correct the reserved products, the settlement device 20 displays a message to notify the user that there are reserved products, as shown in Fig. 12(C). Upon confirming the message, the store clerk may perform an operation to release (correct) the reserved products, such as entering a price corresponding to the reserved products or canceling the reserved products.

[0109] [Configuration for dealing with read failure situations] Here, Fig. 10 shows a process corresponding to a case where the reading of the product code is successful in step S5. However, in the stage of the product code reading process corresponding to step S5, the mobile terminal device 40 may determine that a situation (reading failure situation) corresponding to any of the reading failures of classification numbers 2 to 4 in Fig. 9 has occurred. When it is determined that a reading failure situation has occurred due to any of classification numbers 2 to 4, the mobile terminal device 40 transmits information (reading failure information) relating to the product corresponding to the occurrence of the reading failure situation to the transaction management server 50. When determining the occurrence of a reading failure situation, the mobile terminal device 40 determines which of the pending product classifications 2 to 4 (read NG, pseudo scan, non-scan input) the reading failure situation that has occurred corresponds to. The reading failure information may include information indicating the determined pending product classification.

[0110] Furthermore, when transmitting read failure information in response to the occurrence of a read failure, the mobile terminal device 40 may transmit captured images corresponding to the occurred read failure. The captured images to be transmitted may be extracted from the buffered captured images, for example, by buffering the captured images captured by the imaging unit 408 for reading the product code for a certain period of time. Furthermore, the captured images to be transmitted may be, for example, a predetermined number of still images, or may be moving images for a predetermined period of time in response to the occurrence of a read failure. The captured image transmitted from the mobile terminal device 40 in this manner may be displayed so that a store clerk can check it, for example, on a reserved item processing screen that is displayed when the reserved item is released from the settlement device 20. Alternatively, the transmitted captured image may be displayed on a monitoring device that a store clerk uses to monitor the transaction status in the store.

[0111] Furthermore, when a reading failure occurs as described above, the mobile terminal device 40 treats the product that has become unreadable in response to the reading failure situation (read failure product) as a reserved product. In this case, the mobile terminal device 40 may be configured to treat the unread failure product as a reserved product at the timing when it is determined that a reading failure situation has occurred, and to display a message to inform the customer that the product will be treated as a reserved product. For example, the mobile terminal device 40 may display a message such as "Scanning failed" or "Product was determined to be unreadable" in a pop-up window superimposed on the product registration screen.

[0112] Furthermore, the misread product is treated as a reserved product as described above. On the product registration screen, a registered product list is displayed as shown in FIG. 11(C), but for the reserved products classified as misread products, list items do not need to be displayed in the registered product list. For the reserved products that are not classified as misread products, list items are displayed in the registered product list. Note that for the misread products, list items may be displayed in the registered product list to indicate that they are misread products.

[0113] An example of a processing procedure executed by the mobile terminal device 40 and the transaction management server 50 of this embodiment in relation to product registration, including processing for handling a reading failure situation, will be described with reference to the flowchart of Fig. 13. The processing in Fig. 13 corresponds to Fig. 10, and more specifically shows the process of steps S5 to S11 as including processing for handling a reading failure situation.

[0114] First, an example of a process procedure executed by the mobile terminal device 40 will be described. Step S101: With the product registration screen displayed, the mobile terminal device 40 determines whether or not the reading of the product code has been completed normally.

[0115] Step S102: If the reading of the product code is completed normally, the mobile terminal device 40 transmits to the transaction management server 50 the product registration information including the read product code and the cart identification information. Step S103: In response to receiving the registration completion notification sent from the transaction management server 50 in response to the sending of the product registration information in step S102, the mobile terminal device 40 updates the product registration screen, for example, as shown in FIG. 11(C).

[0116] Step S104: The mobile terminal device 40 detects a reading failure state based on a captured image obtained by causing the imaging unit 408 to capture an image for reading the product code. If it is determined in step S101 that the reading of the product code has not been completed normally, or after the processing of step S103, the mobile terminal device 40 determines whether or not a reading failure state has occurred based on the detection result of the reading failure state.

[0117] The mobile terminal device 40 may be adapted to detect a no-read condition as follows. First, when the mobile terminal device 40 recognizes that the entire barcode of the product is captured in the captured image, but the reading of the barcode is not completed normally (successful) after a certain period of time has elapsed, it determines that a reading failure situation classified as reading NG has occurred.

[0118] In addition, when the mobile terminal device 40 recognizes a product in a captured image but is unable to recognize the barcode at all and therefore is unable to successfully read the barcode, it determines that a reading failure situation classified as a pseudo scan has occurred. Alternatively, the mobile terminal device 40 may determine that a reading failure situation classified as a pseudo scan has occurred if reading of the barcode of a product is not completed successfully because only a portion of the barcode of the product can be recognized in the captured image. Alternatively, the mobile terminal device 40 may determine that a reading failure situation classified as a pseudo scan has occurred if the barcode of a product is recognized in the captured image but the reading of the barcode is not completed successfully because the product is moving too quickly. Such a reading failure situation classified as a pseudo scan may indicate fraudulent activity in which a customer places an item in the shopping cart 80 simply by pretending to perform an operation to have the barcode of the item read.

[0119] 1C, the mobile terminal device 40 can capture an image of the contents of the shopping basket 80 placed in the shopping cart. When the mobile terminal device 40 detects a state in which a new product has been added to the shopping basket 80 even though no attempt to read the barcode of the product is recognized in the captured image, the mobile terminal device 40 determines that a reading failure situation classified as a non-scan input has occurred. For example, a customer may move an already registered product within the shopping basket 80 in order to organize the contents of the shopping basket 80. The mobile terminal device 40 may be configured to distinguish between such a movement of a product and the additional insertion of a new product corresponding to a reading failure situation as a non-scan insertion, based on the captured image. The occurrence of such a reading failure situation classified as a non-scan insertion may indicate fraud, such as a customer placing an item in the shopping cart 80 without having the barcode of the item read by the mobile terminal device 40.

[0120] Step S105: If it is determined in step S104 that a reading failure has occurred, the mobile terminal device 40 assigns a classification number to the pending product corresponding to the current reading failure occurrence, according to the classification as the reading failure detected in step S104. As an example, if it is determined in step S104 that a reading failure situation classified as reading NG has occurred, the mobile terminal device 40 assigns classification number 2 (see FIG. 9) to the corresponding pending product.

[0121] Step S106: The mobile terminal device 40 transmits the unreadable information to the transaction management server 50.

[0122] Step S107: The mobile terminal device 40 updates the product registration screen in response to receiving the registration completion notification transmitted from the transaction management server 50 in response to the transmission of the product registration information in step S102. This allows a list item corresponding to the occurrence of the current reading failure to be additionally displayed in the registered product list on the product registration screen. In this case, the list item does not show information about the specific product such as the product name, but may show, for example, that a reading failure occurred due to the corresponding reserved product classification.

[0123] Step S108: If it is determined in step S104 that a reading failure state has not occurred, or after the process of step S107, the mobile terminal device 40 determines whether or not a settlement transition instruction operation has been accepted. If the settlement transition instruction operation has not been accepted, the process returns to step S101.

[0124] Step S109: When the payment transition instruction operation is accepted, the mobile terminal device 40 converts the cart identification information into a two-dimensional code, for example, and displays the generated two-dimensional code on a code display screen as shown in FIG. 11(D), for example.

[0125] Next, an example of a processing procedure executed by the transaction management server 50 will be described. Step S201: The transaction management server 50 determines whether or not the product registration information transmitted from the mobile terminal device 40 in step S102 has been received.

[0126] Step S202: When the transaction management server 50 receives the product registration information, the transaction management server 50 identifies the cart information indicated by the cart identification information included in the received product registration information. Step S203: The transaction management server 50 updates the cart information identified in step S202. That is, the transaction management server 50 adds the registered product information based on the product code included in the product registration information received in response to step S201 or the reserved product information to the identified cart information. As a result, one product is registered in the cart information.

[0127] Note that the update of the cart information in step S202 includes the registration of products among the reserved products that do not correspond to the reading failure situation. In other words, the update of the cart information in step S202 includes the registration of products among the reserved products whose product codes have been read successfully. Among the reserved products, the products whose product codes have been read successfully are NON-FILE, age verification products, medicines, and security tag products. In addition, although canceled products are not reflected in the process in the same figure, in response to a cancellation operation being performed on the mobile terminal device 40, the transaction management server 50 updates the registered product information of the corresponding product in the cart information so that the corresponding product is managed as a canceled product.

[0128] Step S204: After the process of step S203, the transaction management server 50 transmits a registration completion notification to the mobile terminal device 40.

[0129] Step S205: After the process of step S204, or if it is determined in step S201 that the product registration information has not been received, the transaction management server 50 determines whether or not the read failure information transmitted from the mobile terminal device 40 in step S107 has been received. If the read failure information has not been received, the process returns to step S201.

[0130] Step S206: When the transaction management server 50 receives the unreadable information, it identifies the cart information indicated by the cart identification information included in the received product registration information. Step S207: The transaction management server 50 updates the cart information identified in step S206. In this case, the transaction management server 50 adds the reserved product information including the classification number included in the read failure information received in step S205 to the identified cart information. As a result, one reserved product (read failure product) corresponding to the occurrence of the read failure situation is registered in the cart information.

[0131] Step S208: After the process of step S207, the transaction management server 50 transmits a registration completion notification to the mobile terminal device 40.

[0132] When the customer has finished registering all the products to be purchased, he or she performs a settlement transition instruction operation and has the settlement device 20 read the two-dimensional code displayed on the mobile terminal device 40. After reading the two-dimensional code, the settlement device 20 requests the transaction management server 50 to calculate the subtotal amount, as shown as step S13 in Fig. 9. Here, in this embodiment, when requesting calculation of the subtotal amount, the settlement device 20 requests settlement information to be used in the settlement process using the settlement screen.

[0133] In response to a request for payment information, the transaction management server 50 identifies the corresponding cart information and generates payment information based on the identified cart information. The payment information includes registered product information in the cart information and information such as the subtotal amount for the registered products. When the settlement device 20 receives the settlement information, it displays a settlement screen on the customer display unit 206 that reflects the contents of the received settlement information.

[0134] [Product registration at bulk sales areas] The store of this embodiment has a sales floor that supports self-pricing by weight, where customers use the weighing pricing device 10 to price and register products sold by weight. In sales floors where the weighing pricing device 10 is used in accordance with the self-pricing method, the procedures for registering products and the associated processing in the sales system differ from those in the case where the basic product registration operation described above is performed. This point will be explained below.

[0135] First, an example of a procedure for a customer to register an item at a sales floor where the weighing and pricing device 10 is used will be described. When a customer wishes to purchase a commodity sold by weight, the customer first uses his / her mobile terminal device 40 to input the item name of the commodity to be purchased in the following manner. FIG. 14 shows an example of a display of products sold by weight in a store. In the example shown in FIG. 14, lemons LM, apples AP, and oranges OG are displayed as products sold by weight. Also, product information panels 3000-LM, 3000-AP, and 3000-OG are installed corresponding to the displayed lemons LM, apples AP, and oranges OG. When no particular distinction is made between the product information panels 3000-LM, 3000-AP, and 3000-OG, they will be referred to as product information panel 3000.

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

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

[0138] When inputting the item of the product to be purchased, the customer displays the product registration screen on his / her mobile terminal device 40 and has the mobile terminal device 40 read the product information code presented on the product information panel 3000 of the product to be purchased. The figure shows the customer reading the product information code 3001 corresponding to lemon LM. The scanned image area AR11 on the product registration screen of the mobile terminal device 40 shows the product information code 3001 captured. When the product information code 3001 corresponding to lemon LM is code scanned in this manner, the mobile terminal device 40 acquires product information of lemon LM from the read product information code 3001. The mobile terminal device 40 uses the acquired product information to specify lemon LM as an item of merchandise sold by weight.

[0139] The product registration screen displayed on the mobile terminal device 40 in the figure will be described. The product registration screen in the figure is similar to that in Figures 11(B), 11(C), etc., but for the sake of convenience, the various parts in the product registration screen in the figure are denoted by reference numerals as follows.

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

[0141] In the example shown in the figure, the customer has provisionally registered lemons LM and apples AP as products sold by weight. In this case, the two products sold by weight that the customer specified as items to purchase were lemons LM and apples AP. In this case, the customer will weigh each of the lemons LM and apples AP. The customer will then take out the amount (number) of lemons LM and apples AP that he or she wishes to purchase from the lemons LM and apples AP that are on display. The customer then takes the lemons LM and apples AP that he or she has taken out and goes to the weighing pricing device 10.

[0142] 15 shows the state in which the weighing and pricing device 10 of this embodiment is in a standby state and displays a standby screen on the customer display unit 106. The standby screen is shown enlarged in FIG. 15. In the standby screen shown in FIG. 15, a code reading guide area AR21 and a weighing guide area AR22 are arranged.

[0143] The code reading guidance area AR21 displays information in response to guidance for customers who are registering products using the mobile terminal device 40. In the code reading guidance area AR21, for example, a connection information code CD in the form of a two-dimensional code is displayed, and then a display is displayed instructing the customer to first have the mobile terminal device 40 read the connection information code CD when starting to register the product to be purchased (including weighing and pricing based on the weighing result).

[0144] The connection information code CD is control information for connecting the mobile terminal device 40, on which a shopping application runs, to the weighing and pricing device 10, for example, via Bluetooth.

[0145] The measurement guidance area AR22 displays information corresponding to guidance for customers who do not use the mobile terminal device 40 for shopping. In the measurement guidance area AR22, a display is displayed to guide the customer to place a product corresponding to one of the products to be purchased on the weighing platform 109b of the weighing unit 109 when starting to register products to be purchased.

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

[0147] In response to reading the connection information code CD as described above, the portable terminal device 40 establishes communication with the metered pricing device 10. When the metered pricing device 10 and the portable terminal device 40 are communicatively connected in this manner, the metered pricing device 10 enters a state in which communication is exclusively held by the connected portable terminal device 40. In a state in which communication is exclusively held, the portable terminal device 40 does not connect to other portable terminal devices 40.

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

[0149] In response to establishing communication with the weighing pricing device 10, the mobile terminal device 40 transmits information on the temporarily registered bulk merchandise to the weighing pricing device 10. Specifically, the mobile terminal device 40 in this case transmits information on lemons LM and apples AP as information on the temporarily registered bulk merchandise.

[0150] In addition, the portable terminal device 40 displays a pricing operation screen on the touch panel display unit 406 in response to the establishment of communication with the weighing pricing device 10. Fig. 16(B) shows an example of the pricing operation screen displayed on the touch panel display unit 406 of the portable terminal device 40.

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

[0152] In the figure, the mobile terminal device 40 displays a pricing operation screen similar to that displayed on the weighing and pricing device 10. This allows the customer to weigh, price, and register a provisionally registered product on either the mobile terminal device 40 or the weighing and pricing device 10. It should be noted that the mobile terminal device 40 may display a product registration screen or the like instead of displaying the pricing operation screen. In the following description, an example will be given in which a customer operates the pricing operation screen displayed on the weighing pricing device 10 to perform registration.

[0153] Here, the customer decides to register Apple AP first, of the two products Apple AP and Lemon LM that are provisionally registered. In this case, the customer operates the product selection button BT11-1 corresponding to Apple AP on the pricing operation screen. FIG. 17(A) shows the state in which the customer operates the product selection button BT11-1 corresponding to Apple AP. The product selection button BT11-1 is highlighted in response to being touched by operation. By operating the product selection button BT11-1 in this way, Apple AP is designated as the registration target.

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

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

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

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

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

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

[0160] The customer operates the product selection button BT11-2 corresponding to the lemon LM, and then causes the weighing and pricing device 10 to weigh, price, and issue a label for the lemon LM in the same procedure as for the apple AP described above. When the label for the lemon LM has been issued, weighing and pricing (registration) for all products sold by weight that were provisionally registered is completed.

[0161] In response to the completion of registration of all bulk sales products that were in a provisionally registered state, the display on the customer display unit 106 of the weighing and pricing device 10 is returned to the standby screen (FIG. 15).

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

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

[0164] An example of a process performed by the weighing pricing device 10, the mobile terminal device 40, and the transaction management server 50 of this embodiment in relation to the registration of products sold by weight in one transaction will be described with reference to the flowchart of FIG.

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

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

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

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

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

[0170] Step S2103: If it is determined in step S2102 that the connection process has not been started, the weighing and pricing device 10 determines whether or not the weighing unit 109 has started weighing the item as a result of the customer placing the item on the weighing platform 109b.

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

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

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

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

[0175] Step S2106: When the connection is established, the mobile terminal device 40 transmits the provisionally registered product information. The weighing pricing device 10 acquires the transmitted provisionally registered product information. The provisionally registered product information is a product sold by weight, such as apples AP and lemons LM, whose item has been input in response to the mobile terminal device 40 reading the product information code 3001.

[0176] Step S2107: The weighing pricing device 10, which has acquired the provisionally registered commodity information, displays a pricing operation screen (FIG. 16(C)) on the customer display unit 106. The pricing operation screen is a screen on which product selection buttons BT11 corresponding to each provisionally registered commodity indicated by the acquired provisionally registered commodity information are arranged, and as a pricing operation, an operation of selecting one provisionally registered commodity to be the target of pricing processing from among the provisionally registered commodities is performed.

[0177] Here, the weighing pricing device 10 erases the standby screen that was displayed until the connection process was started, along with the display of the initial pricing operation screen in step S2107 in response to the start of the connection process in step S2102. The connection information code CD is also erased by erasing the standby screen. In other words, the process of step S2107 is a process of erasing the connection information code CD in response to the weighing pricing device 10 establishing a connection with the mobile terminal device 40.

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

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

[0180] Step S2110: On the weighing result screen, a label issuing button BT15 is provided. The customer operates the label issuing button BT15. In response to the operation of the label issuing button BT15, the weighing pricing device 10 issues a label corresponding to the product priced by the current pricing process of step S2018.

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

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

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

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

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

[0186] Step S2212: The customer performs an operation to have the mobile terminal device 40 read the connection information code CD, and the mobile terminal device 40 reads the connection information code CD. In response to the reading of the connection information code CD, the mobile terminal device 40 executes a process for communicatively connecting with the weighing-pricing device 10 according to the connection procedure indicated by the read connection information code CD, between the mobile terminal device 40 and the weighing-pricing device 10.

[0187] Step S2213: When a connection with the weighing pricing device 10 is established by the connection process of step S2212, the mobile terminal device 40 transmits provisionally registered product information to the weighing pricing device 10. The provisionally registered product information is information on the weighing product for which item information has been input by the processes of steps S2201 to S2203.

[0188] Step S2214: After the process of step S2213, the mobile terminal device 40 displays a pricing operation screen (FIG. 16(B)) on the touch panel display unit 406 in place of the product registration screen.

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

[0190] Step S2216: After the process of step S2215, the mobile terminal device 40 determines whether or not the pricing process has been completed for all provisionally registered products. If there are any products for which the pricing process has not yet been completed, the process returns to step S2214. In this case, in step S2214, the mobile terminal device 40 updates the pricing operation screen that has been displayed up until now so that the product selection buttons for provisionally registered products for which the pricing process has been completed become inoperable.

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

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

[0193] [Regarding the occurrence of reading failures at bulk sales counters] When a customer is registering a product at a bulk sales counter as described above, the mobile terminal device 40 is in a state in which the product is being registered and is therefore in a state in which the process of product registration shown in FIG. 13 is being executed. For this reason, when a customer is registering a product in the above manner at a bulk sales counter, a case may occur in which the portable terminal device 40 determines that a reading failure has occurred. This point will be described with reference to FIG. 21(A).

[0194] FIG. 21(A) shows, over time, the timing at which certain events occur according to the procedure when a customer registers an item at a bulk sales counter. A customer goes to a place where merchandise sold by weight is displayed in a sales area that supports selling by weight, and at time t1, has the mobile terminal device 40 read the merchandise information code 3001 corresponding to the type of merchandise that the customer wishes to purchase.

[0195] When the customer has the product information code 3001 read by the mobile terminal device 40, the customer picks out the quantity of products sold by weight that he or she wishes to purchase from the displayed products sold by weight and moves to the weighing pricing device 10. Here, the customer may move to the weighing pricing device 10 while still holding the products he or she has picked up, or may place (contain) them in the shopping basket 80 placed on the shopping cart. The figure shows that at time t2, a certain amount of time has passed since time t1, the products sold by weight that the customer picked up are placed in the shopping basket 80. Also, depending on the customer, at time t2 p In some cases, a customer may take out a bulk product to be purchased and place it in the shopping basket 80 before having the mobile terminal device 40 read the product information code 3001 at the timing shown in FIG. 11. In this way, a customer may place products in the shopping basket 80 at a timing before or after having the mobile terminal device 40 read the product information code 3001.

[0196] Mobile terminal device 40 determines the above-mentioned event of a bulk product being placed in shopping basket 80 as a reading failure situation. In other words, when a bulk product is placed in shopping basket 80, mobile terminal device 40 is placed in holder 71 attached to the shopping cart and captures an image of the inside of shopping basket 80 while executing the process related to product registration shown in FIG. In this case, the customer places the bulk product in the shopping basket 80 without performing any operation to have the mobile terminal device 40 read the product code. Furthermore, the bulk products do not have product codes attached to them. Therefore, the mobile terminal device 40, which captures the situation in which the bulk products are placed in the shopping basket 80, detects the situation in which a new product has been added to the shopping basket 80, even though it does not recognize any attempt to have the product's barcode read. In other words, the mobile terminal device 40 in this case determines that a reading failure situation classified as a non-scanning insertion has occurred. Note that, depending on the situation in which the customer places the bulk product in the shopping basket 80, the mobile terminal device 40 may determine that the insertion is a pseudo-scanning rather than a non-scanning insertion, but in any case, the determination result is that a reading failure situation has occurred.

[0197] As described above, the customer has the portable terminal device 40 read the product information code, picks up the product sold by weight to be purchased, and moves to the weighing pricing device 10. As shown as time t3 in the figure, the customer has the portable terminal device 40 read the connection information code CD displayed on the weighing pricing device 10 at the destination, thereby connecting the portable terminal device 40 and the weighing pricing device 10. As a result of the mobile terminal device 40 and the weighing pricing device 10 being connected, a pricing operation screen is displayed on the customer display unit 106 of the weighing pricing device 10. The customer operates the pricing operation screen as shown in Fig. 16(C) and Fig. 17(A) to specify the product sold by weight to be priced (registered), and places the product sold by weight to be registered on the weighing platform 109b of the weighing pricing device 10 as shown in Fig. 17(B). In response to the product sold by weight being placed on the weighing pricing device 10, at time t4 in the figures, the weighing pricing device 10 performs a process of weighing the product sold by weight and pricing according to the weighed weight. When the pricing process is completed, the weighing pricing device 10 displays a weighing result screen as shown in Fig. 18(A). At time t5 in the figure, the weighing pricing device 10 issues a label (single item label) for the weighing product reflecting the current pricing result in response to operation of the label issue button BT15 on the displayed weighing result screen. At this time, the weighing pricing device 10 completes product registration by transmitting product pricing information to the mobile terminal device 40 in response to operation of the label issue button BT15.

[0198] The customer lifts the item sold by weight from the weighing platform 109b and attaches the issued label to the bag containing the item sold by weight. If there is only one item sold by weight, the customer may attach a label to the item itself. Then, at time t6 in the figure, the customer places the item sold by weight in the shopping basket 80.

[0199] Here, the mobile terminal device 40 also executes the process of Fig. 13 when a bulk product for which the pricing process has been performed and registration has been completed as described above is contained in the shopping basket 80. Furthermore, a label is affixed to the bulk product contained in the shopping basket 80, but in this case, no product code is printed on the label, since the label is intended to certify that the corresponding bulk product has been registered. Therefore, even if a bulk product is placed in the shopping cart 80 at time t6 after registration of the bulk product is complete, the mobile terminal device 40 determines that a reading failure situation classified as a non-scanned entry has occurred.

[0200] In addition, if the customer is familiar with the use of the weighing and pricing device 10, the customer p In other words, when the weighing price determination process is completed at time t4 and the weighing result screen is displayed, the customer may first place a weighing item in the shopping basket 80 at the timing shown as t6. pAt the timing shown in FIG. 11, the weighing product is lifted from the weighing platform 109b and placed in the shopping basket 80. The customer then operates the label issuing button BT15 to issue a label with product pricing information (time t5), and affixes the issued label to the weighing product already in the shopping basket 80. In such a case, the portable terminal device 40 prints the label at time t6, which is before time t5. p At this timing, it is determined that a reading failure state classified as a non-scan input has occurred.

[0201] In this way, when a customer self-registers a bulk product at the bulk product counter, the customer has two opportunities to place the bulk product in the shopping basket 80 (at time t2 (or at time t2 p ), time t6 (or time t6 p ) there is a possibility that it is determined (detected) that a reading failure state has occurred due to non-scan input.

[0202] When such a reading failure is detected, the product registration result in the cart information will be a duplication of the product registration information for the same bulk product that was normally registered and the reserved product information corresponding to the non-scanned input. When a reading failure is detected, the mobile terminal device 40 can display a message informing the customer that the product corresponding to the reading failure will be treated as a reserved product. In this case, the registration of the reserved product information can be erased, for example, by having a store clerk perform a hold release operation corresponding to a non-scan input at the settlement device 20. However, on the other hand, since the same target bulk product is registered normally, it is not desirable for a notification corresponding to a reading failure situation to be displayed on the mobile terminal device 40 when the customer places the product in the shopping cart 80. Also, a reading failure situation such as non-scanning input or pseudo-scanning can be treated as fraudulent activity. Therefore, when a reading failure situation caused by non-scanning input or pseudo-scanning is detected, for example, a monitoring device (not shown) installed in the store can notify the occurrence of fraudulent activity by displaying a message based on information transmitted from the transaction management server 50. However, it is not appropriate to notify the occurrence of a reading failure situation detected during self-registration of such bulk products as fraudulent activity.

[0203] Therefore, in this embodiment, when self-registering a product sold by weight, even if an event occurs in which the product sold by weight is placed in the shopping basket 80, the result is that the detection of the occurrence of a reading failure situation corresponding to that event is invalidated. Hereinafter, the invalidation of the detection of the occurrence of such a reading failure situation is also referred to as reading failure invalidation.

[0204] [About disabling read failure] With reference to FIG. 21(B), an example of setting the invalidation period in invalidating a read failure by the sales system of this embodiment will be described. In the figure, the same as in FIG. 21(A) from time t1 to time t6 (t6 p ) timing is shown. First, the mobile terminal device 40 sets a period (t10 to t11) consisting of a period from time t1 when the product information code is read to time t11, which is a time T2 from the time t1, and a period from time t1 to time t10, which is a time T1 before the time T1, as a first invalidation period TM1. Note that the lengths of time T1 and time T2 may be the same or different. During the first invalidation period TM1, detection of the occurrence of a reading failure situation in response to a customer placing products sold by weight in the shopping basket 80 is invalidated.

[0205] As a mode of read failure invalidation corresponding to the first invalidation period TM1, when a customer places a commodity sold by weight in the shopping cart 80 at time t2, which is later than time t1, the mobile terminal device 40 does not detect that a read failure has occurred, even if the captured image at that time has contents that are detected (determined) as a read failure. This allows the mobile terminal device 40 to not display a notice or the like related to the occurrence of a read failure even if the customer places a commodity sold by weight in the shopping cart 80. Also, in this case, since the mobile terminal device 40 does not transmit the read failure information to the transaction management server 50, it is also possible to prevent the store's monitoring device or the like from displaying a notice of the occurrence of a read failure (fraudulent activity).

[0206] Alternatively, the mobile terminal device 40 may detect (determine) that a reading failure has occurred based on the captured image at that time, but may not display a notice related to the occurrence of the reading failure or transmit the reading failure information to the transaction management server 50. In this case, the mobile terminal device 40, the transaction management server 50, etc. may store history information about the reading failure detected by the mobile terminal device 40.

[0207] In addition, as a mode of the read failure invalidation corresponding to the first invalidation period TM1, the customer puts the bulk product in the shopping basket 80 at time t2 before time t1. p If this is done in In this case, time t2 p When the bulk product is put into the shopping cart 80 at time t2, the reading of the product information code at time t1, which is the trigger for setting the first invalidation period TM1, has not yet been executed. p When bulk merchandise is placed in the shopping cart 80, the system detects the occurrence of a reading failure situation, displays information about the occurrence of the reading failure situation, and transmits information about the reading failure to the transaction management server 50. Thereafter, when the product information code is read at time t1, the portable terminal device 40 invalidates the detection of the occurrence of the reading failure corresponding to time t2p at this point. Specifically, if a notification or other display is being displayed in response to the detection of the occurrence of the reading failure corresponding to time t2p, the portable terminal device 40 stops the display. In addition, the portable terminal device 40 transmits a notification (invalidation notification) to the transaction management server 50 to invalidate the detection of the occurrence of the reading failure corresponding to time t2p. The transaction management server 50 deletes the reserved product information corresponding to the received invalidation notice from the cart information. The transaction management server 50 may also forward the received invalidation notice to a monitoring device. Upon receiving the invalidation notice, the transaction management server 50 stops reporting the corresponding reading failure situation. In this case, the mobile terminal device 40 or the transaction management server 50 may store a history of the detection of the occurrence of a reading failure state corresponding to the time t2p. In this way, the customer places the bulk goods in the shopping basket 80 at time t2, which is before time t1. p When the detection of the occurrence of a read failure state is performed at time t1, the detection is once treated as valid, but becomes invalid at the timing of time t1.

[0208] Furthermore, the mobile terminal device 40 sets the period from time t3 when the connection information code CD is read to time t12, which is the time T3, as the second invalidation period TM2. Time T3 may be determined based on the expected time from when the customer has the mobile terminal device 40 read the connection information code CD to when the customer completes the operation of issuing a label and the act of placing the priced merchandise sold by weight in the shopping cart 80. In the second invalidation period TM2, as in the first invalidation period TM1, detection of the occurrence of a reading failure situation in response to the placement of bulk products in the shopping basket 80 by a customer is also invalidated.

[0209] An example of a process procedure executed by the mobile terminal device 40 for invalidating a read failure will be described with reference to the flowcharts of FIGS. First, the flowchart in FIG. 22 shows an example of a process procedure that the mobile terminal device 40 executes in relation to setting the invalidation periods (first invalidation period TM1, second invalidation period TM2).

[0210] Step S301: The mobile terminal device 40 determines whether or not the product information code of a product sold by weight has been read during the product registration process.

[0211] Step S302: When reading the product information code of a product sold by weight, the mobile terminal device 40 sets a first invalidation period TM1 based on the time point at which the product information code was read this time.

[0212] Step S303: After processing of step S302, or if it is determined in step S301 that the reading of the product information code has not been performed, the mobile terminal device 40 determines whether or not it has performed reading of the connection information code CD displayed on the weighing pricing device 10 for connecting to the weighing pricing device 10. If the reading of the connection information code CD for connecting to the weighing and pricing device 10 is not executed, the process returns to step S301.

[0213] Step S304: When the connection information code CD for connecting to the weighing and pricing device 10 is read, the mobile terminal device 40 sets a second invalidation period TM2 based on the time point when the connection information code CD is read this time. After the process of step S304, the process returns to step S301.

[0214] The flowchart in Fig. 23 shows an example of a processing procedure executed by the mobile terminal device 40 in response to detection of the occurrence of a read failure state. The processing in the figure corresponds to a case where detection of the occurrence of a read failure state is performed regardless of whether or not it is an invalidation period, and then, during the invalidation period, display of a notice regarding the occurrence of a read failure state on the mobile terminal device 40 and transmission of read failure information from the mobile terminal device 40 are not performed.

[0215] Step S401: The mobile terminal device 40 waits for the occurrence of a read failure condition to be detected.

[0216] Step S402: When the occurrence of a reading failure state is detected, the mobile terminal device 40 determines whether the time point when the occurrence of the reading failure state is detected is included in the invalidation period (the first invalidation period or the second invalidation period TM2).

[0217] Step S403: If the invalidation period does not include the invalidation period, the mobile terminal device 40 transmits to the transaction management server 50 read failure information in response to the detection of the occurrence of the current read failure situation. Step S404: Furthermore, the mobile terminal device 40 causes the touch panel display unit 406 to display a message informing the user of the occurrence of a reading failure.

[0218] Step S405: After the process of step S404, or if it is determined in step S402 that the invalidation period is included, the mobile terminal device 40 stores detection history information indicating the history of detection of the occurrence of the current reading failure state. The mobile terminal device 40 may transmit the detection history information to the transaction management server 50, thereby causing the transaction management server 50 to store the detection history information. After the process of step S405, the process returns to step S401.

[0219] The flowchart in FIG. 24 shows an example of a processing procedure in which the mobile terminal device 40 invalidates the detection of the occurrence of a reading failure state before the time that is the reference time of the invalidation period. Step S501: The mobile terminal device 40 waits for the invalidation period to be set in step S302 or step S304 in FIG.

[0220] Step S502: When the invalidation period is set, the mobile terminal device 40 refers to the detection history information stored in itself or in the transaction management server 50.

[0221] Step S503: The portable terminal device 40 judges, as a result of referring to the detection history information in step S502, whether or not the occurrence of a reading failure has been detected during the currently set invalidation period.

[0222] Step S504: When it is determined that the occurrence of a reading failure state has been detected, if the mobile terminal device 40 is currently displaying a notification regarding the occurrence of the reading failure state on the touch panel display unit 406, the mobile terminal device 40 stops the notification. Step S505: When the portable terminal device 40 detects the occurrence of a reading failure situation, it transmits an invalidation notification regarding the detection of the occurrence of the reading failure situation to the transaction management server 50. In response to receiving the invalidation notification, the transaction management server 50 deletes the pending product information from the cart information. In response to receiving the invalidation notification, the transaction management server 50 can stop the notification of the occurrence of the reading failure situation being executed by the monitoring device.

[0223] <Second embodiment> Next, a second embodiment will be described. In this embodiment, the procedure for a customer to register a commodity sold by weight is different from that in the first embodiment as follows. In this embodiment, the product information panel 3000 is not provided in the area where the products sold by weight are displayed. In other words, in this embodiment, the product information code 3001 is not displayed in the area where the products sold by weight are displayed. The customer takes out the quantity of merchandise sold by weight that he or she wishes to purchase from among the displayed merchandise sold by weight, but at this time, the customer does not perform an operation to have the mobile terminal device 40 read the merchandise information code 3001.

[0224] A customer carries a commodity to be purchased and approaches the weighing pricing device 10. When approaching the weighing pricing device 10 from a location where the commodity is displayed, the customer may place the commodity to be purchased in a shopping basket 80 placed in a shopping cart.

[0225] In the standby mode, the weighing pricing device 10 of this embodiment displays a pricing operation screen as a standby screen to be displayed on the customer display unit 106. Fig. 25 shows an example of the pricing operation screen in this embodiment. The pricing operation screen in the figure has a weighing result area AR41. The weighing result area AR41 is an area (column) that displays the weighing results of the bulk product to be priced. The weighing result area AR41 includes a weight area AR41-1, a price per unit weight area AR41-2, and a total price area AR41-3. The weight area AR41-1 is an area in which the measured weight of the item sold by weight to be priced is shown. The price per weight area AR41-2 is an area in which the price per weight of the commodity sold by weight to be priced is shown.

[0226] Among the products sold by weight, there are some that are sold by number, in which the number of items is calculated based on the measured weight and unit weight, and the price is calculated based on the calculated number of items and the unit price per item. In the case of such products sold by weight, the weight area AR41-1 may display the number of items calculated based on the measured weight and unit weight, and the weight unit price area AR41-2 may display the unit price per item. The total amount area AR41-3 is an area showing the total amount of the prices of the bulk items for which pricing has been completed up to this point in the same transaction.

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

[0228] In the example shown in the figure, tab TB-1 is labeled "FRUITS." On the sheet corresponding to tab TB-1, product buttons BT4 for each product sold by weight that is classified as fruit are arranged. Tab TB-2 is labeled "VEG." On the sheet corresponding to tab TB-2, product buttons BT4 (preset keys) for products sold by weight that are classified as vegetables are arranged in a predetermined order. Such a sheet configuration in the pricing screen corresponds to a case in which fruit and vegetable products are sold as bulk products.

[0229] The arrangement order of the product buttons BT4 on the sheet may be determined based on purchase history or a preset priority order, such as by product code or product name. If the number of products in a category corresponding to one tab TB exceeds the number of product buttons BT4 that can fit on one sheet, multiple sheets may be switched by page forwarding or scrolling the sheet.

[0230] In addition, a message area ARm is arranged on the upper side of the product selection area AR42. The message area ARm is an area in which a message with a predetermined content according to the content of the current screen is displayed. In the message area ARm in the same figure, "Please select a product" is displayed. In other words, in this case, the message area ARm displays a message instructing the customer to operate the product button BT4 to specify the item of the product to be priced.

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

[0232] On the initial pricing operation screen, as shown in the figure, either tab TB-1 or TB-2 is selected. A customer who visits the weighing pricing device 10 is asked to price (register) each item of the bulk product to be purchased. The customer then first selects one item from among the bulk products to be purchased as the item to be priced. At this time, if the tab TB corresponding to the category of the bulk product selected as the item to be priced has not been selected, the customer performs an operation to select the tab TB corresponding to the category of the bulk product to be priced. In the same figure, for example, a customer selects "cabbage" as the item to be priced from among the bulk items to be purchased, and then selects tab TB-2, which corresponds to vegetables, the category to which cabbage corresponds.

[0233] In the figure, in response to the selection of tab TB-2, product buttons BT4 for each product sold by weight classified as vegetables are arranged on the sheet. Note that, although only the product name is displayed on the product button BT4 in the figure, for example, an image representing the product may also be displayed in addition to the product name. In this case, the customer is pricing cabbage, so he or she operates the product button BT4 on the sheet that displays the product name "cabbage." In other words, the customer performs an operation to specify that the item of the bulk product to be priced is "cabbage."

[0234] In response to the operation of the commodity button BT4, a guidance screen (not shown) is displayed on the customer display unit 106, which guides the customer to place the cabbage designated as the commodity to be priced on the weighing platform 109b and weigh it. The customer places the cabbage, which is the commodity to be priced, on the weighing platform 109b.

[0235] When the cabbage is placed on the weighing platform 109b, the weighing and pricing device 10 performs weighing and pricing processing according to the weighing result. That is, the weighing and pricing device 10 in this case calculates the price of the cabbage based on the weight of the weighed cabbage and the weight unit price of the cabbage.

[0236] Upon completion of the pricing process, the weighing and pricing device 10 causes the customer display unit 106 to display a weighing result screen. Fig. 26 shows an example of a weighing result screen. In this figure, the same parts as in Fig. 25 are given the same reference numerals and the description will be omitted as appropriate. In the weighing result screen of the same figure, the weighing result area AR41 has changed so that the weight of the cabbage is shown in the weight area AR41-1, the price per weight of the cabbage is shown in the price per weight area AR41-2, and the total amount based on the calculated price of the cabbage is shown in the total amount area AR41-3.

[0237] Also, on the weighing result screen, a label print button BT16 is arranged. Then, in the message area ARm, a message such as "Please press the print button" is displayed, urging the customer to operate the label print button BT16 to print a label (single item label) reflecting the cabbage pricing processing result.

[0238] In this embodiment, the procedure of operating the product button BT4 corresponding to the bulk product to be priced as described above, placing the bulk product to be priced on the weighing platform 109b, and causing the weighing pricing device 10 to execute the pricing process is the same for customers who register products using the mobile terminal device 40 and customers who do not use the mobile terminal device 40. Then, customers who do not use the mobile terminal device 40 to register the product are prompted to operate the label issuing button BT16. In response to the operation of the label issuing button BT16, the weighing pricing device 10 finalizes the pricing performed by the current pricing process, and issues a label (single item label) on which information reflecting the finalized pricing result for the cabbage is printed. The label issued in this case has a code (barcode or two-dimensional code) printed on it. The code printed on the label contains information necessary for settlement at the POS terminal operated by the store clerk, such as the product code and price.

[0239] In addition, the connection information code CD is displayed on the weighing result screen. A customer who uses the mobile terminal device 40 to register a product sold by weight performs an operation to have the mobile terminal device 40 read the connection information code instead of operating the label issuing button BT16. By reading the connection information code CD, the portable terminal device 40 establishes a communication connection with the weighing pricing device 10. In response to the establishment of the connection with the portable terminal device 40, the weighing pricing device 10 finalizes the pricing by the current pricing process and transmits product pricing information for the cabbage to the portable terminal device 40. The weighing pricing device 10 also issues a label (single item label) on which content reflecting the finalized pricing result for the cabbage is printed. In this way, the label issued in response to the communication connection with the portable terminal device 40 does not need to have a code printed on it. The weighing pricing device 10 may transmit commodity registration information based on the commodity pricing information transmitted to the mobile terminal device 40 to the transaction management server 50 via a communication line.

[0240] Although not shown in the figure, after the label is issued, the weighing result screen may be switched to a label application guide screen. The label application guide screen displays messages, pictures, and the like to guide the user to apply the label issued by the weighing and pricing device 10 to the bag containing the cabbage that has just been priced.

[0241] When the label is issued, the customer lifts the cabbage from the weighing platform 109b and attaches the label taken out from the label outlet 110a to the bag containing the cabbage. At this time, the customer may place the bag of cabbage with the label attached in the shopping basket 80 placed on the shopping cart.

[0242] The label attachment guidance screen may be erased, for example, when a sensor provided at the label outlet 110a detects that a label has been removed. When the label attachment guidance screen is erased, the customer display unit 106 may transition to displaying a pricing operation screen for specifying the item of the next bulk commodity to be priced.

[0243] Even in the case of self-registration of bulk products in this embodiment, as a customer goes through the procedure of registering bulk products to be purchased, it may be determined (detected) that a reading failure situation has occurred due to non-scan input on two occasions when the customer places a bulk product in the shopping basket 80 in response to one bulk product. This point will be described with reference to FIG. 27(A).

[0244] FIG. 27(A) shows, over time, the timing at which certain events occur according to the procedure when a customer registers products at a bulk sales counter in this embodiment. When a customer goes to a place where bulk sales items are displayed in a bulk sales counter, first, at time t21, the customer takes out the item he / she wishes to purchase from the displayed items and places the taken-out item in the shopping basket 80 placed on the shopping cart. At this time, the portable terminal device 40 placed in the holder 71 of the shopping cart detects the occurrence of a reading failure situation. After that, the customer goes to the weighing pricing device 10 and operates the product button BT4 at time t22 to specify the product to be priced. After that, the customer places the product to be priced on the weighing platform 109b. As a result, at time t23, the weighing pricing device 10 executes the weighing and pricing process, and at time t24, displays the weighing result screen including the connection information code CD. At time t25, the customer operates the portable terminal device 40 to read the connection information code CD displayed on the weighing result screen, thereby establishing a connection between the portable terminal device 40 and the weighing pricing device 10. As a result, the weighing pricing device 10 confirms the pricing process result, transmits product pricing information to the portable terminal device 40, and issues a label. The customer then attaches the issued label to a bag containing the products to be priced, and places the bag in the shopping cart 80 at time t26. At this time, the portable terminal device 40 placed in the holder 71 of the shopping cart detects the occurrence of a reading failure situation.

[0245] In this way, even under the registration procedure for bulk products in this embodiment, the occurrence of a read failure state is detected at time t21 when a displayed bulk product is placed in shopping basket 80, and at time t26 when a priced bulk product is placed in shopping basket 80. It is preferable that the occurrence of such a read failure state is also invalidated.

[0246] Therefore, in this embodiment, by setting the invalidation period TM11 as shown in FIG. 27(B), detection of the occurrence of a reading failure state at the timings of time t21 and time t26 is invalidated. Specifically, in response to reading the connection information code CD at time t25, the mobile terminal device 40 sets the invalidation period TM11 based on the time t25. That is, the mobile terminal device 40 sets the period from time t25 to time t31, which is the time T11 back, and the period from time t25 to time t32, which is the time T12, as the invalidation period TM11 (t31 to t32). Time T11 may be set based on the time expected to be required from when a customer picks up a commodity to be purchased from among the displayed commodity sold by weight, places it in the shopping basket 80, and has the connection information code CD read by the mobile terminal device 40. Time T12 may be set based on the time expected to be required from when an operation is performed to have the mobile terminal device 40 read the connection information code CD, to when the commodity sold by weight with a confirmed price is placed in the shopping basket 80.

[0247] Then, the mobile terminal device 40 may execute the same processing as in Figures 23 and 24. As a result, an event in which a by-weight product, the price of which has been confirmed, is placed in the shopping basket 80 at the timing corresponding to time t26 is not treated as a reading failure situation, and for example, a notification regarding the occurrence of a reading failure situation is not executed. Also, an event in which a by-weight product is placed in the shopping basket 80 at the timing corresponding to time t21 is once treated as a reading failure situation, but at time t25, an invalidation period TM11 is set, and the event is invalidated so as not to be treated as an occurrence of a reading failure situation.

[0248] In this embodiment, for example, when a customer is trying to purchase multiple items of bulk products, the customer may place the bulk products in the shopping basket 80 multiple times in a location where the bulk products are displayed. In this case, the mobile terminal device 40 will detect the occurrence of a reading failure every time a bulk product is placed in the shopping basket 80. Thereafter, when the customer has the portable terminal device 40 read the connection information code corresponding to the bulk commodity that was initially targeted for pricing, and an invalidation period TM11 is set, all past reading failure situations that are to be included in the set invalidation period TM11 are invalidated.

[0249] <Additional information regarding focus control of mobile terminal devices> As a supplement to the embodiment, three examples of focus control applicable to the imaging unit 408 of the mobile terminal device 40 during code scanning in a situation where the shopping application of the embodiment is running will be described below.

[0250] [Focus control: Example 1] In a first example of focus control, a shopping application applies autofocus control of the camera (imaging unit 408) of the mobile terminal device 40 such as a smartphone to the code scan function. When a customer has a code (such as a product code or a connection information code) read by the mobile terminal device 40, it is preferable that the customer does not have to adjust the distance or angle between the mobile terminal device 40 and the code as much as possible. When the autofocus control of a smartphone camera is applied to reading a code, the camera is controlled to focus on the code, so the code is easily focused on without the above adjustment. However, in this case, for example, when the mobile terminal device 40 is attached to a shopping cart so as to capture an image of the inside of the shopping cart 80, the camera may automatically focus on the barcode of a product already contained in the shopping cart 80, which may result in a product that has already been registered being registered twice.

[0251] [Focus control: Example 2] In a second example of focus control, a shopping application controls the focus mechanism of a camera (imaging unit 408) to repeatedly change the focal length to near or far, so as to focus on the code. When a customer has a portable terminal device 40 running a shopping application read a code (such as a product code or a connection information code), it is preferable that the customer does not have to adjust the distance between the portable terminal device 40 and the code as much as possible. With the focus control of this example, the focal length is changed, so that the customer can reliably focus on the code as long as the customer keeps the code within the imaging range and maintains a certain distance between the portable terminal device 40 and the code. In other words, in this case, the customer does not need to adjust the code by moving it closer to or farther away from the portable terminal device 40 in order to have the code read. However, with the focus control of this example, the focal length is changed by a relatively large amount, so the entire captured image also changes greatly and repeatedly. This is disadvantageous in determining whether or not to insert a non-scanned item based on a change in the state of the shopping cart 80. In addition, there is a possibility that the recognition accuracy will be low for image recognition and other processes for purposes other than code scanning.

[0252] [Focus control: Example 3] A third example of focus control is where a shopping application controls the camera (imaging unit 408) to fix the focal length at a predetermined value. With this type of focus control, it is difficult to focus on the code in the captured image, and the image portion of the code is likely to become blurred. However, depending on the code recognition capabilities of the shopping application, it may be possible to read the code normally even if it is somewhat blurred, and product registration, etc. may not be hindered. For example, in the case of autofocus control, there is a possibility of a malfunction in which the focus is automatically set on the code of a product in the shopping basket 80 and the product is registered. The focus control of this embodiment can prevent such a malfunction. In this example, the fixed focal length may be set based on the characteristics of the device as a camera corresponding to the imaging unit 408, the distance between the code and the mobile terminal device 40 that is expected when a customer has the code read, and the like. Also, a focal length value appropriate for the model of the mobile terminal device 40 as a smartphone may be set, or a function may be provided in the mobile terminal device 40 to automatically set the focal length depending on the code reading situation.

[0253] In addition, the focus control may be switchable between two or more of the first to third examples. The focus control may be switched manually by a customer (user), for example, or the mobile terminal device 40 may determine which focus control is appropriate based on the state of an image captured by the imaging unit 408 when the customer scans the code, and switch the focus control. For example, in a situation where it takes a certain amount of time for the code to be focused and readable, the mobile terminal device 40 may switch to another focus control. Alternatively, the mobile terminal device 40 may switch the focus control based on, for example, the customer's age or the degree of familiarity with the code scan operation. The degree of familiarity with the operation may be determined by the mobile terminal device 40 based on, for example, the time elapsed since the shopping application was installed, the number of times the shopping application was started, the cumulative operation time, etc.

[0254] <Additional information regarding images taken during product registration> As shown in FIG. 11(C), FIG. 19(B), etc., a scan image area AR11 is arranged on the product registration screen displayed on the mobile terminal device 40. In the scan image area AR11, a captured image captured by the imaging unit 408 is displayed. However, in the scan image area AR11, the entire captured image is not displayed, but a predetermined partial area is displayed. The captured image displayed in the scan image area AR11 may be, for example, an area occupying about the upper 1 / 3 to 1 / 2 of the entire area. In this case, the mobile terminal device 40 may use the area displayed in the scan image area AR11 out of the entire captured image as an area to be used for code detection, and may exclude other areas so as not to be used for code detection. When the customer has the mobile terminal device 40 read the product code, the customer adjusts the scan image area AR11 so that the code (product code or connection information code) fits within the scan image area AR11. At this time, the captured image displayed in the scan image area AR11 is limited to a part of the entire area as described above, making it easier for the customer to scan the code. In addition, it is possible to display other areas such as the product registration status area AR12 on the product registration screen, making it possible to provide a product registration screen that is easy for the customer to use. On the other hand, for example, when detecting non-scan insertion, the entire area of ​​the captured image may be used. That is, the mobile terminal device 40 performs detection of non-scan insertion, etc., not only for the area of ​​the captured image that is displayed on the product registration screen, but also for the area that is not displayed on the product registration screen. This makes it possible to provide an easy-to-use product registration screen as described above, and by using the entire area of ​​the captured image, detection of non-scan insertion, etc. can be performed on the entire shopping cart 80.

[0255] <Modification> A modification of this embodiment will now be described.

[0256] [First Modification] In the above-mentioned sales area that supports bulk sales, bulk products may be sold. Bulk products are, for example, fresh foods such as vegetables, fruits, and fish, which have a set unit price per unit but cannot be assigned a product code in advance. As an example, if a store sells apples as a single item, a customer can register the apples as follows: In this case, the customer has the mobile terminal device 40 read the product information code 3001 for apples. As a result, apples as individual products are set as the item to be registered. In response to this, a registration operation screen is displayed on the mobile terminal device 40, indicating that apples as individual products have been set as the item to be registered, and prompting the customer to input the number of apples to be registered. The customer performs an operation on the registration operation screen to input the number of apples (quantity) that he or she wishes to purchase as the registration quantity. In response to the input of the registration quantity, the mobile terminal device 40 calculates the price based on the input registration quantity and, for example, the unit price per apple (which may be the unit price by weight depending on the item). In the case of individual products, unit price information may be included in the product information code. This allows the mobile terminal device 40 to obtain unit price information by reading the product information code. Alternatively, the mobile terminal device 40 may obtain the unit price associated with the item read from the product information code from the transaction management server 50. The price may be calculated by the transaction management server 50 based on the information on the item and purchase quantity sent from the mobile terminal device 40 and, for example, unit price information stored in the transaction management server 50. By acquiring the information on the item, purchase quantity, and price in this way, the registration of the apples as a loose product is completed. In this way, in the case of loose products, there is no need to weigh the products using the weighing and pricing device 10.

[0257] In this way, when registering loose products by self-registration, if a customer places a loose product that is on display in the shopping basket 80, an event corresponding to a reading failure occurs, just as with bulk products. In other words, when loose products are self-registered as described above, at time t2 or time t2 in FIG. 21(B), p As a result, an event corresponding to a reading failure occurs when a loose product is placed in the shopping cart 80.

[0258] For such self-registration of loose products, by executing the same control of invalidating read failure as in the first embodiment, it is possible to invalidate detection of the occurrence of a read failure situation when a customer places loose products in the shopping cart 80. However, in the case of self-registration of loose products, in the flowchart of Fig. 22, processing corresponding to setting the first invalidation period in steps S301 and S302 is executed, and steps S303 and S304 may be omitted.

[0259] Furthermore, self-registration of loose products may be performed by using the weighing pricing device 10 according to the product registration procedure in the first embodiment. In this case, the customer has the mobile terminal device 40 read the product information code 3001 of the loose apples, places the apples in the shopping basket 80, and goes to the weighing pricing device 10. The customer has the portable terminal device 40 read the connection information code CD displayed on the standby screen of the weighing pricing device 10 at the destination, and connects the portable terminal device 40 to the weighing pricing device 10. The customer operates the pricing operation screen to specify apples, and then specifies the number of apples to purchase. In the case of loose products, there is no need to place them on the weighing platform 109b and weigh them. In response to this operation, the weighing pricing device 10 calculates the price based on the specified purchase quantity and the unit price per unit number (unit price) set for the apples, and displays the weighing result screen. The customer performs an operation to instruct label printing on the weighing result screen (operation of label printing button BT15) to finalize the pricing process result and print a label. The customer attaches the printed label to the bag containing the apples.

[0260] Furthermore, self-registration of loose products may be performed by using the weighing and pricing device 10 according to the product registration procedure in the second embodiment. In this case, the customer takes out apples, which are the individual products to be purchased, from the display area, places them in shopping basket 80, and proceeds to weighing pricing device 10. The customer performs an operation to specify apples as the product to be priced on weighing pricing device 10, and then performs an operation to specify the number of apples to be purchased. In this case, too, it is not necessary to place the apples, which are the individual products, on weighing platform 109b and weigh them. The weighing pricing device 10 calculates the price based on the unit price of the apples and the specified number of apples to purchase, and displays a weighing result screen including the connection information code CD. The customer connects the portable terminal device 40 to the weighing pricing device 10 by having the portable terminal device 40 read the connection information code CD. Once communication with the portable terminal device 40 has been established, the weighing pricing device 10 confirms the results of the current pricing process, transmits product pricing information to the portable terminal device 40, and issues a label. The customer attaches the issued label to the bag containing the apples.

[0261] As described above, when self-registering loose products using the weighing pricing device 10 according to the product registration procedure in the first or second embodiment, an event corresponding to a reading failure occurs when a customer places a loose product that was displayed in the shopping basket 80, just like with products sold by weight. Also, for example, an event corresponding to a reading failure occurs when a customer removes a bag containing loose products that was placed in the shopping basket 80, affixes a label, and then places the bag containing the loose products back in the shopping basket 80. In this case, by executing the same control for invalidating a reading failure as in the first or second embodiment, it is possible to invalidate the detection of the occurrence of a reading failure situation when a customer places loose items in the shopping cart 80.

[0262] [Second modified example] In each of the above embodiments, the setting of the invalidation period may be changed as appropriate. For example, in the first embodiment, the self-registration procedure involves having the mobile terminal device 40 read the product information code 3001 and then removing the product from the display area. In such a case, the invalidation period TM1 may exclude the period from time t1 to time t10, which is the time T1 back, and may be limited to the period from time t1 to time t11, which is the time T2. Conversely, if the self-registration procedure involves removing the product from the display area before having the mobile terminal device 40 read the product information code 3001, the invalidation period TM1 may be limited to the period from time t1 to time t10, which is the time T1 back, and may exclude the period from time t1 to time t11, which is the time T2.

[0263] Also, for example, if the self-registration procedure prevents a product from being placed in the shopping cart 80 when it is removed from the display area, the invalidation period TM1 in the first embodiment may not be set. In the second embodiment, the period corresponding to time T11 may be excluded, and the invalidation period TM11 may be set based on the period corresponding to time T12. Conversely, if the self-registration procedure prevents products from being placed in the shopping cart 80 after the pricing process result is finalized, the invalidation period TM2 in the first embodiment may not be set. In the second embodiment, the period corresponding to time T12 may be excluded, and the invalidation period TM11 may be set to the period corresponding to time T11.

[0264] [Third Modification] In this modified example, as a procedure for self-registration, for example, a case is taken in which after the product information code 3001 is read at time t1 in Figure 21 (A), a product taken from the display area may be placed in the shopping cart 80, but no products are placed in the shopping cart 80 before time t1. In such a case, the first invalid period TM1 may be set so that the timing when the product is placed in the shopping cart 80 is between time t1 when the product information code 3001 is read and time t3 when the connection information code CD is read. By setting the first invalid period TM1 in this manner, under the self-registration procedure of this modified example, it is possible to reliably invalidate detection of the occurrence of a reading failure situation occurring in response to a customer placing a product taken out of a display area in the shopping cart 80. The second invalid period TM2 may be set in the same manner as in FIG. 21(B).

[0265] [Fourth Modification] In the first embodiment, the invalidation period TM1 is set in response to the portable terminal device 40 reading the product information code 3001, and thereafter, the invalidation period TM2 is set in response to the portable terminal device 40 reading the connection information code CD. When the mobile terminal device 40 is to read the product information code 3001 and the connection information code CD, the customer holds the mobile terminal device 40 placed in the holder 71 in his / her hand so that the product information code 3001 and the connection information code CD can be imaged. In other words, when the mobile terminal device 40 is to read the product information code 3001 and the connection information code CD, the mobile terminal device 40 is moved as if it were being taken out of the holder 71.

[0266] Therefore, instead of using the reading of the product information code 3001 and the connection information code CD as a trigger for setting the invalidation periods TM1 and TM2, the mobile terminal device 40 may use the detection of its own movement in response to being removed from the holder 71 as a trigger. In this case, the mobile terminal device 40 may be provided with a motion sensor such as a gyro sensor, an angular velocity sensor, etc. In addition, the mobile terminal device 40 may set an invalidation period TM1 in response to a first motion being detected by the motion sensor, and may set an invalidation period TM2 in response to a second motion being detected within a certain time period from the time the first motion was detected. In the second embodiment, the mobile terminal device 40 may set the invalidation period TM11 in response to detection of motion by the motion sensor.

[0267] [Fifth Modification] In each of the above embodiments, the invalidation period is set without any particular restriction in response to the mobile terminal device 40 reading the product code of a product sold by weight or the connection information code corresponding to a weighing pricing device. In contrast, in this modified example, there may be cases where the invalidation period is not set even if the mobile terminal device 40 reads the product information code of a commodity sold by weight or the connection information code corresponding to a weighing pricing device. For this purpose, for example, when the mobile terminal device 40 reads the product information code of a commodity sold by weight or the connection information code corresponding to a weighing pricing device, the mobile terminal device 40 may determine whether or not to set the invalidation period with a certain probability, for example, by generating random numbers. If the invalidation period is not set, when a customer places a bulk product in shopping cart 80, a reading failure occurs as a non-scanned input, and the product is registered as a reserved product, so a store clerk must handle the situation and perform an operation to release the reserved product. For this reason, if there is a certain probability that the invalidation period will not be set, as in this modified example, it is possible to prevent fraudulent behavior such as a malicious customer pretending to register a bulk product, but placing it in shopping cart 80 and not purchasing it.

[0268] [Sixth Modification] In the above embodiment, the invalidation period is set in response to the registration of a product sold by weight (and a product sold individually). The invalidation period may be set when registering a product other than a product sold by weight that normally has a product code attached (hereinafter, also referred to as a normal product). In the case of a regular product, a typical action of a customer who has registered the product is to take the regular product from the product shelf, have the mobile terminal device 40 read the product code of the product, and then place the regular product in the shopping cart 80. However, in reality, the patterns of actions taken in response to the registration of such products are diverse and difficult to predict. For this reason, even if the customer has no intention of committing any fraudulent acts, the action related to registration that the customer happens to take at that time may be determined to be a non-scan insertion. As a specific example, if a certain amount of time passes between when a customer has had their product code read and when they place the product in the shopping basket 80 for some reason, it may be determined that the product was placed in the shopping basket 80 without being scanned. Also, if a product is placed in the shopping basket 80 within a standard time after the product code is read, but the product is then moved and organized within the shopping basket 80, it may be determined that the product was placed in the shopping basket 80 without being scanned, depending on the change in the captured image while the product is being organized.

[0269] Therefore, in this modified example, an invalidation period is set when registering a regular product. As a specific example, the invalidation period may be set until a certain time has elapsed from the time when the mobile terminal device 40 reads the product code of the regular product. This makes it possible to avoid the above-mentioned erroneous determination that the product was entered without being scanned.

[0270] The length of the invalidation period in this modified example may be changed depending on the product, customer, etc. For example, it takes longer for a large or heavy product to be placed in the shopping cart 80 than other products. Therefore, for example, based on the settings in the product information, a longer invalidation period than the standard may be set for such large or heavy products. Also, for example, if the customer is over a certain age based on membership information, etc., a longer invalidation period than the standard may be set.

[0271] [Seventh Variation] In the above embodiment and modified examples, a part of the processes executed by the mobile terminal device 40, the weighing and pricing device 10, the settlement device 20, etc. may be executed by a higher-level device such as the transaction management server 50. As one of the above aspects, the sales system of this embodiment may be provided with the configuration of a thin client system. As an example, the transaction management server 50 or another server may be configured as a thin client-compatible server (e.g., a cloud server), and the mobile terminal device 40, the weighing pricing device 10, the settlement device 20, etc. may function as thin clients. In this case, the thin client terminals, such as the mobile terminal device 40, the weighing pricing device 10, the settlement device 20, etc., transmit captured images and information such as commands corresponding to operations performed on themselves to the cloud server. The cloud server may execute processing in response to information received from the thin client terminal, and transmit image data or web page data as a screen reflecting the processing results to the thin client terminal. The mobile terminal device 40, the weighing pricing device 10, the settlement device 20, etc., as thin client terminals, display the transmitted image data or web page data by an image viewer or web browser. In the above embodiment, for example, a mobile terminal device 40, which is a thin client terminal, may transmit an image to a cloud server, and based on the image received by the cloud server, product registration processing, detection of the occurrence of a reading failure situation, control of invalidating the reading failure, etc. may be performed.

[0272] [Eighth Modification] The above-described embodiments and modifications may be combined as appropriate.

[0273] <Summary of the embodiment> [Technical field] The present invention relates to a product sales data processing system. [Background technology] 2. Description of the Related Art A system is known in which a customer registers an item by himself / herself using a mobile terminal equipped with a camera (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2018-147252 A [Summary of the Invention] [Problem to be solved by the invention] In a system in which customers themselves register products using mobile terminals as described above, it is preferable to be able to detect fraudulent behavior by customers when registering products. However, depending on the circumstances of product registration, there are cases in which a customer's registration is determined to be fraudulent even though the customer has performed the registration work in accordance with the proper procedures. The present invention has been made in consideration of the above circumstances, and has an object to enable appropriate fraudulent activity determination to be made depending on the customer's circumstances during product registration.

[0274] [Means for solving the problem] (1) As described above, one aspect of this embodiment is a product sales data processing system (sales system) that registers products using a mobile terminal (e.g., mobile terminal device 40) operated by a customer in a store, and the product sales data processing system includes a reading means for reading a code, a detection means for detecting the occurrence of a read failure situation in which a customer secures a product whose product code has not been read by the reading means, a display means for displaying information regarding the read failure situation detected by the detection means, and an invalidation means for performing invalidation control (steps S301 to S304, S401 to S405, S501 to S505) that results in the detection of the read failure situation being invalidated in response to the occurrence of the read failure situation based on the timing at which a predetermined code (product information code 3001, connection information code CD) is read by the reading means.

[0275] According to the above configuration, for example, when the product information code 3001 or the connection information code CD is read at a sales counter for products sold by weight (or products sold individually), it is possible to cause a result in which the detection of the occurrence of a read failure state is invalidated. Here, causing a result in which the detection of the occurrence of a read failure state is invalidated includes invalidating the occurrence of a read failure state that has been detected. This allows for an appropriate determination of fraudulent activity to be made depending on the customer's circumstances during product registration.

[0276] (2) One aspect of this embodiment is the product sales data processing system described in (1), wherein the specified code is a product information code identifying a product sold by weight or a product sold individually, and the invalidation means applies the invalidation control to at least one of the occurrence of the reading failure situation up to a specified time before the time when the product information code is read by the reading means and the occurrence of the reading failure situation up to a specified time after that (steps S301, S302, S401 to S405, S501 to S505).

[0277] According to the above configuration, even if a customer takes out a product from the display area and places it in the shopping cart 80 in response to the mobile terminal device 40 reading the product information code 3001 provided at the product display area, the product information code 3001 can be prevented from being treated as a reading insufficient situation.

[0278] (3) One aspect of this embodiment is a product sales data processing system as described in (1) or (2), wherein the specified code is a device code (connection information code CD) that identifies a device that performs pricing processing for products sold by weight or products sold individually, and the invalidation means applies the invalidation control to at least one of the occurrence of the reading failure situation up to a specified time before the time when the device code is read by the reading means and the occurrence of the reading failure situation up to a specified time after that (steps S303, S304, S401 to S405, S501 to S505).

[0279] The connection information code CD uniquely identifies the weighing and pricing device 10 connected to the mobile terminal device 40, and therefore functions as a device code for identifying the device. According to the above configuration, when the portable terminal device 40 reads the connection information code CD for connecting to the weighing pricing device 10, even if a customer places a priced and labeled product in the shopping basket 80, the product is not treated as being in a reading insufficient state.

[0280] (4) One aspect of this embodiment is a product sales data processing system as described in any one of (1) to (3), wherein the specified code includes a product code identifying a product sold by weight or a product sold individually, and an equipment code identifying an equipment that performs pricing processing for the products sold by weight or the products sold individually, and the invalidation means applies invalidation processing to the occurrence of the reading failure situation from the time the product code is read by the reading means to the time the equipment code is read.

[0281] According to the above configuration, it is possible to reliably prevent an event in which a customer places a product that he or she has taken out of the display area and placed in the shopping basket 80 after the product information code 3001 has been read from being treated as a reading failure situation.

[0282] (5) One aspect of this embodiment is a product sales data processing system described in any one of (1) to (4), wherein the reading means reads the code from an image captured by an imaging means (imaging unit 408) during a reading operation in which a customer causes a mobile terminal to read a code, and the detection means detects the occurrence of the reading failure situation based on a change in the image obtained by the imaging means provided to capture an image of the product reserved by the customer.

[0283] In the above configuration, the reading means reads the code from an image captured by the imaging means, which captures a reading operation in which the customer causes the portable terminal to read the code, and the detection means detects the occurrence of a reading failure situation based on a change in the image captured by the imaging means provided to capture an image of the product acquired by the customer. With this configuration, it becomes possible to read the code and detect the occurrence of a reading failure situation based on the captured image captured by the imaging unit 408 included in the mobile terminal device 40.

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

[0285] 10 (10-1, 10-2, 10-3) weighing and pricing device, 20 (20-1, 20-2) settlement device, 30 management device, 40 portable terminal device, 50 transaction management server

Claims

1. A product sales data processing system for registering products using a mobile terminal operated by a customer at a store, A reading means for reading the code; a detection means for detecting an occurrence of a reading failure situation in which a customer acquires a product whose product code has not been read by the reading means; a display means for displaying information regarding the read failure state detected by the detection means; an invalidation means for applying invalidation control to at least one of the occurrence of the reading failure state up to a predetermined time before the time point when the predetermined code is read by the reading means and the occurrence of the reading failure state up to a predetermined time after the time point, which results in invalidating detection of the reading failure state according to the occurrence of the reading failure state; A product sales data processing system comprising:

2. The predetermined code is a product information code that identifies a product sold by weight or a product sold individually.

2. The product sales data processing system according to claim 1.

3. The predetermined code is a device code that identifies a device that performs pricing processing for bulk or individual products.

2. The product sales data processing system according to claim 1.

4. A product sales data processing system for registering products using a mobile terminal operated by a customer at a store, A reading means for reading the code; a detection means for detecting an occurrence of a reading failure situation in which a customer acquires a product whose product code has not been read by the reading means; a display means for displaying information regarding the read failure state detected by the detection means; an invalidation means for applying an invalidation process to the occurrence of the reading failure state from the time when the reading means reads a product code identifying the bulk product or the loose product to the time when a device code identifying a device that performs a pricing process for the bulk product or the loose product is read; A product sales data processing system comprising:

5. The reading means reads the code from a captured image captured by an imaging means of a reading operation by the customer to have the portable terminal read the code, The detection means detects the occurrence of the reading failure state based on a change in an image captured by an imaging means provided to capture an image of the product acquired by the customer.

5. A product sales data processing system according to claim 1.

6. A computer in a product sales data processing system for registering products using a mobile terminal operated by a customer at a store, A reading means for reading the code; a detection means for detecting an occurrence of a reading failure situation in which a customer secures a product whose product code has not been read by the reading means; a display means for displaying information regarding the reading failure state detected by the detection means; a nullifying means for applying a nullifying control to at least one of the occurrence of the reading failure state up to a predetermined time before the time point when the predetermined code is read by the reading means and the occurrence of the reading failure state up to a predetermined time after the time point, which results in the detection of the reading failure state in accordance with the occurrence of the reading failure state being invalid; A program to function as a

7. A computer in a product sales data processing system for registering products using a mobile terminal operated by a customer in a store, A reading means for reading the code; a detection means for detecting an occurrence of a reading failure situation in which a customer secures a product whose product code has not been read by the reading means; a display means for displaying information regarding the reading failure state detected by the detection means; An invalidation means for applying an invalidation process to the occurrence of the reading failure state from the time when the reading means reads the product code identifying the bulk product or the loose product to the time when the device code identifying the device that performs the pricing process for the bulk product or the loose product is read. A program to function as a

Citation Information

Patent Citations

  • Automatic commodity adjustment system

    JP1996147560A

  • Commodity recognition device and commodity recognition program

    JP2017146986A

  • Check apparatus and check program

    JP2018147252A

  • Commodity data processing system and commodity data processing method

    JP2019204550A

  • Server device, control program for server device, and control method for server device

    JP2019204551A

Cited By

  • Commodity sales data processing system

    JP2024180689A