Product sales data processing system

Abstract

To provide a commodity sales data processing system in which a customer performs commodity registration by using a terminal, allowing proper operation according to a situation of accounting.SOLUTION: A commodity sales data processing system includes a customer terminal device that displays code information including transaction identification information identifying a transaction according to a settlement transfer instruction to the customer terminal device, and a settlement device that reads the displayed code information. The system acquires settlement information based on transaction information identified by the transaction identification information included in the code information read by the settlement device, updates accounting situation information indicating a situation for accounting including commodity registration to settlement in one transaction according to processing of the customer terminal device and the settlement device, and determines the possibility of settlement processing using the settlement information acquired based on the accounting situation information corresponding to a transaction of the transaction identification information included in the read code information.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present invention relates to a product sales data processing system. [Background technology]

[0002] 2. Description of the Related Art There is known a self-registration system that allows a customer to register products using a smartphone or the like when shopping in a store (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-219034 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the above-mentioned product sales data processing system in which a customer uses a terminal to register products, the customer basically performs operations related to the transaction from product registration to payment without the intervention of a store clerk. For this reason, the product sales data processing system is required to operate appropriately according to the transaction situation.

[0005] The present invention has been made in consideration of the above circumstances, and has an object to enable a product sales data processing system, in which customers register products using a terminal, to operate appropriately according to the status of the transaction. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a product sales data processing system in which a customer terminal device used by a customer performs product registration processing, and a settlement device performs settlement processing in response to customer operation using settlement information based on the results of the product registration processing, the product sales data processing system comprising: a code information display means for displaying code information including at least transaction identification information that identifies a transaction on the customer terminal device in response to a settlement transition instruction to the customer terminal device; a reading means in the settlement device for reading the displayed code information; a settlement information acquisition means in the settlement device for acquiring settlement information based on transaction information identified by the transaction identification information included in the code information read by the reading means; an updating means for updating accounting status information indicating the status of a transaction including from product registration to settlement in one transaction in accordance with the progress of processing of at least one of the customer terminal device and the settlement device; and a settlement feasibility determination means for determining whether or not settlement processing is possible using the settlement information acquired by the settlement information acquisition means, based on the accounting status information corresponding to the transaction indicated by the transaction identification information included in the code information read by the reading means. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a shopping system in a first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of installation of a settlement device in the first embodiment. [Diagram 3] 1 is a diagram showing an example of the appearance of a settlement device in a first embodiment. FIG. [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a settlement device in the first embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device in the first embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a transaction management device in the first embodiment. [Figure 7] 3A to 3C are diagrams illustrating an example of customer information, store information, and cart information according to the first embodiment. [Figure 8]1 is a sequence diagram showing an example of processing procedures executed by a customer terminal device, a settlement device, and a transaction management device in the first embodiment in response to a transaction. [Figure 9] 1A to 1C are diagrams showing examples of a start-up screen, a product registration initial screen, a product registration update screen, and a code display screen in the first embodiment. [Figure 10] 13A to 13C are diagrams showing an example of a display of a subtotal amount and a display notifying reserved products on the customer side display unit in the first embodiment. [Figure 11] 11 is a flowchart showing an example of a procedure executed by a customer terminal device, a settlement device, and a transaction management device in response to fraudulent conduct occurring when a customer terminal device transmits product registration information in bulk. [Figure 12] FIG. 11 is a diagram illustrating an example of a definition of a transaction situation in the second embodiment. [Figure 13] 13 is a flowchart showing an example of processing procedures executed by a customer terminal device, a settlement device, and a transaction management device in response to a customer terminal-responsive transaction in the second embodiment. [Figure 14] 13A to 13C are diagrams illustrating an example of a payment notification mode in the second embodiment. [Figure 15] A figure showing an example of a mode of settlement impossibility notification in the second embodiment. [Figure 16] A figure showing an example of a mode of settlement impossibility notification in the second embodiment. [Figure 17] A figure showing an example of a mode of settlement impossibility notification in the second embodiment. [Figure 18] A figure showing an example of a mode of settlement impossibility notification in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] First Embodiment [Example of shopping system configuration] Fig. 1 shows an example of the configuration of a shopping system (an example of a product sales data processing system) according to this embodiment. The shopping system in the figure corresponds to accounting (customer terminal-compatible accounting) in which, for example, a customer uses a customer terminal device 50 to register the product to be purchased while taking it from a product shelf, and the same customer also uses a payment device 40 to settle the payment for the registered product. The accounting here refers to a procedure carried out in response to one transaction, including the registration of the product and the settlement of the registered product. The shopping system of this embodiment includes a management device 10, a transaction management device 60, a settlement device 40, a customer terminal device 50, and a credit card settlement server 70.

[0009] The management device 10 and settlement device 40 are installed in a store and are communicatively connected via a LAN 19 (which may be wired or wireless). The management device 10 is a business terminal used by store staff for store management and the like, and is capable of communicating with the transaction management device 60. Although four settlement devices 40 are illustrated in FIG. 1, the number of settlement devices 40 in one store is not particularly limited.

[0010] The customer terminal device 50 is operated by a customer (such as a shopper who is a member of the store, hereinafter also referred to simply as a customer). In addition to typical communication and imaging functions (camera), the customer terminal device 50 has a recognition function that scans the barcode attached to a product to read the product code, that is, recognizes the barcode attached to the product. Note that the recognition function of the customer terminal device 50 needs only to be able to read the product code, and does not need to be able to recognize which product the read product code belongs to. In other words, the customer terminal device 50 needs only to be able to read the product code from the barcode when the barcode exists as an object in an image captured by the imaging function (an image acquired as a through image). Such a customer terminal device 50 may be a smartphone, a tablet terminal, or the like owned by a customer. A shopping application having a function of registering products in accordance with the shopping system of this embodiment is installed in the smartphone, tablet terminal, or the like serving as the customer terminal device 50.

[0011] The customer terminal device 50 may be one that is lent by the store instead of being owned by the customer as described above. In the case of a customer terminal device 50 that is lent by the store, it may be provided as one that is attached to a shopping cart and operated by the customer.

[0012] The customer terminal device 50 also captures an image (e.g., releases the shutter) of the product (e.g., the peripheral portion with a barcode attached) and generates a captured image (image data). The customer terminal device 50 may capture an image by releasing the shutter in response to an operation by the customer who is the operator, but in this embodiment, it is preferable that the customer terminal device 50 captures an image by releasing the shutter at its own discretion.

[0013] In addition, the customer terminal device 50 may be equipped with an image recognition technology that extracts feature points from an image (through image, captured image) and recognizes an imaged subject (object, etc.). For example, the customer terminal device 50 may use the image recognition technology to identify (estimate) an imaged product.

[0014] The settlement device 40 is a settlement device capable of at least cash payment as a settlement method. The settlement device 40 is configured to be able to communicate with the transaction management device 60. The settlement device 40 may be configured to be able to communicate with the transaction management device 60, for example, via the management device 10.

[0015] The transaction management device 60 manages transactions carried out in accordance with the shopping system of this embodiment.

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

[0017] [About the payment device] Fig. 2 is a diagram showing an example of the installation of the settlement device 40. Fig. 2(A) is a perspective view of the settlement device 40 etc. as seen from the customer side. Fig. 2(B) is a perspective view of the settlement device 40 etc. as seen from the store clerk side. As shown in Fig. 2(A), a counter is placed on the right side of the settlement device 40 as seen from the customer side.

[0018] Fig. 3 is a diagram showing an example of the appearance of the settlement device 40. Fig. 3(A) is a perspective view of the settlement device 40 as seen from the customer side. Fig. 3(B) is a perspective view of the settlement device 40 as seen from the store clerk side. Fig. 4 is a diagram showing an example of the configuration of the settlement device 40. In Fig. 3 and Fig. 4, the same parts are given the same reference numerals.

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

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

[0021] The RAM 403 is a read / write memory and stores various information, such as information read from the ROM 402 or the hard disk 404, information acquired from the outside, and information generated during processing.

[0022] The hard disk 404 stores various information. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information acquired from the outside, information generated during processing, and the like.

[0023] The customer-side display unit 405 is a touch display for customers, which displays various information to customers and accepts various inputs from customers. Customer-side scanner unit 406 is a scanner unit for customers, and for example, scans a barcode attached to a product and reads the product code. Customer-side scanner unit 406 may also scan a code (barcode, two-dimensional code, etc.) printed on a bill (registered trademark) and read information required for payment. Customer-side scanner unit 406 may also scan a code (two-dimensional code, etc.) displayed on the display unit of customer terminal device 50 and read information required for payment.

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

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

[0026] The change machine 409 (cash settlement unit) is a cash settlement mechanism, which has an input port for banknotes and coins, and an output port for banknotes and coins, calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. The change machine 409 faces the customer and is operated by the customer. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, detecting the number of coins by denomination, etc.).

[0027] That is, the change machine 409 is used when the price of registered products is settled with cash (money) in the settlement device 40. The change machine 409 has a banknote insertion port for inserting banknotes, a coin insertion port for inserting coins, a banknote discharge port for discharging banknotes, a coin discharge port for discharging coins, a counting unit for counting the inserted or discharged money, a money transport mechanism between the insertion port or discharge port and the storage unit, the above-mentioned sensor, etc. The banknote insertion port and the coin insertion port are also referred to as deposit insertion ports. The banknote discharge port and the coin discharge port are also referred to as change discharge ports. The banknote insertion port and the banknote discharge port may be a common port, and the coin insertion port and the coin discharge port may be a common port.

[0028] The change machine 409 also counts the coins replenished during the closing process and stores them in a storage unit. The change machine 409 also counts the coins to be dispensed during the closing process and discharges them from a change discharge port. The closing process is a process of adjusting the amount of money stored in the change machine 409 (cash on hand / cash on hand) to a reference amount after the store is closed or before the store is opened.

[0029] The store clerk's display unit 410 is a touch display for the store clerk, which displays various information to the store clerk and receives various inputs from the store clerk. The key operation unit 411 is made up of various keys (buttons) and receives various inputs from the store clerk. The store clerk scanner unit 412 is a scanner unit for store clerks, and for example, scans a barcode attached to a product and reads the product code. The store clerk scanner unit 412 also scans a barcode attached to the name tag of the store clerk and reads the store clerk code.

[0030] Although the store clerk's scanner unit 412 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper) is arranged on the key operation unit 411, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 410, the store clerk may operate that preset key to register the product.

[0031] The printing unit 413 prints and issues various media (receipts, bills, etc.). The printing unit 413 can freely rotate to change its orientation (direction of the media issuing port) from the clerk side to the customer side and from the customer side to the clerk side. The orientation of the printing unit 413 may be changed manually, or may be changed automatically (mechanically controlled, etc.) in response to, for example, a transition (switching) of the operation mode described below. The correctness of the orientation of the printing unit 413 may be detected by a sensor or the like.

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

[0033] In addition, the settlement device 40 of this embodiment can be switched between a total of four operating modes: a customer terminal-responsive settlement mode, which is set to perform settlement processing under customer terminal-responsive accounting, and three accounting modes (first to third accounting modes) corresponding to three different patterns of accounting (product registration, settlement). The first payment mode is an operation mode in which the store clerk performs product registration operations and operations corresponding to payment on the payment device 40. The second payment mode is an operation mode in which the store clerk performs product registration operations on the payment device 40, and the customer performs operations corresponding to payment on the same payment device 40. The third payment mode is an operation mode in which the customer performs product registration operations and operations corresponding to payment on the payment device 40. As a result, in a store that has introduced the shopping system of this embodiment, some of the multiple payment devices 40 can be set to customer terminal compatible payment mode to support customer terminal compatible payment, and the other payment devices 40 can be set to, for example, the first or second payment mode so that a store clerk can handle payments in consultation with customers. Note that the other payment devices 40 may also include those set to the third payment mode.

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

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

[0036] The memory unit 602 of the transaction management device 60 stores customer information, store information, product information, and cart information.

[0037] [Information stored in the transaction management device] The customer information stored in the memory unit 602 is information for managing individual customers. The transaction management device 60 generates customer information when a customer is registered (a customer's registration may be considered to have been completed when the customer information of that customer is stored). The transaction management device 60 also updates the customer information as appropriate based on cart information, etc. The transaction management device 60 may update the customer information, for example, by referring to the cart information at a specified time every day.

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

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

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

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

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

[0043] The product information is, for example, information acquired from the store management device 10, and is information about products sold in the store. The product information for one product includes information such as a product code (product identifier), product name, and price.

[0044] Cart information is information for managing individual transactions. The transaction management device 60 generates the cart information at the start of a transaction. In addition, the transaction management device 60 updates the cart information as the transaction progresses (each time a product is registered) (the storage of a product in the cart information may be interpreted as the registration of that product).

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

[0046] The transaction status information corresponds to the second embodiment, which will be described later, and therefore a description thereof will be omitted here.

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

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

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

[0050] The registered product information (registered product N) may include the registration date and time of the Nth product. In other words, the transaction management device 60 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a basis for determining whether or not a service such as a time service should be applied and the effect of the application.

[0051] The reserved product information (total) is information that is updated each time a reserved product (described later) is registered. The reserved product information (total) includes the number of reserved products (number of products), the number of NON-PLU (also called "NO-FILE") reserved products, the number of reserved products that cannot be read (check for unauthorized operation), etc.

[0052] NON-PLU refers to a product whose barcode or product code was successfully scanned in the store (the product code was successfully read), but whose product code is not stored in the product information (a product whose product information is not registered). In addition, the terms "NON-PLU", "NO-FILE", "NON FILE" and the like in the specification, drawings and the like of this application all refer to products for which product information has not been registered as described above.

[0053] The reading NG means that the scanning of the product code at the store has failed (the product code could not be read), or the product has failed to be scanned at the store. In other words, the reading NG means, for example, a timeout process when it is possible to determine that the barcode is not recognized even though the product is imaged for a certain period of time using image recognition technology, or a product that has been timed out. For example, the reading NG is determined to be a case where the barcode cannot be correctly acquired (recognized) due to wrinkles on the package or smudges or dirt on the barcode printing. The reading NG is also determined to be a case where an illegal operation of pretending to read the barcode and putting it in the basket is detected. The customer terminal device 50 is equipped with a sensor (for example, a gyro sensor, an acceleration sensor, a distance sensor, etc.) and can detect that the customer terminal device 50 is reading a barcode (specifically, a situation where the customer terminal device 50 is tilted to read the barcode and an item (product) is present at a certain distance ahead of the customer terminal device 50). If the barcode cannot be read within a predetermined time (if the barcode continues to be read for a predetermined time but the barcode cannot be read), a timeout process occurs and the product is marked as pending (reading failed).

[0054] Reserved Product Information (Reserved Product 1) is information on reserved product 1. Reserved Product Information (Reserved Product 2) is information on reserved product 2. Reserved Product Information (Reserved Product 3) is information on reserved product 3.

[0055] The reserved product information (reserved product N; N is an integer) includes the reserved product type (information indicating whether the reserved product is NON-PLU or cannot be read). If the reserved product type is NON-PLU, the reserved product information (reserved product N) includes the product code. If the reserved product type is cannot be read, the reserved product information (reserved product N) includes image data captured when the reading was NG. For example, if the Nth item is a reserved item due to NON-PLU, the reserved item information (reserved item N) includes the reserved item type "1 (NON-PLU)" and the item code. Also, if the Nth item is a reserved item due to NG reading, the reserved item information (reserved item N) includes the reserved item type "2 (NG reading)" and the image data.

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

[0057] [Example of processing procedure for customer terminal-based accounting] The sequence diagram in FIG. 8 shows an example of a processing procedure executed by customer terminal device 50, settlement device 40, and transaction management device 60 in response to customer terminal-responsive accounting for one transaction. Specifically, Figure 8 shows an example of the processing performed by the customer's customer terminal device 50, the settlement device 40 installed in the store, and the transaction management device 60 installed outside the store, such as in a data center, when a customer visits a store, registers products displayed in the store, and completes payment for the registered products.

[0058] Step S1: The customer terminal device 50 acquires information for identifying a store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (the two-dimensional code may be output on a display screen, a medium on which the two-dimensional code is printed may be attached, etc.), and a customer who visits the store may scan (read) the two-dimensional code with the customer terminal device 50, thereby allowing the customer terminal device 50 to acquire the store identification information. When a customer who visits the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer who visits the store scans the two-dimensional code with the customer terminal device 50, the shopping application may be started, and a screen informing the customer that the transaction management device 60 is currently connected may be displayed as a start-up screen.

[0059] Also, for example, since a store is identified by its location, a customer who visits the store may obtain location information (GPS information) at the store using the customer terminal device 50 (i.e., the store's location information may be obtained as store identification information). When a customer who visits the store starts a shopping application, location information may be obtained and a screen may be displayed as a start-up screen informing the customer that the application is currently connected to the transaction management device 60. If multiple stores are detected from the location information and one cannot be identified, a selection screen may be displayed to allow the customer to select. Alternatively, a mode may be switched to forcefully obtain a two-dimensional code.

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

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

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

[0063] As described above, the transaction management device 60 stores store information such as that shown in Figure 7(B), so when it receives store identification information (it also receives customer identification information) as a transaction start request from the customer terminal device 50, if the received store identification information is a two-dimensional code, it acquires the store identification information by referring to store identification information 1, and if the received store identification information is location information (GPS information), it acquires the store identification information by referring to store identification information 2. Note that if the store identification information received from the customer terminal device 50 is store identification information converted into a two-dimensional code, the transaction management device 60 need only acquire it as is.

[0064] In other words, when the transaction management device 60 receives customer identification information and store identification information from the customer terminal device 50 as a transaction start request, it acquires the store identification information from the store identification information received from the customer terminal device 50, and further acquires the current date, issues (assigns) a serial number, combines the store identification information with the current date and serial number, and stores the combined information as cart identification information in the cart information. Also, when the transaction management device 60 receives store identification information and customer identification information from the customer terminal device 50 as a transaction start request, it acquires the current date and time, and stores the current date and time as the transaction start date and time (generation date and time) in the cart information. Also, when the transaction management device 60 receives store identification information and customer identification information from the customer terminal device 50 as a transaction start request, it stores the customer identification information received from the customer terminal device 50 as customer identification information in the cart information.

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

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

[0067] Step S5: The customer terminal device 50 scans the barcode attached to the product by the customer's operation, and reads the product code. In the figure, it is assumed that the barcode has been successfully scanned. Steps S5 to S9 are repeatedly executed every time the barcode attached to the product is scanned.

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

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

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

[0071] Step S8: After updating the product data in the cart information, the transaction management device 60 generates product registration update screen information (screen information of the product registration screen, which is an update screen to which the registered product has been added) and transmits it to the customer terminal device 50. Specifically, the transaction management device 60 generates product registration update screen information such that the product registration update screen as shown in Fig. 9(C) is displayed on the customer terminal device 50, for example, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0072] The product registration screen (product registration update screen) shown in Fig. 9(C) is displayed on the customer terminal device 50 after "XX bread" is registered as the third product. In other words, when "XX yogurt" is stored in the cart information as the first product, the transaction management device 60 generates product registration update screen information such that "XX yogurt" is displayed on the customer terminal device 50 and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information, when "XX chocolate" is stored in the cart as the second product, the transaction management device 60 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed on the customer terminal device 50 and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information, and when "XX bread" is stored in the cart information as the third product, the transaction management device 60 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed on the customer terminal device 50 as shown in Fig. 9(C) and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

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

[0074] Step S10: The customer terminal device 50 accepts a payment instruction operation as an operation by the customer, for example, a touch of the "Proceed to Checkout" button shown in FIG.

[0075] Step S11: The customer terminal device 50 that has received the payment transition instruction generates a two-dimensional code. That is, the customer terminal device 50 converts information required to execute the payment process for the items purchased by the customer terminal device 50 (e.g., cart identification information) into a two-dimensional code. The customer terminal device 50 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, a code display screen showing the two-dimensional code as shown in FIG. 9(D) is displayed on the display unit.

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

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

[0078] Step S14: The transaction management device 60, which has received the cart identification information and the sub-calculation output request information from the customer terminal device 50, identifies the cart information of the transaction from the cart identification information.

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

[0080] Step S16: After calculating the subtotal, the transaction management device 60 updates the cart information (storing the subtotal (calculated subtotal)), and transmits the subtotal information indicating the calculated subtotal to the settlement device 40 together with the cart identification information.

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

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

[0083] After scanning a product, the customer terminal device 50 transmits the product code to the transaction management device 60 (S5). However, the customer terminal device 50 may be configured not to transmit product codes for products (e.g., products scanned after moving to another store) other than those scanned in the store (the store when the customer visited the store and displayed the product registration initial screen). For example, the customer terminal device 50 acquires and stores location information (GPS information) when the customer visits the store (or when the product registration initial screen is displayed). The customer terminal device 50 also acquires location information when scanning each product, and compares the location information acquired when the customer visits the store (or when the product registration initial screen is displayed). If the two match (or approximately match), the customer terminal device 50 may permit the transmission of the product code of the product to the transaction management device 60, and if they do not match (or approximately match), the customer terminal device 50 may prohibit the transmission of the product code of the product to the transaction management device 60. This makes it possible to prevent inappropriate product registration (for example, product registration to a cart created in another store, etc.).

[0084] When the settlement device 40 prohibits the transmission of the product code as described above, it may display an error message (e.g., "Registration is not possible because it is not in the XX store") on the customer-side display unit 405 after scanning the product. Furthermore, the settlement device 40 may display the above message on the store clerk-side display unit 410 instead of or in addition to the message on the customer-side display unit 405.

[0085] The settlement device 40 reads the two-dimensional code displayed on the display of the customer terminal device 50 and then requests the transaction management device 60 to calculate the subtotal amount (S13), but may not request calculation of the subtotal amount for products other than the product scanned in the store (for example, products scanned in other stores). For example, the settlement device 40 refers to the store identification information of the store (the settlement device 40 may store and refer to the store identification information of the store in its own settlement device 40, or may refer to the store identification information stored in another accessible device), and when reading the two-dimensional code displayed on the display of the customer terminal device 50, compares the cart identification information obtained from the two-dimensional code with the store identification information of the store. The settlement device 40 may permit the request to calculate the subtotal amount if the store identification information included in the cart identification information (see the configuration of the cart identification information in FIG. 7(B)) is configured to include the store identification information of the store, and may prohibit the request to calculate the subtotal amount if it is not configured to include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payments for products that are registered at other stores, etc.).

[0086] When the settlement device 40 prohibits the request for the subtotal amount as described above, after reading the two-dimensional code, the settlement device 40 may display an error message (e.g., "Settlement cannot be completed because the transaction includes products not from the XXX store") on the customer-side display unit 405. The settlement device 40 may also display the above message on the clerk-side display unit 410 instead of or in addition to the message on the customer-side display unit 405.

[0087] In the example of Fig. 8, the transaction management device 60 is configured to calculate the subtotal amount. However, for example, the settlement device 40 may acquire cart information from the transaction management device 60 and calculate the subtotal amount based on the acquired cart information. Alternatively, the transaction management device 60 may transmit cart information to the management device 10 and request calculation of the subtotal amount, the management device 10 may calculate the subtotal amount using the received cart information, and the calculated subtotal amount may be transmitted to the settlement device 40 via the transaction management device 60.

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

[0089] Furthermore, during checkout processing, the transaction management device 60 may determine whether or not the product information included in the cart information includes any reserved products, and if so, may request the checkout device 40 to provide instructions to correct the reserved products. Upon receiving a request to provide instructions to correct the reserved products, the checkout device 40 displays a message to notify the user that there are reserved products, as shown in Fig. 10(B). Upon confirming the message, the store clerk may correct the reserved products by entering a price corresponding to the reserved products or canceling the reserved products, etc.

[0090] <Second embodiment> [overview] Next, a second embodiment will be described. In the first embodiment, each time the customer terminal device 50 scans the code information of a product and reads the product code, the customer terminal device 50 transmits the read product code to the transaction management device 60. That is, in the first embodiment, each time the customer terminal device 50 executes a product registration process in response to the reading of the product code, the transaction management device 60 transmits product registration information including the product code obtained by the product registration process to the transaction management device 60. In this case, each time the transaction management device 60 receives product registration information from the customer terminal device 50, the transaction management device 60 stores the registered product information corresponding to the product code included in the product registration information in the cart information identified by the cart identification information included in the product registration information.

[0091] In contrast, in this embodiment, the customer terminal device 50 stores the product codes acquired by the product registration process in one transaction without transmitting them until a checkout instruction is issued. Then, in response to the checkout instruction being issued, the customer terminal device 50 transmits the product registration information including one or more product codes that it has stored up to that point to the transaction management device 60. The transaction management device 60 stores the registered product information corresponding to each of the one or more product codes included in the product registration information in the cart information identified by the cart identification information included in the received product registration information. In other words, the customer terminal device 50 in this embodiment transmits the product registration information in a lump sum in response to a checkout instruction. In this way, when the customer terminal device 50 transmits product registration information in a lump sum in response to a checkout transition instruction, the number of communications between the customer terminal device 50 and the transaction management device 60 can be reduced, which reduces the processing load and power consumption of the customer terminal device 50. In addition, the amount of traffic between the customer terminal device 50 and the transaction management device 60 can also be reduced.

[0092] [Regarding fraud] However, as described above, when the customer terminal device 50 is configured to send product registration information in bulk, unlike when product registration information is sent each time a product registration process is performed, it becomes possible for malicious customers to commit the following fraudulent acts.

[0093] FIG. 11 shows an example of a procedure executed by customer terminal device 50, settlement device 40, and transaction management device 60 in response to fraudulent activity that occurs when customer terminal device 50 is configured to transmit product registration information in bulk. Step S1001: The customer terminal device 50 transmits a transaction start request to the transaction management device 60 in response to, for example, a transaction start instruction operation (operation of the transaction start instruction button BT10) by a customer. Step S1002: The transaction management device 60 generates cart information in response to receiving the transaction start request transmitted in step S1001. Step S1003: The transaction management device 60 transmits to the customer terminal device 50 cart identification information indicating the cart information generated in step S1002.

[0094] Step S1004: The customer terminal device 50 displays a product registration screen on the display unit 504. Step S1005: The customer performs an operation to register product A as the first product (an operation to have the code of product A read by the code reader (imaging unit 506)). In response to this operation to register product A, the customer terminal device 50 executes a product registration process for product A. As a result, the customer terminal device 50 acquires the product code of product A and stores the acquired product code of product A. Step S1006: Next, the customer performs an operation to register product B as the second product. In response to this operation to register product B, the customer terminal device 50 executes a product registration process for product B. As a result, the customer terminal device 50 acquires the product code of product B and stores the acquired product code of product B.

[0095] Step S1007: The customer performs a payment transition instruction operation after registering the product B. The customer terminal device 50 accepts the payment transition instruction operation. Step S1008: The customer terminal device 50, which has accepted the settlement transition instruction operation in step S1007, transmits product registration information to the transaction management device 60, including the product code of product A registered in step S1005 and the product code of product B registered in step S1006. Step S1009: In response to receiving the product registration information transmitted in step S1008, the transaction management device 60 updates the cart information generated in step S1002. That is, the transaction management device 60 stores in the cart information the product information for each of product A and product B, which corresponds to the product codes of product A and product B included in the product registration information transmitted in step S1008.

[0096] Step S1010: In response to the payment transition instruction operation being performed in step S1007, the customer terminal device 50 generates a two-dimensional code and displays a code display screen with the generated two-dimensional code on the display unit 504. The two-dimensional code on the displayed code display screen indicates the cart identification information transmitted in step S1003. Step S1011: Here, a customer attempting to commit fraud performs an operation to have the image (screen image) of the screen on which the two-dimensional code was displayed in step S1010 saved in the customer terminal device 50 as image data using the screenshot function of the customer terminal device 50. Step S1012: After the customer has saved the screen image of the two-dimensional code in the customer terminal device 50 as described above, the customer performs a product addition declaration operation on the customer terminal device 50. The product addition declaration operation is an operation to return the customer terminal device 50 to a state where product registration is possible again, in response to a case where, for example, a customer realizes that there is a product that they forgot to register after performing a checkout transition instruction operation to temporarily complete product registration. The product addition declaration operation may be, for example, an operation on the "Return to Shopping" button BT20 arranged on the code display screen shown in Fig. 9(D). The customer terminal device 50 accepts the product addition declaration operation performed by the customer and transitions to a state in which the product can be registered. At this time, a product registration screen is displayed on the display unit 504.

[0097] Step S1013: When the product addition declaration operation is performed to display the product registration screen, the customer performs an operation to register product C as the third product. In response to the operation to register product C, the customer terminal device 50 acquires the product code of product C and stores the acquired product code of product C.

[0098] Step S1014: The customer who has registered product C does not display the code display screen by performing a payment transition instruction operation here, but instead displays the screen image saved in step S1011 on the display unit 504. Step S1015: The customer then goes directly to the settlement device 40 and causes the settlement device 40 to read the two-dimensional code on the screen image displayed in step S1014.

[0099] Step S1016: The settlement device 40 that has read the two-dimensional code in step S1015 transmits a settlement information request to the transaction management device 60. Step S1017: The transaction management device 60 identifies the cart information indicated by the cart identification information included in the payment information request sent in step S1016. Step S1018: The transaction management device 60 generates settlement information based on the identified cart information. The settlement information may be information including the contents to be printed on a receipt issued when the settlement process is performed by the settlement device 40. In other words, the settlement information may include information such as the breakdown of registered products and the total amount. The transaction management device 60 transmits the generated settlement information to the settlement device 40. Step S1019: The settlement device 40 executes the settlement process using the settlement information transmitted in step S1018. As the settlement process, the settlement device 40 completes the payment according to the settlement type designated by the customer. When the settlement type is designated as cash settlement, the settlement device 40 accepts a deposit operation from the customer and controls the dispensing of change according to the difference between the deposited amount (deposit amount) and the total price of the products. When the settlement type is designated as credit card, the settlement device 40 transmits the card information read from the credit card to the credit card settlement server 70, for example, via the transaction management device 60 (it does not have to be via the transaction management device 60), so that the settlement is made by credit card. The settlement device 40 also issues a receipt reflecting the settlement process result.

[0100] In the above procedure, the cart information contains product information corresponding to products A and B, but does not contain product information corresponding to product C. Therefore, even though the shopping cart contains three products, A, B, and C, the amount paid by the customer is only the amount corresponding to products A and B. In other words, in this case, the customer takes out products A, B, and C under the pretense of having registered all of them, but in fact has only paid the amount corresponding to products A and B; this is fraud. In this case, since the customer actually performs the operation to have the customer terminal device 50 read the code of product C, the fraud is less likely to be discovered than if the customer puts product C in the shopping cart and tries to take it away without having the customer terminal device 50 read the code information. Such fraud cannot be committed when the customer terminal device 50 transmits product registration information to the transaction management device 60 each time a product is registered, as in the first embodiment. However, if the customer terminal device 50 is configured to transmit product registration information in a lump sum in response to a settlement transition instruction operation being performed, the above-mentioned fraud becomes possible. Therefore, in this embodiment, the customer terminal device 50 is configured to transmit product registration information in bulk in response to a settlement transition instruction operation being performed, and then, as described below, fraud such as that shown in Figure 11 is prevented.

[0101] [Configuration of fraud prevention in this embodiment] In this embodiment, the transaction status for each transaction is managed by transaction management device 60. The transaction status here refers to the status of a transaction including product registration and settlement in one transaction. Figure 12 shows an example of a transaction status definition. Transaction statuses are classified into six statuses. Each of the six statuses is associated with a defined value of "0," "1," "2," "3," "4," or "5." The defined value "0" indicates that the cart information has been generated, but no product information has been stored in the cart information. This type of transaction status corresponds to the situation from when the customer issues a transaction start instruction to the customer terminal device 50 until when the customer issues a payment transition instruction, regardless of whether the customer has registered a product or not. The defined value "1" indicates a transaction status in which at least one item of product information is stored in the cart information, and the transaction management device 60 has not yet sent the settlement information to the settlement device 40 (the settlement device 40 has not acquired the settlement information). This transaction status corresponds to the stage where a legitimate customer has registered one or more items and then performed a settlement transition instruction operation, causing the code display screen to be displayed. The defined value "2" indicates that the transaction status is in the process of registering an additional product. This transaction status corresponds to a state in which, as a legitimate customer action, the customer has not yet performed a checkout instruction operation after declaring the addition of a product to the customer terminal device 50, regardless of whether or not the customer has performed a product registration operation for the additional product on the customer terminal device 50. The defined value "3" indicates a transaction status in which at least one item of product information is stored in the cart information, and the transaction management device 60 has already sent the settlement information to the settlement device 40 (the settlement device 40 has already acquired the settlement information). This type of transaction status corresponds to a state in which a legitimate customer action has been taken to cause the settlement device 40 to read the code display screen displayed on the customer terminal device 50, but the settlement at the settlement device 40 has not yet been completed. The defined value "4" indicates that the transaction is complete. This transaction status corresponds to a state in which the customer has completed payment at the payment settlement device 40 as a legitimate customer action. The defined value "5" indicates that the transaction has been canceled. This type of transaction corresponds to a state in which a legitimate customer has performed an operation to have the settlement device 40 read the code display screen displayed on the customer terminal device 50, and the settlement process has started once, but the transaction has been canceled by the settlement device 40 due to an operation to instruct the settlement device 40 to cancel the transaction, or an abnormality in the settlement device 40. Another example of a transaction being canceled by the settlement device 40 is when the settlement process is not completed even after a predetermined time has elapsed since the settlement process was started by the settlement device 40, resulting in a timeout. Another example of a transaction being canceled by the settlement device 40 is when, after the settlement process has been started by the settlement device 40, the settlement device 40 is unable to detect the customer who was making the settlement while the settlement process has not been completed. Such a situation in which a timeout occurs or the customer cannot be detected occurs, for example, when a customer leaves the settlement device 40 without completing the settlement. The detection of a customer by the settlement device 40 may be performed, for example, based on the output of a sensor that detects the presence of the customer at the location where the customer is located when settlement is performed by the settlement device 40. In this case, the sensor that detects the presence of the customer may be, for example, a human sensor or an imaging device (camera).

[0102] The transaction management device 60 manages transaction status information, which indicates the transaction status defined above, in association with each transaction. As a specific example, the transaction management device 60 may include transaction status information in cart information, as shown in Figure 7(C). The transaction status information indicates a defined value that indicates the current transaction status for the corresponding transaction.

[0103] The flowchart in FIG. 13 shows an example of a processing procedure executed by customer terminal device 50, settlement device 40, and transaction management device 60 of this embodiment in response to customer terminal-based transactions. First, an example of the processing procedure of the customer terminal device 50 will be described. Step S101: The customer terminal device 50 acquires store-specific information in response to, for example, the start of a shopping application. The acquisition of the store-specific information in step S102 may be performed in the same manner as in step S1 in FIG. Step S102: When the customer terminal device 50 acquires the store-specific information in step S101, it displays the start-up screen (FIG. 9(A)) and accepts a transaction start instruction operation (operation of the transaction start instruction button BT10) by the customer. Step S103: The customer terminal device 50 transmits a transaction start request to the transaction management device 60 in response to receiving the transaction start instruction operation in step S102. Step S104: Upon receiving the cart identification information sent from the transaction management device 60 in response to the transaction start request sent in step S103, the customer terminal device 50 stores the received cart identification information and displays a registration screen on the display unit 504.

[0104] Step S105: While the registration screen is displayed, the customer terminal device 50 judges whether or not a product registration operation has been performed. Product registration here refers to the customer operating a code reader to read a barcode, and the customer terminal device 50 acquiring a product code from the read barcode. Step S106: If it is determined in step S105 that the product registration operation has been performed, the customer terminal device 50 acquires the product code from the barcode read by the code reader. Step S107: The customer terminal device 50 updates the product registration information stored therein in accordance with the current transaction so as to include the product code acquired in step S106. Step S108: The customer terminal device 50 adds and displays the currently registered product on the product registration screen.

[0105] Step S109: After the process of step S108, or if it is determined in step S105 that the product registration operation has not been performed, the customer terminal device 50 determines whether or not a payment transition instruction operation has been performed.

[0106] Step S110: If it is determined in step S109 that the checkout instruction operation has been performed, the customer terminal device 50 transmits to the transaction management device 60 the product registration information currently stored therein. The product registration information transmitted in step S110 includes the product code by the processes in steps S106 and S107 after the product registration screen is displayed in the final step S104. The product registration information also includes the cart identifier received in response to step S104. Step S111: In response to the payment transition instruction operation being performed, the customer terminal device 50 generates a two-dimensional code indicating the cart identification information received in step S104, and displays a code display screen including the generated two-dimensional code on the display unit 504.

[0107] Step S112: The customer terminal device 50 judges whether or not a product addition declaration operation has been performed while the code display screen is being displayed. Step S113: When a product addition declaration operation is performed, the customer terminal device 50 transmits a product addition notification notifying that a product addition declaration operation has been performed to the transaction management device 60. After the process of step S113, the process returns to step S104, where the product registration screen is displayed again and product registration operation becomes possible.

[0108] Step S114: If the customer causes the settlement device 40 to read the two-dimensional code displayed in step S111 without performing a product addition declaration operation, as described below, the settlement device 40 requests settlement information from the transaction management device 60 (step S302), and the transaction management device 60 transmits the settlement information to the settlement device 40 in response to the request (step S211). After transmitting the settlement information to the settlement device 40, the transaction management device 60 sets the definition value of the transaction status information to "3." In addition, the customer terminal device 50 transmits a transaction status inquiry to the transaction management device 60 in response to displaying the two-dimensional code in step S111. The transaction management device 60 transmits transaction status information in response to receiving the transaction status inquiry. The customer terminal device 50 then determines whether the defined value of the transaction status information received from the transaction management device 60 is "3." If the defined value of the transaction status information is not "3," processing returns to step S112.

[0109] Step S115: If it is determined in step S114 that the defined value of the transaction status information is "3", this means that the settlement device 40 is in a state where it can start settlement in response to having read the two-dimensional code displayed in step S111. Therefore, the customer terminal device 50 issues a payment guide notification. The payment guide notification may be issued by display on the display unit 504 as shown in Fig. 14. In the figure, a message window WD2 showing a message instructing the customer to make payment at the payment device 40 is superimposed on the code display screen.

[0110] Next, an example of a processing procedure of the transaction management device 60 will be described. Step S201: The transaction management device 60 generates cart information in response to receiving the transaction start request transmitted from the customer terminal device 50 in step S103. Step S202: The transaction management device 60 also sets the defined value of the transaction status information in the cart information generated in step S201 to "0." Step S203: The transaction management device 60 also transmits to the customer terminal device 50 the cart identification information added to the cart information generated in step S201.

[0111] Step S204: The transaction management device 60 determines whether or not the product registration information transmitted from the customer terminal device 50 in step S110 has been received. Step S205: When the product registration information is received, the transaction management device 60 updates the cart information stored therein that is identified by the cart identifier included in the product registration information. In other words, the transaction management device 60 stores the product information that corresponds to the product code included in the received product registration information in the identified cart information. Step S206: In response to storing the product information in the cart information in step S205, the transaction management device 60 sets the definition value of the transaction status information to "1."

[0112] Step S207: The transaction management device 60 determines whether or not the product addition notification transmitted from the customer terminal device 50 in step S113 has been received. Step S208: If a product addition notification is received, the transaction management device 60 sets the definition value of the transaction status information to "2."

[0113] Step S209: After processing of step S208, or if it is determined in step S207 that a product addition notification has not been received, the transaction management device 60 determines whether a settlement information request sent from the settlement device 40 in step S302 has been received. If a settlement information request is not received, the process returns to step S204. Step S210: When a payment information request is received, the transaction management device 60 identifies, from among the cart information stored therein, the cart information indicated by the cart identifier included in the received payment information request. Step S211: The transaction management device 60 generates settlement information using the cart information identified in step S210. Then, the transaction management device 60 transmits the generated settlement information and the accounting status information stored in the cart information identified in step S210 to the settlement device 40. Step S212: In response to sending the settlement information in step S211, the transaction management device 60 sets the definition value of the transaction status information stored in the cart information identified in step S210 to "3." Step S213: The transaction management device 60 transmits the transaction status information, with the definition value set to "3" in step S212, to the customer terminal device 50 on which the shopping application of the application identification information (customer identification information) stored in the cart information identified in step S210 is installed.

[0114] Step S214: After the processing of step S212, the transaction management device 60 waits to receive either a settlement completion notice sent from the settlement device 40 in step S307 or a transaction cancellation notice sent in step S308. Step S215: If a settlement completion notice is received, the transaction management device 60 sets the definition value of the transaction status information stored in the cart information identified in step S210 to "4." Step S216: On the other hand, if a transaction cancellation notice is received, the transaction management device 60 sets the defined value of the transaction status information stored in the cart information identified in step S210 to "5."

[0115] Next, an example of a processing procedure of the settlement device 40 will be described. Step S301: The settlement device 40 reads the two-dimensional code in response to a customer's operation to read the two-dimensional code on the code display screen displayed on the customer terminal device 50. By reading the two-dimensional code, the settlement device 40 obtains cart identification information indicated by the two-dimensional code. Step S302: The settlement device 40 transmits a settlement information request including the cart identification information acquired in step S301 to the transaction management device 60.

[0116] Step S303: In response to the settlement information request sent in step S302, the transaction management device 60 sends settlement information and transaction status information in step S211. The settlement device 40 then determines whether settlement is possible based on the defined value of the transaction status information received from the transaction management device 60. Specifically, the settlement device 40 determines that settlement is possible if the defined value of the received transaction status information is "1", and determines that settlement is not possible if the defined value is other than "1".

[0117] According to the processing procedure of the customer terminal device 50 in the figure, when a legitimate customer has finished registering a product and wishes to proceed to checkout, the customer must perform a checkout transition instruction operation to display the code display screen. When the checkout transition instruction operation is performed, product registration information is sent from the customer terminal device 50 to the transaction management device 60 in step S110. This is also true when a product addition declaration operation is performed to add a registered product; when a customer has finished adding a registered product and wishes to proceed to checkout, the customer must perform a checkout transition instruction operation. Note that even if a product addition declaration operation is performed but the product is not registered, a checkout transition instruction operation must be performed to proceed to checkout. In this way, when a product addition declaration operation is performed but the product is not registered, the product registration information sent by customer terminal device 50 step S110 in response to the checkout transition instruction operation being performed may be, for example, information indicating that no additional products have been added. Then, in response to receiving the product registration information, transaction management device 60 sets the definition value of the transaction status information to "1." Therefore, if the customer has had the two-dimensional code read by settlement device 40 following valid procedures, the defined value of the transaction status information sent from transaction management device 60 in step S211 will be "1." Therefore, if the defined value of the transaction status information sent from the transaction management device 60 in step S211 is other than "1," there is a possibility that some kind of fraud has occurred. For example, if a customer commits the fraud described in Figure 11, the transaction management device 60 sets the defined value of the transaction status information to "2" in response to receiving a product addition notification, but then receives a settlement information request from the settlement device 40 without receiving any product registration information. In this case, the transaction management device 60 will send transaction status information with a defined value of "2" in step S211, and it will be determined in step S303 that settlement is not possible. Note that if the defined value of the transaction status information is other than "1," it may be that some kind of abnormality has occurred in the operation of the system. In any case, if the defined value of the transaction status information is other than "1," it is not appropriate to proceed to settlement processing as is, and so in step S303 it may be determined that settlement is not possible.

[0118] Step S304: If it is determined in step S303 that the settlement is not possible, the settlement device 40 does not proceed to the settlement process, but issues a notification corresponding to the fact that the settlement is not possible (a notification corresponding to the fact that the settlement is not possible). The settlement impossibility response notification in the settlement device 40 may be directed to either the customer or the store clerk, or may be directed to both the customer and the store clerk. The settlement impossibility response notification for the customer may be made by display on the customer side display unit 405. The settlement impossibility response notification for the store clerk may be made by display on the store clerk side display unit 410. The settlement impossibility response notification may also be made by a business terminal such as the management device 10 provided in the store. The management device 10 may be, for example, a customer terminal device 50 in the store or an assist monitor that displays the operating status of the settlement device 40. The business terminal may also be a terminal carried by the store clerk.

[0119] Furthermore, the content of the payment impossibility notification may be changed depending on the definition value of the received transaction status information. For example, when the defined value is "0", "2", etc., a payment impossible notification may be displayed, instructing the customer to perform a payment transition instruction operation to display the code display screen and to read the two-dimensional code again. FIG. 15 shows an example of a payment impossible notification for customers that is displayed on the customer display unit 405 when the defined value is "0", "2", etc. The payment impossible notification shown in the figure displays a message in message area AR10 on the standby screen displayed on the customer display unit 405 saying "Please press the 'Proceed to checkout' button on the app and have the QR code displayed on the smartphone screen read." When the defined value is "3", a non-payment notification may be displayed to inform the customer that the 2D code read this time cannot be accepted because it has already been read by the settlement device 40 in the past. FIG. 16 shows an example of a non-payment notification for the customer that is displayed on the customer display unit 405 when the defined value is "3" or the like. The non-payment notification shown in the figure displays a message saying "This QR code has already been read" in the message area AR10 on the standby screen displayed on the customer display unit 405. When the defined value is "4", a payment impossible notification may be issued to inform the customer that the transaction corresponding to the currently read two-dimensional code cannot be accepted because the transaction has already been completed. Fig. 17 shows an example of a payment impossible notification for the customer that is displayed on the customer display unit 405 when the defined value is "4" or the like. The payment impossible notification shown in the figure displays the message "This transaction has already been settled" in the message area AR10 on the standby screen displayed on the customer display unit 405. When the defined value is "5", a non-payment notification may be displayed to inform the customer that the transaction corresponding to the currently read 2D code has already been canceled and cannot be accepted. Fig. 18 shows an example of a non-payment notification for the customer that is displayed on the customer display unit 405 when the defined value is "5" or the like. The non-payment notification shown in the figure displays the message "This transaction has been canceled" in the message area AR10 on the standby screen displayed on the customer display unit 405. Furthermore, if it is determined in step S303 that payment is not possible, there is a possibility that fraud has been committed by the customer or that a system malfunction has occurred, so the payment device 40 may be configured to issue a notification in step S304 that payment is not possible, in order to call a store employee.

[0120] Step S305: If it is determined in step S303 that settlement is possible, the settlement device 40 starts settlement processing. Step S306: After the settlement process has started, the customer can perform an operation to instruct the settlement device 40 to cancel the settlement for this transaction (a settlement cancel operation). Alternatively, the settlement device 40 may cancel the settlement if some kind of failure occurs during the settlement process and the settlement process cannot be completed. If the transaction is canceled, the payment process is terminated without being completed. The customer is also instructed to return the registered products to the store. Therefore, the payment device 40 determines whether the transaction has been canceled during the payment process. Step S307: If the settlement process is completed without the transaction being canceled, the settlement device 40 sends a settlement completion notice to the transaction management device 60. Step S308: If the transaction is canceled, the settlement device 40 sends a transaction cancellation notice to the transaction management device 60.

[0121] <Modification> Modifications of this embodiment will be described below. The modifications described below may be combined as appropriate. [First Modification] 13, the settlement device 40 determines whether or not settlement is possible based on the transaction status information. In contrast, in this modified example, the transaction management device 60 may determine whether or not settlement is possible based on the transaction status information and transmit the result of the determination to the settlement device 40. Additionally, while the transaction status information in the above embodiment is information indicating a defined value according to the transaction status, the transaction status information may be information indicating, for example, the history of cart information generation, product registration information reception, product addition notification reception, payment information transmission, payment completion notification reception, transaction cancellation notification reception, etc.

[0122] [Second modified example] In this modification, the customer terminal device 50 displays a two-dimensional code including the product code of the product registered for one transaction. As a result, even if a failure occurs and communication between the settlement device 40 and the transaction management device 60 becomes impossible, as long as the settlement device 40 is in an environment where it can obtain the product master, it is possible to generate settlement information and execute settlement processing by reading the two-dimensional code on the code display screen displayed on the customer terminal device 50. Furthermore, the two-dimensional code displayed on the customer terminal device 50 includes the date and time as the expiration date. As a result, if fraud is committed using the procedure shown in Fig. 11, for example, when a screen image saved by the screenshot function is displayed and read by the settlement device 40, if the current date and time has passed the expiration date shown in the two-dimensional code, the settlement device 40 can determine that settlement is not possible. This prevents fraud using the procedure shown in Fig. 11. Also, the transaction management device 60 may set a date and time as the expiration date for each piece of cart information that it manages. In this case, in response to fraudulent activity, for example, as illustrated in FIG. 11, the settlement device 40 reads the two-dimensional code saved as a screen image by the screenshot function and transmits a settlement information request to the transaction management device 60. The transaction management device 60 searches for cart information corresponding to the cart identification information indicated by the two-dimensional code, and checks the expiration date set in the searched cart information. If the current date and time has passed the expiration date set in the searched cart information, the transaction management device 60 can determine that settlement by the settlement device 40 is not possible, and notify the settlement device 40 that settlement is not possible.

[0123] [Third Modification] For example, the customer terminal device 50 may acquire its own location using at least one of GPS, communication with a wireless LAN access point in the store, and communication with a beacon. In addition, the customer terminal device 50 of this modified example may display a two-dimensional code (code display screen) on the condition that the customer terminal device 50 is located within a certain distance from the settlement device 40. In this way, for example, a customer who is trying to commit fraud must move close to the settlement device 40 in order to save a screen image of the two-dimensional code using the screenshot function, which can provide a deterrent effect against fraud.

[0124] [Fourth Variation] In addition, the customer terminal device 50 and the settlement device 40 of this modification may be capable of predetermined short-distance wireless communication, such as NFC (Near Field Communication). In addition, the customer terminal device 50 may display a two-dimensional code on the condition that it is connected to the settlement device 40 via short-distance wireless communication. In this case, the customer terminal device 50 may display the two-dimensional code in response to a customer performing a settlement transfer instruction operation while connected to the settlement device 40 via short-distance wireless communication, or may display the two-dimensional code in response to connection via short-distance wireless communication. This also enhances the fraud prevention effect as in the third modification.

[0125] [Fifth Modification] Furthermore, for example, the customer terminal device 50 on which a shopping application runs may have a function of prohibiting the saving of images by screenshots at least when the code display screen is displayed on the display unit 204.

[0126] [Sixth Modification] As shown in Figures 7(A) and 7(C), the cart information is associated with a customer registered in the customer information by the customer identification information. Therefore, in this modified example, for example, the transaction management device 60 may manage a customer associated with cart information of a transaction that has been determined to be unsettled because the defined value of the accounting status information is a predetermined value, such as "2," so that the customer can be distinguished from other customers who have not been determined to be unsettled.

[0127] [Seventh Variation] The functions of the transaction management device 60 of the above embodiment may be provided, for example, in the settlement device 40, and the function of determining whether or not settlement is possible using the processing procedure of Figure 13 may be configured to be realized by the customer terminal device 50 and the settlement device 40.

[0128] [Eighth Modification] In addition, even in a configuration in which the customer terminal device 50 transmits product registration information to the transaction management device 60 each time it scans the product code information, as in the first embodiment, the transaction status for each transaction may be managed using transaction status information indicating the transaction status for a transaction.

[0129] <Summary of the embodiment> [Technical field] The present invention relates to a product sales data processing system. [Background technology] 2. Description of the Related Art There is known a self-registration system that allows a customer to register products using a smartphone or the like when shopping in a store (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2016-219034 A [Summary of the Invention] [Problem to be solved by the invention] In the above-mentioned product sales data processing system in which a customer uses a terminal to register products, the customer basically performs operations related to the transaction from product registration to payment without the intervention of a store clerk. For this reason, the product sales data processing system is required to operate appropriately according to the transaction situation. The present invention has been made in consideration of the above circumstances, and has an object to enable a product sales data processing system, in which customers register products using a terminal, to operate appropriately according to the status of the transaction. [Means for solving the problem] (1) As described above, one aspect of this embodiment is a product sales data processing system in which a customer terminal device (50) used by a customer performs product registration processing, and a settlement device (40) performs settlement processing in response to an operation by the customer using settlement information based on the result of the product registration processing, the system including: a code information display means for displaying code information including at least transaction identification information for identifying a transaction on the customer terminal device in response to a settlement transition instruction to the customer terminal device; a reading means for reading the displayed code information (e.g., a two-dimensional code) on the settlement device; and a processing means for reading the transaction identification information included in the code information read by the reading means on the settlement device. a settlement information acquisition means for acquiring settlement information based on transaction information (e.g., cart information) specified by information obtained by the customer terminal device, an updating means for updating accounting status information indicating the status of a transaction from product registration to settlement in accordance with the progress of processing of at least one of the customer terminal device and the settlement device, and a settlement feasibility determination means (e.g., processing of step S303) for determining whether or not settlement processing can be performed using the settlement information acquired by the settlement information acquisition means, based on the accounting status information corresponding to the transaction indicated by the transaction identification information included in the code information read by the reading means. In addition, the product sales data processing system of (1) may be equipped with a management means for, for example, reflecting the results of all product registration processes performed up to that point in a transaction in a single transaction in the transaction information in response to the settlement transition instruction to the customer terminal device.

[0130] With the above configuration, for example, with the shopping system of this embodiment, it is possible to obtain transaction status information that shows the status of a transaction from product registration to payment. Obtaining such transaction status information makes it possible to operate the shopping system appropriately according to the transaction status. Furthermore, in the above configuration, whether or not settlement is possible is determined based on the transaction status information. This makes it possible to prevent the settlement process from being executed if the transaction status is not appropriate, and in this respect, the above configuration allows the shopping system to operate appropriately according to the transaction status.

[0131] (2) One aspect of this embodiment is the product sales data processing system described in (1), wherein the settlement feasibility determination means determines that settlement is possible when the accounting status information indicates a normal state (e.g., a state where the defined value is “1”) in which the results of the product registration process have been reflected in the transaction information and the settlement information acquisition means has not yet acquired the settlement information (e.g., the transaction management device 60 has not yet sent the settlement information), and determines that settlement is not possible when the accounting status information indicates a state other than the normal state.

[0132] With the configuration (1) shown above, when a customer registers a product using the normal procedure on customer terminal device 50 and then issues a payment instruction, and the payment device 40 reads the two-dimensional code displayed on customer terminal device 50, the payment device 40 will obtain transaction status information with a defined value of "1" from the transaction management device 60. For this reason, with the configuration of (2), for example, if the payment device 40 reads a two-dimensional code that a customer has displayed using a procedure different from the normal procedure, the payment device 40 will obtain transaction status information with a defined value other than "1," making it possible to prevent payment from being processed.

[0133] (3) One aspect of this embodiment is a product sales data processing system as described in (1) or (2), which is provided with a notification means for making a notification according to the accounting status information when the settlement feasibility determination means determines that settlement processing is not possible.

[0134] According to the above configuration, it is possible to notify either the store clerk or the customer, or both, of appropriate information depending on the content of the transaction status information that was used as the basis for determining that the payment process was not possible.

[0135] In addition, a program for realizing the functions of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, etc. described above in each of the above embodiments may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing as the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, etc. described above. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. In addition, the recording medium also includes a recording medium provided inside or outside and accessible from a distribution server to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network. The above program may also be for realizing part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0136] 1 POS system, 10 management device, 40 settlement device, 50 customer terminal device, 60 transaction management device, 70 credit card settlement server

Claims

1. A product sales data processing system having a customer terminal device that performs a product registration process in response to an operation of a customer, a settlement device that performs a settlement process in response to an operation of the customer by using settlement information based on a result of the product registration process, and a transaction management device that generates transaction information indicating a result of the product registration process performed by the customer terminal device, a code information display means for displaying code information including at least transaction identification information for identifying a transaction on the customer terminal device in response to a settlement transition instruction to the customer terminal device; A reading means for reading the displayed code information in the settlement device; a settlement information acquisition means for acquiring settlement information generated and transmitted by the transaction management device based on the transaction information identified by the transaction identification information included in the code information read by the reading means, in the settlement device; an update means for updating, in the transaction management device, transaction status information indicating the status of a transaction from a first status indicating the first status when the payment transition instruction is issued to a second status indicating the additional registration of a product after the payment transition instruction is issued; a settlement possibility determination means, in the settlement device, for determining that settlement processing is impossible when the accounting status information acquired from the transaction management device by the settlement information acquisition means corresponds to the code information read by the reading means and indicates the second status; A product sales data processing system comprising:

2. The settlement device is provided with a notification means for notifying the fact that settlement is not possible when the settlement possibility determination means determines that settlement processing is not possible.

2. The product sales data processing system according to claim 1.

3. A product sales data processing system having a customer terminal device that performs a product registration process in response to an operation of a customer, a settlement device that performs a settlement process in response to an operation of the customer by using settlement information based on a result of the product registration process, and a transaction management device that generates transaction information indicating a result of the product registration process performed by the customer terminal device, a code information display means for displaying code information including at least transaction identification information for identifying a transaction on the customer terminal device in response to a settlement transition instruction to the customer terminal device; A reading means for reading the displayed code information in the settlement device; a settlement information acquisition means for acquiring settlement information generated and transmitted by the transaction management device based on the transaction information identified by the transaction identification information included in the code information read by the reading means, in the settlement device; an update means for updating, in the transaction management device, transaction status information indicating the status of a transaction from a first status indicating the first status when the payment transition instruction is issued to a second status indicating the additional registration of a product after the payment transition instruction is issued; a settlement possibility determination means for determining whether settlement processing is possible or impossible depending on whether the accounting status information corresponding to the code information read by the reading means indicates the second status in the transaction management device; a transmission means for transmitting a result of the determination by the settlement possibility determination means to the settlement device in the transaction management device; A product sales data processing system comprising:

Images