JP7624202B2 - Product sales data processing system, terminal device, settlement device, and program - Google Patents

Description

The present invention relates to a product sales data processing system, a terminal device, a settlement device, and a program.

A system is known in which customers can register products using a mobile terminal and then use a payment device to make payments for the registered products (see, for example, Patent Document 1).

JP 2018-55700 A

There are cases where a customer completes product registration using a mobile device and starts payment at the payment device, but then realizes that they forgot to register a specific product, such as a plastic bag. In such cases, an additional step is required, such as the customer calling a store clerk, who then corrects the transaction to add a plastic bag to the payment.

The present invention was made in consideration of these circumstances, and aims to make it possible to notify customers at the appropriate time that a particular product has not been registered.

One aspect of the present invention that solves the above-mentioned problems is a product sales data processing system that includes a terminal device used to register products and a settlement device that performs settlement corresponding to the products registered by the terminal device, and includes a registration means that registers products in response to use of the terminal device, a determination means that determines whether a specific product is registered by the registration means, and an information output means that outputs information corresponding to the fact that the specific product is not registered when it is determined by the registration means that the specific product is not registered.

One aspect of this embodiment is a terminal device used to register products in a product sales data processing system, the terminal device comprising: a registration means for registering products; a determination means for determining whether a specific product has been registered by the registration means; and an information output means for displaying information corresponding to the fact that the specific product has not been registered when the registration means determines that the specific product has not been registered.

One aspect of this embodiment is a settlement device in a product sales data processing system that includes a terminal device used to register products and a settlement device that performs settlement corresponding to the products registered by the terminal device, the settlement device including a determination means that determines whether a specific product is registered in response to a declaration that settlement corresponding to the registered product will be performed in response to use of the terminal device, and an information output means that outputs information corresponding to the fact that the specific product is not registered when it is determined that the specific product is not registered.

One aspect of this embodiment is a program for causing a computer serving as a terminal device used to register products in a product sales data processing system to function as a registration means for registering products, a determination means for determining whether a specific product has been registered by the registration means, and an information output means for displaying information corresponding to the fact that the specific product has not been registered when the registration means determines that the specific product has not been registered.

This is a program for causing a computer serving as a settlement device in a product sales data processing system, which includes a terminal device used to register products and a settlement device that performs settlement corresponding to the products registered by the terminal device, to function as a determination means for determining whether a specific product is registered in response to a declaration that settlement corresponding to the registered product will be performed in response to use of the terminal device, and as an information output means for outputting information corresponding to the fact that the specific product is not registered when it is determined that the specific product is not registered.

1 is a diagram illustrating an example of the overall configuration of a product sales data processing system according to an embodiment of the present invention. 1 is a diagram showing an example of the state near the entrance of a store in which a product sales data processing system according to an embodiment of the present invention has been introduced. 1A to 1C are diagrams illustrating examples of how a mobile terminal is set in a shopping cart according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a settlement device according to the first embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a mobile terminal according to the first embodiment. 1 is a diagram illustrating an example of the configuration of a transaction management device according to a first embodiment. 3A to 3C are diagrams illustrating an example of customer information, store information, and cart information according to the first embodiment. A sequence diagram showing an example of processing procedures executed by the mobile terminal, settlement device, and transaction management device in the first embodiment in response to the accounting of a single transaction in self-service operation. 5A to 5C are diagrams showing examples of a start-up screen, a product registration initial screen, a product registration update screen, and a code screen according to the first embodiment. FIG. 13 is a diagram showing an example of a shopping bag purchase confirmation screen according to the first embodiment. 11 is a flowchart showing an example of a processing procedure executed by the mobile terminal according to the first embodiment in response to a settlement transition instruction operation. 13 is a flowchart showing an example of a processing procedure executed by a settlement device 40 according to the second embodiment in response to product registration of a shopping bag. FIG. 11 is a diagram showing an example of a shopping bag purchase confirmation screen according to the second embodiment. FIG. 13 is a diagram illustrating an example of a product registration result area according to the second embodiment. FIG. 13 is a diagram showing an example of a product registration change screen according to the second embodiment; 13A and 13B are diagrams showing examples of a product registration result area and a product registration change screen in a modified example of the embodiment.

First Embodiment
[Example of overall configuration of product sales data processing system]
FIG. 1 shows an example of the overall configuration of a product sales data processing system 1 according to the present embodiment.
The product sales data processing system 1 in the figure includes a store controller 10, a transaction management device 20 (cloud server), a registration settlement device 30, a settlement device 40, a transaction status management device 50 (e.g., a personal computer, etc.), and a mobile terminal 60.
The product sales data processing system 1 in the figure can be introduced into various stores (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).

In the figure, one registered settlement device 30 is illustrated, but the number of registered settlement devices 30 installed in one store may be two or more. In the figure, two settlement devices 40 are illustrated, but the number of settlement devices 40 in one store may be one or three or more. In the figure, one transaction status management device 50 is illustrated, but the number of transaction status management devices 50 in one store may be two or more. In addition, there may be two or more store controllers 10 in one store.

The product sales data processing system 1 in the figure is capable of handling both a store clerk-assisted operation in which a store clerk uses a registration and settlement device 30 to register products, and a self-service operation in which a customer registers products using a mobile terminal 60 and then uses a settlement device 40 to settle the payment.
In the following explanation, self-operation will be mainly described.

The store controller 10, the registration settlement device 30, the settlement device 40, and the transaction status management device 50 are installed in the store. The store controller 10, the registration settlement device 30, the settlement device 40, and the transaction status management device 50 are connected to each other so as to be able to communicate with each other via a LAN 19 (which may be wired or wireless). The store controller 10 is capable of communicating with the transaction management device 20.

The store controller 10 is a device that mainly manages various devices installed in a store. For example, the store controller 10 has a communication function with external devices, and receives product files (product masters) from external devices (e.g., a headquarters server not shown, which may be the transaction management device 20) and supplies them to the registered settlement device 30, etc., and receives transaction information from the settlement device 40, etc. and transmits it to the external device (e.g., the transaction management device 20, etc.).

The transaction management device 20 is a server that provides various services. For example, the transaction management device 20 manages various information corresponding to self-operation (e.g., transaction information (cart information), etc.).

The registration and settlement device 30 is a device that executes the registration process and the settlement process. The registration and settlement device 30 is used by a store clerk (the registration process and the settlement process are executed by the operation of the store clerk).

The settlement device 40 is a device that executes settlement processing. The settlement device 40 is used by a customer. That is, the settlement device 40 executes settlement processing in response to operations by the customer.
In addition, when the payment includes items whose processing is temporarily suspended for confirmation by a store clerk (hereinafter referred to as "pending items"; details will be described later), a store clerk will be called and the store clerk (or the customer) will operate the payment device 40 to confirm the pending items.

The transaction status management device 50 is a device that mainly manages (or monitors) various devices within the LAN 19. The transaction status management device 50 manages the operating status of other devices (e.g., the registered settlement device 30, the settlement device 40, etc.), by displaying various information on the other devices and outputting various commands to the other devices.

The mobile terminal 60 is a terminal used by the customer when registering products in a self-service environment. The mobile terminal 60 is used while being held in a holder of the shopping cart 70, or while being removed from the holder of the shopping cart 70 and held in the customer's hand.

The mobile terminal 60 has a communication function, an imaging function (camera), and also a recognition function that recognizes various codes (barcodes, two-dimensional codes, etc.). For example, the mobile terminal 60 recognizes the barcode attached to a product. In other words, the mobile terminal 60 reads product identification information (product code). The mobile terminal 60 may also extract feature points in an image captured by the imaging function (an image acquired as a through image) and recognize objects (various codes).

The mobile terminal 60 is a smartphone or the like owned by the customer. The mobile terminal 60 may be owned by the store and loaned to the customer when shopping. Although two mobile terminals 60 are shown in the figure, the number of mobile terminals 60 used for product registration in the store varies depending on the number of customers.

A shopping application having a function for registering products in accordance with the self-service operation of this embodiment is installed on the mobile terminal 60.

Figure 2 shows an example of the state near the entrance of a store that has introduced the product sales data processing system 1 of this embodiment. As shown in the figure, near the entrance (or the entrance if the entrance and exit are separate), a rental shopping cart 70, rental shopping baskets 80, and sales shopping bags 90 are prepared. When a customer visits the store, they place the shopping basket 80 in the shopping cart 70, place the shopping bag 90 in the shopping basket 80, etc., and proceed inside the store. At this time, if the customer wishes to do their own shopping, they place the mobile terminal 60 in the shopping cart 70.

The customer may bring the shopping bag 90 that they purchased this time as their own bag the next time they visit the store, or may bring a different bag to use as their own bag. They may also purchase a plastic bag.

Although not shown in the figure, the shopping cart 70 is also provided with a bag for reserved items (described below) in addition to the shopping basket 80.

[Example of setting a mobile terminal in a shopping cart]
In self-operation, when a customer registers an item, the customer can use the mobile terminal 60 while it is held in a holder 71 of a shopping cart 70 (cart-held state), or can remove it from the holder 71 of the shopping cart 70 and hold it in his/her hand (hand-held state).

With reference to Figure 3, an example of how the mobile terminal 60 is set (attached) to the shopping cart 70 when a customer uses the mobile terminal 60 while holding the cart will be described. Figure 3(A) is a side view of the part of the shopping cart 70 where the mobile terminal 60 is set. Figure 3(B) is a top view of the shopping cart 70.

As shown in FIG. 3(A), a holder 71 for setting the mobile terminal 60 is attached to the shopping cart 70. The customer sets the mobile terminal 60 in the holder 71. When the mobile terminal 60 is set in the holder 71, as shown in FIG. 3(B), the image capturing unit 606 (see FIG. 5) is ready to capture an image of the entire shopping bag 90 or my bag.

[About the settlement device]
Fig. 4 is a diagram for explaining the settlement device 40. Fig. 4(A) is a diagram showing an example of the appearance of the settlement device 40 (a front view seen from the customer side). Fig. 4(B) is a diagram showing an example of the configuration of the settlement device 40. In Fig. 4(A) and Fig. 4(B), the same parts are given the same reference numerals.

Below, an example of the configuration of the settlement device 40 shown in FIG. 4(B) will be described with reference to FIG. 4(A). The settlement device 40 comprises a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a display unit 405, a scanner unit 406, a card payment unit 408, a change dispenser 409, a printing unit 413, an audio output unit 414, a communication unit 415, and an imaging unit 416 (camera). These can communicate with each other via a bus. The settlement device 40 may further include a key operation unit and an alarm unit (for example, a lamp on a sign pole, etc.).

The CPU 401 is a central processing unit, and controls the operation of the settlement device 40 by reading and executing programs stored in the ROM 402 .
The ROM 402 is a read-only memory, and stores various types of information used by the CPU 401, including programs.

RAM 403 is a read/write memory, and stores various information as a main storage device. For example, RAM 403 stores information read from ROM 402 or hard disk 404, information acquired from the outside, information generated during processing, etc.

The hard disk 404 stores various information as an auxiliary storage device. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information obtained from the outside, information generated during processing, etc. Note that a storage device such as an SSD (Solid State Drive) may be provided instead of the hard disk 404.

The display unit 405 is a touch panel that displays various information and accepts operations performed on the touch panel.

The scanner unit 406 optically reads various information. For example, the scanner unit 406 scans a code (barcode, two-dimensional code, etc.) displayed on the display unit of the mobile terminal 60 and reads information necessary for the settlement process. The scanner unit 406 may also scan a code printed on an account ticket (registered trademark) issued by another device (for example, a registered settlement device 30) and reads information necessary for the settlement process. The scanner unit 406 may also scan a code attached to a product and read the product code. The scanner unit 406 may also scan a code attached to a store clerk's name tag and read the store clerk code.

The card payment unit 408 is a payment mechanism that uses various cards (credit cards, prepaid cards such as transportation cards, cash cards for debit payments, point cards for point payments, etc.). The card payment unit 408 is equipped with a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient that it is equipped with at least the card recognition unit. The card recognition unit may recognize various cards (e.g., point cards, membership cards, shareholder cards, etc.) for the purpose of granting benefits, discounts, etc.

The change dispenser 409 (cash settlement unit) is a cash settlement mechanism that has an input port for banknotes and coins and an output port for banknotes and coins, calculates the amount of money 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. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, detecting the number of coins by denomination, etc.).

The printing unit 413 prints and issues various media (receipts, bills, etc.).
The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs audio guidance and the like.
The communication unit 415 transmits and receives information between other devices (the store controller 10, the registered settlement device 30, the other settlement devices 40, the transaction status management device 50, etc.).

The imaging unit 416 is configured to capture, for example, an image of the hands of a customer operating the change machine.

[Registered payment devices]
The registration and settlement device 30 may be configured to have a display unit and a scanner unit on each side (clerk side, customer side) and a settlement unit (card settlement unit, cash settlement unit) on one side (customer side). The registration and settlement device 30 configured in this manner may be a device that can be switched to any of a plurality of operation modes (a mode in which the registration process is executed by the operation of the clerk and the settlement process is executed by the operation of the customer, a mode in which the registration process is executed by the operation of the clerk and the customer and the settlement process is executed by the operation of the customer, etc.) depending on, for example, the operating status. Also, if the mode in which the settlement process is executed by the operation of the customer, the registration and settlement device 30 can be used for self-operation. That is, the customer can make a transaction by having the mobile terminal 60 execute the registration process and have the registration and settlement device 30 execute the settlement process.
In the following description, an example will be given in which the registration settlement device 30 is used for self-service operation.

[Example of configuration of a mobile terminal]
5 shows an example of the configuration of the portable terminal 60. The portable terminal 60 in the figure includes a CPU 601, a storage unit 602, a RAM 603, a display unit 604, an operation unit 605, an imaging unit 606, a network-compatible communication unit 607, and a sensor unit 608.

The CPU 601 is a central processing unit that controls the operation of the mobile terminal 60 by reading and executing programs stored in the storage unit 602 .
The storage unit 602 is an auxiliary storage device for the CPU 601, and stores various types of information used by the CPU 601, including programs.
The RAM 603 is a main storage device for the CPU 601 .

The display unit 604 displays an image according to the display control of the CPU 601. The display unit 604 may be configured as a touch panel that allows operations to be performed on the screen.
The operation unit 605 collectively indicates various operators provided on the mobile terminal 60 and various input devices connected to the mobile terminal 60 .

The imaging unit 606 captures images under the control of the CPU 401. In addition, the imaging unit 606 in this embodiment can also function as a part that reads two-dimensional codes in a code reader that processes two-dimensional codes.

The network-compatible communication unit 607 is a part that communicates wirelessly via a network. The network-compatible communication unit 607 enables the mobile terminal 60 to communicate with the transaction management device 20.

The sensor unit 608 collectively indicates various sensors equipped in the mobile terminal 60. The sensor unit 608 may include a motion sensor for detecting a motion state such as the attitude and traveling direction of the mobile terminal 60. The motion sensor may be configured to include a gyro sensor, an acceleration sensor, and the like.
The sensor unit 608 may also include a positioning sensor that detects its own position using a positioning device compatible with GPS, for example.

[Example of transaction management device configuration]
6 shows an example of the configuration of transaction management device 20. Transaction management device 20 in the figure includes a CPU 201, a storage unit 202, a RAM 203, and a network-compatible communication unit 204.
The CPU 201 is a central processing unit, and controls the operation of the transaction management device 20 by reading and executing programs stored in the memory unit 202 .
The storage unit 202 is an auxiliary storage device for the CPU 201, and stores various types of information used by the CPU 201, including programs.
The RAM 203 is a main storage device for the CPU 201 .
The network-compatible communication unit 204 is a part that performs communication via a network.

The memory unit 202 of the transaction management device 20 stores customer information, store information, and cart information.

[Information stored in the transaction management device]
The customer information stored in the memory unit 202 is information for managing individual customers. The transaction management device 20 generates customer information when a customer is registered (a customer may be considered to have been registered when the customer information of that customer is stored). The transaction management device 20 also updates the customer information as appropriate based on cart information, etc. The transaction management device 20 may refer to the cart information at a specified time every day, for example, and update the customer information.

7A shows an example of customer information stored in the memory unit 202 of the transaction management device 20. The customer information in the figure includes customer identification information, customer name, customer registration date, product cancellation information, customer rank, number of points, etc.
The customer identification information is identification information that uniquely identifies a customer.
As the customer identification information (or instead of the customer identification information), for example, application identification information that is uniquely (e.g., sequentially) assigned to each installed shopping application may be used. Also, as the customer identification information (or instead of the customer identification information), terminal identification information unique to the mobile terminal 60 in which the shopping application is installed may be used. The terminal identification information may be hardware identification information uniquely assigned to the hardware of the mobile terminal 60, such as a telephone number assigned to a customer who is a user of the mobile terminal 60, or a MAC (Media Access Control) address.
The customer name is the customer's name or nickname, etc. The customer registration date is the date and time when the customer was registered. Product cancellation information is information regarding cancellation of a product after it has been registered. The customer rank is a rank according to the customer's purchasing history. When generating customer information for a new customer, the customer identification information, customer name, and customer registration date are generated, but since this is before the start of actual trading (product registration), other information (product cancellation information, etc.) is not generated.

The transaction management device 20 generates and stores customer identification information, for example, when a customer is registered (for example, when the mobile terminal 60 downloads or installs a shopping application from an external device (for example, a specified server that provides general applications, the transaction management device 20) to use a shopping service provided by the transaction management device 20). In addition, the transaction management device 20 acquires information entered into the name field of a registration form (input form) using the mobile terminal 60, for example, when a customer is registered, and stores it as the customer name. In addition, the transaction management device 20 acquires the current date and time when the customer is registered, and stores it as the customer registration date.

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

7B shows an example of store information stored in the memory unit 202 of the transaction management device 20. The store information in the figure includes store identification information, store name (branch name), store specific information 1, and store specific information 2.
The store identification information is identification information for uniquely identifying a store. The store identification information shown in Fig. 7B is composed of a store (trade name) or company code and a branch code.
The store name is the name of the store. The store name shown in Fig. 7B is composed of the store (trade name) or company and the branch name.
The store identification information 1 is information on a two-dimensional code (QR code (registered trademark) or the like) for identifying a store in which a transaction takes place (a store where goods are bought and sold).
The store identification information 2 is store location information (GPS information) for identifying the store where the transaction is to be carried out.
In the example shown in FIG. 7B, the store identification information and the store specifying information 1 are different, but the store identification information and the store specifying information 1 may be the same.

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

The cart information is information for managing individual transactions. The transaction management device 20 generates the cart information at the start of a transaction. In addition, the transaction management device 20 updates the cart information as the transaction progresses (each time a product is registered) (it may be considered that a product has been registered when the product is stored in the cart information).

FIG. 7(C) is an example of cart information stored in the memory unit 202 of the transaction management device 20.
The cart information in FIG. 1 includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, and reserved product information.

The cart identification information is identification information that uniquely identifies the cart information, and includes, for example, store identification information, a date, and a serial number (for example, a serial number for each store and date).
The transaction start date and time is the date and time when the transaction starts. The transaction start date and time may be, for example, the date and time when the cart information is generated. The transaction start date and time may be the registration date and time of the first item of product (the date and time when the registered product information (registered product 1) in FIG. 7(C) is stored). The generation date and time of the cart information and the registration date and time of the first item of product may both be stored separately.

The transaction end date and time is the end date and time of the transaction. For example, the transaction start date and time may be the settlement date and time. The customer identification information is customer identification information that identifies the customer of the transaction. When the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are generated, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, etc.) is not generated. The settlement date and time may be the settlement start date and time or the settlement end date and time. Both the settlement start date and time and the settlement end date and time may be stored separately as the transaction end date and time.

Registered product information (total) is information that is updated each time a product is registered. Registered product information (total) includes the number of products (number of products), estimated subtotal amount (e.g., subtotal amount before discounts, etc. are reflected), subtotal amount, etc. Registered product information (registered product 1) is the registration information for one product item. Registered product information (registered product 2) is the registration information for two products. In the example shown in Figure 7 (C), registered product information (registered product 3) to registered product information (registered product 5) are omitted from the illustration. Registered product information (registered product N; N is an integer) includes the product code, product name (product name), price, etc.

The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management device 20 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a basis for determining whether or not to apply a service such as a time service and the effect of applying the service.

The reserved item information (total) is information that is updated each time a reserved item is registered. The reserved item information (total) includes the number of reserved items (items) of all types and the number of reserved items (items) of each type. In this embodiment, the reserved items are classified into multiple types, and each classification is managed by classification number (reserved major classification number, reserved minor classification number). In the example of FIG. 7(C), "Total number of items: 3" in the reserved item information (total) indicates that the number of items in all types (total of reserved items with reserved major classification numbers "1" to "4") is 3, "NON-FILE: 2" indicates that the number of reserved items classified as NON-FILE (total of reserved items with reserved major classification number "1") is 2, and "Read NG: 1" indicates that the number of reserved items classified as read NG (total of reserved items with reserved major classification number "2") is 1.

A NON-FILE means that the barcode or product code was successfully scanned at the store (the product code was read), but the product code has not been stored (registered) in the product file. In other words, reserved products classified as NON-FILE are reserved products whose product code was successfully scanned, but whose product code has not been stored in the product file.

A "no read" means that the product code was not successfully read (scanned) at the store. In other words, a reserved product classified as a "no read" is a reserved product whose product code was not successfully read.

Pending product information (pending product 1) is information on pending product 1. Pending product information (pending product 2) is information on pending product 2. Pending product information (pending product 3) is information on pending product 3.

The reserved product information (reserved product N; N is an integer) includes a reserved major classification number (described below). For example, if the Nth item is a reserved product classified as a NON-FILE with a reserved major classification number of "1", the reserved product information (reserved product N) includes the reserved major classification number "1 (NON-FILE)" and a product code. Also, if the Nth item is a reserved product classified as a read NG with a reserved major classification number of "2", the reserved product information (reserved product N) includes the reserved major classification number "2 (read NG)" and image data (image captured by the mobile terminal 60). Note that the reserved product information for reserved products classified as NON-FILE may include image data in addition to the reserved major classification number "1 (NON-FILE)" and the product code.

Note that the information shown in FIG. 7 is an example of information stored by the transaction management device 20, and the transaction management device 20 may store other information (e.g., a product file). Information about one product in a product file may include, for example, a product code (product identifier), product name, price, etc.

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

Step S1: The mobile terminal 60 acquires information that identifies the store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (the two-dimensional code may be output to a display screen, a medium with the two-dimensional code printed on it may be attached, etc.), and a customer visiting the store may scan (read) the two-dimensional code with the mobile terminal 60, thereby causing the mobile terminal 60 to acquire the store identification information. When a customer visiting the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer visiting the store scans the two-dimensional code with the mobile terminal 60, the shopping application may start and a screen informing the customer that they are currently connected to the transaction management device 20 may be displayed as a start-up screen.

For example, since a store is identified by its location, a customer who visits the store may obtain location information (GPS information) on the mobile terminal 60 at the store (i.e., the store's location information may be obtained as store identification information). When a customer who visits the store starts a shopping application, the location information may be obtained and a screen may be displayed as a startup screen informing the customer that the application is currently connected to the transaction management device 20. If multiple stores are detected from the location information and it is not possible to identify one, a selection screen may be displayed to allow the customer to select. Alternatively, the application may switch to a mode that forcibly obtains a two-dimensional code.

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

The destination information (address of the transaction management device 20) may also be obtained when registering the customer (when downloading or installing a shopping application to the mobile terminal 60) and stored in the memory of the mobile terminal 60. When scanning a two-dimensional code, the destination information may be converted into a two-dimensional code in addition to the store-specific information, and the mobile terminal 60 may obtain the destination information along with the store-specific information by scanning the two-dimensional code.

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

As described above, the transaction management device 20 stores store information such as that shown in FIG. 7(B), so when it receives store identification information (it also receives customer identification information) as a transaction start request from the mobile terminal 60, if the received store identification information is a two-dimensional code, it acquires the store identification information by referring to store identification information 1, and if the received store identification information is location information (GPS information), it acquires the store identification information by referring to store identification information 2. Note that if the store identification information received from the mobile terminal 60 is a two-dimensional code of the store identification information, the transaction management device 20 can simply acquire it as is.

In other words, the transaction management device 20, which receives customer identification information and store identification information from the mobile terminal 60 as a transaction start request, acquires the store identification information from the store identification information received from the mobile terminal 60, and further acquires the current date, issues (assigns) a serial number, combines the store identification information, the current date, and the serial number, and stores them as cart identification information in the cart information. Also, the transaction management device 20, which receives store identification information and customer identification information from the mobile terminal 60 as a transaction start request, acquires the current date and time, and stores them as the transaction start date and time (generation date and time) in the cart information. Also, the transaction management device 20, which receives store identification information and customer identification information from the mobile terminal 60 as a transaction start request, stores the customer identification information received from the mobile terminal 60 as customer identification information in the cart information.

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

Step S4: The mobile terminal 60 receives the cart identification information and the product registration initial screen information from the transaction management device 20, stores the cart identification information, and displays the registration screen on the display unit. Specifically, the mobile terminal 60 displays the product registration initial screen as shown in FIG. 9(B), for example.

The product registration initial screen is a product registration screen that is displayed first when product registration is started.
The product registration screen has a captured image area AR1 and a product registration result area AR2. The captured image area AR1 is an area in which a captured image obtained by imaging by the imaging unit 506 is displayed. A product code (e.g., a barcode) captured so as to fall within a predetermined range in the captured image displayed in the captured image area AR1 is to be read.
The product registration result area AR2 shows the number of registered products (registered points) and the total price for the products registered so far, and is an area in which list items corresponding to each registered product are arranged. In the case of the product registration initial screen shown in the figure, since no products have been registered yet, the product registration result area AR2 is blank with no list items arranged.

Step S5: The customer operates the mobile terminal 60 to scan the barcode attached to the product and read the product code. In the figure, it is assumed that the barcode scan was successful. Steps S5 to S9 are repeated each time a barcode attached to a product is scanned.

The mobile terminal 60 that has acquired the barcode transmits the cart identification information and the product registration information, including the product code obtained by scanning, to the transaction management device 20.

Step S6: The transaction management device 20 receives the product registration information (cart identification information and product code) from the mobile terminal 60 and identifies the cart information of the transaction from the cart identification information included in the received product registration information.

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

Step S8: After updating the product data in the cart information, the transaction management device 20 generates product registration update screen information (screen information of the product registration screen, which is an update screen to which the registered product has been added) and transmits it to the mobile terminal 60. Specifically, the transaction management device 20 generates product registration update screen information on the mobile terminal 60, for example, such that a product registration update screen is displayed on the mobile terminal 60 in which the list item Itm of the currently registered product has been added in the product registration result area AR2, as shown in FIG. 9 (C), and transmits the generated product registration update screen information to the mobile terminal 60 together with the cart identification information.

Note that the icon Icn shown in FIG. 9(C) corresponds to the fifth variant, so its description will be omitted here.

The product registration screen (product registration update screen) shown in Figure 9 (C) is displayed on the mobile terminal 60 after "XX bread" is registered as the third product item. In other words, when "XX yogurt" is stored in the cart information as the first item, the transaction management device 20 generates product registration update screen information such that "XX yogurt" is displayed as the list item Itm on the mobile terminal 60 and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal 60; when "XX chocolate" is stored in the cart as the second item, the transaction management device 20 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed as the list items Itm on the mobile terminal 60 and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal 60; when "XX bread" is stored in the cart information as the third item, the transaction management device 20 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed as the list items Itm on the mobile terminal 60 as shown in FIG. 9(C), and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal 60.

Step S9: The mobile terminal 60, which has received the cart identification information and product registration update screen information from the transaction management device 20, adds the product to the registration screen. Specifically, the mobile terminal 60 displays a product registration update screen such as that shown in FIG. 9(C). As described above, the product registration screen (product registration update screen) shown in FIG. 9(C) is displayed on the mobile terminal 60 after "XX bread" has been registered as the third product item.

Step S10: The mobile terminal 60 accepts a checkout instruction operation as a customer operation. For example, it accepts a touch of the checkout instruction button BT15 that displays "Proceed to checkout" as shown in FIG. 9 (C).

Step S11: The mobile terminal 60 that has accepted the settlement transition instruction operation generates a two-dimensional code. That is, the mobile terminal 60 converts information (e.g., cart identification information) required to execute the settlement process for the products purchased by the mobile terminal 60 into a two-dimensional code. The mobile terminal 60 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, a code screen with a two-dimensional code arranged as shown in FIG. 9(D) is displayed on the display unit.
Also, a message area AR3 is arranged on the code screen. In this case, the message area AR3 displays a message such as "Please read the following code with the settlement machine" to guide the customer to have the scanner unit 406 of the settlement device 40 read the code on the code screen.

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

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

Step S14: The transaction management device 20 receives the cart identification information and the sub-calculation output request information from the mobile terminal 60 and identifies the cart information of the transaction from the cart identification information.

Step S15: After identifying the cart, the transaction management device 20 calculates the subtotal amount using information such as the price in the registered product information included in the cart information corresponding to the identified cart information.

Step S16: Having calculated the subtotal, the transaction management device 20 updates the cart information (stores the subtotal (calculated subtotal)) and transmits the subtotal information indicating the calculated subtotal together with the cart identification information (which may also be cart information) to the settlement device 40.

Here, the subtotal information and cart identification information (or cart information) included in the settlement information may be information (settlement screen information) that the settlement device 40 uses to display the settlement screen.

Step S17: The settlement device 40, which has received the cart identification information (or cart information) and subtotal information from the transaction management device 20, displays the subtotal amount (settlement screen) on the display unit 405.

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

[Regarding product registration for plastic shopping bags]
When a store provides bags (hereinafter referred to as "plastic bags") for customers to pack their purchased items for a fee, the store treats the plastic bag as one of the products. In this case, a product code is attached to the plastic bag by printing it or attaching a sticker, etc. When a customer purchases a plastic bag while shopping, the customer registers the product by having the mobile terminal 60 read the code on the plastic bag in the same way as other products to be purchased.

However, customers often forget to register the shopping bag as a product. If a customer who intended to purchase a shopping bag forgets to register the shopping bag as a product, the customer will simply perform a payment transition instruction operation to have the payment device 40 read the two-dimensional code displayed on the code screen, causing the payment device 40 to start payment. In this way, when the customer realizes that they forgot to register the shopping bag after the payment device 40 has started payment, the product registration details for the corresponding transaction have been confirmed.
For this reason, if a customer wishes to purchase a plastic bag in this transaction, the customer will call a store clerk, for example, by performing a specific operation on the settlement screen displayed on the settlement device 40. Then, the store clerk who responds to the call will go to the settlement device 40 and include the plastic bag in the registered goods by performing a special operation that only a store clerk can perform, such as correcting the transaction. In this case, in order to register the plastic bag that the customer forgot to register, the store clerk must call the store clerk and the store clerk must correct the transaction in response to the call. While the plastic bag is being registered in this way, the settlement device 40 is unnecessarily occupied, disrupting the flow of the transaction at the store.
Therefore, in this embodiment, as described below, the customer is notified that the product registration of the shopping bag has not been completed before the settlement is started at the settlement device 40.

In this embodiment, when the customer determines that they have finished registering all the products to be purchased and performs a checkout instruction operation on the mobile terminal 60 (operation of the checkout instruction button BT15), the mobile terminal 60 determines whether or not a shopping bag has been registered for this product registration (terminal shopping bag registration determination).

The following three examples can be given as examples of terminal plastic bag registration judgments.
As a first example of the terminal plastic bag registration determination, mobile terminal 60 may send a plastic bag registration inquiry to transaction management device 20 to inquire whether a plastic bag has been registered. The plastic bag registration inquiry includes cart identification information corresponding to the current transaction. Transaction management device 20 determines whether a plastic bag has been registered based on whether registered product information for the plastic bag is included in the cart information indicated by the cart identification information included in the received plastic bag registration inquiry, and sends the determination result to mobile terminal 60. Mobile terminal 60 determines whether the plastic bag has been registered based on the received determination result.

As a second example of terminal plastic bag registration determination, the mobile terminal 60 stores product registration information corresponding to each product registration performed in response to the current transaction. Then, when the product type is indicated for each stored product registration information, the mobile terminal 60 may determine whether or not a plastic bag has been registered based on the product type indicated by the product registration information.

For example, the mobile terminal 60 may store the product registration information corresponding to the read product code without transmitting it, as in the second example of the plastic bag registration determination described above, instead of transmitting the product registration information on a product-by-product basis each time a product code is read as shown in FIG. 8. Then, the mobile terminal 60 may transmit all the product registration information stored up to that point in response to, for example, a payment transition instruction operation being performed.

As a third example of the terminal plastic bag registration determination, when the code pattern of the read product code corresponds to a plastic bag during product registration, the mobile terminal 60 may store a plastic bag registration flag indicating that a plastic bag is included in the registered products. Then, in response to a checkout transition instruction operation being performed, the mobile terminal 60 may determine whether a plastic bag has been registered based on whether the plastic bag registration flag has been stored.

If the mobile terminal 60 determines that the plastic bag has been registered as a result of the plastic bag registration determination, the mobile terminal 60 displays the code screen shown in FIG. 9 (C) in response to the payment transition instruction operation.

On the other hand, if the mobile terminal 60 determines that the plastic bag has not been registered as a result of the plastic bag registration determination, the mobile terminal 60 displays a plastic bag purchase confirmation screen instead of the code screen (FIG. 9(C)) in response to a checkout transition instruction operation. The plastic bag purchase confirmation screen is a screen that asks the customer whether or not they wish to purchase a plastic bag, assuming that the customer may have forgotten to register the product as a plastic bag.

10 shows an example of a shopping bag purchase confirmation screen. A message area AR6 is arranged on the shopping bag purchase confirmation screen in the figure. In the message area AR6, a message is displayed to inform the customer that the shopping bag is not registered as a product, and to guide the customer on how to operate the shopping bag purchase confirmation screen.
The shopping bag purchase confirmation screen has a "Purchase" button BT41 and a "Proceed to Checkout" button BT42. If the customer wishes to purchase a shopping bag, the customer operates the "Purchase" button BT41, and if not, the customer operates the "Proceed to Checkout" button BT42.

When the "Purchase" button BT41 is operated, the mobile terminal 60 returns to a state in which product registration according to the current transaction is possible. That is, in response to the operation of the "Purchase" button BT41, the mobile terminal 60 in this case invalidates the previous settlement transition instruction operation and returns to a state in which product registration according to the current transaction is possible. In this case, the display unit 604 of the mobile terminal 60 returns to a state in which the product registration screen (FIG. 9(C)) is displayed. At this time, the product registration result area AR2 of the product registration screen is in a state in which the product registration result at the time the settlement transition instruction operation was performed is carried over.
This allows the customer to register the shopping bag by having the mobile terminal 60 read the product code attached to the shopping bag. In this case, if the customer wishes to register an additional product other than the shopping bag, the customer can register the product by having the mobile terminal 60 read the product code of the product. After completing the product registration in this manner, the customer can again perform the checkout transition instruction operation.
On the other hand, when the “Proceed to Checkout” button BT42 is operated, the mobile terminal 60 displays the code screen (FIG. 9(C)).

With this configuration, if a cashier instruction operation is performed without registering a shopping bag as an item, a shopping bag purchase confirmation screen will be displayed. As a result, if a customer who intended to purchase a shopping bag forgets to register the shopping bag as an item, for example, the customer can return to registering the shopping bag as an item, eliminating the need to call a store clerk at the payment device 40 to correct the transaction.

[Example of processing procedure]
An example of a process procedure executed by the mobile terminal 60 of this embodiment in response to a settlement transition instruction operation will be described with reference to the flowchart of FIG.
Step S101: During product registration, the mobile terminal 60 waits for a payment transition instruction operation to be performed.

Step S102: When the checkout transition instruction operation is performed, the mobile terminal 60 determines whether or not a plastic bag has been registered for this transaction by a plastic bag registration determination. In this step S102, the mobile terminal 60 may perform a terminal plastic bag registration determination by any of the first to third examples as described above.

Step S103: When it is determined in step S102 that the plastic bag is not registered as a product, the mobile terminal 60 displays a plastic bag purchase confirmation screen on the display unit 604.
Step S104: The operation on the shopping bag purchase confirmation screen is either an operation on the "Purchase" button BT41 (purchase declaration operation) or an operation on the "Proceed to checkout" button BT42 (non-purchase declaration operation). While the shopping bag purchase confirmation screen is displayed, the mobile terminal 60 determines whether the purchase declaration operation has been performed, out of the purchase declaration operation and the non-purchase declaration operation.

Step S105: If it is determined in step S104 that the purchase declaration operation has been performed, the mobile terminal 60 returns to a state in which product registration is possible.
Step S106: If it is determined in step S104 that the non-purchase declaration operation has been performed, the mobile terminal 60 displays a code screen.

Second Embodiment
Next, a second embodiment will be described. In this embodiment, the mobile terminal 60 displays a code screen in response to a checkout transition instruction operation, regardless of whether the plastic bag has been registered. In this embodiment, the checkout device 40, which reads the two-dimensional code on the code screen of the mobile terminal 60, performs a checkout bag registration determination (pre-checkout plastic bag registration determination) at a stage before production begins. If the checkout device 40 determines that the plastic bag has not been registered as a product as a result of the pre-checkout plastic bag registration determination, it causes the display unit 405 to display a plastic bag purchase confirmation screen. In this case, a customer who has forgotten to register a plastic bag can perform checkout by operating the plastic bag purchase confirmation screen displayed on the checkout device 40 to include the product registration of the plastic bag in the current transaction.

FIG. 12 shows an example of a processing procedure that the settlement device 40 of this embodiment executes in response to product registration of a shopping bag.
Step S201: When a customer who wishes to settle their account now performs an operation that causes the settlement device 40 to read the two-dimensional code on the code screen displayed on the mobile terminal 60, the settlement device 40 reads the two-dimensional code.
Step S202: In response to the settlement device 40 reading the two-dimensional code, the process of steps S13 to S17 in Fig. 8 is executed. As a result, the settlement device 40 causes the display unit 405 to display a settlement screen reflecting the product registration results in the cart information corresponding to this transaction.

Step S203: Next, the settlement device 40 executes a pre-settlement plastic bag registration determination. In other words, it determines whether a plastic bag has already been registered for this transaction.

When determining whether to register a plastic bag, the settlement device 40 may perform a pre-payment plastic bag registration determination according to any of the following first to third examples.
As a first example of determining whether a plastic bag is registered before checkout, settlement device 40 may send a plastic bag registration inquiry to transaction management device 20. In response to the plastic bag registration inquiry, transaction management device 20 sends a response to settlement device 40 indicating whether the plastic bag is registered or not, depending on whether product registration information for the plastic bag is present in the cart information of the corresponding transaction. Settlement device 40 may determine whether the plastic bag is registered or not based on the content of the received response.

As a second example of determining whether a plastic bag has been registered before checkout, the checkout device 40 may determine whether a plastic bag has been registered based on the checkout screen information sent from the transaction management device 20 and used to display the checkout screen in step S202. Such checkout screen information may be, for example, page information written in a specified markup language or cart information.

As a third example of the pre-payment plastic bag registration determination, the mobile terminal 60 performs the plastic bag registration determination according to, for example, the above-mentioned second or third example. Then, when generating a two-dimensional code to be displayed on the code screen, the mobile terminal 60 includes information indicating whether or not the plastic bag is registered (plastic bag registration determination information) in the two-dimensional code.
The settlement device 40 may determine whether or not the plastic bag is registered depending on whether or not the two-dimensional code read in step S201 includes plastic bag registration determination information.
If it is determined in step S203 that the shopping bag has been registered, the process in the figure ends and payment is made according to the customer's operation.

Step S204: If it is determined in step S203 that the plastic bag has not been registered, the settlement device 40 displays a plastic bag purchase confirmation screen so as to superimpose it on the settlement screen displayed in step S202.

FIG. 13 shows an example of a shopping bag purchase confirmation screen P60 displayed on the payment device 40.
The plastic bag purchase confirmation screen P60 in the figure is in a window format displayed superimposed on the checkout screen. In this case, the checkout screen is displayed in the background of the plastic bag purchase confirmation screen P60. However, the plastic bag purchase confirmation screen P60 may be displayed using the entire display surface of the display unit 405, for example. In this case, the checkout screen is not displayed in the background.

In the shopping bag purchase confirmation screen P60 in the figure, a message area AR61 is arranged. In the message area AR61, a message is displayed instructing the customer to operate the shopping bag registration operation area AR62 in the shopping bag purchase confirmation screen P60 if they intend to purchase a shopping bag (register the product), and to operate the cancel button BT65 if they do not intend to purchase one.

In the plastic bag registration operation area AR62, a plus button BT61 and a minus button BT62 are provided for each size of plastic bag (large plastic bag, medium plastic bag, small plastic bag). Customers can specify the number of plastic bags to be registered by operating the plus button BT61 and the minus button BT62 for each size of plastic bag required. The price of plastic bags according to the number specified for each size of plastic bag is shown in the total amount area AR63.
After designating the plastic bag as described above, the customer operates the Confirm button BT64 (operation to confirm the registration of the plastic bag). In response to the operation of the Confirm button BT64, the registration of the plastic bag based on the size and number inputted in the plastic bag registration operation area AR62 is confirmed.

Returning to FIG.
Step S205: While the plastic bag purchase confirmation screen P60 is being displayed, the settlement device 40 determines whether or not a plastic bag registration confirmation operation has been performed.

Step S206: If it is determined in step S205 that the plastic bag registration confirmation operation has been performed, the settlement device 40 executes a plastic bag registration process. As part of the plastic bag registration process, the settlement device 40 transmits a plastic bag additional registration request to the transaction management device 20. The plastic bag additional registration request includes product registration information indicating the number of plastic bags of each size that was input in the plastic bag registration operation area AR62 when the plastic bag registration confirmation operation was performed.
The transaction management device 20 updates the product registration information included in the received request to add a shopping bag to the cart information corresponding to the current transaction. The transaction management device 20 transmits settlement screen information based on the updated product registration information to the settlement device 40. The settlement device 40 receives the transmitted settlement screen information.

Step S207: Following the plastic bag registration process, the settlement device 40 erases the plastic bag purchase confirmation screen P60.
Step S208: The settlement device 40 updates the display of the settlement screen using the settlement screen information received in the plastic bag registration process in step S205. The settlement screen updated in this way has content that reflects the product registration results of the plastic bag.

Step S209: If the user operates the cancel button BT65 without performing the operation to confirm the registration of the plastic bag in step S205, the settlement device 40 clears the plastic bag purchase confirmation screen. This causes the display unit 405 of the settlement device 40 to return to displaying the settlement screen corresponding to the previous step S202.

<Modification>
Modifications of the present embodiment will be described below. The modifications described below may be combined with the above embodiment and other modifications as appropriate.

[First Modification]
The registration of a plastic bag by a customer is not limited to having the product code attached to the plastic bag read by the mobile terminal 60. For example, a product registration button corresponding to the plastic bag may be provided on the product registration screen displayed on the mobile terminal 60, and the plastic bag may be registered in response to an operation performed on the product registration button.

[Second Modification]
During product registration using the mobile terminal 60, operations on the product registration screen can be used to delete registered products and change the registered quantity.
FIG. 14 shows an extracted product registration result area AR2 on the same product registration screen as shown in FIG. 9(C).
As shown in FIG. 14, the product registration result area AR2 is arranged with an estimate area AR21 and a registration list area AR22. The estimate area AR21 shows the number of registered products (registered number) and the total amount according to the products registered so far, and also shows a settlement transition instruction button BT15. The registration list area AR22 is an area where list items Itm corresponding to each registered product are arranged. A quantity area 221 is arranged in each list item Itm. The quantity area AR221 is an area showing the registered quantity (registered quantity) of the corresponding product. The quantity area AR221 also functions as a button for performing an operation to instruct the display of a product registration change screen, which will be described next.

When the quantity area AR221 in one list item Itm is operated in the product registration result area AR2 shown in FIG. 14, a product registration change screen is displayed. The product registration change screen is a screen where operations are performed to change the registered quantity of the product corresponding to the list item Itm that includes the operated quantity area AR221, cancel the registration, and otherwise change the registered details.

Figure 15 shows an example of a product registration change screen P30 that is displayed in response to operation of the quantity area AR221 in the product registration result area AR2 as described above. The product registration change screen P30 in the figure shows an example in the form of a pop-up screen that is displayed superimposed on the product registration screen.

The product registration change screen P30 in the figure is displayed in response to selecting the list item Itm for the "XX Chocolate" product from among the three list items Itm in the product registration result area AR2 in the figure. In this case, in the product registration result area AR2, the two list items Itm for products other than "XX Chocolate" are grayed out, indicating that they are not available for selection, and the list item Itm for "XX Chocolate" is not grayed out, indicating that it is available for selection.

The product registration change screen P30 is arranged with a cancel button BT31, a quantity/price area AR30, a plus button BT32-1, and a minus button BT32-2.
The cancel button BT31 is a button that is operated to cancel the registration of the target product. When the cancel button BT31 is operated, if the registered quantity of the target product is two or more, the entire registered quantity is cancelled.
The quantity/price area AR30 indicates the registered quantity of the target product corresponding to the current time and the price according to the registered quantity.
The plus button BT32-1 is a button that is operated when making a change to increase the registered quantity of a target product. Each time the plus button BT32-1 is operated, the registered quantity is changed to increase by one.
The minus button BT32-2 is a button that is operated when making a change to decrease the registered quantity of the target product. Each time the minus button BT32-2 is operated, the registered quantity is changed to decrease by one.
In response to a change in the registered quantity by operating the plus button BT32-1 or the minus button BT32-2, the registered quantity and price in the quantity-price area AR30 are changed.

Note that decreasing the registered quantity in response to the operation of the minus button BT32-2 may also be treated as canceling the product. In other words, when the registered quantity of a registered product is decreased, the product corresponding to the decreased quantity may be treated as being canceled.

When the product registration change screen P30 is displayed, for example, if the list item Itm corresponding to the target product is operated, the product registration change screen P30 is cleared and the product registration screen is returned to being displayed.

When canceling the entire quantity of the target product (cancelling the registration), the customer operates the cancel button BT31. When the cancel button BT31 is operated, for example, the product registration change screen P30 is cleared and a confirmation screen is displayed. If the customer is happy to proceed with the cancellation, they perform a cancel instruction operation on the confirmation screen (for example, by operating the execute button). In response to the cancel instruction operation being performed, the confirmation screen is cleared and the display returns to the product registration screen. In this case, although not shown in the figure, in the product registration screen displayed after the confirmation screen is cleared, the list item Itm of the "XX Chocolate" product that was selected for cancellation has been cleared.

Some products sold in stores may be set as set products. Set products are multiple products that meet certain conditions to be part of a set. Set sales are when a set of such set products is sold with special benefits such as discounts or prizes.
One example of the use of set products is when a specific number (or more than a certain number) of products of the same item are purchased as a set, a special benefit is given to the set.
Another example of the use of set products is when a set of a specified number of products is selected from a number of products that have been determined in advance as eligible products and purchased, a special benefit is given to the set.
Another example of set product management is that when a set of multiple pre-specified products is purchased, a special benefit is given to the set.
Set sales of set-compatible products, including those used as described above, may be referred to as bundles, set matches, mix matches, etc., depending on the use.

FIG. 16A shows an example of the appearance of the product registration result area AR2 when set compatible products are registered in a state where they form a set.
In the product registration result area AR2 in the figure, two list items Itm corresponding to each product of the same item "Chocolate Cookie" are arranged. In other words, in this case, it is shown that two products of the same "Chocolate Cookie" are registered. The "Chocolate Cookie" product is a set compatible product that is discounted when purchased as a set of two.
In this case, in each of the two list items Itm corresponding to the product "Chocolate Cookies," the list price of "¥298" is struck through and the discounted price of "¥275" is displayed, indicating that a discount has been applied in accordance with the sale of the set.
In addition, in the list item of the set compatible products, a set compatible product display area AR222 is arranged. The set compatible product display area AR222 indicates that the corresponding product is a set compatible product by displaying, for example, "bulk discount" as shown in the same figure. When a tap operation is performed on the set compatible product display area AR222, a screen such as a pop-up window showing information such as the conditions for selling the corresponding set compatible product is displayed, although not shown in the figure.

In the state shown in the figure, the customer decides to purchase only one "Chocolate Cookie" rather than a set of two. In this case, the customer will delete the registration of one of the two "Chocolate Cookie" products. The customer then operates the quantity area AR221 of one of the two list items Itm corresponding to the two "Chocolate Cookie" products to display the product registration change screen P30.

FIG. 16(B) shows an example of a product registration change screen P30 that is displayed in response to operating the first list item Itm from the top in FIG. 16(A).
The product registration change screen P30 in the figure has a cancel button BT31 and a quantity/price area AR30 arranged therein, but does not have the plus button BT32-1 and minus button BT32-2 arranged therein on the product registration change screen P30 in FIG.
For set-compatible products, the number of items is set as a condition for completing the set. For this reason, changing the registered quantity is meaningless as a registration change for set-compatible products that have already been registered, and it is sufficient if the registration can be deleted. For this reason, it can be said that there is no need for controls (plus button BT32-1 and minus button BT32-2) for changing the registered quantity on the product registration change screen P30 for set-compatible products. In addition, if such controls for changing the registered quantity were provided, it could confuse customers.
Therefore, in this modified example, as shown in FIG. 16(B), the buttons for changing the registration quantity (the plus button BT32-1 and the minus button BT32-2) are not provided on the product registration change screen for set products.

[Third Modification]
When the plastic bag has been registered as a product, a display indicating that the plastic bag has been registered as a product may be displayed on the product registration screen of the mobile terminal 60. As an example of such a display, as shown in Fig. 9(C), an icon Icn indicating that the plastic bag has been registered as a product may be displayed in a position in the captured image area AR1 that does not interfere with the product registration operation. Alternatively, a display may be performed such that a list item Itm for the plastic bag is constantly arranged at the top row in the product registration result area AR2.

[Fourth Modification]
Some customers may decide to use their own bags (my bags) instead of plastic bags when shopping. Such customers may feel annoyed when the plastic bag purchase confirmation screen is displayed as in each of the above embodiments.
Therefore, for example, a customer who is registered as a member of a store may be able to register that he or she is a "my bag user" in the customer (member) information. The customer may be able to register that he or she is a "my bag user" by using a customer information registration/change function of the shopping application.
The product sales data processing system of this embodiment may be configured so that, for customers who have registered as “my bag users,” the shopping bag purchase confirmation screen is not displayed on the mobile terminal 60 or the payment device 40.

In order to prevent the purchase confirmation screen from being displayed in accordance with the first embodiment, the transaction management device 20 may transmit information indicating whether or not the customer is a "my bag user" (my bag use information) to the mobile device 60 during the period from when the mobile device 60 is started and product registration is started until the checkout transition instruction operation is performed. If the received my bag use information indicates that the customer is a "my bag user," the mobile device 60 will not display the shopping bag purchase confirmation screen.
In order to prevent the purchase confirmation screen from being displayed in accordance with the second embodiment, for example, in the process of step S202 in Fig. 12, when the settlement device 40 receives information for displaying the settlement screen from the transaction management device 20, the settlement device 40 may also receive the my-bag use information of the corresponding customer. If the received my-bag use information indicates that the customer is a "my-bag user," the settlement device 40 will not display the shopping bag purchase confirmation screen.

[Fifth Modification]
When product registration begins, for example, the mobile terminal 60 may display a screen (my bag use confirmation screen) asking the customer whether or not they will use their own bag for shopping, and if the customer performs a confirmation operation on the my bag use confirmation screen to indicate that they will use their own bag, the shopping bag purchase confirmation screen may not be displayed thereafter.

[Sixth Modification]
As a modification of the first embodiment, a plastic bag registration determination may be made periodically at a predetermined timing from the start of product registration until the payment transition instruction operation is performed to determine whether or not a plastic bag is included among the products registered so far. The timing of the plastic bag registration determination may be, for example, at a fixed time interval or when product registration for one item is performed.

[Seventh Modification]
If it is desired not to display the plastic bag purchase confirmation screen due to store circumstances, operation, etc., the display function of the plastic bag purchase confirmation screen may be set to be disabled for transactions at that store. The setting of enabling/disabling the display function of the plastic bag purchase confirmation screen may be performed, for example, in the store information stored in the transaction management device 20.

[Eighth Modification]
In the product sales data processing system of this embodiment, for example, the mobile terminal 60 may communicate with a payment server corresponding to various cashless payments, so that the customer can settle the payment without using a settlement device. In this case, for example, after completing product registration, the customer performs an operation on the mobile terminal 60 to instruct a shift to a specified cashless payment (a payment shift instruction operation). In response to the payment shift instruction operation, the mobile terminal 60 communicates with the payment server of the specified cashless payment and makes the payment. Here, the type of cashless payment used by the customer may be registered in advance, for example, by an operation on a shopping application, or the customer may perform a specified operation at the stage of the payment shift instruction operation.

[Ninth Modification]
In the above embodiment, a part of the processing executed by the mobile terminal 60 may be executed by, for example, the transaction management device 20, the registration and settlement device 30, the settlement device 40, the transaction status management device 50, the store controller 10, other higher-level devices in the store, or server devices on the cloud. Similarly, a part of the processing executed by each of the transaction management device 20, the registration and settlement device 30, the settlement device 40, the transaction status management device 50, the store controller 10, etc. may also be executed by other devices.
As one of the above-mentioned aspects, the product sales data processing system of the present embodiment may be provided with a thin client system configuration. As an example, the transaction management device 20 or another server may be configured as a thin client-compatible server device (e.g., a cloud server), and the mobile terminal 60 or the like may function as a thin client terminal.
In this case, for example, the cloud server may execute the plastic bag registration determination in response to a request, inquiry, etc. from the mobile terminal 60.
In addition, the transaction management device 20, transaction status management device 50, store controller 10, etc. may be configured to be distributed across multiple computer devices or servers.

<Overview of the embodiment>
[Technical field]
The present invention relates to a product sales data processing system, a terminal device, a settlement device, and a program.
[Background Art]
2. Description of the Related Art There is known a system in which a customer can register products using a mobile terminal and can then settle the account for the registered products at a settlement device (see, for example, Patent Document 1).
[Prior Art Literature]
[Patent Documents]
[Patent Document 1] JP 2018-55700 A [Summary of the Invention]
[Problem to be solved by the invention]
There are cases where a customer completes product registration using a mobile terminal and starts payment at the payment device, but then realizes that they forgot to register a specific product, such as a plastic bag. In such cases, an additional step is required, where the customer calls a store clerk, who then corrects the transaction to add a plastic bag to the payment.
The present invention has been made in consideration of the above circumstances, and has an object to make it possible to notify a customer at an appropriate time that a specific product has not been registered.

[Means for solving the problems]
(1) As described above, one aspect of this embodiment is a product sales data processing system (1) that includes a terminal device (e.g., a mobile terminal 60) used to register products, and a settlement device (40) that performs settlement corresponding to the products registered by the terminal device, the product sales data processing system including: a registration means that registers products in response to use of the terminal device; a determination means that determines whether a specific product (e.g., a plastic bag) has been registered by the registration means; and an information output means that, when it is determined by the registration means that the specific product has not been registered, outputs information corresponding to the fact that the specific product has not been registered (e.g., a plastic bag purchase confirmation screen).

According to the above configuration, if the customer has not registered the product for the plastic bag, a plastic bag purchase confirmation screen is displayed on the mobile terminal 60 or the settlement device 40.
In this way, for example, a customer who intended to purchase a shopping bag but forgot to register the product can realize that they had forgotten to register the product before moving on to the payment stage. In other words, with the above configuration, it is possible to notify the customer at an appropriate time that a specific product has not been registered.

(2) One aspect of this embodiment is the product sales data processing system described in (1), which includes a declaration means (e.g., a payment transition instruction button BT15) for declaring that a payment corresponding to the product registered by the registration means will be made, the determination means determines whether the specific product has been registered in response to the declaration made by the declaration means, and the information output means includes a confirmation means (e.g., a "Purchase" button BT41 and a "Proceed to checkout" button BT42 on a shopping bag purchase confirmation screen) for confirming whether or not the specific product needs to be registered.

According to the above configuration, if a shopping bag has not been registered as a product when a customer has finished registering the product and performed a checkout instruction operation, the customer is notified that the shopping bag has not been registered as a product, and it is possible to further confirm whether or not the customer intends to purchase a shopping bag. Notification at the checkout instruction operation is efficient in that it provides only one opportunity to notify the customer.

(3) One aspect of this embodiment is the product sales data processing system described in (2), which includes a transition means (e.g., step S105) that, in response to the confirmation means confirming that registration of the specific product is necessary, invalidates the declaration of settlement made by the declaration means and transitions to a state in which the product can be registered by the registration means.

According to the above configuration, if it is confirmed that the customer intends to purchase a plastic bag, the payment transition instruction issued by the payment transition instruction operation can be invalidated, and the state can be restored to one in which product registration is possible. This allows the customer to register the product of a plastic bag and include it in the current transaction.

(4) One aspect of this embodiment is the product sales data processing system described in (1), which includes a settlement instruction information output means for outputting settlement instruction information (e.g., a two-dimensional code on a code screen) that instructs a settlement device to make a settlement corresponding to the product registered by the registration means in response to the declaration means declaring that settlement will be performed, and when the determination means determines that the specific product is not registered in response to obtaining the settlement instruction information output by the settlement instruction information output means, the information output means causes the settlement device to display a registration screen (e.g., a shopping bag purchase confirmation screen P60) on which the specific product can be registered as information corresponding to the specific product not being registered.

According to the above configuration, if a plastic bag has not been registered, when the customer issues a payment transition instruction and goes to the payment device 40, the plastic bag purchase confirmation screen P60 is displayed before the customer starts payment at the payment device 40, and the customer can register the product of the plastic bag before making payment.

(5) One aspect of this embodiment is a terminal device used to register products in a product sales data processing system, the terminal device comprising: a registration means for registering products; a determination means for determining whether a specific product has been registered by the registration means; and an information output means for displaying information corresponding to the fact that the specific product has not been registered when the registration means determines that the specific product has not been registered.

(6) One aspect of this embodiment is a settlement device in a product sales data processing system that includes a terminal device used to register products and a settlement device that performs settlement corresponding to the products registered by the terminal device, the settlement device including a determination means that determines whether a specific product is registered in response to a declaration that settlement corresponding to the registered product will be performed in response to use of the terminal device, and an information output means that outputs information corresponding to the fact that the specific product is not registered when it is determined that the specific product is not registered.

(7) One aspect of this embodiment is a program for causing a computer serving as a terminal device used to register products in a product sales data processing system to function as a registration means for registering products, a determination means for determining whether a specific product has been registered by the registration means, and an information output means for displaying information corresponding to the fact that the specific product has not been registered when the registration means determines that the specific product has not been registered.

(8) One aspect of this embodiment is a program for causing a computer serving as a settlement device in a product sales data processing system, which includes a terminal device used to register products and a settlement device that performs settlement corresponding to the products registered by the terminal device, to function as a determination means for determining whether a specific product is registered in response to a declaration that settlement corresponding to the registered product will be performed in response to use of the terminal device, and as an information output means for outputting information corresponding to the fact that the specific product is not registered when it is determined that the specific product is not registered.

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

1 Product sales data processing system, 10 Store controller, 20 Transaction management device, 40 Payment device, 50 Transaction status management device, 60 Mobile terminal, 70 Shopping cart, 71 Holder, 80 Shopping basket

Claims (5)

A product sales data processing system including a portable terminal device that is used by a customer to register products while moving around a store , and a payment device that performs payment corresponding to the products registered by the terminal device,
A registration means for registering products in response to use of the terminal device;
a determination means for determining whether a specific product is registered by the registration means;
an information output means for outputting information corresponding to the fact that the specific product is not registered when the registration means determines that the specific product is not registered;
a declaration means for declaring that a payment corresponding to the product registered by the registration means will be made;
a settlement instruction information output means for outputting settlement instruction information for instructing a settlement device to carry out a settlement corresponding to the product registered by the registration means in response to the declaration by the declaration means that a settlement will be carried out,
When the determination means determines that the specific product is not registered in response to acquiring the settlement instruction information output by the settlement instruction information output means, the information output means displays, on the settlement device, a registration screen on which the specific product can be registered, as information corresponding to the fact that the specific product is not registered.
Product sales data processing system. A portable terminal device used by a customer to register products while moving around a store in a product sales data processing system,
A registration means for registering a product;
a determination means for determining whether a specific product is registered by the registration means;
and an information output means for displaying, when the registration means determines that the specific product is not registered, information corresponding to the fact that the specific product is not registered. A payment device in a product sales data processing system including a portable terminal device that is used by a customer to register products while moving around a store , and a payment device that performs payment corresponding to the products registered by the terminal device,
a determination means for determining whether a specific product is registered in response to a declaration of settlement corresponding to the registered product in response to use of the terminal device;
an information output means for outputting information corresponding to the fact that the specific product is not registered when it is determined that the specific product is not registered ;
When the terminal device declares that a settlement corresponding to the registered product will be made and the terminal device acquires settlement instruction information outputted by the terminal device as information instructing a settlement device to make a settlement corresponding to the registered product, the information output means displays a registration screen on which the specific product can be registered as information corresponding to the fact that the specific product is not registered, when the determination means determines that the specific product is not registered.
Clearing device. A computer as a portable terminal device used by a customer to register products while moving around a store in a product sales data processing system,
a registration means for registering the product;
a determination means for determining whether a specific product has been registered by the registration means;
A program for causing the program to function as an information output means for displaying information corresponding to the fact that the specific product is not registered when the registration means determines that the specific product is not registered. A computer as a settlement device in a product sales data processing system including a portable terminal device that is used by a customer to register products while moving around a store , and a settlement device that performs settlement corresponding to the products registered by the terminal device,
a determination means for determining whether or not a specific product is registered in response to a declaration of settlement corresponding to the registered product in response to use of the terminal device;
an information output means for outputting information corresponding to the fact that the specific product is not registered when it is determined that the specific product is not registered, and when the determination means determines that the specific product is not registered in response to acquisition of settlement instruction information output by the terminal device as information instructing a settlement device to make a settlement corresponding to the registered product due to a declaration of settlement corresponding to the registered product being made by the terminal device, the information output means displays a registration screen on which the specific product can be registered as information corresponding to the fact that the specific product is not registered.
A program to function as a

Images