JP2021170415A - Registration device and control program therefor - Google Patents

Abstract

To eliminate the need for an information analysis function for monitoring a state of each settlement device by a registration device.SOLUTION: A registration device transmits accounting data together with a list indicating accounting data transfer order set among a plurality of settlement devices to any settlement device. The settlement device, when receiving the accounting data and the list, determines whether or not to be in a state capable of executing settlement of transaction. The settlement device, when being able to execute the settlement of the transaction, transmits a permission response to the registration device. The settlement device, when being unable to execute the settlement of the transaction, transfers the accounting data and the list to any other settlement device on the basis of the list.SELECTED DRAWING: Figure 7

Description

An embodiment of the present invention relates to a checkout system, a registration device and a payment device included in the system, and a control program for operating a computer as a registration device or a payment device.

As a checkout system for mass retailers, there is a type in which a registration device that generates accounting data necessary for settlement of the transaction for each transaction and a settlement device that processes the settlement of the transaction based on the accounting data are separated. .. The registration device waits for the input of data related to product sales. Then, when the data is input by the operator, the registration device generates accounting data based on the data and transmits the accounting data to the settlement device. The payment device listens for input of payment data for accounting data. Then, when the payment data is input by the operator, the payment device processes the settlement of the transaction based on the accounting data and the payment data. The checkout system of the type in which the registration device and the payment device are separated includes a two-person system in which the registration device and the payment device are operated by separate clerk, and a shopper who operates the registration device and the payment device is a shopper. There is a so-called semi-self system, which is a shared system operated by.

In the case of the semi-self method, if the shopper takes time to operate the payment device, the subsequent shoppers will wait for the payment. In order to avoid such a situation, usually, a plurality of payment devices are connected to one registration device. Then, the registration device monitors the status of each payment device, automatically selects a vacant payment device, and transmits the payment information to the payment device. Alternatively, the registration device displays the status of each payment device on the display, the clerk selects a vacant payment device, and the payment information is transmitted to the payment device.

However, in any case, in order for the registration device to monitor the status of each payment device, the registration device needs an information analysis function that collects and analyzes status information (status) from the payment device.

Japanese Unexamined Patent Publication No. 2013-242839

The problem to be solved by the embodiment of the present invention is to provide a checkout system in which the registration device can eliminate the information analysis function for monitoring the state of each payment device, and the registration device and the payment device used in this system. Is to be.

In one embodiment, the registration device is connected to a plurality of payment devices that execute payment processing for goods registered by the registration device via a network.
The registration device includes a transmitting means, a receiving means, and a notification means. The transmission means transmits the data required for the payment process and the list showing the data transfer order set between the plurality of payment devices to one of the payment devices via the network. The receiving means receives information indicating that payment is possible from one payment device that executes payment processing among the plurality of payment devices. The notification means notifies a payment device capable of executing payment processing based on the information received by the receiving means.

The schematic diagram of the checkout system in one Embodiment. A block diagram showing the main circuit configurations of the registration device and the payment device included in the checkout system. The schematic diagram which shows the main data memory area formed in each RAM of a registration device and a payment device. The schematic diagram which shows the main data memory area formed in the RAM of the registration apparatus and the auxiliary storage device. The flow chart which shows the main procedure of the information processing which the CPU of a registration apparatus executes according to a control program. The flow chart which shows the main procedure of the information processing which the CPU of a registration apparatus executes according to a control program. The flow chart which shows the main procedure of the information processing which the CPU of a payment apparatus executes according to a control program. The schematic diagram which shows an example of the registration screen displayed on the touch panel of a registration device. The schematic diagram which shows an example of the accounting confirmation screen displayed on the touch panel of a registration device. The schematic diagram which shows an example of the accounting confirmation screen when the accounting possible response is received. The schematic diagram which shows an example of the accounting confirmation screen when the non-accounting response is received. The schematic diagram which shows an example of the payment method selection screen displayed on the touch panel of a payment device. The schematic diagram which shows an example of the payment screen displayed on the touch panel of a payment device. The schematic diagram which shows an example of the completion screen displayed on the touch panel of a payment device.

Hereinafter, an embodiment of a checkout system in which the registration device can eliminate the need for an information analysis function for monitoring the status of each payment device will be described with reference to the drawings. In this embodiment, a semi-self-type checkout system in which a store clerk operates a registration device and a shopper operates a payment device is illustrated.

FIG. 1 is a schematic view of the checkout system 10 according to the present embodiment. The checkout system 10 includes a plurality of registration devices 11 and a payment device 12 having a larger number than the registration devices 11. The registration device 11 and the payment device 12 are arranged in each checkout lane of the store.

FIG. 1 shows a case where two registration devices 11 and six payment devices 12 are arranged in two checkout lanes. In FIG. 1, one registration device 11 and three payment devices 12 are arranged for one checkout lane. The number of checkout systems 10 including the registration device 11 and the payment device 12 is arbitrary. Further, the ratio of the number of registration devices 11 and the payment devices 12 arranged in the checkout lane is also arbitrary.

The operator of the registration device 11 is a clerk 21 who plays a role called a checker. The operator of the payment device 12 is a shopper 22 who purchases a product sold at a store. However, the payment device 12 may be operated by the clerk 21.

The registration device 11 is attached to the work table 23 in FIG. The work table 23 has a rectangular top plate. By arranging the plurality of work tables 23 so that the longitudinal directions of the top plates are substantially parallel to each other, a passage (checkout lane) for the shopper 22 is formed.

The registration device 11 includes functions of registering sales products, generating accounting data, transferring accounting data to the settlement device 12, and processing settlement. The registration of the product for sale means that the product purchased by the shopper 22 is registered in the registration device 11 as the product for sale. For example, by scanning the barcode attached to the product with a scanner, the product is registered in the registration device 11 as a product for sale. Accounting data is data related to the accounting of sales products registered as one transaction. The accounting data includes the product code, product name, unit price, quantity, amount, etc., which are the identification codes of the products for sale. The settlement process is to process the settlement of a transaction, which is an act of buying and selling goods, based on accounting data. For payment, cash, credit card, electronic money, etc. are used as payment.

The payment device 12 has a payment processing function. That is, when the accounting data is transferred from the registration device 11, the settlement device 12 processes the settlement of the transaction based on the accounting data.

FIG. 2 is a block diagram showing a main circuit configuration of the registration device 11 and the payment device 12. Both the registration device 11 and the payment device 12 are connected to a LAN (local area network) 13 which is a network. Although not shown, a server is connected to the LAN 13. The server has a product database in which product information such as product name and unit price is set in association with the product code of each product.

The registration device 11 and the payment device 12 exchange information via the LAN 13. As the network, another communication network such as the Internet or a wireless LAN may be used instead of the LAN 13. Further, information may be exchanged between the registration device 11 and the payment device 12 via a server.

The registration device 11 includes a CPU (central processing unit) 11a, a ROM (read-only memory) 11b, a RAM (random-access memory) 11c, an auxiliary storage unit 11d, a drawer opening unit 11e, a scanner 11f, and two touch panels 11g1, 11g2. , A printer 11h, a card reader / writer 11i, a communication unit 11j, and a transmission system 11k.

The CPU 11a is connected to the ROM 11b, the RAM 11c, and the auxiliary storage unit 11d via the transmission system 11k to form a computer.
The CPU 11a corresponds to the central part of the computer. The CPU 11a controls each unit to realize various functions as the registration device 11 based on the operating system, middleware, and application program stored in the ROM 11b and the RAM 11c.

The ROM 11b corresponds to the main storage portion of the computer. The ROM 11b stores the operating system. The ROM 11b may store the middleware or application program. The ROM 11b may store data that the CPU 11a refers to when performing various processes.

The RAM 11c corresponds to the main storage portion of the computer. The RAM 11c stores data that the CPU 11a refers to when performing various processes. The RAM 11c is also used as a so-called work area for storing data temporarily used by the CPU 11a for performing various processes.

The auxiliary storage unit 11d corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 11d stores data used by the CPU 11a to perform various processes or data generated by the processes in the CPU 11a. As the auxiliary storage unit 11d, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk drive), an SSD (solid state drive), or the like can be used.

The application program stored in the ROM 11b or the auxiliary storage unit 11d includes a control program described for information processing executed by the registration device 11. The transfer of the registration device 11 is generally performed in a state where the control program is stored in the ROM 11b or the auxiliary storage unit 11d. However, the registration device 11 may be transferred in a state where the control program is not stored in the ROM 11b or the auxiliary storage unit 11d. In this case, the control program is recorded and transferred to a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory. Alternatively, the control program may be transferred via the network, and the control program may be written to the auxiliary storage unit 11d of the separately transferred registration device 11 described above.

The drawer opening unit 11e automatically opens the drawer for accommodating money.
The scanner 11f reads the barcode attached to the product to obtain the product code of the product. As the scanner 11f, various well-known types can be used as they are. The scanner 11f may be compatible with only one of the various well-known types, or may be compatible with a plurality of types. That is, the scanner 11f may include a fixed or handy two-dimensional code scanner. Further, the scanner 11f may include a type of scanner that identifies a product from an image of the product by using an image recognition technique.

Of the two touch panels 11g1 and 11g2, one touch panel 11g1 is for a clerk and the other touch panel 11g2 is for a customer. The touch panels 11g1 and 11g2 both include a display device and a touch sensor. The display device has an arbitrary screen such as a GUI screen. As the display device, a well-known device such as a color LCD can be used. The touch sensor is arranged so as to overlap the display surface of the display device. The touch sensor detects the touch position of the operator on the display surface of the display device and sends the position information to the CPU 11a. A well-known device can be used as the touch sensor.

The touch panel 11g1 for the clerk is provided on the work table 23 so that the display screen faces the work space side of the clerk 21. The customer touch panel 11g2 is provided on the work table 23 so that the display screen faces the aisle side for the shopper 22.

The printer 11h issues a receipt by printing various character strings or images on the receipt paper. As the printer 11h of this type, for example, a thermal printer or a dot impact printer can be used.

The card reader / writer 11i has a function of reading data recorded on the card and a function of writing data to the card. The card may include a membership card called a member's card, a point card, or the like, in addition to a payment card such as a credit card, a debit card, an electronic money card, or a prepaid card. The card reader / writer 11i reads and rewrites the electronic money data (balance, etc.) stored in the electronic money card. The card reader / writer 11i may be any of magnetic, contact, or non-contact devices, and may include a plurality of types of devices.

The communication unit 11j performs data communication with a plurality of payment devices 12 connected via the LAN 13. The communication unit 11j can also perform data communication with another registration device 11 via the LAN 13.

The transmission system 11k transmits data exchanged between the CPU 11a, ROM 11b, RAM 11c, auxiliary storage unit 11d, drawer opening unit 11e, scanner 11f, touch panel 11g1, 11g2, printer 11h, card reader / writer 11i, and communication unit 11j. .. As the transmission system 11k, a well-known one including various buses such as a system bus and various interface circuits connecting these buses and each part can be used.

As the hardware of such a registration device 11, for example, an existing POS terminal can be used.

The payment device 12 includes a CPU 12a, a ROM 12b, a RAM 12c, an auxiliary storage unit 12d, an automatic change machine 12e, a scanner 12f, a touch panel 12g, a printer 12h, a card reader / writer 12i, a communication unit 12j, and a transmission system 12k.

The automatic change machine 12e collects the inserted coins and banknotes. Further, the automatic change machine 12e discharges coins and banknotes as change.

Other functions of the CPU 12a, ROM 12b, RAM 12c, auxiliary storage unit 12d, scanner 12f, touch panel 12g, printer 12h, card reader / writer 12i, communication unit 12j, and transmission system 12k are the CPU 11a, ROM 11b, RAM 11c, and auxiliary storage of the registration device 11. It is equivalent to the unit 11d, the touch panel 11g1, 11g2, the printer 11h, the card reader / writer 11i, the communication unit 11j, and the transmission system 11k.

That is, the CPU 12a is connected to the ROM 11b, the RAM 11c, and the auxiliary storage unit 11d via the transmission system 11k to form a computer. Then, the CPU 12a controls each unit in order to realize various operations as the payment device 12 based on the operating system, middleware, and application program stored in the ROM 12b and the RAM 12c.

The application program stored in the ROM 12b or the auxiliary storage unit 12d includes a control program described for information processing executed by the payment device 12. The transfer of the payment device 12 is generally performed with the control program stored in the ROM 12b or the auxiliary storage unit 12d. However, the payment device 12 may be transferred in a state where the control program is not stored in the ROM 12b or the auxiliary storage unit 12d. In this case, the control program is recorded and transferred to a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory. Alternatively, the control program may be transferred via the network, and the control program may be written to the auxiliary storage unit 12d of the separately transferred payment device 12 described above.

As the hardware of such a payment device 12, for example, an existing POS terminal compatible with the self-method can be used.

The checkout system 10 including the registration device 11 and the payment device 12 having such a configuration forms the data memory areas 31 and 32 shown in FIG. 3 in the RAMs 11c and 12c of the registration device 11 and the payment device 12, respectively.

The data memory area 31 is an area for storing data of products sold in one transaction. The data includes each item of product code, product name, unit price, quantity, and amount. The product code is a unique code for individually identifying each product. For example, a product code represented by a bar code is attached to each product, and the registration device 11 can acquire the product code by scanning the bar code with the scanner 11f. The product name and unit price are the product name and the price per item identified by the corresponding product code. The quantity is the number of units sold for the same product, and the amount is the amount of the quantity sold (sales amount). Hereinafter, the data memory area 31 is referred to as a transaction memory. Then, the one of the registration device 11 is represented by the transaction memory 31a, and the one of the settlement device 12 is represented by the transaction memory 31b.

The data memory area 32 is an area for storing the total number and the total amount of money. The total number is the total number of units sold stored in the transaction memory 31. The total amount is the total amount of sales stored in the transaction memory 31. Hereinafter, the data memory area 32 is referred to as a total memory. Then, the one of the registration device 11 is represented by the total memory 32a, and the one of the payment device 12 is represented by the total memory 32b.

Further, the checkout system 10 forms the data memory area 41 shown in FIG. 4 in the RAM 11c of the registration device 11, and forms the data memory area 42 in the auxiliary storage unit 11d of the registration device 11.

The data memory area 41 is an area for temporarily storing the product code, product name, unit price, quantity, and amount of one product for sale. Hereinafter, the data memory area 41 is referred to as a temporary buffer 41.

The data memory area 42 stores the settlement device ID and the identification name in association with a series of list numbers (accounting data transfer order) starting from "1". The payment device ID is a unique ID assigned to each payment device 12 in order to individually identify each payment device 12, and is stored in, for example, the ROM 12b. Incidentally, the same registration device ID is stored in the ROM 11b for each registration device 11. The identification name is a unique name individually set for each payment device 12. The operator of the registration device 11 can determine which payment device 12 is indicated from the identification name. Hereinafter, the data memory area 42 is referred to as a list table 42.

In the list number "1" of the list table 42, the payment device ID and the identification name of the payment device 12 installed at the location closest to the registration device 11 are preset, and the list number "2" is set to the list number "2". Is preset with a payment device ID and an identification name of the payment device 12 installed at the second closest location to the registration device 11. In this way, the transfer order of the accounting data is set in the order of the shortest distance from the registration device 11. It should be noted that such a setting is an example, and the transfer order does not necessarily have to be set in the order of the closest distance from the registration device 11.

5 and 6 are flow charts showing the main procedures of information processing executed by the CPU 11a of the registration device 11 according to the control program. FIG. 7 is a flow chart showing a main procedure of information processing executed by the CPU 12a of the payment device 12 according to the control program. 8 to 11 are schematic views showing various screen examples displayed on the touch panels 11g1 and 11g2 of the registration device 11. 12 to 14 are schematic views showing various screen examples displayed on the touch panel 12g of the payment device 12. Hereinafter, the operation of the checkout system 10 will be described with reference to these figures. The content of the process described below is an example, and various processes capable of obtaining similar results can be appropriately used.

The registration device 11 has a registration mode as one of the operation modes. When the registration device 11 is started in this registration mode, the CPU 11a starts the control process of the procedure shown in the flow chart of FIG. First, the CPU 11a initializes the RAM 11c (Act1). This initialization clears the transaction memory 31a, the total memory 32a, and the temporary buffer 41.

Next, the CPU 11a causes the registration screen SC1 (see FIG. 8) to be displayed on a part of the screen of the touch panel 11g (Act2).

The registration screen SC1 represents the contents of the temporary buffer 41, the transaction memory 31a, and the total memory 32a, and causes the clerk 21 to confirm the implementation status of the registration process. An example of the registration screen SC1 is shown in FIG. The registration screen SC1 includes display areas R1 and R2. In the display area R1, a display column r11 for displaying the product name and unit price of the most recently registered product, a display column r12 for displaying the quantity, and a display column r13 for displaying the amount of money are displayed as one transaction. A display column r14 is formed in which the total number of products registered for sale and the total amount of money are displayed. In the display area R2, a list of product names, quantities, unit prices, and amounts of products registered for sale prior to the products shown in the display area R1 is formed.

Although not shown, the CPU 11a is a product button for the clerk 21 to specify a product and a subtotal output for the clerk 21 outside the area of the touch panel 11g screen to be the registration screen SC1. Various function buttons such as the subtotal button are also displayed.

After confirming that the registration screen SC1 is displayed on the touch panel 11g, the clerk 21 recognizes that the product purchased by the shopper 22 can be registered. Then, when the shopper 22 comes to the work table 23 with the purchased product, the clerk 21 operates, for example, the scanner 11f or the product button to sequentially input the product code of the product. Then, when the product codes of all the products are input, the clerk 21 touches the subtotal button. By the above operation, the registration of the product purchased by one shopper (sales registration of one transaction) is completed.

In response to such a registration operation, the CPU 11a of the registration device 11 executes the following information processing. First, the CPU 11a displaying the registration screen SC1 waits for the input of the product code (Act3). When the product code is input via the scanner 11f or the product button (YES in Act 3), the CPU 11a acquires the product information such as the product name and the unit price associated with the product code and set in the product database. .. Further, the CPU 11a multiplies this unit price by the number of pieces to calculate the amount of money for the number of pieces. The number is a numerical value when the product code is placed by the numeric keypad or the like before the product code is input, and is "1" when the product code is not placed. In this way, when the CPU 11a generates the product sales data including the product code, the product name, the unit price, the quantity and the amount of money, the CPU 11a stores the product sales data in the temporary buffer 41 (Act 4). At this time, if the product sales data is already stored in the temporary buffer 41, the CPU 11a moves the stored product sales data to the transaction memory 31, and then stores the new product sales data in the temporary buffer 41. Store in.

The CPU 11a adds the number and amount of money stored in the temporary buffer 41 to the total memory 32a. Then, the CPU 11a updates the registration screen SC1 so that the contents of the temporary buffer 41 and the total memory 32a are displayed in the display area R1 and the contents of the transaction memory 31a are displayed in the display area R2 (Act 5).

After updating the registration screen SC1, the CPU 11a confirms whether or not the next product code has been input (Act 6). If the product code has not been entered (NO in Act 6), the CPU 11a confirms whether or not the subtotal button has been touched (Act 7). When the subtotal button is not touched (NO in Act7), the CPU 11a confirms whether or not the product code has been input again (Act6). Thus, the CPU 11a waits for the product code to be input or the subtotal button to be touched as Act 6 and Act 7. When the CPU 11a confirms the occurrence of another event such as another operation being performed in this standby state, the CPU 11a shifts to the process according to the occurrence event. Such an operation is the same in other standby states.

When the product code is input in the standby state of Act6 and Act7 (YES in Act6), the CPU 11a proceeds to the process of Act4. Then, the CPU 11a repeats the subsequent processing in the same manner as described above.

If the subtotal button is touched in the standby state of Act6 and Act7 (YES in Act7), the CPU 11a executes the processing of Act8 and Act9. The processing procedure of Act8 and Act9 is not limited to this order. The order may be changed.

In Act 8, the CPU 11a moves the product sales data stored in the temporary buffer 41 to the transaction memory 31. Then, the CPU 11a generates accounting data from the data of the transaction memory 31a and the data of the total memory 32a (generation means). In Act9, the CPU 11a causes the accounting confirmation screen SC2 (see FIG. 9) to be displayed on a part of the screen of the touch panel 11g.

An example of the accounting confirmation screen SC2 is shown in FIG. The accounting confirmation screen SC2 includes a display area R3 and buttons B1, B2, B3, and B4. The display area R3 displays the total number of the total memory 32a, the total amount, and the like. Buttons B1 and B2 are a subtotal discount button B1 and a subtotal discount button B2 for the clerk 21 to specify that a discount or discount is applied to the total amount. The button B3 is a return button B3 for the clerk 21 to specify that a part of the screen area of the touch panel 11g is returned to the registration screen SC1. Button B4 is an accounting button B4 for the clerk 21 to instruct the clerk 21 to complete the registration of the product for one transaction and shift to accounting.

The CPU 11a displaying the accounting confirmation screen SC2 confirms whether or not the accounting button has been input (Act 10). When the checkout button is not input (NO in Act10), the CPU 11a confirms whether or not the return button B3 is input (Act11). If the back button B3 has not been input (NO in Act 11), the CPU 11a again confirms whether or not the accounting button has been input (Act 10). Thus, the CPU 11a waits for the accounting button B4 or the back button B3 to be input as Act10 and Act11.

The clerk 21 who has confirmed the accounting confirmation screen SC2 confirms whether or not the product purchased by the shopper 22 remains registered. If it remains, the clerk 21 touches the back button B3. If there are no remaining items, the clerk 21 touches the checkout button B4.

When the back button B3 is input in the standby state of Act10 and Act11 (YES in Act11), the CPU 11a returns a part of the screen area of the touch panel 11g to the registration screen SC1 (Act12). After that, the CPU 11a proceeds to the process of Act6, and the subsequent processes are repeated in the same manner as described above.

When the accounting button B4 is touched in the standby state of Act10 and Act11 (YES in Act10), the CPU 11a proceeds to the process of Act13 in FIG. That is, the CPU 11a reads the list of IDs and identification names of the payment device 12 from the list table 42 (Act 13). Next, the CPU 11a detects the payment device ID of the list number “1” from the list table 42 (Act 14). Then, the CPU 11a instructs the communication unit 11j to transmit the accounting data generated in the process of Act 8 and the list data acquired in the process of Act 13 to the settlement device ID of the list number “1” (Act 15). In response to this command, the communication unit 11j transmits "accounting data + list data" to the settlement device ID of the list number "1" and the registration device ID stored in the ROM 11b as the transmission source on the LAN 13. .. This "accounting data + list data" is received by the payment device 12 whose destination payment device ID matches the payment device ID stored in the ROM 12b. Here, the CPU 11a cooperates with the communication unit 11j to form a transmission means.

When the CPU 12a of each payment device 12 receives "accounting data + list data" via the communication unit 12j, does the payment device ID added to the data as a transmission destination match the payment device ID stored in the ROM 12b? Check. If they do not match, the CPU 12a discards the "accounting data + list data". If they match, the CPU 12a takes in "accounting data + list data". Then, the CPU 12a starts the reception interrupt process specifically shown in FIG. 7. Here, the CPU 12a cooperates with the communication unit 12j to form a receiving means.

When the reception interrupt process is started, the CPU 12a first checks the busy flag F (Act 21). The busy flag F is 1-bit data that is set to "1" while the CPU 12a is processing the settlement of the transaction based on the accounting data, and is reset to "0" when the processing is completed, and is stored in the RAM 12c. There is. As described above, while the busy flag F is set, the settlement device 12 is executing the settlement of the transaction. Therefore, the payment device 12 cannot settle a new transaction. Here, the CPU 12a constitutes a determination means for determining whether or not the settlement of the transaction can be executed by the processing of Act21.

When the busy flag F is reset, that is, when the settlement device 12 is in a state where the settlement of the transaction can be executed (YES in Act 21), the CPU 12a executes the processes of Act 22, Act 23, and Act 24. The processing procedure of Act22, Act23 and Act24 is not limited to this order. The order may be changed.

In Act22, the CPU 12a sets the busy flag F to "1".
In Act23, the CPU 12a instructs the communication unit 12j to transmit the command data of the accountable response to the registration device 11 of the data transmission source. In response to this command, the communication unit 12j receives the command data of the accountable response whose destination is the registration device ID set as the source of the "accounting data + list data" and whose source is the settlement device ID stored in the ROM 12b. Is transmitted on the LAN 13. This command data is received by the registration device 11 whose destination registration device ID matches the registration device ID stored in the ROM 11b. Here, the CPU 12a cooperates with the communication unit 12j to form a license response means.

In Act24, the CPU 12a executes accounting processing based on the received accounting data (processing means). The accounting process will be described later. When the accounting process is completed, the CPU 12a resets the busy flag F to “0” (Act25).
This completes the reception interrupt processing of "accounting data + list data" with the busy flag F reset.

On the other hand, when the busy flag F is set, that is, when the settlement device 12 is in a state where the settlement of the transaction cannot be executed (NO in Act 21), the CPU 12a searches the received list data (Act 26). .. Then, the CPU 12a confirms whether or not the payment device ID stored in the ROM 12b is associated with the final list number of the list data (Act 27).

When the payment device ID is not associated with the final list number (NO in Act27), the CPU 12a adds "1" to the list number associated with the payment device ID stored in the ROM 12b from the list data. Detects the payment device ID associated with (Act 28). Then, the CPU 12a instructs the communication unit 12j to transfer the "accounting data + list data" to the detected payment device ID (Act 29). In response to this command, the communication unit 12j transmits "accounting data + list data" to the LAN 13 with the detected payment device ID as the destination and the registration device ID indicating the source as it is. This "accounting data + list data" is received by the payment device 12 whose destination payment device ID matches the payment device ID stored in the ROM 12b. Here, the CPU 12a cooperates with the communication unit 12j to form a transfer means.

On the other hand, when the payment device ID is associated with the final list number (maximum value of the list number) (YES in Act27), the CPU 12a responds unaccountably to the data transmission source registration device 11. Instruct the communication unit 12j to transmit command data. In response to this command, the communication unit 12j receives the command data of the non-accounting response whose destination is the registration device ID set as the source of the "accounting data + list data" and whose source is the settlement device ID stored in the ROM 12b. Is transmitted on the LAN 13. This command data is received by the registration device 11 whose destination registration device ID matches the registration device ID stored in the ROM 11b. Here, the CPU 12a cooperates with the communication unit 12j to form an error response means.
This completes the reception interrupt processing of "accounting data + list data" with the busy flag F set.

The CPU 11a of the registration device 11 that has transmitted the "accounting data + list data" in Act 15 of FIG. 6 waits for a response from the settlement device 12 (Act 16). When the command data indicating the response is received via the communication unit 11j (YES in Act 16), the CPU 11a identifies whether the command data is an accountable response or an unaccountable response (Act 17).

In the case of an accountable response (YES in Act 17), the CPU 11a searches the list table 42 and reads out the identification name stored in association with the payment device ID that is the source of the command data. Then, as shown in FIG. 10, the CPU 11a causes a part of the area R4 of the accounting confirmation screen SC2 to display a message indicating that the settlement device 12 having this identification name is ready for accounting (Act 18). The clerk who confirms this message notifies the shopper to perform the checkout with the payment device 12 specified from the identification name.

On the other hand, in the case of a non-accounting response (NO in Act17), the CPU 11a sends a message indicating that the accounting data could not be transmitted to a part area R5 of the accounting confirmation screen SC2 as shown in FIG. Display (Act 19). After that, the CPU 11a executes the transmission disabling process.

For example, the non-transmission processing waits for the accounting button B4 to be input again, and if it is input, the processing after Act 13 is executed again. In this case, the clerk who confirms the message touches the checkout button B4.

In the non-transmission processing, for example, the accounting data is transmitted to the server with a unique identification code, and the printer 11h is driven to issue an accounting ticket on which a barcode indicating the identification code is printed. In this case, the clerk who confirms the message hands the accounting ticket to the shopper. For example, the shopper has the scanner 12f of the payment device 12 prepared at a place other than the chuck out lane read the barcode of the accounting ticket. Then, the CPU 12a of the payment device 12 acquires the accounting data attached with the identification code obtained from the barcode from the server. Then, the CPU 12a executes the processes of Act22, Act24, and Act25 of FIG. 7 based on the accounting data.

In this way, the clerk 21 registers the product purchased by the shopper 22 with the registration device 11. When the registration is completed, the clerk 21 touches the checkout button B4 on the checkout confirmation screen SC2. Then, the accounting data necessary for the settlement of the transaction with the shopper 22 is transmitted together with the list data of the list table 42. The destination of this "accounting data + list data" is the payment device 12 (referred to as payment device 12-1) identified by the payment device ID of the list number "1".

Here, if the settlement device 12-1 can execute the settlement of the transaction (visit flag F = 0), the settlement device 12-1 transmits the command data of the accountable response to the registration device 11. As a result, on the checkout confirmation screen SC2 of the registration device 11, a message indicating that the checkout is ready is displayed together with the identification name representing the settlement device 12-1, so that the clerk 21 tells the shopper 22. Announce to pay with the payment device 12-1.

On the other hand, if the settlement device 12-1 cannot execute the settlement of the transaction (visit flag F = 1), the "accounting data + list data" is transferred from the settlement device 12-1 to the other settlement device 12. NS. The transfer destination is the payment device 12 (referred to as payment device 12-2) identified by the payment device ID of the list number “2”.

Here, if the settlement device 12-2 can execute the settlement of the transaction (visit flag F = 0), the settlement device 12-2 transmits the command data of the accountable response to the registration device 11. As a result, on the accounting confirmation screen SC2 of the registration device 11, a message indicating that the accounting is ready is displayed together with the identification name indicating the payment device 12-2, so that the clerk 21 tells the shopper 22. Announce to pay with the payment device 12-2.

On the other hand, if the settlement device 12-2 cannot execute the settlement of the transaction (visit flag F = 1), the "accounting data + list data" is transferred from the settlement device 12-2 to the other settlement device 12. NS. The transfer destination is the payment device 12 (referred to as payment device 12-3) identified by the payment device ID of the list number “3”.

Here, if the settlement device 12-3 can execute the settlement of the transaction (visit flag F = 0), the settlement device 12-3 transmits the command data of the accountable response to the registration device 11. As a result, on the accounting confirmation screen SC2 of the registration device 11, a message indicating that the accounting is ready is displayed together with the identification name indicating the payment device 12-3, so that the clerk 21 tells the shopper 22. Announce to pay with the payment device 12-3.

On the other hand, if the settlement device 12-3 cannot execute the settlement of the transaction (visit flag F = 1), the settlement of the transaction is made by all three settlement devices 12-1, 12-2, 12-3. Is impossible. In this case, the settlement device 12-3 transmits the non-accountable response command data to the registration device 11. As a result, a message that transmission is not possible is displayed on the checkout confirmation screen SC2 of the registration device 11, and the clerk 21 touches the checkout button B4 again. Alternatively, since the accounting ticket is issued together with the message that the transmission is not possible, the clerk 21 hands the accounting ticket to the shopper 22.

The shopper 22 who has been notified by the clerk 21 to perform accounting with any of the payment devices 12 moves to the location of the payment device 12. At this time, the settlement device 12 has started the accounting process. When the accounting process starts, the payment device 12 displays the payment method selection screen SC3 (see FIG. 12) on a part of the screen of the touch panel 12g.

FIG. 12 shows an example of the payment method selection screen SC3. The payment method selection screen SC3 includes display areas R11 and R12 and buttons B11 and B12. The display area R11 displays operation guidance for the shopper 22 who operates the payment device 12. The display area R12 displays the total number and the total amount of money stored in the total memory 32b. The button B11 is a payment method button B11 for the shopper to specify one of the payment methods from the plurality of payment methods. The button B12 is a clerk call button B13 for the shopper 22 to specify to call the clerk 21.

In the present embodiment, cash, credit card, and electronic money are exemplified as payment methods, but the payment methods are not limited to these. Other payment methods may be added. Moreover, any payment method may be omitted.

The shopper 22 who has confirmed the payment method selection screen SC3 determines the payment method of the price and touches the payment method button B11. When the payment method button B11 is touched, the payment device 12 displays the payment screen SC4 (see FIG. 13) of the payment method selected by the payment method button B11 on a part of the screen of the touch panel 12g.

An example of the payment screen SC4 is shown in FIG. FIG. 13 is a payment screen SC4 when cash is selected as the payment method. The payment screen SC4 includes display areas R13, R14 and button B13. The display area R13 displays operation guidance for the shopper 22 who operates the payment device 12. The display area R14 displays the total amount, the input amount, and the remaining amount. The button B13 is a settlement button B13 for the shopper who has finished inserting cash to specify the execution of the settlement.

A shopper who selects cash as the payment method inserts cash into the automatic change machine 12e. Then, when the total amount of cash or more is inserted, the settlement button B13 is touched. When the payment button B13 is touched, the payment device 12 executes the payment process by the selected payment method. Since such payment processing is well known, detailed description thereof will be omitted.

When the payment process is completed, the payment device 12 displays the completion screen SC5 (see FIG. 14) on a part of the screen of the touch panel 12g.

FIG. 14 shows an example of the completion screen SC5 for cash payment. The completion screen SC5 includes display areas R15, R16, and R17. The display area R15 displays operation guidance for the shopper 22 who operates the payment device 12. The display area R16 displays a guide image. The guide image is an image that guides the shopper 22 to the receipt issuing port and the change payment exit. Therefore, the shopper can easily know the place where the receipt is issued and the place where the change is paid out from this guide image. The display area R16 displays the amount of change. Therefore, the shopper can know the change amount from the data of the display area R16.

The shopper who confirms the completion screen SC8 receives the receipt and the change according to the guide image. In response to this, in the settlement device 12, the busy flag F is reset to "0", and the accounting standby state is set.

As described above, according to the present embodiment, the registration device 11 may transmit the accounting data to the payment device 12 set in the list number "1" regardless of the state of each payment device 12. Therefore, the information analysis function for the registration device 11 to monitor the state of each payment device 12 is unnecessary.

The present invention is not limited to the above embodiment.
For example, in the above embodiment, the registration device 11 may have a data (settlement device ID / identification name) setting mode for the list table 42, and the data in the list table 42 may be arbitrarily changed. In the case of the above embodiment, since the accounting data is first transmitted to the settlement device 12 set in the list number “1”, the settlement of the transaction is frequently processed by the settlement device 12. Therefore, by changing the data in the list table 42 at an appropriate timing, it is possible to equalize the frequency with which the settlement of transactions is processed.

Further, it goes without saying that the screens SC1, SC2, SC3, SC4, and SC5 illustrated and described in the above embodiment are merely examples and are not limited to the layout shown in the illustration.

In addition, although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof.
The inventions described in the claims of the original application of the present application are described below.
[1] Checkout made by connecting a registration device that generates accounting data necessary for settlement of a transaction for each transaction and a plurality of settlement devices that process settlement of the transaction based on the accounting data via a network. In the system, the registration device is a transmission means for transmitting the accounting data to any of the payment devices via the network together with a list showing the accounting data transfer order set between the plurality of payment devices. The payment device is provided with a notification means for notifying information identifying the payment device from which the permission response is transmitted in response to receiving a permission response from any of the payment devices via the network. Is a receiving means for receiving the accounting data and the list via the network, a determining means for determining whether or not the settlement of the transaction can be executed, and a state in which the settlement of the transaction can be executed. When the accounting data and the list are received, the permission response means for transmitting the permission response to the registration device via the network, and the accounting data and the list in a state in which the settlement of the transaction cannot be executed. A checkout system comprising: a transfer means for transferring the accounting data and the list to any other payment device via the network based on the list.
[2] When the settlement device receives the accounting data and the list in a state in which the settlement of the transaction cannot be executed, all the other settlement devices are also in a state in which the settlement of the transaction cannot be executed. Further including an error response means for transmitting an error response to the registration device via the network, the registration device receives the error response from any of the payment devices via the network. Then, the checkout system according to the appendix [1], further comprising a notification means for notifying an error.
[3] For any of the generation means for generating accounting data necessary for settlement of the transaction for each transaction and a plurality of settlement devices for processing the settlement of the transaction based on the accounting data, the above-mentioned A transmission means for transmitting accounting data via a network together with a list indicating an accounting data transfer order set between the plurality of payment devices, and a permission response received from any of the payment devices via the network. A registration device comprising: a notification means for notifying information identifying the payment device from which the permission response is transmitted.
[4] Receive a list showing the accounting data and the accounting data transfer order set between the plurality of settlement devices via the network from the registration device that generates the accounting data necessary for the settlement of the transaction for each transaction. A receiving means for processing, a processing means for processing the settlement of the transaction based on the accounting data, a determining means for determining whether or not the settlement of the transaction can be executed, and a state in which the settlement of the transaction can be executed. When the accounting data and the list are received in the above, the permission response means for transmitting the permission response to the registration device via the network, and the accounting data and the list in a state where the settlement of the transaction cannot be executed. A payment device comprising: a transfer means for transferring the accounting data and the list to any other payment device via the network based on the list.
[5] For the computer of the registration device that generates the accounting data necessary for the settlement of the transaction for each transaction, for any of the settlement devices among the plurality of settlement devices that process the settlement of the transaction based on the accounting data. , A function of transmitting the accounting data via a network together with a list indicating an accounting data transfer order set between the plurality of payment devices, and receiving a permission response from any of the payment devices via the network. A control program for realizing a function of notifying information identifying the payment device of the permission response transmission source according to the request.
[6] Receives the accounting data and a list showing the accounting data transfer order set between the plurality of settlement devices via the network from the registration device that generates the accounting data necessary for the settlement of the transaction for each transaction. A function of causing a computer of a payment device provided with a receiving means to process the settlement of the transaction based on the accounting data, a function of determining whether or not the settlement of the transaction is feasible, and a settlement of the transaction. When the accounting data and the list are received in a state in which the transaction can be executed, the function of causing the registration device to send a permission response via the network, and the accounting data and the above in a state in which the settlement of the transaction cannot be executed. A control program for realizing a function of transferring the accounting data and the list to any other payment device via the network based on the list when the list is received.

11 ... Registration device, 12 ... Payment device, 11a, 12a ... CPU, 11b, 12b ... ROM, 11c, 12c ... RAM, 11d, 12d ... Auxiliary storage unit, 11e ... Drawer opening unit, 12e ... Automatic change machine, 11f, 12f ... Scanner, 11g1,11g2,12g ... Touch panel, 11h, 12h ... Printer, 11i, 12i ... Card reader / writer, 11j, 12j ... Communication unit, 11k, 12k ... Transmission system, 13 ... LAN, 31 (31a, 31b) ... transaction memory, 32 (32a, 32b) ... total memory, 41 ... temporary buffer, 42 ... list table.

Claims (5)

A registration device for registering products and a plurality of payment devices for executing payment processing for products registered by the registration device are connected by a network, and the payment device cannot execute the payment processing. When the data required for the payment process and the list indicating the data transfer order set between the plurality of payment devices are received in the state, another payment device is required for the payment process according to the data transfer order. Data and the list are transferred, and when the data required for the payment process and the list are received in a state where the payment process can be executed, information indicating that payment can be made to the registration device is sent to the registration device. The registration device of the checkout system to be transmitted.
A transmission means for transmitting the data required for the payment process and the list to any of the payment devices via the network.
A receiving means for receiving information indicating that payment is possible from one payment device that executes the payment processing among the plurality of payment devices.
A notification means for notifying the payment device capable of executing the payment process based on the information received by the reception means, and
A registration device comprising. When the data transfer order of the payment device indicated in the list received in a state where the payment processing cannot be executed is the lowest, the payment processing is performed by all of the plurality of payment devices in the registration device. Send information indicating that it is not executable
The receiving means includes means for receiving information indicating that the payment process cannot be executed by all of the plurality of payment devices.
A notification means for notifying an error when the information received by the reception means is information indicating that the payment process cannot be executed.
The registration device according to claim 1, further comprising. Equipped with a display device for displaying a screen showing the contents of the registered product
The registration device according to claim 1 or 2, wherein the notification means notifies by displaying information identifying the payment device capable of executing the payment process on the display device. The registration device according to any one of claims 1 to 3, wherein the transmission means transmits data necessary for the payment process and the list to the payment device having the highest data transfer order as a transmission destination. .. A registration device for registering products and a plurality of payment devices for executing payment processing for products registered by the registration device are connected by a network, and the payment device cannot execute the payment processing. When the data required for the payment process and the list indicating the data transfer order set between the plurality of payment devices are received in the state, another payment device is required for the payment process according to the data transfer order. Data and the list are transferred, and when the data required for the payment process and the list are received in a state where the payment process can be executed, information indicating that payment can be made to the registration device is sent to the registration device. To the computer of the registration device of the checkout system to send
A function of transmitting the data required for the payment process and the list to any of the payment devices via the network, and
A function of receiving information indicating that payment is possible from one of the plurality of payment devices that executes the payment process, and
A function of notifying the payment device capable of executing the payment process based on the received information, and
Control program to realize.

Images