Monitoring support system and information processing program

Abstract

To make it possible to correct a falsely designated commodity in the case where a single-item commodity has been designated as a transaction commodity when registering a packaged bundle as a transaction commodity.SOLUTION: A monitoring support system includes acquisition means and display means. The acquisition means acquires, when a commodity designated as a transaction commodity on a registration terminal operated by a customer is a predetermined commodity to be checked, an image of the inside of a container for housing a commodity registered as a transaction object, the image being captured at predetermined timing relative to a timing at which the commodity to be checked was registered as the transaction commodity. The display means displays the image acquired by the acquisition means on a management terminal which is different from the registration terminal.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] Embodiments of the present invention relate to a monitoring support system and an information processing program.

Background Art

[0002] A transaction processing system configured to register products to be transacted (hereinafter referred to as transaction products) in accordance with a terminal operation performed by a customer at a store floor is known, for example, as a shopping cart system having a product registration function equipped with a tablet terminal or the like. As one sales form of products processed for transaction in such a transaction processing system, there are products sold as a product obtained by packaging a plurality of products that can also be sold individually as single-item sales products into one package (hereinafter referred to as a bulk package product). For example, a six-pack of canned beer is one example.

[0003] For bulk package products, a product code as the bulk package product is generally displayed on the package for bundling a plurality of single-item sales products. When registering a bulk package product as a transaction product, the product code for the bulk package product should be input. However, the single-item sales products included in a bulk package product often have a product code as a single-item sales product displayed separately, and in many cases, the product code is exposed outside the package for bundling a plurality of single-item sales products. For this reason, when registering a bulk package product as a transaction product, there is a risk that the product code of the single-item sales product is erroneously input. Under such circumstances, when a product different from the product taken out from the sales floor by the customer is specified as a transaction product, it has been desired that measures can be taken to correct it.

Prior Art Literature

Patent Literature

[0004] [Patent Document 1] Japanese Patent Publication No. 2019-133389 [Overview of the project] [Problems that the invention aims to solve]

[0005] The problem that this invention aims to solve is to provide a monitoring support system and information processing device that can take measures to correct the situation when a different product from the product a customer took from the sales floor is designated as the product to be traded. [Means for solving the problem]

[0006] The monitoring support system of the embodiment is This system supports monitoring in a transaction processing system where both bundled package products (which are multiple products that could also be sold individually) and individual products can be designated as transaction items by a customer using a registration terminal, and includes detection means, It is equipped with means for acquisition and means for display. The detection means detects when goods are placed into a container for holding goods that have been registered as traded goods. The means of acquisition is , Nobori Products designated as trading items on the recording terminal Sold individually If it is a product, Individual sales The timing when the product is registered as an item for transaction The product being placed into the container was first detected by the detection means after the product was placed into the container. timing Inside the container The captured image is acquired. The display means is determined by the acquisition means. Once the image is acquired, The acquired images are displayed on a separate management terminal, distinct from the registration terminal. [Brief explanation of the drawing]

[0007] [Figure 1] A block diagram illustrating the schematic configuration of a transaction processing system according to one embodiment. [Figure 2] A block diagram showing the main circuit configuration of the transaction processing device in Figure 1. [Figure 3] This diagram schematically represents the structure of a single data record included in the product master database shown in Figure 2. [Figure 4] A schematic diagram showing the structure of transaction data in Figure 2. [Figure 5] A block diagram showing the main circuit configuration of the attendant terminal in Figure 1. [Figure 6] A block diagram showing the main circuit configuration of the cart terminal in Figure 1. [Figure 7] A perspective view illustrating an example of how a cart terminal is attached to a cart. [Figure 8] A flowchart of cart processing. [Figure 9] A flowchart of cart processing. [Figure 10] A flowchart of transaction processing. [Figure 11] A flowchart of transaction processing. [Figure 12] A diagram illustrating an example of a registration screen. [Figure 13] A flowchart of attendant support processing. [Figure 14] A diagram illustrating an example of an attendant screen. [Figure 15] A diagram illustrating a display example of an immediate confirmation window. [Figure 16] A diagram illustrating an example of a confirmation guidance window. [Figure 17] A diagram illustrating an example of a clerk operation window. [Figure 18] A diagram illustrating an example of a reconfirmation window. MODE FOR CARRYING OUT THE INVENTION

[0008] Hereinafter, an example of an embodiment will be described with reference to the drawings. In the present embodiment, a transaction processing system having a function as a monitoring support system will be described. FIG. 1 is a block diagram illustrating a schematic configuration of a transaction processing system 1 according to the present embodiment.

[0009] The transaction processing system 1 is configured such that a transaction processing device 100, an accounting machine 200, an attendant terminal 300, and a cart terminal 400 can communicate with each other via a communication network 2. The communication network 2 may be the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, or the like, used alone or in any appropriate combination. As an example, the Internet and a mobile communication network are used in combination as the communication network 2. Note that any number of the transaction processing device 100, checkout machine 200, attendant terminal 300, and cart terminal 400 may be included in the transaction processing system 1, and only one of each is shown in FIG. 1.

[0010] The transaction processing device 100 is an information processing device that performs information processing for providing a transaction processing service that processes product sales transactions between a customer and a store in accordance with operations performed by the customer at the store, using the checkout machine 200 and the cart terminal 400 as user interface terminals. The transaction processing device 100 is implemented, for example, as a cloud server and provides the transaction processing service to a plurality of stores. The transaction processing device 100 may be implemented, for example, as a local server and provides the transaction processing service to only one store.

[0011] The checkout machine 200 is installed in a store and executes checkout processing related to checkout of transactions processed by the transaction processing device 100. The checkout machine 200 receives operations performed by an operator during checkout processing. The operator of the checkout machine 200 is mainly the customer. A store clerk may also serve as the operator of the checkout machine 200 in some cases.

[0012] The attendant terminal 300 is an information processing terminal operated by a store clerk who fulfills a role called an attendant. The attendant terminal 300 is a terminal device that provides a user interface for information processing to support the store clerk's work related to transactions processed by the transaction processing system 1. The store clerk's work is, for example, work of monitoring the progress status of transactions being processed and appropriately supporting customers. The attendant terminal 300 is an example of a management terminal.

[0013] The cart terminal 400 is an information processing terminal attached to a shopping cart (hereinafter referred to as "cart") provided in the store. The cart terminal 400 is lent to the customer along with the cart. The cart terminal 400 is a terminal device that receives operations from the customer for transaction processing on the transaction processing device 100. The cart terminal 400 may include an information and communication terminal that is lent to the customer by the store and carried and used by the customer. One of the operations performed by the customer for transaction processing is the operation to specify the product to be registered as a transaction product, as will be described later. Thus, the cart terminal 400 is an example of a registration terminal. Another example of a registration terminal may include an information and communication terminal such as a smartphone that is owned by the customer and carried and used by the customer.

[0014] Figure 2 is a block diagram showing the main circuit configuration of the transaction processing device 100. The transaction processing device 100 includes a processor 101, a main storage unit 102, an auxiliary storage unit 103, a communication unit 104, and a transmission line 105, etc. The processor 101, the main storage unit 102, the auxiliary storage unit 103, and the communication unit 104 are able to communicate with each other via the transmission line 105.

[0015] By connecting the processor 101, the main storage unit 102, and the auxiliary storage unit 103 with a transmission line 105, a computer is configured to perform information processing for controlling the transaction processing device 100. The processor 101 corresponds to the central part of the computer described above. The processor 101 performs information processing to control each part in order to realize various functions as a transaction processing device 100, in accordance with information processing programs such as the operating system and application programs.

[0016] 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.

[0017] The auxiliary storage unit 103 corresponds to the auxiliary storage portion of the computer described above. The auxiliary storage unit 103 can utilize, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk drive), an SSD (solid state drive), or various other well-known storage devices. The auxiliary storage unit 103 stores data used by the processor 101 in performing various processes and data generated by the processing performed by the processor 101. The auxiliary storage unit 103 may also store the information processing program described above. In this embodiment, the auxiliary storage unit 103 stores the transaction processing program PRA, which is one of the information processing programs. The transaction processing program PRA is an application program that describes the procedures for information processing (hereinafter referred to as transaction processing) for registering goods that are the subject of a transaction (hereinafter referred to as transaction goods) and settling the payment for registered transaction goods. The transaction processing program PRA also describes the procedures for attendant support processing, which will be described later. A portion of the storage area of ​​the auxiliary storage unit 103 is used as a storage area for the product master database DBA and the transaction data DAA. The product master database DBA is a collection of data for managing each individual product that can be registered as a transaction product. The transaction data DAA is data that represents the details of a single transaction.

[0018] The communication unit 104 performs communication processing for data communication via the communication network 2. For example, an existing wired communication device for the internet can be used as the communication unit 104. Alternatively, a wireless communication device connected to the communication network 2 via wireless communication may be used as the communication unit 104, either in place of or in addition to the wired communication device. The transmission line 105 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected parts.

[0019] Figure 3 schematically represents the structure of a single data record REA included in the product master database DBA. The product master database DBA is a collection of multiple data records REA associated with each product that can be registered as a trading product. A data record REA includes fields FAA, FAB, FAC, and FAD. Field FAA is set with the product code as the identifier of the associated product. Field FAB is set with the product name assigned to the associated product. Field FAC is set with the manufacturer name of the associated product. A data record REA includes several fields that are not shown after field FAC. These fields contain various data used for processing transactions related to the associated product, such as unit price or applicable tax classification. Field FAD is set with a flag (hereinafter referred to as the bundle flag) that indicates whether confirmation is required for bundled package products that include the associated products. The bundle flag selectively takes two states: "Confirmation Required" or "Confirmation Not Required". Products associated with a data record REA where the bundle flag set in field FAD is in the state of "Confirmation Required" are products that require confirmation.

[0020] The status of the bundled flag may be determined as appropriate by the sales manager of the associated products. For example, the bundled flag may be set to "Confirmation Required" if the associated product is sold individually and may be included in another bundled package product. However, even for products that meet the above conditions, the status of "Confirmation Required" or "Confirmation Not Required" may be determined as appropriate for each product. For example, even if the above conditions are met, if the barcode displayed on the product is not exposed externally in the bundled package product, the bundled flag may be set to "Confirmation Not Required".

[0021] The number of fields included in the data record REA and the data to be set in each field may be determined as appropriate by, for example, the designer or administrator of the transaction processing device 100. The product master database DBA may be updated through maintenance work when changes occur, such as when products that can be registered as transaction products are added or deleted, or when changes occur regarding products that can be registered as transaction products, such as changes in unit price, but it will not be updated in response to the various processes described later.

[0022] Figure 4 is a schematic diagram illustrating the structure of the transaction data DAA. Transaction data DAA is generated for each transaction being processed by the transaction processing unit 100 and stored in the auxiliary storage unit 103. Thus, there may be cases where no transaction data DAA is stored in the auxiliary storage unit 103, or where multiple transaction data DAAs are stored in the auxiliary storage unit 103 simultaneously.

[0023] The transaction data DAA includes fields FBA, FBB, FBC, and FBD. The transaction data DAA may include any number of fields after field FBD. Field FBA is set with the transaction code as the identifier of the transaction. Field FBB is set with the terminal code as the identifier of the cart terminal 400 used by the customer making the transaction. Field FBC is set with the time the customer using the associated cart terminal 400 entered the store. Field FBD is set with a flag (hereinafter referred to as the confirmation flag) for managing the settings regarding confirmation by store staff before payment for the transaction. The confirmation flag takes one of three states: "Not applicable," "Confirmation required," or "Confirmation not required." If there are products already registered as transaction products, fields FBE, FBF, ... associated with each of those transaction products are added to the transaction data DAA. Fields FBE, FBF, ... are set with product data for each separate transaction product. The product data includes the product code and quantity as the identifier of the transaction product. Product data may include various other pieces of information, such as product name, unit price, and discount information. Transaction data DAA is generated and updated as needed through the transaction processing described later.

[0024] Now, as the hardware for the transaction processing device 100, for example, a general-purpose server device can be used. Generally, the transfer of the transaction processing device 100 is carried out with the transaction processing program PRA stored in the auxiliary storage unit 103, but without the transaction data DAA and tag table TAA. However, the hardware in a state where the transaction processing program PRA is not stored in the auxiliary storage unit 103, or in a state where a different version of the same type of application program is stored in the auxiliary storage unit 103, and the transaction processing program PRA may be transferred separately. Furthermore, the transaction processing device 100 may be configured by writing the transaction processing program PRA to the auxiliary storage unit 103 in response to the operation of any operator. The transfer of the transaction processing program PRA can be carried out 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.

[0025] Figure 5 is a block diagram showing the main circuit configuration of the attendant terminal 300. The attendant terminal 300 includes a processor 301, a main memory unit 302, an auxiliary memory unit 303, a touch panel 304, a communication unit 305, and a transmission line 306, among other things.

[0026] The general functions of the processor 301, main memory unit 302, auxiliary memory unit 303, communication unit 305, and transmission line 306 are the same as those of the processor 101, main memory unit 102, auxiliary memory unit 103, and transmission line 105, so their explanation will be omitted. However, the auxiliary memory unit 303 stores the attendant terminal program PRB instead of the transaction processing program PRA. The attendant terminal program PRB is an application program that describes the information processing procedure of the processor 301 for operating the information processing device as an attendant terminal 300.

[0027] The touch panel 304 displays a screen for presenting information to the operator of the attendant terminal 300. The touch panel 304 also accepts input from the operator via touch operations on the screen. The hardware for the attendant terminal 300 may be, for example, a stationary computer device. Alternatively, the hardware for the attendant terminal 300 may be a tablet-type information processing device or a portable information processing device such as a smartphone.

[0028] Figure 6 is a block diagram showing the main circuit configuration of the cart terminal 400. The cart terminal 400 includes a processor 401, a main memory unit 402, an auxiliary memory unit 403, a touch panel 404, a camera 405, an interface unit 406, a wireless communication unit 407, and a transmission line 408, among other things.

[0029] The general functions of the processor 401, main memory unit 402, auxiliary memory unit 403, and transmission line 408 are equivalent to those of the processor 101, main memory unit 102, auxiliary memory unit 103, and transmission line 105. The general functions of the touch panel 404 are also equivalent to those of the touch panel 304. However, the auxiliary memory unit 403 stores the cart terminal program PRC instead of the transaction processing program PRA. The cart terminal program PRC is an application program that describes the information processing procedure of the processor 401 for operating the information processing device as a cart terminal 400.

[0030] Camera 405 captures an image by photographing the entire interior space of the shopping basket placed on the cart. The image obtained by camera 405 will be referred to as the camera image below. The interface unit 406 is connected to external devices such as the weighing scale 498 and the scanner 499. The interface unit 406 interfaces with the connected external devices for data exchange. An existing USB (universal serial bus) controller can be used as the interface unit 406. The weighing scale 498 measures the weight of the shopping basket placed on the cart, along with the weight of the items placed inside. The scanner 499 is attached to the cart and optically scans 1D and 2D barcodes.

[0031] The wireless communication unit 407 performs communication processing for wireless data communication via the communication network 2. For example, an existing wireless communication device for a wireless LAN can be used as the wireless communication unit 407. Alternatively, a communication unit connected to the communication network 2 via a wired connection may be used instead of, or in addition to, the wireless communication unit 407. The basic hardware for the cart terminal 400 is expected to be, for example, the hardware of a tablet-type information processing device.

[0032] Figure 7 is a perspective view showing an example of how the cart terminal 400 is attached to the cart. The cart 900 comprises a caster section 910, a handle frame section 920, and a basket support section 930. The caster section 910 has four wheels 911 for smoothly moving the cart 900 on the floor. The wheels 911 are mounted on the frame 912 so as to be rotatable around a vertical axis.

[0033] The handle frame section 920 includes a pair of vertical frames 921, 921 and a handlebar 922. The vertical frames 921, 921 are erected above the two wheels of the caster section 910. The handlebar 922 connects the upper ends of the vertical frames 921, 921. The basket support section 930 is provided horizontally from the middle of the handle frame section 920. The basket support section 930 holds the shopping basket SB for storing goods. The caster section 910 can also hold the shopping basket SB on top of the frame 912.

[0034] A scanner 499 is attached to the middle of the handlebar 922. A pole 940 is attached to one of the vertical frames 921 such that its tip is positioned above the handlebar 922. The aforementioned cart terminal 400 and touch panel 404 are attached to the tip of this pole 940. The camera 405 of the cart terminal 400 is positioned facing the back of the touch panel 404 and is not shown in Figure 7. This camera 405 can take an overhead, bird's-eye view of the inside of the shopping basket SB, which is held by the basket support 930. A battery case 950 is mounted between vertical frames 921, 921 on the lower end of the handle frame section 920. The battery case 950 houses a battery used as an external power source for the cart terminal 400.

[0035] 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 just an example, and it is possible to change the order of some processes, omit some processes, or add other processes as appropriate. For example, in the following explanation, in order to explain the characteristic operation of this embodiment in an easy-to-understand manner, the explanation of some processes has been omitted. For example, processes are performed to remove products that have already been registered as trading products from the trading products, or to change the number of products that have already been registered as trading products, but these processes have been omitted from the description. Also, for example, if some error occurs, processes may be performed to deal with that error, but such processes have been omitted from the description.

[0036] When the shopping cart terminal 400 is in an operational state for use by a customer, the processor 401 performs information processing for the user interface related to the registration of trading products (hereinafter referred to as shopping cart processing) based on the shopping cart terminal program PRC. Figures 8 and 9 are flowcharts of the cart processing.

[0037] In Figure 8, the processor 401, designated as ACT401, displays a standby screen on the touch panel 404. The standby screen informs the customer that the cart terminal 400 is in standby mode and ready for new use. The processor 401 then proceeds to ACT402 while displaying the standby screen. As ACT402, processor 401 waits for the operation to be performed to initiate use.

[0038] The customer performs a predetermined operation to begin using the cart terminal 400, which is in a standby state. As part of the operation to begin using the cart terminal 400, the customer may also perform an operation to enter a customer code into the cart terminal 400. Upon seeing this operation performed on the cart terminal 400, the processor 401 determines YES in ACT 402 and proceeds to ACT 403.

[0039] As ACT403, processor 401 requests transaction processing unit 100 to start processing a transaction. That is, processor 401 sends request data for a check-in request from wireless communication unit 407 to communication network 2 addressed to transaction processing unit 100. Processor 401 includes the check-in data stored in auxiliary storage unit 403 and the terminal code of the cart terminal 400 in the above request data. The terminal code is pre-assigned to the relevant cart terminal 400 in a way that distinguishes it from other cart terminals 400 and is stored, for example, in auxiliary storage unit 403. If a customer code is entered, processor 401 also includes the customer code in the request data. The check-in data includes at least information for identifying the store where the cart terminal 400 is used. This information is, for example, a store code defined as a store identifier. If there is no need to distinguish between multiple stores operated by the same company, this information may be, for example, a company code for identifying the company. Also, if the same store code can be used by different companies, this information may include, for example, a company code and a store code. However, if the transaction processing unit 100 is operated as a local server, the request data does not need to include the store code.

[0040] When check-in data is transmitted to the transaction processing unit 100 via the communication network 2, the transaction processing unit 100 receives the check-in data via the communication unit 104 and temporarily stores it in the main storage unit 102 or the auxiliary storage unit 103. In this manner, when the check-in data sent from the cart terminal 400 is received by the transaction processing device 100, the processor 101 starts transaction processing for that transaction according to the transaction processing program PRA.

[0041] If processor 101 is already executing a transaction for a different customer, it will start a new transaction as a separate thread from that transaction. In other words, processor 101 may execute multiple transaction processes in parallel. However, the following explanation will focus only on the processing of a transaction for a single customer. Thus, in the following explanation, "cart terminal 400" refers to a single cart terminal 400 used by the customer for the transaction processing of interest. Also, in the following explanation, "transaction" refers to the transaction that is the subject of the processing of interest. Figures 10 and 11 are flowcharts of the transaction process.

[0042] As ACT101, processor 101 generates new transaction data DAA related to the target transaction and stores it in auxiliary storage unit 103. For example, processor 101 determines a new transaction code different from the transaction code used to identify other transactions according to a predetermined rule and sets this transaction code in field FBA of the new transaction data DAA. For example, processor 101 sets the terminal code included in the request data in field FBB of the new transaction data DAA. For example, processor 101 sets the current date and time as the entry date and time in field FBC of the new transaction data DAA. Alternatively, field FBC may be set to the entry date and time included in the request data. In this case, processor 401 in the cart terminal 400 includes in the request data the date and time of the operation to start use, or the date and time the request data was generated, as the entry date and time. For example, processor 101 sets the confirmation flag set in field FBD of the new transaction data DAA to indicate "not applicable". Furthermore, if the request data includes a customer code, processor 101 sets that customer code into the new transaction data DAA. Since the transaction products have not yet been registered, processor 101 does not include product data in the newly generated transaction data DAA.

[0043] As ACT102, processor 101 instructs cart terminal 400 to display the registration screen. For example, processor 101 sends instruction data to cart terminal 400 from communication unit 104 to communication network 2 to instruct the cart terminal 400 to display the registration screen. For example, processor 101 generates screen data for the registration screen and includes this screen data in the instruction data. Alternatively, processor 101 may include data to be displayed on the registration screen in the instruction data instead of screen data for the registration screen.

[0044] When the instruction data in the cart terminal 400 is transmitted via the communication network 2 and received by the wireless communication unit 407, the processor 401 proceeds to ACT 404 in Figure 8. As ACT404, the processor 401 displays a registration screen on the touch panel 404 according to the instruction data. For example, if the instruction data includes screen data, the processor 401 displays the screen represented by that screen data on the touch panel 404. For example, if the instruction data includes data that should be displayed on the registration screen, the processor 401 generates the registration screen by unfolding the display objects corresponding to that data into a predetermined form for the registration screen and displays it on the touch panel 404. Furthermore, the display of other screens on the cart terminal 400, as described below, is performed using the same process as described above.

[0045] Figure 12 shows an example of a registration screen. Note that the screen examples shown in Figure 12 and other figures may omit the illustration of some display objects. The registration screen displays an image representing the registration status in the display area ARA. The registration screen is represented by the button BUA. In the example in Figure 12, the image in the display area ARA shows that two items have been registered, one each with product names "AAAAAAAAAA" and "BBBBBBBBBB", with unit prices of 178 yen and 198 yen respectively, and their reference price is 406 yen. The reference price is calculated by subtracting discounts from various services such as coupons from the sum of the unit prices of all traded items. If the traded items and applicable services remain unchanged when the transaction is settled, this reference price becomes the settlement amount. The image in the display area ARA changes sequentially according to the registration status of the traded items. When processor 101 first executes ACT 102 in Figure 10, the traded items have not yet been registered, so the display area ARA at this time does not display information for each item, but instead displays an image indicating a total of 0 items and a reference price of 0 yen. Button BUA is a soft key used by the operator to initiate the accounting process.

[0046] The customer moves around the store with the cart terminal 400, searching for the items they wish to purchase. When the customer wishes to register an item as a new item to purchase, they perform a predetermined operation on the cart terminal 400 to specify that item. This operation may include, for example, scanning a barcode representing a product code, such as a JAN (Japanese article number) code, with the scanner 499. Another operation may involve tapping a preset button associated with a product displayed on the touch panel 404. Yet another operation may involve directly entering the product code on the touch panel 404.

[0047] In Figure 8, as ACT405, processor 401 checks whether or not a product to be registered has been specified. If processor 401 cannot confirm the relevant event, it determines NO and proceeds to ACT406. As ACT406, processor 401 checks whether accounting has been instructed. If processor 401 cannot confirm the relevant event, it determines NO and returns to ACT405. Thus, processor 401 awaits product designation or accounting instructions as ACT405 and ACT406. If the above-described operation for product designation is performed, processor 401 determines YES in ACT405 and proceeds to ACT407. As ACT407, processor 401 requests the transaction processing unit 100 to register the product, along with notification of the product code of the specified product.

[0048] In the transaction processing unit 100, processor 101 instructs the display of the registration screen as ACT102 in Figure 10, and then proceeds to ACT103. As ACT103, processor 101 checks whether or not product registration has been requested. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT104. As ACT104, processor 101 checks whether or not accounting commencement has been requested. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT103. Thus, processor 101 waits for a request for registration or accounting as ACT103 and ACT104. If a request for registration is made as described above, processor 101 determines YES in ACT103 and proceeds to ACT105.

[0049] As ACT105, processor 101 registers a product as a trading product by updating the transaction data DAA to include product data related to the requested product in response to a product registration request. As ACT106, processor 101 instructs cart terminal 400 to update the registration screen so that an image corresponding to the updated transaction data DAA is displayed in the display area ARA.

[0050] As ACT107, processor 101 checks whether there is a bundled package product that includes the registered transaction product. For example, processor 101 checks the bundled flag set in field FAD of data record REA, which is associated with the registered transaction product in the product master database DBA. Then, if the bundled flag indicates a state of "requires confirmation", processor 101 determines that there is a bundled package product in question and proceeds to ACT108.

[0051] As ACT108, processor 101 sets the confirmation flag in the FBD field of the transaction data DAA to a state indicating "Confirmation Required". After this, processor 101 proceeds to ACT109. If the bundle flag indicates a state indicating "Confirmation Not Required", processor 101 determines NO in ACT107, indicating that there is no bundle package product corresponding to that item, and proceeds to ACT109, skipping ACT108. As ACT109, processor 101 awaits the power-on notification, which will be described later.

[0052] After requesting registration as ACT407 in Figure 8 at the cart terminal 400, the processor 401 proceeds to ACT408. As ACT408, processor 401 updates the registration screen displayed on touch panel 404 in response to the update instruction from processor 101. As ACT409, processor 401 waits for products to be placed into the shopping basket SB held in the basket receiving section 930 of the cart 900, which is equipped with a cart terminal 400.

[0053] Once the customer has completed the aforementioned steps to specify the product to be registered as a transaction item, they add the selected product to their shopping cart SB. It is a rule of customer use of the cart terminal 400 that the previously selected product must be added to the shopping cart SB before proceeding to specify another product.

[0054] When an item is placed in the shopping cart SB, the measurement value from the weight scale 498 changes. The processor 401 monitors this change in measurement value and detects when an item has been placed in the shopping cart SB. If the processor 401 detects that an item has been placed, it determines YES in ACT 409 and proceeds to ACT 410. Thus, by having the processor 401 perform information processing based on the cart terminal program PRC, the computer with the processor 401 as its central component realizes its function as a detection means in cooperation with the weight scale 498.

[0055] As ACT410, processor 401 notifies transaction processing unit 100 of the basket being placed in the basket. For example, processor 401 sends predetermined notification data for notifying the basket of the basket being placed to the transaction processing unit 100 via wireless communication unit 407 to the communication network 2. After detecting the product being placed in the basket, processor 401 acquires the camera image obtained by camera 405 and includes it in the notification data. After this, processor 401 returns to the standby state for ACT405 and ACT406.

[0056] In the transaction processing device 100, if the notification data for the above-mentioned input notification is transmitted to the transaction processing device 100 via the communication network 2 and received by the communication unit 104, the processor 101 determines YES in ACT 109 in Figure 10. Then the processor 101 returns to the waiting state of ACT 103 and ACT 104.

[0057] The transaction processing unit 100 then executes attendant support processing, which is information processing to assist store employees using the attendant terminal 300, as a separate thread from the transaction processing, based on the transaction processing program PRA. Note that the transaction processing and attendant support processing may also be executed based on separate information processing programs.

[0058] Figure 13 is a flowchart of the attendant support process. As ACT141, processor 101 instructs attendant terminal 300 to display the attendant screen. The attendant screen is a screen that allows the attendant to check the progress of transactions for each cart terminal 400. For example, processor 101 sends instruction data to attendant terminal 300 from communication unit 104 to communication network 2 to instruct the display of the attendant screen. For example, processor 101 generates screen data for the attendant screen and includes this screen data in the instruction data. Alternatively, for example, processor 101 may include data that should be displayed on the attendant screen in the instruction data instead of screen data for the attendant screen.

[0059] When the processor 301 in the attendant terminal 300 receives the instruction data transmitted via the communication network 2 and received by the communication unit 305, it displays the attendant screen corresponding to the instruction data on the touch panel 304. For example, if the instruction data includes screen data, the processor 301 displays the screen represented by that screen data on the touch panel 304. For example, if the instruction data includes data that should be displayed on the attendant screen, the processor 301 generates the attendant screen by unfolding the display object corresponding to that data into a predetermined attendant screen form and displays it on the touch panel 304. Furthermore, the display of other screens on the attendant terminal 300, as described below, is performed using the same process as described above.

[0060] Figure 14 shows an example of an attendant screen. The attendant screen shown in Figure 14 displays the transaction progress of each of the four shopping cart terminals 400 in four separate display areas. This is an example where two of the shopping cart terminals 400 have successfully registered the transaction items, and the other two are not being used by customers. Each display area may also include a notification to the store staff in cases where the transaction items registered on the corresponding shopping cart terminal 400 include items that require age verification of the buyer.

[0061] In the transaction processing unit 100, processor 101 instructs the display of the attendant screen as ACT141 in Figure 13, and then proceeds to ACT142. As ACT142, processor 101 checks whether the transaction progress status at each of the cart terminals 400 has changed. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT143. As ACT143, processor 101 checks whether an attendant operation was performed on attendant terminal 300. If processor 101 cannot confirm the event, it determines NO and returns to ACT142. Thus, processor 101 waits for a change in the situation or an attendant operation as ACT142 and ACT143. When an operation is performed by a store employee on the attendant terminal 300 and this is notified from the attendant terminal 300, processor 101 determines YES in ACT143 and proceeds to process to respond to the attendant operation. The processing of processor 101 in this case will not be explained here.

[0062] As mentioned above, when the processor 101 detects a change in the progress of a transaction, such as when the transaction data DAA is updated, it determines YES in ACT142 and proceeds to ACT144. As ACT144, processor 101 instructs attendant terminal 300 to update the attendant screen to reflect changes in the transaction progress.

[0063] As ACT145, processor 101 checks whether confirmation is required regarding the bundled package product. For example, if the change that occurred is the registration of a new trading product, and the bundled flag set in the FAD field of the data record REA associated with that trading product in the product master database DBA is "Confirmation Required", then processor 101 determines that confirmation is required and proceeds to ACT146.

[0064] As ACT146, processor 101 waits for the newly registered trading item to be added to the cart. Then, if, for example, notification data sent from the cart terminal 400 where the new registration was made to notify the cart addition has been transmitted to the trading processing unit 100 via the communication network 2 and received by the communication unit 104, processor 101 determines YES and proceeds to ACT147. As ACT147, processor 101 instructs attendant terminal 300 to display the immediate confirmation window. The immediate confirmation window is a pop-up window that allows store staff to immediately confirm the status of items being placed in shopping basket SB.

[0065] Figure 15 shows an example of the display of the immediate confirmation window. The Instant Confirmation Window WIA shown in Figure 15 is displayed overlaid on the attendant screen after it has been updated in response to a new product with the product name "EEEEEEEEEE" being registered as a transaction item in the cart terminal 400 referred to as "Cart 1," while the attendant screen is in the state shown in Figure 14. Furthermore, in accordance with the fact that the product with the product name "EEEEEEEEEE" is a single-item sale item that may be included in a bundled package product, the Instant Confirmation Window WIA is placed within the display area corresponding to the cart terminal 400 referred to as "Cart 1."

[0066] The immediate confirmation window (WIA) represents the camera image (IMA) and the text string (CSA). The camera image (IMA) is the camera image included in the notification data for notifying the customer that an item has been placed in the shopping cart. The text string (CSA) represents a text message prompting the attendant to confirm whether the item placed in the cart is a single-item sale item.

[0067] In other words, the processor 101 acquires the camera image at this time and displays the camera image on the attendant terminal 300. By having the processor 101 perform information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as both an acquisition means and a display means.

[0068] Thus, the store clerk can visually check the camera image IMA displayed in the instant confirmation window WIA to confirm whether the items placed in the shopping basket SB are individual items. If the clerk confirms that the items are individual items, they can indicate that it is correct by performing a predetermined operation, such as tapping the string "Yes" in the text message MEA. If the clerk confirms that the items are not individual items, such as when a bundled package item is placed in the basket, they can indicate that it is incorrect by performing a predetermined operation, such as tapping the string "No" in the text message MEA. When the processor 301 in the attendant terminal 300 receives these indications, it notifies the transaction processing unit 100 of which indication was made.

[0069] In the transaction processing unit 100, processor 101 instructs the display of a confirmation window as ACT147 in Figure 13, and then proceeds to ACT148. As ACT148, processor 101 checks whether it has been specified as appropriate. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT149. As ACT149, processor 101 checks whether or not an inappropriate event has been specified. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT148. Thus, processor 101 awaits a designation of appropriate or inappropriate as ACT148 and ACT149. When processor 101 receives notification from attendant terminal 300 that an appropriate designation has been made, as described above, it determines YES in ACT148 and proceeds to ACT150.

[0070] As ACT150, processor 101 changes the confirmation flag set in the FBD field of the transaction data DAA for the relevant transaction to a state indicating "no confirmation required". After this, processor 101 proceeds to ACT151. If processor 101 is notified by attendant terminal 300 that an inappropriate designation has been made, it determines YES in ACT149, skips ACT150, and proceeds to ACT151.

[0071] As ACT151, processor 101 instructs attendant terminal 300 to terminate the display of the immediate confirmation window WIA. In response to this instruction, processor 301 on attendant terminal 300 terminates the display of the immediate confirmation window WIA. After this, processor 101 returns to the waiting state for ACT142 and ACT143. If processor 101 cannot confirm that confirmation is necessary as described above, it determines NO in ACT145 and returns to the waiting state for ACT142 and ACT143 without executing ACT146 to ACT151.

[0072] Once the customer has finished registering the items to be traded, they perform a predetermined operation on the cart terminal 400 to instruct the payment process. In response, the processor 401 on the cart terminal 400 determines YES at ACT406 in Figure 8 and proceeds to ACT411. As ACT411, processor 401 requests accounting from transaction processing unit 100.

[0073] In response to this request, the processor 101 in the transaction processing unit 100 determines YES at ACT104 in Figure 10 and proceeds to ACT121 in Figure 11. As ACT121, processor 101 checks whether confirmation of the bundled package product is required. For example, if the confirmation flag set in the FBD field of the transaction data DAA indicates "Confirmation Required", processor 101 determines that confirmation is required and YES, and proceeds to ACT122. As ACT122, processor 101 instructs cart terminal 400 to display a confirmation window. The confirmation window is a screen that informs the customer that they need to have their purchase checked by a store employee.

[0074] After requesting payment as ACT411 in Figure 8 at the cart terminal 400, the processor 401 proceeds to ACT412. As ACT412, processor 401 updates the display on touch panel 404 in response to instructions from transaction processing unit 100. In other words, if processor 401 is instructed to display the confirmation window as described above, it displays the confirmation window. Processor 401 displays the confirmation window and other various windows described later overlaid on the registration screen that was previously displayed on touch panel 404. However, each window may also be displayed replacing the registration screen.

[0075] Figure 16 shows an example of a confirmation window. The confirmation guidance window WIB shown in Figure 16 represents the text string CSB and buttons BUB and BUC. The text string CSB is a text message that informs the customer that they need to have their purchase confirmed by a store employee. Button BUB is a soft key that the operator uses to instruct the system to return to the product registration state. Button BUC is a soft key that the operator uses to instruct the system to proceed with the store employee's confirmation procedure.

[0076] If the customer wishes to proceed with payment, they will initiate the verification process by tapping the BUC button or performing other predetermined actions. Before or after this action, the customer will request verification from the staff. Alternatively, upon receiving a request from the customer, the staff member will initiate the verification process by tapping the BUC button or performing other predetermined actions.

[0077] After displaying a pop-up window as ACT412 in Figure 8, processor 401 proceeds to ACT413. As ACT413, processor 401 checks whether the pop-up window displayed as ACT412 is a confirmation guidance window WIB. If processor 401 has displayed the confirmation guidance window WIB as described above, it determines YES and proceeds to ACT421 in Figure 9. As ACT421, processor 401 checks whether or not the store clerk has been instructed to perform the verification procedure. If processor 401 cannot confirm the relevant event, it determines NO and proceeds to ACT422. As ACT422, processor 401 checks whether it has been instructed to return to product registration. If processor 401 cannot confirm the relevant event, it determines NO and returns to ACT421. Thus, processor 401 awaits an execute instruction or a return instruction as ACT421 and ACT422. If an execute instruction is received as described above, processor 401 determines YES in ACT421 and proceeds to ACT423. As ACT423, processor 401 notifies transaction processing unit 100 that the store clerk has been instructed to perform the verification procedure.

[0078] In the transaction processing unit 100, once the processor 101 has finished issuing the display instruction as ACT122 in Figure 11, it proceeds to ACT123. As ACT123, processor 101 checks whether or not the store clerk has been instructed to perform the verification procedure. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT124. As ACT124, processor 101 checks whether it has been instructed to return to product registration. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT123. Thus, processor 101 awaits an execute instruction or a return instruction as ACT123 and ACT124. When processor 101 is notified that an execution instruction has been given as described above, it determines YES in ACT123 and proceeds to ACT125. As ACT125, processor 101 instructs cart terminal 400 to display the employee operation window. The employee operation window is a window that guides the customer to take action from an employee to begin the employee's verification process.

[0079] After the processor 401 notifies the cart terminal 400 of the execution instruction as ACT423 in Figure 9, it proceeds to ACT424. As ACT424, processor 401 displays the employee operation window on touch panel 404 in response to the above display instructions from transaction processing device 100.

[0080] Figure 17 shows an example of a store clerk operation window. The WIC (Workshop Operator Window) represents the string CSC and the BUD (Button). The string CSC represents a text message to guide the shop employee on the operations they should perform. In this embodiment, the shop employee's operation to initiate verification is to scan the barcode displayed on their employee ID card, which represents the employee code as the employee identifier, with the camera 405. The string CSC shown in Figure 17 represents the text message to guide them through this operation. The BUD (Button) is a soft key used by the operator to instruct the system to return to the product registration state.

[0081] When a customer requests verification, the employee scans the barcode displayed on their employee ID card by holding it up to camera 405. The operation the employee must perform here may be changed to any predetermined operation that a customer would not normally perform, such as entering an employee passcode, and the employee may receive multiple types of operations. The employee performing the operation is equivalent to the verification officer. The employee code from the employee ID card may also be read using an external card reader (not shown) attached to the cart terminal 400.

[0082] In Figure 9, as ACT425, processor 401 checks whether or not an operation was performed by a store employee. If processor 401 cannot confirm the event, it determines NO and proceeds to ACT426. As ACT426, processor 401 checks whether it has been instructed to return to product registration. If processor 401 cannot confirm the relevant event, it determines NO and returns to ACT425. Thus, processor 401 waits for a store clerk operation or return instruction as ACT425 and ACT426. If processor 401 confirms that the predetermined store clerk operation described above has been performed, it determines YES in ACT425 and proceeds to ACT427. As ACT427, processor 401 notifies transaction processing unit 100 that an employee operation has been performed.

[0083] In the transaction processing unit 100, once the processor 101 has finished issuing the display instruction for ACT125 in Figure 11, it proceeds to ACT126. As ACT126, processor 101 checks whether or not an action was taken by a store employee. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT127. As ACT127, processor 101 checks whether or not it has been instructed to return to product registration. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT126. Thus, processor 101 waits for a store clerk operation or return instruction as ACT126 and ACT127. When processor 101 is notified that a store clerk operation has been performed as described above, it determines YES in ACT126 and proceeds to ACT128. As ACT128, processor 101 instructs cart terminal 400 to display a reconfirmation window. The reconfirmation window is a window that guides store staff to perform a visual reconfirmation.

[0084] After the processor 401 in the cart terminal 400 notifies the store clerk of the operation as ACT427 in Figure 9, it proceeds to ACT428. As ACT428, processor 401 displays a reconfirmation window on touch panel 404 in response to the above display instruction from transaction processing unit 100.

[0085] Figure 18 shows an example of a confirmation window. The reconfirmation window WID represents the strings CSD, CSE, and buttons BUE, BUF. The string CSD represents a fixed text message to guide the store clerk on what they need to do. The string CSE represents the product name and quantity of the product that needs to be checked in the shopping cart SB. In the transaction processing device 100, the processor 101 searches the product master database DBA for all data records REA in which the product is set in field FAA for each product code contained in each product data in the transaction data. Then, from among the corresponding data records REA, the processor 101 selects all of those in which the summary flag set in field FAD indicates "check required". The processor 101 then generates the string CSE to represent the product name set in field FAB of the selected data record REA and the quantity shown in the product data included in the transaction data, including the product code set in field FAA of the selected data record REA. Note that Figure 18 is an example where there is only one product to be checked; if there are multiple products to be checked, the string CSE will represent the product names and quantities of those multiple products. Button BUE is a soft key used by the operator to instruct the system to return to the state for product registration. Button BUF is a soft key used by the operator to specify that the input status of the product to be checked is correct.

[0086] Thus, the processor 101 displays the confirmation window WID on the cart terminal 400, performing a guidance operation to allow an employee to confirm the payment for items requiring confirmation. In other words, 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 guidance means.

[0087] The store clerk visually checks the items in the shopping cart SB to confirm whether the individual product represented by the string CSE in the reconfirmation window WID has been correctly added to the shopping cart SB. If the clerk determines that it is correct, they indicate that it is correct by performing a predetermined operation, such as tapping the button BUF.

[0088] On the cart terminal 400, processor 401 displays the confirmation window WID as ACT428 in Figure 9, and then proceeds to ACT429. As ACT429, processor 401 checks whether it has been specified as appropriate. If processor 401 cannot confirm the relevant event, it determines NO and proceeds to ACT430. As ACT430, processor 401 checks whether it has been instructed to return to product registration. If processor 401 cannot confirm the relevant event, it determines NO and returns to ACT429. Thus, processor 401 awaits a valid designation or return instruction in ACT429 and ACT430. If processor 401 confirms that it has been designated as valid as described above, it determines YES in ACT429 and proceeds to ACT431. As ACT431, processor 401 notifies transaction processing unit 100 of the appropriate designation.

[0089] In the transaction processing unit 100, once the processor 101 has finished issuing the display instruction as ACT128 in Figure 11, it proceeds to ACT129. As ACT129, processor 101 checks whether it has been specified as appropriate. If processor 101 cannot confirm the relevant event, it determines NO and proceeds to ACT130. As ACT130, processor 101 checks whether or not it has been instructed to return to product registration. If processor 101 cannot confirm the relevant event, it determines NO and returns to ACT129. Thus, processor 101 awaits a proper designation or return instruction as ACT129 and ACT130. If processor 101 receives notification of a proper designation from cart terminal 400 as described above, it determines YES in ACT129 and proceeds to ACT131.

[0090] As ACT131, processor 101 executes an accounting transfer process to transfer accounting processing to accounting machine 200. For example, processor 101 first instructs cart terminal 400 to display the accounting screen. The accounting screen is a screen for transferring accounting processing related to a transaction to accounting machine 200. The accounting screen displays a barcode representing information that allows accounting machine 200 to make inquiries about the relevant transaction to transaction processing device 100.

[0091] After the processor 401 at the cart terminal 400 notifies the appropriate designation as ACT431 in Figure 9, it proceeds to ACT432. As ACT432, processor 401 displays an accounting screen on touch panel 404 in response to the above display instructions from transaction processing device 100.

[0092] If there are multiple payment machines 200 installed in the store, the customer can choose any unused payment machine 200 and have the barcode scanner on that payment machine 200 read the barcode displayed on the payment screen. In response, the payment machine 200 requests payment data from the transaction processing unit 100 based on the information represented by the barcode read by the barcode scanner.

[0093] In the transaction processing device 100, the processor 101 waits for a request for accounting data as part of the accounting transfer process of ACT131 in Figure 11. Upon receiving a request for accounting data as described above, it sends the accounting data to the requesting accounting machine 200 so that the accounting machine 200 can settle the requested transaction.

[0094] In this manner, the accounting machine 200, in response to the accounting data transmitted from the transaction processing device 100, displays a screen as appropriate, receives customer input regarding accounting, and performs the processing to account for the transaction based on the accounting data. The processing performed by this accounting machine 200 may be similar to the processing performed by the accounting machine in an existing POS system, for example.

[0095] Furthermore, regarding the transfer of accounting processing related to transactions from the cart terminal 400 to the accounting machine 200, in addition to the above, this may also be achieved, for example, by transferring accounting data wirelessly when the cart terminal 400 approaches a specific accounting machine 200. Also, if the accounting machine 200 is in the form of a gate, accounting data related to transactions may be transferred when the cart terminal 400 approaches the gate.

[0096] As described above, in the transaction processing device 100, the processor 101 displays the reconfirmation window WID and allows settlement only after the store clerk has completed their verification that the transaction is appropriate. In other words, the processor 101 inhibits settlement until the verification is complete, and by executing information processing based on the transaction processing program PRA, the computer with the processor 101 as its central component functions as a means of inhibition.

[0097] As ACT132, processor 101 instructs cart terminal 400 to display a completion screen. The completion screen is a screen that notifies the customer that processing of the current transaction on cart terminal 400 has been completed. With this, processor 101 terminates the transaction processing for this transaction.

[0098] After the processor 401 displays the accounting screen as ACT432 in Figure 9 in the cart terminal 400, it proceeds to ACT433. As ACT433, processor 401 displays the completion screen on touch panel 404 in response to the above display instruction from transaction processing device 100. Then, when a predetermined condition is met, such as the duration of the completion screen display exceeding a predetermined time, processor 401 terminates the display of the completion screen and ends the current cart process. Immediately thereafter, or when a predetermined restart condition is met, processor 401 starts a new cart process to prepare for use by the next customer.

[0099] Furthermore, if a customer wishes to cancel proceeding to checkout and return to registering products when the confirmation guidance window WIB shown in Figure 16 is displayed, they will indicate this by performing a predetermined operation such as tapping button BUB. Also, if a customer wishes to cancel the confirmation by the store clerk and return to registering products when the store clerk operation window WIC shown in Figure 17 is displayed, they will indicate this by performing a predetermined operation such as tapping button BUD. Furthermore, if the store clerk confirms, as a result of the confirmation according to the reconfirmation window WID shown in Figure 18, that the product entry is inappropriate, they will indicate this by performing a predetermined operation such as tapping button BUE.

[0100] In the cart terminal 400, the processor 401, in response to the return instruction described above, determines YES in one of ACT422, ACT426, or ACT430 in Figure 9, and proceeds to ACT434. As ACT434, processor 401 notifies transaction processing unit 100 that a return instruction has been issued.

[0101] As ACT435, processor 401 terminates the display of the various pop-up screens that are currently displayed. After this, processor 401 returns to the waiting state of ACT405 and ACT406 in Figure 8. Furthermore, if the store clerk confirms, as a result of the confirmation according to the reconfirmation window WID shown in Figure 18, that the product has been added incorrectly, they will operate the cart terminal 400 to correct the registration of the incorrect transaction product.

[0102] In the transaction processing unit, processor 101, in response to the notification of the return instruction described above, determines YES in one of ACT124, ACT127, or ACT130 in Figure 11, and returns to the waiting state of ACT103 and ACT104 in Figure 10. Furthermore, when the processor 101 performs the verification in ACT121, if, for example, the verification flag set in the FBD field of the transaction data DAA is not "requires verification", it determines that verification is not necessary and proceeds to ACT131, skipping ACT122 to ACT130. Thus, in this case, the processor 401 in the cart terminal 400 receives an instruction from the transaction processing unit 100 to display the accounting screen in response to the accounting request in ACT411 in Figure 8, and therefore displays the accounting screen on the touch panel 404 in ACT412. The processor 401 then determines NO in ACT413 and proceeds to ACT433 in Figure 9.

[0103] As described above, when a product that may be included in a bundled package product is registered as a transaction product, the transaction processing device 100 acquires a camera image of the inside of the shopping cart SB from the cart terminal 400 and displays it on the attendant terminal 300 as an immediate confirmation window WIA as shown in Figure 15. Thus, the store clerk can quickly confirm, based on the display on the attendant terminal 300, whether the individually sold product registered as a transaction product has been properly placed into the shopping cart SB, that is, whether an individually sold product has been mistakenly registered as a transaction product when registering a bundled package product as a transaction product. As a result, if an individually sold product is designated as a transaction product when registering a bundled package product as a transaction product, it becomes possible to take prompt action to correct it.

[0104] Furthermore, the transaction processing device 100 is configured to detect when an item is placed in the shopping cart SB, and after the item subject to verification has been registered as a transaction item, it acquires and displays a camera image taken when the item is detected to have been placed in the cart. In this way, it is possible to display a camera image taken of the inside of the shopping cart SB with the item subject to verification or a bundled package containing that item placed inside.

[0105] Furthermore, the transaction processing unit 100 receives confirmation that the product input is correct in the immediate confirmation window WIA shown in Figure 15. If the transaction processing unit 100 attempts to proceed to checkout without this confirmation, it will guide the customer to have a store employee reconfirm the transaction. In this way, the risk of incorrect product input going unaddressed due to insufficient confirmation in the immediate confirmation window WIA can be reduced.

[0106] Furthermore, the transaction processing device 100 will not allow settlement until the above reconfirmation is complete. This prevents settlement from being carried out with improperly registered products.

[0107] Furthermore, the transaction processing device 100 displays a screen prompting the staff member to check whether bundled package products have been placed in the container, similar to the immediate confirmation window WIA. This makes it easy for the staff member to understand that the camera image displayed on the attendant terminal 300 is for checking whether bundled package products have been placed in the container, and thus allows for accurate support of the verification process.

[0108] This embodiment can be modified in various ways as follows: The placement of items into the shopping cart SB may be detected, for example, by image processing of camera images, or by another sensor such as an infrared sensor. In the case of image processing, the detection of item placement may also be achieved by processing by the processor 101 in the transaction processing device 100 or by processing by the processor 301 in the attendant terminal 300.

[0109] The timing of the camera image capture displayed in the Instant Confirmation Window (WIA) can be determined independently of the detection of product addition to the shopping cart (SB). For example, the camera image captured at a predetermined time after product registration, or at the time of the next product registration, can be displayed in the Instant Confirmation Window (WIA).

[0110] In the above embodiment, the immediate confirmation window WIA prompts confirmation regarding bundled package products, thus assuming that individually sold products that may be included in bundled package products are designated as products requiring confirmation. However, the type of product used as a product requiring confirmation can be changed as appropriate. It is preferable that the content of the confirmation guidance in the immediate confirmation window WIA be adapted to the type of product designated as a product requiring confirmation, but it is also acceptable to simply guide the user to confirm the product requiring confirmation without showing the specific details to be confirmed, or to show only a camera image. Products requiring confirmation could be products that are similar in package size and weight but have different unit prices. For example, rice may be displayed side by side with multiple products of the same size and appearance but with completely different unit prices. In such cases, the above embodiment can also be applied to confirm that the barcode of the displayed rice is scanned, and then another rice product next to it is placed in the shopping basket SB.

[0111] In the above embodiment, some of the processing performed by the transaction processing device 100 may be performed by the accounting machine 200, the attendant terminal 300, or the cart terminal 400. For example, the updating of transaction data may be performed by the processor 401 in the cart terminal 400. For example, the processing of acquiring camera images from the cart terminal 400 may be performed by the processor 301 in the attendant terminal 300. For example, the processing for displaying camera images may be performed by the processor 301 in the attendant terminal 300. In other words, the monitoring support system of the present invention can be realized by a single device such as the transaction processing device 100, or it can be realized by the cooperation of at least two of the devices among the transaction processing device 100, the accounting machine 200, the attendant terminal 300, and the cart terminal 400.

[0112] To capture camera images, a separate camera attached to the cart may be used instead of the camera 405 on the cart terminal 400. The transaction processing device 100 may acquire the camera images from the camera via the cart terminal 400, or it may acquire them through direct communication via the communication network 2. In this case, a terminal device such as a smartphone used by the customer may be used as the registration terminal instead of the cart terminal 400.

[0113] The transaction data DAA may include a confirmation flag for each product data, and in ACT108 in Figure 10, the processor 101 may update the confirmation flag included in the product data that was added to the transaction data DAA in ACT105 immediately before. In this way, when multiple products requiring confirmation are registered as transaction products, it becomes possible to manage whether each of those products requires reconfirmation. Furthermore, if the processor 101 then sets the string CSE displayed in the reconfirmation window WID, which is instructed to be displayed as ACT128 in Figure 11, to represent only product information related to product data that includes a confirmation flag indicating a "requires confirmation" status, it becomes possible to omit reconfirmation of products that have already been confirmed as appropriate by the immediate confirmation window WIA, thereby reducing the workload for store staff.

[0114] 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.

[0115] 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. The invention described in the original claims of this application is listed below. [Note 1] When a product designated as a transaction item on a registration terminal operated by the customer is a predetermined product requiring verification, an acquisition means is provided to acquire an image of the inside of a container for containing the product that has been registered as the subject of the transaction, taken at a predetermined timing relative to the time when the product requiring verification was registered as the subject of the transaction. A display means for displaying the image acquired by the acquisition means on a management terminal separate from the registration terminal, A monitoring and support system equipped with the following features. [Note 2] Detection means for detecting the placement of the product into the container, Furthermore, The acquisition means acquires an image taken at the time when the detection means first detects the product being placed in the container, after the time when the product requiring verification is registered as the subject of a transaction. The monitoring support system described in Appendix 1. [Note 3] When the display means is displaying an image acquired by the acquisition means, if the item requiring verification, which has been registered as the subject of a transaction, has not been designated as having been correctly placed in the container, the guidance means provides guidance to have an employee verify the item when settling the payment for the item requiring verification. The monitoring support system described in Appendix 1 further includes the following: [Note 4] After the guidance operation by the guidance means, a deterrent means to prevent payment until confirmation by an attendant is completed. The monitoring support system described in Appendix 3 further includes the following: [Note 5] The display means displays an image acquired by the acquisition means and also displays a screen prompting the staff member to check whether the container does not contain bundled package products that include products requiring confirmation. The monitoring support system described in Appendix 1. [Note 6] Computers, When a product designated as a transaction item on a registration terminal operated by a customer is a predetermined product requiring verification, an acquisition means acquires an image of the inside of a container for containing the product registered as the subject of the transaction, taken at a predetermined timing relative to the time when the product requiring verification was registered as the subject of the transaction. A display means for displaying the image acquired by the acquisition means on a management terminal separate from the registration terminal, An information processing program that enables a function to work. [Explanation of Symbols]

[0116] 1...Transaction processing system, 2...Communication network, 100...Transaction processing unit, 200...Accounting machine, 300...Attendant terminal, 400...Cart terminal, 101, 301, 401...Processor, 102, 302, 402...Main memory unit, 103, 303, 403...Auxiliary memory unit, 104, 305...Communication unit, 304, 404...Touch panel, 405...Camera, 406...Interface unit, 407...Wireless communication unit, 498...Weighing scale, 499...Scanner.

Claims

1. A system that supports monitoring in a transaction processing system in which a bundled package product, which is a package of multiple products that can also be sold individually, and the said individual products can both be designated as transaction products by a customer using a registration terminal, A detection means for detecting the placement of goods into a container for holding goods that have been registered as trading goods, When the product designated as a transaction product on the registration terminal is the single-item sale product, the acquisition means acquires an image of the inside of the container at the time when the detection means first detects the product being placed into the container, after the time when the single-item sale product is registered as the subject of a transaction. When an image is acquired by the acquisition means, a display means is provided to display the acquired image on a management terminal separate from the registration terminal. A monitoring and support system equipped with the following features.

2. When the display means is displaying an image acquired by the acquisition means, if the registration terminal has not received confirmation that the individual product registered as the subject of the transaction has been correctly placed in the container, the guidance means causes the registration terminal to perform a guidance operation to have an employee confirm the individual product during payment. The monitoring support system according to claim 1, further comprising:

3. After the guidance operation by the aforementioned guidance means is performed, a deterrent means is in place to prevent payment until confirmation by an attendant is completed. The monitoring support system according to claim 2, further comprising:

4. The display means displays an image acquired by the acquisition means and also displays a screen prompting the staff member to check whether a bundled package product, which includes the product also sold as an individual item, has been placed in the container. The monitoring support system according to claim 1.

5. A monitoring support system that assists in monitoring a transaction processing system in which a bundled package product, which is a package of multiple products that can also be sold individually, and the said individual products can both be designated as transaction products by a customer using a registration terminal, comprises a determination means for determining whether a product has been placed into a container for holding a product that has been registered as a transaction product, and a computer provided in an information processing device that is configured together with a customer-operated registration terminal, When the product designated as a transaction product by the registration terminal is the single-item sale product, the acquisition means acquires an image of the inside of the container at the time when the determination means determines that the product was placed into the container after the time the single-item sale product was registered as the subject of the transaction, When an image is acquired by the acquisition means, a display means is provided to display the acquired image on a management terminal separate from the registration terminal. An information processing program that enables a function to work.

Images