Payment devices, systems, and programs

Abstract

To conduct transactions efficiently. [Solution] The payment device performs payment based on registration data generated by a registration device operated by a store employee, and based on customer operation. The payment device comprises a receiving means, an additional registration means, and a payment means. The receiving means receives an authorization command from the registration device after receiving the registration data, which authorizes additional registration. The additional registration means registers additional products upon the receiving means receiving the authorization command. The payment means performs payment based on the products added by the additional registration means and the products indicated by the registration data.

Description

Technical Field

[0001] The present invention relates to a settlement device, a system, and a program.

Background Art

[0002] In recent years, a system including a registration device operated by a store clerk to register products and a settlement device operated by a customer to perform settlement has been spreading (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 transactions may not be carried out efficiently.

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

Means for Solving the Problems

[0006] In order to solve the above-described problems, a settlement device according to an aspect of the present invention is a settlement device that performs settlement by a customer's operation based on registration data generated by a registration device operated by a store clerk, and includes: a receiving unit that receives a permission command for permitting additional registration from the registration device after receiving the registration data; an additional registration unit that performs additional registration of products when the receiving unit receives the permission command; and a settlement unit that performs settlement based on the products additionally registered by the additional registration unit and the products indicated by the registration data. The settlement device is characterized by including these components.

[0007] To solve the above-mentioned problems, another aspect of the present invention is a payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store clerk, and is characterized by comprising: a request means for requesting permission to add products to the registration data; and a payment means that, when permission for additional product registration is approved in response to the request means, performs payment based on the additionally registered products and the products indicated by the registration data.

[0008] To solve the above-mentioned problems, another aspect of the present invention is a payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store clerk, and is characterized by comprising: a declaration receiving means that receives a declaration indicating the start of additional registration for the registration data; and an output means that, upon receiving the declaration by the declaration receiving means, outputs information to the registration device indicating that fact.

[0009] To solve the above-mentioned problems, another aspect of the present invention is a system comprising: a registration device operated by a store clerk to generate registration data; and a settlement device that performs settlement by customer operation based on the registration data generated by the registration device, wherein the settlement device comprises: a receiving means that receives a permission command from the registration device to grant permission for additional registration after receiving the registration data; an additional registration means that performs additional product registration upon the receiving means receiving the permission command; and a settlement means that performs settlement based on the products additionally registered by the additional registration means and the products indicated by the registration data.

[0010] To solve the above-mentioned problems, another aspect of the present invention is a program that causes a computer to function as a payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store clerk, characterized in that the computer functions as a receiving means that receives an authorization command from the registration device that authorizes additional registration after receiving the registration data, an additional registration means that performs additional product registration when the receiving means receives the authorization command, and a payment means that performs payment based on the products additionally registered by the additional registration means and the products indicated by the registration data. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of the network configuration of the sales data processing system according to this embodiment. [Figure 2] This figure shows an example of the appearance of a registered device. [Figure 3] This figure shows an example of the hardware configuration of a registered device. [Figure 4] This figure shows an example of the appearance of a payment processing device. [Figure 5] This figure shows an example of the hardware configuration of a payment processing device. [Figure 6] This sequence diagram shows an example of the flow of additional registration performed by the sales data processing system according to this embodiment. [Figure 7] This figure shows an example of a screen related to additional registration displayed by the payment device. [Figure 8] This figure shows an example of a screen related to additional registration displayed by the registration device. [Figure 9] This is a block diagram showing an example of the functional configuration of a sales data processing system. [Figure 10] This flowchart shows an example of the additional registration process performed by the settlement device according to this embodiment. [Figure 11] This flowchart shows an example of the process related to granting permission for additional registration performed by the registration device according to this embodiment. [Figure 12]It is a sequence diagram showing an example of the process related to additional registration performed by the sales data processing system according to Modification Example 1. [Figure 13] It is a flowchart showing an example of the process related to permission for additional registration performed by the registration device according to Modification Example 1. [Figure 14] It is a flowchart showing an example of the additional registration process performed by the settlement device according to Modification Example 1. [Figure 15] It is a flowchart showing an example of the additional registration process performed by the settlement device according to Modification Example 2. [Figure 16] It is a diagram showing an example of the additional registration screen according to Modification Example 3.

Mode for Carrying Out the Invention

[0012] (Embodiment) (Network Configuration of Sales Data Processing System 1) FIG. 1 is a diagram showing an example of the network configuration of the sales data processing system 1 according to the present embodiment. The sales data processing system 1 is an example of a system. The sales data processing system 1 is introduced into various stores. The various stores are, for example, retail stores, restaurants, etc. Retail stores are, for example, supermarkets, convenience stores, drugstores, discount stores, department stores, various supply stores, etc. Restaurants are fast food, restaurants, izakayas, cafes, cafeterias, food courts, etc.

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

[0014] The store controller 10 stores various types of information necessary for transactions. The various types of information include a product master. The product master is a file that stores product information such as product identification information (e.g., JAN (Japanese Article Number) code), product name, and selling price for each product. Also, the product master includes product identification information, product name, unit price (gram unit price) of products that require measurement (non-fixed-weight products) in addition to fixed-amount products. In addition to the product master, the store controller 10 stores various types of information such as inventory status, sales history, and deposit and withdrawal records. Also, the store controller 10 stores information related to special sales and member information.

[0015] The transaction status management device 11 displays the processing status of the settlement device 30 and controls the settlement device 30. For example, a store employee (monitoring employee) is arranged at the transaction status management device 11, and the settlement device 30 is monitored by the monitoring employee. The status of each of the plurality of settlement devices 30 is displayed on the transaction status management device 11. Specifically, the transaction status management device 11 displays split screens indicating each settlement device 30 and displays the status of each settlement device 30. The monitoring employee supports the customer operating the settlement device 30 and replenishes change and receipt paper.

[0016] The registration device 20 registers products. A store employee is arranged at the registration device 20. The registration device 20 executes a registration process for registering products according to the operation of the store employee. In the registration process, the registration device 20 generates registration data for the products purchased by the customer. The registration device 20 transmits the registration data to the settlement device 30. Although a plurality of registration devices 20 may be arranged in the store, only one registration device 20 may be arranged in the store.

[0017] The settlement device 30 is a device for self-settlement by the customer. The settlement device 30 executes a settlement process based on the registration data received from the registration device 20. Although a plurality of settlement devices 30 may be arranged in the store, only one settlement device 30 may be arranged in the store.

[0018] Furthermore, the registration data is not limited to being transmitted from the registration device 20. The registration data may be encoded into a symbol code by the registration device 20 and displayed on a display medium. The display medium may be, for example, paper or an electronic medium such as a smartphone. The settlement device 30 may acquire the registration data by reading the encoded registration data from the display medium.

[0019] The sales data processing system 1 may also be equipped with a portable 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 customer of a call for an employee from the payment device 30 or if customer fraud is detected.

[0020] (Example configuration of registration device 20) Next, the configuration of the registration device 20 will be explained using Figures 2 and 3. Figure 2 shows an example of the appearance of the registration device 20. Figure 3 shows an example of the hardware configuration of the registration device 20. Counters for placing shopping baskets are arranged on one or both sides of the registration device 20.

[0021] The registration device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer-side display unit 205, a store employee-side display unit 210, a key operation unit 211, a store employee-side scanner unit 212, a printing unit 213, an audio output unit 214, and a communication unit 215. Each unit is connected to the others via a bus 230 so as to be able to communicate with each other.

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

[0023] 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 processing. This information also includes registration data that indicates registered products.

[0024] The hard disk 204 stores various types of information. For example, the hard disk 204 may store various programs executed by the CPU 201 instead of the ROM 202. Furthermore, the hard disk 204 may store information obtained from external sources or information generated during processing, instead of the RAM 203.

[0025] The customer-side display unit 205 is a touch display for the customer. The customer-side display unit 205 is facing the customer and displays various information related to product registration. The customer-side display unit 205 also accepts various inputs from the customer regarding registration. For example, the customer-side display unit 205 displays an age verification button when registering an age-verified product and accepts the press of this button.

[0026] The employee-side display unit 210 is a touch display for employees. The employee-side display unit 210 is directed towards the employee and displays various information and accepts various inputs from the employee. The employee-side display unit 210 displays preset keys corresponding to products, and when the employee operates one of these preset keys, the product is registered.

[0027] The key operation unit 211 is located on the employee's side and is equipped with various keys (hardware keys, buttons). The key operation unit 211 receives various inputs from the employee. The key operation unit 211 is equipped with a registration button corresponding to a product, and when the employee operates this registration button, the product is registered.

[0028] The employee-side scanner unit 212 is a scanner unit for employee use. The employee-side display unit 210 includes an imaging unit 212a and a handheld scanner 212b. The imaging unit 212a is located in the housing of the registration device 20. The imaging unit 212a 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) products. When an employee holds a product over the imaging unit 212a, the product is imaged by the imaging unit 212a. The imaging unit 212a optically images the symbol code (such as a barcode or 2D code attached to the product) or the whole or a part of the product (object) that is held over the imaging window. The handheld scanner 212b is a laser-type scanner unit that can be held by an employee. The employee-side scanner unit 212 only needs to include at least one of the imaging unit 212a and the handheld scanner 212b. Furthermore, the reading method used by the employee-side scanner unit 212 is not limited to CCD, CMOS, or laser; a pen-based method is also possible.

[0029] Symbol codes include barcodes attached to products, employee codes attached to employee name tags, and membership codes attached to membership cards. Barcodes attached to products are codes that identify the product, such as JAN codes, PLU (Price Look Up) codes, and in-store codes. The registration device 20 registers the product when the employee-side scanner unit 212 reads the barcode attached to the product.

[0030] The registration device 20 performs processing based on the code read by the store clerk's scanner unit 212. The registration device 20 determines the type of code read (product code, store clerk code, member code, etc.) by checking the values ​​of flags etc. indicated by predetermined digits in the code, the number of digits read, etc. For example, if the registration device 20 determines that the read code is a product code, it performs product registration processing. If the registration device 20 determines that the read code is a store clerk code, it performs login processing. If the registration device 20 determines that the read code is a member code, it performs processing to acquire member information.

[0031] The printing unit 213 prints and outputs various media (receipts, invoices, etc.).

[0032] The audio output unit 214 outputs sounds related to product registration. For example, the audio output unit 214 outputs reading sounds (scan sounds) when various codes are scanned, voices indicating registered products (registration data), various voice guidance, and warning sounds.

[0033] The communication unit 215 is an interface for sending and receiving information with other devices (such as the store controller 10, transaction status management device 11, and settlement device 30).

[0034] (Example of configuration of payment device 30) Next, the configuration of the payment device 30 will be explained using Figures 4 and 5. Figure 4 shows an example of the appearance of the payment device 30. Figure 5 shows an example of the hardware configuration of the checkout device 30. Counters for placing shopping baskets are arranged on one or both sides of the checkout device 30.

[0035] The payment device 30 includes a CPU 301, a ROM 302, a RAM 303, a hard disk 304, a customer-side display unit 305, a customer-side scanner unit 306, a payment terminal 308, a change dispenser 309, a printing unit 313, an audio output unit 314, a communication unit 315, a camera 316, and a signpost 320. Each unit is connected to the others via a bus 330 so as to be able to communicate with each other.

[0036] The CPU 301 is a central processing unit that controls the operation of the settlement device 30 by reading and executing various programs stored in the ROM 302. These various programs include the settlement processing program according to this embodiment. ROM302 is read-only memory that stores various information used by the CPU301, including various programs.

[0037] RAM303 is a read-and-write memory that stores various types of information. For example, RAM303 stores information obtained from external sources (e.g., registration data obtained from the registration device 20) and information generated during processing (e.g., settlement information). This information also includes settlement information generated during settlement.

[0038] The hard disk 304 stores various types of information. For example, the hard disk 304 stores (records) the imaging results (e.g., video) captured by the camera 316. The hard disk 304 may store various programs executed by the CPU 301 instead of the ROM 302. Alternatively, the hard disk 304 may store information acquired from external sources or information generated during processing instead of the RAM 303.

[0039] The customer-side display unit 305 is a touch display for customers. The customer-side display unit 305 is facing the customer and displays various information related to registration and payment. The customer-side display unit 305 also receives various inputs from the customer regarding payment. For example, by receiving registration data from the employee-side display unit 310, the customer-side display unit 305 displays multiple payment type selection buttons corresponding to multiple payment types. The customer-side display unit 305 accepts the selection of one button (one payment type) from among the multiple payment type selection buttons.

[0040] The customer-side scanner unit 306 is a scanner unit for customers. Specifically, the customer-side scanner unit 306 includes an imaging unit. The imaging unit is an image sensor having an image element such as a CCD or CMOS. The imaging unit reads (images) member information. Member information is represented by a member code (barcode or 2D code) attached to a member card presented by the operator (customer) or a member code (barcode or 2D code) displayed on a mobile terminal. Note that the reading method by the customer-side scanner unit 306 is not limited to CCD or CMOS; a laser method or a pen method can also be used.

[0041] The payment terminal 308 is a payment terminal that reads information stored in various payment media such as various cards and mobile terminals, and performs various payments based on the read information. The reading method of the payment terminal 308 includes contact method and contactless method. The payments performed by the payment terminal 308 include credit card payments, charge media payments, and code payments. Credit card payments are payments based on credit cards. Charge media payments are payments performed based on the balance stored in the charge media. Charge media include, for example, electronic money cards (transportation IC cards and retail IC cards) and mobile terminals. Hereafter, charge media payments will be referred to as electronic money payments. Code payments are payments based on a payment code (a code including customer identification information) displayed on a mobile terminal.

[0042] The change dispenser 309 is a cash settlement mechanism that handles the deposit and withdrawal of cash. The change dispenser 309 is facing the customer and accepts various operations and cash insertions from the customer. Specifically, the change dispenser 309 has an input slot and an output slot for banknotes and coins. The change dispenser 309 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. In addition to being installed on the customer side, the change dispenser 309 may also be installed on the employee side. In this case, the change dispenser 309 may accept various operations and cash insertions from the employee.

[0043] The payment device 30 performs processing based on the code read by the customer-side scanner unit 306. The payment device 30 determines the type of code read (employee code, member code, etc.) by checking the values ​​of flags etc. indicated by predetermined digits in the code, the number of digits read, etc. For example, if the payment device 30 determines that the read code is an employee code, it performs login processing. Also, if the payment device 30 determines that the read code is a member code, it grants the member customer benefits such as points.

[0044] The printing unit 313 prints and outputs various media (receipts, invoices, etc.).

[0045] The audio output unit 314 outputs sounds related to payment. For example, the audio output unit 314 outputs reading sounds (scanning sounds) when various codes are scanned, voice guidance related to payment, and warning sounds.

[0046] The communication unit 315 is an interface for sending and receiving information with other devices (such as the store controller 10, transaction status management device 11, and settlement device 30).

[0047] Camera 316 is mounted above the customer-side display unit 305. Camera 316 is a camera that continuously captures video or still images. Camera 316 can be a CCD camera or a CMOS camera. Camera 316 captures images of the customer's payment operation. Camera 316 also captures images of the banknotes and other items being inserted.

[0048] The sign pole 320 is equipped with, for example, a light-emitting part (e.g., an LED (light-emitting diode)) and can be lit in a predetermined lighting pattern. The lighting pattern includes a color pattern and a flashing pattern. The sign pole 320 can provide various notifications depending on the lighting pattern. These notifications include, for example, notifications indicating the status such as "in use," notifications to call a staff member, and notifications that a customer has committed fraudulent activity.

[0049] (Regarding issues related to adding products to the website) After registration data has been transmitted from the registration device 20 to the payment device 30, a customer may realize they have forgotten to purchase an item (for example, a paid shopping bag, cutlery, etc.). When an additional item needs to be registered, the payment device 30 performs a "recall" to return the registration data to the registration device 20. When registration data is recalled, the employee performing the registration work for the next customer at the registration device 20 stops that work and performs the registration work for the previous customer's additional purchase. Alternatively, without recalling the registration data, it is also possible to register a paid shopping bag (hereinafter referred to as "shopping bag") at the payment device 30 by calling a nearby employee, having that employee log in, and operating the device in a predetermined maintenance mode.

[0050] However, during busy periods, if a previous customer forgets to buy a shopping bag, retrieving the registration data each time would hinder the registration process for the next customer. Furthermore, even if a nearby employee is called to the payment device 30, it is cumbersome to display maintenance mode and register the shopping bag, and if a nearby employee cannot immediately attend to the customer, the customer will be kept waiting. In addition, employees who do not have the authority to log in to the payment device 30, such as part-timers, temporary staff, and employees who are not cashiers, cannot make additional registrations, which can lead to inefficient customer service. As a result, transactions were sometimes not conducted efficiently. Therefore, the sales data processing system 1 according to this embodiment enables efficient transactions by allowing additional registration of specific products in the settlement device 30.

[0051] First, using Figure 6, we will explain the flow of additional registration for the sales data processing system St according to this embodiment. In the following explanation, we will refer to Figures 7 and 8 while describing Figure 6. Furthermore, in the explanation of Figure 6, we will also describe the functional configuration of the sales data processing system 1 shown in Figure 9.

[0052] Figure 6 is a sequence diagram showing an example of the flow of additional registration performed by the sales data processing system St according to this embodiment. Note that the registration device 20 is assumed to be in an invalid state, which does not permit additional registration under normal circumstances. Also, the settlement device 30 is assumed to be in a status that does not allow additional registration (a status other than the additional registration in progress status S4) under normal circumstances.

[0053] Figure 9 is a block diagram showing an example of the functional configuration of the sales data processing system 1. As shown in Figure 9, the registration device 20 comprises a registration unit 901, a transmission unit 902, a reception unit 903, and a receiving unit 904. Each functional unit is implemented by the CPU 201. That is, the CPU 201 implements each functional unit by executing the registration processing program according to this embodiment.

[0054] The settlement device 30 comprises the following functional units: a receiving unit 911, a request unit 912, a transmission unit 913, an additional registration unit 914, a settlement unit 915, a declaration acceptance unit 916, and a status management unit 917. Each functional unit is implemented by the CPU 301. That is, the CPU 301 implements each functional unit by executing the settlement processing program according to this embodiment.

[0055] (Status of payment device 30) First, the status of the settlement device 30 according to this embodiment will be described. The status management unit 917 switches to one of the following six statuses (S1) to (S6). (S1) Standby Status: The status of being in standby mode. (S2) Unselected Status: The status from when registration data is received until the payment type is selected. In other words, the status before the settlement process begins. (S3) Start Request Status: The status when a request to start additional registration has been made to the registration device 20. (S4) Additional Registration Status: The status from the time the registration device 20 receives an authorization command (hereinafter referred to as the "start command") until it receives an termination command. This status indicates that additional registration is possible. (S5) Termination Request Status: The status when a request to terminate the additional registration is made to the registration device 20. Additional registration is possible. (S6) Settlement Status: The status from the time the termination command is received from the registration device 20, or from the time the payment type is selected, until the settlement is completed.

[0056] The registration device 20 can manage the status of the settlement device 30 by obtaining status information from the settlement device 30 or by sending commands to the settlement device 30. In the following, statuses other than the "additional registration in progress" status S4 and the "termination request" status S5 (S1, S2, S3, S6 above) may be collectively referred to as the "additional registration prohibited status".

[0057] (Product registration) The registration unit 901 registers products based on the store clerk's operation. Specifically, the registration unit 901 registers products by receiving product codes read by the store clerk's scanner unit 212, the press of preset keys displayed on the store clerk's display unit 210, or the press of product keys displayed on the key operation unit 211. The registration unit 901 generates registration data including the registered products. The registration unit 901 completes product registration by pressing a predetermined operator (the subtotal button 815 in Figure 8(A)).

[0058] Returning to the explanation of Figure 6. Step S601: Once the registration of the product is complete, the registration device 20 accepts the press of the subtotal button 815 (Figure (A)). Step S602: The registration device 20 receives the designation (device number) of the settlement device 30 to which the registration data will be sent by pressing the settlement device designation button 817 (Figure 8(A)). The transmission unit 902 sends the registration data to the settlement device 30.

[0059] Step S603: The receiving unit 911 of the settlement device 30 receives registration data from the registration device 20 in standby status S1. Step S604: When the receiving unit 911 receives registration data, the settlement device 30 displays the payment type selection screen 710 (Figure 7(A)). The payment type selection screen 710 includes an additional registration button 713 for accepting additional registrations. Upon receiving registration data, the status management unit 917 switches from standby status S1 to unselected status S2.

[0060] (Request for additional registration) Step S605: The declaration reception unit 916 receives the declaration to start additional registration. Specifically, the declaration reception unit 916 receives the declaration to start additional registration when the additional registration button 713 is pressed on the payment type selection screen 710. As a result, the request unit 912 requests the registration device 20 to start additional registration. Specifically, the request unit 912 controls the transmission unit 913 to send request information (start request information) to start additional registration to the registration device 20. Also, when the status management unit 917 receives the declaration to start additional registration, it switches from the unselected status S2 to the start request status S3.

[0061] (Sending the start command) Step S606: The receiving unit 903 of the registration device 20 receives the start request information transmitted by the transmitting unit 913. Upon receiving the start request information, the registration device 20 switches to an authorizing state in which it can authorize the start of additional registration. Step S607: The reception unit 904 accepts permission to start additional registration. Specifically, the registration device 20, in the permission-ready state, displays a start request notification 818 (Figure 8(A)) to notify that a request to start additional registration has been made. The reception unit 904 then accepts permission to start additional registration for the settlement device 30, which is in start request status S3, by accepting the press of the settlement device designation button 817. Once the reception unit 904 accepts permission to start additional registration, the transmission unit 902 sends a start command (also called a "registration permission command") to the settlement device 30 to start the additional registration.

[0062] The registration device 20 (transmitter 902) may send a start command without accepting permission to start additional registration. In other words, the registration device 20 may automatically send a start command when a request to start additional registration is received. Furthermore, when the registration device 20 automatically sends a start command, it may display on the employee-side display unit 210 that additional registration is being performed at the payment device 30 (for example, an icon indicating "Additional product registration in progress").

[0063] (Adding a specific product) Step S608: The receiving unit 911 of the settlement device 30 receives a start command from the registration device 20 based on the request for the start of additional registration by the requesting unit 912. When the receiving unit 911 receives the start command, the status management unit 917 switches from the start request status S3 to the additional registration in progress status S4.

[0064] Step S609: The additional registration unit 914 enables additional registration in the additional registration status S4. Specifically, in the additional registration status S4, the additional registration unit 914 displays the additional registration screen 720 shown in Figure 7(B), activates the customer-side scanner unit 306, and enables the reading of product codes. The additional registration unit 914 scans the product code attached to a specific product (for example, a shopping bag) and adds the shopping bag to the registration.

[0065] A specific product is a pre-configured product. In this embodiment, the specific product is a shopping bag. The additional registration unit 914 only registers products based on the product code of the shopping bag. However, the specific product is not limited to shopping bags. For example, the specific product may be cutlery (described later), small items that are charged for, or products placed near the registration device 20 or the payment device 30, which are products that customers will see at checkout. In this way, the additional registration unit 914 can register additional products according to the status managed by the status management unit 917.

[0066] (Regarding items other than plastic shopping bags) The additional registration unit 914 does not register products other than the specified product. For example, if it reads the product code of another product, the settlement device 30 deletes the read code information. The settlement device 30 may also notify the system that it cannot register the product if it reads the product code of another product, or it may send a notification to the registration device 20 indicating this. Upon receiving the notification, the registration device 20 may notify the system of an error indicating that it has read the product code of another product. The registration device 20 may also register the other product by retrieving the registration data. The additional registration unit 914 does not cancel other products or change the quantity of other products while in the additional registration status S4.

[0067] The additional registration unit 914 may also allow the additional registration of other products. If additional registration of other products is performed, the registration device 20 and the transaction status management device 11 may be notified, and a store employee may be called to confirm the additional product. Furthermore, the ability to add or remove other products may be switchable depending on the settings.

[0068] (Additional registration closed) Step S610: When the payment device 30 finishes registering the shopping bags, it displays the payment type selection screen 710 again. The declaration reception unit 916 receives the declaration from the additional registration unit 914 that the additional registration has been completed. Receiving this declaration means that the payment type selection button 712 is pressed. Note that receiving this declaration may also be done by pressing another button. The other button may be, for example, a dedicated button, the registration completion button 723 in Figure 7(B), or the payment start button 733 in Figure 7(C).

[0069] Step S611: When the declaration receiving unit 916 receives the declaration of completion of additional registration, the request unit 912 requests the registration device 20 to complete the additional registration. Specifically, the request unit 912 controls the transmission unit 913 to send request information (termination request information) to the registration device 20 to terminate the additional registration. When the declaration receiving unit 916 receives the declaration of completion of additional registration, the status management unit 917 switches from the status of "additional registration in progress" S4 to the status of "termination request" S5.

[0070] (Sending termination command) Step S612: The receiving unit 903 of the registration device 20 receives the termination request information transmitted by the transmitting unit 913. When the receiving unit 903 of the registration device 20 receives the termination request information, it displays a termination request notification 828 (Figure 8(B)) to notify that a request to terminate the additional registration has been made. The reception unit 904 receives permission from the store clerk to terminate the additional registration. Specifically, the reception unit 904 receives permission to terminate the additional registration for the payment device 30, which is in the status of additional registration in progress S4, by receiving the press of the payment device designation button 817. When the reception unit 904 receives permission to terminate the additional registration, the transmitting unit 902 sends a termination command to the payment device 30 to terminate the additional registration.

[0071] The registration device 20 may also send a termination command without accepting permission to terminate the additional registration. In other words, the registration device 20 may automatically send a termination command when it receives a request to terminate the additional registration. Furthermore, if the registration device 20 is displaying an icon indicating "Adding product registration in progress" on the employee-side display unit 210, it may automatically send a termination command to clear the icon.

[0072] (Additional registrations are prohibited) Step S613: When the registration device 20 sends a termination command, it transitions to a state where it cannot permit additional registrations. This prevents the registration device 20 from sending a start command to the settlement device 30, except when there is a request for additional registration (when the settlement device 30 is in start request status S3). In other words, the registration device 20 prevents the settlement device 30 from entering the additional registration status S4, except when there is a request for additional registration.

[0073] Step S614: The receiving unit 911 of the settlement device 30 receives a termination command based on the request for termination of additional registration by the requesting unit 912. When the receiving unit 911 receives the termination command, the status management unit 917 switches from termination request status S5 to settlement in progress status S6. The additional registration unit 914 prohibits additional registration in additional registration prohibited statuses, including settlement in progress status S6.

[0074] In the above explanation, the selection of a payment type is considered a declaration of completion of additional registration. Therefore, upon receiving the completion command, the status management unit 917 switches from the completion request status S5 to the settlement status S6 without going through the unselected status S2. However, if the system is configured to accept the declaration of completion of additional registration by pressing a dedicated button, the status management unit 917 should switch from the completion request status S5 to the unselected status S2 upon receiving the completion command, and then accept the selection of a payment type. Once a payment type is selected, the status management unit 917 should switch from the unselected status S2 to the settlement status S6.

[0075] (settlement) Step S615: The settlement unit 915 performs settlement (self-settlement) based on the customer's operation. The settlement unit 915 performs settlement based on the products added and registered by the additional registration unit 914 and the products indicated by the registration data received by the receiving unit 911. Specifically, the settlement unit 915 adds the data of the added products to the registration data and performs settlement. The settlement unit 915 performs settlement processing according to the payment type selected on the payment type selection screen 710. Once settlement is performed by the settlement unit 915, the settlement device 30 terminates the process shown in this sequence diagram. Also, once settlement is complete, the status management unit 917 switches from settlement status S6 to standby status S1.

[0076] Furthermore, in the "Additional Registration Prohibited" status, including the "Checkout" status S6, scanning and registering products is prohibited. In the "Additional Registration Prohibited" status, the additional registration unit 914 may either disable the reading function of the customer-side scanner unit 306, or it may enable the reading function while erasing the scanned code information. Therefore, in the "Additional Registration Prohibited" status, even if a customer unintentionally brings a product code close to the customer-side scanner unit 306 during bagging or other operations, the product can not be registered.

[0077] (The payment method selection screen 710 is not displayed.) The payment method selection screen 710 will not be displayed in the following cases: A configuration in which the payment type is selected in the registration device 20. • A configuration in which the settlement device 30 can settle only one type of payment (for example, cash payment). - In the payment system 30, the point card is read first during payment, and a payment type is associated with the point card; in this operation, payment is made using the associated payment type (for example, including cases where the amount paid with points exceeds the purchase amount). • A configuration in which electronic money payment or credit card payment is performed at the registration device 20. In this configuration, since the registration data is not transmitted to the settlement device 30, no additional registration is performed at the settlement device 30.

[0078] If the payment type selection screen 710 is not displayed, the settlement device 30, upon receiving registration data, may display, for example, the settlement screen 740 (Figure 7(D)) instead of the payment type selection screen 710. In this case, the additional registration button 713 should be displayed on the settlement screen 740.

[0079] (Examples of screens for settlement device 30 and registration device 20) Next, using Figures 7 and 8, we will explain examples of screens related to additional registration displayed on the settlement device 30 and the registration device 20. Figure 7 shows an example of a screen related to additional registration displayed by the settlement device 30. Figure 7(A) shows the payment type selection screen 710. The payment type selection screen 710 includes a total amount field 711, a payment type selection button 712, an add registration button 713, and a staff call button 714.

[0080] The total amount field 711 is an area that shows the total amount of the products (products to be purchased) registered by the registration device 20. The payment type selection button 712 displays buttons corresponding to multiple payment types. These multiple payment types include, for example, cash payment, credit card payment, electronic money payment, and QR code payment. When any of the buttons included in the payment type selection button 712 is pressed, the payment is processed according to the payment type corresponding to the pressed button.

[0081] Button 713, which is used to declare the start of additional registrations, is a button that accepts additional registrations for shopping bags. The staff call button 714 is a button that accepts requests for staff. When the staff call button 714 is pressed, the system transitions to the staff call screen, the sign pole 320 lights up in a predetermined pattern, and a staff member is called. The staff call button 714 is intended to notify multiple staff members, including those working on the transaction status management device 11 and the registration device 20. In contrast, the additional registration button 713 is intended to notify only the staff member operating the registration device 20, which is the source of the registration data. When the add registration button 713 is pressed on the payment type selection screen 710, the settlement device 30 receives a start command in response to the store clerk's operation on the registration device 20 and transitions to the add registration screen 720 shown in Figure 7(B).

[0082] Figure 7(B) shows the additional registration screen 720. The additional registration screen 720 includes a reading guide 721, a guide image 722, and a registration completion button 723. The reading instruction 721 is a notification prompting the customer to have the product code on the shopping bag scanned by the customer-side scanner unit 306. The guidance image 722 is an image (animation, etc.) that prompts the customer to have the customer-side scanner unit 306 read the product code. The guidance image 722 is displayed in a manner that allows the user to recognize the location of the customer-side scanner unit 306 in the payment device 30. This makes it easy for the customer to understand the location of the customer-side scanner unit 306. The registration completion button 723 is a button that accepts the completion of an additional registration. When the product code of the shopping bag is scanned on the additional registration screen 720 and the registration completion button 723 is pressed, the screen transitions to the registration list screen 730 shown in Figure 7(C).

[0083] Figure 7(C) shows the registration list screen 730. The registration list screen 730 includes the registration list 731, a back button 732, and a start payment button 733. The registration list 731 shows the items (in the shopping bag) that were added and registered by the payment device 30, and the items (karinto) that were registered by the registration device 20. The added items (in the shopping bag) are displayed at the top. This allows customers to easily identify the items they have added. Alternatively, the registration list 731 may be configured to display only the added items. This would allow customers to identify the added items even more easily.

[0084] The back button 732 is a button that accepts a return to the additional registration screen 720 (Figure 7(B)). The payment start button 733 is a button that accepts the start of payment. When the payment start button 733 is pressed, the system transitions to the payment type selection screen 710 shown in Figure 7(A). On the payment type selection screen 710, the payment device 30 accepts the declaration of completion of additional registration when one of the payment types (for example, cash payment) is selected from the payment type selection buttons 712. Upon receiving the declaration of completion of additional registration, the payment device 30 receives an end command in accordance with the store clerk's operation on the registration device 20 and transitions to the payment screen 740 shown in Figure 7(D).

[0085] Depending on the screen size, font size, and layout of the customer-side display unit 305, the additional registration screen 720 and the registration list screen 730 may be displayed on a single screen. In this case, the registration completion button 723 does not need to be displayed on that single screen.

[0086] Figure 7(D) shows the settlement screen 740. The settlement screen 740 displays the amount of cash to be inserted. When an amount equal to or greater than the payment amount shown in the figure is inserted, a settlement completion button (not shown) is displayed. When the settlement completion button is pressed, a receipt is issued, and if there is change, in addition to issuing the receipt, the change is paid out and the transaction is completed. Similarly, if a payment method other than cash payment is selected, settlement will be performed according to the accepted payment method and the transaction will be completed.

[0087] (Example of the screen for registration device 20) Figure 8 shows an example of a screen related to additional registration displayed by the registration device 20. Figure 8(A) shows the registration screen 810. The registration screen 810 includes a registered product display area 811, a registered product list area 812, a price display area 813, a preset key 814, a subtotal button 815, an unsettled button 816, and a settlement device specification button 817.

[0088] The registered product display area 811 is the area that displays the most recently registered product by the store clerk. The registered product list area 812 is an area that displays a list of products registered by store staff. The total amount display area 813 is an area for displaying the total amount of registered products. The preset key 814 includes keys corresponding to a plurality of products respectively, and accepts registration of the product corresponding to the pressed key. The subtotal button 815 is a button for accepting completion of product registration. The un-settled button 816 is a button for accepting transition to a list screen of un-settled transactions for which settlement has not been completed. When a transaction to be recalled is selected on the list screen, the registered data is recalled.

[0089] The settlement device designation button 817 has the following three functions. · A function of accepting designation (number) of the settlement device 30 to which the registered data is to be sent. · A function as a start permission button for accepting permission to start additional registration. · A function as an end permission button for accepting permission to end additional registration.

[0090] (Display mode when in use or not in use) The settlement device designation buttons 817a to 817c correspond to the numbers (numbers 1 to 3) assigned to the settlement device 30. The display mode of the settlement device designation button 817 changes depending on whether it is in use or not in use. When the settlement device designation button 817 is in use, the character "used" is attached, and if it is not in use, the character "not" is attached.

[0091] In the illustration, it shows that the first settlement device 30 is in use. That is, in this transaction, it shows that the registered data has been sent to the first settlement device 30 by pressing the settlement device designation button 817a. In the illustration, the second and third settlement devices 3 are shown as not in use. Also, in the illustration, the display modes of the settlement device designation buttons 817a to 817c are all display modes (display mode with a white background) indicating that the corresponding settlement device 30 is in the additional registration prohibited status.

[0092] (Permission to start additional registration) When the registration screen 810 is displayed, if payment device 30 No. 1 requests to start additional registration, a start request notification 818 is displayed. The start request notification 818 indicates that payment device 30 has requested to start additional registration. At this time, the status of payment device 30 is start request status S3. The registration device 20 accepts permission to start additional registration and accepts the press of the payment device designation button 817a when the start request notification 818 is displayed. When the registration device 20 accepts the press of the payment device designation button 817a, it sends a start command to payment device 30 and can switch the status of payment device 30 from start request status S3 to additional registration in progress status S4. If payment device 30 is not in start request status S3, the registration device 20 will not send a start command even if the payment device designation button 817a is pressed. Furthermore, upon receiving a press of the payment device designation button 817a, the registration device 20 changes the display pattern of the payment device designation button 817a, as shown in Figure 8(B).

[0093] (Permission to terminate additional registrations) In the registration screen 820 shown in Figure 8(B), the display mode of the payment device designation button 817a (display mode with a black background) is different from the display mode shown in Figure 8(A) (display mode with a white background). The display mode of the payment device designation button 817a shown in Figure 8(B) indicates that payment device 30 No. 1 is in the status S4 of being added for registration.

[0094] When the registration screen 820 is displayed, if payment device 30 No. 1 requests the completion of additional registration, a completion request notification 828 is displayed. The completion request notification 828 indicates that payment device 30 has requested the completion of additional registration. At this time, the status of payment device 30 is completion request status S5. The registration device 20 accepts permission to complete additional registration and accepts the press of the payment device designation button 817a when the completion request notification 828 is displayed. When payment device 30 accepts the press of the payment device designation button 817a, it sends a completion command to payment device 30 and can switch the status of payment device 30 from completion request status S5 to additional registration prohibited status (for example, settlement in progress status S6). If payment device 30 is not in completion request status S5, the registration device 20 does not send a completion command even if the payment device designation button 817a is pressed. Furthermore, upon receiving a press of the payment device designation button 817a, the display mode of the payment device designation button 817 corresponding to payment device 30 No. 1 returns to the display mode shown in Figure 8(A) (a display mode indicating that additional registration is prohibited: a display mode with a white background).

[0095] With this payment device designation button 817, it is possible to designate the payment device 30, authorize the start of additional registration, and authorize the end of additional registration with a single button. This allows for effective use of the display area of ​​the registration screen 810 and simplifies the operations performed by store staff regarding additional registration.

[0096] Furthermore, the registration screen 820 may display the items (in the shopping bag) that were added and registered by the payment device 30. Specifically, the registered item display area 811 and the registered item list area 812 may display that a shopping bag costing 3 yen has been registered, and the amount display area 813 may display that the total number of items has become 2 and that the total amount has become 240 yen.

[0097] (An example of additional registration processing performed by the settlement device 30) Figure 10 is a flowchart illustrating an example of the additional registration process performed by the settlement device 30 according to this embodiment. As shown in Figure 10, the settlement device 30 determines whether or not it has received registration data from the registration device 20 in standby status S1 (step S1001). The settlement device 30 waits until it receives registration data (step S1001: NO), and when it receives registration data (step S1001: YES), it displays the payment type selection screen 710 shown in Figure 7(A) (step S1002). Upon receiving registration data, the settlement device 30 switches from standby status S1 to unselected status S2.

[0098] Then, on the payment type selection screen 710, the settlement device 30 determines whether or not it has received a declaration to start additional registration when the additional registration button 713 is pressed (step S1003). If the declaration to start additional registration has been received (step S1003: YES), the settlement device 30 requests the registration device 20 to start additional registration (step S1004). When the request to start additional registration is made, the settlement device 30 switches from the unselected status S2 to the start request status S3.

[0099] Next, the settlement device 30 waits until it receives a start command from the registration device 20 (step S1005: NO), and when it receives a start command (step S1005: YES), it displays the additional registration screen 720 shown in Figure 7(B) (step S1006). Upon receiving the start command, the settlement device 30 switches from the start request status S3 to the additional registration status S4.

[0100] The payment device 30 then determines whether the customer-side scanner unit 306 has scanned the product code of the item (shopping bag) to be added for registration (step S1007). If the product code of the shopping bag is not scanned (step S1007: NO), the payment device 30 proceeds to step S1009. On the other hand, if the product code of the shopping bag is scanned (step S1007: YES), the payment device 30 adds the item (shopping bag) for registration (step S1008). If an item is added for registration, the payment device 30 may also send information to the registration device 20 indicating that an item has been added and showing the added item.

[0101] Then, the settlement device 30 determines whether or not it has received a declaration of completion of additional registration by sequentially pressing the registration completion button 723 in Figure 7(B), the settlement start button 733 in Figure 7(C), and the payment type selection button 712 in Figure 7(A) (step S1009). If the declaration of completion of additional registration is not received (step S1009: NO), the settlement device 30 returns to step S1007. On the other hand, if the declaration of completion of additional registration is received (step S1009: YES), the settlement device 30 requests the registration device 20 to complete the additional registration (step S1010). In this case, the settlement device 30 switches from the status of "additional registration in progress" S4 to the status of "completion request" S5.

[0102] Then, the registration device 20 waits until it receives a termination command (step S1011: NO), and when it receives a termination command (step S1011: YES), it proceeds to step S1013.

[0103] If the declaration to start additional registration is not accepted in step S1003 (step S1003: NO), the settlement device 30 determines whether a payment type has been selected (step S1012). If no payment type is selected (step S1012: NO), the settlement device 30 returns to step S1003. On the other hand, if a payment type is selected (step S1012: YES), the settlement process is executed according to the accepted payment type (step S1013).

[0104] Furthermore, the settlement device 30 switches to settlement status S6 at the start of the settlement process. Specifically, if the current status of the settlement device 30 is termination request status S5, it switches from termination request status S5 to settlement status S6. Also, if the current status is unselected status S2, the settlement device 30 switches from unselected status S2 to settlement status S6.

[0105] Then, when the settlement process is executed, the settlement device 30 sends a settlement completion notification to the registration device 20 indicating that the settlement process has been completed (step S1014), and the series of processes ends. When the settlement process is executed, the settlement device 30 switches from settlement status S6 to standby status S1.

[0106] (An example of the process related to granting permission for additional registration performed by the registration device 20) Figure 11 is a flowchart showing an example of the process related to granting permission for additional registration performed by the registration device 20 according to this embodiment. As shown in Figure 11, the registration device 20 determines whether or not the registration of the product has been completed when the subtotal button 815 (Figure 8(A)) is pressed (step S1101).

[0107] The registration device 20 waits until the product registration is complete (step S1101: NO), and once the product registration is complete (step S1101: YES), it accepts the press of the payment device designation button 817 in Figure 8(A) and transmits the registration data to the payment device 30 in standby status S1 (for example, payment device 30 No. 1) (step S1102). The registration device 20 then changes the display of the payment device designation button 817a, which indicates the payment device 30 to which the registration data will be transmitted, to the "in use" display.

[0108] Next, the registration device 20 determines whether or not there is a request from the settlement device 30 to start additional registration (step S1103). If there is no request from the settlement device 30 to start additional registration (step S1103: NO), the registration device 20 proceeds to step S1108. On the other hand, if there is a request from the settlement device 30 to start additional registration (step S1103: YES), the registration device 20 transitions to a permitting state in which it can permit additional registration (step S1104).

[0109] Then, the registration device 20 notifies that a request to start additional registration has been received via a start request notification 818 (Figure 8(A)) (step S1105). Furthermore, when the payment device designation button 817a (Figure 8(A)) is pressed and permission to start additional registration is received (step S1106), the registration device 20 sends a start command to the payment device 30 (step S1107). The registration device 20 then changes the display mode of the payment device designation button 817a to a display mode indicating the additional registration in progress status S4.

[0110] Next, the registration device 20 determines whether or not the settlement device 30 has requested the termination of the additional registration (step S1108). If there is no request from the settlement device 30 to terminate the additional registration (step S1108: NO), the registration device 20 proceeds to step S1113. On the other hand, if there is a request from the settlement device 30 to terminate the additional registration (step S1108: YES), the registration device 20 notifies the settlement device 30 of the request to terminate the additional registration by sending a termination request notification 828 (Figure 8(B)) (step S1109).

[0111] Furthermore, when the payment device designation button 817a (Figure 8(A)) is pressed and permission to complete the additional registration is received (step S1110), the registration device 20 sends a completion command to the payment device 30 (step S1111). The registration device 20 then changes the display mode of the payment device designation button 817a to a display mode indicating the additional registration prohibited status.

[0112] Then, the registration device 20 transitions to a state where permission for additional registration is not permitted (step S1112). The registration device 20 may notify the settlement device 30 of the additionally registered items when it transitions to the state where permission is not permitted. The registration device 20 may also notify the system that it is transitioning to the state where permission is not permitted when it is about to enter the state where permission is not permitted.

[0113] Next, the registration device 20 determines whether or not it has received a settlement completion notification from the settlement device 30 (step S1113). If it does not receive a settlement completion notification from the settlement device 30 (step S1113: NO), the registration device 20 returns to step S1103. If it has received a settlement completion notification from the settlement device 30 (step S1113: YES), the registration device 20 terminates the series of processes.

[0114] (Effects of the embodiment) As described above, the settlement device 30 according to this embodiment receives a start command from the registration device 20 after receiving registration data, registers a specific product, and performs settlement based on the newly registered product and the product indicated by the registration data. This allows customers to easily add items themselves at the payment device 30 without having to retrieve registered data. It also prevents interruptions to the store clerk's registration operations at the registration device 20. Furthermore, even if a store clerk is called to the payment device 30, they can easily add items without having to enter a store clerk code or password, or even switch to maintenance mode (a mode exclusively for store clerks). In addition, even store clerks who do not have login privileges to the payment device 30, such as part-timers, temporary workers, or employees who are not cashiers, can easily add items. Therefore, it is possible to prevent delays in the registration process for the next customer or keep customers who wish to add items waiting when adding items. Thus, transactions can be conducted efficiently.

[0115] Furthermore, the settlement device 30 according to this embodiment prevents additional registrations by receiving a termination command from the registration device 20. This allows the payment device 30 to be set to a status where additional registration is prohibited. Therefore, even if a customer unintentionally brings the product code close to the customer-side scanner unit 306 during bagging or other operations after additional registration has been completed, the product will not be registered. Furthermore, the system can be configured so that products are not registered when customers other than the original customer use the payment device 30. Furthermore, the settlement device 30 can be prevented from switching to the "additional registration prohibited" status based on its own judgment. In other words, the settlement device 30 can switch to the "additional registration prohibited" status under the management of the registration device 20.

[0116] Furthermore, the settlement device 30 according to this embodiment enables settlement by receiving a termination command from the registration device 20. This prevents the settlement device 30 from performing settlement processing on its own initiative. In other words, the settlement device 30 can be made to start settlement processing under the management of the registration device 20.

[0117] Furthermore, the settlement device 30 according to this embodiment receives a declaration indicating the end of additional registration (for example, pressing the payment type selection button 712), requests the registration device 20 to end the additional registration, and receives an end command from the registration device 20 in response to the request to end the additional registration. This allows the system to accept a declaration from the customer that the additional registration has been completed, thus eliminating the need for visual confirmation by a store employee regarding the additional registration, and enabling the payment device 30 to be set to the "additional registration prohibited" status.

[0118] Furthermore, in this embodiment, the settlement device 30 considers the selection of a payment type (pressing the payment type selection button 712) as acceptance of a declaration of completion of additional registration. This eliminates the need to provide a dedicated button for receiving declarations of termination of additional registrations, or to accept clicks on such a dedicated button. Therefore, the process of receiving declarations of termination of additional registrations can be simplified.

[0119] Furthermore, the settlement device 30 according to this embodiment performs additional product registration according to the status indicating the state of the device from the reception of registration data to the completion of settlement. Specifically, the additional registration unit 914 performs additional product registration when the status managed by the status management unit 917 is in the additional registration status S4. This allows the registration device 20 to register additional items before settlement begins in the settlement device 30. Therefore, the newly registered items and the items registered by the registration device 20 can be settled together. Thus, settlement can be performed efficiently.

[0120] (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.

[0121] (Variation 1: An example in which the registration device 20 receives a declaration to start additional registration) First, let's describe Modification 1. In the embodiment described above, we described an example in which the settlement device 30 receives the declaration to start additional registration. In Modification 1, instead of or in addition to such an example, we will describe an example in which the registration device 20 receives the declaration to start additional registration.

[0122] (Permission for additional registration) In Modification 1, if a customer wishes to register additional shopping bags at the checkout device 30, they inform the store clerk. Upon receiving this request, the clerk performs an operation to declare the start of additional registration. In this case, the registration device 20 is configured to accept the declaration to start additional registration (by pressing the checkout device designation button 817a corresponding to the checkout device 30 where the customer who made the request is located). Upon receiving the declaration to start additional registration, the registration device 20 sends a start command to the checkout device 30.

[0123] In Modification 1, since the system does not accept a declaration from the customer to start additional registration, the additional registration button 713 is not displayed on the payment type selection screen 710 in Figure 7(A). Furthermore, the registration device 20 is not required to accept permission to start additional registration. Specifically, the registration device 20 does not display the start request notification 818 (Figure 8(A)) on the registration screen 810.

[0124] (Additional registration closed) Furthermore, in Modification 1, the registration device 20 also accepts the declaration of completion of additional registration. For example, when a store clerk visually confirms that the customer has completed additional registration, they perform an operation related to the declaration of completion of additional registration. In this case, the registration device 20 accepts the declaration of completion of additional registration (pressing the payment device designation button 817a corresponding to the payment device 30 where the customer is located). Upon receiving the declaration of completion of additional registration, the registration device 20 sends a completion command to the payment device 30.

[0125] In Modification 1, since the customer does not declare the termination of additional registration, the registration device 20 is not required to accept permission to terminate additional registration. Specifically, the registration device 20 does not display the termination request notification 828 (Figure 8(B)) on the registration screen 810.

[0126] (Status of the settlement device 30 according to modified example 1) The status of the settlement device 30 in Modification Example 1 does not include the start request status S3 and the end request status S5. That is, the status of the settlement device 30 in Modification Example 1 can be any of the following statuses: standby status S1, unselected status S2, adding registration status S4, and settlement status S6.

[0127] Next, using Figure 12, we will explain the flow of additional registration for the sales data processing system St related to Modified Example 1. Figure 12 is a sequence diagram showing an example of the flow of additional registration performed by the sales data processing system St according to Modification Example 1. In the following description, steps S601 to S604 are the same as in the embodiment and therefore will not be described. In addition, the following description will provide supplementary information on each functional unit shown in Figure 9 as appropriate.

[0128] Step S1201: Once the registration device 20 has finished transmitting the registration data, it transitions to an authorized state in which it can authorize additional registrations. Upon transmission of the registration data, the settlement device 30 (status management unit 917) switches from standby status S1 to unselected status S2. Step S1202: The registration device 20 (reception unit 904) receives a declaration to start additional registration based on an operation by a store employee in response to a customer's request. Upon receiving the declaration to start additional registration, the registration device 20 (transmission unit 902) sends a start command to the settlement device 30.

[0129] Step S1203: The payment device 30 (receiving unit 911) receives a start command from the registration device 20 in the unselected status S2. The payment device 30 switches from the unselected status S2 to the additional registration status S4. In the additional registration status S4, the payment device 30 displays the additional registration screen 720 shown in Figure 7(B), activates the customer-side scanner unit 306, and enables the reading of product codes.

[0130] Step S1204: In the status S4 of "Adding Registration," the payment device 30 (additional registration unit 914) scans the product code attached to the shopping bag and registers the shopping bag. Once the shopping bag is registered, the payment device 30 displays the registration list screen 730 shown in Figure 7(C).

[0131] Step S1205: The store clerk visually and verbally confirms the customer's registration of the shopping bag. As a result, the registration device 20 (reception unit 904) receives a declaration from the store clerk that the additional registration is complete. Upon receiving the declaration that the additional registration is complete, the registration device 20 (transmission unit 902) sends a completion command to the payment device 30.

[0132] Step S1206: When the registration device 20 sends a termination command, it transitions to an unpermitted state and terminates the process shown in this sequence diagram. This prevents the registration device 20 from sending a start command to the settlement device 30, except during the period between sending the registration data and sending the termination command (the period when the settlement device 30 is in the unselected status S2). In other words, the registration device 20 can prevent the settlement device 30 from switching to the additional registration status S4, except during that period.

[0133] Step S1207: The settlement device 30 (receiving unit 911) receives a termination command. Upon receiving the termination command, the settlement device 30 displays the payment type selection screen 710 again. In other words, the settlement unit 915 enables settlement when the receiving unit 911 receives the termination command. The settlement device 30 also switches from the "additional registration in progress" status S4 to the "not selected" status S2. That is, when the receiving unit 911 receives the termination command, the additional registration unit 914 makes additional registration impossible. In additional registration prohibited statuses, including the "not selected" status S2, even if a customer unintentionally brings the product code close to the customer-side scanner unit 306 during bagging or other operations, the product will not be registered.

[0134] The settlement device 30 may also enable the display of the payment type selection screen 710 before receiving the termination command. However, until the termination command is received, the settlement device 30 should disable the payment type selection button 712 or otherwise prevent the selection of a payment type.

[0135] Step S1208: When a payment type is selected, the settlement device 30 switches from the unselected status S2 to the settlement status S6, performs the settlement process according to the selected payment type, and terminates the process shown in this sequence diagram.

[0136] (An example of the process related to granting permission for additional registration performed by the registration device 20 in the modified example 1) Figure 13 is a flowchart showing an example of the process related to the permission for additional registration performed by the registration device 20 according to Modification 1. As shown in Figure 13, the registration device 20 determines whether or not product registration is complete when the subtotal button 815 (Figure 8(A)) is pressed (step S1301). The registration device 20 waits until registration is complete (step S1301: NO). When product registration is complete (step S1301: YES), the registration device 20 accepts (pressing the settlement device designation button 817 in Figure 8(A)) and sends the registration data to the settlement device 30 in standby status S1 (step S1302). The registration device 20 then changes the display mode of the settlement device designation button 817a, which indicates the settlement device 30 to which the registration data is sent, to the "in use" display mode.

[0137] Next, the registration device 20 transitions to an authorizing state in which it can authorize additional registration (step S1303). Then, the registration device 20 determines whether or not it has received a declaration to start additional registration (pressing the payment device designation button 817a for the display mode currently in use) based on the actions of the store clerk in response to the customer's request (step S1304). If the declaration to start additional registration is not received (step S1304: NO), the registration device 20 proceeds to step S1307.

[0138] On the other hand, if the declaration to start additional registration is received (step S1304: YES), it is determined whether the status of the settlement device 30 is unselected status S2 or not (step S1305). If the status of the settlement device 30 is not unselected status S2 (step S1305: NO), the registration device 20 proceeds to step S1307. The registration device 20 may also notify that additional registration is not possible if the status of the settlement device 30 is not unselected status S2, i.e., if settlement processing has started.

[0139] If the status of the settlement device 30 is unselected status S2 (step S1305: YES), the registration device 20 sends a start command to the settlement device 30 (step S1306). The registration device 20 then changes the display mode of the settlement device designation button 817a, which indicates the settlement device 30, to the display mode indicating the status of adding a device in progress S4.

[0140] Next, the registration device 20 determines whether or not it has received a declaration of completion of additional registration (pressing the settlement device designation button 817a, which displays status S4 indicating additional registration in progress) (step S1307). If the declaration of completion of additional registration is not received (step S1307: NO), the registration device 20 proceeds to step S1310. On the other hand, if the declaration of completion of additional registration is received (step S1307: YES), the registration device 20 sends a completion command to the settlement device 30 (step S1308).

[0141] Then, the registration device 20 changes the display mode of the settlement device designation button 817a to a display mode indicating the additional registration prohibited status. The registration device 20 also transitions to an invalid state, making it impossible to permit additional registration (step S1309). The registration device 20 may notify the settlement device 30 of the additionally registered items when transitioning to the invalid state. The registration device 20 may also notify the user that it is transitioning to the invalid state when it is about to enter the invalid state.

[0142] Next, the registration device 20 determines whether or not it has received a settlement completion notification from the settlement device 30 (step S1310). If it does not receive a settlement completion notification from the settlement device 30 (step S1310: NO), the registration device 20 returns to step S1303. If it has received a settlement completion notification from the settlement device 30 (step S1310: YES), the registration device 20 terminates the series of processes.

[0143] (An example of additional registration processing performed by the settlement device 30 according to Modification 1) Figure 14 is a flowchart showing an example of the additional registration process performed by the settlement device 30 according to Modification 1. As shown in Figure 14, the settlement device 30 determines whether or not it has received registration data from the registration device 20 (step S1401). The settlement device 30 waits until it receives registration data (step S1401: NO), and when it receives registration data (step S1401: YES), it displays the payment type selection screen 710 shown in Figure 7(A) (step S1402). When it receives registration data, the settlement device 30 switches from waiting status S1 to unselected status S2.

[0144] Then, on the payment type selection screen 710, the settlement device 30 determines whether or not it has received a start command from the registration device 20 (step S1403). If it receives a start command (step S1403: YES), the settlement device 30 displays the additional registration screen 720 shown in Figure 7(B) (step S1404). When it receives a start command, the settlement device 30 switches from the unselected status S2 to the additional registration status S4.

[0145] The payment device 30 then determines whether the customer-side scanner unit 306 has scanned the product code on the shopping bag (step S1405). If the product code on the shopping bag has not been scanned (step S1405: NO), the payment device 30 proceeds to step S1407. On the other hand, if the product code on the shopping bag has been scanned (step S1405: YES), the payment device 30 registers the product (shopping bag) as an additional item (step S1406). If an additional item has been registered, the payment device 30 may also send information to the registration device 20 indicating that an additional item has been registered and showing the newly registered item.

[0146] The settlement device 30 then determines whether or not it has received a termination command from the registration device 20 (step S1407). If it has not received a termination command (step S1407: NO), the settlement device 30 returns to step S1405. On the other hand, if it has received a termination command (step S1407: YES), it returns to step S1402 and displays the settlement type selection screen 710. When it receives a termination command, the settlement device 30 switches from the status "adding registration in progress" S4 to the status "not selected" S2.

[0147] If no start command is received in step S1403 (step S1403: NO), the settlement device 30 determines whether a payment type has been selected (step S1408). If no payment type has been selected (step S1408: NO), the settlement device 30 returns to step S1403.

[0148] On the other hand, if a payment type is selected (step S1408: YES), the settlement device 30 executes the settlement process according to the payment type selected on the payment type selection screen 710 (step S1409). The settlement device 30 switches from the unselected status S2 to the settlement in progress status S6 based on the selection of the payment type. Next, the settlement device 30 sends a settlement completion notification to the registration device 20 indicating that the settlement process has been completed (step S1410), and terminates the series of processes. After executing the settlement process, the settlement device 30 switches from the settlement in progress status S6 to the standby status S1.

[0149] As described above, the settlement device 30 according to Modification 1 accepts a declaration of the start of additional registration in the registration device 20 and makes additional registration impossible by receiving a termination command from the registration device 20. This allows the payment device 30 to switch to the "adding registration in progress" status S4 without the customer having to press the add registration button 713, as in the embodiment. Therefore, even customers unfamiliar with operating the payment device 30 can easily perform the additional registration process.

[0150] Furthermore, as described above, the settlement device 30 according to Modification 1 receives a declaration of termination of additional registration from the registration device 20 and, upon receiving a termination command from the registration device 20, makes additional registration impossible. This allows the payment device 30 to be switched to a status that prohibits additional registration, under the visual confirmation of a store employee. Therefore, even if a customer unintentionally brings the product code close to the customer-side scanner unit 306 during bagging or other operations after additional registration has been completed, the product will not be registered. Furthermore, the system can be configured so that products are not registered when customers other than the original customer use the payment device 30.

[0151] (Modification 2: Control of the change dispenser 309 when a start command is received) Next, we will describe a second modification. In this second modification, we will describe the control of the change dispenser 309 when the settlement device 30 receives a start command. The sales data processing system 1 according to Modification 2 is configured such that the settlement device 30 does not accept the selection of the payment type, and that cash payment is made. For example, the selection of the payment type may be made in the registration device 20, and information indicating the payment type may be transmitted to the settlement device 30 along with the registration data. Alternatively, the settlement device 30 may only accept cash payment as a payment type.

[0152] The settlement device 30 includes an instruction unit. The instruction unit gives instructions to the change dispenser 309 regarding the start or stop of cash deposits and withdrawals. The change dispenser 309 includes a drive unit and a transport unit, and stores the cash inserted into the input slot in a predetermined storage position. The instruction unit receives registration data and gives the change dispenser 309 an instruction to start cash deposits and withdrawals. In response to the start instruction, the change dispenser 309 operates the drive unit and the transport unit.

[0153] (Instruction to suspend deposits and withdrawals) Furthermore, the instruction unit issues a stop command for deposits and withdrawals when the receiving unit 911 receives a start command. In other words, the instruction unit issues a stop command for deposits and withdrawals when it switches to the status S4 of adding registrations. The stop command causes the change dispenser 309 to stop its drive unit and transport unit.

[0154] (Instruction to start / stop again) The instruction unit, upon receiving a termination command from the receiving unit 911, again issues an instruction to the change dispenser 309 to start deposits and withdrawals. In other words, the instruction unit issues an instruction to start deposits and withdrawals when it switches to an additional registration prohibited status (excluding standby status S1).

[0155] (An example of additional registration processing performed by the settlement device 30 according to Modification 2) Figure 15 is a flowchart showing an example of the additional registration process performed by the settlement device 30 according to Modification 2. As shown in Figure 15, the settlement device 30 determines whether or not it has received registration data from the registration device 20 (step S1501). The settlement device 30 waits until it receives registration data (step S1501: NO), and once it receives registration data (step S1501: YES), it issues an activation command to the change dispenser 309 (step S1502).

[0156] The settlement device 30 then determines whether or not it has received a start command from the registration device 20 (step S1503). If it does not receive a start command (step S1503: NO), the settlement device 30 proceeds to step S1510. On the other hand, if it does receive a start command (step S1503: YES), the settlement device 30 issues a stop command to the change dispenser 309 (step S1504) and displays the additional registration screen 720 shown in Figure 7(B) (step S1505).

[0157] Furthermore, the settlement device 30 may notify the customer not to insert cash while the change dispenser 309 is stopped. Specifically, the settlement device 30 may, for example, display or voice a message such as "Please do not insert cash" on the additional registration screen 720.

[0158] The payment device 30 then determines whether the customer-side scanner unit 306 has scanned the product code on the shopping bag (step S1506). If the product code has not been scanned (step S1506: NO), the payment device 30 proceeds to step S1508. On the other hand, if the product code has been scanned (step S1506: YES), the payment device 30 registers the product (shopping bag) as an additional item (step S1507).

[0159] The settlement device 30 then determines whether or not it has received a termination command (step S1508). If it does not receive a termination command (step S1508: NO), the settlement device 30 returns to step S1506. On the other hand, if it does receive a termination command (step S1508: YES), it again instructs the change dispenser 309 to start deposits and withdrawals (step S1509).

[0160] The settlement device 30 then determines whether or not cash equal to or greater than the settlement amount has been inserted (step S1510). If cash equal to or greater than the settlement amount has not been inserted (step S1510: NO), the settlement device 30 returns to step S1503. If cash equal to or greater than the settlement amount has been inserted (step S1510: YES), the settlement device 30 activates the settlement completion button to accept completion of the settlement and accepts the press of the button (step S1511). Then, the settlement device 30 dispenses the change if there is any, issues a receipt (step S1512), and ends the series of processes.

[0161] As described above, the settlement device 30 according to the modified example 2 issues a start command to the change dispenser 309 upon receiving registration data, and issues a stop command for deposits and withdrawals upon receiving a start command. This makes it possible to prohibit cash deposits during the "Additional Registration in Progress" status S4 and the "Termination Request" status S5 (when the total amount is uncertain), as the total amount is not yet determined due to the additional registration. Therefore, settlement can be carried out properly.

[0162] Furthermore, the settlement device 30 according to the modified example 2 issues a command to start deposits and withdrawals again upon receiving a termination command. This allows the system to accept cash payments and process transactions after the total amount, including the price of the newly registered item (plastic bag), has been finalized. Therefore, transactions can be processed properly.

[0163] (Variation 3: An example where additional registration is done with a button operation) Next, we will describe Modification 3. In the embodiment described above, we described an example in which the additional registration is a scan registration and the additional registration screen 720 in Figure 7(B) is displayed. In Modification 3, we will describe an example in which the additional registration is a button registration associated with button operation, instead of or in addition to such an example.

[0164] Figure 16 shows an example of the additional registration screen 1600 according to Modification 3. The additional registration screen 1600 is a screen that is displayed in place of or in addition to the additional registration screen 720 in Figure 7(B). As shown in Figure 16, the additional registration screen 1600 includes an operation guide 1601, a registration field 1602, a total amount field 1603, an equipment selection button 1604, and a registration completion button 1605.

[0165] Operation guide 1601 is a notification prompting the user to enter the number of shopping bags and press the registration button. Registration field 1602 is a field for specifying the quantity and selling price for each product (each shopping bag) that differs in size and price. Registration field 1602 includes registration buttons 1602a (increase / decrease buttons) corresponding to each product. The payment device 30 (additional registration unit 914) accepts the input of the quantity for each product when the registration button 1602a is pressed and registers the additional product. The total amount column 1603 shows the sum of the amounts of the newly registered items and the amounts of the items registered by the registration device 20.

[0166] The equipment selection button 1604 is a button used when adding cutlery (spoons, forks, chopsticks, etc.) to a store that charges for cutlery. When the equipment selection button 1604 is selected, the payment device 30 displays registration buttons corresponding to spoons, forks, and chopsticks, and the additional items are registered by pressing the respective registration buttons. Depending on the screen size, font size, and layout of the customer-side display unit 305, cutlery may also be made available for additional registration (selection) on the additional registration screen 1600. In this case, the equipment selection button 1604 does not need to be displayed on the additional registration screen 1600. The registration completion button 1605 is a button that accepts the completion of an additional registration. When the registration completion button 1605 is pressed on the additional registration screen 1600, the user transitions to the registration list screen 730 shown in Figure 7(C).

[0167] Furthermore, the additional registration screen 1600 may be configured to display all products, including those registered by the registration device 20. Specifically, the additional registration screen 1600 may display the registration list 731 shown in Figure 7(C). In this case, when the registration completion button 1605 is pressed, the settlement device 30 does not need to transition to the registration list screen 730, but instead should transition to the payment type selection screen 710 (Figure 7(A)).

[0168] According to Modification 3, products without barcodes can also be added for registration. Furthermore, even in the case of a payment device 30 that does not have a customer-side scanner unit 306, additional registration is possible. In addition, the display in the registration field 1602 allows customers to easily identify products that can be added for registration. Moreover, it is possible to restrict additional registration to only the products displayed in the registration field 1602 (shopping bags and cutlery), and prohibit additional registration of other products.

[0169] (Modification 4: Other conditions for ending the S4 status during additional registration) Next, we will describe Modification 4. In the embodiments described above and Modification 1, we described an example in which the trigger for ending the "additional registration in progress" status S4 is a declaration of completion of additional registration by the customer or store clerk. In Modification 4, we will describe other triggers (conditions) for ending the "additional registration in progress" status S4, either as an alternative to or in addition to such an example.

[0170] Below is an example of other triggers (conditions) that can terminate the S4 status for additional registration. • Conditions related to the start of settlement. For example, in the case of cash payment, when cash is inserted. In the case of credit card payment, when the credit card is inserted into the payment terminal 308. Conditions related to the completion of settlement. For example, when receipt data is generated, when the receipt is printed, when the receipt is output, when change is given in cash payments, when the change is removed, when contactless payment is completed in electronic money payments, and when the authorization number is received in credit card payments. • Conditions related to the completion of payment. For example, when the customer leaves. The customer's departure can be detected, for example, by camera 316. • Conditions related to errors. For example, when an error notification is issued in the case of non-payment (when payment is not completed even after a predetermined time has elapsed since the start of payment).

[0171] The settlement device 30 requests the registration device 20 to terminate the additional registration when any of the other triggers (conditions) described above occur. In response, the registration device 20 accepts permission to terminate the additional registration and sends a termination command to the settlement device 30. Upon receiving the termination command, the settlement device 30 switches to an additional registration prohibited status.

[0172] Even if the modification shown in Modification 4 is performed, it is possible to enable additional registration in the settlement device 30 only for a specific period after the registration data has been sent (the period from the receipt of the start command to the receipt of the end command).

[0173] (Variation 5: An example in which the additional registration screen 720 is not displayed in the additional registration status S4) Next, Modification 5 will be described. In the embodiment described above, an example was described in which the additional registration screen 720 shown in Figure 7(B) is displayed in the additional registration status S4. In Modification 5, instead of or in addition to such an example, an example will be described in which the settlement device 30 does not display the additional registration screen 720 in the additional registration status S4.

[0174] In Modification 5, in the status S4 of "Adding Registration in Progress," scanning and registering products (shopping bags) is enabled, similar to the embodiment. For example, when the add registration button 713 is pressed on the payment type selection screen 710, the payment device 30 maintains the payment type selection screen 710. The payment device 30 may also include notifications, marks, and guidance images on the payment type selection screen 710 to prompt scanning of additional products.

[0175] Furthermore, as in the modified example 1 above, if the system is configured to accept a declaration from a store employee to start additional registration, the employee should, when performing the operation related to the declaration, prompt the customer at the payment device 30 to scan the additional items. This allows the customer to understand that they can register the shopping bag even if the additional registration screen 720 is not displayed.

[0176] When an additional item is registered, the payment device 30 emits a scanning sound and transitions to the registration list screen 730 shown in Figure 7(C). This allows the customer to confirm that an additional item has been registered and to verify the registered item.

[0177] According to Modification 5, the additional registration screen 720 is not displayed during additional registration, thus simplifying the screen transitions related to additional registration. Furthermore, since it is not necessary for the customer to press the registration completion button 723 after completing additional registration, the operation related to additional registration can be simplified.

[0178] (Variation 6: Example of a start command being sent from another device) Next, Modification 6 will be described. In the embodiments described above, an example was given in which the start command and end command are transmitted from the registration device 20. Modification 6 will describe an example in which the start command and end command are transmitted from another device, either instead of or in addition to such an example.

[0179] In Modification 6, the other devices are, for example, the following devices. Transaction status management device 11. • A portable terminal carried by store employees. • Another registration device 20, different from the registration device 20 that transmitted the registration data. The procedure for sending start or end commands from other devices is described below.

[0180] (In the case of the sales data processing system 1 according to the embodiment) In the sales data processing system 1 of this embodiment, the other device receives start request information from the settlement device 30 indicating a request to start additional registration. Upon receiving the start request information, the other device receives permission from the store clerk to start additional registration and sends a start command to the settlement device 30. Regarding the sending of an end command, the other device receives end request information from the settlement device 30 to end the additional registration. Upon receiving the end request information, the other device receives permission from the store clerk to end the additional registration and sends an end command to the settlement device 30.

[0181] (In the case of the sales data processing system 1 according to the above modified example 1) In the sales data processing system 1 according to the above modified example 1, when a customer requests additional registration, the store clerk operating the other device performs an operation to declare the start of additional registration. Upon receiving the declaration from the store clerk, the other device sends a start command to the payment device 30. Regarding the transmission of the end command, when the store clerk operating the other device confirms that the registration of additional items by the customer is complete, the other device operates the other device to receive the declaration that additional registration has ended. Upon receiving this, the other device sends an end command to the payment device 30.

[0182] According to Modification 6, in addition to or instead of the employee operating the registration device 20, an employee operating another device can perform operations related to sending start or end commands. This prevents the employee operating the registration device 20 from having to perform interruption work related to additional registration while registering the next customer. Therefore, transactions can be conducted efficiently.

[0183] (Variation 7: Example of additional registration in a fully self-service registration and payment device) Next, Modification 7 will be described. In the embodiment described above, an example of additional registration being performed in a self-service payment device 30 was explained. Modification 7 will describe an example of additional registration being performed in a fully self-service registration payment device, either as an alternative to or in addition to such an example.

[0184] In Modification 7, the sales data processing system 1 includes a registration and settlement device. The registration and settlement device registers products and settles the payment at the customer's discretion. Once the customer has finished registering the products, they press the settlement start button (subtotal button). Upon receiving confirmation of the settlement start button press, the registration and settlement device displays a payment type selection screen. At this stage, if the customer realizes they have forgotten to purchase a shopping bag, the operator performs an operation to declare the start of additional registration.

[0185] The operators include customers and store staff. If the system is to accept declarations from customers to start additional registration, for example, the registration and settlement device can accept the press of the additional registration button 713 on the payment type selection screen 710 shown in Figure 7(A). Alternatively, if the system is to accept declarations from store staff to start additional registration, another device as shown in Modification Example 6 above may accept such declarations, or if an operation unit for store staff (e.g., a touch panel display) is provided on the back side of the registration and settlement device, that operation unit may accept such declarations.

[0186] Furthermore, the employee's operation related to sending the termination command (declaration of termination of additional registration, or permission for termination of additional registration) may also be received by other devices as shown in Modification Example 6 above, or, if an operation unit for the employee (e.g., a touch panel display) is provided on the back side of the registration and settlement device, that operation unit may receive the command.

[0187] According to Modification 7, in a fully self-service registration and settlement device, an operator can quickly and easily perform additional registrations without requiring store staff to enter store staff codes or passwords, nor without requiring a transition to maintenance mode. Therefore, transactions can be conducted efficiently in the sales data processing system 1 equipped with a fully self-service registration and settlement device.

[0188] (Modification 8: Example in which the registration device 20 is equipped with a sub-screen) Next, Modification 8 will be described. Modification 8 describes an example in which the registration device 20 is equipped with a sub-screen. In Modification 8, the employee-side display unit 210 includes a main screen and multiple sub-screens. The main screen displays the product registration screen. The sub-screens display various screens related to additional registration. The various screens related to additional registration are screens that accept permission or declarations to start (or end) additional registration. Alternatively, an additional registration screen 1600 (Figure 16) may be displayed on the sub-screen, allowing the employee to perform additional registration.

[0189] According to Modification 8, the registration device 20 is equipped with a sub-screen, which improves the operability of various operations on the registration device 20 and makes it easier for store staff to grasp various situations.

[0190] (Modification 9: Another example relating to permission to start (or end) additional registration in the registration device 20) Next, Modification 9 will be described. In the embodiment described above, an example was given in which the payment device designation button 817 (Figure 8(A)) has three functions (designation of payment device 30, permission to start additional registration, and permission to end additional registration). Modification 9 will describe an example in which a button is displayed for each of these three functions. In Modification 9, the payment device designation button 817 has only the function of accepting the designation of a payment device.

[0191] (Permission to start additional registrations) In Modification 9, the registration device 20 displays a start permission button to accept permission to start additional registration. The start permission button may be displayed in advance on the staff-side display unit 210 as a preset key. However, if the status of the payment device 30 is not start request status S3 (not unselected status S2 in Modification 1), pressing the start permission button should be disabled. Alternatively, the start permission button may be displayed on the staff-side display unit 210 only when the status of the payment device 30 is start request status S3 (unselected status S2 in Modification 1). The registration device 20 accepts permission to start additional registration by receiving a press of the start permission button from the staff. Even in this way, the registration device 20 can send a start command to the payment device 30.

[0192] Furthermore, when the settlement device designation button 817 is pressed, the registration device 20 may display a small screen that accepts the selection of either a transition to a screen showing the status of the settlement device (for example, a screen showing the balance of the change dispenser 309 or a screen showing the payment status during settlement) or permission to start additional registration. In this case, the reception unit 904 may accept permission to start additional registration on the small screen.

[0193] Furthermore, permission to start additional registration is not limited to pressing the payment device designation button 817. For example, permission may be granted by displaying a separate "Start Additional Registration" button on the registration screen 810 (Figure 8(A)), and pressing this button may allow the user to specify the number of the payment device 30 to be registered. In this case, the "Start Additional Registration" button corresponding to payment devices 30 whose status is not "Start Request Status S3" may be hidden or grayed out to prevent the user from specifying such payment devices 30. Permission to start additional registration may also be granted by a combination of pressing the payment device designation button 817 and pressing the "Start Additional Registration" button and specifying the number.

[0194] (Permission to terminate additional registrations) Similarly, the registration device 20 displays an exit permission button that accepts permission to start additional registration. The exit permission button may be displayed in advance on the staff-side display unit 210 as a preset key. However, if the status of the payment device 30 is not the exit request status S5 (in Modification 1, not the additional registration in progress status S4), pressing the exit permission button can be disabled. Alternatively, the exit permission button may be displayed on the staff-side display unit 210 only when the status of the payment device 30 is the exit request status S5 (in Modification 1, when the additional registration in progress status S4). The registration device 20 accepts permission to end additional registration by receiving a press of the exit permission button from the staff. Even in this way, the registration device 20 can send an exit command to the payment device 30.

[0195] Furthermore, permission to terminate additional registration is not limited to pressing the payment device designation button 817. For example, permission to terminate additional registration may be granted by displaying a separate "terminate additional registration" button on the registration screen 810 (Figure 8(A)), and pressing this button may allow the user to specify the number of the payment device 30 to be terminated. In this case, the "terminate additional registration" button corresponding to payment devices 30 whose status is not "in progress of additional registration" (S4) may be hidden or grayed out to prevent the user from specifying such payment devices 30. Alternatively, permission to terminate additional registration may be granted by a combination of pressing the payment device designation button 817 and pressing the "terminate additional registration" button and specifying the number.

[0196] (Modification 10: An example of enabling the transmission of permission commands under predetermined conditions) Next, Modification 10 will be described. Modification 10 describes an example in which an authorization command (for example, a start command) can be sent under predetermined conditions. The predetermined conditions are, for example, a time period. This time period is set, for example, in the schedule setting, with a start time and an end time. The start time and end time can be the opening time and closing time, or any time within business hours. As a result, the registration device 20 can send authorization commands based on the start time and end time set in the schedule setting. Therefore, additional registration can be enabled during the time period set in the schedule setting, while additional registration can be disabled during time periods other than that time period.

[0197] Furthermore, the specified conditions may be defined as membership ranks. Membership ranks are determined, for example, based on factors such as the purchase amount or number of visits within a certain period. Membership ranks are associated with member identification information. This allows the registration device 20 to send permission commands according to the membership rank associated with the member identification information. Therefore, it is possible to enable additional registration for customers whose membership rank is above a certain rank, while making it impossible to enable additional registration for customers whose membership rank is below a certain rank.

[0198] The following appendices 1 to 3 are disclosed as payment devices related to the above. (Note 1) A receiving means for receiving a command to grant permission for additional registration, An additional registration method that allows the registration of specific products only when permitted, Equipped with, The receiving means is a settlement device that receives the permission command under predetermined conditions.

[0199] (Note 2) The aforementioned predetermined conditions are conditions based on the start time and end time set by the schedule setting. The payment device described in Appendix 1.

[0200] (Note 3) The aforementioned predetermined conditions are conditions based on the membership rank associated with the membership identification information. The payment device described in Appendix 1 or 2.

[0201] (Variation 11: Example where the registration device 20 sends a settlement authorization command) Next, we will describe Modification 11. In the embodiment described above, we described an example in which the registration device 20 sends two commands to the settlement device 30: a start command (registration permission command) and an end command. In Modification 11, instead of these two commands, we will describe an example in which the registration device 20 sends a settlement permission command to the settlement device 30 indicating permission for settlement.

[0202] In the above-described embodiment, the payment device 30 receives a press of the additional registration button 713 (Figure 7(A)) from the operator, sends a request to start additional registration to the registration device 20, and when the store clerk approves it in the registration device 20, "additional registration" is permitted and a "start command" is sent. Modification 11 is a configuration in which, after additional registration is performed in the payment device 30, a notification that additional registration has been completed is sent to the registration device 20, and when the store clerk approves it in the registration device 20, "start of payment processing" is permitted and a "payment permission command (an example of a permission command)" is sent.

[0203] To explain in more detail, in Modification 11, when the settlement device 30 receives a declaration to start additional registration (step S605 in Figure 6), it switches to the status S4 of "additional registration in progress" and enables additional registration. At this time, the settlement device 30 does not request the registration device 20 to start additional registration. Then, when it receives a declaration to end additional registration (step S611 in Figure 6), it requests the registration device 20 to start settlement (end of additional registration). When the registration device 20 receives a request to start settlement, it receives permission to start settlement (approval of additional registration) from the store clerk and sends a settlement permission command to the settlement device 30. When the settlement device 30 receives the settlement permission command, settlement becomes possible.

[0204] The entity that grants permission for settlement is the store clerk, as in the embodiment described above. Furthermore, the device that receives permission to start settlement and the device that transmits the settlement permission command are not limited to the registration device 20, but may be other devices (for example, the transaction status management device 11).

[0205] The following Appendix 4 is disclosed as a settlement device related to the above. (Note 4) A means of accepting declarations for additional registrations, The aforementioned declaration acceptance means accepts the aforementioned declaration, and an additional registration means is provided to register additional information for specific products only (cancellation, quantity changes, etc. are not permitted), A receiving means that receives (acquires) an authorization command for settling the total amount including the products added by the aforementioned additional registration means, The receiving means receives the permission command and performs settlement on the total amount, A payment device equipped with the following features.

[0206] (Variation 12: Another example of additional registration) Next, Modification 12 will be described. Modification 12 describes another example of additional registration. In Modification 12, the payment device 30 receives a declaration indicating the start of additional registration. Upon receiving the declaration, the payment device 30 outputs information to the registration device 20 indicating this. Upon receiving this information, the registration device 20 displays a message indicating that the declaration indicating the start of additional registration has been received at the payment device 30. This allows, for example, a store clerk to move to the payment device 30 and register additional shopping bags at the payment device 30. Alternatively, the registration device 20 may retrieve registration data from the payment device 30 to enable additional registration of shopping bags. In this way, customers can also register shopping bags they forgot to buy.

[0207] (Variation 13: Output format of receipt for transactions with additional registrations) Next, we will describe Modification 13. Modification 13 describes the output method of a receipt for a transaction with additional registrations. In Modification 13, the settlement device 30 prints the unit number of the registration device 20 and the unit number of the settlement device 30 when printing a paper receipt. The receipt is printed in a way that distinguishes between the items registered by the registration device 20 and the items settled by the settlement device 30. If there are additional registered items, the items registered by the registration device 20 and the items settled by the settlement device 30 will be different. In this case, the additional registered items may be printed in a way that distinguishes them from other items.

[0208] Additionally, a barcode for returns will be printed on the receipt. The return barcode will include, for example, the "transaction number" + "date" + "settlement device unit number or registered device unit number".

[0209] Furthermore, if additional registration is performed, the settlement device 30 may print the serial number of the settlement device 30 (its own device) on the receipt as the device that performed the final registration operation, and may also print the serial number of its own device in the return barcode. Also, if the product is registered using only the registration device 20 (no additional registration), the settlement device 30 may print the serial number of the registration device 20 on the receipt, and may also print the serial number of the registration device 20 in the return barcode. In addition, the settlement device 30 also stores the information to be printed on the receipt, such as the serial number of the registration device 20 and the serial number of the settlement device 30, in the transaction history (journal) that the store clerk will check.

[0210] The following Appendix 5 is disclosed as a settlement device related to the above. (Note 5) A settlement device equipped with an output means that, when an additional registration is made via an additional registration means, outputs the device's identification number associated with the transaction information as part of the transaction history, and when no additional registration is made, outputs the registration device's identification number associated with the transaction information.

[0211] (Modification 14: An example where the customer-side display unit 305 of the payment device 30 is a large screen) Next, Modification 14 will be described. Modification 14 describes an example where the customer-side display unit 305 of the payment device 30 is a large screen. The customer-side display unit 305 of the payment device 30 in Modification 14 is assumed to be large enough for the customer to recognize even when displaying two screens as shown in Figures 7(A) to (D). The payment device 30 displays the payment type selection screen 710 (Figure 7(A)) and the additional registration screen 720 (Figure 7(B)) side by side on the customer-side display unit 305. In this case, the additional registration button 713 is not displayed. With this display, as shown in Modification 11 above, the payment device 30 can enable additional registration even without receiving a registration permission command (start command). Furthermore, the payment device 30 can enable payment by receiving a declaration of completion of additional registration, thereby receiving a payment permission command (Modification 11 above) from the registration device 20.

[0212] The following is a summary of the embodiments. [Title of Invention] Settlement device, system, and program [Technical Field] The present invention relates to a settlement device, system, and program. [Background technology]

[0213] In recent years, systems that include a registration device operated by a store employee to register products and a payment device operated by the customer to complete the transaction have become increasingly popular (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2020-181617 [Overview of the prefecture] [Problems the invention aims to solve] However, conventional technology had the problem that it could not always conduct transactions efficiently. This invention has been made in view of these circumstances, and its purpose is to provide a technology that enables efficient transactions.

[0214] [Means for solving the problem] (1) In order to solve the above-mentioned problems, a settlement device according to one aspect of the present invention is A payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store clerk, comprising: a receiving means that receives an authorization command from the registration device that authorizes additional registration after receiving the registration data; an additional registration means that registers additional products upon receiving the authorization command; and a payment means that performs payment based on the products additionally registered by the additional registration means and the products indicated by the registration data. With the above configuration, customers can easily add items themselves at the payment device 30 without having to retrieve registered data. This also prevents interference with the registration operations of store staff at the registration device 20. Furthermore, even if a store staff member is called to the payment device 30, they can easily add items without having to enter a staff code or password, or even switch to maintenance mode (a mode exclusively for staff). In addition, even staff members who do not have login privileges to the payment device 30, such as part-timers, temporary staff, or staff who are not cashiers, can easily add items. Therefore, it is possible to prevent delays in the registration process for the next customer or keep customers who wish to add items waiting when adding items. Thus, transactions can be conducted efficiently.

[0215] (2) In the configuration of (1) above, the receiving means may receive an termination command from the registration device to terminate the additional registration, and the additional registration means may make it impossible to perform additional registration when the receiving means receives the termination command. According to the above configuration, the payment device 30 can be set to a status that prohibits additional registration. Therefore, even if a customer unintentionally brings the product code close to the customer-side scanner unit 306 during bagging or other operations after additional registration has been completed, the product will not be registered. Furthermore, the system can be configured so that products are not registered when customers other than the original customer use the payment device 30. Furthermore, the settlement device 30 can be prevented from switching to the "additional registration prohibited" status based on its own judgment. In other words, the settlement device 30 can switch to the "additional registration prohibited" status under the management of the registration device 20.

[0216] (3) In the configuration of (2) above, the settlement means may be configured to enable settlement when the receiving means receives the termination command. With the above configuration, the settlement device 30 can be prevented from performing settlement processing on its own initiative. In other words, the settlement device 30 can be made to start settlement processing under the management of the registration device 20.

[0217] (4) In the configuration of (2) or (3) above, the receiving means may include a declaration receiving means that receives a declaration indicating the termination of additional registration by the additional registration means, and a requesting means that, upon receiving the declaration by the declaration receiving means, requests the registration device to terminate the additional registration, wherein the receiving means receives the termination command from the registration device based on the requesting means. According to the above configuration, when the additional registration is completed, the customer can declare that the additional registration has been completed, so the payment device 30 can be set to the "additional registration prohibited" status without requiring visual confirmation by a store employee regarding the additional registration.

[0218] (5) In the configuration of (4) above, the declaration acceptance means may consider the selection of any of the multiple payment types as acceptance of the declaration. With the above configuration, it is possible to accept declarations of termination of additional registration without providing a dedicated button for accepting such declarations or without accepting the press of such a dedicated button. Therefore, the operation for accepting declarations of termination of additional registration can be simplified.

[0219] (6) In the configuration of (1) or (2) above, the additional registration means may perform additional product registration according to the status indicating the state of its own device from the time the receiving means receives the registration data until the settlement means completes the settlement. With the above configuration, the registration device 20 can register additional products before settlement begins in the settlement device 30. Therefore, the newly registered products and the products registered by the registration device 20 can be settled together. Thus, settlement can be performed efficiently.

[0220] In addition, in the configuration of (2) or (3) above, the receiving means may be provided with an instruction means that, upon receiving the registration data, issues an instruction to start the deposit and withdrawal of cash to a change machine that deposits and withdraws cash, and the instruction means may issue a stop instruction to stop the deposit and withdrawal of cash upon receiving the start command from the receiving means, and issue another instruction to start the deposit and withdrawal of cash upon receiving the end command from the receiving means, which prohibits the additional registration. With the above configuration, cash payments can be prohibited during the "additional registration in progress" status S4 and the "completion request" status S5 (total amount uncertain) when the total amount is not yet determined due to the additional registration. Furthermore, cash payments can be accepted and settlement can be performed after the total amount, including the price of the additionally registered item (plastic bag), has been determined. Therefore, settlement can be performed appropriately.

[0221] (7) In order to solve the above-mentioned problems, another aspect of the present invention is a payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store employee, and is characterized by comprising: a request means for requesting permission to add products to the registration data; and a payment means that, when permission for additional product registration is approved in response to the request means, performs payment based on the additionally registered products and the products indicated by the registration data.

[0222] (8) In order to solve the above-mentioned problems, another aspect of the present invention is a payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store employee, and is characterized by comprising: a declaration receiving means that receives a declaration indicating the start of additional registration for the registration data; and an output means that, upon receiving the declaration by the declaration receiving means, outputs information to the registration device indicating that fact. According to the above configuration, customers can register additional shopping bags they forgot to buy.

[0223] (9) In order to solve the above-mentioned problems, another aspect of the present invention is a system comprising: a registration device operated by a store clerk to generate registration data; and a settlement device that performs settlement by customer operation based on the registration data generated by the registration device, wherein the settlement device comprises: a receiving means that receives a permission command from the registration device to grant permission for additional registration after receiving the registration data; an additional registration means that performs additional product registration when the receiving means receives the permission command; and a settlement means that performs settlement based on the product additionally registered by the additional registration means and the product indicated by the registration data. With the above configuration, customers can easily add items themselves at the payment device 30 without having to retrieve registered data. This also prevents interference with the registration operations of store staff at the registration device 20. Furthermore, even if a store staff member is called to the payment device 30, they can easily add items without having to enter a staff code or password, or even switch to maintenance mode (a mode exclusively for staff). In addition, even staff members who do not have login privileges to the payment device 30, such as part-timers, temporary staff, or staff who are not cashiers, can easily add items. Therefore, it is possible to prevent delays in the registration process for the next customer or keep customers who wish to add items waiting when adding items. Thus, transactions can be conducted efficiently.

[0224] (9) In order to solve the above-mentioned problems, a program in another aspect of the present invention is: A program that causes a computer to function as a payment device that performs payment by customer operation based on registration data generated by a registration device operated by a store employee, the program characterized in that the computer functions as a receiving means that receives an authorization command from the registration device that authorizes additional registration after receiving the registration data, an additional registration means that performs additional product registration when the receiving means receives the authorization command, and a payment means that performs payment based on the products additionally registered by the additional registration means and the products indicated by the registration data. With the above configuration, customers can easily add items themselves at the payment device 30 without having to retrieve registered data. This also prevents interference with the registration operations of store staff at the registration device 20. Furthermore, even if a store staff member is called to the payment device 30, they can easily add items without having to enter a staff code or password, or even switch to maintenance mode (a mode exclusively for staff). In addition, even staff members who do not have login privileges to the payment device 30, such as part-timers, temporary staff, or staff who are not cashiers, can easily add items. Therefore, it is possible to prevent delays in the registration process for the next customer or keep customers who wish to add items waiting when adding items. Thus, transactions can be conducted efficiently.

[0225] Furthermore, all or part of the functions (input / output, storage, processing (including decision-making)) of the registration device 20 described above may be implemented in a device other than the one described as the entity executing those functions.

[0226] Specifically, the above description described a configuration in which the registration device 20 comprises the following functional units: a registration unit 901, a transmission unit 902, a reception unit 903, and an acceptance unit 904. The settlement device 30 was also described as comprising the following functional units: a reception unit 911, a request unit 912, a transmission unit 913, an additional registration unit 914, a settlement unit 915, a declaration acceptance unit 916, and a status management unit 917. 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. Furthermore, the computer devices equipped with these functional units are not limited to multiple devices; there may be only one.

[0227] Specifically, for example, instead of the registration device 20, the store controller 10 or an external server device may receive a start command from the registration device 20, register additional products, and execute a settlement process based on the newly registered products and the registration data.

[0228] In relation to the above, the registration device 20 and the settlement device 30 may function as so-called thin clients specializing in the input / output interface portion for product registration and settlement. That is, the registration device 20 may receive various inputs (operation by the operator, detection by a device such as a scanner), send the input information (operation information, scan information, etc.) to the cloud server, receive the processing results from the cloud server based on the input information (updated screen information, device control information, etc.), and perform various outputs (display on the display unit, device control).

[0229] Note that a program for realizing the sales data processing system 1, the registration device 20, and the settlement device 30 described above may be recorded on a computer-readable recording medium, and the program may be read into a computer system and executed. Here, the "computer system" is assumed to include hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a USB (Universal Serial Bus) flash memory, an SSD (Solid State Drive), a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable recording medium" also includes a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and holds the program for a certain period of time. Also, the above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Also, the above program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the functions described above in combination with a program already recorded in a computer system.

Explanation of Signs

[0230] 1...Sales data processing system, 10...Store controller, 20...Registration device, 30...Settlement device, 301...CPU, 302...ROM, 303...RAM, 304...Hard disk, 305...Customer-side display unit, 306...Customer-side scanner unit, 308...Payment terminal, 309...Change dispenser, 310...Employee-side display unit, 311...Key operation unit, 312...Employee-side scanner unit, 315...Communication unit, 316...Camera, 901...Registration unit, 902...Transmission unit, 903...Receiver unit, 904...Reception unit, 911...Receiver unit, 912...Request unit, 913...Transmission unit, 914...Additional registration unit, 915...Settlement unit, 916...Declaration reception unit, 917 Status management unit

Claims

1. A payment device that performs payment based on registration data generated by a registration device operated by a store employee, and is operated by the customer. A receiving means that receives a permission command from the registration device after receiving the registration data, which grants permission for additional registration. The receiving means receives the permission command and performs additional product registration, A settlement means that performs settlement based on the products registered by the aforementioned additional registration means and the products indicated by the registration data, A payment processing device characterized by being equipped with the following features.

2. The receiving means receives an termination command from the registration device to terminate the additional registration, The additional registration means prevents additional registration when the receiving means receives the termination command. The settlement device according to feature 1.

3. The settlement means enables settlement when the receiving means receives the termination command. The settlement device according to feature 2.

4. A declaration receiving means that receives a declaration indicating the completion of additional registration by the aforementioned additional registration means, Upon receiving the declaration, the declaration receiving means requests the registration device to complete the additional registration, Equipped with, The receiving means receives the termination command from the registration device based on the request made by the requesting means. The settlement device according to claim 2 or 3.

5. The declaration acceptance means considers the selection of any of the multiple payment types as acceptance of the declaration. The settlement device according to feature 4.

6. The additional registration means performs additional product registration according to the status indicating the state of the device from the time the receiving means receives the registration data until the settlement means completes the settlement. The settlement device according to feature 1 or 2.

7. A payment device that performs payment based on registration data generated by a registration device operated by a store employee, and is operated by the customer. A request means for requesting permission to add products to the aforementioned registration data, In response to the aforementioned request means, if permission for the additional registration of goods is approved, a settlement means is provided to settle the payment based on the newly registered goods and the goods indicated in the registration data. A payment processing device characterized by being equipped with the following features.

8. A payment device that performs payment based on registration data generated by a registration device operated by a store employee, and is operated by the customer. A declaration receiving means for receiving a declaration indicating the start of additional registration for the aforementioned registration data, The declaration receiving means outputs information indicating that the declaration has been received to the registration device, A payment processing device characterized by being equipped with the following features.

9. A system including a registration device operated by a store employee to generate registration data, and a payment device that performs payment based on the registration data generated by the registration device, operated by the customer, The settlement device is, A receiving means that receives a permission command from the registration device after receiving the registration data, which grants permission for additional registration. The receiving means receives the permission command and performs additional product registration, A settlement means that performs settlement based on the products registered by the aforementioned additional registration means and the products indicated by the registration data, A system characterized by comprising the following features.

10. A program that makes a computer function as a payment device that processes payments based on registration data generated by a registration device operated by a store employee, and based on customer operations. The aforementioned computer, A receiving means that, after receiving the aforementioned registration data, receives a permission command from the registration device to grant permission for additional registration. Upon receiving the permission command, the receiving means performs additional registration of products. A settlement means that performs settlement based on the products registered by the aforementioned additional registration means and the products indicated by the registration data, A program characterized by being designed to function as such.

Images