JP7650491B2 - CHECKOUT SYSTEM, PORTABLE TERMINAL DEVICE, AND CHECKOUT METHOD - Google Patents

Description

The present invention relates to a checkout system, a portable terminal device, and a checkout method .

In recent years, so-called self-checkout systems, in which customers register products and then make payments, have become widespread. For example, a self-checkout system is known in which customers register products using a mobile terminal device they carry and then make payments at a payment device (see, for example, Patent Document 1).

To give a specific example, in a self-checkout system, when a customer reads a barcode attached to an item with a mobile terminal device, the information of the read barcode is sent from the mobile terminal device to a cloud server. The cloud server registers the item using the information received from the mobile terminal device. Then, once registration of the item to be purchased is complete, the customer displays a settlement code on the mobile terminal device and has the settlement device read it. After reading the settlement code, the settlement device requests the cloud server to send transaction information to be used for settlement, receives the transaction information from the cloud server, and performs settlement by the customer.

JP 2016-219034 A

However, with conventional technology, customers who are members must, for example, have the settlement device read a settlement code or a membership code printed on a membership card when making a payment, which can require time-consuming operations related to reading various codes. As a result, conventional technology has the problem that the procedures for making a payment can be complicated.

The present invention was made in light of these circumstances, and its purpose is to provide technology that can simplify the procedures at the time of settlement.

In order to solve the above-mentioned problems, a checkout system according to one aspect of the present invention is a checkout system including a portable terminal device that registers products to be purchased by a customer through operation, and a settlement device that settles the payment using transaction information generated by the registration of the products by the portable terminal device, the transaction information being associated with storage medium identification information that identifies a storage medium possessed by the customer, and the settlement device including a reading means that reads the storage medium identification information stored in the storage medium, an acquisition means that acquires the transaction information associated with the storage medium identification information read by the reading means, and a settlement means that executes a settlement process using the transaction information acquired by the acquisition means.

1 is an explanatory diagram showing a network configuration of a shopping system 1 according to an embodiment. FIG. 2 is an explanatory diagram showing an example of installation of a 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 30. 10 is an explanatory diagram showing an example of various information for each mobile terminal device 30 managed by the cloud server Sv. FIG. 4 is a sequence diagram showing the flow of processing related to product registration and settlement in the shopping system 1. [0023] FIG. 10 is a flowchart showing an example of a registration completion process performed by the mobile terminal device 30. 11 is an explanatory diagram showing an example of a screen displayed on a display 409 of a mobile terminal device 30. FIG. 13 is a flowchart showing an example of a cart information identification process performed by the cloud server Sv. 10 is a flowchart showing an example of a settlement process performed by the POS terminal device 20. 11A to 11C are explanatory diagrams showing an example of the transition of screens displayed on the POS terminal device 20 when a settlement code is read. 11A to 11C are explanatory diagrams showing an example of the transition of screens displayed on the POS terminal device 20 when a membership code is read. 13 is an explanatory diagram showing a modified example of a screen displayed on the display 409 of the mobile terminal device 30. FIG.

(Embodiment)
(Network Configuration of Shopping System 1)
1 is an explanatory diagram showing a network configuration of a shopping system 1 according to an embodiment. The shopping system 1 is an example of a checkout system. The shopping system 1 can be introduced in various stores, such as supermarkets, home improvement stores, convenience stores, and various supply stores. In this specification, the terms "customer" and "client" are synonymous unless otherwise specified.

In FIG. 1, the shopping system 1 includes a cloud server Sv, a store controller (store computer, management device) 10, a transaction management device 11, a POS (Point Of Sales) terminal device 20, and a mobile terminal device 30. The POS terminal device 20 is an example of a settlement device. The mobile terminal device 30 is an example of a portable terminal device.

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

The cloud server Sv is a server device that manages various information such as information about customers, information about stores, information about products for each store (product master), and customer membership information. For example, the cloud server Sv generates cart information that indicates a virtual cart for each customer based on product information read by the mobile terminal device 30, and registers the products. The information that the cloud server Sv manages (generates and stores) will be described later with reference to FIG. 5.

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

The transaction management device 11 monitors the POS terminal device 20 and a weighing device (not shown). Specifically, the transaction 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 shopping system 1 may also include a terminal device carried by a store clerk. The terminal device carried by the store clerk may, for example, display the same content as that displayed on the transaction management device 11 or notify the store clerk to be called.

The POS terminal device 20 is a computer device capable of executing a settlement process to settle (pay) for products registered by the mobile terminal device 30. In addition to settling for products registered by the mobile terminal device 30, the POS terminal device 20 can also settle for products registered by its own terminal or by another POS terminal device 20. In other words, in addition to settlement processing, the POS terminal device 20 can also execute a registration process to register products to be purchased (hereinafter sometimes referred to as "product registration"). Note that although multiple POS terminal devices 20 are shown in FIG. 1, there may be only one.

The mobile terminal device 30 is a portable computer device such as a smartphone, tablet device, or mobile phone. The mobile terminal device 30 is equipped with a communication unit, an imaging unit (camera), a touch panel, and the like, and is operated by a customer. In this embodiment, the mobile terminal device 30 is detachably attached to the shopping cart. However, the mobile terminal device 30 may also be installed in a non-detachable manner in the shopping cart. The mobile terminal device 30 may also be owned by the customer, or may be loaned to the customer by the store.

The mobile terminal device 30 scans (reads) the barcode (product code) attached to the product in response to a customer's operation and accepts the registration of the product. In other words, the mobile terminal device 30 has a recognition function that recognizes the barcode attached to the product.

In addition, application software (hereinafter referred to as the "shopping app") for registering products related to the shopping system 1 and for settling the registered products is installed on the mobile terminal device 30. By starting the shopping app, the mobile terminal device 30 reads the barcode attached to the product and transmits the read information to the cloud server Sv. As a result, the product corresponding to the barcode is registered in the cart information (virtual cart) of the cloud server Sv.

When making a payment, the mobile terminal device 30 also displays coded cart identification information for identifying the cart information assigned to the mobile terminal device 30. This code is, for example, a two-dimensional code (QR code (registered trademark)). The customer has the POS terminal device 20 read the two-dimensional code (hereinafter referred to as the "payment code"). When the POS terminal device 20 reads the payment code, it requests the cloud server Sv to send transaction information for the registered items. In response to the request, the POS terminal device 20 then receives the transaction information from the cloud server Sv, and is then able to make the payment. In the following, registered items may be referred to as "registered items".

In this embodiment, the device that performs the settlement is a POS terminal device 20 that can register products depending on the operating mode, but this is not limited to this. For example, the device that performs the settlement may be a device dedicated to settlement that is installed in the store. Also, the device that performs the settlement may be a computer device for settlement that is installed in an undetachable manner on the shopping cart. This computer device may be one that is only capable of card settlement using, for example, a credit card or a prepaid card.

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

The POS terminal device 20 also includes a sign pole 220. The sign pole 220 includes a light-emitting unit. The light-emitting unit of the sign pole 220 is, for example, a lamp or an LED (light emitting diode), and can be lit in a predetermined color or in a predetermined lighting pattern. Depending on the lighting pattern of the sign pole 220, it indicates that the POS terminal device 20 is in use or issues a warning. The sign pole 220 is provided facing upwards, so that even store staff who are not near the POS terminal device 20 can recognize the lighting pattern.

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

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

The CPU 201 is a central processing unit that reads and executes various programs stored in the ROM 202 to control the operation of the POS terminal 20. The various programs include a checkout program according to this embodiment.
The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs.

RAM 203 is a readable and writable memory that stores various information. For example, RAM 203 stores information acquired from the outside (e.g., transaction information (registration information) acquired from cloud server Sv, product master data acquired from store controller 10, etc.) and information generated during processing. This information also includes settlement information generated during the settlement process for settling (paying) registered products (purchased products).

The hard disk 204 stores various information. For example, the hard disk 204 stores the image captured by the camera 216 (e.g., video). The hard disk 204 may store various programs, such as a check-out program executed by the CPU 201, instead of the ROM 202. The hard disk 204 may also store information acquired from the outside and information generated during processing, instead of the RAM 203.

The customer display unit 205 is a touch display for customers. The customer display unit 205 displays various information to customers and receives various inputs from customers.
The customer-side scanner unit 206 is a scanner unit for customers, and optically reads various codes. Examples of the various codes include a payment code displayed on the mobile terminal device 30, a barcode (product code, etc.) attached to a product, and a code (barcode, two-dimensional code, etc.) printed on a bill (registered trademark). The various codes also include gift certificates (gift certificates, coupons, and complimentary coupons) and codes (barcodes, two-dimensional codes, etc.) printed on various cards (for example, membership cards, point cards, etc.).

Note that product registration is not limited to registration by reading the barcode attached to the product. For example, a preset key (a button for ordering the product) corresponding to the product may be displayed on the customer side display unit 205, and the product may be registered by operating (pressing) the preset key.

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

The card payment unit 208 in this embodiment includes a card recognition unit, a display unit, and an operation unit, but is not limited to these and may include at least a card recognition unit. The card recognition unit in this embodiment may be compatible with contact cards (IC cards, magnetic cards) or non-contact cards (IC cards).

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

The clerk-side display unit 210 is a touch display for the clerk. The clerk-side display unit 210 displays various information to the clerk and accepts various inputs from the clerk. For example, the clerk-side display unit 210 displays preset keys (buttons for ordering products) corresponding to products. Products are registered when the clerk operates (presses) the preset keys.

The key operation unit 211 is made up of various keys (hardware keys, buttons). The key operation unit 211 accepts various inputs from the store clerk. Specifically, the key operation unit 211 includes a key that corresponds to a product (e.g., XX newspaper). When the store clerk operates (presses) the key, the product is registered. The key operation unit 211 includes a button that switches between operation modes. Here, we will provide some additional information about the operation modes.

The POS terminal device 20 operates in one of a number of operating modes. The multiple operating modes include, for example, a normal mode, a checkout-only mode, and a full self-service mode. This operating mode enables product registration by the store clerk (hereinafter sometimes referred to as "product registration") and disables product registration by the customer. In the normal mode, payment (face-to-face payment) is possible, including the customer inserting currency (banknotes and coins) and reading various cards.

In normal mode, it is also possible to send registration information to other POS terminal devices 20. Sending registration information to other POS terminal devices 20 means sending the registration information generated in the registration process to other POS terminal devices 20 that can execute settlement processes (POS terminal devices 20 in accounting-only mode), and it is also possible to issue a receipt. Issuing a receipt means coding the registration information generated in the registration process and printing and outputting it on a print medium (sheet).

The accounting-only mode is an operating mode in which the terminal can receive registration information from other POS terminal devices 20 or read various codes (payment codes or codes on bills) to obtain and settle payments. The accounting-only mode is an operating mode in which the terminal does not perform registration processing on its own, but instead performs settlement processing using registration information generated by other POS terminal devices 20.

The full self-service mode is an operating mode in which the customer registers products and settles the bill themselves. As with the billing-only mode, the full self-service mode may obtain registration information by receiving information from another POS terminal device 20 or by reading various codes (payment codes or codes on bills).

The store clerk scanner unit 212 is a scanner unit for store clerks, and optically reads various information. For example, the store clerk scanner unit 212 optically reads various codes. The various codes include barcodes attached to products and store clerk codes attached to store clerk nametags. In addition to the above, the various codes also include codes printed on bills, gift certificates, and various cards.

The printing unit 213 issues various media (receipts, bills, etc.). The printing unit 213 can change the direction of the media issuing port. Specifically, the printing unit 213 has a rotatable mechanism, and is configured so that the media issuing port faces from the store clerk side to the customer side, and from the customer side to the store clerk side. The orientation of the media issuing port may be changeable manually, or may be changeable automatically when the operating mode is switched. The printing unit 213 may be equipped with a sensor that detects whether the orientation of the printing issuing port is correct.

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

The camera 216 is attached to the upper right of the customer display unit 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 for the camera 216. The camera 216 captures the operation status of the customer at the time of payment. Specifically, the camera 216 captures the bills and coins held by the customer, the change machine 209, hand movements, etc. The camera 216 also captures the operation status of the customer at the time of registering the product. Specifically, the camera 216 can capture the inside (products) of the shopping basket on the counter provided on both sides of the POS terminal device 20, and the operation status of the customer at the time of registration.

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

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

The memory 404 stores various data. For example, a flash memory is used as the memory. The memory 404 stores various programs such as a shopping application and a checkout program, and various data such as map data and store information.
The communication unit 405 is connected to a network, and is connected to other devices (for example, a cloud server Sv) via the network. Examples of communication networks that function as networks include the Internet and mobile phone networks.

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

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

(Example of information managed by cloud server Sv)
Next, an example of information managed by the cloud server Sv will be described with reference to FIG.
5 is an explanatory diagram showing an example of various information managed by the cloud server Sv for each mobile terminal device 30. The cloud server Sv stores various information including (A) customer information, (B) member information, (C) store information, and (D) cart information. Note that instead of or in addition to storing the various information in a storage unit within the cloud server Sv, the cloud server Sv may store some or all of the various information in another device, such as a file server, accessible by the cloud server Sv.

(Customer Information)
Fig. 5(A) shows an example of customer information. The customer information is information for managing individual customers. The customer information is information managed for each store or each affiliated store. As shown in Fig. 5(A), the customer information includes customer identification information, a customer name, and a customer registration date.

The customer identification information is identification information that uniquely identifies a customer. The customer identification information is generated when the app is downloaded to the mobile terminal device 30 from the cloud server Sv or a predetermined server that provides general applications. For example, the customer identification information may be application identification information (hereinafter referred to as "app identification information") that is uniquely assigned to each installed shopping app when a shopping app is installed on the mobile terminal device 30. The app identification information may be, for example, a sequential number. Alternatively, the app identification information may be terminal identification information uniquely assigned to the mobile terminal device 30 in which the shopping app is installed. This terminal identification information may be, for example, a telephone number assigned to the customer who is the user of the mobile terminal device 30, or hardware identification information uniquely assigned to the hardware of the mobile terminal device 30, such as a MAC (Media Access Control) address.

The customer name is the customer's name, nickname, etc. The customer name is generated based on information entered in the name field of the registration form (input form) of the mobile terminal device 30 when registering a new customer, for example.
The customer registration date is the date and time when customer information is newly registered in the cloud server Sv. The customer registration date is generated based on the current date and time when a customer is newly registered.

(Member information)
FIG. 5(B) shows an example of member information. Member information is information for managing individual customers. Member information is information managed for each store or each affiliated store. As shown in FIG. 5(B), customer information includes customer identification information, member number, customer name, membership registration date, customer rank, number of points, payment type, and number of points used.

The customer identification information is the same as the customer identification information included in the customer information in FIG. 5 (A). It is used to associate the member information with the customer information. It is sufficient that the member information and customer information include information that can be used to associate the two, and they may not include customer identification information but may include information such as name and date of birth.

The member number is member identification information that uniquely identifies a member. The member number is an example of storage medium identification information.
The customer name is the same information as the customer name included in the customer information in FIG.
The membership registration date is the date and time when a new member is registered.
The customer rank indicates a rank according to the customer's purchasing history.
The number of points is the number of points given to a customer when he or she makes a purchase by presenting a membership card.
The payment type indicates a preset payment type. The payment type can be changed as appropriate by the customer. The number of points to be used indicates the number of points to be used for shopping and whether or not the points can be used.

(Store information)
Fig. 5(C) shows an example of store information. The store information is information for managing each store. As shown in Fig. 5(C), the store information includes store identification information, store name, store identification information 1 (information of a two-dimensional code), and store identification information 2 (location information).
The store identification information includes a store (trade name) or company code and a branch code.
The store name is the name of the store, and is composed of, for example, the store name (trade name) or company name and the branch name.

Store identification information 1 and 2 are information for identifying the store in which a transaction takes place (the store where goods are bought and sold). Store identification information 1 is, for example, two-dimensional code information. Store identification information 2 is location information (GPS information) that indicates the location of the store. Note that in the example shown in FIG. 5(C), store identification information and store identification information 1 are stored separately, but since both are information that can uniquely identify a store, it is sufficient to store at least one of the pieces of information.

(Cart information)
Fig. 5(D) shows an example of cart information. The cart information is information about products registered by a customer at a store. As shown in Fig. 5(D), the cart information includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, membership number, and registered product information.
The cart identification information is information for identifying the cart information. Specifically, the cart identification information includes store identification information, a date, and a serial number (for example, a serial number for each store for each date).

The transaction start date and time is the date and time when the transaction started, for example, the date and time when the cart information was generated. The transaction start date and time may be the registration date and time of one product, and more specifically, may be the date and time when the registered product information (registered product 1: XX medium-thick sauce) shown in FIG. 5 (D) was stored. Also, instead of or in addition to the transaction start date and time, the registration date and time for each product may be stored separately.

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

The registered product information (total) is cumulative information that is updated each time a product is registered. The registered product information (total) includes the number of products, the estimated subtotal amount, the subtotal amount, and the like.
The registered product information (registered product N: N is an integer) includes the number (data number) of the product registered in the Nth item. The registered product information N includes the product code, product name, price, and the date and time of registration of the product. Specifically, the registered product information (registered product 1: XX medium-thick sauce) indicates the product registered in the first item. The registered product information (registered product 2: XX cheese) indicates the product registered in the second item. Note that in the example shown in FIG. 5(D), the registered product information for the third and subsequent items is omitted from the illustration.

Next, we will explain reserved product information that indicates reserved products. Reserved products are products that require confirmation by a store clerk. For example, reserved products are classified into categories such as unscanned products, NON file products, products that require age verification, products that require the removal of security tags, and medicines.

Unscanned products are products on hold that could not be registered due to a failed attempt to scan the product code (the scanner was not able to read it). For example, if the product packaging is wrinkled or the barcode is smudged or dirty, the barcode may not be recognized due to a timeout.

Here, the failure to recognize the barcode due to a timeout will be described in detail. The mobile terminal device 30 is equipped with various sensors (e.g., a gyro sensor, an acceleration sensor, a distance sensor, etc.) and can determine that a barcode is being read using the detection results of the various sensors and the image capture results of the camera 407. Specifically, the mobile terminal device 30 can determine that a barcode is being read using the detection results of the various sensors when the mobile terminal device 30 is tilted and a product is present at a certain distance away from the mobile terminal device 30. Then, if the mobile terminal device 30 determines that a barcode is being read but is unable to read it within a specified time, it will time out and identify the product as an unscanned product.

Unscanned products include, for example, products that have been added to the basket under the pretense of having their barcodes read. In other words, products that have not been read include products that may have been subject to fraudulent manipulation, and include products that require a store clerk to confirm whether or not fraudulent manipulation has occurred. Fraudulent manipulation can be identified, for example, using scan results that indicate whether or not the barcode has been scanned, image results from a camera that captures the inside of the shopping basket, and detection results that detect the total weight of the products in the shopping basket.

A NON file product is, for example, a product that is not registered in the product master. Specifically, a NON file product is a product that could not be registered because the product code was successfully scanned (not marked as an unscanned product) and the product with that product code was queried from the product master but the product could not be identified (the product query was not successful).

Products that require age verification are, for example, products that cannot be purchased by minors, such as alcohol and tobacco.
Products that require the removal of security tags are, for example, products that have security tags attached, such as products that cost more than a certain amount.
Pharmaceuticals, for example, are products that require explanation from a pharmacist.

As shown in FIG. 5 (D), the reserved item information (total) includes the number of reserved items (unscanned items, NON file items) and the reserved item type. The reserved item type is information that indicates the type of reserved item.

The reserved product information (reserved product N: N is an integer) is information about the Nth reserved product, and includes the reserved product type of the Nth reserved product. In this example, a reserved product type of "1" indicates an unscanned product, and a reserved product type of "2" indicates a NON file product. Although not shown, a reserved product type of "3" indicates a product that requires age verification, a reserved product type of "4" indicates a product that requires the removal of the security tag, and a reserved product type of "5" indicates a pharmaceutical product. The reserved product information also includes the registration date and time of the product.

In addition, pending product information for an unscanned product includes pending product type "1" as well as image data for the product (image data captured when the mobile terminal device 30 reads the barcode). For example, pending product information (1) includes pending product type "1 (unscanned product)" and image data.

The pending product information for a NON file product includes the pending product type "2 (NON file product)" as well as the product code read by the mobile terminal device 30. For example, pending product information (2) includes the pending product type "2 (NON file product)" and the product code.

(Functional configuration of the shopping system 1 according to the present embodiment)
Next, the functional configuration of the shopping system 1 according to this embodiment will be described. The shopping system 1 includes a portable terminal device and a settlement device. The portable terminal device is, for example, a mobile terminal device 30. In this embodiment, the portable terminal device will be described as the mobile terminal device 30. The settlement device is, for example, a POS terminal device 20 that operates in a checkout-only mode. In this embodiment, the settlement device will be described as the POS terminal device 20.

The mobile terminal device 30 registers the products to be purchased through the customer's operation. The mobile terminal device 30 uses its imaging function to scan the barcode attached to the product and registers the product. The POS terminal device 20 performs settlement using transaction information generated by the mobile terminal device 30 when the product is registered.

The transaction information is, for example, cart information (see FIG. 5(D)) that includes information on registered products. The transaction information includes customer identification information that identifies the mobile terminal device 30. The entity that generates the transaction information is the cloud server Sv, but it may also be the mobile terminal device 30.

The transaction information is associated with storage medium identification information. Storage medium identification information is information that identifies a storage medium possessed by a customer, such as member identification information (member number). The member number is coded and stored (displayed) on a storage medium such as a member card, for example, as a two-dimensional code (hereinafter referred to as "member code"). Note that the member code may not only be the member number, but may also be the member information itself (see FIG. 5(B)) coded.

As shown in FIG. 5(B), the membership information includes a membership number and customer identification information. If the customer identification information included in the membership information and the customer identification information included in the transaction information are the same, the membership number and the transaction information are associated. For example, the cloud server Sv acquires the customer identification information included in the membership information and the customer identification information included in the transaction information, compares them, and if they are the same, associates the membership number with the transaction information by including the membership number in the cart information (FIG. 5(D)). Note that the association of the membership number with the transaction information is not limited to being performed by the cloud server Sv, but may be performed by the mobile terminal device 30, or may be performed by the cloud server Sv based on an instruction from the mobile terminal device 30, for example.

The POS terminal device 20 includes a reading unit, an acquisition unit, and a settlement unit. The reading unit, acquisition unit, and settlement unit are realized, for example, by the CPU 201. That is, the CPU 201 executes a predetermined program (checkout program) to realize the functions of each unit.

The reading unit reads the storage medium identification information stored in the storage medium. Specifically, the reading unit uses the customer-side scanner unit 206 to read the membership number (membership code) stored on the membership card.

The acquisition unit acquires transaction information associated with the membership number read by the reading unit. When the reading unit reads the membership number, the acquisition unit requests the cloud server Sv to send transaction information associated with the membership number. In response to the request, the acquisition unit acquires the transaction information from the cloud server Sv. The transaction information may be the cart information itself, or may be a portion of the cart information that is necessary for settlement.

The settlement unit executes the settlement process using the transaction information acquired by the acquisition unit. The settlement unit executes the settlement process for a specified payment type.

(Regarding payment using a payment code)
In this embodiment, the POS terminal 20 is capable of settlement using a membership card as well as settlement using the mobile terminal 30 (settlement code). More specifically, the mobile terminal 30 has a specific information output unit that outputs specific information for identifying transaction information. The specific information output unit is realized, for example, by the CPU 401. That is, the CPU 401 executes a predetermined program (checkout program) to realize the function of the transaction information output unit that displays transaction information on the display 409.

The specific information is, for example, cart identification information, and is included in the settlement code. The acquisition unit can acquire transaction information based on the specific information (cart identification information) output by the specific information output unit. Specifically, for example, when the settlement code displayed on the mobile terminal device 30 is read by the reading unit, the acquisition unit makes a request to the cloud server Sv to transmit transaction information corresponding to the cart identification information included in the settlement code. In response to the transmission request, the acquisition unit acquires the transaction information from the cloud server Sv.

The specific information (cart identification information) is not limited to being read by the reading unit. For example, the communication unit 215 may receive the cart identification information from the mobile terminal device 30 by short-range wireless communication. When the communication unit 215 receives the cart identification information, the acquisition unit may make a request to the cloud server Sv to transmit transaction information corresponding to the cart identification information.

In this way, the POS terminal device 20 according to this embodiment can settle the bill by reading either the membership code or the settlement code, and can settle the bill in either way. The POS terminal device 20 can also settle the bill using a bill.

(About automatic selection of payment type)
The settlement unit executes settlement processing with a payment type preset in accordance with the membership number. The payment type is, for example, electronic money, credit card, cash, etc. Furthermore, the payment type includes more detailed types of electronic money, such as a transportation IC card or a store's own IC card.

The payment type can be changed as appropriate in response to customer operations. The payment type may be set in the POS terminal device 20 to the payment type used in the most recent payment. The payment type may also be set from a shopping app on the mobile terminal device 30, or from a web page for members only. When the acquisition unit acquires transaction information, the settlement unit makes it possible to start settlement with a preset payment type. The settlement unit is also capable of performing settlement with a payment type other than the preset payment type.

(Display of payment type reception screen)
The POS terminal device 20 has a display unit. The display unit is, for example, a customer display unit 205. The customer display unit 205 displays a reception screen that accepts the selection of a payment type. When a membership code is read by the reading unit, the customer display unit 205 does not display the reception screen, i.e., skips displaying the reception screen. However, even when a membership code is read by the reading unit, if a payment type has not been set in advance for the membership code (member number), the customer display unit 205 displays the reception screen.

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

Step S601: First, the mobile terminal device 30 starts up a shopping application.
Step S602: The mobile terminal device 30 acquires information that identifies the store (store identification information). Here, an example of how the store identification information is acquired will be described. For example, a two-dimensional code indicating the store identification information (store identification information 1) is displayed near the entrance of the store. The two-dimensional code may be displayed on a predetermined display device, or may be displayed by printing on a medium. The mobile terminal device 30 starts the camera 407 by starting a shopping app in response to an operation of a customer who visits the store. Then, the camera 407 scans the two-dimensional code in response to an operation of the customer. As a result, the mobile terminal device 30 acquires the store identification information. The two-dimensional code may include store identification information for identifying the store.

Note that another example of a manner in which store-specific information is acquired is the acquisition of location information. For example, the mobile terminal device 30 acquires location information (GPS information) in response to an operation by a customer who visits the store. This location information is used for comparison with store-specific information 2 and is information that replaces store-specific information 1. Note that the mobile terminal device 30 may acquire location information and connect to the cloud server Sv by starting a shopping app in response to an operation by a customer who visits the store, and may display a screen as an initial screen informing the user that the device is connected to the cloud server Sv.

The mobile terminal device 30, which has acquired the store-specific information, requests the cloud server Sv to start a transaction. Specifically, the mobile terminal transmits the acquired store-specific information and customer identification information to the cloud server Sv.

Step S603: When the cloud server Sv receives customer identification information and store identification information as a request to start a transaction from the mobile terminal device 30, it generates cart information for the transaction. Specifically, as shown in FIG. 5(D), the cloud server Sv generates cart information including cart identification information, transaction start date and time, and customer identification information. More specifically, when the cloud server Sv receives store identification information from the mobile terminal device 30 as a request to start a transaction, it refers to the store information (see FIG. 5(C)) to identify the store identification information. Note that, when the cloud server Sv receives location information from the mobile terminal device 30, it refers to store identification information 2 of the store information to identify the store identification information corresponding to the location information. Note that, when the two-dimensional code includes the store identification information, the cloud server Sv can also obtain the store identification information by combining the received two-dimensional code.

When the cloud server Sv receives a request to start a transaction from the mobile terminal device 30, it obtains the current date and issues (assigns) a serial number. The cloud server Sv then combines the obtained store identification information, the obtained current date, and the issued serial number, and stores them as cart identification information. When the cloud server Sv receives a request to start a transaction from the mobile terminal device 30, it stores the current date and time as the transaction start date and time (generation date and time) in the cart information. When the cloud server Sv receives a request to start a transaction from the mobile terminal device 30, it stores the received customer identification information in the cart information.

Step S604: After generating the cart information, the cloud server Sv determines whether the customer is a member. Specifically, the cloud server Sv compares the customer identification information included in the cart information with the customer identification information included in the membership information (see FIG. 5(B)) and performs a match determination to determine whether there is a match. If the match determination results in a positive result, the cloud server Sv determines that the customer is a member. If the match determination results in a negative result, the cloud server Sv determines that the customer is a non-member. If it is determined in step S604 that the customer is not a member, the cloud server Sv proceeds to step S607.
Step S605: If the customer is a member, the member number is included in the cart information, thereby associating the member number with the cart identification information (see FIG. 5(D)).

Step S606: The mobile terminal device 30 scans and registers the product (the barcode attached to the product) in response to the customer's operation. When the product is scanned, the mobile terminal device 30 transmits the product code obtained by the scan to the cloud server Sv together with cart identification information. If the product indicated by this product code is a reserved product, the cart identification information and information indicating the reserved product are transmitted.

Step S607: When the cloud server Sv receives the product code and cart identification information from the mobile terminal device 30, it identifies the cart information that includes the received cart identification information, and updates the registered product information included in the identified cart information.

Step S608: The mobile terminal device 30 returns to step S606 until the registration is completed. The completion of the registration is when the settlement start button displayed on the display 409 for accepting the start of settlement is pressed.
Step S609: When the registration is completed, the mobile terminal device 30 performs a registration completion process (see FIG. 7).

Step S610: The POS terminal device 20 scans the settlement code displayed on the mobile terminal device 30 or the membership code displayed on the membership card. The settlement code includes cart identification information. The membership code includes a membership number. Step S610 allows the POS terminal device 20 to obtain information for identifying the cart information (cart identification information or membership number).

Step S611: When the POS terminal 20 scans the settlement code or membership code, it requests the transmission of cart information. In requesting the transmission of cart information, the POS terminal 20 transmits the cart identification information restored from the settlement code or the membership number restored from the membership code to the cloud server Sv.

Step S612: When the cloud server Sv receives a request to send cart information from the POS terminal device 20, it performs a cart information identification process (see FIG. 9). When the cloud server Sv identifies the cart information, it transmits the cart information to the POS terminal device 20.

Step S613: When the POS terminal device 20 receives the cart information from the cloud server Sv, it displays a list of the cart information on the customer side display unit 205. If there are pending items in the list display, the subtotal amount excluding the pending items may be displayed, or the subtotal amount may not be displayed. If there are pending items, a store clerk is called. In this case, the POS terminal device 20 transmits, for example, to the transaction management device 11 or a terminal device carried by the store clerk, information indicating that there are pending items and information to send a store clerk to the POS terminal device 20.

Step S614: The POS terminal 20 executes the settlement process (see FIG. 10). In the settlement process, the POS terminal 20 performs settlement using a specified payment type. In the settlement process, the POS terminal 20, for example, accepts the insertion of cash, dispenses change, and issues a receipt. The POS terminal 20 then sends settlement information indicating the details of the settlement and cart identification information to the cloud server Sv.

Step S615: The cloud server Sv stores the transaction end date and time (settlement date and time) of the cart information including the received cart identification information, and transmits a transaction completion notification to the mobile terminal device 30.
Step S616: When the mobile terminal device 30 receives the transaction completion notification, it deletes the products registered in the mobile terminal device 30 and ends the shopping app. If the mobile terminal device 30 displays a settlement code in the registration completion process in step S609, the mobile terminal device 30 may delete the products registered in the mobile terminal device 30 at the time the settlement code is displayed and end the shopping app. In other words, the cloud server Sv may not perform the process of transmitting the transaction completion notification (step S615).

(An example of the registration completion process (step S609 in FIG. 6) performed by the mobile terminal device 30)
Fig. 7 is a flow chart showing an example of the registration completion process performed by the mobile terminal device 30. In Fig. 7, the mobile terminal device 30 judges whether the customer operating the mobile terminal device 30 is a member (step S701). If the customer is a member (step S701: YES), the mobile terminal device 30 notifies the customer side scanner unit 206 of the POS terminal device 20 to scan the membership code on the membership card (step S702), and ends the series of processes. The membership code includes a membership number and transmission request information for the POS terminal device 20 to perform settlement. The transmission request information is information that requests the cloud server Sv to transmit cart information to the POS terminal device 20.

If the customer is not a member (step S701: NO), the mobile terminal device 30 generates a settlement code and displays it on the display 409 (step S703). The settlement code includes cart identification information and transmission request information for the POS terminal device 20 to perform settlement. The mobile terminal device 30 then notifies the customer side scanner unit 206 of the POS terminal device 20 to scan the settlement code (step S704), and the series of processes ends.

(Example of a screen displayed on the mobile terminal device 30)
Next, an example of a screen displayed on the mobile terminal device 30 will be described with reference to Fig. 8. Fig. 8 is an explanatory diagram showing an example of a screen displayed on the display 409 of the mobile terminal device 30.

Figure 8 (A) shows a registration screen 800 displayed on the display 409 of the mobile terminal device 30 when registering a product. The registration screen 800 includes an imaging area 801, a total display area 802, a checkout start button 803, and a registered product display area 804.

The imaging area 801 is an area where the barcode attached to the product can be imaged using the camera 407 of the mobile terminal device 30. The total display area 802 is an area that shows the total number of registered products and the total price. The start checkout button 803 is a button that is used to complete registration and to receive instructions to start the checkout procedure.

The registered product display area 804 is an area where the product name, quantity, price, etc. of the registered product are displayed. In the registered product display area 804, the registered products are displayed, for example, in the order in which they were registered. Specifically, the most recently registered product is displayed at the top of the registered product display area 804. When the Start Checkout button 803 is pressed on the registration screen 800, the screen transitions to the screen shown in FIG. 8 (B) or FIG. 8 (C) depending on whether the customer operating the mobile terminal device 30 is a member or not.

Figure 8 (B) shows a membership code presentation instruction screen 810. The membership code presentation instruction screen 810 includes a presentation instruction 811, a total amount 812, a confirmation button 813, and a do not have button 814. The presentation instruction 811 is an instruction to have the POS terminal device 20 read the membership code printed on the membership card. The total amount 812 indicates the purchase amount, i.e., the total amount to be paid by the customer at checkout. The confirmation button 813 is a button for accepting consent that the checkout will be made by reading the membership code.

When the membership code is read by the POS terminal 20 (customer-side scanner unit 206), settlement is initiated at the POS terminal 20. Specifically, when the POS terminal 20 reads the membership code, it requests the cloud server Sv to send cart information, and is then able to execute settlement processing using the cart information received from the cloud server Sv in response to the request.

The "No Membership" button 814 is a button that indicates that although the customer is a member, they do not possess a membership card, and therefore payment cannot be started by reading the membership code. When the "No Membership" button is pressed, the screen transitions to, for example, the screen shown in FIG. 8 (C).

Figure 8 (C) shows a display screen 820 on which a settlement code 822 is displayed. The display screen 820 includes a presentation instruction 821, the settlement code 822, a registration return button 823, and a total amount display 824. The presentation instruction 821 indicates an instruction to the POS terminal device 20 to read the settlement code 822. The registration return button 823 is a button that accepts returning to the screen where the product can be scanned (the registration screen 800 in Figure 8 (A)). Note that the registration return button 823 may also be displayed on the presentation instruction screen 810 in Figure 8 (B). The total amount display 824 shows the total amount to be paid by the customer in the settlement process.

When the settlement code 822 is read by the POS terminal 20 (customer-side scanner unit 206), settlement is initiated at the POS terminal 20. Specifically, when the POS terminal 20 reads the settlement code 822, it requests the cloud server Sv to send cart information, and is then able to execute settlement processing using the cart information received from the cloud server Sv in response to the request.

(An example of the cart information identification process (step S612 in FIG. 6) performed by the cloud server Sv)
Fig. 9 is a flow chart showing an example of a cart information identification process performed by the cloud server Sv. In Fig. 9, the cloud server Sv determines whether or not a request to send cart information has been received from the POS terminal 20 (step S901). The cloud server Sv waits until a request to send cart information is received (step S901: NO). When a request to send cart information is received (step S901: YES), the cloud server Sv determines whether or not the request from the POS terminal 20 is a request based on reading a membership code (step S902).

If the transmission request is based on reading the membership code (step S902: YES), the cloud server Sv identifies the cart information using the membership number obtained from the membership code (step S903), transmits the membership information and the cart information to the POS terminal device 20 (step S904), and ends the series of processes. Note that the membership information transmitted to the POS terminal device 20 only needs to include information on the payment type and the number of points used (see FIG. 5 (B)).

On the other hand, if the transmission request is not a transmission request based on reading a membership code (step S902: YES), that is, if the transmission request is a transmission request based on reading a settlement code, the cart information is identified using cart identification information obtained from the settlement code (step S905). The cloud server Sv then transmits the cart information to the POS terminal device 20 (step S906), and the process ends.

(An example of the settlement process (step S614 in FIG. 6) performed by the POS terminal 20)
Fig. 10 is a flow chart showing an example of a settlement process performed by the POS terminal 20. In Fig. 10, the POS terminal 20 determines whether or not it has received cart information from the cloud server Sv (step S1001). The POS terminal 20 waits until it receives the cart information (step S1001: NO). When it receives the cart information (step S1001: YES), the POS terminal 20 determines whether or not it has also received member information (step S1002).

If member information is not received (step S1002: NO), i.e., if cart information is received based on the reading of the settlement code, the POS terminal 20 displays a payment type selection screen (see FIG. 11(B)) that accepts the selection of the payment type (step S1003). The POS terminal 20 then accepts the payment type (step S1004), executes the settlement (step S1005), and ends the series of processes.

On the other hand, if member information has been received in step S1002 (step S1002: YES), i.e., if cart information has been received based on the reading of the member code, the POS terminal 20 identifies the payment type according to the member information received from the cloud server Sv (information on the payment type and information on the number of points used) (step S1006). The POS terminal 20 then skips displaying the payment type selection screen and displays a payment type confirmation screen (see FIG. 12(B)) which is a screen for confirming the payment type (step S1007), and proceeds to step S1005.

(Example of a screen displayed on the customer display unit 205 of the POS terminal device 20)
Next, examples of screens displayed on the customer display unit 205 of the POS terminal 20 will be described with reference to Figures 11 and 12. Figure 11 is an explanatory diagram showing an example of the transition of screens displayed by the POS terminal 20 in response to reading a settlement code. Figure 12 is an explanatory diagram showing an example of the transition of screens displayed by the POS terminal 20 in response to reading a membership code.

Figure 11 (A) shows a standby screen 1100. The standby screen 1100 includes a guide notification 1101. The guide notification 1101 is a notification that prompts the customer to have the customer-side scanner unit 206 read a membership code or a settlement code. When the customer has the customer-side scanner unit 206 read the settlement code displayed on the mobile terminal device 30 on the standby screen 1100, the screen transitions to a payment type selection screen 1110 shown in Figure 11 (B).

Figure 11 (B) shows the payment type selection screen 1110. The payment type selection screen 1110 includes selection buttons 1111 (1111a, 1111b, 1111c) that accept the selection of a payment type. When any of the selection buttons 1111 is pressed, settlement is initiated with the payment type indicated by the pressed selection button 1111.

Figure 12 (A) shows a standby screen 1100 similar to Figure 11 (A). When a customer has the customer-side scanner unit 206 read the membership code displayed on the membership card on the standby screen 1100, the screen transitions to a payment type confirmation screen 1200 shown in Figure 12 (B).

Figure 12 (B) shows a payment type confirmation screen 1200. The payment type confirmation screen 1200 includes a membership number 1201, a payment type 1202, points used information 1203, a selection button 1204, and a payment type selection button 1205. The membership number 1201 indicates the membership number of the member. The payment type 1202 indicates a preset payment type (electronic money in the figure). The points used information 1203 indicates the number of points to be used for shopping (total number of points in the figure). The selection buttons 1204 include a "Yes" button 1204a and a "No" button 1204b.

The "Yes" button 1204a is a button that accepts making a payment with the details indicated by the payment type 1202 and the point usage information 1203. The "No" button 1204b is a button that accepts a change to the details indicated by the payment type 1202 and the point usage information 1203. When the "No" button 1204b is pressed, the screen transitions to a screen that accepts a change to the payment type or a change to the number of points used. The payment type selection button 1205 is a button that accepts a change to the payment type, and when pressed, the screen transitions to, for example, the payment type selection screen 1110 in FIG. 11 (B).

As described above, in the above-mentioned shopping system 1, the POS terminal device 20 reads the membership number (membership code) stored on the membership card, obtains the cart information associated with the read membership number, and executes the settlement process. Therefore, in the case of a member customer, settlement can be performed without having to display the settlement code on the mobile terminal device 30 or have the settlement code read. This eliminates the need for the effort involved in reading various codes, simplifying the procedure at the time of settlement.

In addition, in the above-mentioned shopping system 1, the mobile terminal device 30 displays a settlement code, and the POS terminal device 20 can obtain cart information based on the settlement code. This allows settlement to be made either based on the membership card or based on the settlement code. Therefore, even if a customer does not have a membership card, they can display the settlement code and make a settlement.

In addition, in the above-mentioned shopping system 1, the POS terminal device 20 executes the settlement process with a payment type that is preset in accordance with the membership number. This can reduce the effort required for settlement and simplify the settlement procedure.

In addition, in the above-described shopping system 1, when the membership code is read, the POS terminal device 20 does not display the reception screen for selecting the payment type (see payment type selection screen 1110 in FIG. 11(B)). This allows the reception screen to be skipped, making it possible to quickly settle the payment.

(Modification of the embodiment)
Modifications 1 to 6 of the embodiment will be described below. Note that in the following Modifications 1 to 6, the contents described in the above-mentioned embodiment will be omitted as appropriate. It is also possible to have a configuration in which the configurations shown in the above-mentioned embodiment and Modifications 1 to 6 are respectively combined. Specifically, a configuration may be used that includes all of the above-mentioned embodiment and Modifications 1 to 6, or a configuration may be used that combines the above-mentioned embodiment and any of Modifications 1 to 6.

(Variation 1)
First, a description will be given of Modification 1. In the above-described embodiment, a configuration in which a membership code is displayed on a membership card has been described. In Modification 1, a description will be given of a configuration in which a membership code is displayed on a mobile terminal device 30 in addition to or instead of such a configuration.

Figure 13 is an explanatory diagram showing a modified example of a screen displayed on the display 409 of the mobile terminal device 30. Figure 13 (A) shows a registration screen 800 similar to Figure 8 (A). When the Start Settlement button 803 is pressed on the registration screen 800, if the customer operating the mobile terminal device 30 is a member, the screen transitions to the screen shown in Figure 13 (B). Note that if the customer operating the mobile terminal device 30 is a non-member, the screen transitions to the display screen 820 shown in Figure 8 (C).

Figure 13 (B) shows the membership code display screen 1300. The membership code display screen 1300 includes a presentation instruction 1301, a membership code 1302, a registration return button 823, and a total amount display 824. The presentation instruction 1301 indicates an instruction to the POS terminal device 20 to read the membership code 1302.

When the membership code 1302 is read by the POS terminal 20 (customer-side scanner unit 206), settlement is initiated at the POS terminal 20. Specifically, when the POS terminal 20 reads the membership code 1302, it requests the cloud server Sv to send cart information, and is then able to execute settlement processing using the cart information received from the cloud server Sv in response to the request.

According to variant 1, the customer can display the membership code on the mobile terminal device 30 and make a payment without having to take out the membership card. This eliminates the need to take out the membership code and prevents the procedure from becoming complicated when making a payment. In addition, even if the customer does not have a membership card, the payment can be made based on the membership code, so that the transaction can be carried out with the membership information reflected.

(Variation 2)
Next, a description will be given of Modification 2. In the above-described embodiment, if the user is a member, the payment type selection screen 1110 (see FIG. 11(B)) is not displayed, and the payment type confirmation screen 1200 (see FIG. 12(B)) is displayed. In Modification 2, in addition to or instead of this configuration, a configuration will be described in which the payment type selection screen 1110 (see FIG. 11(B)) is displayed even if the user is a member.

The payment type selection screen according to the second modification may be a screen with fewer selection buttons 1111 than, for example, the payment type selection screen 1110 shown in FIG. 11(B) (see FIG. 11(B)). Specifically, if the customer has set not to pay by credit card, a selection button 1111a that accepts cash as a payment type and a selection button 1111c that accepts electronic money may be displayed. In other words, if the customer is a member, a screen with fewer payment type options may be displayed.

According to the second modification, the number of payment type options can be reduced. This simplifies the settlement procedures.

(Variation 3)
Next, a description will be given of Modification 3. In the above embodiment, a description has been given of a shopping system 1 in which a customer registers products using a mobile terminal device 30, and the customer pays at a POS terminal device 20 in a payment-only mode. In Modification 3, a description will be given of a POS system in which, in addition to or instead of the above configuration, a customer or a store clerk registers products at a POS terminal device 20, and the customer pays at a POS terminal device 20 (including another POS terminal device 20).

In the POS system according to the third variant, the customer can make payments in person in normal mode, by self-checkout in billing-only mode, or by self-checkout in full self-checkout mode. In these types of payments, the POS terminal device 20 can read the membership number (membership code) stored on the membership card, obtain the cart information associated with the read membership number, and execute the payment process.

It is also possible to execute the settlement process using a payment type preset in accordance with the membership number. It is also possible not to display the reception screen (see payment type selection screen 1110 in FIG. 11(B)) that accepts the selection of the payment type when the membership code is read. According to variant 3, it is possible to eliminate the effort involved in settlement for customers who are members, and to simplify the settlement procedure. It is also possible to perform settlement quickly.

(Variation 4)
Next, a description will be given of Modification 4. In the above embodiment, a configuration has been described in which the member information (see FIG. 5(B)) includes the payment type and the number of points used. In Modification 4, a description will be given of a configuration in which, in addition to or instead of such a configuration, the member information includes information other than these.

In the fourth variant example, the information included in the member information is, for example, information on whether to issue a receipt or a receipt. The receipt includes an electronic receipt that can be displayed on the display 409 of the mobile terminal device 30. By including such information in the member information, it is not necessary to select or declare whether to issue a receipt or a receipt at the time of settlement, which simplifies the procedure at the time of settlement.

In addition, information included in the member information is, for example, information on whether or not a parking ticket is held and whether or not a plastic bag is required. By including such information in the member information, the customer does not have to select or declare whether or not they have a parking ticket or whether or not they need a plastic bag at the time of payment, which simplifies the procedure at the time of payment.

Furthermore, when purchasing refrigerated or frozen products, customers can be provided with dry ice. Therefore, the information included in the member information may be information indicating whether or not dry ice is available. By including such information in the member information, when purchasing frozen foods such as ice cream, customers do not need to select or declare whether or not dry ice is available, which simplifies the procedure at the time of payment.

When purchasing a bento box or drink, customers can be provided with chopsticks, spoons, and straws. Therefore, the information included in the membership information may be information indicating whether or not chopsticks, spoons, straws, etc. are provided. By including such information in the membership information, when purchasing a product that can be eaten in or when eat-in is selected, customers do not have to select or declare whether or not chopsticks, spoons, or straws are provided, which simplifies the procedure at the time of payment.

(Variation 5)
Next, Variation 5 will be described. In the above embodiment, as shown in FIG. 11(A), a configuration has been described in which the customer scanner unit 206 reads a membership code or a settlement code to start settlement. In Variation 5, in addition to or instead of such a configuration, a configuration may be adopted in which the customer scanner unit 206 reads the settlement code and then reads the membership code to start settlement. Also, when the membership code is read, the reception screen for accepting the selection of the payment type (see payment type selection screen 1110 in FIG. 11(B)) may not be displayed, that is, the display of payment type selection screen 1110 may be skipped. Variation 5 allows for rapid settlement.

(Variation 6)
Next, a description will be given of Variation 6. In the above embodiment, a configuration has been described in which the procedure for settlement is simplified by having the POS terminal device 20 read the membership code. In Variation 6, in addition to or instead of the above configuration, a description will be given of a configuration in which the procedure for connecting the weighing device and the mobile terminal device 30 is simplified by having the weighing device read the membership code.

The weighing device is a computer device that weighs the product to be weighed. The weighing device is connected to the cloud server Sv via a network. The weighing device calculates the price of the product to be weighed. Here, a normal product is, for example, a product with a JAN code attached. When the mobile terminal device 30 reads the JAN code, it queries the cloud server Sv for the read JAN code and obtains the price data associated with the JAN code.

On the other hand, for products to be weighed, the amount is calculated using the weighed weight (or number) and the unit price of the product to be weighed. In other words, products to be weighed are products whose prices vary depending on the weight and quantity of the item. For example, products to be weighed include fresh foods such as vegetables, fruits, fish, and meat, as well as prepared foods. When the weighing device has completed weighing the product to be weighed, it prints and outputs a label that codes the amount, weight, etc. of the product to be weighed. This label includes the price. In other words, the label (barcode) attached to the product to be weighed uses the NON-PLU (Price Look Up) method.

(Regarding communication connection between the mobile terminal device 30 and the weighing device)
The portable terminal device 30 communicates with the weighing device. Specifically, the portable terminal device 30 performs one-to-one short-range wireless communication with the weighing device, for example, using Bluetooth (registered trademark). Note that, when performing one-to-one communication, the portable terminal device 30 is required to set a function for one-to-one communication to ON. Furthermore, the portable terminal device 30 makes a connection request for one-to-one communication to the weighing device. In response to this connection request, the weighing device starts communication with the portable terminal device 30.

Here, the procedure for connecting the portable terminal device 30 and the weighing device will be described in detail. For example, when the weighing device is not connected to the portable terminal device 30, it is in a pairing-enabled state (standby state) for one-to-one communication connection. In the standby state, the weighing device displays a connection code on the display. The connection code includes information for connecting the portable terminal device 30 and the weighing device (information for searching for surrounding devices, specifying the weighing device, inputting a passkey, etc.).

When the camera 407 of the mobile terminal device 30 reads the connection code, it automatically searches for nearby devices, specifies the weighing device, enters a passkey, and so on. In other words, when a customer reads the connection code with the camera 407 of the mobile terminal device 30, a connection request is automatically made from the mobile terminal device 30 to the weighing device, and a communication connection with the weighing device is automatically established.

In the sixth variation, the membership information (see FIG. 5B) includes identification information of the portable terminal device 30 and information for connecting and communicating with the portable terminal device 30 (hereinafter referred to as "connection information"). When a customer has the membership code read by the scanner of the weighing device, the weighing device queries the cloud server Sv to identify the portable terminal device 30 associated with the membership code. The weighing device then receives connection information for the identified portable terminal device 30 from the cloud server Sv and connects to the portable terminal device 30 by making a connection request to the portable terminal device 30. In response to a connection request from the weighing device, the portable terminal device 30 may display a screen on the display 409 that accepts the selection of whether or not to connect, and connect to the weighing device when it accepts a connection request from the customer.

In this way, in Variation 6, when a customer has the weighing device read the membership code, the weighing device automatically sends a connection request to the portable terminal device 30, making it possible to automatically establish a communication connection between the portable terminal device 30 and the weighing device. Variation 6 eliminates the hassle of connecting the portable terminal device 30 to the weighing device for member customers, and simplifies the procedure for said connection.

The embodiments will be summarized below.
[Name of invention] Checkout system, settlement device, checkout method, and program [Technical field]
The present invention relates to a checkout system, a settlement device, a checkout method, and a program.
[Background Art]
In recent years, so-called self-checkout systems, in which a customer registers products and performs payment, have become widespread. For example, a self-checkout system is known in which a customer registers products using a mobile terminal device carried by the customer and performs payment at a payment device (see, for example, Patent Document 1).
To give a specific example, in a self-checkout system, when a customer reads a barcode attached to an item with a mobile terminal device, the information of the read barcode is sent from the mobile terminal device to a cloud server. The cloud server registers the item using the information received from the mobile terminal device. Then, once registration of the item to be purchased is complete, the customer displays a settlement code on the mobile terminal device and has the settlement device read it. After reading the settlement code, the settlement device requests the cloud server to send transaction information to be used for settlement, receives the transaction information from the cloud server, and performs settlement by the customer.
[Prior Art Literature]
[Patent Documents]
[Patent Document 1] JP 2016-219034 A [Summary of the Invention]
[Problem to be solved by the invention]
However, in the conventional technology, for example, when a customer is a member, the payment device must read a code for payment or a membership code written on a membership card, which can require a lot of work to read various codes. Therefore, the conventional technology has a problem in that the procedure for payment can be complicated.
The present invention has been made in consideration of the above circumstances, and has an object to provide a technique that can simplify the procedures at the time of settlement.

[Means for solving the problems]
(1) In order to solve the above-mentioned problems, a checkout system that is one aspect of the present invention is a checkout system including a portable terminal device that registers products to be purchased by a customer through operation of the portable terminal device, and a settlement device that settles a payment using transaction information generated by the registration of the products by the portable terminal device, wherein the transaction information is associated with storage medium identification information that identifies a storage medium possessed by the customer, and the settlement device includes a reading means that reads the storage medium identification information stored in the storage medium, an acquisition means that acquires the transaction information associated with the storage medium identification information read by the reading means, and a settlement means that executes a settlement process using the transaction information acquired by the acquisition means.
According to the above configuration, in the case of a member customer, settlement can be performed without displaying or reading the settlement code on the mobile terminal device 30. This can therefore eliminate the need for the effort required for reading various codes, thereby simplifying the procedure for settlement.

(2) In the above configuration (1), the portable terminal device may be provided with a specific information output means for outputting specific information for identifying the transaction information, and the acquisition means may be capable of acquiring the transaction information based on the specific information output by the specific information output means.
According to the above configuration, the payment can be made either based on the membership card or based on the payment code. Therefore, even if the customer does not have a membership card, the payment can be made by displaying the payment code.

(3) In the configuration of (1) or (2) above, the settlement means may execute the settlement process with a payment type that is preset in correspondence with the storage medium identification information.
According to the above configuration, it is possible to eliminate the hassle involved in settlement and simplify the procedures involved in settlement.

(4) In the configuration of (3) above, a display means may be provided for displaying a reception screen for accepting the selection of a payment type, and the display means may be configured not to display the reception screen when the storage medium identification information is read by the reading means.
According to the above configuration, the display of the reception screen can be skipped, making it possible to quickly complete the payment.

(5) In order to solve the above-mentioned problems, another aspect of the present invention is a settlement device of a checkout system including a portable terminal device that registers products to be purchased by operation of a customer, and a settlement device that performs settlement using transaction information generated by the registration of the products by the portable terminal device, wherein the transaction information is associated with storage medium identification information that identifies a storage medium possessed by the customer, and the settlement device includes a reading means that reads the storage medium identification information stored in the storage medium, an acquisition means that acquires the transaction information associated with the storage medium identification information read by the reading means, and a settlement means that executes settlement processing using the transaction information acquired by the acquisition means.
According to the above configuration, if the customer is a member, the settlement code can be displayed on the mobile terminal device 30 and settlement can be performed without the need to read the settlement code. This eliminates the need to read various codes and simplifies the procedure for settlement.

(6) In order to solve the above-mentioned problems, a checkout method that is another aspect of the present invention is a checkout method for a checkout system that includes a portable terminal device that registers products to be purchased by a customer's operation, and a settlement device that settles a payment using transaction information generated by the registration of the products by the portable terminal device, wherein the transaction information is associated with storage medium identification information that identifies a storage medium possessed by the customer, and the settlement device executes a process including: a reading step of reading the storage medium identification information stored in the storage medium, an acquisition step of acquiring the transaction information associated with the storage medium identification information read in the reading step, and a settlement step of executing a settlement process using the transaction information acquired in the acquisition step.
According to the above configuration, if the customer is a member, the settlement code can be displayed on the mobile terminal device 30 and settlement can be performed without the need to read the settlement code. This eliminates the need to read various codes and simplifies the procedure at the time of settlement.

(7) In order to solve the above-mentioned problems, another aspect of the present invention is a program used in a computer of a settlement device of a checkout system including a portable terminal device that registers products to be purchased by a customer through operation of the portable terminal device, and a settlement device that settles the payment using transaction information generated by the registration of the products by the portable terminal device, wherein the transaction information is associated with storage medium identification information that identifies a storage medium possessed by the customer, and the program causes the computer used in the settlement device to function as a reading means that reads the storage medium identification information stored in the storage medium, an acquisition means that acquires the transaction information associated with the storage medium identification information read by the reading means, and a settlement means that executes a settlement process using the transaction information acquired by the acquisition means.
According to the above configuration, if the customer is a member, the settlement code can be displayed on the mobile terminal device 30 and settlement can be performed without the need to read the settlement code. This eliminates the need to read various codes and simplifies the procedure at the time of settlement.

All or part of the functions (input/output, storage, processing (including judgment)) of the POS terminal device 20 and the mobile terminal device 30 described above may be realized in a device other than the device described as the entity that executes the function.

Specifically, in the above description, the POS terminal device 20 is provided with a reading unit, an acquisition unit, and a settlement unit, and the mobile terminal device 30 is provided with a specific information output 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 management device 11, the cloud server Sv, or a computer device other than these. Furthermore, the computer device provided with these functional units is not limited to being multiple units, and may be one unit. For example, one computer device may be provided with all of these functional units.

Specifically, for example, instead of the POS terminal device 20, the transaction management device 11 or the cloud server Sv may obtain cart information associated with the membership number and perform settlement.

In relation to the above, the POS terminal device 20 and the mobile terminal device 30 may function as a so-called thin client specialized for the input/output interface when it comes to registering products and settling accounts. In other words, the POS terminal device 20 and the mobile terminal device 30 may accept various inputs (operation by an operator, detection by a device such as a scanner), send input information (operation information, scan information, etc.) to the cloud server Sv, receive the processing results of the cloud server Sv based on the input information (update screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device).

The program for implementing the shopping system 1 and the POS terminal device 20 described above may be recorded on a computer-readable recording medium, and the program may be read into a computer system for execution. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into a computer system. The term "computer-readable recording medium" also includes storage devices that hold a program for a certain period of time, such as volatile memory (RAM) inside a computer system that becomes 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. The program may be transmitted from a computer system that stores the program in a storage device to another computer system via a transmission medium or by a transmission wave in the transmission medium. The "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be for implementing part of the above-mentioned functions. Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, i.e., a differential file (differential program).

Sv: cloud server 1: shopping system 10: store controller 11: transaction management device 20: POS terminal device 30: mobile terminal device 201, 401: CPU
202, 402...ROM
203, 403...RAM
204: Hard disk 205: Customer display unit 206: Customer scanner unit 208: Card payment unit 209: Change machine 210: Clerk display unit 211: Key operation unit 212: Clerk scanner unit 215: Communication unit 217: Image capture unit 405: Communication unit 407: Camera 409: Display

Claims (5)

a portable terminal device for registering products through operation by a customer ;
a settlement device that performs settlement based on transaction information generated by registering the product by the portable terminal device ;
A checkout system comprising:
The transaction information includes member identification information for identifying the member customer in a transaction with a member customer , and does not include the member identification information in a transaction with a non-member customer;
The portable terminal device is
A receiving means for receiving a completion of the registration of the product;
a display means for displaying a screen corresponding to the customer when the reception means receives the completion of the registration;
Equipped with
The display means is
If the customer is a member, a prompting screen is displayed to prompt the customer to have the settlement device read a member code obtained by encoding the member identification information;
In the case of the non-member customer, a settlement code is displayed which is a coded transaction identification information for identifying the transaction information;
The settlement device includes:
A reading means for reading the code ;
an acquisition means for acquiring the transaction information based on the code read by the reading means;
a settlement means for executing a settlement process based on the transaction information acquired by the acquisition means;
Equipped with
The settlement means is
When the member code is read by the reading means, a settlement process is carried out based on the transaction information including the member identification information;
when the settlement code is read by the reading means, a settlement process is executed based on the transaction information obtained from the settlement code.
A checkout system comprising: the display means is capable of accepting, on the instruction screen, a notification that the member card on which the member code is displayed is not in possession, and when accepting the notification, displays the settlement code.
2. The checkout system according to claim 1. a portable terminal device for registering products through operation by a customer;
a settlement device that settles a payment based on transaction information generated by the portable terminal device when a commodity is registered, the transaction information including member identification information for identifying the member customer in a transaction with a member customer and not including the member identification information in a transaction with a non-member customer;
The portable terminal device of a checkout system comprising:
A receiving means for receiving a completion of the registration of the product;
a display means for displaying a screen corresponding to the customer when the reception means receives the completion of the registration;
Equipped with
The display means is
In the case of the member customer, a member code obtained by encoding the member identification information is displayed on an instruction screen that prompts the settlement device to read the member code for executing a settlement process,
In the case of the non-member customer, a settlement code is displayed, which is a coded transaction identification information that identifies the transaction information, and the settlement device displays the settlement code for executing a settlement process.
A portable terminal device comprising: the display means is capable of accepting, on the instruction screen, a notification that the member card on which the member code is displayed is not in possession, and when accepting the notification, displays the settlement code.
4. The portable terminal device according to claim 3, a portable terminal device for registering products through operation by a customer ;
a settlement device that performs settlement based on transaction information generated by registering the product by the portable terminal device ;
A check-out method for a check-out system comprising:
The transaction information includes member identification information for identifying the member customer in a transaction with a member customer , and does not include the member identification information in a transaction with a non-member customer;
The portable terminal device,
A reception step for receiving the completion of the product registration;
a display step of displaying a screen corresponding to the customer when the completion of the registration is accepted in the accepting step;
Perform a process including
In the display step,
If the customer is a member, a prompting screen is displayed to prompt the customer to have the settlement device read a member code obtained by encoding the member identification information;
In the case of the non-member customer, a settlement code is displayed which is a coded transaction identification information for identifying the transaction information;
The settlement device,
a reading step of reading the code ;
an acquiring step of acquiring the transaction information based on the code read in the reading step;
a settlement step of executing a settlement process based on the transaction information acquired in the acquisition step;
Perform a process including
In the settlement step,
If the member code is read in the reading step, a settlement process is carried out based on the transaction information including the member identification information;
When the settlement code is read in the reading step, a settlement process is executed based on the transaction information obtained from the settlement code.
A check-out method comprising:

Images