JP2022108374A - Terminal device, commodity sales data processing system, reporting method, and program - Google Patents

Abstract

To enable shopping to be smoothly performed.SOLUTION: A terminal device includes positional information acquisition means, shop identification information acquisition means, registration means, determination means, and report means. The positional information acquisition means acquires positional information indicating a current place. The shop identification information acquisition means acquires shop identification information presented at a shop. The registration means starts commodity registration in response to establishment of either one of a first condition in which the shop is identified using the positional information and a second condition in which the shop is identified using the shop identification information. The determination means performs a correctness determination about whether or not the commodity registration is being performed correctly. The report means makes a report of an error using a determination result obtained by the determination means. The report means makes the report based on the start condition having been established.SELECTED DRAWING: Figure 18

Description

The present invention relates to a terminal device, a merchandise sales data processing system, a notification method, and a program.

2. Description of the Related Art In recent years, there is known a system in which a shopping application is installed in a mobile terminal device such as a smartphone owned by a customer, and the customer registers products at a store by the customer's own operation (see, for example, Patent Document 1). The mobile terminal device periodically confirms its own position, and notifies an error when the own device is not located inside the store.

Japanese Patent Publication No. 2013-541107

However, in the prior art, there is a problem that if errors are frequently reported, the customer may not be able to carry out the shopping smoothly. For example, in an environment where it is difficult to acquire location information, such as when a store is located underground, the mobile terminal device may judge that it is not located inside the store and frequently report an error. rice field.

SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technology that enables smooth shopping.

In order to solve the above-described problems, a terminal device according to one aspect of the present invention includes location information acquiring means for acquiring location information indicating the current location, and store specifying information acquiring means for acquiring store specifying information presented at the store. and a first condition for specifying the store using the location information, or a second condition for specifying the store using the store specifying information, according to the satisfaction of either one of the start conditions. , registering means for starting product registration, judging means for judging whether or not the product registration is valid, and notifying means for notifying an error using the judgment result of the judging means. The terminal device is characterized in that the notification means performs the notification based on the established start condition.

It is an explanatory view showing network composition of shopping system 1 concerning an embodiment. 2 is an explanatory diagram showing an installation example of the POS terminal device 20; FIG. 2 is a block diagram showing the hardware configuration of the POS terminal device 20; FIG. 2 is an explanatory diagram showing an example of a hardware configuration of a mobile terminal device 50; FIG. 3 is an explanatory diagram showing an example of the appearance of the weighing device 30. FIG. 3 is an explanatory diagram showing an example of a hardware configuration of a weighing device 30; FIG. 4 is an explanatory diagram showing an example of various information for each mobile terminal device 50 managed by a cloud server Sv. FIG. 4 is a sequence diagram showing the flow of processing related to product registration and payment in the shopping system 1. FIG. 4 is a flow chart showing an example of store entry processing performed by the mobile terminal device 50. FIG. 4 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. 6 is a flow chart showing an example of product registration processing for barcode products performed by the mobile terminal device 50. FIG. FIG. 10 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; 6 is a flowchart showing an example of product registration processing for products to be weighed performed by the mobile terminal device 50. FIG. FIG. 4 is an explanatory diagram showing an example of a procedure for registering products to be weighed; 4 is an explanatory diagram showing an example of a standby screen displayed on the weighing device 30; FIG. FIG. 5 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 50 after reading a connection code; 4 is an explanatory diagram showing an example of a screen during weighing displayed on the weighing device 30 and the mobile terminal device 50. FIG. 5 is a flowchart showing an example of notification processing based on position information performed by the mobile terminal device 50. FIG. 3 is an explanatory diagram showing an example of an error screen based on position information displayed on the mobile terminal device 50. FIG. 6 is a flowchart showing an example of notification processing based on product registration operation information performed by the mobile terminal device 50. FIG. FIG. 7 is an explanatory diagram showing an example of an error screen based on product registration operation information displayed on the mobile terminal device 50; 4 is a flowchart showing an example of registration information confirmation processing performed by the POS terminal device 20. FIG. FIG. 10 is an explanatory diagram showing an example of screen transitions displayed on the customer-side display unit 205 of the POS terminal device 20 at the time of payment; 7 is a flow chart showing Modified Example 1 of notification processing based on position information performed by the mobile terminal device 50. FIG. FIG. 11 is a flow chart showing a modified example 2 of notification processing based on position information performed by the mobile terminal device 50. FIG. 13 is a flow chart showing a modification 3 of notification processing based on store identification information performed by the mobile terminal device 50. FIG. FIG. 12 is a flowchart showing a modification 4 of notification processing based on position information performed by the mobile terminal device 50. FIG. FIG. 12 is a flow chart showing a modification 5 of notification processing based on product registration operation information performed by the mobile terminal device 50. FIG. FIG. 12 is a flow chart showing a modification 6 of notification processing based on product registration operation information performed by the mobile terminal device 50. FIG. FIG. 13 is a flow chart showing a modification 7 of notification processing based on product registration operation information performed by the mobile terminal device 50. FIG.

Embodiments of a terminal device, a merchandise sales data processing system, a notification method, and a program according to the present invention will be described below.

(embodiment)
(Network configuration of shopping system 1)
FIG. 1 is an explanatory diagram showing the network configuration of the shopping system 1 according to the embodiment. The shopping system 1 is an example of a product sales data processing system. The shopping system 1 can be installed in various stores such as supermarkets, home centers, convenience stores, and various goods stores.

In FIG. 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. a device 50; The mobile terminal device 50 is an example of a terminal device.

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, respectively. Each device and each terminal is a computer device including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication section, and the like.

The cloud server Sv is a server device that manages various types of information such as customer information, store information, and product information for each store. For example, the cloud server Sv generates cart information indicating a virtual cart for each customer based on the product information read by the mobile terminal device 50, 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.

The store controller 10 manages the POS terminal device 20 and the weighing device 30, and stores various information necessary for transactions such as product masters. The product master is a file in which product information such as product identification information (for example, JAN (Japanese Article Number) code), product name, selling price, etc. of each product is stored. The product master also includes product identification information, product names, and unit prices of products that require weighing (hereinafter referred to as “products to be weighed”). In addition to the product master, the store controller 10 also stores various kinds of information such as inventory status, sales history, deposit/withdrawal records, and the like. Store controller 10 may also store customer membership information.

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

The POS terminal device 20 is a computer device capable of executing settlement processing for performing settlement (settlement) of products registered by the mobile terminal device 50 . The POS terminal device 20 can settle accounts for products registered by the mobile terminal device 50 , as well as for products registered by itself or other POS terminal devices 20 . Further, in the present embodiment, the POS terminal device 20 is capable of switching between operation modes. Specifically, the POS terminal device 20 can operate in a checkout dedicated mode in which it functions as a settlement dedicated device, a clerk registration mode in which product registration is performed by the operation of a store clerk, and a customer registration mode in which product registration is performed by the operation of a customer. It is also possible to operate in (full self mode). In addition, in FIG. 1, the number of POS terminal devices 20 is illustrated as plural, but may be one.

The weighing device 30 is a computer device that weighs products to be weighed. The weighing device 30 calculates the amount of the product to be weighed using the weighed weight (or number) and the unit price of the product to be weighed. A product to be weighed is a product different from a normal product. Here, a normal product is, for example, a product with a JAN code attached. When reading the JAN code, the mobile terminal device 50 inquires of the cloud server Sv about the read JAN code, and acquires price data associated with the JAN code.

On the other hand, products to be weighed are products whose price varies depending on the weight and quantity of the product. Products to be weighed are, for example, fresh foods such as vegetables, fruits, fresh fish, and meat, and side dishes. The weighing device 30 prints and outputs a label that encodes the amount, weight, etc. of the product to be weighed. The label includes the price. The NON-PLU (Price Look Up) method is used for labels (barcodes) attached to products to be weighed. In addition, in FIG. 1, the number of the weighing devices 30 is illustrated as a plurality, but may be one.

The mobile terminal device 50 is a portable computer device such as a smart phone, tablet device, or mobile phone. The mobile terminal device 50 includes a communication unit, an imaging unit (camera), a touch panel, etc., and is operated by a customer. In this embodiment, the mobile terminal device 50 is detachably attached to the shopping cart. However, the mobile terminal device 50 may be installed in a non-detachable manner with respect to the shopping cart. Moreover, the mobile terminal device 50 may be owned by the customer, or may be a loan item that the store lends to the customer.

The mobile terminal device 50 scans (reads) a bar code (product code) attached to the product and accepts registration of the product. That is, the mobile terminal device 50 has a recognition function of recognizing barcodes attached to products.

It should be noted that the recognition function provided in the mobile terminal device 50 is sufficient as long as it can read the product code attached to the product, and does not have to be able to identify the product from the read product code. In other words, if the portable terminal device 50 can read the product code from the barcode when there is a barcode as an object in the captured image captured by the imaging function (the image acquired as the through image). good.

Moreover, 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 for extracting feature points from an image (through image, captured image) and recognizing an imaged target (object or the like). For example, the mobile terminal device 50 may specify (estimate) the imaged product using image recognition technology. By using such image recognition technology, the mobile terminal device 50 can also identify perishable foods such as vegetables and fruits that do not have barcodes, for example.

In addition, application software (hereinafter sometimes referred to as “shopping application”) for registering and paying for products related to the shopping system 1 is installed in the mobile terminal device 50 . By activating the shopping application, the mobile terminal device 50 reads the barcode attached to the product and transmits the read information to the cloud server Sv. As a result, the registered product information corresponding to the barcode is registered in the virtual cart of the cloud server Sv.

The mobile terminal device 50 also uses a two-dimensional code (which may be hereinafter referred to as "checkout code") corresponding to the registered product when checking out. The settlement code is represented by, for example, a QR code (registered trademark). When the POS terminal device 20 reads the payment code, it requests the cloud server Sv to transmit registration information corresponding to the mobile terminal device 50 . Then, when the POS terminal device 20 receives the registration information from the cloud server Sv, it becomes possible for the POS terminal device 20 to settle the account. In the following description, products registered in the virtual cart may be referred to as "registered products".

Further, in the present embodiment, the POS terminal device 20 is used as the device for settlement, but the present invention is not limited to this. For example, the settlement device may be a settlement-dedicated device installed in a store, or may be a settlement computer device installed in a non-detachable manner with respect to a shopping cart. This computer device may, for example, enable only card settlement using credit cards or prepaid cards.

(Installation example of POS terminal device 20)
FIG. 2 is an explanatory diagram showing an installation example of the POS terminal device 20. As shown in FIG. FIG. 2A is a perspective view of the POS terminal device 20 viewed from the customer side. FIG. 2B is a perspective view of the POS terminal device 20 as seen from the store clerk's side. As shown in FIG. 2A, a counter is placed on the right side of the POS terminal device 20 as viewed from the customer side. Although not shown, a counter may be placed on the left side of the POS terminal device 20 in FIG. 2(A). That is, counters may be placed on both sides of the POS terminal 20 . Also, a shopping basket can be placed on the counter.

As shown in FIG. 2, the POS terminal device 20 has a sign pole 220 . The sign pole 220 has a light emitting section. 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 in a predetermined lighting mode. The state of use of the POS terminal device 20 (in use, warning, calling a clerk, etc.) can be notified by the lighting mode of the sign pole 220 . The sign pole 220 is provided facing upward, and it is possible to inform the clerk who is not near the POS terminal device 20 of the usage state of the POS terminal device 20 .

(Configuration example of POS terminal device 20)
Next, the configuration of the POS terminal device 20 will be described with reference to FIGS. 2 and 3. FIG.
FIG. 3 is a block diagram showing the hardware configuration of the POS terminal device 20. As shown in FIG. 2 and 3, the same reference numerals are given to the same parts.

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

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 information used by the CPU 201 including programs.

A RAM 203 is a readable and writable memory, and stores various information. For example, the RAM 203 stores information acquired from the outside (for example, a product master acquired from the store controller 10, etc.) and information generated during processing. This information includes, for example, registration information generated in product registration processing, settlement information generated in settlement processing for settlement of registered products, and the like.

The hard disk 204 stores various information. For example, the hard disk 204 stores imaging results (for example, moving images) captured by the camera 216 . For example, instead of the ROM 202, the hard disk 204 may store various programs such as a merchandise sales data processing program executed by the CPU 201. FIG. Also, instead of the RAM 203, information obtained from the outside or information generated during processing may be stored.

The customer-side display unit 205 is a touch display for customers. The customer-side display unit 205 displays various information to the customer and receives various inputs from the customer.
A customer-side scanner unit 206 is a scanner unit for customers, and optically reads various kinds of information. For example, the customer-side scanner unit 206 optically scans barcodes (product codes, etc.) attached to products and codes (barcodes, two-dimensional codes, etc.) printed on accounting tickets (registered trademark). read. In addition to the above, the customer-side scanner unit 206 scans codes (bar codes, 2 dimension code, etc.) may be read. Note that registration of products is not limited to registration by reading codes by the customer-side scanner unit 206 . For example, it is possible to display a preset key (a button for ordering a product) corresponding to the product on the customer-side display unit 205, and to register the product by operating (pressing) the preset key by the customer. be. Further, the customer-side scanner unit 206 can also 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.

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

Note that the card settlement unit 208 of this embodiment includes a card recognition unit, a display unit, and an operation unit, but is not limited to this, and may include at least a card recognition unit. The card recognition unit of the present embodiment may be compatible with contact cards (IC cards, magnetic cards), or may be compatible with non-contact cards (IC cards). good.

The change dispenser 209 (cash settlement unit) is a cash settlement mechanism, and has an inlet for banknotes and coins and an outlet for banknotes and coins. The change machine 209 calculates the amount of money inserted into the slot, calculates the amount of change that is the difference between the amount of money inserted and the amount of purchase, and ejects the change from the slot. The change dispenser 209 is directed toward the customer side, and receives various operations and cash insertion from the customer. Note that the change machine 209 has a sensor that detects banknotes and coins inserted into the slot. The sensor detects that banknotes and coins have been inserted into the slot, and detects the number of bills and coins by denomination.

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 receives various inputs from the clerk. A preset key (a button for ordering the product) corresponding to the product is displayed on the store clerk-side display unit 210, and the product is registered when the preset key is operated (depressed) by the store clerk. In addition, a subtotal key for accepting the completion of product registration is displayed on the store clerk side display section 210 .

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

The clerk-side scanner unit 212 is a scanner unit for the clerk, and optically reads various kinds of information. For example, the clerk-side scanner unit 212 optically reads a bar code attached to a product or a clerk code attached to a clerk's name tag. In addition to the above, the clerk-side scanner unit 212 may read codes printed on checkout tickets, coupons, and codes printed on various cards. In addition, the clerk-side scanner unit 212 can also read a two-dimensional code for payment. When the clerk-side scanner unit 212 reads the payment code, the POS terminal device 20 can make payment based on the read content.

It should be noted that product registration is not limited to registration by code reading by the store clerk-side scanner unit 212 . For example, a key corresponding to a product (for example, XX newspaper) may be arranged in the key operation unit 211, and the product may be registered when the key is operated (depressed) by the store clerk. .

The printing unit 213 prints and outputs various media (receipts, invoices, accounting coupons, etc.). The printing unit 213 can change the direction of the medium issuing port. Specifically, the printing unit 213 has a rotatable mechanism, and is configured so that the medium issuing port faces from the clerk side to the customer side, and from the customer side to the clerk side. Note that the direction of the medium issuing port may be manually changeable, or may be automatically changeable according to the switching of the operation mode. Note that the printing unit 213 may include a sensor that detects correctness or incorrectness of the orientation of the print issuing port.

The audio output unit 214 outputs audio. For example, the audio output unit 214 outputs audio guidance, warning sounds, and the like. Voice guidance and warning sounds are related to product registration and payment.
The communication unit 215 is an interface that transmits and receives information to and from other devices (store controller 10, transaction status management device 11, and other POS terminal devices 20).

The camera 216 is attached to the upper right of the customer-side display section 205 when viewed from the customer side. The camera 216 is a camera that continuously captures moving images or still images. A CCD (charge coupled device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera can be used as the camera 216 . A camera 216 captures an image of the customer's operation status at the time of payment. Specifically, the camera 216 captures images of banknotes and coins held by the customer, the change machine 209, hand movements, and the like. In addition, the camera 216 captures an image of the customer's operation status at the time of product registration. Specifically, the camera 216 can also capture the inside (merchandise) of shopping baskets on the counters provided on both sides of the POS terminal device 20 and the operation status of the customer at the time of registration. Also, the camera 216 may be separately provided on the store clerk's side. In this case, the POS terminal device 20 can determine whether or not there is a clerk based on the imaging result of the camera 216 provided on the clerk side.

(Hardware Configuration of Mobile Terminal Device 50)
FIG. 4 is an explanatory diagram showing an example of the hardware configuration of the mobile terminal device 50. As shown in FIG. 4, mobile terminal device 50 includes CPU 401, ROM 402, RAM 403, memory 404, communication unit 405, operation unit 406, camera 407, microphone 408, display 409, speaker 410, and GPS (Global Positioning System) unit 411. there is Each part is connected by a bus 420 respectively.

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

The memory 404 stores various data. A flash memory, for example, is used for the memory. The memory 404 stores various programs such as shopping applications and notification programs, and various data such as map data and store information.
The communication unit 405 is connected to a network and connected to another device (for example, transaction management server Sv) via the network. Communication networks that function as networks include the Internet and mobile phone networks.

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

The speaker 410 outputs sounds including voice.
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. In addition, the mobile terminal device 50 includes various sensors (eg, a gyro sensor, an acceleration sensor, a distance sensor, etc.) (not shown), and detects various states of the mobile terminal device 50 (eg, inclination of the mobile terminal device 50, 50 and the product).

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

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.

A RAM 303 is a readable and writable memory, and stores various information. For example, the RAM 303 stores information read from the ROM 302 or memory 304, information obtained from the outside, information generated during processing, and the like.

Memory 304 stores various information. The memory 304 stores, for example, the unit price of the product to be weighed acquired from the store controller 10 . Various information stored in the memory 304 may be stored in an external device (for example, the store controller 10, an external server device, etc.). In this case, when using the various information, the weighing device 30 may inquire of the external device and acquire the various information.

Note that the memory 304 may store programs executed by the CPU 301 instead of the ROM 302 . Also, instead of the RAM 303, the memory 304 may store information read from the ROM 302, information obtained from the outside, information generated during processing, and the like.

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

Further, the communication unit 305 performs short-range wireless communication with the mobile terminal device 50 in addition to communication via network communication. The number of devices that the communication unit 305 can communicate with the mobile terminal device 50 by short-range wireless communication is limited, for example, one device. Specifically, short-range wireless communication is performed with the mobile terminal device 50 on a one-to-one basis. 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, 4G (Generation) line, or the like. Note that the number of mobile terminal devices 50 that can be communicatively connected by the communication unit 305 to the mobile terminal device 50 by short-range wireless communication is not limited to one, and may be two or three.

The display unit 306 displays various information to the customer and receives operations from the customer. Various types of information displayed on the display unit 306 include the name of the product to be weighed and the quantity to be weighed, as well as guidance on weighing. Various information displayed on the display unit 306 is a two-dimensional code (hereinafter sometimes referred to as a “connection code”) read by the mobile terminal device 50 in order to start one-to-one communication with the mobile terminal device 50. .)including.

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

(Example of information managed by 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. It should be noted that the cloud server Sv stores part or all of the various information in another device such as a file server that the cloud server Sv can access instead of or in addition to storing the various information in the storage unit within its own device. may be stored.

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

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

The customer name is the customer's name, nickname, or the like.
The customer registration date is the date and time when the customer information is newly registered in the cloud server Sv.
The customer rank is a rank according to the customer's purchase record.
The number of points is the number of points given to the customer for shopping using the shopping application. Note that the number of points may include the number of points for each store.

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

(store information)
FIG. 7B shows an example of store information. Store information is information for managing each store. As shown in FIG. 7B, the store information includes items such as store identification information, store name, store identification information 1 (two-dimensional code information), and store identification information 2 (location information).
The store identification information includes a store (store 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 (store name) or company name and the branch name.
The store identification information 1 and 2 is information for identifying a store to trade (a store where merchandise is bought and sold). The store specific information 1 is, for example, information represented by a two-dimensional code displayed at the store. The store identification information 2 is location information (GPS information) indicating the location of the store.

(Cart information)
FIG. 7C shows an example of cart information. The cart information is information about products registered by the customer at the store. As shown in FIG. 7C, 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 pending product information (total).
The cart identification information is information for identifying cart information that is a virtual cart. Specifically, the cart identification information includes store identification information, dates, and serial numbers (eg, serial numbers by date for each store).

The transaction start date and time is the date and time when the transaction was started, for example, the date and time when the cart information was generated. Note that the transaction start date and time may be the date and time of registration of one product item, or more specifically, the date and time when the registered product information (registered product 1: ○○ Nakano sauce) shown in FIG. 7(C) is stored. good. Further, instead of or in addition to the transaction start date and time, the registration date and time for each product may be separately stored.

The transaction end date and time is the date and time when the transaction was terminated, specifically, the date and time when the settlement was made. For example, the transaction end date and time is the date and time when the settlement is finished, but it may be the date and time when the settlement is started.
The customer identification information is information that uniquely identifies the customer who conducts the transaction.

Registered product information (total) is cumulative information updated each time a product is registered. The registered product information (total) includes the number of products (number of products), approximate subtotal amount, subtotal amount, and the like.
The registered product information N (N is an integer) includes the product number (data number) registered for the N item. The registered product information N includes the product code, product name, price, registration date and time of the product, and the like. Specifically, the registered product information 1 (○○ medium thick sauce) indicates the product registered as one item. Registered product information 2 (XX cheese) indicates the product registered as the second item. Note that in the example shown in FIG. 7C, the illustration of registered product information for the third and subsequent items is omitted.

Next, the reserved product information (total) will be described. A pending product is a product that requires confirmation by a store clerk before starting payment. For example, pending products include types such as non-scanned products, NON file products, age-confirmed products, security tag products whose security tags need to be removed, and medicines.

An unscanned product is a pending product that could not be registered due to failure in scanning the product code (failure to read by the scanner). For example, if the package of the product is wrinkled, or if the printed barcode is faint or dirty, the barcode may not be recognized due to timeout.

Here, a detailed description will be given of the failure to recognize the barcode due to timeout. The mobile terminal device 50 includes various sensors (eg, a gyro sensor, an acceleration sensor, a distance sensor, etc.), and can determine that a barcode is being read using the detection results of the various sensors and the imaging results of the camera 407. is. Specifically, the mobile terminal device 50 is in a state in which the mobile terminal device 50 is tilted using the detection results of various sensors, and the product is located at a position separated from the mobile terminal device 50 by a certain distance. The existing situation can be identified as reading a barcode. Then, when the mobile terminal device 50 cannot read the barcode within a predetermined period of time after determining that the barcode is being read, the mobile terminal device 50 specifies the unscanned product as a time-out.

Also, unscanned items include, for example, items placed in a basket by pretending to have read the item's barcode. In other words, unscanned products include products that may have undergone unauthorized manipulation, and thus include products that require confirmation by the store clerk as to whether or not there has been unauthorized manipulation. Fraudulent operations are detected using, for example, scan results indicating the presence or absence of barcode scanning, imaging results of cameras that capture images of the inside of a shopping basket, and detection results of detecting the total weight of products in a shopping basket. be done.

A NON file product is, for example, a product that is not registered in the product master. Specifically, for the NON file product, the product code was successfully scanned (not unscanned product), and although the product master (cloud server Sv) was inquired about the product with the product code, the product could not be specified. This is a product that could not be registered due to a failure (the product inquiry was NG).

Age-confirmed products are, for example, products that minors cannot purchase, such as alcoholic beverages and cigarettes.
Security tag products are products with security tags attached, such as products with a certain amount of money or more.
A drug is, for example, a product that requires a pharmacist's explanation.

As shown in FIG. 7C, the pending product information (total) includes the number of items and the type of pending product (unscanned product, NON file product). Reserved product information (reserved product N: N is an integer) is information about N items of reserved products, and includes the reserved product type of the N items of reserved products. The reserved product type is information indicating the type of reserved product. In this example, the reserved product type "1" indicates an unscanned product, and the reserved product type "2" indicates a NON file product. Further, the pending product information includes the registration date and time of the product. The illustration shows that non-scanned products and NON file products are registered as pending products. These types are stored in the information (total).

In addition to the reserved product type "1", the reserved product information of the unscanned product includes 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.

The reserved product information of the NON file product includes the product code read by the mobile terminal device 50 in addition to the reserved product type “2 (NON file product)”. For example, the pending product information 2 includes "2 (NON file product)" indicating the pending product type and the product code.

(Notification of error by portable terminal device 50)
Using the location information received from the GPS unit 411, the mobile terminal device 50 periodically determines whether or not the mobile terminal device 50 is located inside the store. Generally, the mobile terminal device 50 notifies an error when it determines that the mobile terminal device 50 does not exist in the store or when it cannot receive the position information.

Therefore, in an environment where it is difficult to obtain location information, such as when a store is located underground, the mobile terminal device 50 may determine that it is not located inside the store and report an error. . As a result, if an error is frequently reported, the customer may not be able to carry out the shopping smoothly. Therefore, in the present embodiment, frequent notification of errors is suppressed so that shopping can be performed smoothly. The error notification performed by the mobile terminal device 50 will be described in detail below.

(Functional Configuration of 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 section, a shop identification information acquisition section, a registration section, a determination section, a notification section, and a request section. Each unit is implemented by the CPU 401 . That is, the CPU 401 executes the notification program stored in the ROM 402 to implement the function of each unit.

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

The store identification information acquisition unit acquires store identification information presented at the store. The store specific information is represented by, for example, a bar code or a two-dimensional code. The store specific information is presented near the doorway of the store. The shop specific information is displayed on a monitor such as a digital signage, for example. However, the store specific information may be printed on paper and posted on the wall or the like.

The registration unit starts product registration when the start condition is satisfied. The start condition is either one of the first condition and the second condition. The first condition is a condition for specifying a store using position information. Specifically, the first condition uses the location information of the store indicated by the store identification information 2 in FIG. This is a condition for determining that the mobile terminal device 50 exists in the store. The second condition is a condition for specifying a store using the store specifying information. Specifically, the second condition is a condition under which it is determined that the mobile terminal device 50 exists in the store using the store identification information 1 (two-dimensional code information) in FIG. 7(C).

(Details of legal judgment)
The judging unit judges whether or not the merchandise registration is properly performed. Validity determination includes, for example, operation determination and existence determination. First, operation determination will be described. The operation determination is a determination as to whether or not the operation related to product registration is properly performed. If the operation is valid, it means that the product is registered as usual. Product registration is done.

On the other hand, in the operation determination, the determination unit determines that the registration operation is improper when a product different from the usual registration is performed. Specifically, the registration of an unusual product is, for example, a registration that can be regarded as a price check by a competitor. More specifically, for example, when the number of registered products reaches or exceeds a certain number (for example, 50 or more), the determination unit determines that the operation is illegal. If the registered products are all canceled after that, it is more likely that a price check was performed.

Further, in determining the operation, the time required for registration may be taken into consideration. good. Further, in the operation determination, the classification of the registered product may be taken into consideration. , it may be determined that the registration operation is illegal.

Next, existence determination will be described. Presence determination is a determination of whether or not the customer exists at the store using position 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 presence determination, the determination unit determines that the mobile terminal device 50 is valid when it is present in the store (within range). On the other hand, in the presence determination, the determination unit determines that the portable terminal device 50 is not in the store (exists outside the service area) as inappropriate.

(Regarding error notification based on established start conditions)
The notification unit uses the determination result of the determination unit to perform error notification. In principle, the reporting unit reports an error when it is determined to be illegal in the legality determination, and does not report an error when it is determined to be legitimate in the legality determination. After reporting the error, the mobile terminal device 50 may delete the registered product. In addition, when the error is notified, the mobile terminal device 50 may end the shopping application (for example, log out).

The notification unit notifies of an error based on the satisfied start condition. The error notification based on the start condition means that the error notification may or may not be performed depending on the start condition. For example, notification of an error based on presence determination is performed in a transaction when the first condition is met, but is not performed in a transaction when the second condition is met. It should be noted that even if the error notification is not performed, the validity determination by the determination unit may be performed.

(Regarding location information acquisition judgment)
Further, in the present embodiment, the legitimacy determination includes position information acquisition determination in addition to the above-described operation determination and existence determination. The position information acquisition determination is a determination as to whether or not the position information of the current position is acquired by the position information acquiring means during the transaction. In the position information acquisition determination, the determination unit determines that the position information is valid if the position information is acquired, and determines that the position information is invalid if the position information is not acquired.

In addition, in the position information acquisition determination, when the determination result that the position information is acquired is obtained, the determination unit performs the existence determination using the acquired position information. Therefore, the notification unit notifies an error when the position information is acquired in the position information acquisition determination and the portable terminal device 50 is determined not to exist in the store (exists out of service area) in the existence determination.

Notification of an error based on position information acquisition determination is not performed when a position information acquisition determination result in which position information is not acquired is obtained in a transaction based on the establishment of the first condition. That is, when the communication environment is not good, such as when the user is underground, and the location information cannot be acquired (when the determination result indicating that the location information acquisition determination is unfair), the notification unit does not notify the error. . Also, in this case, the registration unit enables continuous product registration. That is, in this embodiment, product registration is not interrupted when position information is not acquired.

(Regarding acquisition request for store specific information)
In the present embodiment, when starting shopping using the shopping application, specifying the store using the location information takes precedence over specifying the store using the store specifying information. Specifically, when the store cannot be specified based on the position information before the product registration is started, that is, when the first condition is not satisfied, the request unit (third request means) requests acquisition of the store specifying information. . More specifically, the request unit makes an acquisition request for shop identification information when the shop cannot be identified using the position information. The request unit makes an acquisition request, for example, by notifying the display 409 of "please read the store specific information".

The registration unit starts product registration when a second condition is satisfied by acquiring the store identification information in response to the acquisition request by the request unit. It should be noted that if the store identification information is not acquired even after a certain period of time has passed, the request unit may request acquisition of the store identification information again. Further, if the store identification information is not acquired even after a certain period of time has passed, the mobile terminal device 50 may notify that shopping cannot be started.

(When connected to weighing device 30)
The registration unit can register the products to be weighed by communicating with the weighing device 30 that weighs the products to be weighed. A product to be weighed cannot be registered unless it is connected to the weighing device 30 for communication. For this reason, the fact that the product to be weighed has been registered means that the mobile terminal device 50 (the customer) is present in the store. Therefore, in the present embodiment, the notification unit does not perform error notification when a product to be weighed is registered, regardless of the start condition. It should be noted that when the product to be weighed is registered, an error notification is not performed, but the judging unit may make a valid judgment.

(Example of processing related to product registration and payment in shopping system 1)
FIG. 8 is a sequence diagram showing the flow of processing related to product registration and payment in the shopping system 1. As shown in FIG. In FIG. 8, a customer visits a store, registers a product to be purchased using his/her mobile terminal device 50, and completes payment for the product on the POS terminal device 20. explain.

Step S801: First, the mobile terminal device 50 executes activation processing for activating the shopping application according to the customer's operation. In the activation process, the mobile terminal device 50 checks the version of the shopping application, and displays a screen prompting an upgrade as necessary. Also, if it is the first activation, the activation process is completed by displaying the consent screen of the terms of use and obtaining the customer's consent.

Step S802: Next, the mobile terminal device 50 performs store entry processing (see FIG. 9). In the store entry process, the mobile terminal device 50 transmits, for example, the location information of the current location obtained from the GPS unit 411 to the cloud server Sv. When cloud server Sv receives the location information of the current location from mobile terminal device 50 , cloud server Sv searches for stores located near mobile terminal device 50 and transmits the information to mobile terminal device 50 . The mobile terminal device 50 identifies the store where the customer is shopping based on the information received from the cloud server Sv, and transmits information on the identified store to the cloud server Sv.

Step S803: The cloud server Sv generates cart information upon receiving the information of the store where the customer is shopping.
Step S804: After completing the entering process, the mobile terminal device 50 waits for the start of shopping. Specifically, the mobile terminal device 50 displays the shopping top screen and waits for the customer to press the shopping start button.

Step S805: The mobile terminal device 50 displays the imaging area on the display 409 and performs shopping start processing.
Step S806: The mobile terminal device 50 performs product registration processing (see FIGS. 11 and 13). Specifically, the mobile terminal device 50 scans the barcode attached to the product according to the customer's operation. When the product is scanned, the portable terminal device 50 transmits the product code obtained by scanning to the cloud server Sv together with the cart identification information. If the product indicated by the read product code is, for example, a reserved product such as an unscanned product, cart identification information and information indicating the reserved product are transmitted as the transmission/reception data D3.

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 containing the received cart identification information and updates the registered product information. Specifically, when the cloud server Sv receives the product code of the N item, it stores the registered product information (registered product N) indicated by the product code. More specifically, the cloud server Sv associates and stores product codes, product names, and prices. The cloud server Sv also updates cumulative information (total number of items, subtotal amount, etc.) of the registered product information in the specified cart information.

Step S808: After performing the product registration process, the mobile terminal device 50 determines whether or not the product registration is valid. Notification processing (see FIGS. 18 and 20) for notification is performed. As a result, for example, when the customer goes out of the store after entering the store and performs an improper product registration such as a price check, an error can be notified.

Step S809: Then, the mobile terminal device 50 performs registered product display processing for adding and displaying the registered product on the registration screen. The registered product display processing includes processing for accepting quantity changes and deletions.
Step S810: The portable terminal device 50 determines whether or not an instruction to start settlement (completion of registration) has been received by the customer's operation. If no instruction to start settlement has been received, the process returns to step S806. When the instruction to start settlement is received, the process proceeds to step S811.

Step S811: The mobile terminal device 50 generates a settlement code upon receiving an instruction to start settlement. 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 the registration information to the POS terminal device 20 . The registration information is information necessary for settlement, and includes, for example, the product name, price, subtotal amount, etc. of the registered product information. After generating the settlement code, the mobile terminal device 50 displays the generated settlement code on the display 409 .

Step S<b>812 : The POS terminal device 20 reads the settlement code displayed on the mobile terminal device 50 . Specifically, the customer who has completed product registration causes the customer-side scanner unit 206 of the POS terminal device 20 to scan the settlement code displayed on the display 409 of the portable terminal device 50 . Thereby, the POS terminal device 20 acquires the cart identification information.

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

Step S814: When the cloud server Sv receives the transmission request information from the POS terminal device 20, it extracts the cart identification information from the transmission request information and identifies the cart information containing the cart identification information.
Step S815: After specifying the cart information, the cloud server Sv transmits to the POS terminal device 20 various information necessary for checkout, including cart identification information, registration information (information indicating registered product information and subtotal amount), and language information. do. It should be noted that, if the specified cart information includes a pending product, the cloud server Sv transmits registration information including information on the pending product to the POS terminal device 20 .

Step S816: When the POS terminal device 20 receives the registration information from the cloud server Sv, the customer confirms the registration information (see FIG. 24). It should be noted that, if the registered information includes a pending product, in the confirmation processing of the registered information, a store clerk is called and the pending product is confirmed by the store clerk.

Step S817: The POS terminal device 20 executes settlement processing. The settlement process includes a process of accepting selection of the payment type. Note that the payment type may be registered in advance in the shopping application. If the payment type is cash, the POS terminal device 20 accepts cash input, pays out change, and issues a receipt in the settlement process. Then, the POS terminal device 20 transmits information indicating the content of the payment and cart information to the cloud server Sv. Then, the cloud server Sv stores the transaction end date and time (settlement date and time) of the cart information.

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: Upon receiving the transaction completion notification, the mobile terminal device 50 deletes the product registered in the mobile terminal device 50 and terminates the shopping application. Note that the mobile terminal device 50 may generate and display the settlement code in step S811, delete the product registered in the mobile terminal device 50, and terminate the shopping application. Thus, a series of processing ends.

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 collectively transmit these pieces of information to the cloud server Sv at the timing of receiving an instruction to start settlement. By doing so, it is possible to reduce the number of communications between the mobile terminal device 50 and the cloud server Sv.

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

Upon receiving the request, the cloud server Sv uses the current location of the mobile terminal device 50 and the shop information in FIG. A store is searched and the search result is transmitted to the mobile terminal device 50 . The mobile terminal device 50 refers to the search result received from the cloud server Sv and determines whether or not there is a store near the mobile terminal device 50 (step S904).

If there is no store near the mobile terminal device 50 (step S904: NO), the mobile terminal device 50 returns to step S903, widens the search range, and makes a request to search for nearby stores again. If there is no store near the mobile terminal device 50, it may be notified that there is no store nearby. If there is a store near the mobile terminal device 50 (step S904: YES), the mobile terminal device 50 determines whether there is one store nearby (step S905).

If there is one store nearby (step S905: YES), the mobile terminal device 50 proceeds to step S907. If there is more than one store nearby (step S905: NO), that is, if there are multiple stores nearby, the mobile terminal device 50 accepts the customer's selection of a store to shop at (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 specified in step S907, the transaction is started when the first condition is met.

If the location information of the current location is not acquired in step S902 (step S902: NO), specifically, for example, if the communication environment is not good and the GPS unit 411 cannot acquire the location information, the mobile terminal device 50 A request is made to read the store identification code presented to the store (step S908). Specifically, in step S908, the portable terminal device 50 notifies on the display 409, "Please scan the store identification code presented at the store."

The portable terminal device 50 waits until the store identification code is read (step S909: NO), and when the store identification code is read (step S909: YES), the identification of the store is completed (step S910), and a series of processing is terminated. do. When the store is specified in step S910, the transaction is started due to the establishment of the second condition.

(Screen example 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. 10A shows a store selection screen 1000 displayed on the display 409 of the mobile terminal device 50. FIG. Store selection screen 1000 includes map area 1001 and selection button 1002 .

A map area 1001 indicates 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 receiving selection of A store and a B store selection button 1002b for receiving selection of B store. When the customer presses one of the selection buttons 1002, the store to enter is determined. If there is only one store candidate, the store is determined as the store to enter.

FIG. 10(B) shows an example when the mobile terminal device 50 acquires the store identification information. In FIG. 10B, a monitor 1010 is, for example, digital signage installed in a store. A store identification code 1011 indicating store identification information is displayed on the monitor 1010 . When the customer activates the shopping application and causes 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 .

Note that the two-dimensional code is not limited to being displayed on the monitor 1010, and may be printed and displayed on a printed matter such as a poster. The printed matter may be posted near the entrance/exit of the store. Alternatively, information corresponding to the store specific information may be presented to the customer for operation input.

It should be noted that the cloud server Sv can also specify the store, and this will be supplemented. FIG. 10C shows an example when the cloud server Sv identifies the store where the mobile terminal device 50 is located. In FIG. 10C, the imaging terminal 1020 is installed, for example, near the entrance of a store. A barcode 1021 indicating the identification information of the mobile terminal device 50 is displayed on the mobile terminal device 50 . When the customer causes the imaging terminal 1020 to read the barcode 1021, the imaging terminal 1020 notifies the cloud server Sv of the fact that the mobile terminal device 50 identified by the barcode 1021 is present in the store along with the shop identification information. Send information indicating Cloud server Sv transmits store identification information indicating the store where mobile terminal device 50 is located to mobile terminal device 50 identified by barcode 1021 . Even in this way, the mobile terminal device 50 can obtain the shop identification information.

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

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

If the timeout has expired (step S1103: YES), the mobile terminal device 50 notifies that the product is on hold (step S1104). The notification prompts the customer to put the merchandise into a reserved merchandise bag separate from the shopping basket, and notifies that the store clerk will register the merchandise at the time of payment. Then, the mobile terminal device 50 registers the pending product information (unreadable product) (step S1105), and ends the series of processes.

In step S1102, if product identification information can be acquired from the barcode (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 that it is a pending product. If the product is not a NON file product (step S1106: NO), the product is registered (step S1107).

Then, the mobile terminal device 50 determines whether or not the registration operation is illegal (step S1108). An illegal registration operation means, for example, that the number of registered products exceeds a certain number (for example, 50 or more). If the registration operation is not illegal (step S1108: NO), the mobile terminal device 50 terminates the series of processes. If the registration operation is illegal (step S1108: YES), the mobile terminal device 50 stores product registration operation information indicating that the registration operation is illegal in the memory 404 (step S1109), and ends the series of processes. .

(Example of a screen 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 the entry processing is completed. 12A shows a top screen 1200 displayed on the display 409 of the mobile terminal device 50. FIG. The top screen 1200 includes information presentation buttons 1201 (1201a to 1201c) and a registration start button 1202. FIG. The shop information button 1201a is a button for accepting start of display of shop information such as a floor guide. The notification button 1201b is a button for accepting display start of notification shop information such as an event. The profit information button 1201c is a button for accepting start of display of sale items such as advertisement information. A registration start button 1202 is a button for accepting start of display of an imaging screen on the display 409 .

FIG. 12B shows a registration screen 1210 for product registration. Registration screen 1210 includes imaging area 1211 , registered product display area 1212 , total amount display area 1213 , and checkout start button 1214 . The imaging area 1211 is an area in which the barcode attached to the 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 in which registered various products (product name, quantity, price, etc.) are displayed. In the registered product display area 1212, registered products are displayed in the order in which they were registered. Specifically, the most recently registered product is displayed above the registered product display area 1212 .

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

FIG. 12(C) shows a settlement start acceptance screen 1220 . Settlement start acceptance screen 1220 includes guidance display 1221 , settlement code 1222 , and registration return button 1223 . The guidance display 1221 shows guidance to the effect that the POS terminal device 20 is caused to read the settlement code 1222 . The settlement code 1222 is, for example, coded 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. A registration return button 1223 is a button for accepting a return to the registration screen 1210 (FIG. 12B). When the customer causes the customer-side scanner unit 206 of the POS terminal device 20 to read the settlement code 1222, the POS terminal device 20 starts settlement.

(An example of product registration processing shown in step S806 of FIG. 8 (part 2))
FIG. 13 is a flowchart showing an example of product registration processing for products 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 portable terminal device 50 waits until the temporary registration code 1403 of the product to be weighed is scanned (step S1301: NO). is provisionally registered (step S1302). Note that the temporarily registered weighing target product is displayed on the display 409 .

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

Note that even if the connection code 1511 is scanned while the product to be weighed is not provisionally registered, the mobile terminal device 50 does not request connection to the weighing device 30 . This is because if the connection time between one mobile terminal device 50 and the weighing device 30 becomes longer, other customers will not be able to use the weighing device 30. This is to shorten the time for which the

When receiving a connection request from the mobile terminal device 50, the weighing device 30 performs pairing including authentication of one-to-one communication and determination of whether the temporarily registered product is a product to be weighed by the weighing device 30. judgment is made. When the pairing is determined to be successful, the weighing device 30 starts one-to-one communication with the mobile terminal device 50 .

Next, the mobile terminal device 50 determines whether communication connection with the weighing device 30 has been established (step S1305). If the communication connection with the weighing device 30 is established (step S1305: YES), the portable terminal device 50 acquires the weight value of the product placed on the platform 320 by the customer from the weighing device 30 (step S1306). After weighing, the weighing device 30 issues a label indicating the weighing result and transmits the weighing result to the portable terminal device 50 according to the customer's operation. That is, after the weighing by the weighing device 30 is completed, the mobile terminal device 50 acquires the weighing result from the weighing device 30 by the operation of the weighing device 30 by the customer.

When acquiring the weighing result, the mobile terminal device 50 displays the weighing result (step S1307). Then, the mobile terminal device 50 displays a registration update screen and officially registers the product to be weighed (step S1308). Thereafter, the mobile terminal device 50 determines whether or not the weighing (main registration) of all the temporarily registered weighing target products has been completed (step S1309). When weighing of all the temporarily registered weighing target products is completed (step S1309: YES), the mobile terminal device 50 terminates communication with the weighing device 30 (step S1310), and terminates a series of processes.

On the other hand, if weighing of all the temporarily registered weighing target products has not been completed (step S1309: NO), the mobile terminal device 50 returns to step S1306 to perform official registration of the other temporarily registered weighing target products. process.

In step S1305, if the communication connection with the weighing device 30 is not established (step S1305: NO), the mobile terminal device 50 notifies a retry (step S1311). The mobile terminal device 50 then determines whether or not to end the registration (step S1312). The mobile terminal device 50 determines to end the registration when receiving the end of the registration from the customer or when the retry is performed a certain number of times.

If the registration is not completed (step S1312: NO), that is, if the continuation of the registration is received from the customer, or if the fixed number of retries has not been performed, the mobile terminal device 50 returns to step S1304. On the other hand, if the registration is to end (step S1312: YES), the mobile terminal device 50 deletes the provisionally registered weighing target product (step S1313), and ends the series of processes.

Note that in the above-described process, the timing at which the weighing result is transmitted to the mobile terminal device 50 is set as the timing at which the label is issued, but this is not restrictive. For example, it may be the timing when the weighing of all the products has been 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 at which the weighing is completed.

(Regarding the procedure for registering products to be weighed)
Next, a procedure for registering a product to be weighed will be described with reference to FIGS. 14 to 17. FIG.
FIG. 14 is an explanatory diagram showing an example of a procedure for registering products to be weighed. FIG. 14 illustrates an example in which the camera 407 of the mobile terminal device 50 captures the identification information of the product to be weighed that the customer wishes to purchase.

In a corner (sales floor) where fruits are placed in the store, commodities 1401 (1401a to 1401c) to be weighed and displays 1402 (1402a to 1402c) are arranged. The products to be weighed 1401 include, for example, a lemon product to be weighed 1401a, an apple product to be weighed 1401b, and an orange product to be weighed 1401c. A display 1402a-1402 is positioned behind each item to be weighed 1401a-1401c. Although the lemon display 1402a will be mainly described below as an example, the same applies to the other displays 1402b and 1402c.

The display 1402a displays the characters "lemon", the unit price, and the temporary registration code 1403. FIG. The unit price indicates the price per kg. The temporary registration code 1403 includes information (product identification information) identifying the product 1401a to be weighed and unit price information. The temporary registration code 1403 is read by the mobile terminal device 50 .

The display 1402a can change the content of the temporary registration code 1403 according to time. For example, it is possible to offer discounts on time services, and to prevent fraudulent transactions using bar codes read in the past. Specifically, for example, by taking a picture of the bar code during the time service on the previous day with a camera and reading the bar code on the next day, the unit price of the product to be weighed during the time service on the previous day 1401 is registered. Note that the content displayed on the display 1402a may be printed on a print medium such as paper.

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

A provisional registration column 1412 displays products provisionally registered by reading the provisional registration code 1403 . In the drawing, the provisional registration fields 1412 (1412a, 1412b) indicate that lemon and apple are provisionally registered. That is, it indicates that the provisional registration code 1403 for apple was also read before the provisional registration code 1403 for lemon was read. The provisional registration field 1412 displays "measurement required" indicating that the weighing is necessary, and "?? yen" indicating that the price is undetermined because the weighing has not been completed.

The official registration field 1413 displays the officially registered product and the amount. The display mode of the main registration field 1413 and the display mode of the temporary registration field 1412 are different. In the illustration, the temporary registration column 1412 is displayed in a shaded display mode. By adopting such a display mode, it is possible to make it easier for the customer to recognize that the provisional registration is being performed, and to prompt the customer to weigh.

FIG. 15 is an explanatory diagram showing an example of a standby screen displayed on the weighing device 30. As shown in FIG. In FIG. 15, the display unit 306 of the weighing device 30 displays a standby screen 1500 displayed during the standby state. The standby screen 1500 includes a first guidance field 1510 and a second guidance field 1520. FIG.

A first guide column 1510 shows a guide when registering a product to be weighed using the mobile terminal device 50 . Specifically, a connection code 1511 is displayed in the first guidance field 1510, and guidance is displayed to the effect that the connection code 1511 is read by the portable terminal device 50. FIG.
The second guidance field 1520 shows guidance when registering the weighing target product without using the mobile terminal device 50 . Specifically, in the second guidance field 1520, guidance is displayed to the effect that the product to be weighed is placed on the scale and weighed. A case of using the mobile terminal device 50 will be described below.

When the customer causes the portable terminal device 50 to read the temporary registration code 1403 of lemon and apple shown in FIG. 14, the connection code 1511 shown in FIG. 15 is read. When the connection code 1511 is read, the mobile terminal device 50 requests the weighing device 30 for communication connection based on the instruction indicated by the connection code 1511 .

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

FIG. 16B shows a screen when communication connection is established. As shown in FIG. 16B, the display 409 of the mobile terminal device 50 displays a guidance display 1620 prompting the user to place the product on the scale. It should be noted that mobile terminal device 50 temporarily registers apples before lemons, and therefore displays guide display 1620 prompting the weighing of apples before the guide display prompting the weighing of lemons.

FIG. 17 is an explanatory diagram showing an example of a screen during weighing displayed on the weighing device 30 and the mobile terminal device 50. As shown in FIG. FIG. 17A shows an operation guidance screen 1700 of the weighing device 30 with no product placed on the platform 320 . The operation guidance screen 1700 includes a guidance display S1, a product name display 1701, a return button 1702, a stop button 1703, a search button 1704, a weighing result column 1705, a unit price column 1706, a total amount column 1707, and a mobile phone. and terminal information 1730 .

Guidance display S1 indicates a guidance prompting the user to place the product on the platform 320 . A product name display 1701 indicates the product name of the product to be weighed. A return button 1702 is a button for accepting a return to the previous screen. A stop button 1703 is a button for accepting the stop of weighing. The search button 1704 is a button for receiving a search for nearby mobile terminal devices 50 in order to reconnect with the mobile terminal device 50 when communication connection with the mobile terminal device 50 is cut off, for example.

A weighing result column 1705 indicates the weight of the product to be weighed placed on the platform 320 . Note that the weighing result column 1705 is not limited to displaying the weight. For example, for products for which the approximate weight per piece is known, the number of products converted based on the weight may be displayed. . A unit price column 1706 indicates the unit price (for example, the price per kilogram). A total amount column 1707 indicates the total amount calculated using the weighing result and the unit price. The portable terminal information 1730 indicates the connected portable terminal device 50 (owner). Specifically, the mobile terminal information 1730 indicates character information "connected with XX".

FIG. 17B shows a weighing completion screen 1710 of the weighing device 30 when weighing is completed. Compared with the operation guide screen 1700 of FIG. 17A, the weighing completion screen 1710 displays the display contents of the weighing result column 1705, the display contents of the total amount column 1707, the guidance display S2, and the print button 1708. different in that A weighing result column 1705 indicates the weight of the product placed on the platform 320 (eg, 1.2006 kg). The total price column 1707 indicates the price (for example, ¥432) calculated using the product weight and unit price.

Guidance display S2 shows a guidance prompting the user to press the print button 1708 . A print button 1708 is a button for receiving label issuance. The print button 1708 is displayed for the first time when the product is placed on the platform 320 and the weight value is stabilized. When the print button 1708 is pressed on the weighing completion screen 1710, the screen shown in FIG. 17C is displayed.

FIG. 17C shows a guidance screen 1720 after label issuance. Guidance screen 1720 shows a screen that prompts the user to attach a label to the bag containing the product to be weighed (apple). When issuing the label, the weighing device 30 transmits the result of weighing the apple (product identification information, the fact that the apple was weighed, the price, etc.) to the portable terminal device 50 by short-range wireless communication. The mobile terminal device 50 displays the screen shown in FIG. 17(D) when receiving the weighing result of the apple.

FIG. 17D shows a screen displayed on the mobile terminal device 50 when the main registration of apple is completed. As shown in FIG. 17(D), the mobile terminal device 50 receives the weighing result of the apple from the weighing device 30, and replaces the provisional registration field 1412b corresponding to the apple (see FIG. 14) with the apple corresponding to the apple. A main registration field 1413a is displayed.

In addition, the characters “weighing required” displayed in the temporary registration are changed to “weighing” in the main registration field 1413 . This can indicate that the weighing of apples is complete. It should be noted that, instead of the characters "measurement" in the main registration field 1413, the measured weight (for example, 0.5 kg) may be displayed, or the unit price (for example, ¥1000/kg) may be displayed. .

Note that the weighing device 30 displays the screen shown in FIG. 17(C), and after a predetermined time (for example, 3 seconds) has elapsed, the screen is changed to a screen prompting the weighing of lemons. The transition of the screens of the weighing device 30 and the mobile terminal device 50 when weighing lemons is the same transition as when weighing apples, and thus description thereof will be omitted. When the main registration of all the temporarily registered weighing target products (apples and lemons) is completed, the weighing device 30 displays the standby screen 1500 shown in FIG. 15 after a predetermined period of time (for example, 3 seconds). do.

(Example of notification processing shown in step S808 of FIG. 8 (Part 1))
FIG. 18 is a flowchart showing an example of notification processing based on position information performed by the mobile terminal device 50. As shown in FIG. As shown in FIG. 18, the mobile terminal device 50 determines whether or not the registered product is the product to be weighed (step S1801). If the registered product is the product to be weighed (step S1801: YES), it is clear that the customer is present in the store. , the process ends.

On the other hand, if the registered product is not a product to be weighed (step S1801: NO), that is, if the registered product is a barcode product, the mobile terminal device 50 sets the first condition (store location using location information). is determined (step S1802). If the transaction is not based on the fulfillment of the first condition (step S1802: NO), that is, if the transaction is based on the fulfillment of the second condition (the condition for specifying the store using the store specifying information), the mobile terminal device 50 Terminate the process as it is. As a result, it is possible to prevent the notification based on the presence determination from being performed in a transaction based on the establishment of the second condition, so that the frequency of error notification can be suppressed.

On the other hand, if the transaction is based on the establishment of the first condition (step S1802: YES), the mobile terminal device 50 (CPU 401) requests the GPS unit 411 to acquire the current location information (step S1803). Then, the mobile terminal device 50 determines whether or not the position information of the current location has been obtained (step S1804). In the position information acquisition determination, if the position information of the current location is not acquired (step S1804: NO), that is, if the communication environment is not good, such as when the mobile terminal device 50 is underground, the mobile terminal device 50 does not report an error. , the process ends. As a result, frequent notification of errors can be suppressed when the communication environment is not good.

On the other hand, in the location information acquisition determination, if 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, Existence determination is performed to determine whether the current position is outside the service area (outside the store) (step S1805). In presence determination, if the current position of the mobile terminal device 50 is not out of range (step S1805: NO), that is, if the current position of the mobile terminal device 50 is within the range (inside the store), the process is finished as it is.

On the other hand, if the current position of the mobile terminal device 50 is out of service area in presence determination (step S1805: YES), that is, the customer (member) who came to the store to check the price moves out of the store and performs the registration operation. If there is a possibility that the mobile terminal device 50 (the customer) is outside the store, an error is notified (step S1806).

Next, the mobile terminal device 50 determines whether or not to retry (step S1807). Note that retrying is performed automatically or by receiving an operation of retrying from the customer within a predetermined upper limit number of times, for example. If the upper limit number of times has been exceeded, the process proceeds to step S1808.

When retrying (step S1807: YES), the mobile terminal device 50 returns to step S1803. When not retrying (step S1807: NO), the mobile terminal device 50 restricts product registration (step S1808), and ends the series of processes. Note that restricting product registration means, for example, canceling the registered product and logging out. Further, in this case, it is possible to cancel the notification of the error by the operation of the store clerk, and furthermore, it is possible to log in again or register the product again. As a result, it is possible to enhance the effect of preventing improper product registration.

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

(Example of notification processing shown in step S808 of FIG. 8 (Part 2))
FIG. 20 is a flowchart showing an example of notification processing based on product registration operation information performed by the mobile terminal device 50 . As shown in FIG. 20, the mobile terminal device 50 (CPU 401) requests acquisition of product registration operation information stored in the memory 404 (step S2001). Then, the mobile terminal device 50 performs operation determination to determine whether or not the product registration operation information stored in the memory 404 is product registration operation information indicating that the registration operation is invalid (step S2002). If the product registration operation information does not indicate that the registration operation is illegal (step S2002: NO), the mobile terminal device 50 ends the series of processes.

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

(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 the mobile terminal device 50. As shown in FIG. As shown in FIG. 21 , an error screen 2100 is displayed on the display 409 of the mobile terminal device 50 . The error screen 2100 indicates that the registration operation is illegal and that product registration is to be canceled (that the registered product will be deleted). When the confirmation button 2101 is pressed on the error screen 2100, the registered product is deleted and the user is logged out.

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

The POS terminal device 20 waits until the cart information is received (step S2201: NO). When cart information is received (step S2201: YES), the POS terminal device 20 displays a list of cart information (registered product information and reserved product information) on the customer-side display unit 205 (step S2202). Then, the POS terminal device 20 determines whether or not the cart information includes pending product information (step S2203).

If the cart information does not include pending product information (step S2203: NO), the POS terminal device 20 proceeds to step S2210. If the cart information includes pending product information (step S2203: YES), the POS terminal device 20 performs settlement prohibition processing (step S2204). For example, the operation of the customer-side display unit 205 is invalidated by the settlement prohibition processing.

Then, the POS terminal device 20 performs clerk calling processing (step S2205). In the clerk calling process, the customer-side display unit 205 displays that the clerk is being called, the sign pole 220 is lit in a predetermined lighting mode, and the transaction status management device 11 is set to display the POS terminal device 20 for the clerk. Display to let you go to.

Next, the POS terminal device 20 determines whether or not the clerk has logged in (step S2206). In order to log in, the clerk causes the clerk-side scanner unit 212 to read the clerk code attached to the clerk's name tag, or inputs the clerk code to the clerk-side display unit 210 or the key operation unit 211, for example.

The POS terminal device 20 waits until the clerk logs in (step S2206: NO). When the store clerk logs in (step S2206: YES), the POS terminal device 20 performs processing for confirming and registering or deleting reserved products one by one (reserved product confirmation processing) (step S2207). The POS terminal device 20 performs the reserved product confirmation process until there are no reserved products left (step S2208: NO). When there are no reserved products left (step S2208: YES), the POS terminal device 20 cancels the settlement prohibition process (step S2209). Then, the POS terminal device 20 displays the settlement start screen (step S2210), and ends the series of processes.

(Example of screen transition at the time of payment displayed on the customer-side display unit 205 of the POS terminal device 20)
FIG. 23 is an explanatory diagram showing an example of screen transitions displayed on the customer-side display unit 205 of the POS terminal device 20 during checkout. FIG. 23A shows a guidance screen 2310. FIG. The guide screen 2310 is a screen prompting the customer-side scanner unit 206 to read the checkout code 1222 (see FIG. 12C). For example, the POS terminal device 20 displays the guidance screen 2310 in the standby state of the checkout mode. On the guidance screen 2310 shown in FIG. 23(A), when the customer causes the customer-side scanner unit 206 to read the checkout code 1222 displayed on the mobile terminal device 50, the list display screen 2320 shown in FIG. 23(B) or , the screen changes to the clerk calling screen 2330 shown in FIG. 23(C).

Note that the list display screen 2320 shown in FIG. 23B includes a registered product display area 2321 , a store clerk call button 2322 , and a checkout start button 2323 . Registered product display area 2321 Displays the product name, purchase points, purchase price, etc. for each registered product, as well as the total points and total price of each registered product. The registered product display area 2321 is displayed, for example, in order of registration.

The clerk call button 2322 is a button for receiving a call from a customer to a clerk. If the customer confirms the registered product display area 2321 and there is a difference between the registered product and the product that the customer wishes to purchase, it becomes necessary to correct the registered product. This correction requires the operation of the store clerk. For example, when the customer confirms the registered product display area 2321, he/she intends to register three items of "○○ meat sauce", but notices that only one item is 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 clerk calling screen 2330 shown in FIG. 23(C).

The clerk calling screen 2330 shown in FIG. 23C indicates that the clerk is being called. When the confirm button 2331 is pressed on the clerk calling screen 2330, the screen changes to a registered product list display screen (not shown). In this list display screen, since the store clerk is being called, the start of payment cannot be accepted. When a store clerk is called and logs in, the screen transitions to a reserved product confirmation screen 2340 shown in FIG. 23(D).

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

The settlement start button 2323 is a button for accepting the start of settlement processing from the customer. The customer confirms the registered product display area 2321 , and if there is no difference between the registered product and the desired product, the customer presses the checkout start button 2323 . When the settlement start button 2323 is pressed, the POS terminal device 20 can perform settlement processing. In the settlement process, the POS terminal device 20 accepts the selection of the settlement type, accepts the insertion of cash or the insertion of a card, and issues a receipt when the settlement is completed.

As described above, the mobile terminal device 50 according to the present embodiment is configured to notify an error based on the transaction start conditions. As a result, the frequency of error notification can be made different between the transaction due to the establishment of the first condition and the transaction due to the establishment of the second condition, so that the error frequency can be suppressed according to the start condition. Therefore, according to the present embodiment, it is possible to prevent the shopping from being interrupted by the notification of the error, so that the shopping can be performed smoothly.

Further, in the present embodiment, the mobile terminal device 50 notifies an error based on existence determination in a transaction when the first condition is satisfied, and does not perform an error notification based on the existence determination in a transaction when the second condition is satisfied. Therefore, it is possible to reduce the frequency of error notification in a transaction when the second condition is satisfied.

In addition, in the present embodiment, the mobile terminal device 50 does not report an error in the transaction under the first condition regardless of whether the position information is acquired in the position information acquisition determination. As a result, when the communication environment is not good, it is possible to suppress the frequent occurrence of error notifications.

Further, in this embodiment, the legitimacy determination includes an operation determination as to whether or not an operation related to product registration is performed legitimately. Thereby, an error can be notified when an illegal registration operation such as a price check is performed. Therefore, it is possible to suppress improper product registration such as price check. For this reason, it is possible to prevent various types of store information such as price information from being easily leaked.

In addition, in the present embodiment, the mobile terminal device 50 does not issue an error notification regardless of the start condition when a product to be weighed is registered. Thereby, when it is clear that the customer exists in the store, it is possible not to notify the error.

Further, in the present embodiment, when the mobile terminal device 50 cannot acquire the location information at the start of the transaction, the mobile terminal device 50 makes an acquisition request for the store identification information, and when the store identification information is acquired in response to the acquisition request, Product registration has started. As a result, even if the location information cannot be acquired, it is possible to prompt the acquisition of the store identification information and start product registration.

(Modification of embodiment)
Modifications 1 to 11 of the embodiment will be described below. In addition, in the following modified examples, the description of the contents described in the above-described embodiment will be omitted as appropriate. Also, it is possible to combine the configurations shown in the above-described embodiment and modified examples 1 to 11, respectively. Specifically, a configuration including all of the above-described embodiment and Modifications 1 to 11, or a configuration including one combination of the above-described embodiment and Modifications 1 to 11 may be

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

In Modified Example 1, the requesting unit (first requesting means) makes an acquisition request for the store identification information in response to the determination result that the location information is not acquired in the location information acquisition determination. The request unit makes an acquisition request for 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 requests acquisition of the shop identification information when, for example, the user is in the basement for a predetermined period of time or longer. Moreover, the predetermined timing is not limited to this, and may be the timing when the number of times product registration is performed reaches a predetermined number or more without acquiring the location information of the current location. The customer causes the mobile terminal device 50 to read the store identification code in response to the store identification information acquisition request from the request unit.

Also, in a store, a two-dimensional code indicating store identification information may be appropriately arranged in an area where the communication environment is not good. As a result, even when the customer is underground, the mobile terminal device 50 can read the two-dimensional code. That is, the store identification information acquisition unit can acquire the store identification information.

Here, the legitimacy determination includes store identification information acquisition determination. The store identification information acquisition determination is a determination as to whether or not the store identification information has been acquired during the transaction. When the store identification information is acquired, it is clear that the customer exists in the store identified by the store identification information. The determination unit determines that the acquisition of the store identification information is valid when the store identification information is acquired, and determines that the store identification information is not acquired even after a certain period of time has passed and is illegal. do. The reporting unit does not report an error when a valid determination result is obtained in the shop identification information acquisition determination, and reports an error when an unjustified determination result is obtained.

(Modification 1 of the notification process shown in step S808 of FIG. 8)
FIG. 24 is a flow chart showing Modified Example 1 of notification processing based on position information performed by the mobile terminal device 50 . As shown in FIG. 24, the mobile terminal device 50 determines whether or not it is a predetermined timing during which the current location information is not acquired due to being underground, for example (step S2401). The mobile terminal device 50 waits until a predetermined timing (step S2401: NO). At a predetermined timing (step S2401: YES), the mobile terminal device 50 determines whether or not the product to be weighed is registered (step S2402).

If the product to be weighed is registered (step S2402: YES), it is clear that the customer is present in the store. End the process.

On the other hand, if the product to be weighed is not registered (step S2402: NO), the mobile terminal device 50 (CPU 401) requests the GPS unit 411 to acquire the current location information (step S2403). Then, the mobile terminal device 50 determines whether or not the position information of the current location has been obtained (step S2404).

If the location information of the current location has been acquired (step S2404: YES), the mobile terminal device 50 compares the location information of the current location with the location information of the store, and determines that the current location of the mobile terminal device 50 is out of range (outside the store). Existence determination is performed as to whether or not (step S2405). In presence determination, if the current position of the mobile terminal device 50 is not out of range (step S2405: NO), that is, if the current position of the mobile terminal device 50 is within the range (inside the store), the process ends.

On the other hand, in presence determination, if the current location of the mobile terminal device 50 is out of range (step S2405: YES), that is, if it can be expected that the registration operation is performed by a customer (member) who has come to the store to check the price, etc., the mobile terminal An error is notified that the device 50 (the customer) is outside the store (step S2406). Then, the mobile terminal device 50 restricts product registration (step S2407), and ends the series of processes.

In addition, in the position information acquisition determination in step S2404, if the position information of the current location is not acquired (step S2404: NO), that is, if the communication environment is still not good, such as when the mobile terminal device 50 is underground, for example, the mobile terminal device 50 It is determined whether or not to retry (step S2408). Note that retrying is performed automatically or by receiving an operation of retrying from the customer within a predetermined upper limit number of times, for example. If the upper limit number of times has been exceeded, the process proceeds to step S2409.

When retrying (step S2408: YES), the mobile terminal device 50 returns to step S2403. When not retrying (step S2408: NO), the mobile terminal device 50 makes an acquisition request for store identification information of the store (step S2409). Then, the mobile terminal device 50 determines whether or not the shop identification information of the shop has been obtained (step S2410). If the store identification information of the store has been acquired (step S2410: YES), the mobile terminal device 50 ends the series of processes. On the other hand, if the store identification information of the store is not acquired even after a certain period of time has passed (step S2410: NO), the mobile terminal device 50 proceeds to step S2406 and notifies an error. It should be noted that the portable terminal device 50 notifies an error even when the acquired shop identification information is not the shop identification information of the relevant shop.

As described above, in Modified Example 1, the mobile terminal device 50 makes an acquisition request for shop-specific information when the position information is not acquired, and performs store-specific information acquisition determination. As a result, even when the customer is located in an area where the communication environment is not good, the customer can make it clear 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 product registration by unfair customers who conduct price checks or the like.

(Modification 2)
Next, Modification 2 of the embodiment will be described. In the first modified example described above, a configuration has been described in which notification is performed based on store identification information acquisition determination regardless of the transaction start condition. In place of or in addition to such a configuration, Modified Example 2 describes a configuration in which notification based on store identification information acquisition determination is not performed in a transaction in which the second condition is satisfied.

In Modified Example 2, the requesting unit (first requesting means) requests acquisition of store identification information when location information is not acquired, such as when the communication environment is not good, in a transaction based on the establishment of the first condition. On the other hand, the requesting unit does not request acquisition of store identification information in a transaction based on the establishment of the second condition.

(Modification 2 of the notification process shown in step S808 of FIG. 8)
FIG. 25 is a flow chart showing Modified Example 2 of notification processing based on position information performed by the mobile terminal device 50 . Note that the flowchart shown in FIG. 25 differs from the flowchart shown in FIG. 24 in step S2501. Therefore, only step S2501 will be described below.

As shown in FIG. 25, when the mobile terminal device 50 determines in step S2402 that the product to be weighed is not registered (step S2402: NO), the first condition (the store is specified using the location information). condition) is satisfied (step S2501). If the transaction is not based on the establishment of the first condition (step S2501: NO), that is, if the transaction is based on the establishment of the second condition (the condition for specifying the store using the store specifying information), the mobile terminal device 50 Terminate the process as it is. As a result, it is possible to prevent the notification based on the presence determination from being performed in a transaction based on the establishment of the second condition, so that the frequency of error notification can be suppressed.

On the other hand, if the transaction is based on 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 location information of the current location. (step S2403).

As described above, in Modified Example 2, the mobile terminal device 50 does not perform notification based on each determination of position information acquisition determination, presence determination, and shop identification information acquisition determination in a transaction based on establishment of the second condition. made it As a result, it is possible to reduce the frequency of error notification in a transaction when the second condition is satisfied.

(Modification 3)
Next, Modification 3 of the embodiment will be described. In the modification 2 described above, a configuration has been described in which notification based on store identification information acquisition determination is not performed in a transaction in which the second condition is satisfied. In place of or in addition to such a configuration, Modified Example 3 describes a configuration in which notification based on store identification information acquisition determination is not performed in a transaction when the first condition is satisfied.

In Modified Example 3, the requesting unit (second requesting means) acquires store-specific information in response to a lapse of a predetermined period of time from the start of product registration in a transaction resulting from establishment of a second condition by acquiring store-specific information. make a request. The predetermined time is, for example, 15 minutes. The requesting unit makes an acquisition request for store identification information every time a predetermined time elapses from the start of the transaction to the start of settlement. On the other hand, the requesting unit (second requesting means) does not request acquisition of the store identification information in the transaction based on the establishment of the first condition for acquiring the position information.

Moreover, in the store, the two-dimensional code indicating the store identification information may be arranged in various places. This allows the mobile terminal device 50 to read the two-dimensional code wherever the customer is in the store. That is, the store identification information acquisition unit can acquire the store identification information. The specific information determination is performed using the store specific information acquired in response to the acquisition request by the requesting unit.

Here, in a transaction based on the establishment of the first condition, the mobile terminal device 50 can periodically acquire position information and perform existence determination. Therefore, the determination unit does not perform store identification information acquisition determination in a transaction based on the establishment of the first condition. For this reason, the notification unit does not perform error notification based on the shop identification information acquisition determination in the transaction based on the establishment of the first condition.

On the other hand, in a transaction based on the establishment of the second condition, it is not possible to confirm the position periodically. Therefore, the determining unit determines whether to obtain the store identification information in the transaction based on the establishment of the second condition. Then, the notification unit notifies of an error based on the store identification information acquisition determination in the transaction due to the establishment of the second condition.

(Modification 3 of the notification process shown in step S808 of FIG. 8)
FIG. 26 is a flow chart showing Modified Example 3 of the notification process based on the shop 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 passed (step S2601). The mobile terminal device 50 waits until a predetermined time elapses (step S2601: NO). After a predetermined period of time has elapsed (step S2601: YES), the mobile terminal device 50 determines whether or not the product to be weighed is registered (step S2602).

If the product to be weighed is registered (step S2602: YES), it is clear that the customer is present in the store, and therefore the mobile terminal device 50 ends the process without performing position information acquisition determination. do.

On the other hand, if the product to be weighed is not registered (step S2602: NO), the mobile terminal device 50 determines whether or not the transaction is based on the establishment of the first condition (the condition for specifying the store using the location information). It judges (step S2603). If the transaction is based on the fulfillment of the first condition (step S2603: YES), the mobile terminal device 50 ends the process without performing position information acquisition determination.

On the other hand, if the transaction is not based on the establishment of the first condition (step S2603: NO), that is, if the transaction is based on the establishment of the second condition (the condition for specifying the store using the store specifying information), the portable terminal device 50 makes an acquisition request for store identification information of the store (step S2604). Then, the portable terminal device 50 determines whether or not the shop identification information of the shop has been obtained (step S2605). If the store identification information of the store has been acquired (step S2605: YES), the mobile terminal device 50 ends the series of processes.

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

As described above, in Modified Example 3, the mobile terminal device 50 makes an acquisition request for store identification information when a predetermined period of time elapses from the start of product registration in a transaction based on the establishment of the second condition. The shop specific information acquisition determination is performed using the shop specific information acquired in response to the acquisition request. As a result, in a transaction based on the establishment of the second condition, it is possible to make it clear that the customer is in the store by having the mobile terminal device 50 read the store identification information (two-dimensional code). Therefore, it is possible to suppress product registration by unfair customers who conduct price checks or the like.

In addition, since the mobile terminal device 50 can periodically acquire the position information and determine the existence of the transaction when the first condition is satisfied, the mobile terminal device 50 can notify an error based on the store identification information acquisition determination. you can avoid doing it. As a result, it is possible to reduce the frequency of error notification in a transaction based on the establishment of the first condition.

(Modification 4)
Next, Modification 4 of the embodiment will be described. Modification 3 described above describes a configuration in which the store identification information is not updated. In place of or in addition to such a configuration, Modified Example 4 describes a configuration that enables the use of updated store identification information and non-updated store identification information.

In Modified Example 4, the shop identification information includes updated shop identification information (hereinafter referred to as "one-time password") that is updated at a predetermined timing and non-updated shop identification information that is not updated. The one-time password is displayed on the monitor, for example. The predetermined timing is, for example, 30 minutes. The one-time password, for example, has an expiration date set, so that the store cannot be specified if the expiration date has passed. The monitor is placed near the entrance/exit of the store. The non-updated store identification information is printed on paper and displayed, for example. The one-time password and the non-updated store specific information are presented to different stores, respectively, but may be presented to the same store.

Here, reading the one-time password means that the customer is highly credible in the store. For this reason, the reporting unit does not report an error based on store identification information acquisition determination in a transaction in which the one-time password is acquired and the second condition is satisfied.

On the other hand, the non-updated shop identification information can be captured by a camera and saved, so that past information can be read outside the shop. Therefore, when the non-updated store identification information is read, it means that the customer is less credible that the customer exists in the store than when the updated store identification information is acquired. Therefore, the notification unit notifies of an error based on the store identification information acquisition determination in the transaction in which the second condition is satisfied in which the non-updated store identification information is acquired.

Further, in Modified Example 4, the requesting unit (second requesting means), in a transaction based on the establishment of the second condition by obtaining the non-updated store identification information, responds to the lapse of a predetermined time from the start of product registration. Make an acquisition request for store specific information. The store identification information to be requested for acquisition is not limited to non-updated store identification information, and may be a one-time password. That is, at a store where both the one-time password and the non-updated store identification information are presented, the request unit may request acquisition of the one-time password.

Moreover, in the store, store identification codes (two-dimensional codes) indicating non-store identification information may be placed everywhere. As a result, wherever the customer is in the store, the mobile terminal device 50 can read the store identification code. 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.

In Modified Example 4, in a transaction based on the establishment of the first condition, notification based on store identification information acquisition determination may be performed (configuration of Modified Example 2), or may not be performed (Modified Example 3).

(Modification 4 of the notification process shown in step S808 of FIG. 8)
FIG. 27 is a flow chart showing Modified Example 4 of the notification process based on the position information performed by the mobile terminal device 50 . Note that the flowchart shown in FIG. 27 differs from the flowchart shown in FIG. 26 in step S2701. Therefore, only step S2701 will be described below. As shown in FIG. 27, when the mobile terminal device 50 determines in step S2603 that the transaction is not due to the establishment of the first condition (step S2603: NO), the second condition If the transaction is based on the fulfillment of the specified condition), it is determined whether or not the transaction is based on the acquisition of the one-time password to satisfy the second condition (step S2701).

If the transaction satisfies the second condition by acquiring the one-time password (step S2701: YES), the mobile terminal device 50 ends the process. As a result, in a transaction based on the establishment of the second condition by obtaining the one-time password, it is possible to prevent the notification based on the store-specific information acquisition determination from being performed, so that the frequency of error notification can be suppressed.

On the other hand, if it is not a transaction that satisfies the second condition by obtaining a one-time password (step S2701: NO), that is, if the transaction is a transaction that satisfies the second condition by obtaining non-updated store identification information, the portable terminal device 50 , the process advances to step S2604 to request acquisition of store identification information of the store.

As described above, in Modified Example 4, the mobile terminal device 50 does not report an error based on store identification information acquisition determination in a transaction in which the one-time password is acquired and the second condition is met. Therefore, when it is expected that the customer is likely to be present at the store, an error notification based on the store identification information acquisition determination is not performed, so the frequency of errors can be suppressed.

Further, in Modified Example 4, an error is notified based on store-specific information acquisition determination in a transaction based on establishment of the second condition in which non-updated store-specific information is acquired. As a result, an error can be reported when it is expected that the customer is unlikely to be present at the store.

(Modification 5)
Next, Modification 5 of the embodiment will be described. Embodiment mentioned above demonstrated the structure which performs alerting|reporting based on operation determination irrespective of the conditions for starting a transaction. In place of or in addition to such a configuration, Modified Example 5 describes a configuration in which the notification based on the operation determination is not performed in the transaction due to the establishment of the second condition.

In Modified Example 5, the notification unit performs notification based on the operation determination in the transaction due to the establishment of the first condition. On the other hand, in the transaction based on the establishment of the second condition, the notification unit does not perform notification based on the operation determination.

(Modification 5 of the notification process shown in step S808 of FIG. 8)
FIG. 28 is a flow chart showing Modified Example 5 of notification processing based on 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.

As shown in FIG. 28, the mobile terminal device 50 determines whether or not the transaction is based on the fulfillment of the first condition (the condition for specifying the store using the location information) (step S2801). If the transaction is not based on the fulfillment of the first condition (step S2801: NO), that is, if the transaction is based on the fulfillment of the second condition (the condition for specifying the store using the store specifying information), the mobile terminal device 50 A series of processing ends without performing operation determination. On the other hand, in step S2801, if the transaction is based on the establishment of the first condition (step S2801: YES), the mobile terminal device 50 (CPU 401) proceeds to step S2001 and acquires product registration operation information stored in the memory 404. make a request.

As described above, in Modified Example 5, the mobile terminal device 50 does not report an error based on operation determination in a transaction when the second condition is satisfied. As a result, it is possible to reduce the frequency of error notification in a transaction when the second condition is met.

(Modification 6)
Next, Modification 6 of the embodiment will be described. In modification 5 described above, a configuration has been described in which notification based on operation determination is not performed in a transaction based on the establishment of the second condition. In place of or in addition to such a configuration, Modification 6 describes a configuration in which notification based on operation determination is not performed in a transaction in which the first condition is satisfied.

In Modified Example 6, the notification unit does not perform notification based on the operation determination in the transaction due to the establishment of the first condition. On the other hand, in a transaction based on the establishment of the second condition, the notification unit performs notification based on the operation determination.

(Modification 6 of the notification process shown in step S808 of FIG. 8)
FIG. 29 is a flow chart showing Modified Example 6 of notification processing based on 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 step S2901. Therefore, only step S2901 will be described below.

As shown in FIG. 29, the mobile terminal device 50 determines whether or not the transaction is based on the fulfillment of the second condition (the condition for specifying the store using the store specifying information) (step S2901). If the transaction is not based on the fulfillment of the second condition (step S2901: NO), that is, if the transaction is based on the fulfillment of the first condition (the condition for specifying the shop using the location information), the mobile terminal device 50 performs the operation End the series of processes without making a decision. On the other hand, in step S2901, if the transaction is based on the fulfillment of the first condition (step S2901: YES), the mobile terminal device 50 (CPU 401) proceeds to step S2001 and acquires product registration operation information stored in the memory 404. make a request.

As described above, in Modified Example 6, the mobile terminal device 50 does not report an error based on operation determination in a transaction when the first condition is satisfied. As a result, it is possible to reduce the frequency of error notification in a transaction based on the establishment of the first condition.

(Modification 7)
Next, Modification 7 of the embodiment will be described. In the sixth modified example described above, a configuration has been described in which notification is given based on operation determination in a transaction based on the establishment of the second condition. In place of or in addition to such a configuration, Modified Example 7 will explain a configuration in which notification based on operation determination is not performed in transactions due to acquisition of a one-time password even in transactions due to the establishment of the second condition.

If the one-time password is acquired, there is a low possibility that unfair product registration such as price check will be performed outside the store. Therefore, in Modified Example 7, the reporting unit does not report an error based on the operation determination in the transaction based on the establishment of the second condition in which the one-time password is acquired.

On the other hand, in the case of the non-updated store identification information, it is possible to read the past information outside the store by capturing the image with a camera and storing it. Therefore, when the non-updated store identification information is acquired, there is a high possibility that unfair product registration such as price check is performed outside the store compared to the case where the one-time password is acquired. For this reason, the reporting unit is configured to report an error based on the operation determination in a transaction based on the establishment of the second condition in which the non-updated store identification information is acquired.

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

(Modification 7 of the notification process shown in step S808 of FIG. 8)
FIG. 30 is a flow chart showing Modified Example 7 of notification processing based on product registration operation information performed by the mobile terminal device 50 . Note that the flowchart shown in FIG. 30 differs from the flowchart shown in FIG. 29 in step S3001. Therefore, only step S3001 will be described below.

As shown in FIG. 30, when the mobile terminal device 50 determines in step S2901 that the transaction is based on the establishment of the second condition (step S2901: YES), it is determined whether the transaction is based on acquisition of the one-time password. It is determined whether or not (step S3001).

If 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. As a result, in a transaction based on the establishment of the second condition by acquiring the one-time password, notification based on the operation determination can be avoided, so the frequency of error notification can be suppressed.

On the other hand, if it is not a transaction that satisfies the second condition by obtaining a one-time password (step S3001: NO), that is, if it is a transaction that satisfies the second condition by obtaining non-updated store identification information, the portable terminal device 50 The (CPU 401 ) proceeds to step S<b>2001 and requests acquisition of product registration operation information stored in the memory 404 .

As described above, in Modified Example 7, the mobile terminal device 50 does not report an error based on operation determination in a transaction in which the one-time password is acquired and the second condition is met. Therefore, when it is expected that there is a low possibility of illegal product registration such as price check outside the store, error notification is not performed, so that the frequency of errors can be suppressed.

Further, in Modified Example 7, an error notification based on operation determination is performed in a transaction based on the establishment of the second condition in which the non-updated store identification information is acquired. As a result, an error can be notified when it is highly likely that an unfair commodity registration such as a price check will be performed outside the store, so that unfair commodity registration such as a price check can be suppressed.

(Modification 8)
Next, Modification 8 of the embodiment will be described. In the embodiment described above, an error is not reported when position information cannot be obtained (see FIG. 18). In place of or in addition to such a configuration, Modification 8 will describe a configuration for reporting an error when the GPS function is turned off.

Description will be made below with reference to FIG. In Modified Example 8, in step S1804 of FIG. 18, if the position information cannot be acquired, the mobile terminal device 50 determines whether the GPS function is OFF. When the GPS function is ON, the process is terminated as it is without performing existence determination. On the other hand, when the GPS function is OFF, notification is made to the effect that the GPS function is to be turned ON. Also, the mobile terminal device 50 may not end the processing shown in FIG. 18 until the GPS function is turned on. Further, if the GPS function is not turned on after a certain period of time has passed, an error indicating that the mobile terminal device 50 (the customer) is outside the store may be reported, or product registration may be restricted.

According to Modified Example 8, it is possible to prevent a customer from intentionally turning off the GPS function and performing improper product registration such as price check.

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

Specifically, in the notification processing based on the position information (see FIG. 18) according to Modification 9, position information acquisition determination and existence determination are performed regardless of whether or not the product to be weighed is registered. Specifically, the mobile terminal device 50 should not perform the processing of step S1801 in FIG. Accordingly, even when a product to be weighed is registered, position information acquisition determination, existence determination, and store identification information acquisition determination can be performed. Therefore, it is possible to notify an error according to the determination result of each determination.

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

Specifically, in Modification 10, the mobile terminal device 50 determines whether or not the product to be weighed is registered before the process of step S2001 in FIG. If so, the process should be terminated as it is. As a result, when the product to be weighed is registered, there is a low possibility of improper product registration, so it is possible not to issue an error notification based on the operation determination. Therefore, the frequency of errors can be suppressed.

(Modification 11)
Next, Modified Example 11 of the embodiment will be described. In the above-described embodiment, it is assumed that an error based on a correctness determination is not notified when a product to be weighed is registered. In place of or in addition to such a configuration, in the eleventh modification, an error based on a correctness determination is not notified simply because the connection history with the weighing device 30 is not registered even if the product to be weighed is not registered. There may be cases.

In this way, if there is a connection history with the weighing device 30, it is clear that the product to be weighed exists in the store even if it is not registered. Therefore, it is possible not to report an error based on the correctness determination. Even if it does in this way, the frequency of an error can be suppressed.

A summary of the embodiments will be described below.
[Title of Invention] Terminal Device, Merchandise Sales Data Processing System, Notification Method, and Program [Technical Field]
The present invention relates to a terminal device, a merchandise sales data processing system, a notification method, and a program.
[Background technology]
2. Description of the Related Art In recent years, there is known a system in which a shopping application is installed in a mobile terminal device such as a smartphone owned by a customer, and the customer registers products at a store by the customer's own operation (see, for example, Patent Document 1). The mobile terminal periodically confirms the location of its own device, and notifies an error when the own device is not located within the store.
[Prior art documents]
[Patent Literature]
[Patent Document 1] Japanese Patent Publication No. 2013-541107 [Summary of the Invention]
[Problems to be solved by the invention]
However, in the prior art, there is a problem that if errors are frequently reported, the customer may not be able to carry out the shopping smoothly. For example, in an environment where it is difficult to acquire location information, such as when a store is located underground, the mobile terminal device may judge that it is not located inside the store and frequently report an error. rice field. SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technology that enables smooth shopping.
[Means to solve the problem]

(1) In order to solve the above-described problems, a terminal device according to one aspect of the present invention includes position information acquiring means for acquiring position information indicating the current location, and store specifying means for acquiring store specifying information presented at the store. satisfaction of any one of a first condition for specifying the store using the information acquiring means and the location information and a second condition for specifying the store using the store specifying information; registration means for starting product registration in response to the above; judging means for judging whether or not the product registration is valid; and wherein the notification means performs the notification based on the established start condition.
According to the above configuration, it is possible to change the frequency of occurrence of error notification between a transaction when the first condition is satisfied and a transaction when the second condition is satisfied, so that the error frequency can be suppressed according to the start condition. can be done. Therefore, according to the present embodiment, it is possible to prevent the shopping from being interrupted by the notification of the error, so that the shopping can be performed smoothly.

(2) In the configuration of (1) above, the legitimacy determination includes presence determination as to whether or not the store exists using the location information acquired during the transaction, and the reporting means The notification based on the presence determination may be performed in the transaction when the first condition is satisfied, and the notification based on the presence determination may not be performed in the transaction when the second condition is satisfied.
According to the above configuration, it is possible not to perform the notification based on the presence determination in the transaction due to the establishment of the second condition. Therefore, it is possible to reduce the frequency of error notification in a transaction when the second condition is satisfied.

(3) In the configuration of (1) or (2) above, the legitimacy determination includes location information acquisition determination as to whether or not the location information was acquired during the transaction, and the reporting means Even if the determination result of the position information acquisition determination that is not acquired is obtained, the notification may not be performed.
According to the above configuration, it is possible to prevent frequent occurrence of error notifications when the communication environment is not good.

(4) In the configuration of (3) above, there may be provided a first requesting means for requesting acquisition of the store identification information in response to a determination result that the location information is not acquired in the location information acquisition determination. good.
According to the above configuration, even if the customer is located in an area where the communication environment is not good, the customer can make it clear that he or she is in the store by having the mobile terminal device 50 read the store identification information (two-dimensional code). can be done. Therefore, it is possible to suppress product registration by unfair customers who conduct price checks or the like.

(5) In any one of the above configurations (1) to (4), the legitimacy determination may include an operation determination as to whether or not the operation related to the product registration is performed legitimately.
According to the above configuration, an error can be notified when an illegal registration operation such as a price check is performed. Therefore, it is possible to suppress improper product registration such as price check. For this reason, it is possible to prevent various types of store information such as price information from being easily leaked.

(6) In any one of the configurations (1) to (5) above, the legitimacy determination includes store-specific information acquisition determination as to whether or not the store-specific information has been acquired during the transaction, and the reporting means , the notification based on the store identification information acquisition determination is not performed in the transaction when the first condition is satisfied, and the notification based on the store identification information acquisition determination is performed in the transaction when the second condition is satisfied. good too.
According to the above configuration, it is possible to clarify that the customer is in the store by causing the mobile terminal device 50 to read the store identification information (two-dimensional code) in a transaction based on the establishment of the second condition. Therefore, it is possible to suppress product registration by unfair customers who conduct price checks or the like. In addition, in a transaction based on the establishment of the first condition, it is possible to periodically acquire location information and determine the existence of a store. can be done. As a result, it is possible to reduce the frequency of error notification in a transaction based on the establishment of the first condition.

(7) In the configuration of (6) above, second requesting means for requesting acquisition of the store identification information when a predetermined period of time has elapsed from the start of the product registration in the transaction based on the establishment of the second condition. may be provided.
According to the above configuration, in a transaction based on the establishment of the second condition, the mobile terminal device 50 is made to read the store identification information (two-dimensional code) every time a predetermined time elapses, thereby making it clear that the user is in the store. be able to. Therefore, it is possible to suppress product registration by unfair customers who conduct price checks or the like.

(8) In any one of the configurations (1) to (7) above, the shop identification information includes updated shop identification information updated at a predetermined timing and non-updated shop identification information that is not updated, and the notification The means does not perform the notification based on the legitimacy determination in the transaction due to the establishment of the second condition in which the updated store identification information is acquired, and the transaction is based on the establishment of the second condition in which the non-updated store identification information is acquired. In the transaction, the notification may be made based on the legitimacy determination.
According to the above configuration, in the case of a transaction based on the acquisition of updated store identification information, it is highly likely that the customer will be present at the store. be able to. In addition, in the case of transactions based on the acquisition of non-updated store identification information, it is unlikely that the customer will be present at the store. be able to.

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

(10) In any one of the configurations (1) to (9) above, a third request means for requesting acquisition of the store identification information when the first condition is not satisfied, wherein the registration means 3. The product registration may be started when the second condition is satisfied by acquiring the store identification information in response to an acquisition request by the requesting means.
According to the above configuration, even if the location information cannot be acquired, it is possible to prompt the acquisition of the shop identification information and start product registration.

(11) In order to solve the above-described problems, a merchandise sales data processing system according to another aspect of the present invention is a merchandise sales data processing system including a terminal device operated by a customer, which stores position information indicating the current location. position information acquisition means for acquiring; store specification information acquisition means for acquiring store specification information presented at the store; a first condition for specifying the store using the position information; registering means for starting product registration in response to establishment of either one of a second condition specifying the store and a validity determination as to whether or not the product registration is validly 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 data processing system.
According to the above configuration, it is possible to change the frequency of occurrence of error notification between a transaction when the first condition is satisfied and a transaction when the second condition is satisfied, so that the error frequency can be suppressed according to the start condition. can be done. Therefore, according to the present embodiment, it is possible to prevent the shopping from being interrupted by the notification of the error, so that the shopping can be performed smoothly.

(12) In order to solve the above-described problems, a notification method according to another aspect of the present invention includes a position information acquisition step in which a computer used in a terminal device acquires position information indicating the current location; a first condition for specifying the store using the location information; and a second condition for specifying the store using the store specifying information. a registration step for starting product registration in response to the establishment of any one of the start conditions; a determination step for determining whether or not the product registration is properly performed; and a notification step of notifying an error using the error, and in the notification step, the notification is performed based on the established start condition.
According to the above configuration, it is possible to change the frequency of occurrence of error notification between a transaction when the first condition is satisfied and a transaction when the second condition is satisfied, so that the error frequency can be suppressed according to the start condition. can be done. Therefore, according to the present embodiment, it is possible to prevent the shopping from being interrupted by the notification of the error, so that the shopping can be performed smoothly.

(13) In order to solve the above-described problems, a program, which is another aspect of the present invention, comprises a computer used in a terminal device, position information acquisition means for acquiring position information indicating the current location, a store presented at the store any one of a store specifying information acquiring means for acquiring specifying information, a first condition for specifying the store using the position information, and a second condition for specifying the store using the store specifying information. Registration means for starting product registration in response to establishment of one of the start conditions, determination means for determining whether or not the product registration is valid, and notification of an error using the determination result of the determination means. and the notification means performs the notification based on the established start condition.
According to the above configuration, it is possible to change the frequency of occurrence of error notification between a transaction when the first condition is satisfied and a transaction when the second condition is satisfied, so that the error frequency can be suppressed according to the start condition. can be done. Therefore, according to the present embodiment, it is possible to prevent the shopping from being interrupted by the notification of the error, so that the shopping can be performed smoothly.

Note that all or part of each function (input/output, storage, processing (including judgment)) in each device (portable terminal device 50, etc.) described above is different from the device described as an execution subject of the function. may be implemented in the apparatus of

Specifically, in the above description, the mobile terminal device 50 is configured to include the location information acquisition unit, the shop identification information acquisition unit, the registration unit, the determination unit, the notification unit, and the request unit. . All or part of these functional units may be provided in another computer device. 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 a computer device other than these. good too. Further, the number of computer devices provided with these functional units is not limited to a plurality, and may be one. For example, one computer device may have all of these functional units.

Specifically, for example, instead of the mobile terminal device 50, the transaction status management device 11 or the cloud server Sv may store the information (registration data) after product registration. Further, 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). good. That is, for example, in step S1802 of the flowchart of FIG. 18, the process of determining the conditions for starting a transaction described as being executed by the mobile terminal device 50 and the process of informing an error performed in step S1806 are performed by the transaction status management apparatus. 11 or cloud server Sv.

In relation to the above, the mobile terminal device 50 may function as a so-called thin client that specializes in an input/output interface for product registration. That is, the mobile terminal device 50 receives various inputs (operator's operation, detection by a device such as a scanner), transmits input information (operation information, scan information, etc.) to the cloud server Sv, and based on the input information, The processing results of the cloud server Sv (update screen information, device control information, etc.) may be received and various outputs (display on the display unit, device control) may be performed.

A program for realizing the shopping system 1 and the portable terminal device 50 described above may be recorded in a computer-readable recording medium, and the program may be read and executed by a computer system. It should be noted that the “computer system” here includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. In addition, "computer-readable recording medium" means a volatile memory (RAM) inside a computer system that acts as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. , includes those that hold the program for a certain period of time. Further, the above program may be transmitted from a computer system storing this program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in a 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. Further, the program may be for realizing part of the functions described above. Further, it may be a so-called difference file (difference program) that can realize the above-described functions in combination with a program already recorded in the computer system.

Sv... Cloud server, 1... Shopping system, 10... Store controller, 11... Transaction situation management device, 20... POS terminal device, 30... Weighing device, 50... Portable 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 (13)

a location information acquiring means for acquiring location information indicating the current location;
store-specific information acquiring means for acquiring store-specific information presented at the store;
In response to satisfaction of either a first condition for specifying the store using the location information or a second condition for specifying the store using the store specifying information, registration means for initiating registration;
a judgment means for judging whether or not the product registration is properly performed;
a notification means for notifying an error using the determination result of the determination means;
with
The notification means performs the notification based on the established start condition,
A terminal device characterized by: The legitimacy determination includes presence determination of whether or not the store exists using the location information acquired during the transaction,
The notification means is
In the transaction due to the establishment of the first condition, the notification based on the existence determination is performed,
Not performing the notification based on the presence determination in the transaction due to the establishment of the second condition,
The terminal device according to claim 1, characterized by: The legitimacy determination includes location information acquisition determination as to whether or not the location information has been acquired during the transaction,
The notification means does not perform the notification even if a determination result of the position information acquisition determination that the position information is not acquired is obtained.
3. The terminal device according to claim 1 or 2, characterized by: A first request means for requesting acquisition of the shop identification information in response to obtaining a determination result that the location information is not acquired in the location information acquisition determination,
4. The terminal device according to claim 3, characterized by: The legitimacy determination includes an operation determination as to whether or not the operation related to the product registration is performed legitimately.
The terminal device according to any one of claims 1 to 4, characterized in that: The legitimacy determination includes store-specific information acquisition determination as to whether or not the store-specific information has been acquired during the transaction,
The notification means is
In the transaction due to the establishment of the first condition, without performing the notification based on the store identification information acquisition determination,
In the transaction due to the establishment of the second condition, performing the notification based on the store identification information acquisition determination,
The terminal device according to any one of claims 1 to 5, characterized in that: a second request means for requesting acquisition of the store identification information in response to a lapse of a predetermined time from the start of the product registration in the transaction based on the establishment of the second condition;
7. The terminal device according to claim 6, characterized by: The store identification information includes updated store identification information that is updated at a predetermined timing and non-updated store identification information that is not updated,
The notification means is
not performing the notification based on the legitimacy determination in the transaction based on the establishment of the second condition in which the updated store identification information is acquired;
Performing the notification based on the legitimacy determination in the transaction due to the establishment of the second condition in which the non-updated store identification information is acquired;
The terminal device according to any one of claims 1 to 7, characterized in that: The registration means is capable of registering the product to be weighed by communicating with a weighing device that weighs the product to be weighed,
wherein the notification means does not perform the notification regardless of the start condition when the product to be weighed is registered;
9. The terminal device according to any one of claims 1 to 8, characterized by: comprising a third request means for requesting acquisition of the shop identification information when the first condition is not satisfied;
The registration means starts the product registration when the second condition is satisfied by acquiring the store identification information in response to the acquisition request by the third request means.
The terminal device according to any one of claims 1 to 9, characterized by: A product sales data processing system including a terminal device operated by a customer,
a location information acquiring means for acquiring location information indicating the current location;
store-specific information acquisition means for acquiring store-specific information presented at the store;
In response to satisfaction of either a first condition for specifying the store using the location information or a second condition for specifying the store using the store specifying information, registration means for initiating registration;
a judgment means for judging whether or not the product registration is properly performed;
a notification means for notifying an error using the determination result of the determination means;
with
The notification means performs the notification based on the established start condition,
A merchandise sales data processing system characterized by: The computer used for the terminal device
a location information acquisition step of acquiring location information indicating the current location;
a store-specific information acquisition step for acquiring store-specific information presented at the store;
In response to satisfaction of either a first condition for specifying the store using the location information or a second condition for specifying the store using the store specifying information, a registration step for initiating registration;
a judging step of judging whether or not the product registration is properly performed;
A notification step of notifying an error using the determination result in the determination step;
and run
In the notification step, the notification is performed based on the established start condition;
A notification method characterized by: The computer used for the terminal device,
location information acquisition means for acquiring location information indicating the current location;
store-specific information acquiring means for acquiring store-specific information presented at the store;
In response to satisfaction of either a first condition for specifying the store using the location information or a second condition for specifying the store using the store specifying information, registration means for initiating registration;
Determination means for determining whether or not the product registration is properly performed;
Reporting means for reporting an error using the determination result of the determination means;
function as
The notification means performs the notification based on the established start condition,
A program characterized by

Images