Commodity sales data processing system

Abstract

To provide a suitable accounting flow line.SOLUTION: Provided is a commodity sales data processing system for executing a registration process of registering commodities and a payment process of making payment for the commodities registered by the registration process, said system comprising: a first device for executing the registration process on the basis of a clerk's operation; a second device for executing the payment process on the basis of a customer's operation with regard to the commodities registered by the first device; and a third device for executing the payment process on the basis of a customer's operation with regard to the commodities registered by a portable device on the basis of a customer's operation on a sales floor in a store. Each of the first, the second and the third devices is installed so that at least a portion of a first accounting flow line formed so as to include the installed points of the first and the second devices and a second accounting flow line formed so as to include the installed point of each of a plurality of the third devices are approximately parallel to each other.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a product sales data processing system. [Background technology]

[0002] There are cases where multiple services related to the sale of goods coexist. For example, a system that provides multiple payment methods in a store is known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-081072 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, problems may arise in accounting flows when multiple services coexist.

[0005] The present invention has been made in consideration of the above circumstances, and has an object to provide an optimal checkout flow line. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a product sales data processing system that executes a registration process to register products and a settlement process to settle products registered by the registration process, comprising a first device that executes the registration process based on the operation of a store clerk, a second device that executes the settlement process for products registered by the first device based on the operation of a customer, and a third device that executes the settlement process for products registered by a portable device based on the operation of the customer in a sales floor within the store, wherein each of the first device, the second device, and the third device are installed so that at least a portion of a first accounting traffic line formed to include the installation point of the first device and the installation point of the second device, and a second accounting traffic line formed to include the installation points of each of the multiple third devices are approximately parallel to each other. [Brief description of the drawings]

[0007] [Figure 1] 1 is a conceptual diagram of a network for explaining a sales system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating the external appearance of the settlement device. [Diagram 3] 2 is a configuration example of a settlement device. [Figure 4] FIG. 2 is a diagram illustrating the external appearance of the registration settlement device. [Diagram 5] 2 is a configuration example of a registration settlement device. [Figure 6] FIG. 2 is a diagram illustrating the appearance of a registration device. [Figure 7] 2 is a configuration example of a registration device. [Figure 8] FIG. 2 is a diagram illustrating the external appearance of the settlement device. [Figure 9] 2 is a configuration example of a settlement device. [Figure 10] 13 is a display example of a mobile terminal. [Figure 11] 13 is a display example of a mobile terminal. [Figure 12] 13 is an example of a display on a settlement device. [Figure 13] 13 is an example of a display on a settlement device. [Figure 14] FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 15] 11 is a sequence diagram showing an example of processing by the settlement device and the cloud server. FIG. [Figure 16] FIG. 11 is a conceptual diagram of a network for explaining a sales system according to a second embodiment. [Figure 17] FIG. 13 is a conceptual diagram of a network for explaining a sales system according to a third embodiment. [Figure 18] FIG. 2 is a diagram illustrating the external appearance of the registration settlement device. [Figure 19] 2 is a configuration example of a registration settlement device. [Figure 20] 1 is an example (Example 1 relating to installation layout) of each device in the sales system of the first embodiment. [Figure 21] 13 is another example (Example 2 relating to installation layout) of the devices in the sales system of the first embodiment. [Figure 22] 13 is an example (Example 3 relating to installation layout) of each device in the sales system of the second embodiment. [Diagram 23] 13 is another example (Example 4 relating to installation layout) of the devices in the sales system of the second embodiment. [Figure 24] 13 is an example (Example 4 relating to installation layout) of each device in the sales system of the third embodiment. [Diagram 25] 13 is a display example of a transaction status management device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] (First embodiment) Fig. 1 is a conceptual diagram of a network for explaining a sales system 1 of a first embodiment. The sales system 1 shown in Fig. 1 includes a headquarters server 10, a cloud server 20, a store controller 30 (e.g., a server, etc.), a transaction status management device 40 (e.g., a personal computer, etc.), a settlement device 50, a registration settlement device 51, a registration settlement device 52, a registration device 53, a settlement device 54, and a mobile terminal 60.

[0009] The store controller 30, the transaction status management device 40, the settlement device 50, the registration settlement device 51, the registration settlement device 52, the registration device 53, and the settlement device 54 are communicatively connected via a LAN 19 (which may be wired or wireless). The store controller 30 is capable of communicating with the headquarters server 10. The sales system 1 can be introduced in various stores (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).

[0010] In Fig. 1, the number of each device (terminal) is an example. For example, in Fig. 1, "..." is illustrated to the right of the transaction status management device 40, but the number of transaction status management devices 40 installed in one store may be one or more. Also, for example, in Fig. 1, two mobile terminals 60 are illustrated, but the number of mobile terminals 60 used in the store changes depending on the number of customers.

[0011] Sales system 1 provides a self-service (hereinafter, sometimes referred to as service A) in which a customer uses a mobile terminal 60 to register a product and uses a settlement device 50 to settle the payment. In other words, service A is a self-service in which a customer registers a product and settles the payment by himself / herself, using mobile terminal 60 for product registration and using settlement device 50 for settlement.

[0012] Furthermore, the sales system 1 provides other services in addition to the service A. For example, as other services, the sales system 1 can provide a service in which a customer uses the registration and settlement device 51 (or the registration and settlement device 52) to register a product and settle the payment, or a service in which a store clerk uses the registration device 53 to register a product and a customer uses the settlement device 54 to settle the payment.

[0013] The headquarters server 10 is installed outside the store (e.g., at a head office or a data center) and is a server that manages the entire sales system 1. The headquarters server 10 stores, for example, various information required for the operation of services including service A (e.g., customer master (member master), product master, sale file, etc.) and performance information of services in the store (e.g., sales performance information, product sales performance information, etc.). The headquarters server 10 communicates with the cloud server 20 and the store controller 30. The headquarters server 10 may communicate with other devices (e.g., a transaction status management device 40, a settlement device 50, etc.). The headquarters server 10 may be composed of multiple servers.

[0014] Cloud server 20 is a server installed outside a store (e.g., in a data center, etc.) and provides service A. Cloud server 20 stores, for example, various information required for the operation of service A (e.g., product master, transaction information (also referred to as cart information), etc.). Cloud server 20 communicates with headquarters server 10 and mobile terminal 60. Cloud server 20 may also communicate with other devices (e.g., store controller 30, transaction status management device 40, etc.). Cloud server 20 may be composed of multiple servers.

[0015] The store controller 30 is a device that controls the part of the sales system 1 that is related to the store. The store controller 30 communicates with each device in the LAN 19 (e.g., the settlement device 50, etc.) and each device outside the LAN 19 (e.g., the headquarters server 10). For example, the store controller 30 receives a product master and a sale file from the headquarters server 10 and provides them to the settlement device 50.

[0016] The transaction status management device 40 is a device that mainly manages each device in the LAN 19. For example, the transaction status management device 40 communicates with each device in the LAN 19 and monitors the processing status, operation status (operation status) and the like of each device in the LAN 19. The transaction status management device 40 may also communicate with each device outside the LAN 19 (e.g., the head office server 10, the cloud server 20) (it may communicate directly or via the store controller 30). For example, the transaction status management device 40 may refer to transaction information (cart information) stored in the cloud server 20.

[0017] The mobile terminal 60 is a terminal used when registering a product in the service A. That is, the customer uses the mobile terminal 60 when registering a product in the service A. The mobile terminal 60 has a communication function, an imaging function (camera), and a recognition function for recognizing various codes (barcodes, two-dimensional codes, etc.). For example, the mobile terminal 60 recognizes a barcode attached to a product. For example, the mobile terminal 60 may extract feature points in an image captured by the imaging function (an image acquired as a through image (live view)) and recognize an object (various codes). Note that the mobile terminal 60 is assumed to be owned by an individual customer (or a corporation) who uses the service A, but may be loaned by the store.

[0018] The settlement device 50 is a device used when making a settlement in service A. That is, a customer uses the settlement device 50 when making a settlement for a product registered using a mobile terminal 60. The configuration of the settlement device 50 will be described later.

[0019] The registration and settlement device 51 is used by a store clerk or a customer. Specifically, the registration and settlement device 51 has a scanner unit on both sides (the store clerk side and the customer side) and a payment unit (specifically, a cash payment unit and a card payment unit) on one side (the customer side). The registration and settlement device 51 has a number of switchable operating modes. The configuration of the registration and settlement device 51 will be described later.

[0020] The registration and settlement device 52 is used by a store clerk or a customer. Specifically, the registration and settlement device 52 has a scanner unit on both sides (the store clerk side and the customer side) and a payment unit (specifically, a card payment unit) on one side (the customer side). The registration and settlement device 52 has multiple switchable operating modes. In other words, the registration and settlement device 52 differs from the registration and settlement device 51, which has a cash payment unit, in that it does not have a cash payment unit.

[0021] The registration device 53 is mainly used by store clerks. The registration device 53 includes a scanner unit and is used exclusively for registering products. The configuration of the registration device 53 will be described later.

[0022] The settlement device 54 is mainly used by customers. The settlement device 54 includes a settlement unit and is used exclusively for settlement. The configuration of the settlement device 54 will be described later.

[0023] (Payment device 50) Fig. 2 is a diagram illustrating the external appearance of the settlement device 50. Fig. 3 shows an example of the configuration of the settlement device 50. In Fig. 2 and Fig. 3, the same parts are denoted by the same reference numerals.

[0024] Hereinafter, a configuration example of the settlement device 50 shown in FIG. 3 will be described with reference to FIG. 2. The settlement device 50 includes a CPU 101, a ROM 102, a RAM 103, a hard disk 104, a display unit 105, a scanner unit 106, a card settlement unit (non-cash settlement unit) 108, a change machine (cash settlement unit) 109, a printing unit 113, an audio output unit 114, a communication unit 115, an imaging unit (camera) 116, and a sign pole 117. These can communicate with each other via a bus. The settlement device 50 (similar to the settlement device 54) may further include a key operation unit consisting of various keys (buttons). The settlement device 50 (similar to the registration settlement device 51, the registration settlement device 52, the registration device 53, the settlement device 54, etc.) may further include a sensor (human sensor, etc.) that detects the presence of a person.

[0025] The CPU 101 is a central processing unit, and controls the operation of the settlement device 50 by reading and executing programs stored in the ROM 102 . The ROM 102 is a read-only memory, and stores various types of information used by the CPU 101, including programs.

[0026] The RAM 103 is a read / write memory and stores various information as a main storage device. For example, the RAM 103 stores information read from the ROM 102 or the hard disk 104, information acquired from the outside, information generated during processing, and the like.

[0027] The hard disk 104 stores various information as an auxiliary storage device. For example, the hard disk 104 may store programs executed by the CPU 101 instead of the ROM 102. Also, instead of the RAM 103, the hard disk 104 may store information read from the ROM 102, information acquired from the outside, information generated in processing, etc. Note that instead of the hard disk 104, a storage device such as an SSD (Solid State Drive) may be provided.

[0028] The display unit 105 is a touch display that displays various information and accepts various inputs.

[0029] The scanner unit 106 optically reads various information. Specifically, the scanner unit 106 scans a code (a two-dimensional code 605 for settlement (described later)) displayed on the display unit of the mobile terminal 60, and reads information necessary for settlement processing. The scanner unit 106 may also scan codes attached to gift certificates (gift certificates, coupons, and complimentary coupons) and various cards (e.g., membership cards, point cards, etc.) and read the respective information. The scanner unit 106 may also scan a code attached to a store clerk's name tag or the like and read the store clerk code.

[0030] In addition to the above, the scanner unit 106 may scan a code attached to a product and read the product code (JAN code, etc.). The scanner unit 106 may also scan a code printed on a receipt (registered trademark) printed and issued by another device (for example, the registration settlement device 51, the registration settlement device 52, the registration device 53, etc.) and read information required for settlement processing.

[0031] The card payment unit 108 is a payment mechanism that uses various cards (credit cards, prepaid cards such as transportation cards, cash cards for debit payments, point cards for point payments, etc.). The card payment unit 108 includes a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient that the card payment unit 108 includes at least the card recognition unit. The card recognition unit may recognize various cards (e.g., point cards, membership cards, stockholder cards, etc.) for the purpose of providing benefits, discounts, etc.

[0032] The card payment unit 108 may be multiple members according to the cards to be read. In other words, the settlement device 50 may have multiple card payment units, such as a first card payment unit 108a for prepaid cards and a second card payment unit 108b for credit cards.

[0033] The change machine 109 is a cash settlement mechanism, which has an input port for banknotes and coins, and an output port for banknotes and coins, calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, detecting the number of coins by denomination, etc.).

[0034] The printing unit 113 prints and issues various media (receipts, etc.). The audio output unit 114 outputs audio. For example, the audio output unit 114 outputs a confirmation sound, a warning sound, audio guidance, and the like.

[0035] The communication unit 115 transmits and receives information to and from other devices (for example, the store controller 30, the transaction status management device 40, etc.). The imaging unit 116, for example, captures an image of the customer. The settlement device 50 may include two or more imaging units 116, and simultaneously capture images of the face and hands (near the insertion slot and ejection slot of the change machine 109). The sign pole 117 has a light emitting part at the tip, and notifies various information (calling a store clerk, operating status, etc.) depending on the light emitting state of the light emitting part.

[0036] (Registration settlement device 51) FIG. 4 is a diagram for explaining the external appearance of registration and settlement device 51. FIG. 5 is an example of the configuration of registration and settlement device 51. In FIG. 4 and FIG. 5, the same parts are given the same reference numerals. Registration and settlement device 51 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer side display unit 205, a customer side scanner unit 206, a card payment unit (non-cash payment unit) 208, a change machine (cash payment unit) 209, a store clerk side display unit 210, a key operation unit 211, a store clerk side scanner unit 212, a printing unit 213, an audio output unit 214, and a communication unit 215. These can communicate with each other via a bus. In addition, the registered settlement device 51 (the same applies to the registered settlement device 52, the registered device 53, the settlement device 54, etc.) may be equipped with an imaging unit (an imaging unit similar to the imaging unit 116 of the settlement device 50), and the registered settlement device 51 may further be equipped with a sign pole (a sign pole similar to the sign pole 117 of the settlement device 50.

[0037] The CPU 201, ROM 202, RAM 203, hard disk 204, card settlement unit 208, change machine 209, audio output unit 214, and communication unit 215 of the registered settlement device 51 are similar to the CPU 101, ROM 102, RAM 103, hard disk 104, card settlement unit 108, change machine 109, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the description will be omitted.

[0038] The customer side display unit 205 is a touch display that displays various information to the customer and accepts various inputs from the customer.

[0039] The customer-side scanner unit 206 is a scanner unit for customers, and optically reads various information. Specifically, the customer-side scanner unit 206 scans the code attached to the product and reads the product code (JAN code, etc.). The customer-side scanner unit 206 may also scan the codes attached to gift certificates and various cards and read the respective information. The customer-side scanner unit 206 may also scan the code attached to the name tag of a store clerk and read the store clerk code. The customer-side scanner unit 206 may also scan the code printed on the bill and read the information required for the payment process.

[0040] Although the customer-side scanner unit 206 is used when a customer registers a product, the customer may register the product by other methods. For example, if a preset key (a button for ordering the product) corresponding to the product is displayed on the customer-side display unit 205, the customer may operate (press) the preset key to register the product.

[0041] The store clerk's display unit 210 is a touch display that displays various information to the store clerk and receives various inputs from the store clerk. Various buttons operated by a store clerk are arranged on the key operation section 211. Reference numeral 211a denotes a mode switching button for switching between operation modes.

[0042] The clerk scanner unit 212 is a scanner unit for use by clerks, and optically reads various information. Specifically, the clerk scanner unit 212 scans codes attached to products and reads product codes (JAN codes, etc.). The clerk scanner unit 212 may also scan codes attached to gift certificates and various cards and read the respective information. The clerk scanner unit 212 may also scan codes attached to clerk nametags, etc., and read the clerk code. The clerk scanner unit 212 may also scan codes printed on bills and read the information required for payment processing.

[0043] Although the store clerk's scanner unit 212 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper, etc.) is arranged on the key operation unit 211, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 210, the store clerk may operate that preset key to register the product.

[0044] The printing unit 213 prints and issues various media (receipts, bills, etc.). The printing unit 213 can freely rotate to change its orientation (direction of the media issuing port) from the store clerk side to the customer side, or from the customer side to the store clerk side. The orientation of the printing unit 213 may be changed manually, or may be changed automatically (mechanically controlled, etc.) based on, for example, a change in the operating mode. The correctness of the orientation of the printing unit 213 may be detected by a sensor, etc.

[0045] (Operation mode of the registration settlement device 51) As described above, the registration and settlement device 51 has a plurality of operation modes. The operation modes are described below. As described above, the condition for switching the operation mode is the operation of the switching button 211a, but the operation mode can also be switched by other conditions (e.g., the passage of time, reception of registration information, reading of a store clerk code, reception of an operation mode switching command transmitted from another device, etc.). The same applies to the registration and settlement device 52.

[0046] (Face-to-face semi-self mode (normal mode)) The face-to-face semi-self-service mode (also called normal mode) is an operation mode in which a store clerk registers products using one side (store clerk side) of the registration and settlement device 51, and a customer settles the payment using the other side (customer side) of the registration and settlement device 51. Therefore, when the operation mode is the face-to-face semi-self-service mode, the store clerk and the customer meet face to face, the store clerk registers the products, and the customer settles the payment.

[0047] (Full self mode) The full self-service mode is an operation mode in which a customer registers products and makes a payment using one side (customer side) of the registration and payment device 51. Therefore, when the operation mode is the full self-service mode, the customer registers products and makes a payment using the customer side (without using the store clerk side).

[0048] (Multiple-unit semi-self-registration mode (registration-only mode)) The multiple-unit semi-self-service registration mode (also referred to as a registration-only mode) is an operation mode in which a store clerk registers products using one side (the store clerk side) of the registration and settlement device 51. Therefore, when the operation mode is the multiple-unit semi-self-service registration mode, the store clerk registers products using the store clerk side (without using the customer side).

[0049] (Multiple-unit semi-self-service payment mode (payment-only mode)) The multiple-machine semi-self-service settlement mode (also referred to as settlement-only mode) is an operation mode in which a customer settles the bill using one side (customer side) of the registered settlement device 51. Therefore, when the operation mode is the multiple-machine semi-self-service settlement mode, the customer settles the bill using the customer side (without using the store clerk side).

[0050] The registered settlement device 51 in the multiple-vehicle semi-self-service registration mode transmits (directly or indirectly via another device) registration information to the other registered settlement device 51 (specifically, the registered settlement device 51 in the multiple-vehicle semi-self-service registration mode) to cause the other registered settlement device 51 (registered settlement device 51 in the multiple-vehicle semi-self-service registration mode) to settle the merchandise registered by the registered settlement device 51 (registered settlement device 51 in the multiple-vehicle semi-self-service registration mode). In other words, the registered settlement device 51 in the multiple-vehicle semi-self-service registration mode receives (directly or indirectly via another device) registration information transmitted by the other registered settlement device 51 (specifically, the registered settlement device 51 in the multiple-vehicle semi-self-service registration mode) to settle the merchandise registered by the other registered settlement device 51 (registered settlement device 51 in the multiple-vehicle semi-self-service registration mode).

[0051] The registered settlement device 51 in the multiple-machine semi-self-service registration mode may issue a bill and have another registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode) settle the merchandise registered by that registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode). In other words, the registered settlement device 51 in the multiple-machine semi-self-service payment mode may settle the merchandise registered by the other registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode) by reading a code printed on a bill issued by the other registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode).

[0052] The above-mentioned operation in each operation mode is an example. For example, the registered settlement device 51 in the multiple-machine semi-self-service registration mode may transmit registration information to the registered settlement device 51 in the face-to-face semi-self-service mode or the registered settlement device 51 in the full self-service mode, or may issue a bill. In other words, the POS terminal in the face-to-face semi-self-service mode (as well as the registered settlement device 51 in the full self-service mode) may settle the product registered by the registered settlement device 51 in the multiple-machine semi-self-service registration mode. Also, for example, the registered settlement device 51 in the face-to-face semi-self-service mode may transmit registration information to the registered settlement device 51 in the full self-service mode or the registered settlement device 51 in the multiple machine semi-self-service settlement mode, or may issue a bill. In other words, the registered settlement device 51 in the full self-service mode (as well as the registered settlement device 51 in the multiple machine semi-self-service settlement mode) may settle the product registered by the registered settlement device 51 in the face-to-face semi-self-service mode. Also, for example, a registered settlement device 51 in face-to-face semi-self-service mode may transmit registration information or issue a bill to another registered settlement device 51 in face-to-face semi-self-service mode. In other words, a registered settlement device 51 in face-to-face semi-self-service mode may settle payments for products registered by another registered settlement device 51 in face-to-face semi-self-service mode.

[0053] (Registration settlement device 52) As described above, the registration and settlement apparatus 52 differs from the registration and settlement apparatus 51 having a cash settlement unit in that it does not have a cash settlement unit. In other words, the registration and settlement apparatus 51 and the registration and settlement apparatus 52 are common except for the points related to the presence or absence of the change dispenser 209. Therefore, a description of the external appearance and configuration example of the registration and settlement apparatus 52 with illustrations will be omitted.

[0054] (Registration device 53) FIG. 6 is a diagram for explaining the appearance of registration device 53. FIG. 7 is an example of the configuration of registration device 53. In FIG. 6 and FIG. 7, the same parts are given the same reference numerals. Registration device 53 includes a CPU 301, a ROM 302, a RAM 303, a hard disk 304, a customer display unit 305, a store clerk display unit 310, a key operation unit 311, a scanner unit 312, a printer unit 313, a voice output unit 314, and a communication unit 315. These can communicate with each other via a bus. Registration device 53 may further include a card settlement unit (a card settlement unit similar to card settlement unit 108 of settlement device 50) and the like.

[0055] The CPU 301, ROM 302, RAM 303, hard disk 304, audio output unit 314, and communication unit 315 of the registration device 53 are similar to the CPU 101, ROM 102, RAM 103, hard disk 104, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the explanation will be omitted.

[0056] The customer-side display unit 305 is a touch display that displays various information to the customer and accepts various inputs from the customer. Since the registration device 53 is a device where products are registered by the store clerk, the customer-side display unit 305 does not basically accept inputs for registering products, but does accept, for example, inputs for confirming the age of the customer with respect to the products registered by the store clerk.

[0057] The store clerk's display unit 310 is a touch display that displays various information to the store clerk and receives various inputs from the store clerk. The key operation section 311 has various buttons arranged thereon that are operated by the store clerk.

[0058] Scanner unit 312 is a scanner unit for store clerks, and optically reads various information. Specifically, scanner unit 312 scans codes attached to products and reads product codes (JAN codes, etc.). Scanner unit 312 may also scan codes attached to gift certificates and various cards and read the respective information. Scanner unit 312 may also scan codes attached to the name tags, etc. of store clerks and read the store clerk codes.

[0059] Scanner unit 312 is used when a store clerk registers a product, but the store clerk may register the product by other methods. For example, if a key corresponding to a product (such as a key corresponding to a sports newspaper) is arranged on key operation unit 311, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on store clerk-side display unit 310, the store clerk may operate that preset key to register the product.

[0060] The printing unit 313, for example, prints and issues various media (e.g., receipts). Various media are issued from an issuing port 313a and handed to the customer by a store clerk. Note that the registration device 53 does not issue receipts when sending registration information to another device (such as the settlement device 54). Also, if the registration device 53 is configured to include a card payment unit, the printing unit 313 may print and issue a receipt after payment is made by the card payment unit.

[0061] (Payment device 54) FIG. 8 is a diagram for explaining the appearance of the settlement device 54. FIG. 9 is a configuration example of the settlement device 54. In FIG. 8 and FIG. 9, the same parts are given the same reference numerals. The settlement device 54 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a customer side display unit 405, a scanner unit 406, a change machine (cash settlement unit) 409, a store clerk side display unit 410, a printing unit 413, an audio output unit 414, and a communication unit 415. These can communicate with each other via a bus. The settlement device 54 may further include a card settlement unit (a card settlement unit similar to the card settlement unit 108 of the settlement device 50) instead of or in addition to the change machine 409.

[0062] The CPU 401, ROM 402, RAM 403, hard disk 404, change machine 409, audio output unit 414, and communication unit 415 of the settlement device 54 are similar to the CPU 101, ROM 102, RAM 103, hard disk 104, change machine 109, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the description will be omitted.

[0063] Customer display unit 405 is a touch display that displays various information to the customer and accepts various inputs from the customer. For example, customer display unit 405 accepts input for confirming the amount inserted (deposited amount) (input to execute payment). In addition, if settlement device 54 is configured to include a card payment unit in addition to change machine 409, customer display unit 405 accepts input for selecting a payment method (payment type) (selection of whether to use cash payment via change machine 409 or various non-cash payments via the card payment unit).

[0064] The scanner unit 406 may, for example, scan codes attached to gift certificates and various cards to read the respective information. The scanner unit 406 may also scan codes attached to the name tags of store clerks and read the store clerk codes. The scanner unit 406 may also scan codes printed on bills and read the information required for the settlement process. The settlement device 54 is a device that settles the bill based on registration information registered by another device (e.g., the registration device 53, etc.), and for example, when adding a product, the scanner unit 406 may scan codes attached to the products and read the product codes (JAN codes, etc.).

[0065] The store clerk's display unit 410 displays various information to the store clerk. Note that the store clerk's display unit 410 may be a touch display and may receive various inputs from the store clerk. The printing unit 413 prints and issues various media (for example, receipts).

[0066] (Example of display on mobile terminal 60) FIG. 10 is a display example of the mobile terminal 60. FIG. 11 is a display example of the mobile terminal 60. FIG. 10(A) is a start screen (menu screen) of service A. When using (registering) service A, the mobile terminal 60 displays a start screen such as that shown in FIG. 10(A). Various buttons are arranged on the start screen. For example, the start screen has a start shopping button BT600 that accepts an instruction to start shopping. When a customer wants to start shopping, they operate the start shopping button BT600.

[0067] Fig. 10(B) is a registration screen (registration screen before registering one item of merchandise; initial registration screen) that is displayed after the shopping start button BT600 is operated on the start screen of Fig. 10(A). The upper side of the registration screen is a captured image display area HR601 that mainly displays captured images. The lower side of the registration screen is a registration information display area HR602 that mainly displays registration information for the merchandise.

[0068] Fig. 10(C) is a registration screen when the barcode attached to the product (XXX bread) is imaged on the registration screen of Fig. 10(B). That is, when a customer registers a desired product (a product to be purchased), the barcode attached to the product is read as shown in Fig. 10(C).

[0069] FIG. 10(D) is a registration screen after the product registration is completed (registration screen after product registration). Specifically, the mobile terminal 60 transmits the product code acquired from the barcode to the cloud server 20. The cloud server 20 refers to the product master and acquires the product name "XXX bread" and the price "¥220" based on the product code. The cloud server 20 stores the product information (product code, product name "XXX bread", quantity "1", price "¥220", etc.) as transaction information (cart information) of the transaction, and transmits the product information (product name "XXX bread", price "¥220", etc.) to the mobile terminal 60. The mobile terminal 60, which has received the product information from the cloud server 20, reflects the product information of the product in the registration information display area HR602. Specifically, as shown in Fig. 10(D), the mobile terminal 60 displays the registered information of the product (product name "XX bread", quantity "1", price "¥220") (symbol a), and displays total information (estimated total "1 item ¥220") (symbol b). The mobile terminal 60 displays part of the registered information (quantity) as a quantity button BT603. The quantity button BT603 is a button for changing the quantity.

[0070] After registering a product (one item of product), the mobile terminal 60 displays an operable Proceed to Checkout button BT604 for accepting checkout instructions, as shown in Fig. 10(D). When the customer wishes to proceed to payment (checkout) (when completing product registration), the customer operates the Proceed to Checkout button BT604.

[0071] FIG. 11(A) shows a registration screen after the registration of the second item (XX Oolong Tea) is completed following the scene of FIG. 10(D). That is, the mobile terminal 60 transmits the product code obtained from the barcode attached to the second item to the cloud server 20. The cloud server 20 refers to the product master and obtains the product name "XX Oolong Tea" and the price "¥150" based on the product code. The cloud server 20 stores the product information (product code, product name "XX Oolong Tea", quantity "1", price "¥150", etc.) as transaction information of the transaction, and transmits the product information (product name "XX Oolong Tea", price "¥150", etc.) to the mobile terminal 60. The mobile terminal 60, which has received the product information from the cloud server 20, reflects the product information of the second item in the registration information display area HR602. Specifically, as shown in FIG. 11(A), the mobile terminal 60 displays (adds) the registration information for the product (product name "XX Oolong Tea", quantity "1", price "¥150") and displays (updates) the total information (estimated total "2 items ¥370")

[0072] When a certain product a becomes a reserved product (described later) in a transaction of a certain mobile terminal 60, the cloud server 20 stores information that the product a is a reserved product as transaction information of the mobile terminal 60. Therefore, the transaction status management device 40 can refer to the transaction information stored in the cloud server 20 and recognize that the product a is a reserved product in the transaction of the mobile terminal 60 (or that the product a exists as a reserved product).

[0073] FIG. 11(B) shows a two-dimensional code display screen that is displayed after the button BT604 for proceeding to checkout is operated following the scene in FIG. 11(A). The two-dimensional code display screen shows a two-dimensional code 605 for checkout. The two-dimensional code 605 for checkout is a two-dimensional code of information required for executing checkout processing. For example, the two-dimensional code 605 for checkout is a two-dimensional code of transaction identification information (cart identification information) that identifies transaction information of the transaction from among multiple pieces of transaction information stored in the cloud server 20. Note that the information to be two-dimensionally coded does not have to be transaction identification information, as long as the transaction information of the transaction can be obtained after reading. For example, the two-dimensional code 605 for checkout may be a two-dimensional code of location information of the transaction information of the transaction (a storage location in the sales system 1, such as a Uniform Resource Identifier (URI)).

[0074] Additionally, an estimated total display area HR606 and a back button BT607 are arranged on the two-dimensional code display screen. In the example of FIG. 11(B), the estimated total display area HR606 displays the estimated total "2 items ￥370." The back button BT607 is a button for returning to shopping (restarting shopping). When the back button BT607 is operated, the mobile terminal 60 displays a registration screen (the registration screen displayed immediately before the Proceed to Checkout button BT604 is operated) instead of the two-dimensional code display screen.

[0075] Fig. 11(C) shows how the settlement device 50 reads the settlement two-dimensional code 605. After completing product registration, the customer causes the settlement device 50 to read the settlement two-dimensional code 605 displayed on the mobile terminal 60, as shown in Fig. 11(C).

[0076] (Example of display on settlement device 50) 12 and 13 are examples of displays on the settlement device 50. Fig. 12 shows an initial screen. When settling the bill for service A, the settlement device 50 displays the initial screen as shown in Fig. 12.

[0077] The initial screen displays a message and a guide map to read the two-dimensional code 605 (QR code (registered trademark) in the figure) for settlement displayed on the mobile terminal 60. Also arranged on the initial screen are a store clerk call button BT501, a balance inquiry button BT502, and language switch buttons BT503 to BT505. The store clerk call button BT501 is a button for calling a store clerk. The balance inquiry button BT502 is a button for inquiring about the balance of various cards. The language switch button BT503 is a button for switching the display (text) on the initial screen from Japanese to English. The language switch button BT504 is a button for switching to Chinese. The language switch button BT505 is a button for switching to Korean.

[0078] After completing product registration, the customer follows the instructions on the initial screen and has the settlement device 50 read the two-dimensional settlement code 605 displayed on the mobile terminal 60 (FIG. 10(C)).

[0079] 13 is a product list screen displayed after reading the two-dimensional settlement code 605, following the scene in Fig. 12. That is, when the settlement device 50 reads the two-dimensional settlement code 605, it displays the product list screen as shown in Fig. 12.

[0080] The product list screen has a product list display area HR510, a product quantity by price range display area HR511, and a total display area HR512. In addition, a store clerk call button BT501 and a checkout button BT509 are arranged on the product list screen. The checkout button BT509 is a button for confirming that there are no problems with the contents displayed on the product list screen and for proceeding with the process. When the checkout button BT509 is operated, the settlement device 50 displays, for example, a payment type selection screen (not shown).

[0081] The product list display area HR510 is an area for displaying a list of products to be settled (purchased). The settlement device 50 displays, in the product list display area HR510, a list of products (product name, quantity, price) included in the transaction information acquired from the cloud server 20 by reading the settlement two-dimensional code 605. In the example of FIG. 13, the settlement device 50 displays XX bread and XX oolong tea in the product list display area HR410.

[0082] The price range item quantity display area HR511 is an area for displaying the quantity of items to be paid for (purchased) by price range (1000 yen or more, 500 yen or more but less than 1000 yen, 200 yen or more but less than 500 yen, less than 200 yen).

[0083] The total display area HR512 is an area for displaying the total of the transaction. In the example of FIG. 13, the settlement device 50 displays in the total display area HR512 a total number of items of 2 (indicated as "Total of 2 items" in the figure), an estimated total amount of 370 yen (indicated as "Estimated total (amount displayed on smartphone) 370 yen"), and a final total amount of 370 yen (indicated as "Final total (amount to be paid) 370 yen" in the figure). The estimated total amount of 370 yen is the total amount displayed on the mobile terminal 60 (i.e., the total amount before the process related to the sale price (described later) is executed). The final total amount of 370 yen is the total amount recalculated by the settlement device 50 (i.e., the total amount after the process related to the sale price (described later) is executed).

[0084] (Processing regarding special sale prices) When the settlement device 50 acquires transaction information from the cloud server 20 after reading the settlement two-dimensional code 605, it refers to the sale file and judges whether the product included in the transaction information matches the sale conditions (i.e., whether a sale (discount, discount, etc.) is applied). If the sale conditions match, it acquires the sale contents (sale price, etc.) from the sale file, recalculates the total amount, and reflects it in the transaction information. Specifically, the settlement device 50 stores the sale price, etc. acquired from the sale file additionally (separately) without erasing (overwriting) the product price, etc. before the sale price is applied, and stores the recalculated total amount additionally (separately) without erasing the total amount before the recalculation. In other words, the settlement device 50 refers to the sale file that was not referenced when the product was registered on the mobile terminal 60, and if the conditions for applying the sale price (sale) are met, it acquires the sale price, etc. to be applied from the sale file, recalculates the total amount, and reflects it in the transaction information. If the conditions for the sale are not met, the settlement device 50 does not apply the sale price, so the final total amount is the same as the estimated total amount. The example in Fig. 13 is a display example when the conditions for the sale are not met (when the sale price is not applied).

[0085] Fig. 14 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, the sequence diagram of Fig. 14 shows an example of the processing of the mobile terminal 60 and the cloud server 20 (product registration processing in service A) from when one product is registered on the mobile terminal 60 until the two-dimensional code for payment 605 is displayed. The left side of Fig. 14 shows the processing of the mobile terminal 60, and the right side shows the processing of the cloud server 20. It is assumed that at the start of the sequence diagram of Fig. 14 (the start of the processing of step S1 for the first time), the mobile terminal 60 displays an initial registration screen as shown in Fig. 10(B).

[0086] Step S1: The mobile terminal 60 reads the barcode attached to the product in response to a reading operation by the customer. That is, the mobile terminal 60 acquires the product code from the barcode attached to the product in response to a reading operation by the customer. Step S2: The mobile terminal 60 transmits to the cloud server 20 transaction identification information for identifying the transaction information of the transaction, and the product code acquired in step S1.

[0087] Step S3: The cloud server 20 receives the transaction identification information and the product code. Step S4: Cloud server 20 updates the transaction information of the transaction (transaction information corresponding to the transaction identification information) based on the product code. That is, cloud server 20 acquires (extracts) the product name and price corresponding to the product code received in step S3 from the product master, and stores the product code, product name, quantity (1), and price in the transaction information corresponding to the transaction identification information received in step S3.

[0088] Step S5: The cloud server 20 transmits product information (such as product name and price) of the product code to the mobile terminal 60. For example, the cloud server 20 generates screen information that reflects the contents of the updated transaction information, and transmits it to the mobile terminal 60.

[0089] Step S6: The mobile terminal 60 receives the product information (screen information) of the product code. Step S7: The mobile terminal 60 updates the registration screen based on the information (screen information) received in step S6. Steps S1 to S7 are repeatedly executed by reading the barcode attached to the product.

[0090] Step S8: The mobile terminal 60 generates a two-dimensional code 605 for payment based on the customer's payment instructions (operation of the Proceed to Payment button BT604) and displays it on the two-dimensional code display screen. Then, the sequence diagram in FIG. 9 ends.

[0091] Fig. 15 is a sequence diagram showing an example of the processing of the settlement device 50 and cloud server 20. Specifically, the sequence diagram of Fig. 15 shows an example of the processing of the settlement device 50 and cloud server 20 (settlement processing in service A) from when the settlement two-dimensional code 605 is read by the settlement device 50 to when the product list screen is displayed. The left side of Fig. 15 shows the processing of the settlement device 50, and the right side shows the processing of the cloud server 20. It is assumed that at the start of the sequence diagram of Fig. 15, the settlement device 50 is displaying an initial screen such as that shown in Fig. 12.

[0092] Step S11: In response to a reading operation by the customer, the settlement device 50 reads the settlement two-dimensional code 605 displayed on the mobile terminal 60. That is, the settlement device 50 obtains transaction identification information that identifies the transaction information of the transaction. Step S12: The settlement device 50 requests transaction information of the transaction from the cloud server 20. For example, the settlement device 50 transmits request information (transaction information acquisition request information) including transaction identification information that identifies the transaction information of the transaction to the cloud server 20.

[0093] Step S13: The cloud server 20 receives the request (transaction information acquisition request information). Step S14: In response to the request, the cloud server 20 transmits the transaction information of the transaction to the settlement device 50. For example, the cloud server 20 transmits to the settlement device 50 the transaction information corresponding to the transaction identification information included in the transaction information acquisition request information received in step S13.

[0094] Step S15: The settlement device 50 receives and stores the transaction information of the transaction. Step S16: The settlement device 50 refers to the sale file, and if the sale conditions match, obtains the details of the sale (sale price, etc.), recalculates the total amount, and reflects it in the transaction information (additionally stores it). The details of step S16 have already been explained in "Processing related to the sale price", so they will be omitted here. Step S17: The settlement device 50 displays a product list screen based on the transaction information, and the sequence diagram in FIG. 15 ends.

[0095] Second embodiment Fig. 16 is a conceptual diagram of a network for explaining a sales system 2 of the second embodiment. The sales system 2 shown in Fig. 16 includes a headquarters server 10, a cloud server 20, a store controller 30, a transaction status management device 40, a settlement device 50, a registration device 53, a settlement device 54, and a mobile terminal 60.

[0096] The sales system 2 of the second embodiment differs from the sales system 1 of the first embodiment in that it does not include a registration settlement device 51 and a registration settlement device 52. The headquarters server 10, cloud server 20, store controller 30, transaction status management device 40, settlement device 50, registration device 53, settlement device 54, and mobile terminal 60 in the sales system 2 of the second embodiment are the same as the headquarters server 10, cloud server 20, store controller 30, transaction status management device 40, settlement device 50, registration device 53, settlement device 54, and mobile terminal 60 in the sales system 1 of the first embodiment, and therefore description thereof will be omitted.

[0097] In addition to service A, the sales system 2 can also provide a service in which, for example, a store clerk uses the registration device 53 to register an item, and a customer uses the settlement device 54 to settle the payment.

[0098] Third embodiment Fig. 17 is a conceptual diagram of a network for explaining a sales system 3 of a third embodiment. The sales system 3 shown in Fig. 17 includes a headquarters server 10, a cloud server 20, a store controller 30, a transaction status management device 40, a settlement device 50, a registration device 53, a settlement device 54, a registration settlement device 59, and a mobile terminal 60.

[0099] The sales system 3 of the third embodiment differs from the sales system 1 of the first embodiment in that it includes a registration settlement device 59 instead of the registration settlement device 51 and the registration settlement device 52. The headquarters server 10, cloud server 20, store controller 30, transaction status management device 40, settlement device 50, registration device 53, settlement device 54, and mobile terminal 60 in the sales system 3 of the third embodiment are the same as the headquarters server 10, cloud server 20, store controller 30, transaction status management device 40, settlement device 50, registration device 53, settlement device 54, and mobile terminal 60 in the sales system 1 of the first embodiment, so description thereof will be omitted.

[0100] In addition to service A, the sales system 3 can also provide services in which, for example, a store clerk uses registration device 53 to register a product and a customer uses settlement device 54 to settle the payment, or a store clerk uses registration settlement device 59 to register a product and then settle the payment.

[0101] The registration and settlement device 59 is mainly used by store clerks. Specifically, the registration and settlement device 59 has a scanner unit and a settlement unit (specifically, a cash settlement unit) on one side (the store clerk side). The configuration of the registration and settlement device 59 will be described later.

[0102] (Registration settlement device 59) FIG. 18 is a diagram for explaining the appearance of the registration settlement device 59. FIG. 19 is a configuration example of the registration settlement device 59. In FIG. 18 and FIG. 19, the same parts are given the same reference numerals. The registration settlement device 59 includes a CPU 501, a ROM 502, a RAM 503, a hard disk 504, a customer side display unit 505, a scanner unit 506, a change machine (cash settlement unit) 509, a store clerk side display unit 510, a key operation unit 511, a printing unit 513, a voice output unit 514, and a communication unit 515. These can communicate with each other via a bus. The registration settlement device 59 may further include a card settlement unit (a card settlement unit similar to the card settlement unit 108 of the settlement device 50), an imaging unit (an imaging unit similar to the imaging unit 116 of the settlement device 50), etc.

[0103] The CPU 501, ROM 502, RAM 503, hard disk 504, audio output unit 514, and communication unit 515 of the registered settlement device 59 are similar to the CPU 101, ROM 102, RAM 103, hard disk 104, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the description will be omitted.

[0104] Customer-side display unit 505 is a touch display that displays various information to the customer and accepts various inputs from the customer. Since registration and settlement device 59 is a device where products are registered by the store clerk, customer-side display unit 505 does not basically accept inputs for registering products, but does accept, for example, inputs for confirming the age of the customer for the products registered by the store clerk.

[0105] The store clerk's display unit 510 is a touch display that displays various information to the store clerk and receives various inputs from the store clerk. The key operation section 511 has various buttons arranged thereon that are operated by the store clerk.

[0106] Scanner unit 512 is a scanner unit for store clerks, and optically reads various information. Specifically, scanner unit 512 scans codes attached to products and reads product codes (JAN codes, etc.). Scanner unit 512 may also scan codes attached to gift certificates and various cards and read the respective information. Scanner unit 512 may also scan codes attached to the name tags, etc. of store clerks and read the store clerk codes.

[0107] Printing unit 513 prints and issues, for example, various media (e.g., receipts). Various media are issued from issuing port 513a and handed to the customer by the store clerk. If registration and settlement device 59 is configured not to have a card payment unit as shown in the figure, a bill may be issued by printing unit 513, or registration information may be sent to another device by communication unit 515, so that card payment is carried out in another device. On the other hand, if registration and settlement device 59 is configured to have a card payment unit, printing unit 513 may print and issue a receipt after payment is made by the card payment unit.

[0108] (Example 1 relating to installation layout) Fig. 20 is an example (Example 1 relating to installation layout) of the installation layout of each device in the sales system 1 (Fig. 1) of the first embodiment. Note that in Fig. 20 (and the other figures as well), the store controller 30 is not shown.

[0109] In FIG. 20 (as well as other figures), the upper side of the figure (area A shown by dashed lines) shows the sales floor of the store according to Example 1, and the center of the figure (area B shown by dashed lines) shows the checkout area of ​​the store. At the bottom of the figure (the opposite side of the sales floor as seen from the checkout area) are installed a shopping counter for bagging etc., and a service counter for accepting consultations, applications etc. Also, the bottom right of the figure is the exit. Note that in this figure (as well as in FIGS. 21 to 23), the area that does not include the shopping counter or the service counter is referred to as the checkout area, but an area that includes at least one of the shopping counter and the service counter may also be referred to as the checkout area. Note that in FIG. 24, the area that includes the service counter is referred to as the checkout area.

[0110] As shown in Fig. 20, the accounting area is provided with three settlement devices 50 (settlement devices 50-1 to 50-3), three registered settlement devices 51 (registered settlement devices 51-1 to 51-3), four registered settlement devices 52 (registered settlement devices 52-1 to 52-4), two registered devices 53 (registered devices 53-1, 53-2), four settlement devices 54 (settlement devices 54-1 to 54-4), and one transaction status management device 40. The registered settlement devices 51-1 to 51-3 (as well as the registered settlement devices 51-1 to 51-4) have multiple operating modes, but all are set to full self-service mode (however, this can be changed as appropriate).

[0111] In Fig. 20, each of KD1-KD4 shown by dotted lines is a checkout flow (checkout lead) formed in the same store. In Fig. 20 (as in other figures), people with shaded bodies (e.g., people with the letter T) are store clerks, and people with plain bodies (e.g., people with the letter K) are customers. The area C shown by the dashed line will be described later.

[0112] (Accounting flow KD1, KD2) The transaction flow line KD1 is a transaction flow that forms a transaction flow in which a store clerk registers products using registration device 53-1, and a customer uses settlement device 54-1 or settlement device 54-2 to pay for the products registered in registration device 53-1. The transaction flow line KD2 is a transaction flow that forms a transaction flow in which a store clerk registers products using registration device 53-2, and a customer uses settlement device 54-2 or settlement device 54-3 to pay for the products registered in registration device 53-2.

[0113] A customer who has put all the items they need in the sales floor into their basket and wishes to check out semi-self-service (specifically, having a store clerk register the items and paying for them themselves) will take the basket and enter the checkout area from the sales floor, as shown by checkout flow line KD1 or checkout flow line D2.

[0114] In the checkout flow line KD1, the clerk uses the registration device 53-1 to register the products (and a paid shopping bag, if necessary) while transferring the products from the basket handed to him by the customer (the basket in which the customer puts the products at the sales floor) to an empty basket. After the clerk has finished registering the products, he performs an operation to select one of the settlement devices 54-1 and 54-2 as the settlement device 54 that will settle the payment for the registered products, and guides the customer (informs the customer of the selected settlement device 54). The customer moves to the indicated settlement device 54 with the basket in which the registered products are placed (the basket into which the products were moved when registering), and settles the payment. In other words, the registration device 53-1 registers the products based on the operation of the clerk, and transmits the registration information to the settlement device 54 selected based on the operation of the clerk. The settlement device 54 that receives the registration information from the registration device 53-1 settles the payment for the products registered in the registration device 53-1 based on the customer's operation. After paying at the payment device 54, the customer moves to the shopping counter with the basket containing the paid-for items, puts the items in the basket into a bag (a personal bag or a paid shopping bag), returns the empty basket to the return area (not shown), and moves to the exit to leave the store.

[0115] After completing the product registration, the store clerk may operate a send button instead of selecting one of the settlement devices 54-1 and 54-2, and guide the customer (informing the customer of one of the settlement devices 54-1 and 54-2 that is automatically selected after operating the send button and notified to the store clerk as the destination for the registration information).

[0116] Also, after registering the products, the store clerk may, instead of selecting one of the settlement devices 54-1 and 54-2 or pressing the send button, operate to print and issue a receipt and guide the customer (informing the customer that the receipt will be read by one of the settlement devices 54-1 and 54-2). When a receipt is issued, the customer moves to the settlement device 54-1 (or 54-2) with the basket containing the registered products, and settles the payment after the receipt is read. In other words, the registration device 53-1 may print and issue a receipt based on the operation of the store clerk, and the settlement device 54-1 (as well as the settlement device 54-2) that reads the receipt may settle the products registered in the registration device 53-1 based on the customer's operation.

[0117] The operation of each device on transaction flow line KD2 (registration device 53-2, settlement device 54-3, settlement device 54-4) is similar to the operation of each device on transaction flow line KD1 (registration device 53-1, settlement device 54-1, settlement device 54-2), so explanation is omitted.

[0118] (Accounting flow KD3) Accounting flow KD3 is an accounting flow that forms an accounting flow in which a customer registers products and settles using registered settlement devices 51-1 to 51-3 or registered settlement devices 52-1 to 52-4. Registered settlement devices 51-1 to 51-3 are devices that support both cash and non-cash payments. Registered settlement devices 52-1 to 51-4 are devices that support only non-cash payments. As described above, registered settlement devices 51-1 to 51-3 (as well as registered settlement devices 52-1 to 52-4) have multiple operating modes, but all are set to full self-service mode.

[0119] A customer who has put all the products he or she needs in the sales floor into the basket and wishes to check out completely by himself or herself (registering the products and paying for them himself or herself) will take the basket and enter the checkout area from the sales floor as shown by checkout flow line KD3.

[0120] In the checkout flow line KD3, a customer who plans to pay in cash moves to one of the registered settlement devices 52-1 to 52-4 with a basket (a basket containing products at the sales floor), registers the products (and a plastic bag for a fee if necessary), and settles the payment by cash. Also, a customer who plans to pay non-cash moves to one of the registered settlement devices 51-1 to 51-3 or 52-1 to 52-4 with a basket, registers the products (and a plastic bag for a fee if necessary), and settles the payment by non-cash. In other words, the registered settlement device 51-1 (as well as the registered settlement device 51-2 and the registered settlement device 51-3) registers the products based on the customer's operation and settles the payment by cash or non-cash. The registered settlement device 52-1 (as well as the registered settlement devices 52-2 to 52-4) registers the products based on the customer's operation, and settles the payment by non-cash.

[0121] In addition, since the customer packs the items placed in the basket into a bag (a reusable shopping bag) at registered settlement device 51-1 (the same applies to registered settlement device 51-2, registered settlement device 51-3, registered settlement device 52-1 to registered settlement device 52-4), after payment at registered settlement device 51-1 (the same applies to registered settlement device 51-2, registered settlement device 51-3, registered settlement device 52-1 to registered settlement device 52-4), the customer does not move to the shopping counter after payment, but returns the empty basket to the return location (not shown) and moves to the exit to leave the store.

[0122] (Accounting flow KD4) The transaction flow line KD4 is a transaction flow line in which the customer uses the mobile terminal 60 to settle the payment for the products that the customer has registered, using the settlement devices 50-1 to 50-3.

[0123] A customer who has registered all the products he or she requires in the sales floor using a mobile terminal 60 and placed them in a basket or the like and wishes to pay by himself or herself (specifically, to settle the bill himself or herself) enters the checkout area from the sales floor with the basket or the like, as shown by checkout flow line KD4.

[0124] In the checkout flow line KD4, the customer moves to one of the checkout machines 50-1 to 50-3 with the basket or the like, registers the products (and a paid shopping bag, if necessary), and checks out. In other words, the checkout machine 50-1 (as well as the checkout machines 50-2 and 50-3) checks out the products registered in the sales area using the mobile terminal 60 based on the customer's operation.

[0125] In addition, since the customer packs the items placed in the basket etc. into a bag (a personal bag, a paid shopping bag) at the settlement device 50-1 (the same applies to settlement devices 50-2 and 50-3), after settlement at the settlement device 50-1 (the same applies to settlement devices 50-2 and 50-3), the customer does not move to the footer after settlement, but returns the empty basket etc. to a return location (not shown) and moves to the exit to leave the store.

[0126] (About the guide) Although not shown in the figure, at the boundary between the sales floor and the checkout area, guidance (alerts) are given to customers to show them which of the checkout paths KD1-4 they should take, and to guide them to the most suitable checkout path. For example, customers are guided by standing signs, hanging from the ceiling, printed on the floor, or by signage devices (e.g., signage devices connected to LAN 19 and controllable by transaction status management device 40). This allows customers to be smoothly guided to the most suitable (desired or selected according to the mode of registration or checkout) path. The notification method is easy to see, using letters, colors, symbols (e.g., arrows, circles, crosses, etc.), or a combination of these.

[0127] Also, guidance may be provided according to the payment method. For example, the accounting flow line KD3 may be divided into two (guiding a path to a registered settlement device 51 (cash compatible device) that supports cash payments, and a path to a registered settlement device 52 (non-cash compatible device) that does not support cash payments), and guidance may be provided separately for customers who wish to pay in cash (cash payment customers) and customers who wish to pay non-cash (non-cash payment customers). This can reduce the occurrence of problems such as a cash payment customer mistakenly using a non-cash compatible device, or a cash payment customer being unable to use a cash payment device because a non-cash payment customer is using it.

[0128] Also, for example, when a certain device is unavailable depending on the time period, the number of customers in the store, the number of store clerks, etc., it may be notified that a transaction cannot be made using the transaction flow using that device (that transaction flow cannot be used). For example, when the registration device 53-1 is out of service due to the absence of a store clerk, it may be notified that a transaction cannot be made using the transaction flow KD1. Also, when both the settlement device 54-3 and the settlement device 54-4 are undergoing maintenance (for example, while a closing process is being performed), it may be notified that a transaction cannot be made using the transaction flow KD2 (if an exceptional operation is performed, such as specifying the settlement devices 54-1 and 54-2 from the registration device 53-2, a transaction can be made using the transaction flow KD2). Note that the signage device may be controlled so that the latest information regarding the availability of the transaction flow is displayed based on the status of each device (for example, the presence or absence of a store clerk at the registration device 53 (for example, login / logout information), and information on whether the settlement device 54 is undergoing maintenance) (obtained from each device). Furthermore, even when a notice is given by a signboard or the like instead of a signage device, the registration device 53 may notify the user of the signboard or the like (notify the user of removing the signboard or turning it over) when the status of each device changes (for example, when logging out from the registration device 53, when maintenance of the settlement device 54 is started, etc.). This prevents the store clerk from forgetting what to do with the signboard or the like, and thus makes it possible to prevent the user from being guided to a checkout route that should not be followed. Note that the destination of the notice for the signboard or the like is not limited to the registration device 53 that has been logged out, and for example, the transaction status management device 40 may be notified instead of or in addition to the registration device 53 that has been logged out. As a result, for example, when the transaction status management device 40 is notified in addition to the registration device 53, the store clerk of the transaction status management device 40, who overlooks and monitors the entire checkout area, is also notified, so that it is possible to more reliably prevent the user from being guided to a checkout route that should not be followed. In addition, when only the transaction status management device 40 is notified, it is possible to effectively prevent the store clerk at the transaction status management device 40, who is in charge of monitoring the entire checkout area, from continuing to guide customers along checkout routes that should not be followed.

[0129] In addition, the above describes the case where a state changes from available to unavailable, but the same applies to the case where a state changes from unavailable to available. For example, if the checkout flow lines KD3 and KD4 are used when the store opens, and checkout flow lines KD1 and KD2 are used sequentially from the time the store is crowded, a notification may be given that checkout flow line KD1 is now available when the user logs in to registration device 53-1, and a notification may be given that checkout flow line KD2 is now available when the user logs in to registration device 53-2. This allows prompt guidance to the checkout flow lines that have become available. The above guidance is also applicable to other embodiments (embodiments 2 to 5) relating to installation layouts, which will be described later.

[0130] In the above, examples have been described in which guidance using signage devices, standing signs, hanging signs, floor printing, etc. is provided at the boundary between the sales floor and the checkout area, but similar guidance may be provided in other locations instead of or in addition to the boundary between the sales floor and the checkout area. For example, guidance may be provided at the entrance of a store. When providing guidance at the entrance of a store, guidance information may include, for example, the congestion status of each checkout flow line based on the number of store staff (work schedule, activity schedule, etc.). For example, according to the schedule, there is currently no store staff at registration device 53-1, so information that checkout flow line KD-1 is not available may be provided on a signage device at the entrance. Instead of or in addition to the congestion status of each checkout flow line based on the number of store staff, the actual congestion status of each checkout flow line may be provided. As an example, cameras may be installed in the store and the number of customers (large or small) lined up on each checkout flow line may be recognized by image processing, and the actual congestion status of each checkout flow line may be provided. When providing guidance at the entrance of a store, guidance information may, for example, guide the type of service (checkout flow) according to the number of items purchased (in other words, guide the efficiency of each device according to the number of items purchased). In other words, if it is known from experience that when the number of items purchased is less than A (A is an integer), the transaction along the checkout flow KD3 allows the customer to complete shopping the fastest, when the number of items purchased is between points A and B (B is an integer greater than A), the transaction along the checkout flow KD1 and KD2 allows the customer to complete shopping the fastest, and when the number of items purchased is more than B, the transaction along the checkout flow KD4 (service A) allows the customer to complete shopping the fastest. Since the optimal checkout flow differs depending on the number of items purchased, it is very effective for both the customer and the store to guide such information to the customer at the entrance in advance. For example, the customer can check the above information at the entrance when starting shopping, and while appropriately checking the current number of items purchased at the start of shopping or during shopping in the store, recognize and select the most suitable transaction (service, checkout flow). Also, a currently recommended transaction (service, checkout flow) may be calculated and provided based on two pieces of information: congestion status (congestion status based on the number of store staff, actual congestion status) and efficiency by device. This calculation may be performed by any device in the sales system 1 (that is, any of the headquarters server 10, cloud server 20, store controller 30, transaction status management device 40, settlement device 50, registration settlement devices 51, 52, registration device 53, settlement device 54, and mobile terminal 60). Also, two or more devices may share the work. Although the other location is described as the entrance of the store, it may be another location within the store. In this way, guidance can be given appropriately.

[0131] (Example 2 relating to installation layout) 21 is an example (Example 2 relating to installation layout) of the installation layout of each device in the sales system 1 (FIG. 1) of the first embodiment. However, in Example 2, the registration and settlement device 52 is not installed.

[0132] As shown in FIG. 21, the transaction area includes two settlement devices 50 (settlement devices 50-1 and 50-2), four registered settlement devices 51 (registered settlement devices 51-1 to 51-4), four registered devices 53 (registered devices 53-1 to 53-4), four registered settlement devices 54 (settlement devices 54-1 to 54-4), and one transaction status management device 40. The registered settlement devices 51-1 to 51-4 have multiple operation modes, but the registered settlement devices 51-1 and 51-2 are set to a settlement-only mode, and the registered settlement devices 51-3 and 51-4 are set to a full self-service mode (however, this can be changed as appropriate). In addition, the registered settlement device 53-4 is not staffed. In FIG. 21, each of KD5 to KD9 shown by a dotted line is a transaction flow line formed in the same store.

[0133] (Accounting flow KD5, KD6) The operation of each device on accounting flow line KD5 (registration device 53-1, settlement device 54-1, settlement device 54-2) and each device on accounting flow line KD6 (registration device 53-2, settlement device 54-3, settlement device 54-4) are similar to the operation of each device on accounting flow line KD1 in the above-mentioned Example 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so explanation is omitted.

[0134] (Accounting flow KD7, KD8) The accounting flow line KD7 is an accounting flow in which a store clerk uses registration device 53-3 to register products, and a customer uses registration and settlement device 51-1 or registration and settlement device 51-2 to settle the payment for the products registered in registration device 53-3. The accounting flow line KD8 is an accounting flow in which a customer uses registration and settlement device 51-3 or registration and settlement device 51-4 to register products and settle the payment.

[0135] A customer who has put all the products he needs in his basket on the sales floor and wants to pay semi-self (specifically, have a sales clerk register the products and pay by himself) takes the basket and enters the checkout area from the sales floor as shown by checkout flow KD7. On the other hand, a customer who has put all the products he needs in his basket on the sales floor and wants to pay fully self (specifically, register the products and pay by himself) takes the basket and enters the checkout area from the sales floor as shown by checkout flow KD8.

[0136] In the checkout flow KD7, the clerk uses the registration device 53-3 to register the products (and a paid shopping bag, if necessary) while transferring the products from the basket handed to him by the customer (the basket in which the customer puts the products at the sales floor) to an empty basket. After the clerk has finished registering the products, he performs an operation to select one of the registration settlement devices 51-1 and 51-2 operating in a settlement-only mode as the registration settlement device 51 that will settle the payment for the registered products, and guides the customer (informing the customer of the selected registration settlement device 51). The customer moves to the registration settlement device 51 to which he has been guided with the basket in which the registered products are put, and settles the payment. In other words, the registration device 53-3 registers the products based on the operation of the clerk, and transmits the registration information to the registration settlement device 51 selected based on the operation of the clerk. The registration settlement device 51 that has received the registration information from the registration device 53-3 settles the payment for the products registered in the registration device 53-3 based on the customer's operation. After paying at the registered payment device 51, the customer carries the basket to the shopping stand, packs the items in the basket into a bag (a personal bag or a paid shopping bag), returns the empty basket to the return area (not shown), and moves to the exit to leave the store.

[0137] In addition, after completing the product registration, the store clerk may operate the send button instead of selecting one of the registered settlement devices 51-1 and 51-2, and guide the customer (informing the customer of one of the registered settlement devices 51-1 and 51-2 that is automatically selected after operating the send button and notified to the store clerk as the destination to which the registration information is to be sent).

[0138] Also, after completing the registration of the products, the store clerk may operate to print and issue a receipt and guide the customer (inform the customer that the receipt will be read by one of the registered settlement devices 51-1 and 51-2) instead of operating to select one of the registered settlement devices 51-1 and 51-2 or operating the send button. When a receipt is issued, the customer moves to the registered settlement device 51-1 (or the registered settlement device 51-2) with the basket containing the registered products, and after the receipt is read, the customer pays. In other words, the registration device 53-3 may print and issue a receipt based on the operation of the store clerk, and the registered settlement device 51-1 (or the registered settlement device 51-2) that reads the receipt may pay for the products registered in the registration device 53-3 based on the customer's operation.

[0139] In checkout flow KD8, since there is no store clerk at registration device 53-4, the customer passes in front of registration device 53-4 with a basket and moves to registration and settlement device 51-3 (or registration and settlement device 51-4), where the customer registers the items (and a paid plastic bag, if necessary) and pays.

[0140] In other words, the transaction mode according to transaction flow KD7 in Example 2 is a mode in which a registered settlement device 51 is used instead of settlement device 54 in transaction flow KD1 in Example 1 (the same is true for transaction flow KD2 in Example 1 and transaction flow KD and KD6 in Example 2). Also, the transaction mode according to transaction flow KD8 in Example 2 is similar to the transaction mode according to transaction flow KD3 in Example 1 (a mode in which a registered settlement device 51 is used), without using registration device 53-4 where no store clerk is present.

[0141] Depending on the congestion level of the store, etc., registration device 53-3 of the checkout flow KD7 may not be used, and the products (and paid plastic bags, if necessary) may be registered and settled at registration and settlement device 51-1 (or registration and settlement device 51-2). In other words, the checkout pattern according to the checkout flow KD7 may be the same as the checkout pattern according to the checkout flow KD8. Depending on the congestion level of the store, etc., registration device 53-4 of the checkout flow KD8 may be used, and the products registered at registration device 53-4 may be settled at registration and settlement device 51-3 (or registration and settlement device 51-4). In other words, the checkout pattern according to the checkout flow KD8 may be the same as the checkout pattern according to the checkout flow KD7.

[0142] The registered settlement device 51-1 (as well as the registered settlement device 51-2) may operate in a settlement-only mode when the clerk is using the registration device 53-3, and may operate in a full self-service mode when the clerk is not using the registration device 53-3. Similarly, the registered settlement device 51-3 (as well as the registered settlement device 51-4) may operate in a settlement-only mode when the clerk is using the registration device 53-4, and may operate in a full self-service mode when the clerk is not using the registration device 53-4.

[0143] For example, when the registration device 53-3 reads the clerk code for login, it notifies the registered settlement device 51-1 and the registered settlement device 51-2 that it has started using the device, and the registered settlement device 51-1 (as well as the registered settlement device 51-2) may switch to the settlement-only mode if the operation mode is not the settlement-only mode when the registration device 53-3 receives the notification. Also, when the registration device 53-3 receives an operation from a clerk (for example, a clerk leaving the registration device 53-3), it notifies the registered settlement device 51-1 and the registered settlement device 51-2 that it has ended using the device, and the registered settlement device 51-1 (as well as the registered settlement device 51-2) may switch to the full self-service mode if the operation mode is not the full self-service mode when the registration device 53-3 receives the notification. The same applies to the registration devices 53-4, 51-3, and 51-4.

[0144] (Accounting flow KD8) The operation of each device (settlement device 50-1, settlement device 50-2) on transaction flow KD9 is similar to the operation of each device (settlement device 50-1 to settlement device 50-3) on transaction flow KD4 in the above-mentioned Example 1 (Figure 20), so explanation will be omitted.

[0145] (Example 3 relating to installation layout) FIG. 22 is an example (Example 3 relating to installation layout) of the devices in the sales system 2 (FIG. 16) of the second embodiment.

[0146] As shown in Figure 22, the checkout area is equipped with six settlement devices 50 (settlement devices 50-1 to 50-6), four registration devices 53 (registration devices 53-1 to 53-4), six settlement devices 54 (settlement devices 54-1 to 54-6), and one transaction status management device 40. In Figure 22, KD10 to KD14 indicated by dotted lines each represent a checkout flow line formed in the store.

[0147] (Accounting Flow KD10) The operation of each device (settlement device 50-1 to settlement device 54-6) on the transaction flow KD10 is the same as that of each device (settlement device 50-1 to settlement device 50-3) on the transaction flow KD4 in the above-mentioned embodiment 1 (FIG. 20), so a description thereof will be omitted. Note that the row of settlement devices 50-1 to 54-3 and the row of settlement devices 50-3 to 54-6 are installed back-to-back (installed so that customers in different rows face each other across the device), so transaction flow KD10 and transaction flow DK10 branch into two along each row. Note that transaction flow KD10 may be passed between the row of settlement devices 50-1 to 54-3 and the row of settlement devices 50-3 to 54-6 so that customers in different rows can operate back-to-back.

[0148] (Accounting flow KD11, KD12) The operation of each device on the transaction flow line KD11 (registration device 53-1, settlement device 54-1, (settlement device 54-2)) and each device on the transaction flow line KD12 (registration device 53-2, settlement device 54-3, (settlement device 54-2)) is similar to the operation of each device on the transaction flow line KD1 in the above-mentioned Example 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so explanation will be omitted. Note that settlement device 54-2 is a device on both transaction flow line KD11 and transaction flow line KD12. In other words, settlement device 54-2 settles both the products registered in registration device 53-1 and the products registered in registration device 53-2.

[0149] (Accounting Flow KD13) The operation of each device on the accounting flow line KD13 (registration device 53-4, settlement device 54-5, settlement device 54-6) is similar to the operation of each device on the accounting flow line KD1 in the above-mentioned Example 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so explanation is omitted.

[0150] (Accounting Flow KD14) The operation of each device (registration device 53-3, settlement device 54-4) on transaction flow KD14 is similar to the operation of each device (registration device 53-1, settlement device 54-1, settlement device 54-2) on transaction flow KD1 in the above-mentioned Example 1 (Figure 20), so a description will be omitted. Note that there is only one settlement device 54 on transaction flow KD13. When there is only one settlement device 54, it is not necessary to select a destination to send the registration information.

[0151] (Example 4 relating to installation layout) FIG. 23 shows another example (Example 4 relating to installation layout) of the installation layout of the devices in the sales system 2 (FIG. 16) of the second embodiment.

[0152] As shown in Figure 23, the checkout area is equipped with one settlement device 50, five registration devices 53 (registration devices 53-1 to 53-5), five settlement devices 54 (settlement devices 54-1 to 54-5), and one transaction status management device 40. In Figure 23, KD15 to KD20 indicated by dotted lines each represent a checkout flow line formed in the store.

[0153] (Accounting flow KD15, KD16, KD18, KD19, KD20) The operation of each device on accounting flow line KD15 (registration device 53-1, settlement device 54-1) is similar to the operation of each device on accounting flow line KD14 in the above-mentioned embodiment 3 (FIG. 23) (registration device 53-3, settlement device 54-4), so a description will be omitted. The same is true for the operation of each device on accounting flow line KD16 (registration device 53-2, settlement device 54-2), the operation of each device on accounting flow line KD18 (registration device 53-3, settlement device 54-3), the operation of each device on accounting flow line KD19 (registration device 53-4, settlement device 54-4), and the operation of each device on accounting flow line KD20 (registration device 53-5, settlement device 54-5).

[0154] (Accounting Flow KD17) The operation of the device (payment settlement device 50-1) in transaction flow KD17 is similar to the operation of each device (payment settlement device 50-1 to payment settlement device 50-3) in transaction flow KD4 in the above-mentioned embodiment 1 (FIG. 20), so the explanation is omitted. Note that two or more payment settlement devices 50 may be installed.

[0155] (Example 5 relating to installation layout) FIG. 24 is an example (Example 5 relating to installation layout) of the devices in the sales system 3 (FIG. 17) of the third embodiment.

[0156] As shown in Figure 24, the checkout area is equipped with two settlement devices 50, three registration devices 53 (registration devices 53-1 to 53-3), six settlement devices 54 (settlement devices 54-1 to 54-6), one registration settlement device 59, and one transaction status management device 40. In Figure 24, KD21 to KD25 shown by dotted lines each represent a checkout flow line formed in the store.

[0157] (Accounting flow KD21, KD22, KD24) The operation of each device on accounting flow line KD21 (registration device 53-1, settlement device 54-1, settlement device 54-2) is similar to the operation of each device on accounting flow line KD1 in the above-mentioned embodiment 1 (FIG. 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so a description will be omitted. The operation of each device on accounting flow line KD22 (registration device 53-2, settlement device 54-3, settlement device 54-4) and the operation of each device on accounting flow line KD24 (registration device 53-3, settlement device 54-5, settlement device 54-6) are also similar.

[0158] (Accounting Flow KD23) The operation of the devices in transaction flow KD23 (payment settlement devices 50-1, 50-2) is similar to the operation of the devices in transaction flow KD4 in the above-described embodiment 1 (FIG. 20) (payment settlement devices 50-1 to 50-3), and therefore will not be described.

[0159] (Accounting Flow KD25) The checkout flow KD25 is a checkout flow that forms the flow of checkout, such as a store clerk using the registration and settlement device 59 to register products and settle the payment.

[0160] When a customer has put all the items they need in the sales area into their basket and wishes to have a sales clerk register the items and settle the bill, they take the basket and enter the payment area from the sales area, as shown by payment flow line KD25.

[0161] In payment flow line KD25, the clerk transfers the products from the basket given by the customer (the basket in which the customer puts the products on the sales floor) to an empty basket, while registering the products (and a paid plastic bag, if necessary) and paying using the registration and settlement device 59. After paying at the registration and settlement device 59, the customer moves to the shopping counter with the basket containing the paid products, packs the products in the basket into a bag (a personal bag, a paid plastic bag), returns the empty basket to the return location (not shown), and moves to the exit to leave the store.

[0162] (Display of transaction status management device 40) 25 is a display example of the transaction status management device 40. The transaction status management device 40 displays a management screen for managing (monitoring) devices (installed cash registers such as the settlement device 50) installed in the store and mobile terminals (mobile terminal 60, etc.) present in the store.

[0163] FIG. 25(A) is an example of an installed register management screen for managing installed registers. FIG. 25(B) is an example of a mobile terminal management screen for managing mobile terminals. For example, the transaction status management device 40 displays the installed register management screen shown in FIG. 25(A) and the mobile terminal management screen shown in FIG. 25(B) in a switchable manner by operating tabs ("Installed Register" and "Mobile Terminal"). Note that FIG. 25(A) is an example of an installed register management screen according to Example 1 (FIG. 20). It is also assumed that a store contains a mixture of mobile terminals 60 that are personal possessions of customers and mobile terminals 60 that are lent by the store.

[0164] (Installation cash register management screen) By operating buttons (layout button BT401, function button BT402), the transaction status management device 40 can switch between displaying an installed register management screen based on layout (installation location) (hereinafter sometimes referred to as the "installed register management screen (layout display)") and an installed register management screen based on function (by device type, checkout flow (by lane), etc.) (hereinafter sometimes referred to as the "installed register management screen (display by function)").

[0165] In Fig. 25(A), the bold frame of the layout button BT401 and the thin frame of the function button BT402 indicate that the last button operated of the layout button BT401 and the function button BT402 was the layout button BT401 (that is, the layout display has been selected). In other words, the installed register management screen shown in Fig. 25(A) is the installed register management screen (layout display).

[0166] In the installed register management screen (layout display) shown in Fig. 25(A), the display area HR403 is the main display area. In the main display area HR403, the transaction status management device 40 displays icons corresponding to each device installed in the checkout area at positions corresponding to the respective devices' installation positions in the checkout area, as shown in Fig. 25(A). The numbered icons are icons corresponding to installed registers (devices for registering products or settling payments). The diagonally lined icons without numbers are icons corresponding to the transaction status management device 40 in question.

[0167] In addition, the layout display may be made to show the position where the customer stands at each device (on which side of each device the customer stands). As an example, in the device corresponding to the icon No. 14 in the upper right of the drawing (the settlement device 50-1 shown in FIG. 20), the customer stands (stands with his back to the device corresponding to the icon No. 9 (the registered settlement device 52-2 shown in FIG. 20), so for example, one side of the icon No. 14 on the No. 9 side may be displayed in a different manner (for example, in a different color) from the other three sides, or a mark indicating that the side on which the customer stands (for example, an image of a circle with the word "customer" written inside it) may be displayed. The mark may be displayed in a different manner depending on whether or not a customer is present (for example, determined by a human sensor, etc.), and for a device operated by a customer, the mark may be displayed in a different manner depending on whether or not the customer is operating the device. The mark may not indicate the position where the customer stands at each device, but may simply indicate whether or not a customer is present or not or whether or not the customer is operating the device.

[0168] In the installed register management screen (layout display) shown in Fig. 25(A), the display area HR404 is a supplemental information display area. The transaction status management device 40 displays, in the supplemental information display area HR404, the type of installed register for each number shown in the main display area HR403, as shown in Fig. 25(A).

[0169] In the installed register management screen (layout display) shown in FIG. 25(A), the display area HR405 is a detailed information display area. Although not shown, the transaction status management device 40 displays detailed information about one installed register (for example, an installed register selected by operating (touching) an icon in the main display area HR403) in the detailed information display area HR405. For example, the transaction status management device 40 displays, as detailed information, the current operating mode in the case where there are multiple operating modes, whether or not the register is being used by a clerk or a customer, the change status, the paper status, etc. In addition, the installed register (i.e., the installed register selected by operation) whose detailed information is displayed in the detailed information display area HR405 may be displayed in a different display mode from the other installed registers in the main display area HR403. In this example, it is displayed with a thick frame, but it may be displayed in a different color from the others, or a mark may be added.

[0170] As described above, the transaction status management device 40 displays the installed register management screen (function display) when the layout button BT401 is operated, but the transaction status management device 40 may display information about each device in a list format by type (or by accounting flow) on the installed register management screen (function display). For example, the installed register management screen (function display) has a main display area HR403, a supplemental information display area HR404, and a detailed information display area HR405, just like the installed register management screen (layout display), and may display information about each device in a list format by type (or by accounting flow) in the main display area HR403.

[0171] (Mobile device management screen) In the mobile terminal management screen shown in Fig. 25(B), the display area HR410 is a terminal number display area. The transaction status management device 40 displays the number of mobile terminals 60 in a transaction in the terminal number display area HR410. A mobile terminal 60 in a transaction is a mobile terminal 60 that is in a transaction after product registration has started and before settlement is completed. The transaction status management device 40 displays various information on the mobile terminal management screen based on, for example, information stored in the cloud server 20 (transaction information of each mobile terminal 60) and information stored in the head office server 10 (customer master, etc.).

[0172] In the mobile terminal management screen shown in FIG. 25(B), the display area HR412 is an area for displaying the number of abnormal transaction terminals. An abnormal transaction is, for example, a transaction that includes a reserved item, and the subsequent settlement process will not be completed normally unless a store clerk checks it. A reserved item is an item whose settlement in the settlement process is temporarily suspended. The reserved items include, for example, unscanned items that have not been scanned, non-file items that have been scanned but whose item code has not been registered in the item master and therefore price and other information could not be obtained, age verification items such as alcohol, medicines that require explanation by a pharmacist, and security tag items with security tags attached. The transaction status management device 40 displays the number of mobile terminals 60 that are abnormal transactions among the mobile terminals 60 that are currently in a transaction in the abnormal transaction terminal number display area HR412.

[0173] In the mobile terminal management screen shown in Fig. 25(B), the display area HR414 is an area for displaying the number of normal transaction terminals. A normal transaction is, for example, a transaction that does not include reserved products and in which the subsequent settlement process is completed normally without confirmation by a store clerk. The transaction status management device 40 displays in the normal transaction terminal number display area HR414 the number of mobile terminals 60 for which the transaction is normal among the mobile terminals 60 in progress.

[0174] In the mobile terminal management screen shown in FIG. 25(B), the display area HR423 is the main display area. The transaction status management device 40 displays a list of information related to the mobile terminal 60 in the transaction in the main display area HR423. The display selection button BT411 is a button for selecting all mobile terminals 60 in the transaction (including both the mobile terminal 60 in which the transaction is abnormal and the mobile terminal 60 in which the transaction is normal) as the mobile terminals 60 to be displayed in the main display area HR423. The display selection button BT413 is a button for selecting the mobile terminal 60 in which the transaction is abnormal as the mobile terminal 60 to be displayed in the main display area HR423. The display selection button BT415 is a button for selecting the mobile terminal 60 in which the transaction is normal as the mobile terminal 60 to be displayed in the main display area HR423. In the example shown in Fig. 25(B), the display selection button BT413 is operated (the gray down button indicates that the button is selected by the operation), and information on the mobile terminal 60 in which the transaction is abnormal is displayed in a list in the main display area HR423. When there are many mobile terminals 60 to be displayed, each one may be displayed in a small size, or may be displayed in multiple pages.

[0175] In the mobile terminal management screen shown in FIG. 25(B), the display area HR425 is a detailed information display area. Although not shown, the transaction status management device 40 displays detailed information about one mobile terminal 60 (for example, a mobile terminal 60 selected by operation in the main display area HR423) in the detailed information display area HR425. For example, the transaction status management device 40 displays the purchase history of the customer as the detailed information (the purchase history of each customer may be stored in the headquarters server 10, for example). In addition, the one mobile terminal 60 (i.e., the mobile terminal 60 selected by operation) displaying the detailed information in the detailed information display area HR425 may be displayed in a display mode different from that of the other mobile terminals 60 in the main display area HR423. In this example, it is displayed with a thick frame, but it may be displayed in a color different from the others, or a mark may be added.

[0176] The display of the transaction status management device 40 has been described above using Fig. 25, but the management screen displayed by the display of the transaction status management device 40 is not limited to the management screen shown in Fig. 25. For example, in the above, an example of switching between the installed register management screen (Fig. 25(A)) and the mobile terminal management screen (Fig. 25(B)) has been described, but instead of or in addition to switching between them, the installed register management screen and the mobile terminal management screen may be displayed simultaneously (for example, displayed side by side, one above the other, or displayed side by side). When displaying them simultaneously, an operation such as making one larger and the other smaller may be accepted. The same applies to the installed register management screen (layout display) and the installed register management screen.

[0177] In the above, the mobile terminals 60 "after product registration starts and before payment is completed" are uniformly monitored without distinguishing between the progress of the processing, but each of the mobile terminals 60 may be monitored for each progress of the processing. For example, the transaction status management device 40 may display any of the following (1) to (6) selectable. For example, each mobile terminal 60 may notify the cloud server 20 of information related to the progress of the processing, and the cloud server 20 may store the information related to the progress of the processing in the transaction information of each mobile terminal 60, so that the transaction status management device 40 recognizes the progress of the processing of each mobile terminal 60 (in other words, extracts the mobile terminals 60 belonging to (1) to (6)).

[0178] (1) The mobile terminal 60 after the start of product registration but before the product registration is completed (for example, before the two-dimensional code 605 for payment is displayed) (i.e., the mobile terminal 60 during product registration) (2) After product registration is complete, the mobile terminal 60 before the start of settlement (for example, before the settlement device 50 reads the settlement two-dimensional code 605) (i.e., the mobile terminal 60 in the process of settlement) (3) A mobile terminal 60 after the start of settlement but before the completion of settlement (i.e., a mobile terminal 60 during settlement) (4) After product registration begins, but before payment begins (i.e., (1)+(2)) on the mobile terminal 60 (5) After product registration is complete, but before payment is completed (i.e., (2)+(3)) on the mobile terminal 60 (6) After product registration has started, but before payment has been completed (i.e., (1)+(2)+(3). Example of FIG. 25(B))

[0179] (Exit gate) In the first embodiment (as well as in the other embodiments), an exit gate may be installed near the exit (or just before the exit) to prevent fraudulent behavior in which a customer leaves the store without paying. The exit gate may be equipped with a reading unit and permit passage by reading a predetermined two-dimensional code for permitting passage. The two-dimensional code for permitting passage may be printed on a receipt issued after payment, for example, or may be displayed on the mobile terminal 60 after payment. The exit gate may be configured to restrict movement, for example, like an automatic ticket barrier at a station, or may simply display a display or issue a voice alert. The exit gate may also be connected to a network (LAN) and managed (monitored and controlled) by the transaction status management device 40.

[0180] As described above, the first to third embodiments have been described. According to the first to third embodiments, when multiple services coexist, it is possible to provide an optimal transaction flow line.

[0181] (Variations, etc.) Although the embodiment has been described above, the device configuration, data configuration, processing flow, display and output aspects, etc. can be appropriately changed, for example, as shown in the following (1), (2), .... In addition, the following (1), (2), ... may be appropriately combined with each other.

[0182] (1) In the above embodiment, the settlement device 50 installed in the store in each sales system has been described as a device that settles the payment for merchandise registered by the mobile terminal 60, but the settlement device 50 may settle the payment for merchandise registered by a device other than the mobile terminal 60 (e.g., the registered settlement device 51, the registered settlement device 52, the registration device 53). For example, the settlement device 50 may receive registration information from the registration device 53 and settle the merchandise registered by the registration device 53, like the settlement device 54. Similarly, the settlement device 54 installed in the store in each sales system has been described as a device that settles the payment for merchandise registered by the registration device 53, but the settlement device 54 may settle the merchandise registered by a device other than the registration device 53 (e.g., the registered settlement device 51, the registered settlement device 52, the mobile terminal 60).

[0183] (2) In the above embodiment, the settlement device 50, the registration settlement device 51, the registration settlement device 52, the registration device 53, the settlement device 54, and the registration settlement device 59 are described as the registration devices or settlement devices installed in the store in each sales system, but the registration devices and settlement devices installed in the store in each sales system are not limited to the above devices. As an example, a registration settlement device (a registration settlement device equivalent to the registration settlement device 51 (or the registration settlement device 52) fixed to the full self-service mode, hereinafter referred to as the registration settlement device 55) where the customer exclusively registers and settles the product may be installed in the store instead of or in addition to the registration settlement device 51 (or the registration settlement device 52). Note that the registration settlement device 51 (or the registration settlement device 52) has a scanner unit used by the customer and a scanner unit used by the store clerk (FIG. 5), but the registration settlement device 55 only needs to have a scanner unit used by the customer.

[0184] (3) In the above embodiment, an example was described in which a customer registers a product using a mobile terminal 60, but the device does not have to be a mobile terminal 60 as long as it is a mobile (portable) device that can register products at the product display location. For example, products may be registered using a tablet terminal lent to customers by the store, or a shopping cart with a display unit (or a display device that can be attached and detached to the shopping cart). The shopping cart may be equipped with an electronic tag recognition unit that recognizes information on an electronic tag.

[0185] (4) Some or all of the functions (input / output, storage, processing (including judgment)) of the settlement device 50 in the above embodiment may be realized by a device other than the device described as the execution subject of the function. For example, at least a part of the processing described using the sequence diagram of FIG. 15 as the processing of the settlement device 50 may be executed by the store controller 30 or the cloud server 20 instead of the settlement device 50. In relation to the above, the settlement device 50 may function as a so-called thin client specialized for input / output interfaces, etc. For example, the settlement device 50 may receive various inputs (customer operations, detection by a device such as a scanner) and transmit the input information (operation information, image information, etc.) to the cloud server 20, and then the cloud server 20 may execute processing according to the information received from the settlement device 50 and transmit the processing result (update screen information, etc.) to the settlement device 50, and then the settlement device 50 may execute an operation (display on a display unit, etc.) according to the information received from the cloud server 20. In other words, the cloud server 20 may execute a program for controlling the operation of the settlement device 50. The same applies to registration settlement device 51, registration settlement device 52, registration device 53, settlement device 54, registration settlement device 55, and registration settlement device 59.

[0186] <Overview of the embodiment> [Technical field] The present invention relates to a product sales data processing system. [Background technology] There are cases where multiple services related to the sale of goods coexist. For example, a system that provides multiple payment methods in a store is known (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2016-081072 A [Summary of the invention] [Problem to be solved by the invention] However, problems may arise with the accounting flow when multiple services coexist. The present invention has been made in consideration of such circumstances, and has an object to provide a suitable accounting flow. [Means for solving the problem]

[0187] (1) A product sales data processing system (e.g., sales systems 1, 2, 3) that executes a registration process to register products and a settlement process to settle products registered by the registration process, comprising: a first device (e.g., registration device 53) that executes the registration process based on the operation of a store clerk; a second device (e.g., settlement device 54) that executes the settlement process for products registered by the first device based on the operation of a customer; and a third device (e.g., settlement device 50) that executes the settlement process for products registered by a portable device (e.g., a mobile terminal 60) in a sales floor within a store based on the operation of the customer, wherein each of the first device, second device, and third device is installed so that at least a portion of a first accounting traffic line formed to include the installation point of the first device and the installation point of the second device, and a second accounting traffic line formed to include the installation points of each of the multiple third devices are approximately parallel to each other. In Example 1 (FIG. 20), for example, at least a portion of transaction flow line KD1 (first transaction flow line) (the portion passing in front of registration device 53-1) and transaction flow line KD4 (second transaction flow line) are approximately parallel to each other. In Example 2 (FIG. 21), for example, at least a portion of transaction flow line KD5 (first transaction flow line) (the portion passing in front of registration device 53-1) and transaction flow line KD9 (second transaction flow line) are approximately parallel to each other. In Example 3 (FIG. 22), for example, at least a portion of transaction flow line KD11 (first transaction flow line) (the portion passing in front of registration device 53-1) and transaction flow line KD10 (second transaction flow line) are approximately parallel to each other. In Example 4 (FIG. 23), for example, at least a portion of transaction flow line KD15 (first transaction flow line) (the portion passing in front of registration device 53-1) and transaction flow line KD17 (second transaction flow line) are approximately parallel to each other. In Example 5 (FIG. 24), for example, at least a portion of transaction flow line KD24 (first transaction flow line) (the portion passing in front of registration device 53-3) and transaction flow line KD23 (second transaction flow line) are approximately parallel to each other. The configuration of (1) can provide an optimal checkout flow. In other words, even when multiple services coexist (when a first checkout flow and a second checkout flow exist), the checkout flow within the store is orderly and easy to understand.

[0188] (2) A product sales data processing system as described in (1), characterized in that it is provided with a fourth device (e.g., registration and settlement devices 51, 52, 55) that executes the registration process and the settlement process based on customer operation, the total number of the third device (e.g., settlement device 50) and the total number of the fourth device (e.g., registration and settlement devices 51, 52, 55) installed is three or more, and a total of three or more of the third device or the fourth device are installed in a line around a designated area. In Example 1 (Figure 20), area C indicated by a dashed line is a specified area (sometimes called a circulating area), and registered settlement devices 51-1 to 51-3, registered settlement devices 52-1 to 52-4, and settlement devices 50-1 to 50-3 are arranged around area C. According to the configuration of (2), the self-service devices are installed in a line around a designated area, making it easier for customers to access any of the self-service devices. Monitoring and support are also made easier. By consolidating the settlement device 50 and the registration settlement devices 51 and 52 in one area, the same support and monitoring capabilities of the clerk during semi-self-service transactions consisting of the registration device 53 and settlement device 54 can also be provided for the full-self-service transaction devices (the settlement device 50, the registration settlement devices 51 and 52). In other words, a layout is realized that allows transactions for many customers to be completed with a small number of clerks, and addresses serious labor shortages.

[0189] (3) The product sales data processing system according to (2), wherein the specified area is an enclosed area having at least two entrances and at least one exit. In Example 1 (FIG. 20), area C has two entrances (checkout flow lines KD3 and KD4) and one or two exits (either or both of the passages that go through the right side or the left side of the transaction status management device 40). In Example 1, registration and settlement device 52-2 and registration and settlement device 52-3 may be installed apart from each other, and the space between the two devices may be used as a passage to area C (i.e., there may be three entrances to area C). Furthermore, four or more entrances or three or more exits may be provided depending on the size and shape of area C and the number of devices installed around area C. According to the configuration of (3), by providing two entrances, it is possible to prevent customers who want to use the settlement device 50 and customers who want to use the registered settlement devices 51 and 52 from lining up in the same line. This makes it possible to prevent customers with different transaction methods from mixing together. If there was only one entrance, the two would mix together, which could lead to problems (for example, a customer using the settlement device 50 having to wait in vain for settlement devices 51 and 52 to become available). Also, if the previous customer and the next customer want different devices, the next customer may follow the previous customer and go to the wrong device. By having one exit and providing a transaction status management device 40 and a monitoring clerk near the exit, visibility of the entire area including the settlement device 50 and registered settlement devices 51, 52 is improved, and the clerk can check the usage status directly with his or her naked eye and also indirectly through the transaction status management device 40, improving support and monitoring. Having a clerk waiting at the exit (in the direction of leaving the store) to provide support and monitoring also has the effect of making it easier for customers to find the clerk, ask for support, and call out to him or her. In addition, customers who use the payment device 50 (customers who use service A and proceed to payment flow KD4) are considered to be customers who value comfort and efficiency when shopping. Therefore, it is important that customers who use the payment device 50 experience a comfortable and efficient payment process using the payment device, etc., in addition to comfortable and efficient product selection and product registration using the mobile terminal 60 in the store, so that they have a good impression throughout the entire process, from entering the store to leaving the store. Here, payment flow KD4 provides the shortest route by lining up the entrance, payment device 50, and exit in a roughly straight line, so that a good impression can be given not only from the flow of entering the store to payment, but also from the flow of payment to leaving the store. Service A is also expected to be a great benefit to stores, which have the least workload for staff and the least amount of time that equipment is occupied. However, it is also extremely beneficial for stores seeking to expand usage, because by providing (or continuing to provide) customers who actually use Service A with a pleasant experience and impression (something like an incentive), it can help to establish the use of Service A and motivate new users through word of mouth (customers who use Service A are generally thought to be sensitive to various trends and have the ability to communicate).

[0190] (4) A product sales data processing system as described in either (2) or (3), further comprising a monitoring device (e.g., a transaction status management device 40) that monitors at least a portion of the third device or the fourth device, and the monitoring device is installed downstream of the first accounting flow path or the second accounting flow path. For example, in the first embodiment (FIG. 20), the monitoring device is installed downstream of the transaction flow line KD4 (second transaction flow line). The configuration of (4) allows for optimal monitoring and support. For example, monitoring can be performed downstream (towards the exit) where customers pass after paying, which can serve as a deterrent to fraud. In addition, the support target is located in the direction of the inside of the store (upstream), which widens the support range.

[0191] (5) A product sales data processing system as described in any of (2) to (4), characterized in that a sucker counter is installed downstream of the installation point of the second device on the first accounting traffic line, and the length of the first accounting traffic line in the specified area in the direction of the first accounting traffic line is less than or equal to the length of the first accounting traffic line in the direction of the first accounting traffic line from the installation point of the first device to the installation position of the sucker counter. In the first embodiment (FIG. 20), the length of the area C indicated by the dashed line in the direction of the transaction flow line KD1 is shorter than the length of the transaction flow line KD1 from the installation point of the registration device 53-1 to the installation position of the sucker counter. According to the configuration (5), the length of the designated area in the direction of traffic flow is reduced, thereby alleviating the feeling of oppression (crampedness) caused by the designated area and also making it possible to ensure an aisle of the required width (the aisle in front of the service counter in Figure 20).

[0192] In addition, a program for implementing the functions of each of the above-described devices (headquarters server 10, store controller 30, transaction status management device 40, settlement device 50, registration settlement device 51, registration settlement device 52, registration device 53, settlement device 54, registration settlement device 55, registration settlement device 59, etc.) may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing of each of the above-described devices. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside the distribution server and accessible to distribute the program. The code of the program stored in the distribution server's recording medium may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined in the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds the program for a certain period of time, such as a volatile memory (RAM) in a computer system that becomes a server or a client when the program is transmitted via a network. The program may be for realizing part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0193] 1, 2, 3…Sales System 10…Headquarters server 20…Cloud server 30…Store Controller 40...Transaction status management device 50…Payment device 51...Registration and settlement device 52...Registration and settlement device 53...Registration device 54…Payment device 59...Registration and settlement device

Claims

1. A merchandise sales data processing system that executes a registration process for registering merchandise and a settlement process for settling the merchandise registered by the registration process, a first device that executes the registration process and the settlement process based on an operation of a customer; a second device that executes the payment process for the products registered by the portable device based on an operation by the customer at the sales floor in the store; Equipped with The first device and the second device are installed in a checkout area provided between the sales floor and an exit, A product sales data processing system characterized in that the first device and the second device are installed in the checkout area so as to form a first entrance through which customers using the first device enter the checkout area from the sales floor side, a second entrance through which customers using the second device enter the checkout area from the sales floor side, and an exit through which customers using the first device or the second device exit the checkout area to the exit side.

2. The first entrance is formed between one of the first devices and another of the first devices, The second inlet is formed between the first device and the second device.

2. The product sales data processing system according to claim 1.

3. A plurality of the first devices, The product sales data processing system described in claim 1 or claim 2, characterized in that the first devices are divided into multiple groups and installed around a specified area in the checkout area so that the operation surfaces of the first devices belonging to one group and the operation surfaces of the first devices belonging to another group face in different directions, and so that the operation surfaces of the first devices belonging to both groups face toward the center of the specified area.

4. The first device is The system includes a cash-accepting device that accepts cash payments and a non-cash-accepting device that does not accept cash payments, A product sales data processing system as described in any one of claims 1 to 3, characterized in that the cash-handling device and the non-cash-handling device are installed so that the operation surfaces of the cash-handling device and the non-cash-handling device face in different directions.

5. A transaction status management device that monitors the operating status of the first device and the second device. Equipped with 5. The merchandise sales data processing system according to claim 1, wherein the transaction status management device is installed on the exit side of the checkout area.

Images