Payment device and program

Abstract

To operate more suitably.SOLUTION: A POS system includes a registration device at which a store clerk registers articles and a plurality of payment devices at which a customer himself / herself makes a payment. The POS system is provided with customer monitoring means for monitoring a behavior of a customer at the payment devices, and notification means capable of notifying the store clerk of the specific behavior of the customer monitored by the customer monitoring means when the customer behavior is a specific behavior requiring notification to the store clerk. The specified behavior includes a first specified behavior having a higher priority for notification and a second specified behavior having a lower priority for notification than the first specified behavior. The notification means notifies the store clerk who registers the articles of the first specified behavior, while not notifying the store clerk who registers the articles of the second specified behavior.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention provides Payment device and program Regarding. [Background technology]

[0002] 2. Description of the Related Art A POS system including a POS register used by a store clerk and a POS settlement machine used by a customer is known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-190067 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when customers themselves operate the payment machine, there are operational problems and there is room for improvement.

[0005] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a technology that can be more suitably operated. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a POS system that includes a registration device where a store clerk registers products and multiple checkout devices where customers themselves settle their payments, and is equipped with a customer monitoring means that monitors customer behavior at the checkout devices, and a notification means that can notify the store clerk of the specific behavior if the customer behavior monitored by the customer monitoring means is a specific behavior that requires notification to the store clerk, wherein the specific behavior includes a first specific behavior that has a high notification priority and a second specific behavior that has a lower notification priority than the first specific behavior, and the notification means notifies the store clerk who registers the products of the first specific behavior but does not notify the store clerk who registers the products of the second specific behavior. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is an example of a network configuration of a POS system according to a first embodiment. [Figure 2] 1A and 1B are diagrams illustrating examples of the appearance of a registration device and a settlement device according to a first embodiment. [Figure 3] FIG. 2 illustrates an example of the configuration of a registration device according to the first embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a settlement device according to the first embodiment. [Figure 5] FIG. 2 is an explanatory diagram illustrating the installation of an imaging unit. [Figure 6] 3 is a display example of the transaction status management device in the first embodiment. [Figure 7] 10 is a display example of a registration device in the first embodiment. [Figure 8] 10 is a display example of a registration device in the first embodiment. [Figure 9] 10 is a display example of a registration device in the first embodiment. [Figure 10] 10 is a display example of a settlement-related notification area in the first embodiment. [Figure 11] 10 is a display example of a settlement device in the first embodiment. [Figure 12] 5 is a flowchart showing an example of the operation of the registration device in the first embodiment. [Figure 13] 5 is a flowchart showing an example of the operation of the registration device in the first embodiment. [Figure 14] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 15] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 16] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 17] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 18] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 19] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 20] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 21] This is an example of information referenced in the currency monitoring process. [Figure 22] 4 is a flowchart showing an example of the operation of the settlement device in the first embodiment. [Figure 23] 10 is a display example of a settlement-related notification area in the second embodiment. [Figure 24] 10 is a flowchart showing an example of the operation of the settlement device in the second embodiment. [Figure 25] 10 is a flowchart showing an example of the operation of the settlement device in the second embodiment. [Figure 26] 11 is a flowchart showing an example of the operation of the settlement device in the third embodiment. [Figure 27] 11 is a flowchart showing an example of the operation of the settlement device in the third embodiment. [Figure 28] 11 is a flowchart showing an example of the operation of the settlement device in the third embodiment. [Figure 29] 11 is a flowchart showing an example of the operation of the settlement device in the third embodiment. [Figure 30]11 is a flowchart showing an example of the operation of the settlement device in the third embodiment. [Figure 31] 11 is a flowchart showing an example of the operation of the settlement device in the third embodiment. [Figure 32] 10 is a flowchart showing an example of the operation of the settlement device in the fourth embodiment. [Figure 33] 10 is a flowchart showing an example of the operation of the settlement device in the fourth embodiment. [Figure 34] 13 is a display example of a registration device in the fifth embodiment. [Figure 35] 13 is a display example of a registration device in the fifth embodiment. [Figure 36] 10 is a flowchart showing an example of the operation of the settlement device in the fifth embodiment. [Figure 37] 10 is a flowchart showing an example of the operation of the settlement device in the fifth embodiment. [Figure 38] 10 is a flowchart showing an example of the operation of the settlement device in the fifth embodiment. [Figure 39] 10 is a flowchart showing an example of the operation of the settlement device in the fifth embodiment. [Figure 40] 10 is a flowchart showing an example of the operation of the settlement device in the fifth embodiment. [Figure 41] 10 is a flowchart showing an example of the operation of the settlement device in the fifth embodiment. [Figure 42] 13 is a flowchart showing an example of the operation of the settlement device in the sixth embodiment. [Figure 43] 13 is a flowchart showing an example of the operation of the settlement device in the sixth embodiment. [Figure 44] FIG. 1 is an explanatory diagram summarizing the first to sixth embodiments. [Figure 45] FIG. 10 is an explanatory diagram illustrating a modified example regarding input. [Figure 46] FIG. 10 is an explanatory diagram illustrating a modified example regarding input. DETAILED DESCRIPTION OF THE INVENTION

[0008] (First embodiment) A first embodiment of the present invention will be described below with reference to the drawings. FIG. 1 shows an example of the network configuration of a POS system 1 according to the first embodiment (the same applies to other embodiments). The POS system 1 shown in FIG. 1 includes a plurality of registration devices 10a, 10b, etc., a plurality of settlement devices 20a, 20b, etc., a store controller 30, and a transaction status management device 40, all of which are communicatively connected via a LAN 11. Hereinafter, when there is no need to distinguish between the individual registration devices 10a, 10b, etc., they will simply be referred to as registration devices 10, and when there is no need to distinguish between the individual settlement devices 20a, 20b, etc., they will simply be referred to as settlement devices 20.

[0009] The registration device 10 is operated by a store clerk and is a device for performing a registration process for purchased items. For example, the registration device 10 executes the registration process, generates registration data (registration information) including the processing content of the registration process (product registration information related to the purchased items of the customer), and transmits the generated registration data to the settlement device 20 designated by the store clerk. The registration device 10 may transmit the registration data to the settlement device 20 via another device (e.g., the store controller 30, etc.), or may transmit the registration data directly to the settlement device 20 without going through another device.

[0010] The settlement device 20 is a device that is mainly operated by customers and that processes the settlement of purchased items. For example, the settlement device 20 receives registration data transmitted from the registration device 10 and executes the settlement process based on the registration data.

[0011] The store controller 30 receives product files from an external device (for example, a server at headquarters) and transmits (distributes) the files to other devices (such as the registration device 10 and the payment device 20). The store controller 30 also receives information from other devices and transmits it to the outside.

[0012] The transaction status management device 40 is operated by a store clerk and monitors (displays on a display, etc.) the status of other devices (registration device 10, settlement device 20, etc.) and customer behavior (actions). For example, the transaction status management device 40 manages the current usage status of the settlement device 20 (in use, idle), the number of coins stored in the settlement device 20 (near end, near full), the remaining amount of receipt paper in the settlement device 20, and the behavior of customers using the settlement device 20. The transaction status management device 40 may be, for example, a personal computer. The transaction status management device 40 may be equipped with a scanner unit and be able to register products, similar to the registration device 10.

[0013] Fig. 2 is a diagram showing an example of the appearance of the registration device 10 and the settlement device 20 of the first embodiment (the same applies to other embodiments). Fig. 3 is a diagram showing an example of the configuration of the registration device 10 of the first embodiment (the same applies to other embodiments). Fig. 4 is a diagram showing an example of the configuration of the settlement device 20 of the first embodiment (the same applies to other embodiments).

[0014] An example of the configuration of the registration device 10 shown in Fig. 3 will be described below with reference to Fig. 2. In Fig. 2 and Fig. 3, the same parts are denoted by the same reference numerals.

[0015] 3, the registration device 10 includes a CPU 101, a ROM 102, a RAM 103, a scanner unit 104, a display unit for store clerks 105, a display unit for customers 106, a hard disk 107, a key operation unit 108, a communication unit 109, an audio output unit 110, a printing unit 111, and a bus 115. These are connected to each other via the bus 115.

[0016] ROM 102 stores various information. For example, ROM 102 stores a product registration program for causing CPU 101 to execute registration processing. RAM 103 temporarily stores various information. For example, RAM 103 temporarily stores information read from ROM 102 or hard disk 107, and information generated by executing the product registration program.

[0017] The scanner unit 104 is a scanner that optically reads barcodes. The scanner unit 104 optically reads barcodes attached to products, acquires product codes from the read barcodes, and stores the acquired product codes in the RAM 103.

[0018] The CPU 101 controls the entire registration device 10. For example, the CPU 101 controls the execution of the registration process by executing a product registration program. As an example, the CPU 101 displays the product names and prices of the purchased products on the display units (the store clerk display unit 105 and the customer display unit 106) based on the product codes read by the scanner unit 104 and the product files stored on the hard disk 107. The CPU 101 also generates registration data including the product codes of all registered products. The CPU 101 controls the communication unit 109 to transmit the generated registration data to the settlement device 20. In addition to transmitting the generated registration data to the settlement device 20, the CPU 101 may store the generated registration data in the RAM 103 or the hard disk 107.

[0019] The clerk display unit 105 is, for example, a liquid crystal touch display device. The clerk display unit 105 displays various information (such as a registration screen) to the clerk. The clerk display unit 105 also displays various buttons (various keys) to be operated by the clerk. For example, the clerk display unit 105 may display product preset buttons corresponding to individual products, a subtotal button for instructing the end of product registration, a settlement device designation button for designating (selecting) the destination of registered data, and a declaration button for accepting various declarations (declarations related to the next operation, the current transaction, or subsequent control).

[0020] The customer display unit 106 is, for example, a liquid crystal touch display device. The customer display unit 106 displays various information (such as the price of each product) to customers. The customer display unit 106 also displays various buttons that customers can operate. For example, the customer display unit 106 can display an OK button for age verification.

[0021] The hard disk 107 stores various types of information, such as information acquired from the outside (such as product files) and information generated by a product registration program.

[0022] Various buttons (such as numeric buttons for inputting figures such as the amount) operated by the store clerk are arranged on key operation unit 108. Note that instead of or in addition to displaying on store clerk display unit 105, the various buttons described as being displayed on store clerk display unit 105 (for example, the above-mentioned subtotal button, declaration button, etc.) may be arranged on key operation unit 108.

[0023] The communication unit 109 is a communication interface for communicating with external devices (other registration devices 10, settlement device 20, store controller 30, transaction status management device 40) via the LAN 11.

[0024] The audio output unit 110 outputs audio. For example, the audio output unit 210 outputs a confirmation sound, a warning sound, audio guidance, etc. The printing unit 111 prints and issues various media.

[0025] The registration device 10 may further include an imaging unit (camera), a timekeeping unit (clock), a card payment unit (card reading unit), and the like.

[0026] Next, an example of the configuration of the settlement device 20 shown in Fig. 4 will be described with reference to Fig. 2. In Fig. 2 and Fig. 4, the same parts are denoted by the same reference numerals.

[0027] 4, the settlement device 20 includes a CPU 201, a ROM 202, a RAM 203, a scanner unit 204, a display unit 206, a hard disk 207, a communication unit 209, an audio output unit 210, a printing unit 211, a change dispenser (automatic change dispenser) 212, a sign pole 213, an imaging unit 214, and a bus 215. These are connected to each other via the bus 215.

[0028] The ROM 202 stores various types of information. For example, the ROM 202 stores an accounting program for causing the CPU 201 to execute a settlement process. The RAM 203 temporarily stores various types of information. For example, the RAM 203 temporarily stores information read from the ROM 202 or the hard disk 207, and information generated by executing the accounting program. The scanner unit 204 is a scanner that optically reads barcodes and the like.

[0029] The CPU 201 controls the entire settlement device 20. For example, the CPU 201 controls the execution of the settlement process by executing a checkout program. As an example, the CPU 201 displays the total amount on the display unit 206 based on the registration data transmitted from the registration device 10. The CPU 201 also acquires information regarding the amount of coins inserted into the change dispenser 212 from the change dispenser 212 and displays the amount of change (deposit) on the display unit 206. The CPU 201 also calculates the amount of change based on the total amount and the amount of deposit, and displays the amount of change on the display unit 206. When the settlement process is completed, the CPU 201 also causes the printing unit 211 to issue a receipt and causes the change dispenser 212 to eject coins in an amount equal to the change amount. When the settlement process is completed, the CPU 201 also generates settlement data (settlement information) including the total amount and the like, and controls the communication unit 209 to transmit the data to an external device (e.g., the store controller 30). The CPU 201 may store the generated settlement data in the RAM 203 or the hard disk 207 in addition to transmitting the data to an external device.

[0030] The display unit 206 is, for example, a liquid crystal touch display device. The display unit 206 displays various information to the customer (operation information, total amount, deposit amount, change amount, etc.). The display unit 206 also accepts various operations from the customer (operation to select a payment method, operation to confirm the deposit amount and execute the settlement, etc.).

[0031] The hard disk 207 stores various types of information, such as information acquired from the outside (such as registration data) and information generated by an accounting program.

[0032] The communication unit 209 is a communication interface for communicating with external devices (such as the registration device 10, other settlement devices 20, the store controller 30, and the transaction status management device 40) via the LAN 11.

[0033] The audio output unit 210 outputs audio. For example, the audio output unit 210 outputs a confirmation sound, a warning sound, audio guidance, and the like.

[0034] The printing unit 211 prints and issues various media, and is provided with a sensor for determining whether or not an issued medium has been removed from the issuing port.

[0035] The change dispenser 212 is an automatic change dispenser (cash settlement unit) that controls the deposit and withdrawal of coins (money) into a storage unit (not shown) in which coins (money) are stored. A sensor is provided to determine whether the change dispensed to the dispensing outlet has been removed. In the examples shown in FIGS. 3 and 4, the change dispenser 212 is built into the settlement device 20, but the change dispenser 212 may also be connected to the settlement device 20.

[0036] The sign pole 213 has indicator lights of multiple colors, and each display mode (off, on, flashing, etc.) notifies the store staff and customers of the status of the self-checkout device 20 (a store staff member is being called, change is nearing end, etc.) and whether the self-checkout device 20 is a specific checkout device 20 (for example, a checkout device 20 designated by a store staff member).

[0037] The imaging unit (camera) 214 (not shown in FIG. 2) captures images of the display unit 206 (display screen) of the self-payment apparatus 20 and the customer using the self-payment apparatus 20.

[0038] The captured images (still images, moving images) captured by the imaging unit 214 are stored (saved) so that they can be viewed (played back) as needed. For example, the settlement device 20 may store the captured images within the settlement device 20 (e.g., hard disk 207) so that the captured images can be viewed on another device (registration device 10, transaction status management device 40). When viewing is required, the other device may play back the captured image data as it receives it partially (gradually) from the settlement device 20, or may play back the captured image data after receiving it all (collectively) from the settlement device 20.

[0039] The storage location (saving location) of the captured image is not limited to the settlement device 20 that generated the captured image. For example, the captured image may be stored in a predetermined settlement device 20 (representative settlement device 20), the registration device 10, the transaction status management device 40, or a cloud server (one server or a collection of multiple servers) not shown. Furthermore, the location where the captured image is played back is not limited to the registration device 10 or the transaction status management device 40. For example, the captured image may be played back in a settlement device 20 (the settlement device 20 that generated the captured image to be played back, or a settlement device 20 different from the settlement device 20 that generated the captured image to be played back), or a management device at headquarters not shown.

[0040] The settlement device 20 further includes a timekeeping unit (clock). The settlement device 20 may further include a card settlement unit (card reading unit) and the like.

[0041] Fig. 5 is an explanatory diagram for explaining the installation of the imaging unit 214. Fig. 5(A) is an explanatory diagram for schematically explaining an installation example of the imaging unit 214 and the imaging range in this installation example. Fig. 5(A) shows an installation example in which the imaging unit 214 is installed above the display unit 206 so that the customer's face is captured near the center of the captured image. In Fig. 5(A), the line a indicates the center direction (optical axis direction) of the image captured by the imaging unit 214, and the line b indicates the imaging range (image capture range by the imaging unit). The same applies to Fig. 5(B).

[0042] Fig. 5(B) is an explanatory diagram that schematically explains another installation example of the imaging unit 214 and the imaging range in this other installation example. Fig. 5(B) is an installation example in which the imaging unit 214 is installed above the display unit 206 so that an image is captured below (closer to the viewer) than in Fig. 5(A).

[0043] (Customer Behavior) Next, the behavior (action) of a customer while using the settlement device 20 will be described. The settlement device 20 monitors the behavior of a customer using the settlement device 20 using the imaging unit 214. In the first embodiment (the same applies to other embodiments), the settlement device 20 recognizes (determines) whether the behavior of a customer using the settlement device 20 is an "exiting behavior," an "operation preparation behavior," or an "operation uncertainty behavior," based on the image captured by the imaging unit 214. The settlement device 20 notifies other devices (the transaction status management device 40, the registration device 10) of the recognition (monitoring) results.

[0044] (Withdrawal behavior) A leaving behavior is an action of leaving the settlement device 20. The settlement device 20 determines that a leaving behavior has occurred when a state before determination that a leaving behavior can be determined based on the captured image (a state before determination of a leaving behavior) continues for a predetermined time or more. In other words, the settlement device 20 determines that a leaving behavior has occurred when a customer leaves the settlement device 20 and does not return immediately.

[0045] The determination of whether or not the state is a pre-leaving behavior determination state varies depending on how the imaging unit 214 is installed. For example, if the imaging unit 214 is installed as shown in FIG. 5(A), the settlement device 20 may determine that the state is a pre-leaving behavior determination state when it is unable to recognize a customer (customer object, the same applies hereinafter) in the captured image, or when the customer recognized in the captured image is smaller than a predetermined size. Also, if the imaging unit 214 is installed as shown in FIG. 5(B), the settlement device 20 may determine that the state is a pre-leaving behavior determination state when it is unable to recognize the upper half of the customer in the captured image.

[0046] (Operation preparation actions) The operation preparatory actions are preparatory actions related to the operation of the settlement device 20. Examples of operation preparatory actions include an action of searching for and taking out a wallet, card case, smartphone, etc. from a bag or the like, an action of searching for and taking out coins, cards (credit cards, prepaid cards, point cards, etc.), coupons (including those printed on past receipts), etc. from a wallet, an action of searching for and taking out a card or coupon from a card case, an action of operating a smartphone to launch a payment app, an action of checking the change and putting it in the wallet, an action of putting the card back into the wallet or card case, an action of checking the app screen or closing the app after payment, etc.

[0047] The settlement device 20 determines that an operation preparatory action has occurred when a state before determination that the action can be determined to be an operation preparatory action based on the captured image (a state before determination of an operation preparatory action) continues for a predetermined time or more. In other words, the settlement device 20 determines that an operation preparatory action has occurred when the customer is taking time to prepare something in front of the settlement device 20.

[0048] The determination of whether or not the state is a pre-operation preparatory behavior determination state varies depending on how the imaging unit 214 is installed. For example, if the imaging unit 214 is installed as shown in FIG. 5(A), the settlement device 20 may determine that the state is a pre-operation preparatory behavior determination state when the customer recognized in the captured image is equal to or larger than a predetermined size but the customer's face cannot be recognized (i.e., the customer is looking down and not at the screen). Also, if the imaging unit 214 is installed as shown in FIG. 5(B), the settlement device 20 may determine that the state is a pre-operation preparatory behavior determination state when the customer recognized in the captured image is equal to or larger than a predetermined size but the customer's face cannot be recognized, or the customer's head (top of the head) can be recognized.

[0049] (Operational confusion) The operation uncertainty behavior is a behavior in which the customer is unsure about how to operate the settlement device 20. The settlement device 20 determines that the behavior is an operation uncertainty behavior when a state before the judgment that can be determined as an operation uncertainty behavior based on the captured image (a state before the judgment of the operation uncertainty behavior) continues for a predetermined time or more. In other words, the settlement device 20 determines that the behavior is an operation uncertainty behavior when the customer is simply taking time in front of the settlement device 20 without making any preparations.

[0050] The determination of whether or not the state is a pre-determination state of hesitant operation behavior differs depending on how the imaging unit 214 is installed. For example, when the imaging unit 214 is installed as shown in Fig. 5(A) (the same applies when the imaging unit 214 is installed as shown in Fig. 5(B)), the settlement device 20 may determine that the state is a pre-determination state of hesitant operation behavior when the customer recognized in the captured image is equal to or larger than a predetermined size and the customer's face can be recognized (i.e., when the customer is looking at the screen).

[0051] (Example of display on the transaction status management device 40) 6 is a display example of the transaction status management device 40 in the first embodiment (the same applies to other embodiments). Specifically, FIG. 6 is an example of a settlement monitoring screen displayed by the transaction status management device 40.

[0052] 6, the settlement-related notification area HR20 at the bottom left of the screen is a display area for notifying information related to settlement (the settlement device 20 and the customer using the settlement device 20). The settlement-related notification area HR20 has a settlement-related notification area HR20-1 for the 201 register (settlement device 20a), a settlement-related notification area HR20-2 for the 202 register (settlement device 20b), a settlement-related notification area HR20-3 for the 202 register (settlement device 20c), and a settlement-related notification area HR20-4 for the 204 register (settlement device 20d; not shown in FIG. 1).

[0053] The "vacant status" at the top of the settlement-related notification area HR20-1 indicates that the usage status of the settlement device 20 (register 201) is vacant.

[0054] The transaction status management device 40 controls the display of the usage status in the settlement-related notification area HR20-1 based on the monitoring result information sent by the 201 cash register. Specifically, the transaction status management device 40 switches the display of the usage status from "unused" to "in use" based on the monitoring result information (in use), and switches the display of the usage status from "in use" to "unused" based on the monitoring result information (unused). The monitoring result information (in use) and the monitoring result information (not in use) will be described later. The same applies to the display of the usage status in the other settlement-related notification areas (such as the settlement-related notification area HR20-2).

[0055] The receipt button BT61 at the bottom left of the settlement-related notification area HR20-1 indicates that the remaining amount of receipt paper in the settlement device 20 (register 201) is low (a state in which receipt paper needs to be replenished). The receipt button BT61 is one of the notification buttons (a notification button that notifies that receipt paper is low). When the receipt button BT61 is operated, detailed notification information (remaining receipt amount, etc.) regarding the state in which receipt paper needs to be replenished is displayed.

[0056] The transaction status management device 40 controls the display of the receipt button BT61 in the settlement-related notification area HR20-1 based on the monitoring result information sent by the 201 cash register. Specifically, the transaction status management device 40 switches the display of the receipt button BT61 from a hidden state to a displayed state based on the monitoring result information (receipt), and switches the display of the receipt button BT61 from a displayed state to a hidden state based on the monitoring result information (non-receipt). The monitoring result information (receipt) and monitoring result information (non-receipt) will be described later. The same applies to the display of the receipt button BT61 in other settlement-related notification areas (such as the settlement-related notification area HR20-2).

[0057] The near-full button BT63 at the bottom left of the settlement-related notification area HR20-1 indicates that there is an excess of any coin in the settlement device 20 (201 register) (meaning that the storage capacity is about to be reached, i.e., the device is in a near-full state). The near-full button BT63 is one of the notification buttons (a notification button that notifies that any coin is in a near-full state). When the near-full button BT63 is operated, detailed notification information regarding the near-full state (information on the coin in question, number of coins, etc.) is displayed.

[0058] The transaction status management device 40 controls the display of the near-full button BT63 in the settlement-related notification area HR20-1 based on the monitoring result information sent by the 201 cash register. Specifically, the transaction status management device 40 switches the display of the near-full button BT63 from a hidden state to a displayed state based on the monitoring result information (near-full state), and switches the display of the near-full button BT63 from a displayed state to a hidden state based on the monitoring result information (non-near-full state). The monitoring result information (near-full state) and the monitoring result information (non-near-full state) will be described later. The same applies to the display of the near-full button BT63 in other settlement-related notification areas (such as the settlement-related notification area HR20-2).

[0059] The near-end button BT62 at the bottom left of the settlement-related notification area HR20-2 indicates that the settlement device 20 (202 register) is running low on one of the coins (indicating that it is about to run out of change, i.e., that it is in a near-end state). The near-end button BT62 is one of the notification buttons (notification buttons that notify that one of the coins is in a near-end state). When the near-end button BT62 is operated, detailed notification information regarding the near-end state (information on the coin in question, number of coins, etc.) is displayed.

[0060] The transaction status management device 40 controls the display of the near-end button BT62 in the settlement-related notification area HR20-2 based on the monitoring result information sent by the 202 cash register. Specifically, the transaction status management device 40 switches the display of the near-end button BT62 from a hidden state to a displayed state based on the monitoring result information (near-end state), and switches the display of the near-end button BT62 from a displayed state to a hidden state based on the monitoring result information (non-near-end state). The monitoring result information (near-end state) and monitoring result information (non-near-end state) will be described later. The same applies to the display of the near-end button BT62 in other settlement-related notification areas (such as the settlement-related notification area HR20-1).

[0061] The Withdraw button BT73 on the left side of the settlement-related notification area HR20-2 indicates that the behavior (action) of a customer using the settlement device 20 (202 register) is a withdrawal behavior. The Withdraw button BT73 is one of the notification buttons (notification buttons that notify that the customer's behavior is a withdrawal behavior). When the Withdraw button BT73 is operated, detailed notification information regarding the withdrawal behavior (information indicating at which processing stage the withdrawal behavior occurred, etc.) is displayed. As shown in FIG. 6, the transaction status management device 40 displays the Withdraw button BT73 in a manner that makes it more noticeable than the Operation Hesitation button BT71 and the Operation Preparation button BT72.

[0062] The transaction status management device 40 controls the display of the Leave button BT73 in the settlement-related notification area HR20-2 based on the monitoring result information sent by the 202 cash register. Specifically, the transaction status management device 40 switches the display of the Leave button BT73 from a hidden state to a displayed state based on the monitoring result information (leaving behavior), and switches the display of the Leave button BT73 from a displayed state to a hidden state based on the monitoring result information (non-leaving behavior). The monitoring result information (leaving behavior) and monitoring result information (non-leaving behavior) will be described later. The same applies to the display of the Leave button BT73 in other settlement-related notification areas (such as the settlement-related notification area HR20-1).

[0063] The image button BT78 on the right side of the settlement-related notification area HR20-2 is a button for displaying (playing) images (still images, moving images) of customers, etc. using the settlement device 20 (202 register). When the image button BT78 is operated, still images are displayed in the still image display areas 1 to 3 on the right side of the settlement monitoring screen, and moving images are displayed in the moving image display area.

[0064] In the example of Figure 6, when the image button BT78 in the settlement-related notification area HR20-2 is operated, the settlement device 20 displays an image captured by the register 202 (in the example of Figure 6, an image for the store clerk to identify the customer who has left; for example, an image of the customer's face or figure) in the still image display area or video display area. The same applies when an image button related to leaving behavior (still image button BT46 or video button BT47 in Figure 10) is operated in the registration device 10.

[0065] In the example of Figure 6, when the image button BT78 in the settlement-related notification area HR20-3 is operated, the settlement device 20 displays an image of the screen of the 203 cash register (in the example of Figure 6, an image for the store clerk to understand the details of the customer's uncertain operation behavior; in other words, a captured image of the screen of the settlement device 20 where progress has stopped) in the still image display area. Note that the settlement device 20 may also display a captured image of the 203 cash register (in the example of Figure 6, an image for the store clerk to check the state of the customer who is uncertain about how to operate the cash register; for example, an image of the customer's face or figure) in the still image display area or video display area.

[0066] In the example of Figure 6, when the image button BT78 in the settlement-related notification area HR20-4 is operated, the settlement device 20 displays an image of the 204 cash register (in the example of Figure 6, an image for the store clerk to check the state of the customer preparing to leave, for example, an image of the customer's face and figure) in the still image display area or video display area. The settlement device 20 may also display an image of the 204 cash register screen (in the example of Figure 6, a captured image of the settlement device 20 screen for the store clerk to check what screen state the store clerk is in preparing to operate) in the still image display area.

[0067] When the image button BT78 is operated, the transaction status management device 40 requests an image from the settlement device 20 and displays the image in the still image display area or video image display area. When an image is requested by the transaction status management device 40 (the same applies when an image is requested by the registration device 10), the settlement device 20 transmits the requested image to the transaction status management device 40, but if the request is made while image capture is in progress, the image capture is continued while the image is being transmitted to the transaction status management device 40 (that is, even if a request is made while image capture is in progress, the image capture is not interrupted). In more detail, the settlement device 20, for example, stores (records) the video being captured while the video is being captured in a memory unit (RAM 203, hard disk 207, etc.), and when the transaction status management device 40 (registration device 10) requests the current video, it transmits a through video (live footage) to the transaction status management device 40 (registration device 10) while maintaining the storage of the video being captured in the memory unit, and when the transaction status management device 40 (registration device 10) requests a past video, it transmits the past video (for example, a video stored in the memory unit (video of the requested part)) to the transaction status management device 40 (registration device 10) while maintaining the storage of the video being captured in the memory unit.

[0068] The transaction status management device 40 displays the image button BT78 when the usage status is in use. That is, the transaction status management device 40 switches the display of the image button BT78 from a hidden state to a displayed state based on the monitoring result information (in use status), and switches the display of the image button BT78 from a displayed state to a hidden state based on the monitoring result information (unused status). The monitoring result information (in use status) and the monitoring result information (not in use status) will be described later. The same applies to the display of the image button BT78 in other settlement-related notification areas (such as the settlement-related notification area HR20-1).

[0069] 6, the image button BT78 in the settlement-related notification area HR20-2 is indicated by a thick frame, and the image button BT78 in the settlement-related notification area HR20-3 and the image button BT78 in the settlement-related notification area HR20-4 are indicated by a thin frame, with the thick frame indicating that the image button BT78 in question has been operated (selected).Thus, although not shown in the figure, still images of customers using register 202 are displayed in still image display areas 1 to 3 on the right side of the settlement monitoring screen, and still images of customers using register 202 are displayed in the video display area.

[0070] The operation hesitation button BT71 on the left side of the settlement-related notification area HR20-3 indicates that the behavior (action) of a customer using the settlement device 20 (203 register) is operation hesitation. The operation hesitation button BT71 is one of the notification buttons (an notification button that notifies that the customer's behavior is operation hesitation). When the operation hesitation button BT71 is operated, detailed notification information regarding the operation hesitation (such as information indicating at which processing stage the operation hesitation occurs) is displayed.

[0071] The transaction status management device 40 controls the display of the operation hesitation button BT71 in the settlement-related notification area HR20-3 based on the monitoring result information transmitted by the 203 cash register. Specifically, the transaction status management device 40 switches the display of the operation hesitation button BT71 from a hidden state to a displayed state based on the monitoring result information (operation hesitation behavior), and switches the display of the operation hesitation button BT71 from a displayed state to a hidden state based on the monitoring result information (non-operation hesitation behavior). The monitoring result information (operation hesitation behavior) and the monitoring result information (non-operation hesitation behavior) will be described later. The same applies to the display of the operation hesitation button BT71 in other settlement-related notification areas (such as the settlement-related notification area HR20-1).

[0072] The operation preparation button BT72 on the left side of the settlement-related notification area HR20-4 indicates that the behavior (action) of a customer using the settlement device 20 (204 register) is an operation preparation action. The exit button BT73 is one of the notification buttons (an notification button that notifies that the customer's behavior is an operation preparation action). When the operation preparation button BT72 is operated, detailed notification information regarding the operation preparation action (such as information indicating at which processing stage the operation preparation action is) is displayed.

[0073] The transaction status management device 40 controls the display of the operation preparation button BT72 in the settlement-related notification area HR20-4 based on the monitoring result information transmitted by the 204 cash register. Specifically, the transaction status management device 40 switches the display of the operation preparation button BT72 from a hidden state to a displayed state based on the monitoring result information (operation preparation action), and switches the display of the operation preparation button BT72 from a displayed state to a hidden state based on the monitoring result information (non-operation preparation action). The monitoring result information (operation preparation action) and monitoring result information (non-operation preparation action) will be described later. The same applies to the display of the operation preparation button BT72 in other settlement-related notification areas (such as the settlement-related notification area HR20-1).

[0074] (Display example of registration device 10) 7 to 9 are display examples of the registration device 10 in the first embodiment. Specifically, FIGS. 7 to 9 are display examples on the clerk display unit 105 of the registration device 10. Note that FIGS. 7 to 9 are display examples of a certain registration device 10 (for example, registration device 10a), and the registration data (registration information) generated in the registration device 10 is basically processed (settlement processing) in one of the two settlement devices 20 (settlement device 20a (register 201) and settlement device 20b (register 202)).

[0075] FIG. 7 shows the display contents of the registration screen in a scene before the registration of one product item. In FIG. 7, the subtotal button BT10 at the bottom right of the screen is a button for instructing the end of the registration process (end of registration of all purchased products in the transaction). The subtotal button BT10 becomes valid after products are registered, so operation of the subtotal button BT10 is invalid in the scene of FIG. 7 before the registration of one product item. Therefore, in the scene of FIG. 7, the subtotal button BT10 is displayed in a display mode indicating that operation is invalid (indicated by a dashed frame in FIG. 7). Note that in the example of FIG. 7, to explicitly indicate that operation of the subtotal button BT10 is invalid, the subtotal button BT10 is displayed in a display mode indicating that operation is invalid, but the subtotal button BT10 does not have to be displayed in the scene of FIG. 7.

[0076] 7, the settlement-related notification area HR10 in the lower left of the screen is a display area for notifying information related to settlement (the settlement device 20 and the customer using the settlement device 20). The settlement-related notification area HR10 has a settlement-related notification area HR10-1 related to the 201 cash register (settlement device 20a) and a settlement-related notification area HR10-2 related to the 202 cash register (settlement device 20b).

[0077] The "empty" symbol in the lower left corner of the settlement-related notification area HR10-1 indicates that the settlement device 20 (register 201) is in an empty state. The "in use" symbol in the lower left corner of the settlement-related notification area HR10-2 indicates that the settlement device 20 (register 202) is in use.

[0078] FIG. 8 shows the display contents of the registration screen in a scene following the scene in FIG. 7. Specifically, FIG. 8 shows the display contents of the registration screen after the product has been registered. In the scene in FIG. 8 after the product has been registered, operation of the subtotal button BT10 is valid. Therefore, in the scene in FIG. 8, the subtotal button BT10 is displayed in a display mode indicating that the operation is valid (shown by a solid line frame in FIG. 8). In this embodiment, when the subtotal button BT10 is operated, the subtotal screen is displayed instead of the registration screen.

[0079] Although FIG. 8 illustrates the scene after the second product (asparagus) has been registered, operation of the subtotal button BT10 is valid after the first product (canned beer) has been registered.

[0080] Figure 9 shows the display content of the subtotal screen in a scene following the scene in Figure 8. Specifically, Figure 9 shows the display content of the subtotal screen after the subtotal button BT10 is operated. In other words, when the subtotal button BT10 is operated in the scene in Figure 8, the registration device 10 displays the subtotal screen of Figure 9 on the clerk display unit 105 instead of the registration screen of Figure 8.

[0081] In Figure 9, the 201 register button BT21 and 202 register button BT22 at the bottom of the screen are buttons for specifying (selecting) the settlement device 20 that will execute the settlement process for the product registration in the transaction. In other words, they are settlement device specification buttons for specifying (selecting) the destination to which the registration data of the transaction will be sent. The 201 register button BT21 is a button for specifying the 201 register (settlement device 20a). The 202 register button BT22 is a button for specifying the 202 register (settlement device 20b). When the 201 register button BT21 is operated, the registration device 10 sends the registration data of the transaction to the 201 register (settlement device 20a), and when the 202 register button BT22 is operated, the registration data of the transaction to the 202 register (settlement device 20b).

[0082] The receipt button BT24 is a button for issuing a receipt (registered trademark) in the printing unit 111. When the receipt button BT24 is operated, the registration device 10 prints and issues a receipt. Information necessary for the settlement process in the payment device 20 is coded and printed on the receipt. The issued receipt is handed over to the customer by a store clerk. The customer then moves to the payment device 20, and the payment process is carried out in the payment device 20 based on the code on the receipt read by the payment device 20 (scanner unit 204).

[0083] The gift certificate button BT25 is a button for settling the account using a gift certificate (also called a gift voucher or cash voucher) (a button that accepts a declaration that the gift certificate will be used for settling the account).

[0084] The registration screen button BT26 is a button for returning the screen from the sub-screen to the registration screen. When the registration screen button BT26 is operated, the registration device 10 returns the screen from the sub-screen to the registration screen. The registration screen button BT26 is used, for example, when changing (adding, canceling) a purchased item.

[0085] Fig. 10 shows an example of the display in the settlement-related notification area HR10 in the first embodiment. Specifically, each of Fig. 10(A) to Fig. 10(E) is an example of the display in the settlement-related notification area HR10-2.

[0086] Fig. 10(A) is a display example of basic notification information related to a settlement (payment device 20, customer using payment device 20). As described above, "In Use" shown in Fig. 10(A) indicates that the usage status of cash register 202 is in use.

[0087] The registration device 10 controls the display of the usage status in the settlement-related notification area HR10-2 (basic notification information, detailed notification information) based on the monitoring result information transmitted by the 202 cash register. Specifically, the registration device 10 switches the display of the usage status from "unused" to "in use" based on the monitoring result information (in use), and switches the display of the usage status from "in use" to "unused" based on the monitoring result information (unused). The same applies to the display of the usage status in the settlement-related notification area HR10-1 (basic notification information, detailed notification information). The monitoring result information (in use) and the monitoring result information (not in use) will be described later.

[0088] The exit button BT43 shown in Figure 10(A) indicates that the behavior (action) of a customer using the payment device 20 (202 register) is an exit behavior. The exit button BT43 is one of the notification buttons (an notification button that notifies that the behavior of the customer is an exit behavior). When the exit button BT43 is operated, detailed notification information regarding the exit behavior (such as information indicating at which processing stage the exit behavior occurred) is displayed.

[0089] The registration device 10 controls the display of the Leave button BT43 in the settlement-related notification area HR10-2 (basic notification information) based on the monitoring result information transmitted by the 202 register. Specifically, the transaction status management device 40 switches the display of the Leave button BT43 from a hidden state to a displayed state based on the monitoring result information (leaving behavior), and switches the display of the Leave button BT43 from a displayed state to a hidden state based on the monitoring result information (non-leaving behavior). The same applies to the display of the Leave button BT43 in the settlement-related notification area HR10-1 (basic notification information). The monitoring result information (leaving behavior) and monitoring result information (non-leaving behavior) will be described later.

[0090] The near-end button BT32 shown in Fig. 10(A) indicates that one of the coins in the settlement device 20 (202 register) is running low (indicating that the device is in a near-end state). The near-end button BT32 is one of the notification buttons (notification buttons that notify that one of the coins is in a near-end state). When the near-end button BT32 is operated, detailed notification information regarding the near-end state (information on the coin, number of coins, etc.) is displayed.

[0091] The registration device 10 controls the display of the near-end button BT32 in the settlement-related notification area HR10-2 (basic notification information) based on the monitoring result information transmitted by the 202 cash register. Specifically, the registration device 10 switches the display of the near-end button BT32 from a hidden state to a displayed state based on the monitoring result information (near-end state), and switches the display of the near-end button BT32 from a displayed state to a hidden state based on the monitoring result information (non-near-end state). The same applies to the display of the near-end button BT32 in the settlement-related notification area HR10-1 (basic notification information). The monitoring result information (near-end state) and the monitoring result information (non-near-end state) will be described later.

[0092] FIG. 10(B) is a display example of detailed notification information related to payment (specifically, detailed notification information related to withdrawal behavior). When a store clerk operates the withdrawal button BT43, the registration device 10 displays detailed notification information (detailed notification information related to withdrawal behavior) as shown in FIG. 10(B). In FIG. 10(B), the phrase "withdrawal behavior (before selection of payment method)" indicates that the withdrawal behavior occurred before the selection of a payment method (the timing of the behavior monitoring process in step S33 of FIG. 14). In FIG. 10(B), the still image button BT46 is a button for displaying (playing) a still image related to the withdrawal behavior. The video button BT47 is a button for displaying (playing) a video related to the withdrawal behavior. For example, when a store clerk operates the still image button BT46 (video button BT47), the registration device 10 requests an image from the payment device 20, displays a small screen (not shown), and plays the still image (video) on the small screen.

[0093] Fig. 10(C) is a display example of detailed notification information related to settlement (specifically, detailed notification information related to the near-end state). When a store clerk operates the near-end button BT32, the registration device 10 displays detailed notification information (detailed notification information related to the near-end state) as shown in Fig. 10(C). In Fig. 10(C), the words "10 yen coins: 8 remaining" indicate that there are 8 10 yen coins remaining.

[0094] 10(D) to 10(E) are display examples (display examples of other scenes) different from those in FIG. 10(A) to FIG. 10(C).

[0095] The receipt button BT31 shown in Figure 10(D) indicates that the remaining amount of receipt paper in the settlement device 20 (201 register) is low (a state in which receipt paper needs to be replenished). The receipt button BT31 is one of the notification buttons (a notification button that notifies that receipt paper is low). When the receipt button BT31 is operated, detailed notification information (such as the remaining amount of receipts) regarding the state in which receipt paper needs to be replenished is displayed.

[0096] The registration device 10 controls the display of the receipt button BT31 in the settlement-related notification area HR10-2 (basic notification information) based on the monitoring result information sent by the 202 cash register. Specifically, the registration device 10 switches the display of the receipt button BT31 from a hidden state to a displayed state based on the monitoring result information (receipt), and switches the display of the receipt button BT31 from a displayed state to a hidden state based on the monitoring result information (non-receipt). The same applies to the display of the receipt button BT31 in the settlement-related notification area HR10-1 (basic notification information). The monitoring result information (receipt) and monitoring result information (non-receipt) will be described later.

[0097] The near-full button BT33 shown in Fig. 10(D) indicates that there is an excess of any coin in the settlement device 20 (202 register) (that the device is in a near-full state). The near-full button BT33 is one of the notification buttons (a notification button that notifies that any coin is in a near-full state). When the near-full button BT33 is operated, detailed notification information regarding the near-full state (information on the relevant coin, number, etc.) is displayed.

[0098] The registration device 10 controls the display of the near-full button BT33 in the settlement-related notification area HR10-2 (basic notification information) based on the monitoring result information transmitted by the 202 cash register. Specifically, the registration device 10 switches the display of the near-full button BT33 from a hidden state to a displayed state based on the monitoring result information (near-full state), and switches the display of the near-full button BT33 from a displayed state to a hidden state based on the monitoring result information (non-near-full state). The same applies to the display of the near-full button BT33 in the settlement-related notification area HR10-1 (basic notification information). The monitoring result information (near-full state) and the monitoring result information (non-near-full state) will be described later.

[0099] FIG. 10(D) is a display example of detailed notification information related to payment (specifically, detailed notification information related to the receipt needing replenishment status). When a store clerk operates the receipt button BT31, the registration device 10 displays detailed notification information (detailed notification information related to the receipt needing replenishment status) as shown in FIG. 10(D). In FIG. 10(D), the words "Remaining receipts: approximately 1 meter" indicate that the remaining quantity of receipt paper is approximately 1 meter.

[0100] Fig. 10(E) is a display example of detailed notification information related to payment (specifically, detailed notification information related to the near-full state). When a store clerk operates the near-full button BT33, the registration device 10 displays detailed notification information (detailed notification information related to the near-full state) as shown in Fig. 10(E). In Fig. 10(E), the words "1000 yen bills: 8 remaining (192 bills)" indicate, for example, that 192 1000 yen bills, which can hold up to 200, are currently stored and only 8 more will be stored.

[0101] (Example of display on settlement device 20) Figure 11 shows an example of a display on the settlement device 20 in the first embodiment (the same applies to other embodiments). Figure 11(A) shows a standby screen. For example, when the settlement device 20 is available (or when the available state continues for a predetermined time or more), it displays the standby screen as shown in Figure 10(A).

[0102] FIG. 11(B) is the payment method selection screen. For example, when the settlement device 20 receives registration data (the same applies when a bill is read), it displays the payment method selection screen as shown in FIG. 11(B). In FIG. 11(B), the cash button BT51, credit button BT52, and electronic money button BT53 are all payment type buttons. The cash button BT51 is a button for selecting (specifying) cash as the payment method (payment method, payment type). The credit button BT52 is a button for selecting a credit card as the payment method. The electronic money button BT53 is a button for selecting electronic money as the payment method.

[0103] 11(C) is a deposit screen (a deposit screen when the deposited amount does not reach the payment amount). For example, when the cash button BT51 is operated on the payment method selection screen, the settlement device 20 displays the deposit screen as shown in FIG. 11(C).

[0104] Fig. 11(D) is a deposit screen (deposit screen when the deposit amount has reached the payment amount). For example, when cash equal to or greater than the purchase amount has been deposited, that is, when the deposit amount has reached the payment amount for the purchased items, the settlement device 20 displays the deposit screen as shown in Fig. 11(D). In Fig. 11(D), the END (RECEIPT) button BT54 is a button for confirming the deposit.

[0105] Fig. 11(E) is the change screen. For example, when the END (receipt) button BT54 is operated on the deposit screen (Fig. 11(D)), the settlement device 20 displays the change screen as shown in Fig. 11(E).

[0106] Figure 11(F) is a receipt screen. For example, when change is removed from the outlet of the change dispenser 212, the settlement device 20 displays a receipt screen such as that shown in Figure 11(F). If no change is due, the settlement device 20 transitions from the deposit screen (Figure 11(D)) to the receipt screen (Figure 11(F)) without displaying the change screen.

[0107] Next, the flow of processing by the registration device 10 will be described with reference to Fig. 12 and Fig. 13. Fig. 12 and Fig. 13 are flowcharts showing an example of the operation of the registration device 10 in the first embodiment (the same applies to other embodiments).

[0108] (Explanation of the flowchart in Figure 12) The flowchart in Fig. 12 shows the flow of a basic transaction (from registering one item of merchandise to transmitting registration data) of the registration device 10. At the start of the flowchart in Fig. 12, it is assumed that the registration device 10 is displaying a screen such as that shown in Fig. 7.

[0109] Step S10: The registration device 10 executes a settlement-related notification process. The settlement-related notification process is a process for notifying information related to the settlement (the settlement device 20, the customer using the settlement device 20). Details of the settlement-related notification process will be described later (FIG. 13). Next, the process proceeds to step S11.

[0110] Step S11: The registration device 10 determines whether or not a scan or the like has been made of the product (one item of product). If a scan or the like has been made (Step S11: YES), the process proceeds to Step S12. If a scan or the like has not been made (Step S11: NO), the process returns to Step S10.

[0111] Step S12: The registration device 10 registers the product (the product scanned in step S10), and then the process proceeds to step S13.

[0112] Step S13: The registration device 10 executes a settlement-related notification process. As described above, the settlement-related notification process is a process for notifying information related to the settlement (the settlement device 20, the customer using the settlement device 20). Details of the settlement-related notification process will be described later (FIG. 13). Next, proceed to step S14.

[0113] Step S14: The registration device 10 determines whether or not a scan or the like has been performed on the product (each product for which Step S3 is executed from the second item onward). If a scan or the like has been performed (Step S14: YES), the process proceeds to Step S15. If a scan has not been performed (Step S14: NO), the process proceeds to Step S16.

[0114] Step S15: The registration device 10 registers the product (the product scanned in step S3), and then the process proceeds to step S16.

[0115] Step S16: The registration device 10 determines whether the subtotal button BT10 has been operated. If it has been operated (Step S16: YES), the display is switched to the subtotal screen (see FIG. 9) and the process proceeds to Step S17. If it has not been operated (Step S16: NO), the process returns to Step S13.

[0116] Step S17: The registration device 10 executes the settlement-related notification process. As described above, the settlement-related notification process is a process for notifying information related to the settlement (the settlement device 20, the customer using the settlement device 20). Details of the settlement-related notification process will be described later (FIG. 13). Next, proceed to step S18.

[0117] Step S18: The registration device 10 determines whether or not an operation to designate a settlement device 20 (operation of the settlement device designation button) has been performed. If an operation has been performed (step S18: YES), the process proceeds to step S9. If no operation has been performed (step S18: NO), the process returns to step S17.

[0118] Step S19: The registration device 10 transmits the registration data to the settlement device 20 (the settlement device 20 designated in step S18). Then, the flowchart in FIG. 12 ends.

[0119] (Explanation of the flowchart in Figure 13) The flowchart in FIG. 13 shows details of the settlement-related notification process (steps S10, S13, S17) in the flowchart in FIG.

[0120] As described above, the registration device 10 executes the settlement-related notification process in steps S10, S13, and S17 of the flowchart in Fig. 12. That is, before the registration of the first product, the registration device 10 simultaneously executes the registration waiting process for the first product (step S11) and the settlement-related notification process (step S10) in parallel; after the registration of the first product and before the operation of the subtotal button BT10, the registration waiting process for each product from the second product onwards (step S14), the process waiting for the operation of the subtotal button BT10 (step S16), and the settlement-related notification process (step S13) in parallel; and after the operation of the subtotal button BT10 and before the operation of the device specification button, the process waiting for the operation of the device specification button (step S18) and the settlement-related notification process (step S17) in parallel. That is, the registration device 10 concurrently processes (multitasks) the series of processes from registering the product to transmitting the registration data, and the settlement-related notification process. The settlement-related notification process will be described below with reference to the flowchart of FIG.

[0121] Step S100: The registration device 10 determines whether or not the monitoring result information transmitted by the settlement device 20 has been received (either directly from the settlement device 20 or via another device). If the information has been received (step S100: YES), the process proceeds to step S101. If the information has not been received (step S100: NO), the process proceeds to step S105.

[0122] Step S101: Based on the monitoring result information received in step S100, the registration device 10 sets (stores) the display content of the basic notification information (see FIG. 10) to be displayed in the settlement-related notification area HR10, and the display content of the detailed notification information (see FIG. 10) to be displayed in the settlement-related notification area HR10. That is, based on the content of the monitoring result information received in step S100, the registration device 10 sets, as the basic notification information, the display content of the usage status (in use, available) and whether or not to display various notification buttons, and sets, as the detailed notification information, the wording to be displayed (such as "Before selecting payment method" or "8 10-yen coins remaining"). Next, the process proceeds to step S102.

[0123] Step S102: The registration device 10 determines whether or not basic notification information is being displayed. That is, the registration device 10 determines whether or not the information currently being displayed in the settlement-related notification area HR10 is basic notification information. If basic notification information is being displayed (Step S102: YES), proceed to Step S103. If basic notification information is not being displayed, that is, if detailed notification information is being displayed (Step S102: NO), proceed to Step S104.

[0124] Step S103: The registration device 10 controls the display of the basic notification information based on the settings stored in step S101, and then the process proceeds to step S105.

[0125] Step S104: The registration device 10 controls the display of the detailed notification information based on the settings stored in step S101, and then the process proceeds to step S105.

[0126] Step S105: The registration device 10 determines whether the basic notification information is being displayed, as in step S102. If the basic notification information is being displayed (step S105: YES), the process proceeds to step S106. If the basic notification information is not being displayed, that is, if the detailed notification information is being displayed (step S105: NO), the process proceeds to step S108.

[0127] Step S106: The registration device 10 determines whether or not a notification button has been operated. That is, the registration device 10 determines whether or not a notification button arranged in the currently displayed basic notification information (for example, the near-end button BT32 or the withdrawal button BT43 in the example of FIG. 10(A)) has been operated. If an operation has been performed (step S106: YES), the process proceeds to step S107. If no operation has been performed (step S106: NO), the flowchart in FIG. 13 (payment-related notification process) ends.

[0128] Step S107: The registration device 10 switches the display of the settlement-related notification area HR10 from basic notification information to detailed notification information based on the setting stored in step S101, and then the flowchart of Fig. 13 (settlement-related notification process) ends.

[0129] Step S108: The registration device 10 determines whether or not the back button BT45 has been operated. That is, the registration device 10 determines whether or not the back button BT45 (see FIG. 10) arranged in the currently displayed detailed notification information has been operated. If there has been an operation (step S108: YES), the process proceeds to step S109. If there has not been an operation (step S108: NO), the flowchart in FIG. 13 (payment-related notification process) ends.

[0130] Step S109: The registration device 10 switches the display of the settlement-related notification area HR10 from detailed notification information to basic notification information based on the setting stored in step S101, and then the flowchart of Fig. 13 (settlement-related notification process) ends.

[0131] Next, the processing flow of the settlement device 20 will be described with reference to Fig. 14 to Fig. 22. Fig. 14 to Fig. 20 and Fig. 22 are flowcharts showing an example of the operation of the settlement device 20 in the first embodiment. Fig. 21 shows an example of information referenced in the currency monitoring process (step S49).

[0132] (Explanation of the flowcharts in FIGS. 14 and 15) The flowcharts in Figures 14 and 15 show the flow of a basic transaction (receiving registration data - settling with cash - sending settlement data) of the settlement device 20. The flowchart in Figure 15 is a continuation of the flowchart in Figure 14. At the start of the flowchart in Figure 14, the settlement device 20 is assumed to be displaying a screen such as that shown in Figure 11(A).

[0133] Step S30 in Figure 14: The settlement device 20 determines whether or not registration data has been received. If it has been received (Step S30: YES), the display switches to the payment method selection screen (see Figure 11(B)) and proceeds to Step S31. If it has not been received (Step S30: NO), the process returns to Step S30.

[0134] Step S31: The settlement device 20 executes a usage status monitoring process. The usage status monitoring process is a process for monitoring the current usage status (in use, unused) of the settlement device 20. Details of the usage status monitoring process of step S30 will be described later (FIG. 16(A)). Next, proceed to step S32.

[0135] Step S32: The settlement device 20 executes initialization processing. The initialization processing is processing for initializing information used in behavior monitoring processing (described later). Details of the initialization processing will be described later (FIG. 16(B)). Next, the process proceeds to step S33.

[0136] Step S33: The settlement device 20 executes a behavior monitoring process. The behavior monitoring process is a process for monitoring the behavior (movement) of a customer who is using the settlement device 20. Details of the behavior monitoring process will be described later (FIGS. 17 to 19). Next, the process proceeds to step S34.

[0137] Step S34: The settlement device 20 determines whether or not a payment type button (cash button BT51, credit button BT52, electronic money button BT53) has been operated. If an operation has been performed (step S34: YES), the display switches to the deposit screen (see FIG. 11(C)) and proceeds to step S35. If no operation has been performed (step S34: NO), the process returns to step S33.

[0138] Step S35: The settlement device 20 executes the initialization process. As described above, the initialization process is a process for initializing information used in the behavior monitoring process (described later). Details of the initialization process will be described later (FIG. 16(B)). Next, the process proceeds to step S36.

[0139] Step S36: The settlement device 20 executes the behavior monitoring process. As described above, the behavior monitoring process is a process for monitoring the behavior (movement) of a customer while using the settlement device 20. Details of the behavior monitoring process will be described later (FIGS. 17 to 19). Next, the process proceeds to step S37.

[0140] Step S37: The settlement device 20 determines whether or not money has been inserted. If money has been inserted (Step S37: YES), the process proceeds to Step S38. That is, the settlement device 20 determines whether or not the insertion of cash as a deposit has been accepted. If money has not been inserted (Step S37: NO), the process returns to Step S36.

[0141] Step S38: The settlement device 20 records the money inserted in step S37 as a deposit. The settlement device 20 also displays the deposit on the deposit screen. Then, the process proceeds to step S39.

[0142] Step S39: The settlement device 20 executes the initialization process. As described above, the initialization process is a process for initializing information used in the behavior monitoring process (described later). Details of the initialization process will be described later (FIG. 16(B)). Next, the process proceeds to step S40.

[0143] Step S40: The settlement device 20 determines whether the deposit amount is equal to or greater than the payment amount. If it is equal to or greater than the payment amount (Step S40: YES), the display switches to the deposit screen (see FIG. 11(D)) and proceeds to Step S41 in FIG. 15. If it is not equal to or greater than the payment amount (Step S40: NO), the process returns to Step S36.

[0144] Step S41 in Figure 15: The settlement device 20 executes the behavior monitoring process. As described above, the behavior monitoring process is a process for monitoring the behavior (movement) of a customer who is using the settlement device 20. Details of the behavior monitoring process will be described later (Figures 17 to 19). Next, the process proceeds to step S42.

[0145] Step S42: The settlement device 20 determines whether the end button (end (receipt) button BT54) has been operated. If it has been operated (Step S42: YES), the display switches to the change screen (see FIG. 11(E)) and proceeds to Step S46. If it has not been operated (Step S42: NO), proceeds to Step S43.

[0146] Step S43: The settlement device 20 determines whether or not money has been inserted. If money has been inserted (Step S43: YES), the process proceeds to Step S44. If money has not been inserted (Step S43: NO), the process returns to Step S41.

[0147] Step S44: The settlement device 20 records the money inserted in step S43 as a deposit. The settlement device 20 also displays the deposit on the deposit screen. Then, the process proceeds to step S45.

[0148] Step S45: The settlement device 20 executes the initialization process. As described above, the initialization process is a process for initializing information used in the behavior monitoring process (described later). Details of the initialization process will be described later (FIG. 16(B)). Then, the process returns to step S41.

[0149] Step S46: The settlement device 20 executes the initialization process. As described above, the initialization process is a process for initializing information used in the behavior monitoring process (described later). Details of the initialization process will be described later (FIG. 16(B)). Next, the process proceeds to step S47.

[0150] Step S47: The settlement device 20 determines whether change is required. That is, the settlement device 20 determines whether the deposit amount (deposit amount) exceeds the payment amount (total amount). If change is required (Step S47: YES), the display switches to the change screen (see FIG. 11(E)) and proceeds to Step S48. If change is not required (Step S47: NO), the display switches to the receipt screen (see FIG. 11(F)) and proceeds to Step S53.

[0151] Step S48: The settlement device 20 dispenses, as change, money in an amount equal to the difference (change amount) between the deposited amount and the payment amount from the dispensing opening. Then, the process proceeds to step S49.

[0152] Step S49: The settlement device 20 executes a money monitoring process. The money monitoring process is a process for monitoring the number of coins stored in the change dispenser 212. Details of the money monitoring process will be described later (FIG. 20). Next, the process proceeds to step S50.

[0153] Step S50: The settlement device 20 executes the behavior monitoring process. As described above, the behavior monitoring process is a process for monitoring the behavior (movement) of a customer while using the settlement device 20. Details of the behavior monitoring process will be described later (FIGS. 17 to 19). Next, the process proceeds to step S51.

[0154] Step S51: The settlement device 20 determines whether the change paid out in step S48 has been removed. If it has been removed (step S51: YES), the display switches to the receipt screen (see FIG. 11(F)) and proceeds to step S52. If it has not been removed (step S51: NO), the process returns to step S50.

[0155] Step S52: The settlement device 20 executes the initialization process. As described above, the initialization process is a process for initializing information used in the behavior monitoring process (described later). Details of the initialization process will be described later (FIG. 16(B)). Next, the process proceeds to step S53.

[0156] Step S53: The settlement device 20 prints a receipt and issues it from the issuing port. Then, the process proceeds to step S54.

[0157] Step S54: The settlement device 20 executes receipt paper monitoring processing. The receipt paper monitoring processing is processing for monitoring the remaining amount of receipt paper printed by the printing unit 211. Details of the receipt paper monitoring processing will be described later (FIG. 22). Next, proceed to step S55.

[0158] Step S55: The settlement device 20 executes the behavior monitoring process. As described above, the behavior monitoring process is a process for monitoring the behavior (movement) of a customer while using the settlement device 20. Details of the behavior monitoring process will be described later (FIGS. 17 to 19). Next, the process proceeds to step S56.

[0159] Step S56: The settlement device 20 determines whether the receipt issued in step S53 has been removed. If it has been removed (step S56: YES), the display switches to the standby screen (see FIG. 11(A)) and proceeds to step S57. If it has not been removed (step S56: NO), the settlement device 20 returns to step S55.

[0160] Step S57: The settlement device 20 executes a usage status monitoring process. The usage status monitoring process is a process for monitoring the current usage status (in use, unused) of the settlement device 20. Details of the usage status monitoring process of step S57 will be described later (FIG. 16(C)). Next, proceed to step S58.

[0161] Step S58: The settlement device 20 executes the initialization process. As described above, the initialization process is a process for initializing information used in the behavior monitoring process (described later). Details of the initialization process will be described later (FIG. 16(B)). Next, the process proceeds to step S59.

[0162] Step S59: The settlement device 20 transmits the settlement data to the store controller 30. Then, the flowcharts of FIGS. 14 and 15 end.

[0163] (Explanation of the flowchart in Figure 16(A)) The flowchart in FIG. 16(A) shows details of the usage status monitoring process (step S31 in the flowchart in FIG. 14).

[0164] Step S200 in FIG. 16(A): The settlement device 20 transmits monitoring result information (in use status) to the transaction status management device 40. The monitoring result information (in use status) is monitoring result information indicating that the usage status of the settlement device 20 is in use. For example, the monitoring result information (in use status) includes the device identification number of the settlement device 20 and information indicating that the usage status is in use. The settlement device 20 may transmit the monitoring result information (in use status) directly to the transaction status management device 40, or may transmit it to the transaction status management device 40 via another device (e.g., the store controller 30). The same applies when transmitting other types of monitoring result information to the transaction status management device 40. The same applies to other embodiments. Next, proceed to step S201.

[0165] The transaction status management device 40 displays "in use" in the settlement-related notification area HR20 based on the monitoring result information (in use state).

[0166] Step S201: The settlement device 20 transmits the monitoring result information (in use status) to the registration device 10. The settlement device 20 may transmit the monitoring result information (in use status) directly to the registration device 10, or may transmit it to the registration device 10 via another device (e.g., the store controller 30, the transaction status management device 40). The same applies when transmitting other types of monitoring result information to the registration device 10. The same applies to other embodiments. Then, this flowchart ends.

[0167] The registration device 10 displays "in use" in the settlement-related notification area HR10 based on the monitoring result information (in use state).

[0168] (Explanation of the flowchart in Figure 16(B)) The flowchart in FIG. 16(B) shows details of the initialization process (steps S32, S35, and S39 in the flowchart in FIG. 14, and steps S45, S46, S52, and S58 in the flowchart in FIG. 15).

[0169] As described above, the settlement device 20 performs initialization processing in steps S32, S35, and S39 of the flowchart in Fig. 14, and in steps S45, S46, S52, and S58 of the flowchart in Fig. 15. In other words, the settlement device 20 performs initialization processing at the start and end of a transaction, as well as when a customer operates the settlement device 20 (operates on the screen) or takes an action (deposits coins, removes change, or removes a receipt).

[0170] The initialization process is a process for initializing information used in the behavior monitoring process (described later) (specifically, various time-keeping timers used to determine whether or not to control notification buttons (such as the exit button BT73 related to customer behavior) from a hidden state to a displayed state in other devices (the registration device 10, the transaction status management device 40)), and is a process for controlling notification buttons (such as the exit button BT73 related to customer behavior) that have been set to a displayed state in other devices (the registration device 10, the transaction status management device 40) based on the control of the behavior monitoring process (described later) to a hidden state. The initialization process will be explained below using the flowchart in Figure 16(B).

[0171] Step S220 in FIG. 16(B): The settlement device 20 initializes the time (measured value) for the duration of the pre-leaving behavior determination state (a state before a determination that can be determined to be a leaving behavior) (time before leaving behavior determination). For example, the settlement device 20 measures the time before leaving behavior determination using a timer (a timer for measuring the time before leaving behavior determination), but in the processing of step S220, the time (time) of the timer is reset. The timer is simply reset and does not start timing. Next, proceed to step S221.

[0172] Step S221: The settlement device 20 initializes the time value (measured value) of the time (time before operation preparatory action determination) during which the pre-operation preparatory action determination state (a state before determination that can be determined to be an operation preparatory action) continues. For example, the settlement device 20 measures the time before operation preparatory action determination using a timer (a timer for measuring the time before operation preparatory action determination), and in the processing of step S221, the time value (time) of the timer is reset. The timer is simply reset and does not start timing. Next, proceed to step S222.

[0173] Step S222: The settlement device 20 initializes the time (measured value) for the duration of the state before hesitant operation behavior determination (a state before determination that can be determined to be hesitant operation behavior) (time before hesitant operation behavior determination). For example, the settlement device 20 measures the time before hesitant operation behavior determination using a timer (a timer for measuring the time before hesitant operation behavior determination), and in the processing of step S222, the time (time) of the timer is reset. The timer is simply reset and does not start timing. Next, proceed to step S223.

[0174] Step S223: The settlement device 20 transmits the monitoring result information (non-withdrawal behavior) to the transaction status management device 40. The monitoring result information (non-withdrawal behavior) is monitoring result information indicating that the behavior of the customer using the settlement device 20 does not constitute withdrawal behavior. The monitoring result information (non-withdrawal behavior) includes the device identification number of the settlement device 20 and information indicating that the behavior of the customer using the settlement device 20 does not constitute withdrawal behavior. Next, proceed to step S224.

[0175] In addition, based on the monitoring result information (withdrawal behavior), the transaction status management device 40 switches the display setting of the withdrawal button BT73 in the settlement-related notification area HR20 from a hidden state to a displayed state, and based on the monitoring result information (non-withdrawal behavior), switches the display setting of the withdrawal button BT73 in the settlement-related notification area HR20 from a displayed state to a hidden state.

[0176] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-exit behavior) when the display setting of the exit button BT73 in the transaction status management device 40 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation preparation behavior) to the transaction status management device 40 when the display setting of the exit button BT73 in the transaction status management device 40 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-exit behavior) to the transaction status management device 40 after transmitting the monitoring result information (exit behavior) but before transmitting the monitoring result information (non-exit behavior) (including the case where both the monitoring result information (exit behavior) and the monitoring result information (non-exit behavior) have been transmitted, but the last one transmitted was the monitoring result information (exit behavior)).

[0177] Step S224: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10. Then, the process proceeds to step S225.

[0178] In addition, based on the monitoring result information (exit behavior), the registration device 10 switches the display setting of the exit button BT43 in the settlement-related notification area HR10 from a hidden state to a displayed state, and based on the monitoring result information (non-exit behavior), switches the display setting of the exit button BT43 in the settlement-related notification area HR10 from a displayed state to a hidden state.

[0179] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-exit behavior) when the display setting of the leave button BT43 in the registration device 10 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-exit behavior) to the registration device 10 when the display setting of the leave button BT43 in the registration device 10 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-exit behavior) to the registration device 10 after transmitting the monitoring result information (exit behavior) but before transmitting the monitoring result information (non-exit behavior) (including the case where both the monitoring result information (exit behavior) and the monitoring result information (non-exit behavior) were transmitted, but the last transmitted information was the monitoring result information (exit behavior)).

[0180] Step S225: The settlement device 20 transmits monitoring result information (non-operation preparatory action) to the transaction status management device 40. The monitoring result information (non-operation preparatory action) is monitoring result information indicating that the behavior of the customer using the settlement device 20 does not correspond to operation preparatory action. The monitoring result information (non-operation preparatory action) includes the device identification number of the settlement device 20 and information indicating that the behavior of the customer using the settlement device 20 does not correspond to operation preparatory action. Next, proceed to step S227.

[0181] In addition, based on the monitoring result information (operation preparation behavior), the transaction status management device 40 switches the display setting of the operation preparation button BT72 in the settlement-related notification area HR20 from a hidden state to a displayed state, and based on the monitoring result information (non-operation preparation behavior), switches the display setting of the operation preparation button BT72 in the settlement-related notification area HR20 from a displayed state to a hidden state.

[0182] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-operation preparatory action) when the display setting of the operation preparation button BT72 in the transaction status management device 40 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation preparatory action) to the transaction status management device 40 when the display setting of the operation preparation button BT72 in the transaction status management device 40 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation preparatory action) to the transaction status management device 40 after transmitting the monitoring result information (operation preparatory action) but before transmitting the monitoring result information (non-operation preparatory action) (including the case where both the monitoring result information (operation preparatory action) and the monitoring result information (non-operation preparatory action) have been transmitted, but the monitoring result information (operation preparatory action) was transmitted last)).

[0183] Step S227: The settlement device 20 transmits the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40. The monitoring result information (non-operation hesitation behavior) is monitoring result information indicating that the behavior of the customer using the settlement device 20 does not correspond to hesitation behavior. The monitoring result information (non-operation hesitation behavior) includes the device identification number of the settlement device 20 and information indicating that the behavior of the customer using the settlement device 20 does not correspond to hesitation behavior. This flowchart then ends.

[0184] In addition, based on the monitoring result information (operational hesitation behavior), the transaction status management device 40 switches the display setting of the operation hesitation button BT71 in the settlement-related notification area HR20 from a hidden state to a displayed state, and based on the monitoring result information (non-operational hesitation behavior), switches the display setting of the operation hesitation button BT71 in the settlement-related notification area HR20 from a displayed state to a hidden state.

[0185] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-operation hesitation behavior) when the display setting of the operation hesitation button BT71 in the transaction status management device 40 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40 when the display setting of the operation hesitation button BT71 in the transaction status management device 40 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40 after transmitting the monitoring result information (operation hesitation behavior) but before transmitting the monitoring result information (non-operation hesitation behavior) (including the case where both the monitoring result information (operation hesitation behavior) and the monitoring result information (non-operation hesitation behavior) were transmitted, but the monitoring result information (operation hesitation behavior) was transmitted last)).

[0186] (Explanation of the flowchart in Figure 16(C)) The flowchart in FIG. 16(C) shows details of the usage status monitoring process (step S57 in the flowchart in FIG. 15).

[0187] Step S210 in Figure 16 (C): The settlement device 20 transmits monitoring result information (available state) to the transaction status management device 40. The monitoring result information (available state) is monitoring result information indicating that the usage status of the settlement device 20 is available. For example, the monitoring result information (available state) includes the device identification number of the settlement device 20 and information indicating that the usage status is available. Next, proceed to step S221.

[0188] The transaction status management device 40 displays "Available" in the settlement-related notification area HR20 based on the monitoring result information (available).

[0189] Step S211: The settlement device 20 transmits the monitoring result information (vacant status) to the registration device 10. Then, this flowchart ends.

[0190] The registration device 10 displays "vacant status" in the settlement-related notification area HR10 based on the monitoring result information (vacant status).

[0191] (Explanation of the flowcharts in Figures 17 to 19) 17 to 19 show details of the behavior monitoring process (steps S33 and S36 in the flowchart of FIG. 14, and steps S41, S50, and S55 in the flowchart of FIG. 15). The flowchart of FIG. 18 is a continuation of the flowchart of FIG. 17. The flowchart of FIG. 19 is a continuation of the flowchart of FIG. 18.

[0192] Step S300 in Figure 17: The settlement device 20 determines whether the customer's behavior is in a pre-leaving behavior determination state based on the captured image. If it is in the pre-leaving behavior determination state (step S300: YES), proceed to step S301. If it is not in the pre-leaving behavior determination state (step S300: NO), proceed to step S320 in Figure 18.

[0193] Step S301: The settlement device 20 starts timing the time before leaving behavior determination. That is, the settlement device 20 starts a timer (a timer for timing the time before leaving behavior determination). Note that if the settlement device 20 has already started timing the time before leaving behavior determination, it continues this timing. That is, if the settlement device 20 has already started a timer, it continues timing using this timer. Next, proceed to step S302.

[0194] Step S302: If the settlement device 20 is timing the time before determining preparatory behavior for operation, it initializes the time value (measured value) of the time before determining preparatory behavior for operation. That is, if the settlement device 20 has started a timer (a timer for timing the time before determining preparatory behavior for operation), it resets the time value of the timer. Note that, as with the initialization process (step S221) shown in FIG. 16(B), the settlement device 20 only resets the time value of the timer and does not start timing. Next, proceed to step S303.

[0195] Step S303: If the settlement device 20 is counting the time before determining a hesitant operation behavior, it initializes the count value (measured value) of the time before determining a hesitant operation behavior. That is, if the settlement device 20 has started a timer (a timer for counting the time before determining a hesitant operation behavior), it resets the count value of the timer. Note that, as with the initialization process (step S222) shown in FIG. 16(B), the settlement device 20 only resets the count value of the timer and does not start timing. Next, proceed to step S310.

[0196] Step S310: The settlement device 20 determines whether the time before leaving behavior determination, which started to be measured in step S301, is equal to or greater than the determination time for determining the time before leaving behavior determination (e.g., 5 seconds). If the time before leaving behavior determination is equal to or greater than the determination time (step S310: YES), proceed to step S310. If the time before leaving behavior determination is not equal to or greater than the determination time (step S310: NO), this flowchart ends.

[0197] Step S311: The settlement device 20 transmits the monitoring result information (non-operation preparation action) to the transaction status management device 40, similar to step S225 in Figure 16(B). Then, proceed to step S313. Note that, similar to step S225 in Figure 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-operation preparation action) to the transaction status management device 40 if the display setting of the operation preparation button BT72 in the transaction status management device 40 is already in the hidden state.

[0198] Step S313: The settlement device 20 transmits the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40, similar to step S227 in Figure 16(B). Then, proceed to step S315. Note that, similar to step S227 in Figure 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40 when the display setting of the operation hesitation button BT71 in the transaction status management device 40 is already in the hidden state.

[0199] Step S315: The settlement device 20 transmits the monitoring result information (exit behavior) to the transaction status management device 40. The monitoring result information (exit behavior) is monitoring result information that indicates that the behavior of the customer using the settlement device 20 corresponds to exit behavior. The monitoring result information (exit behavior) includes the device identification number of the settlement device 20, information indicating that the behavior of the customer using the settlement device 20 corresponds to exit behavior, and timing information. Next, proceed to step S316.

[0200] The timing information in the monitoring result information (withdrawal behavior) is information indicating at what timing the withdrawal behavior occurred. The behavior monitoring process includes the behavior monitoring process of step S33, the behavior monitoring process of step S36, the behavior monitoring process of step S41, the behavior monitoring process of step S50, and the behavior monitoring process of step S55, and the timing information may be information specifying the behavior monitoring process currently being executed (information that can specify which of the behavior monitoring processes of steps S33, S36, S41, S50, and S55 it is).

[0201] Note that the settlement device 20 does not need to transmit the monitoring result information (withdrawal behavior) when the display setting of the Withdraw button BT73 in the transaction status management device 40 is already in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (withdrawal behavior) to the transaction status management device 40 when the display setting of the Withdraw button BT73 in the transaction status management device 40 is in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (withdrawal behavior) to the transaction status management device 40 before transmitting the monitoring result information (withdrawal behavior) (including a case where both the settlement device 20 has transmitted the monitoring result information (withdrawal behavior) and the monitoring result information (non-withdrawal behavior) but the last one transmitted was the monitoring result information (non-withdrawal behavior)).

[0202] Step S316: The settlement device 20 transmits the monitoring result information (leaving behavior) to the registration device 10. Then, this flowchart ends.

[0203] Note that the settlement device 20 does not need to transmit the monitoring result information (exit behavior) when the display setting of the leave button BT43 in the registration device 10 is already in the display state. In other words, the settlement device 20 may transmit the monitoring result information (exit behavior) to the registration device 10 when the display setting of the leave button BT43 in the registration device 10 is in the non-display state. In other words, the settlement device 20 may transmit the monitoring result information (exit behavior) to the registration device 10 before transmitting the monitoring result information (exit behavior) (including the case where both the monitoring result information (exit behavior) and the monitoring result information (non-exit behavior) have been transmitted, but the last transmitted information was the monitoring result information (non-exit behavior)).

[0204] Step S320 in Figure 18: The settlement device 20 determines whether the customer's behavior is in a pre-operation preparatory behavior determination state based on the captured image. If the customer's behavior is in the pre-operation preparatory behavior determination state (step S320: YES), the process proceeds to step S321. If the customer's behavior is not in the pre-operation preparatory behavior determination state (step S320: NO), the process proceeds to step S341 in Figure 19.

[0205] Step S321: The settlement device 20 starts timing the time before determining the preparatory action for operation. That is, the settlement device 20 starts a timer (a timer for timing the time before determining the preparatory action for operation). Note that if the settlement device 20 has already started timing the time before determining the preparatory action for operation, it continues this timing. That is, if the timer has already been started, the settlement device 20 continues timing using this timer. Next, proceed to step S322.

[0206] Step S322: If the settlement device 20 is timing the time before leaving behavior determination, it initializes the time value (measured value) of the time before leaving behavior determination. That is, if the settlement device 20 has started a timer (a timer for timing the time before leaving behavior determination), it resets the time value of the timer. Note that, as with the initialization process (step S220) shown in FIG. 16(B), the settlement device 20 only resets the time value of the timer and does not start timing. Next, proceed to step S323.

[0207] Step S323: The settlement device 20 transmits the monitoring result information (non-withdrawal behavior) to the transaction status management device 40, similar to step S223 in Figure 16(B). Then, proceed to step S324. Note that, similar to step S223 in Figure 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-withdrawal behavior) to the transaction status management device 40 if the display setting of the withdrawal button BT73 in the transaction status management device 40 is already in the hidden state.

[0208] Step S324: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10, similar to step S224 in Fig. 16(B). Then, proceed to step S325. Note that, similar to step S224 in Fig. 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-leaving behavior) to the registration device 10 when the display setting of the leave button BT43 in the registration device 10 is already in the hidden state.

[0209] Step S325: As in step S303 of Fig. 17, if the settlement device 20 is measuring the time before determining a hesitant operation behavior, it initializes the measured value of the time before determining a hesitant operation behavior. Then, the process proceeds to step S326.

[0210] Step S326: The settlement device 20 transmits the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40, similar to step S227 in Figure 16(B). Then, proceed to step S330. Note that, similar to step S227 in Figure 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-operation hesitation behavior) to the transaction status management device 40 when the display setting of the operation hesitation button BT71 in the transaction status management device 40 is already in the hidden state.

[0211] Step S330: The settlement device 20 determines whether the time before operation preparatory behavior determination, which started to be measured in step S321, is equal to or greater than the determination time for determining the time before operation preparatory behavior determination (e.g., 30 seconds). If the time before operation preparatory behavior determination is equal to or greater than the determination time (step S330: YES), proceed to step S331. If the time before operation preparatory behavior determination is not equal to or greater than the determination time (step S330: NO), this flowchart ends.

[0212] Step S331: The settlement device 20 transmits monitoring result information (operation preparatory action) to the transaction status management device 40. The monitoring result information (operation preparatory action) is monitoring result information that indicates that the behavior of the customer using the settlement device 20 corresponds to operation preparatory action. The monitoring result information (operation preparatory action) includes the device identification number of the settlement device 20, information indicating that the behavior of the customer using the settlement device 20 corresponds to operation preparatory action, and timing information. This flowchart then ends.

[0213] The timing information in the monitoring result information (operation preparation behavior) is information indicating the timing of the operation preparation behavior, similar to the timing information in the monitoring result information (withdrawal behavior).

[0214] Note that the settlement device 20 does not need to transmit the monitoring result information (operation preparatory action) when the display setting of the operation preparation button BT72 in the transaction status management device 40 is already in the display state. In other words, the settlement device 20 may transmit the monitoring result information (operation preparatory action) to the transaction status management device 40 when the display setting of the operation preparation button BT72 in the transaction status management device 40 is in the non-display state. In other words, the settlement device 20 may transmit the monitoring result information (operation preparatory action) to the transaction status management device 40 before transmitting the monitoring result information (operation preparatory action) (including a case where both the settlement device 20 has transmitted the monitoring result information (operation preparatory action) and the monitoring result information (non-operation preparatory action) but the last one transmitted was the monitoring result information (non-operation preparatory action)).

[0215] Step S341 in FIG. 19: The settlement device 20 starts timing the time before determining the hesitant operation behavior. That is, the settlement device 20 starts a timer (a timer for timing the time before determining the hesitant operation behavior). Note that if the settlement device 20 has already started timing the time before determining the preparatory operation behavior, it continues this timing. That is, if the timer has already started, the settlement device 20 continues timing using this timer. Next, the process proceeds to step S342.

[0216] Step S342: As in step S322 of Fig. 18, if the time before leaving behavior determination is being measured, the settlement device 20 initializes the measured value (measured value) of the time before leaving behavior determination. Then, the process proceeds to step S343.

[0217] Step S343: The settlement device 20 transmits the monitoring result information (non-withdrawal behavior) to the transaction status management device 40, similar to step S223 in Figure 16(B). Then, proceed to step S344. Note that, similar to step S223 in Figure 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-withdrawal behavior) to the transaction status management device 40 if the display setting of the withdrawal button BT73 in the transaction status management device 40 is already in the hidden state.

[0218] Step S344: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10, similar to step S224 in Fig. 16(B). Then, proceed to step S345. Note that, similar to step S224 in Fig. 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-leaving behavior) to the registration device 10 when the display setting of the leave button BT43 in the registration device 10 is already in the hidden state.

[0219] Step S345: As in step S302 of Fig. 17, if the time before operation preparatory behavior determination is being measured, the settlement device 20 initializes the measured value of the time before operation preparatory behavior determination. Then, the process proceeds to step S346.

[0220] Step S346: The settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the transaction status management device 40, similar to step S225 in Figure 16(B). Then, proceed to step S350. Note that, similar to step S225 in Figure 16(B), the settlement device 20 does not need to transmit the monitoring result information (non-operation preparation behavior) to the transaction status management device 40 if the display setting of the operation preparation button BT72 in the transaction status management device 40 is already in the hidden state.

[0221] Step S350: The settlement device 20 determines whether the time before hesitant operation behavior determination, which began to be measured in step S341, is equal to or greater than the determination time for determining the time before hesitant operation behavior determination (e.g., 20 seconds). If the time before hesitant operation behavior determination is equal to or greater than the determination time (step S350: YES), the process proceeds to step S351. If the time before hesitant operation behavior determination is not equal to or greater than the determination time (step S350: NO), the process ends.

[0222] Step S351: The settlement device 20 transmits monitoring result information (operational uncertainty behavior) to the transaction status management device 40. The monitoring result information (operational uncertainty behavior) is monitoring result information that indicates that the behavior of the customer using the settlement device 20 corresponds to operational uncertainty behavior. The monitoring result information (operational uncertainty behavior) includes the device identification number of the settlement device 20, information indicating that the behavior of the customer using the settlement device 20 corresponds to operational uncertainty behavior, and timing information. This flowchart then ends.

[0223] The timing information in the monitoring result information (operational uncertainty behavior) is information indicating the timing of the operational uncertainty behavior, similar to the timing information in the monitoring result information (withdrawal behavior) and the timing information in the operational preparation behavior (operation preparation behavior).

[0224] The settlement device 20 does not need to transmit the monitoring result information (hesitant operation behavior) when the display setting of the operation hesitation button BT71 in the transaction status management device 40 is already in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (hesitant operation behavior) to the transaction status management device 40 when the display setting of the operation hesitation button BT71 in the transaction status management device 40 is in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (hesitant operation behavior) to the transaction status management device 40 before transmitting the monitoring result information (hesitant operation behavior) (including the case where both the monitoring result information (hesitant operation behavior) and the monitoring result information (hesitant non-operation behavior) have been transmitted, but the last transmitted monitoring result information was the monitoring result information (hesitant non-operation behavior)).

[0225] (Explanation of the flowchart in Figure 20) The flowchart in Fig. 20 shows details of the currency monitoring process (step S49 in the flowchart in Fig. 15). Fig. 21 shows an example of information referenced in the currency monitoring process.

[0226] Step S400 in Figure 20: The settlement device 20 determines whether any of the coins is less than the second lower limit number for determining whether the transaction is near-end. If any of the coins is less than the second lower limit number (step S400: YES), the process proceeds to step S401. If none of the coins is less than the second lower limit number (step S400: NO), the process proceeds to step S402.

[0227] Step S401: The settlement device 20 determines whether any of the coins are below the first lower limit number for determining whether the transaction is near-end. As will be explained in detail in FIG. 21, the first lower limit number is a number that is less than the second lower limit number. If any of the coins are below the first lower limit number (Step S401: YES), the process proceeds to Step S406. If none of the coins are below the first lower limit number (Step S401: NO), the process proceeds to Step S404.

[0228] Step S402: The settlement device 20 transmits monitoring result information (non-near-end state) to the transaction status management device 40. The monitoring result information (non-near-end state) is monitoring result information indicating that none of the coins in the settlement device 20 are in a near-end state. The monitoring result information (non-near-end state) includes the device identification number of the settlement device 20 and information indicating that none of the coins in the settlement device 20 are in a near-end state. Next, proceed to step S403.

[0229] In addition, based on the monitoring result information (near-end state), the transaction status management device 40 switches the display setting of the near-end button BT62 in the settlement-related notification area HR20 from a hidden state to a displayed state, and based on the monitoring result information (non-near-end state), switches the display setting of the near-end button BT62 in the settlement-related notification area HR20 from a displayed state to a hidden state.

[0230] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-near-end state) when the display setting of the near-end button BT62 in the transaction status management device 40 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-near-end state) to the transaction status management device 40 when the display setting of the near-end button BT62 in the transaction status management device 40 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-near-end state) to the transaction status management device 40 after transmitting the monitoring result information (near-end state) but before transmitting the monitoring result information (non-near-end state) (including the case where both the monitoring result information (near-end state) and the monitoring result information (non-near-end state) were transmitted, but the last one transmitted was the monitoring result information (near-end state)).

[0231] Step S403: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10. Then, the process proceeds to step S410.

[0232] Furthermore, based on the monitoring result information (near-end state), the registration device 10 switches the display setting of the near-end button BT32 in the settlement-related notification area HR10 from a hidden state to a displayed state, and based on the monitoring result information (non-near-end state), switches the display setting of the near-end button BT32 in the settlement-related notification area HR10 from a displayed state to a hidden state.

[0233] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-near-end state) when the display setting of the near-end button BT32 on the registration device 10 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-near-end state) to the registration device 10 when the display setting of the near-end button BT32 on the registration device 10 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-near-end state) to the registration device 10 after transmitting the monitoring result information (near-end state) but before transmitting the monitoring result information (non-near-end state) (including the case where both the monitoring result information (near-end state) and the monitoring result information (non-near-end state) have been transmitted, but the last one transmitted was the monitoring result information (near-end state)).

[0234] Step S404: The settlement device 20 transmits monitoring result information (near-end state) to the transaction status management device 40. The monitoring result information (near-end state) is monitoring result information that indicates that any coin in the settlement device 20 is in a near-end state. The monitoring result information (near-end state) includes the device identification number of the settlement device 20, information indicating that any coin in the settlement device 20 is in a near-end state, and information about the near-end state (corresponding coin, number of coins). Next, proceed to step S405.

[0235] Note that the settlement device 20 does not need to transmit the monitoring result information (near-end state) when the display setting of the near-end button BT62 in the transaction status management device 40 is already in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (near-end state) to the transaction status management device 40 when the display setting of the near-end button BT62 in the transaction status management device 40 is in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (near-end state) to the transaction status management device 40 before transmitting the monitoring result information (near-end state) (including the case where both the monitoring result information (near-end state) and the monitoring result information (non-near-end state) have been transmitted, but the last transmitted information was the monitoring result information (non-near-end state)).

[0236] Step S405: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10. Then, proceed to step S410. Note that, similar to step S403, the settlement device 20 does not need to transmit the monitoring result information (non-near-end state) to the registration device 10 when the display setting of the near-end button BT32 in the registration device 10 is already in the hidden state.

[0237] Step S406: The settlement device 20 transmits the monitoring result information (near-end state) to the transaction status management device 40. Then, proceed to step S407. As in step S404, the settlement device 20 does not need to transmit the monitoring result information (near-end state) if the display setting of the near-end button BT62 in the transaction status management device 40 is already in the display state.

[0238] Step S407: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10. Then, the process proceeds to step S410.

[0239] Note that the settlement device 20 does not need to transmit the monitoring result information (near-end state) when the display setting of the near-end button BT32 on the registration device 10 is already in the display state. In other words, the settlement device 20 may transmit the monitoring result information (near-end state) to the registration device 10 when the display setting of the near-end button BT32 on the registration device 10 is in the non-display state. In other words, the settlement device 20 may transmit the monitoring result information (near-end state) to the registration device 10 before transmitting the monitoring result information (near-end state) (including the case where both the monitoring result information (near-end state) and the monitoring result information (non-near-end state) have been transmitted, but the last transmitted information was the monitoring result information (non-near-end state)).

[0240] In addition, the settlement device 20 sends monitoring result information (non-near-end state) when the near-end state is resolved by an increase in currency due to a customer inserting currency (steps S400 (NO), S401 (NO)), as well as when the near-end state is resolved by a store clerk's action (such as replenishing currency).

[0241] Step S410: The settlement device 20 determines whether any of the coins is more than the second upper limit number for determining whether the machine is near-full. If any of the coins is more than the second upper limit number (Step S410: YES), the process proceeds to Step S411. If none of the coins is more than the second upper limit number (Step S410: NO), the process proceeds to Step S412.

[0242] Step S411: The settlement device 20 determines whether any of the coins is more than the second upper limit number for determining whether the machine is near-full. As will be explained in detail in FIG. 21, the first upper limit number is a number that is more than the second upper limit number. If any of the coins is more than the second upper limit number (Step S411: YES), proceed to Step S416. If none of the coins is more than the first upper limit number (Step S411: NO), proceed to Step S414.

[0243] Step S412: The settlement device 20 transmits monitoring result information (non-near-full state) to the transaction status management device 40. The monitoring result information (non-near-full state) is monitoring result information indicating that none of the coins in the settlement device 20 are in a near-full state. The monitoring result information (non-near-full state) includes the device identification number of the settlement device 20 and information indicating that none of the coins in the settlement device 20 are in a near-full state. Next, proceed to step S413.

[0244] In addition, based on the monitoring result information (near-full state), the transaction status management device 40 switches the display setting of the near-full button BT63 in the settlement-related notification area HR20 from a hidden state to a displayed state, and based on the monitoring result information (non-near-full state), switches the display setting of the near-full button BT63 in the settlement-related notification area HR20 from a displayed state to a hidden state.

[0245] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-near-full state) when the display setting of the near-full button BT63 in the transaction status management device 40 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-near-full state) to the transaction status management device 40 when the display setting of the near-full button BT63 in the transaction status management device 40 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-near-full state) to the transaction status management device 40 after transmitting the monitoring result information (near-full state) but before transmitting the monitoring result information (non-near-full state) (including the case where both the monitoring result information (near-full state) and the monitoring result information (non-near-full state) have been transmitted, but the last one transmitted was the monitoring result information (near-full state)).

[0246] Step S413: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10. Then, this flowchart ends.

[0247] In addition, based on the monitoring result information (near-full state), the registration device 10 switches the display setting of the near-full button BT33 in the settlement-related notification area HR10 from a hidden state to a displayed state, and based on the monitoring result information (non-near-full state), switches the display setting of the near-full button BT33 in the settlement-related notification area HR10 from a displayed state to a hidden state.

[0248] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-near full state) when the display setting of the near-full button BT33 on the registration device 10 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-near full state) to the registration device 10 when the display setting of the near-full button BT33 on the registration device 10 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-near full state) to the registration device 10 after transmitting the monitoring result information (near full state) but before transmitting the monitoring result information (non-near full state) (including the case where both the monitoring result information (near full state) and the monitoring result information (non-near full state) have been transmitted, but the last one transmitted was the monitoring result information (near full state)).

[0249] Step S414: The settlement device 20 transmits monitoring result information (near-full state) to the transaction status management device 40. The monitoring result information (near-full state) is monitoring result information that indicates that any coin in the settlement device 20 is in a near-full state. The monitoring result information (near-full state) includes the device identification number of the settlement device 20, information indicating that any coin in the settlement device 20 is in a near-full state, and information about the near-full state (corresponding coins, number of coins). Next, proceed to step S415.

[0250] Note that the settlement device 20 does not need to transmit the monitoring result information (near-full state) when the display setting of the near-full button BT63 in the transaction status management device 40 is already in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (near-full state) to the transaction status management device 40 when the display setting of the near-full button BT63 in the transaction status management device 40 is in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (near-full state) to the transaction status management device 40 before transmitting the monitoring result information (near-full state) (including the case where both the monitoring result information (near-full state) and the monitoring result information (non-near-full state) have been transmitted, but the last transmitted information was the monitoring result information (non-near-full state)).

[0251] Step S415: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10. Then, this flowchart ends. Note that, similar to step S413, the settlement device 20 does not need to transmit the monitoring result information (non-near-full state) to the registration device 10 when the display setting of the near-full button BT33 in the registration device 10 is already in the hidden state.

[0252] Step S416: The settlement device 20 transmits the monitoring result information (near-full state) to the transaction status management device 40. Then, proceed to step S417. As in step S414, the settlement device 20 does not need to transmit the monitoring result information (near-full state) if the display setting of the near-full button BT63 in the transaction status management device 40 is already in the displayed state.

[0253] Step S417: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10. Then, this flowchart ends.

[0254] Note that the settlement device 20 does not need to transmit the monitoring result information (near-full state) when the display setting of the near-full button BT33 on the registration device 10 is already in the display state. In other words, the settlement device 20 may transmit the monitoring result information (near-full state) to the registration device 10 when the display setting of the near-full button BT33 on the registration device 10 is in the non-display state. In other words, the settlement device 20 may transmit the monitoring result information (near-full state) to the registration device 10 before transmitting the monitoring result information (near-full state) (including a case where both the monitoring result information (near-full state) and the monitoring result information (non-near-full state) have been transmitted, but the last transmitted information was the monitoring result information (non-near-full state)).

[0255] In addition, the settlement device 20 sends monitoring result information (non-near-full state) when the near-full state is resolved due to a decrease in currency due to the dispensing of change (steps S410 (NO), S411 (NO)), as well as when the near-full state is resolved due to the action of a store clerk (such as discharging currency).

[0256] The settlement device 20 may execute the above-mentioned determination process (the processes of steps S400, S401, S410, and S411) by referring to the near-end / near-full determination information as shown in Fig. 21. The near-end / near-full determination information shown in Fig. 21 may be stored in a location accessible by the settlement device 20 (for example, each settlement device 20, the transaction status management device 40, or a cloud server).

[0257] According to the near-end / near-full determination information shown in Fig. 21, the second lower limit for the number of 1-yen coins (same for 10-yen coins, 100-yen coins, and 1000-yen bills) is 25, and the first lower limit is 13, and the second lower limit for the number of 5-yen coins (same for 50-yen coins, 500-yen coins, and 5,000-yen bills) is 7, and the first lower limit is 4. Note that the numbers of 2,000-yen bills and 10,000-yen bills are not set because they are not used as change (indicated as "-" in Fig. 21).

[0258] Therefore, if the number of 1 yen coins, 10 yen coins, 100 yen coins, and 1000 yen bills is 25 or more (second lower limit number), and the number of 5 yen coins, 50 yen coins, 500 yen coins, and 5000 yen bills is 7 or more (second lower limit number) (step S400 (NO)), the settlement device 20 will not send monitoring result information (near-end state) to either the transaction status management device 40 or the registration device 10.

[0259] In addition, if at least one of 1 yen coins, 10 yen coins, 100 yen coins, and 1000 yen bills is less than 13 (first lower limit number), or if at least one of 5 yen coins, 50 yen coins, 500 yen coins, and 5000 yen bills is less than 4 (first lower limit number) (step S401 (YES)), the settlement device 20 sends monitoring result information (near-end state) to both the transaction status management device 40 and the registration device 10 (steps S406, S407).

[0260] In cases other than those described above (step S401 (NO)), the settlement device 20 transmits monitoring result information (near-end state) to the transaction status management device 40 (step S404).

[0261] 21, the second upper limit number of 1-yen coins (same for 10-yen coins, 100-yen coins, 1000-yen bills, and 10,000-yen bills) is 172, and the first upper limit number is 190; the second upper limit number of 5-yen coins (same for 50-yen coins and 500-yen coins) is 190, and the first upper limit number is 196; and the second upper limit number of 2,000-yen bills (same for 5,000-yen bills) is 193, and the first upper limit number is 197. For convenience, the description is given assuming that up to 200 of each currency can be stored.

[0262] Therefore, if the number of 1 yen coins, 10 yen coins, 100 yen coins, 1000 yen bills, and 10,000 yen bills is 172 or less (second upper limit number), the number of 5 yen coins, 50 yen coins, and 500 yen coins is 190 or less (second upper limit number), and the number of 2,000 yen bills and 5,000 yen bills is 193 or less (second upper limit number) (step S410 (NO)), the settlement device 20 will not send monitoring result information (near-full state) to either the transaction status management device 40 or the registration device 10.

[0263] In addition, if at least one of 1 yen coins, 10 yen coins, 100 yen coins, 1000 yen bills, and 10,000 yen bills is more than 190 (first upper limit number), or at least one of 5 yen coins, 50 yen coins, and 500 yen coins is more than 196 (first upper limit number), or at least one of 2,000 yen bills and 5,000 yen bills is more than 197 (first upper limit number) (step S411 (YES)), the settlement device 20 sends monitoring result information (near-full state) to both the transaction status management device 40 and the registration device 10 (steps S416, S417).

[0264] In cases other than those described above (step S411 (NO)), the settlement device 20 transmits monitoring result information (near-full state) to the transaction status management device 40 (step S414).

[0265] (Explanation of the flowchart in Figure 22) The flowchart in FIG. 22 shows details of the receipt paper monitoring process (step S54 in the flowchart in FIG. 15).

[0266] Step S420 in Figure 22: The settlement device 20 determines whether the remaining amount of receipt paper is less than the second determination amount (e.g., 2 meters) used to determine the remaining amount of receipt paper. If the remaining amount of receipt paper is less than the second determination amount (step S420: YES), proceed to step S421. If the remaining amount of receipt paper is not less than the second determination amount (step S420: NO), this flowchart ends.

[0267] Step S421: The settlement device 20 determines whether the remaining amount of receipt paper is less than the first determination amount (e.g., 1 meter) used to determine the remaining amount of receipt paper. If the remaining amount of receipt paper is less than the first determination amount (Step S421: YES), proceed to Step S427. If the remaining amount of receipt paper is not less than the first determination amount (Step S420: NO), proceed to Step S424.

[0268] Step S424: The settlement device 20 sends monitoring result information (receipt) to the transaction status management device 40. The monitoring result information (receipt) is monitoring result information indicating that the remaining amount of receipt paper in the settlement device 20 is low (a receipt paper replenishment state). The monitoring result information (receipt) includes the device identification number of the settlement device 20, information indicating that the settlement device 20 is in a receipt paper replenishment state, and information related to the receipt paper replenishment state (remaining receipt amount, etc.). This flowchart then ends.

[0269] In addition, based on the monitoring result information (receipt), the transaction status management device 40 switches the display setting of the receipt button BT61 in the settlement-related notification area HR20 from a hidden state to a displayed state, and based on the monitoring result information (non-receipt), switches the display setting of the receipt button BT61 in the settlement-related notification area HR20 from a displayed state to a hidden state.

[0270] Therefore, the settlement device 20 does not need to send the monitoring result information (receipt) when the display setting of the receipt button BT61 in the transaction status management device 40 is already in the display state. In other words, the settlement device 20 may send the monitoring result information (receipt) to the transaction status management device 40 when the display setting of the receipt button BT61 in the transaction status management device 40 is in the non-display state.

[0271] Step S427: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10. Then, this flowchart ends.

[0272] Based on the monitoring result information (receipt), the registration device 10 switches the display setting of the receipt button BT31 in the settlement-related notification area HR10 from a hidden state to a displayed state, and based on the monitoring result information (non-receipt), switches the display setting of the receipt button BT31 in the settlement-related notification area HR10 from a displayed state to a hidden state.

[0273] Therefore, the settlement device 20 does not need to send the monitoring result information (receipt) when the display setting of the receipt button BT31 on the registration device 10 is already in the display state. In other words, the settlement device 20 may send the monitoring result information (receipt) to the registration device 10 when the display setting of the receipt button BT31 on the registration device 10 is in the non-display state.

[0274] Note that the settlement device 20 sends monitoring result information (non-receipt) when the receipt paper replenishment requirement state is resolved by a store clerk's action (such as refilling receipt paper). This is not shown in the flowchart of FIG. 22. In the first embodiment (as in the second embodiment), when there is a certain amount of receipt paper remaining, the display (presence or absence of display) of the receipt button BT31 on a given device is determined based on the type of device (registration device 10, transaction status management device 40). In other words, if it is the same device, the display of the receipt button BT31 will not change unless a store clerk refills receipt paper. Therefore, in the first embodiment (as in the second embodiment), the sending of monitoring result information (non-receipt) is omitted from the receipt paper monitoring process (FIG. 22).

[0275] On the other hand, in the third to sixth embodiments described below, the display of the receipt button BT31 may change on the same device even if the clerk has not replenished the receipt paper. For example, in the third embodiment (and the fourth embodiment as well), the display of the receipt button BT31 may change depending on the user (regular clerk, restricted clerk). Also, in the fifth embodiment (and the sixth embodiment as well), the display of the receipt button BT31 may change depending on the state (normal notification state, restricted notification state). Therefore, the third embodiment (and the fourth embodiment as well) assumes a change in user, and the fifth embodiment (and the sixth embodiment as well) assumes a change in state, and sends monitoring result information (non-receipt) in the receipt paper monitoring process (FIGS. 31 and 41).

[0276] (Non-cash) As mentioned above, the flowcharts shown in Figs. 14 and 15 show the processing flow when the payment method of the settlement device 20 is cash. Therefore, the execution timing of the initialization processing and behavior monitoring processing in Figs. 14 and 15 is an example when the payment method is cash. When the payment method is a payment method other than cash (credit, electronic money, etc.), the settlement device 20 executes the initialization processing and behavior monitoring processing at execution timings according to the processing corresponding to each payment method. As an example, when the payment method is credit, the initialization processing may be executed when a credit card is inserted as a customer action or when a dispensed credit card is removed, and the behavior monitoring processing may be executed between the time the credit card is dispensed and the time it is removed. The same applies to the other embodiments (second to sixth embodiments) described below.

[0277] 14 and 15 illustrate an example in which the currency monitoring process is executed, but if there is no increase or decrease in currency (for example, if the payment method is a payment method other than cash), the currency monitoring process may be omitted. Also, the flowcharts shown in FIGS. 14 and 15 illustrate an example in which the receipt paper monitoring process is executed, but if a receipt is not printed or issued (for example, if an electronic receipt is used, or if an operation that does not require a receipt, not shown, has been performed), the receipt paper monitoring process may be omitted. In other embodiments (second to sixth embodiments) described below, examples will be described in which neither the currency monitoring process nor the receipt paper monitoring process is omitted, but in such cases, the currency monitoring process and receipt paper monitoring process may be omitted in other embodiments as well.

[0278] (Second embodiment) Next, as a second embodiment, a mode in which the registration device 10 displays an operation confusion button and an operation preparation button will be described. That is, in the first embodiment, the operation confusion button and the operation preparation button were not displayed on the registration device 10, but in the second embodiment, the operation confusion button and the operation preparation button are displayed on the registration device 10. Note that the network configuration, the configuration of each device, etc. in the second embodiment are the same as those in the first embodiment already described, and therefore, the description of the parts common to the first embodiment will be omitted in part or in whole.

[0279] Fig. 23 shows an example of a display in the settlement-related notification area in the second embodiment. Specifically, each of Fig. 23(A) to Fig. 23(D) is an example of a display in the settlement-related notification area HR10-2.

[0280] The operation hesitation button BT41 shown in Figure 23 (A) indicates that the behavior (action) of a customer using the payment device 20 (202 register) is operation hesitation. The operation hesitation button BT41 is one of the notification buttons (an notification button that notifies that the behavior of the customer is operation hesitation). When the operation hesitation button BT41 is operated, detailed notification information regarding the operation hesitation (such as information indicating at which processing stage the operation hesitation occurs) is displayed.

[0281] The registration device 10 switches the display of the operation hesitation button BT41 from a non-display state to a display state based on the monitoring result information (operation hesitation behavior) transmitted by the register 202, and switches the display of the operation hesitation button BT41 from a display state to a non-display state based on the monitoring result information (non-operation hesitation behavior). The same applies to the display of the operation hesitation button BT41 in other payment-related notification areas (payment-related notification area HR20-1, etc.).

[0282] FIG. 23(B) is a display example of detailed notification information related to payment (specifically, detailed notification information related to hesitant operation behavior). When a store clerk operates the hesitant operation button BT41, the registration device 10 displays detailed notification information (detailed notification information related to hesitant operation behavior) as shown in FIG. 23(B). In FIG. 23(B), the phrase "hesitant operation behavior (before operating the finish button)" indicates that the hesitant operation behavior occurred before operating the finish button (the timing of the behavior monitoring process in step S41 of FIG. 15).

[0283] The operation preparation button BT42 shown in Figure 23 (C) indicates that the behavior (action) of a customer using the payment device 20 (202 register) is an operation preparation action. The operation preparation button BT42 is one of the notification buttons (an notification button that notifies that the behavior of the customer is an operation preparation action). When the operation preparation button BT42 is operated, detailed notification information regarding the operation preparation action (such as information indicating at which processing stage the operation preparation action is) is displayed.

[0284] The registration device 10 switches the display of the operation preparation button BT42 from a hidden state to a displayed state based on the monitoring result information (operation preparation behavior) transmitted by the register 202, and switches the display of the operation preparation button BT42 from a displayed state to a hidden state based on the monitoring result information (non-operation preparation behavior). The same applies to the display of the operation preparation button BT42 in other settlement-related notification areas (such as the settlement-related notification area HR20-1).

[0285] FIG. 23(D) is a display example of detailed notification information related to payment (specifically, detailed notification information related to operation preparatory behavior). When a store clerk operates the operation preparation button BT42, the registration device 10 displays detailed notification information (detailed notification information related to operation preparatory behavior) as shown in FIG. 23(D). In FIG. 23(D), the words "operation preparatory behavior (before selection of payment method)" indicate that the operation preparatory behavior in question is operation preparatory behavior at the timing before selection of a payment method (the timing of the behavior monitoring process in step S33 of FIG. 14).

[0286] Figures 24 and 25 are flowcharts showing an example of the operation of the settlement device 20 in the second embodiment. Specifically, Figure 24(A) replaces the dashed frame P1 in Figure 16(B) of the first embodiment. Figure 24(B) replaces the dashed frame P2 in Figure 17 of the first embodiment. Figure 25(A) replaces the dashed frame P3 in Figure 18 of the first embodiment. Figure 25(B) replaces the dashed frame P4 in Figure 19 of the first embodiment.

[0287] (Flowchart of Figure 24(A)) As will be described below, the flowchart in Figure 24(A) differs from the flowchart in Figure 16(B) in that it includes the processes of steps S226 and S228. Steps S226 and S228 will be described below.

[0288] Step S226: Following step S225, the settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10. Then, the process proceeds to step S227.

[0289] In addition, based on the monitoring result information (operation preparation behavior), the registration device 10 switches the display setting of the operation preparation button BT42 in the settlement-related notification area HR10 from a hidden state to a displayed state, and based on the monitoring result information (non-operation preparation behavior), switches the display setting of the operation preparation button BT42 in the settlement-related notification area HR10 from a displayed state to a hidden state.

[0290] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-operation preparatory action) when the display setting of the operation preparation button BT42 in the registration device 10 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation preparatory action) to the registration device 10 when the display setting of the operation preparation button BT42 in the registration device 10 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation preparatory action) to the registration device 10 after transmitting the monitoring result information (operation preparatory action) but before transmitting the monitoring result information (non-operation preparatory action) (including the case where both the monitoring result information (operation preparatory action) and the monitoring result information (non-operation preparatory action) have been transmitted, but the monitoring result information (operation preparatory action) was transmitted last)).

[0291] Step S228: Following step S227, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10. Then, this flowchart ends.

[0292] In addition, based on the monitoring result information (operational uncertainty behavior), the registration device 10 switches the display setting of the operation uncertainty button BT41 in the settlement-related notification area HR10 from a hidden state to a displayed state, and based on the monitoring result information (non-operational uncertainty behavior), switches the display setting of the operation uncertainty button BT41 in the settlement-related notification area HR10 from a displayed state to a hidden state.

[0293] Therefore, the settlement device 20 does not need to transmit the monitoring result information (non-operation hesitation behavior) when the display setting of the operation hesitation button BT41 in the registration device 10 is already in the hidden state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation hesitation behavior) to the registration device 10 when the display setting of the operation hesitation button BT41 in the registration device 10 is in the displayed state. In other words, the settlement device 20 may transmit the monitoring result information (non-operation hesitation behavior) to the registration device 10 after transmitting the monitoring result information (operation hesitation behavior) but before transmitting the monitoring result information (non-operation hesitation behavior) (including the case where both the monitoring result information (operation hesitation behavior) and the monitoring result information (non-operation hesitation behavior) were transmitted, but the last transmitted information was the monitoring result information (operation hesitation behavior)).

[0294] (Flowchart in Figure 24(B)) As will be described below, the flowchart in Figure 24(B) differs from the flowchart in Figure 17 in that it includes the processes of steps S312 and S314. Steps S312 and S314 will be described below.

[0295] Step S312: Following step S311, the settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10, similar to step S226 in Fig. 24(A). Then, proceed to step S313. Note that, similar to step S226 in Fig. 24(A), the settlement device 20 does not need to transmit the monitoring result information (non-exit behavior) to the registration device 10 when the display setting of the exit button BT43 in the registration device 10 is already in the hidden state.

[0296] Step S314: Following step S313, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10, similar to step S228 in Fig. 24(A). Then, proceed to step S315. Note that, similar to step S228 in Fig. 24(A), the settlement device 20 does not need to transmit the monitoring result information (non-operation hesitant behavior) to the registration device 10 when the display setting of the operation hesitation button BT41 in the registration device 10 is already in the hidden state.

[0297] (Flowchart of Figure 25(A)) As will be described below, the flowchart in Figure 25(A) differs from the flowchart in Figure 18 in that it includes the processes of steps S327, S335, and S336. Steps S327, S335, and S336 will be mainly described below.

[0298] Step S327: Following step S326, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10, similar to step S228 in Fig. 24(A). Then, the process proceeds to step S330. Note that, similar to step S228 in Fig. 24(A), the settlement device 20 does not need to transmit the monitoring result information (non-operation hesitant behavior) to the registration device 10 when the display setting of the operation hesitation button BT41 in the registration device 10 is already in the hidden state.

[0299] Step S330: The settlement device 20 determines whether the time before operation preparatory behavior determination, which began to be measured in step S321, is equal to or longer than the second determination time (e.g., 30 seconds) for determining the time before operation preparatory behavior determination. If the time before operation preparatory behavior determination is equal to or longer than the second determination time (step S330: YES), the process proceeds to step S331. If the time before operation preparatory behavior determination is not equal to or longer than the second determination time (step S330: NO), the process ends. Note that in this step S330, the "second determination time" is used in relation to step S335, which will be described later.

[0300] Step S335: Following step S331, the settlement device 20 determines whether the time before operation preparatory behavior determination, which began to be measured in step S321, is equal to or longer than the first determination time (e.g., one minute) for determining the time before operation preparatory behavior determination. If the time before operation preparatory behavior determination is equal to or longer than the first determination time (step S335: YES), the process proceeds to step S336. If the time before operation preparatory behavior determination is not equal to or longer than the first determination time (step S335: NO), the process ends.

[0301] Step S336: The settlement device 20 transmits the monitoring result information (operation preparation behavior) to the registration device 10. Then, this flowchart ends.

[0302] Note that the settlement device 20 does not need to transmit the monitoring result information (operation preparatory action) when the display setting of the operation preparation button BT42 in the registration device 10 is already in the display state. In other words, the settlement device 20 may transmit the monitoring result information (operation preparatory action) to the registration device 10 when the display setting of the operation preparation button BT42 in the registration device 10 is in the non-display state. In other words, the settlement device 20 may transmit the monitoring result information (operation preparatory action) to the registration device 10 before transmitting the monitoring result information (operation preparatory action) (including a case where both the monitoring result information (operation preparatory action) and the monitoring result information (non-operation preparatory action) have been transmitted, but the last transmitted monitoring result information (non-operation preparatory action) was)).

[0303] (Flowchart in Figure 25(B)) As will be described below, the flowchart in Figure 25(B) differs from the flowchart in Figure 19 in that it includes the processes of steps S347, S355, and S356. Steps S347, S355, and S356 will be mainly described below.

[0304] Step S347: Following step S346, the settlement device 20 transmits the monitoring result information (non-operation preparatory action) to the registration device 10, similar to step S226 in Fig. 24(A). Then, proceed to step S350. Note that, similar to step S226 in Fig. 24(A), the settlement device 20 does not need to transmit the monitoring result information (non-operation preparatory action) to the registration device 10 when the display setting of the operation preparation button BT42 in the registration device 10 is already in the hidden state.

[0305] Step S350: The settlement device 20 determines whether the time before determining hesitant operation behavior, which began to be measured in step S341, is equal to or longer than the second determination time (e.g., 20 seconds) for determining the time before determining hesitant operation behavior. If the time before determining hesitant operation behavior is equal to or longer than the second determination time (step S350: YES), the process proceeds to step S351. If the time before determining hesitant operation behavior is not equal to or longer than the second determination time (step S350: NO), the process ends. Note that in this step S350, the "second determination time" is used in relation to step S355, which will be described later.

[0306] Step S355: Following step S351, the settlement device 20 determines whether the time before determining hesitant operation behavior, which began to be measured in step S341, is equal to or longer than the first determination time (e.g., one minute) for determining the time before determining hesitant operation behavior. If the time before determining hesitant operation behavior is equal to or longer than the first determination time (step S355: YES), proceed to step S356. If the time before determining hesitant operation behavior is not equal to or longer than the first determination time (step S355: NO), this flowchart ends.

[0307] Step S356: The settlement device 20 transmits the monitoring result information (hesitant operation behavior) to the registration device 10. Then, this flowchart ends.

[0308] Note that the settlement device 20 does not need to transmit the monitoring result information (hesitant operation behavior) when the display setting of the operation hesitation button BT41 in the registration device 10 is already in the display state. In other words, the settlement device 20 may transmit the monitoring result information (hesitant operation behavior) to the registration device 10 when the display setting of the operation hesitation button BT41 in the registration device 10 is in the non-display state. In other words, the settlement device 20 may transmit the monitoring result information (hesitant operation behavior) to the registration device 10 before transmitting the monitoring result information (hesitant operation behavior) (including the case where both the monitoring result information (hesitant operation behavior) and the monitoring result information (non-hesitant operation behavior) have been transmitted, but the last transmitted information was the monitoring result information (non-hesitant operation behavior)).

[0309] (Third embodiment) Next, as a third embodiment, an embodiment will be described in which the notification mode (notification content, notification conditions, etc.) of information related to settlement (payment settlement device 20, customer using payment settlement device 20) is varied depending on the clerk (type of clerk). In other words, in the first embodiment (second embodiment), the notification mode of information related to settlement differed depending on the device (type of device: transaction status management device 40 / registration device 10), but in the third embodiment, the notification mode of information related to settlement differs depending on the clerk (type of clerk). Note that the network configuration, the configuration of each device, etc. in the third embodiment are similar to those in the first embodiment, etc., already described, and therefore some or all of the description of the parts common to the first embodiment, etc. will be omitted.

[0310] (Type of staff) There are regular clerks who have no restrictions on the notification of information related to payments (payment device 20, customers using payment device 20), and restricted clerks who have restrictions. For example, the distinction between regular clerks and restricted clerks can be made by, for example, classifying skilled clerks (skilled clerks) as regular clerks and inexperienced clerks (inexperienced clerks) as restricted clerks, or by classifying full-time employees as regular clerks and part-time clerks as restricted clerks.

[0311] In the POS system 1, whether a clerk is a regular clerk or a restricted clerk is identified using a clerk code. The clerk code alone may be used to identify whether the clerk is a regular clerk or a restricted clerk, or the clerk code may be used in combination with other information (files). In other words, when a device in the POS system 1 (e.g., the registration device 10, the transaction status management device 40) acquires a clerk code, it may determine whether the clerk is a regular clerk or a restricted clerk from the acquired clerk code (e.g., the value of a predetermined number of digits in the clerk code) itself, or it may determine whether the clerk is a regular clerk or a restricted clerk from the acquired clerk code and a clerk type file (a file that stores information indicating whether the clerk is a regular clerk or a restricted clerk in association with the clerk code).

[0312] There are no particular limitations on the method by which the devices in the POS system 1 acquire the clerk code. For example, if the clerk code is printed as a barcode on the name tag of each clerk, the registration device 10 may acquire the clerk code by reading the barcode on the name tag with the scanner unit 104. Furthermore, instead of or in addition to reading the barcode, the registration device 10 may acquire the clerk code through an input operation by the clerk (an input operation on a predetermined screen of the clerk display unit 105, an input operation using the key operation unit 108). The same applies to the transaction status management device 40.

[0313] The settlement device 20 can recognize whether the clerk using each device (registration device 10, transaction status management device 40) is a regular clerk or a restricted clerk. For example, the registration device 10 (and the transaction status management device 40) may acquire a clerk code at the time of login, use the acquired clerk code to determine whether the clerk who logged in is a regular clerk or a restricted clerk, and transmit the determination result (information indicating whether the clerk is a regular clerk or a restricted clerk) to the settlement device 20, or may simply transmit the clerk code to the settlement device 20. In the case of simply transmitting the clerk code, the settlement device 20, upon receiving the clerk code, uses the clerk code to determine whether the clerk using the registration device 10 (and the transaction status management device 40) is a regular clerk or a restricted clerk.

[0314] (Operation of the registration device 10 in the third embodiment) The operation of the registration device 10 in the third embodiment is similar to the operation of the registration device 10 in the first embodiment (FIGS. 12 and 13). That is, the flowcharts in FIGS. 12 and 13, which were explained as the operation of the registration device 10 in the first embodiment, are applied as the operation of the registration device 10 in the third embodiment. However, in the third embodiment, the registration device 10 transmits the clerk code acquired at the time of login or the like to the settlement device 20.

[0315] (Operation of settlement device 20 in the third embodiment) The flowcharts in Figures 14 and 15, which were explained as the operation of the settlement device 20 in the first embodiment, are applied as the operation of the settlement device 20 in the third embodiment. The flowcharts in Figures 16 to 20 and 22, which were explained as the operation of the settlement device 20 in the first embodiment, are not applied as the operation of the settlement device 20 in the third embodiment. In the third embodiment, the flowcharts in Figures 26 to 31 below are applied instead of the flowcharts in Figures 16 to 20 and 22 of the first embodiment.

[0316] 26 to 31 are flowcharts showing an example of the operation of the settlement device 20 in the third embodiment.

[0317] (Flowchart of Figure 26(A)) The flowchart in FIG. 26(A) shows details of the usage status monitoring process (step S31 in the flowchart in FIG. 14) that is applied in place of the flowchart in FIG. 16(A).

[0318] Step S1200: The settlement device 20 transmits the monitoring result information (in use state) to the registration device 10 that is normally used by the store clerk. Then, the process proceeds to step S1201. Step S1201: The settlement device 20 transmits the monitoring result information (in use state) to the registration device 10 used by the restricted clerk. Then, this flowchart ends.

[0319] (Flowchart of Figure 26(B)) Steps S1220 to S1222 in the flowchart of FIG. 26(B) are similar to steps S220 to S222 in the flowchart of FIG. 16(B), and therefore a description thereof will be omitted.

[0320] Step S1223: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 that is normally used by the store clerk. Then, the process proceeds to step S1224.

[0321] In the third embodiment (and also in the fourth to sixth embodiments), as in the first and second embodiments, the transmission of the monitoring result information may be omitted depending on the display / non-display state of the target notification button on the destination device. For example, in the case of step S1223, the settlement device 20 may omit transmitting the monitoring result information (non-exiting behavior) when the display setting of the exit button BT73 (the notification button to be erased by the monitoring result information (non-exiting behavior)) on the registration device 10 (destination device) normally used by the store clerk is already in the non-display state.

[0322] Step S1224: The settlement device 20 transmits the monitoring result information (non-departure behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1225. Step S1225: The settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1227. Step S1227: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 that is normally used by the store clerk. Then, this flowchart ends.

[0323] (Flowchart of Figure 26(C)) The flowchart in FIG. 26(C) shows details of the usage status monitoring process (step S57 in the flowchart in FIG. 15) that is applied in place of the flowchart in FIG. 16(C).

[0324] Step S1210: The settlement device 20 transmits the monitoring result information (vacant status) to the registration device 10 that is normally used by the store clerk. Then, the process proceeds to step S1221. Step S1211: The settlement device 20 transmits the monitoring result information (vacant status) to the registration device 10 used by the limited clerk. Then, this flowchart ends.

[0325] As in the first and second embodiments, if the display status on the receiving side does not change whether various types of monitoring result information are transmitted or not, the monitoring result information does not need to be transmitted. The same applies to the fourth to sixth embodiments.

[0326] (Explanation of the flowcharts in Figures 27 to 29) The flowcharts in Figures 27 to 29 show details of the behavior monitoring process (steps S33 and S36 in the flowchart in Figure 14, and steps S41, S50, and S55 in the flowchart in Figure 15) that are applied in place of the flowcharts in Figures 17 to 19. The flowchart in Figure 28 is a continuation of the flowchart in Figure 27. The flowchart in Figure 29 is a continuation of the flowchart in Figure 28.

[0327] Steps S1300 to S1310 in the flowchart of FIG. 27 are similar to steps S300 to S310 in the flowchart of FIG. 17, and therefore a description thereof will be omitted.

[0328] Step S1311: The settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1313. Step S1313: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10, which is normally used by a store clerk. Then, the process proceeds to step S1315. Step S1315: The settlement device 20 transmits the monitoring result information (exiting behavior) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1316. Step S1316: The settlement device 20 transmits the monitoring result information (leaving behavior) to the registration device 10 used by the restricted clerk. Then, this flowchart ends.

[0329] Steps S1320, S1321, S1322, S1325, and S1330 in the flowchart of FIG. 28 are similar to steps S320, S321, S322, S325, and S330 in the flowchart of FIG. 18, and therefore description thereof will be omitted.

[0330] Step S1323: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 that is normally used by the store clerk. Then, the process proceeds to step S1324. Step S1324: The settlement device 20 transmits the monitoring result information (non-departure behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1325. Step S1326: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10, which is normally used by a store clerk. Then, the process proceeds to step S1330. Step S1331: The settlement device 20 transmits the monitoring result information (operation preparation behavior) to the registration device 10 that is normally used by the store clerk. Then, this flowchart ends.

[0331] Steps S1341, S1342, S1345, and S1350 in the flowchart of FIG. 29 are similar to steps S341, S342, S345, and S350 in the flowchart of FIG. 19, and therefore description thereof will be omitted.

[0332] Step S1343: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 that is normally used by the store clerk. Then, the process proceeds to step S1344. Step S1344: The settlement device 20 transmits the monitoring result information (non-departure behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1345. Step S1346: The settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10 that is normally used by the store clerk. Then, the process proceeds to step S1350. Step S1351: The settlement device 20 transmits the monitoring result information (hesitant operation behavior) to the registration device 10 that is normally used by the store clerk. Then, this flowchart ends.

[0333] (Explanation of the flowchart in Figure 30) The flowchart of Fig. 30 shows details of the currency monitoring process (step S49 of the flowchart of Fig. 15) that is applied in place of the flowchart of Fig. 20. Steps S1400, S1401, S1410, and S1411 of the flowchart of Fig. 30 are the same as steps S400, S401, S410, and S411 of the flowchart of Fig. 20, and therefore description thereof will be omitted.

[0334] Step S1402: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10, which is normally used by a store clerk. Then, the process proceeds to step S1403. Step S1403: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10 used by the limited clerk. Then, the process proceeds to step S1410. Step S1404: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1405. Step S1405: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10 used by the limited clerk. Then, the process proceeds to step S1410. Step S1406: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10, which is normally used by a store clerk. Then, the process proceeds to step S1407. Step S1407: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10 used by the limited clerk. Then, the process proceeds to step S1410.

[0335] Step S1412: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1413. Step S1413: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10 used by the limited clerk. Then, this flowchart ends. Step S1414: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1415. Step S1415: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10 used by the limited clerk. Then, this flowchart ends. Step S1416: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1417. Step S1417: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10 used by the limited clerk. Then, this flowchart ends.

[0336] (Explanation of the flowchart in Figure 31) The flowchart in Figure 31 shows details of the receipt paper monitoring process (step S54 in the flowchart in Figure 15), which is applied in place of the flowchart in Figure 22. Steps S1420 and S1421 in the flowchart in Figure 31 are the same as steps S420 and S421 in the flowchart in Figure 22, so a description of them will be omitted.

[0337] Step S1424: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1425. Step S1425: The settlement device 20 transmits the monitoring result information (non-receipt) to the registration device 10 used by the authorized store clerk. Then, this flowchart ends.

[0338] Step S1426: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10, which is normally used by the store clerk. Then, the process proceeds to step S1427. Step S1427: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10 used by the authorized clerk. Then, this flowchart ends.

[0339] (Fourth embodiment) Next, as a fourth embodiment, a mode will be described in which the registration device 10 used by the restricted clerk displays an operation confusion button and an operation preparation button. That is, in the third embodiment, the registration device 10 used by the restricted clerk did not display an operation confusion button or an operation preparation button, but in the fourth embodiment, the registration device 10 used by the restricted clerk displays an operation confusion button and an operation preparation button. Note that the network configuration, the configuration of each device, etc. in the fourth embodiment are the same as those in the first embodiment already described, and therefore, the description of the parts common to the first embodiment will be omitted in part or in whole.

[0340] Figures 32 and 23 are flowcharts showing an example of the operation of the settlement device 20 in the fourth embodiment. Specifically, Figure 32(A) replaces the dashed frame P5 in Figure 26(B) of the third embodiment. Figure 32(B) replaces the dashed frame P6 in Figure 27 of the third embodiment. Figure 33(A) replaces the dashed frame P7 in Figure 28 of the third embodiment. Figure 33(B) replaces the dashed frame P8 in Figure 29 of the third embodiment.

[0341] (Flowchart of Figure 32(A)) As will be described below, the flowchart of Figure 32(A) differs from the flowchart of Figure 26(B) in that it includes the processes of steps S1226 and S1228. Steps S1226 and S1228 will be described below.

[0342] Step S1226: Following step S1225, the settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1227.

[0343] Step S1228: Following step S1227, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 used by the restricted store clerk. Then, this flowchart ends. (Flowchart of Figure 32(B)) As will be described below, the flowchart in Figure 32(B) differs from the flowchart in Figure 27 in that it includes the processes of steps S1312 and S1314. Steps S1312 and S1314 will be described below.

[0344] Step S1312: Following step S1311, the settlement device 20 transmits the monitoring result information (non-operation preparation behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1313. Step S1314: Following step S1313, the settlement device 20 transmits the monitoring result information (non-operational hesitant behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1315.

[0345] (Flowchart of Figure 33(A)) As will be described below, the flowchart in Figure 33(A) differs from the flowchart in Figure 28 in that it includes the processes of steps S1327, S1335, and S1336. Steps S1327, S1335, and S1336 will be mainly described below.

[0346] Step S1327: Following step S1326, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1330.

[0347] Step S1330: The settlement device 20 determines whether the time before operation preparatory behavior determination, which began to be measured in step S1321, is equal to or longer than the second determination time (e.g., 30 seconds) for determining the time before operation preparatory behavior determination. If the time before operation preparatory behavior determination is equal to or longer than the second determination time (step S1330: YES), the process proceeds to step S1331. If the time before operation preparatory behavior determination is not equal to or longer than the second determination time (step S1330: NO), the process ends.

[0348] Step S1335: Following step S1331, the settlement device 20 determines whether the time before operation preparatory behavior determination, which began to be measured in step S1321, is equal to or longer than the first determination time (e.g., one minute) for determining the time before operation preparatory behavior determination. If the time before operation preparatory behavior determination is equal to or longer than the first determination time (step S1335: YES), proceed to step S1336. If the time before operation preparatory behavior determination is not equal to or longer than the first determination time (step S1335: NO), this flowchart ends.

[0349] Step S1336: The settlement device 20 transmits the monitoring result information (operation preparation behavior) to the registration device 10 used by the restricted store clerk. Then, this flowchart ends.

[0350] (Flowchart of Figure 33(B)) As will be described below, the flowchart in Figure 33(B) differs from the flowchart in Figure 29 in that it includes the processes of steps S1347, S1355, and S1356. Steps S1347, S1355, and S1356 will be mainly described below.

[0351] Step S1347: Following step S1346, the settlement device 20 transmits the monitoring result information (non-departure behavior) to the registration device 10 used by the restricted store clerk. Then, the process proceeds to step S1350.

[0352] Step S1350: The settlement device 20 determines whether the time before hesitant operation behavior determination, which began to be measured in step S1341, is equal to or longer than the second determination time (e.g., 20 seconds) for determining the time before hesitant operation behavior determination. If the time before hesitant operation behavior determination is equal to or longer than the second determination time (step S1350: YES), the process proceeds to step S1351. If the time before hesitant operation behavior determination is not equal to or longer than the second determination time (step S1350: NO), the process ends.

[0353] Step S1355: Following step S1351, the settlement device 20 determines whether the time before hesitant operation behavior determination, which began to be measured in step S1341, is equal to or longer than the first determination time (e.g., one minute) for determining the time before hesitant operation behavior determination. If the time before hesitant operation behavior determination is equal to or longer than the first determination time (step S1355: YES), the process proceeds to step S1356. If the time before hesitant operation behavior determination is not equal to or longer than the first determination time (step S1355: NO), the process ends.

[0354] Step S1356: The settlement device 20 transmits the monitoring result information (hesitant operation behavior) to the registration device 10 used by the restricted store clerk. Then, this flowchart ends.

[0355] In a configuration in which multiple registration devices 10 can transmit registration data to the same settlement device 20 (a configuration in which the status of a certain settlement device 20 can be monitored by multiple registration devices 10), the multiple registration devices 10 may be able to mutually confirm whether the other registration devices 10 are being used by a regular clerk (experienced clerk) or a limited clerk (inexperienced clerk). For example, in a configuration in which two registration devices 10 each can transmit registration data to three settlement devices 20 (e.g., a configuration in which two registration devices 10 are arranged so that their respective users are back-to-back), an experienced clerk may be able to support (follow) an inexperienced clerk. Therefore, each registration device 10 may display information (such as the clerk's name, job title, and whether the other registration device 10 is in use and the level of the clerk operating it) that allows the experienced clerk to recognize whether the other registration device 10 is in use and the level of the clerk operating it (such as the clerk's name, job title, leader, or trainer). This allows an experienced clerk to appropriately support an inexperienced clerk operating it. In addition, inexperienced store employees can easily confirm that there is someone nearby who can support them, which gives them peace of mind and allows them to concentrate more on their work.

[0356] (Fifth embodiment) Next, as a fifth embodiment, an embodiment will be described in which the notification mode (notification content, notification conditions, etc.) of information related to settlement (settlement device 20, customer using settlement device 20) is changed depending on the declaration (presence or absence of declaration). That is, in the first embodiment (second embodiment), the notification mode of information related to settlement differed depending on the device (type of device: transaction status management device 40 / registration device 10), and in the third embodiment (fourth embodiment), the notification mode of information related to settlement differed depending on the clerk (type of clerk: regular clerk / limited clerk). However, in the fifth embodiment, the notification mode of information related to settlement differs depending on the declaration (presence or absence of declaration). Note that the network configuration, configuration of each device, etc. in the fifth embodiment are similar to those in the first embodiment, etc., already described, and therefore, some or all of the description of the parts common to the first embodiment, etc. will be omitted.

[0357] (Declaration of Restrictions on Notification) The registration device 10 has two states: a state in which there are no restrictions on notification of information related to settlement (payment device 20, customer using payment device 20) (referred to as the "normal notification state" or "non-declaration state"), and a state in which notification of information related to settlement is restricted (referred to as the "notification restricted state", "restricted notification state", or "declaration state"). Depending on the store clerk's operation, the registration device 10 switches from the normal notification state (non-declaration state) to the notification restricted state (declaration state), and also switches from the notification restricted state (declaration state) to the normal notification state (non-declaration state).

[0358] 34 and 35 are display examples of the registration device 10 in the fifth embodiment. Specifically, Fig. 34 shows the display content of the small plan screen when the registration device 10 is in the normal notification state (non-declaration state). Fig. 35 shows the display content of the small plan screen when the registration device 10 is in the notification restricted state (declaration state).

[0359] In FIG. 34, "Normal Notification State (Non-Declaration State)" in the upper center of the settlement-related notification area HR10 indicates that the registration device 10 is in the normal notification state (non-declaration state). The notification restriction button BT80 in the upper left of the settlement-related notification area HR10 is a button that accepts a declaration to restrict notification of information related to settlement. A store clerk (a store clerk who registers products) operates the notification restriction button BT80 when, for example, he or she wants to concentrate on product registration work (product registration processing). For this reason, the notification restriction button BT80 may be referred to as, for example, a concentration button.

[0360] 35, the "Notification restricted state (declared state)" in the upper center of the settlement-related notification area HR10 indicates that the registration device 10 is in the notification restricted state (declared state). The restriction release button BT81 in the upper left of the settlement-related notification area HR10 is a button that accepts the release of the declaration that notification of information related to settlement is restricted.

[0361] When the notification restriction button BT80 is operated in the normal notification state shown in Fig. 34, the registration device 10 switches to the notification restriction state shown in Fig. 35. When the restriction release button BT81 is operated in the notification restriction state shown in Fig. 35, the registration device 10 switches to the normal notification state shown in Fig. 34.

[0362] In addition, when, for example, the number of 500-yen coins in the 201 register (settlement device 20a) is less than the first lower limit (step S2401 (YES) in Fig. 40 described later), the registration device 10 displays the near-end button BT32 in the settlement-related notification area HR10-1 (basic notification information) as shown in Fig. 34 when in the normal notification state, and displays the near-end button BT32 in the settlement-related notification area HR10-1 (basic notification information) when in the notification-restricted state, as shown in Fig. 35. In other words, when any coin is less than the first lower limit, the registration device 10 displays the near-end button BT32 whether in the normal notification state or the notification-restricted state.

[0363] Furthermore, in the 202 register (checkout device 20b), for example, when the number of 1,000 yen bills is less than the second lower limit but is equal to or greater than the first lower limit (all other coins are at least equal to or greater than the first lower limit) (step S2401 (NO) in FIG. 40 described later), the registration device 10 displays the near-end button BT32 in the settlement-related notification area HR10-2 (basic notification information) as shown in FIG. 34 when in the normal notification state, and does not display the near-end button BT32 in the settlement-related notification area HR10-2 (basic notification information) when in the notification-restricted state, as shown in FIG. 35. In other words, when any coin is less than the second lower limit but is equal to or greater than the first lower limit (all other coins are at least equal to or greater than the first lower limit), the registration device 10 displays the near-end button BT32 in the normal notification state, but does not display the near-end button BT32 in the notification-restricted state.

[0364] The same applies to the receipt button BT31 and near-full button BT33. For example, if the remaining amount of receipt paper in the 202 register (payment device 20b) is less than the first determination amount (step S2421 (YES) in FIG. 41, which will be described later), the registration device 10 will display the receipt button BT31 whether in the normal notification state or the notification limited state, as shown in FIGS. 34 and 35. However, if the remaining amount of receipt paper is less than the second determination amount but equal to or greater than the first determination amount (step S2421 (NO) in FIG. 41, which will be described later), the registration device 10 will display the receipt button BT31 in the normal notification state but will not display the receipt button BT31 in the notification limited state.

[0365] (Change of normal notification status / restricted notification status during a transaction) As shown in Figures 34 and 35, when, during a transaction (within one transaction), the normal notification state is switched to the notification restriction state based on the operation of the notification restriction button BT80, or when the notification restriction state is switched to the normal notification state based on the operation of the restriction release button BT81, the display (whether or not to display) of various notification buttons in the settlement-related notification area HR10 is immediately switched (without waiting for the transaction to end), but it may also be controlled, for example, as follows.

[0366] For example, when the notification limit button BT80 is operated (the same applies when the limit release button BT81 is operated), the registration device 10 notifies the settlement device 20 that the notification limit button BT80 has been operated (that the limit release button BT81 has been operated) or that the normal notification state has been switched to the notification limit state (that the notification limit state has been switched to the normal notification state), and when the settlement device 20 receives the above notification, it may execute the behavior monitoring process in Figures 37 to 39, the currency monitoring process in Figure 40, or the receipt monitoring process in Figure 41, which will be described later. The same applies to the sixth embodiment.

[0367] (Changing regular / restricted staff during a transaction) In the fifth embodiment (similar to the sixth embodiment), it was explained that when, during a transaction, the normal notification state is switched to the notification restriction state based on the operation of the notification restriction button BT80, or when the notification restriction state is switched to the normal notification state based on the operation of the restriction release button BT81, the display of various notification buttons in the settlement-related notification area HR10 is immediately switched, but the same may also be true in the above-mentioned third embodiment (similar to the fourth embodiment).

[0368] In other words, in the third embodiment (and the fourth embodiment as well), for example, when the user changes from a regular clerk to a restricted clerk (the same applies when the user changes from a restricted clerk to a regular clerk), the registration device 10 notifies the settlement device 20 that the user has changed from a regular clerk to a restricted clerk (that the user has changed from a restricted clerk to a regular clerk), and when the settlement device 20 receives the above notification, it may also execute the behavior monitoring process of Figures 27 to 29, the currency monitoring process of Figure 30, or the receipt monitoring process / currency monitoring process of Figure 31.

[0369] Note that Figures 34 and 35 explain the settlement-related notification area HR10 on the screen (subtotal screen) after operating the subtotal button BT10, but the same applies to the settlement-related notification area HR10 on the screen before operating the subtotal button BT10 (the registration screen (which may be the registration screen before one product item is registered, or the registration screen after at least one product item has been registered)). In other words, whether before or after operating the subtotal button BT10 (on either the registration screen or the subtotal screen), it is possible to switch from the normal notification state to the notification restriction state by operating the notification restriction button BT80, or to switch from the notification restriction state to the normal notification state by operating the notification cancellation button BT81.

[0370] The settlement device 20 can recognize whether each registration device 10 is in the normal notification state or the notification restricted state. For example, when the registration device 10 switches from the normal notification state to the notification restricted state, it may transmit information indicating that it has switched to the notification restricted state to the settlement device 20, and when it switches from the notification restricted state to the normal notification state, it may transmit information indicating that it has switched to the normal notification state to the settlement device 20.

[0371] (Operation of the registration device 10 in the fifth embodiment) The operation of the registration device 10 in the fifth embodiment is similar to the operation of the registration device 10 in the first embodiment (FIGS. 12 and 13). That is, the flowcharts in FIG. 12 and FIG. 13, which have been described as the operation of the registration device 10 in the first embodiment, are applied as the operation of the registration device 10 in the fifth embodiment. However, in the fifth embodiment, the registration device 10 transmits to the settlement device 20 information indicating that it has switched to the notification restricted state or information indicating that it has switched to the normal notification state.

[0372] (Operation of settlement device 20 in the fifth embodiment) The flowcharts in Figures 14 and 15, which were explained as the operation of the settlement device 20 in the first embodiment, are applied as the operation of the settlement device 20 in the third embodiment. The flowcharts in Figures 16 to 20 and 22, which were explained as the operation of the settlement device 20 in the first embodiment, are not applied as the operation of the settlement device 20 in the fifth embodiment. In the fifth embodiment, the flowcharts in Figures 36 to 41 below are applied instead of the flowcharts in Figures 16 to 20 and 22 of the first embodiment.

[0373] 36 to 41 are flowcharts showing an example of the operation of the settlement device 20 in the fifth embodiment.

[0374] (Flowchart of Figure 36(A)) The flowchart in FIG. 36(A) shows details of the usage status monitoring process (step S31 in the flowchart in FIG. 14) that is applied in place of the flowchart in FIG. 16(A).

[0375] Step S2200: The settlement device 20 transmits monitoring result information (in use state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2201. Step S2201: The settlement device 20 transmits monitoring result information (in use state) to the registration device 10 in the notification restricted state. Then, this flowchart ends.

[0376] (Flowchart of Figure 36(B)) Steps S2220 to S2222 in the flowchart of FIG. 36(B) are similar to steps S220 to S2222 in the flowchart of FIG. 16(B), and therefore a description thereof will be omitted.

[0377] Step S2223: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2224. Step S2224: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2225. Step S1225: The settlement device 20 transmits the monitoring result information (non-operation preparation action) to the registration device 10 in the normal notification state. Then, the process proceeds to step S1227. Step S1227: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 in the normal notification state. Then, this flowchart ends.

[0378] (Flowchart of Figure 36(C)) The flowchart in FIG. 36(C) shows details of the usage status monitoring process (step S57 in the flowchart in FIG. 15) that is applied in place of the flowchart in FIG. 16(C).

[0379] Step S2210: The settlement device 20 transmits monitoring result information (vacant state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2221. Step S2211: The settlement device 20 transmits the monitoring result information (vacant state) to the registration device 10 in the notification restricted state. Then, this flowchart ends.

[0380] (Explanation of the flowcharts in Figures 37 to 39) The flowcharts of Figures 37 to 39 show details of the behavior monitoring process (steps S33 and S36 of the flowchart of Figure 14, and steps S41, S50, and S55 of the flowchart of Figure 15) that are applied in place of the flowcharts of Figures 17 to 19. The flowchart of Figure 38 is a continuation of the flowchart of Figure 37. The flowchart of Figure 39 is a continuation of the flowchart of Figure 38.

[0381] Steps S2300 to S2310 in the flowchart of FIG. 37 are similar to steps S300 to S310 in the flowchart of FIG. 17, and therefore a description thereof will be omitted.

[0382] Step S2311: The settlement device 20 transmits monitoring result information (non-operation preparation action) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2313. Step S2313: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2315. Step S2315: The settlement device 20 transmits the monitoring result information (leaving behavior) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2316. Step S2316: The settlement device 20 transmits the monitoring result information (leaving behavior) to the registration device 10 in the notification restricted state. Then, this flowchart ends.

[0383] Steps S2320, S2321, S2322, S2325, and S2330 in the flowchart of FIG. 38 are similar to steps S320, S321, S322, S325, and S330 in the flowchart of FIG. 18, and therefore description thereof will be omitted.

[0384] Step S2323: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2324. Step S2324: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2325. Step S2326: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2330. Step S2331: The settlement device 20 transmits monitoring result information (operation preparation action) to the registration device 10 in the normal notification state. Then, this flowchart ends.

[0385] Steps S2341, S2342, S2345, and S2350 in the flowchart of FIG. 39 are similar to steps S341, S342, S345, and S350 in the flowchart of FIG. 19, and therefore description thereof will be omitted.

[0386] Step S2343: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2344. Step S2344: The settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2345. Step S2346: The settlement device 20 transmits the monitoring result information (non-operation preparation action) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2350. Step S2351: The settlement device 20 transmits the monitoring result information (hesitant operation behavior) to the registration device 10 in the normal notification state. Then, this flowchart ends.

[0387] (Explanation of the flowchart in Figure 40) The flowchart in Fig. 40 shows details of the currency monitoring process (step S49 in the flowchart in Fig. 15) that is applied in place of the flowchart in Fig. 20. Steps S2400, S2401, S2410, and S2411 in the flowchart in Fig. 40 are similar to steps S400, S401, S410, and S411 in the flowchart in Fig. 20, and therefore description thereof will be omitted.

[0388] Step S2402: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2403. Step S2403: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2410. Step S2404: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2405. Step S2405: The settlement device 20 transmits the monitoring result information (non-near-end state) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2410. Step S2406: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2407. Step S2407: The settlement device 20 transmits the monitoring result information (near-end state) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2410.

[0389] Step S2412: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2413. Step S2413: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10 in the notification restricted state. Then, this flowchart ends. Step S2414: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2415. Step S2415: The settlement device 20 transmits the monitoring result information (non-near-full state) to the registration device 10 in the notification restricted state. Then, this flowchart ends. Step S2416: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2417. Step S2417: The settlement device 20 transmits the monitoring result information (near-full state) to the registration device 10 used by the limited clerk. Then, this flowchart ends.

[0390] (Explanation of the flowchart in Figure 41) The flowchart in Figure 41 shows details of the receipt paper monitoring process (step S54 in the flowchart in Figure 15), which is applied in place of the flowchart in Figure 22. Steps S2420 and S2421 in the flowchart in Figure 41 are the same as steps S420 and S421 in the flowchart in Figure 22, so a description of them will be omitted.

[0391] Step S2424: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2425. Step S2425: The settlement device 20 transmits monitoring result information (non-receipt) to the registration device 10 in the notification restricted state, and then this flowchart ends.

[0392] Step S2426: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10 in the normal notification state. Then, the process proceeds to step S2427. Step S2427: The settlement device 20 transmits the monitoring result information (receipt) to the registration device 10 in the notification restricted state. Then, this flowchart ends.

[0393] (Sixth embodiment) Next, as a sixth embodiment, a mode in which the registration device 10 in the notification restricted state displays an operation confusion button and an operation preparation button will be described. That is, in the fifth embodiment, the registration device 10 in the notification restricted state did not display an operation confusion button and an operation preparation button, but in the sixth embodiment, the registration device 10 in the notification restricted state displays an operation confusion button and an operation preparation button. Note that the network configuration, the configuration of each device, etc. in the sixth embodiment are the same as those in the first embodiment already described, and therefore, the description of the parts common to the first embodiment will be omitted in part or in whole.

[0394] Figures 42 and 43 are flowcharts showing an example of the operation of the settlement device 20 in the sixth embodiment. Specifically, Figure 42(A) replaces the dashed frame P9 in Figure 36(B) of the fifth embodiment. Figure 42(B) replaces the dashed frame P10 in Figure 37 of the fifth embodiment. Figure 43(A) replaces the dashed frame P11 in Figure 38 of the fifth embodiment. Figure 43(B) replaces the dashed frame P12 in Figure 39 of the fifth embodiment.

[0395] (Flowchart of Figure 42(A)) As will be described below, the flowchart of Figure 42(A) differs from the flowchart of Figure 36(B) in that it includes the processes of steps S2226 and S2228. Steps S2226 and S2228 will be described below.

[0396] Step S2226: Following step S2225, the settlement device 20 transmits monitoring result information (non-operation preparation behavior) to the registration device 10 in the alarm state. Then, the process proceeds to step S2227.

[0397] Step S2228: Following step S2227, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 in the notification restricted state. Then, this flowchart ends. (Flowchart of Figure 42(B)) As will be described below, the flowchart in Figure 42(B) differs from the flowchart in Figure 37 in that it includes the processes of steps S2312 and S2314. Steps S2312 and S2314 will be described below.

[0398] Step S2312: Following step S2311, the settlement device 20 transmits monitoring result information (non-operation preparation behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2313. Step S2314: Following step S2313, the settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2315.

[0399] (Flowchart of Figure 43(A)) As will be described below, the flowchart in Figure 43(A) differs from the flowchart in Figure 38 in that it includes the processes of steps S2327, S2335, and S2336. Steps S2327, S2335, and S2336 will be mainly described below.

[0400] Step S2327: The settlement device 20 transmits the monitoring result information (non-operation hesitant behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2330.

[0401] Step S2330: The settlement device 20 determines whether the time before operation preparatory behavior determination, which began to be measured in step S2321, is equal to or longer than the second determination time (e.g., 30 seconds) for determining the time before operation preparatory behavior determination. If the time before operation preparatory behavior determination is equal to or longer than the second determination time (step S2330: YES), proceed to step S2331. If the time before operation preparatory behavior determination is not equal to or longer than the second determination time (step S2330: NO), this flowchart ends.

[0402] Step S2335: Following step S2331, the settlement device 20 determines whether the time before operation preparatory behavior determination, which began to be measured in step S2321, is equal to or greater than the first determination time (e.g., 1 minute) for determining the time before operation preparatory behavior determination. If the time before operation preparatory behavior determination is equal to or greater than the first determination time (step S2335: YES), proceed to step S2336. If the time before operation preparatory behavior determination is not equal to or greater than the first determination time (step S2335: NO), this flowchart ends.

[0403] Step S2336: The settlement device 20 transmits the monitoring result information (operation preparation action) to the registration device 10 in the notification restricted state. Then, this flowchart ends.

[0404] (Flowchart of Figure 43(B)) As will be described below, the flowchart of Figure 43(B) differs from the flowchart of Figure 39 in that it includes the processes of steps S2347, S2355, and S2356. Steps S2347, S2355, and S2356 will be mainly described below.

[0405] Step S2347: Following step S2346, the settlement device 20 transmits the monitoring result information (non-leaving behavior) to the registration device 10 in the notification restricted state. Then, the process proceeds to step S2350.

[0406] Step S2350: The settlement device 20 determines whether the time before hesitant operation behavior determination, which began to be measured in step S2341, is equal to or longer than the second determination time (e.g., 20 seconds) for determining the time before hesitant operation behavior determination. If the time before hesitant operation behavior determination is equal to or longer than the second determination time (step S2350: YES), proceed to step S2351. If the time before hesitant operation behavior determination is not equal to or longer than the second determination time (step S2350: NO), this flowchart ends.

[0407] Step S2355: Following step S2351, the settlement device 20 determines whether the time before hesitant operation behavior determination, which began to be measured in step S2341, is equal to or longer than the first determination time (e.g., one minute) for determining the time before hesitant operation behavior determination. If the time before hesitant operation behavior determination is equal to or longer than the first determination time (step S2355: YES), the process proceeds to step S2356. If the time before hesitant operation behavior determination is not equal to or longer than the first determination time (step S2355: NO), the process ends.

[0408] Step S2356: The settlement device 20 transmits the monitoring result information (hesitant operation behavior) to the registration device 10 in the notification restricted state. Then, this flowchart ends.

[0409] In addition, in a configuration in which multiple registration devices 10 can transmit registration data to the same settlement device 20, the multiple registration devices 10 may be able to mutually confirm whether the other registration devices 10 are in the normal notification state (non-declaration state) or the notification restricted state (declaration state). This makes it easy to implement an operation in which, for example, in a configuration in which two registration devices 10 are each able to transmit registration data to three settlement devices 20, the state of the other registration device 10 is checked (normal notification state, notification restricted state) so that both registration devices 10 do not enter the notification restricted state, and if the other registration device is in the notification restricted state, the own device is not placed in the notification restricted state. In addition, when the other registration device is in the notification restricted state, the own device may be controlled not to enter the notification restricted state (such as by disabling the central button). In other words, in a configuration in which multiple registration devices 10 can transmit registration data to the same settlement device 20, at least one of the multiple registration devices 10 may be controlled to enter the normal notification state.

[0410] The first to sixth embodiments have been described above. Figure 44 is an explanatory diagram summarizing the first to sixth embodiments. Figure 44(A) shows the content related to the first embodiment, Figure 44(B) shows the content related to the second embodiment, Figure 44(C) shows the content related to the third embodiment, Figure 44(D) shows the content related to the fourth embodiment, Figure 44(E) shows the content related to the fifth embodiment, and Figure 44(F) shows the content related to the sixth embodiment.

[0411] In Figures 44(A) to 44(F), "Display ◯" for the usage status indicates that the usage status (in use, available) of the settlement device 20 is displayed. "Display ◯" for the withdrawal button indicates that the withdrawal button (withdraw button BT43, withdraw button BT73) is displayed when the conditions are met.

[0412] "Display ◯" for the operation preparation button indicates that the operation preparation button (operation preparation button BT42, operation preparation button BT72) will be displayed when the condition is met. "Display △" for the operation preparation button indicates that the operation preparation button will be displayed when the condition (a condition that is less likely to be met than the condition for "Display ◯") is met. "-" for the operation preparation button indicates that the operation preparation button will not be displayed.

[0413] The "Display ◯" on the operation hesitation button indicates that the operation hesitation button (operation hesitation button BT41, operation preparation button BT72) will be displayed when the condition is met. The "Display △" on the operation hesitation button indicates that the operation hesitation button will be displayed when the condition (a condition that is less likely to be met than the condition for "Display ◯") is met. The "-" on the operation hesitation button indicates that the operation preparation button will not be displayed.

[0414] The "Display ◯" on the receipt button indicates that the receipt button (receipt button BT31, receipt button BT61) will be displayed when the condition is met. The "Display △" on the receipt button indicates that the receipt button (receipt button BT31, receipt button BT61) will be displayed when the condition (a condition that is less likely to be met than the condition for "Display ◯") is met. The same is true for the "Display ◯" and "Display △" on the near-end button and the "Display ◯" and "Display △" on the near-full button.

[0415] According to the first and second embodiments, notification of information related to settlement (settlement device 20, customer using settlement device 20) to the registration device 10 is more restricted (limited) than notification to the transaction status management device 40. Furthermore, the above restrictions are greater in the first embodiment than in the second embodiment.

[0416] As described above, in the first and second embodiments, the registration device 10 displays the receipt button BT31 ("Display △" in Figures 44(A) and (B)). However, the registration device 10 may not display the receipt button BT31 ("-" in Figure 44). The same applies to the near-end button BT32 and near-full button BT33. In other words, in the first and second embodiments, the registration device 10 may only display the usage status when it comes to information about the settlement device 20 (usage status, receipt paper need to be replenished, near-end status, near-full status). In other words, the notification of information about the settlement device 20 by the registration device 10 may be kept to a minimum necessary for transmitting registration data.

[0417] As described above, the first and second embodiments describe the case where the settlement device 20 transmits the monitoring result information to the registration device 10 and the transaction status management device 40. However, the device to which the settlement device 20 transmits the monitoring result information is not limited to the registration device 10 or the transaction status management device 40. For example, instead of or in addition to the transaction status management device 40, the settlement device 20 may transmit the monitoring result information to a mobile terminal (e.g., a smartphone or tablet terminal) used by a store clerk (basically used when not registering products) or to a signage (electronic advertising device) monitored by the store clerk. In other words, the first and second embodiments describe the case where the settlement device 20 transmits the monitoring result information to the registration device 10, which is a device used by the store clerk who registers products, and the transaction status management device 40, which is a device used by a store clerk other than the store clerk who registers products. However, the device used by the store clerk other than the store clerk who registers products is not limited to the transaction status management device 40 (it may be a mobile terminal or signage).

[0418] According to the third and fourth embodiments, notification of information related to settlement to the registration device 10 used by the limited clerk is more restricted (limited) than notification to the registration device 10 used by the normal clerk. Furthermore, the above-mentioned restrictions are greater in the third embodiment than in the fourth embodiment.

[0419] As described above, in the third and fourth embodiments, the registration device 10 used by the restricted clerk displays the receipt button BT31 ("Display △" in Figures 44(C) and (D)). However, the registration device 10 used by the restricted clerk may not display the receipt button BT31 ("-" in Figure 44). The same applies to the near-end button BT32 and near-full button BT33. In other words, in the third and fourth embodiments, the registration device 10 used by the restricted clerk may only display the usage status when it comes to information about the settlement device 20 (usage status, receipt paper need to be replenished, near-end status, near-full status). In other words, the notification of information about the settlement device 20 by the registration device 10 used by the restricted clerk may be kept to the minimum required for sending registration data.

[0420] 26 to 32, etc., did not mention notifications from the transaction status management device 40. However, for example, in the third and fourth embodiments, various types of monitoring result information may be transmitted to the transaction status management device 40 under the same conditions as the registration device 10 normally used by a store clerk. That is, in the third and fourth embodiments, various types of monitoring result information may be transmitted to the transaction status management device 40, as in the first embodiment. Furthermore, instead of or in addition to the transaction status management device 40, the settlement device 20 may transmit monitoring result information to a mobile terminal (e.g., a smartphone, tablet, etc.) used by a store clerk (basically used when no product is being registered) or to a signage (electronic announcement device) monitored by the store clerk.

[0421] According to the fifth and sixth embodiments, notification of information related to settlement to a registration device 10 in the notification restricted state is more restricted (limited) than notification to a registration device 10 in the normal notification state. Moreover, the above-mentioned restriction is greater in the fifth embodiment than in the sixth embodiment.

[0422] As described above, in the fifth and sixth embodiments, a registration device 10 in the notification restricted state displays the receipt button BT31 ("Display △" in Figures 44(E) and (F)). However, a registration device 10 in the notification restricted state may not display the receipt button BT31 ("-" in Figure 44). The same applies to the near-end button BT32 and the near-full button BT33. In other words, in the fourth and fifth embodiments, a registration device 10 in the notification restricted state may only display the usage status when it comes to information about the settlement device 20 (used status, receipt paper need to be replenished, near-end status, near-full status). In other words, notification of information about the settlement device 20 by a registration device 10 in the notification restricted state may be kept to the minimum required for sending registration data.

[0423] Furthermore, in the explanations of the fifth and sixth embodiments using Figures 34 to 42, etc., no mention was made of notifications by the transaction status management device 40. However, for example, in the fifth and sixth embodiments, various types of monitoring result information may be sent to the transaction status management device 40 under the same conditions as for the registration device 10 in the normal notification state. That is, in the fifth and sixth embodiments, various types of monitoring result information may be sent to the transaction status management device 40, as in the first embodiment. Furthermore, instead of or in addition to the transaction status management device 40, the settlement device 20 may send monitoring result information to a mobile terminal (e.g., a smartphone, tablet terminal, etc.) used by a store clerk (basically used when no product is registered) or to a signage (electronic announcement device) monitored by the store clerk.

[0424] (Screen name) In the above explanation, the screen before the subtotal button BT10 is operated is called the registration screen, and the screen after the subtotal button BT10 is operated is called the subtotal screen, but the names of the screens before and after the subtotal button BT10 may be the same. For example, the screen after the subtotal button BT10 is operated may be called the registration screen, just like the screen before the subtotal button BT10 is operated.

[0425] (Without subtotal button BT10) Although the above describes an embodiment in which the subtotal button BT10 is provided, an embodiment in which the subtotal button BT10 is not provided is also possible. In an embodiment in which the subtotal button BT10 is not provided, for example, after one item of merchandise has been registered, a checkout device designation button (such as the 201 register button BT21), a receipt button BT24, a coupon button BT25, etc. are displayed. Note that in an embodiment in which the subtotal button BT10 is not provided, there is no transition from the registration screen to the subtotal screen, and therefore the registration screen button BT26 is not necessary.

[0426] (Variation) The act of leaving may involve pretending to operate (input). In other words, the person may pretend to operate and then leave. Contactless input is effective in preventing this act of leaving.

[0427] Figures 45 and 46 are explanatory diagrams for explaining modified examples related to input. Figure 45 shows a first method, and Figure 46 shows a second method.

[0428] Figure 45(A) is a schematic diagram showing the settlement device 20 etc. as seen from the side. Figure 45(B) is a schematic diagram showing the settlement device 20 etc. as seen from further above the imaging unit 214. Figure 45(C) is an example of the display on the display unit 206. In Figures 45(A) and 45(B), the symbol T represents the customer's hand, and the symbol JM represents the top surface of the main body housing of the settlement device 20. The same is true for Figure 46.

[0429] As shown in Figures 45(A) and (B), when a customer brings their hand (in this example, all five fingers are extended, but specific fingers may be extended as in Figures 46(A) and (B)) close to the display screen of the display unit 206 (before touching the display screen), the settlement device 20 recognizes the hand from the image captured by the imaging unit 214, and grasps (estimates) the actual position of the hand (position in the left-right direction) from the captured position of the hand in the captured image, and accepts this as input of button C corresponding to the grasped position, as shown in Figure 45(C) (the thick frame in Figure 45(C) indicates that input has been made). The top surface JM of the main body housing may be a color or pattern that makes it easy to recognize the hand in the captured image.

[0430] The method shown in FIG. 45 uses one imaging unit 214 (camera), but to improve accuracy, two imaging units 214a and 214b may be used as shown in FIG.

[0431] As shown in Figures 46(A)(B), when a customer brings their hand (in this example, with the index finger extended, but all five fingers may be extended as in Figures 45(A)(B)) close to the display screen of the display unit 206 (before touching the display screen), the settlement device 20 recognizes the hand from each of the images captured by the imaging units 214a, b, and grasps (estimates) the actual position of the hand from the image position (position in the up, down, left, and right directions) of the hand in each of the images, and accepts it as input of button F corresponding to the grasped position, as shown in Figure 46(C) (the bold frame in Figure 46(F) indicates that input has been made).

[0432] In the examples of Figures 45 and 46, the settlement device 20 may grasp (estimate) the actual position of the hand (up, down, left, and right positions) based on the imaging range (area) of the hand and the distance (distance measurement) from the hand in addition to the imaging position of the hand in the captured image.

[0433] The contactless input method shown in Figures 45 and 46 can prevent people from leaving the facility. Furthermore, this input method also has the effect of improving hygiene and preventing disease.

[0434] The above describes the embodiments, but the above embodiments are merely examples and the specific configurations are not limited to the above embodiments, and also include designs within the scope of the invention that do not deviate from the gist of the invention.

[0435] For example, in the flowchart of FIG. 18 of the first embodiment, the process of step S326 (process of transmitting monitoring result information (non-operation hesitant behavior)) may be omitted. In the flowchart of FIG. 18, when the state before the operation preparatory behavior determination is recognized (for example, between step S320 (YES) and step S330), the monitoring result information (non-operation hesitant behavior) is immediately transmitted as it does not correspond to the operation hesitant behavior, but it may be considered as an operation preparatory behavior for a moment (taking into consideration the possibility of returning to the operation hesitant behavior a moment later), and the monitoring result information (non-operation hesitant behavior) may not need to be transmitted. The same applies to the other embodiments.

[0436] In the flowchart of Fig. 19 of the first embodiment, the process of step S346 (process of transmitting monitoring result information (non-operation preparatory action)) may be omitted. In the flowchart of Fig. 19, at the point when the pre-operation preparatory action determination state is not recognized (for example, between step S320 (NO) and step S350), the monitoring result information (non-operation preparatory action) is immediately transmitted as it does not correspond to the operation preparatory action, but it is also possible not to transmit the monitoring result information (non-operation preparatory action) as it is a momentary non-correspondence (taking into consideration the possibility of returning to the operation preparatory action a moment later). The same applies to the other embodiments.

[0437] In the flowchart of Fig. 17 of the first embodiment, when the state before the departure behavior determination is recognized (between step S300 (YES) and step S310), the operation departure behavior is considered to be a momentary operation departure behavior (taking into consideration the possibility that the behavior may return to an operation hesitation behavior or an operation preparation behavior a moment later), and the monitoring result information (non-operation departure behavior) and the monitoring result information (non-operation hesitation behavior) are not transmitted, but when the state before the departure behavior determination is recognized, the monitoring result information (non-operation departure behavior) and the monitoring result information (non-operation hesitation behavior) may be transmitted. The same applies to the other embodiments.

[0438] In the first embodiment (and other embodiments as well), the determination time for determining the time before determining the leaving behavior is constant (for example, 5 seconds), but it may be varied depending on the timing (which of the behavior monitoring processes in steps S33, S36, S41, S50, and S55 is being performed). For example, the length of the behavior monitoring process in the first step S33 may be set taking into consideration the travel time from the registration device 10 to the settlement device 20. The length may also be varied depending on the complexity of the screen (the more complex the screen, the longer the screen). The length may also be varied depending on the customer (the more favorable the customer, the longer the screen). The same applies to other determination times (the determination time for determining the time before determining the preparatory behavior for operation, the determination time for determining the time before determining the hesitant behavior for operation). The same applies to other embodiments.

[0439] In the second embodiment (and also in the fourth and sixth embodiments), an image button is not displayed in the scene of the notification regarding hesitant operation behavior (FIGS. 23(A)(B)) or the scene of the notification regarding operation preparation behavior (FIGS. 23(A)(B)). However, an image button may also be displayed in the scene of the notification regarding hesitant operation behavior or the scene of the notification regarding operation preparation behavior, similar to the scene of the notification regarding leaving operation behavior (FIGS. 10(A)(B)). In other words, the transaction status management device 40 displays an image button (image button BT78 in FIG. 6) in the scene of the notification regarding leaving operation behavior, hesitant operation behavior, or the scene of the notification regarding operation preparation behavior. However, similar to the transaction status management device 40, an image button may also be displayed in the scene of the notification regarding leaving operation behavior, hesitant operation behavior, or the scene of the notification regarding operation preparation behavior, similar to the transaction status management device 40.

[0440] In the third embodiment (and the fourth embodiment as well), the settlement device 20 was described as being capable of recognizing whether the clerk using each device (registration device 10, transaction status management device 40) is a regular clerk or a restricted clerk. However, in addition to the settlement device 20, the transaction status management device 40 (as well as the mobile terminal used by the clerk and the signage monitored by the clerk) may also be configured to be capable of recognizing whether the clerk using each device (registration device 10) is a regular clerk or a restricted clerk. The transaction status management device 40 (as well as the mobile terminal and signage) may also display information indicating whether the clerk using each device (registration device 10) is a regular clerk or a restricted clerk. For example, the transaction status management device 40 (as well as the mobile terminal used by the clerk and the signage monitored by the clerk) may display a mark, character string, icon, or the like in a display area (see FIG. 6 ) corresponding to each registration device 10, indicating whether the user is a regular clerk or a restricted clerk.

[0441] In the example shown in FIG. 6, the transaction status management device 40 displays each registration device 10 in a predetermined order (in FIG. 6, the order is 201 register → 202 register → 203 register) regardless of the type of clerk using it (regular clerk / restricted clerk). However, the transaction status management device 40 (as well as the mobile terminals used by the clerks and the signage monitored by the clerks) may display each registration device 10 based on the type of clerk using it (regular clerk / restricted clerk). For example, the transaction status management device 40 may preferentially display (in a prominent position, for example, at the top) registration devices 10 used by restricted clerks (or conversely, may preferentially display registration devices 10 used by regular clerks). Furthermore, the transaction status management device 40 may provide separate screens (pages) for registration devices 10 used by regular clerks and registration devices 10 used by restricted clerks, allowing the screens to be switched using a selection area (so-called tabs) or a switching button. This allows for centralized management of the registration devices 10 used by restricted store clerks (or regular store clerks).

[0442] In the fifth embodiment (similar to the sixth embodiment), the settlement device 20 is described as being capable of recognizing whether each registration device 10 is in the normal notification state or the notification restriction state. However, in addition to the settlement device 20, the transaction status management device 40 (as well as the mobile terminal used by the store clerk and the signage monitored by the store clerk) may also be configured to be capable of recognizing whether each registration device 10 is in the normal notification state or the notification restriction state. The transaction status management device 40 (as well as the mobile terminal and signage) may display information indicating whether each registration device 10 is in the normal notification state or the notification restriction state. For example, the transaction status management device 40 (as well as the mobile terminal used by the store clerk and the signage monitored by the store clerk) may display a mark, character string, icon, or the like in a display area (see FIG. 6) corresponding to each registration device 10, indicating whether each registration device 10 is in the normal notification state or the notification restriction state.

[0443] Furthermore, the transaction status management device 40 (as well as the mobile terminals used by store clerks and the signage monitored by store clerks) may display information about each registration device 10 based on its respective status (normal notification status / restricted notification status). For example, the transaction status management device 40 or the like may preferentially display registration devices 10 in the restricted notification status (or conversely, may preferentially display registration devices 10 in the normal notification status). Furthermore, the transaction status management device 40 or the like may provide separate screens for registration devices 10 in the normal notification status and registration devices 10 in the restricted notification status, and may enable switching between the screens using a selection area or a switching button. This allows for centralized management of registration devices 10 in the restricted notification status (or normal notification status).

[0444] (Settlement-related notification area HR10) In the third embodiment (as well as the fourth to sixth embodiments), the size of the settlement-related notification area HR10 may be varied depending on the number of notification buttons displayed in the settlement-related notification area HR10 (it may be displayed larger if the number is large and smaller if the number is small).

[0445] In the fifth embodiment (similar to the sixth embodiment), the size of the settlement-related notification area HR10 is the same whether the device is in the normal notification state or the notification-restricted state (FIGS. 34 and 35), but the size of the settlement-related notification area HR10 may be smaller when the device is in the notification-restricted state than when the device is in the normal notification state. Also, in the third embodiment (similar to the fourth embodiment), the size of the settlement-related notification area HR10 may be the same whether the device is being used by a normal clerk or a restricted clerk, or the size of the settlement-related notification area HR10 may be smaller when the device is being used by a restricted clerk than when the device is being used by a normal clerk.

[0446] In the fifth embodiment (similar to the sixth embodiment), the notification limit button BT80 (remove limit button BT81) is displayed in the settlement-related notification area HR10, but it may be displayed in another location. For example, the notification limit button BT80 (remove limit button BT81) may be displayed at the top of the screen (for example, near "Store Clerk: AAA" in Figures 34 and 35). Furthermore, the notification limit button BT80 (remove limit button BT81) may be displayed on a screen (login screen, settings screen) different from the screen (registration screen, small plan screen) on which the settlement-related notification area HR10 is provided.

[0447] In the above embodiments (first to sixth embodiments), a settlement-related notification area HR10 is provided in addition to the display area (the area at the bottom right of the screen in the examples of FIGS. 9, 34, and 35) that displays the settlement device designation button (the 201 register button BT21, etc.) and the checkout button BT24 (that is, the settlement device designation button, etc., and various notification buttons, etc., are arranged separately on the screen), but the display (arrangement) of the buttons is one example. For example, various notification buttons, etc. related to the 201 register (payment device 20a) may be arranged near the 201 register button BT21 that designates the 201 register, and various notification buttons, etc. related to the 202 register (payment device 20b) may be arranged near the 202 register button BT22 that designates the 202 register. For example, as an example of maintaining the settlement-related notification area HR10, the 201 register button BT21 may be placed in the settlement-related notification area HR10-1 for the 201 register, and the 202 register button BT22 may be placed in the settlement-related notification area HR10-2 for the 202 register. Note that the checkout button BT24 and gift certificate button BT25 are not buttons related to a specific settlement device 20, and therefore are not placed in the settlement-related notification area HR10-1 or the settlement-related notification area HR10-2 (they may be placed in areas of the settlement-related notification area HR10 that do not belong to the settlement-related notification area HR10-1 or the settlement-related notification area HR10-2).

[0448] (Changing regular / restricted staff during a transaction (another example)) In the third embodiment (and the fourth embodiment as well), when the user of the registration device 10 changes from a regular clerk to a restricted clerk during a transaction (within one transaction) (the same applies when the user changes from a restricted clerk to a regular clerk), the registration device 10 immediately (without waiting for the transaction to end) changes the display of the various notification buttons in the settlement-related notification area HR10 to a display that corresponds to the changed user.As a method of changing the display of the various notification buttons in the settlement-related notification area HR10 to a display that corresponds to the changed user, when the user changes from a regular clerk to a restricted clerk (the same applies when the user changes from a restricted clerk to a regular clerk), the registration device 10 notifies the settlement device 20 that the user has changed from a regular clerk to a restricted clerk (the user has changed from a restricted clerk to a regular clerk), and the settlement device 20, upon receiving the above notification, may execute behavior monitoring processing, currency monitoring processing, receipt monitoring processing, and currency monitoring processing. However, when the user of the registration device 10 changes from a regular clerk to a restricted clerk during a transaction (the same applies when the user changes from a restricted clerk to a regular clerk), the method of immediately changing the display of the various notification buttons in the settlement-related notification area HR10 to correspond to the changed user is not limited to this method.

[0449] For example, the settlement device 20 may send two pieces of monitoring result information to the registration device 10, one for regular store clerks and one for restricted store clerks, regardless of whether the user of the registration device 10 is a regular store clerk or a restricted store clerk.

[0450] As an example, in the currency monitoring process (Figure 30), if any currency is less than the first lower limit number (step S1401 (YES) in Figure 30), the settlement device 20 sends two pieces of monitoring result information to the registration device 10: monitoring result information for regular clerk (near-end state) and monitoring result information for limited clerk (near-end state); and if any currency is less than the second lower limit number but is equal to or greater than the first lower limit number (all other currency is at least equal to or greater than the first lower limit number) (step S1401 (NO) in Figure 30), the settlement device 20 sends two pieces of monitoring result information to the registration device 10: monitoring result information for regular clerk (near-end state) and monitoring result information for limited clerk (not near-end state).

[0451] As another example, in the receipt paper monitoring process (Figure 31), if the remaining amount of receipt paper is less than the first judgment amount (step S1421 (YES) in Figure 31), the settlement device 20 sends two pieces of monitoring result information to the registration device 10: monitoring result information (receipt) for regular clerks and monitoring result information (receipt) for restricted clerks; and if the remaining amount of receipt paper is less than the second judgment amount but equal to or greater than the first judgment amount (step S1421 (NO) in Figure 31), the settlement device 20 sends monitoring result information (receipt) for regular clerks and monitoring result information (non-receipt) for restricted clerks to the registration device 10.

[0452] The registration device 10 that receives the two pieces of monitoring result information may store the two pieces of monitoring result information received, regardless of whether the current user is a regular clerk or a restricted clerk, and may refer to either one of the pieces of monitoring result information corresponding to the current user (ignoring the other monitoring result information) to control the display of various notification buttons in the settlement-related notification area HR10, and when the user changes, may refer again to either one of the monitoring result information corresponding to the new user to control the display of various notification buttons in the settlement-related notification area HR10. Note that instead of transmitting two pieces of monitoring result information, one for regular clerks and one for restricted clerks, to the registration device 10, the settlement device 20 may transmit one common monitoring result information including information for regular clerks and information for restricted clerks. In this case, the registration device 10 stores the received common monitoring result information, and refers to either the information for regular store clerks or the information for restricted store clerks contained in the common monitoring result information that corresponds to the current user (ignoring the other information), and controls the display of various notification buttons in the settlement-related notification area HR10.If the user changes, the registration device 10 may again refer to either the information for regular store clerks or the information for restricted store clerks contained in the common monitoring result information that corresponds to the new user, and control the display of various notification buttons in the settlement-related notification area HR10.

[0453] (Changing normal notification status / restricted notification status during a transaction (another example)) In the fifth embodiment (similar to the sixth embodiment), when the registration device 10 switches from a normal notification state to a limited notification state (the same applies when switching from a limited notification state to a normal notification state) during a transaction (within one transaction), as a method of immediately (without waiting for the end of the transaction) changing the display of the various notification buttons in the settlement-related notification area HR10 to a display according to the changed state, when the notification limit button BT80 is operated (the same applies when the limit release button BT81 is operated), the registration device 10 notifies the settlement device 20 that the notification limit button BT80 has been operated (that the limit release button BT81 has been operated) or that the normal notification state has been switched to the limited notification state (that the notification limit state has been switched to the normal notification state), and the settlement device 20 that receives the above notification may execute behavior monitoring processing, currency monitoring processing, receipt monitoring processing, or currency monitoring processing. However, when the registration device 10 switches from the normal notification state to the notification restriction state during a transaction (the same applies when the registration device 10 switches from the notification restriction state to the normal notification state), the method of immediately changing the display of the various notification buttons in the settlement-related notification area HR10 to correspond to the changed state is not limited to this method.

[0454] For example, the settlement device 20 may send two pieces of monitoring result information to the registration device 10, namely, monitoring result information for the normal notification state and monitoring result information for the notification restriction state, regardless of whether the registration device 10 is in the normal notification state or the notification restriction state.

[0455] As an example, in the currency monitoring process (Figure 40), if any currency is less than the first lower limit number (step S2401 (YES) in Figure 40), the settlement device 20 transmits two pieces of monitoring result information to the registration device 10: monitoring result information for the normal alarm state (near-end state) and monitoring result information for the alarm limited state (near-end state); and if any currency is less than the second lower limit number but is equal to or greater than the first lower limit number (all other currency is at least equal to or greater than the first lower limit number) (step S2401 (NO) in Figure 40), the settlement device 20 transmits two pieces of monitoring result information to the registration device 10: monitoring result information for the normal alarm state (near-end state) and monitoring result information for the alarm limited state (non-near-end state).

[0456] As another example, in the receipt paper monitoring process (Figure 41), if the remaining amount of receipt paper is less than the first judgment amount (step S2421 (YES) in Figure 41), the settlement device 20 sends two pieces of monitoring result information to the registration device 10: monitoring result information for the normal notification state (receipt) and monitoring result information for the notification restricted state (receipt); and if the remaining amount of receipt paper is less than the second judgment amount but greater than or equal to the first judgment amount (step S2421 (NO) in Figure 41), the settlement device 20 sends monitoring result information for the normal notification state (receipt) and monitoring result information for the notification restricted state (non-receipt) to the registration device 10.

[0457] The registration device 10 that has received the above two pieces of monitoring result information may store the two pieces of monitoring result information it has received, regardless of whether the current state is the normal notification state or the notification restricted state, and may refer to either one of the monitoring result information corresponding to the current state (ignoring the other monitoring result information) to control the display of various notification buttons in the settlement-related notification area HR10, and when the state switches, may refer again to either one of the monitoring result information corresponding to the changed state to control the display of various notification buttons in the settlement-related notification area HR10. Note that instead of transmitting two pieces of monitoring result information, namely, monitoring result information for the normal notification state and monitoring result information for the notification restricted state, to the registration device 10, the settlement device 20 may transmit one common monitoring result information including information for the normal notification state and information for the notification restricted state. In this case, the registration device 10 stores the received common monitoring result information, and refers to either the information for the normal notification state or the information for the notification restriction state contained in the common monitoring result information that corresponds to the current state (ignoring the other information), and controls the display of various notification buttons in the settlement-related notification area HR10, and when the state changes, refers again to either the information for the normal notification state or the information for the notification restriction state contained in the common monitoring result information that corresponds to the changed state, and controls the display of various notification buttons in the settlement-related notification area HR10.

[0458] (Regarding images) Furthermore, in the above embodiment, the settlement device 20 is equipped with an imaging unit 214 (camera), but the settlement device 20 does not have to be equipped with a camera as long as it is capable of capturing images of customers using the settlement device 20. For example, a camera may be installed on the ceiling, wall, pillar, etc. of the store. That is, a camera may be installed on the ceiling, wall, pillar, etc. instead of or in addition to the camera of the settlement device 20. The camera may be installed in a device having the function of determining customer behavior, or in a device separate from the device having the function of determining customer behavior.

[0459] The timing at which video recording by a camera (the imaging unit 214 of the settlement device 20 or another camera) starts is, for example, the timing at which the registration device 10 transmits the registration data (the timing at which the settlement device 20 receives the registration data). When cameras are installed on a ceiling, wall, pillar, etc., the registration device 10 may instruct the cameras installed on the ceiling, wall, pillar, etc. to start recording when it transmits the registration data, or the settlement device 20 may instruct the cameras installed on the ceiling, wall, pillar, etc. to start recording when it receives the registration data. The timing at which video recording by a camera ends is, for example, the timing at which the settlement device 20 transmits the settlement data (the timing at which the store controller 30 receives the settlement data). When cameras are installed on a ceiling, wall, pillar, etc., the settlement device 20 may instruct the cameras installed on the ceiling, wall, pillar, etc. to stop recording when it transmits the settlement data, or the store controller 30 may instruct the cameras installed on the ceiling, wall, pillar, etc. to stop recording when it receives the settlement data.

[0460] For videos, items such as the machine number (the device identification number of the settlement device 20), transaction number, recording start time, and recording end time may be saved (stored) as indexes, so that videos can be searched using each item stored as an index. For example, a search range may be specified for each item. For still images, items such as the machine number, transaction number, and image capture time may be saved (stored) as indexes, so that still images can be searched using each item stored as an index. Note that videos and still images may be stored in association with each other, so that one can be searched for the other (related to the same transaction).

[0461] Furthermore, various timings in the settlement device 20 may be set as indexes in the video. For example, the timing at which the settlement device 20 starts executing the initialization process (i.e., the timing of the customer's operations and actions on the settlement device 20) may be set as indexes in the video. This allows the registration device 10 (and the transaction status management device 40) to play videos by specifying operations and actions. For example, the registration device 10 (and the transaction status management device 40) can request the settlement device 20 to play a video of the operation of the Finish button (the Finish (Receipt) button BT54 (step S42 (YES) in FIG. 15) to the removal of the receipt (step S42 (NO) in FIG. 15).

[0462] The video (and still images) captured by the settlement device 20 allows the customer (e.g., a customer who has left) to visually recognize external features such as their face, physique, and clothing. By playing the video (and still images) on the registration device 10 and the transaction status management device 40, the store clerk can easily confirm the external features of the customer who has left, etc.

[0463] Alternatively, video (or still images) may be analyzed to extract the external characteristics and display marks, character strings, icons, etc. corresponding to the extracted characteristics. The device that displays the marks, etc. may perform the analysis (extraction of external characteristics), or a device different from the device that displays the marks, etc. may perform the analysis. In other words, the registration device 10 may display marks, etc. corresponding to the external characteristics of a customer based on the analysis results of its own device or another device (another registration device 10, a settlement device 20, a transaction status management device 40, a store controller 30, an external server, etc.). The transaction status management device 40 may display marks, etc. corresponding to the external characteristics of a customer based on the analysis results of its own device or another device (a registration device 10, a settlement device 20, a store controller 30, an external server, etc.). The registration device 10 (transaction status management device 40) may display marks or the like corresponding to the customer's external features in association with the video (still image) being played, or may display marks or the like corresponding to the customer's external features in association with buttons (image button BT78, still image button BT46, video button BT47) before playback. Also, the extracted external features may be saved (stored) as an index so that the video (still image) can be searched.

[0464] In the present embodiment (first to sixth embodiments), as shown in FIG. 9, for example, registration data can be transmitted to an idle settlement device 20 but not to an in-use settlement device 20. However, registration data may also be transmitted to an in-use settlement device 20. In other words, in the present embodiment, transmission of a customer's registration data to a settlement device 20 in use by the previous customer is prohibited (for example, in FIG. 9, operation of the 202 register button BT22, which specifies the in-use register 202, is disabled), but transmission of the customer's registration data to a settlement device 20 in use by the previous customer may be permitted. On the other hand, when the settlement device 20 receives registration data while in use, it buffers (stores in RAM 203) the registration data in order as it receives it, and sequentially retrieves the buffered registration data each time a transaction (payment process) is completed to start a new transaction. That is, in this embodiment, the maximum number of duplicate transmissions of registered data to the same settlement device 20 (maximum number of duplicate receptions of registered data at the settlement device 20) is fixed to 1, but the maximum number of duplicate transmissions (maximum number of duplicate receptions) may be set to 2 or more. The maximum number of duplicate transmissions (maximum number of duplicate receptions) may be changeable for each settlement device 20 by setting.

[0465] Although it has been explained that the start timing of video recording may be the timing of registration data transmission by the registration device 10 (the timing of registration data reception by the settlement device 20), if the maximum number of overlapping transmissions of registration data (maximum number of overlapping receptions) is two or more, the settlement device 20 may receive registration data while in use. In other words, the timing to start recording a video for a new transaction may arrive while video recording for another transaction is in progress. In this case, the currently recorded video continues to be recorded, and a new video recording for the new transaction is not started. However, the start time of the video recording for the new transaction may be stored as an index in the currently recorded video, and may be searchable as the start timing of recording the new transaction. In this way, even if the maximum number of overlapping transmissions of registration data (maximum number of overlapping receptions) is two or more, management is based on the timing of registration data transmission by the registration device 10 (the timing of registration data reception by the settlement device 20).

[0466] (Example when the maximum number of duplicate transmissions (maximum number of duplicate receptions) is 2) Time T1: Transaction A registration data is received during an idle state. Recording begins. This time (time T1) is stored (indexed) as the recording start time for Transaction A. Time T2: During use, the registration data for Transaction B is received and buffered. This time (time T2) is stored (indexed) as the recording start time for Transaction B. Time T3: Settlement data for Transaction A is sent. This time (time T3) is stored (indexed) as the end time of recording for Transaction A. Time T4: The registered data for Transaction B is retrieved from the buffer and Transaction B is started. This time (Time T4) is stored (indexed) as the start time of Transaction B. Time T5: Settlement data for Transaction B is sent. This time (time T5) is stored (indexed) as the end time of recording for Transaction B. This allows searching and playing back the video from time T1 to time T3 as the video of transaction A. Also, searching and playing back the video from time 2 (or time T4) to time T5 as the video of transaction B.

[0467] (Other entities) All or part of the functions (input / output, memory, processing (including judgment)) of each device described above (registration device 10, settlement device 20, store controller 30, transaction status management device 40) may be possessed by an entity (another device) different from the entity described above.

[0468] In the above embodiment, an example was described in which the settlement device 20 controls the destination of the monitoring result information so that information related to settlement (the settlement device 20, the customer using the settlement device 20) becomes "Display ◯", "Display △", or "-" as shown in Figure 44. However, if it becomes as shown in Figure 44, the settlement device 20 does not need to control the destination of the monitoring result information. For example, the sending side (the settlement device 20) may not control the destination, but the receiving side (the transaction status management device 40, the registration device 10) may control it.

[0469] For example, in the first and second embodiments, the settlement device 20 controls the destination (transaction status management device 40, registration device 10) of the monitoring result information so that it becomes "Display ○", "Display △", or "-" as shown in Figures 44(A) and (B), but the settlement device 20 may send the monitoring result information to both the transaction status management device 40 and the registration device 10 at the same time (or send common monitoring result information), and the transaction status management device 40 or the registration device 10 may decide whether to accept or reject the monitoring result information (whether to reflect it or not).

[0470] The settlement device 20 may transmit monitoring result information that includes information for the receiving side (transaction status management device 40, registration device 10) to determine whether to accept or reject (for example, this may be direct information such as information addressed to the transaction status management device 40 or the registration device 10, or details of the determination result (for example, in the case of a near-end state, information indicating whether the state is near-end below the second lower limit or near-end below the first lower limit). As an example, we will supplement the above-mentioned mode of transmitting and receiving monitoring result information (near-end state) that includes information indicating whether the state is near-end below the second lower limit or near-end below the first lower limit. When the settlement device 20 determines that any coin is below the second lower limit number but not below the first lower limit number (step S401 (NO) in Figure 20), the settlement device 20 will transmit monitoring result information that includes information indicating whether the state is near-end below the second lower limit or near-end below the first lower limit. The settlement device 20 then transmits monitoring result information indicating that the balance is near-end (near-end state) to the transaction status management device 40 and the registration device 10. Based on the monitoring result information, the transaction status management device 40 displays the near-end button BT62 ("Take" of the take / discard options), while the registration device 10 ignores the monitoring result information ("Discard" of the take / discard options) and does not display the near-end button BT32. Furthermore, when the settlement device 20 determines that any of the coins is below the first lower limit number (step S401 (YES) in FIG. 20), it transmits monitoring result information indicating that the balance is near-end and below the first lower limit (near-end state) to the transaction status management device 40 and the registration device 10. Based on the monitoring result information, the transaction status management device 40 displays the near-end button BT62 ("Take" of the take / discard options), while the registration device 10 displays the near-end button BT32 ("Take" of the take / discard options) based on the monitoring result information.

[0471] The same applies to the third to sixth embodiments. That is, in the third and fourth embodiments, the settlement device 20 controls the destination of the monitoring result information (the registration device 10 used by the regular clerk, the registration device 10 used by the restricted clerk) so as to display "◯", "△", or "-" as shown in Figures 44(C) and (D), but the settlement device 20 may transmit the monitoring result information to the registration device 10 used by the regular clerk and the registration device 10 used by the restricted clerk at the same time (or transmit common monitoring result information), and the registration device 10 used by the regular clerk or the registration device 10 used by the restricted clerk may decide whether to accept or reject the monitoring result information. Furthermore, in the fifth and sixth embodiments, the settlement device 20 controls the destination of the monitoring result information (the registration device 10 in the normal notification state and the registration device 10 in the notification restricted state) so as to display "◯", "△", or "-" as shown in Figures 44(E) and 44(F). However, the settlement device 20 may transmit the monitoring result information to both the registration device 10 in the normal notification state and the registration device 10 in the notification restricted state at the same time (or transmit common monitoring result information), and the registration device 10 in the normal notification state or the registration device 10 in the notification restricted state may decide whether to accept or reject the monitoring result information. Note that the contents described above in "Changing between normal clerk / restricted clerk during a transaction (another example)" and "Changing between normal notification state and notification restricted state during a transaction (another example)" are aspects in which the registration device 10 decides to accept or reject the monitoring result information.

[0472] Furthermore, in the above embodiment, an aspect has been described in which each settlement device 20 determines the behavior of a customer using its own device (performs behavior monitoring processing), but a settlement device 20 may also determine the behavior of a customer using another settlement device 20. In other words, the behavior of a customer using a certain settlement device 20 may be determined by another settlement device 20. For example, a predetermined representative settlement device 20 may determine the behavior of customers at multiple settlement devices 20, including its own device. In this case, the settlement devices 20 other than the representative send captured images of customers using their own devices to the representative settlement device 20.

[0473] In the above embodiment, the settlement device 20 determines customer behavior (performs behavior monitoring processing) based on captured images. However, the device having the function of determining customer behavior may be a device other than the settlement device 20. For example, the device having the function of determining customer behavior may be the transaction status management device 40 (or the store controller 30, or the registration device 10). That is, the transaction status management device 40 (or the store controller 30, or the registration device 10) may obtain captured images from the settlement device 20 and determine customer behavior. Note that the device having the function of determining customer behavior transmits various types of monitoring result information as needed. However, when the transaction status management device 40 determines customer behavior, it does not need to transmit the monitoring result information to itself (the transaction status management device 40). Also, when the registration device 10 determines customer behavior, it does not need to transmit the monitoring result information to itself (the registration device 10). (However, when the representative registration device 10 determines customer behavior, it is necessary to transmit the monitoring result information to the other registration devices 10.)

[0474] Furthermore, the device having the function of determining customer behavior may be a device different from the transaction status management device 40, the store controller 30, or the registration device 10 (hereinafter referred to as device A). Device A may be a device dedicated to determining customer behavior, or may be a device having functions other than the function of determining customer behavior. In other words, the POS system 1 may include device A (not shown), which acquires captured images from the settlement device 20 and determines customer behavior. Device A transmits various types of monitoring result information as necessary.

[0475] Furthermore, the registration device 10 (and similarly the settlement device 20) only provides an interface (screen display, operation reception, etc.) with the operator (store clerk, customer), and various judgments, generation of output information including display information, storage of information, etc. may be performed by a cloud server (not shown) or the like. For example, a device having the function of judging customer behavior may be a cloud server.

[0476] The embodiments will be summarized below. [Technical field] The present invention relates to a POS system. [Background technology] 2. Description of the Related Art A POS system including a POS register used by a store clerk and a POS settlement machine used by a customer is known (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2018-190067 A [Summary of the Invention] [Problem to be solved by the invention] However, when customers themselves operate the payment machine, there are operational problems and room for improvement. The present invention has been made in light of these circumstances, and its purpose is to provide technology that allows for more optimal operation. [Means for solving the problem]

[0477] (A1) In order to solve the above-mentioned problems, one aspect of the present invention is a POS system including a registration device where a store clerk registers products and a plurality of settlement devices where customers themselves settle their payments, and includes customer monitoring means (e.g., behavior monitoring processing) that monitors customer behavior at the settlement devices, and notification means (e.g., notification of a withdrawal button, operation preparation button, operation hesitation button, etc.) that can notify the store clerk of a specific behavior when the customer behavior monitored by the customer monitoring means is a specific behavior that requires notification to the store clerk (e.g., withdrawal behavior, operation preparation behavior, operation hesitation behavior, etc.). The specific actions include a first specific action having a high notification priority (e.g., withdrawal action) and a second specific action having a lower notification priority (e.g., operation preparation action, operation hesitation action), and the notification means notifies the store clerk who registers the product about the first specific action, but does not notify the store clerk who registers the product about the second specific action (e.g., in the first embodiment, the registration device 10 displays the withdrawal button BT43, but does not display the operation preparation button or the operation hesitation button). According to (A1), the system in which the customer himself operates the checkout machine can be more effectively operated. For example, the store clerk who registers the product is notified about the first specific action, which has a high priority, but is not notified about the second specific action, which has a lower priority, so the store clerk who registers the product can concentrate on registering the product.

[0478] (A2) The POS system described in (A1) is characterized in that the notification means notifies a store clerk other than the store clerk who registers the product regarding the second specific action (for example, the store clerk who uses the transaction status management device 40) (for example, in the first and second embodiments, the transaction status management device 40 displays an operation preparation button BT72 and an operation uncertainty button BT71). According to (A2), the system in which the customer himself operates the payment machine can be operated more optimally.

[0479] (A3) A POS system according to (A1) or (A2), characterized in that the notification means notifies a store clerk other than the store clerk who registers the product regarding the first specific action (for example, in the first and second embodiments, the transaction status management device 40 displays an exit button BT73). According to (A3), the system in which the customer himself operates the payment machine can be operated more optimally.

[0480] (A4) The POS system described in any of (A1) to (A3) is characterized in that, if the progress of settlement at the settlement device, which is proceeding according to the customer's settlement operation, does not progress for a predetermined time (for example, if operation preparation behavior or operation hesitation behavior continues for a predetermined time after the notification in the transaction status management device 40), the notification means notifies the store clerk who registers the product regarding the second specific behavior (for example, in the second embodiment, the registration device 10 displays the operation preparation button BT42 or the operation hesitation button BT41 a predetermined time later than the timing at which the transaction status management device 40 displays the operation preparation button BT72 or the operation hesitation button BT71). According to (A4), the system in which the customer himself operates the payment machine can be operated more optimally.

[0481] (A5) In order to solve the above-mentioned problems, another aspect of the present invention is a POS system including a registration device where a store clerk registers products and a plurality of settlement devices where customers themselves settle their payments, the POS system further comprising: customer monitoring means for monitoring customer behavior at the settlement devices; and notification means for notifying a store clerk of a specific behavior when the customer behavior monitored by the customer monitoring means is a specific behavior that requires notification to a store clerk, the specific behavior including a first specific behavior having a high notification priority and a second specific behavior having a lower notification priority than the first specific behavior, and the store clerk who registers the products is able to impose restrictions on notification of the specific behavior. The POS system is characterized in that there are normal store clerks who are not registered and restricted store clerks who are restricted in the notification of the specific actions, and the notification means notifies both the normal store clerk and the restricted store clerk regarding the first specific action, and notifies the normal store clerk but not the restricted store clerk regarding the second specific action (for example, in the third embodiment, the registration device 10 used by the normal store clerk displays the Exit button BT43, the Operation Preparation button BT42, and the Operation Hesitation button BT41, and the registration device 10 used by the restricted store clerk displays the Exit button BT43 but does not display the Operation Preparation button BT42 or the Operation Hesitation button BT41). According to (A5), the system in which customers themselves operate the payment machines can be operated more optimally.

[0482] (A6) In order to solve the above-mentioned problems, a POS system according to another aspect of the present invention is a POS system including a registration device where a store clerk registers products and a plurality of settlement devices where customers themselves settle their payments, and is equipped with a customer monitoring means for monitoring customer behavior at the settlement devices, a notification means for notifying a store clerk of a specific behavior when the customer behavior monitored by the customer monitoring means is a specific behavior that requires notification to a store clerk, and a notification restriction declaration means (e.g., a notification restriction button BT80) for declaring that notifications by the notification means are restricted, wherein the specific behavior includes a first specific behavior having a high notification priority and a second specific behavior having a lower notification priority than the first specific behavior, and the notification means is When the notification restriction declaration means has not declared a notification (for example, when in a normal notification state), both the first specific action and the second specific action are notified, and when the notification restriction declaration means has declared a notification (for example, when in a notification restriction state), the first specific action is not notified but the second specific action is not notified (for example, in the fifth embodiment, a registration device 10 in a normal notification state displays the leave button BT43, the operation preparation button BT42, and the operation hesitation button BT41, and a registration device 10 in a notification restriction state displays the leave button BT43 but does not display the operation preparation button BT42 or the operation hesitation button BT41). This is a POS system characterized by the above. According to (A6), the system in which customers themselves operate the payment machines can be operated more optimally.

[0483] (A7) A POS system described in any of (A1) to (A6), characterized in that the first specific behavior is customer behavior related to payment fraud (e.g., withdrawal behavior), and the second specific behavior is customer behavior not related to payment fraud (e.g., operation preparation behavior, operation hesitation behavior). According to (A7), the system in which the customer himself operates the payment machine can be operated more optimally.

[0484] (A8) A POS system according to any one of (A1) to (A7), characterized in that the customer monitoring means includes an imaging means capable of capturing images of the customer's settlement operation at the settlement device, and a customer behavior recognition means for recognizing the customer's behavior based on the images captured by the imaging means. According to (A8), the system in which the customer himself operates the payment machine can be operated more optimally.

[0485] (A9) A POS system described in any of (A1) to (A8), characterized in that the customer behavior recognition means is capable of recognizing a withdrawal behavior of leaving the settlement device before completing the settlement (see, for example, Figure 5), and the withdrawal behavior is the first specific behavior. According to (A9), a system in which customers themselves operate the payment machines can be more suitably operated.

[0486] (A10) The POS system according to (A9), wherein the notification means notifies a store clerk of the leaving behavior together with a captured image that can identify the customer recognized as having the leaving behavior. According to (A10), a system in which customers themselves operate the payment machines can be more suitably operated.

[0487] (A11) The POS system described in (A8) or (A9) is characterized in that the customer behavior recognition means is capable of recognizing the operational hesitation behavior of a customer who is unsure about the checkout operation, or the preparatory behavior of a customer who is preparing items necessary for checkout, and the operational hesitation behavior and preparatory behavior are the second specific behavior. According to (A11), a system in which customers themselves operate the payment machines can be more suitably operated.

[0488] (A12) A POS system described in any of (A8) to (A10), further comprising an operation acceptance means for accepting the settlement operation via a display screen, wherein the customer behavior recognition means is capable of recognizing a non-contact instruction action of pointing to an area of ​​the display screen without touching the area, and wherein when the customer behavior recognition means recognizes the non-contact instruction action, the operation acceptance means accepts the settlement operation as if there had been contact with the area pointed to by the non-contact instruction action (see Figures 45 and 46). According to (A12), a system in which customers themselves operate the payment machines can be more suitably operated.

[0489] (B1) In order to solve the above-mentioned problems, another aspect of the present invention is a POS system including a registration device where a store clerk registers products and multiple settlement devices where customers themselves settle their payments, and includes a settlement device monitoring means for monitoring the status of the settlement devices, and a notification means (for example, a display of the usage status, a notification button such as a receipt button, a near-end button, a near-full button, etc.) that can notify the store clerk of a specific status when the status of the settlement device monitored by the settlement device monitoring means is a specific status that requires notification to the store clerk (for example, a usage status display, a notification button such as a receipt button, a near-end button, a near-full button, etc.). button), the specific situations include a first specific situation having a high notification priority (for example, a usage state) and a second specific situation having a lower notification priority (for example, notification buttons such as a receipt button, a near-end button, and a near-full button), and the notification means notifies the store clerk who registers the product of the first specific situation, but does not notify the store clerk who registers the product of the second specific situation (for example, as a modified example of the first and second embodiments, the registration device 10 does not display the receipt button BT31, the near-end button BT32, or the near-full button BT33). According to (B1), the system in which the customer operates the checkout machine can be more effectively operated. For example, the store clerk who registers the product is notified of the first specific situation, which has a high priority, but is not notified of the second specific situation, which has a low priority, so the store clerk can concentrate on registering the product.

[0490] (B2) The POS system described in (B1) is characterized in that the notification means notifies a store clerk other than the store clerk who registers the product regarding the second specific situation (for example, in the first and second embodiments, the transaction status management device 40 displays a receipt button BT61, a near-end button BT62, and a near-full button BT63). According to (B2), the system in which customers themselves operate the payment machines can be operated more optimally.

[0491] (B3) The POS system described in (B1) or (B2) is characterized in that the notification means notifies a store clerk other than the store clerk who registers the product regarding the first specific situation (for example, in the first and second embodiments, the transaction status management device 40 displays the usage status). According to (B3), a system in which customers themselves operate the payment machines can be more effectively operated.

[0492] (B4) In order to solve the above-mentioned problems, another aspect of the present invention is a POS system including a registration device where a store clerk registers products and multiple settlement devices where customers themselves settle their payments, and is equipped with a settlement device monitoring means for monitoring the status of the settlement devices, and a notification means for notifying the store clerk of the specific situation when the status of the settlement device monitored by the settlement device monitoring means is a specific situation that requires notification to the store clerk, the specific situations include a first specific situation with a high notification priority and a second specific situation with a lower notification priority than the first specific situation, and the store clerk who registers the products is selected from the group consisting of a regular store clerk who has no restrictions on notification of the specific situations, and a restricted clerk who has restrictions on the notification of the specific situation, and the notification means notifies both the regular clerk and the restricted clerk about the first specific situation, and notifies the regular clerk about the second specific situation, but not the restricted clerk (for example, as a variation of the third and fourth embodiments, the registration device 10 used by the regular clerk displays the usage status, the receipt button BT31, the near-end button BT32, and the near-full button BT33, and the registration device 10 used by the restricted clerk displays the usage status, but does not display the receipt button BT31, the near-end button BT32, or the near-full button BT33). According to (B4), the system in which customers themselves operate the payment machines can be operated more optimally.

[0493] (B5) In order to solve the above-mentioned problems, a POS system according to another aspect of the present invention is a POS system including a registration device where a store clerk registers products and a plurality of settlement devices where customers themselves settle their payments, and is equipped with a settlement device monitoring means for monitoring the status of the settlement devices, a notification means for notifying the store clerk of the specific situation when the status of the settlement device monitored by the settlement device monitoring means is a specific situation that requires notification to the store clerk, and a notification restriction declaration means (for example, a notification restriction button BT80) for declaring that notifications by the notification means will be restricted, the specific situations including a first specific situation having a high notification priority and a second specific situation having a lower notification priority than the first specific situation, and the notification means is When a notification is not declared by th...

Claims

1. A payment device in a system including a registration device where a store clerk registers products and a plurality of payment devices where customers themselves pay, a customer monitoring means for monitoring customer behavior; a transmission means for transmitting monitoring result information regarding a specific behavior to the registration device when the behavior of the customer monitored by the customer monitoring means is a specific behavior that requires notification to a store clerk; Equipped with the specific actions include a first specific action having a high notification priority and a second specific action having a lower notification priority than the first specific action; The transmitting means Transmitting monitoring result information regarding the first specific behavior to the registration device, while not transmitting monitoring result information regarding the second specific behavior to the registration device. A settlement device characterized by:

2. The transmitting means The monitoring result information regarding the second specific behavior is transmitted to a device used by a store clerk other than the store clerk who registers the product. The settlement device according to claim 1 .

3. The transmitting means The monitoring result information regarding the first specific behavior is transmitted to a device used by a store clerk other than the store clerk who performs the product registration.

3. The settlement device according to claim 1 or claim 2.

4. The transmitting means If the progress of the settlement, which is being made by the customer's settlement operation, does not progress for a predetermined time, monitoring result information regarding the second specific behavior is transmitted to the registration device. The settlement device according to any one of claims 1 to 3.

5. A payment device in a system including a registration device where a store clerk registers products and a plurality of payment devices where customers themselves pay, a customer monitoring means for monitoring customer behavior; a transmission means for transmitting monitoring result information regarding a specific behavior to the registration device when the behavior of the customer monitored by the customer monitoring means is a specific behavior that requires notification to a store clerk; Equipped with the specific actions include a first specific action having a high notification priority and a second specific action having a lower notification priority than the first specific action; The store clerk who registers the product may be a normal store clerk who does not impose any restrictions on the notification of the specific behavior, and a restricted store clerk who imposes restrictions on the notification of the specific behavior, The transmitting means transmitting monitoring result information regarding the first specific behavior to both the registration device where the regular clerk performs product registration and the registration device where the restricted clerk performs product registration; The monitoring result information regarding the second specific behavior is transmitted to the registration device where the regular clerk performs product registration, but is not transmitted to the registration device where the restricted clerk performs product registration. A settlement device characterized by:

6. A payment device in a system including a registration device where a store clerk registers products and a plurality of payment devices where customers themselves pay, a customer monitoring means for monitoring customer behavior; a transmission means for transmitting monitoring result information regarding a specific behavior to the registration device when the behavior of the customer monitored by the customer monitoring means is a specific behavior that requires notification to a store clerk; Equipped with the specific actions include a first specific action having a high notification priority and a second specific action having a lower notification priority than the first specific action; The registration device is capable of declaring that notification to store clerks is to be restricted, The transmitting means Transmitting monitoring result information regarding the first specific behavior to the registration device regardless of whether the declaration has been made or not; Transmit monitoring result information regarding the second specific behavior to the registration device if the declaration has been made, but do not transmit it to the registration device if the declaration has not been made. A settlement device characterized by:

7. A program that causes a computer to function as a payment device in a system that includes a registration device where a store clerk registers products and multiple payment devices where customers themselves pay, comprising: The computer Customer monitoring measures to monitor customer behavior; a transmission means for transmitting monitoring result information regarding a specific behavior of a customer monitored by the customer monitoring means to the registration device when the specific behavior requires notification to a store clerk; It functions as the specific actions include a first specific action having a high notification priority and a second specific action having a lower notification priority than the first specific action; The transmitting means Transmitting monitoring result information regarding the first specific behavior to the registration device, while not transmitting monitoring result information regarding the second specific behavior to the registration device. A program characterized by:

8. A program that causes a computer to function as a payment device in a system that includes a registration device where a store clerk registers products and multiple payment devices where customers themselves pay, comprising: The computer Customer monitoring measures to monitor customer behavior; a transmission means for transmitting monitoring result information regarding a specific behavior of a customer monitored by the customer monitoring means to the registration device when the specific behavior requires notification to a store clerk; It functions as the specific actions include a first specific action having a high notification priority and a second specific action having a lower notification priority than the first specific action; The store clerk who registers the product may be a normal store clerk who does not impose any restrictions on the notification of the specific behavior, and a restricted store clerk who imposes restrictions on the notification of the specific behavior, The transmitting means transmitting monitoring result information regarding the first specific behavior to both the registration device where the regular clerk performs product registration and the registration device where the restricted clerk performs product registration; The monitoring result information regarding the second specific behavior is transmitted to the registration device where the regular clerk performs product registration, but is not transmitted to the registration device where the restricted clerk performs product registration. A program characterized by:

9. A program that causes a computer to function as a payment device in a system that includes a registration device where a store clerk registers products and multiple payment devices where customers themselves pay, comprising: The computer Customer monitoring measures to monitor customer behavior; a transmission means for transmitting monitoring result information regarding a specific behavior of a customer monitored by the customer monitoring means to the registration device when the specific behavior requires notification to a store clerk; It functions as the specific actions include a first specific action having a high notification priority and a second specific action having a lower notification priority than the first specific action; The registration device is capable of declaring that notification to store clerks is to be restricted, The transmitting means Transmitting monitoring result information regarding the first specific behavior to the registration device regardless of whether the declaration has been made or not; Transmit monitoring result information regarding the second specific behavior to the registration device if the declaration has been made, but do not transmit it to the registration device if the declaration has not been made. A program characterized by:

Images