Transaction processing system, transaction processing device, and information processing program

Abstract

This reduces instances where actions performed unintentionally by a customer are mistakenly registered as legitimate actions. [Solution] The transaction processing system of the embodiment comprises a registration means, a determination means, and an output means. The registration means registers the details of a transaction in response to an operation by the customer. The determination means determines whether a predetermined target numerical value related to the registration of the transaction details by the registration means is in a state requiring confirmation, which is within a predetermined range of numerical values ​​that require confirmation. The output means outputs information prompting confirmation in response to the determination means determining that the transaction is in a state requiring confirmation.

Description

Technical Field

[0001] Embodiments of the present invention relate to a transaction processing system, a transaction processing apparatus, and an information processing program.

Background Art

[0002] In a transaction processing apparatus that registers transaction details in response to a customer's operation, such as a self-registration apparatus, the customer may perform an operation that the transaction processing apparatus is accepting without intending to, but it will be accepted as a normal operation. Under such circumstances, it has been desired to be able to reduce the situation where an operation performed by a customer without intention is accepted as a normal operation as it is.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a transaction processing system, a transaction processing apparatus, and an information processing program that can reduce the situation where an operation performed by a customer without intention is accepted as a normal operation as it is.

Means for Solving the Problems

[0005] The transaction processing system of this embodiment comprises a registration means, a determination means, and an output means. The registration means registers the details of a transaction in response to an operation by the customer. The determination means determines whether a predetermined target numerical value related to the registration of the transaction details by the registration means is in a state requiring confirmation, which is within a predetermined range of numerical values ​​that require confirmation. The output means outputs information prompting confirmation in response to the determination means determining that the transaction is in a state requiring confirmation. [Brief explanation of the drawing]

[0006] [Figure 1] A diagram showing the schematic configuration of the transaction processing system according to the first embodiment. [Figure 2] A block diagram showing the main circuit configuration of the transaction processing device and monitoring device in Figure 1. [Figure 3] A diagram showing the schematic configuration of the shopping bag display stand in Figure 1. [Figure 4] Transaction processing flowchart. [Figure 5] Transaction processing flowchart. [Figure 6] Transaction processing flowchart. [Figure 7] Transaction processing flowchart. [Figure 8] A diagram showing an example of a registration screen. [Figure 9] A diagram illustrating an example of a duplicate check screen. [Figure 10] A flowchart for the monitoring process. [Figure 11] A diagram showing an example of a check screen. [Figure 12] A diagram showing an example of a cancellation confirmation screen. [Figure 13] A diagram showing an example of a correction notification screen. [Figure 14] A diagram illustrating an example of a continuous confirmation screen. [Figure 15] A diagram illustrating an example of a continuous confirmation screen. [Figure 16] A diagram showing an example of a product confirmation screen. [Figure 17] A diagram showing an example of a quantity confirmation screen. [Figure 18]A diagram showing the schematic configuration of the transaction processing system according to the second embodiment. [Figure 19] A block diagram showing the main circuit configuration of the management terminal in FIG. 18. [Figure 20] A flowchart of the management process. [Figure 21] A diagram showing an example of a selection screen. [Figure 22] A diagram showing a modified configuration example of the cash register bag storage device shown in FIG. 3. [Figure 23] A diagram showing the schematic configuration in a modified example of the cash register bag storage device. [Embodiments for Carrying Out the Invention]

[0007] Hereinafter, embodiments will be described with reference to the drawings. [First Embodiment] FIG. 1 is a diagram showing the schematic configuration of a transaction processing system 1 according to the first embodiment. The transaction processing system 1 is used, for example, in a checkout corner set within a corresponding store in order to process sales transactions of products in the store. The transaction processing system 1 includes at least one transaction processing device 100 installed in the checkout corner, at least one cash register bag storage device 200, and at least one monitoring device 300. In FIG. 1, a transaction processing system 1 including four transaction processing devices 100 and cash register bag storage devices 200 each, and one monitoring device 300 is shown. It is arbitrary how many of the transaction processing device 100, the cash register bag storage device 200, and the monitoring device 300 the transaction processing system 1 includes respectively. However, the number of transaction processing devices 100 and cash register bag storage devices 200 shall be the same. The ratio of the number of transaction processing devices 100 to the number of monitoring devices 300 is arbitrary.

[0008] The transaction processing device 100 is an information processing device that, in response to an operation by a customer CU, registers the products purchased by the customer CU as transaction products and performs transaction processing for settling the price for all the registered transaction products. That is, the operator of the transaction processing device 100 is the customer CU. However, the transaction processing device 100 may be operated by an operator other than the customer CU, such as a store clerk. In many cases, the details of transactions processed by the transaction processing device 100 are managed by a POS server (not shown). That is, the transaction processing device 100 is also referred to as a POS terminal.

[0009] The cash register bag container 200 stores bags for customers to put the purchased goods in, that is, so-called cash register bags. The cash register bag container 200 pairs with the transaction processing device 100, and for putting the goods targeted by the transaction processed using the paired transaction processing device 100, a customer CU who purchases the corresponding goods takes out a cash register bag.

[0010] The monitoring device 300 is an information processing device for an attendant AT to monitor the operating status of the four transaction processing devices 100 and perform support processing to attend to customer CUs. The monitoring device 300 is also referred to as an attendant device. The operator of the monitoring device 300 is the attendant AT. Note that the attendant AT is generally a store clerk. The attendant AT may be provided at a location separate from the checkout corner. The monitoring device 300 may be portable. And in this case, the monitoring device 300 may not be installed at a specific location, but may be carried by an attendant AT who patrols the checkout corner.

[0011] FIG. 2 is a block diagram showing the main circuit configurations of the transaction processing device 100 and the monitoring device 300. Since the four transaction processing devices 100 shown in FIG. 1 all have the same configuration, FIG. 2 shows only the configuration of one transaction processing device 100. And all four transaction processing devices 100 are capable of communicating with the monitoring device 300 via the communication network 2. The communication network 2 can use the Internet, VPN (virtual private network), LAN (local area network), public communication network, mobile communication network, etc., alone or in appropriate combinations. As an example, a LAN is used as the communication network 2.

[0012] The transaction processing device 100 includes a processor 101, a main memory unit 102, a sub-memory unit 103, a touch panel 104, a handheld scanner 105, a fixed scanner 106, a change dispenser 107, a credit card reader 108, an electronic money reader / writer 109, a printer 110, an alarm lamp 111, a sound unit 112, a communication unit 113, an interface unit 114, and a transmission line 115.

[0013] The processor 101, the main memory unit 102, and the sub-memory unit 103 are connected by a transmission line 115 to form a computer for controlling the transaction processing unit 100. The processor 101 corresponds to the central part of the computer described above. Based on various information processing programs such as the operating system, firmware, and application programs stored in the main storage unit 102 and the sub-storage unit 103, the processor 101 performs information processing to control each part in order to realize various functions of the transaction processing unit 100.

[0014] The main memory unit 102 corresponds to the main memory portion of the computer described above. The main memory unit 102 includes a read-only memory area and a rewritable memory area. The main memory unit 102 stores a portion of the information processing program described above in the read-only memory area. The main memory unit 102 may also store data necessary for the processor 101 to perform processing to control each part in the read-only memory area or the rewritable memory area. The main memory unit 102 uses the rewritable memory area as a work area for the processor 101.

[0015] The sub-storage unit 103 corresponds to the auxiliary storage portion of the computer described above. The sub-storage unit 103 may include well-known storage devices such as EEPROM (electric erasable programmable read-only memory), HDD (hard disk drive), or SSD (solid state drive). The sub-storage unit 103 stores data used by the processor 101 in performing various processes, and data generated by processing by the processor 101. The sub-storage unit 103 may also store application programs. In this embodiment, the sub-storage unit 103 stores the transaction processing program PRA. The transaction processing program PRA is an application program that describes processing procedures related to information processing for processing transactions.

[0016] The touch panel 104 displays various screens to inform the operator of various information. Some of these screens constitute a GUI (graphical user interface), and the touch panel 104 receives touch operations for operating the GUI. The handheld scanner 105 is held and used by the operator, and when it is brought close to a barcode displayed on a product, it reads the barcode and outputs the barcode information it represents. This barcode information includes a product code for identifying the product. The handheld scanner 105 may also read a barcode displayed on the surface of a point card or a barcode displayed on the point membership screen of an information terminal such as a smartphone, and output barcode information including point information, etc. The handheld scanner 105 may also read a barcode for code payment displayed on the payment screen of an information terminal such as a smartphone, and output barcode information including payment information, etc., that the barcode represents. Here, "barcode" may include various types of optically readable codes such as one-dimensional barcodes and two-dimensional barcodes.

[0017] The fixed scanner 106 captures an image of the product held in front of it and then identifies the barcode displayed on the product using image processing. The fixed scanner 106 then outputs the barcode information represented by the identified barcode. The fixed scanner 106 can also use other types of well-known devices that identify barcodes using the reflection of laser light. Like the handheld scanner 105, the fixed scanner 106 may also read barcodes other than those displayed on products.

[0018] The change dispenser 107 comprises a coin safe for storing coins by denomination and a banknote safe for storing banknotes by denomination. The change dispenser 107 takes in inserted coins, identifies their denomination, and stores them in the coin safe according to their denomination. The change dispenser 107 also takes in inserted banknotes, identifies their denomination, and stores them in the banknote safe according to their denomination. In response to a dispensing command from the processor 101, the change dispenser 107 discharges the coins or banknotes stored in the coin safe or banknote safe to the outside of the transaction processing device 100. The change dispenser 107 has a function to manage the number of coins and banknotes stored in the coin safe and banknote safe according to their denomination. Existing automatic change dispensers can be used as such a change dispenser 107.

[0019] The credit card reader 108 reads the data recorded on the credit card inserted into the card slot by the operator. The electronic money reader / writer 109 is equipped with, for example, an NFC (near-field communication) communication unit and reads data from nearby electronic money cards via wireless communication. The electronic money reader / writer 109 also writes data from nearby electronic money cards via wireless communication.

[0020] The printer 110 includes a receipt printer and a journal printer. The receipt printer issues various types of documents by printing various information onto receipt paper. These documents include receipts showing the details of commercial transactions and credit slips related to credit card payments. The documents issued by the receipt printer are ejected to the outside of the transaction processing unit 100. The journal printer prints journal data containing the information printed on the receipt paper by the receipt printer onto journal paper. The journal paper is retained inside the transaction processing unit 100 unless removed by a maintenance worker.

[0021] The alarm lamp 111 lights up or flashes to indicate the status of the device. The sound unit 112 outputs sounds and voices for various announcements and warnings. The sound unit 112 can utilize various well-known sound devices, such as a speech synthesis device and a buzzer, either individually or in combination.

[0022] The communication unit 113 performs data communication via the communication network 2. If the communication network 2 is a LAN, the communication unit 113 can use a well-known communication device adapted to a LAN. The interface unit 114 can connect to any external device and interfaces for the exchange of data between this connected external device and the processor 101. The shopping bag dispenser 200, which is paired with the transaction processing device 100 equipped with this interface unit 114, is connected to the interface unit 114. As the interface unit 114, an existing device compliant with the USB (universal serial bus) standard can be used, for example. The transmission path 115 includes an address bus, a data bus, and control signal lines, etc. The transmission path 115 transmits data and signals exchanged between the connected parts.

[0023] The hardware for the transaction processing device 100 can be existing hardware used as a fully self-service POS terminal. The transaction processing program PRA is typically stored in the sub-storage unit 103 when the transaction processing device 100 is transferred. However, the transaction processing program PRA may be written to the sub-storage unit 103 by the processor 101 in response to an operation by any worker after the transaction processing device 100 has been transferred. In this case, the sub-storage unit 103 of the transferred transaction processing device 100 may store a program of the same type but a different version, or it may not store such a program. In the former case, the program written to the sub-storage unit 103 later will be used in place of the program of the same type but a different version. The transfer of the transaction processing program PRA can be performed by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network.

[0024] The monitoring device 300 includes a processor 301, a main memory unit 302, a sub-memory unit 303, an input unit 304, a display unit 305, a sound unit 306, a communication unit 307, and a transmission line 308, among others. The general functions of the processor 301, main memory unit 302, sub-memory unit 303, sound unit 306, communication unit 307, and transmission line 308 are equivalent to those of the processor 101, main memory unit 102, sub-memory unit 103, sound unit 112, communication unit 113, and transmission line 115. However, the sub-storage unit 303 stores the monitoring program PRB instead of the transaction processing program PRA. The monitoring program PRB is an application program that describes the processing procedures performed by the processor 301 to realize the functions of the monitoring device 300.

[0025] The input unit 304 receives various instructions from the operator. The input unit 304 can use well-known input devices such as touch sensors, key switches, mice, and keyboards, either individually or in combination. The display unit 305 performs various display operations to notify the operator of various information. The display unit 305 can use well-known display devices such as liquid crystal displays and light-emitting devices such as LED lamps, either individually or in combination.

[0026] The hardware of the monitoring device 300 can be, for example, a general-purpose computer. Furthermore, if the monitoring device 300 is portable, as mentioned above, the hardware of the monitoring device 300 can also be, for example, a tablet computer, smartphone, or wearable device. The monitoring device 300 can also be configured using, for example, a tablet computer, smartphone, or wearable device as a user interface device for the attendant AT. The monitoring program PRB is typically stored in the sub-storage unit 303 when the monitoring device 300 is transferred. However, the monitoring program PRB may be written to the sub-storage unit 303 by the processor 301 in response to an operation by any worker after the monitoring device 300 has been transferred. In this case, the sub-storage unit 303 of the transferred monitoring device 300 may store a program of the same type but a different version than the monitoring program PRB, or it may not store such a program. In the former case, the program written to the sub-storage unit 303 later will be used in place of the program of the same type but a different version. The monitoring program PRB can be transferred by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network.

[0027] Figure 3 is a diagram showing the schematic configuration of the shopping bag display unit 200. The left side of Figure 3 is a front view. The right side of Figure 3 is a cross-sectional view taken along the line AA in the front view. The shopping bag dispenser 200 comprises a housing 201. The housing 201 has a space 202 formed inside. Multiple shopping bags PBA are stored in the space 202 in a stacked state. The shopping bags PBA stored in the space 202 are, in principle, taken out one at a time by the customer CU through an opening 203 that connects the space 202 to the outside of the shopping bag dispenser 200. However, in cases such as when the shopping bags PBA are charged with static electricity, multiple shopping bags PBA may be taken out from the opening 203 in a stacked state.

[0028] A light transmission sensor 204 is mounted on the housing 201, flanking the outlet 203. The light transmission sensor 204 measures the amount of light passing through the outlet 203. An electronic unit is attached to the housing 201 in an appropriate manner, although this is not shown in the diagram. This electronic unit comprises a detection processing unit 205 and an interface unit 206.

[0029] The detection processing unit 205 detects that a shopping bag PBA has been removed based on the change in light intensity measured by the transmission sensor 204, and determines the number of shopping bags PBA removed at one time based on the measured light intensity. In other words, the detection processing unit 205 is an example of the first and second detection means. The detection processing unit 205 then notifies the transaction processing device 100, via the interface unit 206, that it has detected the removal, along with the determined number of bags. The interface unit 206 interfaces the exchange of data between the detection processing unit 205 and the transaction processing unit 100. An existing device conforming to the same standards as the interface unit 114 can be used as the interface unit 206.

[0030] Next, the operation of the transaction processing system 1 configured as described above will be explained. Note that the content of the various processes described below is merely an example, and the order of some processes can be changed, some processes can be omitted, or other processes can be added as appropriate. For example, in the following explanation, some processes have been omitted in order to clearly illustrate the characteristic operation of this embodiment. For example, if an error occurs, processing to deal with that error may be performed, but such processing has been omitted from the description.

[0031] Customer CU picks up items displayed on the store floor and takes them to the checkout counter. Then, customer CU selects a transaction processing unit 100 that is not being used by another customer and performs a predetermined operation, for example, on the touch panel 104, to begin registering the transaction items. In response to this operation, the processor 101 starts transaction processing to handle a single transaction, based on the transaction processing program PRA.

[0032] Figures 4, 5, 6, and 7 are flowcharts of the transaction process. In Figure 4, the processor 101, designated as ACT111, displays the registration screen on the touch panel 104. The registration screen shows the registration status of the trading products during the registration process. Figure 8 shows an example of a registration screen. Note that the screen examples shown in Figure 8 and subsequent figures omit the illustration of some of the display elements shown on the screen. For example, buttons display text or illustrations to help the user identify the function assigned to that button, but some of these are omitted from the illustration.

[0033] The registration screen shown in Figure 8 includes display areas ARA, ARB, ARC, ARD, a group of buttons BGA, and buttons BUA, BUB, BUC, BUD, BUE, BUF. Display area ARA displays text and illustrations to guide the user's operation. Display area ARB displays the current date and time. Display area ARC displays the details of registered transactions. In other words, display area ARC displays a list of registered transaction items. Note that examples such as "AAAAAA" and "BBBBBB" shown in display area ARC are actually strings that represent product names, etc. Display area ARD displays the total number of registered transaction items and the total amount. Note that while Figure 8 shows specific display examples in display areas ARC and AED, when ACT111 is executed in Figure 4, no transaction items have been registered yet, so product names and amounts are not displayed in display areas ARC and ARD. The group of buttons BGA includes multiple buttons for specifying that items without barcodes should be registered as transaction items. Button BUA is a soft key for specifying that items sold in boxes or large items such as rice should be registered as transaction items. Button BUB is a soft key used to request a store employee. Button BUC is a soft key used to request cancellation of a transaction currently being registered. Buttons BUD and BUE are soft keys used to request a change of page to display when the product list to be displayed in the display area ARC spans multiple pages. Button BUF is a soft key used to request completion of product registration and proceed to checkout.

[0034] As ACT112, processor 101 checks whether the retrieval notification described later has been issued. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT113. As ACT113, processor 101 checks whether the product to be registered as a trading item has been scanned as described below. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT114.

[0035] As ACT114, processor 101 checks whether the operation described later to specify the product to be registered as a trading product has been performed. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT115. As ACT115, processor 101 checks whether the transition to accounting has been specified as described below. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT112. Thus, processor 101 awaits one of the following as ACT112~ACT115: retrieval notification, product scan, product selection operation, or payment selection.

[0036] If a customer CU purchases a shopping bag (PBA), they take a bag from the shopping bag dispenser 200, which is paired with the transaction processing device 100 they are using. In response, the detection processing unit 205 in the shopping bag dispenser 200 detects the removal of the shopping bag (PBA) and determines the number of shopping bags (PBA) that were taken out.

[0037] As mentioned above, the shopping bag dispenser 200 is configured so that, in principle, one shopping bag PBA is dispensed at a time. Therefore, if a customer CU purchases multiple shopping bags PBA, they will dispense them multiple times. If a shopping bag PBA is dispensed in accordance with the principle, the detection processing unit 205 detects the dispenser and determines that only one bag was dispensed. The detection processing unit 205 then sends notification data for dispensed bag notification, which includes information indicating that only one bag was dispensed, to the transaction processing unit 100 via the interface unit 206. However, as mentioned above, in a single action by a customer CU to dispense one shopping bag PBA, multiple shopping bags PBA may be dispensed stacked on top of each other. In this case, the detection processing unit 205 detects the dispenser and determines the number of bags dispensed. The detection processing unit 205 then sends notification data for dispensed bag notification, which includes information indicating the determined number of bags dispensed, to the transaction processing unit 100 via the interface unit 206.

[0038] Upon receiving this notification data via the interface unit 114, the processor 101 determines that an retrieval notification has been made, and in ACT 112 it determines YES, then proceeds to ACT 121 in Figure 5. As ACT121, processor 101 checks if the number of items to be removed is one, as indicated by the notification data. If the notification data contains data indicating that the number of items removed is one, processor 101 determines it is YES and proceeds to ACT122.

[0039] As ACT122, processor 101 updates the transaction data to include one plastic shopping bag PBA as a transaction item. If processor 101 proceeds to ACT122 without having registered any items as transaction items yet, it generates new transaction data that includes only one plastic shopping bag PBA as a transaction item. Processor 101 stores the transaction data in the main storage unit 102 or the sub-storage unit 103. Processor 101 may represent the plastic shopping bag PBA in the transaction data in a form that distinguishes it from other transaction items, or in a form that does not distinguish it.

[0040] As ACT123, processor 101 updates the registration screen displayed on touch panel 104 to reflect the contents of the transaction data after it was updated in ACT122. Processor 101 may choose to display plastic bags (PBA) separately from other transaction items on the registration screen, or not. After this, processor 101 returns to the standby state of ACT112~ACT115 in Figure 4.

[0041] On the other hand, if processor 101 cannot confirm that only one plastic bag PBA is dispensed, it determines NO in ACT121 and proceeds to ACT124. At this point, the processor 101 determines that the number of items to be retrieved as the target value is within the specified range of two or more, and is therefore in a state requiring confirmation. Thus, by having the processor 101 execute information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as a determination means. As ACT124, processor 101 displays a duplicate confirmation screen on touch panel 104. The duplicate confirmation screen is a screen that allows the customer CU to confirm that a duplicate shopping bag (PBA) has been dispensed.

[0042] Figure 9 shows an example of a duplicate check screen. The duplicate confirmation screen shown in Figure 9 is an example of what happens when two PBA shopping bags are stacked on top of each other while the registration screen shown in Figure 8 is displayed, and both are removed at the same time. The duplicate confirmation screen shown in Figure 9 is a WIA window that pops up on the registration screen shown in Figure 8.

[0043] The window WIA includes the text message MEA and the buttons BUG and BUH. The text message MEA represents a message prompting customer CU to confirm that two shopping bags PBA have been taken out. Processor 101 modifies the text message MEA as appropriate to represent the number of bags notified by the shopping bag dispenser 200. Button BUG is a soft key to receive a specification to register the number of shopping bags PBA represented in the text message MEA as a transaction item. Button BUH is a soft key to receive a specification to refuse to register the displayed number of shopping bags PBA as a transaction item. Thus, the duplicate confirmation screen is an example of information used to prompt confirmation. The processor 101 then performs information processing based on the transaction processing program PRA, and the computer, with the processor 101 as its central component, functions as an output means.

[0044] Customer CU specifies that if they agree to purchase the number of shopping bags PBA indicated in the text message MEA, they should register it as a transaction item by touching button BUG or performing other predetermined actions. Customer CU also specifies that if the number of shopping bags PBA indicated in the text message MEA is too many, they should reject the transaction by touching button BUH or performing other predetermined actions.

[0045] As ACT125, processor 101 checks whether it has been approved to register the multiple plastic bags PBA that have been taken out as transaction items. If, as described above, customer CU has specified that they should be registered as transaction items, processor 101 determines that it has been approved and YES, and proceeds to ACT126.

[0046] In Figure 5, as ACT126, processor 101 updates the transaction data to include the number of shopping bags PBA notified from the shopping bag display unit 200 as a transaction item. If processor 101 proceeds to ACT126 without having registered any items as transaction items yet, it generates new transaction data that includes only the corresponding number of shopping bags PBA as a transaction item. As ACT127, processor 101 displays a registration screen on touch panel 104 showing the contents of the transaction data after it has been updated in ACT126. After this, processor 101 returns to the standby state of ACT112~ACT115 in Figure 4.

[0047] If the customer CU specifies that it is not permitted to register the item as a trading product, as described above, the processor 101 determines NO in ACT125 in Figure 5 and proceeds to ACT128. As ACT128, processor 101 displays a "checking" screen on touch panel 104. The "checking" screen is a screen that notifies the customer CU that the attendant AT is performing a check. The "checking" screen displays text messages such as "A staff member is checking your information" or "Please wait a moment."

[0048] As ACT129, the processor 101 notifies the monitoring device 300 of the duplicate retrieval. For example, the processor 101 sends the notification data received from the shopping bag dispenser 200 directly to the monitoring device 300 via the communication unit 113 to the communication network 2. However, the processor 101 may also send the notification data after performing a predetermined conversion. Alternatively, it may generate and send new notification data to notify the monitoring device 300 of the number of bags retrieved as notified by the notification data received from the shopping bag dispenser 200. When the above notification data is transmitted to the monitoring device 300 via the communication network 2 and received by the communication unit 307, the processor 301 in the monitoring device 300 executes monitoring processing based on the monitoring program PRB.

[0049] Figure 10 is a flowchart of the monitoring process. As ACT311, processor 301 displays a check screen on display unit 305. The check screen is for attendant AT to confirm that duplicate plastic bags (PBA) are being dispensed.

[0050] Figure 11 shows an example of a check screen. The check screen shown in Figure 11 represents the text message MEB, the display area ARE, and the buttons BUI and BUJ. The text message MEB represents a message prompting the attendant AT to check on the incident in which a duplicate shopping bag PBA was taken out. The processor 301 plays a video in the display area ARE showing the customer CU operating the transaction processing device 100 that is the source of the notification taking out the shopping bag PBA. The video displayed in the display area ARE is expected to be a video recorded by a recording system, not shown in Figures 1 and 2, which is installed in the store and records the actions of the customer CU operating the transaction processing device 100. Button BUI is a soft key for specifying the last action to be canceled. Button BUJ is a soft key for specifying that the operation of the transaction processing device 100 that is the source of the notification be performed by the monitoring device 300.

[0051] The attendant AT visually inspects the check screen and decides whether to cancel the previous dispensing of multiple shopping bags PBA and dispense only one, or to remotely operate the transaction processing device 100 that notified the customer. In other words, if the attendant AT determines that the customer CU did not wish to purchase multiple shopping bags PBA and that multiple shopping bags PBA were dispensed against the customer CU's wishes, the attendant AT decides on the former. If the attendant AT decides on the former, they specify a cancellation by performing a predetermined operation, such as touching button BUI. If the attendant AT decides on the latter, they specify a remote operation by performing a predetermined operation, such as touching button BUJ.

[0052] After the processor 301 displays the check screen as ACT311 in Figure 10, it proceeds to ACT312. As ACT312, processor 301 checks if a previous cancellation was specified. If processor 301 cannot confirm the relevant event, it determines NO and proceeds to ACT313.

[0053] As ACT313, processor 301 checks if remote control has been specified. If processor 301 cannot confirm the relevant event, it determines NO and returns to ACT312. Thus, processor 301 waits for either a last-minute cancellation or remote control to be specified as ACT312 and ACT313. If a last-minute cancellation is specified as described above, processor 301 determines YES in ACT312 and proceeds to ACT314.

[0054] As ACT314, processor 301 instructs the notifying transaction processing unit 100 to cancel the transaction immediately. For example, processor 301 sends predetermined instruction data for instructing the transaction processing unit 100 to the communication network 2 via the communication unit 113. As ACT315, processor 301 displays a cancellation confirmation screen on display unit 305. The cancellation confirmation screen is a screen that notifies the attendant AT that the action has been taken as a last-minute cancellation.

[0055] Figure 12 shows an example of a cancellation confirmation screen. The cancellation confirmation screen shown in Figure 12 indicates that the action was taken as a last-minute cancellation using a text message (MEC). The processor 301 then terminates the monitoring process in response to the notification of this duplicate extraction.

[0056] Now, in the transaction processing unit 100, after the processor 101 notifies the system of duplicate removal as ACT129 in Figure 5, it proceeds to ACT130. As ACT130, processor 101 checks whether a previous cancellation was instructed, as described above. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT131.

[0057] As ACT131, processor 101 checks whether a correction has been instructed, as described below. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT130. Thus, the processor 101 waits for instructions to cancel or modify an order as ACT130 and ACT131. When the instruction data sent from the monitoring device 300 to instruct a cancellation, as described above, is transmitted to the transaction processing device 100 via the communication network 2 and received by the communication unit 113, the processor 101 determines YES in ACT130 and proceeds to ACT132.

[0058] As ACT132, processor 101 updates the transaction data to add one plastic shopping bag (PBA) as a transaction item. If processor 101 proceeds to ACT132 without having registered any items as transaction items yet, it generates new transaction data that includes only one plastic shopping bag (PBA) as a transaction item. As ACT133, processor 101 displays a correction notification screen on touch panel 104. The correction notification screen is used to notify the customer CU of the correction results.

[0059] Figure 13 shows an example of a correction notification screen. The correction notification screen shown in Figure 13 is an example of a case where, while the duplicate screen shown in Figure 9 is displayed, the customer CU touches button BUH, resulting in processor 101 proceeding to ACT133. The correction confirmation screen shown in Figure 13 is a screen in which window WIB is displayed as a pop-up instead of window WIA in the duplicate screen shown in Figure 9.

[0060] The window WIB contains text messages MED, MEE, and buttons BUK. Text message MED indicates that only one shopping bag (PBA) has been registered, informing the customer (CU). Text message MEE indicates that the customer (CU) is prompting them to hand over any extra shopping bags (PBA) to a staff member. Button BUK is a soft key used to receive confirmation from the customer (CU) that they have seen the notification on the correction notification screen.

[0061] When the processor 101 displays the correction confirmation screen, if a predetermined event occurs, it proceeds to ACT 134. The event described above is expected to be, for example, when a predetermined operation such as touching button BUK is performed. Alternatively, the event described above is expected to be when a predetermined display period for the correction notification screen ends. As ACT134, processor 101 displays a registration screen on touch panel 104 showing the contents of the transaction data after it has been updated by ACT132. After this, processor 101 returns to the standby state of ACT112~ACT115 in Figure 4.

[0062] Now, if remote operation is specified by attendant AT in the monitoring device 300, the processor 301 determines YES in ACT313 in Figure 10 and proceeds to ACT316. As ACT316, processor 301 displays the register operation screen on display unit 305. The register operation screen is a screen for allowing the attendant AT to operate the transaction processing device 100 that is the source of the notification. The register operation screen is expected to be similar to the registration screen on the transaction processing device 100, for example. However, the register operation screen may include buttons for operations that are not permitted for customer CUs but are permitted for attendant ATs. Also, the register operation screen may be completely different from the registration screen and adapted to operations performed by the attendant AT.

[0063] As ACT317, processor 301 accepts modification operations regarding the registration of plastic bags (PBA) as a trading item on the register operation screen. Attendant AT performs the appropriate operations to specify the modification regarding the registration of plastic bags (PBA) as a trading item. As ACT318, processor 301 instructs the notifying transaction processing unit 100 to modify the transaction data in accordance with the modification operation received by ACT317. For example, processor 301 sends instruction data containing data representing the modification details to the notifying transaction processing unit 100 via the communication unit 307 to the communication network 2. Then processor 301 terminates the monitoring process in response to the notification of the duplicate retrieval.

[0064] When the above instruction data is transmitted to the transaction processing device 100 via the communication network 2 and received by the communication unit 113, the processor 101 of the transaction processing device 100 determines YES at ACT131 in Figure 5 and proceeds to ACT135. As ACT135, processor 101 updates the transaction data according to the data representing the modifications included in the instruction data mentioned above.

[0065] As ACT136, processor 101 displays a correction notification screen on touch panel 104. The correction notification screen displayed here is similar to the one shown in Figure 13, for example, but the content of the text messages MED and MEE is changed according to the correction. As ACT137, processor 101 displays a registration screen on touch panel 104 showing the contents of the transaction data after it has been updated in ACT135. After this, processor 101 returns to the standby state of ACT112~ACT115 in Figure 4.

[0066] As described above, if only one shopping bag PBA is taken out of the shopping bag dispenser 200, the transaction processing device 100 registers the single shopping bag PBA as a transaction item without receiving any input from the customer CU or attendant AT. However, if two or more shopping bags PBA are taken out of the shopping bag dispenser 200 at once, the transaction processing device 100 displays a duplicate confirmation screen to ask the customer CU whether to register the multiple shopping bags PBA taken out as transaction items. Furthermore, if the customer CU refuses to register the multiple shopping bags PBA taken out as transaction items, the transaction processing device 100 corrects the registration of the shopping bags PBA according to the instructions of the attendant AT.

[0067] The customer CU performs a predetermined action to instruct the system to register one of the items it intends to purchase as a transaction item. That is, the customer CU, for example, scans the barcode displayed on the item using a handheld scanner 105 or a fixed scanner 106. This barcode scanning will be referred to as an item scan below. The customer CU also operates the touch panel 104 to directly input the item code, for example. Alternatively, the customer CU presses a preset key for the item on the touch panel 104. In other words, the actions performed by the customer CU here can be similar to those performed on existing fully self-service POS terminals. When the barcode is scanned by the handheld scanner 105 or the fixed scanner 106, the processor 101 determines that it is an item scan and verifies YES at ACT 113 in Figure 4, and proceeds to ACT 141 in Figure 6.

[0068] As ACT141, processor 101 checks whether a barcode scan was performed to specify the product that was registered as the previously traded product. For example, if the first product was specified by product scan, then the previous traded product has not been registered, so processor 101 determines NO and proceeds to ACT142. Processor 101 also determines NO if the current product scan is for the second or subsequent product, and the previous traded product was specified by operation on the touch panel 104.

[0069] As ACT142, processor 101 updates the transaction data to add the product identified by the product code contained in the scanned barcode to the transaction items. As ACT143, processor 101 updates the registration screen displayed on touch panel 104 to reflect the contents of the transaction data after it was updated in ACT142. After this, processor 101 returns to ACT112 to ACT115 in Figure 4.

[0070] After completing ACT143 in Figure 6, processor 101 is in the waiting state for ACT112 to ACT115 in Figure 4. If a new product scan is performed and the process proceeds from ACT113 to ACT141 in Figure 6, the barcode scan is being performed to specify the product that was previously registered as a transaction product. Therefore, ACT141 determines YES and proceeds to ACT144.

[0071] As ACT144, processor 101 determines the time interval between the product scan for the previous transaction and the current product scan. In ACT145, the processor 101 checks whether the time interval determined in ACT144 is a short interval. The processor 101 determines that it is a short interval if it meets a predetermined condition, such as "the time interval determined in ACT144 is below a threshold." The above conditions may be determined as appropriate by the person who determined the specifications of the transaction processing device 100. However, it is preferable that the conditions be set so that a time interval significantly shorter than the typical time interval when a customer CU performs product scans for two products consecutively can be determined as a short interval. If the processor 101 cannot confirm that it is a short interval, it determines NO and proceeds to ACT142 and beyond as described above. However, if the processor 101 can confirm that it is a short interval, it determines YES in ACT145 and proceeds to ACT146.

[0072] At this point, the processor 101 determines that the time interval for the target numerical value is within the numerical range defined as being below a threshold, and is therefore in a state requiring confirmation. Thus, by having the processor 101 execute information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as a determination means. As ACT146, processor 101 displays a continuous confirmation screen on touch panel 104. The continuous confirmation screen is a screen that allows the customer CU to confirm that two product scans were performed at a short interval.

[0073] Figure 14 shows an example of a continuous confirmation screen. The continuous confirmation screen shown in Figure 14 is an example of a case where, while the registration screen shown in Figure 8 is displayed, two scans of a product with the product name "GGGGGG" are performed at short intervals, resulting in the processor 101 proceeding to ACT146. The continuous confirmation screen shown in Figure 14 is a screen in which the window WIC is popped up on the registration screen shown in Figure 8.

[0074] The window WIC includes text messages (MEF) and buttons (BUL, BUM). The text message MEF represents a message prompting the customer CU to confirm that the two scans described above have been performed. Note that "GGGGGG" is actually a string representing the product name associated with the product code shown by the scanned barcode. Button BUL is a soft key used to indicate that the two products shown in the text message MEF have been scanned. Button BUM is a soft key used to indicate that one of the products shown in the text message MEF has not been scanned.

[0075] Figure 15 shows an example of a continuous confirmation screen. The continuous confirmation screen shown in Figure 15 is an example of a case where, while the registration screen shown in Figure 8 is displayed, product scans are performed at short intervals for products with the product names "GGGGGG" and "HHHHHH", resulting in processor 101 proceeding to ACT146. The text message MEF on the continuous confirmation screen shown in Figure 15 represents a message prompting the customer CU to confirm that the two scans described above have been performed. Note that "HHHHHH" is actually a string representing the product name associated with the product code represented by the scanned barcode. Thus, the continuous confirmation screen is an example of information used to prompt confirmation. Then, by having the processor 101 execute information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as an output means.

[0076] When scanning products with the handheld scanner 105 or the fixed scanner 106, in addition to products being scanned intentionally by the customer service provider (CU), the barcode of the same product may be scanned repeatedly, or the barcode of a product located within the scanning range of the handheld scanner 105 or the fixed scanner 106 may be scanned against the customer's will. Furthermore, product scans against the customer's will often occur at short intervals immediately after product scans that were performed according to the customer's wishes.

[0077] If the customer CU has performed the product scan indicated in the text message MEF, they indicate that they have performed the product scan by touching button BUL or performing a predetermined operation. If the customer CU has not performed the product scan indicated in the text message MEF, they indicate that they have not performed the product scan by touching button BUM or performing a predetermined operation.

[0078] In Figure 6, as ACT147, processor 101 checks whether an execution order has been issued. If it is indicated that the customer CU has performed a scan of the relevant product as described above, processor 101 determines that an execution order has been issued and YES, and proceeds with ACT142 and subsequent steps as described above. In other words, processor 101 registers the product that was the target of this product scan as a transaction product. However, if it is indicated that the customer CU has not performed a scan of the relevant product as described above, processor 101 determines that an execution order has not been issued and NO in ACT147, and proceeds to ACT148.

[0079] As ACT148, processor 101 displays a "checking" screen on touch panel 104. The "checking" screen is a screen that notifies the customer CU that the attendant AT is performing a check. The "checking" screen displays text messages such as "A staff member is checking your information" or "Please wait a moment." As ACT149, the processor 101 notifies the monitoring device 300 of the continuous scan. For example, the processor 101 sends predetermined notification data for the continuous scan notification from the communication unit 113 to the communication network 2 addressed to the monitoring device 300.

[0080] When the above notification data is transmitted to the monitoring device 300 via the communication network 2 and received by the communication unit 307, the processor 301 in the monitoring device 300 performs monitoring processing in the same manner as described above. However, in the check screen displayed as ACT311 in Figure 10, the processor 301 displays the text message MEB in Figure 11 as a message prompting the attendant AT to confirm the continuous scan. In addition, in the display area ARE, the processor 301 plays back a video recording of the customer CU's actions regarding the two most recent product scans at the notifying transaction processing device 100.

[0081] The attendant AT visually inspects the check screen and decides whether to cancel the previous product scan or to remotely operate the transaction processing device 100 that issued the notification. In other words, at this time, the customer CU does not wish to register the transaction product based on the previous product scan, so if the attendant AT determines that the previous product scan was incorrect, the attendant AT decides on the former. If the attendant AT decides on the former, the attendant AT specifies the previous cancellation by performing a predetermined operation, such as touching button BUI. If the attendant AT decides on the latter, the attendant AT specifies remote operation by performing a predetermined operation, such as touching button BUJ.

[0082] Now, in the transaction processing unit 100, after the processor 101 notifies of a continuous scan as ACT149 in Figure 6, it proceeds to ACT150. As ACT150, processor 101 checks through monitoring whether a previous cancellation was instructed. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT151.

[0083] As ACT151, processor 101 checks whether a correction has been instructed through monitoring. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT150. Thus, the processor 101 waits for instructions to cancel or modify an order as ACT150 and ACT151. When the instruction data sent from the monitoring device 300 to instruct a cancellation, as described above, is transmitted to the transaction processing device 100 via the communication network 2 and received by the communication unit 113, the processor 101 determines YES in ACT150 and proceeds to ACT152.

[0084] As ACT152, processor 101 displays a correction notification screen on touch panel 104. The correction notification screen displayed by processor 101 is similar to the one shown in Figure 13, for example, but the text messages MED and MEE represent a message notifying that the product targeted in the previous product scan will not be registered as a transaction product.

[0085] In Figure 6, the processor 101, designated as ACT153, displays a registration screen on the touch panel 104 that shows the contents of the current transaction data. If a "cancel immediately" command is issued in this manner, the transaction product will not be registered in response to the previous operation, i.e., the current product scan, and therefore the current product scan will be canceled. In other words, if the button BUM is touched while the continuous confirmation screen shown in Figure 14 is displayed, and then a "cancel immediately" command is issued, one of the two scans of the product named "GGGGGG" will be canceled. Also, if the button BUM is touched while the continuous confirmation screen shown in Figure 15 is displayed, and then a "cancel immediately" command is issued, the scan of the product named "HHHHHH" will be canceled. After this, the processor 101 returns to the waiting state of ACT112~ACT115 in Figure 4.

[0086] Now, if the attendant AT determines that any correction is needed regarding the notified continuous scan, it specifies remote operation and performs the appropriate operation for the correction. When the instruction data transmitted from the monitoring device 300 in response to this operation is transmitted to the transaction processing device 100 via the communication network 2 and received by the communication unit 113, the processor 101 of the transaction processing device 100 determines YES in ACT151 in Figure 6 and proceeds to ACT154. As ACT154, processor 101 updates the transaction data according to the data representing the modifications included in the instruction data mentioned above.

[0087] As ACT155, processor 101 displays a correction notification screen on touch panel 104. The correction notification screen displayed by processor 101 is similar to the one shown in Figure 13, for example, but the content of the text messages MED and MEE is changed according to the correction. As ACT156, processor 101 displays a registration screen on touch panel 104 showing the contents of the transaction data after it was updated in ACT154. After this, processor 101 returns to the standby state of ACT112~ACT115 in Figure 4.

[0088] As described above, if the time interval between two consecutive product scans is too long to be determined as a short interval, the transaction processing device 100 will register the transaction product in response to the later of the two product scans without receiving any input from the customer CU or attendant AT. However, if the time interval is short enough to be determined as a short interval, the transaction processing device 100 will prompt the customer CU to confirm whether to register the transaction product in response to the later of the two product scans by displaying a continuous confirmation screen. Furthermore, if the customer CU refuses to register the product, the transaction processing device 100 will correct the product registration in response to instructions from the attendant AT.

[0089] If the customer CU performs an operation to specify the items to be registered as transaction items using a method other than product scanning, as described above, then the operation to specify the items is considered to have been performed, and ACT114 in Figure 4 is judged as YES, and the process proceeds to ACT161 in Figure 7. As ACT161, processor 101 displays the product confirmation screen on touch panel 104. The product confirmation screen is a screen that allows the customer CU to confirm the specified product.

[0090] Figure 16 shows an example of a product confirmation screen. The product confirmation screen shown in Figure 16 is an example of what happens when an operation is performed to select a product with the product name "JJJJJJ" and a unit price of 68 yen. The product confirmation screen shown in Figure 16 is a screen in which the display area ARF is used instead of the display areas ARC, ARD and buttons BUD, BUE, BUF found on the registration screen.

[0091] Display area ARF represents display areas ARG, ARH, the numeric keypad TKA, and buttons BUN, BUO. Display area ARF displays the string "JJJJJJ" which represents the name of the product specified by the previous operation (hereinafter referred to as the specified product). Above display area ARH, display area ARF displays the string "68 yen" which represents the unit price of the specified product. Below display area ARH, display area ARF displays the string "68 yen" which represents the total price of the specified product.

[0092] The display area ARG shows an image of the appearance of the specified product. However, in Figure 16, the illustration of this image is omitted. The display area ARH shows a numerical value representing the currently specified quantity for the specified product. In this embodiment, the initial value of this quantity is set to "1", and Figure 16 shows the state in which this initial value "1" is displayed in the display area ARH. The numeric keypad TKA includes multiple soft keys for receiving quantity specifications by the customer CU. Button BUN is a soft key for receiving a specification to cancel the registration of the product specified in the previous operation as a trading product. Button BUO is a soft key for receiving a specification to register the specified product as a trading product with the quantity displayed in the display area ARH.

[0093] The customer CU checks the displayed content in the display area ARF to confirm whether the product they attempted to specify in their previous operation is the designated product. If they wish to register the designated product as a trading product, they specify registration by performing a predetermined operation, such as touching button BUO. However, the customer CU can set the quantity before specifying registration. In other words, if the customer CU wants to change the quantity displayed in the display area ARH, they specify the new quantity using the numeric keypad TKA.

[0094] After the processor 101 displays the product confirmation screen as ACT161 in Figure 7, it proceeds to ACT162. As ACT162, processor 101 checks whether registration has been specified as described above. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT163.

[0095] As ACT163, processor 101 checks whether the quantity was specified as described above. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT162. Thus, processor 101 waits for registration or quantity to be specified as ACT162 and ACT163. Then, if a quantity is specified as described above, processor 101 determines YES in ACT163 and proceeds to ACT164.

[0096] As ACT164, processor 101 obtains the quantity specified by the operation of the numeric keypad TKA. As ACT165, processor 101 updates the product confirmation screen to display the acquired quantity in display area ARH. That is, if, for example, "1" and "1" are entered using the numeric keypad TKA, processor 101 updates the product confirmation screen to display "11" in display area ARH and to display the total amount below display area ARH as "748". After this, processor 101 returns to the standby state for ACT162 and ACT163.

[0097] If the customer CU specifies registration as described above, the processor 101 determines YES in ACT162 and proceeds to ACT166. As ACT166, processor 101 checks whether quantity verification is necessary. Processor 101 checks whether the quantity setting is abnormal, for example, if the set quantity is above a predetermined threshold, and whether it meets predetermined conditions. The above threshold may be determined as appropriate by the person who determined the specifications of the transaction processing device 100. However, the quantity that may be abnormal may differ depending on the goods being traded. Therefore, it is preferable to set the above threshold according to the circumstances of the store. For example, in a store that handles many products that can be bought in bulk, it is expected that the threshold will be set higher, taking into account the quantity that can be bought in bulk. Also, in a store that handles many high-priced products that are rarely purchased in multiples at the same time, it is expected that the threshold will be set lower, for example, "2". It is also acceptable to set different thresholds for each product. Then, if processor 101 determines that quantity verification is necessary and YES, and proceeds to ACT167, if the set quantity meets the predetermined conditions.

[0098] At this point, the processor 101 determines that the quantity, which is the target numerical value, is within the numerical range defined as being above a threshold, and is therefore in a state requiring confirmation. Thus, by having the processor 101 execute information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as a determination means. As ACT167, processor 101 displays a quantity confirmation screen on touch panel 104. The quantity confirmation screen is a screen that allows the customer CU to confirm whether the set quantity is correct.

[0099] Figure 17 shows an example of a quantity confirmation screen. The quantity confirmation screen shown in Figure 17 is an example of what happens when the product confirmation screen, which shows "11" in the display area ARH shown in Figure 16, is displayed, and as a result of registration being specified, the processor 101 proceeds to ACT167, and a window WID is displayed as a pop-up for the product confirmation screen.

[0100] The window WID includes the text message MEG and buttons BUP and BUQ. The text message MEG represents a message prompting customer CU to confirm that the item should be registered as a trading product with a quantity of "11". "11" is the number displayed in the ARH display area on the product confirmation screen when registration was specified. The button BUP is a soft key used to confirm that the quantity shown in the text message MEG is correct. The button BUQ is a soft key used to confirm that the quantity shown in the text message MEG is incorrect. Thus, the quantity confirmation screen is an example of information used to prompt confirmation. The processor 101 then performs information processing based on the transaction processing program PRA, and the computer, with the processor 101 as its central component, functions as an output means.

[0101] If the quantity expressed in the text message MEG is correct, the customer CU will indicate that the quantity is correct by performing a predetermined action, such as touching the button BUP. If the quantity expressed in the text message MEG is incorrect, the customer CU will indicate that it is incorrect by performing a predetermined action, such as touching the button BUQ.

[0102] After the processor 101 displays the quantity confirmation screen as ACT167 in Figure 7, it proceeds to ACT168. As ACT168, processor 101 verifies whether it has been specified to register the specified product in the set quantity. If the quantity is specified as described above, processor 101 determines that registration has been specified and proceeds to ACT169. If the set quantity does not meet the predetermined conditions, processor 101 determines NO in ACT166, indicating that quantity verification is not necessary, and proceeds to ACT169, skipping ACT167 and ACT168.

[0103] As ACT169, processor 101 updates the transaction data to add the specified product to the transaction items in the set quantity. As ACT170, processor 101 displays a registration screen on touch panel 104 showing the contents of the transaction data after it was updated in ACT169. After this, processor 101 returns to ACT112 to ACT115 in Figure 4.

[0104] On the other hand, if the processor 101 is found to have an incorrect quantity as described above, it determines NO in ACT168, assuming that registration was not specified, and proceeds to ACT171. As ACT171, processor 101 displays a "checking" screen on touch panel 104. The "checking" screen is a screen that notifies the customer CU that the attendant AT is performing a check. The "checking" screen displays text messages such as "A staff member is checking your order" or "Please wait a moment."

[0105] As ACT172, the processor 101 notifies the monitoring device 300 of the quantity. For example, the processor 101 sends predetermined notification data to the monitoring device 300 from the communication unit 113 to the communication network 2 to notify the set quantity along with the notification of the specified product.

[0106] When the above notification data is transmitted to the monitoring device 300 via the communication network 2 and received by the communication unit 307, the processor 301 in the monitoring device 300 performs monitoring processing in the same manner as described above. However, in the check screen displayed as ACT311 in Figure 10, the processor 301 will display the text message MEB in Figure 11 as a message prompting the attendant AT to confirm the set quantity for the specified product. The processor 301 will also play a video showing the product brought in by the customer CU.

[0107] The attendant AT visually inspects the check screen and determines whether the quantity set by the customer CU is incorrect in light of the number of specified items brought in. The attendant AT then decides whether to cancel the previous quantity specification or to take action by remotely operating the transaction processing device 100 that notified the customer. If the attendant AT decides to cancel the previous quantity specification, they specify the cancellation by performing a predetermined operation, such as touching the BUP button. If the attendant AT decides to take action by remote operation, they specify the remote operation by performing a predetermined operation, such as touching the BUQ button.

[0108] Now, in the transaction processing unit 100, after the processor 101 notifies the quantity as ACT172 in Figure 7, it proceeds to ACT173. As ACT173, processor 101 checks whether a correction has been instructed through monitoring. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT174.

[0109] As ACT174, processor 101 checks through monitoring whether a previous cancellation was instructed. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT173.

[0110] Thus, processor 101 waits for modifications or cancellations as ACT173 and ACT174. When the instruction data sent from monitoring device 300 to instruct a cancellation, as described above, is transmitted to transaction processing device 100 via communication network 2 and received by communication unit 113, processor 101 determines YES in ACT174, returns to ACT161, and repeats ACT161 onwards as described above. In other words, processor 101 redoes the confirmation of the specified goods, including the acceptance of the quantity specification.

[0111] Now, if Attendant AT determines that any modification is necessary regarding the notified quantity, he / she will specify remote operation and perform the appropriate operation for the above modification. When the instruction data transmitted from the monitoring device 300 in response to this operation is transmitted to the transaction processing device 100 via the communication network 2 and received by the communication unit 113, the processor 101 of the transaction processing device 100 determines YES at ACT173 in Figure 7 and proceeds to ACT116 in Figure 4.

[0112] As ACT116, processor 101 updates the transaction data according to the data representing the modifications included in the instruction data mentioned above. As ACT117, processor 101 displays a correction notification screen on touch panel 104. The correction notification screen displayed here is similar to the one shown in Figure 13, for example, but the content of the text messages MED and MEE is changed according to the correction. As ACT118, processor 101 displays a registration screen on touch panel 104 showing the contents of the transaction data after it has been updated in ACT116. After this, processor 101 returns to the standby state for ACT112 to ACT115.

[0113] As described above, if the quantity specified by the customer CU is a value that does not require confirmation, the transaction processing device 100 registers the transaction product with that quantity without receiving any input from the customer CU or the attendant AT. However, if the specified quantity is a value that requires confirmation, the transaction processing device 100 displays a quantity confirmation screen to allow the customer to confirm the quantity. Furthermore, if the specified quantity needs to be corrected, the transaction processing device 100 either has the customer CU specify it again or corrects it according to instructions from the attendant AT. As described above, the computer with the processor 101 as its central component functions as a registration means by having the processor 101 execute information processing based on the transaction processing program PRA.

[0114] Once the customer CU has finished registering all the items to be purchased as transaction items, they specify the transition to checkout by performing a predetermined operation, such as touching the button BUF on the registration screen. In response, the processor 101 determines YES at ACT115 in Figure 4 and proceeds to ACT119.

[0115] As ACT119, processor 101 performs accounting processing. That is, processor 101 calculates the amount to be settled according to the registered transaction details. Then processor 101 performs settlement processing to settle the calculated amount. The details of this accounting processing may be the same as, for example, the processing performed in existing fully self-service type POS terminals. Once processor 101 has finished the accounting processing, it terminates the transaction processing for that transaction.

[0116] As described above, according to the transaction processing system 1, if the number of PBA shopping bags taken out at once from the shopping bag dispenser 200, the time interval between two consecutive product scans, or the quantity specified by the customer CU falls within a predetermined verification range and is in a state requiring verification, the transaction processing device 100 will display various verification screens prompting the customer CU to confirm. This reduces the chances of an unintentional operation by the customer being mistakenly accepted as a legitimate operation. Furthermore, if the transaction processing system 1 is outside the verification range, it proceeds with the registration process without performing verification, thus avoiding unnecessary verification for operations that are unlikely to be inappropriate and not significantly reducing usability.

[0117] Furthermore, according to the transaction processing system 1, if the customer CU determines that the relevant value is inappropriate after confirmation, the correction of that value will be made through the judgment of the attendant AT. This prevents the relevant value from being unfairly modified by the customer CU.

[0118] [Second Embodiment] Figure 18 is a diagram showing the schematic configuration of the transaction processing system 3 according to the second embodiment. In Figure 18, the same reference numerals are used for elements that are the same as those shown in Figure 1, and their detailed explanations are omitted. In the transaction processing system 3, the shopping bag dispenser 200 does not form a pair with the transaction processing device 100. In the example in Figure 18, one shopping bag dispenser 200 is installed near the entrance of the checkout area. However, the number of shopping bag dispensers 200 is arbitrary. The installation location of the shopping bag dispensers 200 is also arbitrary. For example, one of two shopping bag dispensers 200 could be installed between the two transaction processing devices 100 shown at the top of Figure 18, and the other shopping bag dispenser 200 could be installed between the two transaction processing devices 100 shown at the bottom of Figure 18. The transaction processing system 3 further includes a management terminal 400 that is paired with the shopping bag display unit 200. In other words, the transaction processing system 3 has the same number of management terminals 400 as the shopping bag display units 200.

[0119] Figure 19 is a block diagram showing the main circuit configuration of the management terminal 400. The management terminal 400 includes a processor 401, a main memory unit 402, a sub-memory unit 403, an interface unit 404, a touch panel 405, a communication unit 406, and a transmission line 407, among other things.

[0120] The general functions of the processor 401, main memory unit 402, sub-memory unit 403, interface unit 404, touch panel 405, communication unit 406, and transmission line 407 are equivalent to those of the processor 101, main memory unit 102, sub-memory unit 103, interface unit 114, touch panel 104, communication unit 113, and transmission line 115. In the first embodiment, the shopping bag dispenser 200 is connected to the transaction processing device 100, but in the second embodiment, it is connected to the interface unit 404 of the management terminal 400. However, the sub-storage unit 403 stores the management program PRC instead of the transaction processing program PRA. The management program PRC is an application program that describes the processing procedures performed by the processor 401 to realize the functions of the management terminal 400.

[0121] The hardware of the management terminal 400 is expected to be, for example, a tablet computer. The management program PRC is typically stored in the sub-storage unit 403 when the management terminal 400 is transferred. However, the management program PRC may be written to the sub-storage unit 403 by the processor 401 in response to an operation by any worker after the management terminal 400 has been transferred. In this case, the sub-storage unit 403 of the transferred management terminal 400 may or may not store a program of the same type as the management program PRC, albeit a different version. In the former case, the program written to the sub-storage unit 403 later will be used in place of the program of the same type but a different version. The transfer of the management program PRC can be performed by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network.

[0122] Next, we will explain the operation of the transaction processing system 3, which is configured as described above. Note that only operations that differ from those of transaction processing system 1 will be explained below. On the management terminal 400, which is in an operational state that manages the removal of shopping bags PBA from the shopping bag dispenser 200 by the customer CU, the processor 401 executes the following management processes based on the management program PRC.

[0123] Figure 20 is a flowchart of the management process. As ACT411, processor 401 displays a selection screen on touch panel 405. The selection screen allows the customer CU to select one of the multiple transaction processing units 100.

[0124] Figure 21 shows an example of a selection screen. The selection screen shown in Figure 21 is an example where four transaction processing units 100 are installed, as shown in Figure 18. These four transaction processing units 100 are represented by the associated buttons BUR, BUS, BUT, and BUU. The selection screen shown in Figure 21 also represents the text message MEH, which prompts the customer CU to specify which transaction processing unit 100 to use.

[0125] Customer CU proceeds to the checkout counter and, if purchasing a shopping bag PBA, takes a shopping bag PBA from the shopping bag dispenser 200 located near the entrance to the checkout counter. However, before taking a shopping bag PBA, Customer CU must select a transaction processing device 100 that is not being used by another customer and perform a predetermined operation on the management terminal 400 to specify that transaction processing device 100. For example, if Customer CU selects a transaction processing device 100 assigned the number "1", they specify the corresponding transaction processing device 100 by touching the button BUR shown in Figure 21. After this, Customer CU takes a shopping bag PBA from the shopping bag dispenser 200.

[0126] Furthermore, the processor 401 may check the operating status of the transaction processing unit 100 and, if a button associated with the transaction processing unit 100 is in use, it may indicate that it is disabled by graying it out or otherwise, and may also prevent the user from pressing that button.

[0127] Processor 401 displays the selection screen as ACT411, and then proceeds to ACT412. As ACT412, processor 101 waits for one of the transaction processing units 100 to be specified. When a transaction processing unit 100 is specified through a predetermined operation, such as touching one of the buttons BUR to BUU, it determines YES and proceeds to ACT413.

[0128] As ACT413, processor 401 sets the designated transaction processing unit 100 as the transfer destination. As ACT414, processor 101 awaits an ejection notification. As described above, when a customer CU takes a shopping bag PBA from the shopping bag dispenser 200, the detection processing unit 205 in the shopping bag dispenser 200 outputs notification data for removal notification, which includes information indicating the number of bags removed, via the interface unit 206, similar to the first embodiment. However, in this embodiment, the interface unit 206 is connected to the interface unit 404 of the management terminal 400, so the above notification data is received by the management terminal 400 via the interface unit 404. In response, the processor 401 determines that a removal notification has been made and YES in ACT 414, and proceeds to ACT 415.

[0129] As ACT415, processor 401 forwards the notification data sent from the shopping bag display unit 200 to the transaction processing unit 100, which has been determined as the destination in ACT413. In other words, processor 401 sends the notification data from communication unit 406 to communication network 2 addressed to the transaction processing unit 100. When this notification data is transmitted to the transaction processing unit 100 via communication network 2 and received by the communication unit 113 of the transaction processing unit 100, processor 101 of the transaction processing unit 100 determines YES in ACT112 in Figure 4. Processor 101 then processes the data in the same manner as in the first embodiment. Thus, with the transaction processing system 3, the same effects as in the first embodiment can be achieved without having to provide the shopping bag display unit 200 in conjunction with the transaction processing device 100.

[0130] Each of the above embodiments can be modified in various ways as follows. (First variation) Figure 22 shows an example of a modified configuration of the shopping bag display stand 200. Note that Figure 22 only shows the changes from the configuration shown in Figure 3. The shopping bag display stand 200 shown in Figure 22 is equipped with a transparency sensor 211 in addition to the shopping bag display stand 200 shown in Figure 3. Furthermore, the shopping bag display stand 200 shown in Figure 22 is equipped with a detection processing unit 212 in place of the detection processing unit 205 in the shopping bag display stand 200 shown in Figure 3. The transmission sensor 211 is attached to the housing 201 with space 202 in between, and measures the amount of light passing through space 202. In addition to the functions of the detection processing unit 205, the detection processing unit 212 also has the function of detecting the absence of plastic bags (PBA) in space 202 based on the amount of light measured by the transmission sensor 211. In other words, the shopping bag display unit 200 shown in Figure 22 is equipped with a function that detects when the shopping bags PBA stored in the space 202 have run out, in addition to the functionality of the shopping bag display unit 200 shown in Figure 3. Alternatively, the detection processing unit 212 may have, in addition to the functions of the detection processing unit 205, a function to detect when the amount of plastic bags PBA in the space 202 has decreased based on the amount of light measured by the transmission sensor 211. Alternatively, the detection processing unit 212 may have, in addition to the functions of the detection processing unit 205, a function to detect whether the amount of plastic bags PBA in space 202 has decreased or whether they are absent, based on the amount of light measured by the transmission sensor 211.

[0131] (Second variation) Figure 23 shows a schematic configuration of a modified plastic bag display stand. Elements identical to those shown in Figure 3 are denoted by the same reference numerals. The left side of Figure 23 is a front view. The right side of Figure 23 is a cross-sectional view taken along the arrow BB in the front view. The shopping bag dispenser 500 shown in Figure 23 comprises a housing 501. The housing 501 has spaces 502 and 503 formed inside. Space 502 houses multiple shopping bags PBA stacked on top of each other. Space 503 houses multiple shopping bags PBB stacked on top of each other. Shopping bags PBA and shopping bags PBB are of different sizes. Shopping bags PBA stored in space 502 are taken out by customers CU one at a time, in principle, through an opening 504 that connects space 502 to the outside of the shopping bag dispenser 500. Shopping bags PBB stored in space 503 are taken out by customers CU one at a time, in principle, through an opening 505 that connects space 503 to the outside of the shopping bag dispenser 500. However, if the plastic bags PBA become electrostatically charged, multiple plastic bags PBA may be removed from the dispensing opening 504 while stacked on top of each other. Similarly, if the plastic bags PBB become electrostatically charged, multiple plastic bags PBB may be removed from the dispensing opening 505 while stacked on top of each other.

[0132] The shopping bag dispenser 500 has a light transmission sensor 204 attached to the dispensing opening 504. The light transmission sensor 204 measures the amount of light passing through the dispensing opening 504. The shopping bag dispenser 500 also has a light transmission sensor 506 attached to the dispensing opening 505. The light transmission sensor 506 measures the amount of light passing through the dispensing opening 505.

[0133] An electronic unit is attached to the housing 501 in an appropriate manner, although this is not shown in the diagram. This electronic unit comprises an interface unit 206 and a detection processing unit 507. The detection processing unit 507 detects that a shopping bag PBA has been removed based on the change in light intensity measured by the transmission sensor 204, and determines the number of shopping bags PBA that have been removed based on the measured light intensity. The detection processing unit 507 detects that a shopping bag PBB has been removed based on the change in light intensity measured by the transmission sensor 506, and determines the number of shopping bags PBB that have been removed based on the measured light intensity. The detection processing unit 507 then notifies the interface unit 206 that it has detected the removal, along with the determined number of bags. Furthermore, if this shopping bag display unit 500 is used in place of the shopping bag display unit 200 in each of the above embodiments, the processor 101 in the transaction processing device 100 can distinguish between shopping bag PBA and shopping bag PBB and register them as transaction items based on notifications from the shopping bag display unit 500.

[0134] (Other variations) The detection processing units 205 and 507 do not need to determine the number of PBA and PBB shopping bags taken out at one time; they can simply detect whether there is a duplicate.

[0135] The processing performed by the detection processing units 205 and 507 may also be performed by, for example, the processor 101 in the transaction processing device 100. In this case, the first detection means and the second detection means will be provided in the transaction processing device 100.

[0136] It is also acceptable to prompt the attendant AT for confirmation without prompting the customer CU. In other words, for example, the processor 101 may omit at least one of ACT124~ACT127 in Figure 5, ACT146~ACT147 in Figure 6, or ACT166~ACT167 in Figure 7. In this case, the monitoring device 300 will be equipped with an output means. However, it is also possible to prompt the attendant AT for confirmation by, for example, illuminating the alarm lamp 111, in which case the transaction processing device 100 will be equipped with an output means to output information to prompt the attendant AT for confirmation.

[0137] The numerical value used to determine whether a product requires verification can be any value different from those listed in the above embodiment, such as the weight of the product. The numerical range used to determine whether a product requires verification can be defined in a form such as "below a threshold" or "greater than or equal to the first threshold and less than the second threshold." For example, in the case of selling prepared foods by weight, an extremely small quantity may raise suspicion of fraud, so a product designated as a transaction item may be judged as requiring verification if its weight is below a threshold.

[0138] The information output to prompt confirmation may be, for example, a voice message or request data to be displayed on the customer's communication terminal.

[0139] The attendant AT's task of confirming whether an action taken by the customer CU should be canceled may be performed by the attendant AT moving to the vicinity of the relevant transaction processing unit 100.

[0140] Various designations for attendant AT for transaction modifications may be accepted by the transaction processing device 100.

[0141] The configurations of each device in the above embodiment are examples, and elements not shown can be added or some of the illustrated elements can be removed as appropriate. For example, the transaction processing device 100 may be equipped with a surveillance camera for photographing the actions of customer CUs. The monitoring device 300 may also be equipped with functions for registration processing and accounting processing, and various devices for that purpose. Furthermore, the change dispenser 107 may be omitted from the transaction processing device 100.

[0142] Each of the functions realized by processors 101, 301, and 401 through information processing can also be partially or entirely realized by hardware that performs non-program-based information processing, such as logic circuits. Furthermore, each of the above functions can also be realized by combining the aforementioned hardware, such as logic circuits, with software control.

[0143] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of Symbols]

[0144] 1,3...Transaction processing system, 2...Communication network, 100...Transaction processing unit, 101,301,401...Processor, 102,302,402...Main memory unit, 103,303,403...Sub memory unit, 104,405...Touch panel, 105...Handheld scanner, 106...Fixed scanner, 107...Change machine, 108...Credit card reader, 109...Electronic money reader / writer, 110...Printer, 111...Alarm lamp, 112...Sound unit, 113,3 07,406...Communication unit, 114,206,404...Interface unit, 115,308,407...Transmission line, 200,500...Shopping bag display unit, 201...Enclosure, 202...Space, 203...Dispensing outlet, 204,211,506...Transmissive sensor, 205,212,507...Detection processing unit, 300...Monitoring device, 304...Input unit, 305...Display unit, 306...Sound unit, 400...Management terminal, 501...Enclosure, 502,503...Space, 504,505...Dispensing outlet.

Claims

1. A registration means for registering transaction details in response to customer operations, A determination means for determining whether a predetermined target numerical value related to the registration of transaction details by the registration means is in a state requiring confirmation, which is within a predetermined range of numerical values ​​that require confirmation. An output means that outputs information prompting confirmation in response to the determination means determining that the state requiring confirmation is in place, A transaction processing system equipped with the following features.

2. A fixture for storing shopping bags and for customers to take out these shopping bags, A first detection means for detecting the removal of a shopping bag from the fixture, A second detection means for detecting that the removal of shopping bags from the fixture was performed with multiple shopping bags stacked on top of each other, Furthermore, it is equipped with, The registration means adds one shopping bag to the transaction details in response to detection by the first detection means. The determination means determines, in response to detection by the second detection means, that the number of plastic bags taken out from the fixture is within a specified numerical range of two or more, and is therefore in a state requiring confirmation. The transaction processing system according to claim 1.

3. The determination means uses the numerical value specified by the customer when registering the transaction details by the registration means as the target numerical value, and a predetermined range of numerical values ​​as the confirmation range. The transaction processing system according to claim 1.

4. The determination means uses the time between two consecutive customer operations to specify the addition of transaction details by the registration means as the target value, and defines the confirmation range as a time range shorter than a predetermined time. The transaction processing system according to claim 1.

5. A registration means for registering transaction details in response to customer operations, A determination means for determining whether a predetermined target numerical value related to the registration of transaction details by the registration means is in a state requiring confirmation, which is within a predetermined range of numerical values ​​that require confirmation. An output means that outputs information prompting confirmation in response to the determination means determining that the state requiring confirmation is in place, A transaction processing device equipped with the following.

6. The computer installed in the transaction processing unit A registration means for registering transaction details in response to customer operations, A determination means for determining whether a predetermined target numerical value related to the registration of transaction details by the registration means is in a state requiring confirmation, which is within a predetermined range of numerical values ​​that require confirmation. An output means that outputs information prompting confirmation in response to the determination means determining that the state requiring confirmation is in place, An information processing program that enables a function to work.

Images