JP7403876B2 - Product sales data processing system, registration device, payment device, and program - Google Patents

Description

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

A registration device that executes product registration processing in response to product registration operations performed by a store clerk, and a payment device that executes payment processing in accordance with product registration processing performed by the registration device in response to customer operations, are provided separately. A POS system (product sales data processing system) is known (for example, see Patent Document 1).
For example, in the case of a POS register configured to perform product registration processing and payment processing in one machine, store staff will perform operations related to product registration and payment for each customer. .
On the other hand, in a POS register in which the registration device and payment device are separated as in Patent Document 1, store staff perform operations corresponding to payment for each customer in the checkout flow from product registration to payment. There is no need to do this, and only the product registration operation can be performed, which improves the efficiency of customer handling.

JP 2017-50005 Publication

In the above-mentioned Patent Document 1, the registration device selects the payment device to execute the payment process according to the availability of the payment device according to the priority set for the payment device, thereby further improving the efficiency of customer handling. We are trying to ensure that However, in order to improve the efficiency of customer handling at a POS register that includes a registration device and a payment device, it is preferable that the structure of Patent Document 1 is not limited to, and further improvements are made.

The present invention has been made in view of the above circumstances, and an object of the present invention is to improve the efficiency of customer handling in a product sales data processing system that includes a registration device and a payment device.

One aspect of the present invention for solving the above-mentioned problems includes a registration device in which products are registered in response to an operation by a store clerk, and a payment process based on payment information that reflects the product registration result by the registration device. A product sales data processing system comprising a plurality of payment adjustment devices that perform payments in response to customer operations, and product registration means that registers products corresponding to one transaction in response to store clerk operations performed on the registration devices. and a payment-related operation receiving means capable of accepting the start of a payment-related operation corresponding to one transaction performed by a customer on the payment device at a stage before the payment information is acquired, and the product registration means. The present invention is a product sales data processing system that includes a transaction control unit that associates a transaction corresponding to a product registration to be performed with a transaction corresponding to a payment-related operation received by the payment-related operation receiving unit.

Further, one aspect of the present invention provides a registration device in which products are registered in response to operations by a store clerk, and a payment process based on payment information that reflects product registration results by the registration device in response to operations by a customer. A registration device in a product sales data processing system comprising a plurality of checkout devices, the product registration device registering a product corresponding to one transaction in response to an operation by a store clerk; The payment information is acquired by the payment device or the registration device of a transaction corresponding to registration and a transaction corresponding to a payment-related operation performed by a customer on the payment device or the registration device in response to one transaction. This is a registration device equipped with a transaction control means that performs correspondence at a stage before the transactions are made.

Further, one aspect of the present invention provides a registration device in which products are registered in response to operations by a store clerk, and a payment process based on payment information that reflects product registration results by the registration device in response to operations by a customer. A settlement device in a product sales data processing system comprising a plurality of settlement devices that perform settlement operations, the settlement device starting a settlement-related operation corresponding to one transaction performed by a customer on the settlement device before the settlement information is acquired. transaction control that associates a payment-related operation accepting means that can accept from the stage of , a transaction corresponding to the registration of a product performed by the registration device, and a transaction corresponding to the payment-related operation received by the payment-related operation accepting means; It is a payment device comprising means.

Further, one aspect of the present invention provides a registration device in which products are registered in response to operations by a store clerk, and a payment process based on payment information that reflects product registration results by the registration device in response to operations by a customer. A computer installed in a product sales data processing system comprising a plurality of payment settlement devices is used as a product registration means for registering products corresponding to one transaction in accordance with operations performed by a store clerk on the registration device; A settlement-related operation reception means that can accept the start of a settlement-related operation corresponding to one transaction performed on the settlement device at a stage before the settlement information is acquired, and a product registration performed by the product registration means. This is a program for functioning as a transaction control means that associates a corresponding transaction with a transaction corresponding to a payment-related operation received by the payment-related operation receiving means.

Further, one aspect of the present invention provides a registration device in which products are registered in response to operations by a store clerk, and a payment process based on payment information that reflects product registration results by the registration device in response to operations by a customer. A computer serving as a registration device in a product sales data processing system comprising a plurality of payment settlement devices is used as a product registration means for registering products corresponding to one transaction according to operations of a store clerk, and product registration performed by the product registration means. The payment information is acquired by the payment device or the registration device of a transaction corresponding to registration and a transaction corresponding to a payment-related operation performed by a customer on the payment device or the registration device in response to one transaction. This is a program that functions as a transaction control means that associates transactions even before they are processed.

Further, one aspect of the present invention provides a registration device in which products are registered in response to operations by a store clerk, and a payment process based on payment information that reflects product registration results by the registration device in response to operations by a customer. A computer serving as a payment device in a product sales data processing system comprising a plurality of payment payment devices is used to acquire the payment information so that the computer can initiate a payment related operation corresponding to one transaction performed by a customer on the payment device. A payment-related operation reception means that can be accepted from a previous stage; transaction control that associates a transaction corresponding to the registration of a product performed by the registration device with a transaction corresponding to the payment-related operation received by the payment-related operation reception means; This is a program to function as a means.

According to the present invention, an effect can be obtained in that the efficiency of handling customers can be improved in a product sales data processing system that includes a registration device and a payment device.

1 is a diagram showing a configuration example of a POS system in a first embodiment. It is a figure showing an example of appearance of a registration device and a settlement device in a 1st embodiment. It is a diagram showing an example of the configuration of a registration device in the first embodiment. It is a figure showing the example of composition of the payment device in a 1st embodiment. It is a figure showing the example of the mode of payment device state display in a 1st embodiment. It is a figure showing an example of the mode of the payment screen in a 1st embodiment. It is a figure which shows the other aspect example of the payment screen in 1st Embodiment. It is a flow chart which shows the example of a processing procedure which a registration device and a payment device in a 1st embodiment perform. It is a figure which shows the example of the content of the point provision management table in 2nd Embodiment.

Embodiments of the present invention will be described below with reference to the drawings.
<First embodiment>
FIG. 1 shows a configuration example of a POS system 1 (an example of a product sales data processing system) according to the present embodiment. The POS system 1 shown in the figure includes a management device 10, two registration devices 20-1 and 20-2, and three payment devices 30-1, 30-2, and 30-3.
In the following description, unless there is a particular distinction between the registration devices 20-1 and 20-2, they will be referred to as the registration device 20. Further, if there is no particular distinction between the payment devices 30-1, 30-2, and 30-3, they will be referred to as payment devices 30.
The management device 10, the registration device 20, and the payment device 30 are interconnected via a wired or wireless LAN (Local Area Network) 11.

Note that the configuration of the POS system 1 shown in the figure is an example. For example, in the POS system 1, the number of registration devices 20 and payment devices 30 installed is not particularly limited, and may be one or more each. Furthermore, the POS system 1 of this embodiment may have a configuration that does not include the management device 10.
Note that if the configuration of the POS system 1 does not include the management device 10, the management device It may also serve as a function.

The management device 10 is an information processing device that manages the POS system 1, and manages the registration device 20, payment device 30, etc. in the POS system 1, and manages various information such as a product master. The management device 10 appropriately transmits the latest product master to the registration device 20 and each payment device 30. The product master is a file that stores product information such as product identification information (for example, JAN code), product name (product name, item name), sales price, and discount information for each product.
The management device 10 acquires a product master reflecting the latest product information from an external source (for example, a server at the headquarters, a removable storage medium), and transmits it to the registration device 20 and each payment device 30 as appropriate.

The registration device 20 executes a product registration process for registering products to be purchased. The operation for registering a product (product registration operation) is performed, for example, by using a scanner to read a barcode attached to the product, or by operating a preset button displayed on a product registration screen. Through such a product registration operation, for example, product identification information is input to the registration device 20, and the registration device 20 acquires product information corresponding to the input product identification information.
Further, the registration device 20 generates and stores information (hereinafter referred to as settlement information) used for settlement of registered products corresponding to each transaction.

The payment information includes transaction identification information that identifies the corresponding transaction, payment information identification information that identifies the payment information, registration date and time, product identification information of each registered product, product name of each registered product, sales price, It may include discount information, a transaction number (purchase number) indicating the number of items to be purchased, and a total amount (total amount) of items to be purchased. Further, the payment information may further include registration device identification information for identifying the registration device 20 that generated the payment information (that is, the registration device 20 that registered the product related to the payment information). In this way, the settlement information has content that reflects the product registration processing result corresponding to one transaction.

The payment information is used for payment processing in the payment device 30. The settlement process is a process of paying for registered products by selectively using cash, electronic money, a credit card, etc.

In this embodiment, a plurality of payment devices 30 are installed, and any one of the payment devices 30 executes payment processing using the payment information generated by the registration device 20. Examples of modes for specifying the settlement device 30 to perform the settlement process from among the plurality of settlement devices 30 include the following first specification mode and second specification mode.

The first designation mode is a mode in which the store clerk specifies, using the registration device 20, the payment device 30 on which the payment processing is to be executed.
That is, by performing an operation for specifying the payment device 30 on the registration device 20, the store clerk designates the payment device 30 to execute the payment process from among the plurality of payment devices 30.
Note that the registration device 20 is configured to display operating information indicating the operating status of each payment device 30, and when the clerk specifies the payment device 30 in the registration device 20, the clerk confirms the operation status of each payment device 30. It may be possible to do so.

When the clerk specifies the payment device 30, the payment information generated in the registration device 20 is transmitted to the designated payment device 30 via the LAN 11. That is, when the payment device 30 is specified following the product registration process, the registration device 20 transmits payment information that reflects the result of the product registration process to the specified payment device 30.
In the present embodiment, the registration device 20 directly transmits the payment information to the payment device 30, but it may also transmit the payment information to the payment device 30 via the management device 10.

In addition, in the second specification mode, the registration device 20 issues a medium for payment processing (accounting ticket (registered trademark)), and the customer reads the bill handed over by the clerk into one payment device 30. This is the mode in which it is possible to
That is, the customer specifies which payment device 30 is to perform the payment processing from among the plurality of payment devices 30 by causing the payment device 30 to read the bill handed to him by the clerk.
The registration device identification information indicating the issuer's registration device 20 and payment information are printed on the payment ticket in the form of either a barcode (one-dimensional code) or a two-dimensional code. . When the payment device 30 reads the code on the bill, it acquires payment information indicated by the read code.

The payment device 30 executes payment processing according to a customer's operation. Further, when the payment processing is completed, the payment device 30 notifies the registration device 20 of the completion of the payment processing.

Next, configuration examples of the registration device 20 and the payment device 30 will be described with reference to FIGS. 2 to 4.
FIG. 2 is a perspective view showing an example of the appearance of the registration device 20 and the payment device 30. FIG. 3 is a block diagram showing a configuration example of the registration device 20. As shown in FIG. FIG. 4 is a block diagram showing a configuration example of the payment device 30.

As shown in FIG. 3, the registration device 20 includes a CPU (Central Processing Unit) 201, a storage section 202, a RAM (Random Access Memory) 203, a scanner section 204, a clerk display section 205, and a customer display section. It includes a section 205a, an operation section 206, a communication section 207, a buzzer 208, a printing section 209, and a card reader 210. These can communicate with each other via a bus.

The CPU 201 is a central processing unit, and controls the operation of the registration device 20 by reading and executing a program stored in the storage unit 202.
The storage unit 202 is an auxiliary storage device for the CPU 201, and stores various information used by the CPU 201, including programs.

The RAM 203 is the main storage device of the CPU 201 and stores various information. For example, the RAM 203 stores a product master acquired from the management device 10, payment information generated after product registration processing, and the like.
The scanner unit 204 optically reads a barcode (product code) attached to a product.

The store clerk display section 205 is a touch panel (for example, a liquid crystal touch panel), and displays various information for the store clerk.
For example, the store clerk display section 205 displays a product registration screen on which preset buttons associated with product information (product code, etc.) are arranged.

The customer display section 205a displays various information for customers. For example, the customer display section 205a displays the price of the registered product. The customer display section 205a may be a touch panel (for example, a liquid crystal touch panel).

The operation unit 206 includes various operation buttons (such as a subtotal key, a current total key, a numeric key, a correction key, and a preset key) for operating the registration device 20. For example, when an operation button (preset key) is operated, the operation unit 206 receives an operation input regarding product information (product code, etc.) that is registered in advance in the preset key.

The communication unit 207 communicates with other devices via the LAN 11.
The buzzer 208 generates a buzzer sound when a store clerk needs to confirm an operation.
The printing unit 209 prints and issues media as necessary. For example, the printing unit 209 can print and issue a bill.

The card reader 210 is a device that reads information from, for example, an RFID (Radio Frequency Identifier) tag in the form of an IC (Integra Circuit) card.

In FIG. 2, an example of the appearance of the registration device 20 including a scanner section 204, a store clerk display section 205, an operation section 206, a printing section 209, and a card reader 210 is shown.

As shown in FIG. 4, the payment device 30 includes a CPU 301, a storage section 302, a RAM 303, a scanner section 304, a display section 305, an operation section 306, a communication section 307, a buzzer 308, and a printing section 309. , a payment section 310 , a sign pole 311 , a human sensor 312 , and a card reader 313 . These can communicate with each other via a bus.

The CPU 301 is a central processing unit, and controls the operation of the payment device 30 by reading and executing a program stored in the storage unit 302.
The storage unit 302 is an auxiliary storage device for the CPU 301 and stores various information used by the CPU 301 including programs.

The RAM 303 is the main storage device of the CPU 301 and stores various information. For example, the RAM 303 stores the product master acquired from the management device 10 and settlement processing information that reflects the results of executing the settlement processing based on the settlement information obtained from the registration device 20.
The scanner unit 304 optically reads, for example, a code (barcode or two-dimensional code) printed on a bill or a code (membership code) attached to a membership card or the like.

The display unit 305 is a touch panel (for example, a liquid crystal touch panel) and displays various information. For example, the display unit 305 displays a payment screen on which the total amount and the like are displayed.

The operation unit 306 includes various operation buttons (correction key, preset key, etc.) for operating the payment device 30. For example, the operation unit 306 accepts correction of the operation input by operating an operation button (correction key).

The communication unit 307 communicates with other devices via the LAN 11.
When an error or the like occurs, the buzzer 308 generates a buzzer sound to notify the error.
The printing unit 309 prints and issues media. For example, the printing unit 309 prints and issues a paid receipt for the customer to take home when the payment processing (that is, the payment of the purchase price of the product) is completed.

The payment unit 310 performs processing related to payment (settlement). In this embodiment, the type of payment that the payment unit 310 can handle is at least one of the following: payment by cash, payment by using a credit card, and payment by using electronic money. Listed below.
In order to support payment by cash, the payment unit 310 includes a change machine. The change machine includes a bill slot for inserting and discharging banknotes, a coin slot for inserting coins, and a change outlet for discharging change. The payment unit 310 executes a payment using cash using a change machine, and outputs the result of the payment (for example, information indicating whether the payment has been completed) to the CPU 301 via the bus.
Further, when dealing with payment using a credit card, the payment unit 310 includes a credit card reader and performs payment processing using information read by the credit card reader.
Further, in the case of supporting payment using electronic money, the payment unit 310 includes an electronic money reader and performs payment processing using information read by the electronic money reader.

The sign pole 311 has indicator lights of multiple colors, and by lighting or blinking those indicator lights, it can notify information indicating that the payment device 30 is the device designated by the store clerk, and can be operated. To announce something.
The human sensor 312 is a sensor that detects the presence of a person (customer) within a predetermined range in front of the payment device 30 .
The detection output of the human sensor 312 may be used to detect whether or not a person has approached the aircraft, for example, when the payment device 30 automatically displays the payment screen in response to a person approaching the aircraft. Used for judgment. However, the payment device 30 may display the payment screen in response to, for example, receiving payment information or reading a barcode printed on a bill. Sensor 312 may be omitted.

The card reader 313 is a device that reads information from, for example, an RFID tag in the form of an IC card.

FIG. 2 shows an external configuration of the payment device 30 including a scanner section 304, a display section 305, an operation section 306, a printing section 309, a payment section 310, a sign pole 311, a card reader 313, and the like.

The POS system 1 of this embodiment can be operated according to either the first example or the second example below as an accounting procedure from product registration to settlement according to one transaction.
First, a first example of the accounting procedure in this embodiment will be described.
A customer who intends to pay the bill goes to the registration device 20 with his or her purchased products and places the purchased products on a table on which the registration device 20 is installed. A store clerk operating the registration device 20 sequentially registers the purchased products placed on the table for each product type. In response to the registration operation, the registration device 20 executes product registration processing corresponding to one transaction. While the product is being registered in this way, the customer is waiting in front of the registration device 20 for the product registration to be completed.
When the registration of all the products purchased by the customer is completed, the clerk performs a subtotal operation. According to the subtotal operation, the product registration process corresponding to one transaction is completed.

In the clerk display section 205 of the registration device 20 of the present embodiment, an operation is performed to specify a payment device 30 from among payment devices 30-1 to 30-3 to perform payment processing according to one transaction. A designated button is placed. In the case of this embodiment, three payment device designation buttons may be arranged, for example, corresponding to each of the payment devices 30-1 to 30-3.
Among the payment devices 30-1 to 30-3, the clerk determines, for example, a waiting device that is not currently executing payment processing as the payment device 30 to be caused to perform payment processing in accordance with the current transaction, The payment device designation button corresponding to the determined payment device 30 is operated. In response to the operation of the payment device designation button, the registration device 20 sends payment instruction information including payment information that reflects the registration result of the product performed in response to the current transaction to the operated payment device designation button. It is transmitted to the corresponding payment device 30.
The payment instruction information is information that instructs the payment device 30 to execute payment processing. The payment information included in the payment instruction information includes, for example, information on the total amount to be paid by the customer. Further, the payment information may include information such as a breakdown of the registered products and the unit price and price of each product.
Further, the clerk who operated the payment device designation button tells the customer, for example orally, to make the payment using the payment device 30 corresponding to the payment device designation button that he or she operated.

The customer goes to the payment device 30 that the clerk informed him about. At the stage when the customer goes to the payment device 30, the payment device 30 has received the payment instruction information transmitted from the registration device 20, and starts payment processing using the payment information included in the received payment instruction information. Waiting for availability.
When the customer goes to the payment device 30, he or she performs an operation corresponding to the start of payment processing. The operation corresponding to the start of the payment processing is, for example, an operation on a payment start button displayed on the display unit 305 that instructs to start payment. Alternatively, the operation corresponding to the start of the settlement process may be, for example, in the case of payment in cash, an operation of inserting money such as banknotes and coins as a deposit into the settlement unit 310. Alternatively, the operation in response to the start of the payment process may be, for example, an operation to read a membership card.

The payment device 30 executes payment processing in accordance with operations related to the payment started as described above. For example, in the case of payment in cash, the settlement device 30 waits until the total amount of money inserted as a deposit (inserted amount) is equal to or greater than the payment amount (total amount). When the settlement device 30 detects that the input amount is equal to or greater than the payment amount, the settlement device 30 finishes accepting the operation of inserting money as a deposit, and calculates change. When a significant amount of change is calculated, the payment device 30 causes the payment unit 310 to discharge money corresponding to the calculated amount of change. Further, the payment device 30 causes the printing unit 309 to issue a receipt on which the result of the current payment processing is reflected. The customer receives the change discharged from the payment device 30 and the issued receipt.
In this way, the POS system 1 of this embodiment can perform accounting according to the first example of the accounting procedure.

Next, a second example of a checkout procedure that can be performed in the POS system 1 of this embodiment will be described.
A customer places his or her purchased product on a table on which a registration device 20 is installed and requests a store clerk to register the product. The store clerk starts registering the purchased product and also informs the customer that he or she may go to the payment device 30 and perform payment-related operations (payment-related operations) without waiting for the registration of the purchased product to be completed. tell.
In this case, the customer will go to the payment device 30 before the registration of his or her purchased product is completed. In this case, the customer only has to go to the waiting payment device 30 among the payment devices 30-1 to 30-3. Then, the customer starts a predetermined payment-related operation on the payment device 30 at the destination. Even if the payment device 30 of this embodiment is in the standby state in which payment instruction information is not received, if a predetermined payment-related operation is started, the payment device 30 can accept the payment-related operation.
Such a payment-related operation to start payment is similar to the operation corresponding to the start of payment processing in the first example of the accounting procedure described above, such as a payment instruction to start payment displayed on the display unit 305 An operation on the start button is sufficient. Alternatively, the settlement-related operation in response to the start of settlement may be, for example, in the case of payment in cash, an operation of inserting money as a deposit into the settlement unit 310. Alternatively, the payment-related operation in response to the start of payment may be, for example, an operation to read a membership card.
Alternatively, the payment device 30 sets a state in which payment-related operations can be accepted in response to the fact that the payment device 30 determines that there is a person (customer) within a predetermined range in front of the person, for example, based on the detection output of the human sensor 312. You may.
Alternatively, instead of the human sensor 312, an imaging device is installed so that the payment device 30 can take an image of a customer making payment. In response to determining that there is a customer making payment in front of the device 30, a state may be set in which payment-related operations can be accepted.

In this way, in the second example of the accounting procedure, when a product corresponding to one transaction is registered in the registration device 20, the settlement-related operation corresponding to the same transaction is started in the settlement device 30. be able to.
Here, the payment device 30 notifies the registration device 20 of its own status, for example, in response to a status inquiry request from the registration device 20 or at regular intervals. In addition, if the settlement device 30 is in a standby state where settlement instruction information has not yet been received as described above and a settlement-related operation has been started, the settlement device 30 sends a status notification notifying that the settlement device 30 is in a state where it is not ready for transactions. , to each registration device 20. The transaction-unsupported state is the state of the payment device 30 in which a payment-related operation has been accepted but the payment information of the corresponding transaction has not been acquired, that is, the correspondence between the received payment-related operation and the corresponding transaction. Indicates that no attachment has been made.

The registration device 20 that has received the status notification from the payment device 30 displays the payment device status on the clerk display unit 205, indicating the state of the payment device 30 indicated by the received status notification.
FIG. 5 shows an example of how the payment device status is displayed in this embodiment. In the figure, an example is given in which the payment device status is displayed on the product registration screen that is displayed in response to the execution of the product registration process. Further, this figure shows an example in which the payment device 30 that is in a transaction-incompatible state due to the customer starting a payment-related operation as described above is the payment device 30-1.

The product registration screen in the figure has a structure in which sheets (product registration sheets) indicating product registration contents corresponding to each transaction are stacked. A tab (product registration tab: an example of a heading area) is attached to each product registration sheet. In the figure, three product registration tabs TAB1-1, TAB1-2, and TAB1-3 are displayed. The product registration screen in the figure has a structure in which these three product registration sheets are stacked one on top of the other.
Numbers indicating registration order numbers are displayed on the product registration tabs TAB1-1, TAB1-2, and TAB1-3. The registration order number indicates the order in which product registration is started. In the figure, registration order numbers "1", "2", and "3" are displayed on product registration tabs TAB1-1, TAB1-2, and TAB1-3, respectively. This means that the order in which product registration is started is the transaction corresponding to the product registration tab TAB1-1, the transaction corresponding to the product registration tab TAB1-2, and the transaction corresponding to the product registration tab TAB1-3. shows.
In the following description, unless there is a particular distinction between the individual product registration tabs TAB1-1, TAB1-2, TAB1-3, etc., they will be referred to as product registration tabs TAB1.

In this embodiment, the fact that three product registration tabs TAB1 are displayed as shown in the figure means that there are three transactions for which product registration has not yet been completed (product registration is in progress) in the registration device 20. It shows. Of these three product registration sheets, the store clerk can register the product for the corresponding transaction by operating the product registration sheet placed at the forefront. For transactions corresponding to product registration sheets placed below the frontmost page, product registration is suspended.
By performing an operation (touch operation) on the product registration tab TAB1, the store clerk moves the product registration sheet with the operated product registration tab TAB1 to the front, and responds to the product registration sheet moved to the front. You can register products for transactions. In other words, by operating the product registration tab TAB1, the store clerk selects the product registration sheet corresponding to any one transaction from among the transactions for which multiple products are being registered to be active, and selects the product registration sheet corresponding to the active product registration sheet. You can perform product registration operations in transactions.

In the figure, the product registration sheet with the product registration tab TAB1-1 is shown in an active state. In the active product registration sheet, a product button area AR10 is arranged. In the product button area AR10, product buttons corresponding to each product are arranged. For example, a product name indicating a corresponding product is displayed on the product button.
In the product registration operation, the store clerk can specify the product to be registered by operating the product button. Specifically, when a store clerk wants to specify a product with the product name "Product B" as a registration target, the store clerk operates the product button displayed as "Product B" among the product buttons arranged in the product button area AR10. All you have to do is By operating the product button for "Product B", "Product B" is designated as a registration target. Next, the store clerk can perform an operation to input, for example, the quantity of "Product B". By performing the operations described above for each purchased product, the store clerk can register the products one by one.

The product registration sheet shown in the figure shows that two products are currently registered. Specifically, the registered product list area AR11 on the product registration sheet in the figure shows that two products have been registered in the order of "Product A" and "Product B." Furthermore, the registered product area AR12 shows information about the last registered "product B." Further, in the total price area AR13, it is shown that the total number of products registered so far is "2" and the total price of these two products is 1900 yen.

Further, on the product registration screen, payment device designation buttons BT1-1, BT1-2, and BT1-3 are arranged. The payment device specification buttons BT1-1 and BT1-2 correspond to the payment devices 30-1, 30-2, and 30-3, respectively, and are operations for specifying the payment device 30 to perform payment processing (payment device specification operation). This is the button that performs the process.
Note that if there is no particular distinction between the payment device designation buttons BT1-1 and BT1-2, they will be referred to as payment device designation button BT1.

In the payment device designation button BT1, a payment device status display indicating the current status of the corresponding payment device 30 is performed. In the figure, an example is shown in which the payment device status is displayed by badges BG arranged for each payment device designation button BT1.
Specifically, the figure shows an example in which a badge BG displaying "not supported" is placed on the payment device designation button BT1-1. The state of this payment device designation button BT1-1 indicates that the payment device 30-1 is not compatible with transactions. In other words, in this case, the payment device 30-1 starts a payment-related operation corresponding to one transaction by the customer, but the payment-related operation is associated with the transaction corresponding to the registration of the product in the registration device 20. has not yet been made (the payment instruction information has not been received).
Further, in the figure, an example is shown in which a badge BG displaying "standby" is placed on the payment device designation button BT1-2. The state of this payment device designation button BT1-2 indicates that the payment device 30-2 is in a state of waiting for the start of payment processing. In other words, the payment device 30-1 at this time is in a state where the payment-related operation has not been started and the payment instruction information has not been received.
Further, an example is shown in which a badge BG displaying "in use" is placed on the payment device designation button BT1-3. Further, the characters "Payment machine 3" on the payment device designation button BT1-3 are shaded. The state of this payment device designation button BT1-3 indicates that the payment device 30-3 is executing payment processing based on payment information obtained by receiving payment instruction information in response to a customer's operation.
Note that the color, pattern, etc. of the payment device designation button BT1 itself may be displayed to be changed depending on the state of the payment device 30 as described above.

Note that, depending on the payment device status display, various states other than the above-mentioned "unsupported" (transaction unsupported), "standby", and "in use" may also be shown, such as near-end, near-full, and failure. The payment device status display may be displayed in a manner other than the badge BG, such as by displaying characters or icons to fit within the payment device designation button BT1, or by displaying it in a separate area from the payment device designation button BT1. may be done.

Note that regarding the payment device designation button BT1 corresponding to the payment device 30 that is in the "in use" state, a display showing a more detailed state of the "in use" state may be performed. For example, when the payment device 30 in the "in use" state is executing a payment process corresponding to the cash payment type, information regarding the deposited amount will be displayed on the corresponding payment device designation button BT1. may be displayed. In this case, the information regarding the amount deposited as a deposit is such that, for example, in response to the input of money as a deposit in the settlement device 30, the total amount of money deposited to date is displayed. good. Alternatively, the confirmed deposit amount may be displayed when the deposit amount is determined by depositing an amount equal to or greater than the total price of the product.
In addition, when the payment device 30 in the "in use" state is executing payment processing corresponding to the payment type by credit card or electronic money, for example, the payment device 30 in the "in use" state may display a message such as "payment by card" or "payment by electronic money". A display may be displayed indicating that payment processing compatible with credit cards or electronic money is being executed.
The above-mentioned display showing a more detailed state of the "in use" state may be performed instead of the display showing the "in use" state by the badge BG in FIG. 5, for example.

In the following explanation, we will use as an example the case where the transaction corresponding to the customer who has started the payment-related operation on the payment device 30 is the transaction corresponding to the product registration sheet labeled with the product registration tab TAB1-1 in the figure. List.
When the store clerk completes the registration of all products in the transaction corresponding to the product registration sheet of the product registration tab TAB1-1, the payment device 30 that executes the payment processing corresponding to the transaction is activated by the payment devices 30-1 to 30-. Check which one of the three. In this case, the clerk can confirm which payment device 30 is to perform the payment processing corresponding to the transaction by visually confirming, for example, which payment device 30 currently has a corresponding customer.
Note that when the payment device 30 is provided with an imaging device as described above, based on images captured by the imaging device, for example, in response to a determination that the same person has been continuously imaged for a certain period of time or more, The captured image may be displayed on the store clerk display section 205 of the registration device 20. In this way, the store clerk can more accurately confirm which payment device 30 has a corresponding customer.
Then, as a payment device designation operation, the clerk operates the payment device designation button BT1 corresponding to the verified payment device 30. In correspondence with the example of FIG. 5, the payment device designation button BT1 that is the target of the payment device designation operation is the payment device designation button BT1-1 that corresponds to the payment device 30-1. Therefore, in this case, the clerk operates the payment device designation button BT1-1 as the payment device designation operation. Here, a badge BG indicating that the payment device designation button BT1-1 is not compatible with transactions is arranged. When operating the payment device designation button BT1-1, the clerk can also confirm that the badge BG indicates that the transaction is not supported, so the clerk may accidentally press a payment device designation button BT1 other than the payment device designation button BT1-1. It also prevents you from manipulating the

In response to the operation on the payment device designation button BT1-1, the registration device 20 generates payment instruction information including payment instruction information for the transaction corresponding to the product registration sheet to which the product registration tab TAB1-1 is attached. is transmitted to the payment device 30-1.
In response to sending the payment information to the payment device 30-1 as described above, the product registration sheet with the product registration tab TAB1-1 that was previously displayed on the registration device 20 will be changed to It should be erased from the screen. Then, instead, for example, a product registration sheet to which a product registration tab TAB1-2 is attached is displayed in the foreground.
Also, when the product registration sheet with the product registration tab TAB1-2 is displayed in the foreground, the registration order number displayed in the product registration tab TAB1-2 will change from "2" to " The registration order number displayed on the product registration tab TAB1-2 is moved up from "3" to "2".

The settlement device 30-1, which is not ready for transactions, receives the settlement instruction information transmitted from the registration device 20 as described above. As can be understood from the above explanation, the settlement instruction information sent from the registration device 20 to the settlement device 30-1 that is not ready for transactions starts a settlement-related operation for the settlement device 30-1. Respond to customer transactions. In other words, the payment device 30-1, which is in a transaction-unsupported state, receives payment instruction information transmitted from the registration device 20, and responds to payment-related operations initiated by the customer by the registration device 20. This means that the corresponding transaction can be associated with the product registration.

The payment device 30-1, which is not ready for transactions, is already in a state where the customer has already started the payment-related operation at the timing when the payment instruction information transmitted from the registration device 20 is received.
Here, an example of a settlement process that is executed by the settlement device 30-1 in a transaction-unsupported state in response to reception of settlement instruction information will be described, taking as an example a case where a customer pays the price in cash.
After starting the settlement-related operation, the customer performs an operation to insert money as a deposit into the settlement unit 310 in order to pay the price in cash. When the payment instruction information is received, the payment device 30-1 recognizes the payment amount from the payment information included in the received payment instruction information. Then, the settlement device 30-1 determines whether or not the amount deposited as a deposit at this point in time is greater than or equal to the payment amount.
If the input amount is less than the payment amount, the adjustment device 30-1 waits until the input amount, which increases according to the subsequent money insertion operation, reaches the payment amount or more. Then, in response to the input amount being equal to or greater than the payment amount, the settlement device 30-1 calculates the change, discharges the change, issues a receipt, etc.

FIG. 6 shows an example of a payment screen displayed on the display unit 305 of the payment device 30-1 that executes payment processing as described above.
On the payment screen in the figure, a registered product area AR21 and a payment related information area AR22 are arranged.
In the registered product area AR21, information for each product registered in the registration device 20 in the corresponding transaction (registered product information) is displayed. The registered product information is displayed based on the payment instruction information received from the registration device 20. At the stage where the transaction corresponding to the product registration performed in the registration device 20 is not associated with the payment-related operation, the registered product information is not displayed in the registered product area AR21. When the registered product information is hidden in the registered product area AR21, the transaction corresponding to the product registration performed in the registration device 20 is associated with the current payment-related operation, for example, as "not supported". It may be possible to indicate that the state is not set.
In the payment related information area AR22, a product registration result area AR221 is arranged. The product registration result area AR221 is an area that displays product registration results for corresponding transactions. In the example shown in the figure, the number of registered products and the total price of the registered products are displayed as product registration results in the product registration result area AR221. The product registration results in the product registration result area AR221 are displayed based on the payment instruction information received from the registration device 20. Therefore, the product registration result is not displayed until the transaction corresponding to the product registration performed in the registration device 20 is associated with the payment-related operation.
Further, in the payment related information area AR22, an input amount area AR222 is arranged. In the deposited amount area AR222, the amount of deposit deposited by the customer is displayed. The amount of the deposit is displayed in response to the customer starting to insert money as a deposit.

The payment screen in FIG. 6 is an example when the payment type supported by the payment device 30 is limited to cash payments. On the other hand, FIG. 7 shows an example of an aspect of the payment screen in a case where there are a plurality of payment types that can be handled by the payment device 30.

FIG. 7A is an example of a payment screen that is first displayed in response to, for example, a predetermined payment-related operation performed in response to the start of payment. In the payment screen shown in the figure, a registered product area AR31, a payment related information area AR32, and an operation area AR33 are arranged.

In the registered product area AR31, information for each product registered in the registration device 20 in the corresponding transaction (registered product information) is displayed. At the stage where the transaction corresponding to the product registration performed in the registration device 20 is not associated with the payment-related operation, the registered product information is not displayed in the registered product area AR31. In the registered product area AR31, when the registered product information is hidden, it indicates that the transaction corresponding to the product registration performed in the registration device 20 is not associated with the current payment-related operation. It may be possible to do so.

In the settlement related information area AR32, product registration results for the corresponding transaction are displayed. In the example shown in the figure, the number of registered products and the total price of the registered products are displayed as product registration results. The product registration result is not displayed until a transaction corresponding to the product registration performed in the registration device 20 is associated with a payment-related operation.

The operation area AR33 is an area where customers perform payment-related operations. In the operation area AR33 of the figure, a "Yes" button BT21 and a "No" button BT22 are arranged along with a message inquiring the customer whether or not he or she has a membership card.
If the customer has a membership card and wishes to use the membership card for this payment, he or she operates the "Yes" button BT21. On the other hand, if the customer does not have a membership card or does not intend to use the membership card even if he has a membership card, he operates the "No" button BT22.

When the "Yes" button BT21 is operated, although not shown, a message is displayed in the operation area AR33, for example, instructing the user to perform an operation to read the information recorded on the membership card. The customer follows the instructions and operates the scanner unit 304 or card reader 313 to read the information recorded on the membership card.

After the information on the membership card is read, or in response to the "No" button BT22 being operated, the payment screen changes to the mode shown in FIG. 7(B). In the payment screen shown in the figure, the aspect of the operation area AR33 has been changed from that shown in FIG. 7(A). That is, in the operation area AR33 of the figure, a "Yes" button BT31 and a "No" button BT32 are arranged along with a message asking the customer whether or not he or she has a point card.

If the customer has a point card and wishes to use the point card for the current payment, he/she operates the "Yes" button BT31. On the other hand, if the customer does not have a point card or does not intend to use the point card even if he has a point card, he operates the "No" button BT32.

When the "Yes" button BT31 is operated, although not shown, a message is displayed in the operation area AR33, for example, instructing the user to perform an operation to read the information recorded on the point card. The customer follows the instructions and operates the scanner unit 304 or card reader 313 to read the information recorded on the point card.

After the information on the membership card is read, or in response to the "No" button BT32 being operated, the payment screen changes to the mode shown in FIG. 7(C).
Note that if the membership card has a function as a point card, the payment screen may be changed to the payment screen in FIG. 7(C) without displaying the payment screen in FIG. 7(B).

In the operation area AR33 of the payment screen in FIG. 7(C), buttons corresponding to each selectable payment type are arranged along with a message informing the customer that they should select the payment type (payment method). Ru. In the figure, an example is shown in which a "cash" button BT41, a "credit card button" BT42, and an "electronic money" button BT43 are arranged as buttons corresponding to the payment types. That is, the payment type can be selected from among cash, credit card, and electronic money depending on the operation on the operation area AR33 in the figure.
The customer operates the button corresponding to the payment type he/she uses for payment from among the "cash" button BT41, "credit card button" BT42, and "electronic money" button BT43.
When a button corresponding to the payment type is operated, although not shown, a payment screen corresponding to the operation, guidance, etc. for payment according to the payment type selected according to the operated button is displayed. The customer performs a payment operation according to the payment type selected by the customer in accordance with the payment screen that is displayed thereafter.
In this way, in the POS system 1 of this embodiment, accounting can also be performed according to the second example of the accounting procedure.
In addition, in the checkout procedure of the second example, the purchased products for which the product registration has been completed in the registration device 20 are placed in a basket or the like at a predetermined position near the registration device 20 by the store staff, and the customer For example, it may be possible to collect the item after completing the payment.

In the first example of the checkout procedure, in one transaction, first, a store clerk performs a product registration operation on the registration device 20, and then a customer performs a payment-related operation on the payment device 30. That is, in the first example of the checkout procedure, the checkout-related operation is performed after the product registration operation is completed.
On the other hand, in the second example of the checkout procedure, in one transaction, while the store clerk is performing a product registration operation on the registration device 20, the customer can start payment-related processing on the payment device 30. That is, in the second example of the accounting procedure, the period in which the product registration operation is performed and the period in which the settlement-related operation is performed can partially overlap in one transaction. As a result, by operating the second example of the accounting procedure, it is possible to reduce the time required for one transaction and improve the efficiency of customer handling than in the case of the first example of the accounting procedure.

As described above, between the first example and the second example of the accounting procedure, the second example is more advantageous in terms of customer handling efficiency. However, in a store, it is not necessary to always operate according to the second example of the checkout procedure.
For example, the first example of the checkout procedure currently has the aspect that the customer is less likely to be confused because it is a procedure that the customer is accustomed to. Therefore, in a situation where there are few customers and there are few or no queues of customers waiting to pay, the first example of the checkout procedure is used. On the other hand, in a situation where the number of customers waiting in line increases, the system may switch to the second example of the checkout procedure.

Next, with reference to the flowchart of FIG. 8, an example of a processing procedure executed by the registration device 20 and the payment device 30 of this embodiment in response to the second example of the accounting procedure will be described.
Step S101: The registration device 20 determines whether a product registration operation for each product has been performed in one transaction.
Step S102: If it is determined in step S101 that a product registration operation has been performed, the registration device 20 executes a product registration process according to the product registration operation.

Step S103: If it is determined in step S101 that the product registration operation is not performed, or after the process in step S102, the registration device 20 determines whether or not the status notification sent from the payment device 30 has been received. judge. In explaining the figure, a case will be exemplified in which the payment device 30 is configured to transmit a status notification in response to a change in the status of the payment device 30.
Step S104: If it is determined in step S103 that the status notification has been received, the registration device 20 displays the payment device status indicating the status of the payment device 30 that is the source of the received status notification. Specifically, as illustrated in FIG. 5, for example, the payment device status may be displayed using a badge BG or the like placed in response to the payment device designation button BT1.

Step S105: If it is determined in step S103 that the status notification is not received, or after the process in step S104, the registration device 20 determines whether or not a subtotal operation has been performed.
If it is determined that the subtotal operation is not performed, the process returns to step S101.
Step S106: On the other hand, if it is determined in step S105 that a subtotal operation has been performed, the registration device 20 waits for a payment device designation operation to be performed. As described above, the payment device designation operation is an operation on the payment device designation button BT1 corresponding to the payment device 30 on which the payment processing should be executed.
Step S107: In response to the payment device designation operation being performed, the registration device 20 sends the payment device 30 designated by the payment device designation operation to the payment device 30, in which the product registration result corresponding to the current transaction is reflected. Send payment instruction information including information.

Next, the processing of the payment device 30 will be explained.
Step S201: The payment device 30 waits for the payment-related operation to start before the payment instruction information is received.
Step S202: In response to the start of the payment-related operation, the payment device 30 starts processing corresponding to the payment-related operation after the start (payment-related operation corresponding process). For example, in a case where an operation is performed to insert money as a deposit into the payment unit 310 as a payment-related operation in response to a payment in cash, the payment device 30, in step S202, responds to the payment-related operation. As a process, the total amount of inserted money (inserted amount) is detected. Further, the payment device 30 may display the detected input amount on the payment screen of the display unit 305, for example. Although such payment-related operation corresponding processing does not yet utilize payment information, it may be treated as included in the payment processing.

Step S203: Further, in response to the start of a payment-related operation before the payment instruction information is received, the payment device 30 sends a status notification to the registration device 20 indicating that the transaction is not supported. Send for each.

Step S204: After step S203, the payment device 30 waits for payment instruction information to be received while executing the payment-related operation corresponding process started in step S202.
Step S205: When the payment instruction information is received, the payment device 30 executes the subsequent payment processing using the payment information included in the received payment instruction information.
Step S206: Further, in response to receiving the payment instruction information and starting payment processing using the payment information, the payment device 30 sends a status notification to each registered device 20 indicating that the payment device 30 is currently in use. Send to.
Step S207: The payment device 30 waits for the payment process executed in response to step S205 to be completed.
Step S208: When the payment processing is completed, the payment device 30 transmits a status notification to each of the registration devices 20 indicating that the payment device 30 is in a standby state.

<Second embodiment>
Next, a second embodiment will be described. In a POS system that includes a registration device and a payment device, the following example is one of the reasons why the time required for accounting for one transaction becomes long.
In other words, if a customer who is trying to make a payment is a member of the store and wants to receive benefits as a member in response to this transaction, the customer must register when registering the product using the registration device 20. It is necessary to present one's own membership card to the store clerk who operates the device 20. The clerk who is presented with the membership card inputs the customer's membership identification information into the registration device 20 using the membership card, and also performs a product registration operation. Thereby, the current transaction is managed as one that corresponds to the member, and, for example, by communicating between the registration device 20 and the management device 10, benefits such as points are given to the customer.

Membership cards are often carried in wallets or the like. Therefore, in order to present the membership card to the store clerk, the customer must take out his/her wallet or the like while the product is being registered in the registration device. However, customers are aware that the only time they take out their wallet or the like during the checkout process is when they perform a payment-related operation on the payment device. For this reason, customers who are members tend to forget that they need to take out their wallets, etc. at the stage of registering products on the registration device, and they take the time to take out their wallets, etc., making it difficult for them to present their membership cards. There may be delays. Such a delay in presentation of the membership card may impede improvement in customer handling efficiency.

Therefore, in the POS system 1 of the present embodiment, the content of benefits given to a customer who is a member is varied depending on the timing at which a customer who registers a product at the registration device 20 presents a membership card.
In this embodiment, a plurality of processing stages are specifically set corresponding to the product registration process for one transaction in the registration device 20. The number of points awarded is changed depending on which processing stage corresponds to the timing when the member identification information recorded on the member card is read by the card reader 210 or the scanner unit 204 of the registration device 20. Ru. Specifically, the earlier the member identification information is read, the higher the number of points awarded.

In the POS system 1 of the present embodiment, in order to realize the above-mentioned point allocation, for example, the registration device 20 stores a table of the number of points to be allocated, which associates the processing stages with the number of points to be allocated.
FIG. 9 shows an example of a table of the number of points awarded. In the figure, an example is shown in which three processing stages are set: "Before starting product registration processing,""Before subtotal operation," and "Within 5 seconds after subtotal operation."
"Before starting the product registration process" is a stage before the product registration process corresponding to one transaction is started. "Before subtotal operation" is a stage from when the product registration process corresponding to one transaction is started until before subtotal operation is performed. "Within 5 seconds after subtotal operation" is a stage within 5 seconds from the time when the subtotal operation was performed. In addition, in the same figure, the number of points awarded "5" is associated with "Before starting the product registration process", the number of points awarded "3" is associated with "Before subtotal operation", and the number of points awarded "3" is associated with "Before starting the product registration process". An example is shown in which "within 5 seconds after subtotal operation" is associated with the number of points awarded of "1".
It should be noted that the settings of the processing stages and the number of points awarded for each processing stage in the figure are merely examples, and may be changed depending on the operation, for example.

When the registration device 20 of this embodiment reads the member identification information from the membership card, it refers to the number of points awarded table and determines whether the timing of reading the member identification information is in any of the processing stages indicated in the number of points awarded table. Determine whether it is applicable. The registration device 20 acquires the number of points to be awarded that is associated with the determined processing stage from the number of points to be awarded table. The registration device 20 transmits to the management device 10 a privilege award request including the member identification information read from the membership card and the number of award points obtained from the award point number table. The management device 10 performs processing so that the number of points to be awarded included in the same privilege grant request is added to the cumulative value (point balance) of the member's points in the member identification information included in the privilege grant request.
In this way, in the POS system 1 of this embodiment, when a customer registers a product on the registration device 20, the earlier the customer presents the membership card, the more points will be awarded. can do.

Inform the members that the store provides a service in which the earlier the member card is presented, the more points will be awarded. As a result, customers who are members will be conscious of presenting their membership cards as soon as possible when registering products at the registration device 20. As a result, it is less likely that the product registration time will be prolonged due to the customer taking out the member card, and the efficiency of customer handling will be improved.

<Modified example>
Modifications of this embodiment will be described below.
[First modification]
Note that the number of points awarded in the second embodiment is not limited to the number of points awarded according to the table of number of points awarded in FIG. 9, and may be operated more flexibly.
For example, basically, the number of points awarded may be changed according to the customer group based on the table of number of points awarded as shown in FIG. Specifically, for example, if the customer who is a member is an elderly person over a certain age, according to customer information managed by member identification information read from a membership card, "before subtotal operation" and "after subtotal operation" In the processing stage of "within 5 seconds", a predetermined number of points to be awarded may be set higher than that indicated by the number of points to be awarded table. In other words, in the case of elderly people, it often takes time to take out the membership card, which is disadvantageous for elderly people. Therefore, by setting the number of points awarded in this way, the elderly will not be at a disadvantage.
In addition, points can be awarded using a points award table, for example, limited to specific days when store operations are busy (for example, holidays, special sale days, etc.) or specific times (for example, in the evening, when special sales are held). will be operated. On the other hand, on other than a specific day or time period, the table of number of points to be awarded may not be used, and a predetermined number of points to be awarded may be applied regardless of the reading timing of the member identification information. If this type of operation is used, customers will proactively present their membership cards early even when the store is busy, so the number of transactions that can be processed per unit of time will be increased, and customers will be able to check out more quickly. This can effectively shorten the waiting time to receive the service.

[Second modification]
Note that, for example, payment processing corresponding to payment methods that do not require handling of cash, such as credit cards, cash vouchers, and electronic money, can be performed by the registration device 20 that does not include a change machine. In such a case, the store clerk who operates the registration device 20 to register the product confirms the customer's desired payment method by, for example, asking the customer, and then checks the device including not only the payment device 30 but also the registration device 20. The customer may be able to perform an operation to specify which device is to perform the payment processing corresponding to the customer.
In the case of this modification, if a registration device is specified as the device that should execute the payment processing corresponding to the customer, the specified registration device will be able to process the transaction corresponding to the registration of the product and the payment made by the customer. Correspondence with related operations may be made.

[Third modification]
Furthermore, in each of the above embodiments, it is assumed that the store clerk who operates the registration device 20 will verbally interact with the customer, and the store clerk will perform an operation to specify the device that should perform the payment processing corresponding to the customer. It is being done.
However, for example, after the product registration start timing in the registration device 20, the customer can make the payment corresponding to him/her by operating the customer display section 205a of the registration device 20, including specifying the payment method if necessary. It may also be possible to specify a device to execute the process.

[Fourth modification]
In each of the embodiments described above, the POS system 1 has been exemplified, which includes a product registration device that performs product registration processing in response to a store clerk's operation, and a payment device that performs payment processing in response to a customer's operation.
However, as in each of the above embodiments, the configuration of the present embodiment in which a transaction corresponding to a product registration performed in the registration device 20 is associated with a payment-related operation can also be applied to the following POS systems. good.
That is, the configuration of each of the embodiments described above may be applied to a POS system including a plurality of POS registers in which a store clerk performs a product registration operation and a customer performs an operation corresponding to payment while facing the store clerk. In the case of such a POS system, the POS register where the product has been registered issues an instruction (transmission of payment instruction information) to execute payment processing at one of multiple other POS registers. It would be good if it were done.
Furthermore, the configuration of each of the above embodiments includes a first checkout mode in which a store clerk performs a product registration operation and an operation corresponding to payment, and a first checkout mode in which a store clerk performs a product registration operation and a customer performs an operation corresponding to payment. A POS system equipped with a plurality of POS registers that can be switched between a second checkout mode in which customers perform product registration operations and a third checkout mode in which customers perform operations corresponding to product registration and payment. It can also be applied to In the case of such a POS system, for example, the state of the second accounting mode or the third accounting mode can be checked from the POS register where the product was registered in accordance with the operation of the clerk in the first accounting mode or the second accounting mode. It is only necessary that an instruction (transmission of payment instruction information) be given so that payment processing is executed at one of the other POS registers in the POS register.

[Fifth modification]
In the embodiment described above, the mode of specifying the settlement device 30 to execute the settlement process from among the plurality of settlement devices 30 is the mode in which the clerk specifies the settlement device 30 to execute the settlement process using the registration device 20. (first designation mode), and a mode in which the registration device 20 issues a checkout ticket handed to the customer, and the customer reads the checkout ticket handed over by the clerk into one payment device 30 (second designation mode). (designation mode). However, the mode of specifying the payment device 30 is not limited to the above mode. For example, the payment device 30 may be specified as in the third to seventh specification modes below.

As a third designation mode, in response to an operation performed on the send button displayed on the clerk display section 205 upon completion of product registration (or an operation that declares completion of product registration). The registration device 20 may, for example, make a status inquiry to the payment device 30 and recognize the payment device 30 that is capable of payment processing (for example, no failure has occurred and is not in use) and is not in use. One settlement device 30 is determined from among the settlement devices 30 according to a predetermined rule. Then, the registration device 20 transmits the payment information to the determined payment device 30 and instructs it to execute the payment processing.

As a fourth designation mode, the priority order of payment processing is set in advance for the payment device 30. Then, in response to the completion of product registration, a display is displayed on the clerk display section 205 so that the operation of a send button instructing to send payment information to the payment device 30 is enabled. In response to the operation of the send button, the registration device 20 checks whether or not the payment device 30 is capable of payment processing in the order according to the set priority order, and confirms that the payment processing is possible. If not confirmed, the payment device 30 with the next priority is checked. Then, the registration device 20 transmits payment information to the payment device 30 that was first confirmed to be capable of payment processing, and instructs it to execute the payment processing.

The priority order of the payment device 30 according to the predetermined rules in the third designation mode or the payment device 30 in the fourth designation mode is determined based on the number assigned to the payment device 30, for example. It's fine. Alternatively, it may be determined based on the distance from the registration device 20 to the payment device 30. Alternatively, it may be determined based on the relationship between the breakdown of the denominations of change predicted based on the total amount and the number of coins of each denomination stored in the change machine of the settlement device 30.

As a fifth designation mode, the registration device 20 transmits payment information to all payment devices 30. When the payment device 30 that has received the payment information becomes capable of executing payment processing using the payment information included in the payment information that it has received, it sends a payment processing execution notification that notifies that the payment device 30 will execute the payment processing. is sent to the registration device 20 that is the sender of the payment information.
In response to receiving the payment processing execution notification, the registration device 20 displays a display indicating the payment processing device 30 to which the payment processing execution notification is sent (a payment processing execution display). The clerk only has to look at the payment process execution display and tell the customer which payment device 30 is to execute the payment process.
At this time, in addition to displaying the payment processing execution notification, the sign pole 311 of the payment device 30 that sent the payment processing execution notification is lit in a predetermined pattern, or the payment device 30 outputs a predetermined notification sound. It may be possible to notify that the payment process will be executed.

According to the specification of the payment device 30 according to the third to fifth designation modes described above, it is not necessary to determine which payment device 30 should perform the payment process.

As a sixth designation mode, the store clerk places the shopping cart containing the products that have been registered in the registration device 20 in one of the cart storage areas installed corresponding to each payment device 30. move.
The cart storage area is equipped with a sensor (such as a weight sensor or an optical sensor) that detects the shopping cart placed therein. When the sensor determines that a shopping cart has been placed in the cart storage area, the corresponding payment device 30 makes a request, acquires the corresponding payment information from the registration device 20, and executes payment processing. .
In this case as well, the payment device 30 that is to perform the payment process may notify that it will perform the payment process by lighting the sign pole 311 or outputting a notification sound.
Note that instead of the sensor for detecting a placed shopping cart, a human sensor or an imaging device may be provided, for example, corresponding to a store clerk. Then, the registration device 20 determines the movement of the store clerk based on the detection output of the human sensor, the image captured by the imaging device, etc., and based on the determined result, the store clerk It is determined in which of the basket storage areas installed corresponding to the shopping cart the shopping cart is installed. Then, the payment device 30 corresponding to the determined basket storage area may be determined as the payment device 30 that should perform the payment process.

As a seventh designation mode, the registration device 20 transmits settlement instruction information including settlement information and transfer order information that sets the transfer order among the plurality of settlement devices 30 to a certain settlement device 30. . The transfer order information may specify the transfer order cyclically between the payment devices 30.
If the payment device 30 that has received the payment instruction information is capable of executing the payment processing, it transmits a payment processing execution notification to the registration device 20 that is the source of the payment instruction information, and receives the received payment instruction information. The payment process is executed using the payment information included in the payment information.
On the other hand, if the payment device 30 that has received the payment instruction information is unable to execute the payment processing, the payment device 30 that has received the payment instruction information sends the payment to the payment device 30 that is next in the transfer order according to the transfer order information included in the received payment instruction information. Transfer the received payment instruction information. In this way, by sequentially transferring the payment instruction information between the payment devices 30, a procedure corresponding to the designation of the payment device 30 to perform the payment process can be realized.

In each of the above specification modes, the processing related to determining the payment device 30 to execute the payment processing is performed by a predetermined device other than the registration device 20 and the payment device 30, such as the management device 10, registering the product by the registration device 20. It may be executed in response to the completion of processing. The predetermined device other than the registration device 20 and the payment device 30 may be, for example, a device provided for monitoring the state of the payment device 30.

Note that a program for realizing the functions of the above-mentioned registration device 20, payment device 30, etc. is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read into a computer system and executed. Accordingly, processing as the above-mentioned registration device 20, payment device 30, etc. may be performed. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program on the computer system. The "computer system" here includes hardware such as an OS and peripheral devices. Further, a "computer system" may include a plurality of computer devices connected via a network including the Internet, a WAN, a LAN, a communication line such as a dedicated line, etc. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into computer systems. In this way, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The recording medium also includes a recording medium provided internally or externally that can be accessed from the 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. That is, as long as it can be downloaded from the distribution server and installed in an executable form on the terminal device, the format in which it is stored on the distribution server does not matter. Note that the program may be divided into a plurality of parts, downloaded at different timings, and then combined on a terminal device, or the distribution servers that deliver each of the divided programs may be different. Furthermore, a ``computer-readable recording medium'' refers to a storage medium that retains a program for a certain period of time, such as volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network. This shall also include things. Moreover, the above-mentioned program may be for realizing a part of the above-mentioned functions. Furthermore, it may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

<Summary of embodiments>
(1) As explained above, one aspect of the present embodiment includes a registration device (20) in which products are registered in response to operations by a store clerk, and payment information that reflects the product registration results by the registration device. A product sales data processing system (for example, a POS system 1) comprising a plurality of payment devices (30) that perform payment processing based on a customer's operation in response to a store clerk's operation on the registration device. a product registration means for registering a product corresponding to one transaction according to the transaction, and a product registration means for registering a product corresponding to one transaction according to the customer, and starting a payment related operation corresponding to one transaction performed by a customer on the payment device from a stage before the payment information is acquired. a payment-related operation receiving means that can be accepted; a transaction control means for associating a transaction corresponding to the product registration performed by the product registration means with a transaction corresponding to the payment-related operation received by the payment-related operation receiving means; This is a product sales data processing system.

According to the above configuration, before the registration of products corresponding to a certain transaction is completed in the registration device 20, a customer who has responded to the same transaction can initiate an operation corresponding to the payment on the payment device 30. Can be done. In this case, an overlapping period is obtained in which operations corresponding to product registration and operations corresponding to settlement are performed in parallel for the same transaction. As a result, the time required to complete the checkout for one transaction is shortened, and the efficiency of customer handling is improved, compared to the case where the checkout operation is performed after the product registration is completed using the registration device 20, for example. Improvements will be made.

(2) One aspect of the present embodiment is the product sales data processing system described in (1), wherein the payment-related operation receiving means initiates an operation for inserting cash into the payment device. , accepted as the start of a payment-related operation.

According to the above configuration, the operation of inserting money, which is an operation that takes a relatively long time among the settlement operations corresponding to payment in cash, is performed while the product is being registered in the registration device 20. You can leave it there. This makes it possible to further improve the efficiency of customer handling.

(3) One aspect of the present embodiment is the product sales data processing system described in (1) or (2), wherein the payment-related operation receiving means transmits customer identification information for identifying the customer to the payment device. The input operation is accepted as the start of a payment-related operation.

According to the above configuration, for example, a customer performs an operation to cause the payment device 30 to read member identification information (an example of customer identification information) recorded on a membership card while product registration is being performed in the registration device 20. You can keep it.

(4) One aspect of the present embodiment is the product sales data processing system according to any one of (1) to (3), wherein the registration device displays a state of the payment device. The payment device status display means further comprises a payment device status display means, and the payment device status display device displays the status of the payment device that is executing the payment processing based on the acquired payment information and the product information for the transaction corresponding to the payment related operation that has been started. The status of the payment device with which the transaction corresponding to the registration is not associated is displayed in different predetermined manners.

According to the above configuration, even if operations corresponding to the same payment are accepted, the payment device 30 in the state of executing payment processing based on payment information is not associated with the transaction corresponding to product registration. It becomes possible to distinguish and display the status of the payment device 30.

(5) One aspect of the present embodiment includes a registration device in which products are registered in response to an operation by a store clerk, and a payment process based on payment information that reflects the product registration result by the registration device in response to a customer's operation. A registration device in a product sales data processing system comprising a plurality of payment devices that perform payment according to the transaction, a product registration means that registers a product corresponding to one transaction in response to an operation by a store clerk, and a product registration device that registers a product corresponding to one transaction in response to an operation by a store clerk. The transaction corresponding to the registration of the product and the transaction corresponding to the transaction related to the payment performed by the customer on the payment device or the registration device in response to one transaction are recorded in the payment information by the payment device or the registration device. This is a registration device equipped with a transaction control means for associating transactions even before they are acquired.

(6) One aspect of the present embodiment includes a registration device in which products are registered in response to an operation by a store clerk, and a payment process based on payment information that reflects the product registration result by the registration device in response to a customer's operation. A payment device in a product sales data processing system comprising a plurality of payment devices that perform processing according to the payment method, wherein the payment information is acquired to initiate a payment related operation corresponding to one transaction performed by a customer on the payment device. A payment-related operation receiving means that can accept the payment from a stage before the payment is made, a transaction corresponding to the registration of the product performed in the registration device, and a transaction corresponding to the payment-related operation received by the payment-related operation receiving means are associated with each other. The payment device is equipped with a transaction control means.

(7) One aspect of the present embodiment includes a registration device in which products are registered in response to an operation by a store clerk, and a payment process based on payment information that reflects the product registration result by the registration device in response to a customer's operation. A computer included in a product sales data processing system comprising a plurality of payment settlement devices according to the transaction is used as a product registration means for registering products corresponding to one transaction in response to operations performed by a store clerk on the registration device; A settlement-related operation receiving means that can accept the start of a settlement-related operation corresponding to one transaction performed on the settlement device from a stage before the settlement information is acquired; This is a program for functioning as a transaction control means that associates a transaction corresponding to registration with a transaction corresponding to a settlement-related operation received by the settlement-related operation receiving means.

(8) One aspect of the present embodiment includes a registration device in which products are registered in response to an operation by a store clerk, and a payment process based on payment information that reflects the product registration result by the registration device in response to a customer's operation. A computer serving as a registration device in a product sales data processing system comprising a plurality of payment settlement devices according to the operations of a store clerk; and a transaction corresponding to a payment-related operation performed by a customer on the payment device or the registration device in response to one transaction, at a stage before the payment information is acquired by the payment device or the registration device. This is a program that functions as a transaction control means for mapping from

(9) One aspect of the present embodiment includes a registration device in which products are registered in response to an operation by a store clerk, and a payment process based on payment information that reflects the product registration result by the registration device in response to a customer's operation. A computer serving as a settlement device in a product sales data processing system comprising a plurality of settlement devices that perform operations according to the settlement information acquires the start of a settlement-related operation corresponding to one transaction performed by a customer on the settlement device. A payment-related operation reception means that can be accepted from a stage before the payment is made, and a transaction corresponding to the registration of the product performed in the registration device is associated with a transaction corresponding to the payment-related operation accepted by the payment-related operation reception means. A program to function as a transaction control means.

1 POS system, 10 management device, 11 LAN, 20 (20-1, 20-2) registration device, 30 (30-1 to 30-3) payment device, 201 CPU, 202 storage unit, 203 RAM, 204 scanner unit , 205 Display section for clerk, 205a Display section for customer, 206 Operation section, 207 Communication section, 208 Buzzer, 209 Printing section, 210 Card reader, 301 CPU, 302 Storage section, 303 RAM, 304 Scanner section, 305 Display section, 306 Operation section, 307 Communication section, 308 Buzzer, 309 Printing section, 310 Payment section, 311 Sign pole, 312 Human detection sensor, 313 Card reader

Claims (2)

Product sales data comprising a registration device that registers products in response to operations by a store clerk, and a payment device that performs payment processing in response to operations by a customer based on payment information that reflects the registration results of products by the registration device. A processing system,
A product corresponding to one transaction is registered in accordance with the clerk's operation performed on the registration device, and payment information reflecting the product registration result is sent to the payment device designated to execute the payment processing. Product registration means,
A payment-related operation receiving means capable of accepting a payment-related operation corresponding to one transaction performed by a customer on the payment device from a stage before the payment information is acquired;
When displaying the status of the payment device on the registration device, the payment device is in a transaction-unsupported state where the customer has performed a payment-related operation before payment information is acquired. In this case, a first status is displayed indicating that the transaction is in the first state where the transaction is not supported , and the payment device acquires payment information sent from the registration device and executes payment processing. When in the second state of being in use, a second state display is displayed to indicate that the device is in the second state, and the payment device waits for the start of payment processing in a state where no payment-related operation is performed by the customer. display means for displaying a third state indicating that the third state is in the third state ;
When the payment device receives the payment information in the first state, the payment information is applied to a transaction corresponding to the payment-related operation performed in the first state. When the settlement information is acquired by reception in the third state, the acquired settlement information is made to correspond to a new transaction, and according to the settlement-related operation after acquiring the settlement information. A payment method that executes payment processing;
A system equipped with Product sales data comprising a registration device that registers products in response to an operation by a store clerk, and a payment device that performs payment processing in response to a customer's operation based on payment information that reflects the registration result of the product by the registration device. In the processing system, a first program for causing a first computer to function as the payment device, and a second program for causing a second computer to function as the payment device,
The first program registers a product corresponding to one transaction in response to an operation performed by a store clerk on the registration device, and sends payment information that reflects the registration result of the product when execution of payment processing is specified. causing the first computer to function as a product registration means for transmitting to a payment settlement device;
The second program is configured to operate the second computer as a payment-related operation receiving means capable of accepting a payment-related operation corresponding to one transaction performed by a customer on the payment device from a stage before the payment information is acquired. function,
In performing a status display indicating the state of the payment device, the first program is configured to display a state in which the payment device is in a transaction-unsupported state where the customer is performing a payment-related operation before payment information is acquired. In this case, a first status is displayed indicating that the transaction is in the first state where the transaction is not supported , and the settlement device acquires the settlement information sent from the registration device and executes the settlement process. When in the second state of being in use, a second state display is displayed to indicate that the device is in the second state, and the payment device waits for the start of payment processing in a state where no payment-related operation is performed by the customer. when in a third state, the first computer functions as a display means for displaying a third state indicating that the third state is present ;
When the second program acquires the settlement information by reception in the first state, the second program converts the acquired settlement information into a transaction corresponding to a settlement-related operation performed under the first state. When the settlement information is acquired by reception in the third state, the acquired settlement information is made to correspond to a new transaction, and according to the settlement-related operation after acquiring the settlement information. causing the second computer to function as a payment means for executing payment processing;
program for.

Images