Sales data processing device and program

Abstract

To conduct transactions in a favorable manner. [Solution] The sales data processing device comprises a customer-side reading means, a store employee-side reading means, a control means, and a payment execution means. The customer-side reading means is provided on the customer side and reads the symbol code used for payment. The store employee-side reading means is provided on the store employee side and reads the symbol code. The control means controls the reading of the symbol code by the customer-side reading means and the reading of the symbol code by the store employee-side reading means to be in an enabled reading state during payment. The payment execution means executes the payment based on the symbol code read by the customer-side reading means or the store employee-side reading means in the enabled reading state.

Description

Technical Field

[0001] The present invention relates to a sales data processing apparatus and a program.

Background Art

[0002] In stores such as supermarkets, various payment types are used in addition to cash and credit cards during checkout. For example, code payment is used, where payment is made by reading a payment code displayed on a mobile terminal or the like (see, for example, Patent Document 1 below).

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, when there are customers who are not familiar with the operations related to payment, it may take time for checkout, which may prevent quick transactions and may make it impossible to conduct suitable transactions.

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

Means for Solving the Problems

[0006] To solve the above-mentioned problems, a sales data processing device according to one aspect of the present invention is a sales data processing device characterized by comprising: a customer-side reading means provided on the customer side for reading a symbol code used for payment; a store employee-side reading means provided on the store employee side for reading the symbol code; a control means for controlling the reading of the symbol code by the customer-side reading means and the reading of the symbol code by the store employee-side reading means to an effective reading state in the payment; and a settlement execution means for executing settlement based on the symbol code read by the customer-side reading means or the store employee-side reading means in the effective reading state.

[0007] To solve the above-mentioned problems, another aspect of the present invention is a program that causes the computer of a sales data processing device, which includes a customer-side reading unit provided on the customer side for reading a symbol code used for payment, and a store clerk-side reading unit provided on the store clerk side for reading the symbol code, to function as a control means for controlling the reading of the symbol code by the customer-side reading unit and the reading of the symbol code by the store clerk-side reading unit to be in an effective reading state during payment, and as a payment execution means for executing a settlement based on the symbol code read by the customer-side reading unit or the store clerk-side reading unit in the effective reading state. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the network configuration of the sales data processing system according to this embodiment. [Figure 2] This is a perspective view showing an example of the appearance of a registration and settlement device. [Figure 3] This is a block diagram showing an example of the functional configuration of a registration and settlement device. [Figure 4] This figure shows examples of screens displayed on the store clerk's display and the customer's display when using code payment. [Figure 5] This figure shows examples of screens displayed on the staff's display and the customer's display when using payment methods other than QR code payments. [Figure 6]This flowchart shows an example of the registration and settlement process performed by the registration and settlement device according to this embodiment. [Figure 7] This flowchart shows an example of code payment processing performed by a registration and settlement device. [Figure 8] This flowchart shows an example of other payment processing performed by the registered payment device. [Modes for carrying out the invention]

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

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

[0011] The sales data processing system St shown in Figure 1 comprises a store controller 10, a transaction status management device 11, and registration and settlement devices 20 (20-1 to 20-n). Each device is connected to the others 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 can be a LAN (Local Area Network) or a WAN (Wide Area Network), and may be wired or wireless.

[0012] (Store controller 10) The store controller 10 stores various information necessary for transactions. This information includes registration information and settlement information generated by the registration and settlement device 20. It also includes 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 sales price for each product. Furthermore, the product master includes not only fixed-price products but also product identification information, product name, and unit price (price per gram) for products that require weighing (variable-weight products). In addition, the information stored by the store controller 10 also includes inventory status, sales history, deposit and withdrawal records, information on special sales, and member information.

[0013] (Transaction status management device 11) The transaction status management device 11 is a monitor for monitoring. Specifically, the transaction status management device 11 displays the processing status of the registration and settlement device 20 and controls the registration and settlement device 20. For example, a store employee (monitoring employee) is stationed at the transaction status management device 11, and the monitoring employee monitors the registration and settlement device 20. The transaction status management device 11 displays the status of each of the multiple registration and settlement devices 20. Specifically, the transaction status management device 11 displays multiple screens (split screens) corresponding to each of the multiple registration and settlement devices 20, and displays the status of each registration and settlement device 20. In addition, the transaction status management device 11 can also disable the split screens and display a screen corresponding to one registration and settlement device 20 (large screen display) in response to the operation of the monitoring employee. The monitoring employee supports customers operating the registration and settlement device 20 and verifies the age of customers when age-recognized products such as alcoholic beverages are registered in the registration and settlement device 20 in full self-service mode, as described later.

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

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

[0016] (A) The full self-service mode is an operation mode in which the customer registers (self-registers) goods on the device itself and the customer settles (self-settles) on the device itself.

[0017] (B) The clerk registration mode is an operation mode in which the clerk registers goods and performs face-to-face settlement on the device itself or self-settlement in the registration settlement device 20 in the accounting dedicated mode. Face-to-face settlement is settlement performed on the device itself when the customer faces the clerk and is based on the customer's operation. The registration settlement device 20 can also be provided with a change machine on the clerk side instead of or in addition to the customer side. In this case, the settlement in the clerk registration mode can also be settlement performed by the clerk receiving cash or the like from the customer instead of or in addition to face-to-face settlement.

[0018] In the clerk registration mode, the registration and settlement device 20 outputs registration information in order to have another (accounting dedicated mode) registration and settlement device 20 perform self - settlement. The output of the registration information is to transmit the registration information to another registration and settlement device 20. However, the output of the registration information may be to encode the registration information and display it on a display medium. The display medium may be, for example, a paper medium or an electronic device such as a smartphone.

[0019] (C) The accounting dedicated mode is a mode that operates in the above - mentioned other registration and settlement device 20. Specifically, the accounting dedicated mode is a mode that acquires the registration information registered by the registration and settlement device 20 in the clerk registration mode and performs self - settlement. The acquisition of the registration information is to receive the registration information from the registration and settlement device 20 in the clerk registration mode. However, the acquisition of the registration information may be to read the code displayed on the display medium.

[0020] Note that the registration and settlement device 20 may not be able to switch the operation mode. Specifically, the registration and settlement device 20 may be a registration and settlement device that only has the functions of the clerk registration mode. More specifically, the registration and settlement device 20 may have only the function of face - to - face settlement in the clerk registration mode, that is, it may be a registration and settlement device that does not have the function of transmitting the registration information to the registration and settlement device 20 in the accounting dedicated mode.

[0021] (Configuration with a clerk terminal) The sales data processing system St may include a clerk terminal held by a clerk. The clerk terminal may be able to display a screen similar to that of the transaction status management device 11, for example. Also, when a clerk call from a customer or customer fraud is detected in the registration and settlement device 20, the clerk terminal may notify the clerk of this. With such notification, the clerk holding the clerk terminal can go to the registration and settlement device 20 in the full self - service mode or the registration and settlement device 20 in the accounting dedicated mode to provide support to the customer, etc.

[0022] (Configuration with an administrative server) The sales data processing system St may include a management server for managing the registration and settlement devices 20. The management server stores a registration and settlement program that the registration and settlement devices 20 can store, and the program can be used to perform product registration and settlement processing. This allows the management server to manage and control each of the multiple registration and settlement devices 20 for each predetermined storage area. In this case, the registration and settlement device 20 may be equipped with drivers for screen control and printer control, or it may be a thin client that operates by the execution of the registration and settlement program on the management server.

[0023] (Example configuration of the registration and settlement device 20) Next, the configuration of the registration and settlement device 20 will be explained using Figure 2. Figure 2 shows an example of the external appearance of the registration and payment device 20. Although not shown in Figure 2, a counter for placing shopping baskets is placed on one or both sides of the registration and payment device 20.

[0024] The registration and payment device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer-side display unit 205, a customer-side scanner unit 206, a card payment unit 208, a change dispenser 209, a staff-side display unit 210, a key operation unit 211, a staff-side scanner unit 212, a printing unit 213, an audio output unit 214, a communication unit 215, a camera 216, and a signpost 220. These components can communicate with each other via a bus (not shown).

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

[0026] 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 information indicating registered products and settlement information generated during settlement.

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

[0028] The customer-side display unit 205 is a touch display for customers. The customer-side display unit 205 displays various information related to registration and payment to the customer and accepts various inputs from the customer related to registration and payment. These various inputs include, for example, inputs related to registration and payment. For example, the customer-side display unit 205 displays preset keys (product registration buttons) corresponding to products and accepts the registration of the product corresponding to the pressed preset key.

[0029] For example, the customer-side display unit 205 displays a payment type selection screen. The payment type selection screen displays payment type selection buttons (operators) corresponding to the payment types, and accepts the selection of a payment type when these buttons are pressed. Payment types include code payment, credit card payment, cash payment, electronic money payment, and membership point payment. On the payment type selection screen, multiple buttons corresponding to each payment type are displayed side by side.

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

[0031] Symbol codes include barcodes (product codes) attached to products, employee codes attached to employee name tags, and payment codes related to code payments displayed on the customer's mobile device. Product codes are codes that identify products, such as JAN codes, PLU (Price Look Up) codes, and in-store codes. When the customer-side scanner unit 206 reads a product code, the registration and settlement device 20 registers the product corresponding to that product code. The reading method used by the customer-side scanner unit 206 is not limited to CCD or CMOS; laser or pen-based methods are also possible.

[0032] The card payment unit 208 processes payments based on information stored in various media such as various cards and mobile terminals. These various cards include credit cards, prepaid cards such as electronic money cards, point cards, and membership cards. Electronic money is charged to charging media such as transportation IC cards and mobile terminals. Charging to charging media may be done by depositing cash at a designated charging terminal, or, if the charging media is associated with a credit card, by depositing from the credit card.

[0033] The change dispenser 209 is a cash payment mechanism. The change dispenser 209 is facing the customer and accepts various operations and cash insertions from the customer. Specifically, the change dispenser 209 has an input slot and an output slot for banknotes and coins. The change dispenser 209 calculates the amount to be inserted into the input slot, calculates the change amount which is the difference between the inserted amount and the purchase amount, and dispenses the change from the output slot. In addition to being installed on the customer side, the change dispenser 209 may also be installed on the employee side. In this case, the change dispenser 209 may accept various operations and cash insertions from the employee.

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

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

[0036] The employee-side scanner unit 212 is a scanner unit for employee use. Specifically, the employee-side scanner unit 212 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) the product. When an operator holds a product over the employee-side scanner unit 212, the imaging unit images the product. The imaging unit optically images the symbol code (such as a payment code displayed on a mobile terminal, a barcode or 2D code attached to the product) or the entire product or part of the product (object) that is held over the imaging window. Note that the reading method by the employee-side scanner unit 212 is not limited to CCD or CMOS; a laser method or a pen method can also be used.

[0037] Here, the types of symbol codes that the store clerk's scanner unit 212 can read are different from the types of symbol codes that the customer's scanner unit 206 can read. Specifically, the store clerk's scanner unit 212 can read product barcodes, membership codes, payment codes, and gift certificate codes. On the other hand, the customer's scanner unit 206 can read membership codes and payment codes.

[0038] The registration and settlement device 20 performs processing based on the code read by the customer-side scanner unit 206 or the store clerk-side scanner unit 212. The registration and settlement device 20 determines the type of code read (product code, store clerk 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 and settlement device 20 determines that the read code is a product code, it performs product registration processing. If the registration and settlement device 20 determines that the read code is a store clerk code, it performs login processing. If the registration and settlement device 20 determines that the read code is a payment code, it performs the code payment processing described later.

[0039] The printing unit 213 prints and outputs various media (receipts, invoices, etc.). The printing unit 213 has a rotatable mechanism and is configured so that the media output slot faces from the employee side to the customer side, and vice versa.

[0040] The audio output unit 214 outputs sound. For example, the audio output unit 214 outputs reading sounds (scanning sounds) when various codes are scanned, voice guidance, and warning sounds. These sounds are related to product registration and payment.

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

[0042] Camera 216 is mounted above the customer-side display unit 205. Camera 216 is a camera that captures video or a series of still images. Camera 216 can be a CCD camera or a CMOS camera. Camera 216 is a camera for monitoring customers and captures customer registration and payment operations.

[0043] The sign pole 220 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 220 can provide various notifications depending on the lighting pattern. These notifications include, for example, a notification that the sign pole is in use, a notification to call a staff member, or a notification that a customer has committed an illegal act.

[0044] (Functional configuration of the registration and settlement device 20) Figure 3 is a block diagram showing an example of the functional configuration of the registration and settlement device 20. As shown in Figure 3, the registration and settlement device 20 includes a customer-side scanner unit 206 and a store clerk-side scanner unit 212, as well as a settlement execution unit 301, a control unit 302, and a registration unit 303. Each of the settlement execution unit 301, the control unit 302, and the registration unit 303 is implemented by the CPU 201. That is, the CPU 201 implements each of the functional units by executing the sales data processing program according to this embodiment. As mentioned above, the registration and settlement device 20 according to this embodiment operates in store clerk registration mode. The customer-side scanner unit 206 is an example of a customer-side reading unit. The store clerk-side scanner unit 212 is an example of a store clerk-side reading unit.

[0045] (Regarding QR code payments) Here, we will explain code payment. As mentioned above, the symbol code read by the customer-side scanner unit 206 or the store clerk-side scanner unit 212 includes the payment code used for code payment. The payment code is a code in which customer identification information is represented by a two-dimensional code, etc., and is displayed on a mobile device such as a smartphone. The customer displays the payment code on their mobile device and has the customer-side scanner unit 206 or the store clerk-side scanner unit 212 read the payment code.

[0046] When a payment code is read by the customer-side scanner unit 206 or the store clerk-side scanner unit 212, the payment execution unit 301 executes a code payment based on the payment code. Specifically, when the payment execution unit 301 reads a payment code, it requests the code payment server to deduct the amount from the balance corresponding to the customer identification information.

[0047] The code payment server deducts the payment amount from the balance. Once the code payment server has completed the deduction, it sends a deduction completion notification to the registered settlement device 20 and the mobile terminal. Upon receiving the deduction completion notification, the registered settlement device 20 and the mobile terminal display a payment completion screen indicating that the payment has been completed, and the payment is finalized. If the code payment server is unable to deduct the amount due to insufficient funds or other reasons, an error notification is sent to the registered settlement device 20 and the mobile terminal to inform the customer of the error. In this case, the customer can either top up their balance on the code payment server and retry the code payment, or settle the payment using another payment method.

[0048] In the following, code payment based on a payment code read by the customer-side scanner unit 206 will be referred to as "customer-side code payment," and code payment based on a payment code read by the store clerk-side scanner unit 212 will be referred to as "store clerk-side code payment."

[0049] In addition to code payments, the payments performed by the payment execution unit 301 also include cash payments, credit card payments, electronic money payments, and member point payments using points earned by member customers.

[0050] (Regarding situations where there are customers who are unfamiliar with QR code payments) If a customer is unfamiliar with QR code payments, the payment process will take time. If the staff member is unable to do anything while the customer completes the QR code payment, it will not only create a bad impression on the next customer, but it could also increase the length of the queue at the register. Thus, if there are customers unfamiliar with QR code payments, it becomes difficult to handle customers efficiently and transactions cannot be conducted smoothly. Therefore, in this embodiment, transactions can be conducted smoothly even if there are customers unfamiliar with QR code payments. The control unit 302 will be described below.

[0051] (Control Unit 302) The control unit 302 controls the reading state of the customer-side scanner unit 206 and the store clerk-side scanner unit 212 when code payment is selected as the payment type. Specifically, in code payment, the control unit 302 controls the customer-side scanner unit 206 and the store clerk-side scanner unit 212 to enable reading of the payment code. The payment execution unit 301 executes the payment based on the payment code read by the customer-side scanner unit 206 or the store clerk-side scanner unit 212 when the reading is enabled. As a result, even if a customer has trouble with code payment, the store clerk can have the store clerk-side scanner unit 212 read the payment code, allowing the code payment to be completed quickly.

[0052] (Customer payment is valid) The control of the customer-side scanner unit 206 by the control unit 302 is described in detail below. In code payment, the control unit 302 controls the system to a read-enabled state where customer-side code payment is enabled (hereinafter referred to as the "customer-side payment enabled state"). In the customer-side payment enabled state, the customer-side scanner unit 206 becomes capable of reading payment codes. Specifically, for example, in the customer-side payment enabled state, the customer-side scanner unit 206 becomes capable of reading only codes of a predetermined number of digits corresponding to the payment code. In the customer-side payment enabled state, when the payment code is read by the customer-side scanner unit 206, the payment execution unit 301 executes the customer-side code payment based on the payment code.

[0053] When customer payment is enabled, it becomes impossible to read symbol codes other than the payment code. However, the control unit 302 may enable the reading of symbol codes other than the payment code when customer payment is enabled. However, even if another symbol code (for example, a membership code) is read when customer payment is enabled, the control unit 302 should discard (delete) the other payment code.

[0054] (Customer payment invalid) Furthermore, the control unit 302 controls the customer-side code payment to be disabled (hereinafter referred to as "customer-side payment disabled state") at times other than code payment. In the customer-side payment disabled state, the customer-side scanner unit 206 becomes unable to read all symbol codes, including the payment code. However, in the customer-side payment disabled state, the customer-side scanner unit 206 may be able to read other symbol codes other than the payment code (for example, the membership code).

[0055] Furthermore, when the customer payment is invalid, the customer scanner unit 206 may be enabled to read symbol codes including payment codes. However, even if a symbol code is read when the customer payment is invalid, the control unit 302 may discard (delete) the symbol code.

[0056] (Payment is valid on the store clerk's end) Next, the control of the store clerk-side scanner unit 212 by the control unit 302 will be described in detail. In code payment, the control unit 302 controls the system to a read-enabled state where store clerk-side code payment is enabled (hereinafter referred to as the "store clerk-side payment enabled state"). In the store clerk-side payment enabled state, the store clerk-side scanner unit 212 becomes capable of reading payment codes. Specifically, for example, in the customer-side payment enabled state, the store clerk-side scanner unit 212 becomes capable of reading only a predetermined number of digits of code corresponding to the payment code. In the store clerk-side payment enabled state, when the payment code is read by the store clerk-side scanner unit 212, the payment execution unit 301 executes the store clerk-side code payment based on the payment code.

[0057] When the cashier-side payment is enabled, it becomes impossible to read any symbol codes other than the payment code. However, the control unit 302 may enable the reading of other symbol codes other than the payment code when the cashier-side payment is enabled. However, even if another symbol code is read when the cashier-side payment is enabled, the control unit 302 should discard (delete) that other payment code.

[0058] (Payment invalid on the store clerk's end) Furthermore, the control unit 302 controls the clerk-side code payment to be disabled (hereinafter referred to as "clerk-side payment disabled state") at times other than code payment, such as during product registration. In the clerk-side payment disabled state, the clerk-side scanner unit 212 becomes unable to read payment codes. However, in the clerk-side payment disabled state, the clerk-side scanner unit 212 may be able to read other symbol codes besides payment codes. These other symbol codes include, for example, product barcodes, membership codes, and gift certificate codes.

[0059] Furthermore, the control unit 302 may enable the cashier-side scanner unit 212 to read symbol codes, including payment codes, when the cashier-side payment is disabled. However, even if a symbol code is read when the cashier-side payment is disabled, the control unit 302 may discard (delete) the symbol code.

[0060] (Regarding product registration) The registration unit 303 registers products based on the product code. The product code is a barcode (e.g., a JAN code) attached to the product. During product registration, the control unit 302 controls the store clerk-side scanner unit 212 to a state where reading the product code is enabled (hereinafter referred to as the "registration enabled state"). In the registration enabled state, the store clerk-side scanner unit 212 becomes capable of reading product codes. Specifically, for example, in the registration enabled state, the store clerk-side scanner unit 212 becomes capable of reading only a predetermined number of digits of code corresponding to the product code. In the registration enabled state, the registration unit 303 registers products based on the product code read by the store clerk-side scanner unit 212.

[0061] When registration is active, it becomes impossible to read symbol codes other than the product code. However, the control unit 302 may enable the reading of symbol codes other than the product code when registration is active. However, even if another symbol code is read when registration is active, the control unit 302 should discard (delete) that other payment code.

[0062] (Regarding the next customer's product registration) The control unit 302 controls the system to the registration enabled state when a predetermined operation (for example, pressing the next customer registration button 412 in Figure 4(A)) is performed while the cashier's payment is enabled. In the registration enabled state, only the customer's code payment is enabled, and the cashier's code payment is disabled. In the registration enabled state during code payment, the registration unit 303 registers the next customer's products based on the product code read by the cashier's scanner unit 212. The registration information related to the previous customer's product registration and the registration information related to the next customer's product registration are stored in separate memory areas.

[0063] (Screens displayed on the staff-side display unit 210 and the customer-side display unit 205) The control unit 302 displays on the employee-side display unit 210 a message prompting the customer to read the payment code and an operator to accept the start of product registration for the next customer, when the customer-side payment is in an active state and the employee-side payment is in an active state. Here, using Figure 4, examples of the screens of the employee-side display unit 210 and the customer-side display unit 205 controlled by the control unit 302 will be explained.

[0064] Figure 4 shows examples of screens displayed on the store clerk's display unit 210 and the customer's display unit 205 during code payment.

[0065] (Information screen regarding QR code payments) As shown in Figure 4(A), the staff-side display unit 210 displays the staff-side guidance screen 410. The staff-side guidance screen 410 is a screen superimposed (pop-up displayed) on the subplan screen 411. The subplan screen 411 includes a payment type selection button 415. The staff-side guidance screen 410 is displayed when code payment is selected during the payment type selection process after product registration is complete. The selection of the payment type can be accepted from either the customer-side display unit 205 or the staff-side display unit 210. Specifically, when the staff-side display unit 210 is displaying the subplan screen 411, the registration and settlement device 20 can display the payment type selection screen on the customer-side display unit 205, and accept the selection of the payment type by pressing the payment type selection button 415 on the subplan screen 411.

[0066] The staff-side guidance screen 410 includes a notification prompting the staff-side scanner unit 212 to read the payment code. The staff-side guidance screen 410 also includes a next customer registration button 412 and a cancel button 413. The next customer registration button 412 is a button that accepts the start of product registration for the next customer. The Cancel button 413 is a button that accepts the cancellation of a code payment. When the Cancel button 413 is pressed, the staff guidance screen 410 (pop-up display) disappears, and the customer is prompted to select the payment type again. This allows the staff to cancel the code payment. Similarly, if the Cancel button 422, described later, is pressed on the customer-side display unit 205, the staff guidance screen 410 (pop-up display) disappears, and the customer is prompted to select the payment type again.

[0067] Furthermore, in Figure 4(A), the customer-side display unit 205 displays the customer-side guidance screen 420. The customer-side guidance screen 420 is displayed when code payment is selected on the payment type selection screen (not shown) that is displayed after product registration is complete. The customer-side guidance screen 420 includes a notification prompting the customer-side scanner unit 206 to read the payment code.

[0068] The customer guidance screen 420 includes a notification video 421 and a cancel button 422. Notification video 421 is an animated video showing the process of having the customer-side scanner unit 206 read the payment code displayed on the mobile device. The Cancel button 422 is a button that accepts the cancellation of a code payment. When the Cancel button 413 is pressed, the customer-side display unit 205 returns to the payment type selection screen. Similarly, if the Cancel button 413 is pressed on the store employee-side display unit 210, the customer-side display unit 205 also returns to the payment type selection screen.

[0069] When the next customer registration button 412 is pressed on the staff guidance screen 410, the control unit 302 transitions to the next customer registration screen 430 shown in Figure 4(B).

[0070] (Next customer registration screen during code payment) As shown in Figure 4(B), the next customer registration screen 430 is displayed on the staff-side display unit 210. The next customer registration screen 430 includes a next customer tab 431 and a previous customer tab 432. The next customer tab 431 is the tab corresponding to the next customer's transaction. In the diagram, the next customer tab 431 is ON, meaning that the next customer registration screen 430 is the registration screen for the next customer. The diagram also shows that one item, "○○ Coffee," has been registered as the next customer's transaction. The previous customer tab 432 is the tab corresponding to the previous customer's transaction. In the diagram, the previous customer tab 432 is OFF. When the previous customer tab 432 is pressed, the screen for the transaction corresponding to the previous customer is displayed, and the next customer tab 431 is turned OFF.

[0071] In Figure 4(B), the customer-side display unit 205 continues to display the customer-side guidance screen 420. The control unit 302 reads the payment code, and once the code payment is completed, it issues a receipt and finishes the transaction with the previous customer. After finishing the transaction with the previous customer, the control unit 302 hides the previous customer tab 432.

[0072] (Example screen for payment methods other than QR code payments) Figure 5 shows an example of the screens displayed on the employee-side display unit 210 and the customer-side display unit 205 during payment methods other than code payments. In Figure 5, credit card payment is used as an example of other payment methods. However, even in the case of other payment methods such as electronic money payments or cash payments, the employee-side display unit 210 will display a screen similar to the one shown in Figure 5.

[0073] As shown in Figure 5, the staff-side display unit 210 displays the next customer registration guidance screen 510. The next customer registration guidance screen 510 is displayed when credit card payment is selected during the payment method selection process that takes place after product registration is complete. The next customer registration guidance screen 510 is a screen that is superimposed (pop-up displayed) on the subplan screen 511. The next customer registration guidance screen 510 includes a notification that the previous customer is currently being paid for and prompts the next customer to register their products (by pressing the next customer registration button 512).

[0074] The next customer registration guidance screen 510 includes a next customer registration button 512. The next customer registration button 512 is a button that accepts the next customer's request to start product registration. Also, in Figure 5, the customer-side display unit 205 displays the customer-side guidance screen 520. The customer-side guidance screen 520 is a screen that is displayed when credit card payment is selected on the payment type selection screen (not shown) that is displayed after product registration is complete.

[0075] The customer guidance screen 520 includes a guidance image 521 and a cancel button 522. Instruction image 521 shows instructions for inserting a credit card into the card payment unit 208. Specifically, instruction image 521 shows three instructions corresponding to the type of credit card payment (three types: IC payment, magnetic payment, and CR touch payment). The credit card reading method for IC payment is, for example, the insertion method. The credit card reading method for magnetic payment is the sliding method. The credit card reading method for CR touch payment is a contactless method using NFC (Near Field Communication), etc.

[0076] The Cancel button 522 is a button that accepts the cancellation of a credit card payment. When the Cancel button 522 is pressed, the customer-side display unit 205 returns to the payment type selection screen. Note that in the case of credit card payments, the store clerk-side display unit 210 does not display a Cancel button. This is because store clerks cannot intervene in payment methods other than code payments. Specifically, for credit card payments and electronic money payments, the card payment unit 208 is located on the customer side, so store clerks cannot intervene in these payments. Also, for cash payments, the input and output slots of the change machine 209 are located on the customer side, so store clerks cannot intervene in cash payments. For this reason, in the case of payment methods other than code payments, store clerks cannot cancel those other payments through their own operation.

[0077] On the other hand, with code payments, if the balance is insufficient, the payment must be stopped upon the customer's notification that they have noticed the insufficient balance. For this reason, code payments can be stopped by the store staff. In the case of code payments, the customer directs the screen of their mobile device towards the customer-side scanner 206, taking into account the position and angle of the payment code so that the customer-side scanner 206 can read the payment code. For this reason, compared to credit card payments, customers may not be able to complete the payment smoothly with code payments, and store staff may be required to assist the customer.

[0078] (Registration and settlement process performed by the registration and settlement device 20) Figure 6 is a flowchart showing an example of the registration and settlement process performed by the registration and settlement device 20 according to this embodiment. As shown in Figure 6, the registration and settlement device 20 determines whether or not the registration of a product has started (step S601). The registration of a product starts, for example, when a button that accepts the start of product registration is pressed. However, the registration of a product is not limited to this, and product information for one item may be entered by accepting a scan operation or a key operation (pressing a preset key).

[0079] The registration and payment device 20 waits until product registration begins (step S601: NO), and when product registration begins (step S601: YES), the registration and payment device 20 controls the store clerk side to a registration enabled state (step S602). At this time, the registration and payment device 20 controls the customer side to an invalid state in which reading of the symbol code is impossible. The registration and payment device 20 then determines whether or not a product code has been read (or a preset key has been pressed) (step S603). If no product code has been read (step S603: NO), the registration and payment device 20 proceeds to step S605. If a product code has been read (step S603: YES), the registration and payment device 20 registers the product (step S604).

[0080] The registration and settlement device 20 then determines whether or not the product registration is complete (step S605). Product registration is complete when, for example, the subtotal button is pressed. If product registration is not complete (step S605: NO), the registration and settlement device 20 returns to step S603 and repeats the process from steps S603 to S605. On the other hand, if product registration is complete (step S605: YES), the registration and settlement device 20 performs the payment type selection process (step S606). In the payment type selection process, the registration and settlement device 20 displays the payment type selection screen on the customer-side display unit 205 and accepts the customer's selection of the payment type.

[0081] Then, the registration and settlement device 20 determines whether or not code payment has been selected in the payment type selection process (step S607). If code payment is selected (step S607: YES), the registration and settlement device 20 executes the code payment process (Figure 7) (step S608) and terminates the series of processes. On the other hand, if code payment is not selected in the payment type selection process (step S607: NO), it executes another payment process (Figure 8) (step S609) and terminates the series of processes.

[0082] (Code payment processing) Figure 7 is a flowchart illustrating an example of the code payment processing performed by the registration and settlement device 20. As shown in Figure 7, the registration and settlement device 20 controls the store clerk's payment to be active and the customer's payment to be active (step S701). The registration and settlement device 20 then displays guidance screens (store clerk guidance screen 410 and customer guidance screen 420 in Figure 4(A)) on the store clerk's display unit 210 and the customer's display unit 205 (step S702).

[0083] Next, the registration and settlement device 20 determines whether or not to register the next customer (whether or not the next customer registration button 412 in Figure 4(A) was pressed) (step S703). If the customer is not registered (step S703: NO), it determines whether or not the employee-side scanner unit 212 or the customer-side scanner unit 206 has read the payment code (step S704). If the employee-side scanner unit 212 or the customer-side scanner unit 206 has read the payment code (step S704: YES), the registration and settlement device 20 proceeds to step S708 and executes the code payment.

[0084] On the other hand, if the cashier's scanner unit 212 or the customer's scanner unit 206 does not read the payment code (step S704: NO), the registration and settlement device 20 determines whether or not to cancel the code payment (whether or not the cancel button 413 in Figure 4(A) was pressed) (step S705). If the code payment is to be canceled (step S705: YES), the registration and settlement device 20 returns to step S606 in Figure 6 and performs the payment type selection process.

[0085] On the other hand, if the code payment is not canceled (step S705: NO), the registration and settlement device 20 returns to step S703. If the next customer is to be registered in step S703 (step S703: YES), the registration and settlement device 20 is controlled to the registration enabled state (step S706). This makes it possible to register the next customer's products.

[0086] Next, the registration and settlement device 20 determines whether the customer-side scanner unit 206 has read the payment code (step S707). The registration and settlement device 20 waits until the customer-side scanner unit 206 reads the payment code (step S707: NO).

[0087] During this waiting period, if a product code is read (or a preset key is pressed), the registration and settlement device 20 will register the next customer's product according to that product code. During this waiting period, the store clerk can also provide support to the customer regarding the reading of the payment code. Furthermore, during this waiting period, it is also possible to hold off on registering the next customer and retrieve the customer's registration information related to code payment, thereby controlling the store clerk's payment to an active state and reading the payment code with the store clerk's scanner unit 212.

[0088] When the customer-side scanner unit 206 reads the payment code (step S707: YES), the registration and settlement device 20 executes code payment (request for withdrawal from the code payment server) (step S708). Once the code payment is complete, the registration and settlement device 20 issues a receipt (step S709) and ends the series of processes.

[0089] (Other payment processing) Figure 8 is a flowchart illustrating an example of another payment process performed by the registration and settlement device 20. As shown in Figure 8, the registration and settlement device 20 controls the store clerk-side payment invalid state and the customer-side payment invalid state (step S801). The registration and settlement device 20 then displays a guidance screen corresponding to the payment type (for example, the customer-side guidance screen in Figure 5) on the customer-side display unit 205 (step S802). The registration and settlement device 20 then displays the next customer registration guidance screen 510 (Figure 5) on the store clerk-side display unit 210 (step S803).

[0090] Next, the registration and payment device 20 determines whether or not to register the next customer (whether or not the next customer registration button 512 in Figure 5 is pressed) (step S804). If the current customer is not to register (step S804: NO), the registration and payment device 20 proceeds to step S806. On the other hand, if the next customer is to register (step S804: YES), the registration and payment device 20 controls the device to the registration enabled state (step S805). This makes it possible to register the next customer's products.

[0091] Next, the registration and settlement device 20 determines whether the settlement has been completed based on the payment type selected in the payment type selection process (step S606 in Figure 6) (a payment type other than code payment) (step S806). The registration and settlement device 20 waits until the settlement is completed (step S806: NO). During this waiting period, if the registration and settlement device 20 reads a product code (or presses a preset key), it registers the next customer's product according to that product code. If it has not been determined in step S804 to register the next customer, it is also possible to accept a press of the next customer registration button 512 during this waiting period and start the next customer registration. During this waiting period, the store clerk can also provide support to the customer regarding the settlement.

[0092] Once the settlement is complete (step S806: YES), the registration settlement device 20 issues a receipt (step S807) and terminates the series of processes.

[0093] (Effects of the embodiment) As described above, the registration and settlement device 20 according to this embodiment controls the system to enable cashier-side payment and enable customer-side payment in code payment, and executes one of the customer-side code payment or cashier-side code payment. This allows store employees to quickly complete code payments even if a customer has difficulty with the QR code payment process, by having the employee scan the payment code using the employee-side scanner unit 212. This reduces the time employees have to wait for the QR code payment to be completed, enabling faster transactions. This also helps prevent negative impressions from the next customer towards the employee and reduces the length of the queue at the register. Therefore, even if a customer is unfamiliar with QR code payments, the store can efficiently handle customers and conduct transactions smoothly.

[0094] Furthermore, in code payment, the registration and settlement device 20 according to this embodiment is controlled to a registration-enabled state when a predetermined operator (next customer registration button 412 in Figure 4(A)) is operated, and the next customer's products are registered. This allows for customer support during QR code payments, and if the customer is familiar with QR code payments, they are less likely to require assistance from a store employee, allowing the employee to register the next customer at their own discretion. Therefore, it reduces the time employees have to wait for QR code payments to be completed, enabling faster and more effective transactions.

[0095] Furthermore, the registration and settlement device 20 according to this embodiment displays, in code payment, a guide prompting the reading of the payment code (store clerk's guide screen 410 in Figure 4(A)), an operator that accepts the start of product registration for the next customer (next customer registration button 412 in Figure 4(A)), and information displayed on the store clerk's display unit 210. This allows store staff to be prompted to scan the payment code and also to register the next customer. Therefore, it reduces the time store staff have to wait until the code payment is completed, enabling faster and more effective transactions.

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

[0097] (Example of variation 1: Making the member code readable during product registration) First, let's explain Modification 1. Modification 1 describes an example in which the member code can be read during product registration. The member code is a coded representation of member information. The member code is, for example, written on a member card. The registration and payment device 20 can obtain member information from the member code and grant the customer a predetermined benefit (points) from the store.

[0098] (An example of making the membership code readable by both the store clerk and the customer) In Modification 1, the registration and settlement device 20 also enables the reading of the member code while registering the product. Specifically, the registration and settlement device 20 enables the reading of the member code by the employee-side scanner unit 212 and the customer-side scanner unit 206 when, for example, the member call button displayed on the employee-side display unit 210 is pressed. In other words, when the member call button is pressed, the control unit 302 controls the employee-side from a registration valid state (a state in which reading of the member code by the employee-side scanner unit 212 is not possible) to a state in which reading of the member code by the employee-side scanner unit 212 is enabled (hereinafter referred to as the "employee-side member enabled state"). In the employee-side member enabled state, the control unit 302 enables the reading of the member code and makes it impossible to read the product code.

[0099] Furthermore, on the customer side, when the member call button is pressed, the control unit 302 controls the system from a state where reading the member code is impossible (hereinafter referred to as "customer-side member invalid state") to a state where reading the member code at the customer-side scanner unit 206 is enabled (hereinafter referred to as "customer-side member enabled state").

[0100] When a member code is read by either the employee-side scanner unit 212 or the customer-side scanner unit 206, the control unit 302 returns the employee-side scanner from the employee-side member active state to the registration active state, and returns the customer-side scanner from the customer-side member active state to the customer-side member inactive state. As a result, the registration and settlement device 20 can acquire a member code even while registering products.

[0101] (An example where the membership code can be read by either the store clerk or the customer.) In the example above, we described an example in which the member code can be read by either the employee-side scanner unit 212 or the customer-side scanner unit 206, but it is sufficient if the member code can be read by at least one of them. Specifically, when the member call button is pressed, the control unit 302 may control the employee-side scanner from the registration enabled state to the employee-side member enabled state, while maintaining the customer-side member disabled state. Alternatively, when the member call button is pressed, the control unit 302 may maintain the registration enabled state for the employee-side scanner and control the customer-side scanner from the customer-side member disabled state to the customer-side member enabled state.

[0102] (An example of making the store clerk able to read the member code at all times while registering a product.) Furthermore, the control unit 302 may keep the reading of the member code at the employee-side scanner unit 212 permanently enabled while the product is being registered. In other words, the control unit 302 may enable the reading of the member code at the employee-side scanner unit 212 (employee-side member enabled state) when the employee-side registration is enabled. However, in this case, when the employee-side scanner unit 212 reads the member code, the control unit 302 may switch from the employee-side member enabled state to the customer-side member disabled state. Also, if the reading of the member code at the employee-side scanner unit 212 is permanently enabled, the control unit 302 may permanently disable the reading of the member code at the customer-side scanner unit 206.

[0103] (An example of making the customer's membership code always readable during product registration.) Furthermore, the control unit 302 may keep the reading of the member code at the customer-side scanner unit 206 permanently enabled while products are being registered. In other words, the registration and settlement device 20 may enable the reading of the member code at the customer-side scanner unit 206 (customer-side member enabled state) while products are being registered. However, in this case, when the customer-side scanner unit 206 reads the member code, the control unit 302 may switch from the customer-side member enabled state to the customer-side member disabled state. Also, if the reading of the member code at the customer-side scanner unit 206 is permanently enabled, the control unit 302 may permanently disable the reading of the member code at the store clerk-side scanner unit 212.

[0104] Furthermore, reading the member code at the employee-side scanner unit 212 or the customer-side scanner unit 206 may be performed before product registration begins (for example, in a standby state), or after the first product has been registered.

[0105] (Regarding reading the next customer's membership code) When registering the next customer's product, if the previous customer's code payment is processed, the customer-side scanner unit 206 and the store clerk-side scanner unit 212 prioritize reading the previous customer's payment code and do not read the next customer's membership code. Once the previous customer's code payment is complete, the previous customer's transaction is finished, and the customer-side scanner unit 206 and the store clerk-side scanner unit 212 become capable of reading the next customer's membership code.

[0106] (Example of using member points for payment) The symbol code used for payment includes not only the payment code but also the member code. Specifically, the symbol code read by the customer-side scanner unit 206 or the store clerk-side scanner unit 212 includes not only the payment code but also the member code (member information) for using member points. Member points are associated with the member code. Member points have a defined exchange value, for example, 1 point = 1 yen.

[0107] For example, the registration and settlement device 20 proceeds to the subtotal without acquiring member information, and when member point payment is selected on the payment type selection screen displayed on the customer-side display unit 205, it controls the store clerk's member active state and the customer's member active state. In the store clerk's member active state and the customer's member active state, the registration and settlement device 20 displays the store clerk's member code guidance screen and the customer's member code guidance screen. These screens are, for example, the store clerk guidance screen 410 and customer guidance screen 420 in Figure 4(A) that display a notification prompting the reading of the member code (for example, a notification saying "Please let me read your member code").

[0108] The staff member code guidance screen displays a next customer registration button 412 (Figure 4(A)). When the next customer registration button 412 is pressed on the staff member code guidance screen, the staff member's status is changed from active to active registration (transitioning to the next customer registration screen 430 (Figure 4(B))), similar to the case of code payment, and next customer registration becomes possible.

[0109] When the member code is read by the customer-side scanner unit 206 while the employee-side member is active and the customer-side member is active, member point payment (customer-side point payment) is performed based on that member code. Also, when the member code is read by the employee-side scanner unit 212 while the employee-side member is active and the customer-side member is active, member point payment (employee-side point payment) is performed based on that member code.

[0110] Furthermore, when the member code is read by either the employee-side scanner unit 212 or the customer-side scanner unit 206 while the employee-side member is active or the customer-side member is active, the control unit 302 returns the employee-side member from the employee-side member active state to the registration active state, and returns the customer-side member from the customer-side member active state to the customer-side member inactive state. In this way, the registration and settlement device 20 can acquire a member code, accept the number of points to be used (exchange amount) based on that member code, and perform member point settlement.

[0111] According to Variation 1, during product registration, a membership code can be obtained, and benefits can be granted to the customer. Furthermore, during code payment, either customer-side code payment or store-side code payment can be executed, allowing for quick code payments.

[0112] Furthermore, the registration and settlement device 20 according to Modification 1 controls the system to enable cashier-side payment and enable customer-side payment in member point payments, and executes one of the customer-side point payments or cashier-side point payments. This allows store staff to quickly complete member point payments even if customers have difficulty with the point payment process, by having the staff member scan the member code using the staff-side scanner unit 212. This reduces the time staff have to wait while the member point payment is completed, enabling faster transactions. This also helps prevent negative impressions from the next customer towards the staff and reduces the length of the queue at the register. Therefore, even if there are customers unfamiliar with member point payments, the system can efficiently handle customers and ensure smooth transactions.

[0113] (Variation 2: Example of self-checkout in dedicated payment mode) Next, we will describe a second variation. In the embodiment described above, we used face-to-face payment in the employee registration mode as an example. In the second variation, we will describe an example in which face-to-face payment in the employee registration mode or self-payment in the payment-only mode is performed depending on the payment type.

[0114] In Modification 2, the registration and settlement device 20 in the employee registration mode accepts the selection of a payment type, similar to the embodiment. The selection of the payment type is made based on the customer's operation. However, the selection of the payment type may also be made based on the employee's operation in response to a request from the customer. If the selected payment type is cash payment, the registration and settlement device 20 transmits the registration information to the registration and settlement device 20 in the accounting-only mode. As a result, the customer moves to the registration and settlement device 20 in accounting-only mode and makes a cash payment at that registration and settlement device 20.

[0115] On the other hand, if the selected payment type is a non-cash payment (such as code payment, credit card payment, or electronic money payment), face-to-face settlement is performed. For example, if the selected payment type is code payment, the registered settlement device 20 performs code payment during face-to-face settlement, similar to the embodiment.

[0116] According to Modification 2, since cash payments take longer to process than non-cash payments, performing the settlement using the registration settlement device 20 in accounting-only mode reduces the waiting time for customers in the registration settlement device 20 operating in employee registration mode. This allows for efficient customer service and thus facilitates smooth transactions.

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

[0118] In stores such as supermarkets, various payment methods are used for checkout, including cash and credit cards. For example, code-based payment is used, where a payment code displayed on a mobile device is scanned to complete the transaction (see, for example, Patent Document 1 below). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2021-22283 [Overview of the prefecture] [Problems the invention aims to solve] However, with conventional technology, if there were customers unfamiliar with code payments, the settlement process could take a long time, which meant that transactions could not be conducted quickly and could not be performed properly. This invention has been made in view of these circumstances, and its purpose is to provide a technology that enables favorable transactions.

[0119] [Means for solving the problem] (1) In order to solve the above-mentioned problems, a sales data processing device according to one aspect of the present invention is a sales data processing device characterized by comprising: a customer-side reading means provided on the customer side for reading a symbol code used for payment; a store employee-side reading means provided on the store employee side for reading the symbol code; a control means for controlling the reading of the symbol code by the customer-side reading means and the reading of the symbol code by the store employee-side reading means to be in an effective reading state in the payment; and a settlement execution means for executing settlement based on the symbol code read by the customer-side reading means or the store employee-side reading means in the effective reading state. With the above configuration, even if a customer has difficulty with payment, the cashier can quickly complete the payment by having the cashier's scanner unit 212 read the symbol code. This reduces the time the cashier has to wait for the payment to be completed, enabling quick transactions. This also reduces the chance of the next customer having a negative impression of the cashier and prevents the queue of customers waiting at the register from growing. Therefore, even if there are customers who are unfamiliar with payment, the cashier can handle them efficiently and conduct transactions smoothly.

[0120] (2) In the configuration of (1) above, the system may be configured to include a registration means for registering products based on a product code, wherein the control means controls the system to a registration enabled state in which, when a predetermined operation is performed in the read-enabled state, the registration means enables the registration of the next customer's product based on the reading of the product code by the store clerk's reading means, and the registration means registers the next customer's product in the registration enabled state based on the product code read by the store clerk's reading means. According to the above configuration, it is possible to support customers during payment while also allowing store staff to register the next customer at their discretion. Therefore, it is possible to reduce the time store staff have to wait until payment is completed and to conduct quick transactions more effectively.

[0121] (3) In the configuration of (2) above, the store may be provided with a store employee-side display means, and the control means may cause the store employee-side display means to display a message prompting the reading of the symbol code and an operator for accepting the start of product registration for the next customer when the reading is enabled. With the above configuration, store staff can be prompted to read the symbol code and also to register the next customer. Therefore, it is possible to reduce the time store staff have to wait until payment is completed and to conduct quick transactions more effectively.

[0122] (4) In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes the computer of a sales data processing device, which is provided on the customer side and reads a symbol code used for payment, and is provided on the store clerk side and reads the symbol code, to function as a control means for controlling the reading of the symbol code by the customer side reader and the reading of the symbol code by the store clerk side reader to be in an effective reading state during payment, and as a payment execution means for executing a settlement based on the symbol code read by the customer side reader or the store clerk side reader in the effective reading state. With the above configuration, even if a customer has difficulty with payment, the cashier can quickly complete the payment by having the cashier's scanner unit 212 read the symbol code. This reduces the time the cashier has to wait for the payment to be completed, enabling quick transactions. This also reduces the chance of the next customer having a negative impression of the cashier and prevents the queue of customers waiting at the register from growing. Therefore, even if there are customers who are unfamiliar with payment, the cashier can handle them efficiently and conduct transactions smoothly.

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

[0124] Specifically, the above description described a configuration in which the registration and settlement device 20 comprises a settlement execution unit 301, a control unit 302, and a registration unit 303, as shown in Figure 4, etc. However, all or part of these functional units may be provided on other computer devices. For example, all or part of these functional units may be provided on the store controller 10, on an external server device, or on any other computer device. Furthermore, the computer devices equipped with these functional units are not limited to multiple devices, but may consist of just one device.

[0125] Specifically, for example, instead of the registration and settlement device 20, the store controller 10 or an external server device may control the registration and settlement device 20 to either a cashier-side settlement enabled state or a customer-side settlement enabled state during settlement, and execute the settlement based on the symbol code read by the customer or the cashier.

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

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

[0128] St...Sales data processing system, 10...Store controller, 20...Registration and settlement device, 201...CPU, 202...ROM, 203...RAM, 204...Hard disk, 210...Employee-side display unit, 301...Settlement execution unit, 302...Control unit, 303...Registration unit

Claims

1. A customer-side reading device is provided on the customer's side to read the symbol code used for payment, A reading means for the store clerk is provided on the store clerk's side to read the aforementioned symbol code, In the payment described above, a control means controls the reading of the symbol code by the customer-side reading means and the reading of the symbol code by the store clerk-side reading means to be in an effective reading state. In the read-enabled state, a payment execution means that executes a payment based on the symbol code read by the customer-side reading means or the store clerk-side reading means, A sales data processing device characterized by comprising the following features.

2. It includes a registration means for registering products based on product codes, The control means controls the system to a registration enabled state in which, when a predetermined operation is performed in the read-enabled state, the registration of the next customer's product based on the reading of the product code by the store clerk's reading means becomes enabled. The registration means, in the registration valid state, registers the next customer's product based on the product code read by the store employee's reading means. A sales data processing device characterized by the present invention.

3. Equipped with a display means for the staff, The control means causes the store clerk's display means to display a message prompting the reading of the symbol code and an operator for accepting the start of product registration by the next customer, when the reading is enabled. The sales data processing device according to feature 2.

4. A customer-side reader unit is provided on the customer side to read the symbol code used for payment, A reader unit on the employee's side is provided to read the aforementioned symbol code, A computer for a sales data processing device equipped with In the aforementioned payment, a control means controls the reading of the symbol code by the customer-side reading unit and the reading of the symbol code by the store clerk-side reading unit to be in an effective reading state. In the read-enabled state, a payment execution means that executes payment based on the symbol code read by the customer-side reading unit or the store clerk-side reading unit. A program characterized by being designed to function as such.

Images