JP2020091803A - Commodity sales data processing device, commodity sales data processing system and program - Google Patents

Abstract

To efficiently correct data on a registered commodity.SOLUTION: A commodity sales data processing device that can be operated by a customer includes: change acceptance means for accepting a change of commodity information indicating a registered commodity in one transaction; approval input means for accepting input of an approval result by a clerk for the change of the commodity information accepted by the change acceptance means; and commodity information change means for changing the commodity information by input of the approval result by the approval input means.SELECTED DRAWING: Figure 26

Description

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

In stores such as convenience stores and supermarkets, a merchandise sales data processing device (for example, POS register) for registering merchandise is installed. 2. Description of the Related Art In recent years, product sales data processing devices in which customers themselves register products and make payments have become widespread. In such a product sales data processing device, when a customer mistakenly registers a product, correction (change) is performed.

A related technology is an order registration processing device used in restaurants, etc. When a customer inputs an instruction to check vacancy, the server inquires about the room usage status and the room usage status received from the server. There has been proposed an order registration processing device for displaying (see Patent Document 1, for example).

Japanese Unexamined Patent Publication No. 2016-045782

However, when correcting the registered merchandise, for example, from the viewpoint of fraud prevention, the clerk performs a correction operation. Therefore, if there is a correction, the customer must call the clerk and wait for the clerk to complete the correction operation, which may waste time. Further, for example, a correction operation may take time for a store clerk, which may hinder other operations, resulting in a decrease in operation efficiency. Therefore, the conventional technique has a problem that the registered product may not be efficiently corrected.

The present invention has been made in view of such circumstances, and an object thereof is to provide a technique capable of efficiently correcting a registered product.

In order to solve the above-described problems, a product sales data processing device according to an aspect of the present invention is a product sales data processing device that can be operated by a customer, and changes product information indicating a product registered in one transaction. Change acceptance means for accepting from a customer, approval input means for inputting an approval result by a clerk about the change of the product information accepted by the change acceptance means, and the approval result input by the approval input means, It is a product sales data processing device characterized by a product information changing unit for changing product information.

According to the above configuration, the registered product can be corrected (changed) efficiently.

The product sales data processing device further comprises operation display means for displaying the product information in different display areas for each product, and the change accepting means is any one of the display areas displayed by the operation display means. The change of the product information indicated by the received display area may be received by receiving the display area of from the customer.

According to the above configuration, the registered merchandise can be efficiently corrected.

The product sales data processing device further comprises a clerk-side operation unit that can be operated by a clerk, and a customer-side operation unit that can be operated by a customer, wherein the approval input means is responsive to an operation on the clerk-side operation unit. Then, the approval result may be input.

According to the above configuration, the registered merchandise can be efficiently corrected.

In the above-mentioned product sales data processing device, a customer-side operation means that a customer can operate, identification information input means for inputting identification information for identifying a clerk, and a clerk using the identification information input by the identification information input means. A salesclerk specifying means for specifying, and the approval input means, even if the approval result is input by accepting an operation to the customer side operation means when a salesclerk is specified by the salesclerk specifying means. Good.

According to the above configuration, the registered merchandise can be efficiently corrected.

In the above-mentioned product sales data processing device, a mode setting means for setting any one of a plurality of modes is provided, and the approval input means, when the predetermined mode is set by the mode setting means, the customer The approval result may be input by accepting an operation on the side operation means.

According to the above configuration, the registered merchandise can be efficiently corrected.

In the product sales data processing device, the change accepting unit may accept a change in the quantity of the product indicated by the product information to a predetermined quantity, when the product information is registered in a predetermined registration mode.

According to the above configuration, the registered merchandise can be efficiently corrected.

In order to solve the above-described problems, a product sales data processing system according to another aspect of the present invention includes a registration device that registers product information indicating a product and a payment device that performs payment. The settlement device receives a change in the product information registered by the registration device from a customer in one transaction, and the registration device is a store clerk about the change in the product information received by the settlement device. The product sales data processing system is characterized by inputting an approval result and changing the product information by inputting the approval result.

According to the above configuration, the registered merchandise can be efficiently corrected.

In the product sales data processing device system, the settlement device transmits change information indicating a change in the product information received from a customer to the registration device, and the registration device receives the change information from the settlement device. By doing so, the approval result may be input.

According to the above configuration, the registered merchandise can be efficiently corrected.

In the product sales data processing device system, each of the registration device and the settlement device sets one of a plurality of modes, and the settlement device sets the change information when a predetermined mode is set. May be transmitted to the registration device, and the registration device may input the approval result by receiving the change information from the settlement device when a mode different from the predetermined mode is set.

According to the above configuration, the registered merchandise can be efficiently corrected.

In order to solve the problems described above, a program according to another aspect of the present invention is a program that causes a computer to function as a product sales data processing device that can be operated by a customer, and indicates a product registered in one transaction. Change accepting means for accepting a change in product information from a customer, approval input means for inputting an approval result by a clerk regarding the change in the product information accepted by the change accepting means, and the approval result being input by the approval input means According to the above, the program is caused to function as product information changing means for changing the product information.

As described above, according to the present invention, it is possible to efficiently correct a registered product.

It is a network block diagram of the POS system concerning Embodiment 1 of this invention. It is a figure which shows the example of installation of a POS terminal. It is a figure which shows the external example of a POS terminal. It is a figure which shows the structural example of a POS terminal. It is a figure explaining the outline of the operation mode of a POS terminal. It is a figure explaining switching of the operation mode of a POS terminal. It is a schematic diagram explaining the outline of operation|movement of a normal mode. It is a flow chart explaining an outline of operation of a normal mode. It is a schematic diagram explaining the outline of operation|movement of a normal mode. 7 is a flowchart illustrating an outline of operation in a normal mode. It is a schematic diagram explaining the outline of the operation of the full self mode. It is a flow chart explaining an outline of operation in full self mode. It is a schematic diagram explaining the outline of the operation of the double scan mode. 7 is a flowchart illustrating an outline of an operation in double scan mode. It is a display example in a POS terminal in full self mode. It is a display example in a POS terminal in full self mode. It is a display example on the POS terminal 20 in the normal mode. It is a display example on the POS terminal 20 in the normal mode. It is a display example on the POS terminal 20 in the normal mode. It is a display example on the POS terminal 20 in the normal mode. It is a display example on the POS terminal 20 in the normal mode. It is a display example on the POS terminal 20 in the normal mode. It is explanatory drawing which shows the outline of the advertisement display in full self mode. It is an explanatory view showing an example of an advertising information table. It is explanatory drawing which shows an example of the transition of the screen at the time of correcting the registered goods in full self mode. It is explanatory drawing which shows an example of the transition of the screen at the time of correcting the registered goods in full self mode. It is explanatory drawing which shows an example of the transition of the screen at the time of correcting the registered goods in full self mode. It is explanatory drawing which shows the other example of a screen at the time of correcting goods in a full self mode. 6 is a flowchart showing an example of product registration processing in the full self mode performed by the POS terminal 20. 7 is a flowchart showing an example of a product correction process in the full self mode performed by the POS terminal 20. It is explanatory drawing which shows an example of the transition of the screen of the customer side when correcting a product in a semi-self mode. It is explanatory drawing which shows an example of the transition of the screen of the customer side when correcting a product in a semi-self mode. It is explanatory drawing which shows an example of the transition of the screen of the salesclerk side display part 210 of the POS terminal 20 of the upstream side when correcting a product. It is explanatory drawing which shows the other example of a screen at the time of correcting a product in a semi-self mode. It is explanatory drawing which shows the other example of a screen at the time of correcting a product in a semi-self mode. It is explanatory drawing which shows the other example of a screen at the time of correcting a product in a semi-self mode. It is a flowchart which shows an example of the settlement process in the semi-self mode which the POS terminal 20 (settlement device) on the downstream side performs. It is a flowchart which shows an example of a process when the approval request which the POS terminal 20 (registration device) on the upstream side receives is received. It is a network block diagram which shows the shopping system which concerns on Embodiment 2 of this invention. 6 is an explanatory diagram showing an example of various information managed by the cloud server 300. FIG. It is a sequence diagram which shows the flow of a process of the shopping system which concerns on Embodiment 2. FIG. 10 is an explanatory diagram showing an example of screen transition when accepting cancellation of a product in the second embodiment. FIG. 9 is an explanatory diagram showing an example of screen transition when a change in the quantity of products is received in the second embodiment. It is explanatory drawing which shows an example of the settlement screen of Embodiment 2.

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

The POS system 1 can be installed in various stores (convenience store, supermarket, etc.).

FIG. 2 is a diagram showing an installation example of the POS terminal 20. FIG. 2A is a perspective view of the POS terminal 20 and the like as seen from the customer side. FIG. 2B is a perspective view of the POS terminal 20 and the like as seen from the clerk side. As shown in FIG. 2A, a counter is placed on the right side of the POS terminal 20 as seen from the customer side.

FIG. 3 is a diagram showing an example of the appearance of the POS terminal 20. FIG. 3A is a perspective view of the POS terminal 20 viewed from the customer side. FIG. 3B is a perspective view of the POS terminal 20 viewed from the clerk side. FIG. 4 is a diagram showing a configuration example of the POS terminal 20. 3 and 4, the same reference numerals are given to the same portions.

Hereinafter, a configuration example of the POS terminal 20 shown in FIG. 4 will be described with reference to FIG. The POS terminal 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer side display unit 205, a customer side scanner unit 206, a card settlement unit 208, a change dispenser 209, and a clerk side display unit 210. A key operation unit 211, a clerk-side scanner unit 212, a printing unit 213, a voice output unit 214, and a communication unit 215 are provided. These can communicate with each other via a bus. The reference numerals 211a, 211b, and 211c will be described later.

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

The RAM 203 is a read/write memory and stores various information. For example, the RAM 203 stores information acquired from outside (for example, a product master acquired from the store controller 10), information generated in the process (for example, registration information (registered data) generated in a registration process for registering a product, purchase). The payment information generated in the payment processing for payment (payment) of the product) is stored.

The hard disk 204 stores various information. The hard disk 204 may store, for example, a program executed by the CPU 201 instead of the ROM 202. Further, instead of the RAM 203, information acquired from the outside or information generated in the process may be stored.

The customer-side display unit 205 is a touch display for a customer, displays various information to the customer, and receives various inputs from the customer.
The customer-side scanner unit 206 is a scanner unit for a customer, and optically reads various kinds of information.
For example, the customer-side scanner unit 206 optically detects a bar code (product code, etc.) attached to a product or a code (bar code, two-dimensional code, etc.) printed on an accounting ticket (registered trademark). read. In addition to the above, the customer-side scanner unit 206 uses a code (bar code, 2 or the like) printed on a gift certificate (gift certificate, coupon ticket, special treatment ticket) or various cards (for example, a membership card, a point card, etc.). Dimensional code, etc.) may be read. The customer-side scanner unit 206 is used when the customer registers the product, but the customer may register the product by another method. 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.

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 settlement 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 the payment (payment) of purchased products. In addition, the card recognition unit uses the information recognized for the payment (settlement) of the purchased product this time (that is, in the case of credit card payment by credit card, prepaid card payment by prepaid card, the points held by the point card are In addition to using (consuming), etc., when not using the information recognized for the settlement (settlement) of the purchased product this time (for example, when giving a privilege by presenting a credit card, when giving points to a point card) Etc.), various cards may be recognized. The card payment unit 208 of the present 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 of the present embodiment corresponds to a contact type card (IC card, magnetic card), but instead of or in addition to the contact type card, a non-contact type card (IC card). May correspond to.

The change machine 209 (cash payment unit) is a payment mechanism using cash, has an inlet for bills and coins and an outlet for bills and coins, calculates the amount of money inserted into the inlet, and calculates the amount of money paid and the amount of purchase. The change amount which is the difference is calculated, and the change amount is discharged from the discharge port. The change machine 209 is directed to the customer side and is operated by the customer. It should be noted that when a bill or coin is inserted into the insertion slot, it is detected by a sensor (detection of the insertion, detection of the number of denominations, etc.). The card settlement unit 208 and the change machine 209 form a settlement unit.

The clerk-side display unit 210 is a touch display for the clerk, displays various information to the clerk, and receives various inputs from the clerk.
The key operation unit 211 includes various keys (hardware keys, buttons) and receives various inputs from a clerk.
The clerk-side scanner unit 212 is a scanner unit for a clerk and optically reads various kinds of information. For example, the clerk-side scanner unit 212 optically reads a bar code attached to a product or a clerk code attached to a clerk's name tag. In addition to the above, the clerk-side scanner unit 212 may read the code printed on the transaction ticket, the gift certificate, or the code printed on various cards.

The clerk-side scanner unit 212 is used when the clerk registers the product, but the clerk may register the product by other methods. For example, when a key corresponding to a product (for example, a key corresponding to a sports newspaper) is arranged on the key operation unit 211, the clerk operates (presses) the key to register the product. Good. Further, when the store clerk side display unit 210 displays a preset key corresponding to a product, the store clerk may operate the preset key to register the product.

The printing unit 213 prints and issues various media (receipts, accounting tickets, etc.). The printing unit 213 can freely rotate the direction (direction of the medium issuing port) from the clerk side to the customer side and from the customer side to the clerk side. The orientation of the printing unit 213 may be manually changed, or may be automatically changed (mechanically controlled or the like) based on switching of operation modes (details will be described later), for example. The correctness of the orientation of the printing unit 213 may be detected by a sensor or the like. Note that switching the operation mode is also referred to as switching the operation mode.

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

(Outline of each operation mode)
Next, the operation mode of the POS terminal 20 will be described. The POS terminal 20 has a plurality of operation modes. This operation mode is an operation mode during normal work (operation mode related to registration processing and settlement processing), such as a totaling mode for totaling and inquiring about sales, amount of money, etc., and sales staff and maintenance personnel performing setting work and maintenance work. It does not include the maintenance mode when performing training or the training mode when new employees train.

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

In FIG. 5(A), the columns indicate the respective operation modes, and the rows indicate the respective functions (“product registration (clerk side)”, “product registration (customer side)”, “money insertion”,... The reading of the accounting ticket") is shown. The same applies to FIG. 5B (however, the illustration of each function is omitted in FIG. 5B).

In FIG. 5A (the same applies to FIG. 5B), “◯” in the column specified from the column and the row indicates that the function of the row is valid in the operation mode of the column. .. For example, “◯” in the column specified from the column “normal mode (standard mode)” and the row “product registration (store employee side)” indicates that the product registration (store employee side) is valid in the normal mode (standard mode). It shows that. Further, "-" in the column specified by the column and the row indicates that the function of the row is invalid in the operation mode of the column. For example, “-” in the column specified by the column “normal mode” and the row “product registration (customer side)” indicates that product registration (customer side) is invalid in the normal mode.

(Explanation of each function)
The outline of each function shown in FIG. 5A will be described below.

(Product registration (clerk side))
"Product registration (clerk side)" is a function of registering a purchased product on the clerk side (clerk side scanner unit 212, clerk side display unit 210, key operation unit 211). That is, this is a function of executing the registration process of the purchased product by the operation of the clerk (scan by the clerk side scanner unit 212, touch on the clerk side display unit 210, operation of the key operation unit 211).

(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 of executing the registration process of the purchased product by the customer's operation (scan by the customer side scanner unit 206, touch on the customer side display unit 205).

(Injecting money)
The “insertion of money” is a function of accepting insertion of money (banknotes, coins). That is, this is a function of accepting a cash settlement operation (inserting money into the change machine 209).

(Sending registration information to other terminals)
“Send registration information to other terminal” is to send the registration information generated in the registration process to another terminal (another terminal capable of executing the settlement process, for example, another POS terminal 20) (directly to the other terminal). This is a function of transmitting or indirectly transmitting to another terminal via the store controller 10 or the monitoring terminal, and so on.

(Issue of accounting ticket)
"Issue of accounting ticket" is a function of encoding registration information and the like generated in the registration process and issuing a printed medium (accounting ticket).

(Receiving registration information from other terminals)
“Reception of registration information from another terminal” means reception of registration information generated in the registration processing of another terminal (directly received from another terminal or indirectly via the store controller 10 or a monitoring terminal). It is a function to receive from other terminals. The terminal that has received the registration information from the other terminal executes the settlement process based on the registration information.

(Reading the accounting ticket)
The “reading the accounting ticket” is a function of reading the accounting ticket (specifically, the code printed on the accounting ticket or the coded information). The terminal that has read the transaction ticket issued by the other terminal executes the settlement process based on the registration information acquired by reading the transaction ticket.

(Explanation of each operation mode)
Subsequently, an outline of each operation mode shown in FIGS. 5A and 5B will be described.

(Normal mode (Standard mode))
As shown in FIG. 5A, the normal mode (standard mode) is an operation mode in which the product registration (clerk side) is valid “◯” and the product registration (customer side) is invalid “−”. That is, the normal mode (standard mode) is an operation mode in which the registration process is not performed on the customer side but the registration process is performed on the salesclerk side.

Also, in the normal mode (standard mode), as shown in FIG. 5(A), the insertion of money, the transmission of registration information to other terminals, and the issuance of accounting tickets are all valid "○". It is an operation mode. That is, in the normal mode (standard mode), the settlement process after the registration process on the side of the store clerk can be executed by the own terminal or by another terminal. Specifically, in the normal mode (standard mode), the settlement process is executed by the terminal by accepting the input of money into the change machine 209, and the registration information is transmitted to another terminal (or the accounting ticket is displayed). Causes another terminal to execute the payment process (by issuing).

As shown in FIG. 5A, the normal mode (standard mode) is an operation mode in which the registration information is received from other terminals and the bill is read, which are both valid. That is, in the normal mode (standard mode), the settlement process can be executed based on the registration information generated in another terminal. The settlement process after receiving the registration information (or after reading the bill) may be executed in the semi-self mode of FIG. 5(A). That is, when the registration information is received (or the accounting ticket is read) in the normal mode (standard mode), the normal mode (standard mode) is automatically changed to the semi-self mode (accounting-only mode) (clerk). May be requested), and the settlement process may be executed in the semi-self mode (accounting-only mode). In addition, when the procedure shifts to the semi-self mode (accounting-only mode) and the settlement process is executed, the semi-self mode (accounting-only mode) automatically changes to the normal mode (standard mode) (you may ask for permission from the clerk) It may be shifted (returned) or left in the semi-self mode (accounting-only mode).

In the normal mode (standard mode), at least one of the reception of registration information from another terminal and the reading of the accounting ticket may be invalidated "-".

(Full self mode)
As shown in FIG. 5A, the full self mode is an operation mode in which the merchandise registration (customer side) is valid “◯”. That is, the full self mode is an operation mode premised on the registration process on the customer side. However, in the full self mode, product registration (on the side of a clerk) is also valid as "○". In other words, the full self mode is an operation mode in which the registration process on the customer side is premised but the registration process on the salesclerk side is also allowed. The state in which registration processing is being performed on both the customer side and the clerk side may be referred to as the double scan mode.

In the example shown in FIG. 5A, the product registration (clerk side) is valid “◯” in the full self mode, but the product registration (clerk side) is invalid “−” in the full self mode. Good.

In the full self mode, as shown in FIG. 5A, an operation mode in which the insertion of money is valid “◯” and the transmission of registration information to another terminal and the issue of the transaction ticket are invalid “−”. Is. That is, the full self mode is an operation mode premised on the settlement process in the terminal.

In addition, as shown in FIG. 5A, the full self mode is valid for both reception of registration information from another terminal and reading of the accounting ticket, as in the normal mode (standard mode). This is the operation mode. That is, similar to the normal mode (standard mode), in the full self mode, the settlement process can be executed based on the registration information generated in another terminal. The settlement process after receiving the registration information (or after reading the bill) may be executed in the semi-self mode of FIG. 5(A). That is, when the registration information is received (or the accounting ticket is read) in the full self mode, the full self mode automatically shifts to the semi self mode (accounting only mode), and the semi self mode (accounting The settlement process may be executed as a dedicated mode). Further, when the settlement process is executed by shifting to the semi-self mode (accounting-only mode), the semi-self mode (accounting-only mode) may be automatically shifted (returned) to the full self mode, or the semi-self mode ( Accounting only mode) may be left as it is.

(Semi-self mode (accounting only mode))
In the semi-self mode (accounting-only mode), as shown in FIG. 5(A), receiving registration information from another terminal, reading an accounting ticket, and inserting money is valid as "○", and product registration (clerk side) This is an operation mode in which the product registration (customer side) is invalidated "-". That is, the semi-self mode (accounting-only mode) is an operation mode in which the self-terminal does not execute the registration process but exclusively executes the settlement process based on the registration information generated in another terminal. Note that, in the semi-self mode (accounting-only mode), since the operation mode does not execute the registration process (since the registration information is not generated), as shown in FIG. The issuance of accounting tickets is also invalid "-".

(Normal mode (restricted mode))
In the normal mode (restricted mode), as shown in FIG. 5(B), the registration information is transmitted to another terminal and issuance of the transaction ticket, which is set to “◯” in the normal mode (standard mode) of FIG. 5(A). And are invalid "-". That is, the normal mode (restricted mode) is an operation mode in which the function of allowing another terminal to execute the settlement process, which is permitted in the normal mode (standard mode), is restricted.

(Semi-self mode (register only mode))
In the semi-self mode (registration-only mode), as shown in FIG. 5B, product registration (clerk side), transmission of registration information to another terminal, issuance of a transaction ticket are valid “○”, and product registration ( This is an operation mode in which the customer side), the insertion of money, the reception of registration information from other terminals, and the reading of the accounting ticket are invalid “−”. In other words, the semi-self mode (registration-only mode) is an operation mode in which the registration process is executed exclusively in the own terminal and the settlement process is executed in another terminal. Since the semi-self mode (registration-only mode) is premised on a registration operation by a store clerk, the product registration (customer side) is invalidated "-".

(About enable/disable of function)
In the above description, the POS terminal 20 has various functions (product registration (clerk side), product registration (customer side) in FIG. .., the reading of the accounting ticket), the difference between valid “◯” and invalid “−” is explained. In other words, in the above, the POS terminal 20 originally performs all the functions (commodity registration (clerk side), product registration (customer side), insertion of money,..., Reading of accounting ticket in FIG. 5A). It has been described that some of the functions are disabled according to the operation mode (for example, as shown in FIG. 5A, the POS terminal 20 is a product in the normal mode (standard mode). Registration (customer side) is invalid "-", and transmission of registration information to another terminal and issuance of a transaction ticket are invalid "-" when in full self mode).

However, the POS terminal 20 may have different functions that can be executed depending on the operation mode, and the POS terminal 20 necessarily has all the functions originally, and some of the functions are invalid according to the operation mode. It is not necessary to adopt such a configuration. For example, the POS terminal 20 does not have all the functions (a program for realizing the functions) from the beginning, but is required in the operation mode according to the operation mode (for example, when switching the operation mode). A program for realizing a function (a function corresponding to the function marked as “◯” in FIG. 5) is acquired from an external device (for example, the store controller 10, a monitoring terminal, a server (cloud, etc.) outside the store) and executed. If there is a program for realizing a function that is not necessary for the operation mode (a function corresponding to the function that is invalidated “−” in FIG. 5) while maintaining the possible state (holding the program), execute the program. It may be in an unexecutable state (for example, it may be erased). Note that a program for realizing a necessary function may be acquired and made executable after a program for realizing an unnecessary function is set in an unexecutable state. Further, for example, when switching the operation mode, the POS terminal 20 temporarily implements all the programs in an unexecutable state regardless of the operation mode of the transfer destination, and then realizes a function required in the operation mode. The program may be acquired from the outside and made executable. That is, the configuration of the POS terminal 20 may be such that some of the various functions originally provided are disabled "-" according to the operation mode, or necessary depending on the operation mode. It is also possible to provide only appropriate functions.

The normal mode (standard mode), full self mode, semi-self mode (accounting-only mode) of FIG. 5A, normal mode (restriction mode), and semi-self mode (registration-only mode) of FIG. 5B have been described above. However, hereinafter, the description will focus on the normal mode (standard mode), full self mode, and semi self mode (accounting only mode) of FIG. In the following description, the normal mode (standard mode) may be simply referred to as the normal mode. Further, the semi-self mode (accounting-only mode) may be simply referred to as the semi-self mode.

(Switching of operation mode (transition))
Next, switching (shifting) of the operation mode of the POS terminal 20 will be described. Basically, the operation mode of the POS terminal 20 is switched according to an explicit mode switching operation (also referred to as a mode shifting operation, which will be described later) for switching the operation mode by a store clerk. In addition, the POS terminal 20 may switch the operation mode according to another operation different from the mode switching operation (for example, reading a clerk code).

In addition, the operation mode of the POS terminal 20 may be switched regardless of the operation of the store clerk. Specifically, the POS terminal 20 may switch the operation mode according to a mode switching command (mode switching instruction) from another terminal (POS terminal 20, monitoring terminal, mobile terminal, etc.). In addition, the POS terminal 20 may switch the operation mode in accordance with a temporal condition (for example, elapsed time since the last operation, scheduled time, etc.). Further, the POS terminal 20 may switch the operation mode at the start of the process (for example, at the start of the settlement process based on the received registration information, at the start of the settlement process based on the accounting ticket, etc.). Further, the POS terminal 20 may switch the operation mode at the end of the processing (for example, at the end of the settlement processing based on the received registration information, at the end of the settlement processing based on the accounting ticket).

FIG. 6 is a diagram illustrating switching of operation modes of the POS terminal 20. The left side of FIG. 6 shows a combination of the operation modes before and after the switching (the operation mode before the switching→the operation mode after the switching), and the right side shows the conditions (an example) for switching the operation modes. For example, the line a indicates that a mode switching operation, a mode switching command, and a predetermined time period have passed (not used) as an example of conditions for switching the operation mode from the normal mode to the full self mode. That is, when the operation mode is the normal mode, for example, when there is a mode switching operation, a mode switching command, a predetermined time has passed (not used), the operation mode is switched from the normal mode to the full self mode. Showing. The details of the mode switching operation will be described later.

(Normal mode → Full self mode)
As shown in a, in the normal mode, for example, a mode switching operation, a mode switching command (a mode switching command in which the full self mode is specified as the operation mode of the transition destination, etc.), a predetermined time elapses (of a predetermined time If not used), the operation mode is switched from the normal mode to the full self mode.

(Normal mode → Semi-self mode (accounting only mode))
As shown in b, in the normal mode, for example, there was a mode switching operation, a mode switching command (a mode switching command in which the semi-self mode (accounting-only mode) is specified as the operation mode of the transition destination, etc.), and the like. In this case, the operation mode is switched from the normal mode to the semi-self mode (accounting-only mode). Further, in the normal mode, for example, when the registration information is received from another terminal or the accounting ticket is read, the operation mode may be switched from the normal mode to the semi-self mode (accounting only mode). ..

(Full self mode → normal mode)
As shown in FIG. 3C, in the full self mode, for example, when there is a mode switching operation, a mode switching command (a mode switching command in which the normal mode is specified as the operation mode of the transition destination, etc.), The operating mode switches from full self mode to normal mode.

(Full self mode → semi self mode (accounting only mode))
As shown in d, in the full self mode, for example, there is a mode switching operation, a mode switching command (a mode switching command in which a semi-self mode (accounting-only mode) is specified as a destination operation mode, etc.), and the like. In this case, the operation mode is switched from the full self mode to the semi self mode (accounting only mode). Also, in the full self mode, for example, when receiving registration information from another terminal or reading a bill, the operation mode is switched from the full self mode to the semi self mode (accounting only mode). Good.

(Full self mode → double scan mode)
As shown in e, in the full self mode, for example, when a clerk code is read, the operation mode is switched from the full self mode to the double scan mode. Note that the double scan mode is one mode of the full self mode (a state in which, in addition to the function of product registration (customer side), the function of product registration (clerk side) is used. See FIG. 5A).

If the clerk's code is read while in the full self mode, the operation mode may always be switched to the double scan mode regardless of the product registration state. Depending on the operation mode, the operation mode may be switched to a different one. For example, if a clerk code is read while product registration has not yet been performed (that is, product registration has not been performed by the customer), full self mode is switched to normal mode, and Even if the clerk code is read while the product is registered (that is, the product is registered by the customer), the full self mode is switched to the double scan mode. Good.

(Semi-self mode (accounting only mode) → normal mode)
As shown in f, when in the semi-self mode (accounting-only mode), for example, there was a mode switching operation, a mode switching command (a mode switching command in which the normal mode is specified as the operation mode of the transfer destination, etc.), etc. In this case, the operation mode is switched from the semi-self mode (accounting-only mode) to the normal mode. In addition, in the semi-self mode (accounting-only mode), for example, when the settlement process (for example, the settlement process based on the received registration information, the settlement process based on the accounting ticket) is completed, the semi-self mode (accounting-only mode) ), the operation mode may be switched to the normal mode.

(Semi-self mode (accounting only mode) → Full self mode)
As shown in g, when in the semi-self mode (accounting-only mode), there are, for example, a mode switching operation, a mode switching command (a mode switching command in which the full self mode is specified as the operation mode of the transition destination, etc.). In this case, the operation mode is switched from the semi-self mode (accounting-only mode) to the full self mode. In addition, in the semi-self mode (accounting-only mode), for example, when the settlement process (for example, the settlement process based on the received registration information, the settlement process based on the accounting ticket) is completed, the semi-self mode (accounting-only mode) ), the operation mode may be switched to the full self mode.

It should be noted that the mode switching operation may be such that the operation mode of the transfer destination is specified according to the operation. For example, if each button is provided (or displayed) for each migration destination, the operation mode may be switched to each migration destination in response to a mode switching operation of pressing each button. Further, when one button whose switching destination is switched each time the button is pressed is provided (or displayed), the operation mode may be switched each time a mode switching operation for pressing the button is performed.

It should be noted that a button for selecting the operation mode of the transfer destination and a button for determining the transfer to the operation mode selected by the button may be separately provided (or displayed).

(Transition of operation mode by mode switching operation)
Next, transition of operation modes by mode switching operation will be described. The operation mode of the POS terminal 20 is switched according to the explicit mode switching operation by the store clerk (see FIG. 6). Specifically, the operation mode is switched according to the operation of the mode switching button 211a (see FIG. 3B) arranged at the uppermost stage and the rightmost end of the key operation unit 211.

Since the mode switching button 211a is arranged at the corner of the key operation unit 211, it is possible to reduce operation mistakes when switching the operation mode and to easily switch the operation mode. That is, when the mode switching button 211a is present at the corner of the key operation unit 211, for example, when compared with the case where the mode switching button 211a is present near the center of the key operation unit 211, Since the number of other adjacent buttons is small, it is unlikely that an operation error such as operating other buttons in a hurry will occur easily, and the position of the mode switching button 211a to be operated can be instantly specified, so that the mode switching operation can be performed without stress. It can be performed.

Further, since the mode switching button 211a is arranged at the upper right corner (uppermost and rightmost corner) of the key operation portion 211, the mode switching operation is performed not only when the clerk is on the clerk side but also when the clerk is on the customer side. Will be able to. That is, the clerk on the customer side cannot normally see the buttons of the key operation unit 211, but for the mode switching button 211a located at the upper right end of the key operation unit 211, reach out from the customer side and feel for it. Since the mode switching button 211a which is the operation target can be easily recognized only by the (hand feeling), the store clerk on the customer side can perform the mode switching operation without moving to the store clerk side.

In addition, in the present embodiment, the mode switching button 211a is arranged at the upper right corner of the key operation unit 211, but if the position can be recognized only by fumbling (a position that can be relatively easily recognized), the mode can be changed. The switching button 211a may be arranged at a position other than the upper right corner of the key operation unit 211. Further, instead of or in addition to arranging the mode switching button 211a at a position that can be recognized only by groping (for example, the corner at the upper right end), it is possible to distinguish it from other buttons even from the customer side. The mode switching button 211a may be formed in the. For example, the size of the mode switching button 211a may be made different from the sizes of other buttons, or the shape of the mode switching button 211a may be made different from the shapes of other buttons, so that they can be distinguished only by groping. Alternatively, the height of the mode switching button 211a may be different from the height of the other buttons (for example, the mode switching button 211a may be protruded from the other buttons). ), the feel of all or part of the surface (the surface that the hand touches) of the mode switching button 211a may be different from the feel of other buttons (for example, only the surface of the mode switching button 211a is rough or bumpy). It may be made to feel, or protrusions or depressions may be provided only on the surface of the mode switching button 211a).

In addition, in the present embodiment, the mode switching button 211a is arranged in the key operation unit 211 in consideration of the various advantages as described above, but instead of disposing the mode switching button 211a in the key operation unit 211. Alternatively, in addition, a mode switching button (not shown) may be arranged on the screen displayed on the clerk-side display unit 210.

(Operation in each operation mode)
FIG. 7 is a schematic diagram for explaining the outline of the operation in the normal mode. Specifically, FIG. 7 is a schematic diagram showing the flow of processing and the operation of a person (a clerk, a customer) when the settlement processing is executed in the own terminal in the normal mode. FIG. 8 is a flowchart for explaining the outline of the operation in the normal mode. Specifically, FIG. 8 is a flowchart for explaining the outline of the operation when the settlement process is executed in the own terminal in the normal mode.

In the normal mode (similarly when the settlement process is performed in the own terminal and the case where the settlement process is performed in another terminal), the clerk stores the customer's purchase product in the clerk side (the clerk side scanner unit 212, the clerk side display unit 210, Registration is performed using the key operation unit 211) (upper part of FIG. 7). That is, the POS terminal 20 executes the registration process of the purchased product by the operation of the clerk (scan by the clerk-side scanner unit 212, touch on the clerk-side display unit 210, operation of the key operation unit 211) (upper stage of FIG. 7). ).

When the registration process by the clerk is completed, the customer confirms the total amount of the purchased products on the clerk-side display unit 210, inserts money (cash) into the change machine 209, or operates the card settlement unit 208 to make a payment. (Lower part of FIG. 7). That is, the POS terminal 20 executes the settlement process by the customer's operation or the like (cashing into the change machine 209, operation of the card settlement unit 208) (the lower part of FIG. 7).

That is, when the settlement process is executed in the own terminal in the normal mode, as shown in FIG. 8, the merchandise is scanned and the like at first (step S10: YES), and the merchandise is registered (step S11). After pressing the subtotal key (for example, the subtotal key displayed on the clerk-side display unit 210 or the subtotal key arranged on the key operation unit 211) (step S30: YES), on the customer side, for example, the change machine 209. Is settled (step S50), and the process is completed. The subtotal key in step S30 is an operation key for completing the registration process, and may be referred to as a subtotal button, a registration completion key, a registration completion button, a checkout key, a checkout button, or the like.

The customer may wait until the registration process by the clerk is completed (until the total amount of money is fixed), or cash may be inserted into the change machine 209 before the registration process is completed. That is, the POS terminal 20 can accept deposit during the registration process (upper part of FIG. 7).

Further, the customer may select a payment method (also referred to as a payment type, a payment method, or a payment type) before the registration process is completed. That is, the POS terminal 20 can accept the selection of the payment method during the registration process.

Further, the clerk may wait until the customer completes the payment (until the customer changes or receives the receipt), or may register the next customer's purchased product. That is, the POS terminal 20 can register the purchased product of the next customer during the settlement process (the lower part of FIG. 7). Further, the clerk may be absent during the settlement by the customer (lower part of FIG. 7). In other words, the reception of the customer may be finished during the settlement of the customer.

In addition, when there is change, the POS terminal 20 controls the payout of change and/or ticket by the change machine 209 to prevent forgetting of change, and detects that the customer has removed the change/tag. It is also possible to control the issuance of the receipt by the printing unit 213 after the recognition. The same applies to other operation modes.

FIG. 9 is a schematic diagram for explaining the outline of the operation in the normal mode. Specifically, FIG. 9 is a schematic diagram showing the flow of processing and the operation of a person (clerk, customer) when causing another terminal to execute the settlement processing in the normal mode (standard mode). FIG. 10 is a flowchart illustrating the outline of the operation in the normal mode. Specifically, FIG. 10A is a flowchart for explaining the outline of the operation in the case of causing another terminal to execute the settlement process in the normal mode (standard mode). Note that FIG. 10B is a flowchart showing the basic flow of the operation in the other terminal (other device) of FIG. 10A.

In the normal mode (similarly when the settlement process is performed in the own terminal and the case where the settlement process is performed in another terminal), the clerk stores the customer's purchase product in the clerk side (the clerk side scanner unit 212, the clerk side display unit 210, Registration is performed using the key operation unit 211) (upper part of FIG. 9). That is, the POS terminal 20 (the POS terminal 20-1 in the example of FIG. 9) is registered by the store clerk by operating the store clerk side scanner unit 212, the store clerk side display unit 210, the key operation unit 211, and the like. Is executed (upper part of FIG. 9).

When the registration process by the clerk is completed, the customer moves to another POS terminal 20 (POS terminal 20-2 in the example of FIG. 9), confirms the total price of the purchased goods on the clerk side display unit 210, and then the change machine. Money is put into 209 or the card settlement unit 208 is operated to make a payment (the lower part of FIG. 9). That is, the other POS terminal 20 executes the settlement process by the customer's operation or the like (inserting money into the change machine 209, operation of the card payment unit 208) (the lower part of FIG. 9 ).

The other POS terminal 20 (POS terminal 20-2) is supplied with information necessary for the settlement process (registration information generated in the POS terminal 20-1).

In addition, the clerk specifies the POS terminal 20 (either one of the POS terminal 20-2 and the POS terminal 20-3 in the example of FIG. 9) that executes the settlement process on the POS terminal 20-1. Alternatively, the clerk causes the POS terminal 20-1 to issue a medium (payment ticket) to be read by the POS terminal 20 (POS terminal 20-2 or POS terminal 20-3 in the example of FIG. 9) that executes the settlement process. May be.

That is, in the case of causing another terminal to execute the settlement process in the normal mode, as shown in FIG. 10A, the merchandise is scanned or the like at first by the clerk (step S10: YES) and the merchandise is registered (step S11). ). After the subtotal key (for example, the subtotal key displayed on the clerk-side display unit 210 or the subtotal key arranged on the key operation unit 211 or the like) is pressed (step S30: YES), for example, another adjustment process is executed. When the POS terminal 20 is designated (step S31: YES), the registration information is transmitted to the designated POS terminal 20 (step S32), and the processing on the registration side is completed.

The clerk can register the purchased product of the next customer after designating another terminal (lower part of FIG. 9). Further, the store clerk may be absent after designating another terminal (lower part of FIG. 9).

Further, in the example shown in FIG. 10A, another POS terminal 20 is specified after the subtotal key is pressed, but another POS terminal 20 may be specified without pressing the subtotal key. . For example, a subtotal key and a key for designating another POS terminal 20 are arranged on the registration screen (a key for issuing a transaction ticket may also be arranged) and the POS terminal 20 is designated. The registration information may be transmitted when the key is pressed. In the mode of designating another POS terminal 20 without pressing the subtotal key, it is not necessary to depress the subtotal key after pressing the key for designating another POS terminal 20.

Although omitted in the example shown in FIG. 10A, it is also possible to issue a transaction ticket to be read by another POS terminal 20 and cause the other POS terminal 20 to execute the settlement process. The key for issuing the transaction ticket may be pressed after pressing the subtotal key, or may be pressed before pressing the subtotal key. In the mode of pressing the key for issuing the accounting ticket before pressing the subtotal key, it is not necessary to press the subtotal key after pressing the key for issuing the accounting ticket.

Note that the other POS terminal 20 (POS terminal 20-2 in the example of FIG. 9) that has received the registration information, after receiving the registration information (step S40: YES), is in the semi-self mode, as shown in FIG. 10B. If it is not (accounting only mode), it shifts (switches) to semi-self mode (accounting only mode). That is, if the current operation mode (when receiving registration information) is the full self mode (step S41: YES), the full self mode is shifted to the semi-self mode (accounting-only mode) (step S42), and the current operation mode is set. If is the normal mode (step S43: YES), the normal mode is shifted to the semi-self mode (accounting-only mode) (step S42). Then, on the customer side, for example, the change machine 209 performs the settlement (step S50), and the processing on the settlement side is completed.

In the example shown in FIG. 10B, the other POS terminals 20 that have received the registration information shift to the semi-self mode (accounting-only mode) after receiving the registration information, if not the semi-self mode (accounting-only mode). However, it is not necessary to shift to the semi-self mode (accounting-only mode). That is, since the settlement process is possible even in the normal mode or the full self mode (see FIG. 5), the settlement process may be executed in the normal mode or the full self mode.

In the normal mode (standard mode), as described above, the function of executing the settlement process on the customer side of the own terminal by using the registration information generated in the registration process after executing the registration process on the salesclerk side (FIG. 7). , FIG. 8) and the registration information generated in the registration process to another terminal (another terminal capable of executing the settlement process, for example, another POS terminal 20) to cause the other terminal to perform the settlement process. (See FIGS. 9 and 10) and the registration information generated in the registration processing (or information for obtaining the registration information) is converted into a code (bar code, two-dimensional code, etc.) and printed, and a transaction ticket is issued. And a function of causing the other terminal to execute a settlement process.

On the other hand, in the normal mode (restricted mode), as shown in FIG. 5B, among the functions of the normal mode (standard mode) described above, the registration information generated in the registration process is transmitted to another terminal and the other information is transmitted. A function for causing a terminal to execute a settlement process, and issuing a transaction ticket in which the registration information generated in the registration process (or information for obtaining the registration information) is printed and issued to the other terminal. This is a mode in which the functions to be executed are restricted.

Further, among the functions of the normal mode (standard mode) described above, the function of transmitting the registration information generated in the registration processing to another terminal and causing the other terminal to execute the settlement processing, and the registration information generated in the registration processing ( Alternatively, the function of issuing an accounting ticket printed by encoding (printing information for obtaining the registration information) and causing the other terminal to execute the settlement process is also a function of the semi-self mode (registration-only mode). That is, the semi-self mode can be classified into a registration-only mode and an accounting-only mode. However, the semi-self mode (registration-only mode) uses the registration information generated in the registration process as shown in FIG. 5B. A function to send to a terminal to cause the other terminal to execute a settlement process, and issue a transaction ticket printed by encoding the registration information generated in the registration process (or information for obtaining the registration information) A function of causing the other terminal to execute a settlement process. In other words, the semi-self mode (registration-only mode) is one of the functions of the above-described normal mode (standard mode), which uses the registration information generated in the registration process after the registration process is performed by the clerk. This is a mode in which the function of executing settlement processing on the customer side is limited. That is, the semi-self mode (registration-only mode) is an operation mode in which registration processing is exclusively executed.

As shown in FIG. 5A, the semi-self mode (accounting-only mode) has a function of receiving registration information generated in registration processing in another terminal and executing a settlement process, and a function issued in another terminal. It also includes the function to read the bill and execute the settlement process. That is, the semi-self mode (accounting-only mode) is an operation mode in which the settlement process is executed exclusively.

FIG. 11 is a schematic diagram for explaining the outline of the operation in the full self mode. FIG. 12 is a flowchart illustrating the outline of the operation in the full self mode.

In the full self mode, the customer registers his or her purchased product 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 merchandise by the customer's operation (scan by the customer side scanner unit 206, touch on the customer side display unit 205) (upper part of FIG. 11 ).

When the registration process is completed, the customer confirms the total price of the purchased products on the customer-side display unit 205, deposits cash in the change machine 209, or operates the card settlement unit 208 to make a payment (the lower part of FIG. 11). ). That is, the POS terminal 20 executes the settlement process by the customer's operation or the like (cash input to the change machine 209, operation of the card settlement unit 208) (lower part of FIG. 11 ).

That is, in the case of the full self mode, as shown in FIG. 12, the customer scans the product (step S20: YES) and registers the product (step S21). After the registration completion key (for example, the registration completion key displayed on the customer side display unit 205) is pressed (step S40: YES), on the customer side, for example, the change machine 209 performs the settlement (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 be referred to as a registration completion button, a subtotal key, a subtotal button, a checkout key, a checkout button, or the like.

In the full self mode, as shown in FIG. 11, the customer side executes the registration process and the settlement process, but the clerk side cannot do anything. That is, even when the POS terminal 20 is operating in the full self mode, for example, the clerk scans the product (double scan mode) or the clerk displays various information. It is possible.

FIG. 13 is a schematic diagram for explaining the outline of the operation in the double scan mode. FIG. 14 is a flowchart for explaining the outline of the operation in the double scan mode. The double scan mode is one mode of the full self mode, but in FIG. 13 and FIG. 14, both operation modes will be described separately for convenience.

In the full self mode, the customer registers his/her purchased product on the customer side (upper part of FIG. 11, upper part of FIG. 13). That is, the POS terminal 20 executes the registration processing of the purchased product by the operation of the customer (upper part of FIG. 11, (upper part of FIG. 13)).

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

When the registration process is completed, the customer confirms the total price of the purchased products on the customer side display unit 205, deposits cash in the change machine 209, or operates the card settlement unit 208 to make a payment (the lower part of FIG. 13). ). In other words, the POS terminal 20 executes the settlement process by the customer's operation or the like (cash input to the change machine 209, operation of the card settlement unit 208) (lower part of FIG. 13).

That is, when the registration process is executed in the full self mode (see FIG. 12 ), as shown in FIG. 14A, the clerk code is read by the clerk-side scanner unit 212 (step S110: YES). The operation mode shifts from the full self mode to the double scan mode (step S111).

After shifting to the double scan mode, as shown in FIG. 14B, the merchandise is registered by scanning the clerk side scanner unit 212 (step S10: YES) (step S11) and the customer side scanner unit 206. The product is registered by scanning (step S20: YES) (step S21). Subtotal key (for example, the subtotal key displayed on the clerk-side display unit 210, or the subtotal key arranged on the key operation unit 211) or the registration completion key (for example, the registration displayed on the customer-side display unit 205) After pressing the (completion key or the like) (step S41: YES), on the customer side, for example, the change machine 209 makes a payment (step S50), and the process is completed.

In the double scan mode, the clerk may wait until the customer completes the settlement (until the customer changes or receives the receipt), or may register the purchased product for the next customer. That is, the POS terminal 20 can register the purchased product of the next customer during the settlement process (lower part of FIG. 13). Further, the store clerk may be absent during the settlement by the customer (the lower part of FIG. 13). In other words, the reception of the customer may be finished during the settlement of the customer.

As shown in FIG. 14A, when the store clerk code is read in the full self mode, the operation mode shifts from the full self mode to the double scan mode. However, reading the store clerk code is one of login operations. May be one. Further, the operation mode may shift from the full self mode to the double scan mode when another operation (for example, a login operation different from reading the clerk code) is performed in the full self mode. Further, the operation mode may shift from the double scan mode to the full self mode when the operation by the store clerk is stopped in the double scan mode (for example, when a predetermined time has passed from the time of the last operation).

(Notification of operation mode)
Each POS terminal 20 may notify the current operation mode of its own terminal. For example, each POS terminal 20 may display the current operation mode of its own terminal on the clerk-side display unit 210. Specifically, each POS terminal 20 displays a screen having an operation mode display field of its own terminal on the salesclerk side display unit 210, and displays the current operation mode of its own terminal in the operation mode display field on the screen. May be. In addition, each POS terminal 20 displays a screen on which images (for example, button-like images) corresponding to each operation mode are arranged on the clerk side display unit 210, and the current operation mode of the own terminal is displayed on the screen. The image to be displayed may be displayed in a display mode different from the image not corresponding to the current operation mode (for example, a display mode that is more conspicuous than the display modes of other images). For example, when operating in two operation modes, the normal mode and the full self mode, the normal mode image and the full self mode image are always displayed, and the normal mode image is displayed when the current operation mode of the self terminal is the normal mode. The display mode may be displayed in a more prominent display mode than the full self mode image, and the full self mode image may be displayed in a more prominent display mode than the normal mode image when the current operation mode of the own terminal is the full self mode. .. Each POS terminal 20 may also display the current operation mode of its own terminal on the customer side display unit 205.

Each POS terminal 20 may notify the current operation mode of another terminal instead of or in addition to the current operation mode of its own terminal. That is, each POS terminal 20 may notify the current operation mode of the other terminal by mutually recognizing the current operation mode of the other terminal. An example of a method in which each POS terminal 20 mutually recognizes the current operation mode of another terminal is that each POS terminal 20 notifies the other terminal of the operation mode (latest operation mode) after the operation mode transition (the latest operation mode). Via the store controller 10 or the monitoring terminal, etc.). Further, each POS terminal 20 may notify the current processing status of another terminal, as in the current operation mode of another terminal.

Further, each POS terminal 20 may notify information according to the current operation mode or the like (operation mode, processing status, etc.) of its own terminal. For example, each POS terminal 20 may display various types of information on the customer-side display unit 205 when the current operation mode of the POS terminal 20 is the full self mode, for example, when the POS terminal 20 is on standby. Further, the POS terminal 20 may notify information according to the current operation mode of another terminal instead of or in addition to the information according to the current operation mode of the own terminal.

Even if the operation mode is switched by the operation of the store clerk (by mode switching operation, reading of the store clerk code, etc.), the operation mode is switched without the operation of the store clerk (mode switching command, predetermined time Even if it is due to progress, etc.), the operation mode of the own terminal or another terminal is notified.

(Memory of information related to operation mode)
Each POS terminal 20 may store in which operation mode a transaction (process) was performed, as information regarding the operation mode. 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 executes the registration process and the settlement process determines that the transaction As information (for example, settlement information) (or in association with information regarding the transaction), information indicating that the registration process and the settlement process regarding the transaction were performed in the normal mode (standard mode) (for example, the operation mode is identified. Possible information) may be stored.

Note that each POS terminal 20 may also store in which terminal the transaction (processing) was performed. In the above example, the POS terminal 20-1 may store, as the information related to the transaction, information indicating that the registration processing and the settlement processing have been executed in the own terminal (POS terminal 20-1). More specifically, the POS terminal 20-1 stores the terminal identification information of its own terminal as the identification information (terminal identification information) of the terminal that has performed the registration process, and at the same time as the terminal identification information of the terminal that has performed the settlement process. The terminal identification information of the terminal may be stored. 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 has executed the entire process (registration process, settlement process).

Further, for example, first, the POS terminal 20-1 operating in the normal mode (standard mode) executes the registration process for a certain transaction, and then the POS terminal 20-2 operating in the semi-self mode (accounting-only mode). However, when the settlement process is executed for the transaction based on the registration information by the registration process, the POS terminal 20-2 that has executed the settlement process stores the information (or the settlement information) related to the transaction (or The information indicating that the registration process related to the transaction was performed in the normal mode (standard mode) and the settlement process related to the transaction was performed in the semi-self mode (accounting-only mode). Information may be stored. In addition to the above, the POS terminal 20-1 that has performed the registration process may also store information indicating that the registration process related to the transaction was performed in the normal mode (standard mode).

In the above example, the POS terminal 20-2, which has executed the settlement process, stores the information indicating that the registration process has been executed in the other terminal (POS terminal 20-1) as the information regarding the transaction, and the self-terminal (POS). Information indicating that the settlement process has been executed in the terminal 20-2) may be stored. More specifically, the POS terminal 20-2 stores the terminal identification information of the other terminal (POS terminal 20-1) as information (terminal identification information) of the terminal that has performed the registration process, and the terminal that has performed the settlement process. The terminal identification information of its own terminal (POS terminal 20-2) may be stored as the terminal identification information of. In the above example, on the side of the POS terminal 20-2 that executes the settlement process, the terminal identification information and the operation mode (specifically, the normal mode (standard mode)) of the POS terminal 20-1 that executed the registration process are displayed. It is only necessary to be able to acquire the identifying information. For example, the terminal identification information of the POS terminal 20-1 and the information identifying the operation mode are supplied from the POS terminal 20-1 side to the POS terminal 20-2 side (for example, transmission/reception as registration information, a transaction ticket). It is sufficient if it is configured to be supplied through).

In addition, each POS terminal 20 may store the transition (switching) of the operation mode as information regarding the operation mode. For example, when the operation mode of the POS terminal 20-1 is changed from a certain operation mode to another operation mode, which operation mode has the POS terminal 20-1 moved along with the operation mode transition time? Information (for example, information capable of identifying the operation mode after the transition) may be stored. In addition, the POS terminal 20-1 has information about which operation mode has been changed to which operation mode along with the operation mode transition time (for example, information that can identify the operation mode before the transition and the operation mode after the transition. May be stored).

Even when the operation mode of each POS terminal 20 is switched by the operation of the store clerk (when the mode is switched, by reading the store clerk code, etc.), the operation mode is switched without the operation of the store clerk ( Even if it is a mode switching command, a case where a predetermined time has elapsed, or the like), information regarding the transition of the operation mode may be stored. In the above case, each POS terminal 20 is based on what information the operation mode is changed to (for example, the operation mode is changed by the operation by the store clerk with the store clerk code “XXX”, the terminal identification information “XX”). The fact that the operation mode has been changed by a mode switching command from the POS terminal 20 of “X”) may be stored.

Note that the store controller 10, the monitoring terminal, or the like may store information regarding the operation mode instead of or in addition to the POS terminal 20.

Further, the information regarding the operation mode stored as described above may be output (displayed, transmitted, printed, etc.) as necessary. For example, the POS terminal 20 provides the receipt output in the full self mode with information indicating that the process (registration process, settlement process) has been performed in the full self mode (information in a mode in which only the clerk can recognize the contents, or the customer). Information in a form that can also be recognized) may be printed. Receipts output in other operation modes may be printed in the same manner. Further, for example, the POS terminal 20 (or the monitoring terminal) may display the operation mode at the time of processing. As an example, when the transaction number (information that can identify a transaction) is input on a predetermined search screen or the like, the POS terminal 20 (or the monitoring terminal) performs the registration process and the settlement process for the corresponding transaction. For at least one of the terminals, the processed terminal (terminal identification information or the like) and the operation mode (information capable of identifying the operation mode) may be displayed.

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

(Display example of POS terminal 20 in full self mode)
15 and 16 are display examples on the POS terminal 20 in the full self mode. Specifically, FIG. 15(A), FIG. 15(B), and FIG. 16(A) to FIG. 16(F) are all tables on the customer side display unit 205 of the POS terminal 20-3 in the full self mode. It is an example.

FIG. 15A shows the display contents of the registration start screen before the start of the registration process. In FIG. 15A, a registration start button BT30 on the right side of the screen is a button for instructing the start of product registration. The customer operates the registration start button BT30 when starting the product registration. Buttons BT35 to BT37 at the lower left of the screen are buttons for switching the display language to English, Chinese, and Korean, respectively.

FIG. 15B shows the display contents of the registration screen in a state where two items of goods (Daifuku Mochi) are registered. Note that when the registration start button BT30 is operated on the registration start screen shown in FIG. 15A, the POS terminal 20-3 displays the registration screen in which no product has been registered yet. For convenience of description, FIG. 15B shows a registration screen after the products (tea, Daifuku-mochi) have already been registered.

In FIG. 15B, the image GA01 at the lower left of the screen shows the state of the other terminal (POS terminal 20-1) (specifically, the normal mode). The image GA02 at the lower left of the screen shows the state of the other terminal (POS terminal 20-2) (specifically, the normal mode). The transaction button BT32 at the bottom right of the screen is a button for instructing the end of product registration. The customer operates the checkout button BT32 after the product registration is completed. The clerk call button BT33 is a button for calling a clerk. The customer operates the clerk call button BT33 when calling the clerk (for example, when the clerk needs support).

The buttons BT35 to BT37 are buttons for switching the display language to English, Chinese, and Korean, respectively, as described above. The “vegetable” button BT38 is a button for displaying each vegetable preset key (see FIG. 17).

FIG. 16A shows the display contents of the payment screen (payment method selection screen) displayed when the payment processing is started. For example, the POS terminal 20-3 displays the payment method selection screen as shown in FIG. 16A when the checkout button BT32 is operated on the registration screen (see FIG. 15B).

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

FIG. 16C shows the display contents of the settlement screen (payment screen) displayed when determining the deposit amount. For example, the POS terminal 20-3 displays the deposit screen as shown in FIG. 16C when cash (deposit money) equal to or larger than the payment amount (purchase amount) is input.

FIG. 16D shows the display contents of the settlement screen (change screen) displayed when the change is released. For example, the POS terminal 20-3 displays the change screen as shown in FIG. 16D when the end (receipt) button BT40 is operated on the deposit screen (FIG. 16C).

FIG. 16(E) shows the display contents of the settlement screen (receipt screen) displayed when the change is removed. For example, the POS terminal 20-3 displays the receipt screen as shown in FIG. 16E when the change is removed from the outlet of the change dispenser 209. In addition, the POS terminal 20 may install a sensor such as a photo sensor in the vicinity of the outlet and determine that the change has been removed when the sensor recognizes an object (assuming the customer's hand). FIG. 16F is a pause screen displayed in the pause mode (pause state).

The POS terminal 20-3 displays the registration start screen (FIG. 15(A)) after the receipt screen (FIG. 16(E)) is displayed. 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 include a sensor capable of recognizing that the receipt has been removed from the issuing port. When no change is generated, the change screen (FIG. 16C) may be changed to the receipt screen (FIG. 16E) without displaying the change screen (FIG. 16D). ..

(Display example of POS terminal 20 in normal mode)
17 to 22 are display examples on 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 in the normal mode (standard mode). ) Is a display example on the clerk side display unit 210 of the POS terminal 20-1. 17(B), FIG. 18(B), FIG. 19(B), FIG. 20(B), FIG. 21(B), and FIG. 22(B) are all POS terminals 20 in the normal mode (standard mode). It is a display example on the customer side display unit 205 of -1.

FIG. 17A shows the display content on the registration screen in the initial state on the salesclerk side display unit 210. In the following description, unless otherwise noted, the initial state is a state in which processing is not in progress, for example, a state in which nothing has been registered for the product, and nothing has been done regarding payment (settlement). In a state (a payment method has not been selected, cash has not been registered, gift certificates have not been registered, etc.), and nothing has been done about the customer (a member card etc. has not been read, etc.) is there.

In FIG. 17A, a tab area T1 at the upper right of the screen is a tab corresponding to each display content (display screen). The POS terminal 20-1 interrupts the registration process of the customer (the reason for the interruption is that the customer returns to the store for the purpose of adding a purchased product), and the registration process of the next customer is possible. That is, the POS terminal 20-1 displays a new registration screen for the next customer while holding (storing) the display content (registration content) of the registration screen for the customer based on the operation of the clerk. Although the number of tabs is one (tab area T1) in the example shown in FIG. 17A, the POS terminal 20-1 displays a number of tabs corresponding to the number of ongoing registration screens (number of customers) (tab The registration screen to be activated (active) is switched according to the operation (pressing) of the regions T1, T2, T3,..., And tabs.

In the tab area T1, information for identifying the tab from other tabs (the number “1” in the example of FIG. 17A) is displayed. Further, in the tab area T1, a display field HR01 for displaying the amount of money deposited by the customer is provided. Although not displayed in the example shown in FIG. 17A, various information (described later) other than the above is displayed in the tab area T1.

The image GA02 at the lower left of the screen shows the state of the other terminal (POS terminal 20-2) (specifically, the normal mode). The image GA03 at the lower left of the screen shows the state of the other terminal (POS terminal 20-3) (specifically, the full self mode).

FIG. 17B shows the display content on the customer-side display unit 205 in the initial state. That is, when the POS terminal 20-1 displays the registration screen on the clerk-side display unit 210 as shown in FIG. 17(A), the customer-side display unit 205 displays the registration screen as shown in FIG. 17(B). The small screen (small window) SG01 is displayed on the settlement screen (payment screen).

The small screen SG01 allows the customer to select the payment method. The customer selects either cash, credit or electronic money as the payment method on the small screen SG01. When the customer desires cash as the payment method, the customer may throw in cash (deposit) before selecting cash as the payment method on the small screen SG01. The POS terminal 20-1 erases the small screen SG01 when any payment method is selected on the small screen SG01. Further, when cash is input before the payment method is selected on the small screen SG01, the POS terminal 20-1 processes the cash as selected as the payment method, and erases the small screen SG01.

When the can of beer is registered by the clerk from the state where the clerk side display unit 210 displays the registration screen of FIG. 17A, the POS terminal 20-1 displays the clerk side display unit 210 of FIG. Display the registration screen as shown in.

In FIG. 18A, the subtotal button BT10 at the bottom right of the screen is a button for instructing the end of product registration. The store clerk operates (touches) the subtotal button BT10 after the product registration is completed.

The 20-2 cash register button BT12 is a button for designating a 20-2 cash register (POS terminal 20-2). When designating the POS terminal 20-2 as the terminal for transmitting the registration information, the clerk operates the 20-2 cashier button BT12. "(Normal)" shown on the 20-2 cash register button BT12 indicates that the operation mode of the POS terminal 20-2 corresponding to the 20-2 cash register button BT12 is the normal mode.

The 20-3 cash register button BT13 is a button for designating a 20-3 cash register (POS terminal 20-3). When designating the POS terminal 20-3 as the terminal for transmitting the registration information, the clerk operates the 20-3 cash register button BT13. "(Full Self)" shown on the 20-3 cash register button BT13 indicates that the operation mode of the POS terminal 20-3 corresponding to the 20-3 cash register button BT13 is the full self mode.

The accounting ticket button BT15 is a button for causing the printing unit 213 to issue an accounting ticket. The clerk operates the accounting ticket button BT15 when the POS terminal 20 that has read the accounting ticket (the POS terminal 20 that the customer has read the accounting ticket) executes the process.

When the POS terminal 20 in the normal mode and the POS terminal 20 in the full self mode are compared as the POS terminal 20 to which the registration information is transmitted, the POS terminal 20 in the full self mode is better than the POS terminal 20 in the normal mode. Is preferable as a destination of registration information. Since the POS terminal 20 in the normal mode is basically operated by a store clerk (see FIGS. 7 and 8), processing (for example, registration processing, customer correspondence, etc.) continues to exist, and registration is performed. Even if you send information, it is likely that it can not be processed immediately, and even if it is available (even if there is no clerk or customer), basically it is vacant to immediately respond to the customer who wants to support the clerk. On the other hand, the POS terminal 20 in the full self mode can process the registration information immediately after sending the registration information if there is no customer. This is because such problems are unlikely to occur.

In view of the above, the clerk is informed whether or not it is preferable as the POS terminal 20 as the transmission destination of the registration information, or which is more preferable when there are a plurality of transmission destinations of the registration information. As an example, in FIG. 18A, the outline portion of the 20-3 register button BT13 corresponding to the POS terminal 20-3 in the full self mode, which is relatively preferable as the destination of the registration information, is indicated by a solid line, and the destination of the registration information is indicated. The outline portion of the 20-2 register button BT12 corresponding to the POS terminal 20-2 in the normal mode, which is relatively unfavorable as, is indicated by a broken line. Note that the above-described notification by the contour portion is an example, and whether the POS terminal 20 as the transmission destination of the registration information is preferable, or which is more preferable when there are a plurality of transmission destinations of the registration information The notification mode is not limited as long as can be recognized. For example, if it is relatively unfavorable, the background color of the button may be displayed in gray-down, or the entire button may be provided with a punishment mark or a diagonal line. The display size, shape, and display position of the button may be changed depending on whether or not the POS terminal 20 to which the registration information is transmitted is preferable, and some information (“priority” or “recommended”) may be displayed on the button. Badge-like image, etc.) may be attached.

When the POS terminal 20-1 displays the registration screen as shown in FIG. 18(A) on the salesclerk side display unit 210, the customer side display unit 205 displays a small screen as shown in FIG. 18(B). The screen SG01 is displayed by being superimposed on the settlement screen (payment screen). The total amount was 0 yen because the product was not registered on the payment screen (payment screen) of FIG. 17B, but the total amount of money was 215 yen on the payment screen (payment screen) of FIG. 18B. Is registered, the total amount is 215.

In the POS terminal 20-1, when 500 yen is put in by the customer from the state where the registration screen of FIG. 18(A) is displayed on the salesclerk side display unit 210, the salesclerk side display unit 210 is shown in FIG. 19(A). Display the registration screen as shown in.

Since the customer puts in 500 yen, 500 is displayed in the display field HR01 at the upper right of the screen in FIG. 19(A). In addition, since the payment of 500 yen means that the payment is made at the own terminal (POS terminal 20-1), it is used when the payment is made at the other terminals (POS terminal 20-2, POS terminal 20-3). Buttons (20-2 cash register button BT12, 20-3 cash register button BT13, accounting ticket button BT15) are hidden (erased).

When the POS terminal 20-1 displays the registration screen as shown in FIG. 19(A) on the salesclerk side display unit 210, the payment screen (payment screen) as shown in FIG. 19(B) is displayed. It is displayed on the customer side display unit 205. Note that the small screen SG01 has been erased because 500 yen has been input by the customer.

In the POS terminal 20-1, from the state in which the registration screen of FIG. 19(A) is displayed on the salesclerk-side display unit 210, the salesclerk has registered two products (aspara) and three products (paste lunch). When the customer further inputs 500 yen, the salesclerk side display unit 210 displays a registration screen as shown in FIG. Since the customer additionally puts in 500 yen, 1000 is displayed in the display field HR01 at the upper right of the screen in FIG.

When the POS terminal 20-1 displays the registration screen as shown in FIG. 20(A) on the clerk-side display unit 210, the payment screen (payment screen) as shown in FIG. 20(B) is displayed. It is displayed on the customer side display unit 205.

When the clerk operates the subtotal button BT10 from the state where the clerk side display unit 210 displays the registration screen of FIG. 20A, the POS terminal 20-1 displays the clerk side display unit 210 of FIG. ), a small screen (small window) SG02 is displayed so as to be superposed on the registration screen, and the customer side display unit 205 displays a payment screen (payment screen) as shown in FIG. 21B. In addition, the small screen SG02 is for notifying the clerk of the information related to settlement (total amount of money, amount of money deposited into the device (deposit amount of money)).

When the customer operates the end (receipt) button BT40 from the state where the customer side display unit 205 displays the settlement screen (payment screen) of FIG. 21B, the POS terminal 20-1 displays the clerk side. 22A, the message screen MG1 is displayed so as to be superimposed on the registration screen, and the customer-side display unit 205 displays a payment screen (change screen) as shown in FIG. 22B. indicate.

The message screen MG1 informs the clerk of the change. The POS terminal 20-1 erases the message screen MG1 superimposed and displayed on the registration screen regardless of the operation of the store clerk (for example, automatically after a lapse of a predetermined time). Note that the POS terminal 20-1 may delete the message screen MG1 superimposed and displayed on the registration screen in accordance with the operation of the clerk (touch on the message screen MG1 or the like).

Although illustration is omitted from FIG. 22 onward, the POS terminal 20-1 displays the payment screen similar to that of FIG. 16E on the customer side display unit 205 and the payment screen on the clerk side display unit 210. Display the corresponding message.

In the above description, attention is paid to the overall processing in the POS terminal 20, and no processing is in progress (product not registered, cash not inserted, payment type not selected, gift certificate not registered, customer information not acquired). Although the state (1) is referred to as the initial state, it may be referred to as the initial state by paying attention to a part of the processing. For example, the cash-in product registration state (product registration, cash insertion, payment type not selected, gift certificate not registered, customer information not acquired) can be said to be the initial state when focusing on the overall processing. Although it is not, it can be said that it is the initial state when paying attention only to the state of selecting the payment type. In addition, when attention is focused on the two states of the product registration state and the payment type selection state, it cannot be said that the initial state, but the two states of the payment type selection state and the gift certificate registration state. When paying attention to, it may be said that it is the initial state.

In the example shown in FIG. 21, the POS terminal 20-1 displays the small screen SG02 by superimposing it on the registration screen when the subtotal key is operated (FIG. 21(A)). When the subtotal key is operated, the terminal 20-1 may display the small plan surface displaying the information and the like displayed on the small screen SG02 instead of (switching) to the registration screen.

(Example of operation mode switching process)
Next, an example of the operation mode switching process of the POS terminal 20 will be described with reference to FIGS. 23 and 24. FIG. 23 is a flowchart showing an example of the operation mode switching process performed by the POS terminal 20 in which the mode switching button is pressed. Since any of the POS terminals 20 is provided with a mode switching button, the processing shown in FIG. 23 is started when the mode switching button is pressed on any of the POS terminals 20. The process shown in the flowchart of FIG. 23 is always started (periodically at a very short time interval) in each POS terminal 20.

Step S201: The POS terminal 20 determines whether or not the mode switching button 211a has been pressed. When the mode switching button 211a is not pressed, the POS terminal 20 proceeds to step S208. When the mode switching button 211a is pressed, the POS terminal 20 proceeds to step S202.
Step S202: The POS terminal 20 transmits a mode switching command to another POS terminal 20, and proceeds to step S203.

Step S203: The POS terminal 20 determines whether or not its own terminal is processing. The process here is, for example, a product registration process or a settlement process for accepting payment from a customer. The POS terminal 20 proceeds to step S204 when its own terminal is processing. If the POS terminal 20 is not processing it, the POS terminal 20 proceeds to step S206.
Step S204: The POS terminal 20 informs (displays) that its own terminal is processing, and proceeds to step S205.
Step S205: The POS terminal 20 determines whether or not the process being executed is completed. The POS terminal 20 waits until the process being executed ends, and when the process being executed ends, the process proceeds to step S206.

Step S206: The POS terminal 20 performs mode switching processing, and proceeds to step S207. The mode switching process is a process of switching to a mode different from the current mode, and is, for example, a process of switching to any one of the normal mode, the accounting-only mode, and the full self mode, which is different from the current mode.
Step S207: The POS terminal 20 notifies that the mode switching of its own terminal is completed, and proceeds to step S208.

Step S208: The POS terminal 20 determines whether or not the information indicating that the processing is in progress is received from another POS terminal 20 to which the mode switching command is transmitted. When the POS terminal 20 does not receive the information indicating that it is being processed from another POS terminal 20, the process proceeds to step S210. When the POS terminal 20 receives the information indicating that the process is in progress from the other POS terminal 20, the process proceeds to step S209.

Step S209: The POS terminal 20 informs that another POS terminal 20 is processing, and proceeds to step S210.
Step S210: The POS terminal 20 determines whether or not the information indicating that the mode switching is completed is received from another POS terminal 20. When the POS terminal 20 does not receive the information indicating that the mode switching is completed from another POS terminal 20, the POS terminal 20 ends the series of processes as it is. When the POS terminal 20 receives the information indicating that the mode switching is completed from another POS terminal 20, the process proceeds to step S211.
Step S211: The POS terminal 20 notifies that the mode switching of the other POS terminals 20 has been completed, and ends the series of processes.

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

Step S221: The POS terminal 20 determines whether or not a mode switching command has been received. When the POS terminal 20 does not receive the mode switching command, the POS terminal 20 ends the series of processes as it is. When the POS terminal 20 receives the mode switching command, the process proceeds to step S222.
Step S222: The POS terminal 20 determines whether or not its own terminal is processing. 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 processing the process, the POS terminal 20 proceeds to step S223. If the POS terminal 20 is not processing it, the POS terminal 20 proceeds to step S225.

Step S223: The POS terminal 20 transmits the fact that the process is in progress to the POS terminal 20 which is the transmission source of the mode switching command, and proceeds to step S224.
Step S224: The POS terminal 20 determines whether or not the process being executed is completed. The POS terminal 20 waits until the process being executed ends, and when the process being executed ends, the process proceeds to step S225.

Step S225: The POS terminal 20 performs mode switching processing, and proceeds to step S226.
Step S226: The POS terminal 20 transmits information indicating that the mode switching is completed to the POS terminal 20 which is the transmission source of the mode switching command, and proceeds to step S227.
Step S227: The POS terminal 20 notifies that the mode switching of its own terminal is completed, and ends the series of processes.

(About an example of screen transition when correcting products in full self mode)
Next, with reference to FIGS. 25 to 27, an example of screen transitions when a product is corrected in the full self mode will be described. 25 to 27 are explanatory diagrams showing an example of screen transitions when correcting a registered product in the full self mode. Note that, in the following description and drawings, the same content as the content of the above-described screen transition will be denoted by the same reference numeral, and description thereof will be omitted.

FIG. 25A shows that, in the full self mode, two products, “tea” and “sweet potato”, are registered by the customer's operation. For example, for "tea", the customer registers the product by causing the POS terminal 20 to read the barcode. As for “sweet potato”, the customer registers the product by selecting an area (button) indicating “sweet potato” from the preset keys. In addition, a guide display 2501 is displayed in FIG. The guidance display 2501 indicates that the customer can correct the registered product by long-pressing the area indicating the product desired to be corrected (changed).

As shown in (A) of FIG. 25, it is assumed that the customer long presses the area indicating “sweet potato”. That is, it is assumed that the customer has performed an operation for correcting the product "sweet potato". In this case, the screen changes to the screen shown in FIG. FIG. 25(B) shows a confirmation screen as to whether or not to cancel “sweet potato”. When the customer selects “Yes” on the confirmation screen, the screen changes to the screen shown in FIG. If the customer selects “No” on the confirmation screen, for example, the screen returns to the screen shown in FIG.

FIG. 25C shows a notification screen indicating that the clerk is calling to cancel the "sweet potato". In addition, in FIG. 25C, the area in which “sweet potato” is registered is different from the normal display mode (bold, framed, special color) so that it can be clearly shown that the product is a product to be corrected. Etc.) is displayed. With this, when the store clerk goes, the product to be corrected can be grasped at a glance. Also, the product to be corrected becomes clear to the customer.

Here, the timing for calling the store clerk may be the timing when "Yes" shown in (B) of FIG. 25 is pressed (the timing after the confirmation screen), or the product is long-pressed in (A) of FIG. The timing (timing of long pressing) may be used. By calling the clerk at the timing of long-pressing, the clerk can be called quickly. In addition, by calling the clerk at a timing after the confirmation screen, it is possible to prevent the clerk from calling the clerk due to an erroneous operation of the customer or calling the clerk due to an operation error or misunderstanding of the customer. Further, the notification for calling the store clerk is performed, for example, on the POS terminal 20 operated or browsed by the store clerk, the mobile terminal owned by the store clerk, the management device, or the like.

FIG. 26D shows a screen when a store clerk goes to the POS terminal 20 on which the correction operation has been performed and the store clerk presses the clerk button. In FIG. 26D, when the clerk presses the clerk button, the screen changes to the screen shown in FIG.

In (E) of FIG. 26, a notification prompting the clerk to read the clerk code is displayed. When the clerk, for example, causes the POS terminal 20 to read the clerk code attached to his/her name tag, the clerk is authenticated. If the authentication is successful, the screen changes to the screen shown in (F) of FIG. On the other hand, if the authentication fails, for example, an error message is displayed. Note that another store clerk may be called together with the display of the error message. In this case, the other store clerk may go to the POS terminal 20 that has performed the correction operation and perform authentication, so that the other store clerk may approve the correction. Note that the authentication of the clerk is not limited to the authentication using the clerk code, and may be biometric authentication such as fingerprint authentication or authentication by inputting a password.

FIG. 26F shows a confirmation screen for approval by the store clerk. The clerk visually confirms whether the correction content entered by the customer is correct (whether it is an operation error or registration error) (checks the product in the basket), and if it is determined to be correct, the confirmation screen is displayed. Click "Yes". When the clerk selects "Yes" on the confirmation screen, the screen changes to the screen shown in FIG. On the other hand, if the clerk selects “No” on the confirmation screen, the series of correction operations is canceled, and the screen returns to the screen shown in FIG. In this case, the correction will not be accepted.

FIG. 27G shows a notification screen indicating that the correction (cancellation) has been completed. In addition, the product (sweet potato) that has been subject to cancellation is not hidden but is clearly indicated as a canceled product by, for example, attaching a strike line. Thereby, the customer and the store clerk can easily understand that the product has been canceled. Specifically, if the canceled product is hidden, if the customer confirms the canceled product, it is necessary to check whether the product to be purchased matches the product being displayed. You'll be checking each one to make sure the canceled items aren't displayed. Such confirmation is more troublesome for the customer, and particularly when the number of products to be purchased is large. In the present embodiment, the canceled product is displayed with a strike-through line so that the customer can easily understand the product to be corrected even when the number of registered products is large.

As shown in FIGS. 25 to 27, in the present embodiment, the customer performs a part of the correction operation and the clerk only has to press the approval button, so that the waiting time of the customer for the correction can be shortened. In addition, the operation of the clerk can be simplified. Therefore, the registered merchandise can be efficiently corrected.

(About another screen example when correcting products in full self mode)
Next, with reference to FIG. 28, another screen example when correcting the product in the full self mode will be described. FIG. 28 is an explanatory diagram showing another example of a screen when correcting a product in the full self mode. Note that FIG. 28 differs from the screens shown in FIGS. 26 and 27 in that the change in quantity is accepted.

FIG. 28A shows that, in the full self mode, two products, “tea” and “sweet potato”, are registered by the operation of the customer. As shown in (A) of FIG. 28, it is assumed that the customer long presses the area indicating “tea”. In this case, the screen transitions to the screen shown in FIG. FIG. 28B shows a screen for accepting a change in quantity. In FIG. 28B, when the “+” button is pressed, the quantity is added according to the number of times the button is pressed. On the other hand, when the "-" button is pressed, the quantity is subtracted according to the number of times the button is pressed. By setting the quantity to “0”, the product can be canceled as in FIGS. 27 and 28.

In FIG. 28B, when a change in the quantity is accepted, the change button 2801 becomes operable. Here, it is assumed that the change button 2801 is pressed after accepting a change of increasing quantity. In this case, since it is not recognized that the increase in the quantity is a fraudulent act, the increase in the quantity is recognized as it is without requiring the approval of the store clerk, and the screen returns to the registration screen of FIG.

On the other hand, it is assumed that the change button 2801 is pressed after the change in which the quantity decreases is accepted. In this case, since the store clerk needs to confirm whether or not the correction is valid, the store clerk is called. However, the quantity of the product registered by scanning the barcode cannot be set to "0". Specifically, as shown in FIG. 28B, the customer presses the "-" button when the quantity is "1". In this case, the screen changes to that shown in FIG.

FIG. 28C shows a screen indicating that the registered merchandise cannot be set to “0” by scanning the barcode. In the case of a product with a bar code, the customer may mistakenly register the bar code twice in a row. For this reason, the quantity can be changed from "2" to "1" or from "3" to "2". Therefore, it is possible to accept a correction to reduce the quantity to "0".

On the other hand, regarding a product with a bar code, it is clear that the product actually exists due to the reading of the bar code, and therefore it is not assumed to change the quantity to “0”. Therefore, it can be considered that there is a high possibility that an operation of changing “1”→“0” for a product with a bar code is an erroneous operation. Therefore, it is necessary to prevent such an erroneous operation. ing.

In addition, even if the product has a barcode, the customer may want to cancel the product after registering the product, for example, because the amount of money is unexpected. In this case, the customer may call the store clerk by pressing the store clerk call button and perform the cancel operation by the store clerk. The cancel operation by the store clerk is performed by, for example, displaying a list of products by the operation of the store clerk who succeeded in the authentication using the store clerk code, and selecting the product to be canceled by the store clerk from among them.

Note that whether the deletion of the product is accepted by pressing the area indicating the product as shown in FIGS. 25 to 27 or the change of the quantity is accepted as shown in FIG. 28 depends on the clerk. It may be possible to change the setting. Further, when the area indicating the product is pressed, it is possible to display a selection screen as to whether to accept the deletion of the product or the change of the quantity so that the customer can select.

(Regarding an example of product registration processing in the full self mode performed by the POS terminal 20)
FIG. 29 is a flowchart showing an example of product registration processing in the full self mode performed by the POS terminal 20.
Step S301: The POS terminal 20 determines whether or not there is a touch on the clerk-side display unit 210 (preset key), an operation of the key operation unit 211, a scan of the clerk-side scanner unit 212, or the like. The POS terminal 20 waits when there is no scan or the like, and proceeds to step S302 when there is a scan or the like.

Step S302: The POS terminal 20 registers the merchandise, displays the merchandise on the clerk-side display section 210, and proceeds to step S303.
Step S303: The POS terminal 20 determines whether or not a product correction has been accepted. If the POS terminal 20 does not accept the correction of the product, the POS terminal 20 proceeds to step S306. When the POS terminal 20 receives the correction of the product, the POS terminal 20 proceeds to step S304.
Step S304: The POS terminal 20 determines whether or not the quantity is to be increased. If the POS terminal 20 determines that the quantity has not increased, that is, if the quantity has decreased, the process proceeds to step S305. When the POS terminal 20 determines that the quantity has increased, the process proceeds to step S306.

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 determines whether or not the subtotal key of the key operation unit 211 has been pressed. When the subtotal key is not pressed, the POS terminal 20 returns to step S301. When the subtotal key is pressed, the POS terminal 20 proceeds to step S307.

Step S307: The POS terminal 20 determines whether or not a product correction has been accepted. When the POS terminal 20 does not accept the correction of the product, the POS terminal 20 proceeds to step S308. When the POS terminal 20 receives the correction of the product, the POS terminal 20 proceeds to step S309.

Step S308: The POS terminal 20 determines whether the settlement has been completed. In the settlement, the POS terminal 20, for example, displays a small plan surface, and upon receipt of a settlement operation such as input of a deposit or pressing a current total button, issues a receipt or the like. In addition, in the settlement, a change or a change according to the current amount may be released. If the settlement is not completed, the POS terminal 20 returns to step S307. When the settlement is completed, the POS terminal 20 ends the series of processes.

Step S309: The POS terminal 20 determines whether or not the change is an increase in the quantity. If the POS terminal 20 determines that the quantity has not increased, that is, if the quantity has decreased, the process proceeds to step S310. If the POS terminal 20 determines that the increase in the quantity has been changed, the process proceeds to step S311.

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 for changing the subtotal amount, and proceeds to step S308.

(About an example of product correction processing in the full self mode performed by the POS terminal 20)
FIG. 30 is a flowchart showing an example of product correction processing in the full self 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 of FIG. In addition, below, it demonstrates as a process of step S305.

Step S321: The POS terminal 20 calls the clerk to 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 input. The clerk code may be, for example, the clerk may read the clerk code attached to the clerk's name tag on the clerk-side scanner unit 212, or the clerk may directly input the clerk code (number) by operating the key operation unit 211. It is input by doing. The POS terminal 20 waits until the clerk code is input, and when the clerk code is input, the process proceeds to step S323.

Step S323: The POS terminal 20 determines whether or not the authentication of the clerk using the clerk code has succeeded. When the POS terminal 20 fails to authenticate the clerk, the POS terminal 20 proceeds to step S324. When the POS terminal 20 succeeds in authenticating the clerk, the process proceeds to step S325.
Step S324: The POS terminal 20 reports an error and returns to step S301. In the correction process of step S310 of FIG. 29, the process proceeds to step S311 after the process of step S324.
Step S325: The POS terminal 20 determines whether or not the approval result has been received from the 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.

Step S326: The POS terminal 20 determines whether or not the accepted approval result is an approval result allowing the correction. The POS terminal 20 returns to step S301 when the accepted approval result is an approval result that does not allow correction. In this case, no correction is made. The POS terminal 20 proceeds to step S327 if the accepted approval result is an approval result that allows the correction.
Step S327: The POS terminal 20 corrects the registered product, and returns to step S301.

With the processing shown in FIGS. 29 and 30, when the POS terminal 20 receives a correction from the customer, the POS terminal 20 calls the store clerk and receives the approval from the store clerk to correct the registration information. As a result, the customer performs a part of the operation related to the correction of the product information, so that the waiting time of the customer related to the correction can be shortened. Further, since the store clerk only has to go to the POS terminal 20 and perform an operation for approval, the store clerk's operation for changing the product information can be simplified.

(About an example of screen transition when correcting products in the semi-self mode)
Next, with reference to FIGS. 31 and 32, an example of transition of screens in the case of correcting a product in the semi-self mode will be described. In the following description, the POS system 1 in which the normal mode POS terminal 20 is arranged on the upstream side of the accounting lead wire and the semi-self mode POS terminal 20 is arranged on the downstream side of the accounting lead wire will be described as an example. In the following, in the POS system 1, a case will be described in which, after the registration of the product by the clerk at the upstream POS terminal 20, the downstream POS terminal 20 makes a correction when the customer pays. Further, the transition of the screen of the downstream POS terminal 20 (screen of the customer side display unit 205) in the POS system will be described below.

31 and 32 are explanatory diagrams showing an example of the transition of the screen on the customer side when the product is corrected in the semi-self mode. FIG. 31A shows a screen of the customer-side display unit 205 when a plurality of types of products are registered by the operation of the store clerk in the upstream POS terminal 20 and the payment is made in the downstream POS terminal 20. A guide display 3101 is displayed in FIG. The guidance display 3101 indicates that the customer can correct the registered product by long pressing the area indicating the product desired to be corrected.

As shown in (B) of FIG. 31, it is assumed that the customer has long pressed the area indicating “sweet potato”. Specifically, for example, it is assumed that "sweet potatoes" have not been purchased by the customer's recognition, but "sweet potatoes" are registered, and the customer has performed an operation to correct "sweet potatoes". In this case, the screen changes to the screen shown in FIG. FIG. 31C shows a confirmation screen as to whether or not to cancel the “sweet potato”. When the customer selects “Yes” on the confirmation screen, the screen changes to the screen shown in FIG. At this time, the content of the correction and the correction approval request are transmitted from the downstream POS terminal 20 to the upstream POS terminal 20. In FIG. 31C, if the customer selects “No” on the confirmation screen, for example, the screen returns to the screen shown in FIG.

FIG. 32D shows a notification screen for waiting until the approval of the store clerk (store clerk who registered the product) arranged on the upstream POS terminal 20 to cancel the “sweet potato”. It should be noted that an example of a screen when the store clerk approves will be described later with reference to FIG. 33. In addition, in (D) of FIG. 32, the area in which “sweet potato” is registered is a display mode different from the normal display mode (bold type, framed area, special color) so that it can be clearly shown that the product is a product to be corrected. Etc.) is displayed. As a result, the product to be corrected becomes clear to the customer.

FIG. 32E shows a notification screen indicating that the correction (cancellation) has been completed by the clerk's approval at the upstream POS terminal 20. In addition, the product (sweet potato) that has been subject to cancellation is not hidden but is clearly indicated as a canceled product by, for example, attaching a strike line. It should be noted that, if the approval of the store clerk is not obtained, that is, if the registration of "sweet potato" is not incorrect, the cancellation of "sweet potato" will not be permitted.

(Regarding an example of screen transition of the clerk side display unit 210 of the upstream POS terminal 20 when correcting a product)
Next, with reference to FIG. 33, an example of the transition of the screen of the salesclerk side display unit 210 of the upstream POS terminal 20 when correcting a product will be described. FIG. 33 is an explanatory diagram showing an example of the screen transition of the clerk-side display unit 210 of the upstream POS terminal 20 when correcting a product. In the description of FIG. 33, the upstream POS terminal 20 is in the normal mode, and the downstream POS terminal 20 has finished registering the customer's product to be paid for and then registered the next customer's product. To do.

FIG. 33A shows a screen when the product of the next customer is registered. The image GA02 at the lower left of the screen in FIG. 33A indicates that the downstream POS terminal 20 (POS terminal 20-2) is in the semi-self mode. In addition, the notification image 3301 shows a reminder that the clerk at the downstream POS terminal 20 needs support or the like. The notification image 3301 is displayed, for example, when a correction approval request or a store clerk calling request is issued from the downstream POS terminal 20. In FIG. 33A, when the clerk presses the image GA02 or the notification image 3301, the screen changes to the screen shown in FIG. 33B.

FIG. 33B shows a confirmation screen for approval by the clerk. If the store clerk can instantly determine that the registration is wrong, or if the clerk can visually confirm the erroneous registration from the position of the store clerk, the POS terminal 20 on the upstream side performs an approval operation (press “Yes”). ). On the other hand, if the clerk cannot confirm from the POS terminal 20 on the upstream side whether or not the registration is incorrect, the clerk moves to the POS terminal 20 on the downstream side and visually confirms the correction contents. And approve it. Further, the POS terminal 20 on the downstream side may accept the approval of the clerk. Specifically, the clerk's approval may be accepted at the downstream POS terminal 20 by displaying a confirmation screen for approval by the clerk on the salesclerk-side display unit 210 of the downstream POS terminal 20. As a result, the POS terminal 20 on the downstream side can quickly accept the approval of the store clerk. The store clerk may return to the upstream POS terminal 20 and accept the store clerk's approval at the upstream POS terminal 20.

When the clerk selects “Yes” on the confirmation screen shown in FIG. 33B, the correction (cancellation) is completed. On the other hand, if the clerk selects “No”, the correction will not be accepted. Further, the approval result selected by the clerk is transmitted to the POS terminal 20 on the downstream side. When either a "yes" or "no" operation is accepted from the salesclerk on the confirmation screen, the screen transitions to the screen shown in FIG. 33C, and the merchandise of the next customer is continuously registered.

As shown in FIGS. 31 to 33, in the present embodiment, the correction operation is accepted from the customer at the time of settlement in the semi-self mode. Here, from the viewpoint of a customer who pays at the POS terminal 20 on the downstream side, it is difficult for the clerk who is placed on the POS terminal 20 on the upstream side to speak to the clerk who has registered the product for the next customer. Therefore, it may be a psychological burden for the customer to request (request) the correction. In the present embodiment, the clerk does not directly request the correction, but the clerk can be notified of the content of the correction through the POS terminal 20, so that the customer's mental burden when making the correction can be reduced.

Further, when performing a series of correction operations, the customer performs a part of the correction operations, and the clerk only has to press the approval button. Therefore, it is possible to shorten the waiting time of the customer related to the correction and also to simplify the operation of the store clerk. Further, the clerk can approve the correction while registering the product of the next customer. Therefore, the registered merchandise can be efficiently corrected.

31 to 33, the case where the correction is performed when the customer makes the settlement has been described, but the present invention is not limited to this, and the correction can be performed when the customer's product is registered. Specifically, when a clerk is registering a product at the upstream POS terminal 20, a customer waiting for registration at the POS terminal 20 is displayed on the customer-side display unit 205 (see FIGS. 17 to 22). It is also possible to accept the correction during registration of the merchandise by the store clerk by long-pressing the area indicated by (B) in each figure.

(About other screen examples when correcting products in semi-self mode)
Next, another screen example when correcting a product in the semi-self mode will be described with reference to FIGS. 34 to 36. 34 to 36 are explanatory diagrams showing other screen examples when correcting a product in the semi-self mode. 34 to 36, among the items indicating the product name, the number, and the amount of money in the display region indicating the product, changes in the items indicated by the long-pressed display region are accepted. 31 to 33.

34A, 35A, and 36A show the customer-side display unit 205 when the POS terminal 20 on the downstream side performs the payment due to the registration of the product on the POS terminal 20 on the upstream side. Shows the screen. In FIG. 34A, it is assumed that the customer long-presses the area indicating the product name (the display area indicating the characters “tomato”) in the area of the product “tomato”. In this case, the screen transition is similar to the case of canceling the "sweet potato" shown in FIG. 31 (see (C) of FIG. 31, (D), and (E) of FIG. 32).

Further, as shown in (A) of FIG. 35, it is assumed that the customer long presses the area showing the number of pieces of the product “tomato”. In this case, the screen changes to the screen shown in FIG. FIG. 35B shows a screen for accepting a change in quantity. The description when accepting the change in the quantity is as described in FIGS. 28B and 28C. Then, in FIG. 35B, when the quantity change is confirmed by the approval of the clerk, the screen changes to the screen shown in FIG. 35C.

FIG. 35C shows a notification screen indicating that the correction (change in the quantity) has been completed. Further, the quantity and amount of the product (tomato) before the change is not displayed but is displayed in a display mode different from the normal display mode so that the corrected content can be grasped. Thereby, the customer can easily recognize that the quantity of the product has been changed.

Further, as shown in (A) of FIG. 36, it is assumed that the customer long presses the area showing the amount of money in the area of the product “tomato”. In this case, the screen changes to the screen shown in FIG. Here, with regard to products on time sale, close-up products, etc., the buying price recognized by the customer may differ from the selling price registered in the preset key. Therefore, in the present embodiment, it is possible to accept the change in the amount of money from the customer. FIG. 36B shows a screen for accepting a change in the amount. FIG. 36B shows a screen on which the input of the amount of money from the customer can be accepted with the ten keys.

In FIG. 36B, when the change in the amount of money is accepted, the enter button 3601 becomes operable. When the customer depresses the decision button 3601 and obtains the approval of the clerk to confirm the change in the amount, the screen changes to the screen shown in (C) of FIG. 36. When the decision button 3601 is pressed, a notification image 3301 (see (A) of FIG. 33) is displayed on the salesclerk side display unit 210 of the upstream POS terminal 20, and the salesclerk's approval can be accepted. .. FIG. 36C shows a notification screen to the effect that the correction (change in amount) has been completed. Also, the price of the product (tomato) before the change is not hidden, but is displayed so that the corrected content can be grasped. Thereby, the customer can easily recognize that the price of the product has been changed.

34 to 36, an example of correcting a product in the semi-self mode has been described, but the same correction can be performed in the case of the full self mode. That is, in the full self mode, when displaying each item indicating the product name, the number, and the amount of money in the display area indicating the product, the item indicated by the long-pressed display area among these items is changed. You may make it accept.

It should be noted that, by pressing the area indicating the product as shown in FIGS. 31 and 32, the deletion of the product (including the quantity change) is accepted, or the product is deleted as shown in FIGS. 34 to 36. It may be possible to change the setting of whether to accept the change of the item by pressing the area indicating the item, by the operation of the store clerk. Further, among the plurality of items, the items for which correction can be accepted may be capable of being set and changed by the operation of the clerk. Specifically, for example, among the items indicating the product name, the number of items, and the amount of money, the item name and the number of items are set to be able to accept corrections, and the amount of money is set to not be accepted for correction. Good. Further, the correction target is not limited to the items described above, and may include, for example, items to which discount coupons are applied and items to which events such as time sale are applied.

(About an example of the settlement process in the semi-self mode performed by the POS terminal 20)
FIG. 37 is a flowchart showing an example of the settlement process in the semi-self mode performed by the POS terminal 20 (settlement device) on the downstream side. Note that the POS terminal 20 that performs the process of FIG. 37 is the POS terminal 20 (also referred to as “accounting apparatus”) arranged on the downstream side.
Step S341: The POS terminal 20 determines whether or not the registration information is received from the upstream POS terminal 20. The POS terminal 20 waits until the registration information is received, and when the registration information is received, the process proceeds to step S342.

Step S342: The POS terminal 20 determines whether or not the correction has been accepted from the customer. If the POS terminal 20 does not accept the correction from the customer, the process proceeds to step S347. When the POS terminal 20 receives the correction from the customer, the POS terminal 20 proceeds to step S343.
Step S343: The POS terminal 20 transmits an approval request to the upstream POS terminal 20 (also referred to as “registration device”), and proceeds to step S344.

Step S344: The POS terminal 20 determines whether or not the approval result has been received from the upstream POS terminal 20. The POS terminal 20 waits until it receives the approval result from the upstream POS terminal 20, and when receiving the approval result from the upstream POS terminal 20, proceeds to step S345.

Step S345: The POS terminal 20 determines whether or not the received approval result is an approval result allowing the correction. If the received approval result is an approval result that does not allow correction, the POS terminal 20 proceeds to step S347. In this case, no correction is made. If the received approval result is an approval result that allows the correction, the POS terminal 20 proceeds to step S346.

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 determines whether the settlement has been completed. When the settlement is not completed, the POS terminal 20 returns to step S342. When the settlement is completed, the POS terminal 20 ends the series of processes.

By the above-described processing, when the POS terminal 20 on the downstream side (POS terminal 20 in the semi-self mode) receives the correction from the customer, it makes an approval request to the POS terminal 20 on the upstream side, and the approval result for the correction is obtained. If so, the regenerated registration information can be received. As a result, the customer performs a part of the operation related to the correction of the product information, so that the waiting time of the customer related to the correction can be shortened.

(Regarding an example of processing performed when the approval request is received by the POS terminal 20 on the upstream side)
FIG. 38 is a flow chart showing an example of processing when an approval request is received by the POS terminal 20 (registration device) on the upstream side. The process shown in the flowchart of FIG. 38 is always started (periodically at a very short time interval) in the upstream POS terminal 20.

Step S361: The POS terminal 20 determines whether or not an approval request for correction of the registered product has been received from the downstream POS terminal 20 (settlement device). The POS terminal 20 waits until receiving the approval request, and when receiving the approval request, the process proceeds to step S362.

Step S362: The POS terminal 20 notifies the clerk that the approval request has been received, and proceeds to step S363. For example, the POS terminal 20 notifies the clerk that the approval request has been received by displaying the notification image 3301 (see (A) of FIG. 33) on the clerk-side display unit 210.
Step S363: The POS terminal 20 determines whether or not the approval result (see (B) of FIG. 33) 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.

Step S364: The POS terminal 20 transmits the approval result to the POS terminal 20 on the downstream side, and proceeds to step S365.
Step S365: The POS terminal 20 determines whether or not the accepted approval result is an approval result allowing the correction. When the accepted approval result is an approval result that does not allow correction, the POS terminal 20 ends the series of processes. In this case, no correction is made. The POS terminal 20 proceeds to step S366 when the accepted approval result is an approval result that allows the correction.

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 POS terminal 20 on the downstream side, and ends the series of processes.

By the above-described process, the upstream POS terminal 20 (the POS terminal 20 in the normal mode) receives the approval request from the downstream POS terminal 20, thereby accepting the approval of the store clerk and transmitting the accepted approval result to the downstream side. Can be transmitted to the POS terminal 20. In addition, when the approval result permitting the correction is received, the registration information can be regenerated and transmitted to the POS terminal 20 on the downstream side. Thereby, the clerk can approve the correction of the product information of the previous customer even when the product of the next customer is registered. Therefore, it is possible to reduce the load on the clerk when approving.

According to the above-described first embodiment, the customer performs a part of the operation related to the change of the product information, and the clerk only has to perform the approval operation. Therefore, the operation of the clerk related to the change of the product information is performed. It can be simplified. Therefore, the registered merchandise can be efficiently changed. This makes it possible to suitably change the product information and improve the convenience of the product sales data processing device.

(Embodiment 2)
Next, a second embodiment of the present invention will be described. In the above-described first embodiment, the configuration in which the POS terminal 20 performs product registration, product correction, approval of correction, and settlement is described. In the second embodiment, a configuration will be described in which the registration of a product and the correction of the product are accepted by the mobile terminal, and the approval and the settlement of the correction are performed by the settlement device. In the description of the second embodiment, the same components as those in the first embodiment described above will be denoted by the same reference numerals, and the description thereof will be appropriately omitted.

FIG. 39 is a network configuration diagram showing a shopping system according to the second embodiment 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.

The cloud server 300 is a computer device including a CPU, a ROM, a RAM, a communication unit, and the like. The settlement device 400 is a computer device including a CPU, a ROM, a RAM, a communication unit, a touch panel, a key operation unit, a scanner unit, a card settlement unit, a change machine, a printing unit, a voice output unit, and the like. The settlement device 400 may be a dedicated device for settlement, or may be the POS terminal 20 by setting the POS terminal 20 of the first embodiment in the semi-self mode. The mobile terminal 500 is a computer device including a CPU, a ROM, a RAM, a communication unit, an imaging unit (camera), a touch panel, a voice output unit, a voice input unit, and the like.

The store controller 10 and the settlement device 400 are installed in the store and are communicably connected via a LAN 11 (wired or wireless). The store controller, the settlement device 400, and the mobile terminal 500 are connected to the cloud server 300 so that they can communicate with each other.

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

The mobile terminal 500 is a terminal device operated by a customer (a shopper who is a member of the store, etc.), and is, for example, a communication device including a display screen such as a smartphone, a tablet device, and a mobile phone. The mobile terminal 500 is a device that receives registration of products. The mobile terminal 500 has a function of scanning a barcode attached to a product and reading the product code, in addition to a general communication function and an imaging function (camera). That is, the mobile terminal 500 has a recognition function of recognizing a barcode attached to a product.

Note that the recognition function of the mobile terminal 500 is only required to be able to read the product code, and the product may not be specified from the read product code. That is, when the barcode is present as an object in the captured image captured by the image capturing function (the image acquired as the through image), the mobile terminal 500 is only required to be able to read the product code from the barcode. .

In addition, the mobile terminal 500 images a product (for example, a peripheral portion with a barcode) and generates a captured image (image data). For example, the mobile terminal 500 generates a captured image by releasing the shutter according to its own judgment. However, the mobile terminal 500 may generate a captured image by releasing the shutter according to the operation of the customer who is the operator.

In addition, the mobile terminal 500 may include image recognition technology that extracts a feature point from an image (through image, captured image) and recognizes an imaging target (object or the like). For example, the mobile terminal 500 may identify (estimate) the imaged product using an image recognition technique. Specifically, the mobile terminal 500 may identify the fresh food such as vegetables and fruits without the barcode by the image recognition technology.

In addition, a predetermined application (application software) is installed in the mobile terminal 500. The mobile terminal 500 can read a product code and register a product corresponding to the read product code (transmitted to the cloud server 300 and registered) by activating a predetermined application.

The mobile terminal 500 is, for example, a property of each customer. However, the mobile terminal 500 may be a loan item that the store lends to the customer. Note that the number of mobile terminals 500 (the number of operating terminals) changes according to the number of visitors. Although two mobile terminals 500 are illustrated in FIG. 39, the number of mobile terminals 500 is actually several tens, several hundreds, or more.

The settlement device 400 is a device for performing settlement of a product registered by a registration operation of a customer using the mobile terminal 500. The settlement device 400 accepts payment by cash, credit card, prepaid card, or the like.

39 shows a plurality of settlement devices 400, the number of settlement devices 400 may be one. Further, one store controller 10 may be installed in one store, or two or more store controllers 10 may be installed.

(Example of information managed by the cloud server 300)
Next, an example of information managed by the cloud server 300 will be described. 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.

FIG. 40A shows an example of customer information. The customer information is information for managing each customer. Specifically, the customer information includes customer identification information, a customer name, a customer registration date, cancellation information, a customer rank, and the number of points.

The customer identification information is identification information that uniquely identifies the customer. The customer name is, for example, the customer's name or nickname. The customer registration date is the date and time when the customer information is newly registered in the cloud server 300. The cancellation information is information indicating the number of times the registered product is canceled after the product is registered during shopping. The customer rank is a rank according to the purchase record of the customer.

The number of points is the number of points given to the customer by shopping using this application. The number of points may include the number of points for each store. Further, the customer information shown in FIG. 40A is an example, and in the second embodiment, at least the customer identification information may be included. Note that the cloud server 300 generates customer identification information, a customer name, and a customer registration date when generating customer information of a new customer, but since it is before the start of the actual transaction (commodity registration), other Information (cancellation information, etc.) is not generated.

FIG. 40B shows an example of store information. The store information is information for managing each store. Specifically, the shop information includes shop identification information, a shop name, shop identification information 1 (two-dimensional code information), and shop identification information 2 (position information). The store identification information includes a store (store name) or company code and a branch code. The store name is the name of the store, and is composed of, for example, a store name (store name) or a company name, and a branch name.

The store specifying information 1 and 2 are information for specifying a store to be traded (a store where goods are bought and sold). The store specifying information 1 is, for example, information of a two-dimensional code (QR code (registered trademark) or the like). The store identification information 2 is position information (GPS information) of the store. In addition, in the example shown in FIG. 40B, the store identification information and the store identification information 1 are stored separately, but since both are information that can uniquely identify the store, at least one of them is stored. Information may be stored.

FIG. 40C shows an example of basket information. The basket information is information about customer purchases at the store. Specifically, the 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. The basket identification information is information for identifying the basket information. Specifically, the basket identification information includes store identification information, a date, and a serial number (for example, a serial number for each store-specific date).

The transaction start date and time is the transaction start date and time, for example, the generation date and time of the basket information. The transaction start date and time may be the registration date and time of one item of merchandise (the date and time when the registered merchandise information (registered merchandise 1) shown in (C) of FIG. 40 is stored). Also, the registration date and time of each product may be stored separately.

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 who performs the transaction. Although the cloud server 300 generates the basket identification information, the transaction start date and time, and the customer identification information when generating the basket information, since it is before the actual transaction (commodity registration) is started, other information (transaction end) (Date and time etc.) is not generated.

The registered product information (total) is information that is updated each time a product is registered. The registered product information (total) includes the number of products (the number of products) and the subtotal amount. The registered merchandise information (1) is registration information for one item of merchandise. The registered merchandise information (2) is registration information of two commodities. In the example shown in (C) of FIG. 40, the registered product information of three or more items is omitted.

The cancellation candidate information (this time total) indicates the number of times the cancellation of the registered product is accepted after the product is registered during the current shopping. The cancellation candidate information (cancellation candidate 1) includes a product code indicating a product to be canceled and the quantity of the product. Although not shown, if the cancellation is actually completed with the approval of the clerk, cancellation information (not shown) indicating that the cancellation is completed is stored. Further, the cancellation information is added to the history so far and stored in the customer information of (A).

Next, the processing flow of the shopping system will be described with reference to FIG. FIG. 41 is a sequence diagram showing a processing flow of the shopping system according to the second embodiment. Note that FIG. 41 shows a flow until a customer visits a store, the customer uses the mobile terminal 500 of the customer to register the product to be purchased, and the payment device 400 completes the payment of the product. Is shown.

Step S401: First, the mobile terminal 500 acquires information specifying a store (for example, store specifying information). Here, an example of an acquisition mode of information that specifies a store 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 and output on a predetermined display device or may be displayed and output by printing on a medium.

The printed medium is, for example, a paper medium. This paper medium may be affixed near the entrance of the store, or may be distributed to customers at the store. The customer who visits the store uses the mobile terminal 500 to scan the two-dimensional code. Thereby, the mobile terminal 500 can acquire the store identification information. Note that the two-dimensional code may include store identification information for identifying the store.

Further, the mobile terminal 500 may display a screen prompting the scanning of the two-dimensional code as an initial screen when a predetermined application (application software) is activated in response to the operation of the customer who has visited the store. Further, when the mobile terminal 500 scans the two-dimensional code according to the operation of the customer who visits the store, the mobile terminal 500 activates the application and displays a screen notifying that the cloud server 300 is being connected as an initial screen. Good.

Moreover, acquisition of position information is mentioned as another example of the acquisition mode of the information which specifies a store. For example, the mobile terminal 500 acquires position information (GPS information) according to the operation of the customer who visits the store. This position information is information that replaces the store identification information. Note that the mobile terminal 500 acquires position information by the application being activated in response to the operation of the customer who has come to the store, and displays a screen notifying that the cloud server 300 is being connected as an initial screen. Good.

Although the cloud server 300 specifies a store according to the position information from the mobile terminal 500, there are cases where a plurality of stores are specified in this specification (a case where one shop cannot be specified). In this case, the cloud server 300 may transmit the information indicating that to the mobile terminal 500. Then, the mobile terminal 500 may display a selection screen for allowing the customer to specify the store, or may notify that the customer is prompted to scan the two-dimensional code indicating the store identification information.

The mobile terminal 500 that has acquired the shop identification information transmits the acquired shop 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, for example, information stored in the cloud server 300 or the mobile terminal 500 when newly registering a customer (when installing an application in the mobile terminal 500). Specifically, the information such as the name entered in the registration form is attached to the customer identification information by the cloud server 300 and stored in the cloud server 300 and the mobile terminal 500.

In addition, when the mobile terminal 500 acquires the store specifying information, the mobile terminal 500 may output information regarding services being implemented in the store (leaflet information distributed on that day) or usable coupon information on the display screen. For example, the information on the service and the coupon information may be transmitted from the cloud server 300 when the mobile terminal 500 makes a transaction start request to the cloud server 300.

The mobile terminal 500 also stores the information of the transmission destination (address of the cloud server 30) when newly registering a customer (when installing an application on the mobile terminal 500). The two-dimensional code displayed near the entrance of the store may include the destination information (address of the cloud server 300) in addition to the store identification information. The mobile terminal 500 can also access the cloud server 300 by scanning the two-dimensional code to acquire the store identification information and the destination information.

Step S402: When the cloud server 300 receives the customer identification information and the store identification information as a transaction start request from the mobile terminal 500, the cloud server 300 generates basket information of the transaction. Specifically, the cloud server 300 generates basket identification information, transaction start date and time, and customer identification information (see (C) in FIG. 40). Note that the cloud server 300 does not generate other information (transaction end date and time, etc.) at this timing because the actual transaction (commodity registration) has not yet started.

More specifically, when the cloud server 300 receives the store identification information and the customer identification information as the transaction start request from the mobile terminal 500, the cloud server 300 refers to the store information (see (B) of FIG. 40) and stores the store identification information. Identify. When the cloud server 300 receives the position information from the mobile terminal 500, the cloud server 300 refers to the store identification information 2 of the store information and identifies the store identification information corresponding to the position information. If the two-dimensional code includes the store identification information, the cloud server 300 can also obtain the store identification information by combining the received two-dimensional code.

In addition, when the cloud server 300 receives a transaction start request (store identification information and customer identification information) from the mobile terminal 500, the cloud server 300 acquires the current date and issues a serial number (numbering). Furthermore, the 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. When receiving the transaction start request from the mobile terminal 500, the cloud server 300 stores the current date and time in the transaction start date and time (generation date and time) in the basket information. When receiving the transaction start request from the mobile terminal 500, the cloud server 300 stores the customer identification information received from the mobile terminal 500 in the customer identification information in the basket information.

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

Step S404: Upon receiving 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, a screen before product registration in FIG. 42A, and details will be described later.

Step S405: The mobile terminal 500 scans the barcode attached to the product and reads the product code according to the operation of the customer. In FIG. 41, it is assumed that the scanning of the barcode is successful. When the mobile terminal 500 acquires the product code, the mobile terminal 500 transmits the acquired product code and the basket identification information to the cloud server 300 (see transmission/reception data D3 in FIG. 41).

Step S406: When the cloud server 300 receives the product code and the basket identification information from the mobile terminal 500, the cloud server 300 specifies the basket information including the received basket identification information.

Step S407: The cloud server 300 updates the product data included in the specified basket information. Specifically, when the product code of N items is received, the cloud server 300 stores the product code as the product code of the registered product information (registered product N). Furthermore, the cloud server 300 stores the product code, the product name, and the price in association with each other as product information (registered product N). Further, the cloud server 300 updates the cumulative information (cumulative number of products, subtotal amount, etc.) of the registered product information in the specified basket information.

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

Step S409: Upon receiving the basket identification information and the product registration update screen information from the cloud server 300, the mobile terminal 500 displays the product registration update screen with the product added to the registration screen. The product registration update screen is, for example, the screen shown in FIG. 42(A), and the details will be described later. Although not shown in FIG. 41 for convenience of description, the processing of steps S405 to S409 is processing that is repeatedly executed each time the barcode attached to the product is scanned. That is, the processes of steps S405 to S409 loop until the accounting instruction of step S410, which will be described later, is received.

Step S410: The mobile terminal 500 receives an accounting instruction by a customer operation. The accounting instruction is accepted, for example, by pressing a “accounting button” shown in FIG. 42 described later.

Step S411: The mobile terminal 500, upon receiving the accounting instruction, generates a two-dimensional code. The two-dimensional code includes information (for example, basket identification information) necessary for executing the settlement process in the settlement device 400 for the product to be purchased. When the mobile terminal 500 generates the two-dimensional code, the generated two-dimensional code is displayed on the display unit. The display screen of the two-dimensional code is, for example, the screen shown in FIG. 41D, and the details will be described later.

Step S412: The customer who has completed the product registration goes to the place where the settlement device 400 is arranged. 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 (the customer-side scanner unit 206 of FIG. 4 when the POS terminal 20 is applied as the settlement device 400) displays the display of the mobile terminal 500 according to the operation of the clerk or the customer. Read the two-dimensional code (basket identification information) displayed on the section.

Step S413: The settlement device 400, when reading the two-dimensional code displayed on the display unit of the mobile terminal 500, requests the cloud server 300 to calculate the subtotal amount. For example, the settlement device 400 transmits a calculation request (small calculation request information) for requesting the calculation of the subtotal amount and the basket identification information restored from the two-dimensional code to the cloud server 300 (transmission/reception data D5 in FIG. 40). ..

Step S414: When the cloud server 300 receives the basket identification information and the small calculation request information from the settlement device 400, the cloud server 300 identifies the basket information including the received basket identification information.

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

Step S416: When the subtotal amount is specified, the cloud server 300 transmits the 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).

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

Step S418: The settlement device 400 executes payment (settlement) when the subtotal amount is displayed on the display unit. Specifically, the settlement device 400 receives the selection of the payment type. Further, when the settlement is completed, the settlement device 400 issues a receipt and sends the settlement completion information to the cloud server 300 together with the basket information. Then, the cloud server 300 stores the transaction end date (settlement date) of the basket.

Further, in step S418, the customer selects the settlement method for performing the settlement processing of the product on the settlement screen. However, the payment method may be registered in the application in advance. When the payment method is registered, the settlement device 400 may not display the screen for selecting the payment method. Even when the payment method is registered, the settlement device 400 may display a screen for selecting the payment method.

When the payment method is cash, the deposit money is accepted, the change amount is calculated, and if there is change, the change is released. Further, the payment method can be payment by a gift certificate or payment by points of a point member. It is also possible to use a coupon ticket or a discount ticket. Even in this case, the settlement device 400 performs payment in the same manner as normal payment processing such as paying out change and issuing a receipt. In addition, when the clerk needs the ticket such as when collecting the gift certificate at the time of payment, the settlement device 400 calls the clerk. Specifically, the settlement device 400 may call the clerk when the payment method required by the clerk is selected. In addition, the settlement device 400 may give a notification to the service counter or a manned POS when the clerk selects a required payment method.

(Regarding an example of the transition of the screen when receiving the correction of the product of the second embodiment)
Next, an example of the screen transition when the correction of the product according to the second embodiment is received will be described with reference to FIGS. 42 and 43. FIG. 42 is an explanatory diagram showing an example of a screen transition when accepting cancellation of a product in the second embodiment.

In FIG. 42A, the customer operates the mobile terminal 500 to cause the mobile terminal 500 to read the barcode of the product, and two products of “XX tea” and “XX bread” are registered. Indicates that The screen of FIG. 42(A) is a screen displayed by the process of step 409 of FIG. 41. In the screen before registering the product (product registration initial screen: see step S404 in FIG. 41), the item of the product is displayed in blank. In addition, a guide display 4201 is displayed in FIG. The guidance display 4201 indicates that the customer can correct the registered product by long-pressing the item column of the product desired to be corrected (changed). Note that the operation of correction is not limited to long-pressing the item of the target product, and for example, the “correction button” is displayed and the target product is selected by pressing the button. It may be done.

As shown in (A) of FIG. 42, it is assumed that the area indicating “XX pan” is pressed and held. That is, it is assumed that the customer has performed an operation of correcting the product "○○ bread". In this case, the screen changes to the screen shown in FIG. FIG. 42(B) shows a confirmation screen as to whether or not to cancel “XX bread”. When the customer selects “No” on the confirmation screen, for example, the screen returns to the screen shown in FIG. 42(A), and the product registration can be accepted again. On the other hand, when the customer selects “Yes” on the confirmation screen, the screen changes to the screen shown in FIG. 42(C).

Here, the processing of the mobile terminal 500 and the cloud server 300 when the customer selects “Yes” on the confirmation screen will be described. When the customer selects “Yes” on the confirmation screen, the mobile terminal 500 transmits the information indicating the cancellation request, the product code to be canceled, and the basket identification information to the cloud server 300. Upon receiving these pieces of information from the mobile terminal 500, the cloud server 300 identifies the basket information (see (C) of FIG. 40) including the received basket identification information.

The cloud server 300 updates the product data included in the specified basket information. Specifically, when the cloud server 300 receives the product code of the N item to be canceled, the cloud server 300 refers to the registered product information of the specified basket information, and the product corresponding to the product code (registered product N). The cancellation is stored as cancellation candidate information. The cancellation candidate information is information in which a product code, a product name, and a price are associated with each other (see (C) of FIG. 40). Further, the cloud server 300 does not update the cumulative information (cumulative number of products, subtotal amount, etc.) of the registered product information because the cancellation has not been completed (because the approval by the store clerk has not been completed). However, since it is expected that cancellation will be performed after that, the cumulative information (cumulative number of items, subtotal amount, etc.) of the registered merchandise information may be updated, or both the updated value and the value not updated. May be stored. Alternatively, the cloud server 300 may display 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.

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

FIG. 42C shows a screen when the cancellation of the product is accepted. In addition, in FIG. 42C, it is displayed that the cancellation of the product has not been finalized and that the clerk needs the approval at the time of checkout. In addition, the product (XX bread) to be canceled is not hidden but is clearly marked as a product to be canceled by, for example, attaching a strike line. Thereby, the customer can easily grasp the product to be canceled. When the customer continues shopping after (C) in FIG. 42 and then presses the “payment button”, the screen changes to the screen shown in (D) in FIG. 42.

FIG. 42D shows a display screen of the two-dimensional code used in the settlement process of the product to be purchased. The process of the mobile terminal 500 when the "accounting button" is pressed is as shown in steps S410 and S411 of FIG. Note that, also in (D) of FIG. 42, as in (C), "approval required" indicating that approval of the clerk is required at the time of accounting is displayed. When the two-dimensional code shown in (D) of FIG. 42 is read by the settlement device 400, the settlement device 400 performs the settlement process.

(Regarding another screen example when correcting the product of the second embodiment)
FIG. 43 is an explanatory diagram illustrating an example of screen transitions when a change in the quantity of products is received in the second embodiment. Note that FIG. 43 differs from the screen shown in FIG. 42 in that the change in quantity is accepted.

In FIG. 43A, the customer operates the mobile terminal 500 to cause the mobile terminal 500 to read the barcode of the product, and two products of “XX tea” and “XX bread” are registered. Indicates that As shown in (A) of FIG. 43, it is assumed that the customer has long pressed the area indicating “XX bread”. In this case, the screen changes to the screen shown in FIG. 43(B). FIG. 43B shows a screen for accepting a change in quantity. In FIG. 43B, when the “+” button is pressed, the quantity is added according to the number of times the button is pressed. On the other hand, when the "-" button is pressed, the quantity is subtracted according to the number of times the button is pressed. Note that it is also possible to cancel the product by setting the quantity to "0" as in the case of FIG.

In FIG. 43B, it is assumed that the enter button 4301 is pressed after accepting a change in which the quantity increases. In this case, since it is not recognized that the increase in the quantity is a fraudulent act, the increase in the quantity is recognized as it is without requiring the approval of the clerk, and the screen returns to the registration screen of FIG.

On the other hand, it is assumed that the decision button 4301 is pressed after accepting the change of decreasing the quantity. In this case, since it is necessary for the store clerk to confirm whether or not the correction is valid, the store clerk's approval is required at the time of payment. Further, the quantity of the product registered by scanning the barcode may not be set to “0”. Specifically, as shown in FIG. 43(B), when the quantity is "1", even if the customer presses the "-" button, it may not be "0".

Even in this case, the customer may want to cancel, so the quantity may be set to “0” and the cancel operation may be performed by the clerk at the time of payment. In addition, as shown in FIG. 42 described above, whether the deletion of the product is accepted by pressing the area indicating the product or the change of the quantity is accepted as shown in FIG. 43 is changed by the clerk. It may be possible to do so. Further, when the area indicating the product is pressed, it is possible to display a selection screen as to whether to accept the deletion of the product or the change of the quantity so that the customer can select.

(About an example of the settlement screen of the second embodiment)
FIG. 44 is an explanatory diagram showing an example of the settlement screen of the second embodiment. FIG. 44A shows a payment screen displayed by the payment device 400 reading the two-dimensional code (see FIG. 44D) displayed on the mobile terminal 500. The process of reading the two-dimensional code and displaying the payment screen is as shown in steps S412 to S417 of FIG. On the settlement screen of FIG. 44A, it is displayed that the clerk is calling.

Then, when a store clerk near the settlement device 400 causes the settlement device 400 to read the store clerk code attached to his/her name tag, the store clerk is authenticated. If a store clerk near the settlement device 400 has already logged in (for example, if there is a store clerk placed in the settlement device 400), there is no need to perform authentication again.

FIG. 44B shows a confirmation screen for approval by the store clerk. The clerk visually confirms whether the correction content entered by the customer is correct (whether it is an operation error or registration error) (checks the product in the basket), and if it is determined to be correct, the confirmation screen is displayed. Click "Yes". When the clerk selects "Yes" on the confirmation screen, the cancellation of the target product is completed.

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

FIG. 44C shows a product registration update screen in which the correction (cancellation) is completed and the settlement becomes possible. As shown in (C) of FIG. 44, the total amount of money is reduced by cancellation of the product as compared with (B) of FIG. 44. Further, the product (XX bread) that is the object of cancellation is not hidden but is marked with a cancellation line, for example. As a result, the canceled product is specified. Therefore, the customer and the store clerk can easily understand that the product has been canceled.

According to the second embodiment, the customer can accept the cancellation or correction of the product while registering the product, that is, without waiting for the settlement. Therefore, it is not necessary to accept cancellations and corrections at the time of settlement, and the settlement can be speeded up. Therefore, it is possible to reduce congestion at the time of payment.

(Modification of Embodiment 2)
Next, a modified example of the second embodiment will be described. In the second embodiment described above, the configuration in which the clerk approves the correction in the settlement device 400 has been described. In the modification of the second embodiment, a configuration will be described in which, instead of or in addition to such a configuration, a store clerk goes to a place where a customer exists to approve the correction.

In a modified example, the mobile terminal 500 is assumed to be carried not only by the customer but also by a store clerk (one or more clerk) in the sales floor. The mobile terminal 500 carried by the store clerk may be owned by the store clerk or may be a loaned item from the store. The mobile terminal 500 carried by the store clerk is managed by the cloud server 300 so that the store clerk can be identified. Specifically, the cloud server 300 stores, for example, the identification information (clerk) and the address in association with each other for each mobile terminal 500 of each clerk.

In addition, the cloud server 300 also manages a sales floor in charge of the salesclerk. Specifically, the cloud server 300 stores the identification information of the store clerk and the sales floor in charge of the store clerk in association with each other, and also stores each product and the sales floor in association with each other. As a result, the cloud server 300 can identify a sales floor person in charge (a salesclerk in charge of the sales floor) based on the product. Specifically, the cloud server 300 can specify the sales floor corresponding to the product based on the product, and further can specify the store clerk corresponding to the specified sales floor.

In the modified example, as shown in FIG. 42B, it is assumed that the customer cancels the product. In this case, the customer's mobile terminal 500 transmits information regarding 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 cancellation information received from the customer's mobile terminal 500 (see (C) in FIG. 40). Further, the cloud server 300 identifies the person in charge of the sales floor from the updated products, and transmits the information indicating that the cancellation has been accepted and the product information of the cancellation target to the mobile terminal 500 of the person in charge.

Then, the store clerk goes to the customer who has performed the cancel operation, visually confirms the product or the like to be canceled, and if there is no problem, performs the approval operation using the portable terminal 500 of the store clerk. The mobile terminal 500 of the store clerk, when the approval is made, transmits information indicating the approval to the cloud server 300. When the cloud server 300 receives the information from the mobile terminal 500 of the store clerk, the cloud server 300 updates the cumulative information (cumulative number of products, subtotal amount, etc.) of the registered product information. As a result, the cancellation can be completed without waiting for the settlement.

Further, in the above description, when the mobile terminal 500 accepts the cancellation, the information indicating that the cancellation has been accepted from the cloud server 300 is transmitted to the mobile terminal 500 of the sales floor person in charge. Instead of such a configuration, or in addition to such a configuration, it is also possible to adopt a configuration in which the transmission is performed to the mobile terminal 500 of the store clerk near the customer who performed the cancel operation. However, position information is used for such a configuration.

More specifically, when the customer performs a product cancellation operation, the customer's mobile terminal 500 has information indicating a cancellation request, the product code to be canceled, and basket identification information, as well as the mobile phone concerned. The position information of the terminal 500 is also transmitted to the cloud server 300. The position information is, for example, information for specifying the position in the store. For example, the mobile terminal 500 uses the detection results of various sensors arranged in the store, the signal and radio field intensity of the wireless LAN arranged in the store, the detection results of various sensors built in the mobile terminal 500, and the like. , Location information can be obtained.

The cloud server 300 also manages the location information of the clerk. Specifically, the mobile terminal 500 of the store clerk sequentially transmits the position information of its own terminal to the cloud server 300. Upon receiving the position information of the clerk, the cloud server 300 updates the position information in association with the identification information of the clerk. When the cloud server 300 receives the cancellation information including the position information of the customer's mobile terminal 500 from the customer's mobile terminal 500, the cloud server 300 receives the information about the cancellation based on the position information and the stored clerk position information. Information indicating that the cancellation has been accepted is transmitted to the mobile terminal 500 of the nearby store clerk. As a result, a store clerk near the customer who has performed the cancel operation can be quickly sent to the customer. Even in this case, the cancellation can be completed without waiting for the settlement.

Further, in the above description, the configuration in which the store clerk uses the mobile terminal 500 of the store clerk to approve the cancellation, but it is also possible to approve the cancellation using the mobile terminal 500 of the customer. More specifically, when the cloud server 300 receives information regarding cancellation from the customer's mobile terminal 500, the cloud server 300 issues a password (information that only the clerk can know) for accepting the cancellation approval, and the issued password is used by the clerk. It is transmitted to the mobile terminal 500.

The store clerk goes to the customer who has performed the cancel operation, visually confirms the product or the like to be canceled, and if there is no problem, inputs the password from a predetermined screen on the mobile terminal 500 of the customer. The entered password is transmitted from the mobile terminal 500 of the customer to the cloud server 300, and is used to determine whether the password matches the password issued by the cloud server 300. If the cloud server 300 determines that they match, the cloud server 300 approves the cancellation. Then, the cloud server 300 updates the cumulative information of the registered merchandise information (cumulative number of products, subtotal amount, etc.) and transmits merchandise item registration update screen information including the updated cumulative information to the mobile terminal 500 of the customer. Even in this case, the cancellation can be completed without waiting for the settlement.

According to the modified example described above, it is not necessary to approve cancellation at the time of payment, and therefore payment can be performed more quickly. Therefore, it is possible to further alleviate congestion at the time of payment.

The supplementary notes are disclosed below.

(Appendix 1)
In a product sales data processing device that can be operated by a customer, change accepting means for accepting from the customer a change in product information indicating a product registered in one transaction, and a clerk regarding the change in the product information accepted by the change accepting means. Product sales data processing, comprising: an approval input means for inputting a result of approval by the user; and a product information changing means for changing the product information by inputting the approval result by the approval input means. apparatus.

Supplementary note about Appendix 1. One transaction is, for example, a transaction from the start of registration of a product by the operation of the customer to the completion of settlement. The product information is, for example, registration information. The timing at which the change receiving means receives the change in the product information from the customer is an arbitrary timing from the start of the registration of the product to the completion of the settlement, for example, before the depression of the subtotal key during the registration of the product. The timing may be the timing, or the timing after the subtotal key whose product has been registered is pressed.

The merchandise sales data processing device (POS terminal 20) calls the clerk when the change is accepted by the change accepting means. The calling of the store clerk is performed at the POS terminal 20 in which the store clerk is arranged, the mobile terminal carried by the store clerk, or the management device.

The approval input means inputs the approval result by the clerk who received the call. The mode of input by the approval input unit may be, for example, directly accepting the operation of the store clerk, or may be received from another terminal (another POS terminal 20, a mobile terminal carried by the store clerk, or a management device). .. By inputting the approval result, the product information changing unit changes the product information.

According to Supplementary Note 1, since the customer performs a part of the operation related to the change of the product information, and the clerk only needs to perform the approval operation, the operation of the clerk related to the change of the product information is simplified. be able to. In addition, it is possible to shorten the waiting time of the customer regarding the change. Therefore, the registered merchandise can be efficiently changed. In addition, since customers can request changes even if they are not verbal, for example, for customers who are concerned about further congestion due to changes or who feel embarrassed to change, The mental burden can be reduced. Thus, according to Supplementary Note 1, it is possible to suitably change the product information and improve the convenience of the product sales data processing device.

(Appendix 2)
Operation change display means for displaying the product information in different display areas for each product is further provided, and the change accepting means accepts one of the display areas displayed by the operation display means from a customer. The product sales data processing device according to appendix 1, wherein the product information change indicated by the received display area is received.

The additional note 2 is, for example, that the customer accepts the change of the product information by long-pressing the display area indicating the product desired to be changed (see (A) of FIG. 25 ). Further, Supplementary Note 2 includes a content that, among the items indicating the product name, the number, and the amount of money in the display region indicating the product, the item indicated by the long-pressed display region is accepted (FIGS. 34 to 34). 36). Thus, the customer can specify the product to be changed by simply pressing the change target displayed on the display screen. In addition, the customer can specify the product to be changed with a single operation, for example. As a result, the product information can be efficiently changed.

However, the change receiving means may display a button indicating that the change is to be performed, and by pressing the button, the customer may selectably receive the product or item desired to be changed. That is, the change of the product information may be accepted by a plurality of operations.

(Appendix 3)
The shop assistant side operation unit operable by a store clerk and the customer side operation unit operable by a customer are further provided, and the approval input means inputs the approval result according to an operation on the shop assistant side operation unit. The product sales data processing device according to appendix 1 or 2, characterized in that.

Appendix 3 has the content that, for example, in the POS terminal 20 including the clerk-side display unit 210 and the customer-side display unit 205, the clerk's approval is accepted by operating the clerk-side display unit 210. Further, for example, it is possible to accept a change from a customer by operating the customer-side display unit 205. Accordingly, when the clerk is registering the product on the clerk-side display unit 210 or when the product information is received from the customer after the product is registered, the clerk can approve the product on the spot. Therefore, it is possible to reduce the load on the clerk when approving. As a result, the product information can be efficiently changed, and the convenience of the product sales data processing device can be improved.

(Appendix 4)
Customer-side operation means operable by a customer, identification information input means for inputting identification information for identifying a clerk, and clerk identification means for identifying a clerk using the identification information input by the identification information input means. Note that the approval input means inputs the approval result by accepting an operation to the customer-side operation means when a clerk is specified by the clerk specifying means. The product sales data processing device described in any one of 1.

The customer-side operation means of Supplementary Note 4 is a display unit that receives a change in product information from a customer, and is, for example, a 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. Supplementary note 4 is specifically that when a change is received from a customer, the store clerk goes to the terminal that has received the change, and if the store clerk is successfully authenticated, the approval is received from the store clerk. Accordingly, the approval of the store clerk can be received on the screen in which the product information change is received from the customer, so that the change operation and the approval operation can be continuously performed. Therefore, it is easy for the customer and the store clerk to understand the details of the change and the change, and it is possible to prevent misidentification and erroneous operation of the change. Therefore, the product information can be efficiently changed.

(Appendix 5)
A mode setting means for setting any one of a plurality of modes is provided, and the approval input means receives an operation to the customer side operation means when a predetermined mode is set by the mode setting means. The product sales data processing device according to appendix 4, wherein the approval result is input.

Note 5 is specifically the content that when the full self mode is set, the approval of the store clerk is accepted by operating the customer-side display unit 205. As a result, in the full self mode, the customer-side display unit 205 can accept registration of product information and change of product information from the customer, and also approval of the clerk. Therefore, in the full self mode, the change operation and the approval operation can be continuously performed on the customer side display unit 205. Therefore, the product information can be efficiently changed.

(Appendix 6)
Any one of appendices 1 to 5 characterized in that the change accepting means accepts a change in the quantity of the product indicated by the product information to a predetermined quantity when the product information is registered in a predetermined registration mode. The product sales data processing device described in one.

The predetermined registration mode in Supplementary Note 6 is, for example, a registration mode by reading a barcode. The predetermined quantity is, for example, a quantity excluding "0". Appendix 6 is, specifically, the content that, when the product information is registered by reading the barcode, the change of the product quantity to a quantity excluding “0” is accepted. In other words, when the product information is registered by reading the barcode, the change in the quantity of the product is set to "0" is not accepted.

This is because, for a product with a bar code, it is clear that the product actually exists due to the reading of the bar code, and therefore it is not assumed that the quantity will be changed to “0”. For this reason, it is highly probable that a change to "0" in the quantity is an erroneous operation, so it is not accepted. According to Supplementary Note 6, it is possible to prevent an erroneous operation associated with a quantity change, and it is possible to efficiently change the product information.

(Appendix 7)
A product sales data processing system comprising: a registration device for registering product information indicating a product; and a payment device for performing payment, wherein the payment device is one of the product information registered by the registration device in one transaction. Receiving a change from a customer, the registration device changes the product information by inputting an approval result by a clerk about the change of the product information received by the settlement device, and inputting the approval result. A featured product sales data processing system.

The registration device in Appendix 7 is, for example, the POS terminal 20 in the normal mode arranged on the upstream side, and registers the product information by the operation of the store clerk. The registration device only needs to have a function of registering product information, in other words, it does not have to have a function of registering product information by a customer operation or a function of performing settlement by a customer operation. Good. In addition, the settlement device of Supplementary Note 7 is, for example, a POS terminal 20 in a semi-self mode arranged on the downstream side, and the settlement is performed by a customer's operation. In addition, the settlement device may have a function of performing settlement by a customer's operation, in other words, may not have a function of registering product information. Further, a plurality of settlement devices may be installed corresponding to one registration device.

When receiving the change of the product information from the customer, the settlement device requests the registration device to approve the change. Note that the settlement device may only make a request for approval of the change to the registration device, and may not send the content of the change. Upon receiving the approval request from the settlement device, the registration device receives the approval by the store clerk for the change in the product information. The registration device may receive only the approval request from the settlement device and display only the approval button for accepting the approval, for example. In this case, the clerk can press the approval button by visually confirming the changes made by the customer at the settlement device.

According to Supplementary Note 7, the customer performs a part of the operation related to the change of the product information in the settlement device, and the clerk only needs to perform the approval operation in the registration device. Therefore, the clerk related to the change of the product information. The operation of can be simplified. Further, it is possible to shorten the waiting time of the customer who performs the change operation in the settlement device. Therefore, the registered merchandise can be efficiently changed. Thus, according to Supplementary Note 7, it is possible to suitably change the product information and improve the convenience of the product sales data processing system.

(Appendix 8)
The settlement device transmits change information indicating a change in the product information received from a customer to the registration device, and the registration device receives the change information from the settlement device to input the approval result. The product sales data processing system according to appendix 7, characterized in that.

Appendix 8 is, specifically, when the settlement device accepts the change of the product information from the customer, the change information (including the content of the change and the approval request) is transmitted to the registration device, and the registration device sends the change information from the settlement device. The content is that the reception of the clerk's approval is received. Thereby, the clerk can grasp the content of the change in the settlement device. Therefore, when the store clerk is registering the product in the registration device or when a change in the product information is received from the customer after the product is registered, the store clerk can approve the change on the spot. As a result, it is possible to reduce the load on the clerk when approving. Therefore, the product information can be changed efficiently, and the convenience of the product sales data processing system can be improved.

(Appendix 9)
The registration device and the settlement device both set any one of a plurality of modes, the settlement device, when setting a predetermined mode, transmits the change information to the registration device, the The commodity sales according to appendix 8, wherein the registration device inputs the approval result by receiving the change information from the settlement device when a mode different from the predetermined mode is set. Data processing system.

Appendix 9 is, specifically, when the settlement device (the POS terminal 20 on the downstream side) sets the full self mode, the change information is transmitted to the registration device, and the registration device (the POS terminal 20 on the upstream side) transmits the change information. The contents are that the change information is received from the settlement device when the normal mode is set. The product information can be changed according to the mode set in each POS terminal 20 in the POS system 1. Therefore, it is possible to efficiently change the product information in the full self mode.

(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 change receiving unit receiving a change of product information indicating a product registered in one transaction from the customer, and the change receiving unit. It is characterized by functioning as an approval input unit for inputting an approval result by a clerk about the change of the product information, and a product information changing unit for changing the product information by the approval result input by the approval input unit. Program to do.

The program for realizing the POS system 1 and the POS terminal 20 described above may be recorded in a computer-readable recording medium and the computer system may read the program and execute the program. The “computer system” mentioned here includes an OS and hardware such as peripheral devices. Further, the “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system. Further, the "computer-readable recording medium" is a volatile memory (RAM) inside a computer system that serves as a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those that hold the program for a certain period of time are also included. Further, the program may be transmitted from a computer system that stores the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having 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. Further, the program may be for realizing a part of the functions described above. Further, it may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

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 settlement section 209... Change machine 210... Salesclerk side display section 211... Key operation section 212... Salesclerk side scanner section 213... Printing section 214... Voice output section 215... Communication unit

Claims (10)

In the product sales data processing device that can be operated by customers,
Change accepting means for accepting from a customer a change in product information indicating a product registered in one transaction,
Approval input means for inputting an approval result by a clerk about the change of the product information accepted by the change accepting means,
Product information changing means for changing the product information by inputting the approval result by the approval input means,
A product sales data processing device comprising: Further comprising operation display means for displaying the product information in different display areas for each product,
The change accepting unit accepts a change in the product information indicated by the accepted display region by accepting any one of the display regions displayed by the operation display unit from the customer.
The product sales data processing device according to claim 1, wherein A clerk-side operation unit that can be operated by a clerk,
A customer-side operation unit that can be operated by the customer,
Further equipped with,
The approval input means inputs the approval result according to an operation on the operation section on the clerk side,
The product sales data processing device according to claim 1 or 2, characterized in that. Customer-side operation means that can be operated by the customer,
Identification information input means for inputting identification information for identifying a clerk,
A clerk specifying means for specifying a clerk using the identification information input by the identification information inputting means,
Equipped with
The approval input means inputs the approval result by accepting an operation to the customer side operation means when a clerk is specified by the clerk specifying means.
The product sales data processing device according to any one of claims 1 to 3, characterized in that. A mode setting means for setting any one of a plurality of modes is provided,
The approval input means inputs the approval result by accepting an operation to the customer side operation means when a predetermined mode is set by the mode setting means,
The product sales data processing device according to claim 4, characterized in that. The change accepting unit accepts a change in the quantity of the product indicated by the product information to a predetermined quantity when the product information is registered in a predetermined registration mode,
The product sales data processing device according to any one of claims 1 to 5, characterized in that. A product sales data processing system comprising: a registration device for registering product information indicating a product; and a payment device for payment.
The settlement device is
Accepting from the customer a change in the product information registered by the registration device in one transaction,
The registration device is
Enter the approval result by the clerk about the change of the product information accepted by the settlement device,
By changing the product information by inputting the approval result,
A product sales data processing system characterized in that The settlement device transmits change information indicating a change in the product information received from a customer to the registration device,
The registration device inputs the approval result by receiving the change information from the settlement device.
The product sales data processing system according to claim 7, wherein. Each of the registration device and the settlement device sets one of a plurality of modes,
The settlement device transmits the change information to the registration device when a predetermined mode is set,
The registration device inputs the approval result by receiving the change information from the settlement device when a mode different from the predetermined mode is set.
The product sales data processing system according to claim 8, wherein. A program that causes a computer to function as a product sales data processing device that can be operated by a customer,
Change accepting means for accepting from a customer a change in product information indicating a product registered in one transaction,
Approval input means for inputting the approval result by the clerk about the change of the product information accepted by the change accepting means,
Product information changing means for changing the product information by inputting the approval result by the approval input means,
A program characterized by making it function as.

Images