program

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 Program this.

Background Art

[0002] In recent years, a system has been known in which a shopping application is installed on a mobile terminal device such as a smartphone possessed by a customer, and the customer registers a product by his / her own operation in a store (see, for example, Patent Document 1). The mobile terminal device periodically checks the position of its own device and notifies an error when the device is not located inside the store.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art, there has been a problem that if an error is frequently notified, it may not be possible to allow a customer to smoothly make a purchase. For example, in an environment where it is difficult to acquire position information, such as when a store is located underground, the mobile terminal device may determine that it is not located inside the store and frequently notify an error.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technology that enables a customer to smoothly make a purchase.

Means for Solving the Problems

[0006] In order to solve the above problems, a terminal device according to an aspect of the present invention includes position information acquisition means for acquiring position information indicating a current location, store specific information acquisition means for acquiring store specific information presented in a store, and a first condition for specifying the store using the position information and a second condition for specifying the store using the store specific information. Registration means for starting product registration in response to the establishment of any one of the start conditions, determination means for making a validity determination as to whether the product registration is being properly performed, and notification means for performing error notification using the determination result of the determination means. The notification means performs the notification based on the established start condition. A terminal device characterized by that.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

[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 the 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 into various stores such as supermarkets, home improvement stores, 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 are communicably 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 communicably connected via a LAN (Local Area Network) 55. Each device and each terminal are computer devices equipped with a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, and the like.

[0012] The cloud server Sv is a server device that manages various types of information such as information about customers, information about stores, and information about products for each store. For example, based on the product information read by the mobile terminal device 50, the cloud server Sv generates cart information indicating a virtual cart for each customer and registers the product in the virtual cart. 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 device 20 and the weighing device 30, and stores various types of information necessary for transactions such as a product master. The product master is a file in which product information such as product identification information (for example, JAN (Japanese Article Number) code), product name, and selling price of each product is stored. In addition, the product master includes product identification information of products that require weighing (hereinafter referred to as "weighing target products"), product names, unit prices of weighing target products, and the like. In addition to the product master, the store controller 10 stores various types of 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 (operation mode, processing status, etc.) of the POS terminal device 20 and controls the POS terminal device 20. Further, the transaction status management device 11 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 have only a monitoring function.

[0015] The POS terminal device 20 is a computer device capable of executing a settlement process for settling (settling) the products registered by the portable terminal device 50. In addition to settling the products registered by the portable terminal device 50, the POS terminal device 20 can also settle the products registered by itself or other POS terminal devices 20. Further, in the present embodiment, the POS terminal device 20 can switch the operation mode. Specifically, the POS terminal device 20 can operate not only in the accounting dedicated mode that functions as a dedicated settlement device, but also in the clerk registration mode in which product registration is performed by the operation of a clerk, or in the customer registration mode (full self-service mode) in which product registration is performed by the operation of a customer. Note that in FIG. 1, the number of POS terminal devices 20 is illustrated as a plurality, but it 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 amount of the product to be weighed using the weighed weight (or quantity) and the unit price of the product to be weighed. The product to be weighed is a product different from ordinary products. Here, ordinary products are, for example, products with a JAN code attached. When the portable terminal device 50 reads the JAN code, it inquires the read JAN code to the cloud server Sv and acquires the price data associated with the JAN code.

[0017] On the one hand, the merchandise to be weighed is merchandise whose price varies according to the weight or quantity of the item. The merchandise to be weighed is, for example, fresh food such as vegetables, fruits, fresh fish, and meat, or prepared dishes. The weighing device 30 prints and outputs a label encoding the amount, weight, etc. of the merchandise to be weighed. The price is included in the label. The label (barcode) attached to the merchandise to be weighed uses the NON-PLU (Price Look Up) method. In FIG. 1, the number of weighing devices 30 is illustrated as a plurality, but it may be one.

[0018] The portable terminal device 50 is a portable computer device such as a smartphone, a tablet device, or a mobile phone. The portable terminal device 50 includes a communication unit, an imaging unit (camera), a touch panel, etc., and is operated by a customer. In the present embodiment, the portable terminal device 50 is detachably attached to the shopping cart. However, the portable terminal device 50 may be fixedly installed to be non-detachable from the shopping cart. Also, the portable terminal device 50 may be the customer's property, or may be a lent item lent by the store to the customer.

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

[0020] Note that the recognition function provided in the portable terminal device 50 only needs to be able to read the product code attached to the product, and it does not necessarily need to be able to identify the product from the read product code. That is, when a barcode exists as an object in the captured image (image acquired as a through image) captured by the imaging function in the portable terminal device 50, it only needs to be able to read the product code from the barcode.

[0021] In addition, the mobile terminal device 50 may be equipped with image recognition technology. Specifically, the mobile terminal device 50 may be equipped with image recognition technology that extracts feature points from an image (a through-image, a captured image) and recognizes an object to be imaged (such as an object). For example, the mobile terminal device 50 may identify (estimate) a captured product using image recognition technology. By using such image recognition technology, the mobile terminal device 50 can also identify fresh foods such as vegetables and fruits without barcodes, for example.

[0022] In addition, application software (hereinafter sometimes referred to as a "shopping app") for registering and settling accounts for products related to the shopping system 1 is installed in the mobile terminal device 50. By activating the shopping app, the mobile terminal device 50 reads a barcode attached to a 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] In addition, when performing settlement, the mobile terminal device 50 has a two-dimensional code (hereinafter sometimes referred to as a "settlement code") corresponding to the registered product. The settlement code is represented by, for example, a QR code (registered trademark). When the POS terminal device 20 reads the settlement code, it sends a request to the cloud server Sv to transmit the registration information corresponding to the mobile terminal device 50. Then, when the POS terminal device 20 receives the registration information from the cloud server Sv, it becomes possible to perform settlement at the POS terminal device 20. Hereinafter, the products registered in the virtual cart may sometimes be referred to as "registered products".

[0024] In addition, in this embodiment, the device for performing settlement is the POS terminal device 20, but it is not limited to this. For example, the device for performing settlement may be a dedicated settlement device installed in the store, or a computer device for settlement detachably installed on the shopping cart. This computer device may, for example, only enable settlement using a credit card or a prepaid card.

[0025] (Installation example of the POS terminal device 20) FIG. 2 is an explanatory diagram showing an installation example of the POS terminal device 20. FIG. 2(A) is a perspective view of the POS terminal device 20 as viewed from the customer side. FIG. 2(B) is a perspective view of the POS terminal device 20 as viewed 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 viewed from the customer side. Although omitted in the illustration, in FIG. 2(A), a counter may also be placed on the left side of the POS terminal device 20. That is, the counter may be placed on both sides of the POS terminal device 20. Also, the counter can hold a shopping basket.

[0026] As shown in FIG. 2, the POS terminal device 20 includes a sign pole 220. The sign pole 220 includes a light emitting part. The light emitting part of the sign pole 220 is, for example, a lamp or an LED (light emitting diode), and can be lit in a predetermined color and a predetermined lighting mode. By the lighting mode of the sign pole 220, it is possible to notify the usage state (in use, warning, clerk call, etc.) of the POS terminal device 20. The sign pole 220 is provided upward, and it is possible to notify the usage state of the POS terminal device 20 to store clerks who are not near the POS terminal device 20.

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

[0028] Hereinafter, with reference to FIG. 2, a configuration example of the POS terminal device 20 shown in FIG. 3 will be described. The POS terminal device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer-side display unit 205, a customer-side scanner unit 206, a card payment unit 208, a change dispenser 209, a store employee-side display unit 210, a key operation unit 211, a store employee-side 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, and 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 memory that can be read from and written to, and stores various types of information. For example, the RAM 203 stores information acquired from the outside (for example, 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 registered products.

[0031] The hard disk 204 stores various types of information. For example, the hard disk 204 stores imaging results (for example, videos) 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. Further, instead of the RAM 203, it may store information acquired from the outside and information generated during processing.

[0032] The customer-side display unit 205 is a touch display for customers. The customer-side display unit 205 displays various types of 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 types of information. For example, the customer-side scanner unit 206 optically reads barcodes (such as product codes) attached to products and codes (barcodes, two-dimensional codes, etc.) printed on accounting tickets (registered trademarks). In addition to the above, the customer-side scanner unit 206 may also read codes (barcodes, two-dimensional codes, etc.) printed on vouchers (product vouchers, coupon vouchers, discount vouchers) and various cards (for example, membership cards, point cards, etc.). Note that the registration of products 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 can be registered when the preset key is operated (pressed) by the customer. Also, the customer-side scanner unit 206 can read the settlement 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 perform settlement based on the read content.

[0033] The card payment unit 208 is a payment mechanism using various cards (credit cards, prepaid cards such as transportation cards, point cards, etc.). The card payment unit 208 includes a card recognition unit (reading unit), a display unit, and an operation unit. The card recognition unit magnetically or electrically reads information on various cards. The read information is used for settling the purchased products. Note that the card recognition unit can also recognize information to be used in the settlement of the current purchased products, for example, when using the points held on a point card. Also, the card recognition unit can recognize information not used in the settlement of the current purchased products, for example, when adding points to a point card.

[0034] Although the card payment unit 208 of this embodiment includes a card recognition unit, a display unit, and an operation unit, it is not limited to these and may include at least a card recognition unit. The card recognition unit of this embodiment may be compatible with contact cards (IC cards, magnetic cards) or contactless cards (IC cards).

[0035] The change machine 209 (cash settlement unit) is a cash settlement mechanism, 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 insertions from customers. The change machine 209 also 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 each 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 the products are registered by the clerk operating (pressing) the preset keys. The clerk-side display unit 210 also displays a subtotal key that accepts the 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 store - side scanner unit 212 is a scanner unit for store employees and optically reads various types of information. For example, the store - side scanner unit 212 optically reads the barcodes attached to products and the employee codes attached to employee name tags. In addition to the above, the store - side scanner unit 212 may also read the codes printed on the receipt vouchers, the product vouchers, and the codes printed on various cards. Also, the store - side scanner unit 212 can read two - dimensional codes for settlement. When the settlement code is read by the store - side scanner unit 212, the POS terminal device 20 can perform settlement based on the read content.

[0039] Note that the registration of products is not limited to registration by reading codes with the store - side scanner unit 212. For example, keys corresponding to products (e.g., ○○ Newspaper) may be arranged on the key operation unit 211, and when the keys are operated (pressed) by the store employee, the registration of the corresponding products may be performed.

[0040] The printing unit 213 prints and outputs various media (receipts, receipts, accounting vouchers, etc.). The printing unit 213 can change the direction of the media outlet. Specifically, the printing unit 213 has a rotatable mechanism and is configured such that the media outlet faces from the store - side to the customer - side and also from the customer - side to the store - side. Note that the direction of the media outlet may be manually changeable or may be automatically changed according to a change in the operation mode. In addition, the printing unit 213 may be equipped with a sensor for detecting the correctness of the direction of the printing outlet.

[0041] The voice output unit 214 outputs voice. For example, the voice output unit 214 outputs voice guidance, warning sounds, etc. The voice guidance and warning sounds are related to product registration and settlement. The communication unit 215 is an interface for transmitting and receiving information with 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-side display unit 205 when viewed from the customer side. The camera 216 is a camera that continuously captures videos or still images. For the camera 216, it is possible to use a CCD (charge coupled device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera. The camera 216 captures the operation status of the customer at the time of settlement. Specifically, the camera 216 captures banknotes, coins, change machines 209, hand movements, etc. held by the customer. Also, the camera 216 captures the operation status of the customer at the time of product registration. Specifically, the camera 216 can also capture the inside of the shopping basket (products) on the counter provided on both sides of the POS terminal device 20 and the operation status of the customer at the time of registration. Additionally, the camera 216 may be separately provided on the store clerk side. In this case, the POS terminal device 20 can determine the presence or absence of the store clerk based on the imaging result of the camera 216 provided on the store clerk side.

[0043] (Hardware Configuration of the Portable Terminal Device 50) FIG. 4 is an explanatory diagram showing an example of the hardware configuration of the portable terminal device 50. In FIG. 4, the portable 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 by a bus 420.

[0044] The CPU 401 controls the entire portable terminal device 50. The ROM 402 records various programs. The RAM 403 is used as a work area for the CPU 401. That is, the CPU 401 controls the entire portable terminal device 50 by executing various programs recorded in the ROM 402 while using the RAM 403 as a work area.

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

[0046] The operation unit 406 is a touch panel that displays a plurality of touch keys for inputting characters, numerical values, various instructions, etc., and hard keys. The camera 407 reads barcodes 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, etc.

[0047] The speaker 410 outputs sounds including voices. The GPS unit 411 has a function of receiving position information from GPS satellites and detecting the current position of the mobile terminal device 50 on the map data. Further, the mobile terminal device 50 is provided with various sensors (not shown) such as a gyro sensor, an acceleration sensor, and a distance sensor, and has a function of detecting various states of the mobile terminal device 50 (such as the inclination of the mobile terminal device 50 and the distance between the mobile terminal device 50 and the product).

[0048] (Configuration example of the weighing device 30) Next, with reference to FIGS. 5 and 6, a configuration example of the weighing device 30 will be described. Hereinafter, with reference to FIG. 5, the configuration example of the weighing device 30 shown in FIG. 6 will be described. FIG. 5 is an explanatory diagram showing an example of the appearance of the weighing device 30. FIG. 6 is an explanatory diagram showing an example of the hardware configuration of the weighing device 30. As shown in FIG. 5 or FIG. 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 stage 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 information used by the CPU 301 including programs.

[0050] The RAM 303 is a memory that can be read from and written to, and stores various information. For example, the RAM 303 stores information read from the ROM 302 or the memory 304, information acquired from the outside, information generated in the process, and the like.

[0051] The memory 304 stores various information. The memory 304 stores, for example, the unit price of the merchandise to be weighed acquired from the store controller 10. Note that 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, etc.). In this case, when using the various information, the weighing device 30 may inquire of the external device to acquire the various information.

[0052] Note that the memory 304 may store programs executed by the CPU 301 instead of the ROM 302. Further, the memory 304 may store information read from the ROM 302, information acquired from the outside, information generated in the process, and the like instead of the RAM 303.

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

[0054] In addition to communication via network communication, the communication unit 305 performs short-range wireless communication with the mobile terminal device 50. The number of mobile terminal devices 50 that the communication unit 305 can communicate with via short-range wireless communication is limited, for example, one. Specifically, one-to-one short-range wireless communication is performed with the mobile terminal device 50. The one-to-one short-range wireless communication is, for example, Bluetooth (registered trademark). Note that the one-to-one short-range 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. Note that the number of mobile terminal devices 50 that the communication unit 305 can communicate with via short-range 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 product name and measurement quantity of the product to be measured during weighing, as well as guidance regarding weighing. In addition, the various information displayed on the display unit 306 includes a two-dimensional code (hereinafter sometimes referred to as a "connection code") that causes the mobile terminal device 50 to read in order 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 regarding the product to be measured (weight, selling price, barcode indicating these, etc.) is printed. The scanner unit 308 reads various codes (barcodes, two-dimensional codes, etc.). The voice output unit 309 outputs voice. For example, the voice output unit 309 outputs voice guidance regarding weighing. The load cell 310 is a sensor that detects weight. The load cell 310 measures the weight of the merchandise to be weighed placed on the mounting table 320.

[0057] (An example of information managed by the cloud server Sv) FIG. 7 is an explanatory diagram showing an example of various information for each mobile terminal device 50 managed by the cloud server Sv. The cloud server Sv stores various information including (A) customer information, (B) store information, and (C) cart information. Note that 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 instead of or in addition to storing the various information in the storage unit within its own device.

[0058] (Customer information) FIG. 7(A) shows an example of customer information. Customer information is information for managing individual customers. The customer information may be membership information for each store or affiliated store. As shown in FIG. 7(A), the 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 "app identification information") uniquely assigned to each installed shopping app when the shopping app is installed on the mobile terminal device 50. The app identification information may be, for example, a sequentially assigned number. Alternatively, the app identification information may be terminal identification information uniquely assigned to the mobile terminal device 50 on which the shopping app is installed. This terminal identification information may be, for example, a phone number assigned to the customer who is the user of the mobile terminal device 50 or hardware identification information assigned to be unique 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, etc. The customer registration date is the date and time when customer information was newly registered in the cloud server Sv. The customer rank is a rank according to the customer's purchase history. The number of points is the number of points awarded to a customer for shopping using the shopping app. The number of points may include the number of points awarded to 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 app 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 the 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 on 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. 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). Store identification information 1 is, for example, information represented by a two-dimensional code posted in the store. Store identification information 2 is location information (GPS information) that indicates the location of the store.

[0063] (Cart information) FIG. 7(C) shows an example of cart information. The cart information is information regarding products registered by a customer at a store. As shown in FIG. 7(C), the 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 by date for each store).

[0064] The transaction start date and time is the date and time when the transaction started, for example, the generation date and time of the said cart information. Note that the transaction start date and time may be the registration date and time of one item of product, specifically, it may be the date and time when the registered product information (registered product 1: ○○ medium thick sauce) shown in FIG. 7(C) was memorized. Also, instead of or in addition to the transaction start date and time, the registration date and time for each product may be memorized separately.

[0065] The transaction end date and time is the date and time when the transaction ended, specifically, the date and time when settlement was completed. For example, the transaction end date and time is the date and time when settlement was completed, but it may also be the date and time when settlement started. The customer identification information is information for uniquely identifying the customer who conducts the said 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), estimated subtotal amount, subtotal amount, etc. The registered product information N (N is an integer) includes the number (data number) of the product registered in the Nth item. The registered product information N includes a product code, product name, price, the registration date and time of the said product, etc. Specifically, the registered product information 1 (○○ medium thick sauce) indicates the product registered in the first item. The registered product information 2 (○○ cheese) indicates the product registered in the second item. Note that in the example shown in FIG. 7(C), the illustration of the registered product information after the third item is omitted.

[0067] Next, we will explain the reserved product information (total). Reserved products are products that require confirmation by a store clerk before the checkout can begin. For example, reserved products are classified into categories such as unscanned products, non-file products, age verification products, security tag products that require the security tag to be removed, and pharmaceuticals.

[0068] Unscanned products are reserved products that could not be registered due to a failure to scan the product code (the scanner was not able to read it). For example, if the product packaging 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 a barcode due to a timeout will be described in detail. The mobile terminal device 50 is equipped with various sensors (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.), and is able to 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 is able to 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 product is present at a certain distance from the mobile terminal device 50. Then, if the mobile terminal device 50 determines that a barcode is being read but is unable to read it within a predetermined time, the mobile terminal device 50 times out and identifies the product as an unscanned product.

[0070] Furthermore, unscanned items include, for example, items that were placed in the cart by pretending to have their barcodes scanned. In other words, unscanned items include items that may have been subject to fraudulent manipulation, and therefore include items that require confirmation by a store clerk to determine whether fraud has occurred. Fraudulent manipulation is detected, for example, using scan results indicating whether the barcode has been scanned, image results from a camera capturing an image of the inside of the shopping cart, or detection results detecting the total weight of the items in the shopping cart.

[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 identified (the product query was rejected).

[0072] Age verification products are products that cannot be purchased by minors, such as alcohol and tobacco. Security tagged merchandise is merchandise with a security tag attached, such as merchandise over a certain amount of money. Medicines, 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 reserved product. In this example, a reserved product type of "1" indicates an unscanned product, and a reserved product type of "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, these types will be stored in the reserved product information (total).

[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] In addition, the hold product information of NON-file products includes the product code read by the mobile terminal device 50 in addition to the hold product type "2 (NON-file products)". For example, the hold product information 2 includes "2 (NON-file products)" indicating the hold product type and the product code.

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

[0077] Therefore, 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 perform error notification. As a result, if errors are frequently notified, it may prevent customers from shopping smoothly. Thus, in this embodiment, the frequent occurrence of error notification is suppressed to enable smooth shopping. Hereinafter, the error notification performed by the mobile terminal device 50 will be described in detail.

[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 identification 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, by the CPU 401 executing the notification program stored in the ROM 402, the functions of each unit are realized.

[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 the location information from, for example, the GPS unit 411. Note that the mobile terminal device 50 is not limited to acquiring the location information from the GPS unit 411. For example, the mobile terminal device 50 may acquire the location information using short-range wireless communication. Examples of short-range 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-range wireless communication or triangulation based on the radio wave intensity. In addition, the location information acquisition unit can also acquire the location information using iBeacon (registered trademark), which is a communication system using BLE (Bluetooth Low Energy).

[0080] The store identification information acquisition unit acquires store identification information displayed in a store. The store identification information is represented, for example, by a barcode or a two-dimensional code. The store identification information is displayed near the entrance or exit of the store. The store identification information is displayed, for example, on a monitor such as a digital signage. However, the store identification 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 a 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 located within a store using the store location information 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 located within 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 determines whether product registration is being performed legitimately. The determination of authenticity includes, for example, an operation determination and an existence determination. First, the operation determination will be described. The operation determination is a determination of whether an operation related to product registration is being performed legitimately. An operation being legitimate means that a product is registered as usual, and more specifically, 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, if the operation determination determines that an unusual product has been registered, the determination unit determines that the registration operation is inappropriate. Specifically, the registration of an unusual product is, for example, a registration that can be considered a price check by a competitor. More specifically, for example, if the number of registered products exceeds a certain number (for example, 50 or more), the determination unit determines that the operation is inappropriate. Note that if all registered products are subsequently canceled, it is more likely that a price check has been performed.

[0084] In addition, the determination of the operation may take into consideration the time required for registration, specifically, if a certain number or more of products are registered within a predetermined time, the determination unit may determine that the registration operation is improper. In addition, the classification of the registered products may be considered in the determination of the operation, specifically, if a certain number or more of products in a specific classification (e.g., instant curry) are registered, the determination unit may determine 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 if 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 if it is not present in the store (outside the service area).

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

[0087] The notification unit notifies an error based on the start condition that has been met. 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 made in a transaction in which a first condition is met, but is not made in a transaction in which a second condition is met. Note that even if an error is not notified, the determination unit may still make a validity determination.

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

[0089] 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 in the store (is out of range), the notification unit notifies an error.

[0090] Based on the position information acquisition determination, when the determination result of the position information acquisition determination where the position information cannot be acquired is obtained in a transaction due to the satisfaction of the first condition, the error notification is not performed. That is, when the communication environment is not good, such as when underground, and the position information cannot be acquired (when a determination result indicating impropriety is obtained in the position information acquisition determination), the notification unit does not notify an error. Also, in this case, the registration unit is enabled to continue performing product registration. That is, in this embodiment, product registration is not interrupted when the position information cannot be acquired.

[0091] (Regarding the acquisition request for store identification information) In this embodiment, when starting shopping using the shopping app, the identification of the store using the position information is given priority over the identification of the store using the store identification information. Specifically, when the store cannot be identified based on the position information before the start of product registration, that is, when the first condition is not satisfied, the request unit (the third request means) makes a request to acquire the store identification information. More specifically, when the store cannot be identified using the position information, the request unit makes a request to acquire the store identification information. The request unit makes a request for acquisition, for example, by notifying on the display 409 "Please read the store identification information".

[0092] The registration unit starts product registration in response to the satisfaction of the second condition by the acquisition of the 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 period of time, the request unit may request the acquisition of the store identification information again. Also, if the store identification information is not acquired even after a certain period of time, the mobile terminal device 50 may notify that shopping cannot be started.

[0093] (Regarding the case of connecting to the weighing device 30) The registration unit can register a product to be weighed by establishing a communication connection with the weighing device 30 that weighs the product. A product to be weighed cannot be registered unless it establishes a communication connection with the weighing device 30. Therefore, the fact that a product to be weighed has been successfully registered means that the mobile terminal device 50 (customer) is present in the store. Therefore, in this embodiment, the notification unit does not issue an error notification when a product to be weighed is registered, regardless of the start conditions. Note that, although an error notification is not issued when a product to be weighed is registered, the determination unit may still determine whether the product is valid.

[0094] (An example of a process related to product registration and payment in the shopping system 1) 8 is a sequence diagram showing the flow of processing related to product registration and payment in the shopping system 1. Note that FIG. 8 explains the flow from when a customer visits a store, registers a product to be purchased using his / her mobile terminal device 50, to when the customer 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 app in response to a customer's operation. During the startup process, the mobile terminal device 50 checks the version of the shopping app and displays a screen prompting the customer to upgrade if necessary. If this is the first startup, the mobile terminal device 50 displays a screen for consent to the terms of use and obtains the customer's consent, thereby completing the startup process.

[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. Upon receiving the current location information from the mobile terminal device 50, the cloud server Sv searches for stores located near the mobile terminal device 50 and transmits the search results 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: When the cloud server Sv receives information on the store where the customer shops, it generates cart information. Step S804: After completing the store entry process, the mobile terminal device 50 waits for the start of shopping. Specifically, the mobile terminal device 50 displays the top screen for shopping and waits for the customer to press the shopping start button.

[0098] Step S805: The mobile terminal device 50 causes the imaging area to be displayed on the display 409 and performs the shopping start process. Step S806: The mobile terminal device 50 performs a product registration process (see FIGS. 11 and 13). Specifically, the mobile terminal device 50 scans the barcode attached to the product according to the customer's operation. When the product is scanned, the mobile terminal device 50 transmits the product code obtained by the scan to the cloud server Sv together with the cart identification information. In the case where the product indicated by the read product code is a pending product such as an unscanned product, the cart identification information and information indicating the pending product are transmitted as the transmission / reception data D3.

[0099] Step S807: When the cloud server Sv receives the product code and the 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 the 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, the product name, and the 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 among the identified cart information.

[0100] Step S808: When the mobile terminal device 50 performs the product registration process, it determines whether the product registration is valid or not, and if the validity determination results in an invalid determination, it performs a notification process (see FIGS. 18 and 20) to notify an error. This makes it possible to notify an error if, for example, an invalid product registration such as a price check is made after leaving the store after the store entry process.

[0101] Step S809: Then, the mobile terminal device 50 performs a registered product display process to add and display the registered product on the registration screen. The registered product display process includes a process to accept quantity changes, deletions, and the like. Step S810: The mobile terminal device 50 determines whether or not an instruction to start settlement (registration completion) has been accepted by the customer, and if an instruction to start settlement has not been accepted, the process returns to step S806. If an 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 causing the POS terminal device 20 to 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, and the like, from 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 20 reads the settlement code displayed on the mobile terminal 50. Specifically, the customer who has completed product registration causes the customer-side scanner unit 206 of the POS terminal 20 to scan the settlement code displayed on the display 409 of the mobile terminal 50. As a result, the POS terminal 20 obtains cart identification information.

[0104] Step S813: After reading the settlement code, the POS terminal 20 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 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, it 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 20 executes the 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 app. If the payment type is cash, the POS terminal 20 accepts the insertion of cash, dispenses change, and issues a receipt in the settlement process. The POS terminal 20 then transmits information indicating the settlement details and cart information to the cloud server SV. The cloud server SV then stores the transaction completion date and time (settlement date and time) in the cart information.

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

[0109] Note that in the above-described process, in step S806, each time a product is registered (scanned) by the mobile terminal device 50, the cart identification information and the product code are transmitted to the cloud server Sv. However, these transmissions are not limited to being performed each time a product is registered. For example, the mobile terminal device 50 may transmit this information to the cloud server Sv in a batch at the timing when an instruction to start settlement is received. By doing so, the number of communication times between the mobile terminal device 50 and the cloud server Sv can be suppressed.

[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 of 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 issues a request to the GPS unit 411 to acquire the current location information (step S901). Then, the mobile terminal device 50 determines whether it has acquired the current location information (step S902). If the current location information has been acquired (step S902: YES), the mobile terminal device 50 issues a request to the cloud server Sv to search for nearby stores (step S903).

[0111] Upon receiving 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 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 makes a request for searching for surrounding stores again. Note that if there is no store near the mobile terminal device 50, it may notify 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 the number of stores nearby is one (step S905).

[0113] If the number of stores nearby is one (step S905: YES), the mobile terminal device 50 proceeds to step S907. If the number of stores nearby is not one (step S905: NO), that is, if there are multiple stores nearby, the mobile terminal device 50 accepts a selection of the store where the customer will shop (step S906). Then, the mobile terminal device 50 completes the identification of the store (step S907) and ends the series of processes. When the store is identified in step S907, a transaction due to the fulfillment of the first condition is started.

[0114] In step S902, if the current location information is not obtained (step S902: NO), specifically, for example, when the communication environment is not good and the GPS unit 411 cannot obtain the location information, the mobile terminal device 50 makes a request to read the store identification code presented at the store (step S908). Specifically, in step S908, the mobile terminal device 50 notifies on the display 409 "Please scan the store identification code presented at the store".

[0115] The mobile terminal device 50 waits until it reads the store identification code (step S909: NO). When it reads the store identification code (step S909: YES), it completes the identification of the store (step S910) and ends a series of processes. When the store is identified in step S910, a transaction due to the fulfillment of the second condition is started.

[0116] (Example of a screen displayed on the display 409 of the mobile terminal device 50 when entering the 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 the 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 selection buttons 1002.

[0117] The map area 1001 shows two candidates (Store A and Store B) located around the mobile terminal device 50 on the map screen. The selection buttons 1002 include an A store selection button 1002a for accepting the selection of Store A and a B store selection button 1002b for accepting the selection of Store B. When the customer presses any of the selection buttons 1002, the store to enter is determined. When there is only one candidate store, that store is determined as the store to enter.

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

[0119] Note that the two-dimensional code is not limited to being displayed on the monitor 1010, and may be printed and displayed on printed materials such as posters. The printed material may be posted near the entrance and exit of the store. Also, information corresponding to the store identification information may be presented to allow customers to make an operation input.

[0120] Note that the cloud server Sv can also identify the store, and this will be supplemented. FIG. 10(C) shows an example when the cloud server Sv identifies the store where the mobile terminal device 50 is located. In FIG. 10(C), the imaging terminal 1020 is installed, for example, near the entrance and exit of the store. A barcode 1021 indicating the identification information of the own device is displayed on the mobile terminal device 50. When the customer allows the imaging terminal 1020 to read the barcode 1021, the imaging terminal 1020 transmits information indicating that the mobile terminal device 50 identified by the barcode 1021 exists in the store, together with the store identification information, to the cloud server Sv. The cloud server Sv transmits the store identification information indicating the store where the mobile terminal device 50 is located to the mobile terminal device 50 identified by the barcode 1021. Even in this way, the mobile terminal device 50 can obtain the store identification information.

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

[0122] The mobile terminal device 50 waits until scanning of the barcode starts (step S1101: NO). When scanning of the barcode starts (step S1101: YES), the mobile terminal device 50 determines whether 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 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 a timeout has occurred (step S1103: YES), the mobile terminal device 50 notifies the customer that the item is on hold (step S1104). The notification urges the customer to put the item into a separate reserved item bag rather than into the shopping cart, and notifies the customer that the item will be registered by a store clerk at the time of checkout. The mobile terminal device 50 then registers the on-hold item information (unreadable item) (step S1105), and ends the series of processes.

[0124] If product identification information can be acquired from the barcode in step S1102 (step S1102: YES), the mobile terminal device 50 determines whether 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 determines whether the registration operation is invalid (step S1108). The registration operation is invalid when, for example, the number of registered products is equal to or greater than a certain number (for example, equal to or greater than 50). 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] (Screen example displayed on the display 409 of the mobile terminal device 50 after completion of the store entry process) FIG. 12 is an explanatory diagram showing an example of a screen displayed on the display 409 of the mobile terminal device 50 after completion of the store entry process. 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 for accepting the start of display of store information such as a floor guide. The notice button 1201b is a button for accepting the start of display of notice store information such as an event. The beneficial information button 1201c is a button for accepting the start of display of sale items such as advertising information. The registration start button 1202 is a button for accepting the start of display of an imaging screen on the display 409.

[0127] FIG. 12(b) shows a registration screen 1210 when performing product registration. The registration screen 1210 includes an imaging area 1211, a registered product display area 1212, a total amount display area 1213, and a settlement 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. In the registered product display area 1212, the registered products are displayed in the order of registration. Specifically, the most recently registered product is displayed above the registered product display area 1212.

[0128] The total amount display area 1213 is an area where the total number of points and the total amount of the registered products are displayed. The settlement start button 1214 is a button for completing the registration of products and accepting the start of settlement. In FIG. 12(B), when the settlement start button 1214 is pressed, the screen shown in FIG. 12(C) is shifted to.

[0129] FIG. 12(C) shows a payment start reception screen 1220. The payment start reception screen 1220 includes a guidance display 1221, a payment code 1222, and a registration return button 1223. The guidance display 1221 displays guidance to have the POS terminal device 20 read the payment code 1222. The payment 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 cart information transmission request 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 payment code 1222, payment is started at the POS terminal device 20.

[0130] (Example (part 2) of the product registration process shown in step S806 of FIG. 8) 13 is a flowchart showing an example of a product registration process for a product to be weighed performed by the mobile terminal device 50. As shown in FIG. 13, the mobile terminal device 50 determines whether or not the temporary registration code 1403 (see FIG. 14) of the product to be weighed 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). 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 mobile terminal device 50 then determines whether or not it has scanned the connection code displayed on the display unit 306 of the weighing device 30 (step S1303). The mobile terminal device 50 waits until it scans the connection code 1511 (see FIG. 15) (step S1303: NO). If it scans the connection code 1511 (step S1303: YES), the mobile terminal device 50 sends a connection request for one-to-one communication to the weighing device 30 (step S1304).

[0132] Even if the connection code 1511 is scanned while the product to be measured is not provisionally registered, the mobile terminal device 50 does not send a connection request to the measuring device 30. This is because if the connection time between one mobile terminal device 50 and the measuring device 30 becomes long, other customers will be unable to use the measuring device 30 for that much time. Therefore, it is to shorten the time that one mobile terminal device 50 occupies the measuring device 30.

[0133] When there is a connection request from the mobile terminal device 50, the measuring device 30 performs pairing determination including authentication of one-to-one communication and determination as to whether the provisionally registered product is the product to be measured by the measuring device 30. When pairing is successful in the pairing determination, the measuring 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 measuring device 30 has been established (step S1305). When a communication connection with the measuring device 30 has been established (step S1305: YES), the mobile terminal device 50 acquires the measured value of the product placed on the mounting table 320 from the measuring device 30 (step S1306). Note that when the measurement is completed, the measuring device 30 issues a label indicating the measurement result according to the customer's operation and transmits the measurement result to the mobile terminal device 50. That is, when the measurement in the measuring device 30 is completed, the mobile terminal device 50 acquires the measurement result from the measuring device 30 by the operation of the measuring device 30 by the customer.

[0135] When the mobile terminal device 50 acquires the measurement result, it displays the measurement result (step S1307). Then, the mobile terminal device 50 displays a registration update screen and performs final registration of the product to be measured (step S1308). After this, the mobile terminal device 50 determines whether the measurement (final registration) of all the products to be measured provisionally registered has been completed (step S1309). When the measurement of all the products to be measured provisionally registered has been completed (step S1309: YES), the mobile terminal device 50 ends the communication with the measuring device 30 (step S1310) and ends a series of processes.

[0136] On the other hand, if the weighing of all provisionally registered weighable items has not been completed (step S1309: NO), the mobile terminal device 50 returns to step S1306 and performs a process for performing final registration of other provisionally registered weighable items.

[0137] In step S1305, if the communication connection with the weighing device 30 cannot be 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 an acceptance of the end of registration from the customer or when a retry has been performed a certain number of times.

[0138] If the registration is not ended (step S1312: NO), that is, when it receives an acceptance of the continuation of registration from the customer or when a retry has not been performed a certain number of times, the mobile terminal device 50 returns to step S1304. On the other hand, if it ends the registration (step S1312: YES), the mobile terminal device 50 deletes the provisionally registered weighable items (step S1313) and ends a series of processes.

[0139] In the above-described process, the timing at which the weighing result is transmitted to the mobile terminal device 50 is the timing of issuing the label, but it is not limited to this. For example, it may be the timing when the weighing of all items is completed in the weighing device 30. In this case, the timing at which the weighing result is displayed on the mobile terminal device 50 may be the timing when the weighing is completed.

[0140] (Procedure for registering weighable items) Next, with reference to FIGS. 14 to 17, the procedure for registering weighable items will be described. FIG. 14 is an explanatory diagram showing an example of a registration procedure for weighable items. In FIG. 14, an example will be described in which identification information of a weighable item that a customer wishes to purchase is imaged by the camera 407 of the mobile terminal device 50.

[0141] In the corner (sales floor) in the store where fruits are placed, a metering target product 1401 (1401a to 1401c) and a display 1402 (1402a to 1402c) are arranged. The metering target product 1401 includes, for example, a metering target product 1401a for lemons, a metering target product 1401b for apples, and a metering target product 1401c for oranges. The displays 1402a to 1402 are arranged behind each metering target product 1401a to 1401c. In the following, mainly the display 1402a for lemons will be taken as an example for explanation, but the same applies to the other displays 1402b and 1402c.

[0142] On the display 1402a, the characters "Lemon", the unit price, and a provisional registration code 1403 are displayed. The unit price indicates the price per 1 kg. The provisional registration code 1403 includes information (product identification information) for identifying the metering target product 1401a and information on the unit price. The provisional registration code 1403 is read by the portable terminal device 50.

[0143] Note that the display 1402a can change the content of the provisional registration code 1403 according to time. For example, it is possible to perform price discounts in time services or prevent fraud such as conducting transactions using barcodes read in the past. Specifically, this kind of fraud is, for example, taking a picture of the barcode during the time service of the previous day with a camera and then having the barcode read the next day, and registering the metering target product 1401 at the unit price during the time service of the previous day. The content displayed on the display 1402a may also be printed on a printing medium such as paper.

[0144] When the portable terminal device 50 reads the provisional registration code 1403, it provisionally registers the read metering target product 1401. The display screen of the portable terminal device 50 shown in FIG. 14 shows a provisional registration screen 1410. The provisional registration screen 1410 includes an imaging result 1411, a provisional registration column 1412, a final registration column 1413, and a total display column 1414. The imaging result 1411 shows, for example, an image when the provisional registration code 1403 for lemons is read.

[0145] The provisional registration field 1412 displays products that have been provisionally registered by reading the provisional registration code 1403. In the illustration, 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 also 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 provisional registration field 1412. In the illustration, the provisional registration field 1412 is displayed in a shaded display mode. By using such a display mode, it is possible to make the customer aware that provisional 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 that is displayed during standby mode is displayed on the display unit 306 of the weighing device 30. The standby screen 1500 includes a first information field 1510 and a second information field 1520.

[0148] The first information field 1510 shows information for registering a commodity to be weighed using the mobile terminal device 50. Specifically, the first information field 1510 displays a connection code 1511, and displays information to have the mobile terminal device 50 read the connection code 1511. The second guidance field 1520 displays guidance for registering the products to be weighed without using the mobile terminal device 50. Specifically, the second guidance field 1520 displays guidance urging the user to place the products to be weighed on a scale and weigh them. The following describes the case where the mobile terminal device 50 is used.

[0149] The customer has mobile terminal device 50 read temporary registration code 1403 for lemon and apple shown in Figure 14, and then has mobile terminal device 50 read connection code 1511 shown in Figure 15. Upon reading connection code 1511, mobile terminal device 50 requests weighing device 30 for a communication connection based on the instructions indicated by connection code 1511.

[0150] Figure 16 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 50 after reading the connection code. Figure 16(A) shows the standby screen when a connection request is made. As shown in Figure 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 complete, the screen changes to that shown in Figure 16(B).

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

[0152] 17 is an explanatory diagram showing an example of a screen displayed during weighing 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 products have 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 field 1705, a unit price field 1706, a total amount field 1707, and mobile terminal information 1730.

[0153] The guidance display S1 shows guidance prompting to place a product on the mounting table 320. The product name display 1701 shows the product name of the product to be weighed. The return button 1702 is a button that accepts returning to the previous screen. The stop button 1703 is a button that accepts stopping the weighing. The search button 1704 is a button that accepts searching for surrounding mobile terminal devices 50 in order to reconnect to the mobile terminal device 50 when, for example, the communication connection with the mobile terminal device 50 is disconnected.

[0154] The weighing result column 1705 shows the weight of the product to be weighed placed on the mounting table 320. Note that the weighing result column 1705 is not limited to displaying the weight. For example, for a product for which the approximate weight per piece is known, the number converted based on the weight may be displayed. The unit price column 1706 shows the unit price (for example, the price per kilogram). The total amount column 1707 shows the total amount calculated using the weighing result and the unit price. The mobile terminal information 1730 shows the connected mobile terminal device 50 (owner). Specifically, the mobile terminal information 1730 shows character information such as "Connected with ○○".

[0155] Figure 17(B) shows the weighing completion screen 1710 of the weighing device 30 when the weighing is completed. The weighing completion screen 1710 is different from the operation guidance screen 1700 in Figure 17(A) in that the display content of the weighing result column 1705, the display content of the total amount column 1707, the guidance display S2, and the print button 1708 are displayed. The weighing result column 1705 shows the weight of the product placed on the mounting table 320 (for example, 1.2006 kg). The total amount column 1707 shows the amount calculated using the weight of the product and the unit price (for example, ¥432).

[0156] The guidance display S2 shows guidance prompting to press the print button 1708. The print button 1708 is a button that accepts issuing a label. The print button 1708 is displayed for the first time when a product is placed on the mounting table 320 and the weighing value has stabilized. When the print button 1708 is pressed on the weighing completion screen 1710, the screen shown in Figure 17(C) is displayed.

[0157] Figure 17(C) shows a guide screen 1720 after the label has been issued. The guide screen 1720 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 Figure 17(D).

[0158] Figure 17(D) shows a screen displayed on mobile terminal device 50 when the official registration of the apples is complete. As shown in Figure 17(D), mobile terminal device 50 receives the weighing results of the apples from weighing device 30, and as a result, official registration field 1413a corresponding to the apples is displayed in place of temporary registration field 1412b (see Figure 14) corresponding to the apples.

[0159] Additionally, the words "weighing required" that were displayed in the provisional registration have been changed to "weighing" in the main registration field 1413. This indicates that the weighing of the apples has been completed. Note that instead of the word "weighing" in the main 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., three seconds) has elapsed since the weighing device 30 displayed the screen shown in Figure 17(C), the weighing device 30 transitions to a screen prompting the user to weigh the lemons. The transition of the screens on the weighing device 30 and the mobile terminal device 50 when weighing lemons is the same as when weighing apples, and therefore a description thereof will be omitted. After the official registration of all provisionally registered products to be weighed (apples and lemons) has been completed, the weighing device 30 displays the standby screen 1500 shown in Figure 15 after a predetermined time (e.g., three seconds) has elapsed.

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

[0162] On the other hand, when the registered product is not a product to be weighed (step S1801: NO), that is, when the registered product is a barcode product, the mobile terminal device 50 determines whether it is a transaction due to the fulfillment of the first condition (condition for identifying the store using location information) (step S1802). When the mobile terminal device 50 is not a transaction due to the fulfillment of the first condition (step S1802: NO), that is, when it is a transaction due to the fulfillment of the second condition (condition for identifying the store using store identification information), the process ends as it is. Thereby, in a transaction due to the fulfillment of the second condition, it is possible to suppress the frequency of error notifications because notifications based on presence determination are not performed.

[0163] On the other hand, when it is a transaction due to the fulfillment of the first condition (step S1802: YES), the mobile terminal device 50 (CPU 401) requests the GPS unit 411 to acquire the location information of the current location (step S1803). Then, the mobile terminal device 50 performs a location information acquisition determination as to whether it has acquired the location information of the current location (step S1804). In the location information acquisition determination, when the location information of the current location is not acquired (step S1804: NO), that is, for example, when in an underground area where the communication environment is not good, the mobile terminal device 50 ends the process as it is without notifying an error. Thereby, it is possible to suppress the frequent notification of errors when the communication environment is not good.

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

[0165] On the other hand, in the presence determination, if the current location of the mobile terminal device 50 is outside the range (step S1805: YES), that is, if there is a possibility that a customer (member) who came to the store for price check or the like has moved outside the store and is performing a registration operation, the mobile terminal device 50 (the customer) notifies an error that it exists outside the store (step S1806).

[0166] Next, the mobile terminal device 50 determines whether to perform a retry (step S1807). Note that the retry is performed automatically or by accepting an operation to perform a retry from the customer, as long as it is within a preset upper limit number of times. If the upper limit number of times is exceeded, the process may proceed to step S1808.

[0167] When performing a retry (step S1807: YES), the mobile terminal device 50 returns to step S1803. When not performing a retry (step S1807: NO), the mobile terminal device 50 restricts product registration (step S1808) and ends a series of processes. Note that restricting product registration means, for example, canceling the registered product and logging out. Also, in this case, the error notification can be canceled by the operation of the store clerk, and further, re-login or re-product registration may be enabled. Thereby, the deterrent effect of preventing improper product registration can be enhanced.

[0168] (Example of an error screen based on the location information displayed on the mobile terminal device 50) FIG. 19 is an explanatory diagram showing an example of an error screen based on the position 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 the product registration is to be aborted (i.e., the registered product is to be deleted). When the 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 the retry button 1902 is pressed on the error screen 1900, the position information is acquired again and the presence determination is performed again. If 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 the screen where product registration is possible.

[0169] (An example of the notification process shown in step S808 of FIG. 8 (Part 2)) FIG. 20 is a flowchart showing an example of a notification process based on the product registration operation information performed by the mobile terminal device 50. As shown in FIG. 20, the mobile terminal device 50 (CPU 401) issues a request to acquire the 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 improper registration operation (step S2002). If it is not product registration operation information indicating an improper registration operation (step S2002: NO), the mobile terminal device 50 ends the series of processes.

[0170] On the other hand, if it is product registration operation information indicating an improper 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 indicating 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 product and logging out the user.

[0171] (Example of error screen based on product registration operation information displayed on 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 mobile terminal device 50. As shown in FIG. 21, an error screen 2100 is displayed on display 409 of mobile terminal device 50. Error screen 2100 indicates that the registration operation is improper and that product registration is to be aborted (i.e., registered products are to be deleted). When confirmation button 2101 is pressed on error screen 2100, the registered products are deleted and the user is logged out.

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

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

[0174] If the cart information does not include pending product information (step S2203: NO), POS terminal device 20 proceeds to step S2210. If the cart information includes pending product information (step S2203: YES), POS terminal device 20 performs a settlement prohibition process (step S2204). By the settlement prohibition process, for example, the operation of customer display unit 205 is disabled.

[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 lights up 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 determines whether the clerk has logged in (step S2206). To log in, the clerk may, for example, have the clerk scanner unit 212 read the clerk code attached to the clerk's name tag, or may manually input 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 performs a process of registering or deleting 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). Then, the POS terminal 20 displays a checkout start screen (step S2210) and ends the series of processes.

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

[0179] Note that the list display screen 2320 shown in FIG. 23(B) includes a registered product display area 2321, a clerk call button 2322, and a settlement start button 2323. The registered product display area 2321 shows, for each registered product, the product name, the number of purchased items, the purchase amount, etc., and also shows the total number of items and the total amount of various registered products. The registered product display area 2321 is displayed, for example, in the registration order.

[0180] The clerk call button 2322 is a button that accepts a call from the customer to the clerk. When the customer checks the registered product display area 2321 and there is a difference between the registered products and the products the customer wishes to purchase, it becomes necessary to correct the registered products. This correction requires the operation of the clerk. For example, when the customer checks the registered product display area 2321 and notices that, although intending to register 3 items of "○○ meat sauce", only 1 item has been registered. In this case, the customer presses the clerk call button 2322 to call the clerk. When the clerk call button 2322 is pressed, the screen transitions to the screen 2330 with the clerk being called shown in FIG. 23(C).

[0181] The staff call screen 2330 shown in Fig. 23(C) indicates that the staff is being called. When the confirmation button 2331 is pressed on the staff call screen 2330, it transitions to a list display screen of registered products (not shown). Note that on this list display screen, since the staff is being called, it is not possible to accept the start of settlement. When the staff is called and the staff logs in, it transitions to the pending product confirmation screen 2340 shown in Fig. 23(D).

[0182] On the pending product confirmation screen 2340, the staff registers or deletes products while confirming with the customer one by one. When there are no more pending products, it transitions to the list display screen 2320 shown in Fig. 23(B).

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

[0184] As described above, the mobile terminal device 50 according to this embodiment is configured to notify an error based on the start condition of the transaction. As a result, the frequency of error notifications can be made different between the transaction based on the fulfillment of the first condition and the transaction based on the fulfillment of the second condition, so the frequency of errors can be suppressed according to the start condition. Therefore, according to this embodiment, it is possible to suppress the shopping from being hindered by the error notification, so the shopping can be carried out smoothly.

[0185] Also, in this embodiment, the mobile terminal device 50 is configured to notify an error based on the existence determination in a transaction when the first condition is satisfied, and not to notify an error based on the existence determination in a transaction when the second condition is satisfied. Therefore, in a transaction when the second condition is satisfied, the frequency of error notifications can be suppressed.

[0186] Also, in this embodiment, the mobile terminal device 50 is configured not to notify an error in a transaction based on the first condition regardless of whether the location information is obtained in the location information acquisition determination. Thereby, it is possible to suppress the occurrence of frequent error notifications when the communication environment is not good.

[0187] Also, in this embodiment, the validity determination includes an operation determination as to whether the operation related to product registration is properly performed. Thereby, an error can be notified when an improper registration operation such as price checking is performed. Therefore, improper product registrations such as price checking can be suppressed. For this reason, it is possible to suppress the leakage of various information in the store such as price information.

[0188] Also, in this embodiment, when a product to be measured is registered, the mobile terminal device 50 is configured not to notify an error regardless of the start condition. Thereby, when it is clear that the customer is present in the store, it is possible not to notify an error.

[0189] Also, in this embodiment, when the mobile terminal device 50 cannot obtain location information at the start of a transaction, it makes a request to obtain store identification information, and starts product registration in response to the acquisition of the store identification information in response to the acquisition request. Thereby, even when location information cannot be obtained, it is possible to prompt the acquisition of store identification information and start product registration.

[0190] (Modification Example of the Embodiment) The following describes Modification Examples 1 to 11 of the embodiment. In each of the following modification examples, the description of the content described in the above-described embodiment will be omitted as appropriate. Also, it is possible to adopt a configuration in which each configuration shown in the above-described embodiment and Modification Examples 1 to 11 is combined. Specifically, it may be a configuration that includes all of the above-described embodiment and Modification Examples 1 to 11, or it may be a configuration that is a combination of one of the above-described embodiment and Modification Examples 1 to 11.

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

[0192] In Modification Example 1, the request unit (first request means) makes a request to acquire store identification information in response to obtaining a determination result that position information is not acquired in the position information acquisition determination. The request unit makes a request to acquire store identification information at a predetermined timing. The predetermined timing is, for example, the timing when the period during which the position information of the current location is not acquired becomes a predetermined period (for example, 15 minutes). In other words, the request unit makes a request to acquire store identification information, for example, when staying underground or the like for a predetermined period or more. Also, the predetermined timing is not limited to this, and it may be the timing when the number of times of product registration has reached a predetermined number or more without the position information of the current location being acquired. In response to the request to acquire store identification information by the request unit, the customer causes the portable terminal device 50 to read the store identification code.

[0193] Also, in the store, a two-dimensional code indicating store identification information may be appropriately arranged in an area where the communication environment is not good. Thereby, even when the customer is underground or the like, the portable terminal device 50 can be made to read the two-dimensional code. That is, the store identification information acquisition unit can acquire the store identification information.

[0194] Here, the legitimacy determination includes a store identification information acquisition determination. The store identification information acquisition determination is a determination as to whether store identification information has been acquired during a transaction. If the store identification information has been acquired, it is clear that there is a customer at the store identified by the store identification information. The determination unit determines that it is legitimate when the store identification information is acquired in the store identification information acquisition determination, while determining that it is improper when the store identification information is not acquired even after a certain period of time has elapsed. The notification unit does not notify an error when a legitimate determination result is obtained in the store identification information acquisition determination, and notifies an error when an improper determination result is obtained.

[0195] (Modification Example 1 of the Notification Process Shown in Step S808 of FIG. 8) FIG. 24 is a flowchart showing Modification Example 1 of the notification process based on position information performed by the mobile terminal device 50. As shown in FIG. 24, the mobile terminal device 50 determines whether it is a predetermined timing at which a period during which the current location position information is not acquired becomes a predetermined period, for example, when in a place such as underground (step S2401). The mobile terminal device 50 waits until the predetermined timing (step S2401: NO). When the predetermined timing arrives (step S2401: YES), the mobile terminal device 50 determines whether a commodity to be measured is registered (step S2402).

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

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

[0198] When the current location information is obtained (step S2404: YES), the mobile terminal device 50 compares the location information of the current location with the location information of the store to determine whether the current location of the mobile terminal device 50 is outside the coverage area (outside the store) (step S2405). In the presence determination, if the current location of the mobile terminal device 50 is not outside the coverage area (step S2405: NO), that is, if the current location of the mobile terminal device 50 is inside the coverage area (inside the store), the process ends as it is.

[0199] On the other hand, in the presence determination, if the current location of the mobile terminal device 50 is outside the coverage area (step S2405: YES), that is, if it can be expected that it is a registration operation by a customer (member) who has come to the store for price checking or the like, the mobile terminal device 50 (the customer) notifies an error indicating that it is outside the store (step S2406). Then, the mobile terminal device 50 restricts product registration (step S2407) and ends the series of processes.

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

[0201] When a retry is to be performed (step S2408: YES), the mobile terminal device 50 returns to step S2403. When a retry is not to be performed (step S2408: NO), the mobile terminal device 50 makes a request to acquire the store identification information of the store (step S2409). Then, the mobile terminal device 50 determines whether it has acquired the store identification information of the store (store identification information acquisition determination) (step S2410). When the store identification information of the store has been acquired (step S2410: YES), the mobile terminal device 50 ends a series of processes. On the other hand, when 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 even when the acquired store identification information is not the store identification information of the store, the mobile terminal device 50 notifies an error.

[0202] As described above, in Modification 1, when the position information cannot be acquired, the mobile terminal device 50 makes a request to acquire the store identification information and performs a store identification information acquisition determination. Thereby, even when the customer is located in an area with a poor communication environment, the customer can clarify that they are in the store by having the mobile terminal device 50 read the store identification information (two-dimensional code). Therefore, it is possible to suppress improper product registration by customers who perform price checks and the like.

[0203] (Modification 2) Next, Modification 2 of the embodiment will be described. In Modification 1 described above, a configuration in which notification based on store identification information acquisition determination is performed regardless of the start condition of the transaction was described. Instead of or in addition to such a configuration, in Modification 2, a configuration in which notification based on store identification information acquisition determination is not performed in a transaction due to the satisfaction of the second condition will be described.

[0204] In Modification 2, the request unit (first request means) makes a request to acquire the store identification information when the position information cannot be acquired, such as when the communication environment is not good, in a transaction due to the satisfaction of the first condition. On the other hand, the request unit does not make a request to acquire the store identification information in a transaction due to the satisfaction of the second condition.

[0205] (Modification Example 2 of the Notification Process Shown in Step S808 of FIG. 8) FIG. 25 is a flowchart showing a modification example 2 of the notification process based on the position information performed by the mobile terminal device 50. Note that, compared with the flowchart shown in FIG. 24, step S2501 is different in the flowchart shown in FIG. 25. Therefore, hereinafter, only step S2501 will be described.

[0206] As shown in FIG. 25, when the mobile terminal device 50 determines in step S2402 that the merchandise to be measured is not registered (step S2402: NO), it determines whether it is a transaction due to the fulfillment of the first condition (a condition for identifying a store using position information) (step S2501). If the mobile terminal device 50 determines that it is not a transaction due to the fulfillment of the first condition (step S2501: NO), that is, if it is a transaction due to the fulfillment of the second condition (a condition for identifying a store using store identification information), the process ends as it is. Thereby, in a transaction due to the fulfillment of the second condition, it is possible not to perform notification based on the existence determination, so that the frequency of error notification can be suppressed.

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

[0208] As described above, in modification example 2, the mobile terminal device 50 does not perform notification based on each of the position information acquisition determination, the existence determination, and the store identification information acquisition determination in a transaction due to the fulfillment of the second condition. Thereby, in a transaction due to the fulfillment of the second condition, the frequency of error notification can be suppressed.

[0209] (Modification Example 3) Next, Modification Example 3 of the embodiment will be described. In Modification Example 2 described above, in the transaction due to the satisfaction of the second condition, a configuration in which notification based on the store identification information acquisition determination is not performed was described. Instead of or in addition to such a configuration, in Modification Example 3, a configuration in which notification based on the store identification information acquisition determination is not performed in the transaction due to the satisfaction of the first condition will be described.

[0210] In Modification Example 3, the request unit (second request means) makes a request for acquiring store identification information in response to the elapse of a predetermined time from the start of product registration in a transaction due to the satisfaction of the second condition by acquiring the store identification information. The predetermined time is, for example, 15 minutes. The request unit makes a request for acquiring store identification information every time the predetermined time elapses 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 for acquiring store identification information in a transaction due to the satisfaction of the first condition in which the location information has been acquired.

[0211] Also, in the store, two-dimensional codes indicating the store identification information may be arranged everywhere. Thereby, no matter where the customer is in the store, the mobile terminal device 50 can be made to read the two-dimensional code. That is, the store identification information acquisition unit can acquire the store identification information. The specific information determination is performed using the store identification information acquired in response to the acquisition request by the request unit.

[0212] Here, in the transaction due to the satisfaction of the first condition, the mobile terminal device 50 can periodically acquire the location information and perform the presence determination. Therefore, the determination unit does not perform the store identification information acquisition determination in the transaction due to the satisfaction of the first condition. For this reason, the notification unit does not notify an error based on the store identification information acquisition determination in the transaction due to the satisfaction of the first condition.

[0213] On the other hand, in the transaction due to the satisfaction of the second condition, a regular location check cannot be performed. Therefore, the determination unit performs the store identification information acquisition determination in the transaction due to the satisfaction of the second condition. And the notification unit notifies an error based on the store identification information acquisition determination in the transaction due to the satisfaction of the second condition.

[0214] (Modification Example 3 of the Notification Process Shown in Step S808 of FIG. 8) FIG. 26 is a flowchart showing a modification example 3 of the notification process based on the store identification information performed by the mobile terminal device 50. As shown in FIG. 26, the mobile terminal device 50 determines whether or not a predetermined time (for example, 20 minutes) has elapsed (step S2601). The mobile terminal device 50 waits until the predetermined time elapses (step S2601: NO). When the predetermined time elapses (step S2601: YES), the mobile terminal device 50 determines whether or not a product to be measured is registered (step S2602).

[0215] If the product to be measured is registered (step S2602: YES), since it is clear that the customer is present in the store, the mobile terminal device 50 ends the process as it is without performing the position information acquisition determination.

[0216] On the other hand, if the product to be measured is not registered (step S2602: NO), the mobile terminal device 50 determines whether or not it is a transaction due to the fulfillment of the first condition (the condition for identifying the store using the position information) (step S2603). If it is a transaction due to the fulfillment of the first condition (step S2603: YES), the mobile terminal device 50 ends the process as it is without performing the position information acquisition determination.

[0217] On the other hand, if it is not a transaction due to the fulfillment of the first condition (step S2603: NO), that is, if it is a transaction due to the fulfillment of the second condition (the condition for identifying the store using the store identification information), the mobile terminal device 50 requests acquisition of the store identification information of the store (step S2604). Then, the mobile terminal device 50 performs a store identification information acquisition determination as to whether or not it has acquired the store identification information of the store (step S2605). When it has acquired the store identification information of the store (step S2605: YES), the mobile terminal device 50 ends the series of processes.

[0218] On the other hand, if the store specific information of the store is not acquired even after a lapse of a certain period of time (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 a series of processes.

[0219] As described above, in Modification 3, in the transaction due to the satisfaction of the second condition, the mobile terminal device 50 makes a request for acquisition of store specific information in response to the elapse 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. Thereby, in the transaction due to the satisfaction of the second condition, it is possible to clarify that the user is in the store by having the mobile terminal device 50 read the store specific information (two-dimensional code). Therefore, it is possible to suppress improper product registration by customers who perform price checks and the like.

[0220] Also, in the transaction due to the satisfaction of the first condition, since the mobile terminal device 50 can periodically acquire position information and perform an existence determination, it is possible not to notify an error based on the store specific information acquisition determination. Thereby, in the transaction due to the satisfaction of the first condition, the frequency of error notification can be suppressed.

[0221] (Modification 4) Next, Modification 4 of the embodiment will be described. In Modification 3 described above, a configuration in which the store specific information is not updated has been described. Instead of or in addition to such a configuration, Modification 4 will describe a configuration that enables the use of updated store specific information and non-updated store specific information.

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

[0223] Here, the fact that the one-time password is read means that the customer's credibility of being present in the store is high. Therefore, in a transaction due to the establishment of the second condition in which the one-time password is acquired, the notification unit does not notify an error based on the store identification information acquisition determination.

[0224] On the other hand, regarding the non-updated store identification information, by capturing and storing it with a camera, it is possible to let it read the past outside the store. Therefore, when the non-updated store identification information is read, it means that the customer's credibility of being present in the store is lower than when the updated store identification information is acquired. Therefore, the notification unit is configured to notify an error based on the store identification information acquisition determination in a transaction due to the establishment of the second condition in which the non-updated store identification information is acquired.

[0225] Also, in Modification 4, the request unit (second request means) makes a request to acquire non-store identification information in response to the elapse of a predetermined time from the start of product registration in a transaction due to the establishment of the second condition by acquiring the non-updated store identification information. The store identification information targeted for the acquisition request is not limited to the non-updated store identification information, and may also be a one-time password. That is, in a store where both the one-time password and the non-updated store identification information are presented, the request unit may request to acquire the one-time password.

[0226] Also, in the store, a store identification code (two-dimensional code) indicating non-store specific information may be placed everywhere. As a result, no matter where the customer is in the store, the store identification code can be read by the portable terminal device 50. That is, the store specific information acquisition unit can acquire the non-store specific information. The specific information determination is performed using the non-store specific information acquired in response to the acquisition request by the request unit.

[0227] In addition, in Modification Example 4, in the transaction due to the satisfaction of the first condition, notification based on the store specific information acquisition determination may or may not be performed (configuration of Modification Example 2 or configuration of Modification Example 3).

[0228] (Modification Example 4 of the notification process shown in step S808 of FIG. 8) FIG. 27 is a flowchart showing a fourth modification of the notification process based on the position information performed by the portable terminal device 50. Note that the flowchart shown in FIG. 27 is different from the flowchart shown in FIG. 26 in step S2701. For this reason, only step S2701 will be described below. As shown in FIG. 27, when the portable terminal device 50 determines in step S2603 that the transaction is not due to the satisfaction of the first condition (step S2603: NO), that is, when the transaction is due to the satisfaction of the second condition (condition for specifying the store using the store specific information), the portable terminal device 50 determines whether the transaction is due to the satisfaction of the second condition by obtaining a one-time password (step S2701).

[0229] When the transaction is due to the satisfaction of the second condition by obtaining a one-time password (step S2701: YES), the portable terminal device 50 ends the process as it is. As a result, in the transaction due to the satisfaction of the second condition by obtaining a one-time password, notification based on the store specific information acquisition determination can be prevented from being performed, so that the frequency of error notification can be suppressed.

[0230] On the other hand, when the transaction is not the one where the second condition is satisfied by obtaining the one-time password (step S2701: NO), that is, when the transaction is the one where the second condition is satisfied by obtaining the non-updated store identification information, the mobile terminal device 50 proceeds to step S2604 and requests to obtain the store identification information of the store.

[0231] As described above, in Modification 4, the mobile terminal device 50 does not notify an error based on the store identification information acquisition determination in the transaction where the second condition is satisfied by obtaining the one-time password. Therefore, when it is highly likely that the customer is present in the store, the frequency of errors can be suppressed because no error notification based on the store identification information acquisition determination is given.

[0232] Also, in Modification 4, an error notification based on the store identification information acquisition determination is given in the transaction where the second condition is satisfied by obtaining the non-updated store identification information. As a result, when it is considered that the possibility of the customer being present in the store is low, an error can be notified, so improper product registration such as price checking can be suppressed.

[0233] (Modification 5) Next, Modification 5 of the embodiment will be described. In the above-described embodiment, a configuration in which a notification based on the operation determination is given regardless of the start condition of the transaction has been described. Instead of or in addition to such a configuration, in Modification 5, a configuration in which a notification based on the operation determination is not given in the transaction where the second condition is satisfied will be described.

[0234] In Modification 5, in the transaction where the first condition is satisfied, the notification unit gives a notification based on the operation determination. On the other hand, in the transaction where the second condition is satisfied, the notification unit does not give a notification based on the operation determination.

[0235] (Modification 5 of the notification process shown in step S808 of FIG. 8) FIG. 28 is a flowchart showing a fifth modification of the notification process based on the product registration operation information performed by the mobile terminal device 50. Note that the flowchart shown in FIG. 28 differs from the flowchart shown in FIG. 20 in step S2801. Therefore, only step S2801 will be described below.

[0236] As shown in FIG. 28, the mobile terminal device 50 determines whether it is a transaction due to the fulfillment of the first condition (a condition for identifying a store using location information) (step S2801). If it is not a transaction due to the fulfillment of the first condition (step S2801: NO), that is, if it is a transaction due to the fulfillment of the second condition (a condition for identifying a store using store identification information), the mobile terminal device 50 ends a series of processes without performing an operation determination. On the other hand, in step S2801, if it is a transaction due to the fulfillment of the first condition (step S2801: YES), the mobile terminal device 50 (CPU 401) proceeds to step S2001 and requests acquisition of the product registration operation information stored in the memory 404.

[0237] As described above, in the fifth modification, the mobile terminal device 50 is configured not to notify an error based on an operation determination in a transaction due to the fulfillment of the second condition. Thereby, the frequency of error notification can be suppressed in a transaction due to the fulfillment of the second condition.

[0238] (Sixth Modification) Next, a sixth modification of the embodiment will be described. In the fifth modification described above, a configuration in which no notification based on an operation determination is made in a transaction due to the fulfillment of the second condition was described. Instead of or in addition to such a configuration, in the sixth modification, a configuration in which no notification based on an operation determination is made in a transaction due to the fulfillment of the first condition will be described.

[0239] In the sixth modification, in a transaction due to the fulfillment of the first condition, the notification unit does not perform a notification based on an operation determination. On the other hand, in a transaction due to the fulfillment of the second condition, the notification unit performs a notification based on an operation determination.

[0240] (Modification Example 6 of the Notification Process Shown in Step S808 of FIG. 8) FIG. 29 is a flowchart showing Modification Example 6 of the notification process based on the product registration operation information performed by the mobile terminal device 50. Note that the flowchart shown in FIG. 29 differs from the flowchart shown in FIG. 20 in that step S2901 is different. Therefore, hereinafter, only step S2901 will be described.

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

[0242] As described above, in Modification Example 6, the mobile terminal device 50 is configured not to notify an error based on an operation determination in a transaction due to the establishment of the first condition. Thereby, the frequency of error notification can be suppressed in a transaction due to the establishment of the first condition.

[0243] (Modification Example 7) Next, Modification Example 7 of the embodiment will be described. In Modification Example 6 described above, a configuration in which notification based on an operation determination is performed in a transaction due to the establishment of the second condition has been described. Instead of or in addition to such a configuration, in Modification Example 7, a configuration in which notification based on an operation determination is not performed in a transaction due to the establishment of the second condition or in a transaction by acquiring a one-time password will be described.

[0244] When a one-time password is obtained, the possibility of improper product registration such as price checking outside the store is low. Therefore, in Modification Example 7, the notification unit does not notify an error based on the operation determination in a transaction due to the establishment of the second condition that the one-time password is obtained.

[0245] On the other hand, in the case of non-updated store identification information, by capturing and storing images with a camera, it is possible to read past information outside the store. Therefore, when non-updated store identification information is obtained, the possibility of improper product registration such as price checking outside the store is higher than when a one-time password is obtained. For this reason, the notification unit notifies an error based on the operation determination in a transaction due to the establishment of the second condition that non-updated store identification information is obtained.

[0246] In Modification Example 7, in a transaction due to the establishment of the first condition, notification based on the operation determination may be performed (configuration of Modification Example 5), or may not be performed (configuration of Modification Example 6).

[0247] (Modification Example 7 of the notification process shown in step S808 of FIG. 8) FIG. 30 is a flowchart showing Modification Example 7 of the notification process based on the product registration operation information performed by the mobile terminal device 50. Note that 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, when the mobile terminal device 50 determines in step S2901 that the transaction is due to the establishment of the second condition (step S2901: YES), it determines whether the transaction is a transaction due to the acquisition of a one-time password (step S3001).

[0249] When the transaction is a transaction by obtaining a one-time password (step S3001: YES), the mobile terminal device 50 ends the process as it is. Thereby, in the transaction by the establishment of the second condition by obtaining the one-time password, since it is possible not to perform the notification based on the operation determination, the frequency of error notification can be suppressed.

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

[0251] As described above, in Modification 7, the mobile terminal device 50 does not perform error notification based on the operation determination in the transaction by the establishment of the second condition in which the one-time password is obtained. Therefore, when it can be expected that there is a low possibility of improper product registration such as price checking outside the store, error notification is not performed, so the frequency of errors can be suppressed.

[0252] Also, in Modification 7, error notification based on the operation determination is performed in the transaction by the establishment of the second condition in which the non-updated store identification information is obtained. Thereby, when it can be expected that there is a high possibility of improper product registration such as price checking outside the store, errors can be notified, so improper product registration such as price checking can be suppressed.

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

[0254] The following will be described with reference to FIG. 18. In Modification 8, in step S1804 of FIG. 18, when position information cannot be obtained, the mobile terminal device 50 determines whether the GPS function is OFF. If the GPS function is ON, the process ends without performing the presence determination. On the other hand, if the GPS function is OFF, a notification to turn on the GPS function is made. Also, the mobile terminal device 50 may not end the process shown in FIG. 18 until the GPS function is turned on. Further, if the GPS function does not turn on even after a certain period of time has elapsed, the mobile terminal device 50 (the customer) may notify an error indicating that the customer is outside the store, or may restrict product registration.

[0255] According to Modification 8, it is possible to prevent a customer from deliberately turning off the GPS function and performing improper product registration such as price checking.

[0256] (Modification 9) Next, Modification 9 of the embodiment will be described. In the above-described embodiment, when a product to be measured is registered, an error based on position information is not notified (see FIG. 18). Instead of or in addition to such a configuration, in Modification 9, an error based on position information may be notifiable regardless of whether a product to be measured is registered.

[0257] Specifically, in the notification process based on the position information according to Modification 9 (see FIG. 18), a position information acquisition determination and a presence determination are made regardless of whether a product to be measured is registered. Specifically, the mobile terminal device 50 may not perform the process of step S1801 in FIG. 18. As a result, even when a product to be measured is registered, a position information acquisition determination, a presence determination, and a store identification information acquisition determination can be performed. Therefore, an error can be notified according to the determination result of each determination.

[0258] (Modification 10) Next, Modification Example 10 of the embodiment will be described. In the above-described embodiment, regardless of whether or not the product to be measured is registered, an error based on the registration operation information is notified (see FIG. 20). Instead of or in addition to such a configuration, in Modification Example 10, when the product to be measured is registered, an error based on the registration operation information may not be notified.

[0259] Specifically, in Modification Example 10, the mobile terminal device 50 determines whether or not the product to be measured is registered before the process of step S2001 in FIG. 20, and if the product to be measured is registered, the process may be terminated as it is. Thereby, when the product to be measured is registered, since the risk of performing improper product registration is low, it is possible not to notify an error based on the operation determination. Therefore, the frequency of errors can be suppressed.

[0260] (Modification Example 11) Next, Modification Example 11 of the embodiment will be described. In the above-described embodiment, not notifying an error based on the validity determination is based on the case where the product to be measured is registered. Instead of or in addition to such a configuration, in Modification Example 11, not notifying an error based on the validity determination may be based on the case where even if the product to be measured is not registered, there is simply a connection history with the measuring device 30.

[0261] ] In this way, if there is a connection history with the measuring device 30, it is clear that the product to be measured exists in the store even if it is not registered. For this reason, it is possible not to notify an error based on the validity determination. Even if it is configured in this way, the frequency of errors can be suppressed.

[0262] Hereinafter, an overview of the embodiment will be described. [Title of the 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 Art] In recent years, there has been known a system in which a shopping application is installed on a mobile terminal device such as a smartphone possessed by a customer, and the customer himself / herself operates to register products in a store (see, for example, Patent Document 1). The mobile terminal periodically checks its own position, and when the device is not located within the store, it notifies an error. [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Patent Application Publication No. 2013-541107 [Summary of the Invention] [Problems to be Solved by the Invention] However, in the prior art, there has been a problem that if an error is frequently notified, it may be impossible to smoothly let the customer make a purchase. For example, in an environment where it is difficult to obtain position information, such as when the store is located underground, the mobile terminal device may determine that it is not located within the store and frequently notify an error. The present invention has been made in view of such circumstances, and its object is to provide a technology that can smoothly perform shopping. [Means for Solving the Problems]

[0263] (1) In order to solve the above-described problems, a terminal device according to an aspect of the present invention includes: position information acquisition means for acquiring position information indicating a current location; store specific information acquisition means for acquiring store specific information presented in a store; registration means for starting product registration in response to the establishment of one of a first condition for specifying the store using the position information and a second condition for specifying the store using the store specific information; determination means for performing a validity determination as to whether the product registration is being properly performed; and notification means for notifying an error using the determination result of the determination means, wherein the notification means performs the notification based on the established start condition. The terminal device is characterized by the above. According to the above configuration, in the transaction due to the satisfaction of the first condition and the transaction due to the satisfaction of the second condition, the occurrence frequency of error notification can be made different, so that the error frequency can be suppressed according to the start condition. Therefore, according to the present embodiment, it is possible to suppress the shopping from being hindered by the error notification, and thus the shopping can be smoothly carried out.

[0264] (2) In the configuration of the above (1), the validity determination includes an existence determination as to whether or not it exists in the store using the position information acquired during the transaction, and the notification means performs the notification based on the existence determination in the transaction due to the satisfaction of the first condition, and may not perform the notification based on the existence determination in the transaction due to the satisfaction of the second condition. According to the above configuration, in the transaction due to the satisfaction of the second condition, it is possible not to perform the notification based on the existence determination. Therefore, in the transaction due to the satisfaction of the second condition, the frequency of error notification can be suppressed.

[0265] (3) In the configuration of the above (1) or (2), the validity determination includes a position information acquisition determination as to whether or not the position information has been acquired during the transaction, and the notification means may not perform the notification even if the determination result of the position information acquisition determination in which the position information is not acquired is obtained. According to the above configuration, it is possible to suppress the frequent occurrence of error notifications when the communication environment is not good.

[0266] (4) In the configuration of the above (3), a first request means for making a request for acquisition of the store identification information may be provided in response to obtaining a determination result in which the position information is not acquired in the position information acquisition determination. According to the above configuration, even when the customer is located in an area where the communication environment is not good, the customer can clarify that he / she is in the store by having the portable terminal device 50 read the store identification information (two-dimensional code). Therefore, it is possible to suppress improper product registration by customers who perform price checks and the like.

[0267] (5) In any of the configurations (1) to (4) above, the legitimacy determination may include an operation determination as to whether the operation related to the product registration has been properly performed. According to the above configuration, an error can be notified when an improper registration operation such as price checking is performed. Therefore, improper product registrations such as price checking can be suppressed. For this reason, it is possible to suppress the leakage of various information in the store such as price information.

[0268] (6) In any of the configurations (1) to (5) above, the legitimacy determination includes a store identification information acquisition determination as to whether the store identification information has been acquired during the transaction, and the notification means does not perform the notification based on the store identification information acquisition determination in the transaction where the first condition is satisfied, and may perform the notification based on the store identification information acquisition determination in the transaction where the second condition is satisfied. According to the above configuration, in a transaction where the second condition is satisfied, it is possible to clarify that the user is in the store by having the portable terminal device 50 read the store identification information (two-dimensional code). Therefore, it is possible to suppress improper product registrations by customers who perform price checks and the like. Also, in a transaction where the first condition is satisfied, since it is possible to periodically acquire the location information and perform the presence determination, it is possible not to perform the error notification based on the store identification information acquisition determination. Thereby, in the transaction where the first condition is satisfied, the frequency of error notification can be suppressed.

[0269] (7) In the configuration of (6) above, in the transaction where the second condition is satisfied, a second request means for making a request to acquire the store identification information may be provided in response to the elapse of a predetermined time from the start of the product registration. According to the above configuration, in a transaction where the second condition is satisfied, it is possible to clarify that the user is in the store by having the portable terminal device 50 read the store identification information (two-dimensional code) every time a predetermined time elapses. Therefore, it is possible to suppress improper product registrations by customers who perform price checks and the like.

[0270] (8) In any of the configurations of (1) to (7) above, the store identification information includes updated store identification information updated at a predetermined timing and non-updated store identification information that is not updated. The notification means may be configured not to perform the notification based on the validity determination in a transaction due to the establishment of the second condition when the updated store identification information is acquired, and to perform the notification based on the validity determination in a transaction due to the establishment of the second condition when the non-updated store identification information is acquired. According to the above configuration, in the case of a transaction due to the acquisition of updated store identification information, since it can be expected that the customer is likely to be present in the store, it is possible not to notify an error based on the store identification information acquisition determination or the operation determination. Further, in the case of a transaction due to the acquisition of non-updated store identification information, since it can be expected that the customer is less likely to be present in the store, by making it possible to notify such an error, it is possible to suppress improper product registration such as price checking.

[0271] (9) In any of the configurations of (1) to (8) above, the registration means can register the product to be measured by communicating with a weighing device that weighs the product to be measured. The notification means may be configured not to perform the notification regardless of the start condition when the product to be measured is registered. According to the above configuration, when it is clear that the customer is present in the store, it is possible not to notify an error.

[0272] (10) In any of the configurations of (1) to (9) above, when the first condition is not satisfied, it is provided with a third request means for requesting the acquisition of the store identification information. The registration means may start the product registration in response to the establishment of the second condition by the acquisition of the store identification information in response to the acquisition request by the third request means. According to the above configuration, even when the location information cannot be acquired, it is possible to prompt the acquisition of the store identification information and start the product registration.

[0273] (11) In order to solve the above-described problems, a product sales data processing system according to another aspect of the present invention is a product sales data processing system including a terminal device operated by a customer, the system comprising: a position information acquisition means for acquiring position 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 a start condition of either a first condition for identifying the store using the position 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 is being properly performed; and a notification means for notifying an error using the determination result of the determination means, wherein the notification means performs the notification based on the established start condition. A product sales data processing system characterized by the above is provided. According to the above configuration, in the transaction based on the establishment of the first condition and the transaction based on the establishment of the second condition, the occurrence frequency of error notification can be made different, so that the error frequency can be suppressed according to the start condition. Therefore, according to the present embodiment, it is possible to suppress the shopping from being hindered by the error notification, and thus the shopping can be smoothly performed.

[0274] (12) In order to solve the above-described problems, a notification method according to another aspect of the present invention is a method in which a computer used in a terminal device executes: a position information acquisition step of acquiring position information indicating a current location; a store identification information acquisition step of acquiring store identification information presented in a store; a registration step of starting product registration in response to the establishment of a start condition of either a first condition for identifying the store using the position information or a second condition for identifying the store using the store identification information; a determination step of making a validity determination as to whether the product registration is being properly performed; and a notification step of notifying an error using the determination result in the determination step, wherein in the notification step, the notification is performed based on the established start condition. A notification method characterized by the above is provided. According to the above configuration, in the transaction due to the satisfaction of the first condition and the transaction due to the satisfaction of the second condition, the occurrence frequency of error notification can be made different, so that the error frequency can be suppressed according to the start condition. Therefore, according to the present embodiment, it is possible to suppress the shopping from being hindered by the error notification, so that the shopping can be smoothly performed.

[0275] (13) In order to solve the above-described problems, a program according to another aspect of the present invention causes a computer used in a terminal device to function as position information acquisition means for acquiring position information indicating a current location, store-specific information acquisition means for acquiring store-specific information presented in a store, registration means for starting product registration in response to the satisfaction of one of a first condition for specifying the store using the position information and a second condition for specifying the store using the store-specific information, determination means for making a validity determination as to whether the product registration is being properly performed, and notification means for performing error notification using the determination result of the determination means, and the notification means performs the notification based on the satisfied start condition. A program characterized by that. According to the above configuration, in the transaction due to the satisfaction of the first condition and the transaction due to the satisfaction of the second condition, the occurrence frequency of error notification can be made different, so that the error frequency can be suppressed according to the start condition. Therefore, according to the present embodiment, it is possible to suppress the shopping from being hindered by the error notification, so that the shopping can be smoothly performed.

[0276] Note that all or part of each function (input / output, storage, processing (including determination)) in each device (such as the mobile terminal device 50) described above may be realized in another device different from the device described as the execution subject of the function.

[0277] Specifically, in the above description, the configuration in which the mobile terminal device 50 includes a location information acquisition unit, a store identification information acquisition unit, a registration unit, a determination unit, a notification unit, and a request unit has been described. All or part of these functional units may be provided in other computer devices. For example, all or part of these functional units may be provided in the transaction status management device 11, may be provided in the cloud server Sv, or may be provided in other computer devices. Also, the computer devices in which these functional units are provided are not limited to a plurality of units, and may be one unit. For example, one computer device may include 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 (registration data) after product registration. 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 processing (see FIGS. 8, 18, and 20). That is, for example, in step S1802 of the flowchart of FIG. 18, the process of determining the start condition of the transaction described as being executed by the mobile terminal device 50, and the process of notifying an error performed 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 sink client specialized for the input / output interface part regarding product registration. That is, the mobile terminal device 50 may receive various inputs (operations by an operator, detections by devices such as scanners), 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] Note that the shopping system 1 and the program for realizing the mobile terminal device 50 described above may be recorded on a computer-readable recording medium, and the program may be read into a computer system and executed. Here, the "computer system" shall include hardware such as an OS and peripheral devices. Also, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable recording medium" shall also include 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, and holds the program for a certain period of time. Also, the above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having 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. Also, the above program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the functions described above in combination with a program already recorded in a computer system.

Explanation of Signs

[0281] Sv… Cloud server, 1… Shopping system, 10… Store controller, 11… Transaction status management device, 20… POS terminal device, 30… Measuring 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

A program that causes a computer to function as a mobile terminal device that starts product registration in response to obtaining store-specific information presented in a store, wherein the computer is a store-specific information acquisition means capable of acquiring updated store-specific information and non-updated store-specific information, a registration means that starts product registration in response to the establishment of either one of a first condition for specifying the store using the updated store-specific information and a second condition for specifying the store using the non-updated store-specific information, functioning as, wherein the registration means when starting the product registration due to the establishment of the second condition, continues the product registration by acquiring store-specific information every time a predetermined time elapses, when starting the product registration due to the establishment of the first condition, continues the product registration regardless of the acquisition of store-specific information, and is characterized by causing the computer to function as such.

Images