Product sales data processing system, product sales data processing method, settlement device, and program

Abstract

To efficiently correct a registered commodity.SOLUTION: A commodity sales data processing device operable by a customer, includes: change reception means for receiving a change in commodity information indicating a commodity registered in one transaction from the customer; approval input means for receiving an approval result by a clerk for the change in the commodity information received by the change reception means; and commodity information change means for changing the commodity information when the approval result is input from the approval input means.SELECTED DRAWING: Figure 26

Description

[Technical field]

[0001] The present invention ,quotient Product sales data processing system, product sales data processing method, payment device, and programs. [Background technology]

[0002] Convenience stores, supermarkets, and other stores are equipped with product sales data processing devices (e.g., POS registers) that register products. In recent years, product sales data processing devices that allow customers to register products and make payments themselves have become widespread. In such product sales data processing devices, if a customer mistakenly registers a product, the data is corrected (changed).

[0003] A related technology has been proposed, which is an order registration processing device used in restaurants and other establishments, which, when a customer inputs an instruction to check room availability, queries a server about the room usage status and displays the room usage status received from the server (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0005] However, when correcting a registered product, for example, the correction operation is performed by a store clerk from the viewpoint of preventing fraud. Therefore, when a correction is required, the customer must call a store clerk and wait for the store clerk to complete the correction operation, which may waste time. In addition, for example, the correction operation may take time for the store clerk, which may interfere with other work and lead to a decrease in work efficiency. Therefore, the conventional technology has a problem that it may not be possible to efficiently correct registered products.

[0006] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a technique that enables registered products to be corrected efficiently. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, one aspect of the present invention is a product sales data processing system including a terminal device carried by a customer to register products, and a settlement device to settle payments for products registered by the terminal device, the terminal device having a change acceptance means for accepting, from the customer, a change to product information indicating products registered in one transaction by accepting an operation from the customer, and the settlement device: a payment means for performing payment for the registered product based on an operation by a customer when the change acceptance means does not accept the change to the product information; Depending on the change acceptance method Before Changes to product information If accepted, an approval input means for inputting an approval result by a store clerk; and a product information change means for changing the product information in response to the approval result being input by the approval input means. The payment means performs payment for the product indicated by the product information changed by the product information change means based on an operation by the customer. The present invention relates to a product sales data processing system.

[0008] According to the above configuration, it is possible to efficiently correct (change) registered products.

[0009] In order to solve the above-mentioned problems, another aspect of the present invention is a merchandise sales data processing method for a merchandise sales data processing system including a terminal device carried by a customer for registering merchandise and a settlement device for settling payments for merchandise registered by the terminal device, the terminal device receiving an operation from the customer and receiving, from the customer, a change acceptance step of accepting a change to merchandise information indicating merchandise registered in one transaction. Processing including The settlement device executes the change acceptance In steps a first settlement step of settling the registered product based on a customer's operation if the change to the product information is not accepted; an approval input step of inputting an approval result by a store clerk if the change to the product information is accepted in the change acceptance step; a product information change step of changing the product information by inputting the approval result in the approval input step; Leave A second method of making a payment for the product indicated by the changed product information based on an operation of the customer. of and a checkout step.

[0010] According to the above configuration, it is possible to efficiently correct registered products.

[0011] In order to solve the above-mentioned problems, a payment device according to another aspect of the present invention is a device carried by a customer to register products. At the same time, by accepting an operation from the customer, a change in product information indicating a product registered in one transaction is accepted from the customer. A payment device of a product sales data processing system including a terminal device and a payment device for performing payment for products registered by the terminal device, a payment means for performing payment for the registered product based on a customer's operation when the change in the product information is not accepted by the terminal device; The terminal device By Changes to the above product information If accepted an approval input means for inputting an approval result by a store clerk; and a product information change means for changing the product information in response to the approval result being input by the approval input means, The settlement means settles the account for the product indicated by the product information changed by the product information change means based on an operation by the customer. The settlement device is characterized by the above.

[0012] According to the above configuration, it is possible to efficiently correct registered products.

[0013] In order to solve the above-mentioned problems, another aspect of the present invention is a program that a customer carries to register a product. At the same time, by accepting an operation from the customer, a change in product information indicating a product registered in one transaction is accepted from the customer. A program for causing a computer to function as a settlement device of a product sales data processing system including a terminal device and a settlement device for settling a product registered by the terminal device, the program comprising: a payment means for performing payment for the registered products based on a customer's operation when the change in the product information is not accepted by the terminal device; The terminal device By Changes to the above product information If accepted an approval input means for inputting an approval result by a store clerk, and a product information changing means for changing the product information by inputting the approval result by the approval input means; The settlement means settles the account for the product indicated by the product information changed by the product information change means based on an operation by the customer. This is a program characterized by the following:

[0014] According to the above configuration, it is possible to efficiently correct registered products. Effect of the Invention

[0018] As described above, according to the present invention, correction of registered products can be efficiently carried out. [Brief description of the drawings]

[0019] [Figure 1] 1 is a network configuration diagram of a POS system according to a first embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram illustrating an example of an installation of a POS terminal. [Diagram 3] FIG. 1 is a diagram illustrating an example of the appearance of a POS terminal. [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a POS terminal. [Diagram 5] FIG. 2 is a diagram for explaining an outline of operation modes of the POS terminal. [Figure 6] FIG. 13 is a diagram illustrating switching of operation modes of a POS terminal. [Figure 7] FIG. 4 is a schematic diagram for explaining an outline of operation in a normal mode. [Figure 8] 10 is a flowchart outlining an operation in a normal mode. [Figure 9]FIG. 4 is a schematic diagram for explaining an outline of operation in a normal mode. [Figure 10] 10 is a flowchart for explaining an outline of an operation in a normal mode. [Figure 11] FIG. 13 is a schematic diagram for explaining an outline of the operation in a full self mode. [Figure 12] 10 is a flowchart outlining an operation in a full self mode. [Figure 13] FIG. 11 is a schematic diagram for explaining an outline of the operation in a double scan mode. [Figure 14] 11 is a flowchart outlining an operation in a double scan mode. [Figure 15] 13 is a display example of a POS terminal in full self-service mode. [Figure 16] 13 is a display example of a POS terminal in full self-service mode. [Figure 17] 13 is a display example on the POS terminal 20 in the normal mode. [Figure 18] 13 is a display example on the POS terminal 20 in the normal mode. [Figure 19] 13 is a display example on the POS terminal 20 in the normal mode. [Figure 20] 13 is a display example on the POS terminal 20 in the normal mode. [Figure 21] 13 is a display example on the POS terminal 20 in the normal mode. [Figure 22] 13 is a display example on the POS terminal 20 in the normal mode. [Diagram 23] FIG. 13 is an explanatory diagram showing an overview of advertisement display in a full self mode. [Figure 24] FIG. 11 is an explanatory diagram illustrating an example of an advertisement information table. [Diagram 25] FIG. 13 is an explanatory diagram showing an example of a screen transition when correcting a registered product in the full self-service mode. [Figure 26] FIG. 13 is an explanatory diagram showing an example of a screen transition when correcting a registered product in the full self-service mode. [Figure 27]FIG. 13 is an explanatory diagram showing an example of a screen transition when correcting a registered product in the full self-service mode. [Figure 28] FIG. 13 is an explanatory diagram showing another example of a screen when correcting a product in the full self-service mode. [Figure 29] 13 is a flowchart showing an example of a product registration process in a full self-service mode performed by the POS terminal 20. [Diagram 30] 13 is a flowchart showing an example of a product correction process performed by the POS terminal 20 in a full self-service mode. [Diagram 31] FIG. 13 is an explanatory diagram showing an example of a transition of a screen on the customer side when correcting a product in the semi-self-service mode. [Diagram 32] FIG. 13 is an explanatory diagram showing an example of a transition of a screen on the customer side when correcting a product in the semi-self-service mode. [Diagram 33] FIG. 13 is an explanatory diagram showing an example of a transition of a screen on the store clerk display unit 210 of the upstream POS terminal 20 when correcting a product. [Diagram 34] FIG. 13 is an explanatory diagram showing another example of a screen when correcting a product in the semi-selfie mode. [Diagram 35] FIG. 13 is an explanatory diagram showing another example of a screen when correcting a product in the semi-selfie mode. [Diagram 36] FIG. 13 is an explanatory diagram showing another example of a screen when correcting a product in the semi-selfie mode. [Figure 37] 13 is a flowchart showing an example of a settlement process in semi-self-service mode performed by a downstream POS terminal 20 (settlement device). [Figure 38] 13 is a flowchart showing an example of a process performed by an upstream POS terminal 20 (registration device) when an approval request is received. [Figure 39] FIG. 11 is a network configuration diagram showing a shopping system according to a second embodiment of the present invention. [Diagram 40] 2 is an explanatory diagram showing an example of various information managed by the cloud server 300. FIG. [Diagram 41] FIG. 11 is a sequence diagram showing a processing flow of a shopping system according to a second embodiment. [Diagram 42] FIG. 11 is an explanatory diagram showing an example of a screen transition when canceling a product in the second embodiment. [Diagram 43] FIG. 11 is an explanatory diagram showing an example of a screen transition when accepting a change in the quantity of a product in the second embodiment. [Diagram 44] FIG. 11 is an explanatory diagram showing an example of a settlement screen in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] (Embodiment 1) Fig. 1 is a network configuration diagram of a POS (Point Of Sales) system according to a first embodiment of the present invention. The POS system 1 shown in Fig. 1 includes three POS terminals 20-1, 20-2, and 20-3, and a store controller (store computer, management device) 10, which are communicatively connected via a LAN 11. Hereinafter, the POS terminals 20-1, 20-2, and 20-3 will be collectively referred to as the POS terminal 20 unless otherwise specified. The POS system 1 may further include a monitoring terminal (not shown) that displays the status of the POS terminal 20 (operation mode, processing status, etc.) and controls the POS terminal 20.

[0021] The POS system 1 can be introduced into various stores (convenience stores, supermarkets, etc.).

[0022] Fig. 2 is a diagram showing an example of installation of the POS terminal 20. Fig. 2(A) is a perspective view of the POS terminal 20, etc., as seen from the customer side. Fig. 2(B) is a perspective view of the POS terminal 20, etc., as seen from the store clerk side. As shown in Fig. 2(A), a counter is placed to the right of the POS terminal 20 as seen from the customer side.

[0023] Fig. 3 is a diagram showing an example of the appearance of the POS terminal 20. Fig. 3(A) is a perspective view of the POS terminal 20 as seen from the customer side. Fig. 3(B) is a perspective view of the POS terminal 20 as seen from the store clerk side. Fig. 4 is a diagram showing an example of the configuration of the POS terminal 20. In Fig. 3 and Fig. 4, the same parts are given the same symbols.

[0024] An example of the configuration of the POS terminal 20 shown in Fig. 4 will be described below with reference to Fig. 3. The POS terminal 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer display unit 205, a customer scanner unit 206, a card payment unit 208, a change dispenser 209, a store clerk display unit 210, a key operation unit 211, a store clerk scanner unit 212, a printing unit 213, an audio output unit 214, and a communication unit 215. These can communicate with each other via a bus. The reference characters 211a, 211b, and 211c will be described later.

[0025] The CPU 201 is a central processing unit, and controls the operation of the POS terminal 20 by reading and executing programs stored in the ROM 202 . The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs.

[0026] The RAM 203 is a read / write memory and stores various information. For example, the RAM 203 stores information acquired from the outside (e.g., a product master acquired from the store controller 10) and information generated during processing (e.g., registration information (registration data) generated during a registration process for registering products, settlement information generated during a settlement process for settling (paying) purchased products, etc.).

[0027] The hard disk 204 stores various information. For example, the hard disk 204 may store programs executed by the CPU 201 instead of the ROM 202. Also, instead of the RAM 203, the hard disk 204 may store information acquired from the outside and information generated during processing.

[0028] The customer-side display unit 205 is a touch display for customers, which displays various information to customers and accepts various inputs from customers. The customer-side scanner unit 206 is a scanner unit for customers, and optically reads various information. For example, the customer-side scanner unit 206 optically reads barcodes (product codes, etc.) attached to products and codes (barcodes, two-dimensional codes, etc.) printed on bills (registered trademarks). In addition to the above, the customer-side scanner unit 206 may read codes (barcodes, two-dimensional codes, etc.) printed on gift certificates (gift certificates, coupons, and complimentary coupons) and various cards (for example, membership cards, point cards, etc.). The customer-side scanner unit 206 is used when a customer registers a product, but the customer may register the product by other methods. For example, when a preset key (a button for ordering a product) corresponding to a product is displayed on the customer-side display unit 205, the customer may operate (press) the preset key to register the product.

[0029] The card payment unit 208 is a payment mechanism using various cards (credit cards, prepaid cards such as transportation cards, point cards, etc.). The card payment unit 208 includes a card recognition unit (reading unit), a display unit, and an operation unit. The card recognition unit magnetically or electrically reads information on various cards. The read information is used for payment (settlement) of the purchased items. The card recognition unit may recognize various cards not only when the recognized information is used for payment (settlement) of the purchased items (i.e., in the case of credit card payment, prepaid card payment, and the use (consumption) of points held on a point card), but also when the recognized information is not used for payment (settlement) of the purchased items (for example, when a special offer is given by presenting a credit card, when points are given to a point card, etc.). The card payment unit 208 of this embodiment includes a card recognition unit (reading unit), a display unit, and an operation unit, but the card payment unit 208 may include at least a card recognition unit. Further, the card recognition unit in this embodiment is compatible with contact cards (IC cards, magnetic cards), but may be compatible with non-contact cards (IC cards) instead of or in addition to contact cards.

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

[0031] The store clerk's display unit 210 is a touch display for the store clerk, which displays various information to the store clerk and receives various inputs from the store clerk. The key operation unit 211 is made up of various keys (hardware keys, buttons) and receives various inputs from the store clerk. The store clerk scanner unit 212 is a scanner unit for store clerks, and optically reads various information. For example, the store clerk scanner unit 212 optically reads barcodes attached to products and store clerk codes attached to store clerk nametags. In addition to the above, the store clerk scanner unit 212 may also read codes printed on bills, gift certificates, and various cards.

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

[0033] The printing unit 213 prints and issues various media (receipts, bills, etc.). The printing unit 213 can freely rotate to change its orientation (direction of the media issuing port) from the clerk side to the customer side, or from the customer side to the clerk side. The orientation of the printing unit 213 may be changed manually, or may be changed automatically (mechanically controlled, etc.) based on, for example, a change in operating mode (details to be described later). The correctness of the orientation of the printing unit 213 may be detected by a sensor or the like. Changing the operating mode is also referred to as a transition of the operating mode.

[0034] The audio output unit 214 outputs audio. For example, the audio output unit 214 outputs audio guidance and the like. The communication unit 215 transmits and receives information to and from other terminals (other POS terminals 20, the store controller 10).

[0035] (Overview of each operation mode) Next, the operation modes of the POS terminal 20 will be described. The POS terminal 20 has a plurality of operation modes. The operation modes are operation modes during normal business (operation modes related to registration processing and settlement processing), and do not include a counting mode for counting and inquiring sales and inventory, a maintenance mode for a store clerk or maintenance staff to perform setting and maintenance work, a training mode for a new employee to undergo training, etc.

[0036] FIG. 5 is a diagram for explaining an outline of the operation modes of the POS terminal 20. The POS terminal 20 has, for example, three types of operation modes (normal mode (standard mode), full self-service mode, and semi-self-service mode (accounting only mode)) shown in FIG. 5(A). The POS terminal 20 may have a normal mode (restricted mode) shown in FIG. 5(B) instead of or in addition to the normal mode (standard mode) shown in FIG. 5(A). The POS terminal 20 may have a semi-self-service mode (registration only mode) shown in FIG. 5(B) instead of or in addition to the normal mode (standard mode) shown in FIG. 5(A). The POS terminal 20 may have a semi-self-service mode (registration only mode) shown in FIG. 5(B) instead of or in addition to the semi-self-service mode (accounting only mode) shown in FIG. 5(A).

[0037] In Fig. 5(A), the columns indicate each operation mode, and the rows indicate each function ("Product registration (clerk side)", "Product registration (customer side)", "Insert coins", ..., "Read receipt"). The same is true in Fig. 5(B) (however, illustration of each function is omitted in Fig. 5(B)).

[0038] In FIG. 5(A) (as well as FIG. 5(B)), an "o" in a field identified by a column and a row indicates that the function of that row is enabled in the operation mode of that column. For example, an "o" in a field identified by the column "normal mode (standard mode)" and the row "product registration (clerk side)" indicates that product registration (clerk side) is enabled in normal mode (standard mode). Also, a "-" in a field identified by a column and a row indicates that the function of that row is disabled in the operation mode of that column. For example, a "-" in a field identified by the column "normal mode" and the row "product registration (customer side)" indicates that product registration (customer side) is disabled in normal mode.

[0039] (Explanation of each function) Below, an overview of each function shown in FIG. 5(A) will be given.

[0040] (Product registration (store clerk side)) "Product registration (clerk side)" is a function for registering purchased products on the clerk side (clerk side scanner unit 212, clerk side display unit 210, key operation unit 211). In other words, it is a function for executing registration processing of purchased products by the operation of the clerk (scanning by clerk side scanner unit 212, touching on clerk side display unit 210, operating key operation unit 211).

[0041] (Product registration (customer side)) "Product registration (customer side)" is a function for registering purchased products on the customer side (customer side scanner unit 206, customer side display unit 205). In other words, it is a function for executing registration processing of purchased products by customer operations (scanning by customer side scanner unit 206, touching customer side display unit 205).

[0042] (Inserting currency) "Deposit of money" is a function to accept the insertion of money (bills and coins). In other words, it is a function to accept the operation of settling with cash (inserting money into the change machine 209).

[0043] (Send registration information to other devices) "Sending registration information to other terminals" is a function to send the registration information generated in the registration process to other terminals (other terminals capable of executing settlement processes, for example, other POS terminals 20) (either directly to the other terminals, or indirectly to the other terminals via the store controller 10 or a monitoring terminal, etc.; the same applies below).

[0044] (Issuance of bills) The "issuance of a receipt" function encodes the registration information generated in the registration process and issues a printed medium (receipt).

[0045] (Receiving registration information from other devices) "Receiving registration information from another terminal" is a function to receive registration information generated in the registration process of another terminal (receiving directly from another terminal, or receiving indirectly from another terminal via the store controller 10 or a monitoring terminal, etc. The same applies below). The terminal that receives the registration information from another terminal executes the settlement process based on the registration information.

[0046] (Reading the bill) "Read receipt" is a function to read receipts (specifically, the code printed on the receipt or the encoded information). A terminal that reads a receipt issued by another terminal executes the settlement process based on the registration information obtained by reading the receipt.

[0047] (Explanation of each operation mode) Next, an overview of each operation mode shown in FIG. 5(A) and FIG. 5(B) will be described.

[0048] (Normal mode (standard mode)) The normal mode (standard mode) is an operation mode in which product registration (clerk side) is enabled "◯" and product registration (customer side) is disabled "-" as shown in Fig. 5(A). In other words, the normal mode (standard mode) is an operation mode in which the registration process is not performed on the customer side but is performed on the clerk side.

[0049] Also, as shown in Fig. 5(A), the normal mode (standard mode) is an operating mode in which the insertion of coins, the transmission of registration information to other terminals, and the issuance of a bill are all enabled "O". In other words, in the normal mode (standard mode), the settlement process after the registration process on the store clerk's side can be performed on the store's own terminal or can be performed by another terminal. Specifically, in the normal mode (standard mode), the settlement process is performed on the store's own terminal by accepting the insertion of coins into the change dispenser 209, and the settlement process is caused to be performed by the other terminal by transmitting registration information to the other terminal (or by issuing a bill).

[0050] Also, as shown in FIG. 5(A), the normal mode (standard mode) is an operation mode in which both the reception of registration information from another terminal and the reading of a bill are enabled "○". That is, in the normal mode (standard mode), the settlement process can be executed based on the registration information generated in the other terminal. The settlement process after the reception of the registration information (or the reading of the bill) may be executed in the semi-self-service mode of FIG. 5(A). That is, when the registration information is received (or the bill is read) in the normal mode (standard mode), the device may automatically switch from the normal mode (standard mode) to the semi-self-service mode (only for billing) (permission from a store clerk may be required) and the settlement process may be executed in the semi-self-service mode (only for billing). Also, when the device switches to the semi-self-service mode (only for billing) and the settlement process is executed, the device may automatically switch (return) from the semi-self-service mode (only for billing) to the normal mode (standard mode) (permission from a store clerk may be required), or the device may remain in the semi-self-service mode (only for billing).

[0051] In the normal mode (standard mode), at least one of the reception of registration information from other terminals and the reading of accounting tickets may be disabled ("-").

[0052] (Full self mode) As shown in FIG. 5(A), the full self-service mode is an operating mode in which product registration (customer side) is enabled (O). In other words, the full self-service mode is an operating mode that assumes registration processing on the customer side. However, the full self-service mode also enables product registration (clerk side). In other words, the full self-service mode is an operating mode that assumes registration processing on the customer side, but also allows registration processing on the clerk side. The state in which registration processing is performed on both the customer side and the clerk side is sometimes referred to as double scan mode.

[0053] In the example shown in FIG. 5(A), in the full self-service mode, product registration (clerk side) is enabled (circle), but in the full self-service mode, product registration (clerk side) may be disabled (-).

[0054] As shown in Fig. 5(A), the full self-service mode is an operation mode in which insertion of coins is enabled (◯) and transmission of registration information to other terminals and issuance of bills is disabled (-). In other words, the full self-service mode is an operation mode that assumes that the settlement process will be carried out at the terminal.

[0055] As shown in FIG. 5(A), the full self-service mode is an operation mode in which both reception of registration information from other terminals and reading of bills are enabled "○" in the same way as the normal mode (standard mode). In other words, in the full self-service mode, the settlement process can be executed based on the registration information generated in the other terminal, in the same way as the normal mode (standard mode). The settlement process after reception of the registration information (or reading of the bill) may be executed in the semi-self-service mode of FIG. 5(A). In other words, when the registration information is received (or the bill is read) in the full self-service mode, the mode may automatically switch from the full self-service mode to the semi-self-service mode (accounting only mode) and the settlement process may be executed in the semi-self-service mode (accounting only mode). In addition, when the mode switches to the semi-self-service mode (accounting only mode) and the settlement process is executed, the mode may automatically switch (return) from the semi-self-service mode (accounting only mode) to the full self-service mode, or may remain in the semi-self-service mode (accounting only mode).

[0056] (Semi-self mode (accounting only mode)) As shown in Fig. 5(A), semi-self-service mode (accounting-only mode) is an operating mode in which receiving registration information from other terminals, reading receipts, and inserting coins are enabled (◯), and product registration (clerk side) and product registration (customer side) are disabled (-). In other words, semi-self-service mode (accounting-only mode) is an operating mode in which the registration process is not performed on the terminal itself, but the settlement process is performed solely based on registration information generated on other terminals. Note that because semi-self-service mode (accounting-only mode) is an operating mode in which registration processes are not performed (because registration information is not generated), sending registration information to other terminals and issuing receipts are both disabled (-), as shown in Fig. 5(A).

[0057] (Normal mode (Limited mode)) As shown in Fig. 5(B), the normal mode (restricted mode) disables the sending of registration information to other terminals and the issuing of accounting tickets, which are enabled (◯) in the normal mode (standard mode) in Fig. 5(A), by setting them to disabled (-). In other words, the normal mode (restricted mode) is an operating mode that limits the function of allowing other terminals to execute payment processing, which is permitted in the normal mode (standard mode).

[0058] (Semi-self mode (registration only mode)) As shown in Fig. 5(B), semi-self-service mode (registration-only mode) is an operating mode in which product registration (store clerk side), sending of registration information to other terminals, and issuing of receipts are enabled (◯), and product registration (customer side), insertion of coins, receiving of registration information from other terminals, and reading of receipts are disabled (-). In other words, semi-self-service mode (registration-only mode) is an operating mode in which the registration process is carried out exclusively on the terminal itself, and payment is processed at other terminals. Note that because semi-self-service mode (registration-only mode) is premised on the registration operation being performed by a store clerk, product registration (customer side) is disabled (-).

[0059] (About enabling and disabling the function) In the above, it has been explained that the various functions (product registration (clerk side), product registration (customer side), coin insertion, ..., receipt reading in Fig. 5(A)) of the POS terminal 20 itself are enabled "◯" or disabled "-" depending on the operation mode. In other words, it has been explained above that the POS terminal 20 originally has all the functions (product registration (clerk side), product registration (customer side), coin insertion, ..., receipt reading in Fig. 5(A)), and some of these functions are disabled depending on the operation mode (for example, as shown in Fig. 5(A), the POS terminal 20 disables product registration (customer side) "-" when in normal mode (standard mode), and disables sending registration information to other terminals and issuing receipts "-" when in full self-service mode).

[0060] However, the POS terminal 20 may have different executable functions depending on the operation mode, and the POS terminal 20 does not necessarily have to have all the functions from the beginning and disable some of the functions depending on the operation mode. For example, the POS terminal 20 does not have all the functions (programs for realizing the functions) from the beginning, but rather acquires a program for realizing a function required in the operation mode (function corresponding to the function marked as "○" in FIG. 5) from the outside (for example, the store controller 10, a monitoring terminal, a server outside the store (such as a cloud)) depending on the operation mode (for example, when switching the operation mode), and makes it executable, and when a program for realizing a function not required for the operation mode (function corresponding to the function marked as "-" in FIG. 5) exists (when held), the program may be made in an inexecutable state (for example, may be erased). Note that the program for realizing the unnecessary function may be made in an inexecutable state, and then the program for realizing the necessary function may be acquired and made executable. Also, for example, when switching between operation modes, the POS terminal 20 may temporarily disable all programs regardless of the operation mode to which the operation mode is to be switched, and then obtain from the outside a program for implementing functions required in the operation mode and make the program executable. In other words, the configuration of the POS terminal 20 may be such that some of the various functions originally provided are disabled "-" depending on the operation mode, or such that only the necessary functions are provided appropriately depending on the operation mode.

[0061] The normal mode (standard mode), full self-service mode, semi-self-service mode (accounting only mode) in Fig. 5(A), the normal mode (restricted mode) in Fig. 5(B), and semi-self-service mode (registration only mode) have been described above, but the following description will focus on the normal mode (standard mode), full self-service mode, and semi-self-service mode (accounting only mode) in Fig. 5(A). In the following description, the normal mode (standard mode) may be simply referred to as the normal mode. Also, the semi-self-service mode (accounting only mode) may be simply referred to as the semi-self-service mode.

[0062] (Switching (transitioning) operation modes) Next, a description will be given of switching (transition) of the operation mode of the POS terminal 20. The operation mode of the POS terminal 20 is basically switched in accordance with an explicit mode switching operation (also called a mode transition operation; details will be described later) for switching the operation mode by a store clerk. In addition, the operation mode of the POS terminal 20 may be switched in accordance with an operation other than the mode switching operation (for example, reading a store clerk code, etc.).

[0063] The POS terminal 20 may switch the operation mode without being operated by a store clerk. Specifically, the POS terminal 20 may switch the operation mode according to a mode switching command (mode switching instruction) from another terminal (the POS terminal 20, a monitoring terminal, a mobile terminal, etc.). The POS terminal 20 may switch the operation mode according to a time condition (for example, the time elapsed since the last operation, a fixed time according to a schedule, etc.). The POS terminal 20 may switch the operation mode at the start of a process (for example, at the start of a settlement process based on the received registration information, at the start of a settlement process based on a receipt, etc.). The POS terminal 20 may switch the operation mode at the end of a process (for example, at the end of a settlement process based on the received registration information, at the end of a settlement process based on a receipt).

[0064] FIG. 6 is a diagram for explaining switching of the operation mode of the POS terminal 20. The left side of FIG. 6 shows a combination of operation modes before and after switching (operation mode before switching → operation mode after switching), and the right side shows the conditions (examples) for switching the operation mode. For example, row a shows that, as an example of the conditions for switching the operation mode from the normal mode to the full self mode, there is a mode switching operation, a mode switching command, and a predetermined time lapse (not used). In other words, when the operation mode is the normal mode, for example, if there is a mode switching operation, a mode switching command, or a predetermined time lapse (not used), the operation mode switches from the normal mode to the full self mode. Details of the mode switching operation will be described later.

[0065] (Normal mode → Full self mode) As shown in a, when in normal mode, for example, if a mode switching operation, a mode switching command (such as a mode switching command in which full self mode is specified as the operation mode to be transitioned to), or a predetermined time has elapsed (a predetermined period of non-use), the operation mode will switch from normal mode to full self mode.

[0066] (Normal mode → Semi-self mode (accounting only mode)) As shown in b, when in normal mode, for example, if there is a mode switching operation or a mode switching command (such as a mode switching command specifying semi-self mode (accounting only mode) as the destination operating mode), the operating mode switches from normal mode to semi-self mode (accounting only mode). Also, when in normal mode, for example, if registration information is received from another terminal or an accounting ticket is read, the operating mode may be switched from normal mode to semi-self mode (accounting only mode).

[0067] (Full self mode → Normal mode) As shown in c, when in full self mode, for example, if a mode switching operation or a mode switching command (such as a mode switching command in which normal mode is specified as the destination operating mode) is performed, the operating mode is switched from full self mode to normal mode.

[0068] (Full self-service mode → Semi-self-service mode (accounting only mode)) As shown in d, when in full self mode, for example, if there is a mode switching operation or a mode switching command (such as a mode switching command specifying semi-self mode (accounting only mode) as the destination operating mode), the operating mode switches from full self mode to semi-self mode (accounting only mode). Also, when in full self mode, for example, if registration information is received from another terminal or an accounting ticket is read, the operating mode may be switched from full self mode to semi-self mode (accounting only mode).

[0069] (Full self mode → double scan mode) As shown in e, when in full self-service mode, if, for example, a store clerk code is read, the operation mode switches from full self-service mode to double scan mode. Note that double scan mode is one aspect of full self-service mode (a state in which the product registration (store clerk) function is used in addition to the product registration (customer) function. See FIG. 5(A)).

[0070] If the clerk code is read when in the full self-service mode, the operation mode may always switch to the double scan mode regardless of the state of product registration, or may switch to a different operation mode depending on the state of product registration. For example, if the clerk code is read when a product has not yet been registered (i.e., when the customer has not yet registered the product), the operation mode may switch from the full self-service mode to the normal mode, and if the clerk code is read when a product has already been registered (i.e., when the customer has registered the product), the operation mode may switch from the full self-service mode to the double scan mode.

[0071] (Semi-self mode (accounting only mode) → Normal mode) As shown in f, when in the semi-self-service mode (accounting only mode), for example, if there is a mode switching operation or a mode switching command (such as a mode switching command in which the normal mode is specified as the operation mode to transition to), the operation mode switches from the semi-self-service mode (accounting only mode) to the normal mode. Also, when in the semi-self-service mode (accounting only mode), for example, if a settlement process (for example, a settlement process based on received registration information, a settlement process based on a bill) is completed, the operation mode may be switched from the semi-self-service mode (accounting only mode) to the normal mode.

[0072] (Semi-self-service mode (accounting only mode) → Full self-service mode) As shown in g, when in semi-self-service mode (accounting only mode), for example, if there is a mode switching operation or a mode switching command (such as a mode switching command in which full self-service mode is specified as the operation mode to transition to), the operation mode switches from semi-self-service mode (accounting only mode) to full self-service mode. Also, when in semi-self-service mode (accounting only mode), for example, if a settlement process (for example, settlement process based on received registration information, settlement process based on a bill) is completed, the operation mode may be switched from semi-self-service mode (accounting only mode) to full self-service mode.

[0073] The mode switching operation may be any operation that specifies the operation mode of the destination in response to the operation. For example, when a button for each destination is provided (or displayed), the operation mode may be switched to each destination in response to a mode switching operation of pressing each button. Also, when a button that switches the destination each time it is pressed is provided (or displayed), the operation mode may be switched each time the mode switching operation of pressing the button is performed.

[0074] It should be noted that a button for selecting a destination operation mode and a button for confirming the transition to the operation mode selected by the button may be separately provided (or displayed).

[0075] (Transition of operation mode by mode switching operation) Next, the transition of the operation mode by the mode switching operation will be described. The operation mode of the POS terminal 20 is switched according to an explicit mode switching operation by a store clerk (see FIG. 6). Specifically, the operation mode is switched according to the operation of the mode switching button 211a (see FIG. 3(B)) located at the top and right end of the key operation unit 211.

[0076] In addition, since the mode switching button 211a is located at a corner of the key operation unit 211, it is possible to reduce operational errors when switching the operation mode and to easily switch the operation mode. In other words, when the mode switching button 211a is located at a corner of the key operation unit 211, compared to when the mode switching button 211a is located near the center of the key operation unit 211, for example, the number of other buttons adjacent to the mode switching button 211a to be operated is smaller, so that operational errors such as hastily operating other buttons are less likely to occur, and the position of the mode switching button 211a to be operated can be instantly identified, allowing the mode switching operation to be performed without stress.

[0077] Furthermore, since the mode switching button 211a is located in the upper right corner (top row and rightmost) of the key operation unit 211, the mode switching operation can be performed not only when the clerk is on the clerk side but also when the clerk is on the customer side. In other words, a clerk on the customer side cannot usually see the buttons on the key operation unit 211, but the clerk can easily recognize the mode switching button 211a located on the upper right corner of the key operation unit 211 by reaching out from the customer side and feeling for it (by touch), so the clerk on the customer side can perform the mode switching operation without moving to the clerk side.

[0078] In this embodiment, the mode switching button 211a is disposed in the upper right corner of the key operation unit 211, but the mode switching button 211a may be disposed in a position other than the upper right corner of the key operation unit 211 as long as the position is recognizable by touch alone (a position that is relatively easy to recognize). Also, instead of or in addition to disposing the mode switching button 211a in a position recognizable by touch alone (for example, the upper right corner), the mode switching button 211a may be formed so as to be distinguishable from other buttons even from the customer side. For example, the size of mode switching button 211a may be made different from the size of the other buttons to the extent that it can be distinguished by touch alone, the shape of mode switching button 211a may be made different from the shape of the other buttons, or the height of mode switching button 211a may be made different from the height of the other buttons (for example, mode switching button 211a may be made to protrude more than the other buttons), or the feel of all or part of the surface (the surface that the hand touches) of mode switching button 211a may be made different from the feel of the other buttons (for example, only the surface of mode switching button 211a may be made rough or bumpy to the touch, or only the surface of mode switching button 211a may be provided with protrusions or depressions).

[0079] In this embodiment, taking into consideration the various advantages as described above, the mode switching button 211a is arranged on the key operation unit 211. However, instead of or in addition to arranging the mode switching button 211a on the key operation unit 211, a mode switching button (not shown) may be arranged on the screen displayed on the store clerk side display unit 210.

[0080] (Operation in each operation mode) Fig. 7 is a schematic diagram for explaining an overview of operation in normal mode. Specifically, Fig. 7 is a schematic diagram showing the flow of processing and the actions of people (store clerks, customers) when a settlement process is performed at the terminal in normal mode. Fig. 8 is a flowchart for explaining an overview of operation in normal mode. Specifically, Fig. 8 is a flowchart for explaining an overview of operation when a settlement process is performed at the terminal in normal mode.

[0081] In normal mode (both when the payment process is performed at the customer's own terminal and when the payment process is performed at another terminal), the store clerk registers the purchased items of the customer on the store clerk side (store clerk scanner unit 212, store clerk display unit 210, key operation unit 211) (upper part of FIG. 7). That is, the POS terminal 20 executes the registration process of the purchased items by the operation of the store clerk (scanning by store clerk scanner unit 212, touching store clerk display unit 210, operating key operation unit 211) (upper part of FIG. 7).

[0082] When the clerk has completed the registration process, the customer checks the total amount of the purchased items on the clerk-side display unit 210, and settles the bill by inserting currency (cash) into the change machine 209 or by operating the card payment unit 208 (lower part of FIG. 7). In other words, the POS terminal 20 executes the settlement process according to the customer's operation (inserting cash into the change machine 209, operating the card payment unit 208) (lower part of FIG. 7).

[0083] That is, when a settlement process is performed at the own terminal in normal mode, first, the clerk scans the products (step S10: YES) and registers the products (step S11), as shown in Fig. 8. After a subtotal key (e.g., a subtotal key displayed on the clerk display unit 210 or a subtotal key arranged on the key operation unit 211) is pressed (step S30: YES), the customer settles the amount using, for example, the change dispenser 209 (step S50), and the process is completed. The subtotal key in step S30 is an operation key for completing the registration process, and may also be called a subtotal button, a registration completion key, a registration completion button, a bill key, or a bill button.

[0084] The customer may wait until the registration process is completed by the store clerk (until the total amount is finalized), or may insert cash into the change dispenser 209 before the registration process is completed. In other words, the POS terminal 20 can accept deposits during the registration process (upper part of FIG. 7).

[0085] In addition, the customer may select a payment method (also referred to as a payment type, settlement method, or settlement type) before completing the registration process. In other words, the POS terminal 20 can accept the selection of a payment method during the registration process.

[0086] The store clerk may wait until the customer completes the payment (until the customer receives the change and receipt), but may also register the items purchased by the next customer. That is, the POS terminal 20 can register the items purchased by the next customer during the payment process (lower part of FIG. 7). The store clerk may also be absent while the customer is paying (lower part of FIG. 7). That is, the store clerk may finish serving the customer while the customer is paying.

[0087] Furthermore, when there is change, the POS terminal 20 may control the dispenser 209 to dispense the change and the change note to prevent the customer from forgetting to take the change, and after detecting with a sensor or the like that the customer has removed the change and the change note, control the printing unit 213 to print a receipt. This is also true in other operation modes.

[0088] FIG. 9 is a schematic diagram for explaining an outline of operation in normal mode. Specifically, FIG. 9 is a schematic diagram showing the flow of processing and the actions of people (store clerks, customers) when another terminal is made to execute a settlement process in normal mode (standard mode). FIG. 10 is a flowchart for explaining an outline of operation in normal mode, etc. Specifically, FIG. 10(A) is a flowchart for explaining an outline of operation when another terminal is made to execute a settlement process in normal mode (standard mode). Note that FIG. 10(B) is a flowchart showing the basic flow of operation in the other terminal (other device) of FIG. 10(A).

[0089] In normal mode (both when the payment process is performed at the store's own terminal and when the payment process is performed at another terminal), the store clerk registers the purchased items of the customer on the store clerk side (store clerk scanner unit 212, store clerk display unit 210, key operation unit 211) (upper part of FIG. 9). That is, the POS terminal 20 (POS terminal 20-1 in the example of FIG. 9) executes the registration process of the purchased items by the operation of the store clerk (operation of the store clerk scanner unit 212, store clerk display unit 210, key operation unit 211, etc.) (upper part of FIG. 9).

[0090] When the clerk has completed the registration process, the customer moves to another POS terminal 20 (POS terminal 20-2 in the example of FIG. 9), checks the total amount of the purchased items on the clerk's display unit 210, and settles the bill by inserting coins into the change machine 209 or operating the card payment unit 208 (lower part of FIG. 9). In other words, the other POS terminal 20 executes the settlement process according to the customer's operation (inserting coins into the change machine 209, operating the card payment unit 208) (lower part of FIG. 9).

[0091] The other POS terminal 20 (the POS terminal 20-2) is provided with information necessary for the settlement process (such as the registration information generated in the POS terminal 20-1).

[0092] The store clerk may use the POS terminal 20-1 to specify the POS terminal 20 that will execute the payment process (either the POS terminal 20-2 or the POS terminal 20-3 in the example of FIG. 9). Alternatively, the store clerk may use the POS terminal 20-1 to issue a medium (a bill) to be read by the POS terminal 20 that will execute the payment process (the POS terminal 20-2 or the POS terminal 20-3 in the example of FIG. 9).

[0093] That is, when the other terminal is to execute the settlement process in the normal mode, as shown in Fig. 10(A), the clerk first scans the product (step S10: YES) and registers the product (step S11). After pressing a subtotal key (e.g., a subtotal key displayed on the clerk display unit 210 or a subtotal key arranged on the key operation unit 211) (step S30: YES), for example, another POS terminal 20 to execute the settlement process is designated (step S31: YES), and the registration information is sent to the designated POS terminal 20 (step S32), completing the process on the registration side.

[0094] After specifying another terminal, the store clerk can register the next customer's purchase (lower part of FIG. 9). Also, after specifying another terminal, the store clerk may be absent (lower part of FIG. 9).

[0095] 10(A), another POS terminal 20 is designated after pressing the subtotal key, but it is also possible to designate another POS terminal 20 without pressing the subtotal key. For example, a subtotal key and a key for designating another POS terminal 20 may be arranged on the registration screen (and a key for issuing a bill may also be arranged), and registration information may be transmitted when the key for designating the POS terminal 20 is pressed. In the aspect in which another POS terminal 20 is designated without pressing the subtotal key, it is not necessary to press the subtotal key after pressing the key for designating the other POS terminal 20.

[0096] 10(A), a receipt to be read by another POS terminal 20 may be issued, and the other POS terminal 20 may execute the settlement process. The key for issuing the receipt may be pressed after the subtotal key is pressed, or may be pressed before the subtotal key. In the case where the key for issuing the receipt is pressed before the subtotal key is pressed, it is not necessary to press the subtotal key after pressing the key for issuing the receipt.

[0097] The other POS terminal 20 (POS terminal 20-2 in the example of FIG. 9) that has received the registration information transitions (switches) to semi-self-service mode (accounting only mode) after receiving the registration information (step S40: YES) as shown in FIG. 10(B) if it is not in semi-self-service mode (accounting only mode). That is, if the current operation mode (at the time of receiving the registration information) is full-self-service mode (step S41: YES), it transitions from full-self-service mode to semi-self-service mode (accounting only mode) (step S42), and if the current operation mode is normal mode (step S43: YES), it transitions from normal mode to semi-self-service mode (accounting only mode) (step S42). Then, at the customer's side, settlement is performed by, for example, the change dispenser 209 (step S50), and the settlement process is completed.

[0098] In the example shown in Fig. 10(B), the other POS terminal 20 that received the registration information switches to semi-self-service mode (accounting only mode) if it was not already in semi-self-service mode (accounting only mode) after receiving the registration information, but it does not have to switch to semi-self-service mode (accounting only mode). In other words, because payment processing is possible even in normal mode or full self-service mode (see Fig. 5), payment processing may be performed in normal mode or full self-service mode.

[0099] As described above, the normal mode (standard mode) includes a function for executing a registration process on the store clerk's side and then executing a settlement process at the customer's side of the terminal using the registration information generated in the registration process (see Figures 7 and 8); a function for sending the registration information generated in the registration process to another terminal (another terminal capable of executing a settlement process, such as another POS terminal 20) to have the other terminal execute the settlement process (see Figures 9 and 10); and a function for issuing a receipt printed with the registration information generated in the registration process (or information for obtaining the registration information) as a code (barcode, two-dimensional code, etc.) and having the other terminal execute the settlement process.

[0100] On the other hand, the normal mode (restricted mode), as shown in Figure 5 (B), is a mode in which, among the functions of the normal mode (standard mode) described above, the following functions are restricted: a function of sending the registration information generated in the registration process to another terminal and having the other terminal execute the settlement process, and a function of issuing an accounting ticket that is printed by encoding the registration information generated in the registration process (or information for obtaining the registration information), and having the other terminal execute the settlement process.

[0101] Among the functions of the normal mode (standard mode) described above, the function of transmitting the registration information generated in the registration process to another terminal and having the other terminal execute the settlement process, and the function of issuing a bill on which the registration information generated in the registration process (or information for acquiring the registration information) is coded and printed, and having the other terminal execute the settlement process, are also functions of the semi-self-service mode (registration-only mode). In other words, the semi-self-service mode can be classified into a registration-only mode and a settlement-only mode, but the semi-self-service mode (registration-only mode) includes a function of transmitting the registration information generated in the registration process to another terminal and having the other terminal execute the settlement process, and a function of issuing a bill on which the registration information generated in the registration process (or information for acquiring the registration information) is coded and printed, and having the other terminal execute the settlement process, as shown in FIG. 5(B). In other words, the semi-self-service mode (registration-only mode) is a mode in which the function of executing the registration process on the customer's side using the registration information generated in the registration process after the clerk executes the registration process is restricted from among the functions of the normal mode (standard mode) described above. In other words, the semi-self mode (registration-only mode) is an operation mode in which the registration process is executed exclusively.

[0102] As shown in Fig. 5(A), the semi-self-service mode (accounting-only mode) includes a function to receive registration information generated in the registration process on another terminal and execute the payment process, and a function to read an accounting ticket issued on another terminal and execute the payment process. In other words, the semi-self-service mode (accounting-only mode) is an operating mode that exclusively executes the payment process.

[0103] Fig. 11 is a schematic diagram for explaining an outline of the operation in the full self mode, and Fig. 12 is a flowchart for explaining an outline of the operation in the full self mode.

[0104] In the full self-service mode, the customer registers the purchased items on the customer side (customer side scanner unit 206, customer side display unit 205) (upper part of FIG. 11). That is, the POS terminal 20 executes the registration process of the purchased items by the customer's operation (scanning by the customer side scanner unit 206, touching the customer side display unit 205) (upper part of FIG. 11).

[0105] When the registration process is completed, the customer checks the total amount of the purchased items on the customer side display unit 205, and settles the bill by inserting cash into the change machine 209 or operating the card payment unit 208 (lower part of FIG. 11). That is, the POS terminal 20 executes the settlement process according to the customer's operation (inserting cash into the change machine 209, operating the card payment unit 208) (lower part of FIG. 11).

[0106] That is, in the case of the full self-service mode, as shown in Fig. 12, the product is scanned (step S20: YES) and registered (step S21) on the customer side. After a registration completion key (e.g., a registration completion key displayed on the customer side display unit 205) is pressed (step S40: YES), the customer performs settlement, for example, using the change dispenser 209 (step S50), and the process is completed. The registration completion key in step S40 is an operation key for completing the registration process, and may also be called a registration completion button, subtotal key, subtotal button, bill key, bill button, etc.

[0107] In the full self-service mode, as shown in Fig. 11, the customer executes both the registration process and the payment process, but this does not mean that the store clerk cannot do anything. In other words, even when the POS terminal 20 is operating in the full self-service mode, the store clerk can, for example, scan products (double scan mode) and display various information.

[0108] Fig. 13 is a schematic diagram for explaining an outline of the operation of the double scan mode. Fig. 14 is a flow chart for explaining an outline of the operation of the double scan mode. Note that the double scan mode is one aspect of the full self mode, but for the sake of convenience, the two operation modes are distinguished in Fig. 13 and Fig. 14.

[0109] In the full self-service mode, the customer registers the purchased items on the customer side (upper part of FIG. 11, upper part of FIG. 13). That is, the POS terminal 20 executes the registration process of the purchased items by the customer's operation (upper part of FIG. 11, (upper part of FIG. 13)).

[0110] During the registration process by the customer, the store clerk registers the products purchased by the customer on the store clerk side (middle part of FIG. 13). That is, the POS terminal 20 executes the registration process by the customer's operation and the registration process by the store clerk's operation (middle part of FIG. 13).

[0111] When the registration process is completed, the customer checks the total amount of the purchased items on the customer side display unit 205, and settles the bill by inserting cash into the change machine 209 or operating the card payment unit 208 (lower part of FIG. 13). That is, the POS terminal 20 executes the settlement process according to the customer's operation (inserting cash into the change machine 209, operating the card payment unit 208) (lower part of FIG. 13).

[0112] In other words, when the registration process is being performed in full self-service mode (see FIG. 12), if the store clerk code is read by the store clerk side scanner unit 212 (step S110: YES), as shown in FIG. 14(A), the operating mode transitions from full self-service mode to double scan mode (step S111).

[0113] After the mode is switched to the double scan mode, as shown in Fig. 14(B), the clerk scanner unit 212 scans the product (step S10: YES) to register the product (step S11), and the customer scanner unit 206 scans the product (step S20: YES) to register the product (step S21). After pressing a subtotal key (e.g., a subtotal key displayed on the clerk display unit 210 or a subtotal key arranged on the key operation unit 211) or a registration completion key (e.g., a registration completion key displayed on the customer display unit 205) (step S41: YES), the customer uses, for example, the change dispenser 209 to settle the bill (step S50), and the process is completed.

[0114] In the double scan mode, the store clerk may wait until the customer completes the payment (until the customer receives the change and receipt), but may also register the items purchased by the next customer. That is, the POS terminal 20 can register the items purchased by the next customer during the payment process (lower part of FIG. 13). Also, the store clerk may be absent while the customer is paying (lower part of FIG. 13). That is, the store clerk may finish serving the customer while the customer is paying.

[0115] As shown in Fig. 14(A), when the clerk code is read in the full self-service mode, the operation mode transitions from the full self-service mode to the double scan mode, but reading the clerk code may be one of the login operations. Also, when another operation (for example, a login operation other than reading the clerk code) is performed in the full self-service mode, the operation mode may transition from the full self-service mode to the double scan mode. Also, when no operation is performed by the clerk in the double scan mode (for example, when a predetermined time has passed since the last operation), the operation mode may transition from the double scan mode to the full self-service mode.

[0116] (Operation mode notification) Each POS terminal 20 may notify its own current operation mode. For example, each POS terminal 20 may display its own current operation mode on the store clerk display unit 210. Specifically, each POS terminal 20 may display a screen having an operation mode display field of its own terminal on the store clerk display unit 210, and display its own current operation mode in the operation mode display field on the screen. Also, each POS terminal 20 may display a screen on which images (e.g., button-like images) corresponding to each operation mode are arranged on the store clerk display unit 210, and display the image corresponding to the current operation mode of its own terminal on the screen in a display mode different from images not corresponding to the current operation mode (e.g., a display mode that stands out more than the display modes of other images). For example, when operating in two operation modes, normal mode and full self-service mode, a normal mode image and a full self-service mode image may be always displayed, and when the current operation mode of the terminal is normal mode, the normal mode image may be displayed in a more prominent display manner than the full self-service mode image, and when the current operation mode of the terminal is full self-service mode, the full self-service mode image may be displayed in a more prominent display manner than the normal mode image. Each POS terminal 20 may similarly display the current operation mode of its own terminal on the customer-side display unit 205.

[0117] Furthermore, each POS terminal 20 may report the current operation mode of the other terminal instead of or in addition to the current operation mode of the own terminal. That is, each POS terminal 20 may report the current operation mode of the other terminal by recognizing the current operation mode of the other terminal. One example of a method for each POS terminal 20 to recognize the current operation mode of the other terminal is a method in which each POS terminal 20 notifies the other terminal of the operation mode after the transition (the latest operation mode) after the transition of the operation mode (directly notifying the other terminal via the LAN 11, or notifying the other terminal via the store controller 10, a monitoring terminal, etc.). Furthermore, each POS terminal 20 may report the current processing status of the other terminal as well as the current operation mode of the other terminal.

[0118] Furthermore, each POS terminal 20 may report information according to its own current operation mode, etc. (operation mode, processing status, etc.). For example, when the current operation mode of the POS terminal 20 is the full self mode, for example when it is in standby, the POS terminal 20 may display various information on the customer side display unit 205. Furthermore, the POS terminal 20 may report information according to the current operation mode, etc. of other terminals instead of or in addition to the information according to the current operation mode of the terminal itself.

[0119] In addition, even if the operation mode is changed by a store clerk (by a mode switching operation, reading of a store clerk code, etc.), or even if the operation mode is changed without a store clerk's operation (by a mode switching command, the passage of a specified time, etc.), the operation mode of the own terminal and other terminals will be notified.

[0120] (Memory of information on operation mode) Each POS terminal 20 may store, as information on the operation mode, in which operation mode the transaction (process) was performed. For example, when the POS terminal 20-1 operating in the normal mode (standard mode) executes the registration process and the settlement process for a certain transaction, the POS terminal 20-1 that executed the registration process and the settlement process may store information (e.g., information that can identify the operation mode) that the registration process and the settlement process for the transaction were performed in the normal mode (standard mode) as information on the transaction (e.g., settlement information) (or in association with the information on the transaction).

[0121] Each POS terminal 20 may also store at which terminal the transaction (process) was performed. In the above example, the POS terminal 20-1 may store information indicating that the registration process and the settlement process were performed at its own terminal (the POS terminal 20-1) as information related to the transaction. More specifically, the POS terminal 20-1 may store the terminal identification information of its own terminal as the identification information (terminal identification information) of the terminal that performed the registration process, and may store the terminal identification information of its own terminal as the terminal identification information of the terminal that performed the settlement process. Alternatively, the POS terminal 20-1 may store the terminal identification information of its own terminal as the terminal identification information of the terminal that performed the entire process (registration process, settlement process).

[0122] Also, for example, if the POS terminal 20-1 operating in normal mode (standard mode) first executes a registration process for a certain transaction, and then the POS terminal 20-2 operating in semi-self mode (accounting-only mode) executes a settlement process for the transaction based on the registration information from the above registration process, the POS terminal 20-2 that executed the settlement process may store information that the registration process for the transaction was performed in normal mode (standard mode) as information about the transaction (for example, settlement information) (or in association with information about the transaction), and may also store information that the settlement process for the transaction was performed in semi-self mode (accounting-only mode). In addition to the above, the POS terminal 20-1 that executed the registration process may also store information that the registration process for the transaction was performed in normal mode (standard mode).

[0123] In the above example, the POS terminal 20-2 that executed the settlement process may store information that the registration process was executed in the other terminal (POS terminal 20-1) as information regarding the transaction, and may store information that the settlement process was executed in its own terminal (POS terminal 20-2). More specifically, the POS terminal 20-2 may store the terminal identification information of the other terminal (POS terminal 20-1) as information (terminal identification information) of the terminal that executed the registration process, and may store the terminal identification information of its own terminal (POS terminal 20-2) as the terminal identification information of the terminal that executed the settlement process. In the above example, it is sufficient that the POS terminal 20-2 that executes the settlement process is able to obtain the terminal identification information of the POS terminal 20-1 that executed the registration process and information identifying the operation mode (specifically, normal mode (standard mode)). For example, the terminal identification information of POS terminal 20-1 and information identifying the operating mode may be supplied from POS terminal 20-1 to POS terminal 20-2 (for example, transmitted and received as registration information, or supplied via a bill).

[0124] Each POS terminal 20 may also store information about transitions (switching) of operation modes as information about operation modes. For example, when the operation mode of the POS terminal 20-1 transitions from one operation mode to another, the POS terminal 20-1 may store information about which operation mode it transitioned to (e.g., information that can identify the operation mode after transition) together with the time of transition of the operation mode. The POS terminal 20-1 may also store information about which operation mode it transitioned from to (e.g., information that can identify the operation mode before transition, information that can identify the operation mode after transition) together with the time of transition of the operation mode.

[0125] Each POS terminal 20 may store information regarding the transition of the operation mode, whether the operation mode was switched by an operation by a store clerk (by a mode switching operation, by reading a store clerk code, etc.) or whether the operation mode was switched without an operation by a store clerk (by a mode switching command, by the passage of a predetermined time, etc.). In the above case, each POS terminal 20 may store information regarding the basis on which the operation mode was switched (for example, that the operation mode was switched by an operation by a store clerk with the store clerk code "xxx", that the operation mode was switched by a mode switching command from the POS terminal 20 with the terminal identification information "xxx").

[0126] Instead of or in addition to the POS terminal 20, the store controller 10, a monitoring terminal, or the like may store information related to the operation mode.

[0127] Furthermore, the information on the operation mode stored as described above may be output (displayed, transmitted, printed, etc.) as necessary. For example, the POS terminal 20 may print information (information that only the store clerk can recognize, or information that can also be recognized by the customer) indicating that the process (registration process, settlement process) was performed in the full self-service mode on a receipt output in the full self-service mode. Receipts output in other operation modes may be printed in the same manner. Also, for example, the POS terminal 20 (or the monitoring terminal) may display the operation mode at the time of processing. As an example, when a transaction number (information that can identify a transaction) is input into a predetermined search screen or the like, the POS terminal 20 (or the monitoring terminal) may display the terminal (terminal identification information, etc.) on which the process was performed and the operation mode (information that can identify the operation mode) for at least one of the registration process and the settlement process for the corresponding transaction.

[0128] In the following description, it is assumed that the POS terminals 20-1 and 20-2 are in the normal mode (specifically, the normal mode (standard mode)), and the POS terminal 20-3 is in the full self mode.

[0129] (Display example of POS terminal 20 in full self-service mode) Fig. 15 and Fig. 16 are display examples of the POS terminal 20 in the full self-service mode. Specifically, Fig. 15(A), Fig. 15(B), Fig. 16(A) to Fig. 16(F) are all display examples of the customer-side display unit 205 of the POS terminal 20-3 in the full self-service mode.

[0130] Fig. 15(A) shows the display contents of the registration start screen before the start of the registration process. In Fig. 15(A), the registration start button BT30 on the right of the screen is a button for instructing the start of product registration. A customer operates the registration start button BT30 when starting product registration. The buttons BT35 to BT37 at the bottom left of the screen are buttons for switching the display language between English, Chinese, and Korean, respectively.

[0131] Fig. 15(B) shows the display contents of the registration screen in a state where the second item (daifuku mochi) has been registered. When the registration start button BT30 is operated on the registration start screen shown in Fig. 15(A), the POS terminal 20-3 displays a registration screen in a state where no items have been registered yet, but for the sake of convenience, Fig. 15(B) shows the registration screen after the items (tea and daifuku mochi) have already been registered.

[0132] In FIG. 15(B), image GA01 at the bottom left of the screen indicates the state of the other terminal (POS terminal 20-1) (specifically, that it is in normal mode). Image GA02 at the bottom left of the screen indicates the state of the other terminal (POS terminal 20-2) (specifically, that it is in normal mode). The checkout button BT32 at the bottom right of the screen is a button for instructing the end of product registration. The customer presses the checkout button BT32 after product registration is complete. The store clerk call button BT33 is a button for calling a store clerk. The customer presses the store clerk call button BT33 when calling a store clerk (for example, when the customer needs the support of a store clerk).

[0133] As described above, the buttons BT35 to BT37 are buttons for switching the display language to English, Chinese, and Korean, respectively. The "vegetable" button BT38 is a button for displaying each preset key for vegetables (see FIG. 17).

[0134] Fig. 16(A) shows the display contents of the settlement screen (payment method selection screen) displayed when starting the settlement process. For example, when the checkout button BT32 is operated on the registration screen (see Fig. 15(B)), the POS terminal 20-3 displays the payment method selection screen as shown in Fig. 16(A).

[0135] Fig. 16(B) shows the display contents of the settlement screen (deposit screen) displayed when starting a cash payment. For example, when cash is operated on the payment method selection screen (see Fig. 16(A)), the POS terminal 20-3 displays the deposit screen as shown in Fig. 16(B).

[0136] Fig. 16(C) shows the display contents of the settlement screen (deposit screen) displayed when the deposit amount is decided. For example, when the POS terminal 20-3 receives cash (deposit) that is equal to or greater than the payment amount (purchase amount), the POS terminal 20-3 displays the deposit screen as shown in Fig. 16(C).

[0137] Fig. 16(D) shows the display contents of the settlement screen (change screen) displayed when dispensing change. For example, when the END (receipt) button BT40 is operated on the deposit screen (Fig. 16(C)), the POS terminal 20-3 displays the change screen as shown in Fig. 16(D).

[0138] Fig. 16(E) shows the display contents of the settlement screen (receipt screen) displayed when the change has been removed. For example, when the change has been removed from the outlet of the change dispenser 209, the POS terminal 20-3 displays a receipt screen as shown in Fig. 16(E). The POS terminal 20 may have a sensor such as a photosensor installed near the outlet, and may determine that the change has been removed when the sensor recognizes an object (presumably a customer's hand). Fig. 16(F) shows the pause screen displayed in pause mode (pause state).

[0139] After displaying the receipt screen (FIG. 16(E)), the POS terminal 20-3 displays the registration start screen (FIG. 15(A)). For example, the POS terminal 20-3 displays the registration start screen after the receipt is removed from the issuing port of the printing unit 213. The POS terminal 20 may be equipped with a sensor capable of recognizing that the receipt has been removed from the issuing port. Also, if no change is to be made, the screen may transition from the deposit screen (FIG. 16(C)) to the receipt screen (FIG. 16(E)) without displaying the change screen (FIG. 16(D)).

[0140] (Display example of POS terminal 20 in normal mode) 17 to 22 are display examples of the POS terminal 20 in the normal mode. Specifically, Fig. 17(A), Fig. 18(A), Fig. 19(A), Fig. 20(A), Fig. 21(A), and Fig. 22(A) are all display examples of the store clerk display unit 210 of the POS terminal 20-1 in the normal mode (standard mode). Fig. 17(B), Fig. 18(B), Fig. 19(B), Fig. 20(B), Fig. 21(B), and Fig. 22(B) are all display examples of the customer display unit 205 of the POS terminal 20-1 in the normal mode (standard mode).

[0141] 17(A) shows the display contents on the initial state registration screen on the store clerk display unit 210. In the following explanation, unless otherwise specified, the initial state refers to a state in which no processing is progressing, for example, a state in which no products have been registered yet, and no payment (settlement) has been made yet (no payment method has been selected, no cash has been inserted, no gift certificates have been registered, etc.), and no customer has been made yet (no membership card has been read, etc.).

[0142] In Fig. 17(A), the tab area T1 in the upper right corner of the screen is a tab corresponding to each display content (display screen). The POS terminal 20-1 can interrupt the registration process of the customer (the reason for interruption is to return to the store to add an item to be purchased, etc.) and perform the registration process of the next customer. In other words, the POS terminal 20-1 displays a new registration screen for the next customer while retaining (storing) the display content (registration content) of the registration screen for the customer based on the operation of the store clerk. In the example shown in Fig. 17(A), there is one tab (tab area T1), but the POS terminal 20-1 displays tabs (tab areas T1, T2, T3, ...) in number according to the number of registration screens (number of customers) in progress, and switches the registration screen to be enabled (active) according to the operation (pressing) of the tab.

[0143] In tab area T1, information that distinguishes the tab from other tabs (the number "1" in the example of FIG. 17(A)) is displayed. In addition, tab area T1 is provided with a display field HR01 that displays the amount of money deposited by the customer. In addition to the above, various other information (described later) is also displayed in tab area T1, although this is not shown in the example shown in FIG. 17(A).

[0144] An image GA02 at the bottom left of the screen indicates the state of the other terminal (the POS terminal 20-2) (specifically, the normal mode). An image GA03 at the bottom left of the screen indicates the state of the other terminal (the POS terminal 20-3) (specifically, the full self mode).

[0145] Fig. 17(B) shows the initial display contents on the customer display unit 205. That is, when the POS terminal 20-1 displays the registration screen on the store clerk display unit 210 as shown in Fig. 17(A), the POS terminal 20-1 displays the small screen (small window) SG01 on the customer display unit 205, superimposed on the settlement screen (deposit screen), as shown in Fig. 17(B).

[0146] The small screen SG01 allows the customer to select a payment method. The customer selects either cash, credit, or electronic money as the payment method on the small screen SG01. If the customer desires cash as the payment method, he / she may insert cash (a deposit) before selecting cash as the payment method on the small screen SG01. When any payment method is selected on the small screen SG01, the POS terminal 20-1 clears the small screen SG01. Also, when cash is inserted before a payment method is selected on the small screen SG01, the POS terminal 20-1 processes it as if cash was selected as the payment method, and clears the small screen SG01.

[0147] When a can of beer is registered by a store clerk while the POS terminal 20-1 is displaying the registration screen of FIG. 17(A) on the store clerk display unit 210, the POS terminal 20-1 displays a registration screen as shown in FIG. 18(A) on the store clerk display unit 210.

[0148] 18(A), a subtotal button BT10 at the bottom right of the screen is a button for instructing the end of product registration. After completing product registration, the store clerk operates (touches) the subtotal button BT10.

[0149] The 20-2 register button BT12 is a button for designating the 20-2 register (POS terminal 20-2). When the store clerk designates the POS terminal 20-2 as the terminal to which registration information is to be transmitted, the clerk operates the 20-2 register button BT12. "(Normal)" displayed on the 20-2 register button BT12 indicates that the operation mode of the POS terminal 20-2 corresponding to the 20-2 register button BT12 is the normal mode.

[0150] The 20-3 register button BT13 is a button for designating the 20-3 register (POS terminal 20-3). When the store clerk designates the POS terminal 20-3 as the terminal to which registration information is to be transmitted, the clerk operates the 20-3 register button BT13. "(Full self-service mode)" displayed on the 20-3 register button BT13 indicates that the operation mode of the POS terminal 20-3 corresponding to the 20-3 register button BT13 is the full self-service mode.

[0151] The receipt button BT15 is a button for issuing a receipt in the printing unit 213. A store clerk operates the receipt button BT15 when executing a process on the POS terminal 20 that read the receipt (the POS terminal 20 from which the customer has read the receipt).

[0152] In addition, when comparing the POS terminal 20 in the normal mode with the POS terminal 20 in the full self-service mode as the destination of the registration information, the POS terminal 20 in the full self-service mode is more preferable as the destination of the registration information than the POS terminal 20 in the normal mode. The POS terminal 20 in the normal mode is basically operated by a store clerk (see Figs. 7 and 8), so there is a continuous process (e.g., registration process, customer service, etc.) and it is highly likely that the registration information cannot be processed immediately even if it is transmitted, and even if it is free (even if there is neither a store clerk nor a customer), it is basically preferable to keep it free in order to immediately respond to customers who request the support of a store clerk, whereas the POS terminal 20 in the full self-service mode can transmit the registration information and process it immediately if there is no customer, and even if there is a customer, the above-mentioned problem is unlikely to occur because the process can be simply performed in order.

[0153] In view of the above, the clerk is notified as to whether or not the POS terminal 20 to which the registration information is to be sent is preferable, or which of the multiple destinations to which the registration information is to be sent is more preferable. As an example, in FIG. 18(A), the outline of the 20-3 register button BT13 corresponding to the POS terminal 20-3 in the full self-service mode, which is a relatively preferable destination to which the registration information is to be sent, is shown by a solid line, and the outline of the 20-2 register button BT12 corresponding to the POS terminal 20-2 in the normal mode, which is a relatively unpreferable destination to which the registration information is to be sent, is shown by a broken line. Note that the above-mentioned notification by the outline is only an example, and the notification mode is not limited as long as the clerk can recognize whether or not the POS terminal 20 to which the registration information is to be sent is preferable, or which of the multiple destinations to which the registration information is to be sent is more preferable. For example, the background color of the button for the relatively unpreferable one may be grayed out, or a penalty mark or a diagonal line may be added to the entire button. In addition, the display size, shape, and display position of the button may be varied depending on whether or not it is desirable as a POS terminal 20 to which the registration information is to be sent, and some information (such as a badge-like image saying "Preferred" or "Recommended") may be added to the button.

[0154] When the POS terminal 20-1 displays a registration screen as shown in Fig. 18(A) on the store clerk display unit 210, it displays the small screen SG01 superimposed on the settlement screen (deposit screen) as shown in Fig. 18(B) on the customer display unit 205. Note that in the settlement screen (deposit screen) of Fig. 17(B), no products were registered so the total amount was 0 yen, but in the settlement screen (deposit screen) of Fig. 18(B), a can of beer costing 215 yen has been registered so the total amount is 215.

[0155] When a customer deposits 500 yen while the registration screen of FIG. 18(A) is being displayed on the store clerk display unit 210, the POS terminal 20-1 displays a registration screen such as that shown in FIG. 19(A) on the store clerk display unit 210.

[0156] Since the customer has inserted 500 yen, the display field HR01 in the upper right corner of the screen in Fig. 19(A) shows 500. Also, since the customer has inserted 500 yen, the payment will be settled at the customer's own terminal (POS terminal 20-1), so the buttons (20-2 register button BT12, 20-3 register button BT13, and bill button BT15) used for settling at other terminals (POS terminal 20-2, POS terminal 20-3) are not displayed (are erased).

[0157] When the POS terminal 20-1 displays a registration screen as shown in Fig. 19(A) on the store clerk display unit 210, it displays a settlement screen (deposit screen) as shown in Fig. 19(B) on the customer display unit 205. Note that the small screen SG01 is cleared because the customer has inserted 500 yen.

[0158] When the POS terminal 20-1 is displaying the registration screen of Fig. 19(A) on the clerk display unit 210, and the clerk registers the second item (asparagus) and the third item (seaweed lunch box) and the customer inserts an additional 500 yen, the POS terminal 20-1 displays a registration screen as shown in Fig. 20(A) on the clerk display unit 210. As the customer has inserted an additional 500 yen, 1000 is displayed in the display field HR01 in the upper right corner of the screen in Fig. 20(A).

[0159] When the POS terminal 20-1 displays a registration screen such as that shown in FIG. 20(A) on the store clerk display unit 210, it displays a settlement screen (deposit screen) such as that shown in FIG. 20(B) on the customer display unit 205.

[0160] When the POS terminal 20-1 operates the subtotal button BT10 while the registration screen of Fig. 20(A) is displayed on the clerk display unit 210, the POS terminal 20-1 displays a small screen (small window) SG02 on the clerk display unit 210 as shown in Fig. 21(A) by superimposing it on the registration screen, and displays a settlement screen (deposit screen) as shown in Fig. 21(B) on the customer display unit 205. The small screen SG02 notifies the clerk of settlement-related information (total amount, amount deposited in the device (deposit amount)).

[0161] When the customer operates the finish (receipt) button BT40 while the POS terminal 20-1 is displaying the settlement screen (deposit screen) of Figure 21 (B) on the customer display unit 205, the POS terminal 20-1 displays the message screen MG1 superimposed on the registration screen as shown in Figure 22 (A) on the clerk display unit 210, and displays the settlement screen (change screen) as shown in Figure 22 (B) on the customer display unit 205.

[0162] The message screen MG1 notifies the store clerk about the change. The POS terminal 20-1 erases the message screen MG1 displayed superimposed on the registration screen without the operation of the store clerk (for example, automatically after a predetermined time has passed). The POS terminal 20-1 may erase the message screen MG1 displayed superimposed on the registration screen in response to the operation of the store clerk (such as touching the message screen MG1).

[0163] Although not shown in Figures 22 and onwards, the POS terminal 20-1 displays a settlement screen similar to that shown in Figure 16(E) and onwards on the customer display unit 205, and displays a message corresponding to the settlement screen on the store clerk display unit 210.

[0164] In the above description, the focus is on the overall processing in the POS terminal 20, and a state in which no processing is in progress (a state in which no product is registered, no cash is inserted, no payment type is selected, no gift certificates are registered, and no customer information is acquired) is referred to as the initial state, but there may be cases in which the focus is on a portion of the processing and the state is referred to as the initial state. For example, the cash-inserted product registration state (a state in which products are registered, cash is inserted, no payment type is selected, no gift certificates are registered, and no customer information is acquired) cannot be called the initial state when the focus is on the overall processing, but it may be called the initial state when the focus is on the state of selection of the payment type only. Also, it cannot be called the initial state when the focus is on the two states of product registration and payment type selection, but it may be called the initial state when the focus is on the two states of payment type selection and gift certificate registration.

[0165] In the example shown in Figure 21, when the subtotal key is operated, the POS terminal 20-1 displays the small screen SG02 superimposed on the registration screen (Figure 21 (A)). However, when the subtotal key is operated, the POS terminal 20-1 may display a small screen that displays the information displayed on the small screen SG02 instead of (switches to) the registration screen.

[0166] (An example of an operation mode switching process) Next, an example of the operation mode switching process of the POS terminal 20 will be described with reference to Figures 23 and 24. Figure 23 is a flowchart showing an example of the operation mode switching process performed by the POS terminal 20 when the mode switching button is pressed. Since each POS terminal 20 is provided with a mode switching button, the process shown in Figure 23 is started when the mode switching button is pressed in any of the POS terminals 20. The process shown in the flowchart in Figure 23 is started constantly (periodically at very short time intervals) in each POS terminal 20.

[0167] Step S201: The POS terminal 20 judges whether or not the mode switching button 211a has been pressed. If the mode switching button 211a has not been pressed, the POS terminal 20 proceeds to step S208. If the mode switching button 211a has been pressed, the POS terminal 20 proceeds to step S202. Step S202: The POS terminal 20 transmits a mode switching command to the other POS terminals 20, and proceeds to step S203.

[0168] Step S203: The POS terminal 20 judges whether or not the terminal itself is in a process. The process here is, for example, a product registration process or a settlement process for accepting payment from a customer. If the POS terminal 20 itself is in a process, the POS terminal 20 proceeds to step S204. If the POS terminal 20 itself is not in a process, the POS terminal 20 proceeds to step S206. Step S204: The POS terminal 20 notifies (displays) that the terminal is processing, and proceeds to step S205. Step S205: The POS terminal 20 judges whether the currently running process has ended. The POS terminal 20 waits until the currently running process has ended, and when the currently running process has ended, the process proceeds to step S206.

[0169] Step S206: The POS terminal 20 performs a mode switching process, and proceeds to step S207. The mode switching process is a process of switching to a mode different from the current mode, for example, a process of switching to any one of a normal mode, a checkout-only mode, and a full self-service mode, which is different from the current mode. Step S207: The POS terminal 20 notifies the user that the mode switching of the terminal has been completed, and proceeds to step S208.

[0170] Step S208: The POS terminal 20 judges whether or not it has received information indicating that processing is in progress from the other POS terminal 20 to which the mode switching command was sent. If the POS terminal 20 has not received information indicating that processing is in progress from the other POS terminal 20, it proceeds to step S210. If the POS terminal 20 has received information indicating that processing is in progress from the other POS terminal 20, it proceeds to step S209.

[0171] Step S209: The POS terminal 20 notifies the other POS terminals 20 that processing is in progress, and proceeds to step S210. Step S210: The POS terminal 20 judges whether or not information indicating that mode switching is complete has been received from the other POS terminal 20. If the POS terminal 20 does not receive information indicating that mode switching is complete from the other POS terminal 20, the POS terminal 20 ends the series of processes. If the POS terminal 20 receives information indicating that mode switching is complete from the other POS terminal 20, the POS terminal 20 proceeds to step S211. Step S211: The POS terminal 20 notifies the other POS terminals 20 that the mode switching has been completed, and ends the series of processes.

[0172] Next, the mode switching process performed by the POS terminal 20 that has received a mode switching command will be described with reference to Fig. 24. Fig. 24 is a flowchart showing an example of the operation mode switching process performed by the POS terminal 20 that has received a mode switching command. The process shown in the flowchart of Fig. 24 is constantly (periodically at very short time intervals) started in each POS terminal 20.

[0173] Step S221: The POS terminal 20 judges whether or not a mode switching command has been received. If the POS terminal 20 has not received a mode switching command, the POS terminal 20 ends the series of processes. If the POS terminal 20 has received a mode switching command, the POS terminal 20 proceeds to step S222. Step S222: The POS terminal 20 judges whether or not the terminal itself is in a process. The process here is, for example, a product registration process or a settlement process for accepting payment from a customer. If the POS terminal 20 is in a process, the POS terminal 20 proceeds to step S223. If the POS terminal 20 is not in a process, the POS terminal 20 proceeds to step S225.

[0174] Step S223: The POS terminal 20 transmits a message to the POS terminal 20 that transmitted the mode switching command that the processing is in progress, and the process proceeds to step S224. Step S224: The POS terminal 20 judges whether the currently running process has ended. The POS terminal 20 waits until the currently running process has ended, and when the currently running process has ended, the process proceeds to step S225.

[0175] Step S225: The POS terminal 20 performs a mode switching process, and proceeds to step S226. Step S226: The POS terminal 20 transmits information indicating that the mode switching has been completed to the POS terminal 20 that transmitted the mode switching command, and proceeds to step S227. Step S227: The POS terminal 20 notifies the user that the mode switching of the terminal has been completed, and ends the series of processes.

[0176] (One example of screen transition when correcting a product in full self-service mode) Next, an example of screen transition when correcting a product in full self-service mode will be described with reference to Figs. 25 to 27. Figs. 25 to 27 are explanatory diagrams showing one example of screen transition when correcting a registered product in full self-service mode. In the following description and drawings, the same reference numerals are used for the contents of the screen transitions similar to those described above, and the description will be omitted.

[0177] FIG. 25(A) shows that in the full self-service mode, two products, "tea" and "sweet potato", have been registered by a customer. For example, for "tea", the customer has the POS terminal 20 read a barcode to register the product. For "sweet potato", the customer selects an area (button) indicating "sweet potato" from among the preset keys to register the product. Also, FIG. 25(A) displays guidance display 2501. Guidance display 2501 indicates that the customer can correct the registered product by pressing and holding the area indicating the product that he or she wishes to correct (change).

[0178] As shown in FIG. 25(A), suppose that a customer presses and holds the area showing "sweet potato." In other words, suppose that the customer performs an operation to make a correction to the product "sweet potato." In this case, the screen shown in FIG. 25(B) is displayed. FIG. 25(B) shows a confirmation screen for asking whether or not to cancel "sweet potato." If the customer selects "Yes" on the confirmation screen, the screen is displayed as shown in FIG. 25(C). Note that if the customer selects "No" on the confirmation screen, the screen is returned to, for example, the screen shown in FIG. 25(A).

[0179] FIG. 25(C) shows a notification screen that a store clerk is being called to cancel "sweet potato." Also, in FIG. 25(C), the area in which "sweet potato" is registered is displayed in a different display mode from the normal display mode (bold, framed, special color, etc.) so that it is clear that it is a product that needs correction. This allows the store clerk to know at a glance which product needs correction when he or she arrives. It also becomes clear to the customer which product needs correction.

[0180] Here, the timing for calling the store clerk may be the timing when "Yes" shown in FIG. 25(B) is pressed (the timing after the confirmation screen appears), or the timing when the product is pressed and held in FIG. 25(A) (the timing of the long press). By calling the store clerk at the timing of the long press, the store clerk can be called quickly. Also, by calling the store clerk after the confirmation screen appears, it is possible to prevent the store clerk from being called due to a customer's incorrect operation, or due to a customer's operating error or misunderstanding. Also, the notification to call the store clerk is sent, for example, from the POS terminal 20 operated or viewed by the store clerk, a mobile terminal carried by the store clerk, a management device, etc.

[0181] Fig. 26(D) shows the screen when a store clerk goes to the POS terminal 20 where the correction operation was performed and presses the store clerk button. When the store clerk presses the store clerk button in Fig. 26(D), the screen transitions to the screen shown in Fig. 26(E).

[0182] In FIG. 26 (E), a notification is displayed to prompt the clerk to read the clerk code. When the clerk reads the clerk code attached to his / her name tag, for example, into the POS terminal 20, the clerk is authenticated. If the authentication is successful, the screen transitions to the screen shown in FIG. 26 (F). On the other hand, if the authentication is unsuccessful, for example, an error message is displayed. In addition to displaying the error message, another clerk may be called. In this case, the other clerk may go to the POS terminal 20 where the correction operation was performed and perform authentication, so that the correction can be approved by the other clerk. Note that the authentication of the clerk is not limited to authentication using the clerk code, and may be biometric authentication such as fingerprint authentication, or authentication by inputting a password.

[0183] (F) of FIG. 26 shows a confirmation screen for approval by the store clerk. The store clerk visually checks (by checking the products in the basket) whether the corrections entered by the customer are correct (whether they are an incorrect operation or registration), and if they are determined to be correct, presses "Yes" on the confirmation screen. If the store clerk selects "Yes" on the confirmation screen, the screen transitions to that shown in (G) of FIG. 27. On the other hand, if the store clerk selects "No" on the confirmation screen, the series of correction operations is canceled, and the screen returns to, for example, that shown in (A) of FIG. 25. In this case, the corrections are not approved.

[0184] FIG. 27 (G) shows a notification screen that the correction (cancellation) has been completed. The canceled product (sweet potato) is not hidden, but is clearly indicated as a canceled product by, for example, drawing a line through it. This allows customers and store clerks to easily understand that the product has been canceled. To be more specific, if the canceled product is hidden, when a customer checks the canceled product, the customer checks whether the product to be purchased matches the displayed product one by one to confirm that the canceled product is not displayed. This check is troublesome for customers, and is even more troublesome when a large number of products are to be purchased. In this embodiment, by displaying the canceled product with a line through it, a customer can easily understand the product to be corrected even when a large number of products are registered.

[0185] As shown in Figures 25 to 27, in this embodiment, the customer performs part of the correction operation and the store clerk only needs to press the approval button, which shortens the customer's waiting time for correction and simplifies the operation of the store clerk. Therefore, correction of registered products can be performed efficiently.

[0186] (Other screen examples when correcting an item in Full Self Mode) Next, another example of a screen when correcting a product in the full self-service mode will be described with reference to Fig. 28. Fig. 28 is an explanatory diagram showing another example of a screen when correcting a product in the full self-service mode. Note that Fig. 28 differs from the screens shown in Figs. 26 and 27 in that it accepts changes to the quantity.

[0187] FIG. 28(A) shows that in full self-service mode, two products, "tea" and "sweet potato," have been registered by a customer. As shown in FIG. 28(A), assume that the customer presses and holds the area showing "tea." In this case, the screen shown in FIG. 28(B) appears. FIG. 28(B) shows a screen that accepts changes to the quantity. In FIG. 28(B), when the "+" button is pressed, the quantity is increased according to the number of times it is pressed. On the other hand, when the "-" button is pressed, the quantity is decreased according to the number of times it is pressed. Note that the product can be canceled by setting the quantity to "0," in the same way as in FIG. 27 and FIG. 28.

[0188] In (B) of Fig. 28, when a change to the quantity is accepted, the change button 2801 becomes operable. Here, assume that the change button 2801 is pressed after a change to increase the quantity is accepted. In this case, since the increase in the quantity is not recognized as fraudulent behavior, the increase in the quantity is accepted as is without the need for approval by a store clerk, and the screen returns to the registration screen of (A) of Fig. 28.

[0189] On the other hand, suppose that the change button 2801 is pressed after accepting a change that decreases the quantity. In this case, a store clerk is called, as it is necessary for the store clerk to confirm whether or not the correction is legitimate. However, for products that have been registered by reading a barcode, it is not possible to change the quantity to "0." Specifically, as shown in FIG. 28(B), when the quantity is "1," the customer presses the "-" button. In this case, the screen transitions to the screen shown in FIG. 28(C).

[0190] (C) in Figure 28 shows a screen indicating that a product that has been registered by scanning a barcode cannot be changed to "0." In the case of products with barcodes, it is possible for a customer to mistakenly scan the barcode twice in a row, resulting in an erroneous registration. For this reason, changes such as changing the quantity from "2" to "1" or from "3" to "2" can occur, so corrections to reduce the quantity to a number excluding "0" are acceptable.

[0191] On the other hand, for products with barcodes, since reading the barcode makes it clear that the product actually exists, changing the quantity to "0" is not anticipated. For this reason, changing the quantity of products with barcodes from "1" to "0" is likely to be an operational error, and measures are taken to prevent such errors from occurring.

[0192] Even for products with barcodes, there are cases where a customer wants to cancel a purchase after registering the product, for example, because the price was unexpected. In this case, the customer can press the store clerk call button to call a store clerk, who can then cancel the purchase. The store clerk can cancel the purchase by, for example, displaying a list of products through the operation of a store clerk who has been successfully authenticated using the store clerk code, and selecting the product to be canceled from the list.

[0193] It may be possible for a store clerk to change the settings as to whether to accept deletion of a product by pressing an area showing a product as shown in Figures 25 to 27, or to accept a change in quantity as shown in Figure 28. Also, a selection screen may be displayed to allow a customer to select whether to accept deletion of a product or a change in quantity by pressing an area showing a product.

[0194] (An example of product registration processing in the full self-service mode performed by the POS terminal 20) FIG. 29 is a flowchart showing an example of a product registration process performed by the POS terminal 20 in the full self-service mode. Step S301: The POS terminal 20 judges whether or not there is a touch on the store clerk display unit 210 (preset key), an operation on the key operation unit 211, a scan on the store clerk scanner unit 212, etc. If there is no scanning, etc., the POS terminal 20 waits, and if there is a scanning, etc., the POS terminal 20 proceeds to step S302.

[0195] Step S302: The POS terminal 20 registers the product and displays it on the store clerk display unit 210, and then the process proceeds to step S303. Step S303: The POS terminal 20 judges whether or not the correction of the product has been accepted. If the correction of the product has not been accepted, the POS terminal 20 proceeds to step S306. If the correction of the product has been accepted, the POS terminal 20 proceeds to step S304. Step S304: The POS terminal 20 judges whether the change is an increase in the quantity. If the POS terminal 20 judges that the change is not an increase in the quantity, that is, that the change is a decrease in the quantity, the process proceeds to step S305. If the POS terminal 20 judges that the change is an increase in the quantity, the process proceeds to step S306.

[0196] Step S305: The POS terminal 20 performs a correction process and returns to step S301. Details of the correction process will be described later with reference to FIG. Step S306: The POS terminal 20 judges whether or not the subtotal key of the key operation unit 211 has been pressed. If the subtotal key has not been pressed, the POS terminal 20 returns to step S301. If the subtotal key has been pressed, the POS terminal 20 proceeds to step S307.

[0197] Step S307: The POS terminal 20 judges whether or not the correction of the product has been accepted. If the correction of the product has not been accepted, the POS terminal 20 proceeds to step S308. If the correction of the product has been accepted, the POS terminal 20 proceeds to step S309.

[0198] Step S308: The POS terminal 20 judges whether or not the settlement is complete. In the settlement, the POS terminal 20 displays a sub-screen and issues a receipt or the like when it accepts settlement operations such as input of the deposit amount or pressing of the current total button. In addition, in the settlement, the POS terminal 20 may dispense change according to the deposit amount and the current total. If the settlement is not complete, the POS terminal 20 returns to step S307. If the settlement is complete, the POS terminal 20 ends the series of processes.

[0199] Step S309: The POS terminal 20 judges whether the change is an increase in the quantity. If the POS terminal 20 judges that the change is not an increase in the quantity, that is, that the change is a decrease in the quantity, the process proceeds to step S310. If the POS terminal 20 judges that the change is an increase in the quantity, the process proceeds to step S311.

[0200] Step S310: The POS terminal 20 performs a correction process, and proceeds to step S311. Details of the correction process will be described later with reference to FIG. Step S311: The POS terminal 20 performs a subtotal change process to change the subtotal amount, and then proceeds to step S308.

[0201] (An example of product correction processing performed by the POS terminal 20 in the full self-service mode) Fig. 30 is a flowchart showing an example of a product correction process in the full self-service mode performed by the POS terminal 20. The correction process shown in Fig. 30 shows details of the processes shown in steps S305 and S310 in Fig. 29. The following description will be given as the process of step S305.

[0202] Step S321: The POS terminal 20 calls the clerk from another terminal (another POS terminal 20, a mobile terminal carried by the clerk, or a management device), and proceeds to step S322. Step S322: The POS terminal 20 determines whether or not the clerk code has been entered. The clerk code is entered, for example, by the clerk having the clerk scanner unit 212 read the clerk code attached to the clerk's name tag, or by the clerk operating the key operation unit 211 to directly enter the clerk code (number). The POS terminal 20 waits until the clerk code is entered, and proceeds to step S323 when the clerk code is entered.

[0203] Step S323: The POS terminal 20 judges whether or not the authentication of the store clerk using the store clerk code has been successful. If the authentication of the store clerk has failed, the POS terminal 20 proceeds to step S324. If the authentication of the store clerk has succeeded, the POS terminal 20 proceeds to step S325. Step S324: The POS terminal 20 notifies the error, and returns to step S301. In the correction process in step S310 of Fig. 29, the process proceeds to step S311 after the process in step S324. Step S325: The POS terminal 20 judges whether or not the approval result has been received from the store clerk. The POS terminal 20 waits until the approval result is received from the store clerk, and when the approval result is received, the process proceeds to step S326.

[0204] Step S326: The POS terminal 20 judges whether the accepted approval result is an approval result that approves the correction. If the accepted approval result is an approval result that does not approve the correction, the POS terminal 20 returns to step S301. In this case, the correction is not made. If the accepted approval result is an approval result that approves the correction, the POS terminal 20 proceeds to step S327. Step S327: The POS terminal 20 corrects the registered product, and returns to step S301.

[0205] 29 and 30, when the POS terminal 20 receives a correction from a customer, it can correct the registered information by calling a store clerk and receiving approval from the store clerk. This allows the customer to perform part of the operations related to correcting the product information, thereby shortening the customer's waiting time for the correction. In addition, the store clerk only needs to go to the POS terminal 20 and perform the operation of approving, which simplifies the operations of the store clerk related to changing the product information.

[0206] (One example of screen transitions when correcting an item in semi-self-service mode) Next, an example of screen transitions when correcting an item in semi-self-service mode will be described with reference to Figs. 31 and 32. The following description will be given using as an example a POS system 1 in which a normal mode POS terminal 20 is placed upstream of the checkout path, and a semi-self-service mode POS terminal 20 is placed downstream of the checkout path. The following description will be given of a case in which, after a store clerk has completed product registration at the upstream POS terminal 20 in the POS system 1, corrections are made when a customer makes payment at the downstream POS terminal 20. The following description will be given of the screen transitions of the downstream POS terminal 20 in the POS system (the screen of the customer display unit 205).

[0207] Figures 31 and 32 are explanatory diagrams showing an example of the transition of the customer side screen when correcting an item in the semi-self mode. Figure 31(A) shows the screen of the customer side display unit 205 when multiple types of items are registered by the operation of a store clerk at the upstream POS terminal 20 and payment is made at the downstream POS terminal 20. Figure 31(A) shows a guide display 3101. The guide display 3101 indicates that the customer can correct the registered item by long pressing the area showing the item that the customer wants to correct.

[0208] As shown in FIG. 31B, it is assumed that a customer long presses the area showing "sweet potato". Specifically, for example, it is assumed that the customer does not recognize that he / she has purchased "sweet potato", but "sweet potato" is registered, and the customer performs an operation to correct "sweet potato". In this case, the screen shown in FIG. 31C is displayed. FIG. 31C shows a confirmation screen for whether or not to cancel "sweet potato". If the customer selects "Yes" on the confirmation screen, the screen is displayed as shown in FIG. 32D. At this time, the content of the correction and a request for approval of the correction are transmitted from the downstream POS terminal 20 to the upstream POS terminal 20. If the customer selects "No" on the confirmation screen in FIG. 31C, for example, the screen is returned to the screen shown in FIG. 31A.

[0209] FIG. 32(D) shows a notification screen that indicates that the customer must wait for approval from a store clerk (the store clerk who registered the product) at the upstream POS terminal 20 in order to cancel "sweet potato." An example of the screen displayed when the store clerk gives approval will be described later with reference to FIG. 33. In FIG. 32(D), the area where "sweet potato" is registered is displayed in a different display mode from the normal display mode (bold, framed, special color, etc.) so that it is clear that this is the product that needs to be corrected. This makes it clear to the customer which product needs to be corrected.

[0210] 32(E) shows a notification screen that indicates that the correction (cancellation) has been completed as a result of approval by a store clerk at the upstream POS terminal 20. Moreover, the product that was the subject of cancellation (sweet potato) is not hidden, but is clearly indicated as a cancelled product, for example by drawing a line through it. Note that if approval by the store clerk is not obtained, i.e., if the registration of "sweet potato" is not an error, the cancellation of "sweet potato" will not be permitted.

[0211] (An example of screen transition on the store clerk display unit 210 of the upstream POS terminal 20 when correcting a product) Next, an example of the transition of the screen on the store clerk display unit 210 of the upstream POS terminal 20 when correcting a product will be described with reference to Fig. 33. Fig. 33 is an explanatory diagram showing an example of the transition of the screen on the store clerk display unit 210 of the upstream POS terminal 20 when correcting a product. In the explanation of Fig. 33, it is assumed that the upstream POS terminal 20 is in normal mode, has finished registering the product of the customer who will make the settlement at the downstream POS terminal 20, and is registering the product of the next customer.

[0212] Fig. 33(A) shows a screen when registering the product of the next customer. Image GA02 at the bottom left of the screen of Fig. 33(A) shows that the state of the downstream POS terminal 20 (POS terminal 20-2) is in semi-self mode. Also, notification image 3301 shows a warning that the downstream POS terminal 20 needs support from a store clerk. Notification image 3301 is displayed, for example, when there is a request for approval of corrections or a request to call a store clerk from the downstream POS terminal 20. When the store clerk presses image GA02 or notification image 3301 in Fig. 33(A), the screen transitions to the screen shown in Fig. 33(B).

[0213] FIG. 33B shows a confirmation screen for approval by the store clerk. If the store clerk can instantly determine that the registration is incorrect, or if the store clerk can visually confirm that the registration is incorrect from the store clerk's position, the store clerk may perform an approval operation (pressing "Yes") at the upstream POS terminal 20. On the other hand, if the store clerk cannot confirm whether the registration is incorrect from the upstream POS terminal 20, the store clerk moves to the downstream POS terminal 20, visually confirms the content of the correction, and performs an approval operation. The downstream POS terminal 20 may also accept the approval of the store clerk. Specifically, the store clerk's confirmation screen for approval may also be displayed on the store clerk-side display unit 210 of the downstream POS terminal 20, so that the downstream POS terminal 20 may accept the approval of the store clerk. This allows the downstream POS terminal 20 to quickly accept the approval of the store clerk. The store clerk may return to the upstream POS terminal 20 and accept the approval of the store clerk at the upstream POS terminal 20.

[0214] If the clerk selects "Yes" on the confirmation screen shown in FIG. 33(B), the correction (cancellation) is completed. On the other hand, if the clerk selects "No", the correction is not approved. The approval result selected by the clerk is sent to the downstream POS terminal 20. If the clerk selects either "Yes" or "No" on the confirmation screen, the screen transitions to the screen shown in FIG. 33(C), and the registration of the next customer's products continues.

[0215] As shown in Figs. 31 to 33, in this embodiment, a correction operation is accepted from a customer at the time of settlement in the semi-self-service mode. Here, from the customer making the settlement at the downstream POS terminal 20, it may be difficult to call out to the store clerk at the upstream POS terminal 20 because the store clerk has registered the products for the next customer, and it may be mentally burdensome for the customer to propose (request) a correction. In this embodiment, the correction is not proposed directly to the store clerk, but the contents of the correction can be notified to the store clerk via the POS terminal 20, so that the mental burden on the customer when making a correction can be reduced.

[0216] Furthermore, when making a series of correction operations, the customer performs part of the correction operation, and the store clerk only has to press the approval button. This reduces the customer's waiting time for corrections and simplifies the operation of the store clerk. Furthermore, the store clerk can approve the correction while continuing to register the next customer's product. Therefore, corrections to registered products can be made efficiently.

[0217] 31 to 33, a case where a correction is made when a customer settles the bill has been described, but this is not limiting, and corrections can also be made when the customer's product is being registered. Specifically, while a store clerk is registering a product at the upstream POS terminal 20, a customer waiting for registration at the POS terminal 20 can press and hold an area showing the product (see (B) in each of Figs. 17 to 22) displayed on the customer side display unit 205, thereby accepting corrections while the product is being registered by the store clerk.

[0218] (Other screen examples when correcting an item in semi-self mode) Next, other screen examples when correcting a product in the semi-self-service mode will be described with reference to Figs. 34 to 36. Figs. 34 to 36 are explanatory diagrams showing other screen examples when correcting a product in the semi-self-service mode. Note that Figs. 34 to 36 differ from Figs. 31 to 33 in that, among the display areas showing the products, the items showing the product name, quantity, and price, the items shown in the display area that is long pressed are accepted for change.

[0219] (A) of each of Figures 34, 35, and 36 shows the screen of the customer-side display unit 205 when a payment is made at the downstream POS terminal 20 after a product has been registered at the upstream POS terminal 20. In (A) of Figure 34, it is assumed that the customer presses and holds the area showing the product name (the display area showing the characters "tomato") in the area of ​​the product "tomato". In this case, the screen transition is the same as that in the case of canceling "sweet potato" shown in Figure 31 (see (C) of Figure 31, and (D) and (E) of Figure 32).

[0220] Also, assume that a customer presses and holds the area of ​​the product "tomatoes" that indicates the quantity, as shown in FIG. 35(A). In this case, the screen transitions to the screen shown in FIG. 35(B). FIG. 35(B) shows a screen that accepts a change in quantity. The explanation of accepting a change in quantity is as explained in FIG. 28(B) and (C). Then, when the change in quantity is confirmed with the approval of the store clerk in FIG. 35(B), the screen transitions to the screen shown in FIG. 35(C).

[0221] Figure 35(C) shows a notification screen that the correction (change in quantity) has been completed. The quantity and price of the product (tomatoes) before the change are not hidden, but are displayed in a different display mode from the normal display mode so that the content of the correction can be understood. This allows the customer to easily understand that the quantity of the product has been changed.

[0222] Also, as shown in FIG. 36(A), assume that a customer presses and holds the area showing the price within the area of ​​the product "Tomato." In this case, the screen transitions to the screen shown in FIG. 36(B). Here, for products on limited time sales or clearance items, the purchase price recognized by the customer may differ from the selling price registered in the preset key. For this reason, in this embodiment, it is possible to accept a change in price from the customer. FIG. 36(B) shows a screen that accepts a change in price. FIG. 36(B) shows a screen that can accept the input of the price from the customer using the numeric keypad.

[0223] In FIG. 36B, when the change in the amount is accepted, the OK button 3601 becomes operable. When the customer presses the OK button 3601 and obtains the approval of the store clerk, the change in the amount is confirmed, and the screen transitions to the screen shown in FIG. 36C. When the OK button 3601 is pressed, a notification image 3301 (see FIG. 33A) is displayed on the store clerk display unit 210 of the upstream POS terminal 20, and the store clerk's approval can be accepted. FIG. 36C shows a notification screen that the correction (change in amount) has been completed. In addition, the price of the product (tomatoes) before the change is not hidden, but is displayed so that the content of the correction can be understood. This allows the customer to easily understand that the price of the product has been changed.

[0224] 34 to 36, an example of correcting a product in the semi-self-service mode has been described, but corrections can also be made in the full-self-service mode in the same way. That is, in the full-self-service mode, when the items indicating the product name, quantity, and price are displayed in the display area showing the product, a change to the item indicated by the display area that has been pressed and held may be accepted.

[0225] It may be possible to change the settings by a store clerk as to whether to accept deletion of a product (including a change in quantity) by pressing an area showing a product as shown in Figs. 31 and 32, or to accept changes to the items by pressing an area showing the item of the product as shown in Figs. 34 to 36. It may also be possible to change the settings of items that can be corrected among a plurality of items by a store clerk. Specifically, for example, among the items showing the product name, quantity, and price, the product name and quantity may be set to be correctable, and the price may be set to not be correctable. In addition, the items to be corrected are not limited to the above-mentioned items, and may include items to which discount coupons are applied, items to which events such as time sales are applied, and the like.

[0226] (An example of a settlement process in the semi-self-service mode performed by the POS terminal 20) Fig. 37 is a flow chart showing an example of a settlement process in the semi-self mode performed by the downstream POS terminal 20 (account settlement device). The POS terminal 20 performing the process in Fig. 37 is the POS terminal 20 (also called the "account settlement device") located downstream. Step S341: The POS terminal 20 judges whether or not registration information has been received from the upstream POS terminal 20. The POS terminal 20 waits until it receives the registration information, and when it receives the registration information, it proceeds to step S342.

[0227] Step S342: The POS terminal 20 judges whether or not a correction has been received from the customer. If the POS terminal 20 has not received a correction from the customer, the process proceeds to step S347. If the POS terminal 20 has received a correction from the customer, the process proceeds to step S343. Step S343: The POS terminal 20 transmits an approval request to the upstream POS terminal 20 (also called the "registration device"), and proceeds to step S344.

[0228] Step S344: The POS terminal 20 judges whether or not the approval result has been received from the upstream POS terminal 20. The POS terminal 20 waits until the approval result has been received from the upstream POS terminal 20, and when the approval result has been received from the upstream POS terminal 20, the POS terminal 20 proceeds to step S345.

[0229] Step S345: The POS terminal 20 judges whether the received approval result is an approval result that approves the correction. If the received approval result is an approval result that does not approve the correction, the POS terminal 20 proceeds to step S347. In this case, the correction is not made. If the received approval result is an approval result that approves the correction, the POS terminal 20 proceeds to step S346.

[0230] Step S346: The POS terminal 20 receives the regenerated registration information from the upstream POS terminal 20, and proceeds to step S347. Step S347: The POS terminal 20 judges whether or not the settlement is complete. If the settlement is not complete, the POS terminal 20 returns to step S342. If the settlement is complete, the POS terminal 20 ends the series of processes.

[0231] By the above-mentioned process, when the downstream POS terminal 20 (the POS terminal 20 in the semi-self mode) accepts a correction from a customer, it requests approval from the upstream POS terminal 20, and when an approval result that approves the correction is obtained, it can receive the regenerated registration information. As a result, the customer performs part of the operation related to correcting the product information, and it is possible to shorten the waiting time for the customer to make the correction.

[0232] (An example of a process performed by the upstream POS terminal 20 when an approval request is received) Fig. 38 is a flowchart showing an example of a process performed by the upstream POS terminal 20 (registration device) when an approval request is received. The process shown in the flowchart in Fig. 38 is constantly (periodically at very short time intervals) started in the upstream POS terminal 20.

[0233] Step S361: The POS terminal 20 judges whether or not an approval request for correction of a registered product has been received from a downstream POS terminal 20 (payment device). The POS terminal 20 waits until the approval request is received, and when the approval request is received, the process proceeds to step S362.

[0234] Step S362: The POS terminal 20 notifies the store clerk that the approval request has been received, and proceeds to step S363. For example, the POS terminal 20 notifies the store clerk that the approval request has been received by displaying a notification image 3301 (see FIG. 33A) on the store clerk display unit 210. Step S363: The POS terminal 20 judges whether or not the approval result (see FIG. 33B) has been received from the store clerk. The POS terminal 20 waits until the approval result is received from the store clerk, and when the approval result is received, the process proceeds to step S364.

[0235] Step S364: The POS terminal 20 transmits the approval result to the downstream POS terminal 20, and proceeds to step S365. Step S365: The POS terminal 20 judges whether the accepted approval result is an approval result that approves the correction. If the accepted approval result is an approval result that does not approve the correction, the POS terminal 20 ends the series of processes. In this case, the correction is not made. If the accepted approval result is an approval result that approves the correction, the POS terminal 20 proceeds to step S366.

[0236] Step S366: The POS terminal 20 regenerates the registration information, and proceeds to step S367. Step S367: The POS terminal 20 transmits the registration information to the downstream POS terminal 20, and ends a series of processes.

[0237] Through the above-described process, the upstream POS terminal 20 (the POS terminal 20 in normal mode) can receive the approval request from the downstream POS terminal 20, accept the approval of the store clerk, and transmit the accepted approval result to the downstream POS terminal 20. Furthermore, when an approval result that approves the correction is accepted, the registration information can be regenerated and transmitted to the downstream POS terminal 20. This allows the store clerk to approve the correction of the previous customer's product information even when the store clerk is registering the next customer's product. This reduces the burden on the store clerk when giving approval.

[0238] According to the above-mentioned embodiment 1, since the customer performs some of the operations related to the change of the product information, and the store clerk only needs to perform the operation of approving, the operations of the store clerk related to the change of the product information can be simplified. Therefore, the registered products can be changed efficiently. This allows the product information to be changed appropriately, and the convenience of the product sales data processing device can be improved.

[0239] (Embodiment 2) Next, a second embodiment of the present invention will be described. In the first embodiment described above, a configuration was described in which product registration, product correction, correction approval, and settlement are performed in the POS terminal 20. In the second embodiment, a configuration will be described in which product registration and product correction are accepted by a mobile terminal, and correction approval and settlement are performed by a settlement device. In the description of the second embodiment, the same reference numerals will be used for the same components as in the first embodiment described above, and the description will be omitted as appropriate.

[0240] 39 is a network configuration diagram showing a shopping system according to embodiment 2 of the present invention. In FIG. 39, the shopping system includes a store controller (store computer, management device) 10, a cloud server 300, a settlement device 400, and a mobile terminal 500.

[0241] The cloud server 300 is a computer device equipped with a CPU, ROM, RAM, a communication unit, etc. The settlement device 400 is a computer device equipped with a CPU, ROM, RAM, a communication unit, a touch panel, a key operation unit, a scanner unit, a card settlement unit, a change dispenser, a printing unit, an audio output unit, etc. The settlement device 400 may be a device dedicated to settlement, or the POS terminal 20 of the first embodiment may be set in semi-self mode to become the POS terminal 20. The mobile terminal 500 is a computer device equipped with a CPU, ROM, RAM, a communication unit, an imaging unit (camera), a touch panel, an audio output unit, an audio input unit, etc.

[0242] The store controller 10 and the settlement device 400 are installed in a store and are communicatively connected via a LAN 11 (which may be wired or wireless). The store controller, the settlement device 400, and the mobile terminal 500 are each communicatively connected to a cloud server 300.

[0243] The cloud server 300 manages various types of information such as information on customers, information on stores, information on products for each store, etc. The information managed (generated and stored) by the cloud server will be described later with reference to FIG.

[0244] The mobile terminal 500 is a terminal device operated by a customer (such as a shopper who is a member of the store), and is, for example, a communication device equipped with a display screen, such as a smartphone, tablet device, or mobile phone. The mobile terminal 500 is a device that accepts product registration. In addition to typical communication and imaging functions (camera), the mobile terminal 500 has a function for scanning a barcode attached to a product to read the product code. In other words, the mobile terminal 500 has a recognition function for recognizing the barcode attached to the product.

[0245] The recognition function of the mobile terminal 500 may be capable of reading a product code, and may not be capable of identifying a product from the read product code. In other words, when a barcode exists as an object in a captured image (an image acquired as a through image) captured by the imaging function, the mobile terminal 500 may be capable of reading a product code from the barcode.

[0246] Furthermore, the mobile terminal 500 captures an image of a product (e.g., the surrounding area with a barcode attached thereto) and generates a captured image (image data). For example, the mobile terminal 500 generates a captured image by releasing the shutter at its own discretion. However, the mobile terminal 500 may also generate a captured image by releasing the shutter in accordance with an operation by a customer who is an operator.

[0247] Furthermore, the mobile terminal 500 may be equipped with an image recognition technology that extracts feature points from an image (through image, captured image) and recognizes an imaged subject (object, etc.). For example, the mobile terminal 500 may use the image recognition technology to identify (estimate) an imaged product. Specifically, the mobile terminal 500 may use the image recognition technology to identify fresh foods such as vegetables and fruits that do not have barcodes.

[0248] A predetermined application (application software) is installed in the mobile terminal 500. By starting the predetermined application, the mobile terminal 500 can read a product code and register a product corresponding to the read product code (by transmitting the product code to the cloud server 300 and registering the product).

[0249] Moreover, the mobile terminals 500 are, for example, owned by each customer. However, the mobile terminals 500 may be loaned by the store to the customer. The number of mobile terminals 500 (the number in operation) varies depending on the number of customers. In FIG. 39, two mobile terminals 500 are illustrated as an example, but in reality, the number will be tens, hundreds, or more.

[0250] The settlement device 400 is a device that settles the payment for products registered by a customer's registration operation using the mobile terminal 500. The settlement device 400 accepts payment by, for example, cash, credit card, prepaid card, and the like.

[0251] 39 illustrates a plurality of settlement devices 400, the number of settlement devices 400 may be one. Also, one store controller 10 may be installed in one store, or two or more store controllers 10 may be installed in one store.

[0252] (An example of information managed by the cloud server 300) Next, a description will be given of an example of information managed by the cloud server 300. Fig. 40 is an explanatory diagram showing an example of various information managed by the cloud server 300. The cloud server 300 stores various information including (A) customer information, (B) store information, and (C) basket information.

[0253] (A) of Fig. 40 shows an example of customer information. Customer information is information for managing individual customers. Specifically, customer information includes customer identification information, customer name, customer registration date, cancellation information, customer rank, and number of points.

[0254] The customer identification information is identification information that uniquely identifies a customer. The customer name is the customer's name or nickname, etc. The customer registration date is the date and time when the customer information was newly registered in the cloud server 300. The cancellation information is information that indicates the number of times a registered product was cancelled after being registered during shopping. The customer rank is a rank according to the customer's purchasing history.

[0255] The number of points is the number of points given to a customer for shopping using this application. The number of points may include the number of points for each store. The customer information shown in FIG. 40(A) is an example, and in the second embodiment, it is sufficient to include at least the customer identification information. When the cloud server 300 generates customer information for a new customer, it generates the customer identification information, the customer name, and the customer registration date, but does not generate other information (cancellation information, etc.) because the actual transaction (product registration) has not yet started.

[0256] (B) of FIG. 40 shows an example of store information. Store information is information for managing each store. Specifically, store information includes store identification information, store name, store identification information 1 (two-dimensional code information), and store identification information 2 (location information). Store identification information includes a store (trade name) or company code, and a branch code. Store name is the name of the store, and is composed of, for example, a store name (trade name) or company name, and a branch name.

[0257] Store identification information 1 and 2 are information for identifying a store where a transaction takes place (a store where goods are bought and sold). Store identification information 1 is, for example, information in the form of a two-dimensional code (QR code (registered trademark), etc.). Store identification information 2 is store location information (GPS information). In the example shown in FIG. 40(B), store identification information and store identification information 1 are stored separately, but since both are information that can uniquely identify a store, at least one of the pieces of information may be stored.

[0258] (C) of FIG. 40 shows an example of basket information. Basket information is information relating to a customer's purchases at a store. Specifically, basket information includes basket identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, and cancellation candidate information. Basket identification information is information for identifying the basket information. Specifically, basket identification information includes store identification information, a date, and a serial number (for example, a serial number specific to each store and date).

[0259] The transaction start date and time is the date and time when the transaction started, for example, the date and time when the basket information was generated. The transaction start date and time may be the registration date and time of one product (the date and time when the registered product information (registered product 1) shown in FIG. 40(C) was stored). The registration date and time of each product may also be stored separately.

[0260] The transaction end date and time is the end date and time of the transaction, for example, the settlement date and time. The settlement date and time may be the settlement start date and time or the settlement end date and time. The customer identification information is customer identification information that identifies the customer performing the transaction. Note that while the cloud server 300 generates the basket identification information, transaction start date and time, and customer identification information when generating the basket information, it does not generate other information (transaction end date and time, etc.) because this is before the start of the actual transaction (product registration).

[0261] Registered product information (total) is information that is updated each time a product is registered. Registered product information (total) includes the number of items (number of products) and the subtotal amount. Registered product information (1) is the registration information for the first product item. Registered product information (2) is the registration information for the second product item. In the example shown in Figure 40 (C), registered product information for the third and subsequent products is omitted.

[0262] The cancellation candidate information (current total) indicates the number of times that cancellation of a registered item has been accepted after the item was registered during this shopping trip. The cancellation candidate information (cancellation candidate 1) includes the item code indicating the item to be cancelled and the quantity of that item. Although not shown, when cancellation is actually completed with approval from a store clerk, cancellation information (not shown) indicating that cancellation has been completed is stored. Furthermore, the cancellation information is added to the previous history and stored in the customer information (A).

[0263] Next, the processing flow of the shopping system will be described with reference to Fig. 41. Fig. 41 is a sequence diagram showing the processing flow of the shopping system according to the second embodiment. Fig. 41 shows the flow from when a customer visits a store, registers a product to be purchased using the customer's mobile terminal 500, to when the customer completes payment for the product using the payment device 400.

[0264] Step S401: First, the mobile terminal 500 acquires information that identifies a store (for example, store identification information). Here, an example of how the information that identifies a store is acquired will be described. For example, a two-dimensional code indicating the store identification information is displayed near the entrance of the store. The two-dimensional code may be displayed on a specific display device, or may be displayed by printing on a medium.

[0265] The printed medium is, for example, a paper medium. This paper medium may be attached near the entrance of the store, or may be distributed to customers in the store. A customer who visits the store scans the two-dimensional code using a mobile terminal 500. This enables the mobile terminal 500 to obtain store identification information. The two-dimensional code may include store identification information for identifying the store.

[0266] Furthermore, when a predetermined application (application software) is started in response to an operation by a visiting customer, the mobile terminal 500 may display a screen that prompts the user to scan a two-dimensional code as an initial screen. Furthermore, when a two-dimensional code is scanned in response to an operation by a visiting customer, the mobile terminal 500 may start an application and display a screen that notifies the user that the mobile terminal 500 is currently connected to the cloud server 300 as an initial screen.

[0267] Another example of the manner in which the information identifying a store is acquired is the acquisition of location information. For example, the mobile terminal 500 acquires location information (GPS information) in response to an operation by a customer who has visited the store. This location information is information that replaces the store identification information. Note that the mobile terminal 500 may acquire location information by starting an app in response to an operation by a customer who has visited the store, and may display a screen notifying the user that the mobile terminal 500 is connected to the cloud server 300 as an initial screen.

[0268] In addition, the cloud server 300 identifies the store according to the location information from the mobile terminal 500, but in this identification, there are cases where a plurality of stores are identified (when one store cannot be identified). In this case, the cloud server 300 may transmit information indicating that to the mobile terminal 500. Then, the mobile terminal 500 may display a selection screen for allowing the customer to identify the store, or may notify the customer to scan a two-dimensional code indicating the store identification information.

[0269] The mobile terminal 500, which has acquired the store identification information, transmits the acquired store identification information together with the customer identification information to the cloud server 300 as a transaction start request (transmission / reception data D1 in FIG. 40). The customer identification information is information that is stored in the cloud server 300 and the mobile terminal 500, for example, when a new customer is registered (when an app is installed in the mobile terminal 500). Specifically, the information such as the name entered in the registration form is assigned the customer identification information by the cloud server 300, and is stored in the cloud server 300 and the mobile terminal 500.

[0270] Furthermore, when the mobile terminal 500 acquires the store identification information, the mobile terminal 500 may output information on the service being carried out in the store (information on flyers distributed on that day) and available coupon information on the display screen. For example, the mobile terminal 500 may make a transaction start request to the cloud server 300, and the information on the service and the coupon information may be transmitted from the cloud server 300.

[0271] The mobile terminal 500 also stores destination information (address of cloud server 30) when registering a new customer (when installing an app on the mobile terminal 500). The two-dimensional code displayed near the entrance of the store may contain destination information (address of cloud server 300) in addition to store identification information. The mobile terminal 500 can also access the cloud server 300 by scanning the two-dimensional code to obtain destination information together with store identification information.

[0272] Step S402: When cloud server 300 receives customer identification information and store identification information as a request to start a transaction from mobile terminal 500, it generates basket information for the transaction. Specifically, cloud server 300 generates basket identification information, transaction start date and time, and customer identification information (see FIG. 40(C)). Note that cloud server 300 does not generate other information (transaction end date and time, etc.) at this timing because it is before the start of the actual transaction (product registration).

[0273] Specifically, when cloud server 300 receives store identification information and customer identification information as a request to start a transaction from mobile terminal 500, it refers to the store information (see (B) of FIG. 40) to identify the store identification information. When cloud server 300 receives location information from mobile terminal 500, it refers to store identification information 2 of the store information to identify the store identification information corresponding to the location information. When the two-dimensional code includes the store identification information, cloud server 300 can also obtain the store identification information by combining the received two-dimensional code.

[0274] Furthermore, when cloud server 300 receives a transaction start request (store specification information and customer identification information) from mobile terminal 500, it acquires the current date and issues (assigns) a serial number. Furthermore, cloud server 300 combines the acquired store identification information, the acquired current date, and the issued serial number, and stores them as basket identification information. Furthermore, when cloud server 300 receives a transaction start request from mobile terminal 500, it stores the current date and time as the transaction start date and time (generation date and time) in the basket information. Furthermore, when cloud server 300 receives a transaction start request from mobile terminal 500, it stores the customer identification information received from mobile terminal 500 as the customer identification information in the basket information.

[0275] Step S403: When the cloud server 300 generates the basket for the transaction, it generates product registration initial screen information (screen information of the product registration screen, which is the initial screen), and transmits it to the mobile terminal 500. Specifically, the cloud server 300 transmits basket identification information to the mobile terminal 500 together with the product registration initial screen information (transmission / reception data D2 in FIG. 41).

[0276] Step S404: When the mobile terminal 500 receives the basket identification information and the product registration initial screen information from the cloud server 300, the mobile terminal 500 stores the basket identification information and displays the product registration initial screen on the display unit. The product registration initial screen is, for example, the screen before product registration in FIG. 42(A), and will be described in detail later.

[0277] Step S405: In response to a customer's operation, the mobile terminal 500 scans the barcode attached to the product and reads the product code. In Fig. 41, it is assumed that the barcode has been successfully scanned. Upon acquiring the product code, the mobile terminal 500 transmits the acquired product code and basket identification information to the cloud server 300 (see transmission / reception data D3 in Fig. 41).

[0278] Step S406: Upon receiving the product code and the basket identification information from the mobile terminal 500, the cloud server 300 identifies basket information including the received basket identification information.

[0279] Step S407: Cloud server 300 updates the product data included in the identified basket information. Specifically, when cloud server 300 receives the product code of item N, it stores the product code as the product code of registered product information (registered product N). Furthermore, cloud server 300 associates the product code, product name, and price and stores them as product information (registered product N). Cloud server 300 also updates the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered product information in the identified basket information.

[0280] Step S408: When the cloud server 300 updates the product data in the basket, it generates product registration update screen information (screen information of the product registration screen which is the update screen on which the registered product is added) and transmits it to the mobile terminal 500. Specifically, the cloud server 300 transmits basket identification information together with the product registration update screen information to the mobile terminal 500 (transmission / reception data D4 in FIG. 41).

[0281] Step S409: When mobile terminal 500 receives the basket identification information and product registration update screen information from cloud server 300, it displays a product registration update screen in which the product has been added to the registration screen. The product registration update screen is, for example, the screen shown in FIG. 42(A), and details will be described later. Note that, although not shown in FIG. 41 for ease of explanation, the processing of steps S405 to S409 is processing that is repeatedly executed each time a barcode attached to a product is scanned. In other words, the processing of steps S405 to S409 loops until a checkout instruction is received in step S410, which will be described later.

[0282] Step S410: The mobile terminal 500 accepts a checkout instruction operated by the customer. The checkout instruction is accepted, for example, by pressing the "Checkout button" shown in Figure 42, which will be described later.

[0283] Step S411: When the mobile terminal 500 receives a payment instruction, it generates a two-dimensional code. This two-dimensional code includes information (e.g., basket identification information) required for the settlement device 400 to execute the settlement process for the product to be purchased. When the mobile terminal 500 generates the two-dimensional code, it displays the generated two-dimensional code on the display unit. The display screen for the two-dimensional code is, for example, the screen shown in FIG. 41(D), and details will be described later.

[0284] Step S412: After completing the product registration, the customer goes to the location where the settlement device 400 is located. The settlement device 400 scans (reads) the two-dimensional code displayed on the display unit of the mobile terminal 500. Specifically, the code reading unit of the settlement device 400 (customer-side scanner unit 206 in FIG. 4 when the POS terminal 20 is applied as the settlement device 400) reads the two-dimensional code (basket identification information) displayed on the display unit of the mobile terminal 500 in response to an operation by a store clerk or a customer.

[0285] Step S413: When the settlement device 400 reads the two-dimensional code displayed on the display unit of the mobile terminal 500, it requests the calculation of the subtotal amount from the cloud server 300. For example, the settlement device 400 transmits a calculation request (subtotal calculation request information) requesting calculation of the subtotal amount and basket identification information restored from the two-dimensional code to the cloud server 300 (transmission and reception data D5 in FIG. 40).

[0286] Step S414: When the cloud server 300 receives the basket identification information and the sub-calculation output request information from the settlement device 400, the cloud server 300 identifies basket information including the received basket identification information.

[0287] Step S415: When the cloud server 300 identifies the basket information, it calculates (identifies) the subtotal amount (registered product information (total)) included in the identified basket information. If there is a discount for each product, in step S415, the discount amount for each product may be calculated to calculate the subtotal amount.

[0288] Step S416: When the cloud server 300 specifies the subtotal amount, it transmits subtotal information indicating the specified subtotal amount together with the basket identification information to the settlement device 40 (transmission / reception data D6 in FIG. 41).

[0289] Step S417: When the settlement device 400 receives the basket identification information and the subtotal information from the cloud server 300, it displays the subtotal on the display (customer-side display unit 205 in FIG. 4 when the POS terminal 20 is applied as the settlement device 400). The display screen for the subtotal (settlement screen) is, for example, the screen shown in FIG. 44(A), and details will be described later.

[0290] Step S418: The settlement device 400 displays the subtotal amount on the display and then executes the payment (settlement). Specifically, the settlement device 400 accepts the selection of the payment type. Furthermore, when the settlement is completed, the settlement device 400 issues a receipt and transmits settlement completion information together with the basket information to the cloud server 300. The cloud server 300 then stores the transaction end date and time (settlement date and time) for that basket.

[0291] In step S418, the customer selects a payment method for performing the payment process for the product on the payment screen. However, the payment method may be registered in advance in the app. If a payment method is registered, the payment device 400 does not need to display a screen for selecting a payment method. Even if a payment method is registered, the payment device 400 may display a screen for selecting a payment method.

[0292] When the payment method is cash, the settlement device 400 accepts the deposit, calculates the amount of change, and dispenses the change if there is any. The payment method can also be payment by gift certificate or by points of a point member. Coupons and discount tickets can also be used. Even in this case, the settlement device 400 performs the payment in the same manner as normal payment processing, such as dispensing change and issuing a receipt. When a store clerk is required, such as when collecting a gift certificate at the time of payment, the settlement device 400 calls the store clerk. Specifically, the settlement device 400 may call the store clerk when a payment method that requires a store clerk is selected. When a payment method that requires a store clerk is selected, the settlement device 400 may also issue a notification to guide the user to a service counter or a manned POS.

[0293] (An example of screen transition when accepting corrections to a product in the second embodiment) Next, an example of a screen transition when accepting correction of a product in embodiment 2 will be described with reference to Fig. 42 and Fig. 43. Fig. 42 is an explanatory diagram showing an example of a screen transition when accepting cancellation of a product in embodiment 2.

[0294] FIG. 42(A) shows that a customer operates the mobile terminal 500 to have the mobile terminal 500 read the barcodes of the products, and thus two products, "XX tea" and "XX bread", are registered. The screen of FIG. 42(A) is a screen displayed by the process of step 409 of FIG. 41. Note that in the screen before the product is registered (product registration initial screen: see step S404 of FIG. 41), the product items are displayed as blanks. Also, FIG. 42(A) shows a guide display 4201. The guide display 4201 shows that the customer can correct the registered product by pressing and holding the item field of the product that he / she wishes to correct (change). Note that the operation of correction is not limited to pressing and holding the item of the target product, and for example, a "correction button" may be displayed and the target product may be selected by pressing the button.

[0295] As shown in (A) of FIG. 42, suppose that the area showing "XX Bread" is pressed and held. In other words, suppose that the customer performs an operation to make a correction to the product "XX Bread". In this case, the screen shown in (B) of FIG. 42 is displayed. (B) of FIG. 42 shows a confirmation screen for asking whether or not to cancel "XX Bread". If the customer selects "No" on the confirmation screen, for example, the screen returns to that shown in (A) of FIG. 42, and it becomes possible to accept product registration again. On the other hand, if the customer selects "Yes" on the confirmation screen, the screen transitions to that shown in (C) of FIG. 42.

[0296] Here, the processing of mobile terminal 500 and cloud server 300 when the customer selects "Yes" on the confirmation screen will be described. When the customer selects "Yes" on the confirmation screen, mobile terminal 500 transmits information indicating a cancellation request, the product code to be canceled, and basket identification information to cloud server 300. When cloud server 300 receives this information from mobile terminal 500, it identifies basket information (see (C) in FIG. 40) that includes the received basket identification information.

[0297] The cloud server 300 updates the product data included in the identified basket information. Specifically, when the cloud server 300 receives the product code of the Nth item to be cancelled, the cloud server 300 refers to the registered product information of the identified basket information and stores the product (registered product N) corresponding to the product code as cancellation candidate information. The cancellation candidate information is information in which the product code, the product name, and the price are associated with each other (see (C) of FIG. 40). In addition, the cloud server 300 does not update the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered product information because the cancellation is not completed (approval by the store clerk is not completed). However, since it is expected that cancellation will be performed later, the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered product information may be updated, or both the updated value and the non-updated value may be stored. In addition, the cloud server 300 may transmit both the updated value and the non-updated value to the mobile terminal 500, so that both values ​​are displayed on the mobile terminal 500.

[0298] When the cloud server 300 updates the basket information, it generates product registration update screen information (screen information indicating that the cancellation has been accepted) and transmits it to the mobile terminal 500. When the mobile terminal 500 receives the product registration update screen information, it displays the screen of FIG. 42(C).

[0299] FIG. 42(C) shows the screen that appears when a request to cancel an item is accepted. FIG. 42(C) also displays a message that the cancellation of the item has not been finalized and that approval from a store clerk is required at the time of checkout. The item to be canceled (XX bread) is not hidden, but is clearly indicated as such by, for example, drawing a line through it. This allows the customer to easily identify the item to be canceled. If the customer continues shopping after FIG. 42(C) and then presses the "Checkout button," the screen transitions to the screen shown in FIG. 42(D).

[0300] FIG. 42(D) shows a display screen of a two-dimensional code used in the payment process for the product to be purchased. The processing of the mobile terminal 500 when the "Checkout button" is pressed is as shown in steps S410 and S411 of FIG. 41. FIG. 42(D) also displays "Approval Required" to indicate that approval from a store clerk is required for payment, just like FIG. 42(C). When the two-dimensional code shown in FIG. 42(D) is read by the payment device 400, the payment process will be carried out in the payment device 400.

[0301] (Other screen examples when correcting the product in embodiment 2) Fig. 43 is an explanatory diagram showing an example of a screen transition when accepting a change in the quantity of a product in embodiment 2. Note that Fig. 43 differs from the screen shown in Fig. 42 in that a change in the quantity is accepted.

[0302] FIG. 43(A) shows that two products, "XX tea" and "XX bread", have been registered by a customer operating the mobile terminal 500 to have the mobile terminal 500 read the product barcodes. As shown in FIG. 43(A), assume that the customer presses and holds the area showing "XX bread". In this case, the screen transitions to the screen shown in FIG. 43(B). FIG. 43(B) shows a screen for accepting changes to the quantity. In FIG. 43(B), when the "+" button is pressed, the quantity is increased according to the number of times it is pressed. On the other hand, when the "-" button is pressed, the quantity is decreased according to the number of times it is pressed. It is also possible to cancel a product by setting the quantity to "0", as in FIG. 42.

[0303] In (B) of Fig. 43, suppose that after accepting a change to increase the quantity, the confirm button 4301 is pressed. In this case, since the increase in quantity is not recognized as fraudulent, the increase in quantity is recognized as it is without requiring approval from a store clerk, and the screen returns to the registration screen of (A) of Fig. 43.

[0304] On the other hand, suppose that the confirm button 4301 is pressed after a change that decreases the quantity is accepted. In this case, the store clerk needs to confirm whether or not the correction is legitimate, and therefore the store clerk's approval is required at the time of payment. Also, for products that have been registered by reading a barcode, it may be arranged not to set the quantity to "0." Specifically, as shown in FIG. 43(B), when the quantity is "1," it may be arranged not to set it to "0" even if the customer presses the "-" button.

[0305] Even in this case, since a customer may wish to cancel, the quantity can be set to "0" and the store clerk can cancel the order at the time of payment. Also, as shown in FIG. 42 above, the store clerk may be able to change the settings as to whether to accept deletion of the product when the area showing the product is pressed, or to accept a change in the quantity when shown in FIG. 43. Also, a selection screen may be displayed to allow the customer to select whether to accept deletion of the product or a change in the quantity when the area showing the product is pressed.

[0306] (An example of the settlement screen in the second embodiment) Figure 44 is an explanatory diagram showing an example of a settlement screen in embodiment 2. (A) of Figure 44 shows the settlement screen displayed when the settlement device 400 reads a two-dimensional code (see (D) of Figure 44) displayed on the mobile terminal 500. The process of reading the two-dimensional code and displaying the settlement screen is as shown in steps S412 to S417 of Figure 41. The settlement screen in (A) of Figure 44 displays a message that a store clerk is being called.

[0307] When a store clerk near the settlement device 400 reads the store clerk code on his / her name tag into the settlement device 400, the store clerk is authenticated. Note that if a store clerk near the settlement device 400 has already logged in (for example, if there is a store clerk assigned to the settlement device 400), there is no need to perform authentication again.

[0308] (B) of Figure 44 shows the confirmation screen for approval by the store clerk. The store clerk visually checks (by checking the products in the basket) whether the corrections entered by the customer are correct (whether they are an operational error or a registration error), and if they are determined to be correct, presses "Yes" on the confirmation screen. When the store clerk selects "Yes" on the confirmation screen, the cancellation of the target product is complete.

[0309] The processing of the settlement device 400 and cloud server 300 in this case will be described below. When "Yes" is selected on the confirmation screen, the settlement device 400 transmits information indicating that to the cloud server 300. When the cloud server 300 receives the information from the settlement device 400, it updates the cumulative information of the registered product information (cumulative number of items, subtotal amount, etc.). Then, the cloud server 300 transmits product registration update screen information including the updated cumulative information to the settlement device 400. When the settlement device 400 receives the product registration update screen information, it displays the screen shown in FIG. 44(C).

[0310] FIG. 44(C) shows the product registration update screen after the correction (cancellation) has been completed and payment is now possible. As shown in FIG. 44(C), the total amount has been reduced compared to FIG. 44(B) due to the cancellation of the product. Also, the product that was the subject of the cancellation (XX bread) is not hidden but is marked with a strikethrough, for example. This makes the canceled product clear. Therefore, customers and store clerks can easily understand that the product has been canceled.

[0311] According to the second embodiment, a customer can cancel or correct a product while registering the product, i.e., without waiting until the time of payment. Therefore, it is not necessary to accept cancellations or corrections at the time of payment, and payment can be expedited. Therefore, congestion at the time of payment can be alleviated.

[0312] (Modification of the second embodiment) Next, a modified version of the second embodiment will be described. In the second embodiment described above, a configuration has been described in which a store clerk approves the correction at the settlement device 400. In the modified version of the second embodiment, instead of or in addition to such a configuration, a configuration will be described in which a store clerk goes to the location of the customer to approve the correction.

[0313] In the modified example, the mobile terminals 500 are assumed to be carried not only by customers but also by sales clerks (one or more sales clerks) in the sales area. The mobile terminals 500 carried by the sales clerk may be owned by the sales clerk or may be loaned from the store. The mobile terminals 500 carried by the sales clerks are managed by the cloud server 300 so as to be identifiable for each sales clerk. Specifically, the cloud server 300 stores, for example, identification information (sales clerk) and an address for each sales clerk's mobile terminal 500 in association with each other.

[0314] Cloud server 300 also manages the sales floors that the sales clerks are in charge of. Specifically, cloud server 300 stores the identification information of the sales clerks in association with the sales floors that the sales clerks are in charge of, and also stores each product in association with the sales floor. This allows cloud server 300 to identify the sales floor manager (the sales clerk in charge of the sales floor) based on the product. Specifically, cloud server 300 can identify the sales floor corresponding to the product based on the product, and further identify the sales clerk corresponding to the identified sales floor.

[0315] In the modified example, it is assumed that a customer cancels a product as shown in (B) of Fig. 42. In this case, the customer's mobile terminal 500 transmits information related to the cancellation (information indicating a cancellation request, the product code to be canceled, and basket identification information) to the cloud server 300. The cloud server 300 updates the basket information based on the information related to the cancellation received from the customer's mobile terminal 500 (see (C) of Fig. 40). Furthermore, the cloud server 300 identifies the sales clerk from the updated products, and transmits to the mobile terminal 500 of the clerk information indicating that the cancellation has been accepted and information on the product to be canceled.

[0316] The store clerk then visits the customer who performed the cancellation operation, visually checks the product etc. to be canceled, and if there are no problems, performs an approval operation using the store clerk's mobile terminal 500. When approval is given, the store clerk's mobile terminal 500 transmits information to that effect to the cloud server 300. When the cloud server 300 receives the information from the store clerk's mobile terminal 500, it updates the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered product information. This allows the cancellation to be completed without waiting until the checkout.

[0317] In the above description, a configuration has been described in which, when mobile terminal 500 accepts a cancellation, information indicating that the cancellation has been accepted is transmitted from cloud server 300 to mobile terminal 500 of the salesperson. Instead of or in addition to this configuration, it is also possible to configure the information to be transmitted to mobile terminal 500 of a salesperson who is close to the customer who performed the cancellation operation. However, to configure in this way, location information is used.

[0318] Specifically, when a customer cancels a product, the customer's mobile terminal 500 transmits information indicating a cancellation request, the product code to be cancelled, basket identification information, and also location information of the mobile terminal 500 to the cloud server 300. The location information is, for example, information for identifying a location within a store. For example, the mobile terminal 500 can obtain the location information by using the detection results of various sensors installed in the store, the signals and radio wave strength of a wireless LAN installed in the store, the detection results of various sensors built into the mobile terminal 500, and the like.

[0319] The cloud server 300 also manages the location information of the store clerk. Specifically, the mobile terminal 500 of the store clerk successively transmits the location information of its own terminal to the cloud server 300. When the cloud server 300 receives the location information of the store clerk, it updates the location information by associating it with the identification information of the store clerk. When the cloud server 300 receives information about the cancellation including the location information of the customer's mobile terminal 500 from the customer's mobile terminal 500, it transmits information that the cancellation has been accepted to the mobile terminal 500 of the store clerk near the customer based on the location information and the stored location information of the store clerk. This allows the store clerk near the customer who performed the cancellation operation to be sent to the customer quickly. Even in this way, the cancellation can be completed without waiting until the time of payment.

[0320] In the above description, the store clerk approves the cancellation using the store clerk's mobile terminal 500, but the cancellation can also be approved using the customer's mobile terminal 500. More specifically, when the cloud server 300 receives information regarding the cancellation from the customer's mobile terminal 500, it issues a password (information that only the store clerk can know) for accepting the approval of the cancellation, and transmits the issued password to the store clerk's mobile terminal 500.

[0321] The store clerk visits the customer who performed the cancellation operation, visually checks the product to be cancelled, and if there are no problems, enters the password on a specified screen on the customer's mobile terminal 500. The entered password is sent from the customer's mobile terminal 500 to the cloud server 300 and is used to determine whether it matches the password issued by the cloud server 300. If the cloud server 300 determines that they match, it approves the cancellation. Then, the cloud server 300 updates the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered product information, and transmits product registration update screen information including the updated cumulative information to the customer's mobile terminal 500. This also makes it possible to complete the cancellation without waiting until the time of payment.

[0322] According to the above-described modified example, since it is not necessary to approve the cancellation at the time of payment, payment can be made more quickly, and therefore congestion at the time of payment can be further alleviated.

[0323] The following supplementary notes are disclosed below.

[0324] (Appendix 1) A product sales data processing device operable by a customer, comprising: a change accepting means for accepting from a customer changes to product information indicating products registered in a transaction; an approval input means for inputting the result of approval by a store clerk regarding the change to the product information accepted by the change accepting means; and a product information change means for changing the product information in response to the approval result being input by the approval input means.

[0325] A supplementary note regarding Supplementary Note 1: A transaction is, for example, a transaction from when product registration is started by a customer's operation to when payment is completed. Product information is, for example, registration information. The timing at which the change accepting means accepts a change to the product information from the customer is any timing from when product registration is started to when payment is completed, and may be, for example, before the subtotal key is pressed while the product is being registered, or after the subtotal key is pressed when product registration is completed.

[0326] When the change acceptance means accepts the change, the product sales data processing device (POS terminal 20) calls a store clerk. The store clerk is called by the POS terminal 20 where the store clerk is located, a mobile terminal carried by the store clerk, or the management device.

[0327] The approval input means inputs the approval result from the called store clerk. The mode of input by the approval input means may be, for example, direct acceptance of the operation of the store clerk, or reception from another terminal (another POS terminal 20, a mobile terminal carried by the store clerk, or a management device). When the approval result is input, the product information change means changes the product information.

[0328] According to Supplementary Note 1, since some of the operations related to changing product information are performed by the customer, and the store clerk only needs to perform the operation of approving, the operations of the store clerk related to changing product information can be simplified. In addition, the waiting time of customers related to changes can be shortened. Therefore, changes to registered products can be made efficiently. In addition, since the customer can request a change without speaking, for example, the mental burden related to changes can be reduced for customers who are concerned about further congestion due to the change when it is crowded, or customers who feel embarrassed about making a change. As a result, according to Supplementary Note 1, changes to product information can be made appropriately, and the convenience of the product sales data processing device can be improved.

[0329] (Appendix 2) The product sales data processing device described in Appendix 1 is further provided with an operation display means for displaying the product information in a different display area for each product, and the change accepting means accepts changes to the product information indicated by the accepted display area by accepting from a customer any of the display areas displayed by the operation display means.

[0330] Specifically, note 2 states that, for example, a customer can change product information by pressing and holding a display area showing a product that the customer wishes to change (see FIG. 25(A)). Note 2 also includes the content that, of the display areas showing products, the items showing the product name, quantity, and price, that are shown in the display area that is pressed and held can be changed (see FIGS. 34 to 36). This allows the customer to specify the product to be changed by simply pressing the item to be changed that is displayed on the display screen. Also, the customer can specify the product to be changed with, for example, a single operation. This allows product information to be changed efficiently.

[0331] However, the change acceptance means may display a button indicating that a change is to be made, and when the button is pressed, the change acceptance means may accept the product or item that the customer wishes to change in a selectable manner. In other words, the change acceptance means may accept changes to the product information through multiple operations.

[0332] (Appendix 3) 3. A product sales data processing device as described in appendix 1 or 2, further comprising a store clerk operation unit that can be operated by a store clerk and a customer operation unit that can be operated by a customer, wherein the approval input means inputs the approval result in response to an operation on the store clerk operation unit.

[0333] Supplementary note 3 is, for example, that in a POS terminal 20 equipped with a clerk display unit 210 and a customer display unit 205, approval from a clerk is received by operating the clerk display unit 210. Also, for example, it is possible to receive changes from a customer by operating the customer display unit 205. This allows the clerk to give approval on the spot when registering a product on the clerk display unit 210 or when a change to product information is received from a customer after the product has been registered. This reduces the burden on the clerk when giving approval. This allows changes to product information to be made efficiently, improving the convenience of the product sales data processing device.

[0334] (Appendix 4) A product sales data processing device as described in any one of Appendices 1 to 3, comprising a customer-side operation means that can be operated by a customer, an identification information input means for inputting identification information that identifies a store clerk, and a store clerk identification means for identifying a store clerk using the identification information input by the identification information input means, wherein the approval input means inputs the approval result by accepting an operation to the customer-side operation means when a store clerk is identified by the store clerk identification means.

[0335] The customer-side operation means in Supplementary Note 4 is a display unit that accepts changes to product information from a customer, such as the customer-side display unit 205 in the POS terminal 20 or a display unit of a settlement device that does not have a product registration function. Specifically, Supplementary Note 4 is that when a change is accepted from a customer, a store clerk goes to the terminal that accepted the change, and if the store clerk's authentication is successful, approval is accepted from the store clerk. This allows the store clerk's approval to be accepted on the screen that accepted the change to the product information from the customer, so that the change operation and the approval operation can be performed consecutively. Therefore, the customer and the store clerk can easily understand the content of the change and that the change has been made, and misunderstandings and erroneous operations related to the change can be prevented. This allows changes to be made efficiently.

[0336] (Appendix 5) A product sales data processing device as described in Appendix 4, further comprising a mode setting means for setting one of a plurality of modes, and wherein the approval input means, when a predetermined mode is set by the mode setting means, inputs the approval result by accepting an operation on the customer side operation means.

[0337] Specifically, Supplementary Note 5 is that when the full self-service mode is set, approval from a store clerk is received by operating the customer-side display unit 205. As a result, in the full self-service mode, the customer-side display unit 205 can receive product information registration and changes to the product information from the customer, and can also receive approval from the store clerk. Therefore, in the full self-service mode, the customer-side display unit 205 can perform change operations and approval operations consecutively. This allows efficient changes to product information.

[0338] (Appendix 6) The product sales data processing device described in any one of Appendices 1 to 5, characterized in that the change accepting means accepts a change to a predetermined quantity of the product indicated by the product information when the product information is registered in a predetermined registration manner.

[0339] The predetermined registration mode in Supplementary Note 6 is, for example, a registration mode by reading a barcode. Also, the predetermined quantity is, for example, a quantity excluding "0". Specifically, Supplementary Note 6 states that when product information is registered by reading a barcode, the quantity of the product is accepted to be changed to a quantity excluding "0". In other words, when product information is registered by reading a barcode, a change to the quantity of the product to "0" is not accepted.

[0340] This is because, for products with barcodes, it is clear that the product actually exists because the barcode was read, so changing the quantity to "0" is not anticipated. For this reason, changing the quantity to "0" is not accepted because it is highly likely to be a mistake. According to Appendix 6, it is possible to prevent mistakes in changing the quantity, and product information can be changed efficiently.

[0341] (Appendix 7) A product sales data processing system comprising a registration device which registers product information indicating a product, and a settlement device which performs settlement, wherein the settlement device accepts from a customer changes to the product information registered by the registration device in a single transaction, and the registration device inputs an approval result from a store clerk regarding the change to the product information accepted by the settlement device, and changes the product information by inputting the approval result.

[0342] The registration device in Supplementary Note 7 is, for example, a POS terminal 20 in normal mode located on the upstream side, which registers product information through the operation of a store clerk. The registration device only needs to have a function for registering product information, in other words, it does not need to have a function for registering product information through the operation of a customer or a function for settling the bill through the operation of a customer. The settlement device in Supplementary Note 7 is, for example, a POS terminal 20 in semi-self-service mode located on the downstream side, which setstling the bill through the operation of a customer. The settlement device only needs to have a function for settling the bill through the operation of a customer, in other words, it does not need to have a function for registering product information. A plurality of settlement devices may be installed corresponding to one registration device.

[0343] When the settlement device accepts a change to the product information from a customer, it requests the registration device to approve the change. Note that the settlement device may only request approval for the change to the registration device and not transmit the details of the change. When an approval request is received from the settlement device, the registration device accepts approval for the change to the product information from a store clerk. For example, the registration device may receive only the approval request from the settlement device and display only an approval button to accept approval. In this case, the store clerk can press the approval button by visually checking the changes made by the customer on the settlement device, etc.

[0344] According to supplementary note 7, since the customer performs some of the operations related to changing the product information at the settlement device, and the store clerk only needs to perform the operation of approving at the registration device, the operations of the store clerk related to changing the product information can be simplified. In addition, the waiting time of the customer performing the operation of changing the product information at the settlement device can be shortened. Therefore, the registered product can be changed efficiently. As a result, according to supplementary note 7, the product information can be changed preferably, and the convenience of the product sales data processing system can be improved.

[0345] (Appendix 8) The product sales data processing system described in Appendix 7, characterized in that the settlement device transmits change information indicating changes to the product information accepted from the customer to the registration device, and the registration device inputs the approval result by receiving the change information from the settlement device.

[0346] Specifically, Supplementary Note 8 states that when the settlement device accepts a change to product information from a customer, it transmits change information (including the content of the change and an approval request) to the registration device, and the registration device receives the change information from the settlement device, thereby accepting approval from the store clerk. This allows the store clerk to understand the content of the change at the settlement device. Therefore, when the store clerk is registering a product in the registration device, or when a change to product information is accepted from a customer after the product has been registered, the store clerk can give approval on the spot. This reduces the burden on the store clerk when giving approval. This allows changes to product information to be made efficiently, improving the convenience of the product sales data processing system.

[0347] (Appendix 9) The product sales data processing system described in Appendix 8, characterized in that the registration device and the settlement device are both set to one of a plurality of modes, and when the settlement device sets a predetermined mode, it sends the change information to the registration device, and when the registration device sets a mode different from the predetermined mode, it inputs the approval result by receiving the change information from the settlement device.

[0348] Specifically, Supplementary Note 9 states that when the settlement device (the downstream POS terminal 20) sets the full self-service mode, it transmits change information to the registration device, and when the registration device (the upstream POS terminal 20) sets the normal mode, it receives change information from the settlement device. Product information can be changed according to the mode set in each POS terminal 20 in the POS system 1. Therefore, product information can be changed efficiently in the full self-service mode.

[0349] (Appendix 10) A program that causes a computer to function as a product sales data processing device that can be operated by a customer, the program functioning as: a change accepting means that accepts from a customer changes to product information indicating products registered in a transaction; an approval input means that inputs an approval result by a store clerk regarding the change to the product information accepted by the change accepting means; and a product information change means that changes the product information in response to the approval result being input by the approval input means.

[0350] The program for implementing the POS system 1 and the POS terminal 20 described above may be recorded in a computer-readable recording medium, and the program may be read into the computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system. The term "computer-readable recording medium" also includes devices that hold the program for a certain period of time, such as volatile memory (RAM) in a computer system that becomes a server or client when the program is transmitted via a network such as the Internet or a communication line such as a telephone line. The program may be transmitted from a computer system that stores the program in a storage device to another computer system via a transmission medium or by a transmission wave in the transmission medium. The "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be for implementing part of the above-mentioned functions. Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0351] 1. POS system 10…Store Controller 20…POS terminal 201…CPU 202...ROM 203...RAM 204...Hard disk 205…Customer side display section 206…Customer side scanner section 208…Card payment department 209…Change machine 210...Staff side display section 211...Key operation section 212…Clerk side scanner 213…Printing Department 214...Audio output unit 215…Communications Department

Claims

1. A product sales data processing system including a terminal device carried by a customer for registering products, and a payment device for settling the products registered by the terminal device, the terminal device includes a change receiving means for receiving, from a customer, a change to product information indicating a product registered in one transaction by receiving an operation from the customer; The settlement device includes: a payment means for performing payment for the registered product based on an operation by a customer when the change acceptance means does not accept the change to the product information; an approval input means for inputting an approval result by a store clerk when the change acceptance means accepts the change to the product information; a product information changing means for changing the product information in response to the approval result being input by the approval input means; Equipped with The settlement means performs settlement for the product indicated by the product information changed by the product information change means based on an operation by the customer. A product sales data processing system comprising:

2. A merchandise sales data processing method for a merchandise sales data processing system including a terminal device carried by a customer for registering merchandise, and a payment device for settling payments for merchandise registered by the terminal device, comprising: the terminal device executes a process including a change acceptance step of accepting, from the customer, a change to product information indicating a product registered in one transaction by accepting an operation from the customer; The settlement device includes: a first payment step of performing payment for the registered product based on an operation of a customer when the change of the product information is not accepted in the change acceptance step; an approval input step of inputting an approval result by a store clerk when the change to the product information is accepted in the change acceptance step; a product information changing step of changing the product information by inputting the approval result in the approval input step; a second payment step of performing payment for the product indicated by the product information changed in the product information change step based on an operation of the customer; A merchandise sales data processing method comprising the steps of:

3. A payment device of a product sales data processing system including a terminal device which is held by a customer to register products and which receives operations from the customer to accept changes to product information indicating products registered in one transaction, and a payment device which performs payment for the products registered by the terminal device, a payment means for performing payment for the registered products based on an operation by a customer when the change in the product information is not accepted by the terminal device; an approval input means for inputting an approval result by a store clerk when the change to the product information is accepted by the terminal device; a product information changing means for changing the product information in response to the approval result being input by the approval input means; Equipped with The settlement means performs settlement for the product indicated by the product information changed by the product information change means based on an operation by the customer. A settlement device characterized by:

4. A program for causing a computer to function as a settlement device of a product sales data processing system including a terminal device which is held by a customer to register products and which accepts, from the customer, operations to change product information indicating products registered in one transaction, and a settlement device which settles the payment for the products registered by the terminal device, The computer, a payment means for performing payment for the registered products based on an operation by a customer when the change in the product information is not accepted by the terminal device; an approval input means for inputting an approval result by a store clerk when the change in the product information is accepted by the terminal device; a product information changing means for changing the product information in response to the approval result being input by the approval input means; Function as a The settlement means performs settlement for the product indicated by the product information changed by the product information change means based on an operation by the customer. A program characterized by:

Images