Product sales data processing system

Abstract

To improve the convenience of a customer in a self registration system in which the customer performs commodity registration using a terminal.SOLUTION: A commodity sales data processing system includes: transaction determination means for determining whether there is a halfway transaction in which commodity registration is being performed by a customer terminal device for performing commodity registration in a predetermined time; and operation control means for controlling the operation of a settlement device for executing a customer terminal correspondence settlement for commodities registered by the customer terminal device on the basis of the result of the determination by the transaction determination means.SELECTED DRAWING: Figure 11

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] For example, in consideration of the widespread use of self-registration systems in which customers use terminals to register products, it is preferable to provide convenience to customers who use the self-registration system.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide convenience to customers in a self-registration system in which customers register products using a terminal. [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 including a customer terminal device that registers products, a transaction management device that stores product registration information reflecting the product registration results by the customer terminal device, and a settlement device that performs customer terminal-compatible settlement corresponding to the products registered by the customer terminal device based on the product registration information, wherein the product sales data processing system is equipped with a transaction determination means that determines whether or not there is an ongoing transaction while product registration is being performed by the customer terminal device at a specified time, and an operation control means that controls the operation of the settlement device that performs customer terminal-compatible settlement corresponding to the products registered by the customer terminal device based on the determination result of the transaction determination means. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a shopping system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of installation of a settlement device in this embodiment. [Diagram 3] 1 is a diagram showing an example of the appearance of a settlement device according to an embodiment of the present invention; [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a settlement device in the present embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device in the present embodiment. [Figure 6] 1 is a diagram illustrating an example of the configuration of a transaction management device in this embodiment. [Figure 7] 3A to 3C are diagrams illustrating an example of customer information, store information, and cart information according to the present embodiment. [Figure 8] A sequence diagram showing an example of a processing procedure executed by a customer terminal device, a settlement device, and a transaction management device in this embodiment in response to customer terminal-responsive accounting for one transaction. [Figure 9] 11A to 11C are diagrams illustrating an example of a product registration initial screen, a product registration update screen, and a code screen according to the present embodiment. [Figure 10] 13A to 13C are diagrams showing an example of the display of the subtotal amount and the display notifying of reserved products on the customer side display unit in this embodiment. [Figure 11]A diagram showing an example of a processing procedure executed by the settlement device in this embodiment in relation to the termination control of the customer terminal-responsive settlement mode. [Figure 12] A diagram showing an example of a processing procedure executed by the settlement device in this embodiment in relation to the startup control of the customer terminal-compatible settlement mode. [Figure 13] 13A to 13C are diagrams showing an example of a settlement device status screen and an in-progress transaction status screen in this embodiment. [Figure 14] 5A and 5B are diagrams illustrating an example of a start-up screen and a product registration screen according to the embodiment. [Figure 15] FIG. 13 is a diagram showing an example of a closing process execution confirmation screen in the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] <Embodiment> [Example of shopping system configuration] Fig. 1 shows an example of the configuration of a shopping system according to this embodiment. The shopping system in the figure corresponds to accounting (customer terminal-compatible accounting) in which, for example, a customer takes out a product to be purchased from a shelf, registers the taken-out product using a customer terminal device 50, and also settles the registered product at a settlement device 40. The accounting here refers to a procedure carried out in response to one transaction, including product registration and settlement of the registered product. In the following explanation, settlement carried out by a customer using the settlement device 40 in customer terminal-compatible accounting is also referred to as customer terminal-compatible settlement. 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 the 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 capable of communicating with a 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 provided by the store instead of being owned by the customer as described above. In the case of a customer terminal device 50 provided by the store, it may be provided as a device that is attached to a shopping cart and operated by the customer.

[0012] The customer terminal device 50 also captures an image (releases the shutter) of the product (for example, the surrounding area with a barcode) and generates a captured image (image data). The customer terminal device 50 may release 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 releases 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] The settlement device 40 of this embodiment can be switched between a total of four operating modes: a customer terminal-compatible settlement mode that is set to perform settlement corresponding to customer terminal-compatible settlement, and three accounting modes (first to third accounting modes) that correspond 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. For example, the transaction management device 60 may refer to the cart information at a predetermined time every day, for example, and update the customer information.

[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. The cart identification information is identification information that uniquely identifies a cart. 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.

[0046] The transaction end date and time is the end date and time of the transaction. For example, the transaction end date and time may be the settlement date and time. The customer identification information is 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.

[0047] 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 (1) is the registration information for one product item. Registered product information (2) is the registration information for two products. In the example shown in Figure 7 (C), registered product information (3) to registered product information (5) are omitted from the illustration. Registered product information (N; N is an integer) includes the product code, product name (product name), price, etc.

[0048] The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management device 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.

[0049] 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.

[0050] 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.

[0051] 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).

[0052] 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.

[0053] 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) and image data (image data captured when reading was NG). For example, if the Nth item is a reserved product due to NON-PLU, the reserved product information (reserved product N) includes the reserved product type "1 (NON-PLU)" and image data. Also, if the Nth item is a reserved product due to reading being NG, the reserved product information (reserved product N) includes the reserved product type "2 (cannot be read)" and image data.

[0054] 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).

[0055] [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.

[0056] 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.

[0057] 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.

[0058] The customer terminal device 50, which has acquired the store identification information, transmits the acquired store identification information together with the customer identification information as a transaction start request to the transaction management device 60. The transaction start request may be transmitted in response to a customer's operation on the customer terminal device 50, or may be transmitted in response to acquisition of the store identification information. 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.

[0059] 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 addition, in the case of scanning a two-dimensional code, the destination information may also be converted into a two-dimensional code in addition to the store-specific information, 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.

[0060] 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 a cart for the transaction. Specifically, it generates cart information as shown in Fig. 7(C). Note that 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.

[0061] 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.

[0062] 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, the current date, and the 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.

[0063] Step S3: The transaction management device 60, which has generated the cart 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 cart identification information.

[0064] 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(A).

[0065] 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.

[0066] The customer terminal device 50 that has acquired the barcode transmits the scanned product code to the transaction management device 60 together with the cart identification information.

[0067] Step S6: The transaction management device 60 receives the cart identification information and the product code from the customer terminal device 50 and identifies the cart of the transaction from the cart identification information.

[0068] Step S7: The transaction management device 60 updates the product data in the identified cart. Specifically, when the transaction management device 60 receives a product code as the Nth item, it stores the product code as the product code of the registered product information (registered product N) in the cart information of the identified cart, 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). In addition, the transaction management device 60 updates the registered product information (total) in the cart information of the identified cart.

[0069] Step S8: After updating the product data in the cart, 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 a product registration update screen such as that shown in Fig. 9(B) 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.

[0070] The product registration screen (product registration update screen) shown in Fig. 9(B) is displayed on the customer terminal device 50 after "XX bread" is registered as the third product. That is, when "XX yogurt" is stored in the cart 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, when "XX bread" is stored in the cart 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(B) and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0071] 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(B). As described above, the product registration screen (product registration update screen) shown in Fig. 9(B) is displayed on the customer terminal device 50 after "XX bread" is registered as the third product item.

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

[0073] Step S11: The customer terminal device 50 that has accepted the accounting instruction generates a two-dimensional code. That is, the customer terminal device 50 converts information required to execute the settlement 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 screen showing the two-dimensional code as shown in FIG. 9(C) is displayed on the display unit.

[0074] 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 a store clerk into the recognition range of the customer-side scanner unit 406.

[0075] 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.

[0076] 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 of the transaction from the cart identification information.

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

[0078] 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.

[0079] 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).

[0080] 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.

[0081] 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.).

[0082] 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.

[0083] Furthermore, if the location information acquired when scanning the product does not match (or approximately matches) the location information acquired when the customer arrived at the store, or if the location information cannot be acquired when scanning the product and comparison of the location information cannot be performed, the customer terminal device 50 may send information equivalent to a notification of transaction completion to the transaction management device 60 and update the transaction completion date and time. For example, a state in which the location information does not match may indicate fraud, such as a customer registering a product while temporarily leaving the store. Also, a state in which location information cannot be received when scanning a product occurs, for example, due to a malfunction of the customer terminal device 50. It is not desirable for the cart information to remain in such a state and for the transaction to not be completed. In such a case, when the location information becomes comparable and returns to a matching state, the customer terminal device 50 may, for example, clear the transaction end date and time in the cart information, thereby returning the corresponding transaction to a state in which it has not been completed.

[0084] The settlement device 40 reads the two-dimensional code displayed on the display unit of the customer terminal device 50 and then requests the transaction management device 60 to calculate the subtotal amount (S12), 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 unit 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, payment for products registered at other stores, etc.).

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] [Operation control of payment device: Termination control of customer terminal compatible payment mode] In a store in which the shopping system of this embodiment is installed, the time period during which customer terminal-based transactions are accepted on a business day (transaction acceptance time period) may be set to be shorter than the business hours for operational reasons. As an example, if the opening and closing hours on a business day are 9:00-20:00, the transaction acceptance time period may be set to be 10:00-19:00. In this way, by setting the transaction acceptance time period shorter than the business hours, the burden on store staff of guiding customers who use customer terminal device 50 to make transactions and dealing with problems can be reduced, and operations according to opening and closing times can be carried out smoothly. However, for example, there are cases where a customer starts registering products in customer terminal-compatible accounting before 7 p.m., but 7 p.m. passes before product registration is completed. In such a case, if the customer terminal-compatible accounting mode is terminated at 7 p.m. for a settlement device 40 that has been operating in the customer terminal-compatible accounting mode, the following will occur. That is, a customer who has been registering products under customer terminal-compatible accounting that began before 7 p.m. cannot make a settlement using the settlement device 40 in the customer terminal-compatible accounting mode after 7 p.m. In this case, the customer must go to a settlement device 40 that is operating in, for example, the second or third accounting mode to make a settlement. In this case, the customer may feel inconvenienced or feel that the customer terminal-compatible accounting service is not very useful.

[0090] Therefore, in this embodiment, for example, for a transaction in which product registration corresponding to customer terminal-compatible accounting has begun before the end of the accounting acceptance period, settlement can be made at a settlement device 40 set to the first accounting mode even after the accounting acceptance period has passed. By providing convenience to customers in this way, for example, it is possible to prevent customers from feeling inconvenienced or unhelpful about the customer terminal-compatible accounting service, which can also lead to the spread of customer terminal-compatible accounting services.

[0091] The flowchart in FIG. 11 shows an example of a processing procedure executed by the settlement device 40 in relation to the termination control of the customer terminal corresponding settlement mode. Step S101: The settlement device 40, which is operating with the customer terminal-compatible settlement mode set, waits for the end of the transaction acceptance period. Step S102: When it is determined that the end time of the transaction acceptance period has arrived, the settlement device 40 makes an in-progress transaction inquiry to the transaction management device 60. The in-progress transaction inquiry is a command to inquire as to whether there are any transactions (in-progress transactions) that started before the end time of the customer terminal compatible transaction acceptance period but have not yet been settled after the end time has passed.

[0092] In response to the mid-transaction inquiry in step S102, the transaction management device 60 determines whether or not there is a mid-transaction. When determining whether or not there is a mid-transaction, the transaction management device 60 may determine whether or not there is cart information stored in the memory unit 602 in which the transaction start date and time is before the end time of the accounting acceptance period and the transaction end date and time is unconfirmed. A transaction corresponding to such cart information is a mid-transaction. However, some customers may register products partially in the customer terminal-compatible checkout, but then stop shopping or change their mind and settle the payment using the checkout device 40 set to another operating mode (any of the first to third checkout modes) other than the customer terminal-compatible checkout mode. In such cases, the cart information generated in response to the partially registered products in the customer terminal-compatible checkout may be stored in the transaction management device 60 without being erased. It is preferable to prevent transactions corresponding to such invalid cart information from being treated as halfway transactions. Therefore, when determining whether or not there is a halfway transaction, the transaction management device 60 may treat cart information whose transaction start date and time is before the end time of the checkout acceptance period and whose transaction end date and time is not yet determined, and whose transaction start date and time is more than a certain time before the current time, as not corresponding to a halfway transaction. The transaction management device 60 transmits the result of the determination as to whether or not there is an incomplete transaction to the settlement device 40.

[0093] Step S103: The settlement device 40 determines, based on the determination result sent from the transaction management device 60, whether or not there is an incomplete transaction. If it is determined that there is an incomplete transaction, the process returns to step S102. The incomplete transaction inquiry in step S102 is executed after a certain time has elapsed since the incomplete transaction inquiry in step S102. In other words, the process in step S102 is executed at regular intervals when there is an incomplete transaction.

[0094] Step S104: On the other hand, if it is determined in step S103 that there is no mid-transaction, the settlement device 40 ends the customer terminal corresponding settlement mode. The settlement device 40 that has ended the customer terminal-compatible settlement mode may proceed directly to a closing process. The closing process is also called a closing process, and includes a process of transmitting the history of settlement processes (sales results) for each transaction stored by the settlement device 40 to the management device 10, etc. Alternatively, the settlement device 40 that has ended the customer terminal-compatible settlement mode may be set to a predetermined settlement device 40 among the first accounting mode, the second accounting mode, and the third accounting mode. Alternatively, the settlement device 40 that has ended the customer terminal-compatible settlement mode may transition to a predetermined accounting mode after executing a closing process corresponding to operation in the customer terminal-compatible settlement mode.

[0095] For example, if the customer terminal-compatible settlement mode is set for multiple settlement devices 40, all of the settlement devices 40 in the customer terminal-compatible settlement mode will execute the process shown in the figure. Therefore, if it is determined that there is at least one mid-transaction, all of the settlement devices 40 in the customer terminal-compatible settlement mode will maintain the customer terminal-compatible settlement mode. For example, in a store, it may be desirable to limit the settlement devices 40 that maintain the customer terminal-compatible settlement mode in response to a mid-transaction to some of the settlement devices 40 in which the customer terminal-compatible settlement mode is set. In such a case, the settlement devices 40 that execute the process shown in the figure to some of the settlement devices 40 in which the customer terminal-compatible settlement mode is set, and the other settlement devices 40 in which the customer terminal-compatible settlement mode is set may end the customer terminal-compatible settlement mode in response to the end of the transaction acceptance time period, and execute, for example, a closing process. Furthermore, depending on the number of pending transactions, the number of settlement devices 40 that maintain the customer terminal-compatible settlement mode after the end of the accounting acceptance period may be controlled to be changed among the settlement devices 40 that have the customer terminal-compatible settlement mode set. In this way, when controlling the operation of some of the settlement devices 40 in which the customer terminal-compatible settlement mode is set to maintain the customer terminal-compatible settlement mode, one settlement device 40 functioning as a master may determine which settlement devices 40 will maintain the customer terminal-compatible settlement mode and which settlement devices 40 will terminate the customer terminal-compatible settlement mode, and perform operation control of each settlement device 40.

[0096] By executing the process in the figure, the customer terminal-responsive settlement mode is maintained until the settlement of all pending transactions is completed and there are no more pending transactions, even if the end of the accounting acceptance period is reached. As a result, even if product registration using customer terminal-responsive settlement is started before the end of the accounting acceptance period, but the accounting acceptance period has passed by the time of settlement, settlement can be made by settlement device 40 set to customer terminal-responsive settlement mode.

[0097] [Operation control of payment device: Start-up control of payment mode compatible with customer terminals] In order to make it impossible to handle customer terminal-based payments before the start of the payment acceptance period, the payment device 40 is set to a state in which the customer terminal-based payment mode is not set. However, for the convenience of customers, it is preferable to make customer terminal-based payments possible for customers who enter the store after opening time and wish to carry out customer terminal-based payments before the start of the payment acceptance period. Therefore, in this embodiment, if a customer starts registering a product for customer terminal-compatible accounting between the time when the store opens and the start time of the accounting reception hours, the customer terminal-compatible accounting can be handled even before the start time of the accounting reception hours.

[0098] The flowchart in Fig. 12 shows an example of a processing procedure executed by the settlement device 40 in relation to the start-up control of the customer terminal compatible settlement mode. When the processing in the figure is started, a predetermined mode state other than the customer terminal compatible settlement mode is set in the settlement device 40. The predetermined mode state other than the customer terminal compatible settlement mode may be, for example, any one of the first to third accounting modes, or may be, for example, a mode selection standby mode before a mode is selected from the customer terminal compatible settlement mode or the first to third accounting modes.

[0099] Step S201: The settlement device 40, which is set to the customer terminal-compatible settlement mode and is operating, determines whether the start time of the transaction acceptance period has arrived. Step S202: If it is determined that the start time of the transaction acceptance period has not yet arrived, the settlement device 40 makes an inquiry about an intermediate transaction to the transaction management device 60. In this case, an intermediate transaction is a transaction that started after the store opening time, but the settlement has not yet been completed at the present time. In response to the mid-transaction inquiry in step S202, the transaction management device 60 determines whether or not there is a mid-transaction, and transmits the determination result regarding the presence or absence of a mid-transaction to the settlement device 40.

[0100] Step S203: The settlement device 40 determines whether or not there is an incomplete transaction based on the determination result sent from the transaction management device 60. In this case, the cart information corresponding to an incomplete transaction is cart information in which the transaction start date and time is before the start time of the accounting acceptance period and the transaction end date and time is not yet determined. If it is determined that there is no mid-transaction, the process returns to step S201. As a result, the mid-transaction inquiry in step S202 is executed at regular time intervals before the start time of the transaction acceptance period, provided that there is no mid-transaction.

[0101] Step S204: On the other hand, if it is determined in step S203 that there is an ongoing transaction, or if it is determined in step S201 that the start time of the transaction acceptance period has arrived, the settlement device 40 activates the customer terminal-compatible settlement mode. At this time, if an operation mode other than the customer terminal-compatible settlement mode had been set up until that point, the settlement device 40 switches from the previous operation mode to the customer terminal-compatible settlement mode.

[0102] By executing the process shown in the figure, it is possible for a customer to carry out a transaction via a customer terminal even after the store has opened and the transaction acceptance period has not yet begun.

[0103] <Modification> Modifications of this embodiment will be described below. The modifications described below may be combined as appropriate. [First Modification] In the shopping system of this embodiment, an assist monitor (monitoring device) may be provided in the store. The management device 10 may also be used as the assist monitor. The assist monitor is capable of displaying various situations in the store. The store clerk in charge can grasp the situation in the store by using the assist monitor.

[0104] In addition, the assist monitor of this embodiment may be capable of displaying a settlement device status screen that indicates the state (status) of the settlement device 40. The settlement device status screen can be displayed at any time, for example, during business hours, in response to an operation by a store clerk in charge of the assist monitor. FIG. 13(A) shows an example of a settlement device status screen. In the settlement device status screen, a settlement device button BT1 corresponding to each settlement device 40 installed in the store is arranged. In the figure, an example is shown in which four settlement device buttons BT1-1, BT1-2, BT1-3, and BT1-4 are arranged as the settlement device button BT1, in accordance with the fact that four settlement devices 40 are installed in the store.

[0105] In addition, the settlement device status screen includes a mode instruction area AR1 and a usage status instruction area AR2. The mode indication area AR1 indicates the operating mode (customer terminal compatible settlement mode, or any of the first to third accounting modes) set for each settlement device 40 corresponding to the settlement device button BT1. The figure shows an example in which the customer terminal compatible settlement mode is set for three settlement devices 40 corresponding to the settlement device buttons BT1-1 to BT1-3, and the first accounting mode is set for one settlement device 40 corresponding to the settlement device button BT1-4.

[0106] The usage status indication area AR2 indicates the usage status of each settlement device 40 corresponding to the settlement device button BT1. In the figure, examples of the usage status are shown in which the settlement device 40 corresponding to the settlement device button BT1-1 is "in use", the settlement device 40 corresponding to the settlement device button BT1-2 is "unused", the settlement device 40 corresponding to the settlement device button BT1-3 is "called", and the settlement device 40 corresponding to the settlement device button BT1-4 is "in use". "In use" indicates that in the customer terminal-compatible payment mode, the payment process is being carried out in response to the customer's operation, and in the first payment mode, it indicates that either the product registration process or the payment process is being carried out. "Unused" indicates that no transaction-related processes such as product registration or payment have been carried out and the transaction is on standby. "Call" indicates that the device is in a state where a store clerk is being called. In the case of the customer terminal-compatible payment mode, the store clerk is called when the registered items include a reserved item. In the case of an operating mode in which the store clerk does not interact with customers, such as the customer terminal-compatible payment mode or the third accounting mode, the store clerk is called when the registered items include an item that requires age verification, such as tobacco or alcohol. When a store clerk confirms by the assist monitor that a payment device 40 is in a state where a store clerk is being called, for example, he or she or another store clerk can respond by having a store clerk go to the payment device 40 in the state where a store clerk is being called.

[0107] In addition, if a malfunction or maintenance is occurring, that fact may be indicated in either the mode indication area AR1 or the usage status indication area AR2.

[0108] Additionally, the settlement device status screen has an in-progress transaction status button BT2. The in-progress transaction status button BT2 is a button operated to instruct the display of an in-progress transaction status screen that shows the current status of an in-progress transaction. When the store clerk wants to know the status of an in-progress transaction, he or she operates the in-progress transaction status button BT2. In response to the operation of the in-progress transaction status button BT2, the in-progress transaction status screen is displayed on the assist monitor. In response to the operation of the mid-transaction status button BT2, the assist monitor sends a mid-transaction screen request to the transaction management device 60. In response to the mid-transaction screen request, the transaction management device 60 searches for cart information stored in the memory unit 602 that is in a mid-transaction state at the store to which the requesting assist monitor corresponds, and the transaction management device 60 uses the searched cart information to generate a mid-transaction screen that shows information for each mid-transaction (mid-transaction information), and sends the generated mid-transaction screen to the assist monitor that sent the mid-transaction screen request. The assist monitor displays the sent mid-transaction screen.

[0109] Fig. 13(B) shows an example of the mid-transaction status screen. The mid-transaction status screen in the figure shows mid-transaction information for each current mid-transaction. The mid-transaction information for one mid-transaction includes the serial number, transaction start date and time, number of registered products, number of reserved products, cumulative amount, and status information. The serial number is a number serving as identification information for identifying the corresponding mid-transaction, and is obtained based on the cart identification information in the cart information. The transaction start date and time is the date and time when the corresponding mid-transaction started, and is obtained based on the transaction start date and time in the cart information. The number of registered products indicates the number of products that have been registered up to the present time under the corresponding mid-transaction. The number of registered products is obtained based on the registered product information in the cart information. The number of registered products may include reserved products. The number of reserved items indicates the number of reserved items among the registered items, and is also obtained based on the registered item information in the cart information. The cumulative amount is the amount accumulated according to the prices of the products registered up to the present time under the corresponding mid-way transaction. The cumulative amount is calculated based on the number of products, the price, etc. indicated in the product registration information in the cart information. The status indicates the current state of the pending transaction. In the figure, the status of the pending transaction with serial number "00175" is "Settling". The "Settling" status indicates that the pending transaction is being settled by a customer using settlement device 40. The status of the pending transaction with serial number “00176” is “Product registration in progress.” The “Product registration in progress” status indicates that the product registration by the customer terminal device 50 has not yet been completed for the corresponding pending transaction. The status of the pending transaction with serial number "00177" is "product registration in progress" with the number of registered products set to "0". In correspondence with Fig. 8, this indicates that cart information has been created in step S2, but product data has not yet been updated even once in step S7. In this embodiment, even if the number of registered products is "0", as long as cart information has been generated, it is treated as "product registration in progress".

[0110] A "Back" button BT4 is provided on the mid-transaction status screen. When the "Back" button BT4 is operated, the assist monitor clears the mid-transaction status screen and returns to the state where the settlement device status screen is displayed.

[0111] In addition, in response to the operation of the mid-transaction status button BT2 arranged on the settlement device status screen of FIG. 13(A), instead of the mid-transaction status screen of FIG. 13(B), a mid-transaction status detail screen of the mode exemplified in FIG. 13(C) may be displayed. In addition to the mid-transaction status button BT2, a mid-transaction detail status button may be separately arranged on the settlement device status screen of FIG. 13(A). In this case, in response to the operation of the mid-transaction status button BT2, the mid-transaction status screen of FIG. 13(B) may be displayed, and in response to the operation of the mid-transaction detail status button, the mid-transaction status detail screen of FIG. 13(C) may be displayed.

[0112] 13(C), an in-progress transaction list area AR31 and an in-progress transaction detailed information area AR32 are arranged. In the in-progress transaction list area AR31, a list of currently existing in-progress transactions is displayed. In the mid-transaction list area AR31, the list items corresponding to each mid-transaction are arranged from top to bottom in order of, for example, the transaction start date and time. The order of the list items may be, other than the transaction start date and time, the order of the elapsed time from the transaction start time, the number of registered products, etc., and the order criteria may be changed by operation, etc. Each list item corresponding to one pending transaction shows the serial number, membership number, transaction start date and time, elapsed time, number of registered products, cumulative amount, etc., for the corresponding pending transaction. The serial number is a number serving as identification information for identifying the corresponding mid-transaction, and is obtained based on the cart identification information in the cart information. The transaction start date and time is the date and time when the corresponding mid-transaction started, and is obtained based on the transaction start date and time in the cart information. The elapsed time indicates the time from the start date and time of the transaction to the present. The number of registered products indicates the number of products that have been registered up to the present time under the corresponding mid-transaction. The number of registered products is obtained based on the registered product information in the cart information. The number of registered products may include reserved products. The cumulative amount is the amount accumulated according to the prices of the products registered up to the present time under the corresponding mid-way transaction. The cumulative amount is calculated based on the number of products, the price, etc. indicated in the product registration information in the cart information. In addition, the list items may also show the number of reserved items, as well as an icon (for example, an icon showing the words "guaranteed" or "years") to inform the store clerk that there are reserved items or items that require age verification, or other items that require the intervention of a store clerk to purchase. The number of reserved items indicates the number of reserved items among the registered items. The number of reserved items is also obtained based on the registered item information in the cart information. The various icons displayed in the list items may be not only pictorial symbols, but also pictorial symbols that include letters or symbols. The list items also indicate the type (terminal type) of the customer terminal device 50 used by the customer for the transaction. As for the terminal type, "cart" indicates that the terminal device used by the customer is a tablet terminal held in a cart. "Customer terminal" indicates that the terminal used by the customer is a mobile terminal or tablet terminal owned by the customer. "Store terminal" indicates that the terminal used by the customer is a terminal device rented out by the store.

[0113] The mid-transaction detail information area AR32 shows detailed information about the mid-transaction corresponding to the list item selected from the mid-transaction list area AR31. The mid-transaction detail information area AR32 shows the serial number, member number, and transaction start date and time corresponding to the selected mid-transaction, and also shows a list of information about products registered up to now under the selected mid-transaction. The list item corresponding to one registered product shows the product identifier, product name, price, etc. Also, if a discount was applied in response to the registration of the product, information on the discount result is also shown. Additionally, among the product list items, the display mode of items that correspond to reserved products or age verification products is changed so that they can be distinguished from other products.

[0114] Returning to Fig. 13(A) for explanation, a "Close" button BT3 is arranged on the settlement device status screen. The "Close" button BT3 is a button that is operated when a store clerk manually executes a closing process for the settlement device 40. For example, when manually executing a closing process for the settlement device 40 corresponding to the settlement device button BT1-2, the store clerk operates the settlement device button BT1-2 to designate the settlement device 40 associated with the settlement device button BT1-2 as the target for the closing process. The store clerk then operates the close button BT3. In response to such an operation, the assist monitor transmits a closing process request to the settlement device 40 associated with the settlement device button BT1-2, for example. In response to the transmitted closing process request, the settlement device 40 associated with the settlement device button BT1-2 terminates the customer terminal compatible settlement mode and executes the closing process. In the above example, a single close button BT3 is provided for use with multiple settlement device buttons BT1. However, for example, a corresponding close button may be provided for each settlement device button BT1. It should be noted that the system may be configured so that a store clerk can manually execute the opening process for the settlement device 40 by operating the settlement device status screen.

[0115] Also, the clerk may be able to manually execute the closing process by operating the settlement device 40. The clerk goes to the settlement device 40 that is to execute the closing process and performs an operation to instruct the closing process. In response to the operation to instruct the closing process being performed, the settlement device 40 displays a closing process execution confirmation screen for confirming the execution of the closing process on the clerk's display unit 410 (or the customer's display unit 205). Note that the operation to instruct the closing process can be accepted when there is no pending transaction outside the accounting acceptance hours (for example, after the end of the accounting acceptance hours). Even when there is a pending transaction outside the accounting acceptance hours, the settlement device 40 is configured not to accept the operation to instruct the closing process so that the settlement corresponding to the pending transaction can be waited. Fig. 15 shows an example of the closing process execution confirmation screen. When the store clerk wants to execute the closing process, he / she operates the "Yes" button BT11. When the "Yes" button BT11 is operated, the settlement device 40 starts executing the closing process. When the "No" button BT12 is operated, the settlement device 40 does not execute the closing process and returns to the display of the previous screen, for example.

[0116] [Second modified example] In this embodiment, even if the accounting acceptance time period has ended, an in-progress transaction in which product registration was started before the end of the accounting acceptance time period can be settled by the settlement device 40 in the customer terminal settlement mode. However, once the accounting acceptance time period has ended, it is not possible to start product registration using customer terminal settlement. Specifically, even if a customer operates the shopping application to cause the customer terminal device 50 to send a transaction start request after the transaction reception hours have passed, the transaction management device 60 will notify the customer terminal device 50 that the transaction cannot be started without executing the process to generate a cart in response to the sent transaction start request.

[0117] However, a customer who is about to start a transaction through customer terminal-based accounting is not necessarily aware of the closing time even when the closing time of the accounting acceptance period is approaching. Furthermore, even if a customer is aware that the closing time is approaching, he or she may not have an accurate grasp of the time remaining until the closing time. For example, if such a customer performs an operation on customer terminal device 50 to start a transaction through customer terminal-based accounting after the closing time of the accounting acceptance period, he or she may have the impression that the transaction has been unexpectedly rejected.

[0118] Therefore, in this modified example, for the convenience of such customers, a notification regarding the end of the transaction acceptance period is made on the customer terminal device 50. In this modified example, an example is given of a case in which product registration is started in response to an operation to instruct the start of product registration in customer terminal-compatible transactions (product registration start instruction operation) being performed on a start-up screen that is displayed in response to the launch of a shopping application.

[0119] Fig. 14(A) shows an example of a start-up screen displayed on display unit 504 of customer terminal device 50. In store name area AR10 of the start-up screen in the figure, a store name based on the store identification information acquired by customer terminal device 50 in step S1 of Fig. 8 is displayed. In other words, the store name displayed in store name area AR10 indicates the store where the customer is currently staying. The start-up screen also includes a transaction reception time zone designation area AR20. The transaction reception time zone designation area AR20 shows the transaction reception time zones determined for the store whose store name is displayed in the store name area AR10. The transaction reception time zone designation area AR20 in the figure shows the start and end times of the transaction reception time zones. For example, if the store identification information includes transaction reception time zones, the transaction reception time zone designation area AR20 may be displayed based on the transaction reception time zones included in the acquired store identification information. Alternatively, if the application data for the installed shopping application includes transaction reception time zones for each store, the transaction reception time zone designation area AR20 may be displayed based on the transaction reception time zones included in the application data.

[0120] Also, on the start screen, a checkout start button BT10 is arranged. The checkout start button BT10 is a button operated to instruct the start of a customer terminal-compatible checkout for one transaction. In response to the operation of the checkout start button BT10, the display on display unit 504 transitions to the product registration initial screen (FIG. 9(A)), and the product registration is started under customer terminal-compatible checkout. The start-up screen in FIG. 11 is displayed when the time is a certain amount of time prior to the end of the transaction acceptance period.

[0121] Fig. 14(B) shows an example of the start-up screen that is displayed when the time period is from the end of the transaction acceptance period to a certain time before that (end time period). The start-up screen in this figure newly displays an end notice message MS1 that was not displayed on the start-up screen in Fig. 14(A). The end notice message MS1 is a message that notifies customers that the end of the accounting period is approaching. Specifically, the end notice message MS1 in the figure notifies customers of the time remaining from the current time until the end of the accounting period. The end notice message MS1 may simply have a message content that informs customers that the end of the accounting period is approaching, such as "The accounting period will end soon," but it is more useful for customers to be informed of the remaining time.

[0122] Fig. 14(C) shows an example of a start-up screen that is displayed when the end time of the transaction acceptance period has passed. In the start-up screen of this figure, an end message MS2 is displayed instead of the end notice message MS1 that was displayed in Fig. 14(B). The end message MS2 is a message that notifies the customer that the transaction acceptance period has ended. The completion message MS2 in the figure is displayed in place of the text "Start shopping" on the checkout start button BT10. This clearly shows that the checkout start button BT10 has changed from the operable state in Figures 4(A) and 4(B) to an inoperable state.

[0123] In addition, in the processing of Figure 11 described above, an example was given of a case in which no particular deadline is set for the time during which the settlement device 40 in the customer terminal-compatible settlement mode will accept settlement in response to an intermediate transaction in which product registration begins before the end of the accounting acceptance time period. However, depending on the operation of the store, a time limit (acceptance deadline) may be set for the time during which the settlement device 40 in the customer terminal compliant settlement mode accepts settlement in response to an unsettled transaction. Such an acceptance deadline may be, for example, a time corresponding to closing time, or a predetermined time between the end of the transaction acceptance period and closing time. When an acceptance deadline is set in this manner, a customer who is registering a product due to an unfinished transaction must complete product registration before the acceptance deadline and begin settlement at the settlement device 40 in customer terminal settlement mode. Therefore, in the customer terminal device 50, when the current time reaches a certain time before the acceptance deadline, a notification that the acceptance deadline is approaching may be given.

[0124] FIG. 14(D) shows an example of a product registration screen where a notification is given that the acceptance deadline is approaching. In a mid-transaction that has not yet been settled when a certain time has passed before the acceptance deadline, the product registration screen is displayed on the display unit 504 of the customer terminal device 50 because the product is being registered. Therefore, when a certain time has passed before the acceptance deadline, as shown in FIG. 14, an end notice message MS3 is displayed on the product registration screen to notify the customer that the acceptance deadline is approaching. Specifically, the end notice message MS3 in FIG. 14 notifies the customer of the remaining time from the current time to the acceptance deadline. The end notice message MS3 may be a message that simply informs the customer that the acceptance of the settlement device 40 in the customer terminal-compatible settlement mode is about to end, but it is more useful for the customer to be presented with a specific remaining time. The end notice message MS3 in the figure is displayed in a balloon from the "Proceed to Checkout" button BT20. The "Proceed to Checkout" button BT20 is a button that is operated to complete product registration and move to checkout. By displaying the end notice message MS3 as a balloon from the "Proceed to Checkout" button BT20, the customer can intuitively understand that the content of the end notice message MS3 is to inform the customer that the acceptance deadline is approaching. In addition to the end notice message MS3, the customer terminal device 50 may emit an alarm sound from a sound device or output a voice message when a predetermined time remains until the reception deadline. Alternatively, the customer terminal device 50 may issue an end notice by issuing an indicator or the like. This configuration also allows the customer to recognize that the reception deadline is approaching.

[0125] [Third Modification] If the settlement for the mid-transaction has not been started by the settlement device 40 in the customer terminal settlement mode even after the acceptance deadline has passed, the cart information may be sent as settlement information to the settlement device 40 in which the first or second accounting mode is set, for example, when product registration is completed. The settlement device 40 in which the first or second accounting mode is set executes the settlement process using the sent settlement information. In this way, when performing settlement with the settlement device 40 in which the first or second accounting mode is set, it is not necessary to register the product to be purchased again.

[0126] [Fourth Modification] In the example of the process procedure in Fig. 8, 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. In other words, in the example of the process procedure in Fig. 8, each time the customer terminal device 50 executes a product registration process in response to the reading of a 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 (step S5). 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 (steps S6 and S7). In contrast, customer terminal device 50 in this modified example is configured to store 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 a checkout instruction being issued, customer terminal device 50 is configured to transmit the product registration information including one or more product codes that it has stored up to that point to 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, customer terminal device 50 in this embodiment is configured to transmit the product registration information in bulk in response to a checkout instruction. In this way, when customer terminal device 50 transmits product registration information in bulk in response to a transaction instruction, the number of communications between customer terminal device 50 and transaction management device 60 can be reduced, which reduces the processing load and power consumption of customer terminal device 50. In addition, the amount of traffic between customer terminal device 50 and transaction management device 60 can also be reduced.

[0127] In this way, when sending product registration information in bulk in response to a transaction instruction, the customer terminal device 50 may first send a transaction start request to the transaction management device 60, for example, in response to step S1 of Fig. 8. This allows the transaction management device 60 to generate cart information for the corresponding transaction in response to the timing at which the customer starts the transaction, and to set the transaction in an incomplete state. The transaction management device 60 also sends cart identification information indicating the generated cart information to the customer terminal device 50. In this case, the customer terminal device 50 stores the read product code each time it is read without transmitting it. Then, in response to a checkout instruction operation, the customer terminal device 50 transmits product registration information indicating the product registration results up to that point to the transaction management device 60. The transaction management device 60 uses the transmitted product registration information to update the cart information. In other words, in this modified example, in response to a bulk transmission of product registration information in one transaction, the transaction management device 60 executes the processing of steps S6 and S7 once to generate cart information reflecting all registered products. After this, customer terminal device 50, settlement device 40, and transaction management device 60 may execute the same processes as those from step S11 onward in FIG.

[0128] In addition, in order to generate cart information for the corresponding transaction depending on the timing at which the customer starts a transaction and to set the transaction status to an incomplete state, for example, when the customer enters the store, the customer may perform an operation to have the customer terminal device 50 read entry verification code information provided at the entrance of the store. The entry verification code information includes information that instructs the shopping application to send a transaction start request to the transaction management device 60. In response to reading the entry verification code information, the customer terminal device 50 sends a transaction start request to the transaction management device 60. In addition, the customer terminal device 50 may measure its own location, and when the measured location falls within the range corresponding to the store, transmit a request to start a transaction to the transaction management device 60.

[0129] [Fifth Modification] The accounting acceptance hours and acceptance deadlines on a business day may be changed, for example, on a day-of-the-week, month-by-month, year-by-year basis, etc.

[0130] <Overview 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] For example, in consideration of the widespread use of self-registration systems in which customers use terminals to register products, it is preferable to provide convenience to customers who use the self-registration system. The present invention has been made in view of the above circumstances, and has an object to provide convenience to customers in a self-registration system in which customers register products using a terminal. [Means for solving the problem] (1) As described above, one aspect of this embodiment is a product sales data processing system including a customer terminal device (50) that registers products, a transaction management device (60) that stores product registration information reflecting the product registration results by the customer terminal device, and a settlement device (40) that executes customer terminal-compatible settlement corresponding to the products registered by the customer terminal device based on the product registration information, and the product sales data processing system is equipped with a transaction determination means that determines whether or not there is an ongoing transaction while product registration is being executed by the customer terminal device at a specified time, and an operation control means that controls the operation of the settlement device that executes customer terminal-compatible settlement corresponding to the products registered by the customer terminal device based on the determination result of the transaction determination means.

[0131] According to the above configuration, under customer terminal-compatible accounting, if an ongoing transaction occurs within a specified time, the settlement device 40 can be left operating in the customer terminal-compatible settlement mode. As a result, even if the operation is such that payment cannot be accepted at a specific time for customer terminal-based accounting, payment can be accepted by the payment device 40 in the customer terminal-based payment mode. This provides convenience to customers in a self-registration system in which customers register products using the customer terminal device 50.

[0132] (2) One aspect of this embodiment is the product sales data processing system described in (1), wherein the specified time is a time after an operational end time (e.g., the end time of a period during which payments are accepted) that terminates the acceptance of payments at the customer terminal, and when the transaction determination means determines that there is an ongoing transaction, the operation control means maintains the settlement device in a state in which settlement at the customer terminal cannot be performed, rather than transitioning the settlement device to a state in which settlement at the customer terminal cannot be performed.

[0133] According to the above configuration, even if the end time of the transaction acceptance period has passed, the settlement of an ongoing transaction can be accepted by the settlement device 40 in the customer terminal compatible settlement mode.

[0134] (3) One aspect of this embodiment is a product sales data processing system as described in (1) or (2), which includes an operation display control means that, when the transaction determination means determines that there is no pending transaction, causes the settlement device to display an operation means for transitioning the customer terminal-compatible settlement to a state in which it cannot be executed.

[0135] According to the above configuration, if there is no pending transaction outside of the transaction acceptance hours, the store clerk can, at his / her discretion, operate the settlement device 40 to execute the closing process.

[0136] (4) One aspect of this embodiment is a product sales data processing system described in any one of (1) to (3), wherein the specified time is a time before a start time established for store operations as the start time for accepting customer terminal-based settlement, and when the transaction determination means determines that there is an ongoing transaction, the operation control means controls the settlement device to change from a state in which customer terminal-based settlement cannot be performed to a state in which customer terminal-based settlement can be performed.

[0137] According to the above configuration, even if a transaction is in progress before the start time of the transaction acceptance period, the settlement device 40 in the customer terminal compatible settlement mode can accept the settlement.

[0138] (5) One aspect of this embodiment is a product sales data processing system according to any one of (1) to (4), wherein the operation control means controls at least a portion of a plurality of settlement devices.

[0139] According to the above configuration, in addition to the customer terminal-based payment service, a store can also provide other types of payment in parallel, such as payments handled by a store clerk or customers registering products and paying for them themselves at a payment device.

[0140] (6) One aspect of this embodiment is a product sales data processing system as described in any one of (1) to (5), comprising a display control means for displaying, on the customer terminal device, time-period-related information relating to a time period that has been operationally determined as a time period during which the customer terminal-based settlement is accepted.

[0141] According to the above configuration, information regarding transaction acceptance hours established by the store is displayed on the customer terminal device 50, allowing the customer to understand the transaction acceptance hours.

[0142] (7) One aspect of this embodiment is the product sales data processing system described in (6), wherein the display control means displays information relating to the time from the start to the end of the time period as the time period related information.

[0143] According to the above configuration, by looking at the information displayed on the customer terminal device 50, the customer can specifically know when the transaction acceptance period starts and ends.

[0144] (8) One aspect of this embodiment is a product sales data processing system as described in (6) or (7), wherein the display control means displays information regarding the relationship between the time period and the current time as the time period related information.

[0145] (9) One aspect of this embodiment is the product sales data processing system described in (8), in which the display control means displays, as the time period related information, the remaining time until the end of the time period at the current time.

[0146] According to the above configurations (8) and (9), a customer can see the information displayed on the customer terminal device 50 and understand, for example, the remaining time until the end of the transaction acceptance period. The display control means can also cause the customer terminal device 50 to display the time remaining until the start of the transaction acceptance period before the transaction acceptance period begins.

[0147] (10) One aspect of this embodiment is a product sales data processing system as described in (8) or (9), wherein the display control means displays, as the time zone related information, a notification of the end of the time zone in response to the current time having passed the time zone.

[0148] According to the above configuration, a customer can see the information displayed on the customer terminal device 50 and understand that the transaction acceptance period has ended.

[0149] 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]

[0150] 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 including a customer terminal device in which a product taken from a product shelf by the customer is registered, a transaction management device that stores registered product information reflecting the product registration results by the customer terminal device, and a settlement device that executes customer terminal-compatible settlement corresponding to the product registered by the customer terminal device based on the registered product information, A transaction determination means for determining whether or not there is a transaction in progress during product registration by a customer terminal device; an operation control means for controlling the operation of a settlement device which executes settlement of the products registered by the customer terminal device; When the transaction determination means determines that there are pending transactions when transitioning the settlement devices to a state in which settlement cannot be executed, the operation control means maintains the settlement devices in a state in which settlement can be executed without transitioning the settlement devices to a state in which settlement cannot be executed among the multiple settlement devices according to the number of pending transactions determined to exist. Product sales data processing system.

2. A computer in a product sales data processing system including a customer terminal device in which a product taken from a product shelf by the customer is registered, a transaction management device that stores registered product information reflecting the product registration results by the customer terminal device, and a settlement device that executes customer terminal corresponding settlement corresponding to the product registered by the customer terminal device based on the registered product information, A transaction determination means for determining whether or not there is a transaction in progress during the product registration by the customer terminal device; An operation control means for controlling the operation of a settlement device that executes settlement of products registered by a customer terminal device, and when the transaction determination means determines that there is an incomplete transaction when transitioning the settlement device to a state in which settlement cannot be executed, the operation control means maintains a state in which settlement can be executed for the settlement device corresponding to the number of incomplete transactions determined to exist, among a plurality of settlement devices, without transitioning the settlement to a state in which settlement cannot be executed. A program to function as a

Images