System, sales data processing device, and program

Abstract

To support appropriate transactions. [Solution] The system comprises a registration unit, an acquisition unit, a display control unit, and a declaration reception unit. The registration unit registers products based on customer operations. The acquisition unit acquires images capturing the status of each product registration operation performed by the registration unit. The display control unit displays an image list, arranged by the acquisition unit, to the customer. The declaration reception unit accepts a declaration from the customer that payment will be made for each product registered by the registration unit. The display control unit displays the image list upon receipt of the declaration by the declaration reception unit.

Description

Technical Field

[0001] The present invention relates to a system, a sales data processing device, and a program.

Background Art

[0002] In recent years, full self-checkout has become widespread. In full self-checkout, products are registered by customer operations, and settlement is performed by customer operations (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art, there is a problem that unauthorized product registration may occur or product registration may be missed, and transactions may not be properly conducted.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technology capable of supporting appropriate transactions.

Means for Solving the Problems

[0006] In order to solve the above-described problems, a system according to an aspect of the present invention includes a registration unit that registers products by customer operations, an acquisition unit that respectively acquires captured images of situations related to the registration operations of each product by the registration unit, and a display control unit that displays an image list in which the captured images acquired by the acquisition unit are arranged side by side, toward the customer. The system is characterized by this.

[0007] To solve the above-mentioned problems, another aspect of the present invention is a sales data processing device comprising: a registration unit that registers products based on customer operations; an acquisition unit that acquires captured images of the status of each product registration operation performed by the registration unit; and a display control unit that displays an image list arranged by the acquisition unit to the customer.

[0008] To solve the above-mentioned problems, another aspect of the present invention is a program that causes the computer of a sales data processing system to function as a registration unit that registers products based on customer operations, an acquisition unit that acquires images capturing the status of each product registration operation by the registration unit, and a display control unit that displays an image list, which is an arrangement of the images acquired by the acquisition unit, to the customer. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the network configuration of the sales data processing system according to this embodiment. [Figure 2] This is a perspective view showing an example of the appearance of a registration and settlement device. [Figure 3] This is a block diagram showing an example of the hardware configuration of a registration and settlement device. [Figure 4] This is a block diagram showing an example of the functional configuration of a registration and settlement device. [Figure 5] This figure shows an example of screen transitions for the customer-side display unit controlled by the display control unit. [Figure 6] This figure shows an example of screen transitions for the customer-side display unit controlled by the display control unit. [Figure 7] This flowchart shows an example of the registration and settlement process performed by the registration and settlement device according to this embodiment. [Figure 8] This is an explanatory diagram showing the network configuration of the sales data processing system related to Modification Example 1. [Figure 9]This is a block diagram including an example of the functional configuration of a sales data processing system according to Modification Example 1. [Figure 10] This is a sequence diagram showing the processing flow from product registration to transaction completion in a sales data processing system. [Figure 11] This is an explanatory diagram showing the network configuration of the sales data processing system related to Modification Example 2. [Figure 12] This is a block diagram including an example of the functional configuration of the sales data processing system according to Modification Example 2. [Figure 13] This flowchart shows an example of the exit process performed by the exit device according to Modification 2. [Modes for carrying out the invention]

[0010] (Embodiment) The following embodiment describes a configuration in which a fully self-checkout system is used.

[0011] (Network configuration of sales data processing system St) Figure 1 shows an example of the network configuration of the sales data processing system St according to this embodiment. The sales data processing system St is installed in various types of stores. These stores include, for example, retail stores and restaurants. Retail stores include, for example, supermarkets, convenience stores, drugstores, discount stores, department stores, and general merchandise stores. Restaurants include fast food restaurants, restaurants, bars, cafes, diners, and food courts. In this embodiment, the store is a supermarket.

[0012] The sales data processing system St shown in FIG. 1 includes a store controller 10, a transaction status management device 11, and registration settlement devices 20 (20-1 to 20-n). Each device is communicably connected via a network 55. Each device is a computer device provided with a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), a communication unit, and the like. The network 55 is a LAN (Local Area Network) or a WAN (Wide Area Network), and may be wired or wireless.

[0013] (Store controller 10) The store controller 10 stores various types of information necessary for transactions. The various types of information include registration information and settlement information generated in the registration settlement device 20. The various types of information also include a product master. The product master is a file that stores product information such as product identification information (for example, JAN (Japanese Article Number) code), product name, and selling price for each product. Furthermore, the product master includes not only fixed-amount products but also product identification information, product names, and unit prices (gram unit prices) of products that require weighing (non-fixed-weight products). The various types of information stored by the store controller 10 also include inventory status, sales history, deposit and withdrawal records, information on special sales, member information, and the like.

[0014] (Transaction status management device 11) The transaction status management device 11 is a monitoring monitor. Specifically, the transaction status management device 11 displays the processing status of the registration settlement device 20 and controls the registration settlement device 20. For example, a store clerk (monitoring clerk) is arranged in the transaction status management device 11, and the registration settlement device 20 is monitored by the monitoring clerk. The status of each of the plurality of registration settlement devices 20 is displayed on the transaction status management device 11. Specifically, the transaction status management device 11 displays a plurality of screens (split screens) corresponding to each of the plurality of registration settlement devices 20 and displays the status of each registration settlement device 20. Note that the transaction status management device 11 can also cancel the split screen and display a screen corresponding to one registration settlement device 20 (large screen display) according to the operation of the monitoring clerk. The monitoring clerk supports the customer operating the registration settlement device 20 and checks the age of the customer when an age confirmation product such as alcohol is registered in the registration settlement device 20 in the full self-service mode described later.

[0015] (Registration and settlement device 20) The registration settlement device 20 (20-1 to 20-n) is a POS (Point Of sales) terminal device capable of registering and settling goods. Specifically, the registration settlement device 20 includes a registration unit and a settlement unit. The registration unit executes a registration process for registering goods. The registration unit generates registration information including the product information of the goods purchased by the customer in the registration process. The settlement unit executes a settlement process based on the registration information generated in the registration process. The settlement unit generates settlement information including the type of settlement and the amount of deposits and withdrawals in the settlement process. In FIG. 1, the number of registration settlement devices 20 (n) indicates a plurality of units, but it may also be one unit.

[0016] (Operation mode) The registration settlement device 20 can switch the operation mode. The operation mode here includes (A) full self-service mode, (B) clerk registration mode, and (C) accounting-only mode. Each operation mode will be described below. It is assumed that the registration settlement device 20 according to the present embodiment operates in the full self-service mode.

[0017] (A) Full self-service mode is an operating mode in which the customer registers products on the device (self-registration) and the customer completes payment on the device (self-payment).

[0018] (B) The staff registration mode is an operating mode in which a staff member registers products and performs face-to-face payment at the device or self-payment at the registration payment device 20 in the payment-only mode. Face-to-face payment is a payment made at the device in face with a staff member, based on the customer's actions. The registration payment device 20 may also be equipped with a change dispenser on the staff member's side, in addition to or instead of the customer's side. In this case, payment in the staff registration mode may also be made by the staff member receiving cash from the customer and performing the payment, in addition to or instead of face-to-face payment.

[0019] In the employee registration mode, the registration payment device 20 outputs registration information to enable self-payment at other registration payment devices 20 (in the payment-only mode). Outputting registration information involves transmitting the registration information to other registration payment devices 20. However, outputting registration information may also involve encoding the registration information and displaying it on a display medium. The display medium may be, for example, paper or an electronic device such as a smartphone.

[0020] (C) The dedicated payment mode is a mode that operates in the other registration payment device 20 described above. Specifically, the dedicated payment mode is a mode in which self-payment is performed by acquiring registration information registered by the registration payment device 20 in the employee registration mode. Acquisition of registration information is done by receiving registration information from the registration payment device 20 in the employee registration mode. However, acquisition of registration information may also be done by reading a code displayed on a display medium.

[0021] The registration and payment device 20 does not need to be capable of switching operating modes. Specifically, the registration and payment device 20 may be a registration and payment device that only has the function of full self mode.

[0022] (Configuration equipped with a staff terminal) Furthermore, the sales data processing system St may be equipped with an employee terminal carried by the employee. The employee terminal may, for example, be capable of displaying a screen similar to that of the transaction status management device 11. The employee terminal may also notify the employee when a customer calls for assistance from the registration and settlement device 20, or when customer fraud is detected. Such notification allows the employee carrying the employee terminal to go to the registration and settlement device 20 in full self-service mode or in accounting-only mode to provide support to the customer.

[0023] (Example configuration of the registration and settlement device 20) Next, an example of the configuration of the registration and settlement device 20 will be described using Figures 2 and 3. Figure 2 is a perspective view showing an example of the appearance of the registration and settlement device 20. Figure 3 is a block diagram showing an example of the hardware configuration of the registration and settlement device 20. In Figures 2 and 3, the same parts are denoted by the same reference numerals.

[0024] As shown in Figure 2, an upstream counter 231 and a work support system 240 are positioned on either side of the registration and settlement device 20. The upstream counter 231 is used to place items awaiting registration and shopping baskets containing those items. The work support system 240 includes a downstream counter 241. The downstream counter 241 is used to place registered items and shopping bags containing those items.

[0025] The work support system 240 includes a downstream counter 241, a weighing scale 242, a work support rack 243, and a voucher storage unit 244. The weighing scale 242 is placed on the downstream counter 241. The work support rack 243 is placed on top of the weighing scale 242 and is a rack that assists with bagging and other tasks for registered products. The voucher storage unit 244 is located below the downstream counter 241 and collects used vouchers.

[0026] Furthermore, a spare parts storage compartment 250 is located at the bottom of the device housing 20a of the registration and settlement device 20. The spare parts storage compartment 250 stores spare parts such as receipt paper.

[0027] The following describes an example configuration of the registration and settlement device 20 shown in Figure 4, with reference to Figure 3. The registration and settlement device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer-side display unit 205, a customer-side scanner unit 206, a card payment unit 208, a change dispenser 209, an audio output unit 211, a communication unit 212, a printing unit 213, a camera 214, a monitoring monitor 215, a signpost 216, and a weighing device 242. These components can communicate with each other via a bus.

[0028] The CPU 201 is a central processing unit that controls the operation of the registration and settlement device 20 by reading and executing various programs stored in the ROM 202. These various programs include the sales data processing program according to this embodiment. ROM202 is read-only memory that stores various types of information used by the CPU201, including programs.

[0029] RAM203 is a read-and-write memory that stores various types of information. For example, RAM203 stores information obtained from external sources (such as product master data obtained from the store controller 10) and information generated during various processes. Specifically, the information generated during various processes includes registration information generated during the registration process for registering products, and settlement information generated during the settlement process for settling registered products.

[0030] The hard disk 204 stores various types of information. For example, the hard disk 204 stores the imaging results (e.g., video) captured by the camera 214. The hard disk 204 may store various programs executed by the CPU 201 instead of the ROM 202. Alternatively, the hard disk 204 may store information acquired from external sources or information generated during processing instead of the RAM 203.

[0031] The customer-side display unit 205 is a touch display for customers. The customer-side display unit 205 displays various information related to registration and payment to the customer and accepts various inputs from the customer related to registration and payment. For example, the customer-side display unit 205 displays preset keys corresponding to products and accepts the press of a preset key. As a result, the registration and payment device 20 registers the product. In addition, during payment, the customer-side display unit 205 displays multiple payment type selection buttons corresponding to multiple payment types and accepts the selection of one of the multiple payment type selection buttons (one of the payment types). As a result, the registration and payment device 20 performs payment using one of the payment types. Note that the customer-side display unit 205 is designed to fit within the width of the device housing 20a.

[0032] The customer-side scanner unit 206 is a scanner unit for the customer. Specifically, the customer-side scanner unit 206 is equipped with an imaging unit. The imaging unit is an image sensor having an image element such as a CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor). The imaging unit reads (images) the product. When the operator (customer) holds the product over the customer-side scanner unit 206, the imaging unit images the product. The imaging unit optically images the code symbol (such as a barcode or 2D code attached to the product) held over the imaging window, or the whole or a part of the product (object).

[0033] Code symbols include barcodes attached to products and employee codes attached to employee name tags. Barcodes attached to products are codes that identify the product, such as JAN codes, PLU (Price Look Up) codes, and in-store codes. The customer-side scanner unit 206 reads the barcode attached to the product, and the registration and payment device 20 registers the product. The reading method by the customer-side scanner unit 206 is not limited to CCD or CMOS; laser or pen-based methods are also possible.

[0034] The card payment unit 208 is a payment terminal that reads information stored on various media such as various cards and mobile terminals, and performs various payments based on the read information. The reading method of the card payment unit 208 includes contact and contactless methods. Various payments include credit card payments, electronic money payments, point card payments, and code payments. Electronic money is charged to charging media such as transportation IC cards and mobile terminals. Code payments are made by reading a code (including customer identification information and remaining balance) displayed on a mobile terminal, for example.

[0035] The change dispenser 209 is a cash payment mechanism and has an input slot for banknotes and coins, and an output slot for banknotes and coins. The change dispenser 209 calculates the amount to be inserted into the input slot, calculates the change amount which is the difference between the inserted amount and the purchase amount, and dispenses the change from the output slot. The change dispenser 209 is facing the customer and accepts various operations and cash insertions from the customer. The change dispenser 209 also has a sensor that detects banknotes and coins inserted into the input slot. This sensor detects that banknotes and coins have been inserted into the input slot, and also detects the number of items of each denomination.

[0036] The weighing device 242 is positioned on the downstream counter 241 and detects the weight of registered products. A weighing pan 245 is placed on top of the weighing device 242. The weighing pan 245 is equipped with a stopper 246. The stopper 246 prevents products or shopping baskets placed on the weighing pan 245 from falling off. In addition, a weighing guard 247 is provided on the customer side of the downstream counter 241 to prevent the operator (customer) from touching it and inadvertently measuring the load.

[0037] The weighing device 242 weighs the weight excluding the weight of the weighing pan 245 and the weight of the work support rack 243. Furthermore, if shopping bags are hung on the work support rack 243 or a shopping basket is placed on the weighing pan 245, the weighing device 242 weighs the weight excluding these items. In the diagram, the size of the downstream counter 241 and the weighing pan 245 is such that they can accommodate a shopping bag or the like that corresponds to one shopping basket. However, their size may be such that they can accommodate shopping bags or the like that that correspond to two or more shopping baskets. Also, multiple downstream counters 241 may be arranged side-by-side, and multiple weighing devices 242 may be placed in that arrangement.

[0038] When the registration and settlement device 20 registers a product, it queries the store controller 10 for the weight (theoretical weight value) of the product. The registration and settlement device 20 performs a weighing determination to determine whether the increased weight measured by the weighing scale 242 is within a predetermined range of the theoretical weight value. If the weighing determination result indicates that it is within the predetermined range, it determines that the registration has been performed successfully. On the other hand, if the weighing determination result indicates that it is not within the predetermined range, the registration and settlement device 20 determines that a weight anomaly has occurred. A weight anomaly includes the case where the weight of the weighing scale 242 does not increase even though the product has been registered. Furthermore, a weight anomaly also includes the case where the weight of the weighing scale 242 increases even though the product has not been registered.

[0039] The audio output unit 211 outputs sound. For example, the audio output unit 211 outputs voice guidance or warning sounds. The voice guidance and warning sounds are related to, for example, product registration or payment.

[0040] The communication unit 212 is an interface for sending and receiving information with other devices (store controller 10, transaction status management device 11, and other registration and settlement devices 20).

[0041] The printing unit 213 prints and outputs various media (receipts, etc.). The printing unit 213 can change the direction of the media output slot.

[0042] Camera 214 is mounted on the top of the customer-side display unit 205. Camera 214 captures video or still images. Camera 214 is an image sensor with an image sensor such as a CCD or CMOS. In addition, camera 214 is equipped with a fisheye lens or wide-angle lens, making it possible to capture customers over a wide area.

[0043] Camera 214 is mounted above the customer-side display unit 205. Camera 214 is a camera that continuously captures video or still images. Camera 214 can be a CCD camera or a CMOS camera. Camera 214 captures images of the customer's actions when registering products and during checkout. Camera 214 also captures images of the inside (products) of the shopping basket (upstream shopping basket) placed on the upstream counter 231. Furthermore, camera 214 can capture images of banknotes and coins held by the customer during checkout, as well as the change machine 209 and hand movements.

[0044] The camera 214 is positioned to capture good images of customer operations and shopping baskets upstream. For example, the camera 214 may be positioned so as to protrude from the customer-side display unit 205 toward the customer (towards the front). Furthermore, from the viewpoint of capturing better images of the checkout process, the camera 214 may be positioned facing the change dispenser 209, enabling it to capture images centered on the change dispenser 209 (cash slot).

[0045] Camera 214 continuously takes images while the system is running. The images captured by camera 214 are stored as recordings on the hard disk 204. The recording period is, for example, from the time the customer declares the start of use of the registration and payment device 20 until the customer completes the payment and leaves the registration and payment device 20. The presence or absence of a customer in front of the registration and payment device 20 is determined, for example, by a human presence sensor (not shown) provided in the registration and payment device 20. Alternatively, camera 214 may record only the period during which a customer is in front of the registration and payment device 20.

[0046] Furthermore, the captured images may be continuously recorded while the registration and settlement device 20 is running. In other words, the captured images may be continuously recorded regardless of whether a transaction has taken place or whether a customer is in front of the registration and settlement device 20. If continuous recording is performed, the registration and settlement device 20 may be equipped with a function to save the necessary parts and delete the unnecessary parts. For example, the period to be saved is from 5 seconds before the start of product registration is accepted until 5 seconds have elapsed after the receipt is taken out. On the other hand, the unnecessary parts are those that indicate a period not to be saved and are deleted.

[0047] The images captured by camera 214 can be used as surveillance images to monitor customers making payments. These images can be used, for example, to verify the amount actually deposited or as evidence. For example, suppose a customer tells a monitoring employee that they inserted a 10,000 yen bill but received less change. In this case, the employee can verify the denominations of money actually inserted by examining the captured images. Specifically, if the captured images confirm the insertion of a 10,000 yen bill, the monitoring employee can determine that the change machine 209 is malfunctioning. On the other hand, if the captured images do not confirm the insertion of a 10,000 yen bill (for example, if a 5,000 yen bill is confirmed), the monitoring employee can determine that the customer is making a false statement. These captured images can also be presented to the customer as evidence and can be displayed, for example, on the monitoring monitor 215 or the transaction status management device 11.

[0048] The monitoring monitor 215 displays the images captured by the camera 214. The monitoring monitor 215 is mounted above the customer-side display unit 205. The monitoring monitor 215 is positioned higher than the camera 214. Specifically, the monitoring monitor 215 is positioned at approximately the same height as the sign pole 216. This allows the monitoring staff to check both the monitoring monitor 215 and the sign pole 216 simultaneously. In addition, the monitoring monitor 215 and the camera 214 are positioned to fit within the width of the device housing 20a.

[0049] The images displayed by the monitoring monitor 215 are real-time images (video). By constantly displaying real-time video on the monitoring monitor 215, customers using the registration and settlement device 20 can be made aware that they are being monitored, thereby increasing the deterrent effect against fraud. The monitoring monitor 215 can also display images (recorded videos) stored on the hard disk 204.

[0050] Furthermore, the monitoring monitor 215 can change the orientation of its display screen to any direction in the up, down, left, or right directions. For example, the monitoring monitor 215 is oriented towards the transaction status management device 11 (monitoring employee). Because the monitoring monitor 215 is positioned above and oriented towards the transaction status management device 11, even an employee far from the registration and settlement device 20 (a monitoring employee standing in front of the transaction status management device 11) can monitor the customer's series of operations. In addition, if an error occurs, the monitoring monitor 215 can display a recording of the series of operations performed by the customer, or a recording of the moment the error occurred. The monitoring monitor 215 may have a larger screen than the customer-side display unit 205. This improves visibility for monitoring employees at a distance and further enhances the deterrent effect of surveillance.

[0051] The sign pole 216 is mounted on the device housing 20a. The sign pole 216 is positioned above the customer-side display unit 205 so as not to interfere with the monitoring screen 215. The sign pole 216 is equipped with a light-emitting part. The light-emitting part of the sign pole 216 is, for example, an LED (light-emitting diode). The light-emitting part can be lit in a predetermined color or in a predetermined lighting pattern. The predetermined lighting patterns include a lighting pattern indicating standby (e.g., solid green), a lighting pattern indicating use (e.g., flashing green), a lighting pattern to call a staff member, such as one near the end of change or receipt paper (e.g., flashing yellow), and a lighting pattern indicating insufficient change or an abnormality (e.g., flashing red). The lighting pattern indicating use may be a more detailed lighting pattern; for example, the lighting pattern indicating payment in progress and the lighting pattern indicating product registration may be different. Since the sign pole 216 is positioned above the customer-side display unit 205, staff members who are not near the registration and payment device 20 can also recognize the lighting patterns.

[0052] A numbered plate 216a is provided at the bottom of the sign pole 216. The numbered plate 216a indicates the number of the registration payment device 20 that is assigned to each registration payment device 20. The display medium on which this number is displayed may be an electronic medium or a non-electronic medium such as a plate.

[0053] The sign pole 216 and the numbered tag 216a are integrated and their orientation can be changed as needed. Even if the orientation of the sign pole 216 and the monitoring monitor 215 are changed, they are configured not to interfere with each other. The registration and payment device 20 can also be configured to include a display unit for the staff (staff-side display unit) in addition to the customer-side display unit 205. Even in such a configuration, the sign pole 216 and the monitoring monitor 215 will not interfere with each other, nor will they interfere with the staff-side display unit.

[0054] (Regarding inappropriate product listings) In fully self-checkout systems, inappropriate product registration can occur. Inappropriate product registration includes fraudulent product registration. Specifically, fraudulent product registration involves registering a product at a low price even though the product is expensive. More specifically, fraudulent product registration includes registering multiple products together to show only one product (so-called duplicate registration), or replacing the product code (barcode) attached to a product with the product code of a cheaper product before registering it.

[0055] Furthermore, inappropriate product registration includes products that are not registered. Products that are not registered include those that are intentionally not registered by the customer and those that are not registered unintentionally by the customer. Unintentional failure to register by the customer means, for example, that an unregistered product is placed in a shopping cart in a location that is out of the customer's sight, and the customer does not notice the product.

[0056] As described above, inappropriate product registration sometimes occurred in fully self-checkout systems. This embodiment aims to suppress such inappropriate product registration and support appropriate transactions. The functional configuration of the registration and settlement device 20 will be described below with reference to Figure 4.

[0057] (Functional configuration of the registration and settlement device 20) Figure 4 is a block diagram showing an example of the functional configuration of the registration and settlement device 20. As shown in Figure 4, the registration and settlement device 20 comprises the following functional units: a registration unit 401, an acquisition unit 402, a guidance unit 403, a declaration acceptance unit 404, and a display control unit 405. Each functional unit is implemented by the CPU 201. That is, the CPU 201 implements each functional unit by executing the sales data processing program according to this embodiment. As mentioned above, the registration and settlement device 20 is assumed to operate in full self-service mode.

[0058] In the following sections, we will explain each of the functional components shown in Figure 4, with reference to Figure 5. Figure 5 shows an example of screen transitions of the customer-side display unit 205 controlled by the display control unit 405.

[0059] (Registration Section 401) The registration unit 401 registers products based on customer operations. These operations include, for example, reading the product code attached to the product (scanning operation) or pressing the preset key 512 (operator) shown in Figure 5(A). In the following, registration by scanning may be referred to as "scan registration," and registration by pressing the preset key 512 may be referred to as "preset registration." The preset key 512 is, for example, a key corresponding to the product "○○ Melon" or a key corresponding to the product "○○ Pear." However, the registration operation may also include input operations such as manually entering the product code, or search operations to find the target product from the classification to which the product belongs. However, these input operations and search operations may be performed from an operation screen (maintenance screen) that can be displayed by a store employee. In the following, products that are registered by scanning may be referred to as "scan registered products," and products that are registered using presets may be referred to as "preset registered products."

[0060] (Acquisition unit 402) The acquisition unit 402 acquires each captured image 543 (Figure 5(D)) that captures the situation related to the registration operation of each product by the registration unit 401. The captured image 543 is captured by the customer-side scanner unit 206. The situation related to the product registration operation includes the timing of product registration and the timing before and after product registration. For example, when scan registration is performed, the situation related to the product registration operation is the situation related to the product reading operation. The situation related to the product reading operation includes the condition of the product to be read and the condition of the customer's hands at the time of scanning.

[0061] In this case, due to fraudulent registration or operational errors during registration, products may not be scanned correctly. Considering this, in this embodiment, the imaging timing is set to a few seconds after the product is detected in the imaging area 513 (Figure 5(A)). In other words, the customer-side scanner unit 206 images the condition of the product and the customer's hands, regardless of whether the product code is read or not. Therefore, it is possible to capture images in the event of fraud, such as when a customer pretends to register a product but moves it to a shopping cart downstream. Note that the imaging timing may also be set to the timing when the product is detected in the imaging area 513.

[0062] Furthermore, the customer-side scanner unit 206 may also capture an image of the situation related to the product reading operation at the time of scanning (registration timing) when the product is scanned (when the product is scanned correctly). In this way, even if overlapping registrations are performed or registrations are performed after replacing the product code, an image of the situation at the time of registration can be obtained.

[0063] (Guidance section 403: Regarding captured images when registering presets) In the case of preset registration, there is no need to move the product to the customer-side scanner unit 206 so that it is visible in the imaging area when registering the product. For this reason, with preset registration, an image of the product cannot be obtained unless it is intentionally photographed. Therefore, in this embodiment, the guidance unit 403 provides guidance prompting the user to photograph the preset registered product in order to obtain an image of the preset registered product. This guidance is, for example, a guidance prompting the user to bring the preset registered product closer to the customer-side scanner unit 206, as shown in the guidance screen 530 of Figure 5(C). The guidance unit 403 provides this guidance and also activates the customer-side scanner unit 206. The customer-side scanner unit 206 photographs the preset registered product that is visible in the imaging area 531 (Figure 5(C)). The acquisition unit 402 acquires the image 543 of the preset registered product that was photographed in accordance with the guidance unit 403. In this way, even when it is not a scan registration, in other words, the acquisition unit 402 can acquire an image of a product other than a scan registered product (for example, a preset registered product).

[0064] The registration and settlement device 20 may also determine whether or not an image of a preset registered product has been acquired. Furthermore, if the registration and settlement device 20 determines that the image has not been acquired, it may also notify that the product registration has not been completed correctly. In this case, the registration and settlement device 20 may also be configured to prevent the registration of the next product until it determines that an image of the preset registered product has been acquired (until the product registration is completed correctly). This helps to reduce the chances of missing images during preset registration.

[0065] (Declaration Reception Department 404) The declaration reception unit 404 receives a declaration (hereinafter referred to as the "declaration to commence settlement") indicating that settlement will be initiated for each product registered by the registration unit 401. The declaration to commence settlement indicates the completion of product registration. In other words, the declaration reception unit 404 receives the declaration to commence settlement by receiving the press of the registration completion button 522 (Figure 5(B)) which indicates the completion of product registration.

[0066] (Display control unit 405) When the declaration reception unit 404 receives the declaration to start payment, the display control unit 405 displays the image list 542 (Figure 5(D)) on the customer-side display unit 205. The image list 542 is a screen displaying each captured image 543 acquired by the acquisition unit 402. The number of captured images 543 corresponds to the number of registered products. For example, if there are 10 registered products, the number of captured images 543 is also 10. If there are many captured images 543 and the image list 542 does not fit on one page, the display control unit 405 can display the image list 542 across multiple pages. Switching to the second page or later may be done automatically (for example, automatically after a few seconds have elapsed) or manually (by pressing a predetermined page switching button).

[0067] (Regarding image 544 of the basket) Camera 214 captures a basket image 544 (Figure 5(D): an example of a storage area image) showing the contents of the upstream shopping basket (an example of a storage area). Unregistered items are stored in the upstream shopping basket (upstream counter 231). The customer registers each item in the upstream shopping basket one by one, and once the registration of an item is complete, the customer places that item in another shopping basket (downstream shopping basket). The acquisition unit 402 acquires the basket image 544 captured by camera 214. Camera 214 also captures images of the contents of the upstream shopping basket and various customer operations from the start to the end of the transaction.

[0068] The display control unit 405 displays the image list 542 and the basket image 544 on the customer-side display unit 205. The image list 542 and the basket image 544 are displayed side by side, but either one of them may be displayed by switching the display.

[0069] The timing at which the shopping cart image 544 is captured is, for example, when the payment start declaration is received (more specifically, when the registration completion button 522 in Figure 5(B) is pressed). In other words, the shopping cart image 544 is an image (still image) captured at the time the payment start declaration is received. Note that the shopping cart image 544 may also be a real-time image (video).

[0070] (An example of a screen transition controlled by the display control unit 405) Next, an example of screen transitions on the customer-side display unit 205 will be described with reference to Figures 5 and 6. Figures 5 and 6 show an example of screen transitions of the customer-side display unit 205 controlled by the display control unit 405. Figure 5(A) shows the registration start screen 510. The registration start screen 510 is displayed when the registration start button is pressed on a standby screen (not shown). The registration start screen 510 includes a registration guide 511, a preset key 512, and an imaging area 513.

[0071] Registration instruction 511 indicates instructions to have the customer-side scanner unit 206 read the product code. The preset key 512 is a button that accepts product registration and is displayed corresponding to the product. In the illustration, the preset key 512 includes an image of the product and text information indicating the product. In the illustration, the preset key 512 includes, for example, a key corresponding to the product "○○ Melon" and a key corresponding to the product "○○ Pear".

[0072] The imaging area 513 is the area that shows the real-time image (video) captured by the customer-side scanner unit 206. The imaging area 513 includes a reading area 514 from which product codes (barcodes) can be read. The reading area 514 is the area surrounded by a block-shaped mark 514a. The mark 514a prompts the customer to place the product code within the reading area 514. When the registration and settlement device 20 detects a product code within the reading area 514, it registers the product indicated by that product code.

[0073] On the registration start screen 510, when the customer scans the product code or presses the preset key 512 and registers the product, the registration and settlement device 20 transitions to the product registration screen 520 shown in Figure 5(B).

[0074] Figure 5(B) shows the product registration screen 520. The product registration screen 520 includes a list of registered products 521, a registration completion button 522, and an imaging area 513. The Registered Products List 521 shows a list of registered products. In the diagram, the Registered Products List 521 shows that four products are registered. The four products are "○○ Canned Coffee," "○○ Melon," "○○ Pear," and "○○ Potato Chips." The registration completion button 522 is a button that accepts the declaration to start settlement. When the registration completion button 522 is pressed, the user transitions to the registration confirmation screen 540 shown in Figure 5(D).

[0075] Here, we will explain the screen that appears when a product is registered by pressing preset key 512. Figure 5(C) shows the guidance screen 530. The guidance screen 530 is displayed when a product is registered by pressing a preset key 512. The guidance screen 530 prompts the user to take an image of the registered product. Specifically, the guidance screen 530 displays instructions (hereinafter sometimes referred to as "image guidance") prompting the user to bring the product closer to the customer-side scanner unit 206. For example, when the preset key 512 corresponding to "○○ Melon" is pressed, the product corresponding to the pressed key (○○ Melon) is registered, and the user transitions to the guidance screen 530.

[0076] On the guidance screen 530, the imaging area 531 shows the image being captured by the customer-side scanner unit 206. The customer-side scanner unit 206 captures images of the products within the imaging area. This allows the user to obtain an image of the product registered by pressing the preset key 512. Once the customer-side scanner unit 206 has finished capturing images, the user returns to the product registration screen 520.

[0077] Figure 5(D) shows the registration confirmation screen 540. The registration confirmation screen 540 includes a total field 541, an image list 542, a shopping cart image 544, a re-registration button 545, and a checkout start button 546. The total column 541 shows the total number of registered items and the total price. Image list 542 shows each captured image 543 (543a~543d) that captures the situation when each product is registered.

[0078] Image 543a shows the situation when "○○ potato chips" was registered. Image 543b is an image of "○○ Melon" captured in accordance with the imaging guidance. Specifically, image 543b shows the image captured on the guidance screen 530. Image 543c shows an image of "○○ pear" captured in response to the imaging guidance.

[0079] Image 543d shows the situation when "○○ Canned Coffee" was registered. In image 543d, the customer's hand is covering the product code, and it may appear as if it is not registered, but as shown in the registered product list 521 (Figure 5(B)), "○○ Canned Coffee" is registered. In other words, image 543d is an image taken at some point before or after the product code of "○○ Canned Coffee" was scanned (at the moment when the hand was covering the product code).

[0080] In this embodiment, since a weighing device 242 is provided, an abnormality can be detected if the weight of an unregistered product increases. However, if the product is small (light) (if the weight increase is within a predetermined range), it may not be detected as an abnormality. In this embodiment, even if a customer's hand is covering the product code and the product is not registered, the captured image 543 can make the customer aware that the product is not registered. This can encourage the customer to register the product.

[0081] The basket image 544 shows the inside of the upstream shopping basket (a shopping basket containing unregistered items). In the illustration, basket image 544 indicates that items remain in the shopping basket.

[0082] The re-registration button 545 is a button that allows the user to return to a state where product registration is accepted again. When the re-registration button 545 is pressed, the user returns to the product registration screen 520 in Figure 5(B). This makes it possible to register any products remaining in the shopping cart.

[0083] The "Start Checkout" button 546 is a button that accepts the start of checkout. The customer checks the image list 542 and the shopping cart image 544, and then presses the "Start Checkout" button 546. When the "Start Checkout" button 546 is pressed, the user is redirected to the payment type selection screen shown in Figure 6(A).

[0084] Figure 6(A) shows the payment type selection screen 610. The payment type selection screen 610 is a screen that accepts the selection of a payment type. The payment type selection screen 610 includes multiple payment type selection buttons 611 corresponding to the payment types. The payment type selection buttons 611 include buttons corresponding to cash, credit card, electronic money, code payment, and others. When any of the payment type selection buttons 611 are pressed, the payment processing is performed using the payment type corresponding to the pressed button. For example, if the button indicating cash is pressed among the payment type selection buttons 611, the screen transitions to the payment processing screen 620 shown in Figure 6(B).

[0085] Figure 6(B) shows the payment processing screen 620. The payment processing screen 620 includes an income / expense column 621. The income / expense column 621 displays the total amount, the amount received, the amount of change, etc. When the customer inserts an amount equal to or greater than the total amount into the change machine 209, a receipt issuance button (not shown) is displayed. When the receipt issuance button is pressed, if there is change, the change is dispensed, a receipt is issued, and the transaction is completed.

[0086] (Registration and settlement process performed by the registration and settlement device 20) Figure 7 is a flowchart showing an example of the registration and settlement process performed by the registration and settlement device 20 according to this embodiment. As shown in Figure 7, the registration and settlement device 20 waits until the registration of a product begins when the registration start button is pressed on the standby screen (step S701: NO). When the registration of a product begins (step S701: YES), the registration and settlement device 20 determines whether or not a product (object) has been detected within the imaging area of ​​the customer-side scanner unit 206 in order to determine whether or not a product scanning operation has been detected (step S702).

[0087] If a product (object) is detected within the imaging area (step S702: YES), that is, if a scan operation is detected, the registration and settlement device 20 acquires an image of the detected object, which is the product, and the customer's hands (step S703). The registration and settlement device 20 then determines whether or not the customer-side scanner unit 206 has scanned the product (product code) (step S704a). If the product has been scanned (step S704a: YES), the registration and settlement device 20 acquires the product information indicated by the barcode in the image obtained by the scan (step S704b), then proceeds to step S708a1 to register the product. On the other hand, if the product has not been scanned (step S704a: NO), the registration and settlement device 20 proceeds to step S708d.

[0088] In step S702, if no product (object) is detected within the imaging area (step S702: NO), the registration and payment device 20 determines whether or not the preset key 512 (Figure 5(A)) has been pressed (step S705a). If the preset key 512 has not been pressed (step S705a: NO), the registration and payment device 20 returns to step S702. On the other hand, if the preset key 512 has been pressed (step S705a: YES), the registration and payment device 20 acquires product information corresponding to the preset key 512 (step S705b). Then, the registration and payment device 20 displays the guidance screen 530 (Figure 5(C)) and provides guidance (imaging guidance) prompting the customer to bring the registered product closer to the customer-side scanner unit 206 (step S706).

[0089] Then, the registration and settlement device 20 takes an image of the product and acquires the image obtained from the image (step S707). Then, the registration and settlement device 20 registers the product (step S708a1). Note that product registration may be performed immediately after the preset key 512 is pressed in step S705a.

[0090] When the registration and settlement device 20 registers a product, it stores the image of the scanned product acquired in step S703 and the image of the preset product acquired in step S707 (step S708a2). Note that the timing of image acquisition and product information acquisition differs between scan registration and preset registration. Specifically, in the case of scan registration, product information is acquired in step S704b after the image is acquired in step S703. On the other hand, in the case of preset registration, image is acquired in step S707 after product information is acquired in step S705b.

[0091] Next, the registration and payment device 20 determines whether the registered product is a store employee verification product (step S708b). Store employee verification products are, for example, products that require age verification, pharmaceuticals, or products that require the removal of security tags. If the registered product is not a store employee verification product (step S708b: NO), the registration and payment device 20 proceeds to step S708d.

[0092] If the registered product is a store employee verification product (step S708b: YES), the registration and settlement device 20 performs a store employee call process (step S708c). In the store employee call process, if the device transitions to a predetermined maintenance screen and the store employee verifies the product, the registration and settlement device 20 proceeds to the process in step S708d. Note that the determination in step S708b as to whether or not a product is a store employee verification product is not limited to being made each time a store employee verification product is registered, but may be made after the product registration is complete. In other words, the store employee call process in step S708c may be made after the product registration is complete (after the registration completion button 522 in step S709 is pressed).

[0093] Next, the registration and settlement device 20 determines whether there is an abnormality (weight abnormality) in the weight measured by the weighing device 242 (step S708d). An abnormality is, for example, an increase in weight even though the product has not been registered, or the increase in weight of a registered product is not within a predetermined range relative to the theoretical weight value. If there is no weight abnormality (step S708d: NO), the registration and settlement device 20 proceeds to step S709. Note that in cases of overlapping registration of light products or when there is no difference in the weight of the product before and after changing the product code (when the weight difference is small), the device may not detect a weight abnormality. However, in this embodiment, since the image list 542 is displayed before settlement begins, a deterrent effect can be obtained against overlapping registration and registration by changing the product code.

[0094] On the other hand, if there is a weight anomaly (step S708d: YES), for example, if there is a duplicate registration or registration due to the replacement of product codes, the registration and settlement device 20 performs a store employee call process (step S708e). In the store employee call process, after transitioning to a predetermined maintenance screen and confirming with a store employee, the registration and settlement device 20 proceeds to the process in step S709.

[0095] Next, the registration and payment device 20 determines whether or not the registration completion button 522 (Figure 5(B)) has been pressed (step S709). If the registration completion button 522 is not pressed (step S709: NO), the registration and payment device 20 returns to step S702. On the other hand, if the registration completion button 522 is pressed (step S709: YES), the registration and payment device 20 acquires a basket image 544 taken from the inside of the shopping basket on the upstream side (step S710).

[0096] Next, the registration and payment device 20 displays the image list 542 and the basket image 544 on the customer-side display unit 205 on the registration confirmation screen 540 (Figure 5(D)) (step S711). Then, the registration and payment device 20 determines whether or not it has accepted the transition to a state where product registration is accepted again, that is, whether or not the re-registration button 545 (Figure 5(D)) has been pressed (step S712).

[0097] If the re-registration button 545 is pressed (step S712: YES), the registration and settlement device 20 returns to step S702. If the re-registration button 545 is not pressed (step S712: NO), the registration and settlement device 20 determines whether or not it has accepted the start of settlement, that is, whether or not the start of settlement button 546 (Figure 5(D)) has been pressed (step S713).

[0098] If the settlement start button 546 is not pressed (step S713: NO), the registration settlement device 20 returns to step S712 and waits for either the re-registration button 545 or the settlement start button 546 to be pressed. If the settlement start button 546 is pressed (step S713: YES), the registration settlement device 20 displays the payment type selection screen 610 (Figure 6(A)) and performs a payment type selection process to accept the selection of a payment type (step S714). Then, the registration settlement device 20 executes the settlement process, including settlement and receipt issuance, according to the selected payment type (step S715), and ends the series of processes.

[0099] As described above, the registration and settlement device 20 according to this embodiment displays an image list 542 which is a collection of captured images 543 (Figure 5(D)) that capture the status of the customer's registration operation. This allows customers to be aware that their reading operations are being recorded (monitored). Therefore, it has a deterrent effect against fraudulent product registration. Furthermore, the image list 542 allows customers to understand the registration operations for each product. For example, if a customer intends to purchase four items but only three are registered, they can notice that there are missing items. This allows the customer to be prompted to register the missing items. Additionally, since a re-registration button 545 is displayed on the same screen, if the customer notices a missing item, they can easily transition to the re-registration operation from that screen, thus reducing the likelihood of missed registrations. Therefore, it can support appropriate transactions.

[0100] Furthermore, the registration and settlement device 20 according to this embodiment displays the image list 542 when it receives a settlement start declaration (pressing the registration completion button 522 (Figure 5(B))). This allows the customer to be presented with a list of images 542 as soon as registration is complete. Therefore, the customer can be made aware that the scanning operation is being monitored as soon as registration is complete, and they can also be made aware of any products that have not been registered.

[0101] Furthermore, the registration and settlement device 20 according to this embodiment displays an image list 542 and a shopping cart image 544. This allows us to more efficiently alert customers to any products they may have missed registering.

[0102] Furthermore, the registration and settlement device 20 according to this embodiment acquires an image showing the status related to the product code reading operation. This allows the situation during the scan operation to be displayed as an captured image 543, making the customer aware that their scan operation is being recorded (monitored). Therefore, it can improve the deterrent effect against fraud such as duplicate registration or substitution of product codes.

[0103] Furthermore, the registration and settlement device 20 according to this embodiment provides guidance prompting the user to take an image of the registered product when the preset key 512 is pressed, and displays the captured image 543 of the product taken in response to the guidance. This allows the system to recognize that a product has been registered based on the registration operation by pressing the preset key 512. In other words, if the image 543 of the product in question is not displayed in the image list 542, the customer can be made aware that there is a product that has not been registered.

[0104] (Modified examples of the embodiment) Next, modifications of the embodiments will be described. In the following modifications, explanations of the contents described in the embodiments described above will be omitted as appropriate. Furthermore, it is also possible to combine each of the following modifications and each of the components of the embodiments.

[0105] (Example of modification 1: Registering products using a mobile device) First, let's describe Modification 1. In the embodiment described above, we described an example in which products are registered (self-registered) at the registration and settlement device 20. In Modification 1, we will describe an example in which a customer uses a mobile terminal to register products (self-registered) as they walk around the store.

[0106] (Network configuration of sales data processing system St1) Figure 8 is an explanatory diagram showing the network configuration of the sales data processing system St1 according to Modification Example 1. As shown in Figure 8, the sales data processing system St1 includes a cloud server Sv, a store controller 10, a transaction status management device 11, a mobile terminal device 30, and a settlement device 40.

[0107] Each device and each terminal is connected to each other via a network so that they can communicate with one another. For example, the store controller 10, the transaction status management device 11, and the settlement device 40 are each connected to each other via a network 55 such as a LAN so that they can communicate with one another. Each device and each terminal is a computer device equipped with a CPU, ROM, RAM, communication unit, etc.

[0108] The cloud server Sv is a server device that manages various types of information, such as customer information, store information, store-specific product information (product master), and customer membership information. For example, based on product information read by the mobile terminal device 30, the cloud server Sv generates cart information representing a virtual shopping cart for each customer and registers the products.

[0109] The settlement device 40 is a computer device capable of settling payments for items registered by the mobile terminal device 30. The settlement device 40 may be a registered settlement device 20 operating in a dedicated accounting mode, or it may be a self-service settlement device that only has the functionality of a dedicated accounting mode. In Figure 8, multiple settlement devices 40 are shown as an example, but there may be only one.

[0110] The mobile terminal device 30 is a portable computer device such as a smartphone, tablet, or mobile phone. The mobile terminal device 30 includes a communication unit, an imaging unit (camera), a touch panel, etc., and is operated by the customer. In this embodiment, the mobile terminal device 30 is detachably attached to the shopping cart. However, the mobile terminal device 30 may be permanently installed on the shopping cart. Also, the mobile terminal device 30 may be owned by the customer or lent to the customer by the store. The mobile terminal device 30 is placed in a predetermined position on the shopping cart. The predetermined position is a position from which the entire shopping basket placed on the shopping cart can be imaged.

[0111] The mobile terminal device 30 has application software (hereinafter referred to as the "shopping app") installed for registering products related to the sales data processing system St1 and for settling payments for registered products. By launching the shopping app, the mobile terminal device 30 scans (reads) the barcode (product code) attached to the product and accepts product registration. When the mobile terminal device 30 reads the barcode attached to the product, it sends the read information to the cloud server Sv. As a result, the product corresponding to that barcode is registered in the cart information (virtual cart) of the cloud server Sv.

[0112] The payment device 40 acquires cart identification information from the mobile terminal device 30 at the time of payment. Based on this cart identification information, the payment device 40 receives cart information from the cloud server Sv and performs payment. The acquisition of cart identification information is performed by reading a two-dimensional code (hereinafter referred to as the "payment code") displayed on the mobile terminal device 30. The payment code is a coded representation of the cart identification information used to identify the cart information assigned to the mobile terminal device 30.

[0113] (Functional configuration of sales data processing system St1) Figure 9 is a block diagram showing an example of the functional configuration of the sales data processing system St1 according to Modification 1. As shown in Figure 9, the sales data processing system St1 comprises a cloud server Sv, a mobile terminal device 30, and a settlement device 40.

[0114] (Regarding the mobile terminal device 30) The mobile terminal device 30 comprises the following functional units: a registration unit 401, an acquisition unit 402, a guidance unit 403, a declaration acceptance unit 404, and a display control unit 405. Each functional unit is implemented by the CPU of the mobile terminal device 30. That is, the CPU implements each functional unit by executing the sales data processing program according to this embodiment.

[0115] The registration unit 401 is defined as the reading of a product code by the imaging unit of the mobile terminal device 30, or the pressing of a preset key displayed on the display of the mobile terminal device 30. In the modified example 1, the image is captured by the imaging unit. In other words, the imaging unit captures the situation related to the registration operation of each product by the registration unit 401. The mobile terminal device 30 transmits the captured image to the cloud server Sv in association with the registration information. The cloud server Sv stores cart information including the registration information and the captured image. The guidance unit 403 also provides imaging guidance, prompting the user to bring the product registered by pressing the preset key closer to the imaging unit.

[0116] The acquisition unit 402 acquires images capturing the status of each product registration operation performed by the registration unit 401. The declaration reception unit 404 receives a settlement commencement declaration for each product registered by the registration unit 401. The display control unit 405 displays a list of images on the display when the settlement commencement declaration is received by the declaration reception unit 404.

[0117] (Regarding the payment device 40) The settlement device 40 comprises an acquisition unit 402 and a display control unit 405. Each functional unit is realized by the CPU of the settlement device 40. That is, the CPU realizes each functional unit by executing the sales data processing program according to this embodiment.

[0118] When the acquisition unit 402 reads the payment code displayed on the mobile terminal device 30, it acquires cart information from the cloud server Sv. The cart information includes product registration information and captured images. At the time of payment, the display control unit 405 displays an image list in which the captured images are arranged.

[0119] (An example of the process from product registration to transaction completion in the sales data processing system St1) Figure 10 is a sequence diagram showing the processing flow from product registration to transaction completion in the sales data processing system St1. Figure 10 illustrates the process from when a customer visits a store, registers the products they wish to purchase using their mobile terminal device 30, and completes the transaction using the payment device 40.

[0120] Step S1001: First, the mobile terminal device 30 launches the shopping app. Step S1002: The mobile terminal device 30 acquires information that identifies a store (store identification information). The store identification information is represented, for example, by a two-dimensional code near the entrance of the store. The two-dimensional code may be displayed on a predetermined display device or printed on paper. The mobile terminal device 30 activates its camera when the shopping app is launched based on customer operation and scans the two-dimensional code. As a result, the mobile terminal device 30 acquires the store identification information. The two-dimensional code also contains instructions to request the cloud server Sv to start a transaction. Therefore, once the mobile terminal device 30 acquires the store identification information, it requests the cloud server Sv to start a transaction. Specifically, the mobile terminal transmits the acquired store identification information and customer identification information (terminal identification information) to the cloud server Sv.

[0121] Furthermore, store identification information may be obtained based on location information. For example, when the mobile terminal device 30 launches the shopping app, it acquires GPS information indicating its current location and sends a query to the cloud server Sv based on the acquired GPS information. The cloud server Sv extracts the nearest store to the mobile terminal device 30 based on the GPS information and sends the extraction result to the mobile terminal device 30. When the mobile terminal device 30 receives the extraction result from the cloud server Sv, The nearest store is displayed, and the customer is allowed to select a store to use. The mobile terminal device 30 then transmits store identification information indicating the selected store and customer identification information (terminal identification information) to the cloud server Sv.

[0122] Step S1003: When the cloud server Sv receives a transaction initiation request (customer identification information and store identification information) from the mobile terminal device 30, it generates cart information for that transaction. The cart information includes, for example, the following information: Cart identification information. • Customer identification information. • Transaction start date and time. • Registered product information. • Captured image. • Basket image. • If the mobile terminal device 30 and the shopping cart are connected via Bluetooth® or similar, the identification information (machine number) of the shopping cart.

[0123] Cart identification information is information that combines, for example, a serial number assigned by numbering, store identification information, and the current date. Customer identification information is information that identifies the customer. Registered product information shows the product information registered in this transaction. Captured images are images taken when each product is registered. Basket images are images that show the products in the shopping cart. At the start of a transaction, since no products have been registered, the registered product information, captured images, and basket images all show NULL. The cloud server Sv transmits the cart identification information to the mobile terminal device 30. As a result, the cart identification information is used as information to identify the transaction in that transaction. When the cloud server Sv generates cart information, it transmits setting information specific to the target store to the mobile terminal device 30. When the mobile terminal device 30 receives the setting information from the cloud server Sv, it can display a registration screen corresponding to the setting information of the visited store.

[0124] Step S1004: The mobile terminal device 30 detects a product registration operation. Detection of a registration operation occurs when a product (object) is detected within the imaging area of ​​the imaging unit, or when a preset key displayed on the display is pressed.

[0125] Step S1005: The mobile terminal device 30 acquires an image. The image is either an image showing the situation related to the product code reading operation, or an image based on the image guidance provided by the guidance unit 403.

[0126] Step S1006: The mobile terminal device 30 registers the product corresponding to the scanned product code or the product corresponding to the preset key. Once the product is registered, the mobile terminal device 30 sends product information indicating the product and cart identification information to the cloud server Sv.

[0127] Step S1007: When the cloud server Sv receives product information and cart identification information from the mobile terminal device 30, it identifies the cart information containing the received cart identification information and updates the registered product information contained in the identified cart information.

[0128] Step S1008: The mobile terminal device 30 repeats the process in steps S1004 to S1007 until it receives a declaration to start settlement. Receiving a declaration to start settlement means that the registration complete button displayed on the display of the mobile terminal device 30 is pressed.

[0129] Step S1009: When the mobile terminal device 30 receives a declaration to start payment, it acquires a picture of the shopping cart.

[0130] Step S1010: The mobile terminal device 30 displays a registration confirmation screen (similar to the registration confirmation screen 540 in Figure 5(D)) on its display, which includes a list of images acquired in step S1005 and the basket image acquired in step S1009.

[0131] On the registration confirmation screen, the shopping cart image shows that all registered items have been placed in the shopping cart. This allows customers to easily determine if any items have been missed by comparing the number of items shown in the shopping cart image with the number of items shown in the image list, especially if the number of items to be registered is small. If any items are missed, the customer can register them. Specifically, when the re-registration button (a button similar to the re-registration button 545 in Figure 5(D)) displayed on the registration confirmation screen is pressed, the mobile terminal device 30 returns to the process in step S1004 and accepts the registration of the items.

[0132] Step S1011: The mobile terminal device 30 receives confirmation that the payment start button (a button similar to the payment start button 546 in Figure 5(D)) displayed on the registration confirmation screen has been pressed.

[0133] Step S1012: When the payment start button is pressed, the mobile terminal device 30 displays a payment code.

[0134] Step S1013: The payment device 40 scans the payment code displayed on the mobile terminal device 30. The payment code includes cart identification information and information indicating that a request for cart information should be sent to the cloud server Sv. Step S1014: When the payment device 40 scans the payment code, it requests the cloud server Sv to send cart information. In the request to send cart information, the payment device 40 sends the cart identification information obtained from the payment code to the cloud server Sv.

[0135] Step S1015: When the cloud server Sv receives a request to send cart information from the payment device 40, it identifies the cart information based on the cart identification information. Step S1016: When the cloud server Sv identifies the cart information, it transmits the cart information to the payment device 40.

[0136] Step S1017a: When the payment device 40 receives cart information from the cloud server Sv, it displays a registration confirmation screen (similar to the registration confirmation screen 540 in Figure 5(D)) containing various information (registration information, captured image, basket image) on the customer-side display unit of the payment device 40.

[0137] Step S1017b: The payment device 40 performs a staff call process depending on whether or not there are any reserved items for the customer to purchase. Reserved items are items that require staff verification, such as age verification items, medicines, items with security tags, and items eligible for return. If there are no reserved items, the payment device 40 proceeds to the process from step S1018 onwards. On the other hand, if there are reserved items, the staff call process transitions to a predetermined maintenance screen and staff verification is performed, at which point the registration payment device 20 proceeds to the process from step S1018 onwards. In other words, if there are reserved items, the payment device 40 displays a registration confirmation screen (similar to the registration confirmation screen 540 in Figure 5(D)) on the customer-side display unit until a staff member arrives. This allows the customer to view the image list and the shopping basket image on the registration confirmation screen until a staff member arrives.

[0138] Step S1018: The payment device 40 receives confirmation that the payment start button (a button similar to the payment start button 546 in Figure 5(D)) displayed on the registration confirmation screen has been pressed. The payment device 40 may also enable the re-registration of the product before the payment start button is pressed. The re-registration of the product may be performed based on the operation of a store employee after being called by a store employee.

[0139] Step S1019: The settlement device 40 displays a payment type selection screen (similar to the payment type selection screen 610 in Figure 6(A)) and performs a payment type selection process to accept the selection of a payment type.

[0140] Step S1020: The settlement device 40 performs settlement processing, including settlement and receipt issuance, according to the selected payment type. Once the settlement processing is complete, the settlement device 40 sends a settlement completion notification to the cloud server Sv.

[0141] Step S1021: When the cloud server Sv receives a payment completion notification from the settlement device 40, it executes the transaction completion process. In the transaction completion process, for example, the transaction completion date and time (settlement date and time) is stored in the cart information.

[0142] Step S1022: The cloud server Sv sends a transaction completion notification to the mobile terminal device 30. Step S1023: When the mobile terminal device 30 receives a transaction completion notification from the cloud server Sv, it executes the transaction completion process. In the transaction completion process, the mobile terminal device 30 deletes the products registered on its device and closes the shopping application.

[0143] As described above, the sales data processing system St1 (mobile terminal device 30 and payment device 40) according to Modification 1 displays an image list in which captured images of the situation when each product is registered by the customer's operation are arranged side by side. This allows customers to be aware that their reading operations are being monitored. Therefore, it has a deterrent effect on fraudulent product registration. Furthermore, the image list allows customers to understand the registration process for each product, enabling them to notice any missing items. This allows customers to be prompted to register any missing items, thus reducing registration errors. Therefore, according to Modification 1, appropriate transactions can be supported.

[0144] (Example of a shopping cart equipped with a weighing unit) In Modification 1, the shopping cart may be equipped with a weighing unit. The shopping cart equipped with a weighing unit is connected to the mobile terminal device 30 via Bluetooth or the like. The shopping cart transmits the weighing result from the weighing unit to the mobile terminal device 30. This allows the mobile terminal device 30 to provide notifications according to the weighing result (increase or decrease in weight). For example, if the weighing result shows an increase in weight even though the product has not been registered, the mobile terminal device 30 can determine that an abnormality has occurred, such as that the product has been illegally placed in the shopping cart. When the shopping cart and the mobile terminal device 30 are connected via communication, the cart information includes the shopping cart's identification information (machine number).

[0145] The weighing unit weighs the items placed in the shopping cart. Items include products in the shopping basket and the customer's personal belongings in the shopping basket. The portable terminal device 30 determines whether there is an abnormality (weight abnormality) in the weight measured by the weighing device 242. The timing for determining whether there is a weight abnormality is, for example, after detecting the product registration operation (after step S1004) and before receiving the declaration to start payment (before step S1008). A weight abnormality is, for example, when the weight increases even though no product has been registered, or when the weight increase of a registered product is not within a predetermined range relative to the theoretical weight value.

[0146] If there is an abnormality in weight, a staff call process is initiated. The staff call process may be performed during product registration or at the start of checkout. If the staff call process is performed during product registration, it is performed on the mobile terminal device 30. After staff verification is performed during the staff call process, the mobile terminal device 30 returns to a state where it is possible to register the product. If the staff call process is performed before the start of checkout, it is performed on the checkout device 40. After staff verification is performed during the staff call process, the checkout device 40 makes the checkout process possible.

[0147] (Example of displaying the registration confirmation screen only while a store employee is being called) Furthermore, in the modified example 1, the registration confirmation screen on the payment device 40 (a screen similar to the registration confirmation screen 540 in Figure 5(D)) may be displayed only when a store clerk call process is performed. In other words, if a store clerk call process is not performed, the payment device 40 may not display the registration confirmation screen. Specifically, if the cart information received by the cloud server Sv (step S1016) does not include any reserved items, the payment device 40 may perform the payment type selection process in step S1019 without performing the processes in steps S1017a, S1017b, and S1018.

[0148] (Modification 2: Example with exit device) Next, we will describe Modification 2. Modification 2 describes a sales data processing system St2 equipped with a store exit device.

[0149] (Network configuration of sales data processing system St2) Figure 11 is an explanatory diagram showing the network configuration of the sales data processing system St2 according to Modification 2. As shown in Figure 11, the sales data processing system St2 includes a store controller 10, a transaction status management device 11, a registration and settlement device 20, and a store exit device 60.

[0150] Each device and each terminal is connected to the network 55 in a way that allows for communication. Each device and each terminal is a computer device equipped with a CPU, ROM, RAM, communication unit, etc.

[0151] The registration and settlement device 20 shall operate in full self-service mode. Upon completion of settlement, the registration and settlement device 20 shall issue a settlement completion certificate. The settlement completion certificate shall display information indicating that settlement has been completed and transaction identification information identifying the transaction in a two-dimensional code (hereinafter referred to as the "exit code"). The exit code may be printed on paper or displayed on a portable electronic device carried by the customer.

[0152] The exit device 60 is installed in the passageway through which customers pass after completing their payment. As shown in Figure 12, the exit device 60 includes an exit gate 1211, an exit monitor 1212, and a rotating light 1213. When the exit device 60 reads the exit code, it opens the exit gate 1211. When the exit device 60 reads the exit code, it obtains transaction information identified by the transaction identification information from the store controller 10. The transaction information includes registration information, captured images (images capturing the situation when each product is registered), and basket images. The transaction information may also be included in the exit code. In this case, the exit device 60 can obtain the transaction information by decoding the exit code. Alternatively, the transaction information can be stored in an external server device instead of the store controller 10. In this case, when the exit device 60 reads the exit code, it should obtain the transaction information from the external server device.

[0153] A store employee is stationed at the exit monitor 1212. The exit monitor 1212 is a touch panel display. Based on the transaction information, the exit monitor 1212 displays a registration confirmation screen (similar to the registration confirmation screen 540 in Figure 5(D)). The rotating light 1213 is installed near the exit gate. The rotating light 1213 illuminates in various modes, such as an open light mode, a closed light mode, and an alert mode to indicate an error.

[0154] The exit monitor 1212 receives various operations from store staff. These operations include operations related to the occurrence of an abnormality that causes the exit gate 1211 to remain closed. For example, if a store staff member checks the registration confirmation screen and finds a clear discrepancy between the registered product and the product the customer possesses (for example, if one large-sized product is registered, but the customer is found to possess multiple copies of that product), the store staff member operates the exit monitor 1212 to keep the exit gate 1211 closed. At this time, the rotating light 1213 lights up in an alert pattern. The store staff member can then speak to the customer who has stopped at the exit gate 1211 to confirm the products the customer is possessing.

[0155] (Functional configuration of sales data processing system St2) Figure 12 is a block diagram showing an example of the functional configuration of the sales data processing system St2 according to Modification 2. As shown in Figure 12, the sales data processing system St1 comprises a store controller 10, a registration and settlement device 20, and a store exit device 60.

[0156] (Regarding the exit device 60) The store exit device 60 comprises a store exit reception unit 1201, an acquisition unit 402, and a display control unit 405. Each functional unit is implemented by the CPU of the store exit device 60. That is, the CPU implements each functional unit by executing the sales data processing program according to this embodiment.

[0157] The exit reception unit 1201 accepts exit operations from customers who have finished settling payments for items registered by the registration unit 401. The exit reception unit 1201 includes, for example, a scanner device. The exit operation is an operation related to reading an exit code. The exit reception unit 1201 reads the exit code. Note that the exit operation may also be an operation to input transaction identification information (numbers, etc.). Once the exit reception unit 1201 reads the exit code, it makes the exit gate 1211 available to open.

[0158] When the exit operation is received by the exit reception unit 1201, the acquisition unit 402 requests the store controller 10 to send transaction information and acquires the transaction information from the store controller 10. The display control unit 405 of the exit device 60 displays a registration screen (similar to the registration confirmation screen 540 in Figure 5(D)) related to the customer's transaction on the exit monitor (exit display unit) provided in a predetermined exit area.

[0159] (Store exit process performed by store exit device 60) Figure 13 is a flowchart showing an example of the store exit process performed by the store exit device 60 according to Modification 2. As shown in Figure 13, the store exit device 60 scans the store exit code (step S1301). Then, based on the store exit code, the store exit device 60 requests the store controller 10 to send transaction information (step S1302) and receives the transaction information from the store controller 10 (step S1303).

[0160] Next, the exit device 60 displays a registration confirmation screen (similar to the registration confirmation screen 540 in Figure 5(D)) on the exit monitor 1212 based on the registration information (step S1304). Then, the exit device 60 determines whether or not it has received an operation related to an abnormality from the store employee (step S1305).

[0161] If no operation related to the occurrence of an abnormality is accepted (step S1305: NO), the exit device 60 opens the exit gate 1211 (step S1306) and terminates the series of processes. On the other hand, if an operation related to the occurrence of an abnormality is accepted (step S1305: YES), the exit device 60 illuminates the rotating light 1213 in an alert-indicating lighting pattern (step S1307), closes the exit gate 1211 (step S1308), and terminates the series of processes.

[0162] As described above, the sales data processing system St2 (store exit device 60) according to the modified example 2 acquires captured images when a customer who has finished settling their bill performs a store exit operation (store exit code reading operation) and displays a list of images related to the customer's transaction on the store exit monitor 1212. This allows customers to be aware that their scanning operations are being monitored even when they leave the store. Therefore, it has a deterrent effect on fraudulent product registration. Furthermore, by displaying an image list on the exit monitor, store staff can verify the registration operation for each product and the products the customer possesses. Thus, it can support appropriate transactions.

[0163] (Example of modified example 1 where the sales data processing system St1 includes a store exit device 60) In addition, the sales data processing system St1 in Modification 1 may be equipped with a store exit device 60. The settlement device 40 (Figure 8) in Modification 1 issues a settlement completion certificate including a store exit code when settlement is completed. The store exit device 60 receives a store exit operation (exit code reading operation) from a customer who has completed settlement, acquires an image, and displays a list of images related to the customer's transaction on the store exit monitor.

[0164] (Variation 3: An example of showing or hiding the basket image 544) Next, we will describe Modification 3. Modification 3 describes an example of controlling the display or hiding of the basket image 544. In Modification 3, the registration and payment device 20 analyzes the basket image in the upstream shopping basket to determine whether or not there are any products. If the registration and payment device 20 determines that there are products in the upstream shopping basket, it displays the basket image 544 on the registration confirmation screen 540 (Figure 5(D)). On the other hand, if the registration and payment device 20 determines that there are no products in the upstream shopping basket, it does not display the basket image 544 on the registration confirmation screen 540 (Figure 5(D)).

[0165] According to Modification 3, the shopping cart image 544 can be displayed depending on whether or not there are items in the shopping cart. This makes it possible to more effectively make customers aware that there are items remaining in their shopping cart. In addition, when the shopping cart image 544 is displayed, the monitoring staff can easily understand that there are items that have not been registered. This allows them to carefully monitor the customer in question, thereby improving the efficiency of monitoring.

[0166] (Example 4: When registered using a preset key, the product will not be imaged.) Next, Modification 4 will be described. In the embodiment described above, an example was given in which imaging of the product was performed even when it was registered using a preset key. Modification 4 will describe an example in which imaging of the product is not performed when it is registered using a preset key. In Modification 4, the guidance unit 403 does not provide imaging guidance even if the product is registered by pressing a preset key.

[0167] Furthermore, for products registered using a preset key, the display control unit 405 displays a pre-prepared image instead of the captured image 543 (Figure 5(D)). The image can be any image, such as an illustration or photograph, that allows the user to recognize that it is a registered product. For example, the image may be an image included in the preset key 512 (Figure 5(A)), or it may be text information for the product in question.

[0168] According to Modification 4, the registration and settlement device 20 does not perform imaging guidance by the guidance unit 403 and does not image registered products using preset keys, thereby speeding up product registration and reducing the processing load related to imaging guidance and imaging.

[0169] (Modification 5: An example in which the registration and settlement device 20 is not equipped with a weighing device 242) Next, Modification 5 will be described. In the embodiment described above, an example was described in which the registration and settlement device 20 is equipped with a weighing scale 242. In Modification 5, an example will be described in which the registration and settlement device 20 is not equipped with a weighing scale 242. In Modification 5, the registration and settlement device 20 does not make a judgment regarding weight abnormalities (step S708d in Figure 7). For this reason, the registration and settlement device 20 also does not perform the process of calling a store clerk in the event of a weight abnormality (step S708e in Figure 7).

[0170] In Modification 5, the display control unit 405 also displays the captured image 543 when a scan operation is detected, regardless of whether the product is registered or not. In Modification 5, since no judgment is made regarding weight abnormalities, even if the customer's hand is covering the product code during the product scan operation (for example, captured image 543d in Figure 5(D)) and the product is not registered, a weight abnormality will not be detected. The display control unit 405 displays the captured image 543 related to the scan operation.

[0171] According to Modification 5, when the declaration to start settlement is received, the image list 542 and captured image 543 in Figure 5(D) are displayed, allowing the customer to realize that the product in question is not registered. This encourages the customer to register the product.

[0172] (Variation 6: An example of displaying the image list at a time other than when the settlement commencement declaration is received) Next, we will describe Modification 6. In the embodiment described above, the image list 542 (Figure 5(D)) was shown in an example where it is displayed at the time the settlement commencement declaration is received. In Modification 6, we will describe an example where the image list 542 is displayed at a time other than that. In Modification 6, the image list 542 may be displayed at the following times, in addition to or instead of the time the settlement commencement declaration is received.

[0173] (Each time a product is registered) For example, the image list 542 may be displayed each time a product is registered. Specifically, the display control unit 405 may display the image list 542 with the captured image 543 of the product added each time a product is registered. In this case, the image list 542 may be hidden after a certain period of time (for example, a few seconds).

[0174] (While the product is being registered, at any time) Furthermore, the image list 542 may be displayed at all times while a product is being registered. Specifically, the display control unit 405 displays the image list 542 at all times while a product is being registered. Then, each time a product is registered, the display control unit 405 should add the captured image 543 of that product to the image list 542.

[0175] (Timing after settlement is complete) Furthermore, the image list 542 may be displayed after the settlement is completed. Specifically, the image list 542 may be displayed after the settlement start button 546 (Figure 5(D)) is pressed. For example, the image list 542 may be displayed on the payment type selection screen 610 (Figure 6(A)) or on the payment processing screen 620 (Figure 6(B)). Also, the image list 542 may be displayed on a screen after the settlement is completed (for example, a screen prompting the user to receive a receipt).

[0176] According to Modification 6, the customer can be made aware that their reading operations are being monitored. This has a deterrent effect on fraudulent product registration. In addition, the image list 542 allows the customer to understand the registration operations for each product, so they can notice if there are any products that have not been registered. As a result, the customer can initiate a separate transaction to register the products that were not registered.

[0177] (Example 7: Displaying captured image 543 when fraud is detected) Next, we will describe Modification 7. In the embodiment described above, the captured image 543 is an image capturing the situation when each product is registered. In Modification 7, the captured image 543 is an image capturing the situation when each product is registered, and is also an image when fraud is detected. Fraud is, for example, a weight anomaly (registration by overlapping registrations or changing product codes). Also, if the registration and settlement device 20 is configured not to have a weighing scale 242, fraud can be defined as a scan operation being detected but the product not being registered.

[0178] According to Modification 7, when fraud is detected, the captured image 543 (image list 542) is displayed, thereby improving the deterrent effect against fraudulent product registration. In addition, the monitoring staff can easily understand that fraud may have occurred because the captured image 543 is displayed. Therefore, the efficiency of monitoring can be improved, and thus a deterrent effect against fraudulent product registration can be obtained.

[0179] (Variation 8: An example of displaying the image list 542 on the transaction status management device 11) Next, we will describe Modification 8. Modification 8 describes an example in which the transaction status management device 11 displays the image list 542. The transaction status management device 11 displays multiple screens (split screens) corresponding to each of the multiple registration settlement devices 20. In Modification 8, the transaction status management device 11 may display the image list 542 and the shopping cart image 544 on the split screen.

[0180] The registration and payment device 20 that is the target of displaying the image list 542 and the shopping cart image 544 may be the registration and payment device 20 that displays the image list 542. If there is a registration and payment device 20 among the multiple registration and payment devices 20 that displays the image list 542, the split screen may be canceled and the image list 542 and shopping cart image 544 corresponding to that registration and payment device 20 may be displayed (large screen display).

[0181] Furthermore, as shown in the modified example 2 above, the transaction status management device 11 can also be used as the exit monitor 1212. In this case, when a customer passes through, the exit device 60 may cancel the split screen displayed on the transaction status management device 11 and display the image list 542 and shopping cart image 544 corresponding to that customer on the transaction status management device 11 (large screen display). Specifically, the exit device 60 can scan the exit code to obtain the image list 542 corresponding to the customer's transaction information and display the image list 542 and shopping cart image 544 on the transaction status management device 11 (large screen display).

[0182] According to Modification 8, in the transaction status management device 11, store employees can check the image list 542 and the shopping cart image 544. This enhances the deterrent effect against fraudulent product registration and also enhances the deterrent effect against registration omissions.

[0183] (Modification 9: Another example related to the acquisition of captured images) Next, we will describe Modification 9. In the embodiment described above, we described an example in which an image of a product captured by the customer-side scanner unit 206 is acquired. In Modification 9, we will describe an example in which an image of a product captured by the camera 214 is acquired instead of or in addition to the customer-side scanner unit 206.

[0184] In the normal imaging mode, camera 214 captures an image (a bird's-eye view) that includes information about the customer and their surroundings. In modified example 9, when a product is registered using a preset key, the registration and payment device 20 switches from the normal imaging mode to a predetermined imaging mode. The predetermined imaging mode is a mode in which camera 214 captures the preset registered product together with, or instead of, the customer-side scanner unit 206. Specifically, in the predetermined imaging mode, camera 214 focuses on the customer's hands and the area around the customer-side display unit 205 (touch panel operation unit) to reliably acquire an image of the product the customer is holding. As a result, the acquisition unit 402 acquires the image of the preset registered product captured by camera 214. When camera 214 has finished capturing the image, the registration and payment device 20 exits the imaging mode and returns to the normal imaging mode.

[0185] The following is a summary of the embodiments. [Title of Invention] System, Sales Data Processing Device, and Program [Technical Field] The present invention relates to a system, a sales data processing device, and a program. [Background technology]

[0186] In recent years, fully self-checkout systems have become widespread. In fully self-checkout systems, customers register their items and complete the payment process themselves (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2020-017075 [Overview of the prefecture] [Problems the invention aims to solve] However, conventional technology had problems such as the possibility of fraudulent product registration or omissions in product registration, which could prevent transactions from being conducted properly. This invention has been made in view of these circumstances, and its purpose is to provide a technology that can support appropriate transactions.

[0187] [Means for solving the problem] (1) In order to solve the above-mentioned problems, a system according to one aspect of the present invention is characterized by comprising: a registration unit that registers products by customer operation; an acquisition unit that acquires captured images of the status of each product registration operation by the registration unit; and a display control unit that displays an image list arranged by the acquisition unit to the customer. The above configuration allows customers to be aware that their reading operations are being monitored. This deters fraudulent product registration. Furthermore, the image list 542 allows customers to understand the registration process for each product. For example, if a customer intends to purchase four items but only three are registered, they can notice that there are missing items. This allows customers to be prompted to register the missing items, thereby reducing registration errors. Consequently, it supports appropriate transactions.

[0188] (2) In the configuration of (1) above, a declaration receiving unit may be provided that receives a declaration that payment will be made for each product registered by the registration unit, and the display control unit may display the image list when the declaration is received by the declaration receiving unit. According to the above configuration, the image list 542 can be presented to the customer at the time registration is complete. Therefore, at the time registration is complete, the customer can be made aware that the reading operation is being monitored, and can also be made aware of any products that have not been registered.

[0189] (3) In the configuration of (1) or (2) above, the acquisition unit may acquire an image of the storage unit showing the inside of the storage unit used for transporting the goods, in addition to the captured image, and the display control unit may display the image list and the storage unit image. The above configuration allows for more efficient notification of any unregistered products to customers.

[0190] (4) In the configuration of (1) or (2) above, the system may be configured to include an exit reception unit that receives an exit operation from the customer who has finished settling the payment for the goods registered by the registration unit, the acquisition unit acquires the captured image when the exit operation is received by the exit reception unit, and the display control unit displays the list of images related to the customer's transaction on an exit display unit provided in a predetermined exit area. With the above configuration, customers can be made aware that their scanning operations are being monitored even when they leave the store. This has a deterrent effect on fraudulent product registration. In addition, by displaying a list of images on the exit monitor, store staff can verify the registration operation for each product and the products the customer is holding. Therefore, it is possible to support appropriate transactions.

[0191] (5) In the configuration of (1) or (2) above, the registration unit may register the product by reading the product code attached to the product at the customer's operation, and the acquisition unit may acquire the captured image showing the status of the reading operation for each product. With the above configuration, the situation during the scan operation can be displayed as the captured image 543, allowing customers to be aware that their scan operation is being monitored. This improves the deterrent effect against fraud such as duplicate registration or substitution of product codes.

[0192] (6) In the configuration of (1) or (2) above, the registration unit may register a product by pressing an operator corresponding to the product, and the guidance unit may provide guidance to prompt imaging of the product registered by pressing the operator, and the acquisition unit may acquire the image of the product that has been imaged in accordance with the guidance. According to the above configuration, pressing the preset key 512 allows the system to recognize that a product has been registered based on the registration operation. In other words, if the image 543 of the product in question is not displayed in the image list 542, the customer can be made aware that there is a product that has not been registered.

[0193] (7) In order to solve the above-mentioned problems, another aspect of the present invention is a sales data processing device comprising: a registration unit that registers products by customer operation; an acquisition unit that acquires captured images of the status of each product registration operation by the registration unit; and a display control unit that displays an image list arranged by the acquisition unit to the customer. The above configuration allows customers to be aware that their reading operations are being monitored. This deters fraudulent product registration. Furthermore, the image list 542 allows customers to understand the registration process for each product. For example, if a customer intends to purchase four items but only three are registered, they can notice that there are missing items. This allows customers to be prompted to register the missing items, thereby reducing registration errors. Consequently, it supports appropriate transactions.

[0194] (8) In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes the computer of a sales data processing system to function as a registration unit that registers products based on customer operations, an acquisition unit that acquires images capturing the status of each product registration operation by the registration unit, and a display control unit that displays an image list, which is an arrangement of the images acquired by the acquisition unit, to the customer. The above configuration allows customers to be aware that their reading operations are being monitored. This deters fraudulent product registration. Furthermore, the image list 542 allows customers to understand the registration process for each product. For example, if a customer intends to purchase four items but only three are registered, they can notice that there are missing items. This allows customers to be prompted to register the missing items, thereby reducing registration errors. Consequently, it supports appropriate transactions.

[0195] Furthermore, all or part of the functions (input / output, storage, processing (including judgment)) of the registration and settlement device 20 described above may be implemented in a device other than the one described as the entity that executes the said function.

[0196] Specifically, the above description described a configuration in which the registration and settlement device 20 or the mobile terminal device 30 comprises the following functional units: a registration unit 401, an acquisition unit 402, a guidance unit 403, a declaration acceptance unit 404, and a display control unit 405, as shown in Figure 4 or Figure 9. The description also described a configuration in which the settlement device 40 comprises the following functional units: an acquisition unit 402 and a display control unit 405. Furthermore, the description described a configuration in which the store exit device 60 comprises the following functional units: an acquisition unit 402, a display control unit 405, and a store exit acceptance unit 1201, as shown in Figure 13. However, all or part of these functional units may be provided in other computer devices. For example, all or part of these functional units may be provided in the store controller 10, an external server device, or another computer device. Also, the computer devices equipped with these functional units are not limited to multiple devices; there may be only one.

[0197] Specifically, for example, instead of the registration and payment device 20, the mobile terminal device 30, the payment device 40, and the store exit device 60, the store controller 10 or an external server device may display an image list 542 which is a collection of captured images 543 (Figure 5(D)) showing the situation when a customer registers an item.

[0198] In relation to the above, the registration and settlement device 20, the mobile terminal device 30, the settlement device 40, and the store exit device 60 may function as so-called thin clients specializing in the input / output interface portion for product registration and settlement. In other words, the registration and settlement device 20, the mobile terminal device 30, the settlement device 40, and the store exit device 60 may receive various inputs (operation by the operator, detection by a device such as a scanner), transmit the input information (operation information, scan information, etc.) to the server device, receive the processing results of the server device based on the input information (updated screen information, device control information, etc.), and perform various outputs (display on the display unit, device control).

[0199] Furthermore, the programs for implementing the sales data processing systems St, St1, St2, the registration and settlement device 20, the mobile terminal device 30, the settlement device 40, and the store exit device 60 described above may be recorded on a computer-readable recording medium, and the programs may be loaded into a computer system and executed. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as USB (Universal Serial Bus) flash memory, SSD (Solid State Drive), flexible disk, magneto-optical disk, ROM, CD-ROM, and storage devices such as hard disks built into a computer system. In addition, "computer-readable recording medium" also includes volatile memory (RAM) inside a computer system that acts as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, which retains the program for a certain period of time. Furthermore, the above program may be transmitted from the computer system that stores the program in a storage device, etc., to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" used to transmit the program refers to a medium that has the function of transmitting information, such as a network (communication network) like the Internet or a communication line (communication line) like a telephone line. Furthermore, the program described above may be intended to implement only a part of the functions mentioned above. Moreover, it may be a so-called differential file (differential program) that can implement the aforementioned functions in combination with a program already recorded in the computer system. [Explanation of Symbols]

[0200] St, St1, St2…Sales data processing system, Sv…Cloud server, 10…Store controller, 20…Registration and settlement device, 30…Mobile terminal device, 40…Settlement device, 60…Store exit device, 201…CPU, 202…ROM, 203…RAM, 204…Hard disk, 205…Customer-side display unit, 206…Customer-side scanner unit, 242…Weighing device, 214…Camera, 401…Registration unit, 402…Acquisition unit, 403…Information unit, 404…Declaration reception unit, 405…Display control unit, 1201…Store exit reception unit

Claims

1. A registration unit that registers products based on customer operations, An acquisition unit acquires images capturing the status of each product registration operation performed by the aforementioned registration unit, A display control unit that displays an image list, arranged in order of the captured images acquired by the acquisition unit, to the customer, A system characterized by comprising the following features.

2. The system includes a declaration receiving unit that accepts declarations of intent to settle each product registered by the aforementioned registration unit. The display control unit displays the image list when the declaration is received by the declaration receiving unit. The system according to feature 1.

3. In addition to the captured image, the acquisition unit acquires an image of the storage unit showing the inside of the storage unit used for transporting the goods. The display control unit displays the image list and the storage unit image. The system according to claim 1 or 2, characterized in that it is the same as described in claim 1 or 2.

4. The store is equipped with an exit reception unit that accepts exit requests from customers who have completed payment for the goods registered by the registration unit, The acquisition unit acquires the captured image when the exit operation is received by the exit reception unit. The display control unit causes the exit display unit, which is provided in a predetermined exit area, to display the list of images related to the customer's transaction. The system according to claim 1 or 2, characterized in that it is the same as described in claim 1 or 2.

5. The registration unit registers the product by reading the product code attached to the product based on the customer's operation. The acquisition unit acquires the captured image showing the status related to the reading operation of each product. The system according to claim 1 or 2.

6. The registration unit registers products by pressing the corresponding operator. The system includes a guide unit that prompts the user to take an image of the registered product by pressing the aforementioned control, The acquisition unit acquires the captured image of the product captured in accordance with the guidance. The system according to claim 1 or 2.

7. A registration unit that registers products based on customer operations, An acquisition unit acquires images capturing the status of each product registration operation performed by the aforementioned registration unit, A display control unit that displays an image list, arranged in order of the captured images acquired by the acquisition unit, to the customer, A sales data processing device characterized by comprising the following features.

8. The computer for the sales data processing system A registration unit that registers products based on customer operations. An acquisition unit acquires images capturing the status of each product registration operation performed by the aforementioned registration unit. A display control unit that displays an image list, arranged in order of the captured images acquired by the acquisition unit, to the customer. A program characterized by being designed to function as such.

Images