Item sales data processing system, program, monitoring device, and server

Abstract

To enable an item sales data processing system in which customers themselves register items using mobile terminals to efficiently resolve inadequate item registration results.SOLUTION: An item sales data processing system for registering items based on item registration operation by a customer using a portable terminal device includes: acquisition control means for allowing a monitoring device used by a clerk to acquire registration defective item information concerning a defective item for which the registration result is defective when the registration result of the item based on the item registration operation is defective; display control means for displaying on the monitoring device a screen based on the registration defective item information acquired by the acquisition control means; and normal registration means for registering the registration defective item as a normal item in response to an input of registration complementary information to the displayed screen.SELECTED DRAWING: Figure 14

Description

Technical Field

[0001] The present invention relates to a product sales data processing system, a program, a monitoring device, and a server device.

Background Art

[0002] A system in which customers themselves register products using mobile terminals is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a product sales data processing system in which customers themselves register products using mobile terminals, the registration result of a product may be incomplete. For a product with an incomplete registration result, for example, the incomplete state of the registration result is eliminated by the operation of a store clerk. It is preferable that such elimination of the incomplete state of the registration result be performed efficiently.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to enable the elimination of an incomplete state of a product registration result to be performed efficiently in a product sales data processing system in which customers themselves register products using mobile terminals.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-described problems is a product sales data processing system that registers a product based on a product registration operation by a customer using a mobile terminal device. When the registration result of the product based on the product registration operation is incomplete, acquisition control means causes a monitoring device used by a store clerk to acquire registration incomplete product information regarding the registration incomplete product whose registration result is incomplete, display control means causes the monitoring device to display a screen based on the registration incomplete product information acquired by the acquisition control means, and normal registration means that performs normal registration to register the registration incomplete product as a normal product in response to registration completion information being input to the displayed screen. The product sales data processing system is provided with these components.

[0007] Also, one aspect of the present invention is a program for causing a computer in a product sales data processing system that registers a product based on a product registration operation by a customer using a mobile terminal device to function as acquisition control means for causing a monitoring device used by a store clerk to acquire registration incomplete product information regarding a registration incomplete product whose registration result is incomplete when the registration result of the product based on the product registration operation is incomplete, display control means for causing the monitoring device to display a screen based on the registration incomplete product information acquired by the acquisition control means, and normal registration means for performing normal registration to register the registration incomplete product as a normal product in response to registration completion information being input to the displayed screen.

[0008] Also, one aspect of the present invention is a monitoring device used by a store clerk in a product sales data processing system that registers a product based on a product registration operation by a customer using a mobile terminal device. When the registration result of the product based on the product registration operation is incomplete, acquisition means for acquiring registration incomplete product information regarding the registration incomplete product whose registration result is incomplete, display control means for displaying a screen based on the registration incomplete product information acquired by the acquisition means, and normal registration means for performing normal registration to register the registration incomplete product as a normal product in response to registration completion information being input to the displayed screen. The monitoring device is provided with these components.

[0009] Also, one aspect of the present invention is a program for causing a computer as a monitoring device used by a store clerk in a product sales data processing system that registers a product based on a product registration operation by a customer using a portable terminal device to function as an acquisition means for acquiring incomplete product information regarding a product with an incomplete registration result when the registration result of the product based on the product registration operation is incomplete, a display control means for displaying a screen based on the incomplete product information acquired by the acquisition means, and a normal registration means for performing normal registration to register the incomplete product as a normal product in response to the input of registration completion information to the displayed screen.

[0010] Also, one aspect of the present invention is a server device provided in a product sales data processing system that registers a product based on a product registration operation by a customer using a portable terminal device, the server device comprising: an acquisition control means for causing a monitoring device used by a store clerk to acquire incomplete product information regarding a product with an incomplete registration result when the registration result of the product based on the product registration operation is incomplete; a display control means for causing a monitoring device operated by the store clerk to display a screen based on the incomplete product information acquired by the acquisition control means; and a normal registration means for performing normal registration to register the incomplete product as a normal product in response to the input of registration completion information to the screen displayed on the monitoring device.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Mode for Carrying Out the Invention

[0012] <Embodiment> [Configuration Example of Shopping System] FIG. 1 shows a configuration example of a shopping system (an example of a product sales data processing system) according to the present embodiment. The shopping system in the figure corresponds to an accounting (customer - terminal - corresponding accounting) in which, for example, while a customer takes out a product to be purchased from a product shelf, the registration of the taken - out product is performed using a customer terminal device 50, and the same customer also performs the settlement of the registered product using a settlement device 40. The accounting here includes the registration of a product and the settlement of the registered product, and refers to a procedure performed corresponding to a single transaction. The shopping system of this embodiment includes a management device 10, a transaction management device 60, a settlement device 40, a customer terminal device 50, a monitoring device 80, and a credit card payment server 70.

[0013] The management device 10, the settlement device 40, and the monitoring device 80 are installed in the store and are communicably connected via a LAN 19 (which may be wired or wireless). The management device 10 is a business terminal used by a store clerk for store management and the like, and is communicable with the transaction management device 60.

[0014] The monitoring device 80 is a business terminal that monitors the status of transactions performed by customers using the customer terminal device 50 in the store, and is communicable with the transaction management device 60. In FIG. 1, four settlement devices 40 are illustrated, but the number of settlement devices 40 in one store is not particularly limited.

[0015] The customer terminal device 50 is operated by a customer (such as a shopper who is a member of the store, hereinafter simply referred to as a customer). In addition to a general communication function and imaging function (camera), the customer terminal device 50 has a recognition function of scanning a barcode attached to a product to read the product code, that is, recognizing the barcode attached to the product. Note that the recognition function provided in the customer terminal device 50 only needs to be able to read the product code, and does not necessarily need to be able to recognize which product the read product code belongs to. That is, the customer terminal device 50 only needs to be able to read the product code from the barcode when the barcode exists as an object in the captured image (the image acquired as a through image) captured by the imaging function.

[0016] Such a customer terminal device 50 may be a smartphone, a tablet terminal, or the like owned by the customer. A shopping application having a function of performing product registration corresponding to the shopping system of this embodiment is installed in a smartphone, a tablet terminal, or the like as the customer terminal device 50.

[0017] Further, the customer terminal device 50 may be, for example, a terminal lent by a store to a customer. An application having a function of performing product registration corresponding to the shopping system of the present embodiment is also installed in the customer terminal device 50 lent by the store to the customer. The customer terminal device 50 lent by the store to the customer may be of a mode that can be used while being held by the customer, or may be of a mode that can be used by the customer while being attached to, for example, a shopping cart.

[0018] Further, the customer terminal device 50 captures an image of a product (for example, a peripheral part with a barcode) (for example, presses the shutter) and generates a captured image (image data). The customer terminal device 50 may be an imaging that presses the shutter according to the operation of the customer who is the operator, but in the present embodiment, it is preferable that the customer terminal device 50 is an imaging that presses the shutter according to its own determination.

[0019] Further, the customer terminal device 50 may be equipped with an image recognition technology that extracts feature points from an image (through image, captured image) and recognizes an imaging target (object, etc.). For example, the customer terminal device 50 may identify (estimate) the captured product using the image recognition technology.

[0020] The settlement device 40 is a settlement device capable of at least cash payment as a settlement method. The settlement device 40 is configured to be communicable with the transaction management device 60. Note that the settlement device 40 may be made communicable with the transaction management device 60, for example, through the relay of the management device 10.

[0021] The transaction management device 60 manages transactions performed corresponding to the shopping system of the present embodiment.

[0022] The credit card settlement server 70 executes settlement processing corresponding to the credit card in response to the transmission of a credit card settlement request from the settlement device 40, the customer terminal device 50, etc.

[0023] [Regarding the settlement device] FIG. 2 is a diagram showing an installation example of the settlement device 40. FIG. 2(A) is a perspective view of the settlement device 40 and the like as viewed from the customer side. FIG. 2(B) is a perspective view of the settlement device 40 and the like as viewed from the store clerk side. As shown in FIG. 2(A), a counter is placed on the right side of the settlement device 40 as viewed from the customer side.

[0024] FIG. 3 is a diagram showing an appearance example of the settlement device 40. FIG. 3(A) is a perspective view of the settlement device 40 as viewed from the customer side. FIG. 3(B) is a perspective view of the settlement device 40 as viewed from the store clerk side. FIG. 4 is a diagram showing a configuration example of the settlement device 40. In FIGS. 3 and 4, the same parts are denoted by the same reference numerals.

[0025] Hereinafter, with reference to FIG. 3, a configuration example of the settlement device 40 shown in FIG. 4 will be described. The settlement device 40 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a customer-side display unit 405, a customer-side scanner unit 406, a card settlement unit 408, a change dispenser 409, a store clerk-side display unit 410, a key operation unit 411, a store clerk-side scanner unit 412, a printing unit 413, an audio output unit 414, and a communication unit 415. These can communicate with each other via a bus.

[0026] The CPU 401 is a central processing unit, and controls the operation of the settlement device 40 by reading and executing the 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.

[0027] The RAM 403 is a read-write memory, and stores various types of information. For example, the RAM 403 stores information read from the ROM 402 or the hard disk 404, information acquired from the outside, information generated in the process, and the like.

[0028] The hard disk 404 stores various information. The hard disk 404 may store, for example, programs executed by the CPU 401 instead of the ROM 402. Further, instead of the RAM 403, it may store information read from the ROM 402, information acquired from the outside, information generated in the process, and the like.

[0029] The customer-side display unit 405 is a touch display for customers, which displays various information to customers and accepts various inputs from customers. The customer-side scanner unit 406 is a scanner unit for customers. For example, it scans a code attached to a product (for example, a code other than a barcode such as a two-dimensional code) and reads the product code. Further, the customer-side scanner unit 406 may scan a code (barcode, two-dimensional code, etc.) printed on the receipt (registered trademark) and read information necessary for settlement. Further, the customer-side scanner unit 406 may scan a code (two-dimensional code, barcode, etc.) displayed on the display unit of the customer terminal device 50 and read information necessary for settlement.

[0030] Note that the customer-side scanner unit 406 is used when a customer registers a product, but the customer may register the product by other methods. For example, when a preset key (a button for ordering a product) corresponding to the product is displayed on the customer-side display unit 405, the customer may operate (press) the preset key to register the product.

[0031] The card settlement unit 408 is a settlement mechanism using various cards (prepaid cards such as credit cards and transportation cards). The card settlement unit 408 of the present embodiment includes a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient if it includes at least a card recognition unit. Note that the card recognition unit may recognize various cards (for example, membership cards, point cards, etc.) that are not directly used for settlement (payment).

[0032] The change machine 409 (cash settlement unit) is a settlement mechanism using cash, having an inlet for bills and coins, an outlet for bills and coins, calculating the amount of money inserted into the inlet, calculating the change amount which is the difference between the inserted amount and the purchase amount, and discharging the change from the outlet. Note that the change machine 409 is directed towards the customer side and is operated by the customer. When bills or coins are inserted into the inlet, they are detected by sensors (detection of insertion, detection of the number of each denomination, etc.).

[0033] That is, the change machine 409 is used when the settlement device 40 settles the price of registered goods in cash (currency). The change machine 409 has a bill inlet for inserting bills, a coin inlet for inserting coins, a bill outlet for discharging bills, a coin outlet for discharging coins, a counting unit for counting the currency inserted or discharged, a currency conveyance mechanism between the inlet or outlet and the storage unit, the above-described sensors, etc. Note that the bill inlet and the coin inlet are also referred to as the deposit inlets. The bill outlet and the coin outlet are also referred to as the change outlets. Note that the bill inlet and the bill outlet may be common, and the coin inlet and the coin outlet may be common.

[0034] Also, the change machine 409 counts the currency replenished during the closing process and stores it in the storage unit. Also, the change machine 409 counts the currency to be withdrawn during the closing process and discharges it from the change outlet. The closing process is a process of adjusting the amount of money (cash balance / cash balance) stored in the change machine 409 to the reference amount after closing or before opening.

[0035] The store clerk display unit 410 is a touch display for store clerks, displaying various information to the store clerks and receiving various inputs from the store clerks. The key operation unit 411 is composed of various keys (buttons) and receives various inputs from the store clerks. The store clerk scanner unit 412 is a scanner unit for store clerks. For example, it scans the barcode attached to a product and reads the product code. Also, the store clerk scanner unit 412 scans the barcode etc. attached to the store clerk's name tag and reads the store clerk code.

[0036] Note that the clerk-side scanner unit 412 is used when the clerk registers a product, but the clerk may also register the product by other methods. For example, when a key corresponding to a product (e.g., a key corresponding to a sports newspaper, etc.) is arranged on the key operation unit 411, the clerk may operate (press) the key to register the product. Also, when a preset key corresponding to a product is displayed on the clerk-side display unit 410, the clerk may operate the preset key to register the product.

[0037] The printing unit 413 prints and issues various media (receipts, accounting tickets, etc.). The printing unit 413 can be rotated freely in the direction (the direction of the media issuing port) from the clerk side to the customer side and from the customer side to the clerk side. The orientation of the printing unit 413 may be changed manually, or may be changed automatically (mechanically controlled, etc.) according to, for example, the transition (switching) of the operation modes described later. Note that the correctness of the orientation of the printing unit 413 may be detected by a sensor or the like.

[0038] The voice output unit 414 outputs voice. For example, the voice output unit 414 outputs voice guidance and the like. The communication unit 415 executes communication with other devices (other settlement devices 40 and management devices 10).

[0039] Note that the settlement device 40 of the present embodiment can be switched between a total of four operation modes, namely, a customer terminal corresponding settlement mode set to perform settlement processing under customer terminal corresponding accounting, and three accounting modes (first to third accounting modes) corresponding to three different patterns of accounting (product registration, settlement). The first accounting mode is an operation mode in which the clerk performs operations corresponding to product registration and settlement on the settlement device 40. The second accounting mode is an operation mode in which the clerk performs an operation corresponding to product registration on the settlement device 40, and the customer performs an operation corresponding to settlement on the same settlement device 40. The third accounting mode is an operation mode in which the customer performs operations corresponding to product registration and settlement on the settlement device 40. As a result, in a store that has introduced the shopping system of this embodiment, for some of the plurality of settlement devices 40, by setting the customer terminal-compatible settlement mode, it can support customer terminal-compatible settlement. For other settlement devices 40, for example, by setting the first accounting mode or the second accounting mode, a store clerk can interact with customers to perform accounting. Note that those in which the third accounting mode is set in other settlement devices 40 may also be included.

[0040] [Configuration example of customer terminal device] FIG. 5 shows a configuration example of the customer terminal device 50. The customer terminal device 50 in the figure includes a CPU 501, a storage unit 502, a RAM 503, a display unit 504, an operation unit 505, an imaging unit 506, and a network-compatible communication unit 507. The CPU 501 is a central processing unit, and controls the operation of the customer terminal device 50 by reading and executing programs stored in the storage unit 502. The storage unit 502 is an auxiliary storage device of the CPU 501, and stores various types of information used by the CPU 501 including programs. The RAM 503 is the main storage device of the CPU 501. The display unit 504 displays an image according to the display control of the CPU 501. The display unit 504 may be configured as a touch panel capable of operating on the screen. The operation unit 505 collectively represents various operation elements provided in the customer terminal device 50 and various input devices connected to the customer terminal device 50. The imaging unit 506 performs imaging according to the control of the CPU 401. In addition, the imaging unit 506 of this embodiment can also function as a part that reads a two-dimensional code in a code reader that processes two-dimensional codes. The network-compatible communication unit 507 is a part that communicates wirelessly via a network. The customer terminal device 50 can communicate with the transaction management device 60 through the network-compatible communication unit 507.

[0041] [Configuration example of transaction management device] Figure 6 shows a configuration example of the transaction management device 60. The transaction management device 60 in the figure includes a CPU 601, a storage unit 602, a RAM 603, and a network-compatible communication unit 604. The CPU 601 is a central processing unit, and controls the operation of the transaction management device 60 by reading and executing programs stored in the storage unit 602. The storage unit 602 is an auxiliary storage device of the CPU 601, and stores various types of information used by the CPU 501, including programs. The RAM 603 is the main storage device of the CPU 601. The network-compatible communication unit 604 is a part for communicating via a network.

[0042] The storage unit 602 of the transaction management device 60 stores customer information, store information, product master (product information), and cart information.

[0043] [Configuration Example of Monitoring Device] Figure 7 shows a configuration example of the monitoring device 80. The monitoring device 80 in the figure includes a CPU 801, a storage unit 802, a RAM 803, an in-store compatible communication unit 804, a network-compatible communication unit 805, a display unit 806, and an operation unit 807. The CPU 801 is a central processing unit, and controls the operation of the monitoring device 80 by reading and executing programs stored in the storage unit 802. The storage unit 602 is an auxiliary storage device of the CPU 801, and stores various types of information used by the CPU 801, including programs. The RAM 803 is the main storage device of the CPU 801. The in-store compatible communication unit 804 communicates with terminals such as the settlement device 40 and the management device 10 in the store via the LAN 19. The network-compatible communication unit 805 is a part for communicating with the outside via a network. In the case of the monitoring device 80, the network-compatible communication unit 805 can communicate with the transaction management device 60 on the cloud. The display unit 806 displays an image according to the control of the CPU 801. The display unit 806 may be configured as a touch panel. The operation unit 807 collectively refers to the operation elements provided in the monitoring device 80 and the input devices connected to the monitoring device 80.

[0044] [Regarding the information stored in the transaction management device] The customer information stored in the storage unit 602 is information for managing individual customers. The transaction management device 60 generates customer information at the time of customer registration (it may be understood that the customer registration of a certain customer is completed when the customer information of that customer is stored). In addition, the transaction management device 60 appropriately updates the customer information based on the cart information and the like. The transaction management device 60 may refer to the cart information at a predetermined time every day, for example, and update the customer information.

[0045] FIG. 8(A) shows an example of the customer information stored in the storage unit 602 of the transaction management device 60. The customer information in the figure includes customer identification information, customer name, customer registration date, cancellation information, customer rank, number of points, and the like. The customer identification information is identification information that uniquely identifies a customer. Note that the customer identification information may be, for example, application identification information that is uniquely assigned to each installed shopping application when the shopping application of the present embodiment is installed. The application identification information may be, for example, a number that is uniquely (e.g., sequentially) assigned to each installed shopping application. Alternatively, the application identification information may be terminal identification information unique to the customer terminal device 50 on which the shopping application is installed. The terminal identification information may be, for example, a telephone number assigned to the customer who is the user of the customer terminal device 50, or hardware identification information that is assigned to be unique to the hardware of the customer terminal device 50, such as a MAC (Media Access Control) address. The customer name is the customer's name, nickname, etc. The customer registration date is the date and time when the customer was registered. The cancellation information is information regarding the cancellation of registered products after registration. The customer rank is a rank according to the customer's purchase record. Note that when generating customer information for a new customer, customer identification information, customer name, and customer registration date are generated, but since it is before the start of actual transactions (product registration), other information (such as cancellation information) is not generated.

[0046] The transaction management device 60 generates and stores customer identification information, for example, when a customer registers (for example, when the customer terminal device 50 downloads or installs a shopping application from the outside (for example, a predetermined server that provides all applications, the transaction management device 60) to use the shopping service provided by the transaction management device 60). Also, the transaction management device 60 acquires, for example, the information entered in the name field of the registration form (input form) using the customer terminal device 50 when a customer registers, and stores it as the customer name. Further, the transaction management device 60 acquires, for example, the current date and time at the time of customer registration, and stores it as the customer registration date.

[0047] Note that the transaction management device 60 may store part or all of the customer information in another device (such as a file server accessible by the transaction management device 60) instead of or in addition to storing the customer information in the storage unit within its own device.

[0048] FIG. 8(B) shows an example of the store information stored in the storage unit 602 of the transaction management device 60. The store information in the figure includes store identification information, store name (branch name), store identification information 1, and store identification information 2. The store identification information is identification information that uniquely identifies a store. The store identification information shown in FIG. 8(B) is composed of a store (store number) or a company code and a branch code. The store name is the name of the store. The store name shown in FIG. 8(B) is composed of a store (store number) or a company and a branch name. The store identification information 1 is information of a two-dimensional code (such as a QR code (registered trademark)) for identifying the store where the transaction (sale and purchase of products) is carried out. The store specific information 2 is the location information (GPS information) of the store for identifying the store to conduct transactions. In the example shown in FIG. 8(B), the store identification information and the store specific information 1 are different, but the store identification information and the store specific information 1 may be the same.

[0049] Note that the transaction management device 60 may obtain and store store information and the like from the outside (such as a server (not shown) of the head office that oversees each store). In addition, instead of or in addition to storing the store information in the storage unit within the device itself, the transaction management device 60 may store part or all of the store information in another device (such as a file server accessible by the transaction management device 60).

[0050] The cart information is information for managing individual transactions. The transaction management device 60 generates cart information at the start of a transaction. Also, the transaction management device 60 updates the cart information as the transaction progresses (each time a product is registered) (it may be understood that the registration of the product is completed when the product is stored in the cart information).

[0051] FIG. 8(C) is an example of the cart information stored in the storage unit 602 of the transaction management device 60. The cart information in the figure includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, in-cart product information (registered product information, reserved product information), cancellation information, and the like.

[0052] The cart identification information is identification information that uniquely identifies the cart information. For example, the cart identification information includes the store identification information, the date, and a serial number (for example, a serial number by store and date). The transaction start date and time is the start date and time of the transaction. The transaction start date and time may be, for example, the generation date and time of the cart information. Note that the transaction start date and time may be the registration date and time of one item of product (the date and time when the registered product information (registered product 1) in FIG. 8(C) is stored). The generation date and time of the cart information and the registration date and time of one item of product may be stored separately.

[0053] The transaction end date and time is the end date and time of the transaction. For example, the transaction end date and time may be the settlement date and time. The customer identification information is the customer identification information that identifies the customer of the said transaction. Note that at the time of generating the cart information, the cart identification information, the transaction start date and time, and the customer identification information are generated, but since it is before the start of the actual transaction (product registration), other information (such as the transaction end date and time) is not generated. The settlement date and time may be the settlement start date and time or the settlement end date and time. As the transaction end date and time, it is also possible to separately store both the settlement start date and time and the settlement end date and time.

[0054] The registered product information (total) is information that is updated each time a product is registered. The registered product information (total) includes the quantity (number of products), the estimated subtotal amount (for example, the subtotal amount before discounts, etc.), the subtotal amount, etc. The registered product information (registered product 1) is the registration information of one item of product. The registered product information (registered product 2) is the registration information of two items of product. Note that in the example shown in FIG. 8(C), the illustration of the registered product information (registered product 3) to the registered product information (registered product 5) is omitted. The registered product information (N; N is an integer) includes the product code, the product name, the price, etc.

[0055] The registered product information (N) may include the registration date and time of the Nth item of product. That is, the transaction management device 60 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 the necessity of applying services such as time services and the effects after application.

[0056] The reserved product information (total) is information that is updated each time a reserved product is registered. A reserved product is a product that was not normally registered due to a predetermined factor and was temporarily registered in a reserved state. The reserved product information (total) includes the quantity (number of products) of the reserved products, the quantity of NON-FILE among the reserved products, the quantity of read NG (operation error confirmation required) among the reserved products, etc.

[0057] "NON-FILE" refers to a product (a product with unregistered product information) where the barcode or product code scan was successful in the store (the product code could be read), but the product code is not stored as product information in the product master.

[0058] "Read NG" refers to the situation where the product code scan failed in the store (the product code could not be read), or it refers to the product for which the product code scan failed in the store. That is, for "Read NG", for example, when imaging a product for a certain period of time by image recognition technology but barcode recognition is not achieved and it can be determined, a timeout process is performed, and it is a product for which the timeout process was performed. For example, due to reasons such as wrinkles on the package, smudges or dirt on the barcode printing, or the barcode being printed on a transparent film, even if the customer performs an operation to read the barcode, if the barcode cannot be correctly acquired (recognized), it is determined as "Read NG".

[0059] Pending product information (Pending product 1) is the information of one item of pending product. Pending product information (Pending product 2) is the information of two items of pending product. Pending product information (Pending product 3) is the information of three items of pending product.

[0060] Pending product information (Pending product N; N is an integer) includes pending product type (information indicating whether the pending product is NON-FILE or Read NG) and image data (image data captured when Read NG). For example, when the Nth item of product is a pending product due to NON-FILE, the pending product information (Pending product N) includes the pending product type "1 (NON-FILE)", product code, and image data. Also, when the Nth item of product is a pending product due to Read NG, the pending product information (Pending product N) includes the pending product type "2 (Read NG)" and image data.

[0061] Figure 9 shows an example of the definition of pending products corresponding to the cart information of this embodiment. In the figure, an example where the pending products are classified into 8 is shown. Classification numbers from "1" to "8" are assigned to each of the 8 classifications of pending products. The classification of the hold item with classification number 1 is "NON-FILE" as explained in FIG. 8. The classification of the hold item with classification number 2 is "NG reading" as explained in FIG. 8.

[0062] The classification of the hold item with classification number 3 is "pseudo scan input". The hold item of "pseudo scan input" is a product for which the customer attempted to have the product code read by the customer terminal device 50, but the customer terminal device 50 was unable to read the code properly.

[0063] As a specific example, for "pseudo scan input", a situation where the product was placed within the imaging range of the imaging unit 506, but the product code was not placed within the imaging range of the imaging unit 506 applies. Also, for "pseudo scan input", a situation where the product was placed within the imaging range of the imaging unit 506, but an area without a code was imaged applies. Also, for "pseudo scan input", a situation where the product was placed within the imaging range of the imaging unit 506 with the code portion hidden by a finger or the like applies. Also, for "pseudo scan input", a situation where the product code was imaged by the imaging unit 506, but the product was passed through the imaging range of the imaging unit 506 at a speed at which the customer terminal device 50 could not read the code applies.

[0064] The classification of the hold item with classification number 4 is "non-scan input". The hold item of "non-scan input" is a product that was placed in the shopping basket without performing an operation to position the product within the imaging range of the imaging unit 506. This non-scan input can occur, for example, when the customer terminal device 50 is fixedly attached to the shopping cart and is configured to be able to image the inside of the shopping basket placed on the shopping cart. For example, when the customer terminal device 50 determines, based on the captured image, that a product has been placed in the shopping cart even though the product code has not been scanned, it can be determined that non-scan input has been performed.

[0065] The classification of the reserved items with classification number 5 is "age verification items". "Age verification items" are items for which it is necessary for the store clerk to verify the customer's age at the time of sale, such as alcohols and cigarettes.

[0066] The classification of the reserved items with classification number 6 is "pharmaceuticals". "Pharmaceuticals" are items for which it is necessary for those with qualifications such as pharmacists to request verification from the purchaser.

[0067] The classification of the reserved items with classification number 7 is "anti-theft tag items". "Anti-theft tag items" are items for which it is necessary for the store clerk to remove the anti-theft tag from the item at the time of sale because the anti-theft tag is attached.

[0068] The classification of the reserved items with classification number 8 is "cancelled items". "Cancelled items" are items that have been registered once but have been cancelled by the customer's cancellation operation on the customer terminal device 50. "Cancelled items" are, for example, taken back from the customer by the store clerk at the time of settlement.

[0069] In the present embodiment, among the classification numbers 1 to 7, the reserved items corresponding to any of the four classifications of "NON-FILE", "reading NG", "pseudo-scan input", and "non-scan input" of classification numbers 1 to 4 are unspecified items. Unspecified items are items for which, for example, it has not been determined which of the items registered in the product master they are, resulting in an incomplete registration result.

[0070] The product master is stored, for example, in the management device 10. The product master stores product information for each product sold in the store. The product information corresponding to one product includes a plurality of predetermined information items including a product code and a product name. The transaction management device 60 stores the product master acquired from the management device 10. The transaction management device 60 uses the stored product master for processing related to product registration and the like.

[0071] For the reserved item corresponding to the classification number 1 "NON-FILE", the item code is acquired by code scanning in response to the item registration operation, but the item information corresponding to the acquired item code is not registered in the item master. Therefore, it is not specified which of the items registered in the item master the reserved item corresponding to the classification number 1 "NON-FILE" is. Specifically, the customer terminal device 50 may transmit the item code acquired by code scanning to the transaction management device 60, and the transaction management device 60 may compare the transmitted item code with the item code of the item registered in the item master stored in the transaction management device 60. If it is determined as a result of the comparison that the same item code as the transmitted item code does not exist in the item master, the transaction management device 60 may treat the item as a reserved item corresponding to the classification number 1 "NON-FILE" and notify the customer terminal device 50 of the fact. For pending products that fall into one of the three categories of classification numbers 2 to 4, "Read NG", "Pseudo scan input", and "Non-scan input", the product code has failed to be acquired as a result of the code scan in response to the product registration operation. Therefore, it is not possible to identify which of the products registered in the product master the pending products that fall into one of the three categories of classification numbers 2 to 4, "Read NG", "Pseudo scan input", and "Non-scan input", are. Such unspecified products are products that can be released from their status as reserved products (reserved status) by a store clerk operating the monitoring device 80 as described below, and can be registered normally.

[0072] In addition, instead of or in addition to storing the cart information in its own memory, the transaction management device 60 may store some or all of the cart information in another device (such as a file server accessible by the transaction management device 60).

[0073] [Example of basic processing procedure for self-operation] The sequence diagram of FIG. 10 shows an example of the processing procedure executed by the customer terminal device 50, the settlement device 40, and the transaction management device 60 in response to the accounting of a single transaction in self-operation. Specifically, the processing in the figure shows an example of the processing of the customer terminal device 50, the settlement device 40, and the transaction management device 60 until the customer registers the product to be purchased from the products displayed in the store and the settlement for the registered product is completed.

[0074] Step S1: The customer terminal device 50 acquires information for specifying the store (store specification information). For example, a two-dimensional code for specifying the store is displayed near the entrance of the store (output the two-dimensional code to the display screen, attach a medium printed with the two-dimensional code, etc.), and the customer who visits the store scans (reads) the two-dimensional code with the customer terminal device 50, so that the customer terminal device 50 may acquire the store specification information. In addition, when the customer who visits the store launches the shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as the start screen, or when the customer who visits the store scans the two-dimensional code with the customer terminal device 50, the shopping application may be launched and a screen notifying the customer that the customer is connected to the transaction management device 60 may be displayed as the start screen.

[0075] Also, for example, since the store is specified by its location, the customer who visits the store may acquire location information (GPS information) with the customer terminal device 50 in the store (that is, the location information of the store may be acquired as the store specification information). In addition, when the customer who visits the store launches the shopping application, the location information may be acquired and a screen notifying the customer that the customer is connected to the transaction management device 60 may be displayed as the start screen. If multiple stores are detected from the location information and cannot be specified to one, a selection screen may be displayed for the customer to select. Or it may be switched to a mode that forcibly acquires the two-dimensional code.

[0076] FIG. 11(A) shows an example of a startup screen of a shopping application displayed on the display unit 504 of the customer terminal device 50. In the startup screen of this figure, the store name is displayed. This store name is displayed based on the store identification information acquired in step S1. When the customer wants to start product registration for shopping, the customer operates the transaction start instruction button BT10 arranged on the startup screen. In response to the operation of the transaction start instruction button BT10, the customer terminal device 50 transmits a transaction start request including the acquired store identification information and customer identification information to the transaction management device 60. The transaction start request may be transmitted in response to the customer's operation on the customer terminal device 50 as described above, or may be transmitted in response to the acquisition of the store identification information without particularly receiving an operation. Regarding the customer identification information, at the time of customer registration (when downloading or installing the shopping application on the customer terminal device 50), the information entered in the name field of the registration form using the customer terminal device 50 may be stored in the customer information of the transaction management device 60. In addition to the transaction management device 60, it may also be stored in the storage unit of the customer terminal device 50. When the store is identified (when the product registration initial screen described later is acquired), the store name of the store, the services in progress (the flyer information distributed on that day), and the available coupon information may be displayed on the screen (the product registration initial screen or a screen different from the product registration initial screen). The information on services and coupons may be acquired from the transaction management device 60 as screen information, for example.

[0077] Also, the information of the transmission destination (the address of the transaction management device 60) may be acquired at the time of customer registration (when downloading or installing the shopping application on the customer terminal device 50) and stored in the storage unit of the customer terminal device 50. When using the mode of scanning a two-dimensional code, in addition to the store identification information, the information of the transmission destination may also be two-dimensionally coded, and by scanning the two-dimensional code with the customer terminal device 50, the customer terminal device 50 may also acquire the information of the transmission destination together with the store identification information.

[0078] Step S2: The transaction management device 60 that has received customer identification information and store identification information as a transaction start request from the customer terminal device 50 generates cart information for the transaction. In the initially generated cart information, cart identification information, the transaction start date and time, and customer identification information are stored. However, since it is before the start of the actual transaction (product registration), other information (transaction end date and time, product information (registered product information, reserved product information), etc.) is not stored.

[0079] As described above, the transaction management device 60 stores store information as shown in FIG. 8(B). Therefore, when the transaction management device 60 receives store identification information as a transaction start request from the customer terminal device 50 (although it also receives customer identification information), if the received store identification information is a two-dimensional code, the transaction management device 60 refers to Store Identification Information 1 to obtain store identification information. If the received store identification information is location information (GPS information), the transaction management device 60 refers to Store Identification Information 2 to obtain store identification information. In addition, if the store identification information received by the transaction management device 60 from the customer terminal device 50 is the store identification information encoded as a two-dimensional code, the transaction management device 60 may obtain it as it is.

[0080] That is, the transaction management device 60 that has received customer identification information and store identification information as a transaction start request from the customer terminal device 50 obtains store identification information from the store identification information received from the customer terminal device 50. Furthermore, the transaction management device 60 obtains the current date, issues (assigns) a serial number, combines the store identification information, the current date, and the serial number, and stores them as the cart identification information in the cart information. In addition, the transaction management device 60 that has received store identification information or customer identification information as a transaction start request from the customer terminal device 50 obtains the current date and time and stores it as the transaction start date and time (generation date and time) in the cart information. Moreover, the transaction management device 60 that has received store identification information or customer identification information as a transaction start request from the customer terminal device 50 stores the customer identification information received from the customer terminal device 50 as the customer identification information in the cart information.

[0081] Step S3: The transaction management device 60 that 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 customer terminal device 50. Specifically, for example, the transaction management device 60 generates product registration initial screen information, and transmits the generated product registration initial screen information to the customer terminal device 50 together with the cart identification information.

[0082] Step S4: The customer terminal device 50 that has received the cart identification information and the product registration initial screen information from the transaction management device 60 stores the cart identification information, and displays the registration screen on the display unit. Specifically, for example, the customer terminal device 50 displays a product registration initial screen as shown in FIG. 11(B).

[0083] Step S5: By the operation of the customer, the customer terminal device 50 scans the barcode attached to the product and reads the product code. In the figure, it is assumed that the barcode scanning is successful. Steps S5 to S9 are repeatedly executed each time the barcode attached to the product is scanned.

[0084] The customer terminal device 50 that has acquired the barcode transmits product registration information including the cart identification information and the product code obtained by scanning to the transaction management device 60.

[0085] Step S6: The transaction management device 60 that has received the product registration information (cart identification information and product code) from the customer terminal device 50 identifies the cart information for the transaction from the cart identification information included in the received product registration information.

[0086] Step S7: The transaction management device 60 updates the product data in the identified cart information. Specifically, when the received product registration information includes a product code as item N, the transaction management device 60 stores the product code as the product code of the registered product information (registered product N) in the identified cart information, acquires 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). Also, the transaction management device 60 updates the registered product information (total) in the identified cart information.

[0087] Step S8: The transaction management device 60 that has updated the product data in the cart information generates product registration update screen information (screen information of the product registration screen which is an update screen with the registered product added), and transmits it to the client terminal device 50. Specifically, the transaction management device 60 generates, for example, product registration update screen information such that a product registration update screen in which a list item of the product newly registered in the registered product list is added is displayed on the client terminal device 50 as shown in FIG. 11(C), and transmits the generated product registration update screen information to the client terminal device 50 together with the cart identification information.

[0088] Note that the product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the customer terminal device 50 after "〇〇 Food Bread" is registered as a product of three items. That is, when the transaction management device 60 stores "〇〇 Yogurt" in the cart information as one item, it generates product registration update screen information such that "〇〇 Yogurt" is displayed on the customer terminal device 50, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information. When "〇〇 Chocolate" is stored in the cart as the second item, it generates product registration update screen information such that "〇〇 Yogurt" and "〇〇 Chocolate" are displayed on the customer terminal device 50, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information. When "〇〇 Food Bread" is stored in the cart information as the third item, as shown in FIG. 11(C), it generates product registration update screen information such that "〇〇 Yogurt", "〇〇 Chocolate", and "〇〇 Food Bread" are displayed on the customer terminal device 50, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0089] Note that in response to the registration of one product, for example, as shown in FIG. 12(A), a registered product presentation screen WD1 for presenting the currently registered product may be displayed. Also, in the registered product presentation screen WD1 of the same figure, in response to the target product corresponding to eat-in, an example is shown in which a "Yes" button BT1 and a "No" button BT2 for confirming with the customer whether to eat and drink by eat-in are arranged. In this case, the consumption tax rate for the target product is made different depending on whether the "Yes" button BT1 is operated or the "No" button BT2 is operated, and the price of the product is calculated accordingly.

[0090] Step S9: The client terminal device 50 that has received the cart identification information and the product registration update screen information from the transaction management device 60 adds a product to the registration screen. Specifically, the client terminal device 50 displays a product registration update screen as shown in FIG. 11(C), for example. As described above, the product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the client terminal device 50 after "〇〇 Food Bread" is registered as three items of products.

[0091] Step S10: The client terminal device 50 accepts a settlement transition instruction operation as an operation by the customer. For example, it accepts the touch of the "Proceed to Checkout" button shown in FIG. 11(C).

[0092] Step S11: The client terminal device 50 that has accepted the settlement transition instruction operation generates a two-dimensional code. That is, the client terminal device 50 encodes information (for example, cart identification information) necessary for performing settlement processing on the purchased products by the client terminal device 50 into a two-dimensional code. The client terminal device 50 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, it displays a code display screen with a two-dimensional code as shown in FIG. 11(D) on the display unit.

[0093] Step S12: The settlement device 40 scans (reads) the two-dimensional code displayed on the display unit of the client terminal device 50. For example, the settlement device 40 scans the two-dimensional code displayed on the display unit of the client terminal device 50 that is directed within the recognition range of the customer-side scanner unit 406 by the customer.

[0094] Step S13: The settlement device 40 that has read the two-dimensional code displayed on the display unit of the client terminal device 50 requests the transaction management device 60 to calculate the subtotal amount. For example, the settlement device 40 transmits a calculation request (subtotal calculation request information) for requesting the calculation of the subtotal amount to the transaction management device 60 together with the cart identification information obtained from the two-dimensional code.

[0095] Step S14: The transaction management device 60 that has received the cart identification information and the subtotal calculation request information from the customer terminal device 50 identifies the cart information of the transaction from the cart identification information.

[0096] Step S15: The transaction management device 60 that has identified the cart calculates the subtotal amount by using information such as the price in the registered product information included in the cart information corresponding to the identified cart information.

[0097] Step S16: The transaction management device 60 that has calculated the subtotal amount updates the cart information (stores the subtotal amount (calculated subtotal amount)) and transmits the subtotal information indicating the calculated subtotal amount to the settlement device 40 together with the cart identification information.

[0098] Step S17: The settlement device 40 that has received the cart identification information and the subtotal information from the transaction management device 60 displays the subtotal amount on the customer-side display unit 405, for example, as shown in FIG. 12(B).

[0099] Step S18: The settlement device 40 that has displayed the subtotal amount on the customer-side display unit 405 executes payment (settlement). Specifically, the settlement device 40 accepts the selection of the settlement type. In the case of cash, it accepts the deposit of the deposit, calculates the change amount, and if there is change, discharges the change and issues a receipt. Also, when the settlement is completed, the settlement device 40 transmits the settlement completion information to the transaction management device 60 together with the cart information, and the transaction management device 60 stores the transaction end date and time (settlement date and time) of the cart.

[0100] Note that the customer terminal device 50 transmits the product code to the transaction management device 60 after scanning the product (S5). However, it may be configured not to transmit the product code for products scanned within the store (the store where the product registration initial screen was displayed when the customer visited) other than the scanned product (for example, products scanned after moving to another store). For example, the customer terminal device 50 acquires and stores location information (GPS information) when visiting the store (or when the product registration initial screen is displayed). Also, the customer terminal device 50 acquires location information when scanning each product, and compares the location information acquired at the time of product scanning with the location information acquired when visiting the store (or when the product registration initial screen is displayed). Then, the customer terminal device 50 may permit the transmission of the product code of the product to the transaction management device 60 when the two match (or substantially match), and prohibit the transmission of the product code of the product to the transaction management device 60 when they do not match (or substantially match). This can prevent inappropriate product registration (for example, product registration for a cart generated in another store, etc.).

[0101] When the transmission of the product code is prohibited as described above, the settlement device 40 may display an error message (for example, "Registration is not possible because it is not within Store XX") on the customer display unit 405 after scanning the product. Also, the settlement device 40 may display the above message on the store employee display unit 410 instead of or in addition to the customer display unit 405.

[0102] In addition, after the settlement device 40 reads the two-dimensional code displayed on the display unit of the customer terminal device 50, it requests the transaction management device 60 to calculate the subtotal amount (S13). However, it may be configured not to request the calculation of the subtotal amount for products other than the products scanned within the store (for example, products scanned at other stores, etc.). For example, the settlement device 40 refers to the store identification information of the store (it may store and refer to the store identification information of the store in the self-settlement device 40, or refer to the store identification information stored in other accessible devices), and when reading the two-dimensional code displayed on the display unit of the customer terminal device 50, it compares the cart identification information obtained from the two-dimensional code with the store identification information of the store. Then, when the store identification information included in the cart identification information is configured to include the store identification information of the store, the settlement device 40 may permit the request for calculating the subtotal amount, and when it is not configured to include the store identification information of the store, it may prohibit the request for calculating the subtotal amount. This can prevent inappropriate settlement (for example, settlement of products registered in other stores, etc.).

[0103] When the settlement device 40 prohibits the request for the subtotal amount as described above, it may display an error message (for example, "Since it includes products from stores other than store XX, settlement cannot be performed") on the customer-side display unit 405 after reading the two-dimensional code. Further, the settlement device 40 may display the above message on the store clerk-side display unit 410 instead of or in addition to the customer-side display unit 405.

[0104] In the example of the processing procedure in FIG. 10, the transaction management device 60 is configured to calculate the subtotal amount. However, for example, the settlement device 40 may be configured to obtain cart information from the transaction management device 60 and calculate the subtotal amount based on the obtained cart information. Alternatively, the transaction management device 60 may transmit the cart information to the management device 10 and request the calculation of the subtotal amount, and the management device 10 may calculate the subtotal amount using the received cart information and transmit the calculated subtotal amount to the settlement device 40 via the transaction management device 60.

[0105] Note that, during the settlement process, the transaction management device 60 may check the cancellation status of the customer's previous products based on the customer information and cart information of the corresponding customer, and determine whether a warning against fraud should be issued. If it is determined that a warning should be issued, the transaction management device 60 may, for example, cause the settlement device 40 to execute a notification for the warning.

[0106] Also, during the settlement process, the transaction management device 60 may determine whether there are any pending products among the product information included in the cart information. If there are pending products, the transaction management device 60 may request the settlement device 40 to issue an instruction to modify the pending products. Upon receiving the request for an instruction to modify the pending products, the settlement device 40 will display a notification indicating that there are pending products, as shown in FIG. 12(C). The store clerk who has confirmed the notification will perform operations such as inputting the price corresponding to the pending product or canceling the pending product as the cancellation (modification) of the pending product.

[0107] [Regarding the remote operation for cancellation of hold] The cancellation of the hold status (cancellation of hold) for the pending product is performed by the store clerk operating the settlement device 40 which displays a notification indicating that there are pending products, as shown in FIG. 12(C). However, in this case, the store clerk needs to visit the settlement device 40 that is notifying the existence of the pending product one by one. Therefore, in the shopping system of this embodiment, it is made possible for the store clerk to cancel the hold of the pending product by operating the monitoring device 80 for the unspecified products included among the pending products registered in the abnormal transaction. That is, in this embodiment, it is possible to perform a remote operation (remote operation for cancellation of hold) to cancel the hold status of the unspecified product using the monitoring device 80 without the store clerk having to visit the settlement device 40. By enabling such a hold release remote operation, it becomes unnecessary for the settlement device 40 to perform hold release for hold items corresponding to unspecified items. As a result, the hold release of hold items can be performed even at a stage prior to the settlement by the settlement device 40, enabling efficient hold release of hold items. Also, since it becomes possible to distribute the hold release operation between the settlement device 40 and the monitoring device 80, it becomes possible to shorten the total waiting time for hold release at the settlement device 40, and it also becomes possible to improve the utilization efficiency of the settlement device 40.

[0108] Hereinafter, the flow of the hold release remote operation in this embodiment will be described. In the following description, an operation of causing the customer terminal device 50 to scan (read) a code (for example, a barcode) attached to a product for the customer to register the product is also referred to as a product registration operation. The customer terminal device 50 has a code scanning function of extracting a code from an image captured by the imaging unit 506 and acquiring code information. The customer terminal device 50 can acquire a product code by scanning the code attached to the product.

[0109] The customer is made to perform a product registration operation by causing the customer terminal device 50 to scan the code attached to the product to be purchased by the customer at the store sales floor. When a product is registered as a result of the product registration operation, as shown in FIG. 11(C), the product registration screen is updated such that a list item of the product registered this time is added in the registered product list.

[0110] Furthermore, when the customer terminal device 50 of this embodiment determines that a product for which a product registration operation has been performed corresponds to an unspecified item among the hold items as a result, it displays a hold release guidance screen. The hold release guidance screen is a screen on which an operation of notifying the customer that the product targeted by the current product registration operation is treated as an unspecified item and designating (selecting) whether to request a hold release remote operation for the hold release of the unspecified item is performed.

[0111] First, an example will be described below in the case where, as a result of the product registration operation, it is determined that the product to be registered is an unspecified product corresponding to "NON-FILE" of classification number 1.

[0112] Figure 13(A) shows an example of the hold cancellation guidance screen WD51. The hold cancellation guidance screen WD51 in the figure is an example displayed in a window form arranged to overlap the product registration screen. On the hold cancellation guidance screen WD51 in the figure, a message is displayed notifying the customer that the product targeted in the current product registration operation has been registered as an unspecified product among the held products and guiding that a remote hold cancellation operation can be requested. Also, on the hold cancellation guidance screen WD51, an operation request button BT51 and an operation not required declaration button BT52 are arranged. The operation request button BT51 is a button to be operated when the customer requests a remote hold cancellation operation on the spot. The operation not required declaration button BT52 is a button to be operated when the customer does not request a remote hold cancellation operation on the spot and asks the store clerk to cancel the hold when performing settlement at the settlement device 40.

[0113] In addition, the product registration screen displayed in the background of the hold cancellation guidance screen WD51 in the figure has been updated to a state reflecting the result of the current product registration operation. That is, in the list item of the product at the bottom of the product registration screen, it is displayed as "Held product: NON-FILE". Such a display of the list item indicates that, as a result of the current product registration operation, it has been registered as a held product corresponding to "NON-FILE" of classification number 1. Also, in the case of a held product corresponding to "NON-FILE" of classification number 1, since the product information associated with the acquired product code has not been obtained, the price information has not been obtained either. For this reason, the price is not displayed in the list item of the product at the bottom of the product registration screen.

[0114] In this case, since the customer requested a remote operation to lift the hold on the spot, the customer operated the operation request button BT51. In response to the operation of the operation request button BT51, the customer terminal device 50 transmits operation request information to the transaction management device 60. The operation request information includes cart identification information and hold item reference information. If the item targeted for the current product registration operation is an unspecified item as "NON-FILE" with a classification number of 1, the hold item reference information includes the product code acquired by the customer terminal device 50 through code scanning and the captured image captured by the imaging unit 506 when the code scanning is being performed. If the item targeted for the current product registration operation is an unspecified item among "Read NG", "Pseudo Scan Input", and "Non-Scan Input" with classification numbers 2 to 4, the hold item reference information includes the captured image captured by the imaging unit 506 when the code scanning is being performed, but does not include the product code.

[0115] The transaction management device 60 transfers the received operation request information to the monitoring device 80. At this time, the transaction management device 60 includes the product information registered as an unspecified item in response to the current product registration operation in the operation request information and transmits it to the monitoring device 80.

[0116] When the customer terminal device 50 transmits the operation request information to the monitoring device 80 via the transaction management device 60 as described above, it displays a hold cancellation waiting screen WD52 instead of the hold cancellation guidance screen WD51. Figure 13(B) shows an example of the hold cancellation waiting screen WD52. The hold cancellation waiting screen WD52 in the figure is an example of a window form that is superimposed and arranged on the product registration screen, similar to the hold cancellation guidance screen WD51. In the hold cancellation waiting screen WD52 in the figure, a message is displayed to inform the customer that the hold cancellation operation is currently being performed and to wait until the hold cancellation of the unspecified item by the hold cancellation operation is completed.

[0117] In addition, the monitoring device 80 that has received the operation request information causes the product information input screen to be displayed on the display unit 806. The store clerk in charge of monitoring who uses the monitoring device 80 can, by the display of the product information input screen, grasp that a request for a hold release remote operation has been made by the customer.

[0118] Note that prior to displaying the product information input screen, the monitoring device 80 may display on the display unit 806 a hold release operation confirmation screen on which a notification that a request for a hold release remote operation has been made by the customer and a declaration operation as to whether to perform the hold release remote operation in response to the request are performed. The declaration operation as to whether to perform the hold release remote operation may be an operation on either a button for declaring to perform the hold release remote operation or a button for declaring not to perform the hold release remote operation. When the store clerk performs an operation declaring to perform the hold release remote operation on the hold release operation confirmation screen, the display on the display unit 806 is changed to the product information input screen. Also, when the store clerk performs an operation declaring not to perform the hold release remote operation on the hold release operation confirmation screen, the display on the display unit 806 is made to return to a predetermined screen before the hold release operation confirmation screen was displayed.

[0119] FIG. 14(A) shows an example of the product information input screen displayed on the display unit 806. The product information input screen in the figure has a product code input area AR30-1, a search button BT31, a product name input area AR30-2, a selling price input area AR30-3, a product type input area AR30-4, a warning type input area AR30-5, a confirmation button BT32, a deletion button BT33, and a scan status image area AR31 arranged therein.

[0120] Note that when there is no particular distinction among the product code input area AR30-1, the product name input area AR30-2, the selling price input area AR30-3, the product type input area AR30-4, and the warning type input area AR30-5, they are described as the input area AR30.

[0121] The product code input area AR30-1 is an input area where the product codes of unspecified products targeted for release from hold are entered. The search button BT31 is a button that is operated when searching for products registered in the product master when entering a product code in the product code input area AR30-1. The product name input area AR30-2 is an input area where the product name is entered. The selling price input area AR30-3 is an input area where the selling price is entered. The product type input area AR30-4 is an input area where the product type is entered. The warning type input area AR30-5 is an input area where the warning type is entered. The confirmation button BT32 is a button for which an operation to instruct the display of an input information confirmation screen for confirming the content of the information entered in each of the above input areas AR30 is performed when executing the release from hold. The delete button BT33 is a button that is operated when deleting the registration as a held product for an unspecified product targeted for release from hold as the release from hold.

[0122] The scan status image area AR31 is an area where the scan status image is displayed. The scan status image is a captured image obtained by the imaging unit 506 when the code of an unspecified product targeted for release from hold by the customer terminal device 50 is being scanned in response to the customer's product registration operation. The content of such a scan status image indicates the status of the unspecified product targeted for release from hold when the product code is being scanned by the customer terminal device 50. Also, in the scan status image area AR31, a plurality of scan status images with different imaging timings, for example, may be displayed. The scan status image may also be a moving image or a time-lapse image composed of still images captured at regular intervals.

[0123] When the unspecified product was "NON-FILE" with classification number 1, the product code was successfully obtained as a result of scanning the code according to the product registration operation. However, the product information associated with the obtained product code was not retrieved. Therefore, in the initial display state of the product information input screen, the product code is already entered in the product code input area AR30-1, but the remaining product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5 are all in a state where information has not been entered.

[0124] So, the store clerk performs an operation of inputting information corresponding to the unspecified product targeted for hold cancellation into each of the above input areas AR30 where information has not been entered. At this time, the store clerk can look at the scan information image displayed in the scan status image area AR31 to determine what kind of product the unspecified product targeted for hold cancellation is. As a result, the store clerk can identify what kind of information should be entered in each of the product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5. When determining the information to be entered in each of the above input areas AR30, the store clerk may be referred to a product catalog or the like where product information that can be handled in the store is published, for example. Then, the store clerk is required to perform an operation of inputting the identified information into each of the product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5. As a result, as shown in Fig. 14(A), in all input areas including the product code input area AR30-1, product name input area AR30-2, selling price input area AR30-3, product type input area AR30-4, and warning type input area AR30-5, a state where information about the unspecified product targeted for hold cancellation has been entered is obtained.

[0125] When all the input areas AR30 are filled with information as described above, the store clerk operates the confirmation button BT32. In response to the operation of the confirmation button BT32, although not shown in the figure, an input information confirmation screen is displayed on the display unit 806. On the input information confirmation screen, the content of the information input in each input area AR30 on the product information input screen is shown, and an execution button for instructing the execution of cancellation of suspension is arranged. After the store clerk checks the content of the information shown on the product information input screen, the store clerk operates the execution button. In response to the operation of the execution button, the monitoring device 80 transmits a suspension cancellation request including the information (simple product information) input in the input area AR30 to the transaction management device 60.

[0126] When the transaction management device 60 receives the suspension cancellation request, it replaces the suspension product information of the suspension product that is the target of the current suspension cancellation stored in the cart information with the registered product information including the simple product information included in the received suspension cancellation request. As a result, the suspension state of the suspended product as an unspecified product is released and it is treated as being normally registered.

[0127] When the transaction management device 60 releases the suspension state of the suspended product as an unspecified product and performs normal registration (normal registration) as described above, it transmits a suspension cancellation completion notice to the client terminal device 50. The suspension cancellation completion notice includes information on the product registration update screen changed to a mode indicating that the corresponding list item, which indicated that it was a suspended product, has been normally registered by the current suspension cancellation.

[0128] When the client terminal device 50 receives the suspension cancellation completion notice, first, it displays a suspension cancellation confirmation screen WD53 instead of the suspension cancellation standby screen WD52 that has been displayed so far. FIG. 13(C) shows an example of the suspension cancellation confirmation screen WD53. On the suspension cancellation confirmation screen WD53 in the figure, a message notifying the customer that the suspension cancellation remote operation has been completed and the suspension has been cancelled, and a confirmation button BT53 are arranged. By viewing the displayed hold cancellation confirmation screen WD53, the customer can grasp that the hold cancellation of the held item as the current unspecified item has been completed. As confirmation that the hold cancellation has been completed, the customer operates the confirmation button BT53.

[0129] In response to the operation of the confirmation button BT53, the customer terminal device 50 erases the hold cancellation confirmation screen WD53. Further, the customer terminal device 50 updates the display of the product registration screen by using the information of the product registration update screen included in the hold cancellation completion notification.

[0130] Figure 13(D) shows the product registration screen updated after the hold cancellation confirmation screen WD53 has been erased. In the product registration screen of this figure, in the product registration screens of Figures 13(A) to 13(D), the bottom list item shown as "Held Item: NON - FILE" has changed to a state where the product name is displayed like "○○ Bread" and the price (selling price) is also displayed. Further, in the bottom list item of the product registration screen of this figure, for example, by being displayed as "Hold Cancelled", it is shown that the product corresponding to the list item has been normally registered due to the hold cancellation.

[0131] In the case of the mode of displaying the hold cancellation standby screen WD52 as illustrated in Figure 13(B), the once - displayed hold cancellation standby screen WD52 is not erased until the hold cancellation remote operation is completed. In this case, even if the customer still has an item to register, while the hold cancellation standby screen WD52 is being displayed, the customer cannot perform the product registration operation and must wait. Therefore, instead of displaying the hold cancellation waiting screen WD52 in response to the operation of the operation request button BT51 (Fig. 13A) on the hold cancellation guidance screen WD51, the client terminal device 50 may transition to the following display. That is, the client terminal device 50 may operate the hold cancellation guidance screen WD51 in response to the operation of the operation request button BT51 and return to the product registration screen. Moreover, on the product registration screen, in the list item of the held product targeted for the hold cancellation remote operation request, display is performed in a predetermined manner indicating that it is waiting for the completion of the hold cancellation remote operation. Then, in response to the completion of the hold cancellation remote operation, on the product registration screen, a notification that the hold cancellation remote operation has been completed and the hold of the held product has been cancelled is made in a predetermined manner. The notification of the cancellation of the hold may be, for example, a pop-up window in which a message notifying the cancellation of the hold according to Fig. 13(C) is shown. Also, the notification of the cancellation of the hold may be accompanied by the output of sound, vibration, etc. together with the display. By making the product registration screen be displayed after the operation of the operation request button BT51 in this way, even while the hold cancellation remote operation is being performed, the customer can perform product registration operations.

[0132] Also, if the customer determines not to request a hold cancellation remote operation at this stage because, as shown in Fig. 13(A), when performing settlement at the settlement device 40 while the hold cancellation guidance screen WD51 is displayed, the customer asks the settlement device 40 to cancel the hold, the customer operates the non-operation declaration button BT52. When the non-operation declaration button BT52 is operated, the client terminal device 50 deletes the hold cancellation guidance screen WD51 and returns to the state where the product registration screen is displayed. In this case, the client terminal device 50 does not transmit operation request information, etc. to the transaction management device 60. Also, in this case, in the list item of the corresponding held product on the product registration screen displayed after the deletion of the hold cancellation guidance screen WD51, the display indicating that it is the held product before the non-operation declaration button BT52 was operated is maintained.

[0133] In addition, when a store employee using the monitoring device 80 determines to cancel the hold by deleting the registration of the held item as an unspecified item as a hold cancellation remote operation, the employee operates the delete button BT33 on the product information input screen. When the delete button BT33 is operated, the monitoring device 80 sends a hold cancellation request instructing the deletion of the registration as a held item to the transaction management device 60. In this case, the transaction management device 60 deletes the held item information of the held item to be cancelled this time from the cart information in response to the reception of the hold cancellation request. As a result, the held item as an unspecified item is treated as if the registration has been deleted, and the hold is cancelled. In this case, the transaction management device 60 is configured to include, in the hold cancellation completion notice sent to the customer terminal device 50 in response to the hold cancellation, the information of the product registration update screen in which the corresponding list item indicating that it is a held item has been deleted.

[0134] Also, there may be cases where the customer decides to cancel the hold of the held item by deleting the registration. As an example, a case can be cited where the customer accidentally caused the customer terminal device 50 to read the code for an item that the customer did not intend to purchase, but then returned the item to the shelf as it was. Therefore, the deletion of the registration of the held item as an unspecified item may be made, for example, specifiable by the customer when performing the operation of requesting the hold cancellation remote operation. In this case, for example, on the hold cancellation guidance screen WD51, an operation may be enabled to request the hold cancellation remote operation after selecting either changing to a normal registration or deleting the registration as the hold cancellation.

[0135] Next, an example will be described in the case where, as a result of the customer performing a product registration operation using the customer terminal device 50, the product to be registered is determined to be an unspecified item corresponding to any one of "Reading NG", "Pseudo-scan input", and "Non-scan input" with classification numbers 2 to 4. Also in this case, the client terminal device 50 displays a hold cancellation guidance screen WD51 as shown in Fig. 13(A). However, in this case, on the product registration screen displayed in the background of the hold cancellation guidance screen WD51, the list item of the bottommost product indicating the result of the current product registration operation shows, for example, instead of the display of "Held Product: NON-FILE", content indicating that the reading of the product code by the product registration operation has failed, such as "Held Product: Code Unreadable". Also, in this case as well, when the hold cancellation guidance screen WD51 is displayed, the customer operates either the operation request button BT51 or the no-operation declaration button BT52 according to his or her own judgment on whether to request a hold cancellation remote operation. When the operation request button BT51 is operated, in response to the hold cancellation remote operation performed by the store clerk at the monitoring device 80, on the client terminal device 50, as shown in Figs. 13(B) and 13(C), the display on the display unit 504 transitions. Then, in response to the customer operating the confirmation button BT53 on the hold cancellation confirmation screen WD53 displayed as shown in Fig. 13(C), a product registration screen reflecting the current hold cancellation is displayed as shown in Fig. 13(D).

[0136] Also, in this case, the product information input screen displayed in response to the monitoring device 80 receiving a hold cancellation remote operation request may be the same as Fig. 14(A). However, when the unspecified product corresponds to any one of "Reading NG", "Pseudo-Scan Input", and "Non-Scan Input" in classification numbers 2 to 4, the product code has not been acquired by the product registration operation. Therefore, in the initial display state of the product information input screen, in addition to the product name input area AR30-2, the selling price input area AR30-3, the product type input area AR30-4, and the warning type input area AR30-5, the information in the product code input area AR30-1 is also in an uninput state.

[0137] In this case, if the store clerk is to perform normal registration by canceling the hold through a remote hold cancellation operation, the clerk is required to input information into each input area AR30 on the product information input screen. Also in this case, the store clerk can determine what kind of product it is by looking at the scan status image displayed in the scan status image area AR31. Then, after inputting information into each of the input areas AR30, the store clerk operates the confirmation button BT32 to display the input information confirmation screen, and performs an instruction operation to execute the hold cancellation for the displayed input information confirmation screen. As a result, the hold is canceled for the unspecified product, and then normal registration is performed. When the unspecified product corresponds to any one of "Reading NG", "Pseudo Scan Input", and "Non-Scan Input" with classification numbers 2 to 4, the store clerk may input the product name or the like grasped by looking at the scan status image displayed in the scan status image area AR31 as a search key (search condition), and for example, operate the search button BT31 to execute a search. In this case, the monitoring device 80 accesses, for example, the product master stored in the transaction management device 60 or the management device 10 to search for a product corresponding to the input search key. The store clerk performs an operation to specify the corresponding product from among the searched products. The monitoring device 80 can obtain the product information of the specified product from the product master and use the obtained product information to input information into each input area AR30.

[0138] Also, when the unspecified product corresponds to "NON-FILE" with classification number 1, it may be possible to search for the product for normal registration. However, the determination result that the unspecified product corresponds to "NON-FILE" is due to the absence of corresponding product information in the product master stored in the transaction management device 60. Therefore, if the unspecified product corresponds to "NON-FILE", there is no meaning in accessing the product master of the transaction management device 60 for product search, as in the case of unspecified products of "Reading NG", "Pseudo-scan input", and "Non-scan input". However, for example, although corresponding product information is registered in the product master of the store controller (e.g., the management device 10 may also be used) of the store or in the product master database provided outside the store such as the headquarters of affiliated stores (store chains), there is a possibility that this registered product information is not reflected in the product master of the transaction management device 60. Therefore, when the unspecified product corresponds to "NON-FILE", the monitoring device 80 may be configured to access the product master stored in the store controller or the product master database outside the store in response to the operation of the search button BT31, and search for the product information of the product corresponding to the input search key.

[0139] In addition, when the store clerk cancels the registration as an unspecified product by means of a hold cancellation remote operation, the store clerk operates the delete button BT33 on the product information input screen.

[0140] Next, with reference to FIG. 14(B), another example of the product information input screen displayed on the monitoring device 80 will be described. In the product information input screen of this figure, an input area AR40 (product code input area AR40-1, product type input area AR40-2, warning type input area AR40-3, product name input area AR40-4, selling price (sale value) input area AR40-5, quantity unit input area AR40-6, tax exemption flag input area AR40-7, special sale setting input area AR40-8, tax information input area AR40-9), a scan status image area AR41, a search button BT41, a confirmation button BT42, and a delete button BT43 are arranged. On such a product information input screen, for each of the input areas AR40, as simple product information, the product code, product type, warning type, product name, selling price (sale value), unit of quantity, tax exemption flag, special sale setting, and tax information are to be input. On the product information input screen of Fig. 14(B), for example, since information regarding tax exemption, consumption tax, special sales, etc. can also be input as simple product information, when releasing the hold on an unspecified product and performing normal registration, settings such as tax exemption, consumption tax, special sales, etc. can be made in advance.

[0141] The state where a product is registered in the cart information as a held product is an incomplete state where it cannot directly proceed to the settlement stage as it is, and it needs to be resolved by changing to normal registration or deleting the registration before proceeding to the settlement stage. In this embodiment, since a remote operation for releasing the hold is possible with the monitoring device 80, the registration as a held product can be released even at a stage before settlement is performed by the settlement device 40. Also, for example, it is possible to distribute the release of the hold on the held product between the monitoring device 80 and the settlement device 40. As a result, the release of the hold on the held product can be performed efficiently.

[0142] Also, the information items as simple product information input to the product information input screen during the remote operation for releasing the hold are some of the information items included in the product information stored in the product master. The information items included in the product master are, corresponding to each of the input area AR30 in Fig. 14(A) and the input area AR40 in Fig. 14(B), in addition to the product code, product name, selling price, product type, warning type, unit of quantity, tax exemption flag, special sale setting, and tax information, for example, medium classification, small classification, cost price, standard retail price, size, weight, specification, content volume, registration date and time, update date and time, etc. For example, taking medium classification and small classification as examples, they may be necessary for product management in the store, but are not necessarily required for transactions. That is, among the information items included in the product master, there is information that does not necessarily need to be used during transactions.

[0143] Therefore, in the present embodiment, for the information items input to the input areas AR30 and AR40 on the product information input screen where the hold cancellation remote operation is performed, the information items required to enable the transaction are limited. As a result, when performing the hold cancellation remote operation, the store clerk no longer needs to input more information items than necessary, thus improving the efficiency of hold cancellation for unspecified products.

[0144] Note that it is not necessary for the input of information items corresponding to all input areas (AR30, AR40) arranged on the product information input screen to be mandatory. Also, on the product information input screen, for example, when information items that can identify the classification of the product, such as the product name or product type, are input, among the remaining uninput input areas, for the information items that are no longer mandatory or become non-inputtable under the corresponding classification, the input areas may be changed in such a way that this is indicated.

[0145] [Example of processing procedure] With reference to the flowchart of FIG. 15, an example of the processing procedure executed by the customer terminal device 50, the transaction management device 60, and the monitoring device 80 in relation to the hold cancellation of unspecified products will be described. The processing in this figure shows more specifically, in correspondence with FIG. 9, the processing process of steps S5 to S11 including the processing corresponding to unspecified products.

[0146] First, an example of the processing procedure executed by the customer terminal device 50 will be described. Step S101: The customer terminal device 50 waits for a code scan corresponding to a product registration operation in a state where the product registration screen is displayed, and determines whether the reading of the product code (acquisition of the product code) by the code scan has been successfully completed in response to the product registration operation.

[0147] Step S102: When the reading of the product code is successfully completed, the customer terminal device 50 transmits product registration information including the read product code and cart identification information to the transaction management device 60.

[0148] Step S103: The client terminal device 50 receives the registration completion notification transmitted from the transaction management device 60 in response to the transmission of the product registration information in step S102. The client terminal device 50 updates the product registration screen by using the information of the product registration update screen included in the received registration completion notification, for example, as illustrated in FIG. 11(C).

[0149] The products for which registration has been completed by the transaction management device 60 in response to the registration completion notification received in step S103 include, in addition to the products normally registered in response to the reading of the product code, the "NON-FILE" with classification number 1, the "age confirmation products", "pharmaceuticals", and "anti-theft tag products" with classification numbers 5 to 7 as pending products. If the product to be registered this time is a pending product (unspecified product) as "NON-FILE" with classification number 1, a product list indicating that it is a pending product as "NON-FILE" is added to the updated product registration screen in step S103.

[0150] Step S104: The client terminal device 50 determines whether the registration result corresponding to the current product registration operation is a registration as a pending product of "NON-FILE" with classification number 1. If it is determined that the registration is a registration as a pending product of "NON-FILE" with classification number 1, the process transitions to step S108. If it is determined that the registration is not a registration as a pending product of "NON-FILE" with classification number 1, the process transitions to step S114.

[0151] Step S105: If the reading of the product code in step S101 is not completed normally, the product to be registered by the current product registration operation will be an unspecified product due to any of the "Reading NG", "Pseudo Scan Input", and "Non-Scan Input" with classification numbers 2 to 4. Therefore, in this case, the client terminal device 50 performs a classification determination as to which classification of "Reading NG", "Pseudo Scan Input", and "Non-Scan Input" corresponding to classification numbers 2 to 4 the unspecified product to be registered belongs to.

[0152] Customer terminal device 50 is configured to detect failure in reading the product code based on a captured image obtained by having imaging unit 506 capture an image when reading the product code in step S101. If failure in reading the product code is detected, it is determined in step S101 that reading of the product code was not completed normally.

[0153] Then, the customer terminal device 50 performs a determination in step S105 as follows, depending on the detected state of failure in reading the product code. First, when the customer terminal device 50 detects that the entire barcode of a product has been captured in the captured image, but that the reading of the barcode has not been completed successfully (successful) and a certain period of time has passed, it determines that the product code has been classified as "Read NG" under classification number 2.

[0154] In addition, when the customer terminal device 50 detects that the product code has not been read properly, that is, the product is recognized in the captured image but the barcode cannot be recognized at all and therefore the barcode reading was not completed successfully, it determines that the product is classified as a "pseudo scan input" under classification number 3. Alternatively, if the customer terminal device 50 detects that the product code reading was not completed successfully because only a portion of the product's barcode could be recognized in the captured image, it will determine that the item is classified as a "pseudo scan input" under classification number 3. Alternatively, if the customer terminal device 50 detects that the product's barcode was recognized in the captured image but the product was moving too quickly and the barcode reading was not completed successfully, it will determine that the item is classified as a "pseudo scan input" under classification number 3.

[0155] In addition, when a product code cannot be read, which is classified as classification number 3 "pseudo scan insertion," there is a possibility that fraud is being committed in which a customer simply pretends to scan the product's barcode and places the product in their shopping cart.

[0156] In addition, when the customer terminal device 50 is attached to the shopping cart so as to image the inside of the shopping basket, it is possible to image the contents of the shopping basket placed on the shopping cart. When the customer terminal device 50 detects a failure to read a product code indicating that a new product has been additionally placed in the shopping basket, even though it is not recognized that the barcode of the product is about to be read in the captured image, it determines that it is classified as "non-scanned input" with a classification number of 4.

[0157] For example, a customer may move a product that has already been registered in order to organize the contents of the shopping basket. The customer terminal device 50 may be configured to be able to distinguish such product movement from the additional placement of a new product corresponding to a failure to read a product code as "non-scanned input" based on the captured image. When such a failure to read a product code classified as "non-scanned input" occurs, there may be a possibility that fraud is being committed in which the customer puts the product directly into the shopping basket without having the barcode of the product read by the customer terminal device 50.

[0158] Step S106: The customer terminal device 50 transmits product registration information corresponding to the classification determined in step S105 to the transaction management device 60. The product registration information transmitted in step S106 does not include a product code. Further, the product registration information transmitted in step S106 may include information indicating the classification determined in step S105.

[0159] Step S107: The customer terminal device 50 receives a registration completion notice transmitted from the transaction management device 60 in response to the transmission of the product registration information in step S106. The customer terminal device 50 updates the product registration screen using the information on the product registration update screen included in the received registration completion notice. On the updated product registration screen, for example, a product list indicating that it is a reserved product (unspecified product) corresponding to any of classification numbers 2 to 4 is added.

[0160] Step S108: After the process of step S107, or when it is determined in step S104 that it is a registration as a reserved item of "NON-FILE" with classification number 1, the client terminal device 50 causes the hold cancellation guidance screen WD51 (Fig. 13(A)) to be displayed on the display unit 504.

[0161] Step S109: The client terminal device 50 determines whether the operation request button BT51 arranged on the hold cancellation guidance screen WD51 has been operated.

[0162] Step S110: When the operation request button BT51 is operated, the client terminal device 50 transmits operation request information to the transaction management device 60. Step S111: Further, the client terminal device 50 causes the hold cancellation waiting screen WD52 to be displayed instead of the hold cancellation guidance screen WD51.

[0163] While the hold cancellation waiting screen WD52 is being displayed, the client terminal device 50 waits for the reception of the hold cancellation completion notification transmitted from the transaction management device 60. When the hold cancellation completion notification is received, the client terminal device 50 causes the hold cancellation confirmation screen WD53 to be displayed instead of the hold cancellation waiting screen WD52.

[0164] The hold cancellation confirmation screen WD53 displayed in step S112 is erased in response to an operation on the confirmation button BT53 by the customer. When the hold cancellation waiting screen WD52 is erased, the client terminal device 50 updates the product registration screen using the information on the product registration update screen included in the hold cancellation completion notification received in step S112. When the normal registration of the product targeted for hold cancellation is performed, in the updated product registration screen, the product list of the targeted product, which was indicated as a reserved product, has changed to a state indicating that it has been normally registered. Also, when the registration of the targeted product, which was in the hold state as a hold cancellation, is deleted, in the updated product registration screen, the product list of the targeted product, which was indicated as a reserved product, has changed to a state where it has been deleted.

[0165] Step S114: After the process of step S113, or when it is determined in step S104 that the item is not registered as a "NON-FILE" hold item with classification number 1, or when it is determined in step S109 that the no-operation declaration button BT52 on the hold cancellation guidance screen WD51 has been operated, the customer terminal device 50 determines whether a settlement transition instruction operation has been performed while the product registration screen is being displayed. If the settlement transition instruction operation is not performed, the process returns to step S101.

[0166] Step S115: When the settlement transition instruction operation is performed, the customer terminal device 50, for example, encodes the cart identification information into a two-dimensional code and causes the generated two-dimensional code to be displayed on the display unit 504 by, for example, the code display screen illustrated in FIG. 11(D).

[0167] Next, a description will be given of an example of a processing procedure executed by the transaction management device 60. Step S201: The transaction management device 60 determines whether it has received the product registration information transmitted from the customer terminal device 50 in step S102.

[0168] Step S202: When the transaction management device 60 receives the product registration information, it identifies the cart information indicated by the cart identification information included in the received product registration information. Step S203: The transaction management device 60 updates the cart information identified in step S202. That is, the transaction management device 60 adds the in-cart product information (registered product information or hold product information) based on the product code included in the product registration information received corresponding to step S201 to the identified cart information. Thereby, the product is registered in the cart information.

[0169] Depending on the update of the cart information in step S202, in addition to the normally registered products, products among the reserved products that do not fall under classification numbers 2 to 4 ("Reading NG", "Pseudo-scan input", "Non-scan input") are registered. That is, the update of the cart information in step S202 includes the registration of products for which the reading of the product code has been completed normally among the reserved products. Products for which the reading of the product code has been completed normally among the reserved products are "NON-FILE" of classification number 1, "Age confirmation product" of classification number 5, "Pharmaceutical product" of classification number 6, and "Security tag product" of classification number 7. Also, regarding the "Cancelled product" of classification number 8, although it is not reflected in the processing of the figure, in response to the cancellation operation being performed on the client terminal device 50, the transaction management device 60 updates the reserved product information of the corresponding product in the cart information so that the corresponding product is managed as a cancelled product.

[0170] Step S204: After the processing of step S203, the transaction management device 60 transmits a registration completion notice to the client terminal device 50.

[0171] Step S205: After the processing of step S204, or when it is determined in step S201 that product registration information is not received, the transaction management device 60 determines whether product registration information of a reserved product (unspecified product) corresponding to any of classification numbers 2 to 4 ("Reading NG", "Pseudo-scan input", "Non-scan input") transmitted from the client terminal device 50 in step S106 is received. If the product registration information is not received, the process returns to step S201.

[0172] Step S206: When the product registration information is received, the transaction management device 60 specifies the cart information indicated by the cart identification information included in the received product registration information. Step S207: The transaction management device 60 updates the cart information identified in step S206. In this case, the transaction management device 60 adds the hold item information including the classification number included in the product registration information received corresponding to step S205 to the identified cart information. Thereby, one hold item corresponding to a hold item (unspecified item) corresponding to any of classification numbers 2 to 4 ("reading NG", "pseudo-scan input", "non-scan input") in the cart information is registered. Step S208: After the process of step S207, the transaction management device 60 transmits a registration completion notification to the client terminal device 50.

[0173] Step S209: After the process of step S208, the transaction management device 60 determines whether operation request information transmitted from the client terminal device 50 is received by step S110. If it is determined that the operation request information is not received, the process returns to step S201.

[0174] Step S210: When it is determined in step S209 that the operation request information has been received, the transaction management device 60 transfers the received operation request information to the monitoring device 80. At this time, the transaction management device 60 is configured to include the hold item information added to the cart information in the update of the cart information in step S207 in the operation request information.

[0175] Step S211: In response to the operation request information transmitted in step S210, a hold cancellation request (cart information update request) corresponding to the completion of the hold cancellation remote operation is transmitted from the monitoring device 80. The transaction management device 60 updates the cart information in response to the reception of the hold cancellation request. That is, when the hold cancellation request includes simple product information, the transaction management device 60 generates registered product information using the simple product information. The transaction management device 60 replaces the hold item information added when updating the cart information in step S207 with the generated registered product information. Thereby, the hold item as an unspecified item is normally registered and the hold is cancelled. In addition, when the transaction management device 60 instructs to delete the registration of the reserved item corresponding to the release request, the transaction management device 60 deletes the reserved item information added when updating the cart information in step S207 from the cart information. As a result, the reserved item as an unspecified item is released from reservation by canceling the registration.

[0176] Step S212: In response to the cancellation of the reservation being performed by updating the cart information in step S211, the transaction management device 60 transmits a reservation cancellation completion notice to the client terminal device 50.

[0177] Next, a description will be given of an example of a processing procedure executed by the monitoring device 80. Step S301: The monitoring device 80 waits for the operation request information transmitted from the transaction management device 60 in step S210 to be received.

[0178] Step S302: When the operation request information is received, the monitoring device 80 causes the display unit 806 to display the product information input screen.

[0179] Step S303: The store clerk performs a normal registration operation or a registration deletion operation as a remote operation for canceling the reservation on the displayed product information input screen. The normal registration operation is an operation of inputting information into the input area AR30 (AR40) and instructing the execution of reservation cancellation for the input information confirmation screen displayed by operating the confirmation button BT32 (BT42). The registration deletion operation is an operation on the deletion button BT33 (BT43). The monitoring device 80 accepts the remote operation for canceling the reservation performed as described above.

[0180] Step S304: In response to the completion of the remote operation for canceling the reservation, the monitoring device 80 transmits a reservation cancellation request to the transaction management device 60. The reservation cancellation request includes simple product information based on the information input into the input area AR30 (AR40) when the normal registration operation is performed as the remote operation for canceling the reservation. Further, the reservation cancellation request has content instructing the deletion of the registration of the corresponding reserved item when the registration deletion operation is performed as the remote operation for canceling the reservation.

[0181] <Modification Example> Hereinafter, modification examples of the present embodiment will be described. The modification examples described below may be combined with the above-described embodiment and other modification examples as appropriate.

[0182] [First Modification Example] In the above-described embodiment, the held items subject to the hold cancellation remote operation are those corresponding to four classifications of "NON-FILE", "Read NG", "Pseudo-Scan Input", and "Non-Scan Input" as unspecified items. As this modification example, a hold cancellation remote operation may be enabled for predetermined held items corresponding to classifications other than the above four classifications. As an example, for "age confirmation items", for example, depending on the store clerk's confirmation that the customer is of an age at which the item can be sold based on the customer's membership information or the customer's face image transmitted from the customer terminal device 50, the hold may be cancelled and normal registration may be enabled.

[0183] [Second Modification Example] In the above-described embodiment, in response to the transmission of operation request information from the customer terminal device 50, the monitoring device 80 displays a product information input screen, and the store clerk performs a hold cancellation remote operation. However, for example, there may be a case where operation request information is transmitted from a plurality of different customer terminal devices 50 almost simultaneously. Therefore, the monitoring device 80 may be configured to be able to display a list of corresponding customers (operation request list) for each customer terminal device 50 that has transmitted operation request information. The store clerk may select one list item from among the list items presented in the operation request list and perform a hold cancellation remote operation corresponding to the operation request information corresponding to the selected list item. Also, the list items in the operation request list may be sortable according to a predetermined sorting criterion. For example, the list items in the operation request list may be sortable based on the reception order of the operation request information, the registration count order of the held items among the registered products, etc.

[0184] [Third Modification Example] Further, in the monitoring device 80, a list of customers (customers with reserved items list) corresponding to transactions in which reserved items are registered may be displayed. In this case, for example, based on past transaction histories, for list items of customers with a high frequency of reserved item registration, they may be displayed in a manner different from other list items so that this can be grasped. Also, the list items of the customers with reserved items list may be made sortable according to a predetermined sorting criterion. For example, the list items of the customers with reserved items list may be made sortable in the order of the current number of item registrations. Also, the list items of the customers with reserved items list may be sorted according to the distance between the current position of the corresponding customer and the settlement device 40 for each list item. The current position of the customer is obtained by acquiring the current position of the customer terminal device 50. The monitoring device 80 can acquire, for example, position information measured by the customer terminal device 50 using a positioning function corresponding to its own GPS or the like via, for example, the transaction management device 60. Also, for example, beacons for acquiring terminal identification information by communicating with the customer terminal device 50 are provided at each predetermined position in the store, and the monitoring device 80 can also acquire the position information of the customer terminal device 50 by associating the position information received from the beacon with the position of the beacon that is the transmission source of the position information. Also, the list items of the customers with reserved items list may be made sortable in the order of the credit level of the corresponding customer for each list item. For example, the transaction management device 60 stores credit level information in which a credit level is set for each customer based on the customer's past transaction records and the like. The monitoring device 80 can acquire the credit level of the corresponding customer for each list item from the credit level information stored by the transaction management device 60.

[0185] [Fourth Modification Example] In the above embodiment, when a customer performs an operation of requesting a hold cancellation remote operation on the customer terminal device 50 (operation on the operation request button BT51), a product information input screen for normal registration of the target held product is displayed on the monitoring device 80. That is, in the above embodiment, in response to the customer performing an operation of requesting a hold cancellation remote operation, a store clerk is enabled to perform a hold cancellation remote operation for canceling the hold of the held product. However, even if the customer does not perform an operation of requesting a hold cancellation remote operation, a store clerk may be enabled to perform a hold cancellation remote operation for canceling the hold of the held product. For example, the registration result of a held product as "NON-FILE" is caused by a deficiency on the store side, such as the corresponding product information not being registered in the product master. Therefore, for example, when a held product as "NON-FILE" is registered, the customer terminal device 50 may transmit operation request information to the transaction management device 60 even if the customer does not perform an operation of requesting a hold cancellation remote operation. In response to receiving the operation request information, the transaction management device 60 can display a product information input screen corresponding to the held product registered as corresponding to "NON-FILE". As a result, when a held product as "NON-FILE" is registered, a store clerk can operate the monitoring device 80 to perform normal registration without the customer performing an operation of requesting a hold cancellation remote operation (request for normal registration). In this case, since the customer does not need to perform an operation for requesting normal registration even though it is a deficiency on the store side, it is less likely for the customer to feel dissatisfied.

[0186] Note that when a store clerk is enabled to perform a hold cancellation remote operation for canceling the hold of a held product without a request from the customer in this way, even if the customer terminal device 50 transmits operation request information, it does not need to display a hold cancellation guidance screen WD51 or a hold cancellation standby screen WD52 as shown in FIGS. 13(A) and 13(B). However, if in this case, a hold cancellation confirmation screen WD53 in the form exemplified in FIG. 13(C) is displayed in response to the completion of the hold cancellation of the held product by the hold cancellation remote operation by the store clerk, the completion of the hold cancellation will be notified to the customer abruptly, and for example, the customer is likely to be confused. Therefore, in this case, on the hold cancellation confirmation screen WD53, it is preferable to display a message that allows the customer to understand that although the customer's request was not solicited, the store clerk performed a remote hold cancellation operation. For example, the message could be something like "The previous item could not be registered properly, so the store clerk handled it remotely."

[0187] [Fifth Modification Example] The monitoring device 80 in the above-described embodiment may be, for example, a terminal installed in the backyard of a store, or it may be a mobile terminal carried by a store clerk.

[0188] [Sixth Modification Example] In the above-described embodiment, the monitoring device 80 is configured to obtain the product information included in the operation request information by receiving the operation request information transmitted by the customer terminal device 50 via the transaction management device 60. That is, the monitoring device 80 in the above-described embodiment is configured to passively obtain product information. However, the monitoring device 80 may be configured to actively obtain product information by, for example, querying the transaction management device 60 for product information at a predetermined timing such as every certain period of time. In this case, the transaction management device 60 may transmit the product information that it has received from the customer terminal device 50 and stored in response to the query from the monitoring device 80 to the monitoring device. Alternatively, the transaction management device 60 may cause the customer terminal device 50 to transmit the product information in response to the query from the monitoring device 80 and transfer the received product information to the monitoring device. Also, the product information may be transmitted and received directly between the customer terminal device 50 and the monitoring device 80 without the transaction management device 60 acting as a relay.

[0189] [Seventh Modification Example] In addition, in the above-described embodiment, part of the processing executed by the customer terminal device 50 may be executed by, for example, the transaction management device 60, the monitoring device 80, the settlement device 40, the management device 10, other upper-level devices within the store, or server devices on the cloud. Similarly, part of the processing executed by each of the transaction management device 60, the monitoring device 80, the settlement device 40, the management device 10, etc. may be executed by other devices. As one of the above-described aspects, the shopping system of the present embodiment may include a configuration of a sync client system. As an example, the transaction management device 60 or another server may be configured as a server compatible with sync clients (for example, a cloud server), and the customer terminal device 50, the monitoring device 80, etc. may be made to function as sync clients. In addition, the transaction management device 60, the monitoring device 80, the management device 10, etc. may be configured to be distributed among a plurality of computer devices and servers.

[0190] <Summary of the Embodiment> [Technical Field] The present invention relates to a product sales data processing system. [Background Art] A system in which customers register products themselves using a mobile terminal is known (see, for example, Patent Document 1). [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Patent Application Laid-Open No. 2018-147252 [Summary of the Invention] [Problems to be Solved by the Invention] In a product sales data processing system in which customers register products themselves using a mobile terminal, the registration result of a product may be incomplete. For a product with an incomplete registration result, for example, the incomplete state of the registration result is eliminated by the operation of a store clerk. It is preferable that such elimination of the incomplete state of the registration result be performed efficiently. The present invention has been made in view of such circumstances, and an object thereof is to enable the elimination of an incomplete state of a product registration result to be performed efficiently in a product sales data processing system in which customers register products themselves using a mobile terminal.

[0191] [Means for Solving the Problem] (1) As described above, one aspect of the present embodiment is a product sales data processing system that registers a product based on a product registration operation using a customer's mobile terminal device (for example, the customer terminal device 50). When the registration result of the product based on the product registration operation is incomplete (for example, when registered as a pending product), registration incomplete product information (for example, operation request information (including cart identification information and pending product reference information), S210) regarding the registration incomplete product (for example, the pending product) with an incomplete registration result is acquired by a monitoring device (for example, the monitoring device 80) used by a store clerk, a display control means for causing the monitoring device to display a screen (for example, a product information input screen) based on the registration incomplete product information acquired by the acquisition control means, and a normal registration means for performing a normal registration of registering the registration incomplete product as a normal product in response to the input of registration completion information (for example, simple product information input into the input area AR30 (AR40)) with respect to the displayed screen. A product sales data processing system comprising:

[0192] According to the above configuration, when a pending product is registered as a result of performing a product registration operation, a store clerk can perform a remote operation to cancel the pendency on the monitoring device 80 to cancel the pendency. As a result, even at a stage before settlement is performed by the settlement device 40, the registration as a pending product can be cancelled. Also, for example, it becomes possible to distribute the cancellation of the pendency of the pending product between the monitoring device 80 and the settlement device 40. As a result, the cancellation of the pendency of the pending product (an example of resolving a state where the registration result of the product is incomplete) can be performed efficiently.

[0193] (2) One aspect of this embodiment is the product sales data processing system described in (1), wherein the incompletely registered product is a product for which product information associated with the product code acquired by the mobile terminal device in response to the product registration operation does not exist in the product information database (e.g., product master) used for product management in the store (e.g., a pending product classified as "NON-FILE"). The display control means displays a screen that presents a predetermined part of the information items included in the product information as input items for the registration completion information (e.g., input areas AR30 (AR40)), and the normal registration means performs normal registration of the incompletely registered product based on the product code and the information input into the input items.

[0194] According to the above configuration, as a remote operation for releasing the hold on a pending product classified as "NON-FILE", by inputting predetermined information items other than the product code acquired by the product registration operation into the product information input screen, the information necessary for product registration is complemented, and it becomes possible to release the hold as normal registration.

[0195] (3) One aspect of this embodiment is the product sales data processing system described in (1) or (2), wherein the incompletely registered product is a product for which the product code could not be acquired from the captured image as a result of the product registration operation that caused the mobile terminal device to capture the product code. The display control means presents the captured image as an image showing the product to be normally registered to the user (e.g., store clerk), and displays a screen that presents a predetermined part of the information items included in the product information stored in the product information database used for product management in the store as input items for the registration completion information. The normal registration means performs normal registration of the incompletely registered product based on the information input into the input items.

[0196] According to the above configuration, as a remote operation for releasing the hold on the held goods classified as "Reading NG", "Pseudo-scan input", or "Non-scan input", by inputting predetermined information items on the product information input screen, the information necessary for product registration will be supplemented, and it will be possible to release the hold as normal registration.

[0197] (4) One aspect of this embodiment is the product sales data processing system according to any one of (1) to (3), wherein the display control means controls so that a list of customers including the unregistered products among the registration results of the products based on the product registration operation is displayed on the monitoring device.

[0198] According to the above configuration, the store clerk can grasp the situation of the customers registering the held goods in the store by means of the monitoring device 80.

[0199] (5) One aspect of this embodiment is the product sales data processing system according to any one of (1) to (4), further comprising notification control means for controlling so that a display for notifying the customer that the registration result in an incomplete state can be resolved by an operation of the store clerk on the monitoring device is performed on the portable terminal device when the registration result of the product based on the product registration operation is incomplete.

[0200] According to the above configuration, the customer can request the store clerk to perform a remote operation for releasing the hold after being notified that the remote operation for releasing the hold is possible.

[0201] (6) One aspect of this embodiment is the product sales data processing system according to any one of (1) to (5), wherein the acquisition control means causes the monitoring device used by the store clerk to acquire the unregistered product information even without receiving an operation for requesting normal registration (for example, an operation on the operation request button BT51) by the customer when the registration result of the product based on the product registration operation is incomplete.

[0202] According to the above configuration, even if the customer does not perform an operation to request normal registration, the store clerk can cancel the reservation of the product registered as a reserved product. Such a configuration is effective in that normal registration can be performed without requesting the customer to perform an operation to request normal registration when the product is registered as a reserved product due to a deficiency on the store side, for example, like "NON-FILE".

[0203] (7) One aspect of this embodiment is a program for causing a computer in a product sales data processing system that registers a product based on a product registration operation using a mobile terminal device by a customer to function as acquisition control means for causing a monitoring device used by a store clerk to acquire registration incomplete product information regarding a registration incomplete product whose registration result based on the product registration operation is incomplete, display control means for causing the monitoring device to display a screen based on the registration incomplete product information acquired by the acquisition control means, and normal registration means for performing normal registration to register the registration incomplete product as a normal product in response to registration completion information being input to the displayed screen.

[0204] (8) One aspect of this embodiment is a monitoring device used by a store clerk in a product sales data processing system that registers a product based on a product registration operation using a mobile terminal device by a customer, the monitoring device including acquisition means for acquiring registration incomplete product information regarding a registration incomplete product whose registration result based on the product registration operation is incomplete, display control means for displaying a screen based on the registration incomplete product information acquired by the acquisition means, and normal registration means for performing normal registration to register the registration incomplete product as a normal product in response to registration completion information being input to the displayed screen.

[0205] (9) One aspect of this embodiment is a program for causing a computer, which is a monitoring device used by a store clerk in a product sales data processing system that registers a product based on a product registration operation by a customer using a mobile terminal device, to function as an acquisition means for acquiring registration incomplete product information regarding a registration incomplete product whose registration result based on the product registration operation is incomplete, a display control means for displaying a screen based on the registration incomplete product information acquired by the acquisition means, and a normal registration means for performing normal registration to register the registration incomplete product as a normal product in response to the input of registration completion information to the displayed screen.

[0206] (10) One aspect of this embodiment is a server device (for example, the transaction management device 60) provided in a product sales data processing system that registers a product based on a product registration operation by a customer using a mobile terminal device, the server device including an acquisition control means for causing a monitoring device used by a store clerk to acquire registration incomplete product information regarding a registration incomplete product whose registration result based on the product registration operation is incomplete, a display control means for causing a monitoring device operated by the store clerk to display a screen based on the registration incomplete product information acquired by the acquisition control means, and a normal registration means for performing normal registration to register the registration incomplete product as a normal product in response to the input of registration completion information to the screen displayed on the monitoring device.

[0207] In addition, a program for realizing functions as the above-described management device 10, settlement device 40, customer terminal device 50, transaction management device 60, monitoring device 80, etc. in each of the above embodiments is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read into a computer system and executed, thereby performing processes as the above-described management device 10, settlement device 40, customer terminal device 50, transaction management device 60, monitoring device 80, etc. Here, "reading and executing the program recorded on the recording medium into the computer system" includes installing the program in the computer system. The "computer system" as used herein is assumed to include hardware such as an OS and peripheral devices. Further, the "computer system" may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, or dedicated line. The "computer-readable recording medium" refers to a portable medium such as a flexible disk, magneto-optical disk, ROM, CD-ROM, or a storage device such as a hard disk built into the computer system. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The recording medium also includes an internal or external recording medium provided so as to be accessible from a distribution server for distributing 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 executable on the terminal device. That is, any form stored in the distribution server may be used as long as it can be downloaded from the distribution server and installed in a form executable on the terminal device. Note that the program may be divided into a plurality of parts, downloaded at different timings, and then combined on the terminal device, or the distribution servers for distributing the divided programs may be different. Further, the "computer-readable recording medium" also includes a volatile memory (RAM) inside a computer system serving as a server or a client when a program is transmitted via a network, which holds the program for a certain period of time. Also, the above program may be for realizing a part of the above-described functions.Furthermore, it may be a so-called differential file (differential program) that can be realized in combination with a program already recorded in the computer system for the above-described functions.

Explanation of Signs

[0208] 10 Management device, 40 Settlement device, 50 Client terminal device, 60 Transaction management device, 70 Credit card payment server, 80 Monitoring device

Claims

1. A product registration means for registering a product based on a product registration operation by a customer using a terminal device, A display control means for displaying a screen related to a product with incomplete registration whose registration result by the product registration means is incomplete, Normal registration means for performing normal registration of registering the product with incomplete registration as a normal product in response to the input of registration completion information, and The product with incomplete registration is a product for which product information associated with a product code acquired by the terminal device in response to the product registration operation does not exist in a product information database used for product management in the store, The display control means displays, on the screen related to the product with incomplete registration, so as to include an image of the corresponding product with incomplete registration when it was registered by the product registration means A product sales data processing system.

2. The display control means displays the screen for presenting a predetermined part of information items included in the product information as input items for the registration completion information, The normal registration means performs normal registration of the product with incomplete registration based on the product code and the information input to the input items The product sales data processing system according to claim 1.

3. The product with incomplete registration is a product for which a product code could not be acquired from an imaging image by the terminal device as a result of the product registration operation of causing the terminal device to image a product code, The display control means presents the imaging image as an image showing a product to be normally registered to the user, and displays the screen for presenting a predetermined part of information items included in the product information stored in a product information database used for product management in the store as input items for the registration completion information, The normal registration means performs normal registration of the product with incomplete registration based on the information input to the input items The product sales data processing system according to claim 1 or 2.

4. Further comprising notification control means for controlling so that a display for notifying a customer that the registration result in an incomplete state can be resolved by an operation of a store clerk is performed on the terminal device when the registration result of the product based on the product registration operation is incomplete The product sales data processing system according to any one of claims 1 to 3.

5. A computer in a product sales data processing system, A product registration means for registering a product based on a product registration operation by a customer using a terminal device, A display control means for displaying a screen related to a registration-incomplete product whose registration result by the product registration means is incomplete; A normal registration means for performing normal registration to register the registration-incomplete product as a normal product in response to the input of registration completion information; A program for causing the above to function, wherein the registration-incomplete product is a product for which product information associated with a product code acquired by the terminal device in response to the product registration operation does not exist in a product information database used for product management at the store, and the display control means displays, on the screen related to the registration-incomplete product, so as to include an image of the corresponding registration-incomplete product when it was registered by the product registration means; Program.

Images