Portable terminal device

Abstract

To allow shopping to be performed smoothly.SOLUTION: A terminal device includes positional information acquisition means, shop specifying information acquisition means, registration means, determination means, and notification means. The positional information acquisition means acquires positional information indicating a current place. The shop specifying information acquisition means acquires shop specifying information presented in a shop. The registration means starts commodity registration in response to establishment of a start condition which is one of a first condition that the shop is specified using the positional information and a second condition that the shop is specified using the shop specifying information. The determination means performs a valid determination as to whether the commodity registration is performed validly. The notification means performs error notification using a result of the determination performed by the determination means. The notification means performs the notification based on the established start condition.SELECTED DRAWING: Figure 18

Description

[Technical field]

[0001] The present invention relates to a mobile terminal device. [Background technology]

[0002] In recent years, a system has become known in which a shopping application is installed on a mobile terminal device such as a smartphone carried by a customer, and the customer registers products by themselves in a store (see, for example, Patent Document 1). The mobile terminal device periodically checks its own location, and if it is not located within the store, it reports an error. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2013-541107 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, there is a problem that if an error is frequently reported, the customer may not be able to shop smoothly. For example, in an environment where it is difficult to obtain location information, such as when the store is located underground, the mobile terminal device may determine that it is not located within the store and may report an error frequently.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique that enables shopping to be carried out smoothly. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, a terminal device according to one embodiment of the present invention comprises: a location information acquisition means for acquiring location information indicating a current location; a store identification information acquisition means for acquiring store identification information presented in a store; a registration means for starting product registration in response to the establishment of either a first condition for identifying the store using the location information or a second condition for identifying the store using the store identification information; a determination means for making a validity determination as to whether the product registration has been performed validly; and a notification means for notifying an error using a determination result of the determination means, wherein the notification means issues the notification based on the start condition that has been established. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is an explanatory diagram showing a network configuration of a shopping system 1 according to an embodiment. [Diagram 2] FIG. 2 is an explanatory diagram showing an example of installation of a POS terminal device 20. [Diagram 3] 2 is a block diagram showing a hardware configuration of the POS terminal device 20. FIG. [Figure 4] FIG. 2 is an explanatory diagram showing an example of a hardware configuration of a mobile terminal device 50. [Diagram 5] FIG. 2 is an explanatory diagram showing an example of the appearance of a weighing device 30. [Figure 6] FIG. 2 is an explanatory diagram showing an example of a hardware configuration of a weighing device 30. [Figure 7] 1 is an explanatory diagram showing an example of various information for each mobile terminal device 50 managed by the cloud server Sv; [Figure 8] 2 is a sequence diagram showing a flow of processes relating to product registration and payment in the shopping system 1. FIG. [Figure 9] 13 is a flowchart showing an example of a store entry process performed by the mobile terminal device 50. [Figure 10] FIG. 13 is an explanatory diagram showing an example of a screen displayed on the display 409 of the mobile terminal device 50 when entering a store. [Figure 11]13 is a flowchart showing an example of product registration processing for a barcode product performed by the mobile terminal device 50. [Figure 12] FIG. 13 is an explanatory diagram showing an example of a screen displayed on the display 409 of the mobile terminal device 50 after the store entry process is completed. [Figure 13] 13 is a flowchart showing an example of a product registration process for a product to be weighed, which is performed by the mobile terminal device 50. [Figure 14] FIG. 11 is an explanatory diagram showing an example of a registration procedure for a commodity to be weighed. [Figure 15] 11 is an explanatory diagram showing an example of a standby screen displayed on the weighing device 30. FIG. [Figure 16] 10 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 50 after the connection code is read. FIG. [Figure 17] 10 is an explanatory diagram showing an example of a screen displayed on the weighing device 30 and the mobile terminal device 50 during weighing. FIG. [Figure 18] 11 is a flowchart showing an example of a notification process based on location information performed by the mobile terminal device 50. [Figure 19] 11 is an explanatory diagram showing an example of an error screen based on location information displayed on the mobile terminal device 50. FIG. [Figure 20] 13 is a flowchart showing an example of a notification process based on product registration operation information, which is performed by the mobile terminal device 50. [Figure 21] 11 is an explanatory diagram showing an example of an error screen based on product registration operation information displayed on the mobile terminal device 50. FIG. [Figure 22] 13 is a flowchart showing an example of a registration information confirmation process performed by the POS terminal 20. [Figure 23] 11 is an explanatory diagram showing an example of screen transitions displayed on the customer display unit 205 of the POS terminal device 20 during payment. FIG. [Figure 24] 13 is a flowchart showing a first modification of the notification process based on location information performed by the mobile terminal device 50. [Diagram 25] 13 is a flowchart showing a second modification of the notification process based on location information performed by the mobile terminal device 50. [Figure 26]13 is a flowchart showing a third modified example of the notification process based on the store-specific information, which is performed by the mobile terminal device 50. [Figure 27] 13 is a flowchart showing a fourth modified example of the notification process based on location information performed by the mobile terminal device 50. [Figure 28] 13 is a flowchart showing a fifth modified example of a notification process based on product registration operation information, which is performed by the mobile terminal device 50. [Figure 29] 13 is a flowchart showing a sixth modified example of the notification process based on product registration operation information, which is performed by the mobile terminal device 50. [Diagram 30] 13 is a flowchart showing a seventh modified example of the notification process based on product registration operation information, which is performed by the mobile terminal device 50. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, embodiments of a terminal device, a product sales data processing system, a notification method, and a program according to the present invention will be described.

[0009] (Embodiment) (Network configuration of shopping system 1) 1 is an explanatory diagram showing a network configuration of a shopping system 1 according to an embodiment. The shopping system 1 is an example of a product sales data processing system. The shopping system 1 can be introduced in various stores such as supermarkets, home improvement centers, convenience stores, and various supply stores.

[0010] 1, the shopping system 1 includes a cloud server Sv, a store controller (management device, store computer) 10, a transaction status management device 11, a POS (Point Of Sales) terminal 20, a weighing device 30, and a mobile terminal device 50. The mobile terminal device 50 is an example of a terminal device.

[0011] Each device and each terminal is communicatively connected via a network. For example, the store controller 10, the transaction status management device 11, the POS terminal device 20, and the weighing device 30 are communicatively connected via a LAN (Local Area Network) 55. Each device and each terminal is a computer device equipped with a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, etc.

[0012] The cloud server Sv is a server device that manages various information such as information about customers, information about stores, and information about products for each store. For example, the cloud server Sv generates cart information indicating a virtual cart for each customer based on product information read by the mobile terminal device 50, and registers the products in the virtual cart. The information managed (generated and stored) by the cloud server Sv will be described later with reference to FIG. 7.

[0013] The store controller 10 manages the POS terminal devices 20 and the weighing devices 30, and stores various information necessary for transactions, such as a product master. The product master is a file that stores product information such as product identification information (e.g., JAN (Japanese Article Number) code), product name, and sales price for each product. The product master also includes product identification information, product name, and unit price of products that require weighing (hereinafter referred to as "products to be weighed"). In addition to the product master, the store controller 10 also stores various information such as inventory status, sales history, and deposit and withdrawal records. The store controller 10 may also store customer membership information.

[0014] The transaction status management device 11 is a device that monitors the POS terminal device 20 and the weighing device 30. Specifically, the transaction status management device 11 displays the status of the POS terminal device 20 (operation mode, processing status, etc.) and controls the POS terminal device 20. The transaction status management device 11 also displays the processing status, etc. of the weighing device 30 and controls the weighing device 30. Note that the transaction status management device 11 may only have a monitor function.

[0015] The POS terminal device 20 is a computer device capable of executing a settlement process for settling (paying) the amount of merchandise registered by the mobile terminal device 50. The POS terminal device 20 can settle the amount of merchandise registered by the mobile terminal device 50, as well as the amount of merchandise registered by the POS terminal device 20 itself or by another POS terminal device 20. In this embodiment, the POS terminal device 20 can switch between different operation modes. Specifically, the POS terminal device 20 can operate in a checkout-only mode in which it functions as a settlement-only device, as well as in a clerk registration mode in which merchandise registration is performed by a clerk's operation, and a customer registration mode (full self-service mode) in which merchandise registration is performed by a customer's operation. Although FIG. 1 illustrates a plurality of POS terminal devices 20, the number of POS terminal devices 20 may be one.

[0016] The weighing device 30 is a computer device that weighs the product to be weighed. The weighing device 30 calculates the price of the product to be weighed using the weighed weight (or number) and the unit price of the product to be weighed. The product to be weighed is a product that is different from normal products. Here, normal products are, for example, products that have a JAN code attached. When the mobile terminal device 50 reads the JAN code, it queries the cloud server Sv for the read JAN code and obtains the price data associated with the JAN code.

[0017] On the other hand, the product to be weighed is a product whose price varies depending on the weight and quantity of the item. Examples of the product to be weighed include fresh foods such as vegetables, fruits, fresh fish, and meat, and prepared foods. The weighing device 30 prints and outputs a label that codes the amount, weight, etc. of the product to be weighed. The label includes the price. The label (barcode) attached to the product to be weighed uses the NON-PLU (Price Look Up) method. Note that, although FIG. 1 illustrates an example of multiple weighing devices 30, there may be only one.

[0018] The mobile terminal device 50 is a portable computer device such as a smartphone, a tablet device, or a mobile phone. The mobile terminal device 50 includes a communication unit, an imaging unit (camera), a touch panel, and the like, and is operated by a customer. In this embodiment, the mobile terminal device 50 is detachably attached to the shopping cart. However, the mobile terminal device 50 may be installed in a shopping cart so as not to be detachable. The mobile terminal device 50 may be owned by the customer, or may be a loaned item lent to the customer by the store.

[0019] The mobile terminal device 50 scans (reads) a barcode (product code) attached to a product and accepts the registration of the product. That is, the mobile terminal device 50 has a recognition function for recognizing a barcode attached to a product.

[0020] The recognition function of the mobile terminal device 50 is sufficient if it can read the product code attached to the product, and does not need to identify the product from the read product code. In other words, when a barcode exists as an object in an image captured by the imaging function (an image acquired as a through image), the mobile terminal device 50 is sufficient if it can read the product code from the barcode.

[0021] The mobile terminal device 50 may also include image recognition technology. Specifically, the mobile terminal device 50 may include image recognition technology that extracts feature points from an image (through image, captured image) and recognizes an imaged subject (object, etc.). For example, the mobile terminal device 50 may use the image recognition technology to identify (estimate) an imaged product. By using such image recognition technology, the mobile terminal device 50 can also identify fresh foods such as vegetables and fruits that do not have barcodes.

[0022] Furthermore, application software (hereinafter, sometimes referred to as a "shopping app") for registering and paying for products related to the shopping system 1 is installed in the mobile terminal device 50. By starting the shopping app, the mobile terminal device 50 reads the barcode attached to the product and transmits the read information to the cloud server Sv. As a result, the registered product information corresponding to the barcode is registered in the virtual cart of the cloud server Sv.

[0023] When making a payment, the mobile terminal device 50 uses a two-dimensional code (hereinafter sometimes referred to as a "payment code") corresponding to the registered product. The payment code is represented, for example, by a QR code (registered trademark). When the POS terminal device 20 reads the payment code, it requests the cloud server Sv to transmit registration information corresponding to the mobile terminal device 50. When the POS terminal device 20 receives the registration information from the cloud server Sv, it becomes possible to make a payment at the POS terminal device 20. Note that, hereinafter, products registered in the virtual cart may be referred to as "registered products".

[0024] In this embodiment, the device that performs the settlement is the POS terminal device 20, but is not limited to this. For example, the device that performs the settlement may be a device dedicated to settlement installed in the store, or a computer device for settlement that is permanently installed in the shopping cart. This computer device may be one that only validates card settlement using, for example, a credit card or a prepaid card.

[0025] (Example of installation of POS terminal device 20) FIG. 2 is an explanatory diagram showing an example of the installation of the POS terminal device 20. FIG. 2(A) is a perspective view of the POS terminal device 20 as seen from the customer side. FIG. 2(B) is a perspective view of the POS terminal device 20 as seen from the store clerk side. As shown in FIG. 2(A), a counter is placed on the right side of the POS terminal device 20 as seen from the customer side. Although not shown in the figure, a counter may also be placed on the left side of the POS terminal device 20 in FIG. 2(A). In other words, counters may be placed on both sides of the POS terminal device 20. A shopping basket can also be placed on the counter.

[0026] As shown in Fig. 2, the POS terminal 20 includes a sign pole 220. The sign pole 220 includes a light emitting unit. The light emitting unit of the sign pole 220 is, for example, a lamp or an LED (light emitting diode), and can be lit in a predetermined color or in a predetermined lighting manner. Depending on the lighting manner of the sign pole 220, it is possible to notify the usage status of the POS terminal 20 (in use, warning, calling a store clerk, etc.). The sign pole 220 is provided facing upward, and it is possible to notify the usage status of the POS terminal 20 to a store clerk who is not near the POS terminal 20.

[0027] (Example of configuration of POS terminal device 20) Next, the configuration of the POS terminal 20 will be described with reference to FIG. 2 and FIG. Fig. 3 is a block diagram showing the hardware configuration of the POS terminal device 20. In Fig. 2 and Fig. 3, the same parts are denoted by the same reference numerals.

[0028] An example of the configuration of the POS terminal device 20 shown in Fig. 3 will be described below with reference to Fig. 2. The POS terminal device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer display unit 205, a customer scanner unit 206, a card payment unit 208, a change dispenser 209, a store clerk display unit 210, a key operation unit 211, a store clerk scanner unit 212, a printing unit 213, an audio output unit 214, a communication unit 215, and a camera 216. These can communicate with each other via a bus.

[0029] The CPU 201 is a central processing unit that controls the operation of the POS terminal device 20 by reading and executing various programs stored in the ROM 202 . The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs.

[0030] The RAM 203 is a readable and writable memory, and stores various information. For example, the RAM 203 stores information acquired from the outside (for example, a product master acquired from the store controller 10) and information generated during processing. This information includes, for example, registration information generated during product registration processing and settlement information generated during settlement processing for settling registered products.

[0031] The hard disk 204 stores various information. For example, the hard disk 204 stores imaging results (e.g., video) captured by the camera 216. The hard disk 204 may store various programs such as a product sales data processing program executed by the CPU 201, instead of the ROM 202. Also, instead of the RAM 203, the hard disk 204 may store information acquired from the outside and information generated during processing.

[0032] The customer display unit 205 is a touch display for customers. The customer display unit 205 displays various information to customers and accepts various inputs from customers. The customer-side scanner unit 206 is a scanner unit for customers, and optically reads various information. For example, the customer-side scanner unit 206 optically reads barcodes (product codes, etc.) attached to products and codes (barcodes, two-dimensional codes, etc.) printed on bills (registered trademarks). In addition to the above, the customer-side scanner unit 206 may read codes (barcodes, two-dimensional codes, etc.) printed on gift certificates (gift certificates, coupons, and complimentary coupons) and various cards (for example, membership cards, point cards, etc.). Note that product registration is not limited to registration by reading codes by the customer-side scanner unit 206. For example, a preset key (a button for ordering a product) corresponding to a product may be displayed on the customer-side display unit 205, and the product may be registered by operating (pressing) the preset key by the customer. The customer-side scanner unit 206 may also read a payment code displayed on the mobile terminal device 50. When the settlement code is read by the customer side scanner unit 206, the POS terminal device 20 can carry out settlement based on the read content.

[0033] The card payment unit 208 is a payment mechanism that uses various cards (credit cards, prepaid cards such as transportation cards, point cards, etc.). The card payment unit 208 is equipped with a card recognition unit (reading unit), a display unit, and an operation unit. The card recognition unit magnetically or electrically reads information from various cards. The read information is used to settle the purchase. The card recognition unit is also capable of recognizing information to be used in settling the purchase, for example, when using points held on a point card. The card recognition unit is also capable of recognizing information that is not used in settling the purchase, for example, when adding points to a point card.

[0034] In addition, the card payment unit 208 of this embodiment includes a card recognition unit, a display unit, and an operation unit, but is not limited thereto and may include at least a card recognition unit. In addition, the card recognition unit of this embodiment may be compatible with contact cards (IC cards, magnetic cards) or non-contact cards (IC cards).

[0035] The change machine 209 (cash settlement unit) is a mechanism for settlement using cash, and has an input port for banknotes and coins, and an output port for banknotes and coins. The change machine 209 calculates the amount inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. The change machine 209 faces the customer side, and accepts various operations and cash insertion from customers. The change machine 209 has a sensor that detects banknotes and coins inserted into the input port. The sensor detects that banknotes and coins have been inserted into the input port, and detects the number of banknotes by denomination.

[0036] The clerk-side display unit 210 is a touch display for the clerk. The clerk-side display unit 210 displays various information to the clerk and accepts various inputs from the clerk. The clerk-side display unit 210 displays preset keys (buttons for ordering products) corresponding to products, and products are registered by the clerk operating (pressing) the preset keys. The clerk-side display unit 210 also displays a subtotal key for accepting completion of product registration.

[0037] The key operation unit 211 is composed of various keys (hardware keys, buttons). The key operation unit 211 accepts various inputs from a store clerk. For example, the key operation unit 211 includes a button corresponding to a product, and accepts registration of the product by operating the button. Also, for example, the key operation unit 211 includes a mode switching button, and accepts switching of the operation mode by operating the mode switching button.

[0038] The clerk scanner unit 212 is a scanner unit for the clerk, and optically reads various information. For example, the clerk scanner unit 212 optically reads barcodes attached to products and clerk codes attached to the clerk's nametags. In addition to the above, the clerk scanner unit 212 may read codes printed on bills, gift certificates, and various cards. The clerk scanner unit 212 can also read two-dimensional codes for payment. When the payment code is read by the clerk scanner unit 212, the POS terminal device 20 can make a payment based on the read content.

[0039] The registration of a product is not limited to registration by reading a code by the store clerk's scanner unit 212. For example, a key corresponding to a product (e.g., XX newspaper) may be arranged on the key operation unit 211, and the product may be registered by the store clerk operating (pressing) the key.

[0040] The printing unit 213 prints and outputs various media (receipts, invoices, bills, etc.). The printing unit 213 is capable of changing the direction of the medium issuing port. Specifically, the printing unit 213 has a rotatable mechanism, and is configured so that the medium issuing port faces from the store clerk side to the customer side, and from the customer side to the store clerk side. The orientation of the medium issuing port may be changeable manually, or may be changeable automatically in response to switching of the operating mode. The printing unit 213 may be equipped with a sensor that detects whether the orientation of the printing issuing port is correct.

[0041] The audio output unit 214 outputs audio. For example, the audio output unit 214 outputs audio guidance, warning sounds, etc. The audio guidance and warning sounds are related to product registration and payment. The communication unit 215 is an interface for transmitting and receiving information to and from other devices (the store controller 10, the transaction status management device 11, and other POS terminal devices 20).

[0042] The camera 216 is attached to the upper right of the customer display unit 205 as seen from the customer side. The camera 216 is a camera that continuously captures moving images or still images. A CCD (charge coupled device) camera or a CMOS (complementary metal oxide semiconductor) camera can be used as the camera 216. The camera 216 captures the operation status of the customer at the time of payment. Specifically, the camera 216 captures the bills and coins held by the customer, the change machine 209, hand movements, and the like. The camera 216 also captures the operation status of the customer at the time of registering the product. Specifically, the camera 216 can capture the inside (products) of a shopping basket on a counter provided on both sides of the POS terminal device 20, and the operation status of the customer at the time of registration. The camera 216 may also be provided separately on the store clerk side. In this case, the POS terminal device 20 can determine the presence or absence of a store clerk based on the image captured by the camera 216 provided on the store clerk side.

[0043] (Hardware configuration of the mobile terminal device 50) Fig. 4 is an explanatory diagram showing an example of a hardware configuration of mobile terminal device 50. In Fig. 4, mobile terminal device 50 includes a CPU 401, a ROM 402, a RAM 403, a memory 404, a communication unit 405, an operation unit 406, a camera 407, a microphone 408, a display 409, a speaker 410, and a GPS (Global Positioning System) unit 411. Each unit is connected to each other via a bus 420.

[0044] The CPU 401 is responsible for the overall control of the mobile terminal device 50. The ROM 402 stores various programs. The RAM 403 is used as a work area for the CPU 401. That is, the CPU 401 uses the RAM 403 as a work area and executes various programs stored in the ROM 402 to thereby control the entire mobile terminal device 50.

[0045] The memory 404 stores various data. For example, a flash memory is used as the memory. The memory 404 stores various programs such as a shopping application and a notification program, and various data such as map data and store information. The communication unit 405 is connected to a network, and is connected to other devices (for example, the transaction management server Sv) via the network. The communication network that functions as the network includes the Internet and a mobile phone network.

[0046] The operation unit 406 is a touch panel that displays a plurality of touch keys for inputting characters, numbers, various instructions, etc., or hard keys. The camera 407 reads bar codes attached to products and various two-dimensional codes. The microphone 408 inputs the operator's voice. The display 409 displays icons, cursors, menus, windows, characters, images, codes, and the like.

[0047] The speaker 410 outputs sounds including voice. The GPS unit 411 has a function of receiving position information from a GPS satellite and detecting the current position of the mobile terminal device 50 on map data. The mobile terminal device 50 also includes various sensors (not shown, for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.) and has a function of detecting various states of the mobile terminal device 50 (for example, the inclination of the mobile terminal device 50 and the distance between the mobile terminal device 50 and a commodity).

[0048] (Configuration example of the weighing device 30) Next, a configuration example of the weighing device 30 will be described with reference to Fig. 5 and Fig. 6. Below, the configuration example of the weighing device 30 shown in Fig. 6 will be described with reference to Fig. 5. FIG. 5 is an explanatory diagram showing an example of the appearance of the weighing device 30. As shown in FIG. Fig. 6 is an explanatory diagram showing an example of the hardware configuration of the weighing device 30. As shown in Fig. 5 or 6, the weighing device 30 includes a CPU 301, a ROM 302, a RAM 303, a memory 304, a communication unit 305, a display unit 306, a printing unit 307, a scanner unit 308, an audio output unit 309, a load cell 310, and a platform 320. These can communicate with each other via a bus 330.

[0049] The CPU 301 is a central processing unit, and controls the operation of the weighing device 30 by reading and executing various programs, such as a transaction information output program, stored in the ROM 302 . The ROM 302 is a read-only memory, and stores various types of information used by the CPU 301, including programs.

[0050] The RAM 303 is a readable and writable memory and stores various information, for example, information read from the ROM 302 or memory 304, information acquired from the outside, information generated during processing, and the like.

[0051] The memory 304 stores various information. For example, the memory 304 stores the unit price of the commodity to be weighed obtained from the store controller 10. The various information stored in the memory 304 may be stored in an external device (for example, the store controller 10 or an external server device). In this case, the weighing device 30 may obtain the various information by inquiring of the external device when using the various information.

[0052] The memory 304 may store programs executed by the CPU 301, instead of the ROM 302. The memory 304 may store information read from the ROM 302, information acquired from the outside, information generated during processing, etc., instead of the RAM 303.

[0053] The communication unit 305 is an interface for transmitting and receiving information to and from an external device. The communication unit 305 receives the unit price corresponding to the product identification information of the product to be weighed from the store controller 10. The weighing device 30 calculates the selling price of the product to be weighed using the weight (or number) of the product placed on the platform 320 and the unit price.

[0054] Further, the communication unit 305 performs short-distance wireless communication with the mobile terminal device 50 in addition to communication via network communication. The number of mobile terminal devices 50 that the communication unit 305 can connect to through short-distance wireless communication is limited, for example, to one. To be more specific, the communication unit 305 performs short-distance wireless communication one-to-one with the mobile terminal device 50. The one-to-one short-distance wireless communication is, for example, Bluetooth (registered trademark). The one-to-one short-distance wireless communication may be communication using a communication protocol such as NFC (Near Field Communication), Wi-Fi (registered trademark), optical communication, or a 4G (Generation) line. The number of mobile terminal devices 50 that the communication unit 305 can connect to through short-distance wireless communication is not limited to one, and may be two or three.

[0055] The display unit 306 displays various information to the customer and accepts operations from the customer. The various information displayed on the display unit 306 includes the name of the product being weighed and the number of products being weighed, as well as guidance regarding the weighing. The various information displayed on the display unit 306 also includes a two-dimensional code (hereinafter sometimes referred to as a "connection code") that is read by the mobile terminal device 50 to start one-to-one communication with the mobile terminal device 50.

[0056] The printing unit 307 is a label issuing unit that outputs a printed matter (hereinafter also referred to as a "label") on which information about the product to be weighed (such as the weight and selling price of the product to be weighed, and a barcode indicating these) is printed. The scanner unit 308 reads various codes (bar codes, two-dimensional codes, etc.). The audio output unit 309 outputs audio. For example, the audio output unit 309 outputs audio guidance related to weighing. The load cell 310 is a sensor that detects weight and measures the weight of the product to be weighed placed on the platform 320.

[0057] (An example of information managed by the cloud server Sv) 7 is an explanatory diagram showing an example of various information managed by the cloud server Sv for each mobile terminal device 50. The cloud server Sv stores various information including (A) customer information, (B) store information, and (C) cart information. Note that instead of or in addition to storing the various information in a storage unit within the cloud server Sv, the cloud server Sv may store some or all of the various information in another device, such as a file server, accessible by the cloud server Sv.

[0058] (Customer information) FIG. 7(A) shows an example of customer information. Customer information is information for managing individual customers. Customer information may be membership information for each store or each affiliated store. As shown in FIG. 7(A), customer information includes items such as customer identification information, customer name, customer registration date, customer rank, and number of points.

[0059] The customer identification information is identification information that uniquely identifies a customer. The customer identification information may be, for example, application identification information (hereinafter referred to as "application identification information") that is uniquely assigned to each installed shopping application when the shopping application is installed in the mobile terminal device 50. The application identification information may be, for example, a sequentially assigned number. Alternatively, the application identification information may be terminal identification information that is uniquely assigned to the mobile terminal device 50 in which the shopping application is installed. This terminal identification information may be, for example, a telephone number assigned to the customer who is the user of the mobile terminal device 50, or hardware identification information that is uniquely assigned to the hardware of the mobile terminal device 50, such as a MAC (Media Access Control) address.

[0060] The customer name is the customer's name, nickname, or the like. The customer registration date is the date and time when the customer information was newly registered in the cloud server Sv. The customer rank is a rank according to the customer's purchasing history. The number of points is the number of points given to a customer for shopping using the shopping app. The number of points may include the number of points for each store.

[0061] The customer identification information, customer name, and customer registration date are generated when customer information for a new customer is generated. Specifically, the customer identification information is generated when a shopping application is downloaded to the mobile terminal device 50 from the cloud server Sv or a predetermined server that provides general applications. For example, the customer name is generated based on information entered in the name field of the registration form (input form) of the mobile terminal device 50 when a new customer is registered. Furthermore, the customer registration date is generated based on the current date and time when the new customer is registered.

[0062] (Store information) Fig. 7(B) shows an example of store information. Store information is information for managing each store. As shown in Fig. 7(B), store information includes items such as store identification information, store name, store identification information 1 (information of two-dimensional code), and store identification information 2 (location information). The store identification information includes a store (trade name) or company code and a branch code. The store name is the name of the store, and is composed of, for example, the store name (trade name) or company name and the branch name. The store identification information 1 and 2 are information for identifying a store where a transaction takes place (a store where a product is bought and sold). The store identification information 1 is, for example, information represented by a two-dimensional code posted in the store. The store identification information 2 is location information (GPS information) indicating the location of the store.

[0063] (Cart information) Fig. 7(C) shows an example of cart information. Cart information is information about products registered by a customer at a store. As shown in Fig. 7(C), cart information includes items such as cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information (total), and reserved product information (total). The cart identification information is information for identifying the cart information, which is a virtual cart. Specifically, the cart identification information includes store identification information, a date, and a serial number (for example, a serial number for each store for each date).

[0064] The transaction start date and time is the date and time when the transaction started, for example, the date and time when the cart information was generated. The transaction start date and time may be the registration date and time of one item of product, specifically, the date and time when the registered product information (registered product 1: XX medium-thick sauce) shown in FIG. 7(C) was stored. Instead of or in addition to the transaction start date and time, the registration date and time for each product may be stored separately.

[0065] The transaction end date and time is the date and time when the transaction is ended, specifically, the date and time when the settlement is completed. For example, the transaction end date and time is the date and time when the settlement is completed, but may be the date and time when the settlement is started. The customer identification information is information that uniquely identifies the customer who performs the transaction.

[0066] The registered product information (total) is cumulative information that is updated each time a product is registered. The registered product information (total) includes the number of items (number of products), the estimated subtotal amount, the subtotal amount, etc. Registered product information N (N is an integer) includes the number (data number) of the product registered in item N. Registered product information N includes the product code, product name, price, and the registration date and time of the product. Specifically, registered product information 1 (XX medium-thick sauce) indicates the product registered in item 1. Registered product information 2 (XX cheese) indicates the product registered in item 2. Note that in the example shown in FIG. 7(C), the registered product information for items 3 and onward is omitted from the illustration.

[0067] Next, the reserved item information (total) will be explained. A reserved item is an item that requires confirmation by a store clerk before the settlement can begin. For example, there are types of reserved items, such as unscanned items, non-file items, age verification items, security tag items that require the security tag to be removed, and medicines.

[0068] Unscanned products are products that could not be registered due to failure to scan the product code (the scanner was not able to read it). For example, if the product package is wrinkled or the barcode is smudged or dirty, the barcode may not be recognized due to a timeout.

[0069] Here, the failure to recognize the barcode due to a timeout will be described in detail. The mobile terminal device 50 includes various sensors (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.) and can determine that a barcode is being read using the detection results of the various sensors and the image capture results of the camera 407. Specifically, the mobile terminal device 50 can determine that a barcode is being read using the detection results of the various sensors when the mobile terminal device 50 is tilted and a commodity is present at a position a certain distance away from the mobile terminal device 50. Then, when the mobile terminal device 50 determines that a barcode is being read and is unable to read the barcode within a predetermined time, it determines that a timeout has occurred and identifies the commodity as an unscanned commodity.

[0070] Moreover, unscanned items include, for example, items that have been put into the basket by pretending to have read the barcode of the item. In other words, unscanned items include items that may have been tampered with, and therefore include items that require confirmation by a store clerk as to whether or not there has been tampering. Tampering is detected, for example, using a scan result indicating whether or not the barcode has been scanned, an image captured by a camera capturing an image of the inside of the shopping basket, or a detection result detecting the total weight of the items in the shopping basket.

[0071] A NON-file product is, for example, a product that is not registered in the product master. Specifically, a NON-file product is a product that could not be registered because the product code was successfully scanned (not marked as an unscanned product) and the product with that product code was queried from the product master (cloud server Sv) but the product could not be specified (the product query was NG).

[0072] Age-verification items are items that minors cannot purchase, such as alcohol and tobacco. An anti-theft tag product is a product that has an anti-theft tag attached, such as a product that is over a certain amount of money. Pharmaceuticals, for example, are products that require explanation from a pharmacist.

[0073] As shown in FIG. 7(C), the reserved product information (total) includes the number of items and the type of reserved product (unscanned products, non-file products). The reserved product information (reserved product N: N is an integer) is information on N reserved products and includes the reserved product type of the N reserved products. The reserved product type is information indicating the type of the reserved product. In this example, the reserved product type "1" indicates an unscanned product, and the reserved product type "2" indicates a non-file product. The reserved product information also includes the registration date and time of the product. Note that the illustration shows that unscanned products and non-file products are registered as reserved products, but if age verification products, security tag products, or pharmaceuticals are registered as reserved products, the reserved product information (total) stores these types.

[0074] Furthermore, the pending product information of an unscanned product includes the pending product type "1" as well as image data of the product (image data captured when the mobile terminal device 50 reads the barcode). For example, pending product information 1 includes "1 (unscanned product)" indicating the pending product type and image data.

[0075] Furthermore, the reserved product information of the NON-file product includes the reserved product type “2 (NON-file product)” as well as the product code read by the mobile terminal device 50. For example, the reserved product information 2 includes “2 (NON-file product)” indicating the reserved product type and the product code.

[0076] (Regarding error notification by the mobile terminal device 50) The mobile terminal device 50 periodically performs a presence determination to determine whether or not the device is located within the store, using the location information received from the GPS unit 411. In general, the mobile terminal device 50 notifies an error when it determines in the presence determination that the device is not located within the store or when it cannot receive location information.

[0077] For this reason, in an environment where it is difficult to obtain location information, such as when the store is located underground, the mobile terminal device 50 may determine that it is not located inside the store and may report an error. If errors are reported frequently, the customer may not be able to shop smoothly. In this embodiment, therefore, the frequent reporting of errors is suppressed, enabling the customer to shop smoothly. The reporting of errors by the mobile terminal device 50 will be described in detail below.

[0078] (Functional configuration of the mobile terminal device 50) First, the functional configuration of the mobile terminal device 50 will be described. The mobile terminal device 50 includes a location information acquisition unit, a store specific information acquisition unit, a registration unit, a determination unit, a notification unit, and a request unit. Each unit is realized by the CPU 401. That is, the CPU 401 executes a notification program stored in the ROM 402 to realize the function of each unit.

[0079] The location information acquisition unit acquires location information indicating the current location of the mobile terminal device 50. The location information acquisition unit acquires location information from, for example, the GPS unit 411. Note that the mobile terminal device 50 is not limited to acquiring location information from the GPS unit 411. For example, the mobile terminal device 50 may acquire location information using short-distance wireless communication. Examples of short-distance wireless communication include Wi-Fi (registered trademark), NFC (Near field communication), Bluetooth (registered trademark), EnOcean (registered trademark), Wi-SUN, and Zigbee (registered trademark). The location information acquisition unit can estimate (acquire) the location of the mobile terminal device 50 using the radio wave intensity of the short-distance wireless communication or triangulation based on the radio wave intensity. In addition, the location information acquisition unit can also acquire location information using iBeacon (registered trademark), which is a communication system using BLE (Bluetooth Low Energy).

[0080] The store specific information acquisition unit acquires store specific information presented in a store. The store specific information is represented, for example, by a barcode or a two-dimensional code. The store specific information is presented near the entrance of the store. The store specific information is displayed, for example, on a monitor such as a digital signage. However, the store specific information may also be printed on paper and posted on a wall or the like.

[0081] The registration unit starts product registration in response to the establishment of the start condition. The start condition is either a first condition or a second condition. The first condition is a condition in which a store is identified using location information. Specifically, the first condition is a condition in which it is determined that the mobile terminal device 50 is present in a store using the location information of the store indicated by the store identification information 2 in FIG. 7(C) and the location information indicating the current location of the mobile terminal device 50 acquired from the GPS unit 411. The second condition is a condition in which a store is identified using the store identification information. Specifically, the second condition is a condition in which it is determined that the mobile terminal device 50 is present in a store using the store identification information 1 (two-dimensional code information) in FIG. 7(C).

[0082] (Details of the validity judgment) The determination unit performs a validity determination as to whether or not product registration has been performed validly. The validity determination includes, for example, an operation determination and an existence determination. First, the operation determination will be described. The operation determination is a determination as to whether or not an operation related to product registration has been performed validly. An operation being valid means that a product is registered as usual, and specifically means that the barcode of a product taken out from a product shelf is read by the mobile terminal device 50 installed in the shopping cart and the product is registered.

[0083] On the other hand, when an unusual product is registered in the operation determination, the determination unit determines that the registration operation is improper. Specifically, an unusual product is registered that can be considered as a price check by a competitor. More specifically, for example, when the number of registered products exceeds a certain number (e.g., 50 or more), the determination unit determines that the operation is improper. Note that if all registered products are subsequently canceled, it can be said that there is a high possibility that a price check has been performed.

[0084] In addition, the time required for registration may be taken into consideration in the operation judgment, specifically, when a certain number or more of products are registered within a predetermined time, the judgment unit may judge that the registration operation is improper. In addition, the classification of registered products may be taken into consideration in the operation judgment, specifically, when a certain number or more of products in a specific classification (e.g., instant curry) are registered, the judgment unit may judge that the registration operation is improper.

[0085] Next, the presence determination will be described. The presence determination is a determination as to whether or not the mobile terminal device 50 is present in the store using location information acquired during the transaction. Specifically, the presence determination is a determination made using the location information of the store and the location information of the current location of the mobile terminal device 50. In the presence determination, the determination unit determines that the mobile terminal device 50 is valid when it is present in the store (within the service area). On the other hand, in the presence determination, the determination unit determines that the mobile terminal device 50 is invalid when it is not present in the store (outside the service area).

[0086] (Regarding error notification based on a satisfied start condition) The notification unit notifies an error using the judgment result of the judgment unit. In principle, the notification unit notifies an error when the validity judgment determines that the item is invalid, and does not notify an error when the validity judgment determines that the item is valid. When notifying an error, the mobile terminal device 50 may delete the registered item. Furthermore, when notifying an error, the mobile terminal device 50 may end the shopping app (for example, log out).

[0087] The notification unit notifies an error based on the start condition that has been satisfied. Notification of an error based on the start condition means that an error may or may not be notified depending on the start condition. For example, notification of an error based on an existence determination is performed in a transaction in which a first condition is satisfied, but is not performed in a transaction in which a second condition is satisfied. Note that even if an error is not notified, the determination unit may still perform a validity determination.

[0088] (Regarding location information acquisition judgment) In the present embodiment, the authenticity determination includes a location information acquisition determination in addition to the above-mentioned operation determination and presence determination. The location information acquisition determination is a determination as to whether or not location information of a current location is acquired by the location information acquisition means during a transaction. In the location information acquisition determination, if location information is acquired, the determination unit determines that the transaction is authentic, and on the other hand, if location information is not acquired, the determination unit determines that the transaction is invalid.

[0089] In addition, when the determination result of the location information acquisition determination indicates that the location information has been acquired, the determination unit performs a presence determination using the acquired location information. Therefore, when the location information acquisition determination indicates that the location information has been acquired and the presence determination indicates that the mobile terminal device 50 is not present in the store (is outside the service area), the notification unit notifies an error.

[0090] An error based on the location information acquisition judgment is not notified if a judgment result of the location information acquisition judgment is obtained in which location information is not acquired in a transaction due to the establishment of the first condition. In other words, when the communication environment is not good, such as when the user is underground, and location information cannot be acquired (when a judgment result indicating inappropriateness is obtained in the location information acquisition judgment), the notification unit does not notify an error. In this case, the registration unit allows product registration to continue. In other words, in this embodiment, product registration is not interrupted when location information is not acquired.

[0091] (Request for acquisition of store-specific information) In this embodiment, when starting shopping using a shopping app, identifying a store using location information is prioritized over identifying a store using store identification information. Specifically, if a store cannot be identified based on location information before product registration begins, that is, if the first condition is not met, the request unit (third request means) requests acquisition of store identification information. More specifically, if a store cannot be identified using location information, the request unit requests acquisition of store identification information. The request unit makes the request by, for example, displaying a notification on display 409 such as "Please read the store identification information."

[0092] The registration unit starts product registration in response to the establishment of the second condition, which is the acquisition of store identification information in response to the acquisition request by the request unit. If the store identification information is not acquired even after a certain time has passed, the request unit may request acquisition of the store identification information again. If the store identification information is not acquired even after a certain time has passed, the mobile terminal device 50 may notify the user that shopping cannot be started.

[0093] (When connected to a weighing device 30) The registration unit is capable of registering a commodity to be weighed by communicating with the weighing device 30 that weighs the commodity. A commodity to be weighed cannot be registered unless it is communicatively connected to the weighing device 30. For this reason, the fact that a commodity to be weighed has been registered means that the mobile terminal device 50 (customer) is present in the store. Therefore, in this embodiment, the notification unit is configured not to notify of an error when a commodity to be weighed is registered, regardless of the start condition. Note that, although an error is not notified when a commodity to be weighed is registered, the determination unit may make a valid determination.

[0094] (An example of a process related to product registration and payment in the shopping system 1) Fig. 8 is a sequence diagram showing the flow of processes related to product registration and payment in the shopping system 1. Fig. 8 explains the flow of processes in which a customer visits a store, registers a product to be purchased using his / her mobile terminal device 50, and completes payment for the product using the POS terminal device 20.

[0095] Step S801: First, the mobile terminal device 50 executes a startup process to start the shopping application in response to a customer's operation. In the startup process, the mobile terminal device 50 checks the version of the shopping application, and displays a screen to encourage the user to upgrade if necessary. If this is the first startup, a screen for consenting to the terms of use is displayed, and the startup process is completed by obtaining consent from the customer.

[0096] Step S802: Next, the mobile terminal device 50 performs a store entry process (see FIG. 9). In the store entry process, the mobile terminal device 50 transmits, for example, current location information obtained from the GPS unit 411 to the cloud server Sv. When the cloud server Sv receives the current location information from the mobile terminal device 50, it searches for stores existing near the mobile terminal device 50 and transmits the information to the mobile terminal device 50. The mobile terminal device 50 identifies the store where the customer will shop based on the information received from the cloud server Sv, and transmits information about the identified store to the cloud server Sv.

[0097] Step S803: Upon receiving the information about the store where the customer will shop, the cloud server Sv generates cart information. Step S804: When the store entry process is completed, the mobile terminal device 50 waits for the start of shopping. Specifically, the mobile terminal device 50 displays a top screen for shopping and waits for the customer to press a shopping start button.

[0098] Step S805: The mobile terminal device 50 displays the imaging area on the display 409 and starts the shopping process. Step S806: The mobile terminal device 50 performs product registration processing (see FIGS. 11 and 13). Specifically, the mobile terminal device 50 scans the barcode attached to the product in response to an operation by the customer. After scanning the product, the mobile terminal device 50 transmits the product code obtained by scanning to the cloud server Sv together with cart identification information. Note that if the product indicated by the read product code is, for example, a reserved product such as an unscanned product, the cart identification information and information indicating the reserved product are transmitted as the transmission / reception data D3.

[0099] Step S807: When the cloud server Sv receives the product code and cart identification information from the mobile terminal device 50, it identifies the cart information including the received cart identification information, and updates the registered product information. Specifically, when the cloud server Sv receives the product code of an Nth item, it stores the registered product information (registered product N) indicated by the product code. More specifically, the cloud server Sv stores the product code, product name, and price in association with each other. In addition, the cloud server Sv updates the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered product information from the identified cart information.

[0100] Step S808: When the mobile terminal device 50 performs the product registration process, it performs a validity determination as to whether the product registration has been performed validly, and performs a notification process (see Figs. 18 and 20) to notify an error if the validity determination results in an invalid product registration. This makes it possible to notify an error if, for example, an invalid product registration such as a price check is performed after going outside the store after the store entry process.

[0101] Step S809: The mobile terminal device 50 then performs a registered product display process for adding and displaying the registered product on the registration screen. The registered product display process includes a process for accepting changes to the quantity, deletion, and the like. Step S810: The mobile terminal device 50 judges whether or not an instruction to start settlement (registration completion) has been accepted by an operation of the customer, and if the instruction to start settlement has not been accepted, the process returns to step S806. If the instruction to start settlement has been accepted, the process proceeds to step S811.

[0102] Step S811: When the mobile terminal device 50 receives an instruction to start settlement, it generates a settlement code. The settlement code includes cart identification information and transmission request information for making the POS terminal device 20 perform settlement. When the transmission request information is transmitted from the POS terminal device 20 to the cloud server Sv, the cloud server Sv transmits registration information to the POS terminal device 20. The registration information is information necessary for settlement, and includes, for example, the product name, price, subtotal amount, and the like, among the registered product information. When the mobile terminal device 50 generates the settlement code, it displays the generated settlement code on the display 409.

[0103] Step S812: The POS terminal device 20 reads the settlement code displayed on the mobile terminal device 50. Specifically, the customer who has completed the registration of the product causes the customer-side scanner unit 206 of the POS terminal device 20 to scan the settlement code displayed on the display 409 of the mobile terminal device 50. As a result, the POS terminal device 20 obtains the cart identification information.

[0104] Step S813: When the POS terminal 20 reads the settlement code, it requests the cloud server Sv to transmit cart information. Specifically, the POS terminal 20 transmits transmission request information restored from the settlement code to the cloud server Sv.

[0105] Step S814: Upon receiving the transmission request information from the POS terminal 20, the cloud server Sv extracts the cart identification information from the transmission request information, and identifies the cart information including the cart identification information. Step S815: When the cloud server Sv identifies the cart information, it transmits various information necessary for settlement, including cart identification information, registration information (information indicating registered product information and subtotal amount), and language information, to the POS terminal device 20. If the identified cart information includes reserved products, the cloud server Sv transmits the registration information including information on the reserved products to the POS terminal device 20.

[0106] Step S816: When the POS terminal device 20 receives the registration information from the cloud server Sv, the POS terminal device 20 performs a customer registration information confirmation process (see FIG. 24). If the registration information includes a reserved item, the registration information confirmation process calls a store clerk, who then confirms the reserved item.

[0107] Step S817: The POS terminal device 20 executes a settlement process. The settlement process includes a process for accepting the selection of a payment type. The payment type may be registered in advance in the shopping application. If the payment type is cash, the POS terminal device 20 accepts the insertion of cash, dispenses change, and issues a receipt in the settlement process. The POS terminal device 20 then transmits information indicating the settlement details and cart information to the cloud server Sv. The cloud server Sv then stores the transaction end date and time (settlement date and time) of the cart information.

[0108] Step S818: The cloud server Sv transmits a transaction completion notification to the mobile terminal device 50, which indicates that the transaction has been completed. Step S819: When the mobile terminal device 50 receives the transaction completion notification, it deletes the products registered in the mobile terminal device 50 and terminates the shopping application. Note that when the mobile terminal device 50 generates and displays the settlement code in step S811, it may delete the products registered in the mobile terminal device 50 and terminate the shopping application. In this way, a series of processes is completed.

[0109] In the above process, in step S806, the cart identification information and the product code are transmitted to the cloud server Sv every time the mobile terminal device 50 registers (scans) a product. However, this transmission is not limited to every time a product is registered. For example, the mobile terminal device 50 may transmit this information to the cloud server Sv all at once when an instruction to start checkout is received. In this way, the number of communications between the mobile terminal device 50 and the cloud server Sv can be reduced.

[0110] (An example of the store entry process shown in step S802 of FIG. 8) Next, an example of the store entry process shown in step S802 in FIG. 8 will be described with reference to FIG. 9. FIG. 9 is a flowchart showing an example of the store entry process performed by the mobile terminal device 50. As shown in FIG. 9, the mobile terminal device 50 requests the GPS unit 411 to acquire location information of the current location (step S901). Then, the mobile terminal device 50 determines whether or not the location information of the current location has been acquired (step S902). If the location information of the current location has been acquired (step S902: YES), the mobile terminal device 50 requests the cloud server Sv to search for nearby stores (step S903).

[0111] In response to the request, the cloud server Sv searches for stores within a predetermined range (within 300 m) from the current location of the mobile terminal device 50 using the current location of the mobile terminal device 50 and the store information in Fig. 7(B) and transmits the search results to the mobile terminal device 50. The mobile terminal device 50 refers to the search results received from the cloud server Sv and determines whether or not there is a store near the mobile terminal device 50 (step S904).

[0112] If there is no store near the mobile terminal device 50 (step S904: NO), the mobile terminal device 50 returns to step S903, expands the search range, and requests a surrounding store search again. If there is no store near the mobile terminal device 50, it may notify the user that there is no store nearby. If there is a store near the mobile terminal device 50 (step S904: YES), the mobile terminal device 50 determines whether there is only one store nearby (step S905).

[0113] If there is one store nearby (step S905: YES), the mobile terminal device 50 proceeds to step S907. If there is not one store nearby (step S905: NO), that is, if there are multiple stores nearby, the mobile terminal device 50 accepts the customer's selection of the store to shop at (step S906). Then, the mobile terminal device 50 completes identifying the store (step S907) and ends the series of processes. By identifying the store in step S907, a transaction is initiated when the first condition is met.

[0114] In step S902, if the location information of the current location is not acquired (step S902: NO), specifically, for example, if the communication environment is not good and the GPS unit 411 cannot acquire the location information, the mobile terminal device 50 requests to read the store identification code presented in the store (step S908). Specifically, in step S908, the mobile terminal device 50 notifies the display 409, such as "Please scan the store identification code presented in the store."

[0115] The mobile terminal device 50 waits until the store identification code is read (step S909: NO), and when the store identification code is read (step S909: YES), the identification of the store is completed (step S910), and the series of processes ends. When the store is identified in step S910, a transaction is started when the second condition is satisfied.

[0116] (Example of a screen displayed on the display 409 of the mobile terminal device 50 when entering a store) Fig. 10 is an explanatory diagram showing an example of a screen displayed on the display 409 of the mobile terminal device 50 when entering a store. Fig. 10(A) shows a store selection screen 1000 displayed on the display 409 of the mobile terminal device 50. The store selection screen 1000 includes a map area 1001 and a selection button 1002.

[0117] The map area 1001 shows two candidate stores (Store A and Store B) located in the vicinity of the mobile terminal device 50 on the map screen. The selection buttons 1002 include a Store A selection button 1002a for accepting the selection of Store A, and a Store B selection button 1002b for accepting the selection of Store B. When the customer presses either of the selection buttons 1002, the store to be entered is confirmed. Note that when there is only one candidate store, that store is confirmed as the store to be entered.

[0118] Fig. 10(B) shows an example of when the mobile terminal device 50 acquires store identification information. In Fig. 10(B), a monitor 1010 is, for example, a digital signage installed in a store. A store identification code 1011 indicating the store identification information is displayed on the monitor 1010. When a customer starts a shopping app and has the mobile terminal device 50 read the store identification code 1011, the mobile terminal device 50 can identify the store from the store identification code 1011.

[0119] The two-dimensional code is not limited to being displayed on the monitor 1010, and may be printed and displayed on a printed matter such as a poster. The printed matter may be posted near the entrance or exit of the store. Also, information equivalent to the store-specific information may be displayed and the customer may input it by operation.

[0120] It should be noted that the cloud server Sv can also identify the store, and this will be explained in more detail. FIG. 10C shows an example of the cloud server Sv identifying the store where the mobile terminal device 50 is located. In FIG. 10C, the imaging terminal 1020 is installed, for example, near the entrance of the store. A barcode 1021 indicating the identification information of the mobile terminal device 50 is displayed on the mobile terminal device 50. When a customer causes the imaging terminal 1020 to read the barcode 1021, the imaging terminal 1020 transmits to the cloud server Sv the store identification information as well as information indicating that the mobile terminal device 50 identified by the barcode 1021 is located in the store. The cloud server Sv transmits to the mobile terminal device 50 identified by the barcode 1021 the store identification information indicating the store where the mobile terminal device 50 is located. In this manner, the mobile terminal device 50 can also obtain the store identification information.

[0121] (One example of the product registration process shown in step S806 of FIG. 8 (part 1)) Fig. 11 is a flowchart showing an example of product registration processing for a barcode product performed by the mobile terminal device 50. As shown in Fig. 11, the mobile terminal device 50 determines whether scanning of a barcode attached to a product has started (step S1101). The mobile terminal device 50 can determine whether scanning of a barcode has started using detection results of various sensors and imaging results of the camera 407.

[0122] The mobile terminal device 50 waits until scanning of the barcode starts (step S1101: NO), and when scanning of the barcode starts (step S1101: YES), it determines whether or not product identification information has been acquired from the barcode by scanning (step S1102). If product identification information cannot be acquired from the barcode (step S1102: NO), the mobile terminal device 50 determines whether or not a timeout has occurred (step S1103). If a timeout has not occurred (step S1103: NO), the mobile terminal device 50 returns to step S1102.

[0123] If the timeout has occurred (step S1103: YES), the mobile terminal device 50 notifies the customer that the product is on hold (step S1104). The notification prompts the customer to place the product in a separate reserved product bag rather than in the shopping basket, and notifies the customer that the product will be registered by a store clerk at the time of payment. The mobile terminal device 50 then registers the on-hold product information (unreadable product) (step S1105), and ends the series of processes.

[0124] In step S1102, if the product identification information can be acquired from the barcode (step S1102: YES), the mobile terminal device 50 judges whether or not the product is a NON-file product (step S1106). If the product is a NON-file product (step S1106: YES), the mobile terminal device 50 proceeds to step S1104 and notifies the user that the product is on hold. If the product is not a NON-file product (step S1106: NO), the mobile terminal device 50 registers the product (step S1107).

[0125] Then, the mobile terminal device 50 judges whether the registration operation is invalid (step S1108). The registration operation is invalid when, for example, the number of registered products is a certain number or more (for example, 50 or more). If the registration operation is not invalid (step S1108: NO), the mobile terminal device 50 ends the series of processes. If the registration operation is invalid (step S1108: YES), the mobile terminal device 50 stores product registration operation information indicating that the registration operation is invalid in the memory 404 (step S1109), and ends the series of processes.

[0126] (Example of a screen displayed on the display 409 of the mobile terminal device 50 after the store entry process is completed) FIG. 12 is an explanatory diagram showing an example of a screen displayed on the display 409 of the mobile terminal device 50 after the store entry process is completed. FIG. 12(a) shows a top screen 1200 displayed on the display 409 of the mobile terminal device 50. The top screen 1200 includes information presentation buttons 1201 (1201a to 1201c) and a registration start button 1202. The store information button 1201a is a button that accepts a command to start displaying store information such as a floor guide. The announcement button 1201b is a button that accepts a command to start displaying store information such as an event. The bargain information button 1201c is a button that accepts a command to start displaying sale items such as advertising information. The registration start button 1202 is a button that accepts a command to start displaying an imaged screen on the display 409.

[0127] FIG. 12(b) shows a registration screen 1210 for registering a product. The registration screen 1210 includes an imaging area 1211, a registered product display area 1212, a total amount display area 1213, and a checkout start button 1214. The imaging area 1211 is an area where a barcode attached to a product can be imaged (scanned) by the function of the camera 407 of the mobile terminal device 50. The registered product display area 1212 is an area where various registered products (product name, quantity, price, etc.) are displayed. The registered products are displayed in the order in which they were registered in the registered product display area 1212. Specifically, the most recently registered product is displayed at the top of the registered product display area 1212.

[0128] The total amount display area 1213 is an area where the total number of registered items and the total amount are displayed. The checkout start button 1214 is a button for completing the registration of items and accepting the start of checkout. When the checkout start button 1214 is pressed in Fig. 12(B), the screen changes to the screen shown in Fig. 12(C).

[0129] FIG. 12(C) shows a settlement start reception screen 1220. The settlement start reception screen 1220 includes a guidance display 1221, a settlement code 1222, and a registration return button 1223. The guidance display 1221 displays guidance to have the POS terminal device 20 read the settlement code 1222. The settlement code 1222 is, for example, coded information such as cart identification information of the mobile terminal device 50 or information for causing the POS terminal device 20 to transmit a transmission request for cart information to the cloud server Sv. The registration return button 1223 is a button for accepting a return to the registration screen 1210 (FIG. 12(B)). When the customer has the customer-side scanner unit 206 of the POS terminal device 20 read the settlement code 1222, settlement is started in the POS terminal device 20.

[0130] (Example (part 2) of the product registration process shown in step S806 of FIG. 8) Fig. 13 is a flow chart showing an example of a product registration process of a product to be weighed performed by the mobile terminal device 50. As shown in Fig. 13, the mobile terminal device 50 judges whether or not the temporary registration code 1403 of the product to be weighed (see Fig. 14) has been scanned (step S1301). The temporary registration code 1403 of the product to be weighed is posted near the product to be weighed. The mobile terminal device 50 waits until the temporary registration code 1403 of the product to be weighed is scanned (step S1301: NO), and when the temporary registration code 1403 of the product to be weighed is scanned (step S1301: YES), the mobile terminal device 50 provisionally registers the product to be weighed (step S1302). The provisionally registered product to be weighed is displayed on the display 409.

[0131] The portable terminal device 50 then determines whether or not the connection code displayed on the display unit 306 of the weighing device 30 has been scanned (step S1303). The portable terminal device 50 waits until the connection code 1511 (see FIG. 15) is scanned (step S1303: NO). When the connection code 1511 is scanned (step S1303: YES), the portable terminal device 50 makes a connection request for one-to-one communication to the weighing device 30 (step S1304).

[0132] Even if the connection code 1511 is scanned when the commodity to be weighed has not been provisionally registered, the mobile terminal device 50 will not make a connection request to the weighing device 30. This is because if the connection time between one mobile terminal device 50 and the weighing device 30 becomes long, other customers will be unable to use the weighing device 30, and therefore, the purpose is to shorten the time that one mobile terminal device 50 occupies the weighing device 30.

[0133] When a connection request is received from the mobile terminal device 50, the weighing device 30 performs a pairing determination, including authentication of one-to-one communication and a determination as to whether the provisionally registered product is a product to be weighed by the weighing device 30. If the pairing determination is successful, the weighing device 30 starts one-to-one communication with the mobile terminal device 50.

[0134] Next, the mobile terminal device 50 determines whether a communication connection with the weighing device 30 has been established (step S1305). If a communication connection with the weighing device 30 has been established (step S1305: YES), the mobile terminal device 50 obtains the weight value of the product placed on the platform 320 by the customer from the weighing device 30 (step S1306). When the weighing device 30 finishes weighing, it issues a label indicating the weighing result in response to the customer's operation and transmits the weighing result to the mobile terminal device 50. In other words, when the weighing on the weighing device 30 is completed, the mobile terminal device 50 obtains the weighing result from the weighing device 30 in response to the customer's operation of the weighing device 30.

[0135] When the mobile terminal device 50 acquires the weighing result, it displays the weighing result (step S1307). Then, the mobile terminal device 50 displays a registration update screen and officially registers the products to be weighed (step S1308). After that, the mobile terminal device 50 judges whether or not the weighing (official registration) of all provisionally registered products to be weighed has been completed (step S1309). If the weighing of all provisionally registered products to be weighed has been completed (step S1309: YES), the mobile terminal device 50 ends communication with the weighing device 30 (step S1310) and ends the series of processes.

[0136] On the other hand, if weighing of all of the provisionally registered products to be weighed has not been completed (step S1309: NO), the mobile terminal device 50 returns to step S1306 and performs processing for officially registering the other provisionally registered products to be weighed.

[0137] In step S1305, if a communication connection with the weighing device 30 is not established (step S1305: NO), the mobile terminal device 50 notifies a retry (step S1311). Then, the mobile terminal device 50 determines whether to end the registration (step S1312). The mobile terminal device 50 determines to end the registration when it receives a notice of the end of the registration from the customer or when a certain number of retries have been performed.

[0138] If registration is not to be terminated (step S1312: NO), that is, when continuation of registration is accepted from the customer or when a certain number of retries have not been performed, the mobile terminal device 50 returns to step S1304. On the other hand, if registration is to be terminated (step S1312: YES), the mobile terminal device 50 erases the provisionally registered product to be weighed (step S1313) and terminates the series of processes.

[0139] In the above process, the timing when the weighing result is transmitted to the portable terminal device 50 is the timing when the label is issued, but this is not limited to the timing. For example, it may be the timing when weighing of all products is completed in the weighing device 30. In this case, the timing when the weighing result is displayed on the portable terminal device 50 may be the timing when the weighing is completed.

[0140] (Procedure for registering products to be weighed) Next, a procedure for registering a commodity to be weighed will be described with reference to Figs. Fig. 14 is an explanatory diagram showing an example of a registration procedure for a commodity to be weighed. In Fig. 14, an example will be described in which the camera 407 of the mobile terminal device 50 captures an image of identification information of a commodity to be weighed that a customer wishes to purchase.

[0141] In a corner (sales floor) in the store where fruits are placed, products to be weighed 1401 (1401a to 1401c) and displays 1402 (1402a to 1402c) are arranged. The products to be weighed 1401 include, for example, a lemon product to be weighed 1401a, an apple product to be weighed 1401b, and an orange product to be weighed 1401c. The displays 1402a to 1402 are arranged behind the products to be weighed 1401a to 1401c. Note that, in the following, the lemon display 1402a will be mainly used as an example, but the same applies to the other displays 1402b and 1402c.

[0142] Display 1402a displays the character "lemon", the unit price, and temporary registration code 1403. The unit price indicates the price per 1 kg. Temporary registration code 1403 includes information for identifying commodity 1401a to be weighed (commodity identification information) and unit price information. Temporary registration code 1403 is read by mobile terminal device 50.

[0143] The display 1402a can change the contents of the provisional registration code 1403 depending on the time. For example, it can prevent fraudulent acts such as discounts during limited time sales and transactions using barcodes read in the past. Specifically, this fraudulent act involves, for example, taking a picture of a barcode during a limited time sales on the previous day with a camera, and then having the barcode read the next day to register the weighing target product 1401 at the unit price during the limited time sales on the previous day. The contents displayed on the display 1402a may be printed on a print medium such as paper.

[0144] When the mobile terminal device 50 reads the temporary registration code 1403, it temporarily registers the read product 1401 to be weighed. The display screen of the mobile terminal device 50 shown in Fig. 14 shows a temporary registration screen 1410. The temporary registration screen 1410 includes an imaging result 1411, a temporary registration field 1412, a main registration field 1413, and a total display field 1414. The imaging result 1411 shows, for example, an image when the temporary registration code 1403 of a lemon is read.

[0145] The provisional registration field 1412 displays products that have been provisionally registered by reading the provisional registration code 1403. In the figure, the provisional registration field 1412 (1412a, 1412b) indicates that lemons and apples have been provisionally registered. In other words, it indicates that the provisional registration code 1403 for apples was read before the provisional registration code 1403 for lemons was read. The provisional registration field 1412 displays "Weighing Required," which indicates that weighing is required, and "?? yen," which indicates that the price is undetermined because weighing has not been completed.

[0146] The final registration field 1413 displays the final registered product and price. The display mode of the final registration field 1413 is different from the display mode of the temporary registration field 1412. In the figure, the temporary registration field 1412 is displayed in a shaded display mode. By using such a display mode, it is possible to make the customer easily aware that the temporary registration is in progress, and to encourage the customer to weigh the product.

[0147] Fig. 15 is an explanatory diagram showing an example of a standby screen displayed on the weighing device 30. In Fig. 15, a standby screen 1500 displayed during standby is displayed on the display unit 306 of the weighing device 30. The standby screen 1500 includes a first notification field 1510 and a second notification field 1520.

[0148] The first information field 1510 shows information for registering a product to be weighed using the mobile terminal device 50. Specifically, the first information field 1510 shows a connection code 1511, and shows information for having the mobile terminal device 50 read the connection code 1511. The second notification field 1520 shows a guide for registering the product to be weighed without using the mobile terminal device 50. Specifically, the second notification field 1520 shows a guide encouraging the user to place the product to be weighed on a scale and weigh it. The following describes the case where the mobile terminal device 50 is used.

[0149] The customer causes mobile terminal device 50 to read temporary registration code 1403 for lemon and apple shown in Fig. 14, and then causes mobile terminal device 50 to read connection code 1511 shown in Fig. 15. When mobile terminal device 50 reads connection code 1511, it makes a request for communication connection to weighing device 30 based on the instructions indicated by connection code 1511.

[0150] Fig. 16 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 50 after reading the connection code. Fig. 16(A) shows a standby screen when a connection request is made. As shown in Fig. 16(A), the display 409 of the mobile terminal device 50 displays a status display 1610 indicating that a communication connection with the weighing device 30 is being attempted. When pairing is completed, the screen transitions to the screen shown in Fig. 16(B).

[0151] Fig. 16(B) shows a screen when a communication connection is established. As shown in Fig. 16(B), a guidance display 1620 that prompts the user to place a product on the scale is displayed on the display 409 of the mobile terminal device 50. Note that, since the mobile terminal device 50 provisionally registered apples before lemons, the guidance display 1620 that prompts the user to weigh apples is displayed before the guidance display that prompts the user to weigh lemons.

[0152] 17 is an explanatory diagram showing an example of a screen during weighing displayed on the weighing device 30 and the mobile terminal device 50. Fig. 17(A) shows an operation guide screen 1700 of the weighing device 30 when no product has been placed on the platform 320. The operation guide screen 1700 includes a guide display S1, a product name display 1701, a back button 1702, a cancel button 1703, a search button 1704, a weighing result column 1705, a unit price column 1706, a total amount column 1707, and mobile terminal information 1730.

[0153] The guidance display S1 shows guidance encouraging the user to place the product on the platform 320. The product name display 1701 shows the product name of the product to be weighed. The back button 1702 is a button that accepts returning to the previous screen. The cancel button 1703 is a button that accepts canceling weighing. The search button 1704 is a button that accepts searching for nearby mobile terminal devices 50 in order to reconnect with the mobile terminal device 50 when, for example, the communication connection with the mobile terminal device 50 is disconnected.

[0154] The weighing result field 1705 shows the weight of the product to be weighed that is placed on the platform 320. The weighing result field 1705 is not limited to displaying the weight, and may display, for example, the number of products converted based on the weight for products whose approximate weight per unit is known. The unit price field 1706 shows the unit price (e.g., the price per kilogram). The total amount field 1707 shows the total amount calculated using the weighing result and the unit price. The mobile terminal information 1730 shows the currently connected mobile terminal device 50 (owner). Specifically, the mobile terminal information 1730 shows text information such as "Connected to Mr. XX".

[0155] Fig. 17(B) shows a weighing completion screen 1710 of the weighing device 30 when weighing is complete. The weighing completion screen 1710 differs from the operation guide screen 1700 of Fig. 17(A) in that it displays the contents of a weighing result field 1705, the contents of a total amount field 1707, a guide display S2, and a print button 1708. The weighing result field 1705 shows the weight of the product placed on the platform 320 (e.g., 1.2006 kg). The total amount field 1707 shows the amount calculated using the weight and unit price of the product (e.g., 432 yen).

[0156] The guidance display S2 shows guidance to encourage pressing of the print button 1708. The print button 1708 is a button for accepting printing of a label. The print button 1708 is displayed only when a product is placed on the platform 320 and the weighing value becomes stable. When the print button 1708 is pressed on the weighing completion screen 1710, the screen shown in FIG. 17(C) is displayed.

[0157] Fig. 17(C) shows a guide screen 1720 after the label has been issued. The guide screen 1720 shows a screen that prompts the user to affix a label to the bag containing the product to be weighed (apples). When issuing the label, the weighing device 30 transmits the weighing results of the apples (product identification information, the fact that they have been weighed, the price, etc.) to the mobile terminal device 50 via short-range wireless communication. When the mobile terminal device 50 receives the weighing results of the apples, it displays the screen shown in Fig. 17(D).

[0158] Figure 17(D) shows a screen displayed on the mobile terminal device 50 when the official registration of the apples is completed. As shown in Figure 17(D), due to the fact that the weighing result of the apples has been received from the weighing device 30, the mobile terminal device 50 displays official registration field 1413a corresponding to the apples in place of temporary registration field 1412b (see Figure 14) corresponding to the apples.

[0159] Also, the word "Weighing required" that was displayed in the provisional registration has been changed to the word "Weighing" in the official registration field 1413. This suggests that the weighing of the apples has been completed. Note that instead of the word "Weighing" in the official registration field 1413, the weighed weight (e.g., 0.5 kg) or the unit price (e.g., 1000 yen / kg) may be displayed.

[0160] After a predetermined time (e.g., 3 seconds) has elapsed since the weighing device 30 displayed the screen shown in Fig. 17(C), the weighing device 30 transitions to a screen that prompts the user to weigh the lemon. The transition of the screens on the weighing device 30 and the mobile terminal device 50 when weighing a lemon is the same as that when weighing an apple, and therefore a description thereof will be omitted. After the official registration of all provisionally registered products to be weighed (apples and lemons) is completed, the weighing device 30 displays the standby screen 1500 shown in Fig. 15 after a predetermined time (e.g., 3 seconds) has elapsed.

[0161] (One example of the notification process shown in step S808 of FIG. 8 (part 1)) Fig. 18 is a flowchart showing an example of a notification process based on location information performed by the mobile terminal device 50. As shown in Fig. 18, the mobile terminal device 50 judges whether or not the registered product is a product to be weighed (step S1801). If the registered product is a product to be weighed (step S1801: YES), it is clear that the customer is present in the store, and the mobile terminal device 50 ends the process without performing a location information acquisition judgment or a presence judgment.

[0162] On the other hand, if the registered product is not a weighing target product (step S1801: NO), that is, if the registered product is a barcode product, the mobile terminal device 50 determines whether the transaction is due to the first condition being met (the condition that the store is identified using location information) (step S1802). If the transaction is not due to the first condition being met (step S1802: NO), that is, if the transaction is due to the second condition being met (the condition that the store is identified using store identification information), the mobile terminal device 50 ends the process as is. This makes it possible to prevent a notification based on the presence determination from being made in a transaction due to the second condition being met, thereby reducing the frequency of error notifications.

[0163] On the other hand, if the transaction is due to the first condition being satisfied (step S1802: YES), the mobile terminal device 50 (CPU 401) requests the GPS unit 411 to acquire location information of the current location (step S1803). The mobile terminal device 50 then performs a location information acquisition determination to determine whether or not the location information of the current location has been acquired (step S1804). If the location information acquisition determination determines that the location information of the current location has not been acquired (step S1804: NO), that is, if the communication environment is not good, for example, if the mobile terminal device 50 is underground, the mobile terminal device 50 ends the process without reporting an error. This makes it possible to prevent error reports from being issued frequently when the communication environment is not good.

[0164] On the other hand, if the location information of the current location is acquired in the location information acquisition determination (step S1804: YES), the mobile terminal device 50 compares the location information of the current location with the location information of the store to perform a presence determination as to whether the current location of the mobile terminal device 50 is out of range (outside the store) (step S1805). If the current location of the mobile terminal device 50 is not out of range in the presence determination (step S1805: NO), that is, if the current location of the mobile terminal device 50 is within range (inside the store), the process ends.

[0165] On the other hand, if the presence determination indicates that the current location of the mobile terminal device 50 is out of range (step S1805: YES), that is, if there is a risk that a customer (member) who came to the store to check prices or the like has moved outside the store and is performing registration operations, an error is notified that the mobile terminal device 50 (the customer) is outside the store (step S1806).

[0166] Next, the mobile terminal device 50 judges whether or not to perform a retry (step S1807). Note that the retry is performed automatically or by receiving an operation to perform a retry from the customer, if the number of retries is within a preset upper limit, for example. If the number of retries exceeds the upper limit, the process may proceed to step S1808.

[0167] If a retry is to be performed (step S1807: YES), the mobile terminal device 50 returns to step S1803. If a retry is not to be performed (step S1807: NO), the mobile terminal device 50 restricts product registration (step S1808) and ends the series of processes. Note that restricting product registration means, for example, canceling the registered product and logging out. In this case, the store clerk may be able to cancel the error notification and may also enable re-login and re-product registration. This can enhance the effect of deterring improper product registration.

[0168] (Example of an error screen based on location information displayed on the mobile terminal device 50) FIG. 19 is an explanatory diagram showing an example of an error screen based on location information displayed on the mobile terminal device 50. As shown in FIG. 19, an error screen 1900 is displayed on the display 409 of the mobile terminal device 50. The error screen 1900 indicates that the customer is outside the store and that product registration is to be canceled (the registered product is to be deleted). When a confirmation button 1901 is pressed on the error screen 1900, the registered product is deleted and the user is logged out. On the other hand, when a retry button 1902 is pressed on the error screen 1900, location information is acquired again and a presence determination is performed again. When it is determined in the second presence determination that the customer is in the store, the error screen 1900 is terminated and the screen returns to one where product registration is possible.

[0169] (An example (part 2) of the notification process shown in step S808 of FIG. 8) Fig. 20 is a flowchart showing an example of a notification process based on product registration operation information performed by the mobile terminal device 50. As shown in Fig. 20, the mobile terminal device 50 (CPU 401) requests acquisition of product registration operation information stored in the memory 404 (step S2001). Then, the mobile terminal device 50 performs an operation determination to determine whether the product registration operation information stored in the memory 404 is product registration operation information indicating an inappropriate registration operation (step S2002). If the product registration operation information is not product registration operation information indicating an inappropriate registration operation (step S2002: NO), the mobile terminal device 50 ends the series of processes.

[0170] On the other hand, if the product registration operation information indicates an inappropriate registration operation (step S2002: YES), that is, for example, if the number of registered products is a certain number or more (for example, 50 or more), the mobile terminal device 50 notifies an error that an unnatural registration operation has been performed (step S2003). Then, the mobile terminal device 50 restricts the product registration (step S2004) and ends the series of processes. Note that restricting the product registration means, for example, canceling the registered products and logging out.

[0171] (Example of an error screen based on product registration operation information displayed on the mobile terminal device 50) Fig. 21 is an explanatory diagram showing an example of an error screen based on product registration operation information displayed on the mobile terminal device 50. As shown in Fig. 21, an error screen 2100 is displayed on the display 409 of the mobile terminal device 50. The error screen 2100 displays a message that the registration operation is invalid and that the product registration will be canceled (the registered product will be deleted). When a confirmation button 2101 is pressed on the error screen 2100, the registered product is deleted and the user is logged out.

[0172] (An example of the registration information confirmation process shown in step S816 of FIG. 8) Fig. 22 is a flowchart showing an example of a registration information confirmation process performed by the POS terminal device 20. As a premise of the flowchart shown in Fig. 22, the POS terminal device 20 reads a settlement code displayed on the mobile terminal device 50 and requests the cloud server Sv to transmit the registration information. Then, as shown in Fig. 22, the POS terminal device 20 determines whether or not cart information of the mobile terminal device 50 has been received from the cloud server Sv (step S2201).

[0173] The POS terminal 20 waits until it receives the cart information (step S2201: NO). When it receives the cart information (step S2201: YES), the POS terminal 20 displays the cart information (registered product information and reserved product information) in a list on the customer side display unit 205 (step S2202). Then, the POS terminal 20 determines whether the cart information includes reserved product information (step S2203).

[0174] If the cart information does not include reserved product information (step S2203: NO), the POS terminal 20 proceeds to step S2210. If the cart information includes reserved product information (step S2203: YES), the POS terminal 20 performs a checkout prohibition process (step S2204). For example, the checkout prohibition process disables operations on the customer display unit 205.

[0175] Then, the POS terminal device 20 performs a store clerk calling process (step S2205). In the store clerk calling process, the customer side display unit 205 displays a message that a store clerk is being called, the sign pole 220 is illuminated in a predetermined lighting mode, and the transaction status management device 11 displays a message to direct the store clerk to the target POS terminal device 20.

[0176] Next, the POS terminal 20 judges whether or not the clerk has logged in (step S2206). To log in, the clerk, for example, reads the clerk code on the clerk's name tag with the clerk scanner unit 212, or manually inputs the clerk code into the clerk display unit 210 or key operation unit 211.

[0177] The POS terminal 20 waits until the store clerk logs in (step S2206: NO). When the store clerk logs in (step S2206: YES), the POS terminal 20 checks the reserved items one by one and registers or deletes them (reserved item confirmation process) (step S2207). The POS terminal 20 continues the reserved item confirmation process until there are no reserved items left (step S2208: NO). When there are no reserved items left (step S2208: YES), the POS terminal 20 cancels the checkout prohibition process (step S2209). The POS terminal 20 then displays a checkout start screen (step S2210) and ends the series of processes.

[0178] (Example of screen transition at checkout displayed on the customer side display unit 205 of the POS terminal device 20) FIG. 23 is an explanatory diagram showing an example of screen transitions displayed on the customer display unit 205 of the POS terminal device 20 during payment. FIG. 23(A) shows a guide screen 2310. The guide screen 2310 is a screen that prompts the customer scanner unit 206 to read the payment code 1222 (see FIG. 12(C)). For example, the POS terminal device 20 displays the guide screen 2310 in standby mode for payment only. When the customer causes the customer scanner unit 206 to read the payment code 1222 displayed on the mobile terminal device 50 on the guide screen 2310 shown in FIG. 23(A), the screen transitions to a list display screen 2320 shown in FIG. 23(B) or a store clerk calling screen 2330 shown in FIG. 23(C).

[0179] 23(B) includes a registered product display area 2321, a call clerk button 2322, and a checkout start button 2323. The registered product display area 2321 shows the product name, number of items purchased, and purchase price for each registered product, as well as the total number of items and total price for each registered product. The registered product display area 2321 is displayed in the order of registration, for example.

[0180] The call clerk button 2322 is a button for receiving a call from a customer to a clerk. When a customer checks the registered product display area 2321 and finds that the registered product differs from the product he or she wishes to purchase, the registered product needs to be corrected. This correction requires the operation of a clerk. For example, when a customer checks the registered product display area 2321, he or she realizes that only one item of "XX meat sauce" has been registered, although he or she intended to register three items. In this case, the customer presses the call clerk button 2322 to call a clerk. When the call clerk button 2322 is pressed, the screen transitions to a clerk calling screen 2330 shown in FIG. 23(C).

[0181] The store clerk calling screen 2330 shown in Fig. 23(C) indicates that a store clerk is being called. When the confirmation button 2331 is pressed on the store clerk calling screen 2330, the screen transitions to a list display screen (not shown) of registered products. Note that this list display screen cannot accept the start of settlement because the store clerk is being called. Once the store clerk has been called and logged in, the screen transitions to a pending product confirmation screen 2340 shown in Fig. 23(D).

[0182] On the reserved item confirmation screen 2340, the store clerk registers or deletes items while confirming with the customer one by one. Then, when there are no more reserved items, the screen transitions to the list display screen 2320 shown in FIG. 23(B).

[0183] The checkout start button 2323 is a button that accepts the start of the checkout process from the customer. The customer checks the registered product display area 2321, and if there is no difference between the registered product and the product that the customer wishes to purchase, the customer presses the checkout start button 2323. When the checkout start button 2323 is pressed, the POS terminal 20 can perform the checkout process. In the checkout process, the POS terminal 20 accepts the selection of a payment type, accepts the insertion of cash or a card, and issues a receipt when the checkout is complete.

[0184] As described above, the mobile terminal device 50 according to the present embodiment is adapted to notify an error based on the start condition of a transaction. This allows the frequency of error notifications to be different between a transaction resulting from the fulfillment of the first condition and a transaction resulting from the fulfillment of the second condition, thereby making it possible to reduce the frequency of errors according to the start condition. Therefore, according to the present embodiment, it is possible to prevent shopping from being hindered by error notifications, allowing shopping to be carried out smoothly.

[0185] In the present embodiment, the mobile terminal device 50 issues an error notification based on the presence determination in a transaction in which the first condition is satisfied, but does not issue an error notification based on the presence determination in a transaction in which the second condition is satisfied. Therefore, the frequency of error notifications in a transaction in which the second condition is satisfied can be reduced.

[0186] In addition, in this embodiment, the mobile terminal device 50 does not notify an error in a transaction based on the first condition, regardless of whether or not location information is acquired in the location information acquisition determination. This makes it possible to prevent frequent error notifications when the communication environment is not good.

[0187] In addition, in this embodiment, the validity determination includes an operation determination as to whether or not the operation related to the product registration is performed validly. This makes it possible to notify an error when an invalid registration operation such as a price check is performed. This makes it possible to prevent invalid product registration such as a price check. This makes it possible to prevent various store information such as price information from being easily leaked.

[0188] In this embodiment, the mobile terminal device 50 is configured not to notify of an error when a commodity to be weighed is registered, regardless of the start condition. This makes it possible to notify of an error when it is clear that a customer is present in the store.

[0189] In this embodiment, when the mobile terminal device 50 is unable to acquire location information at the start of a transaction, the mobile terminal device 50 requests acquisition of store-specific information, and starts product registration when the store-specific information is acquired in response to the acquisition request. This allows the mobile terminal device 50 to prompt acquisition of store-specific information and start product registration even when the mobile terminal device 50 is unable to acquire location information.

[0190] (Modification of the embodiment) The following describes Modifications 1 to 11 of the embodiment. In each of the following modifications, the contents described in the above embodiment will be omitted as appropriate. It is also possible to combine the configurations shown in the above embodiment and Modifications 1 to 11. Specifically, the above embodiment and Modifications 1 to 11 may all be included, or one of the above embodiment and Modifications 1 to 11 may be included.

[0191] (Variation 1) First, a first modified example of the embodiment will be described. In the above-described embodiment, a configuration in which store identification information is not acquired during shopping has been described (see FIG. 18). Instead of or in addition to such a configuration, in a first modified example, a configuration in which store identification information is acquired during shopping will be described.

[0192] In the first modification, the request unit (first request means) makes a request to acquire store identifying information in response to a determination result that location information is not acquired in the location information acquisition determination. The request unit makes a request to acquire store identifying information at a predetermined timing. The predetermined timing is, for example, a timing when a period during which location information of the current location is not acquired reaches a predetermined period (for example, 15 minutes). In other words, the request unit makes a request to acquire store identifying information when, for example, the customer is underground for a predetermined period or longer. Furthermore, the predetermined timing is not limited to this, and may be a timing when the number of times product registration is performed without acquiring location information of the current location reaches a predetermined number or more. In response to the request to acquire store identifying information by the request unit, the customer causes the mobile terminal device 50 to read a store identifying code.

[0193] In addition, in the store, two-dimensional codes indicating store identification information may be appropriately placed in areas where the communication environment is poor. This allows the mobile terminal device 50 to read the two-dimensional code even when the customer is in a basement or the like. That is, the store identification information acquisition unit can acquire the store identification information.

[0194] Here, the validity determination includes a store-specific information acquisition determination. The store-specific information acquisition determination is a determination of whether or not store-specific information has been acquired during the transaction. If store-specific information has been acquired, it is clear that a customer is present in the store identified by the store-specific information. In the store-specific information acquisition determination, the determination unit determines that the transaction is valid if store-specific information has been acquired, and determines that the transaction is invalid if no store-specific information has been acquired even after a certain period of time has passed. The notification unit does not notify an error if a valid determination result is obtained in the store-specific information acquisition determination, and notifies an error if an invalid determination result is obtained.

[0195] (Modification 1 of the notification process shown in step S808 of FIG. 8) Fig. 24 is a flowchart showing a first modified example of the notification process based on location information performed by the mobile terminal device 50. As shown in Fig. 24, the mobile terminal device 50 judges whether or not a predetermined timing has come when a period during which location information of the current location has not been acquired has reached a predetermined period, for example, due to being underground (step S2401). The mobile terminal device 50 waits until the predetermined timing comes (step S2401: NO). When the predetermined timing comes (step S2401: YES), the mobile terminal device 50 judges whether or not the product to be weighed has been registered (step S2402).

[0196] If the commodity to be weighed is registered (step S2402: YES), it is clear that the customer is present in the store, so the mobile terminal device 50 ends the process without performing location information acquisition determination and presence determination.

[0197] On the other hand, if the commodity to be weighed is not registered (step S2402: NO), the mobile terminal device 50 (CPU 401) requests the GPS unit 411 to acquire location information of the current location (step S2403). Then, the mobile terminal device 50 performs a location information acquisition determination as to whether or not the location information of the current location has been acquired (step S2404).

[0198] When the location information of the current location is acquired (step S2404: YES), the mobile terminal device 50 compares the location information of the current location with the location information of the store to perform a presence determination as to whether the current location of the mobile terminal device 50 is out of range (outside the store) (step S2405). If the presence determination shows that the current location of the mobile terminal device 50 is not out of range (step S2405: NO), that is, if the current location of the mobile terminal device 50 is within range (inside the store), the process ends.

[0199] On the other hand, if the presence determination indicates that the current location of the mobile terminal device 50 is out of range (step S2405: YES), that is, if the registration operation is expected to be performed by a customer (member) who came to the store to check a price or the like, an error is notified that the mobile terminal device 50 (the customer) is outside the store (step S2406). Then, the mobile terminal device 50 restricts product registration (step S2407), and ends the series of processes.

[0200] Furthermore, if the location information of the current location is not acquired in the location information acquisition determination in step S2404 (step S2404: NO), that is, for example, if the communication environment is still not good, such as when the user is underground, the mobile terminal device 50 determines whether to perform a retry (step S2408). Note that the retry is performed automatically or by receiving an operation to perform a retry from the customer, for example, within a preset upper limit. If the upper limit is exceeded, the process may proceed to step S2409.

[0201] If a retry is to be performed (step S2408: YES), the mobile terminal device 50 returns to step S2403. If a retry is not to be performed (step S2408: NO), the mobile terminal device 50 requests acquisition of store identification information of the store (step S2409). Then, the mobile terminal device 50 performs a store identification information acquisition determination as to whether or not the store identification information of the store has been acquired (step S2410). If the store identification information of the store has been acquired (step S2410: YES), the mobile terminal device 50 ends the series of processes. On the other hand, if the store identification information of the store has not been acquired even after a certain period of time has elapsed (step S2410: NO), the mobile terminal device 50 proceeds to step S2406 and notifies an error. Note that the mobile terminal device 50 also notifies an error if the acquired store identification information is not the store identification information of the store.

[0202] As described above, in the first modification, the mobile terminal device 50 requests acquisition of store identification information when location information is not acquired, and performs a store identification information acquisition determination. This allows a customer to clearly indicate that he or she is in the store by having the mobile terminal device 50 read the store identification information (two-dimensional code) even if the customer is located in an area with poor communication environment. This makes it possible to prevent unauthorized customers from registering products that check prices, etc.

[0203] (Variation 2) Next, a second modification of the embodiment will be described. In the first modification described above, a configuration is described in which a notification based on a store specific information acquisition determination is performed regardless of the start condition of the transaction. Instead of or in addition to such a configuration, in the second modification, a configuration is described in which a notification based on a store specific information acquisition determination is not performed in a transaction in which a second condition is satisfied.

[0204] In the second modification, the request unit (first request means) requests acquisition of store specific information in a transaction in which the first condition is satisfied, when location information cannot be acquired due to a poor communication environment, etc. On the other hand, the request unit does not request acquisition of store specific information in a transaction in which the second condition is satisfied.

[0205] (Modification 2 of the notification process shown in step S808 of FIG. 8) Fig. 25 is a flowchart showing a second modified example of the reporting process based on location information performed by the mobile terminal device 50. The flowchart shown in Fig. 25 differs from the flowchart shown in Fig. 24 in step S2501. Therefore, only step S2501 will be described below.

[0206] 25, when the mobile terminal device 50 determines in step S2402 that the commodity to be weighed is not registered (step S2402: NO), it determines whether the transaction is due to the first condition being met (a condition in which a store is identified using location information) (step S2501). If the transaction is not due to the first condition being met (step S2501: NO), that is, if the transaction is due to the second condition being met (a condition in which a store is identified using store identification information), the mobile terminal device 50 ends the process. This makes it possible to prevent a notification based on a presence determination from being made in a transaction due to the second condition being met, thereby reducing the frequency of error notifications.

[0207] On the other hand, if the transaction is due to the first condition being met (step S2501: YES), the mobile terminal device 50 (CPU 401) proceeds to step S2403 and requests the GPS unit 411 to obtain location information of the current location (step S2403).

[0208] As described above, in the second modification, the mobile terminal device 50 does not issue a notification based on the location information acquisition determination, the presence determination, and the store specific information acquisition determination in a transaction in which the second condition is satisfied. This makes it possible to reduce the frequency of error notifications in a transaction in which the second condition is satisfied.

[0209] (Variation 3) Next, a third modification of the embodiment will be described. In the second modification, a configuration in which a notification based on a store specific information acquisition determination is not performed in a transaction in which the second condition is satisfied is described. Instead of or in addition to such a configuration, in the third modification, a configuration in which a notification based on a store specific information acquisition determination is not performed in a transaction in which the first condition is satisfied is described.

[0210] In the third variation, the request unit (second request means) makes a request to acquire store identifying information in response to a predetermined time having elapsed since the start of product registration in a transaction in which the second condition is satisfied by acquiring store identifying information. The predetermined time is, for example, 15 minutes. The request unit makes a request to acquire store identifying information each time the predetermined time has elapsed between the start of the transaction and the start of settlement. On the other hand, the request unit (second request means) does not make a request to acquire store identifying information in a transaction in which the first condition is satisfied by acquiring location information.

[0211] Furthermore, two-dimensional codes indicating store identification information may be placed in various places in the store. This allows the mobile terminal device 50 to read the two-dimensional codes wherever the customer is in the store. That is, the store identification information acquisition unit can acquire the store identification information. The identification information determination is performed using the store identification information acquired in response to an acquisition request by the request unit.

[0212] Here, in a transaction in which the first condition is satisfied, the mobile terminal device 50 can periodically acquire location information and perform a presence determination. Therefore, in a transaction in which the first condition is satisfied, the determination unit does not perform a store specific information acquisition determination. Therefore, in a transaction in which the first condition is satisfied, the notification unit does not notify of an error based on the store specific information acquisition determination.

[0213] On the other hand, in a transaction in which the second condition is satisfied, periodic location confirmation cannot be performed. Therefore, in a transaction in which the second condition is satisfied, the determination unit determines whether store-specific information has been acquired. Then, in a transaction in which the second condition is satisfied, the notification unit notifies an error based on the determination that store-specific information has been acquired.

[0214] (Modification 3 of the notification process shown in step S808 of FIG. 8) Fig. 26 is a flowchart showing a third modified example of the notification process based on store-specific information performed by the mobile terminal device 50. As shown in Fig. 26, the mobile terminal device 50 determines whether a predetermined time (e.g., 20 minutes) has elapsed (step S2601). The mobile terminal device 50 waits until the predetermined time has elapsed (step S2601: NO). When the predetermined time has elapsed (step S2601: YES), the mobile terminal device 50 determines whether the product to be weighed has been registered (step S2602).

[0215] If the commodity to be weighed is registered (step S2602: YES), it is clear that the customer is present in the store, so the mobile terminal device 50 does not perform a location information acquisition determination and ends the process.

[0216] On the other hand, if the product to be weighed is not registered (step S2602: NO), the mobile terminal device 50 determines whether the transaction is due to the first condition (the condition that the store is identified using location information) being met (step S2603). If the transaction is due to the first condition being met (step S2603: YES), the mobile terminal device 50 ends the process without determining whether location information has been obtained.

[0217] On the other hand, if the transaction is not due to the first condition being satisfied (step S2603: NO), that is, if the transaction is due to the second condition being satisfied (a condition in which a store is identified using store identification information), the mobile terminal device 50 makes a request to acquire store identification information for the store (step S2604). Then, the mobile terminal device 50 makes a store identification information acquisition determination as to whether or not the store identification information for the store has been acquired (step S2605). If the store identification information for the store has been acquired (step S2605: YES), the mobile terminal device 50 ends the series of processes.

[0218] On the other hand, if the store identification information of the store is not acquired even after a certain period of time has elapsed (step S2605: NO), the mobile terminal device 50 notifies an error (step S2606). Then, the mobile terminal device 50 restricts product registration (step S2607) and ends the series of processes.

[0219] As described above, in the third modification, in a transaction in which the second condition is satisfied, the mobile terminal device 50 requests acquisition of store specific information in response to the passage of a predetermined time from the start of product registration, and performs a store specific information acquisition determination using the store specific information acquired in response to the acquisition request. In this way, in a transaction in which the second condition is satisfied, the mobile terminal device 50 can read the store specific information (two-dimensional code) to make it clear that the customer is in the store. This makes it possible to prevent unauthorized customers from registering products by performing price checks, etc.

[0220] Furthermore, since the mobile terminal device 50 can periodically acquire location information and perform presence determination in a transaction in which the first condition is satisfied, it is possible to prevent error notification based on the store-specific information acquisition determination. This makes it possible to reduce the frequency of error notification in a transaction in which the first condition is satisfied.

[0221] (Variation 4) Next, a fourth modified example of the embodiment will be described. In the third modified example described above, a configuration in which the store identification information is not updated will be described. Instead of or in addition to such a configuration, in the fourth modified example, a configuration will be described in which updated store identification information and non-updated store identification information can be used.

[0222] In the fourth variant, the store identifying information includes updated store identifying information (hereinafter referred to as "one-time password") that is updated at a predetermined timing, and non-updated store identifying information that is not updated. The one-time password is displayed, for example, on a monitor. The predetermined timing is, for example, 30 minutes. The one-time password is, for example, set with an expiration date, so that an expired one cannot identify the store. The monitor is placed near the entrance / exit of the store. The non-updated store identifying information is, for example, printed on paper and posted. The one-time password and the non-updated store identifying information are each presented at different stores, but may also be presented at the same store.

[0223] Here, the fact that the one-time password is read means that there is a high degree of credibility that the customer is present at the store. Therefore, in a transaction in which the one-time password is obtained and the second condition is met, the notification unit does not notify of an error based on the determination of whether store-specific information has been obtained.

[0224] On the other hand, by capturing an image of non-updated store identifying information with a camera and storing it, it is possible to read outdated information outside the store. Therefore, when non-updated store identifying information is read, it means that there is less credibility that the customer is in the store compared to when updated store identifying information is obtained. Therefore, the notification unit notifies an error based on the store identifying information acquisition determination in a transaction due to the establishment of the second condition in which non-updated store identifying information is obtained.

[0225] In addition, in the fourth modification, the request unit (second request means) requests acquisition of non-store specific information in response to a predetermined time having elapsed since the start of product registration in a transaction in which the second condition is satisfied by acquiring non-updated store specific information. The store specific information that is the subject of the acquisition request is not limited to non-updated store specific information, and may be a one-time password. That is, in a store in which both a one-time password and non-updated store specific information are presented, the request unit may request acquisition of a one-time password.

[0226] Furthermore, in the store, store identification codes (two-dimensional codes) indicating non-store identification information may be placed in various places. This allows the mobile terminal device 50 to read the store identification codes wherever the customer is in the store. That is, the store identification information acquisition unit can acquire the non-store identification information. The identification information determination is performed using the non-store identification information acquired in response to an acquisition request by the request unit.

[0227] In addition, in the fourth variant, in a transaction in which the first condition is satisfied, a notification may be made based on a store-specific information acquisition determination (configuration of the second variant), or may not be made (configuration of the third variant).

[0228] (Modification 4 of the notification process shown in step S808 of FIG. 8) Fig. 27 is a flowchart showing a fourth modified example of the notification process based on location information performed by the mobile terminal device 50. The flowchart shown in Fig. 27 differs from the flowchart shown in Fig. 26 in step S2701. Therefore, only step S2701 will be described below. As shown in Fig. 27, when the mobile terminal device 50 determines in step S2603 that the transaction is not the transaction for which the first condition is satisfied (step S2603: NO), that is, when the transaction is the transaction for which the second condition (the condition for identifying the store using store identifying information) is satisfied, the mobile terminal device 50 determines whether the transaction is the transaction for which the second condition is satisfied by obtaining a one-time password (step S2701).

[0229] If the transaction is one in which the second condition is met by acquiring a one-time password (step S2701: YES), the mobile terminal device 50 ends the process. This makes it possible to prevent a notification based on the store-specific information acquisition determination from being issued in a transaction in which the second condition is met by acquiring a one-time password, thereby reducing the frequency of error notifications.

[0230] On the other hand, if the transaction does not satisfy the second condition by obtaining a one-time password (step S2701: NO), that is, if the transaction satisfies the second condition by obtaining non-updated store-specific information, the mobile terminal device 50 proceeds to step S2604 and makes a request to obtain store-specific information for the store.

[0231] As described above, in the fourth modification, the mobile terminal device 50 is configured not to notify of an error based on the determination of acquisition of store specific information in a transaction where the second condition is met in which a one-time password is acquired. Therefore, when it is expected that the customer is likely to be in the store, an error based on the determination of acquisition of store specific information is not notified, so that the frequency of errors can be reduced.

[0232] In addition, in the fourth modification, in a transaction where the second condition is met and non-updated store specific information is acquired, an error is reported based on the store specific information acquisition judgment. This makes it possible to report an error when it is expected that the customer is unlikely to be in the store, thereby preventing inappropriate product registrations such as price checks.

[0233] (Variation 5) Next, a fifth modified example of the embodiment will be described. In the above-described embodiment, a configuration in which a notification based on an operation determination is performed regardless of the start condition of the transaction is described. Instead of or in addition to such a configuration, in the fifth modified example, a configuration in which a notification based on an operation determination is not performed in a transaction in which the second condition is met will be described.

[0234] In the fifth modification, in a transaction in which the first condition is satisfied, the notification unit issues a notification based on the operation determination, whereas in a transaction in which the second condition is satisfied, the notification unit does not issue a notification based on the operation determination.

[0235] (Fifth modified example of the notification process shown in step S808 of FIG. 8) Fig. 28 is a flowchart showing a fifth modified example of the notification process based on product registration operation information performed by the mobile terminal device 50. The flowchart shown in Fig. 28 is different from the flowchart shown in Fig. 20 in step S2801. Therefore, only step S2801 will be described below.

[0236] 28, the mobile terminal device 50 judges whether the transaction is due to the first condition (the condition that a store is identified using location information) being satisfied (step S2801). If the transaction is not due to the first condition being satisfied (step S2801: NO), that is, if the transaction is due to the second condition (the condition that a store is identified using store identification information) being satisfied, the mobile terminal device 50 ends the series of processes without performing operation judgment. On the other hand, if the transaction is due to the first condition being satisfied in step S2801 (step S2801: YES), the mobile terminal device 50 (CPU 401) proceeds to step S2001 and makes a request to acquire product registration operation information stored in the memory 404.

[0237] As described above, in the fifth modification, the mobile terminal device 50 does not notify an error based on the operation judgment in a transaction in which the second condition is satisfied. This makes it possible to reduce the frequency of error notifications in a transaction in which the second condition is satisfied.

[0238] (Variation 6) Next, a sixth modified example of the embodiment will be described. In the fifth modified example described above, a configuration in which a notification based on an operation determination is not performed in a transaction in which the second condition is satisfied is performed is described. Instead of or in addition to such a configuration, in the sixth modified example, a configuration in which a notification based on an operation determination is not performed in a transaction in which the first condition is satisfied is described.

[0239] In the sixth modification, in a transaction in which the first condition is satisfied, the notification unit does not issue a notification based on the operation determination, whereas in a transaction in which the second condition is satisfied, the notification unit issues a notification based on the operation determination.

[0240] (Variation 6 of the notification process shown in step S808 of FIG. 8) Fig. 29 is a flowchart showing a sixth modified example of the notification process based on product registration operation information performed by the mobile terminal device 50. The flowchart shown in Fig. 29 is different from the flowchart shown in Fig. 20 in step S2901. Therefore, only step S2901 will be described below.

[0241] 29, the mobile terminal device 50 judges whether the transaction is due to the fulfillment of the second condition (the condition that the store is identified using the store identification information) (step S2901). If the transaction is not due to the fulfillment of the second condition (step S2901: NO), that is, if the transaction is due to the fulfillment of the first condition (the condition that the store is identified using the location information), the mobile terminal device 50 ends the series of processes without performing operation judgment. On the other hand, if the transaction is due to the fulfillment of the first condition in step S2901 (step S2901: YES), the mobile terminal device 50 (CPU 401) proceeds to step S2001 and makes a request to acquire product registration operation information stored in the memory 404.

[0242] As described above, in the sixth modification, the mobile terminal device 50 does not notify an error based on the operation judgment in a transaction in which the first condition is satisfied. This makes it possible to reduce the frequency of error notifications in a transaction in which the first condition is satisfied.

[0243] (Variation 7) Next, a seventh modification of the embodiment will be described. In the sixth modification described above, a configuration is described in which a notification based on an operation determination is made in a transaction in which the second condition is satisfied. Instead of or in addition to such a configuration, in the seventh modification, a configuration is described in which a notification based on an operation determination is not made in a transaction in which a one-time password is acquired even in a transaction in which the second condition is satisfied.

[0244] If a one-time password is acquired, there is a low possibility that improper product registration, such as price checks, will be performed outside the store. For this reason, in the seventh modification, the notification unit is configured not to notify of an error based on the operation judgment in a transaction in which the second condition is met in which a one-time password is acquired.

[0245] On the other hand, in the case of non-updated store specific information, it is possible to read past information outside the store by capturing an image with a camera and storing it. Therefore, when non-updated store specific information is acquired, there is a higher possibility that improper product registration such as price checks will be performed outside the store compared to when a one-time password is acquired. For this reason, the notification unit is configured to notify of an error based on an operation determination in a transaction due to the establishment of the second condition in which non-updated store specific information is acquired.

[0246] In the seventh modification, in a transaction in which the first condition is met, a notification based on an operation determination may be made (the configuration of the fifth modification), or may not be made (the configuration of the sixth modification).

[0247] (Seventh modification of the notification process shown in step S808 of FIG. 8) Fig. 30 is a flowchart showing a seventh modified example of the notification process based on product registration operation information performed by the mobile terminal device 50. The flowchart shown in Fig. 30 is different from the flowchart shown in Fig. 29 in step S3001. Therefore, only step S3001 will be described below.

[0248] As shown in FIG. 30, if the mobile terminal device 50 determines in step S2901 that the transaction is a transaction in which the second condition is satisfied (step S2901: YES), it determines whether the transaction is a transaction in which a one-time password is obtained (step S3001).

[0249] If the transaction is a transaction for which a one-time password is obtained (step S3001: YES), the mobile terminal device 50 ends the process. This makes it possible to prevent a notification based on the operation determination from being made in a transaction for which the second condition is satisfied by obtaining a one-time password, thereby reducing the frequency of error notifications.

[0250] On the other hand, if the transaction is not one in which the second condition is satisfied by obtaining a one-time password (step S3001: NO), that is, if the transaction is one in which the second condition is satisfied by obtaining non-updated store-specific information, the mobile terminal device 50 (CPU 401) proceeds to step S2001 and makes a request to obtain product registration operation information stored in memory 404.

[0251] As described above, in the seventh modification, the mobile terminal device 50 is configured not to notify an error based on the operation judgment in a transaction in which the second condition is met and a one-time password is acquired. Therefore, since an error is not notified when it is expected that there is a low possibility of an improper product registration such as a price check outside the store, the frequency of errors can be reduced.

[0252] In addition, in the seventh modification, in a transaction in which the second condition is met in which non-updated store-specific information is acquired, an error based on an operation determination is notified. This makes it possible to notify an error when it is expected that there is a high possibility that improper product registration such as price checks will be performed outside the store, thereby preventing improper product registration such as price checks.

[0253] (Variation 8) Next, an eighth modified example of the embodiment will be described. In the above-described embodiment, an error is not notified when location information cannot be acquired (see FIG. 18). Instead of or in addition to such a configuration, an eighth modified example will be described in which an error is notified when the GPS function is turned off.

[0254] The following will be described with reference to Fig. 18. In the eighth modification, in step S1804 in Fig. 18, if the location information cannot be acquired, the mobile terminal device 50 determines whether or not the GPS function is OFF. If the GPS function is ON, the process ends without performing a presence determination. On the other hand, if the GPS function is OFF, a notification is given to turn the GPS function ON. Furthermore, the mobile terminal device 50 may not end the process shown in Fig. 18 until the GPS function is ON. Furthermore, if the GPS function is not turned ON even after a certain period of time has elapsed, an error may be given to the effect that the mobile terminal device 50 (the customer) is outside the store, or product registration may be restricted.

[0255] According to the eighth modification, it is possible to prevent a customer from intentionally turning off the GPS function and performing an inappropriate product registration such as a price check.

[0256] (Variation 9) Next, a ninth modified example of the embodiment will be described. In the above-described embodiment, an error based on location information is not notified when a product to be weighed is registered (see FIG. 18). Instead of or in addition to this configuration, in the ninth modified example, an error based on location information may be notified regardless of whether a product to be weighed is registered.

[0257] Specifically, in the notification process based on location information according to the ninth modification (see FIG. 18), a location information acquisition determination and a presence determination are performed regardless of whether or not a product to be weighed is registered. Specifically, the mobile terminal device 50 may not perform the process of step S1801 in FIG. 18. This allows the location information acquisition determination, presence determination, and store-specific information acquisition determination to be performed even if a product to be weighed is registered. This allows an error notification to be performed according to the determination result of each determination.

[0258] (Variation 10) Next, a tenth modified example of the embodiment will be described. In the above-described embodiment, an error based on the registered operation information is notified regardless of whether the product to be weighed is registered (see FIG. 20). Instead of or in addition to this configuration, in the tenth modified example, when the product to be weighed is registered, an error based on the registered operation information may not be notified.

[0259] Specifically, in the tenth modification, the mobile terminal device 50 determines whether or not the product to be weighed is registered before the process of step S2001 in Fig. 20, and if the product to be weighed is registered, the process ends. In this way, if the product to be weighed is registered, there is a low risk of an inappropriate product being registered, and therefore it is possible to prevent an error based on the operation determination from being notified. Therefore, the frequency of errors can be reduced.

[0260] (Variation 11) Next, an eleventh modified example of the embodiment will be described. In the above-described embodiment, an error based on a validity determination is not notified when the commodity to be weighed is registered. Instead of or in addition to this configuration, in the eleventh modified example, an error based on a validity determination may not be notified when the commodity to be weighed is not registered, but there is simply a connection history with the weighing device 30.

[0261] In this way, if there is a connection history with the weighing device 30, it is clear that the weighing target product is present in the store even if it is not registered. Therefore, it is possible to prevent an error based on a validity determination from being notified. Even if this is done, the frequency of errors can be reduced.

[0262] The embodiments will be summarized below. [Name of invention] Terminal device, product sales data processing system, notification method, and program [Technical field] The present invention relates to a terminal device, a product sales data processing system, a notification method, and a program. [Background technology] In recent years, a system has become known in which a shopping application is installed on a mobile terminal device such as a smartphone carried by a customer, and the customer registers products by themselves in a store (see, for example, Patent Document 1). The mobile terminal periodically checks its own location, and if it is not located within the store, it reports an error. [Prior art document] [Patent documents] [Patent Document 1] Special Publication No. 2013-541107 [Summary of the Invention] [Problem to be solved by the invention] However, in the conventional technology, if an error is frequently reported, the customer may not be able to shop smoothly. For example, in an environment where it is difficult to obtain location information, such as when the store is located underground, the mobile terminal device may determine that it is not located within the store and may frequently report an error. The present invention has been made in view of such circumstances, and its purpose is to provide a technology that allows customers to shop smoothly. [Means for solving the problem]

[0263] (1) In order to solve the above-mentioned problems, a terminal device according to one embodiment of the present invention includes: location information acquisition means for acquiring location information indicating a current location; store identification information acquisition means for acquiring store identification information presented in a store; registration means for starting product registration in response to the establishment of one of a first condition for identifying the store using the location information and a second condition for identifying the store using the store identification information; determination means for determining whether the product registration is being performed legitimately; and notification means for notifying an error using a determination result of the determination means, wherein the notification means issues the notification based on the start condition that has been established. According to the above configuration, the frequency of error notifications can be made different for transactions resulting from the fulfillment of the first condition and transactions resulting from the fulfillment of the second condition, so that the frequency of errors can be reduced according to the start condition. Therefore, according to this embodiment, it is possible to prevent shopping from being hindered by error notifications, so that shopping can be carried out smoothly.

[0264] (2) In the configuration of (1) above, the legitimacy determination may include a presence determination of whether or not the product is present in the store using the location information obtained during the transaction, and the notification means may issue the notification based on the presence determination in a transaction where the first condition is satisfied, and may not issue the notification based on the presence determination in a transaction where the second condition is satisfied. According to the above configuration, in a transaction in which the second condition is satisfied, it is possible to prevent a notification based on the presence determination from being made. Therefore, in a transaction in which the second condition is satisfied, it is possible to reduce the frequency of error notifications.

[0265] (3) In the configuration of (1) or (2) above, the legitimacy determination may include a location information acquisition determination as to whether or not the location information was acquired during the transaction, and the notification means may not issue the notification even if the result of the location information acquisition determination is that the location information was not acquired. According to the above configuration, when the communication environment is not good, it is possible to prevent frequent error notifications.

[0266] (4) In the above configuration (3), a first request means may be provided for making a request to acquire the store identifying information in response to a determination result that the location information is not to be acquired in the location information acquisition determination. According to the above configuration, even if a customer is located in an area with poor communication environment, the customer can clearly identify that he or she is in the store by having the mobile terminal device 50 read the store identification information (two-dimensional code). Therefore, it is possible to prevent unauthorized customers from registering products for price checks, etc.

[0267] (5) In any of the above configurations (1) to (4), the validity determination may include an operation determination as to whether or not an operation related to the product registration has been performed validly. According to the above configuration, if an improper registration operation such as a price check is performed, an error can be notified. Therefore, improper product registration such as a price check can be prevented. Therefore, various information in the store such as price information can be prevented from being easily leaked.

[0268] (6) In any of the configurations (1) to (5) above, the legitimacy determination may include a store-specific information acquisition determination as to whether or not the store-specific information has been acquired during the transaction, and the notification means may not provide the notification based on the store-specific information acquisition determination in a transaction in which the first condition is satisfied, and may provide the notification based on the store-specific information acquisition determination in a transaction in which the second condition is satisfied. According to the above configuration, in a transaction in which the second condition is satisfied, the presence of the customer in the store can be made clear by having the mobile terminal device 50 read the store identification information (two-dimensional code). This makes it possible to prevent unauthorized customers from registering products that check prices, etc. In addition, in a transaction in which the first condition is satisfied, location information can be periodically acquired to perform a presence determination, so that an error notification based on the determination of the acquisition of store identification information is not issued. This makes it possible to reduce the frequency of error notifications in a transaction in which the first condition is satisfied.

[0269] (7) In the configuration of (6) above, a second request means may be provided for making a request to acquire the store-specific information in response to a predetermined time having elapsed since the start of the product registration in a transaction in which the second condition is satisfied. According to the above configuration, in a transaction in which the second condition is satisfied, the mobile terminal device 50 reads the store identification information (two-dimensional code) every time a predetermined time elapses, thereby making it clear that the customer is in the store. Therefore, it is possible to prevent unauthorized customers from registering products to check prices, etc.

[0270] (8) In any of the configurations (1) to (7) above, the store identification information may include updated store identification information that is updated at a predetermined timing and non-updated store identification information that is not updated, and the notification means may not issue the notification based on the validity determination in a transaction resulting from the fulfillment of the second condition for which the updated store identification information is obtained, and may issue the notification based on the validity determination in a transaction resulting from the fulfillment of the second condition for which the non-updated store identification information is obtained. According to the above configuration, in the case of a transaction based on the acquisition of updated store specific information, it is expected that the customer is likely to be in the store, so it is possible to prevent an error based on the store specific information acquisition judgment or the operation judgment from being notified. Also, in the case of a transaction based on the acquisition of non-updated store specific information, it is expected that the customer is unlikely to be in the store, so by making it possible to notify the error, it is possible to suppress improper product registration such as price checks.

[0271] (9) In any of the configurations (1) to (8) above, the registration means may be capable of registering the commodity to be weighed by communicating with a weighing device that weighs the commodity to be weighed, and the notification means may be configured not to issue the notification when the commodity to be weighed is registered, regardless of the start condition. According to the above configuration, when it is clear that a customer is present in the store, it is possible to prevent an error notification from being issued.

[0272] (10) In any of the configurations (1) to (9) above, a third request means may be provided for making a request to acquire the store identifying information if the first condition is not satisfied, and the registration means may start the product registration in response to the satisfaction of the second condition being satisfied by the store identifying information being acquired in response to the request made by the third request means. According to the above configuration, even if location information cannot be acquired, acquisition of store-specific information can be prompted, and product registration can be started.

[0273] (11) In order to solve the above-mentioned problems, a product sales data processing system which is another aspect of the present invention is a product sales data processing system including a terminal device operated by a customer, and comprises: location information acquisition means for acquiring location information indicating a current location; store identification information acquisition means for acquiring store identification information presented in a store; registration means for starting product registration in response to the establishment of either a first condition under which the store is identified using the location information or a second condition under which the store is identified using the store identification information; determination means for making a validity determination as to whether the product registration is being performed validly; and notification means for notifying an error using a determination result of the determination means, wherein the notification means makes the notification based on the start condition that has been established. This product sales data processing system is characterized in that it comprises: location information acquisition means for acquiring location information indicating a current location; store identification information acquisition means for acquiring store identification information presented in a store; registration means for starting product registration in response to the establishment of either a first condition under which the store is identified using the location information or a second condition under which the store is identified using the store identification information; determination means for making a validity determination as to whether the product registration is being performed validly; and notification means for notifying an error using a determination result of the determination means. According to the above configuration, the frequency of error notifications can be made different for transactions resulting from the fulfillment of the first condition and transactions resulting from the fulfillment of the second condition, so that the frequency of errors can be reduced according to the start condition. Therefore, according to this embodiment, it is possible to prevent shopping from being hindered by error notifications, so that shopping can be carried out smoothly.

[0274] (12) In order to solve the above-mentioned problems, another aspect of the present invention is an alert method, the alert method comprising the steps of: a location information acquisition step in which a computer used in a terminal device acquires location information indicating a current location; a store identification information acquisition step in which store identification information presented in a store is acquired; a registration step in which product registration is started in response to the establishment of one of a first condition for identifying the store using the location information and a second condition for identifying the store using the store identification information; a determination step in which the product registration is determined to be valid or not; and a notification step in which an error is notified using the determination result in the determination step, wherein in the notification step, the alert is made based on the start condition that has been established. According to the above configuration, the frequency of error notifications can be made different for transactions resulting from the fulfillment of the first condition and transactions resulting from the fulfillment of the second condition, so that the frequency of errors can be reduced according to the start condition. Therefore, according to this embodiment, it is possible to prevent shopping from being hindered by error notifications, so that shopping can be carried out smoothly.

[0275] (13) In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes a computer used in a terminal device to function as: location information acquisition means for acquiring location information indicating a current location; store identification information acquisition means for acquiring store identification information presented in a store; registration means for starting product registration in response to the establishment of either a first condition for identifying the store using the location information or a second condition for identifying the store using the store identification information; determination means for determining whether the product registration is being performed legitimately; and notification means for notifying an error using a determination result of the determination means, wherein the notification means makes the notification based on the start condition that has been established. According to the above configuration, the frequency of error notifications can be made different for transactions resulting from the fulfillment of the first condition and transactions resulting from the fulfillment of the second condition, so that the frequency of errors can be reduced according to the start condition. Therefore, according to this embodiment, it is possible to prevent shopping from being hindered by error notifications, so that shopping can be carried out smoothly.

[0276] In addition, all or part of each function (input / output, storage, processing (including judgment)) of each device (mobile terminal device 50, etc.) described above may be realized in a device other than the device described as the entity that executes the function.

[0277] Specifically, in the above description, the mobile terminal device 50 is described as having a location information acquisition unit, a store identification information acquisition unit, a registration unit, a determination unit, a notification unit, and a request unit. All or a part of these functional units may be provided in another computer device. For example, all or a part of these functional units may be provided in the transaction status management device 11, the cloud server Sv, or other computer devices. In addition, the computer device in which these functional units are provided is not limited to being multiple, and may be one. For example, one computer device may have all of these functional units.

[0278] Specifically, for example, instead of the mobile terminal device 50, the transaction status management device 11 or the cloud server Sv may store information after product registration (registration data). Also, for example, instead of the transaction status management device 11 or the cloud server Sv, the transaction status management device 11 or the cloud server Sv may execute various processes such as notification processes (see Figs. 8, 18, and 20). That is, for example, the process of determining the start conditions of a transaction, which has been described as being executed by the mobile terminal device 50 in step S1802 of the flowchart in Fig. 18, and the process of notifying an error, which is executed in step S1806, may be executed by the transaction status management device 11 or the cloud server Sv.

[0279] In relation to the above, the mobile terminal device 50 may function as a so-called thin client specialized in an input / output interface portion with respect to product registration. In other words, the mobile terminal device 50 may accept various inputs (operation by an operator, detection by a device such as a scanner), transmit input information (operation information, scan information, etc.) to the cloud server Sv, receive the processing results of the cloud server Sv based on the input information (update screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device).

[0280] The above-described shopping system 1 and the program for implementing the mobile terminal device 50 may be recorded in a computer-readable recording medium, and the program may be read and executed by the computer system. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as a flexible disk, an optical magnetic disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built into the computer system. The term "computer-readable recording medium" also refers to a storage device 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 such as the Internet or a communication line such as a telephone line. The above-described program may be transmitted from a computer system that stores the program in a storage device to another computer system via a transmission medium or by a transmission wave in the transmission medium. The "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The above-described program may also be for implementing a part of the above-described 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]

[0281] Sv...cloud server, 1...shopping system, 10...store controller, 11...transaction status management device, 20...POS terminal device, 30...weighing device, 50...mobile terminal device, 201, 301, 401...CPU, 205...customer side display unit, 215, 305, 405...communication unit, 406...operation unit, 407...camera, 409...display, 411...GPS unit

Claims

[Claim 1] A location information acquisition means for acquiring location information indicating a current location; A store specific information acquisition means for acquiring store specific information presented in a store; a registration means for starting product registration in response to the establishment of one of a first condition for identifying the store using the location information and a second condition for identifying the store using the store identification information; A determination means for determining whether the product registration is valid or not; a notification means for notifying an error using a result of the determination by the determination means; Equipped with The notification means performs the notification based on the start condition that has been established. A mobile terminal device comprising:

Images