System and server

Abstract

To enable appropriate registration of products.SOLUTION: A system is provided, comprising: a product identification unit for identifying a product to be purchased; a generation unit configured to generate transaction information including unidentified information regarding the product when the product to be purchased cannot be identified by the product identification unit; a compilation / analysis unit for compiling or analyzing the transaction information generated by the generation unit; and an output unit for outputting a result of the compilation or analysis by the compilation / analysis unit.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a system and a server.

Background Art

[0002] There is known a product data processing device that displays a warning when an unregistered product is put into a basket (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] However, even if a warning is issued each time, inappropriate events during product registration, such as an unregistered product being put into a basket, do not necessarily decrease.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technique for appropriately registering products.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-described problems is a system including: a product identification unit that identifies a product to be purchased; a generation unit that generates transaction information including unspecified information about the product when the product to be purchased is not identified by the product identification unit; a aggregation / analysis unit that aggregates or analyzes the transaction information generated by the generation unit; and an output unit that outputs the result of the aggregation or analysis by the aggregation / analysis unit.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Embodiments for Carrying Out the Invention

[0008] FIG. 1 is a conceptual diagram of a network for explaining the sales system 1 of the present embodiment. The sales system 1 shown in FIG. 1 includes a store controller 10, a cloud server 20, a registration settlement device 30, a settlement device 40, a transaction status management device 50, a mobile terminal 60, and a tabulation analysis device 80.

[0009] The sales system 1 can be introduced into various business formats (supermarkets, convenience stores, drugstores, home centers, home appliance mass retailers, etc.). In FIG. 1, the dashed line T indicates the inside of the store (product display area, checkout area, backyard, office, etc.). As shown in FIG. 1, the store controller 10, the registration settlement device 30, the settlement device 40, the transaction status management device 50, and the tabulation analysis device 80 are installed inside the store. These are communicably connected via a LAN 19 (which may be wired or wireless). There is a mobile terminal 60 inside the store. The mobile terminal 60 is basically used in a state (set state) attached to a cart (shopping cart) 70 (specifically, a holder portion 72). The cloud server 20 is installed outside the store (for example, at the head office or data center, etc.). The devices installed inside the store (store controller 10, registration settlement device 30, settlement device 40, transaction status management device 50, tabulation analysis device 80) and the devices installed outside the store (cloud server 20) can communicate (communicate directly or via the store controller 10).

[0010] Note that in FIG. 1, the number of each device (terminal) is an example. For example, in FIG. 1, "..." is illustrated on the right side of the settlement device 40, but the number of settlement devices 40 installed inside the store may be one or more. Also, for example, in FIG. 1, two mobile terminals 60 are illustrated, but the number of mobile terminals 60 used inside the store varies according to the number of customers.

[0011] (Mobile Terminal 60) The mobile terminal 60 is used by customers. Specifically, the mobile terminal 60 is used when a customer registers a product in the store by himself / herself. A shopping application (hereinafter simply referred to as "app") having a self-registration function by the customer himself / herself is installed in the mobile terminal 60. The mobile terminal 60 is the customer's smartphone (a smartphone owned by the customer himself / herself).

[0012] Although illustration is omitted, the mobile terminal 60 includes, for example, a CPU, a storage unit, a display unit, an operation unit, a communication unit, and an imaging unit (camera).

[0013] The CPU is a central processing unit, and controls the entire mobile terminal 60 by reading and executing programs stored in the storage unit. The storage unit stores various information (for example, information referred to or generated by the CPU, information acquired from the outside, etc.). The storage unit is a general term for one or more various storage members (for example, those serving as memory or storage. For example, RAM, ROM, hard disk, SSD (Solid State Drive), etc.). The display unit is, for example, a liquid crystal display, and displays various information (including image information). The display unit is configured as a touch panel capable of receiving operations on the display screen. The operation unit receives operations of an operator (customer). The operation unit is a general term for one or more various operation members (various operation elements (hard buttons) provided on the housing). Since the display unit is configured as a touch panel, it may be regarded as a part of the operation unit. The communication unit transmits and receives various information. The communication unit is a general term for one or more various communication members (for example, communication members such as mobile wireless communication such as 5G, wireless LAN, short-range wireless communication, and non-contact communication). The imaging unit acquires (generates) an imaging image (still image, moving image).

[0014] Needless to say, the mobile terminal 60 (and other devices as well) includes a timing unit (timing function). For example, the mobile terminal 60 can manage the current time, the elapsed time from a certain point in time, and the remaining time until a certain time by the timing unit. Further, the mobile terminal 60 may include a detection unit (one or more various detection members such as a GPS sensor, an acceleration sensor, and a gyro sensor).

[0015] The mobile terminal 60 can display the captured image by the imaging unit on the display unit as a so-called through image (live view image). Instead of or in addition to displaying the captured image on the display unit as a through image, the mobile terminal 60 may store the captured image in the storage unit. That is, the mobile terminal 60 may store the captured image in the storage unit without displaying it on the display unit as a through image, or may display it on the display unit as a through image without storing it in the storage unit, or may store it in the storage unit while displaying it on the display unit as a through image. Further, the mobile terminal 60 may transmit the captured image to the cloud server 20.

[0016] The mobile terminal 60 is equipped with various image processing functions. For example, the mobile terminal 60 is equipped with an object recognition function for recognizing an object from the captured image. Further, the mobile terminal 60 is equipped with a barcode reading function for reading a barcode (code symbol) attached to a product from the captured image (that is, recognizing the barcode of the captured image by the object recognition function and reading the recognized barcode to obtain a product ID (product identification information)). Further, the mobile terminal 60 is equipped with a scan operation detection function for detecting a scan operation (sweeping operation) of a product by a customer from the captured image (for example, detecting based on whether a human hand or a barcode newly appears in the captured image). Further, the mobile terminal 60 may be equipped with an object detection function (background difference processing function) for detecting the appearance of an object (a new object) using a plurality of captured images (background image, observation image, etc.).

[0017] (Settlement device 40) The settlement device 40 is used by the customer. Specifically, the settlement device 40 settles the products registered by the mobile terminal 60 based on the customer's operation. When there are products that require confirmation by the store clerk during settlement, the store clerk is called and the store clerk (or the customer) operates the settlement device 40.

[0018] Although illustration is omitted, the settlement device 40 includes a CPU, a storage unit, a display unit, a scanner unit, a non-cash settlement unit (card settlement unit, code settlement unit), a cash settlement unit (change dispenser), a printing unit, an audio output unit, an imaging unit, and a communication unit. Note that the settlement device 40 may further include a key operation unit composed of one or more various operation members, a human sensor that detects (detects, recognizes) the presence of a person, and the like.

[0019] (Registered settlement device 30) The registered settlement device 30 is used by customers. Specifically, the registered settlement device 30 registers products based on the operations of customers and settles accounts based on the operations of customers. Although illustration is omitted, the registered settlement device 30 includes a CPU, a storage unit, a display unit, a scanner unit, a non-cash settlement unit (card settlement unit, code settlement unit), a cash settlement unit (change dispenser), a printing unit, an audio output unit, an imaging unit (camera), and a communication unit. Note that the registered settlement device 30 may further include a key operation unit composed of one or more various operation members, a human sensor that detects (detects, recognizes) the presence of a person, and the like.

[0020] (Cloud server 20) The cloud server 20 is a server that mainly supports the registration of products by the mobile terminal 60. The cloud server 20 stores various information (see FIG. 3). In addition, the cloud server 20 supplies various information (for example, screen information, etc.) to, for example, the mobile terminal 60 and devices installed in the store. Although illustration is omitted, the cloud server 20 includes at least a CPU, a storage unit, and a communication unit. The cloud server 20 may be composed of a plurality of servers.

[0021] (Store controller 10) The store controller 10 is a server mainly responsible for information communication between devices installed inside the store and devices installed outside the store. Although illustration is omitted, the store controller 10 includes at least a CPU, a storage unit, and a communication unit.

[0022] (Transaction status management device 50) The transaction status management device 50 is, for example, a device (such as a personal computer) that manages (monitors, controls, etc.) the registration settlement device 30, the settlement device 40, and the mobile terminal 60. For example, the transaction status management device 50 monitors (displays) the processing status and operation status of the registration settlement device 30 and the settlement device 40. Further, the transaction status management device 50 monitors (accesses the cloud server 20 and displays or modifies transaction information stored in the cloud server 20, etc.) the processing status and operation status of the mobile terminal 60. The transaction status management device 50 includes at least a CPU, a storage unit, a display unit (which may be configured as a touch panel), an operation unit (such as a keyboard and a mouse), and a communication unit. The transaction status management device 50 can communicate with a printing device (not shown) and may output various information from the printing device. The transaction status management device 50 is installed, for example, in an accounting area and is used by store clerks.

[0023] (Aggregation and analysis device 80) The aggregation and analysis device 80 is a device (such as a personal computer) that aggregates and analyzes transactions (past transactions). For example, the aggregation and analysis device 80 aggregates and analyzes transactions made by the mobile terminal 60 (accesses the cloud server 20 and aggregates and analyzes transaction information stored in the cloud server 20, etc.). The aggregation and analysis device 80 includes at least a CPU, a storage unit, a display unit (which may be configured as a touch panel), an operation unit (such as a keyboard and a mouse), and a communication unit. The aggregation and analysis device 80 can communicate with a printing device (not shown) and may output various information from the printing device. The transaction status management device 50 is installed, for example, in an office or a backyard and is used by store clerks.

[0024] Note that the sales system 1 may include devices other than those described above. For example, in a store, on one side (the store clerk side), there may be a display unit for store clerks, a scanner unit, etc., and on the other side (the customer side, the side opposite to the store clerk side), there may be a display unit for customers, a settlement unit (one or both of a cash settlement unit and a non-cash settlement unit), and a registration settlement device 31 (not shown) that registers products based on the operation of the store clerk and settles accounts based on the operation of the customer may be installed. Also, in the store, on one side, there may be a display unit for store clerks and a scanner unit for store clerks. On the other side, it has a customer display unit, a customer scanner unit, and a settlement unit (either one or both of a cash settlement unit and a non-cash settlement unit). As operating modes, it has a normal mode (similar to the registration and settlement device 31, an operation mode in which products are registered based on the operation of a store clerk and settlement is made based on the operation of a customer), and a full self-service mode (similar to the registration and settlement device 30, an operation mode in which products are registered based on the operation of a customer and settlement is made based on the operation of a customer). A registration and settlement device 32 (not shown) may be installed. Also, in the store, a registration and settlement device 33 (not shown) that registers products based on the operation of a store clerk and settles based on the operation of a store clerk may be installed. Further, in the store, a semi-self-service device group (a registration device 34 (not shown), a settlement device 35 (not shown)) that registers products based on the operation of a store clerk and settles based on the operation of a customer may be installed.

[0025] FIG. 2 is an explanatory diagram for explaining a cart 70 to which a mobile terminal 60 can be attached. As shown in FIG. 2, the cart 70 has a shopping basket placement part 71 on which a shopping basket (not shown) can be placed, and a holder part 72 to which the mobile terminal 60 can be attached.

[0026] In the example shown in FIG. 2, no shopping basket is placed on the shopping basket placement part 71, and the mobile terminal 60 is not attached to the holder part 72. However, a customer who comes to the store places a shopping basket on the shopping basket placement part 71 and attaches the mobile terminal 60 to the holder part 72. When imaging is performed by the imaging unit while the mobile terminal 60 is attached to the holder part 72, an imaging image in the direction of looking down from the position of the holder part 72 toward the shopping basket side is acquired.

[0027] FIG. 3 shows an example of various information. The cloud server 20 stores various types of information as shown in FIG. 3, for example.

[0028] The cloud server 20 stores a store master as shown in FIG. 3(A). The store master in FIG. 3(A) has data items such as a store ID (store identification information), store name, address, nearest station, and sales floor area.

[0029] The cloud server 20 stores a product master as shown in FIG. 3(B). The product master in FIG. 3(B) has data items such as product ID, classification, product name, etc. In addition to the PLU (JAN code, in-store code), the product ID may also store a preset number (described later).

[0030] The cloud server 20 stores a display position master as shown in FIG. 3(C). The display position master in FIG. 3(C) has data items of store ID, product ID, and display position. That is, the display position master indicates the display position for each store and each product.

[0031] The cloud server 20 stores a customer master as shown in FIG. 3(D). The customer master in FIG. 3(D) has data items such as customer ID (customer identification information), registered name, contact information, gender, date of birth, registration date, registration store, mobile terminal, app, etc. In the data item of the mobile terminal, the model name, type of OS, version of OS, etc. are stored. In the data item of the app, the type of app (distribution, media distribution, etc.), version of the app, etc. are stored.

[0032] For example, when the mobile terminal 60 downloads an app from the cloud server 20 (or another server that provides the app), the cloud server 20 may generate a customer master based on communication control information (information in the header part, etc.) between the cloud server 20 and the mobile terminal 60, information input in the registration form (input form), information of the app downloaded to the mobile terminal 60, etc. In addition, as a data item of the customer master, a terminal ID (terminal identification information) unique to the mobile terminal 60 that has downloaded the app may be stored. The terminal ID may be, for example, a phone number assigned to a customer who is a user of the mobile terminal 60, or hardware identification information such as a MAC (Media Access Control) address.

[0033] The cloud server 20 stores transaction information (also referred to as cart information) as shown in FIG. 3(E). The cloud server 20 generates transaction information at the start of product registration (self-registration) by individual mobile terminals 60. Also, the cloud server 20 updates the transaction information as the transaction progresses.

[0034] The transaction information in FIG. 3(E) has data items such as a transaction ID (transaction identification information), customer ID, total, transaction start date and time, transaction end date and time, settlement device, settlement type, registered products (registered product 1 to registered product N), presence / absence of unregistered secured products, unregistered secured products (unregistered secured product 1 to unregistered secured product N), etc.

[0035] The transaction ID is identification information that uniquely identifies transaction information (a transaction by self-registration). The transaction ID includes a store ID, date, and serial number. The customer ID is a customer ID that identifies the customer of the transaction. The total is the total points and total amount in the transaction. 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 transaction information. 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 settlement device is a device ID (device identification information) that identifies the settlement device 40 that executed the settlement process for the transaction. The settlement type is information indicating the settlement type (cash settlement, credit settlement, etc.) of the transaction (for example, cash settlement is 1, credit settlement is 2, electronic money settlement is 3, etc.).

[0036] The registered product M is registration information of the product registered in item M (for example, the product ID of the registered product in item M, the product name of the registered product in item M, the price of the registered product in item M). For example, when there are two product registrations in the transaction, registered product 1 (product ID of the registered product in item 1, product name of the registered product in item 1, price of the registered product in item 1), registered product 2 (product ID of the registered product in item 2, product name of the registered product in item 2, price of the registered product in item 2) are stored.

[0037] The unregistered secured item M is information on unregistered secured items of item M (described later) (for example, the date and time of generation of unregistered secured items of item M, the unregistered secured sub-classification of unregistered secured items of item M (described later), two or more image data before and after the generation of unregistered secured items of item M, etc.). For example, in the transaction, when there are two unregistered secured items, Unregistered Secured Item 1 (date and time of generation of unregistered secured items of item 1, unregistered secured sub-classification of unregistered secured items of item 1, two or more image data before and after the generation of unregistered secured items of item 1, etc.) and Unregistered Secured Item 2 (date and time of generation of unregistered secured items of item 2, unregistered secured sub-classification of unregistered secured items of item 2, two or more image data before and after the generation of unregistered secured items of item 2, etc.) are stored.

[0038] At the time of generating transaction information, information exists in the data items of transaction ID, customer ID, and transaction start date and time. However, since it is before the start of the actual transaction (product registration), information does not exist in other data items (transaction end date and time, settlement device, payment type, registered products, unregistered secured products). In the transaction information, data items without information may not exist (data items may be added when information exists).

[0039] The cloud server 20 stores customer performance information as shown in Fig. 3(F). The display position master in Fig. 3(F) has data items such as customer ID, last visit, total number of transactions, rank, and point information. The cloud server 20 generates (updates) customer performance information based on the transaction information after the transaction is completed.

[0040] Note that the information shown in Fig. 3 is an example of the information stored in the cloud server 20, and the cloud server 20 may store other information (for example, unregistered secured classification file (described later), store layout master (not shown), etc.).

[0041] (Unregistered Secured Item) An unregistered secured item is an item that has been secured without being registered. Unregistered secured items are items that require confirmation by the store clerk during settlement. Unregistered secured items are classified into several types.

[0042] FIG. 4 is an explanatory diagram for explaining the classification of unregistered secured products. In the present embodiment, unregistered secured products are classified by a major classification (unregistered secured major classification) and a minor classification (unregistered secured minor classification). Each device in the sales system 1 can refer to a file (unregistered secured classification file) showing the classification in FIG. 4.

[0043] Unregistered secured products are classified into two major classifications of unregistered secured product major classifications "1" and "2". Unregistered secured products classified into the unregistered secured product major classification "1" are NON-FILE unregistered secured products. NON-FILE unregistered secured products are unregistered secured products for which a product reading operation (an operation of holding the product barcode within the imaging range of the mobile terminal 60) has been performed and the product ID has been read, but the product ID is not stored in the product master. Only the unregistered secured product minor classification "11" exists under (subordinate to) the unregistered secured product major classification "1".

[0044] Unregistered secured products classified into the unregistered secured product major classification "2" are unregistered secured products with a reading failure. Unregistered secured products with a reading failure are unregistered secured products for which the product ID has not been read. Under the unregistered secured product major classification "2", unregistered secured product minor classifications "21" to "24" exist.

[0045] Unregistered secured products classified into the unregistered secured product minor classification "21" are unregistered secured products with pseudo scanning (such as covering). For example, unregistered secured products for which a product reading operation has been performed but the reading fails because part of the barcode is covered by a finger or the like, or unregistered secured products for which the reading fails because the imaging angle of the barcode is inappropriate, correspond to unregistered secured products with pseudo scanning (such as covering).

[0046] Unregistered secured products classified into the unregistered secured product minor classification "22" are unregistered secured products with pseudo scanning (short time). For example, unregistered secured products for which a product reading operation has been performed but the reading fails because the imaging time of the barcode is too short correspond to unregistered secured products with pseudo scanning (short time).

[0047] The unregistered secured products classified into the unregistered secured product subcategory "23" are unregistered secured products such as barcode defects. For example, among the unregistered secured products for which the product reading operation has been performed, unregistered secured products that have failed to be read due to wrinkles, scratches, dirt, etc. on the barcode, or unregistered secured products that have failed to be read due to barcode reflection, etc. correspond to unregistered secured products such as barcode defects.

[0048] The unregistered secured products classified into the unregistered secured product subcategory "24" are unregistered secured products of non-scan input. For example, among the unregistered secured products for which the product reading operation has not been performed (because the operation of holding the barcode of the product within the imaging range of the mobile terminal 60 has not been performed), unregistered secured products that have failed to be read correspond to unregistered secured products of non-scan input.

[0049] In addition, in FIG. 4, "reading operation: yes" indicates that the product reading operation has been performed, "reading operation: no" indicates that the product reading operation has not been performed, "reading success or failure: success" indicates that the barcode has been successfully read by the reading operation, and "reading success or failure: failure" indicates that the barcode has failed to be read by the reading operation.

[0050] FIGS. 5 to 7 are flowcharts showing an example of the operation of the mobile terminal 60. Although omitted in the flowcharts of FIGS. 5 to 7, the mobile terminal 60 always performs imaging by the imaging unit in order to recognize the barcode reading operation and the input of the product into the shopping basket. Further, the mobile terminal 60 stores the captured images (at least the captured images in which the object has changed) until at least the flowcharts of FIGS. 5 to 7 are completed.

[0051] Note that when a customer comes to the store and starts shopping (registering products), the customer operates the shopping start button BT10 (Fig. 11(A)). The mobile terminal 60 sends a shopping start request including the store ID and the customer ID to the cloud server 20 based on the operation of the shopping start button BT10. The cloud server 20 that has received the shopping start request from the mobile terminal 60 generates transaction information for the transaction (assigns a transaction ID), and sends the transaction ID to the mobile terminal 60 together with the screen information of the initial registration screen (Fig. 11(B)). That is, the mobile terminal 60 acquires the transaction ID of the self-transaction when the initial registration screen is displayed. Note that the customer ID is stored, for example, in the storage unit of the mobile terminal 60 as information input by the mobile terminal 60 in a registration form (input form) when, for example, downloading an app.

[0052] (Flowchart of Fig. 5) Step S100: The mobile terminal 60 determines whether there has been a barcode reading operation. For example, when the mobile terminal 60 recognizes a barcode in the captured image (through image), it determines that there has been a barcode reading operation. Note that in addition to recognizing a barcode, the mobile terminal 60 may determine that there has been a barcode reading operation when it recognizes an object resembling a barcode (a striped object). Note that one or more images are stored as comparison images in the storage unit of the mobile terminal 60 (or in another device that the mobile terminal 60 can refer to, such as the storage unit of the cloud server 20) as images of objects resembling barcodes. The mobile terminal 60 may determine that it has recognized an object resembling a barcode when it recognizes an image similar to any of the comparison images in the captured image. If there has been a barcode reading operation (Step S100: YES), the process proceeds to Step S101. If there has been no barcode reading operation (Step S100: NO), the process proceeds to Step S104.

[0053] Step S101: The mobile terminal 60 determines whether the barcode reading was successful. That is, the mobile terminal 60 determines whether it has obtained the product ID from the barcode. If the reading is successful (Step S101: YES), it proceeds to Step S110. If the reading is not successful (Step S101: NO), it proceeds to Step S102.

[0054] Step S102: The mobile terminal 60 determines whether there has been an input of a product into the shopping basket. For example, the mobile terminal 60 may determine that there has been an input of a product into the shopping basket if there is a change in the captured image (when a new object is recognized). If there has been an input of a product (Step S102: YES), it proceeds to Step S120. If there has been no input of a product (Step S102: NO), it proceeds to Step S103.

[0055] Step S103: The mobile terminal 60 determines whether a predetermined time has elapsed since the reading operation (the determination in Step S100(YES)). If the predetermined time has elapsed (Step S103: YES), it proceeds to Step S120. If the predetermined time has not elapsed (Step S103: NO), it returns to Step S101.

[0056] Step S104: Similar to Step S102, the mobile terminal 60 determines whether there has been an input of a product into the shopping basket. If there has been an input of a product (Step S104: YES), it proceeds to Step S120. If there has been no input of a product (Step S104: NO), this flowchart ends.

[0057] Step S110: Following Step S101(YES), the mobile terminal 60 executes a reading success process (described later). Then this flowchart ends.

[0058] Step S120: Following Step S102(YES), Step S103(YES), and Step S104(YES), the mobile terminal 60 executes a reading failure process (described later). Then this flowchart ends.

[0059] (Flowchart of FIG. 6) The flowchart of FIG. 6 is an example of the successful reading process (S110) of FIG. 5. Step S112: The mobile terminal 60 acquires (extracts) a captured image. For example, the mobile terminal 60 acquires (extracts) a captured image corresponding to the current successful reading (the current captured image, the captured image 2 seconds ago, the captured image 4 seconds ago,... including at least the captured images before and after the product is inserted) from among the captured images captured by the imaging unit. Subsequently, it proceeds to step S113.

[0060] Step S113: The mobile terminal 60 transmits the successful reading information to the cloud server 20. The successful reading information includes the transaction ID of the transaction (the transaction ID acquired at the start of the transaction), the product ID read in step S101, and the plurality of captured images acquired in step S112. Subsequently, it proceeds to step S114.

[0061] Step S114: The mobile terminal 60 receives the screen information transmitted from the cloud server 20. Subsequently, it proceeds to step S115. Step S115: The mobile terminal 60 updates the registration screen based on the screen information. Then this flowchart ends.

[0062] (Flowchart of FIG. 7) The flowchart of FIG. 7 is an example of the unsuccessful reading process (S120) of FIG. 5. Step S121: The mobile terminal 60 determines the classification of the unregistered secured product. For example, the mobile terminal 60 may determine the sub-classification of the unregistered secured product as follows.

[0063] When transitioning from step S102 (YES) in FIG. 5 to the unsuccessful reading process (step S120), the sub-classification of the unregistered secured product is determined to be "22 (Pseudo-scan (short time))". That is, the mobile terminal 60 determines that the reason for the unsuccessful reading is due to the short reading operation time, and classifies it as a pseudo-scan (short time).

[0064] When transitioning from step S103 (YES) in FIG. 5 to the reading failure process (step S120), and when a part of the barcode is hidden in the captured image (when a finger or the like is overlapping), the unregistered secured product sub-classification is determined as "21 (Pseudo-scan (covering, etc.))". That is, the mobile terminal 60 determines that the reason for the failure to read despite the reading operation not being a short-time reading operation is due to a part of the barcode not being visible, and classifies it as a pseudo-scan (covering, etc.).

[0065] When transitioning from step S103 (YES) in FIG. 5 to the reading failure process (step S120), and when a part of the barcode is not hidden in the captured image (when a finger or the like is not overlapping), the unregistered secured product sub-classification is determined as "23 (Barcode defect, etc.)". That is, the mobile terminal 60 determines that the reason for the failure to read despite the reading operation not being a short-time reading operation is due to wrinkles, scratches, dirt, etc. on the barcode or reflection of the barcode, etc., and classifies it as a barcode defect, etc.

[0066] When transitioning from step S104 (YES) in FIG. 5 to the reading failure process (step S120), the unregistered secured product sub-classification is determined as "24 (Non-scan input)". That is, the mobile terminal 60 classifies it as a non-scan input because no reading operation was performed and the input of the product was detected.

[0067] Step S122: The mobile terminal 60 acquires (extracts) the captured image. For example, the mobile terminal 60 acquires the captured image corresponding to the current reading failure (the current captured image, the captured image 2 seconds ago, the captured image 4 seconds ago,... including at least the captured images before and after the input of the product) from the captured images captured by the imaging unit. Subsequently, it proceeds to step S123.

[0068] Step S123: The mobile terminal 60 transmits the reading failure information to the cloud server 20. The reading failure information includes the transaction ID of the transaction (the transaction ID obtained at the start of the transaction), the unregistered secured product subcategory determined in step S121, and the plurality of captured images obtained in step S122. Subsequently, the process proceeds to step S124.

[0069] Step S124: The mobile terminal 60 receives the screen information transmitted from the cloud server 20. Subsequently, the process proceeds to step S125. Step S125: The mobile terminal 60 updates the registration screen based on the screen information. Then this flowchart ends.

[0070] FIG. 8 is a flowchart showing an example of the operation of the cloud server 20. Specifically, FIG. 8 shows the operation of the cloud server 20 at the registration stage of the transaction (i.e., the operation with the mobile terminal 60).

[0071] (Flowchart of FIG. 8) Step S200: The cloud server 20 determines whether it has received the reading success information transmitted by the mobile terminal 60 in step S113 of FIG. 6. If it has received the reading success information (step S200: YES), the process proceeds to step S210. If it has not received the reading success information (step S200: NO), the process proceeds to step S230.

[0072] Step S210: The cloud server 20 determines whether the product can be identified. That is, the cloud server 20 determines whether the product ID included in the reading success information is stored in the product master (FIG. 3(B)). If the product can be identified (step S210: YES), the process proceeds to step S211. If the product cannot be identified (step S210: NO), the process proceeds to step S221.

[0073] Step S211: The cloud server 20 identifies the transaction information. That is, the cloud server 20 identifies the transaction information of the transaction ID included in the reading success information. Subsequently, the process proceeds to step S212. Step S212: The cloud server 20 updates the transaction information identified in step S211. For example, the cloud server 20 adds the registered products to the transaction information. That is, the cloud server 20 stores the products whose product IDs are read by the mobile terminal 60 in step S101 of FIG. 5 as registered products in the transaction information. In addition, the cloud server 20 updates the total (total points, total amount). Subsequently, it proceeds to step S213.

[0074] Step S213: The cloud server 20 transmits the updated (registered product added, total updated) screen information to the mobile terminal 60. Note that the mobile terminal 60 receives the screen information in step S114 of FIG. 6. Then this flowchart ends.

[0075] Step S221: The cloud server 20 identifies the transaction information in the same manner as in step S211. Subsequently, it proceeds to step S222. Step S222: The cloud server 20 updates the transaction information identified in step S221. For example, the cloud server 20 adds the unregistered secured products (unregistered secured sub-category "11") to the transaction information. That is, the cloud server 20 stores the products whose product IDs are read by the mobile terminal 60 in step S101 of FIG. 5 as unregistered secured products (NON-FILE) in the transaction information. Subsequently, it proceeds to step S223.

[0076] Step S223: The cloud server 20 transmits the updated (unregistered secured products (unregistered secured sub-category "11" added) screen information to the mobile terminal 60. Note that the mobile terminal 60 receives the screen information in step S114 of FIG. 6. Then this flowchart ends.

[0077] Step S230: The cloud server 20 determines whether it has received the reading failure information transmitted by the mobile terminal 60 in step S123 of FIG. 7. If it has received the reading failure information (step S230: YES), it proceeds to step S231. If it has not received the reading failure information (step S230: NO), this flowchart ends.

[0078] Step S231: The cloud server 20 identifies the transaction information. That is, the cloud server 20 identifies the transaction information of the transaction ID included in the reading failure information. Subsequently, it proceeds to step S232. Step S232: The cloud server 20 updates the transaction information identified in step S231. For example, the cloud server 20 adds an unregistered secured product (any one of the unregistered secured subcategories "21" to "24" included in the reading failure information) to the transaction information. That is, the cloud server 20 stores, as an unregistered secured subcategory (any one of the pseudo scans (such as covering), pseudo scans (short time), barcode defects, etc., non-scan input indicated by the reading failure information), the products for which the mobile terminal 60 did not read the product ID in step S101 of FIG. 5, in the transaction information. Subsequently, it proceeds to step S233.

[0079] Step S233: The cloud server 20 transmits the screen information after the update (addition of an unregistered secured product (any one of the unregistered secured subcategories "21" to "24")) to the mobile terminal 60. Note that the mobile terminal 60 receives the screen information in step S124 of FIG. 7. And this flowchart ends.

[0080] FIG. 9 is a flowchart showing an example of the operation of the settlement device 40. Note that when the customer finishes shopping (registration of products) and operates the button BT20 (FIG. 12(C)) to proceed to accounting, the mobile terminal 60 displays a settlement code (two-dimensional code in FIG. 12(D)) based on the operation of the button BT20 to proceed to accounting. The settlement code is information obtained by two-dimensionally coding information (for example, the transaction ID of the transaction) that can identify the transaction information of the transaction.

[0081] (Flowchart of FIG. 9) Step S300: The settlement device 40 reads the settlement code displayed on the mobile terminal 60. For example, when the customer holds the settlement code displayed on the mobile terminal 60 in front of the scanner unit of the settlement device 40, the settlement device 40 reads the settlement code displayed on the mobile terminal 60. Subsequently, it proceeds to step S301.

[0082] Step S301: The settlement device 40 transmits transaction information acquisition request information for requesting the acquisition of the transaction information of the transaction to the cloud server 20. The transaction information acquisition request information includes the transaction ID acquired from the settlement code read in step S300 and the device ID of the settlement device 40. Subsequently, the process proceeds to step S302.

[0083] Step S302: The settlement device 40 receives the screen information transmitted from the cloud server 20. Subsequently, the process proceeds to step S303. Step S303: The settlement device 40 displays a product list screen based on the screen information. If there are unregistered reserved products, the process proceeds to step S304. If there are no unregistered reserved products, the process proceeds to step S305.

[0084] Step S304: The settlement device 40 registers the unregistered reserved products based on the operation of the store clerk. Subsequently, the process proceeds to step S305. Step S305: The settlement device 40 performs settlement based on the operation of the customer. Subsequently, the process proceeds to step S306.

[0085] Step S306: The settlement device 40 transmits settlement completion information. If there were no unregistered reserved products (if the unregistered reserved products were not registered in step S304), the settlement completion information includes the transaction ID and the settlement information from step S305 (the device ID of the settlement device 40, the payment type). If there were unregistered reserved products (if the unregistered reserved products were registered in step S304), the settlement completion information includes the transaction ID, the registration information of the unregistered reserved products in step S304, and the settlement information from step S305 (the device ID of the settlement device 40, the payment type). Subsequently, the process proceeds to step S307.

[0086] Step S306: The settlement device 40 prints and issues a receipt. And this flowchart ends.

[0087] FIG. 10 is a flowchart showing an example of the operation of the cloud server 20. Specifically, FIG. 10 shows the operation of the cloud server 20 in the settlement stage of a transaction (i.e., the operation with the settlement device 40).

[0088] (Flowchart of FIG. 10) Step S240: The cloud server 20 receives the transaction information acquisition request information transmitted by the settlement device 40 in step S301 of FIG. 9. Subsequently, it proceeds to step S241. Step S241: The cloud server 20 identifies the transaction information. That is, the cloud server 20 identifies the transaction information of the transaction ID included in the transaction information acquisition request information. Subsequently, it proceeds to step S242. Step S242: The cloud server 20 transmits the screen information of the product list screen based on the transaction information identified in step S241 to the settlement device 40. The settlement device 40 receives the screen information in step S302 of FIG. 9.

[0089] Step S243: The cloud server 20 receives the settlement completion information transmitted by the settlement device 40 in step S306 of FIG. 9. Subsequently, it proceeds to step S250. Step S250: The cloud server 20 determines whether there is registration information of the registered secured product. That is, the cloud server 20 determines whether it has received the settlement completion information including the registration information of the registered secured product in step S243 (whether the settlement completion information received in step S243 includes the registration information of the registered secured product). If there is registration information of the registered secured product (step S250: NO), it proceeds to step S261. If there is no registration information of the registered secured product (step S250: NO), it proceeds to step S251.

[0090] Step S251: The cloud server 20 identifies the transaction information. That is, the cloud server 20 identifies the transaction information of the transaction ID included in the settlement completion information. Subsequently, it proceeds to step S252.

[0091] Step S252: The cloud server 20 updates the transaction information identified in step S251. For example, the cloud server 20 stores the transaction completion date and time, and settlement information (device ID of the settlement device 40, settlement type) in the transaction information. Then this flowchart ends.

[0092] Step S261: Similar to step S251, the cloud server 20 identifies transaction information. Subsequently, it proceeds to step S262.

[0093] Step S262: The cloud server 20 updates the transaction information identified in step S261. For example, the cloud server 20 stores the transaction completion date and time, settlement information (device ID of the settlement device 40, settlement type), and registration information of unregistered secured goods in the transaction information. Then this flowchart ends.

[0094] (Sequence between the mobile terminal 60 and the cloud server 20 / in the case of normal registration) (1) The mobile terminal 60 transmits the reading success information to the cloud server 20 (step S113 in FIG. 6). (2) The cloud server 20 receives the reading success information (step S200 in FIG. 8). (3) The cloud server 20 identifies the transaction information (step S211 in FIG. 8) and adds the registered product to the identified transaction information (step S212 in FIG. 8). (4) The cloud server 20 transmits the screen information of the registration screen with the added registered product to the mobile terminal 60 (step S213 in FIG. 8). (5) The mobile terminal 60 receives the screen information (step S114 in FIG. 6) and displays the registration screen with the added registered product (step S115 in FIG. 6).

[0095] (Sequence between the mobile terminal 60 and the cloud server 20 / in the case of NON - FILE) (1) The mobile terminal 60 transmits the reading success information to the cloud server 20 (step S113 in FIG. 6). (2) The cloud server 20 receives the reading success information (step S200 in FIG. 8). (3) The cloud server 20 identifies transaction information (step S221 in FIG. 8) and adds unregistered secured products of NON-FILE to the identified transaction information (step S222 in FIG. 8). (4) The cloud server 20 transmits the screen information of the registration screen with unregistered secured products of NON-FILE added to the mobile terminal 60 (step S223 in FIG. 8). (5) The mobile terminal 60 receives the screen information (step S114 in FIG. 6) and displays the registration screen with unregistered secured products of NON-FILE added (step S115 in FIG. 6).

[0096] (In the case of the sequence / read failure between the mobile terminal 60 and the cloud server 20) (1) The mobile terminal 60 transmits read failure information to the cloud server 20 (step S123 in FIG. 7). (2) The cloud server 20 receives the read failure information (step S230 in FIG. 8). (3) The cloud server 20 identifies transaction information (step S231 in FIG. 8) and adds unregistered secured products with a read failure (any one of pseudo-scan (coating, etc.), pseudo-scan (short time), barcode defect, etc., non-scan input) to the identified transaction information (step S232 in FIG. 8). (4) The cloud server 20 transmits the screen information of the registration screen with unregistered secured products with a read failure added to the mobile terminal 60 (step S233 in FIG. 8). (5) The mobile terminal 60 receives the screen information (step S124 in FIG. 7) and displays the registration screen with unregistered secured products with a read failure added (step S125 in FIG. 7).

[0097] (Sequence between the settlement device 40 and the cloud server 20) (1) The settlement device 40 reads the settlement code (step S300 in FIG. 9). (2) The settlement device 40 transmits transaction information acquisition request information to the cloud server 20 (step S301 in FIG. 9). (3) The cloud server 20 receives the transaction information acquisition request information (step S240 in FIG. 10). (4) The cloud server 20 identifies the transaction information (step S241 in FIG. 10) and transmits the screen information of the product list screen to the settlement device 40 (step S242 in FIG. 10).

[0098] (5) The settlement device 40 receives the screen information (step S302 in FIG. 9) and displays the product list screen (step S303 in FIG. 9). (6) If there are unregistered reserved products, the settlement device 40 registers the unregistered reserved products (step S304 in FIG. 9). (7) The settlement device 40 performs settlement (step S305 in FIG. 9). (8) The settlement device 40 transmits the settlement completion information to the cloud server 20 (step S306 in FIG. 9). When there are no unregistered reserved products (when the unregistered reserved products are not registered), the settlement device 40 transmits the settlement completion information including the transaction ID and the settlement information (the device ID of the settlement device 40, the settlement type) to the cloud server 20. When there are unregistered reserved products (when the unregistered reserved products are registered), the settlement device 40 transmits the settlement completion information including the transaction ID, the settlement information, and the registration information of the unregistered reserved products to the cloud server 20. (9) The settlement device 40 prints and issues a receipt (step S307 in FIG. 9).

[0099] (10) The cloud server 20 receives the settlement completion information (step S243 in FIG. 10). (11) When the cloud server 20 has received the settlement completion information that does not include the registration information of the registered reserved products, it identifies the transaction information (step S251 in FIG. 10) and stores the transaction end date and time and the settlement information in the identified transaction information (step S252 in FIG. 10). On the other hand, when the cloud server 20 has received the settlement completion information that includes the registration information of the registered reserved products, it identifies the transaction information (step S261 in FIG. 10) and stores the transaction end date and time, the settlement information, and the registration information of the unregistered reserved products in the identified transaction information (step S262 in FIG. 10).

[0100] Figures 11 and 12 are display examples of the mobile terminal 60. Figure 11(A) is a menu screen. After the application is launched, the mobile terminal 60 displays a menu screen as shown in Figure 11(A). For example, a two-dimensional code encoding access information including the store ID of the store is prepared near the entrance of the store (by pasting a medium printed with the two-dimensional code, displaying the two-dimensional code, etc.). When a customer who has come to the store reads the two-dimensional code with the mobile terminal 60, the mobile terminal 60 launches the application and sends a transaction start request including the store ID and the customer ID to the cloud server 20. The cloud server 20 that has received the transaction start request from the mobile terminal 60 sends the screen information of the menu screen to the mobile terminal 60. The mobile terminal 60 receives the above screen information and displays a menu screen as shown in Figure 11(A). Also, when a customer who has come to the store operates the mobile terminal 60 to launch the application, the mobile terminal 60 displays a screen for instructing the reading of the two-dimensional code. When the two-dimensional code is read, a transaction start request including the store ID and the customer ID is sent to the cloud server 20 as described above, and a menu screen as shown in Figure 11(A) may be displayed.

[0101] Figure 11(B) is an initial registration screen. When the customer operates the shopping start button BT10 on the menu screen, the mobile terminal 60 displays an initial registration screen as shown in Figure 11(B). For example, based on the operation of the shopping start button BT10, the mobile terminal 60 sends a shopping start request including the store ID and the customer ID to the cloud server 20. The cloud server 20 that has received the shopping start request from the mobile terminal 60 generates transaction information for the transaction (assigns a transaction ID) and sends the transaction ID to the mobile terminal 60 together with the screen information of the initial registration screen (Figure 11(B)). The mobile terminal 60 receives the above screen information and displays an initial registration screen as shown in Figure 11(B). Note that there is a button BT20 to proceed to checkout on the initial registration screen, but the operation of the button BT20 to proceed to checkout is effective only when there is one or more items, so the operation is invalid on the initial registration screen (shown by a dashed line in the figure).

[0102] Figure 11(C) shows the initial registration screen when the reading operation (barcode scan) of 〇〇 bread is being performed. Figure 11(D) shows the registration screen when 〇〇 bread has been registered. That is, when the mobile terminal 60 successfully reads 〇〇 bread (step S101(YES) in FIG. 5), it sends the read success information to the cloud server 20 (step S113 in FIG. 6), receives the updated screen information from the cloud server 20 (step S114 in FIG. 6), and displays the registration screen as shown in FIG. 11(D) (step S115 in FIG. 6).

[0103] Figure 12(A) shows the registration screen when the reading operation of 〇〇 coffee is being performed. Figure 12(B) shows the registration screen when the reading of 〇〇 coffee fails (simulated scan (covering, etc.)). That is, when the mobile terminal 60 fails to read 〇〇 coffee and determines that the failure is due to a part of the barcode being invisible (step S121 in FIG. 7), it sends the read failure information to the cloud server 20 (step S123 in FIG. 7), receives the updated screen information from the cloud server 20 (step S124 in FIG. 7), and displays the registration screen as shown in FIG. 12(B) (step S125 in FIG. 7).

[0104] Figure 12(C) shows the registration screen after that, when the reading operation of 〇〇 potato is performed, 〇〇 potato is registered, and then the reading operation of 〇〇 chocolate is performed, and the reading of 〇〇 chocolate fails (simulated scan (short time)). The registration screen in FIG. 12(C) displays information about the first item of 〇〇 bread, the second item of unregistered secured product with a failed reading (actually 〇〇 coffee), the third item of 〇〇 potato, and the fourth item of unregistered secured product with a failed reading (actually 〇〇 chocolate).

[0105] Figure 12(D) is the settlement code display screen. For example, when the customer operates the button BT20 to proceed to the accounting on the registration screen in FIG. 12(C), the mobile terminal 60 displays the settlement code display screen as shown in FIG. 12(D). The settlement code is displayed on the settlement code display screen.

[0106] (Preset product) The mobile terminal 60 may display product buttons for registering each product without, for example, a barcode or the like, and register the product based on the operation of the product buttons. For example, a number for identifying each product is associated with each product button, and the mobile terminal 60 may send the number corresponding to the operated product button to the cloud server 20. The registration by the product button is referred to as preset registration, the product registered by the product button (the product by preset registration) is referred to as a preset product, and the number associated with each product button (the number for identifying each preset product) may be referred to as a preset number.

[0107] Note that when the preset registration is not performed, the mobile terminal 60 determines it as a non-scanned input when detecting the input of a product without a reading operation. However, when the preset registration is performed, the mobile terminal 60 may determine it as a non-scanned input when detecting the input of a product without a reading operation or an operation of the product button.

[0108] FIGs. 13 to 16 are display examples of the settlement device 40. FIG. 13 is a product list screen. For example, when the settlement device 40 reads the settlement code in FIG. 12(D), it displays a product list screen as shown in FIG. 13 (step S301 in FIG. 9). In the detail information area AR40, similar to the registration screen in FIG. 12(C), information regarding each product (〇〇 bread, unregistered secured product with reading failure (actually 〇〇 coffee), 〇〇 potato, unregistered secured product with reading failure (actually 〇〇 chocolate)) is displayed.

[0109] In the detailed information area AR40, for each unregistered secured item, a registration button BT41 for registering each unregistered secured item is displayed. The registration button BT41 becomes operable when the store clerk is the operator (for example, when the store clerk logs in to the cash register 40 such as by having the cash register 40 read the store clerk code). When the registration button BT41 of one unregistered secured item is operated, the cash register 40 displays an unregistered secured item registration screen for registering the unregistered secured item (step S304 in FIG. 9).

[0110] The customer checks the content on the product list screen and, if there are no problems, operates the accounting button BT42. When the accounting button BT42 is operated, the cash register 40 displays a payment type selection screen (not shown) for accepting the selection of a payment type (cash payment, credit card payment, etc.). Since there are unregistered secured items, on the product list screen in FIG. 13, the operation of the accounting button BT42 is invalid.

[0111] FIG. 14 shows an unregistered secured item registration screen displayed as a small screen (pop-up screen) SG50. For example, when the store clerk logs in on the product list screen in FIG. 13 and the store clerk operates the registration button BT41 of an unregistered secured item with a reading NG between ○○ bread and ○○ potatoes (actually ○○ coffee), the cash register 40 displays the small screen SG50 in front of the product list screen as shown in FIG. 14. Note that the cash register 40 may be able to read barcodes while the small screen SG50 is being displayed.

[0112] The small screen SG50 is provided with a product information area AR51 and an image area AR54. Also, on the small screen SG50, a registration execution button BT55 and a do not purchase button BT56 are displayed.

[0113] The product information area AR51 is an area for displaying information (product name, price, etc.) of the unregistered secured item to be registered. That is, when registering the unregistered secured item, the registration details (product name, price, etc.) of the unregistered secured item are determined, and the product information area AR51 is an area for displaying the determined details for confirmation.

[0114] In the product information area AR51, the PLU button BT52 and the preset button BT53 are displayed. When the PLU button BT52 is operated (similarly when the preset button BT53 is operated), the settlement device 40 displays a virtual keyboard with numeric buttons, execution buttons, etc. arranged thereon. Note that when the PLU button BT52 is operated, the settlement device 40 may display product buttons for preset registration instead of the virtual keyboard.

[0115] Also, in the product information area AR51, a plus button and a minus button are displayed, and it is also possible to accept changes in the quantity (number) (since the initial value of the quantity is 1, no operation is required when registering one item of a certain product). Note that the minus button becomes effective when the quantity is 2 or more.

[0116] The image area AR54 is an area for displaying a captured image corresponding to the unregistered secured product. The captured image G11 is a captured image before the unregistered secured product is inserted. The captured image G13 is a captured image after the unregistered secured product is inserted. The thick frame FL of the captured image G13 indicates an area including the difference (the object of XX coffee) between the captured image G11 and the captured image G13. The store clerk can confirm which product the unregistered secured product is by the image area AR54 (the captured images G11, G13).

[0117] The registration execution button BT55 is a button to be operated when registering the unregistered secured product. The "do not purchase" button BT56 is a button to be operated when not purchasing the unregistered secured product. That is, it is a button to be operated when the product has become an unregistered secured product (basically in the customer's hand), but there is no intention to purchase and the purchase is to be cancelled. The "do not purchase" button BT56 may be referred to as the cancellation button BT56. Note that the registration execution button BT55 becomes effective when the registration content is specified (when the product name, etc. is displayed in the product information area AR51).

[0118] (Registration of Unregistered Reserved Items by PLU Input) The store clerk operates the PLU button BT52 in the product information area AR51. The cash register 40 displays a virtual keyboard based on the operation of the PLU button BT52. The store clerk operates the virtual keyboard to input the product ID. When there is an input of the product ID, the cash register 40 displays the input product ID (displayed in the display column on the right side of the PLU button BT52), and refers to the product master stored in the device itself (or makes an inquiry to other devices such as the store controller 10 or the cloud server 20), identifies the product name and price of the product with the said product ID, and displays the identified product name and price in the product information area AR51.

[0119] In addition, when the product ID is NON - FILE (when the product name and price of the product with the said product ID cannot be identified), the cash register 40 may display an error message indicating that it is NON - FILE. Also, when it is NON - FILE, the store clerk may input the product name and price using the virtual keyboard, and the cash register 40 may display the product name and price input by the store clerk in the product information area AR51. Note that the registration type (described later) of the input of the product name and price by the virtual keyboard is PLU input (it may be classified separately as other registration types).

[0120] The store clerk checks the product name and price in the product information area AR51 and operates the registration execution button BT55.

[0121] (Registration of Unregistered Reserved Items by Preset Input) The store clerk may register the unregistered reserved item by operating the preset button BT53. Specifically, the store clerk operates the preset button BT53 in the product information area AR51. The settlement device 40 displays a virtual keyboard based on the operation of the preset button BT53. The store clerk operates the virtual keyboard to input a preset number. When a preset number is input, the settlement device 40 displays the input preset number (in the display column on the right side of the preset button BT53), refers to the product master stored in its own device, etc., identifies the product name and price of the product with the preset number, and displays the identified product name and price in the product information area AR51.

[0122] As described above, the settlement device 40 may display product buttons based on the operation of the preset button BT53. In this case, the store clerk operates the product buttons. When there is an operation of the product button, the settlement device 40 displays the product name and price of the product corresponding to the product button (the product with the preset number corresponding to the product button) in the product information area AR51.

[0123] The store clerk checks the product name and price in the product information area AR51 and operates the registration execution button BT55.

[0124] (Registration of Unregistered Reserved Items by Scanning Barcodes) The store clerk may register the unregistered reserved item by reading the product ID (barcode) of the product (the unregistered reserved item) with the scanner unit. When the product ID is successfully read, the settlement device 40 displays the product ID (in the display column on the right side of the PLU button BT52), refers to the product master stored in its own device, etc., identifies the product name and price of the product with the product ID, and displays the identified product name and price in the product information area AR51.

[0125] In addition, when the product ID is NON-FILE, the settlement device 40 may display an error message indicating that it is NON-FILE. Also, when it is NON-FILE, the store clerk may input the product name and price using the virtual keyboard, and the settlement device 40 may display the product name and price input by the store clerk in the product information area AR51.

[0126] The store clerk checks the product name and price in the product information area AR51 and operates the registration execution button BT55.

[0127] (Cancellation of Purchase of Unregistered Reserved Product) When the store clerk confirms that the customer will not purchase the product, the store clerk operates the "Do not purchase" button BT56 (cancellation button BT56). The settlement device 40 stores that the purchase of the product has been cancelled based on the operation of the "Do not purchase" button BT56.

[0128] FIG. 15 is a product list screen after registering an unregistered reserved product (actually XX coffee) with a reading NG in the small screen SG50 of FIG. 14. For example, in the small screen SG50 of FIG. 14, when the store clerk operates the registration execution button BT55 while the settlement device 40 is displaying the product name "XX coffee" and the price "160 yen" in the product information area AR51, the small screen SG50 is erased and a product list screen as shown in FIG. 15 is displayed.

[0129] FIG. 16 is a product list screen after registering another unregistered reserved product (actually XX chocolate) with a reading NG. Since there are no unregistered reserved products left, the operation of the accounting button BT42 is enabled on the product list screen of FIG. 16. Hereinafter, the customer will operate.

[0130] (Subsequent Flow) The customer checks the content on the product list screen in Fig. 16, and if there are no problems, operates the accounting button BT42. When the accounting button BT42 is operated, the settlement device 40 displays a settlement type selection screen (not shown). The customer selects a desired settlement type on the settlement type selection screen. The settlement device 40 displays a settlement screen (not shown, which may be a plurality of settlement screens that transition according to the customer's operations (actions)), and settles according to the customer's operations (actions) corresponding to the selected settlement type (step S305 in Fig. 9).

[0131] After settlement, the settlement device 40 transmits settlement completion information to the cloud server 20 (step S306 in Fig. 9). For example, when settling in cash from the product list screen in Fig. 16, the settlement device 40 transmits settlement completion information including the transaction ID, settlement information (the device ID of the settlement device 40, settlement type "cash"), registration information of the first unregistered reserved product, and registration information of the second unregistered reserved product to the cloud server 20.

[0132] The first unregistered reserved product includes the staff code of the staff who registered the first unregistered reserved product, the registration type (information indicating the difference between PLU input / preset input / scan / purchase cancellation) for registering the first unregistered reserved product, product ID "49XXX…", product name "〇〇 Coffee", and price "￥160". The second unregistered reserved product includes the staff code of the staff who registered the second unregistered reserved product, the registration type for registering the second unregistered reserved product, product ID "45XXX…", product name "〇〇 Chocolate", and price "￥240".

[0133] Note that the cloud server 20 that has received the settlement completion information reflects the settlement completion information in the transaction information of the transaction (step S262 in Fig. 10).

[0134] Finally, the settlement device 40 prints and issues a receipt (step S307 in Fig. 9).

[0135] FIG. 17 is an explanatory diagram for explaining registered products and unregistered secured products in transaction information. In the mobile terminal 60, on the registration screen of FIG. 12(C) (〇〇 bread, unregistered secured product with reading failure (actually 〇〇 coffee), 〇〇 potato, unregistered secured product with reading failure (actually 〇〇 chocolate)), the button BT20 for proceeding to settlement is operated. After the operation of the button BT20 for proceeding to settlement, the settlement code displayed is read by the settlement device 40. In the settlement device 40, on the product list screen of FIG. 16 (product list screen after registering two unregistered secured products with reading failure), the settlement button BT42 is operated. After the settlement is completed, the settlement completion information is transmitted to the cloud server 20. In the cloud server 20, it is assumed that the settlement completion information is reflected in the transaction information of the transaction.

[0136] FIG. 17(A) schematically shows the information stored as registered product 1 in the transaction information at the time of product registration. That is, when the mobile terminal 60 successfully reads the product ID "491XX…" from the barcode of 〇〇 bread, it transmits the reading success information including the transaction ID "XXX", the product ID "491XX…", and a plurality of captured images (image 1, image 2, …) to the cloud server 20 (step S113 in FIG. 6). The cloud server 20 receives the above reading success information and stores, as registered product 1 in the transaction information of the transaction ID "XXX", the product ID "491XX…" in the reading success information, the product name "〇〇 bread" of the product with the product ID "491XX…", and the price "￥220" of the product with the product ID "491XX…" as shown in FIG. 17(A) (step S212 in FIG. 8).

[0137] Figure 17(B) schematically shows the information stored as the registered product 2 in the transaction information at the time of product registration. That is, when the mobile terminal 60 successfully reads the product ID "492XX..." from the barcode of XX Potatoes, it transmits the read success information including the transaction ID "XXX", the product ID "492XX...", and a plurality of captured images (Image 1, Image 2,...) to the cloud server 20 (step S113 in FIG. 6). The cloud server 20 receives the above read success information and stores, as the registered product 2 in the transaction information of the transaction ID "XXX", the product ID "492XX..." in the read success information, the product name "XX Potatoes" of the product with the product ID "492XX...", and the price "￥220" of the product with the product ID "492XX..." (step S212 in FIG. 8).

[0138] As shown in FIGS. 17(A) and 17(B), the captured images in the read success information are not stored as registered products. That is, since the captured images in the read success information are used when the product ID is not stored in the product master (when it is NON-FILE) (for confirming the products that become NON-FILE in the settlement device 40), when the product ID in the read success information is stored in the product master (when it is not NON-FILE) as shown in FIGS. 17(A) and 17(B), the captured images in the read success information are not stored as registered products. Note that even when the product ID is stored in the product master (when it is not NON-FILE), the captured images in the read success information may be stored as registered products.

[0139] The left side of the arrow in Fig. 17(C) schematically shows the information stored as unregistered reserved product 1 in the transaction information at the time of product registration. That is, when the mobile terminal 60 fails to read the product ID due to barcode covering or the like, it transmits the reading failure information including the transaction ID "XXX", the unregistered reserved product subcategory "21 (covering, etc.)", and a plurality of captured images (Image 1, Image 2, …) to the cloud server 20 (step S123 in Fig. 7). The cloud server 20 receives the above reading failure information and stores, as unregistered reserved product 1 in the transaction information of the transaction ID "XXX", the occurrence date and time (current date and time), the unregistered reserved product subcategory "21" in the reading failure information, and the captured images (Image 1, Image 2, …) as shown on the left side of the arrow in Fig. 17(C) (step S232 in Fig. 8).

[0140] The left side of the arrow in Fig. 17(D) schematically shows the information stored as unregistered reserved product 2 in the transaction information at the time of product registration. That is, when the mobile terminal 60 fails to read the product ID because of a short time, it transmits the reading failure information including the transaction ID "XXX", the unregistered reserved product subcategory "22 (short time)", and a plurality of captured images (Image 1, Image 2, …) to the cloud server 20 (step S123 in Fig. 7). The cloud server 20 receives the above reading failure information and stores, as unregistered reserved product 2 in the transaction information of the transaction ID "XXX", the occurrence date and time (current date and time), the unregistered reserved product subcategory "22" in the reading failure information, and the captured images (Image 1, Image 2, …) as shown on the left side of the arrow in Fig. 17(D) (step S232 in Fig. 8).

[0141] The right side of the arrow in Fig. 17(C) schematically shows the information of the unregistered secured item 1 updated after settlement. The right side of the arrow in Fig. 17(D) schematically shows the information of the unregistered secured item 2 updated after settlement. That is, after settlement, the settlement device 40 transmits to the cloud server 20 the settlement completion information including the transaction ID, the settlement information (device ID of the settlement device 40, payment type "cash"), the registration information of the first unregistered secured item (clerk code "XXX", registration type (e.g., PLU input), product ID "49XXX…", product name "〇〇 coffee", price "￥160"), and the registration information of the second unregistered secured item (clerk code "XXX", registration type (e.g., PLU input), product ID "45XXX…", product name "〇〇 chocolate", price "￥240") (step S306 in Fig. 9).

[0142] The cloud server 20 receives the above settlement completion information, and for the unregistered secured item 1 in the transaction information of the transaction ID "XXX", as shown on the right side of the arrow in Fig. 17(C), stores the product ID "49XXX…" in the settlement completion information, the product name "〇〇 coffee" in the settlement completion information, the price "￥160" in the settlement completion information, the clerk code "XXX" in the settlement completion information, and the registration type "PLU input" in the settlement completion information. For the unregistered secured item 2 in the transaction information of the transaction ID "XXX", as shown on the right side of the arrow in Fig. 17(D), stores the product ID "45XXX…" in the settlement completion information, the product name "〇〇 chocolate" in the settlement completion information, the price "￥240" in the settlement completion information, the clerk code "XXX" in the settlement completion information, and the registration type "PLU input" in the settlement completion information (step S262 in Fig. 10).

[0143] Fig. 17(E) schematically shows the information stored as an unregistered secured item in another scenario (NON-FILE scenario).

[0144] The left side of the arrow in FIG. 17(E) schematically shows the information stored as the unregistered reserved product M in the transaction information at the time of product registration. For example, when the mobile terminal 60 successfully reads the product ID "493XX..." from the barcode of XX ramen, it transmits the read success information including the transaction ID "XXX", the product ID "493XX...", and a plurality of captured images (Image 1, Image 2,...) to the cloud server 20 (step S113 in FIG. 6). Although the cloud server 20 has received the above read success information, if "493XX..." is not stored in the product master (when it is NON-FILE), as shown in FIG. 17(E), as the registered product M in the transaction information of the transaction ID "XXX", as shown in FIG. 17(E), the issue date and time (current date and time), the unregistered reserved product sub-category "11" in the read failure information, and the captured images (Image 1, Image 2,...) are stored (step S222 in FIG. 8).

[0145] The right side of the arrow in FIG. 17(E) schematically shows the information of the unregistered reserved product M updated after settlement. For example, after settlement, the settlement device 40 transmits the settlement completion information including the transaction ID, the settlement information (the device ID of the settlement device 40, the settlement type "cash"), and the registration information of the above unregistered reserved product (the non-FILE unregistered reserved product of "493XX...") (store clerk code "XXX", registration type (PLU input), product name "XX ramen", price "￥268") to the cloud server 20 (step S306 in FIG. 9).

[0146] The cloud server 20 receives the above settlement completion information, and for the unregistered reserved product M in the transaction information of the transaction ID "XXX", as shown on the right side of the arrow in FIG. 17(E), the product name "XX ramen" in the settlement completion information, the price "￥258" in the settlement completion information, the store clerk code "XXX" in the settlement completion information, and the registration type "PLU input" in the settlement completion information are stored (step S262 in FIG. 10).

[0147] That is, after the transaction (settlement) is completed, registered products such as those in Fig. 17(A) and Fig. 17(B), and unregistered secured products (actually registered unregistered secured products) such as the right side of the arrow in Fig. 17(C), the right side of the arrow in Fig. 17(D), and the right side of the arrow in Fig. 17(E) will be stored in the transaction information.

[0148] In the examples of Figs. 17(C) to 17(E), since unregistered secured products are registered by PLU input, "PLU input" is stored as the registration type. However, if unregistered secured products are registered by preset input, "preset input" will be stored as the registration type, and if unregistered secured products are registered by barcode scanning, "scan" will be stored as the registration type. Also, when the purchase of an unregistered secured product is canceled, "purchase cancellation" is stored as the registration type.

[0149] When canceling the purchase of a registered secured product, the clerk code of the clerk who executed the cancellation process (the clerk who operated the non-purchase button BT56) is stored, but the transaction ID, product name, and price are not stored, similar to the case on the right side of the arrow.

[0150] Note that the cancellation process may be executed after identifying the product (it may be possible to operate the non-purchase button BT56 instead of the registration execution button BT55 after PLU input, preset input, or barcode scanning). When the cancellation process is executed after identifying the product, in addition to the clerk code, the identified transaction ID, the corresponding product name, and the corresponding price are stored, and "purchase cancellation" is stored as the registration type. In this way, products that were not purchased after becoming unregistered secured products can also be included in the scope of aggregation and analysis. Therefore, not only can the number of targets be increased, but more advanced analysis (such as analysis distinguishing the final purchase or not) can also be performed as needed.

[0151] Figs. 18 and 19 are display examples of the aggregation and analysis device 80. The aggregation and analysis device 80 displays various screens related to the sales system 1.

[0152] (Basket Missing List Screen) For example, the aggregation analysis device 80 displays a missing item list screen related to missing items (securing unregistered products). For example, as shown in FIG. 18, the aggregation analysis device 80 displays a management screen that displays various information according to the selection in the menu area AR80 as an initial screen. When "missing items" is selected in the menu area AR80, a missing item list screen is displayed as one of the management screens.

[0153] The missing item list screen in FIG. 18 is provided with a condition setting area AR81, a result display area AR82, and a list display area AR86. Also, on the missing item list screen in FIG. 18, a product list button BT83, a transaction list button BT84, a sorting specification button BT85, a print button BT88, and a data output button BT89 are displayed.

[0154] The condition setting area AR81 is an area for setting conditions. In the list display area AR86, it is possible to set time (a time range for narrowing down the information to be listed) as a condition. For example, when the date and time button is operated, the aggregation analysis device 80 displays a small screen for setting the start date and time and the end date and time, and the store clerk sets the start date and time and the end date and time on the small screen. Note that the initial value in the initial state (immediately after the selection of "missing items" in the menu area AR80) may be, for example, no specification (the entire period without narrowing down), or the previous month for one month.

[0155] Also, in the condition setting area AR81, it is possible to set items (major classification of securing unregistered items, minor classification of securing unregistered items, day of the week, time zone, store clerk, customer, etc.) as conditions. For example, the store clerk sets a desired item from the pull-down button. Note that the initial value in the initial state may be, for example, no specification (no narrowing down).

[0156] It is also possible to set conditions (compound conditions) that combine two or more items, such as "Sunday and morning and unregistered secured major category '1'" or "customer '〇〇' and unregistered secured major category '2'". The compound conditions may be prepared in advance as options using a pull-down button, or may be set on a small screen that can be freely set instead of the pull-down button.

[0157] The result display area AR82 is an area for displaying the aggregated results of missing items. The list display area AR86 is an area for displaying the list information of missing items. When the execution button in the condition setting area AR81 is operated, the aggregation analyzer 80 displays the aggregation results in the result display area AR82 and the list information in the list display area AR86.

[0158] The product list button BT83, the transaction list button BT84, and the sort specification button BT85 are buttons for controlling the display of the list display area AR86. The product list button BT83 is a button for displaying list information in units of products as the display of the list display area AR86. The transaction list button BT84 is a button for displaying list information in units of transactions as the display of the list display area AR86. The sort specification button BT85 is a button for selecting the display order (new order / old order) of the list display area AR86. The product list button BT83 and the transaction list button BT84 are buttons whose ON state (specified state) / OFF state (non-specified information) is switched based on an operation. When one is in the ON state, the other is in the OFF state. The initial value in the initial state may be that the product list button BT83 is in the ON state (the transaction list button BT84 is in the OFF state) and the specification by the sort specification button BT85 is "new order".

[0159] Incidentally, it has been described that when the execution button in the condition setting area AR81 is operated, the aggregation analysis device 80 displays the aggregation result in the result display area AR82 and displays the list information in the list display area AR86. However, when "falling out of the basket" in the menu area AR80 is selected, the aggregation result may be displayed in the result display area AR82 and the list information may be displayed in the list display area AR86. That is, when "falling out of the basket" in the menu area AR80 is selected, the aggregation analysis device 80 may display the aggregation result in the result display area AR82 and display the list information in the list display area AR86 as if the execution button has been operated with the initial values (for example, no conditions for time and items are specified, the product list button BT83 is in the ON state, in the order of new).

[0160] As shown in FIG. 18, the following eight aggregation values are displayed in the result display area AR82. (1) Number of occurrence of reading NG: The number of cases where reading NG (unregistered secured product major classification "2") has occurred. When reading NG occurs multiple times in the same drawer, each is counted. (2) Number of products with reading NG: The number (type) of products that have become reading NG. Even if the same product has become reading NG multiple times, it is counted as 1. (3) Number of transactions with occurrence of reading NG: The number of transactions in which reading NG has occurred one or more times. Even if reading NG occurs multiple times in the same drawer, it is counted as 1. (4) Number of customers with occurrence of reading NG: The number of customers in which reading NG has occurred one or more times. Even if reading NG occurs multiple times for the same customer, it is counted as 1. (5) Number of occurrence of NON-FILE: The number of cases where NON-FILE (unregistered secured product major classification "1") has occurred. When NON-FILE occurs multiple times in the same drawer, each is counted. (6) Number of products with NON-FILE: The number (type) of products that have become NON-FILE. Even if the same product has become NON-FILE multiple times, it is counted as 1. (7) Number of transactions with NON-FILE occurrences: This is the number of transactions in which NON-FILE has occurred one or more times. Even if NON-FILE has occurred multiple times within the same transaction, it is counted as one. (8) Number of customers with NON-FILE occurrences: This is the number of customers in which NON-FILE has occurred one or more times. Even if NON-FILE has occurred multiple times for the same customer, it is counted as one.

[0161] In the example shown in FIG. 18, list information for items that have fallen out of the basket is displayed in the list display area AR86. The display items (data items) for each piece of information are date and time (the date and time when the unregistered reservation for the item occurred), day of the week, major category (unregistered reservation major category), minor category (unregistered reservation minor category), product ID (the product ID obtained at the time of registration if the unregistered reservation product is NON-FILE, and the product ID obtained by the clerk's operation at the time of settlement if the unregistered reservation product is a reading NG), transaction ID (the transaction ID of the transaction including the unregistered reservation product), customer ID (the customer ID of the customer of the transaction including the unregistered reservation product), device ID of the settlement device, and clerk ID (the clerk ID of the clerk who registered the unregistered reservation product at the time of settlement).

[0162] The print button BT88 is a button for printing the contents of the screen. When the print button BT88 is operated, the aggregation analysis device 80 prints one or both of the aggregation result (the display contents of the result display area AR82) and the list information (the display contents of the list display area AR86 (contents of all pages including subsequent pages)) together with the conditions (the display contents of the condition setting area AR81) (sends print data to the printing device).

[0163] The data output button BT89 is a button for outputting the contents of the screen. When the data output button BT89 is operated, the aggregation analysis device 80 outputs the list information (the display contents of the list display area AR86 (contents of all pages including subsequent pages)) in a predetermined format (e.g., CSV format) to a specified location (on the desktop screen, USB memory, etc.).

[0164] In the missing basket list screen of FIG. 18, the results (number of occurrences, etc.) are displayed on the upper side, and the list of transaction information is displayed on the lower side. In this way, the results (number of occurrences, etc.) and the list of transaction information are arranged vertically. However, they may be arranged vertically in the reverse order, that is, the list of transaction information is displayed on the upper side and the results (number of occurrences, etc.) are displayed on the lower side. Further, the results (number of occurrences, etc.) and the list of transaction information may be arranged horizontally.

[0165] (Missing Basket Details Screen) The aggregation analysis device 80 displays a missing basket details screen for each individual missing basket (unregistered item secured). For example, when one piece of information (row) is selected (touched) on the missing basket list screen, the aggregation analysis device 80 displays the missing basket details screen. Specifically, when the information at the top (arrow A) of the list display in the list display area AR of the missing basket list screen in FIG. 18 is selected, the aggregation analysis device 80 displays a missing basket details screen as shown in FIG. 19.

[0166] The missing basket details screen in FIG. 19 is provided with an image area AR90 and an individual information area AR100. On the missing basket details screen in FIG. 19, a back button BT117, a print button BT118, and a data output button BT119 are displayed.

[0167] The image area AR90 is an area for displaying a captured image corresponding to the unregistered item secured. The captured image G11 is a captured image before the unregistered item secured is inserted. The captured image G12 is a captured image when the unregistered item secured is being inserted. The captured image G13 is a captured image after the unregistered item secured is inserted. The captured image G12L is an enlarged image of the captured image G12. Note that the image to be enlarged among the captured images G11 to G13 can be selected by touch.

[0168] The individual information area AR100 is provided with a customer area AR101, a mobile terminal / app area AR102, a leakage area AR103, a settlement response area AR104, and a product area AR105. Also, a reference button BT110 is displayed in the individual information area AR100.

[0169] In the upper part of the individual information area AR100 (the part not belonging to the customer area AR101, the mobile terminal / app area AR102, the leakage area AR103, the settlement response area AR104, and the product area AR105), the transaction ID of the transaction including the unregistered secured product and the shopping time of the transaction (transaction start date and time, transaction end date and time) are displayed.

[0170] When the reference button BT110 is operated, the aggregation analysis device 80 displays information related to the transaction. For example, when the reference button BT110 is operated, the aggregation analysis device 80 displays a small screen in front of the leakage details screen and lists other products registered in the transaction on the small screen.

[0171] In the customer area AR101, the registered name, customer ID, and attributes of the customer (the customer of the transaction including the unregistered secured product) are displayed. The attributes can be obtained from the customer master (gender, date of birth). A detail button BT111 is displayed in the customer area AR101. When the detail button BT111 is operated, the aggregation analysis device 80 displays information related to the customer. For example, when the detail button BT111 is operated, the aggregation analysis device 80 displays a small screen in front of the leakage details screen and displays the customer's last visit date, total number of transactions, rank, point information, etc. on the small screen. The last visit date, etc. are obtained from the customer performance information.

[0172] In the mobile terminal / app area AR102, information about the mobile terminal 60 and the app used in the transaction is displayed. Note that information about the mobile terminal 60 and the app is obtained from the customer master. Additionally, information about the mobile terminal 60 and the app may be included in the individual transaction information, and information about the mobile terminal 60 and the app may be obtained from the transaction information. A reference button BT112 is displayed in the mobile terminal / app area AR102. When the reference button BT112 is operated, the aggregation analysis device 80 displays information about the mobile terminal 60 and the app. For example, when the reference button BT112 is operated, the aggregation analysis device 80 may display a small screen in front of the missing basket details screen, and display information about the occurrence of securing unregistered products using the mobile terminal 60 (including the same OS version) (e.g., for the most recent 30 items) and information about the occurrence of securing unregistered products using the app (including the same version) (e.g., for the most recent 30 items) on the small screen.

[0173] In the missing basket area AR103, information related to the missing basket is displayed. A reference button BT113 is displayed in the missing basket area AR103. When the reference button BT113 is operated, the aggregation analysis device 80 displays information related to the missing basket. For example, when the reference button BT113 is operated, the aggregation analysis device 80 may display a small screen in front of the missing basket details screen, and display other information related to the missing basket of the transaction on the small screen, or display unregistered secured products of the same unregistered secured subcategory (e.g., the most recent 10 products).

[0174] In the settlement response area AR104, information related to the response at the time of settlement of the unregistered secured product is displayed. A reference button BT114 is displayed in the settlement response area AR104. When the reference button BT114 is operated, the aggregation analysis device 80 displays information related to the response at the time of settlement of the unregistered secured product. For example, when the reference button BT114 is operated, the aggregation analysis device 80 may display a small screen in front of the missing basket details screen, and display other response information of the same store clerk (e.g., for the most recent 10 items) on the small screen.

[0175] In the product area AR105, information about the unregistered secured product is displayed. Note that "XX Chocolate" in the product area AR105 is a different type of chocolate from "XX Chocolate" in FIGS. 16 and 17(D). A detail button BT115 is displayed in the product area AR105. When the detail button BT115 is operated, the aggregation analysis device 80 displays information about the unregistered secured product. For example, when the detail button BT115 is operated, the aggregation analysis device 80 may display a small screen on the front of the missing basket detail screen and display the shelf position of the product on the small screen, or may display the occurrence information of the unregistered securing of the product (for example, for the most recent 10 items).

[0176] The back button BT117 is a button for returning from the missing basket detail screen to the missing basket list screen. When the print button BT188 is operated, the aggregation analysis device 80 displays the missing basket list screen instead of the missing basket detail screen.

[0177] The print button BT188 is a button for printing the content of the screen. When the print button BT188 is operated, the aggregation analysis device 80 prints (sends print data to a printing device) the information displayed in the individual information area AR100 (including the information displayed in the customer area AR101, the mobile terminal / app area AR102, the missing basket area AR103, the settlement-time response area AR104, and the product area AR105).

[0178] The data output button BT189 is a button for outputting the content of the screen. When the data output button BT189 is operated, the aggregation analysis device 80 converts the information displayed in the individual information area AR100 into a PDF and outputs it to a specified location (on the desktop screen, USB memory, etc.).

[0179] (Other various screens displayed by the aggregation analysis device 80) The screens displayed by the aggregation analysis device 80 are not limited to the missing basket list screen (Fig. 18) and the missing basket details screen (Fig. 19). The aggregation analysis device 80 displays various other screens.

[0180] The aggregation analysis device 80 may aggregate the missing baskets by store and display them on the screen. For example, the aggregation analysis device 80 may aggregate the number of reading NG occurrences per month (the number of reading NG occurrences in January is XX, the number of reading NG occurrences in February is XX, …) for a specified period (e.g., the past one year) by store and display them in a graph (e.g., bar graph, line graph). Also, for example, the aggregation analysis device 80 may aggregate the reading NG occurrence frequency (the number of unregistered and secured items with reading NG out of the total number of purchased items) for a specified period by store (the reading NG occurrence frequency of store A is XX%, the reading NG occurrence frequency of store B is XX%, …) and display it in a graph (e.g., bar graph). The occurrence frequency may also be referred to as the occurrence rate.

[0181] Related to the above, the aggregation analysis device 80 may display the occurrence rates of missing baskets (unregistered and secured items) for each store side by side (displayed as numerical values or various graphs, sorted and displayed in descending or ascending order of the occurrence rate) so that the occurrence rates of missing baskets for each store can be compared (e.g., the occurrence rate for a period specified from the screen).

[0182] Instead of or in addition to the above, the aggregation analysis device 80 may aggregate the missing baskets by time (yearly, monthly, day of the week, time zone) and display them on the screen. For example, the aggregation analysis device 80 may aggregate the number of reading NG occurrences by day of the week (the number of reading NG occurrences on Sunday is XX, the number of reading NG occurrences on Monday is XX, …) for a specified period and display them in a graph (e.g., bar graph, pie graph). Also, for example, the aggregation analysis device 80 may aggregate the reading NG occurrence frequency by time zone (e.g., the reading NG occurrence frequency from 10:00 to 12:00 is XX%, the reading NG occurrence frequency from 12:00 to 16:00 is XX%, …) for a specified period and display it in a graph (e.g., bar graph).

[0183] Instead of or in addition to the above, the aggregation analysis device 80 may aggregate the basket misses by customer characteristics and display them on the screen. For example, the aggregation analysis device 80 may aggregate the occurrence frequency of reading NG by customer attribute and rank for a specified period (the occurrence frequency of customers in the M1 layer S rank is XX%, the occurrence ratio of the M1 layer A rank is XX%, …, the occurrence frequency of customers in the F3 layer B rank is XX%), and display it in a graph (e.g., bar graph, pie graph). Also, for example, the aggregation analysis device 80 may aggregate the occurrence frequency of reading NG by the total number of customer transactions for a specified period (the occurrence frequency of less than 10 times is XX%, the occurrence ratio of 10 - 20 times is XX%, the occurrence frequency of 21 times or more is XX%), and display it in a graph (e.g., bar graph, pie graph).

[0184] Instead of or in addition to the above, the aggregation analysis device 80 may aggregate the basket misses by classification of unregistered reservation (major classification of unregistered reservation, minor classification of unregistered reservation) and display them on the screen. For example, the aggregation analysis device 80 may aggregate the occurrence ratio of reading NG by minor classification of unregistered reservation for a specified period (the number of unregistered reservation products in each minor classification of unregistered reservation with respect to the total number of all unregistered reservation products) (the minor classification of unregistered reservation "11" is XX%, the minor classification of unregistered reservation "21" is XX%, …), and display it in a graph (e.g., pie graph).

[0185] Instead of or in addition to the above, the aggregation analysis device 80 may aggregate the basket misses by display position (shelf position) of unregistered reservation products and display them on the screen.

[0186] Instead of or in addition to the above, the aggregation analysis device 80 may aggregate the basket misses by model of the mobile terminal 60 or by version of the OS of the mobile terminal 60 and display them on the screen.

[0187] Instead of or in addition to the above, the aggregation analysis device 80 may aggregate the basket misses by version of the app and display them on the screen.

[0188] The mobile terminal 60 may be a lending terminal lent by the store. The aggregation analysis device 80 may, instead of or in addition to the above, aggregate and screen-display the basket escapes according to the type of the mobile terminal 60 (customer-owned item / lending terminal). The mobile terminal 60 as a lending terminal may acquire the customer ID after lending and erase the customer ID after return. The method for acquiring the customer ID is not particularly limited. For example, the mobile terminal 60 as a lending terminal may accept the input of the customer ID on the menu screen (FIG. 11(A)), or may accept the input of the customer ID after the operation of the shopping start button BT10 on the menu screen (before displaying the initial registration screen (FIG. 11(B))).

[0189] (Change of classification) The classification for ensuring unregistered items (major classification for ensuring unregistered items, minor classification for ensuring unregistered items) may be changeable. For example, a classification change button may be arranged on the basket escape details screen (FIG. 19). When a store clerk operates the classification change button, the aggregation analysis device 80 may display a small screen in front of the basket escape details screen and accept the change of classification on the small screen. For example, the store clerk may compare the classification shown in the basket escape area AR103 (classification by the mobile terminal 60) with the image shown in the image area AR90 (captured images G11 to G13). If the store clerk determines that the classification shown in the basket escape area AR103 is inappropriate, the classification may be changed. When the aggregation analysis device 80 accepts the change of classification, it transmits the classification change information to the cloud server 20, and the cloud server 20 updates the transaction information (minor classification for ensuring the unregistered item). That is, the change of classification is reflected in the transaction information. Note that the change date and time, the classification before the change, the classification after the change, the store clerk ID of the store clerk who made the change, etc. may also be left in the transaction information.

[0190] By changing the classification to an appropriate one, the accuracy of subsequent aggregation and analysis can be improved.

[0191] As described above, the sales system 1 according to the embodiment has been explained. According to the sales system 1, products can be registered appropriately. That is, based on the results of aggregation and analysis by the aggregation analysis device 80, various countermeasures for ensuring unregistered products can be considered, and appropriate (effective) countermeasures can be taken. As a result, the situation of unregistered products gradually decreases, and products can be registered appropriately.

[0192] For example, by identifying the time period with a high rate of product omission, measures can be considered based on the tendency according to the time period, such as increasing the number of store staff during that time period and broadcasting a message in the store indicating that additional staff are on duty to deter customers' fraudulent behavior. This can lead to a reduction in product omission during that time period. As the sales system 1, the time period with a high rate of product omission may be spontaneously presented (alert output) to the store side. For example, the cloud server 20 may transmit information indicating the time period with a high rate of product omission to the terminals used by the store staff in the store. Also, the cloud server 20 may transmit information indicating the time period with a high rate of product omission in the store together with the store ID to the device at the headquarters.

[0193] When a tendency of reading failure is observed for a specific product, the display environment (brightness, arrangement, layout, etc.) of the product may be a problem. Therefore, these aspects can be considered, and improvements in lighting (changing or adding lighting fixtures), review of display methods and layout can be carried out to lead to a reduction in reading failure. Similar to the time period with a high rate of product omission, as the sales system 1, the store side may be spontaneously presented with the possibility of problems in the display environment of a specific product.

[0194] If the product with a reading failure is an in-store marked product (a product with an in-store code), since the barcode (in-store code) printed on the label may be the problem, it may be advisable to review the barcode system and size. When a label printer that issues in-store marking labels is connected to the system, a correction instruction can be sent to the label printer, and the printing conditions of the label, such as the barcode system, printing size, printing position, and printing color, can be directly changed based on the analysis results. This can lead to a reduction in the reading failure of in-store marked products. Similar to the other cases described above, as the sales system 1, it may also be advisable to spontaneously notify the store side about the possibility of a problem with the in-store code of a specific product.

[0195] If a tendency of pretending to read (especially "not scanned and put in") is observed for the barcode of a specific product, then by changing the display position of the product to an area with high popularity (crowded) or an area where a store employee is always present, etc., the tendency of pretending to read can be suppressed. Similar to the other cases described above, as the sales system 1, it may also be advisable to spontaneously notify the store side about the tendency of pretending to read for the barcode of a specific product.

[0196] If an analysis result is obtained indicating that the tendency of items falling out of the basket is related to various conditions (model, OS, version) of the customer's mobile terminal 60 used, then similar to the other cases described above, as the sales system 1, it may also be advisable to spontaneously notify the store side about the possibility of a problem with various conditions related to the mobile terminal 60. Also, guidance information (illustrations, videos showing habits of product reading and methods to avoid failures) can be sent from the cloud server 20 to the corresponding mobile terminal 60. If it depends on the version, a notification may be given to prompt an update. That is, it may be directly directed at the customer.

[0197] When the analysis result shows that the tendency of skipping the basket is related to customer attributes such as gender and age, similar to the other cases described above, as the sales system 1, it may spontaneously present that a tendency of pretending to read the barcode of a specific product is observed. Also, guidance information may be sent to the mobile terminal 60 of the corresponding customer attribute. That is, it may directly appeal to the customer.

[0198] When a tendency of having many NON-FILEs is observed, since there may be a registration mistake by the registration clerk in charge of the product, a notification or work instruction to improve the registration work may be sent from the cloud server 20 to the code registration terminal. Also, the cloud server 20 may notify the display work terminal to prompt the display work clerk to perform a pre-display scan check.

[0199] The various advanced analyses (specifically, analyses leading to solutions) as described above are impossible to achieve only by collecting information at the time of basket skipping. In the sales system 1, in addition to the information at the time of basket skipping, the result of the response to the basket-skipped product by the clerk at the settlement device 40 after the basket skipping occurs is stored in combination with the information at the time of basket skipping, so the various advanced analyses as described above are possible.

[0200] (Modification examples, etc.) As described above, each embodiment has been explained. However, the configuration of the device, the configuration of the data, the flow of the process, the mode of display and output, etc. can be appropriately changed as shown in the following (1) to (10) for example. Also, the following (1) to (10) may be appropriately combined with each other.

[0201] (1) In the above-described embodiment, the mobile terminal 60 (customer-owned / lent terminal) was described as a smartphone, but it suffices that the customer can register the product himself / herself in the sales floor (product display area). For example, the mobile terminal 60 may be a tablet terminal (customer-owned / lent terminal). Further, in the above-described embodiment, the mobile terminal 60 was described as being attached to the cart 70 (holder unit 72), but the mobile terminal 60 may be integrally configured with the cart 70. That is, the mobile terminal 60 (smartphone, tablet terminal), which is a lent terminal, may be a part of the cart 70.

[0202] (2) In the above-described embodiment, the mobile terminal 60 was described as transmitting information (reading success information, reading failure information) to the cloud server 20 for each product (each time the barcode reading operation is performed), but the mobile terminal 60 may transmit a plurality of information to the cloud server 20 collectively when the product registration is completed (when the operation of the accounting progress button BT20 is performed). That is, the mobile terminal 60 may store the product master in the storage unit and proceed with the process without communicating with the cloud server 20 until the product registration is completed, and transmit a plurality of information to the cloud server 20 collectively when the registration is completed. In other words, the cloud server 20 only needs to have the information of all products (registered products, unregistered secured products) reflected in the transaction information of the mobile terminal 60 when the transaction information of a certain mobile terminal 60 is requested from the settlement device.

[0203] (3) In the above-described embodiment, the product registered by the mobile terminal 60 was described as being settled by the settlement device 40, but the product registered by the mobile terminal 60 may be settled by the registration settlement device 30. For example, the settlement code may be read by the scanner unit of the registration settlement device 30 to settle the product registered by the mobile terminal 60. Similarly, the settlement may be performed by the registration settlement device 32. Further, by providing a scanner unit operated by the customer, the settlement may also be performed by the registration settlement device 31 or the settlement device 35. That is, the store clerk may register the unregistered secured product in a device other than the settlement device 40 (registration settlement device 30, registration settlement device 31, registration settlement device 32, settlement device 35).

[0204] (4) In the above-described embodiment, it has been described that the transaction status management device 50 is installed in the accounting area and the aggregation analysis device 80 is installed in the office or the backyard. However, the installation location of the aggregation analysis device 80 does not have to be the office or the backyard. For example, the aggregation analysis device 80 may be installed in the accounting area, or may be installed outside (for example, at the head office) that can communicate with the sales system 1. Further, the aggregation analysis device 80 may be a portable device (such as a notebook computer, a tablet terminal, a smartphone, etc.).

[0205] The transaction status management device 50 may also have the function of the aggregation analysis device 80. A device that executes registration processing or settlement processing based on the operation of a store clerk (for example, the registration and settlement device 31, the registration and settlement device 32, the registration and settlement device 33, the registration device 34) may also have the function of the aggregation analysis device 80.

[0206] (5) In the above-described embodiment, it has been described that the aggregation analysis device 80 aggregates and analyzes the unregistered confirmation of products in the portable terminal 60. However, the device to be aggregated and analyzed is not limited to the portable terminal 60. For example, the aggregation analysis device 80 may aggregate and analyze the unregistered confirmation of products in the registration and settlement device 30, the registration and settlement device 31, the registration and settlement device 32, the registration and settlement device 33, the registration device 34.

[0207] In addition, in the case of ensuring the unregistration of products in a device where a store clerk registers products (for example, the registration and settlement device 31, the registration and settlement device 32 (normal mode), the registration and settlement device 33, the registration device 34), it is not necessary (or may be assumed) to assume the "21 (pseudo scan (covering, etc.))", "22 (pseudo scan (short time))", and "24 (non-scan input)" of the unregistered confirmation sub-classification.

[0208] (6) In the above-described embodiment, an example has been described in which the unregistered confirmation of products is classified into "NON-FILE", "pseudo scan (covering, etc.)", "pseudo scan (short time)", "barcode defect, etc.", and "non-scan input" (Fig. 4). However, it may be classified more finely (in the remarks column of Fig. 4), or may be classified from other perspectives.

[0209] (7) In the above embodiment, when there is a change in the captured image (when a new object is recognized), that is, when it is determined that a product has been inserted through image processing (image recognition), it has been described. However, the method for determining whether a product has been inserted is not limited to this. For example, a vibration sensor (vibration detection unit) may be provided in the cart 70 (near the shopping basket placement unit 71), and when a predetermined vibration (such as a vibration pattern) is detected, it may be determined that a product has been inserted. Also, for example, a scale (measurement unit) may be provided in the cart 70 (shopping basket placement unit 71), and when the measured value (weight of the shopping basket + product) increases, it may be determined that a product has been inserted.

[0210] (8) In the above embodiment, an example has been described in which the aggregation analysis device 80 displays the results of aggregation and analysis on the display unit. However, the aggregation analysis device 80 may output the results of aggregation and analysis to other devices instead of or in addition to displaying them on the display unit, or may print the aggregation and analysis on paper.

[0211] (9) In the above embodiment, it has been described that the "transaction information" includes the unregistered secured products 1 to N (unspecified information), and the "unspecified information" includes the "judgment result of the reason for not being registered (unregistered secured sub - classification)" and the "information such as the product ID and price specified later (information at the time of specification)" (FIG. 3(E), FIG. 17). However, it is only necessary that the "unspecified information" and the "information at the time of specification" are associated with each other, and the "information at the time of specification" does not have to be included in the "unspecified information". For example, according to the right side of the arrow in FIG. 17(C), the unregistered secured product 1 includes the following (a) to (h): (a) Generation time: YYMMDDHHMM (b) Unregistered secured sub - classification: 21 (coating, etc.) (c) Captured image: Image 1, Image 2,... (d) Product ID: 49XXX... (e) Product name: 〇〇 coffee (f) Price: ￥160 (g) Clerk ID: XXX (h) Registration type: PLU input Although it has been described as if all of (a) to (h) above are "unspecified information" and (d) to (h) are "information at the time of specification", it is sufficient that the "unspecified information" and the "information at the time of specification" are associated with each other, and (a) to (c) above may be referred to as "unspecified information" and (d) to (h) as "information at the time of specification".

[0212] That is, the cloud server 20 may generate unspecified information ((a) to (c)) including the determination result (b) and the information at the time of specification (d) to (h), and store it in the storage unit as part of the transaction information. Alternatively, the cloud server 20 may generate information associating the unspecified information ((a) to (c)) including the determination result (b) and the information at the time of specification (d) to (h) as part of the transaction information, and store it in the storage unit.

[0213] Further, the cloud server 20 may generate and store unspecified information as information associated with the transaction information without including the unspecified information in the transaction information.

[0214] (10) Some or all of each function (input / output, storage, processing (including determination)) in each device (for example, the store controller 10, the cloud server 20, the registration settlement device 30, the registration settlement device 31, the registration settlement device 32, the registration settlement device 33, the registration device 34, the settlement device 35, the settlement device 40, the transaction status management device 50, the mobile terminal 60, the aggregation analysis device 80, etc.) may be realized in another device different from the device described as the execution entity of the function.

[0215] For example, the cloud server 20 may execute a program for controlling the operation of the aggregation analysis device 80, and the aggregation analysis device 80 may display a screen (for example, the basket leakage list screen in FIG. 18 and the basket leakage details screen in FIG. 19) by means of a browsing function. In this case, the aggregation analysis device 80, which is a client, requests (demands) the cloud server 20 to aggregate and analyze transactions based on the operations of the store clerk. The cloud server 20 aggregates and analyzes the transactions based on the request from the aggregation analysis device 80, and transmits a basket leakage list screen showing the results of the aggregation and analysis to the aggregation analysis device 80. Note that the aggregation analysis device 80 may control the display of the screen itself on its own device, but may request the cloud server 20 for the aggregation and analysis of transactions.

[0216] Further, the mobile terminal 60 may display a screen (for example, various screens shown in FIGS. 11 and 12) provided by the cloud server 20 by means of a browsing function instead of an app. Other devices such as the settlement device 40 and the transaction status management device 50 may also display a screen provided by the cloud server 20 by means of a browsing function.

[0217] Further, instead of the mobile terminal 60, the cloud server 20 may determine the classification of unregistered reserved goods. That is, in the above embodiment, the reason (such as unregistered reserved sub-classification) why the goods purchased by the mobile terminal 60 could not be identified is being judged (step S122 in FIG. 7), but the cloud server 20 may judge the reason why the goods purchased by it could not be identified.

[0218] <Summary of the Embodiment> [Technical Field] The present invention relates to a system and a server. [Background Art] A product data processing device that displays a warning when an unregistered product is put into a basket is known (see, for example, Patent Document 1). [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Patent Application Laid-Open No. 2019-086944 [Summary of the Invention] [Problems to be Solved by the Invention] However, even if a warning is issued each time, inappropriate events during product registration, such as unregistered products being put into the basket, do not necessarily decrease. The present invention has been made in view of such circumstances, and an object thereof is to provide a technique for appropriately registering products.

[0219] [Means for Solving the Problems] (1) One aspect of the present embodiment for solving the above-described problems includes a product identification unit that identifies a product to be purchased, and when the product to be purchased is not identified by the product identification unit, generates transaction information including unspecified information regarding the product (for example, unregistered secured products 1 to unregistered secured products N), a totaling / analysis unit (for example, the CPU of the totaling / analysis device 80) that totals or analyzes the transaction information generated by the generation unit, and an output unit (for example, the display unit of the totaling / analysis device 80) that outputs the result of the totaling or analysis by the totaling / analysis unit. A system (for example, the sales system 1) characterized by comprising these components. According to the system of (1), products can be registered appropriately.

[0220] (2) A reason determination unit that determines the reason why the product to be purchased is not identified by the product identification unit (for example, the process of step S121 by the mobile terminal 60) is provided, and the generation unit generates, as the transaction information, information in which the unspecified information including the determination result by the reason determination unit is associated with the identification time information when the product not identified by the product identification unit is identified. The system according to (1), characterized by this. According to the system of (2), products can be registered appropriately.

[0221] (3) The output unit outputs a list of the transaction information generated by the generation unit and the number of occurrences of unspecified products in a certain period totaled or analyzed by the totaling / analysis unit side by side (for example, in the basket omission list screen of FIG. 18, the result (number of occurrences, etc.) is displayed on the upper side, and the list of transaction information is displayed on the lower side, and the result (number of occurrences, etc.) and the list of transaction information are displayed side by side vertically). The system according to (2), characterized by this. According to the system of (3), products can be properly registered.

[0222] A system according to any one of (1) to (3), comprising a storage unit (for example, FIG. 3(A)) that stores customer information regarding customers who purchase products, wherein the aggregation and analysis unit aggregates or analyzes the information generated by the generation unit using the customer information. According to the system of (4), products can be properly registered.

[0223] One aspect of the present embodiment that solves the above-described problems is a system (for example, sales system 1) including a product registration terminal (for example, mobile terminal 60), an aggregation and analysis device (for example, aggregation and analysis device 80), and a server (for example, cloud server 20), wherein the server includes a storage unit that stores transaction information (for example, FIG. 3(E)) including unspecified information regarding products not specified in the product registration terminal, and the aggregation and analysis device includes an aggregation and analysis unit that aggregates or analyzes the transaction information stored by the storage unit, and an output unit that outputs the result of the aggregation or analysis by the aggregation and analysis unit. According to the system of (5), products can be properly registered.

[0224] One aspect of the present embodiment that solves the above-described problems is a server in a system (for example, sales system 1) including a product registration terminal (for example, mobile terminal 60), an aggregation and analysis device (for example, aggregation and analysis device 80), and a server (for example, cloud server 20), the server including a storage unit that stores transaction information including unspecified information regarding products not specified in the product registration terminal, an aggregation and analysis unit that aggregates or analyzes the transaction information stored by the storage unit based on a request from the aggregation and analysis device, and an output unit that outputs the result of the aggregation or analysis by the aggregation and analysis unit to the aggregation and analysis device. According to the system of (6), products can be properly registered.

[0225] Note that, a program for implementing the functions of each of the devices described above (for example, the aggregation analysis device 80, the settlement device 40, the cloud server 20, the mobile terminal 60, the registered settlement device 30, the transaction status management device 50, the store controller 10, the registered settlement device 31, the registered settlement device 32, the registered settlement device 33, the registration device 34, the settlement device 35, etc.) may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to perform the processing of each of the above devices. Here, "reading the program recorded on the recording medium into the computer system and executing it" 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. Also, 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. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, magneto-optical disk, ROM, CD-ROM, etc., and 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. Also, the recording medium 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, as long as it can be downloaded from the distribution server and installed in a form executable on the terminal device, the form stored in the distribution server does not matter. 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 each of the divided programs may be different. Furthermore, the "computer-readable recording medium" is assumed to include a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network, which holds the program for a certain period of time.Further, the above program may be for realizing a part of the functions described above. Additionally, it may be a so-called differential file (differential program) that can realize the functions described above in combination with a program already recorded in the computer system.

Description of Signs

[0226] 1…Sales system 10…Store controller 20…Cloud server 30…Registration and settlement device 31…Registration and settlement device 32…Registration and settlement device 33…Registration and settlement device 34…Registration device 35…Settlement device 40…Settlement device 50…Transaction status management device 60…Mobile terminal 70…Shopping cart 80…Aggregation and analysis device

Claims

1. A product identification unit that identifies a product to be purchased; A generation unit that generates transaction information including unspecified information regarding the product when the product to be purchased is not identified by the product identification unit; An aggregation / analysis unit that aggregates or analyzes the transaction information generated by the generation unit; An output unit that outputs the result of the aggregation or analysis by the aggregation / analysis unit A system characterized by comprising the above.

2. A reason determination unit that determines the reason why the product to be purchased is not identified by the product identification unit Comprising, The generation unit, Generates information that associates, as the transaction information, the unspecified information including the determination result by the reason determination unit and the identification time information when the product not identified by the product identification unit is identified. The system according to claim 1, characterized by the above.

3. The output unit, Outputs a list of the transaction information generated by the generation unit and the number of occurrences of unspecified products during a certain period aggregated or analyzed by the aggregation / analysis unit side by side. The system according to claim 2, characterized by the above.

4. A storage unit that stores customer information regarding a customer who purchases a product Comprising, The aggregation / analysis unit, Aggregates or analyzes the information generated by the generation unit using the customer information. The system according to any one of claims 1 to 3, characterized by the above.

5. A system including a product registration terminal, an aggregation / analysis device, and a server, The server, Comprises a storage unit that stores transaction information including unspecified information regarding a product not identified at the product registration terminal Comprising, The aggregation / analysis device, An aggregation / analysis unit that aggregates or analyzes the transaction information stored by the storage unit; An output unit that outputs the result of the aggregation or analysis by the aggregation / analysis unit A system characterized by comprising the above.

6. A server in a system including a product registration terminal, an aggregation / analysis device, and a server, A storage unit that stores transaction information including unspecified information regarding a product not identified at the product registration terminal; An aggregation / analysis unit that aggregates or analyzes the transaction information stored by the storage unit based on a request from the aggregation / analysis device; An output unit that outputs the result of the aggregation or analysis by the aggregation / analysis unit to the aggregation / analysis device A server characterized by comprising the above.

Images