Registration information management device, registration device, settlement device, system, and program

Abstract

To conduct transactions efficiently.SOLUTION: A registration information management device comprises registration means and transaction control means. The registration means registers, for each registration procedure indicating a registration operation of commodity by a customer from start to end, customer identification information for identifying the customer performing a registration operation in association with registration information based on the registration operation. When customer identification information pertaining to an earlier registration procedure matches customer identification information pertaining to a later registration procedure, the transaction control means enables settlement of payment based on the registration information pertaining to the earlier registration procedure and the registration information pertaining to the later registration procedure.SELECTED DRAWING: Figure 6

Description

Technical Field

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

Background Art

[0002] In stores and the like, a checkout system may be introduced in which a registration device for registering products and a settlement device for settlement are separated (see, for example, Patent Document 1). In particular, in recent years, a self-service type in which a customer performs a registration operation on a registration device and a customer performs a settlement operation on a settlement device has been spreading.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, in a self-service cash register, after the registration of products is completed, a customer may notice an oversight such as forgetting to buy something and wish to make additional registrations. However, in the prior art, if separate settlements are made for the previously registered products and the products for which additional registration is desired, it may take time for the settlement and transactions may not be carried out efficiently. There was such a problem.

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

Means for Solving the Problems

[0006] In order to solve the above-described problems, a registration information management apparatus according to an aspect of the present invention registers, for each registration procedure indicating from the start to the end of a product registration operation by a customer, customer identification information for identifying the customer who performs the registration operation and registration information based on the registration operation in association with each other. When the customer identification information related to a previous registration procedure matches the customer identification information related to a subsequent registration procedure, the registration information management apparatus is characterized by including transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure.

[0007] In order to solve the above-described problems, a registration apparatus according to another aspect of the present invention is a registration apparatus that is connected to the registration information management apparatus described above and performs product registration. The registration apparatus includes an input unit for inputting registration information based on the registration operation. When the customer identification information related to a previous registration procedure matches the customer identification information related to a subsequent registration procedure, the input unit enables input of the registration information related to the subsequent registration procedure when a period from completion of the previous registration procedure to start of the subsequent registration procedure is less than a predetermined period, and prohibits input of the registration information related to the subsequent registration procedure when the period is equal to or more than the predetermined period.

[0008] In order to solve the above-described problems, a settlement apparatus according to another aspect of the present invention is a settlement apparatus that is connected to the registration information management apparatus described above and performs settlement by a customer's settlement operation. The settlement apparatus includes customer identification information acquisition means for acquiring customer identification information for identifying the customer who performs the settlement operation, request means for making a transmission request for registration information to the registration information management apparatus based on the customer identification information acquired by the customer identification information acquisition means, selection means for selecting whether to total the registration information related to a plurality of registration procedures when the registration information received from the registration information management apparatus in response to the transmission request is the registration information related to a plurality of registration procedures, and settlement means for performing settlement based on the selection result of the selection means.

[0009] In order to solve the above-described problems, a system according to another aspect of the present invention is a system including a registration device and a settlement device, where the registration device associates and registers customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation for each registration procedure indicating from the start to the end of the registration operation of a product by a customer, and the settlement device includes transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure when the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure. A system characterized by this.

[0010] In order to solve the above-described problems, a program according to another aspect of the present invention causes a computer of a registration information management device to function as registration means for associating and registering customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation for each registration procedure indicating from the start to the end of the registration operation of a product by a customer, and transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure when the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure. A program characterized by this.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12A

Figure 12B

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Modes for Carrying Out the Invention

[0012] (Embodiment) (Network Configuration of the 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 introduced into various stores. The various stores are, for example, supermarkets, home centers, convenience stores, restaurants, various supply stores, and the like.

[0013] As shown in FIG. 1, the sales data processing system 1 includes a management server 10, a store controller 20, a transaction status management device 30, a plurality of registration devices 40, and a plurality of settlement devices 50. These devices are communicably connected via a network 60. These devices are computer devices provided with a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, and the like.

[0014] The management server 10 is an example of a registration information management device. The management server 10 is a server device provided inside or outside the store. The management server 10 includes a customer registration information DB (database) 11 (FIG. 8) and manages registration information indicating products to be purchased by each customer. Note that the customer registration information DB 11 is not limited to being provided in the management server 10 and may be provided in a device other than the management server 10.

[0015] The store controller 20 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 of the product subject to measurement, etc. for products that require measurement (products subject to measurement). In addition to the product master, the store controller 20 also stores various types of information such as inventory status, sales history, and deposit and withdrawal records. The store controller 20 may also store customer membership information.

[0016] The transaction status management device 30 displays the processing status of the registration device 40, the settlement device 50, etc., and controls the registration device 40 and the settlement device 50. For example, a store employee (monitoring store employee) is arranged at the transaction status management device 30, and the registration device 40 and the settlement device 50 are monitored by the monitoring store employee. The status of each of the registration device 40 and the settlement device 50 is displayed on the transaction status management device 30. Specifically, the transaction status management device 30 displays split screens respectively shown by the registration device 40 and the settlement device 50 to display the status of each device. The monitoring store employee supports customers operating the registration device 40 and the settlement device 50, and performs age verification when an age verification product is registered in the registration device 40.

[0017] The registration device 40 performs product registration (self-registration) by the operation of the customer. Specifically, the registration device 40 accepts a predetermined registration operation from the customer and executes a registration process for registering the product. In the registration process, registration information indicating the product purchased by the customer is generated. The registration device 40 transmits the generated registration information to the management server. The number of registration devices 40 is plural, but may also be one.

[0018] The settlement device 50 performs the settlement of goods (self - settlement) based on the operations of customers. Specifically, the settlement device 50 receives registration information from the management server 10, accepts a predetermined settlement operation from the customer, and executes a settlement process. In the settlement process, settlement information is generated. The settlement device 50 transmits the generated settlement information to the management server. Note that the number of settlement devices 50 may be multiple, but it may also be one.

[0019] Note that the sales data processing system 1 may include a store clerk terminal held by a store clerk. The store clerk terminal may display, for example, a screen similar to that of the transaction status management device 30. Also, when a store clerk is called by a customer in the registration device 40 or the settlement device 50, or when customer fraud is detected in the registration device 40 or the settlement device 50, the store clerk terminal may notify the store clerk of the fact.

[0020] (Hardware Configuration of Management Server 10) FIG. 2 is a block diagram showing an example of the hardware configuration of the management server 10. In FIG. 2, the management server 10 includes a CPU 101, a memory 102, and a communication I / F (interface) 103. Also, each part is connected by a bus 110.

[0021] The CPU 101 controls the overall operation of the management server 10. The memory 102 includes, for example, a ROM, a RAM, and a flash ROM. For example, the flash ROM and the ROM store various programs. The various programs include the registration information management program according to the present embodiment.

[0022] The RAM is used as a work area for the CPU 101. The programs stored in the memory 102 are loaded into the CPU 101 to cause the CPU 201 to execute the coded processing.

[0023] The communication I / F 103 is connected to a network 60 such as the Internet through a communication line and is connected to other devices (for example, the store controller 20, the transaction status management device 30, the registration device 40, the settlement device 50, etc.) via the network 60.

[0024] (Configuration Example of Registration Device 40) Next, the configuration of the registration device 40 will be described with reference to FIG. 3. FIG. 3 is an explanatory diagram showing an example of the configuration of the registration device 40. The registration device 40 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, an audio output unit 207, a communication unit 208, a camera 209, and a signature pole 220. These can communicate with each other via a bus (not shown).

[0025] The CPU 201 is a central processing unit, and controls the operation of the registration device 40 by reading and executing various programs stored in the ROM 202. The various programs include the registration information input program according to the present embodiment. The ROM 202 is a read-only memory, and stores various information used by the CPU 201 including various programs.

[0026] The RAM 203 is a memory that can be read from and written to, and stores various information. For example, the RAM 203 stores information acquired from the outside and information generated in the process. Also, this information includes registration information indicating registered products and customer identification information for identifying customers.

[0027] The hard disk 204 stores various information. The hard disk 204 stores, for example, imaging results (e.g., a customer's face image or a video showing the customer's actions) captured by the camera 312. The hard disk 204 may store various programs executed by the CPU 201 instead of the ROM 202, for example. Also, the hard disk 204 may store information acquired from the outside and information generated in the process instead of the RAM 203.

[0028] The customer display unit 205 is a touch display for customers. The customer display unit 205 displays various information to customers and accepts various inputs from customers. The customer display unit 205 displays product selection buttons (preset keys) corresponding to products, and accepts the registration of products when the product selection buttons are pressed.

[0029] The customer scanner unit 206 is a scanner unit for customers and optically reads various information. The various information includes, for example, product codes (barcodes) attached to products and member codes (barcodes: member information) attached to membership cards.

[0030] The audio output unit 207 outputs sound. For example, the audio output unit 310 outputs voice guidance, warning sounds, etc. The voice guidance and warning sounds are, for example, related to product registration.

[0031] The communication unit 208 is an interface for transmitting and receiving information with other devices (such as the management server 10, the store controller 20, the transaction status management device 30, the settlement device 50, etc.) via the network 60. Specifically, the communication unit 311 manages the interface between the network 60 and the internal device of itself and controls the input and output of data from other devices.

[0032] The camera 209 is attached above the customer display unit 205. The camera 209 is a camera that continuously captures videos or still images. A CCD (charge coupled device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera can be used for the camera 209. The camera 209 captures the facial images of customers and the product registration operations by customers.

[0033] The registration device 40 has a face recognition function (not shown). Specifically, the registration device 40 reads a face from an image captured by the camera 209 and identifies the customer's face based on the characteristic positions such as eyes, nose, mouth, etc., and the size of the face area. The registration device 40 can obtain the face recognition result as customer identification information.

[0034] The sign pole 220 includes a lighting unit such as an LED (light emitting diode), for example. The lighting unit lights up in a predetermined lighting mode. The lighting mode includes the lighting color and the blinking speed. The sign pole 220 notifies the store clerk of being in use, calling the store clerk, or the occurrence of an unauthorized operation by the customer according to the lighting mode.

[0035] (Configuration example of the settlement device 50) Next, the configuration of the settlement device 50 will be described with reference to FIG. 4. FIG. 4 is an explanatory diagram showing an example of the configuration of the settlement device 50. The settlement device 50 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 printing unit 307, a card payment unit 308, a change dispenser 309, an audio output unit 310, a communication unit 311, a camera 312, and a sign pole 320. These can communicate with each other via a bus (not shown).

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

[0037] The RAM 303 is a memory that can be read from and written to, and stores various information. For example, the RAM 303 stores information obtained from the outside and information generated in the process. Further, this information includes registration information generated by the registration device 40 and settlement information generated in the settlement.

[0038] The hard disk 304 stores various information. The hard disk 304 stores, for example, imaging results (e.g., a customer's face image or a video showing the customer's actions) captured by the camera 312. The hard disk 304 may store various programs executed by the CPU 301, for example, instead of the ROM 302. Further, the hard disk 304 may store information acquired from the outside or information generated in the process, instead of the RAM 303.

[0039] The customer-side display unit 305 is a touch display for customers. The customer-side display unit 305 displays various information to the customer and receives various inputs from the customer. The customer-side display unit 305 displays buttons for receiving a selection of a payment type, and receives a selection of the payment type when the button is pressed.

[0040] The customer-side scanner unit 306 is a scanner unit for customers and optically reads various information. The various information includes, for example, a product code (barcode) attached to a product or a membership code (barcode: customer identification information) attached to a membership card.

[0041] The printing unit 307 prints and outputs various media (receipts, invoices, etc.). The card payment unit 308 is a payment mechanism using various cards. The various cards include credit cards, prepaid cards such as electronic money, and also point cards.

[0042] The change machine 309 is a payment mechanism using cash. The change machine 309 is directed towards the customer side and receives various operations and cash inputs from the customer. Specifically, the change machine 309 has an inlet and an outlet for banknotes and coins. The change machine 309 calculates the amount of money inserted into the inlet, calculates the change amount which is the difference between the inserted amount and the purchase amount, and discharges the change from the outlet.

[0043] The voice output unit 310 outputs sound. For example, the voice output unit 310 outputs voice guidance, warning sounds, etc. The voice guidance and warning sounds are, for example, related to settlement.

[0044] The communication unit 311 is an interface for transmitting and receiving information with other devices (such as the management server 10, the store controller 20, the transaction status management device 30, the registration device 40, etc.) via the network 60. Specifically, the communication unit 311 manages the interface between the network 60 and the internal part of the device itself, and controls the input and output of data from other devices.

[0045] The camera 312 is attached above the customer-side display unit 305. The camera 312 is a camera that continuously captures videos or still images. A CCD camera or a CMOS camera can be used for the camera 312. The camera 312 captures the settlement operation by the customer.

[0046] The settlement device 50 has a face recognition function (not shown). Specifically, the settlement device 50 reads the face from the image captured by the camera 312, and identifies the customer's face based on the characteristic positions such as eyes, nose, mouth, etc. and the size of the face region. The settlement device 50 can obtain the face recognition result as customer identification information.

[0047] The sign pole 320 includes a lighting unit such as an LED, for example. The lighting unit lights up in a predetermined lighting mode. The lighting mode includes the lighting color and the blinking speed. The sign pole 320 notifies the store staff of its being in use, the calling of the store staff, or the occurrence of an illegal operation by the customer according to the lighting mode.

[0048] (Regarding a series of operations of the sales data processing system 1) In the sales data processing system 1 according to the present embodiment, a customer registers a product in the registration device 40, and the customer performs settlement in the settlement device 50. Hereinafter, with reference to FIG. 5, a series of operations of the sales data processing system 1 will be described.

[0049] FIG. 5 is a sequence diagram showing an example of a series of operations of the sales data processing system 1. Step S501: When the registration device 40 receives a predetermined operation indicating the start of a transaction (product registration), it acquires customer identification information (hereinafter referred to as "customer ID (Identification)"). The customer ID is information that can uniquely identify a customer, and for example, it is the face recognition result of the customer who performs the product registration operation. The customer ID is obtained based on the imaging result of the camera 209.

[0050] Step S502: When the registration device 40 receives a registration operation from the customer, it inputs registration information indicating the product to be registered. When the input of the registration information is completed, the registration device 40 generates customer registration information associating the customer ID with the registration information. Note that the order of the process in Step S501 and the process in Step S502 is not limited. That is, the input of the registration information may be performed first, and the acquisition of the customer ID may be performed later.

[0051] Step S503: When the input of the registration information is completed, the registration device 40 generates customer registration information associating the customer ID with the registration information. The registration device 40 transmits the generated customer registration information to the management server 10. Step S504: When the management server 10 receives the customer registration information from the registration device 40, it stores the received customer registration information in the customer registration information DB 11.

[0052] After the customer completes the input of the registration information, the customer moves to the settlement device 50. Step S505: When the settlement device 50 receives a settlement start operation from the customer, it captures an image of the customer's face with the camera 312, and acquires a customer ID (face recognition result) based on the imaging result of the camera 312. The customer ID may be identification information associated with the face recognition result, or may be the face image data itself, or may be a part of the data obtained from the face image. Step S506: When the settlement device 50 acquires the customer ID, it makes a transmission request to the management server 10 regarding the registration information of the customer. The transmission request includes the customer ID.

[0053] Step S507: When the management server 10 receives a transmission request from the settlement device 50, it identifies the registration information based on the transmission request. Specifically, the management server 10 identifies the customer ID that matches the customer ID included in the transmission request among the customer IDs stored in the customer registration information DB11. Further, the management server 10 identifies the registration information associated with the identified customer ID.

[0054] Step S508: The management server 10 transmits the identified registration information to the settlement device 50. Step S509: When the settlement device 50 receives the registration information from the management server 10, it performs settlement based on the registration information. When the settlement is completed, a series of transactions is completed. As described above, in the sales data processing system 1 according to the present embodiment, self-registration by the customer is performed in the registration device 40, and self-settlement by the customer is performed in the settlement device 50.

[0055] (In the case of wishing to add registration) Here, the customer may wish to add registration when, for example, they notice they have forgotten to register a product after the registration of the product is completed, or when they notice a product that has been forgotten to be registered (scanned) in the shopping cart. If separate settlements are performed for the product for which additional registration is desired and the product for which the registration procedure has been completed previously, it will take time for the settlement. Therefore, not only is it troublesome for the customer, but it may also lead to a decrease in the operation efficiency of the settlement device 50, and there is a risk that transactions cannot be carried out efficiently.

[0056] Therefore, in the present embodiment, the product for which additional registration is desired and the product for which the registration procedure has been completed previously can be processed in a single settlement procedure so that transactions can be carried out efficiently. Hereinafter, the outline of the sales data processing system 1 according to the present embodiment will be described with reference to FIG. 6.

[0057] (Outline of the sales data processing system 1 according to the embodiment) FIG. 6 is an explanatory diagram showing a schematic flow of the sales data processing system 1 according to the embodiment. Step S601: When the registration device 40 receives a predetermined operation indicating the start of a transaction (product registration), it generates a new transaction ID (transaction identification information for identifying the transaction) and acquires the customer ID. Note that the transaction ID may be generated by the management server 10 and transmitted from the management server 10 to the registration device 40.

[0058] Step S602: The registration device 40 inputs registration information by receiving a product registration operation by the customer. The registration information includes the transaction ID. When the input of the registration information is completed, the registration device 40 generates customer registration information associating the customer ID with the registration information, and transmits the customer registration information to the management server 10.

[0059] Step S603: When the management server 10 receives the customer registration information from the registration device 40, it stores the received customer registration information in the customer registration information DB 11. Note that when the registration device 40 transmits the customer registration information to the management server 10, it displays a standby screen and accepts product registration by other customers.

[0060] After this, there may be cases where the customer wishes to perform additional registration, such as when the customer notices that they have forgotten to buy a product, or when they notice a product that has been forgotten to be registered (scanned) in the shopping cart. In the present embodiment, the processing after Step S604 can be executed before the settlement of the previously registered products.

[0061] Step S604: The customer goes to the sales floor to pick up the product for which additional registration is desired, and then returns to any registration device 40 with the product to be additionally registered. If the period from the completion of the previous registration procedure to the start of the subsequent registration procedure is within a predetermined period, the registration device 40 receives a predetermined operation indicating the start of a transaction (product registration) related to the subsequent registration procedure. Then, the registration device 40 acquires the customer ID from the imaging result of the customer's face image again, and generates a new transaction ID related to the subsequent registration procedure.

[0062] Step S605: If the period from the completion of the previous registration procedure to the start of the subsequent registration procedure is equal to or longer than a predetermined period, the registration device 40 performs a clerk call process. As a result, the monitoring clerk can go to the registration device 40 and confirm the products related to the previous registration procedure and the products related to the additional registration to be registered next. When the confirmation by the clerk is completed, product registration as shown in Step S606 becomes possible.

[0063] Step S606: The registration device 40 receives the product registration operation by the customer again to input registration information. When the input of the registration information is completed, the registration device 40 generates customer registration information associating the customer ID related to the subsequent registration procedure with the registration information, and transmits it to the management server 10.

[0064] Step S607: When the management server 10 receives the customer registration information from the registration device 40, it stores the received customer registration information in the customer registration information DB11. Since the transaction ID of the customer registration information related to the subsequent registration procedure is different from the transaction ID of the customer registration information related to the previous registration procedure, each registration information will be stored separately.

[0065] Step S608: When the customer completes the input of product information (product registration), the customer moves to the payment device 50.

[0066] Step S609: The payment device 50 acquires the customer ID and makes a transmission request for the registration information. The management server 10 identifies the customer registration information by identifying the customer ID that matches the customer ID included in the transmission request. The identified customer registration information is the customer registration information related to a plurality of registration procedures or the customer registration information related to one registration procedure. The customer registration information related to a plurality of registration procedures includes the customer registration information related to the subsequent registration procedure and the customer registration information related to the previous registration procedure. The management server 10 further identifies (extracts) the registration information from the identified customer registration information and transmits the registration information to the payment device 50.

[0067] Step S610: When the settlement device 50 acquires registration information related to one or more registration procedures from the management server 10, the settlement device 50 performs settlement related to one settlement procedure based on the acquired registration information.

[0068] As described above, in the sales data processing system 1 according to the present embodiment, even after the registration of a product is completed, it is possible to add a product, and it is possible to perform settlement for the newly added product and the product related to the previous registration procedure in one settlement procedure.

[0069] (Functional configuration of the sales data processing system 1) Next, the functional configuration of the sales data processing system 1 according to the present embodiment will be described. FIG. 7 is an explanatory diagram showing an example of the functional configuration of the sales data processing system 1. As shown in FIG. 7, the management server 10 includes functional units such as a registration unit 701 and a transaction control unit 702. Each functional unit is realized by the CPU 101. That is, by the CPU 101 executing the registration information management program according to the present embodiment, each functional unit is realized.

[0070] The registration device 40 includes a customer ID acquisition unit 711, an input unit 712, and a call processing unit 713. Each functional unit is realized by the CPU 201. That is, by the CPU 201 executing the registration information input program according to the present embodiment, each functional unit is realized.

[0071] The settlement device 50 includes a customer ID acquisition unit 721, a request unit 722, a settlement unit 723, and a selection unit 724. Each functional unit is realized by the CPU 301. That is, by the CPU 301 executing the settlement processing program according to the present embodiment, each functional unit is realized.

[0072] (Customer ID acquisition unit 711: Registration device 40) The customer ID acquisition unit 711 includes a face recognition unit (not shown), and performs face recognition of a customer who performs a product registration operation based on the imaging result of the camera 209. The customer ID acquisition unit 711 acquires an identification ID (customer identification information) indicating the face recognition result. The customer ID acquisition unit 711 acquires a customer ID for each registration procedure. The registration procedure refers to the period from the start to the end of the product registration process (registration operation) (completion of input of product information).

[0073] Note that the customer ID does not have to be limited to the face recognition result, and any information that can uniquely identify the customer is acceptable. For example, the customer ID may be any one of membership information, My Number card information, and driver's license information. That is, the customer ID may be information stored in an information storage medium such as various cards. In this case, the customer ID acquisition unit 711 may acquire the customer ID when information (such as a barcode) attached to the information storage medium is read by the customer-side scanner unit 206.

[0074] Note that the face recognition unit does not have to be provided in the registration device 40, and may be provided in another device or the management server 10. In this case, the face recognition unit provided in another device or the management server 10 may acquire the imaging result from the registration device 40 and perform face recognition based on the acquired imaging result. And in this case, the customer ID acquisition unit 711 may acquire the customer ID from the face recognition unit provided in another device or the management server 10.

[0075] (Input unit 712: Registration device 40) The input unit 712 of the registration device 40 inputs registration information by a customer's operation. Specifically, the input unit 712 inputs registration information indicating the product when a product selection button displayed on the customer-side display unit 205 is pressed or when a product code is read by the customer-side scanner unit 206. The registration device 40 generates customer registration information in which the registration information input to the input unit 712 is associated with the customer ID acquired by the customer ID acquisition unit 711. When the input of the registration information is completed, the registration device 40 transmits the customer registration information to the management server 10.

[0076] (Registration Department 701: Management Server 10) The registration department 701 registers the customer registration information transmitted from the registration device 40 in the customer registration information DB11. Note that the association between the customer ID and the registration information is not limited to being performed by the registration device 40, and may also be performed by the registration department 701 (management server 10).

[0077] (Customer Registration Information DB11 According to the Embodiment) FIG. 8 is a diagram showing an example of the customer registration information stored in the customer registration information DB11 according to the embodiment. As shown in FIG. 8, the customer registration information DB11 includes items of "customer ID", "registration information", and "settlement completion flag". The registration information includes items of "transaction ID", "registration date and time", "product code", "product name", "quantity", and "selling price". Note that the registration information includes product information ( "product code", "product name", "selling price") indicating each product. When information is input into each item, the customer registration information is stored as a record.

[0078] Note that in the illustration, the settlement completion flag shows an example stored in the customer registration information DB11, but it is not limited to this. The settlement completion flag may be stored in a storage unit different from the customer registration information DB11. In other words, the customer registration information DB11 only needs to store at least the customer registration information.

[0079] The "transaction ID" indicates identification information for identifying the registration procedure. The "registration date and time" is the date and time when the product was registered. The "registration date and time" is, for example, the date and time when the registration was completed, but it may also be the start date and time of the registration. Although not shown, the customer registration information DB11 also stores the date and time when the settlement was completed. The "product code" indicates identification information for identifying the product. The "product name" indicates the name of the product. The "quantity" indicates the quantity of the registered product. The "selling price" indicates the unit price of the product. The "settlement completed flag" is a flag indicating whether the settlement of the product shown in the registration information has been completed. The "settlement completed flag" is set to OFF when the settlement is not completed, and set to ON when the settlement is completed.

[0080] For example, in the illustration, the customer registration information 800a indicates that the "I1001" of the customer ID 801a is associated with the registration information 802a, and also indicates that the settlement has not been completed. In this way, the customer registration information DB11 stores by associating the un-settled registration information, the customer ID, and the transaction ID (registration identification information).

[0081] (Regarding the acquisition of the customer ID in the subsequent registration procedure) After the registration of the registration information related to the previous registration procedure is completed, the customer ID acquisition unit 711 acquires the customer ID (face recognition result) of the customer who performs the registration operation of the product in the subsequent registration procedure. The subsequent registration procedure is a registration procedure performed before the start of the settlement based on the registration information related to the previous registration procedure. The subsequent registration procedure is a registration procedure on the same day (the current day) as the previous registration procedure.

[0082] (Regarding the input of the registration information in the subsequent registration procedure) Next, the customer registration information related to the subsequent registration procedure will be described. After the registration of the registration information related to the previous registration procedure is completed, the input unit 712 inputs the registration information by the operation of the customer in the subsequent registration procedure.

[0083] Note that in the subsequent registration procedure, either the input of the registration information or the acquisition of the customer ID may be performed first. The registration device 40 generates customer registration information associating the customer ID related to the subsequent registration procedure with the registration information related to the subsequent registration procedure, and transmits the customer registration information to the management server 10.

[0084] (Registration of the customer registration information in the subsequent registration procedure) The registration unit 701 registers the customer registration information related to subsequent registration procedures received from the registration device 40 in the customer registration information DB11. The registration unit 701 registers the registration information including the transaction ID generated for each registration procedure. Among the customer registration information, the transaction IDs attached to the registration information are different from each other. Therefore, in subsequent registration procedures, the registration unit 701 registers the registration information including a transaction ID different from the transaction ID related to the previous registration procedure. In other words, regardless of whether the customer ID related to the previous registration procedure matches the customer ID related to the subsequent registration procedure, customer registration information is registered separately in each registration procedure.

[0085] For example, as shown in FIG. 8, the customer registration information 800a and 800b indicates that the customer IDs 801a and 801b are the same, that is, they are registration information of the same person. The transaction IDs of the registration information 802a and 802b are different from each other. In this way, even if the customers who have performed the registration operation are the same person, the registration unit 701 separately registers the customer registration information 800a (registration information 802a) related to the previous registration procedure and the customer registration information 800b (registration information 802b) related to the subsequent registration procedure. In other words, when there are a plurality of transaction IDs 801 associated with the customer registration information 800 and stored, the management server 10 can sum up the plurality of transaction IDs 801 (registration information 802).

[0086] (Customer ID acquisition unit 721: Settlement device 50) The customer ID acquisition unit 721 includes a face recognition unit (not shown) and performs face recognition of the customer who performs the settlement operation based on the imaging result of the camera 312. The customer ID acquisition unit 721 acquires the customer ID indicating the face recognition result. The customer ID acquisition unit 721 outputs the acquired customer ID to the request unit 722.

[0087] (Request unit 722: Settlement device 50) When the request unit 722 acquires the customer ID from the customer ID acquisition unit 721, it makes a request to the management server 10 (transaction control unit 702) to transmit the registration information. The transmission request includes the customer ID acquired by the customer ID acquisition unit 721.

[0088] Note that the face recognition unit is not limited to being provided in the settlement device 50, and may be provided in other devices or the management server 10. In this case, the face recognition unit provided in other devices or the management server 10 may acquire the imaging result from the settlement device 50 and perform face recognition based on the acquired imaging result. And in this case, the request unit 722 may acquire the customer ID from the face recognition unit provided in other devices or the management server 10.

[0089] (Transaction control unit 702: Management server 10) The transaction control unit 702 determines whether the customer ID related to the previous registration procedure matches the customer ID related to the subsequent registration procedure. If they match in this determination, the transaction control unit 702 enables settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure. Specifically, the transaction control unit 702 specifies the customer ID that matches the customer ID of the customer who performs the settlement operation from among the customer IDs stored in the customer registration information DB 11. Further, the transaction control unit 702 specifies the registration information associated with the specified customer ID.

[0090] When additional registration is performed, the specified registration information is, for example, registration information associated with different transaction IDs respectively, that is, registration information related to a plurality of registration procedures. Note that when no additional registration is performed, the specified registration information is registration information with a single transaction ID attached, that is, registration information related to a single registration procedure.

[0091] In FIG. 8, the customer registration information 800a and 800b are customer registration information related to a plurality of registration procedures. For example, when the customer ID included in the transmission request is "I1001", the transaction control unit 702 specifies the customer IDs 801a and 801b ("I1001") related to a plurality of registration procedures among the customer registration information 800 stored in the customer registration information DB 11. And the transaction control unit 702 specifies the registration information 802a and 802b (registration information related to a plurality of registration procedures) associated with the specified customer IDs 801a and 801b.

[0092] In FIG. 8, the customer registration information 800c is the customer registration information related to one registration procedure. When the customer ID included in the transmission request is "I5621", the transaction control unit 702 identifies the customer ID 801c ("I5621") among the customer registration information 800 stored in the customer registration information DB 11. Then, the transaction control unit 702 identifies the registration information 802c (registration information related to one registration procedure) associated with the identified customer ID 801c.

[0093] The transaction control unit 702 transmits the registration information related to the identified one or more registration procedures to the settlement device 50. Thereby, the transaction control unit 702 can perform settlement in one settlement procedure based on the registration information related to the one or more registration procedures.

[0094] (Settlement unit 723: Settlement device 50) The settlement unit 723 performs settlement based on the registration information received in response to the transmission request of the request unit 722. For example, when the settlement unit 723 receives the registration information related to a plurality of registration procedures, the settlement unit 723 performs settlement for the registration information related to the plurality of registration procedures in one settlement procedure. One settlement procedure refers to from the start to the end of the settlement operation.

[0095] For example, the settlement performed for the registration information related to a plurality of registration procedures in one settlement procedure is the settlement performed by displaying the registration information 802a and the registration information 802b on the same screen. Note that when there is no additional registration, the settlement unit 723 receives the registration information related to one registration procedure and performs settlement (normal settlement process) based on the registration information related to one registration procedure.

[0096] (Selection unit 724: Settlement device 50) The selection unit 724 selects whether to total the registration information related to a plurality of registration procedures based on the registration information received from the management server 10 in response to the transmission request of the request unit 722. Specifically, when the selection unit 724 receives the registration information related to a plurality of registration procedures from the management server 10, the selection unit 724 makes the above selection. In the above selection, the selection unit 724 displays a predetermined selection screen, for example, to accept from the customer whether to total the registration information related to a plurality of registration procedures.

[0097] When it is selected on the selection screen to sum up, the actuarial department 723 will perform a combined actuarial calculation on the registration information related to multiple registration procedures. Specifically, the actuarial department 723 accepts the selection of one settlement type and issues one receipt. On the other hand, when it is selected on the selection screen not to sum up, the actuarial department 723 will execute separate actuarial processes on the registration information related to multiple registration procedures. Specifically, for each of the multiple registration procedures, the actuarial department 723 accepts the selection of the settlement type respectively and issues separate receipts. Note that the selection unit 724 may automatically make the selection not only according to the customer's selection but also according to a preset setting.

[0098] (Allowance or Prohibition of Additional Registration: Registration Device 40) Here, in the case where the customer notices a product that has been forgotten to be registered (scanned) in the shopping cart, etc., the customer may want to perform additional registration immediately. Therefore, if it is within a predetermined period after the previous registration procedure is completed, the input unit 712 enables the input of the registration information related to the subsequent registration procedure as additional registration. The conditions for enabling additional registration include the following two conditions. · The customer ID related to the previous registration procedure and the customer ID related to the subsequent registration procedure are the same. · The period from the completion of the previous registration procedure to the start of the subsequent registration procedure (hereinafter referred to as the "period until the start of additional registration") is less than the predetermined period.

[0099] On the other hand, if the period until the start of additional registration is longer than the predetermined period, the input unit 712 prohibits the input of the registration information related to the subsequent registration procedure. The release of the prohibition is to receive a predetermined operation from the store clerk. However, the release of the prohibition is not limited to this, and it may also be that the actuarial calculation related to the previous registration procedure is completed. Note that the predetermined period is a preset period and is a period that can be changed according to the setting.

[0100] (Call Processing Unit 713: Registration Device 40) If the period until the start of additional registration is equal to or longer than a predetermined period, the calling processing unit 713 performs a store clerk calling process. The store clerk calling process includes causing the customer-side display unit 205 and the sign pole 220 to output in a predetermined output mode, and causing the transaction status management device 30 to display that a store clerk is being called. Specifically, in the store clerk calling process, the customer-side display unit 205 displays a predetermined screen indicating that a store clerk is being called and the products related to the previous registration procedure. Also, in the store clerk calling process, the sign pole 220 lights up in a predetermined lighting mode indicating that a store clerk is being called. Further, the transaction status management device 30 causes the registration device 40 that is the target of the call to display that there is an additional registration.

[0101] When the store clerk calling process is performed, the monitoring store clerk who has gone to the registration device 40 checks the products related to the previous registration procedure displayed on the customer-side display unit 205 and the products held by the customer. Thereby, the monitoring store clerk can confirm that there are no mistakes regarding the products related to the previous registration procedure and the products related to the additional registration to be registered next. Thus, an appropriate transaction can be supported.

[0102] When the store clerk finishes checking the products and the registration device 40 accepts a predetermined cancellation input, the input unit 712 cancels the prohibition on input of registration information related to the subsequent registration procedure and enables the input of registration information. The predetermined cancellation input is, for example, inputting store clerk identification information for identifying the store clerk or accepting a predetermined operation indicating the cancellation of the input prohibition on the store clerk's screen.

[0103] Note that the registration device 40 may permit up to the registration completion operation without prohibiting the input of registration information. However, the registration device 40 should prohibit the transition to the settlement process. Also, in this case, the registration device 40 may impose a limit based on the previous number of product items (number of registration lines). Specifically, the registration device 40 may maintain the input prohibition when the previous number of product items is equal to or more than a predetermined number, and permit up to the registration completion operation when the number is less than the predetermined number.

[0104] (Registration information input process performed by the registration device 40 according to the embodiment) Next, with reference to FIGS. 9 to 12, various processes performed by the sales data processing system 1 according to the embodiment will be described. FIG. 9 is a flowchart showing an example of registration information input processing performed by the registration device 40 according to the embodiment. In FIG. 9, the registration device 40 determines whether it is the start of the product registration procedure (step S901). The determination in step S901 is, for example, that the start button indicating the start of product registration is pressed on a standby screen (not shown).

[0105] The registration device 40 waits until the start of the product registration procedure (step S901: NO), and when the start of the product registration procedure occurs (step S901: YES), based on the imaging result of the camera 209, it acquires the customer ID (face recognition result) of the customer who performs the registration operation in the device itself (step S902).

[0106] Next, the registration device 40 performs a transmission request process of registration information (FIG. 10) to the management server 10 (step S903). Then, the registration device 40 determines whether registration information has been input by receiving a registration operation from the customer (step S904). If the registration information is not input (step S904: NO), the registration device 40 proceeds to the process of step S906. On the other hand, if the registration information is input (step S904: YES), the registration device 40 stores the input registration information in a predetermined storage unit and displays it on the customer-side display unit 205 (step S905).

[0107] Then, the registration device 40 determines whether the registration procedure has been completed (step S906). The completion of the registration procedure is, for example, receiving the pressing of the registration completion button. If the registration procedure has not been completed (step S906: NO), the registration device 40 returns to step S904. On the other hand, if the registration procedure has been completed (step S906: YES), the registration device 40 transmits the customer registration information in which the customer ID is associated with the registration information stored in a predetermined storage unit to the management server 10 (step S907) and ends the series of processes.

[0108] (Processing related to the transmission request of registration information performed by the registration device 40 and the management server 10 according to the embodiment) FIG. 10 is a flowchart showing an example of the processing related to the transmission request of registration information performed by the registration device 40 and the management server 10 according to the embodiment. In FIG. 10, when starting the product registration related to the subsequent registration procedure, the processing including making the product related to the previous registration procedure displayable in the registration device 40 will be described.

[0109] In FIG. 10, the registration device 40 makes a transmission request for the registration information related to the previous registration procedure to the management server 10 (step S1001). The transmission request includes the customer ID. Then, regardless of whether it is an additional registration, the registration device 40 newly generates a transaction ID (step S1002) and proceeds to the processing of step S1007.

[0110] When the management server 10 receives the transmission request, it refers to the customer registration information DB11 and determines the presence or absence of a customer ID that matches the customer ID included in the transmission request (step S1003). Next, when there is no customer ID that matches the customer ID included in the transmission request (step S1004: NO), that is, when it is not an additional registration, the management server 10 ends the processing as it is. On the other hand, when there is a customer ID that matches the customer ID included in the transmission request (step S1004: YES), that is, when it is an additional registration, the management server 10 determines whether the settlement completion flag corresponding to the customer ID is OFF (whether it is unsettled) (step S1005).

[0111] If the settlement completion flag corresponding to the customer ID is not OFF (step S1005: NO), that is, if the settlement completion flag is ON (settled), the management server 10 ends the process as it is. On the other hand, if the settlement completion flag corresponding to the customer ID is OFF (step S1005: YES), that is, if it is unsettled, the management server 10 identifies the transaction ID corresponding to the customer ID. Then, the management server 10 transmits the registration information (registration information related to the previous registration procedure) with the identified transaction ID attached to the registration device 40 (step S1006) and ends the process.

[0112] The registration device 40 determines whether it has received the registration information related to the previous registration procedure from the management server 10 (step S1007). If it has not received the registration information (step S1007: NO), that is, if it is not an additional registration, the process proceeds to step S904 in FIG. 9. On the other hand, if it has received the registration information (step S1007: YES), that is, if it is an additional registration, the registration device 40 determines whether the period until the start of additional registration is within the predetermined period (less than the predetermined period) (step S1008).

[0113] If the period until the start of additional registration is within the predetermined period (step S1008: YES), the management server 10 enables the input of the registration information related to the subsequent registration procedure (step S1009), proceeds to step S1012, and displays the registration information related to the previous registration procedure. On the other hand, if the period until the start of additional registration is not within the predetermined period (step S1008: NO), the registration device 40 prohibits the input of the registration information related to the subsequent registration procedure (step S1010).

[0114] Furthermore, the registration device 40 performs a clerk call process (step S1011). After performing the clerk call process, when the registration device 40 receives a predetermined cancellation input from the clerk, it displays the registration information related to the previous registration procedure received in step S1007 (step S1012) and proceeds to the process of step S904 in FIG. 9.

[0115] Through such processing, when the registration device 40 starts product registration related to subsequent registration procedures, it becomes possible to display the previously registered products on the customer display unit 205.

[0116] (Registration information management process performed by the management server 10 according to the embodiment) FIG. 11 is a flowchart showing an example of the registration information management process performed by the management server 10 according to the embodiment. In FIG. 11, an example including the process when the management server 10 receives customer registration information from the registration device 40 and the process when the management server 10 receives a transmission request for registration information or a settlement completion notification from the settlement device 50 will be described.

[0117] In FIG. 11, the management server 10 determines whether it has received customer registration information from the registration device 40 (step S1101). If it has not received the customer registration information (step S1101: NO), the management server 10 proceeds to step S1103. On the other hand, if it has received the customer registration information (step S1101: YES), the management server 10 registers the customer registration information in the customer registration information DB 11 (step S1102).

[0118] Next, the management server 10 determines whether it has received a transmission request for registration information from the settlement device 50 (step S1103). If it has not received the transmission request for registration information from the settlement device 50 (step S1103: NO), the management server 10 proceeds to step S1110. On the other hand, if it has received the transmission request for registration information from the settlement device 50 (step S1103: YES), the management server 10 refers to the customer registration information DB 11 and determines whether there is a customer ID that matches the customer ID included in the transmission request (step S1104).

[0119] And when there is no customer ID that matches the customer ID included in the transmission request (step S1105: NO), the management server 10 proceeds to the process of step S1110. On the other hand, when there is a customer ID that matches the customer ID included in the transmission request (step S1105: YES), the management server 10 determines whether all the settlement completion flags associated with the customer ID are ON (whether the settlement has been completed) (step S1106).

[0120] When all the settlement completion flags associated with the customer ID are ON (step S1106: YES), that is, when the settlement has been completed, the management server 10 proceeds to the process of step S1110. On the other hand, when not all the settlement completion flags associated with the customer ID are ON (step S1106: NO), that is, when there is at least one uncompleted registration procedure, the management server 10 determines whether there are multiple uncompleted registration procedures (step S1107). Note that specifically, having multiple uncompleted registration procedures means that a plurality of transaction IDs corresponding to the customer ID are stored.

[0121] When there are not multiple uncompleted registration procedures (step S1107: NO), the registration information related to one registration procedure is transmitted to the settlement device 50 (step S1108). On the other hand, when there are multiple uncompleted registration procedures (step S1107: YES), the registration information related to the multiple registration procedures is transmitted to the settlement device 50 (step S1109).

[0122] Next, the management server 10 determines whether it has received a settlement completion notice indicating that the settlement has been completed from the settlement device 50 (step S1110). The settlement completion notice includes the customer ID. When the settlement completion notice is not received (step S1110: NO), the management server 10 ends the series of processes. On the other hand, when the settlement completion notice is received (step S1110: YES), the management server 10 sets the settlement completion flag corresponding to the customer ID included in the settlement completion notice to ON (step S1111) and ends the series of processes.

[0123] (Settlement process performed by the settlement device 50 according to the embodiment) FIG. 12A is a flowchart showing an example of the settlement process performed by the settlement device 50 according to the embodiment. The process shown in FIG. 12A shows an example of enabling settlement in one settlement procedure when registration information related to a plurality of registration procedures is received.

[0124] In FIG. 12A, the settlement device 50 determines whether it is the start of the settlement procedure (step S1201). The determination in step S1201 is that a start button indicating the start of settlement is pressed on a standby screen (not shown).

[0125] The settlement device 50 waits until the start of the settlement procedure (step S1201: NO), and when the settlement procedure starts (step S1201: YES), based on the imaging result of the camera 312, it acquires the customer ID (face recognition result) of the customer who performs the settlement operation by itself (step S1202). Then, the settlement device 50 makes a transmission request for registration information including the customer ID to the management server 10 (step S1203).

[0126] Then, the settlement device 50 determines whether it has received the registration information (step S1204). If it has not received the registration information (step S1204: NO), that is, if there is no registration information corresponding to the customer ID acquired in step S1202, the settlement device 50 ends the process as it is. On the other hand, if it has received the registration information (step S1204: YES), the settlement device 50 determines whether the received registration information is registration information related to a plurality of registration procedures (step S1205).

[0127] If the received registration information does not pertain to registration information for multiple registration procedures (step S1205: NO), that is, if it is registration information for a single registration procedure, the settlement device 50 executes normal settlement processing for the single registration procedure (step S1206) and proceeds to the processing of step S1211. On the other hand, if the received registration information pertains to registration information for multiple registration procedures (step S1205: YES), the settlement device 50 displays a selection screen on the customer-side display unit 305 for receiving a selection as to whether to total the registration information for the multiple registration procedures (step S1207).

[0128] (Example of a selection screen) Here, with reference to FIG. 12B, an example of a selection screen for receiving a selection as to whether to total the registration information for multiple registration procedures will be described. FIG. 12B is a diagram showing an example of a selection screen for receiving a selection as to whether to total the registration information for multiple registration procedures. In FIG. 12B, the selection screen 1220 includes a total button 1221, a separate accounting button 1222, and a clerk call button 1223.

[0129] The total button 1221 accepts the instruction to total. The separate accounting button 1222 accepts the instruction not to total (to perform separate accounting). The clerk call button 1223 accepts the call for a clerk.

[0130] If, on the selection screen 1220, the instruction to total (total button 1221) is accepted (step S1208: YES), the settlement device 50 totals the registration information for the multiple registration procedures and performs settlement processing (step S1209), and proceeds to the processing of step S1211. On the other hand, if, on the selection screen 1220, the instruction not to total (separate accounting button 1222) is accepted (step S1208: NO), the settlement device 50 performs separate settlement processing for the registration information for the multiple registration procedures (step S1210). Then, the settlement device 50 transmits a settlement completion notice indicating the registration information for which settlement processing has been performed to the management server 10 (step S1211), and ends the series of processing.

[0131] As described above, the management server 10 according to the present embodiment registers by associating a customer ID with registration information for each registration procedure. Further, when the customer ID related to the previous registration procedure matches the customer ID related to the subsequent registration procedure, the management server 10 enables settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure. Thereby, for the additionally registered product (the product related to the subsequent registration procedure) and the previously registered product (the product related to the previous registration procedure), settlement can be performed by a single settlement procedure. Specifically, after the registration of the product related to the previous registration procedure is completed, if the customer notices that they have forgotten to register a product or have forgotten to register (scan) the products in the shopping cart, etc., the customer can perform additional registration of the product, and for the additionally registered product and the previously registered product, settlement can be performed by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the hassle of settlement for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0132] Note that when a customer wishes to return a product, they cannot return it by their own operation. Specifically, when a customer wishes to return a product, the customer presses the clerk call button to call a clerk. The return is performed based on the operation of the clerk. The clerk call may be performed on the registration device 40 or the settlement device 50. In other words, the clerk call button may be displayed on at least one of the registration device 40 and the settlement device 50.

[0133] Further, the management server 10 according to the present embodiment registers registration information including a transaction ID generated for each registration procedure, and in a subsequent registration procedure, registers registration information including a transaction ID different from the transaction identification information related to the previous registration procedure. As a result, in the additional registration of products, it is possible to register products by newly attaching a transaction ID to the registration information in the same manner as the registration information of normal products. Also, it is possible to settle the registration information related to a plurality of registration procedures by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the hassle of settlement for customers, suppress a decrease in the operation efficiency of the settlement device 50, and conduct transactions efficiently.

[0134] In addition, when the customer ID related to the previous registration procedure matches the customer ID related to the subsequent registration procedure, the registration device 40 according to the present embodiment enables the input of the registration information related to the subsequent registration procedure when the period until the start of additional registration is less than a predetermined period. Also, the registration device 40 prohibits the input of the registration information related to the subsequent registration procedure when the period until the start of additional registration is longer than a predetermined period. As a result, when the period until the start of additional registration is less than a predetermined period, that is, for example, when a customer notices a product that has been forgotten to be registered (scanned) in the shopping cart, the customer can immediately perform additional registration. On the other hand, when the period until the start of additional registration is longer than a predetermined period, by prohibiting additional registration, for multiple registration procedures by the same person, a store clerk can confirm that there are no mistakes regarding the products related to the previous registration procedure and the products related to the additional registration to be performed next, and prevent multiple registration procedures by the same person. Therefore, it is possible to support appropriate transactions.

[0135] In addition, when the period until the start of additional registration is longer than a predetermined period, the registration device 40 according to the present embodiment performs a process of calling a store clerk. As a result, the store clerk can confirm that there are no mistakes regarding the products related to the previous registration procedure and the products related to the additional registration to be performed next. Therefore, it is possible to support appropriate transactions.

[0136] In addition, the settlement device 50 according to the present embodiment acquires the customer ID of a customer who performs a settlement operation, and based on the acquired customer ID, makes a transmission request for registration information to the management server 10. Then, when the registration information received from the management server 10 in response to the transmission request is registration information related to a plurality of registration procedures, the settlement device 50 selects whether to sum up the registration information related to the plurality of registration procedures, and performs settlement based on the result of the selection. Thereby, in one settlement procedure for the product related to the subsequent registration procedure and the product related to the previous registration procedure, it is possible to perform an optimal settlement according to the customer's request. For example, when receiving a shopping request from an acquaintance, settlement can be performed without summing up, and when adding registration for one's own shopping, settlement can be performed by summing up. Furthermore, since one settlement procedure is performed and settlement can be performed quickly, it is possible to reduce the annoyance for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0137] (Modification of the embodiment) Next, a modification of the embodiment will be described. In the following modifications, the description of the content described in the above-described embodiment will be omitted as appropriate. Also, it is possible to combine the following modifications and the above-described embodiment respectively.

[0138] (Modification 1) In the above-described embodiment, an example in which different transaction IDs are assigned to the registration information of the product to be additionally registered and the registration information of the product registered previously has been described. In Modification 1, an example in which the registration information related to the subsequent registration procedure and the registration information related to the previous registration procedure are registered (additionally registered) with the same transaction ID will be described. As shown in the embodiment, the mode of using different transaction IDs for each registration procedure and the mode of using the same registration ID in a plurality of registration procedures as shown in Modification 1 may be switchable according to a preset setting or the selection of a store clerk.

[0139] (Outline of the sales data processing system 1 according to Modification 1) First, the outline of the sales data processing system 1 according to Modification 1 will be described. FIG. 13 is an explanatory diagram showing a schematic flow of the sales data processing system 1 according to Modification 1. Hereinafter, mainly, steps S1301 to S1303 will be described.

[0140] Step S1301: When the customer returns to any of the registration devices 40, if the previous registration procedure has been completed and it is within a predetermined period, the registration device 40 accepts a predetermined operation indicating the start of a transaction (product registration) related to the subsequent registration procedure as it is. Specifically, the registration device 40 acquires a customer ID related to the subsequent registration procedure.

[0141] Step S1302: Next, if the customer ID related to the previous registration procedure and the customer ID related to the subsequent registration procedure are the same and the period until the start of additional registration is less than the predetermined period, the registration device 40 acquires the transaction ID related to the previous registration procedure. Then, the registration device 40 accepts the customer's product registration operation again, and inputs the registration information as the same transaction ID as the transaction ID related to the previous registration procedure. When the input of the registration information is completed, the registration device 40 generates customer registration information associating the customer ID and the registration information, and transmits the generated customer registration information to the management server 10.

[0142] Step S1303: When the management server 10 receives the customer registration information from the registration device 40 again, it stores the received customer registration information in the customer registration information DB 11a (FIG. 14). Note that the transaction ID of the customer registration information related to the subsequent registration procedure and the transaction ID of the customer registration information related to the previous registration procedure are the same. For this reason, the customer registration information related to the subsequent registration procedure and the customer registration information related to the previous registration procedure are stored with the same transaction ID.

[0143] (Regarding the functional configuration of the management server 10 according to Modification 1) Next, with reference to FIG. 7, the functional configuration of the management server 10 according to Modification 1 will be described. In Modification 1, the registration unit 701 identifies a customer ID that matches the customer ID related to the previous registration procedure in a subsequent registration procedure. Then, the registration unit 701 transmits the identified customer ID related to the previous registration procedure to the registration device 40. In the registration device 40, the registration information related to the subsequent registration procedure is associated with the transaction ID related to the previous registration procedure. As a result, the registration unit 701 can register the registration information of the product to be additionally registered and the registration information of the products related to the previous and subsequent registration procedures with the same transaction ID. In addition, the registration unit 701 sets ON a flag (additional flag) indicating that it is an additional registration in the registration information of the product to be additionally registered.

[0144] The transaction control unit 702 enables settlement based on the registration information. The registration information is the registration information related to the previous registration procedure and the subsequent registration procedure, and specifically, is the registration information associated with a customer ID that matches the customer ID of the customer who performs the settlement operation. The transaction control unit 702 identifies a customer ID that matches the customer ID of the customer who performs the settlement operation from among the customer IDs stored in the customer registration information DB 11a. Further, the transaction control unit 702 identifies the registration information associated with the identified customer ID.

[0145] The identified registration information is the registration information associated with one transaction ID regardless of the presence or absence of additional registration. In addition, a flag (additional flag) indicating that it is an additional registration is set ON in the registration information of the additionally registered product.

[0146] The settlement unit 723 receives, from the management server 10, the registration information related to a plurality of registration procedures associated with one transaction ID, and performs settlement in one settlement procedure based on the registration information.

[0147] When the registration information received from the management server 10 includes registration information with the additional flag set ON, the selection unit 724 selects whether to sum up the registration information related to a plurality of registration procedures.

[0148] As described above, in Modification 1, when there is registration information (unsettled data) related to the input customer ID in the registration unit 701, the registration unit 701 adds the registration information. On the other hand, when there is no unsettled data, a new transaction ID (transaction identification information) is generated, and product information is registered corresponding to the generated transaction ID.

[0149] (Customer registration information DB11a according to Modification 1) FIG. 14 is a diagram showing an example of customer registration information stored in the customer registration information DB11a according to Modification 1. As shown in FIG. 14, the customer registration information DB11a includes an item of "addition flag" in addition to the items of the customer registration information DB11 shown in the embodiment. When information is input into each item, the customer registration information according to Modification 1 is stored as a record.

[0150] The "addition flag" is a flag indicating that additional registration has been performed. The "addition flag" is set to ON in the case of an additionally registered product, and is set to OFF in the case of a product that has not been additionally registered.

[0151] For example, in the illustration, the customer registration information 1400a shows that a plurality of registration information 1402a and 1402b are associated with one customer ID 1401a which is "I1001". Also, the registration information 1402a has the addition flag set to OFF, that is, it indicates that it is not an additionally registered product. The registration information 1402b has the addition flag set to ON, that is, it indicates that it is an additionally registered product.

[0152] (Processing related to the transmission request of registration information performed by the registration device 40 and the management server 10 according to Modification 1) FIG. 15 is a flowchart showing an example of processing related to the transmission request of registration information performed by the registration device 40 and the management server 10 according to Modification 1. Hereinafter, mainly, the processing of step S1501 and step S1502 will be described.

[0153] In step S1007 of FIG. 15, the registration device 40 determines whether it has received registration information related to the previous registration procedure from the management server 10 (step S1007). If the registration information is not received (step S1007: NO), that is, if it is not an additional registration, a new transaction ID is generated (step S1502), and the process proceeds to step S904 of FIG. 9.

[0154] On the other hand, if the registration information is received (step S1007: YES), that is, if it is an additional registration, the registration device 40 acquires the transaction ID associated with the received registration information (the transaction ID related to the previous registration procedure) (step S1501), and the process proceeds to step S1008. Thereby, the registration device 40 can generate customer registration information by associating the transaction ID related to the previous registration procedure with the registration information of the product to be additionally registered.

[0155] (Registration Information Management Process Performed by the Management Server 10 According to Modification Example 1) FIG. 16 is a flowchart showing an example of the registration information management process performed by the management server 10 according to Modification Example 1. In FIG. 16, the management server 10 determines whether it has received customer registration information from the registration device 40 (step S1601). If the customer registration information is not received (step S1601: NO), the management server 10 proceeds to step S1606. On the other hand, if the customer registration information is received (step S1601: YES), the management server 10 registers the customer registration information in the customer registration information DB11a (step S1602).

[0156] Then, the management server 10 refers to the customer registration information DB11a and determines the presence or absence of a customer ID that matches the customer ID included in the customer registration information (step S1603). And if there is no customer ID that matches the customer ID included in the customer registration information in the registration device 40 (step S1604: NO), the management server 10 proceeds to the process of step S1606. On the other hand, if there is a customer ID that matches the customer ID included in the transmission request (step S1604: YES), the management server 10 sets the additional flag of the received customer registration information to ON (step S1605).

[0157] Next, the management server 10 determines whether it has received a transmission request for registration information from the settlement device 50 (step S1606). If the management server 10 has not received a transmission request for registration information from the settlement device 50 (step S1606: NO), it proceeds to step S1611. On the other hand, if the management server 10 has received a transmission request for registration information from the settlement device 50 (step S1606: YES), it refers to the customer registration information DB 11a and determines whether there is a customer ID that matches the customer ID included in the transmission request (step S1607).

[0158] Then, if there is no customer ID that matches the customer ID included in the transmission request (step S1608: NO), the management server 10 proceeds to the process of step S1611. On the other hand, if there is a customer ID that matches the customer ID included in the transmission request (step S1608: YES), the management server 10 determines whether the settlement completion flag associated with the customer ID is ON (i.e., whether the settlement has been completed) (step S1609).

[0159] If the settlement completion flag associated with the customer ID is ON (step S1609: YES), that is, if the settlement has been completed, the management server 10 proceeds to the process of step S1611. On the other hand, if the settlement completion flag associated with the customer ID is not ON (step S1610: NO), that is, if the settlement has not been completed, the management server 10 transmits the registration information associated with the customer ID to the settlement device 50 (step S1610). Note that, in the transmission of the registration information, information indicating an additional flag associated with the registration information is also transmitted.

[0160] Next, the management server 10 determines whether it has received a settlement completion notification indicating that the settlement has been completed from the settlement device 50 (step S1611). The settlement completion notification includes a transaction ID. If the settlement completion notification is not received (step S1611: NO), the management server 10 ends the series of processes. On the other hand, if the settlement completion notification is received (step S1611: YES), the management server 10 sets the settlement completion flag corresponding to the transaction ID included in the settlement completion notification to ON (step S1612) and ends the series of processes.

[0161] (Settlement process performed by the settlement device 50 according to Modification 1) FIG. 17 is a flowchart showing an example of the settlement process performed by the settlement device 50 according to Modification 1. Hereinafter, mainly, the process of step S1701 will be described. In step S1204 of FIG. 17, the settlement device 50 determines whether it has received registration information by sending a request for registration information (step S1204). In step S1204, information on an additional flag associated with the registration information is also received together with the registration information.

[0162] When the settlement device 50 receives the registration information from the management server 10 (step S1204: YES), it determines whether the additional flag associated with the received registration information is ON (step S1701). If the additional flag is OFF (step S1701: NO), that is, if the registration information related to one registration procedure is received in step S1204, the settlement device 50 executes the normal settlement process related to one registration procedure (step S1206) and ends the series of processes. On the other hand, if the additional flag is ON (step S1701: YES), that is, if the registration information related to a plurality of registration procedures is received in step S1204, the settlement device 50 displays a selection screen on the customer-side display unit 305 for accepting a selection as to whether to total the registration information related to the plurality of registration procedures (step S1207).

[0163] As described above, the management server 10 according to Modification 1 associates and registers a customer ID that matches the customer ID related to the previous registration procedure with the registration information related to the subsequent registration procedure in the subsequent registration procedure. As a result, in the additional registration of products, even if a new transaction ID is not generated in the registration information, the transaction ID related to the previous registration procedure can be attached to and registered in the registration information related to the subsequent registration procedure. In addition, the registration information related to a plurality of registration procedures can be settled by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the annoyance of settlement for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0164] (Modification 2) Next, Modification 2 will be described. In Modification 2, an example will be described in which the registration procedure is temporarily suspended (interrupted), and further, the store clerk temporarily holds the product during the suspension. In Modification 2, the registration procedure includes from the start of the product registration process to the start of the suspension and from the end of the suspension to the end of the registration process. In other words, the registration procedure includes the "registration procedure before suspension" from the start of the product registration process to the start of the suspension and the "registration procedure after suspension" from the end of the suspension to the end of the registration process.

[0165] In Modification 2, the transaction control unit 702 associates and registers the same transaction ID with each registration information in the registration procedure before suspension and the registration procedure after suspension. In addition, the transaction control unit 702 enables settlement of the registration information related to the registration procedure before suspension and the registration information related to the registration procedure after suspension in a single settlement procedure.

[0166] (Outline of the sales data processing system 1 according to Modification 2) FIG. 18 is an explanatory diagram showing a schematic flow of the sales data processing system 1 according to Modification 2. Step S1801: When the registration device 40 receives a predetermined operation indicating the start of a transaction (product registration), it newly generates a transaction ID (transaction identification information for identifying the transaction) and acquires the customer ID. In addition, the registration device 40 inputs registration information by receiving a product registration operation by the customer.

[0167] Step S1802: The registration device 40 displays a hold button and a discard button (registration cancellation button) on the registration screen. The hold button accepts the hold (interruption) of the registration procedure. The discard button accepts the cancellation of the registration procedure.

[0168] Step S1803: When the registration device 40 accepts the pressing of the discard button, it discards the input registration information and returns to the standby screen.

[0169] Step S1804: There may be a case where the customer wishes to add a product, such as when the customer notices that they have forgotten to buy a product. In this case, the customer presses the hold button. When the registration device 40 accepts the pressing of the hold button, it generates customer registration information associating the registration information and the customer ID input before accepting the hold button, and transmits it to the management server 10. When the management server 10 receives the customer registration information from the registration device 40, it stores the received customer registration information in the customer registration information DB11. The customer registration information includes information (hold flag) indicating whether it is on hold.

[0170] Step S1805: The registration device 40 performs a clerk calling process. As a result, the monitoring clerk arranged in the transaction status management device 30 goes to the registration device 40 by the calling process and temporarily stores the products related to the registration procedure before the hold. When the registration device 40 puts the registration procedure on hold, it displays the standby screen and enables accepting the product registration of other customers.

[0171] Step S1806: When a customer who wishes to add a product returns to any of the registration devices 40 with the product to be added, the registration device 40 again acquires the customer ID from the imaging result of the customer's face image. When the registration device 40 acquires the customer ID, it makes a transmission request for the registration information to the management server 10. By the transmission request, the management server 10 refers to the customer registration information DB11 and determines the presence or absence of the registration information on hold corresponding to the customer ID. If there is registration information on hold, the management server 10 transmits the registration information on hold to the registration device 40.

[0172] Step S1807: The management server 10 gives a notification instruction to the store clerk indicating that product registration is to be resumed. The said notification instruction is given, for example, to the transaction status management device 30 and the registration device 40. Thereby, the transaction status management device 30 notifies the monitoring store clerk to deliver the temporarily held product to the customer (indicating the resumption of registration). Further, the registration device 40 notifies the monitoring store clerk to deliver the temporarily held product to the customer (indicating the resumption of registration) by lighting the sign pole 220 in a predetermined manner.

[0173] Step S1808: The registration device 40 ends the suspension and performs additional product registration. The transaction ID in the additional registration is the same transaction ID as before the suspension. When the input of the registration information related to the additional registration is completed, the registration device 40 generates customer registration information associating the registration information related to the additional registration with the customer ID and transmits it to the management server 10. When the management server 10 receives the customer registration information from the registration device 40, it stores the received customer registration information in the customer registration information DB11.

[0174] Step S1809: When the customer completes the input of product information (product registration), the customer moves to the settlement device 50.

[0175] Step S1810: The settlement device 50 acquires the customer ID and makes a request to transmit the registration information. The management server 10 identifies the target customer registration information by identifying the customer ID that matches the customer ID included in the transmission request. The identified customer registration information is the customer registration information related to the registration procedure before the suspension and the registration procedure after the suspension. The management server 10 further identifies (extracts) the registration information from the identified customer registration information and transmits the registration information to the settlement device 50.

[0176] Step S1811: When the settlement device 50 acquires the registration information related to the registration procedure before the suspension and the registration procedure after the suspension from the management server 10, it performs settlement related to one settlement procedure based on the said registration information. In the settlement, the temporarily held product is delivered to the customer. Note that the delivery of the product may be performed at the time of the additional registration in Step S1808.

[0177] In addition, when delivering the product, it may be determined whether the customer IDs match. The entity for such determination may be the settlement device 50 or the management server 10. Also, when the product is deposited in step S1805, a deposit ticket may be given to the customer, and in step S1811, the deposit ticket may be exchanged.

[0178] As described above, in the sales data processing system 1 according to the second modification example, during the registration of the product, it can be put on hold (interrupted), and the product before the interruption and the product related to the additional registration after the interruption can be settled in a single settlement procedure.

[0179] Note that the sales data processing system 1 may be provided with an exit gate. In this case, the product may be delivered at the exit gate. Also, in this case, the temporarily deposited product may be transported near the exit gate, and the notification instruction in step S1807 and the notification based thereon may be performed on the monitor provided in the exit gate or the monitor of the terminal device near the gate. Thereby, the store clerk can deliver the temporarily deposited product to the customer at the exit gate.

[0180] (Registration information input process performed by the registration device 40 according to the second modification example) FIG. 19 is a flowchart showing an example of the registration information input process performed by the registration device 40 according to the second modification example. Hereinafter, mainly the processes of steps S1901 to S1906 will be described. In FIG. 19, when the registration device 40 acquires the customer ID (face recognition result) (step S902), it performs a transmission request process for registration information (FIG. 20) on the management server 10 (step S1901).

[0181] Also, in step S904, when registration information is not input (step S904: NO), the registration device 40 determines whether the discard button has been pressed (step S1902). When the discard button has been pressed (step S1902: YES), the registration information stored in a predetermined storage unit is discarded (erased) (step S1903), and a series of processes ends.

[0182] On the other hand, in step S1902, when the discard button has not been pressed (step S1902: NO), the registration device 40 determines whether the hold button has been pressed (step S1904). When the hold button has not been pressed (step S1904: NO), the registration device 40 proceeds to the process of step S906.

[0183] On the other hand, when the hold button has been pressed (step S1904: YES), the customer registration information is transmitted to the management server 10 (step S1905). Note that in step S1905, a notification indicating a hold is also transmitted together with the customer registration information. By this notification, the management server 10 turns on the hold flag for the customer registration information. After this, the registration device 40 performs a clerk call process (step S1906), and a series of processes ends.

[0184] (Processing related to the transmission request of registration information performed by the registration device 40 and the management server 10 according to Modification 2) FIG. 20 is a flowchart showing an example of processing related to the transmission request of registration information performed by the registration device 40 and the management server 10 according to Modification 2. Hereinafter, mainly, the processing of steps S2001 to S2004 will be described.

[0185] In step S1004 of FIG. 20, when the settlement completion flag corresponding to the customer ID that matches the customer ID included in the transmission request is OFF (step S1004: YES), that is, when it is unsettled, the management server 10 determines whether the hold flag indicating that it is on hold is ON (step S2001).

[0186] When the registration information does not indicate being on hold (step S2001: NO), the management server 10 proceeds to the process of step S1005. On the other hand, when the registration information indicates being on hold (step S2001: YES), the management server 10 sends a notification instruction to the store clerk to the transaction status management device 30 and the registration device 40 (step S2002). Note that when the transaction status management device 30 receives the notification instruction, it notifies that the registration will resume. Then, the management server 10 sets the hold flag to OFF (step S2003) and proceeds to the process of step S1005.

[0187] In step S2004, the registration device 40 determines whether it has received a notification instruction from the management server 10 (step S2004). When it has not received the notification instruction (step S2004: NO), that is, when it is not on hold, the registration device 40 proceeds to the process of step S1006. On the other hand, when it has received the notification instruction (step S2004: YES), the registration device 40 performs a notification process indicating the resumption of registration (step S2005) and proceeds to the process of step S1006. In the notification process, the sign pole 220 of the registration device 40 is lit in a predetermined manner (a manner indicating that the stored goods are to be delivered to the customer).

[0188] As described above, the management server 10 according to the second modification example is capable of putting on hold (interrupting) the registration of goods by the customer and further allowing the customer to perform additional registration of goods after the hold. Specifically, the management server 10 associates and registers the customer ID and the registration information in the registration procedure before the hold and the registration procedure after the hold respectively, and enables settlement based on the registration information related to the registration procedure before the hold and the registration information related to the registration procedure after the hold. As a result, for the products registered after the hold and the products registered before the hold, settlement can be performed by a single settlement procedure. Specifically, when a customer notices that they have forgotten to register a product or have forgotten to register (scan) a product in the shopping cart during the registration procedure, the customer can put the product registration on hold, and after the hold, for the products registered after the hold and the products registered before the hold, settlement can be performed by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the hassle of settlement for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0189] Also, in the sales data processing system 1 according to Modification 2, when a registration hold is performed, the store clerk temporarily holds the product before the hold and delivers the product to the customer after the hold. As a result, since the store clerk can check the product before the hold, it is possible to prevent misregistration due to a mixture of products before and after the hold and to prevent fraud such as proceeding to settlement without registering the product.

[0190] (Modification 3) Next, Modification 3 will be described. Modification 3 describes an example in which the store clerk call (step S1805 in FIG. 18) described in Modification 2 is not performed. That is, Modification 3 describes an example in which temporary holding of products at the time of hold is not performed.

[0191] In Modification 3, in step S1804 of FIG. 18, when the registration device 40 receives the pressing of the hold button, it generates customer registration information and transmits it to the management server 10 to put the product registration on hold. Then, the registration device 40 does not perform the store clerk call process of step S1805. For this reason, without the store clerk performing temporary holding, the customer returns to the sales floor and goes to pick up the products for which additional registration is desired.

[0192] Then, in the additional registration, the notification instruction shown in step S1807 is given. As a result, the transaction status management device 30 and the registration device 40 notify the monitoring clerk that the registration is to be resumed. Then, the clerk can go to the customer and check the goods before and after the reservation. If the sales data processing system 1 is provided with an exit gate, the confirmation may be made at the exit gate. Also, the notification instruction in step S1807 and the notification based on this may be made on the monitor provided at the exit gate or the monitor of the terminal device near the gate. Thereby, the clerk can check the goods before and after the reservation at the exit gate.

[0193] As described above, when a reservation for product registration is made, the sales data processing system 1 according to Modification 3 notifies the clerk that the registration is to be resumed after the resumption of registration. As a result, the clerk can check the goods before and after the reservation, so that it is possible to prevent incorrect registration due to a mixture of goods before and after the reservation, and to prevent fraud such as proceeding to settlement without registering the goods.

[0194] (Modification 4) Next, Modification 4 will be described. In the above-described embodiment, an example in which the registration unit 701 and the transaction control unit 702 shown in FIG. 7 are provided in the management server 10 has been described. In Modification 4, an example in which the registration unit 701 is provided in the registration device 40 and the transaction control unit 702 is provided in the settlement device 50 will be described. Also, an example in which the customer registration information DB 11 is provided in each of a plurality of registration devices 40 will be described.

[0195] In Modification 4, the registration unit 701 provided in the registration device 40 registers the customer registration information generated by the own device in the customer registration information DB 11. The customer registration information registered in the customer registration information DB 11 is, for example, customer registration information generated in the own device. Note that the customer registration information stored in the customer registration information DB 11 is shared among a plurality of registration devices 40 and among a plurality of settlement devices 50.

[0196] The transaction control unit 702 included in the settlement device 50 determines whether the customer ID acquired at the start of the settlement procedure matches the customer IDs related to a plurality of registration procedures (the previous registration procedure and the subsequent registration procedure). Specifically, the transaction control unit 702 inquires of each registration device 40 about the presence or absence of the customer ID related to the previous registration procedure and the presence or absence of the customer ID related to the subsequent registration procedure that match the customer ID acquired at the start of the settlement. As a result of the inquiry, if there are matching customer IDs, the transaction control unit 702 acquires the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure from the registration device 40 that was the inquiry destination. Then, the transaction control unit 702 enables settlement based on the acquired registration information.

[0197] Note that in Modification Example 4, the entity that determines whether there is a match is not limited to the settlement device 50 and may be the management server 10. Specifically, as in the embodiment, the transaction control unit 702 may make a request to the management server 10 to transmit registration information. In this case, the management server 10 determines the presence or absence of a customer ID that matches the customer ID included in the transmission request, and may transmit the registration information to the settlement device 50 according to the determination result.

[0198] The sales data processing system 1 according to Modification Example 4 can enable settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure without including the management server 10. For this reason, while simplifying the configuration of the sales data processing system 1, it is possible to suppress a decrease in the operation efficiency of the settlement device 50 and perform transactions efficiently.

[0199] (Modification Example 5) Next, Modification Example 5 will be described. In the above-described embodiment, an example in which the shopping on the same day is settled in one settlement procedure for the additionally registered products and the products before the additional registration was described. In Modification Example 5, an example in which the unsettled products and the products registered by the same customer who visited the store on a later date are settled in one settlement procedure will be described.

[0200] In Modification 5, the customer registration information DB 11 stores customer registration information including a settlement completion flag for a predetermined period (e.g., 10 days). Suppose a customer leaves the store without settling. Then, the settlement completion flag remains OFF. And when the customer visits the store again later and registers a product, the customer ID of the customer is obtained. At the start of registration, the registration device 40 sends a request to transmit registration information related to the previous registration procedure (step S1001 in FIG. 10).

[0201] If the registration device 40 receives registration information with a different date due to the transmission request, it notifies that there is unsettled registration information (prompting the previous settlement). That is, if the dates of the previous registration procedure and the subsequent registration procedure are the same, the registration device 40 displays a screen for additional registration, and if the dates do not match, it notifies that there is unsettled registration information. Also, this notification may be made by the settlement device 50.

[0202] For example, when the settlement device 50 receives registration information related to an unsettled registration procedure before the previous day and the registration procedure on the current day, it settles the registration information related to multiple registration procedures in one settlement procedure.

[0203] In Modification 5, it may be possible to register products on the current day on the condition that the settlement for the unsettled registration procedure is completed. Specifically, before registering products on the current day, the registration device 40 may prompt to complete the unsettled registration procedure. And after the settlement for the unsettled registration procedure is completed, the registration device 40 may enable product registration on the current day.

[0204] According to Modification 5, it is possible to appropriately make the customer settle for unsettled transactions. That is, the store can collect the unsettled amount.

[0205] (Modification 6) Next, Modification 6 will be described. In Modification 6, an example of enabling the addition of products in the settlement device 50 will be described. In Modification 6, after the customer finishes registering products in the registration device 40, the customer moves to the settlement device 50. What the customer who has moved to the settlement device 50 does first is considered to be reading customer identification information or adding a product that was forgotten to be registered.

[0206] (Screen at the start of operation displayed on the settlement device 50 according to Modification 6) Therefore, in Modification 6, the settlement device 50 causes the selection screen to be displayed on the customer-side display unit 305 before the start of settlement. FIG. 21 is a diagram showing an example of a screen at the start of operation displayed on the settlement device 50 according to Modification 6. In FIG. 21, the selection screen 2100 includes a customer ID reading button 2101, an additional registration button 2102, and a clerk call button 2103.

[0207] The customer ID reading button 2101 accepts the start of reading the customer ID. The additional registration button 2102 accepts additional registration. The clerk call button 2103 accepts the calling of a clerk. When the customer ID reading button 2101 is pressed, the settlement device 50 acquires the customer ID and starts settlement. When the additional registration button 2102 is pressed, the settlement device 50 acquires the customer ID and accepts the additional registration of products. When performing additional registration, the settlement device 50 may assign a new transaction ID or the same transaction ID as the transaction ID related to the previous registration procedure.

[0208] In additional registration, the settlement device 50 may display the registered registration information in detail or may not display it in detail. Further, the settlement device 50 may display a switching button that accepts switching between display and non-display for the detailed display, and perform detailed display in response to the pressing of the switching button. Furthermore, when displaying the registration information in detail, the settlement device 50 may change the display mode of the background.

[0209] In addition, when the same product as the product to be additionally registered is already registered, the settlement device 50 may display a confirmation screen such as "Do you want to add it?" Further, when performing additional registration, the settlement device 50 may display a "quantity change button". Note that the quantity change button accepts additional registration (increase in quantity) and does not accept quantity subtraction. This can prevent fraud such as performing settlement by subtracting the quantity.

[0210] Hereinafter, a summary of the embodiments will be described. [Title of the Invention] Registration Information Management Device, Registration Device, Settlement Device, System, and Program [Technical Field] The present invention relates to a registration information management device, a registration device, a settlement device, a system, and a program. [Background Art] In a store or the like, a checkout system may be introduced in which a registration device for registering products and a settlement device for performing settlement are separated (see, for example, Patent Document 1). In particular, in recent years, a self-service type in which a customer performs a registration operation on a registration device and the customer performs a settlement operation on a settlement device has been becoming popular. [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-016413 [Summary of the Invention] [Problems to be Solved by the Invention] Here, in a self-service cash register, after the registration of a product is completed, the customer may notice an oversight such as forgetting to buy something and wish to perform additional registration. However, in the prior art, if settlement is performed separately for the previously registered product and the product for which additional registration is desired, it may take time for settlement and transactions may not be carried out efficiently, which is a problem. The present invention has been made in view of such circumstances, and an object thereof is to provide a technique capable of efficiently conducting transactions.

[0211] [Means for Solving the Problems] (1) To solve the above problems, a registration information management device according to an aspect of the present invention associates and registers customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation for each registration procedure indicating the start to the end of a product registration operation by a customer. When the customer identification information related to a previous registration procedure matches the customer identification information related to a subsequent registration procedure, it is characterized by including transaction control means that enables settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure. According to the above configuration, for a product for which additional registration is desired (product related to a subsequent registration procedure) and a product registered previously (product related to a previous registration procedure), settlement can be performed by a single settlement procedure. For this reason, after the registration of the product related to the previous registration procedure is completed, when the customer notices that they have forgotten to buy a product or have forgotten to register (scan) the product in the shopping cart, etc., when the customer desires to add a product, for the product for which additional registration is desired and the product registered previously, settlement can be performed by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the annoyance for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0212] (2) In the configuration of (1) above, the registration means may register registration information including transaction identification information generated for each registration procedure, and in the subsequent registration procedure, register registration information including transaction identification information different from the transaction identification information related to the previous registration procedure. According to the above configuration, in the additional registration of a product, similar to the registration information of a normal product, a product can be registered by newly attaching a transaction ID to the registration information. Also, the registration information related to a plurality of registration procedures can be settled by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the annoyance of settlement for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0213] (3) In the configuration of (1) above, the registration means may register by associating customer identification information that matches the customer identification information related to the previous registration procedure with the registration information related to the subsequent registration procedure in the subsequent registration procedure. According to the above configuration, in the additional registration of a product, without generating a new transaction ID for the registration information, the transaction ID related to the previous registration procedure can be attached to the registration information related to the subsequent registration procedure and registered. Also, the registration information related to a plurality of registration procedures can be settled by one settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the annoyance of settlement for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0214] (4) In order to solve the above-described problems, a registration device according to another aspect of the present invention is a registration device that is connected to the registration information management device described above and performs product registration, and includes an input unit that inputs registration information based on the registration operation. When the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure, the input unit enables the input of the registration information related to the subsequent registration procedure when the period from the completion of the previous registration procedure to the start of the subsequent registration procedure is less than a predetermined period, and prohibits the input of the registration information related to the subsequent registration procedure when the period is equal to or more than the predetermined period. The registration device is characterized by this. According to the above configuration, when the period until the start of additional registration is less than a predetermined period, that is, for example, when a customer notices a product that has been forgotten to be registered (scanned) in the shopping cart, the customer can immediately perform additional registration. On the other hand, when the period until the start of additional registration is equal to or more than a predetermined period, by prohibiting additional registration, for a plurality of registration procedures by the same person, a store clerk can check the products, or prevent a plurality of registration procedures by the same person from being performed. Therefore, it is possible to support appropriate transactions.

[0215] (5) In the above configuration, when the period is equal to or more than a predetermined period, a call processing means for performing a process of calling a store clerk may be provided. According to the above configuration, the store clerk can confirm that there are no mistakes regarding the products related to the previous registration procedure and the products related to the additional registration that is about to be registered. Therefore, it is possible to support appropriate transactions.

[0216] (6) In order to solve the above-described problems, a settlement device according to another aspect of the present invention is a settlement device that is connected to the registration information management device described above and performs settlement by a customer's settlement operation, and includes: a customer identification information acquisition means for acquiring customer identification information for identifying a customer who performs a settlement operation; a request means for making a transmission request for registration information to the registration information management device based on the customer identification information acquired by the customer identification information acquisition means; a selection means for selecting whether to total the registration information related to a plurality of registration procedures when the registration information received from the registration information management device in response to the transmission request is registration information related to a plurality of registration procedures; and a settlement means for performing settlement based on the selection result of the selection means. According to the above configuration, in one settlement procedure for the products related to the subsequent registration procedure and the products related to the previous registration procedure, it is possible to perform an optimal settlement according to the customer's request. For example, when receiving a shopping request from an acquaintance, settlement can be performed without totaling, and when adding additional registration for one's own shopping, settlement can be performed by totaling. Furthermore, since one settlement procedure is performed, settlement can be performed quickly, so that the annoyance for the customer can be reduced, the decrease in the operation efficiency of the settlement device 50 can be suppressed, and transactions can be performed efficiently.

[0217] (7) In order to solve the above-described problems, a system according to another aspect of the present invention is a system including a registration device and a settlement device, wherein the registration device includes a registration means for registering, in association with each other, customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation from the start to the end of a registration procedure indicating a product registration operation by a customer, and the settlement device includes a transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure when the customer identification information related to the previous registration procedure and the customer identification information related to the subsequent registration procedure match. According to the above configuration, for a product for which additional registration is desired (a product related to a subsequent registration procedure) and a product registered previously (a product related to a previous registration procedure), settlement can be performed by a single settlement procedure. For this reason, when a customer desires to add registration for a product, such as when the customer notices that they have forgotten to register a product or have forgotten to register (scan) a product in the shopping cart after the registration of the product related to the previous registration procedure is completed, settlement can be performed for the product for which additional registration is desired and the product registered previously by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the annoyance for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0218] (8) In order to solve the above-described problems, a program according to another aspect of the present invention causes a computer of a registration information management device to register, for each registration procedure indicating from the start to the end of a product registration operation by a customer, customer identification information for identifying the customer who performs the registration operation and registration information based on the registration operation in association with each other, and when the customer identification information related to a previous registration procedure matches the customer identification information related to a subsequent registration procedure, enables settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure. The program is characterized by functioning as transaction control means. According to the above configuration, for a product for which additional registration is desired (a product related to a subsequent registration procedure) and a product registered previously (a product related to a previous registration procedure), settlement can be performed by a single settlement procedure. For this reason, when a customer desires to add registration for a product, such as when the customer notices that they have forgotten to register a product or have forgotten to register (scan) a product in the shopping cart after the registration of the product related to the previous registration procedure is completed, settlement can be performed for the product for which additional registration is desired and the product registered previously by a single settlement procedure. Therefore, since settlement can be performed quickly, it is possible to reduce the annoyance for the customer, suppress a decrease in the operation efficiency of the settlement device 50, and perform transactions efficiently.

[0219] (9-1) In order to solve the above-described problems, an information processing apparatus according to another aspect of the present invention is an information processing apparatus that stores, in association with each other, unsettled registration information, customer identification information, and registration identification information, and sums up the plurality of registration identification information when there are a plurality of registration identification information stored in association with the customer identification information.

[0220] (9-2) In order to solve the above-described problems, an information processing apparatus according to another aspect of the present invention is an information processing apparatus characterized in that when there is unsettled data related to the customer identification information input by the customer identification information input means for inputting identification information, additional registration is performed on the unsettled data, and when there is no unsettled data, new transaction identification information is generated, and product information is registered corresponding to the generated transaction identification information.

[0221] Note that all or part of each function (input / output, storage, processing (including determination)) in the sales data processing system 1 (management server 10, registration device 40, settlement device 50) described above may be realized in another device different from the device described as the execution subject of the function.

[0222] Specifically, all or part of each functional unit (see FIG. 7) provided in the management server 10, registration device 40, and settlement device 50 may be provided in another computer device. For example, all or part of each functional unit may be provided in the management server 10 or in another computer device. Further, the computer device in which each functional unit is provided is not limited to a plurality of units, and may be one unit. For example, one computer device may be provided with all of the functional units.

[0223] In relation to the above, the registration device 40 and the settlement device 50 may function as so-called thin clients specialized in the input / output interface part regarding various displays and the like. That is, the registration device 40 and the settlement device 50 receive various inputs (operations of an operator and detections of devices), transmit input information (operation information, detection information, etc.) to the management server 10, receive processing results (update screen information, control information of devices, etc.) of the management server 10 based on the input information, and may perform various outputs (display on a display unit, control of devices).

[0224] Incidentally, a program for realizing the sales data processing system 1, the management server 10, the registration device 40, and the settlement device 50 described above may be recorded on a computer-readable storage medium, and the program may be read into a computer system and executed. Here, the "computer system" shall include hardware such as an OS and peripheral devices. Further, the "computer-readable storage 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 storage medium" shall also include 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 that 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

[0225] 1…Sales data processing system, 10…Management server, 11…Terminal order information DB, 40…Registration device, 50…Settlement device, 701…Registration section, 702…Transaction control section, 711…Customer ID acquisition section, 712…Input section, 713…Call processing section, 721…Customer ID acquisition section, 722…Request section, 723…Settlement section, 724…Selection section

Claims

1. Registration means for associating and registering customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation for each registration procedure indicating from the start to the end of the product registration operation by the customer; Transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure when the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure; A registration information management device characterized by comprising the above.

2. The registration means: Registers registration information including transaction identification information generated for each registration procedure, In the subsequent registration procedure, registers registration information including transaction identification information different from the transaction identification information related to the previous registration procedure. The registration information management device according to claim 1, characterized by the above.

3. The registration means, in the subsequent registration procedure, associates and registers customer identification information that matches the customer identification information related to the previous registration procedure and the registration information related to the subsequent registration procedure. The registration information management device according to claim 1, characterized by the above.

4. A registration device connected to the registration information management device according to any one of claims 1 to 3 for performing product registration, Comprising an input unit for inputting registration information based on the registration operation, When the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure, the input unit: Enables input of the registration information related to the subsequent registration procedure when the period from the completion of the previous registration procedure to the start of the subsequent registration procedure is less than a predetermined period, Prohibits input of the registration information related to the subsequent registration procedure when the period is equal to or more than the predetermined period. A registration device characterized by the above.

5. Comprises a calling processing means for performing a process of calling a store clerk when the period is equal to or more than the predetermined period. The registration device according to claim 4, characterized by the above.

6. A settlement device connected to the registration information management device according to any one of claims 1 to 3 for performing settlement by a customer's settlement operation, Customer identification information acquisition means for acquiring customer identification information for identifying a customer who performs the settlement operation, Request means for making a request to the registration information management device to transmit registration information based on the customer identification information acquired by the customer identification information acquisition means. When the registration information received from the registration information management device in response to the transmission request is registration information related to a plurality of registration procedures, selection means for selecting whether to total the registration information related to the plurality of registration procedures; Settlement means for performing settlement based on the selection result of the selection means; A settlement device comprising the same.

7. A system including a registration device and a settlement device, The registration device includes registration means for registering, in association with each other, customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation for each registration procedure indicating from the start to the end of the registration operation of a product by the customer. The settlement device includes transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure when the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure. A system characterized by the above.

8. Causing a computer of a registration information management device to function as Registration means for registering, in association with each other, customer identification information for identifying a customer who performs the registration operation and registration information based on the registration operation for each registration procedure indicating from the start to the end of the registration operation of a product by the customer, Transaction control means for enabling settlement based on the registration information related to the previous registration procedure and the registration information related to the subsequent registration procedure when the customer identification information related to the previous registration procedure matches the customer identification information related to the subsequent registration procedure, A program characterized by the above.

Images