Product 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 Art

[0002] There may be a coexistence of a plurality of services related to the sale of products. For example, a system that provides a plurality of payment methods in a store is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, problems may occur in the accounting process when a plurality of services coexist.

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

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-mentioned problems is a product sales data processing system that performs a registration process for registering products and a settlement process for settling payments for products registered by the registration process, comprising: a first device that performs the registration process based on the operation of a store employee; a second device that performs the settlement process based on the operation of a customer for products registered by the first device; and a third device that performs the settlement process based on the operation of a customer for products registered by a portable device in the sales area of ​​the store based on the operation of a customer, wherein the first device, the second device, and the third device are installed such that at least a portion of a first checkout route, which is formed to include the installation point of the first device and the installation point of the second device, and a second checkout route, which is formed to include the installation points of each of the plurality of third devices, are substantially parallel to each other. [Brief explanation of the drawing]

[0007] [Figure 1] This is a conceptual diagram of a network illustrating the sales system of the first embodiment. [Figure 2] This is a diagram illustrating the external appearance of the payment device. [Figure 3] This is an example of a payment processing system configuration. [Figure 4] This is a diagram illustrating the external appearance of the registration and settlement device. [Figure 5] This is an example of the configuration of a registration and settlement device. [Figure 6] This is a diagram illustrating the appearance of the registered device. [Figure 7] This is an example of the configuration of the registered device. [Figure 8] This is a diagram illustrating the external appearance of the payment device. [Figure 9] This is an example of a payment processing system configuration. [Figure 10] This is an example of how it looks on a mobile device. [Figure 11] Examples of displays on mobile devices, etc. [Figure 12] This is an example of a display on a payment device. [Figure 13] This is an example of a display on a payment device. [Figure 14] It is a sequence diagram showing an example of the processing of a mobile terminal and a cloud server. [Figure 15] It is a sequence diagram showing an example of the processing of a payment device and a cloud server. [Figure 16] It is a conceptual diagram of a network for explaining the sales system of the second embodiment. [Figure 17] It is a conceptual diagram of a network for explaining the sales system of the third embodiment. [Figure 18] It is a diagram for explaining the appearance of a registered payment device. [Figure 19] It is a configuration example of a registered payment device. [Figure 20] It is an example of the installation layout of each device in the sales system of the first embodiment (Example 1 related to the installation layout). [Figure 21] It is another example of the installation layout of each device in the sales system of the first embodiment (Example 2 related to the installation layout). [Figure 22] It is an example of the installation layout of each device in the sales system of the second embodiment (Example 3 related to the installation layout). [Figure 23] It is another example of the installation layout of each device in the sales system of the second embodiment (Example 4 related to the installation layout). [Figure 24] It is an example of the installation layout of each device in the sales system of the third embodiment (Example 4 related to the installation layout). [Figure 25] It is a display example of a transaction status management device.

Mode for Carrying Out the Invention

[0008] (First Embodiment) FIG. 1 is a conceptual diagram of a network for explaining a sales system 1 according to the 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 or the like), a transaction status management device 40 (e.g., a personal computer or the like), 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 communicably connected via a LAN 19 (which may be wired or wireless). The store controller 30 is communicable with the headquarters server 10. The sales system 1 can be introduced into various stores (such as supermarkets, convenience stores, drugstores, home centers, home appliance量贩 stores, etc.).

[0010] In FIG. 1, the number of each device (terminal) is an example. For example, in FIG. 1, "..." is illustrated on the right side 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 according to the number of customers.

[0011] The sales system 1 provides a self-service (hereinafter sometimes referred to as Service A) in a mode where a product is registered using the mobile terminal 60 and settlement is performed using the settlement device 50. That is, Service A is a self-service in a mode where the customer himself / herself performs product registration and settlement, using the mobile terminal 60 for product registration and the settlement device 50 for settlement.

[0012] Furthermore, in addition to service A, sales system 1 also provides other services. For example, other services that sales system 1 can provide include a service in which the customer registers and pays for goods using the registration and payment device 51 (or registration and payment device 52), or a service in which a store clerk registers goods using the registration device 53 and the customer pays using the payment device 54.

[0013] The headquarters server 10 is located outside the store (for example, at the head office or a data center) and is a server that manages the entire sales system 1. The headquarters server 10 stores various information necessary for the operation of services, including service A (for example, customer master (member master), product master, special sale files, etc.) and service performance information at the store (for example, 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 also communicate with other devices (for example, the transaction status management device 40, the settlement device 50, etc.). The headquarters server 10 may be composed of multiple servers.

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

[0015] The store controller 30 is a device that controls the part of the sales system 1 that pertains to the store in question. The store controller 30 communicates with various devices within the LAN 19 (e.g., the checkout device 50) and various devices outside the LAN 19 (e.g., the headquarters server 10). For example, the store controller 30 receives product master data and special offer files from the headquarters server 10 and supplies them to the checkout device 50.

[0016] The transaction status management device 40 is primarily a device that manages each device within the LAN 19. For example, the transaction status management device 40 communicates with each device within the LAN 19 and monitors the processing status, operating status (operational status), etc., of each device within the LAN 19. The transaction status management device 40 may also communicate with devices outside the LAN 19 (for example, the headquarters server 10, the cloud server 20) (either 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 used when registering products in Service A. In other words, customers use the mobile terminal 60 when registering products in Service A. In addition to communication functions and imaging functions (camera), the mobile terminal 60 is equipped with recognition functions that recognize various codes (barcodes, 2D codes, etc.). For example, the mobile terminal 60 recognizes barcodes attached to products. For example, the mobile terminal 60 may extract feature points in the captured image (image acquired as a through image (live view)) captured by the imaging function and recognize objects (various codes). It is assumed that the mobile terminal 60 is owned by the individual (or corporation) customer using Service A, but it may also be lent by the store.

[0018] The payment device 50 is used when settling payments in Service A. In other words, customers use the payment device 50 when settling payments for products they have registered using their mobile terminal 60. The configuration of the payment device 50 will be described later.

[0019] The registration and settlement device 51 is used by store staff or customers. Specifically, the registration and settlement device 51 is equipped with scanner units on both sides (store staff side and customer side) and a settlement unit (specifically, a cash settlement unit and a card settlement unit) on one side (customer side). The registration and settlement device 51 has multiple 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 store staff or customers. Specifically, the registration and settlement device 52 is equipped with scanner units on both sides (store staff side and customer side) and a settlement unit (specifically, a card settlement unit) on one side (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 settlement unit, in that it does not have a cash settlement unit.

[0021] The registration device 53 is primarily used by store employees. The registration device 53 is equipped with a scanner and is used exclusively for registering products. The configuration of the registration device 53 will be described later.

[0022] The settlement device 54 is primarily used by customers. The settlement device 54 is equipped with a settlement section and is used exclusively for settlement. The configuration of the settlement device 54 will be described later.

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

[0024] The following describes an example configuration of the payment device 50 shown in Figure 3, with reference to Figure 2. The payment device 50 comprises a CPU 101, a ROM 102, a RAM 103, a hard disk 104, a display unit 105, a scanner unit 106, a card payment unit (non-cash payment unit) 108, a change machine (cash payment unit) 109, a printing unit 113, an audio output unit 114, a communication unit 115, an imaging unit (camera) 116, and a signpost 117. These can communicate with each other via a bus. The payment device 50 (and the payment device 54 similarly) may further include a key operation unit composed of various keys (buttons). The payment device 50 (and the registered payment device 51, registered payment device 52, registered device 53, payment device 54, etc.) may further include a sensor (such as a motion sensor) for detecting the presence of a person.

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

[0026] RAM103 is a read / write memory that stores various types of information as main memory. For example, RAM103 stores information read from ROM102 and hard disk 104, information obtained from external sources, and information generated during processing.

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

[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 types of information. Specifically, the scanner unit 106 scans the code (2D code 605 for payment (described later)) displayed on the mobile terminal 60 and reads the information necessary for payment processing. The scanner unit 106 may also scan codes attached to gift certificates (vouchers, coupons, discount vouchers) and various cards (e.g., membership cards, point cards, etc.) and read the information attached to them. The scanner unit 106 may also scan codes attached to employee name tags, etc., and read employee codes.

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

[0031] The card payment unit 108 is a payment mechanism that accepts various types of 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 if it includes at least a card recognition unit. The card recognition unit may recognize various types of cards (e.g., point cards, membership cards, shareholder cards, etc.) for purposes such as granting benefits or discounts.

[0032] Furthermore, the card payment unit 108 may consist of multiple components corresponding to the card to be read. In other words, the settlement device 50 may, for example, 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 dispenser 109 is a cash payment mechanism that has an input slot for banknotes and coins, and an output slot for banknotes and coins. It calculates the amount to be inserted into the input slot, calculates the change amount which is the difference between the inserted amount and the purchase price, and dispenses the change from the output slot. When banknotes or coins are inserted into the input slot, this is detected by a sensor (detection of the insertion, detection of the number of coins of each denomination, etc.).

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

[0035] The communication unit 115 transmits and receives information with other devices (for example, the store controller 30, the transaction status management device 40, etc.). The imaging unit 116, for example, images the customer. The payment device 50 may be equipped with two or more imaging units 116, and may simultaneously image the face and hands (near the input and output slots of the change machine 109). The sign pole 117 has a light-emitting part at its tip, and various information (such as calling for staff, operating status, etc.) is communicated depending on the pattern of light emitted by the light-emitting part.

[0036] (Registration and settlement device 51) Figure 4 is a diagram illustrating the external appearance of the registration and settlement device 51. Figure 5 is an example of the configuration of the registration and settlement device 51. In Figures 4 and 5, the same parts are denoted by the same reference numerals. The registration and settlement device 51 comprises 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 dispenser (cash payment unit) 209, a staff-side display unit 210, a key operation unit 211, a staff-side scanner unit 212, a printing unit 213, an audio output unit 214, and a communication unit 215. These can communicate with each other via a bus. Furthermore, the registration and settlement device 51 (and the registration and settlement devices 52, 53, 54, etc.) may also be equipped with an imaging unit (similar to the imaging unit 116 of the settlement device 50), and the registration and settlement device 51 may also be equipped with 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 payment unit 208, change dispenser 209, voice output unit 214, and communication unit 215 of the registered payment device 51 are the same as those of the CPU 101, ROM 102, RAM 103, hard disk 104, card payment unit 108, change dispenser 109, voice output unit 114, and communication unit 115 of the payment device 50, so some or all of the explanation 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 types of information. Specifically, the customer-side scanner unit 206 scans codes attached to products and reads product codes (such as JAN codes). The customer-side scanner unit 206 may also scan codes attached to vouchers and various cards and read the information contained therein. Furthermore, the customer-side scanner unit 206 may scan codes attached to employee name tags and read employee codes. In addition, the customer-side scanner unit 206 may scan codes printed on payment slips and read the information necessary for payment processing.

[0040] The customer-side scanner unit 206 is used when a customer registers a product, but the customer may register a product by other means. For example, if a preset key (a button to order a product) corresponding to a product is displayed on the customer-side display unit 205, the customer may register a product by operating (pressing) that preset key.

[0041] The employee-side display unit 210 is a touch display that displays various information to the employee and accepts various inputs from the employee. The key operation section 211 contains various buttons for operation by store staff. Reference numeral 211a denotes a mode switching button for switching between operating modes.

[0042] The employee-side scanner unit 212 is a scanner unit for employees and optically reads various types of information. Specifically, the employee-side scanner unit 212 scans codes attached to products and reads product codes (such as JAN codes). The employee-side scanner unit 212 may also scan codes attached to vouchers and various cards and read the information contained therein. Furthermore, the employee-side scanner unit 212 may scan codes attached to employee name tags, etc., and read employee codes. In addition, the employee-side scanner unit 212 may scan codes printed on payment slips and read the information necessary for settlement processing.

[0043] The employee-side scanner unit 212 is used when an employee registers a product, but the employee may register a product by other means. For example, if the key operation unit 211 has keys corresponding to products (for example, a key corresponding to a sports newspaper), the employee may register the product by operating (pressing) those keys. Also, if the employee-side display unit 210 displays preset keys corresponding to products, the employee may register the product by operating those preset keys.

[0044] The printing unit 213 prints and issues various media (receipts, payment slips, etc.). The printing unit 213 can be rotated to change its orientation (direction of the media issuing slot) from the employee side to the customer side and from the customer side to the employee side. The orientation of the printing unit 213 may be changed manually, or it may be changed automatically (mechanically controlled, for example) based on a change in the operating mode. The correctness of the orientation of the printing unit 213 may be detected by a sensor or other means.

[0045] (Operating mode of the registration and settlement device 51) As described above, the registration and settlement device 51 has multiple operating modes. The operating modes will be described below. As described above, the operating mode is switched by operating the switch button 211a, but the operating mode can also be switched by other conditions (for example, elapsed time, reception of registration information, reading of the store clerk code, reception of an operating mode switching command transmitted from another device, etc.). The same applies to the registration and settlement device 52.

[0046] (Face-to-face semi-self-service mode (normal mode)) The face-to-face semi-self-service mode (also referred to as normal mode) is an operating mode in which a store employee registers products using one side (employee side) of the registration and payment device 51, and the customer makes the payment using the other side (customer side) of the registration and payment device 51. Therefore, when the operating mode is face-to-face semi-self-service mode, the store employee and the customer face each other, the employee registers the products, and the customer makes the payment.

[0047] (Full self mode) Full self-service mode is an operating mode in which the customer registers and pays for goods using one side (the customer side) of the registration and payment device 51. Therefore, when the operating mode is full self-service mode, the customer registers and pays for goods using the customer side (without using the store clerk side).

[0048] (Multiple-unit semi-self-registration mode (registration-only mode)) The multi-unit semi-self-service registration mode (also called the registration-only mode) is an operating mode in which a store employee registers products using one side (the employee side) of the registration and payment device 51. Therefore, when the operating mode is the multi-unit semi-self-service registration mode, the employee registers the products using the employee side (without using the customer side).

[0049] (Multiple-unit semi-self-service payment mode (payment-only mode)) The multi-unit semi-self-service payment mode (also called payment-only mode) is an operating mode in which the customer makes a payment using one side (the customer side) of the registered payment device 51. Therefore, when the operating mode is the multi-unit semi-self-service payment mode, the customer makes the payment using the customer side (without using the store clerk side).

[0050] The registration and settlement device 51 in the multi-unit semi-self-service registration mode transmits registration information to other registration and settlement devices 51 (specifically, registration and settlement devices 51 in the multi-unit semi-self-service registration mode) (either indirectly via other devices or directly), thereby causing the other registration and settlement devices 51 (registration and settlement devices 51 in the multi-unit semi-self-service registration mode) to settle the goods registered by the said registration and settlement device 51 (registration and settlement device 51 in the multi-unit semi-self-service registration mode). In other words, the registration and settlement device 51 in the multi-unit semi-self-service registration mode receives registration information transmitted by other registration and settlement devices 51 (specifically, registration and settlement devices 51 in the multi-unit semi-self-service registration mode) (either indirectly via other devices or directly), thereby settling the goods registered by the other registration and settlement devices 51 (registration and settlement devices 51 in the multi-unit semi-self-service registration mode).

[0051] Furthermore, a registration and settlement device 51 in a multi-unit semi-self-service registration mode may issue a payment slip and have another registration and settlement device 51 (multi-unit semi-self-service registration device 51) settle the payment for the items registered by that registration and settlement device 51 (multi-unit semi-self-service registration device 51). In other words, a registration and settlement device 51 in a multi-unit semi-self-service registration mode may settle the payment for items registered by another registration and settlement device 51 (multi-unit semi-self-service registration device 51) by reading the code printed on the payment slip issued by that other registration and settlement device 51 (multi-unit semi-self-service registration device 51).

[0052] The operation of each operating mode described above is merely an example. For example, the registration and settlement device 51 in the multi-unit semi-self-service registration mode may transmit registration information to the registration and settlement device 51 in the face-to-face semi-self-service mode or the registration and settlement device 51 in the full self-service mode, or it may issue a payment slip. In other words, the POS terminal in the face-to-face semi-self-service mode (and the registration and settlement device 51 in the full self-service mode) may settle the payment for items registered by the registration and settlement device 51 in the multi-unit semi-self-service registration mode. Also, for example, the registration and settlement device 51 in the face-to-face semi-self-service mode may transmit registration information to the registration and settlement device 51 in the full self-service mode or the registration and settlement device 51 in the multi-unit semi-self-service settlement mode, or it may issue a payment slip. In other words, the registration and settlement device 51 in the full self-service mode (and the registration and settlement device 51 in the multi-unit semi-self-service settlement mode) may settle the payment for items registered by the registration and settlement device 51 in the face-to-face semi-self-service mode. For example, a face-to-face semi-self-service registration and payment device 51 may transmit registration information to another face-to-face semi-self-service registration and payment device 51, or it may issue a payment slip. In other words, a face-to-face semi-self-service registration and payment device 51 may settle payments for items registered by another face-to-face semi-self-service registration and payment device 51.

[0053] (Registration and settlement device 52) As described above, the registration settlement device 52 differs from the registration settlement device 51, which has a cash settlement unit, in that it does not have a cash settlement unit. In other words, except for the presence or absence of the change dispenser 209, the registration settlement device 51 and the registration settlement device 52 are the same. Therefore, a diagrammatic explanation of the appearance and configuration example of the registration settlement device 52 will be omitted.

[0054] (Registration device 53) Figure 6 is a diagram illustrating the external appearance of the registration device 53. Figure 7 is an example of the configuration of the registration device 53. In Figures 6 and 7, the same parts are denoted by the same reference numerals. The registration device 53 comprises a CPU 301, a ROM 302, a RAM 303, a hard disk 304, a customer-side display unit 305, a store employee-side display unit 310, a key operation unit 311, a scanner unit 312, a printing unit 313, an audio output unit 314, and a communication unit 315. These can communicate with each other via a bus. The registration device 53 may further include a card payment unit (similar to the card payment unit 108 of the settlement device 50), etc.

[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 the same as those of 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 used by store staff to register products, the customer-side display unit 305 does not generally accept inputs for product registration. However, it does accept inputs such as age verification for products registered by store staff.

[0057] The employee-side display unit 310 is a touch display that displays various information to the employee and accepts various inputs from the employee. The key operation section 311 contains various buttons for the store staff to operate.

[0058] The scanner unit 312 is a scanner unit for store employees and optically reads various types of information. Specifically, the scanner unit 312 scans codes attached to products and reads product codes (such as JAN codes). The scanner unit 312 may also scan codes attached to vouchers and various cards and read the information contained therein. Furthermore, the scanner unit 312 may scan codes attached to employee name tags, etc., and read employee codes.

[0059] The scanner unit 312 is used when a store employee registers a product, but the employee may register a product by other means. For example, if the key operation unit 311 has keys corresponding to products (for example, a key corresponding to a sports newspaper), the employee may register the product by operating (pressing) those keys. Also, if the employee-side display unit 310 displays preset keys corresponding to products, the employee may register the product by operating those preset keys.

[0060] The printing unit 313 prints and issues various media (e.g., payment slips). These media are issued from the issuing slot 313a and handed to the customer by the store clerk. Note that the registration device 53 does not issue payment slips when it transmits registration information to another device (such as the payment 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 has been processed by the card payment unit.

[0061] (Payment device 54) Figure 8 is a diagram illustrating the external appearance of the payment device 54. Figure 9 is an example of the configuration of the payment device 54. In Figures 8 and 9, the same parts are denoted by the same reference numerals. The payment device 54 comprises 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 dispenser (cash settlement unit) 409, a staff-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 payment device 54 may also further include a card settlement unit (similar to the card settlement unit 108 of the payment device 50) in place of or in addition to the change dispenser 409.

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

[0063] The customer-side display unit 405 is a touch display that displays various information to the customer and accepts various inputs from the customer. For example, the customer-side display unit 405 accepts input to confirm the amount deposited (amount received) (input indicating that payment will be made). Also, if the settlement device 54 is configured to include a card payment unit in addition to the change dispenser 409, the customer-side display unit 405 accepts input to select the payment method (type of payment) (selection of whether to make a cash payment using the change dispenser 409 or one of various non-cash payments using the card payment unit).

[0064] The scanner unit 406 may, for example, scan codes attached to gift certificates and various cards and read the information contained therein. The scanner unit 406 may also scan codes attached to employee name tags and read employee codes. The scanner unit 406 may also scan codes printed on payment slips and read the information necessary for settlement processing. The settlement device 54 is a device that settles payments based on registration information registered by other devices (for example, the registration device 53, etc.). However, for example, when adding items, the scanner unit 406 may scan codes attached to the items and read the item codes (JAN codes, etc.).

[0065] The employee-side display unit 410 displays various information to the employee. The employee-side display unit 410 may also be a touch display that accepts various inputs from the employee. The printing unit 413 prints and issues various media (for example, receipts).

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

[0067] Figure 10(B) is the registration screen (the registration screen before registering the first product; the initial registration screen) that appears after the shopping start button BT600 is operated on the start screen of Figure 10(A). The upper part of the registration screen is the image display area HR601, which mainly displays the captured image. The lower part of the registration screen is the registration information display area HR602, which mainly displays the product registration information.

[0068] Figure 10(C) shows the registration screen in Figure 10(B) when scanning the barcode attached to a product (XX loaf of bread). In other words, when registering the desired product (the product to be purchased), the customer has the barcode attached to the product scanned, as shown in Figure 10(C).

[0069] Figure 10(D) shows the registration screen after product registration is complete. Specifically, the mobile terminal 60 sends the product code obtained from the barcode to the cloud server 20. The cloud server 20 refers to the product master and obtains the product name "XX Bread" and price "¥220" based on the product code. The cloud server 20 stores the product information (product code, product name "XX Bread", quantity "1", price "¥220", etc.) as transaction information (cart information) for the transaction and sends the product information (product name "XX Bread", price "¥220", etc.) to the mobile terminal 60. The mobile terminal 60, having 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 Figure 10(D), the mobile terminal 60 displays the registered information of the product (product name "○○ Bread", quantity "1", price "¥220") (symbol a) and the total information (approximate total "1 item ¥220") (symbol b). The mobile terminal 60 displays a portion of the registered information (quantity) as a quantity button BT603. The quantity button BT603 is a button for changing the quantity.

[0070] Furthermore, after registering a product (one item), the mobile terminal 60 displays a button BT604 that allows the user to proceed to checkout, as shown in Figure 10(D). When the customer wants to proceed to checkout (finish registering the product), they operate the button BT604.

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

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

[0073] Figure 11(B) shows the 2D code display screen that appears after the "Proceed to Checkout" button BT604 is pressed, following the scene in Figure 11(A). The 2D code display screen shows the settlement 2D code 605. The settlement 2D code 605 is a 2D code representing the information necessary to execute the settlement process. For example, the settlement 2D code 605 is a 2D code representing transaction identification information (cart identification information) that identifies the transaction information of the transaction in question from among multiple transaction information stored in the cloud server 20. Note that the information to be 2D 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 settlement 2D code 605 may be a 2D code representing the location information of the transaction information of the transaction in question (storage location within the sales system 1, such as a URI (Uniform Resource Identifier)).

[0074] The 2D code display screen also includes an estimated total display area HR606 and a back button BT607. In the example in Figure 11(B), the estimated total display area HR606 displays the estimated total "2 items ¥370". The back button BT607 is used to return to shopping (restart shopping). When the back button BT607 is pressed, the mobile terminal 60 displays the registration screen (the registration screen immediately before pressing the "Proceed to Checkout" button BT604) instead of the 2D code display screen.

[0075] Figure 11(C) shows how the payment device 50 reads the payment 2D code 605. After completing product registration, the customer has the payment device 50 read the payment 2D code 605 displayed on the mobile terminal 60, as shown in Figure 11(C).

[0076] (Example of display on payment device 50) Figures 12 and 13 show examples of the display of the payment device 50. Figure 12 is the initial screen. When settling payment for service A, the payment device 50 displays the initial screen shown in Figure 12.

[0077] The initial screen displays a message and a map instructing the user to scan the 2D payment code 605 (shown as QR code® in the diagram) displayed on the mobile terminal 60. The initial screen also includes a staff call button BT501, a balance inquiry button BT502, and language switching buttons BT503-BT505. The staff call button BT501 is used to call a staff member. The balance inquiry button BT502 is used to check the balance of various cards. The language switching button BT503 switches the display (text) on the initial screen from Japanese to English. The language switching button BT504 switches to Chinese. The language switching button BT505 switches to Korean.

[0078] After completing product registration, the customer follows the instructions on the initial screen and has the payment device 50 read the 2D code 605 displayed on the mobile terminal 60 (Figure 10(C)).

[0079] Figure 13 shows the product list screen displayed after reading the 2D code 605 for payment, following the scene in Figure 12. In other words, when the payment device 50 reads the 2D code 605 for payment, it displays the product list screen as shown in Figure 12.

[0080] The product list screen includes a product list display area HR510, a price range product count display area HR511, and a total display area HR512. The product list screen also includes a staff call button BT501 and a checkout button BT509. The checkout button BT509 is used to confirm that the information displayed on the product list screen is correct and to proceed with the transaction. When the checkout button BT509 is pressed, the payment 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 paid for (purchased). The payment device 50 displays a list of products (product name, quantity, price) included in the transaction information obtained from the cloud server 20 by reading the payment 2D code 605 in the product list display area HR510. In the example in Figure 13, the payment device 50 displays XX bread and XX oolong tea in the product list display area HR410.

[0082] The HR511 price range product count display area is used to display the number of products in each price range (1000 yen or more, 500 yen or more but less than 1000 yen, 200 yen or more but less than 500 yen, and less than 200 yen) for the product you intend to checkout (purchase).

[0083] The total display area HR512 is the area for displaying the total of the transaction. In the example in Figure 13, the settlement device 50 displays 2 as the total points (shown as "Total 2 points" in the figure), 370 yen as the estimated total amount (shown as "Estimated Total (Smartphone Displayed Amount) ¥370" in the figure), and 370 yen as the final total amount (shown as "Final Total (Payment Amount) ¥370" in the figure). The estimated total amount of 370 yen is the total amount displayed by the mobile terminal 60 (i.e., the total amount before the processing related to the sale price (described later)). The final total amount of 370 yen is the total amount recalculated by the settlement device 50 (i.e., the total amount after the processing related to the sale price (described later)).

[0084] (Handling of sale prices) When the settlement device 50 obtains transaction information from the cloud server 20 after reading the settlement 2D code 605, it refers to the special sale file and determines whether the products included in the transaction information meet the conditions for a special sale (i.e., whether a special sale (discount, etc.) is applicable). If the conditions for a special sale are met, it obtains the details of the special sale (special sale price, etc.) from the special sale file, recalculates the total amount, and reflects it in the transaction information. Specifically, the settlement device 50 does not erase (overwrite) the product price etc. before the special sale price is applied, but additionally (separately) stores the special sale price etc. obtained from the special sale file, and does not erase the total amount before recalculation, but additionally (separately) stores the total amount after recalculation. In other words, the settlement device 50 refers to the special sale file, which was not referenced when registering products with the mobile terminal 60, and if the conditions for applying the special sale price (special sale) are met, it obtains the applicable special sale price etc. from the special sale file, recalculates the total amount, and reflects it in the transaction information. Furthermore, if the conditions for the special sale are not met, the settlement device 50 will not apply the special sale price, and the final total amount will be the same as the estimated total amount. The example in Figure 13 is an example of the display when the conditions for the special sale are not met (when the special sale price is not applied).

[0085] Figure 14 is a sequence diagram showing an example of processing by the mobile terminal 60 and the cloud server 20. Specifically, the sequence diagram in Figure 14 shows an example of processing by the mobile terminal 60 and the cloud server 20 (product registration processing in service A) from the time that product 1 is registered on the mobile terminal 60 until the 2D code 605 for settlement is displayed. The left side of Figure 14 shows the processing of the mobile terminal 60, and the right side shows the processing of the cloud server 20. At the start of the sequence diagram in Figure 14 (the start of processing in the first step S1), the mobile terminal 60 is assumed to be displaying the initial registration screen as shown in Figure 10(B).

[0086] Step S1: The mobile terminal 60 reads the barcode attached to the product in response to the customer's reading operation. In other words, the mobile terminal 60 obtains the product code from the barcode attached to the product in response to the customer's reading operation. Step S2: The mobile terminal 60 sends transaction identification information that identifies the transaction information of the transaction, and the product code obtained in Step S1, to the cloud server 20.

[0087] Step S3: The cloud server 20 receives the transaction identification information and the product code. Step S4: The cloud server 20 updates the transaction information for the transaction (the transaction information corresponding to the transaction identification information) based on the product code. In other words, the cloud server 20 retrieves (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 sends the product information (product name, price, etc.) for the product code to the mobile terminal 60. For example, the cloud server 20 generates screen information that reflects the updated transaction information and sends it to the mobile terminal 60.

[0089] Step S6: The mobile terminal 60 receives product information (screen information) for 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 repeated each time the barcode attached to the product is read.

[0090] Step S8: The mobile terminal 60 generates a 2D code 605 for settlement based on the customer's payment instruction (operation of the "Proceed to Checkout" button BT604) and displays it on the 2D code display screen. Then the sequence diagram in Figure 9 ends.

[0091] Figure 15 is a sequence diagram showing an example of the processing of the payment device 50 and the cloud server 20. Specifically, the sequence diagram in Figure 15 shows an example of the processing of the payment device 50 and the cloud server 20 (payment processing in service A) from the time the payment device 50 reads the 2D code 605 for payment until the product list screen is displayed. The left side of Figure 15 shows the processing of the payment device 50, and the right side shows the processing of the cloud server 20. At the start of the sequence diagram in Figure 15, the payment device 50 is assumed to be displaying the initial screen as shown in Figure 12.

[0092] Step S11: The settlement device 50 reads the settlement 2D code 605 displayed on the mobile terminal 60 in response to the customer's reading operation. In other words, the settlement device 50 obtains transaction identification information that identifies the transaction information of the transaction in question. Step S12: The settlement device 50 requests transaction information for the transaction from the cloud server 20. For example, the settlement device 50 sends request information (transaction information acquisition request information) to the cloud server 20, which includes transaction identification information that identifies the transaction information for the transaction.

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

[0094] Step S15: The settlement device 50 receives and stores the transaction information for the transaction. Step S16: The settlement device 50 refers to the special sale file, and if it matches the special sale conditions, it retrieves the details of the special sale (special 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 special sale price," so they are omitted here. Step S17: The settlement device 50 displays the product list screen based on the transaction information. Then, the sequence diagram in Figure 15 ends.

[0095] (Second Embodiment) Figure 16 is a conceptual diagram of a network illustrating the sales system 2 of the second embodiment. The sales system 2 shown in Figure 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 the registration and settlement device 51 and the registration and 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, so their description is omitted.

[0097] In addition to service A, sales system 2 can also provide services such as when a store clerk registers products using registration device 53 and the customer makes a payment using payment device 54.

[0098] (Third embodiment) Figure 17 is a conceptual diagram of a network illustrating the sales system 3 of the third embodiment. The sales system 3 shown in Figure 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 and 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 and settlement device 59 instead of registration and settlement devices 51 and 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 those in the sales system 1 of the first embodiment, so their description is omitted.

[0100] In addition to service A, sales system 3 can also provide services such as those in which a store clerk registers products using registration device 53 and the customer settles the payment using payment device 54, or services in which a store clerk registers products and settles the payment using registration and payment device 59.

[0101] The registration and settlement device 59 is primarily used by store employees. Specifically, the registration and settlement device 59 is equipped with a scanner unit and a settlement unit (specifically, a cash settlement unit) on one side (the employee side). The configuration of the registration and settlement device 59 will be described later.

[0102] (Registration and settlement device 59) Figure 18 is a diagram illustrating the external appearance of the registration and settlement device 59. Figure 19 is an example of the configuration of the registration and settlement device 59. In Figures 18 and 19, the same parts are denoted by the same reference numerals. The registration and 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 dispenser (cash settlement unit) 509, a staff-side display unit 510, a key operation unit 511, a printing unit 513, an audio output unit 514, and a communication unit 515. These can communicate with each other via a bus. The registration and settlement device 59 may further include a card settlement unit (similar to the card settlement unit 108 of the settlement device 50) and 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 registration settlement device 59 are the same as those of 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.

[0104] The customer-side display unit 505 is a touch display that displays various information to the customer and accepts various inputs from the customer. Since the registration and payment device 59 is a device where products are registered by store staff, the customer-side display unit 505 does not generally accept inputs for product registration. However, it does accept inputs such as age verification for products registered by store staff.

[0105] The employee-side display unit 510 is a touch display that displays various information to the employee and accepts various inputs from the employee. The key operation unit 511 is equipped with various buttons for the store staff to operate.

[0106] The scanner unit 512 is a scanner unit for store employees and optically reads various types of information. Specifically, the scanner unit 512 scans codes attached to products and reads product codes (such as JAN codes). The scanner unit 512 may also scan codes attached to vouchers and various cards and read the information contained therein. Furthermore, the scanner unit 512 may scan codes attached to employee name tags, etc., and read employee codes.

[0107] The printing unit 513 prints and issues various media (e.g., receipts). These media are issued from the issuing slot 513a and handed to the customer by the store clerk. If the registration and settlement device 59 is configured as shown in the figure and does not have a card payment unit, the printing unit 513 may issue a payment slip or the communication unit 515 may transmit registration information to another device in order to perform card payment. On the other hand, if the registration and settlement device 59 is configured to have a card payment unit, the printing unit 513 may print and issue a receipt after payment has been made by the card payment unit.

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

[0109] In Figure 20 (and similarly in other figures), the upper part of the figure (area A indicated by the dashed line) shows the sales floor of the store according to Example 1, and the center of the figure (area B indicated by the dashed line) shows the checkout area of ​​the same store. In the lower part of the figure (opposite the sales floor side from the checkout area), there is a packing counter for bagging items and a service counter for receiving inquiries and applications. The lower right of the figure is the exit. In this figure (and similarly in Figures 21 to 23), the area that does not include the packing counter or service counter is referred to as the checkout area, but the area that includes at least one of the packing counter or service counter may also be referred to as the checkout area. In Figure 24, the area that includes the service counter is referred to as the checkout area.

[0110] As shown in Figure 20, the accounting area is equipped with three settlement devices 50 (settlement devices 50-1 to 50-3), three registration settlement devices 51 (registration settlement devices 51-1 to 51-3), four registration settlement devices 52 (registration settlement devices 52-1 to 52-4), two registration devices 53 (registration devices 53-1 and 53-2), four settlement devices 54 (settlement devices 54-1 to 54-4), and one transaction status management device 40. The registration settlement devices 51-1 to 51-3 (and similarly for registration 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 Figure 20, the dotted lines KD1 to KD4 represent the checkout routes (checkout paths) formed within the store. In Figure 20 (and other figures), individuals with diagonal lines (e.g., those labeled T) are store employees, while individuals with solid-colored bodies (e.g., those labeled K) are customers. The area C, indicated by the dashed line, will be discussed later.

[0112] (Accounting workflow KD1, KD2) The KD1 checkout flow is an accounting flow in which a store clerk registers products using the registration device 53-1, and the customer pays for the products registered in the registration device 53-1 using the payment device 54-1 or payment device 54-2. The KD2 checkout flow is an accounting flow in which a store clerk registers products using the registration device 53-2, and the customer pays for the products registered in the registration device 53-2 using the payment device 54-2 or payment device 54-3.

[0113] Customers who have placed all the necessary items into their baskets on the sales floor and wish to use a semi-self-service checkout system (specifically, product registration by a store employee followed by self-payment) should take their baskets and enter the checkout area from the sales floor as shown in checkout route KD1 or checkout route D2.

[0114] In the checkout route KD1, the store clerk transfers items from the basket handed to them by the customer (the basket into which the customer placed items on the sales floor) to an empty basket, while registering the items (and paid shopping bags if necessary) using the registration device 53-1. After registering the items, the store clerk selects one of the payment devices 54, either payment device 54-1 or payment device 54-2, to be used for payment of the registered items, and guides the customer (informing the customer of the selected payment device 54). The customer takes the basket containing the registered items (the basket into which the items were transferred during registration), moves to the designated payment device 54, and makes the payment. In other words, the registration device 53-1 registers the items based on the store clerk's operation and transmits the registration information to the payment device 54 selected based on the store clerk's operation. The payment device 54, having received the registration information from the registration device 53-1, makes the payment for the items registered in the registration device 53-1 based on the customer's operation. Furthermore, after paying at the payment terminal 54, customers move to the packing area with the basket containing the purchased items, pack the items in the basket into a bag (reusable bag, paid shopping bag), return the empty basket to the return area (not shown), and then move to the exit to leave the store.

[0115] Alternatively, after registering the product, the store clerk may, instead of selecting either payment device 54-1 or payment device 54-2, operate the send button and guide the customer (informing the customer of which of payment devices 54-1 or 54-2 is automatically selected after the operation of the send button and notified to the store clerk as the destination for sending the registration information).

[0116] Alternatively, after registering the products, the store clerk may, instead of selecting either payment device 54-1 or payment device 54-2 or pressing the send button, print and issue a receipt and guide the customer (informing the customer to have the receipt read by either payment device 54-1 or payment device 54-2). Once a receipt is issued, the customer takes the basket containing the registered products, moves to payment device 54-1 (or payment device 54-2), has the receipt read, and then makes the payment. In other words, the registration device 53-1 prints and issues a receipt based on the store clerk's operation, and payment device 54-1 (and similarly payment device 54-2) that reads the receipt may then process the payment for the products registered in the registration device 53-1 based on the customer's operation.

[0117] The operation of each device on accounting flow path KD2 (registration device 53-2, settlement device 54-3, settlement device 54-4) is the same as the operation of each device on accounting flow path KD1 (registration device 53-1, settlement device 54-1, settlement device 54-2), so the explanation is omitted.

[0118] (Accounting workflow KD3) The KD3 checkout flow is a checkout flow in which customers register their goods and settle their accounts using either the registration and settlement devices 51-1 to 51-3 or the registration and settlement devices 52-1 to 52-4. The registration and settlement devices 51-1 to 51-3 are devices that support both cash and non-cash payments. The registration and settlement devices 52-1 to 51-4 are devices that support non-cash payments only. As mentioned above, the registration and settlement devices 51-1 to 51-3 (and similarly the registration and settlement devices 52-1 to 52-4) have multiple operating modes, but all are set to full self-service mode.

[0119] Customers who have placed all the necessary items into their shopping baskets and wish to use a fully self-service checkout system (registering and paying for their items themselves) should take their baskets and enter the checkout area from the sales floor as shown in checkout route KD3.

[0120] In the KD3 checkout flow, customers planning to pay with cash move to one of the registration and settlement devices 52-1 to 52-4 with their basket (the basket containing the goods in the sales area), register the goods (and paid shopping bags if necessary), and pay with cash. Customers planning to pay with cash move to one of the registration and settlement devices 51-1 to 51-3 or 52-1 to 52-4 with their basket, register the goods (and paid shopping bags if necessary), and pay with cash. In other words, registration and settlement device 51-1 (and similarly for registration and settlement devices 51-2 and 51-3) registers the goods based on the customer's operation and settles the payment with either cash or cash. Registration and settlement device 52-1 (and similarly for registration and settlement devices 52-2 to 52-4) register the goods based on the customer's operation and settles the payment with cash or cash.

[0121] Furthermore, customers pack the items placed in their baskets into bags (reusable bags, paid shopping bags) at the registration and payment device 51-1 (the same applies to registration and payment devices 51-2, 51-3, and registration and payment devices 52-1 to 52-4). After payment at the registration and payment device 51-1 (the same applies to registration and payment devices 51-2, 51-3, and registration and payment devices 52-1 to 52-4), they do not move to the packing counter, but return the empty basket to the return area (not shown) and move to the exit to leave the store.

[0122] (Accounting workflow KD4) The payment flow KD4 is the payment flow when a customer uses payment devices 50-1 to 50-3 to pay for products they have registered using a mobile terminal 60.

[0123] Customers who have registered all the necessary items in the sales area using their mobile terminal 60 and placed them in a basket, etc., and who wish to pay by themselves (specifically, to settle the bill themselves), will take the basket, etc., and enter the checkout area from the sales area as shown in the checkout route KD4.

[0124] In the checkout route KD4, customers move to one of the payment devices 50-1 to 50-3 with the baskets mentioned above, register their items (including paid shopping bags if necessary), and pay. In other words, payment device 50-1 (and similarly for payment devices 50-2 and 50-3) processes the payment for items registered on the sales floor using the mobile terminal 60, based on the customer's operation.

[0125] Furthermore, customers pack the items placed in baskets, etc., into bags (reusable bags, paid shopping bags) at the payment terminal 50-1 (the same applies to payment terminals 50-2 and 50-3). After payment at payment terminal 50-1 (the same applies to payment terminals 50-2 and 50-3), they do not move to the packing counter, but return the empty baskets, etc., to the return area (not shown) and move to the exit to leave the store.

[0126] (Regarding the information) Although not shown in the diagram, at the boundary between the sales floor and the checkout area, there are signs (notifications) indicating which of the checkout routes KD1-4 to choose for customers, and guidance to lead customers to the most suitable checkout route. For example, customers are guided by signs, hanging signs from the ceiling, floor printing, and signage devices (for example, signage devices connected to LAN19 and controllable from the transaction status management device 40). This allows customers to be smoothly guided to the most suitable route (selected according to the desired route or the type of registration and settlement). The notification methods are easy to see, using text, colors, symbols (for example, arrows, circles and crosses, etc.) or combinations thereof.

[0127] Furthermore, guidance may be provided according to the payment method. For example, the checkout route KD3 may be divided into two paths (a path leading to the registered settlement device 51 (cash handling device) that supports cash payments, and a path leading to the registered settlement device 52 (non-cash handling device) that does not support cash payments), and customers who wish to pay in cash (cash payment customers) and customers who wish to pay by other means (non-cash payment customers) may be guided accordingly. This can reduce problems such as cash payment customers mistakenly using a non-cash handling device, or cash payment customers being unable to use a cash handling device because it is being used by a non-cash payment customer.

[0128] Furthermore, if a certain device is unavailable due to factors such as the time of day, the number of customers in the store, or the number of staff, the system may notify customers that payment cannot be made using the payment route that utilizes that device (that the payment route is unavailable). For example, if registration device 53-1 is out of service due to the absence of staff, the system may notify customers that payment cannot be made using payment route KD1. Also, if both settlement devices 54-3 and 54-4 are undergoing maintenance (for example, during closing procedures), the system may notify customers that payment cannot be made using payment route KD2 (however, if an exception is made, such as specifying settlement devices 54-1 and 54-2 from registration device 53-2, payment can still be made using payment route KD2). In addition, the signage system may be controlled to display the latest information regarding the availability of payment routes based on the status of each device (for example, the presence or absence of staff at registration device 53 (for example, login / logout information), and information on whether settlement device 54 is undergoing maintenance) (obtained from each device). Furthermore, even when using signs or other means of notification instead of digital signage, the registration device 53 may also notify customers about the signs (such as removing the signs or reversing their orientation) when the status of each device changes (for example, when logging out of the registration device 53 or when maintenance of the payment device 54 begins). This prevents staff from forgetting what to do with the signs, thus preventing customers from being continuously guided to the wrong checkout routes. The notification about the signs is not limited to the logged-out registration device 53; for example, the transaction status management device 40 may also be notified in place of or in addition to the logged-out registration device 53. In this case, for example, if the transaction status management device 40 is notified in addition to the registration device 53, the staff of the transaction status management device 40, which oversees and monitors the entire checkout area, will also be notified, thus more reliably preventing customers from being continuously guided to the wrong checkout routes. Furthermore, if the notification is sent only to the transaction status management device 40, it is possible to efficiently prevent the store staff of the transaction status management device 40, who are responsible for monitoring the entire accounting area, from continuously guiding customers to accounting routes that should not be used.

[0129] Furthermore, while the above describes the case where a system goes from being available to being unavailable, the same applies to the case where a system goes from being unavailable to being available. For example, if the store starts using checkout routes KD3 and KD4 at opening time, and then adds checkout routes KD1 and KD2 sequentially during busy periods, the registration device 53-1 may be notified when the customer logs in that checkout route KD1 is now available, and the registration device 53-2 may be notified when the customer logs in that checkout route KD2 is now available. This allows for prompt guidance to the customer regarding the checkout route that has become available. The above guidelines also apply to the other installation layout examples (Examples 2-5) described later.

[0130] Furthermore, while the above describes examples of providing guidance using signage devices, freestanding signs, hanging signs, floor printing, etc., at the boundary between the sales area and the checkout area, similar guidance may be provided in other locations instead of, or in addition to, the boundary between the sales area and the checkout area. For example, guidance may be provided at the entrance of the store. When providing information at the store entrance, the information could include, for example, the congestion status of each checkout route based on the number of staff members (work schedule, activity schedule, etc.). For example, according to the above schedule, information such as "According to the above schedule, there are currently no staff members at registration device 53-1, therefore checkout route KD-1 is unavailable" could be displayed on a signage device at the entrance. Instead of, or in addition to, providing information on the congestion status of each checkout line based on the number of staff members, the actual congestion status of each checkout line may be provided. For example, cameras may be installed in the store to recognize the number (large or small) of customers queuing at each checkout line using image processing, and the actual congestion status of each checkout line may be provided. When providing information at the store entrance, for example, it might be helpful to guide customers on the type of service (checkout route) corresponding to the number of items purchased (in other words, guide them on the efficiency of different devices according to the number of items purchased). That is, if it has been found through experience that the transaction using checkout route KD3 is the fastest way to finish shopping when the number of items purchased is less than A (where A is an integer), the transactions using checkout routes KD1 and KD2 are the fastest way to finish shopping when the number of items purchased is between A and B (where B is an integer greater than A), and the transaction using checkout route KD4 (service A) is the fastest way to finish shopping when the number of items purchased exceeds B, then since the optimal checkout route differs depending on the number of items purchased, providing this kind of information to customers in advance at the entrance is very effective for both customers and stores. For example, customers can check the above information at the entrance when they start shopping, and while shopping in the store, they can check the current number of items purchased as needed, recognize which transaction (service, checkout route) is most suitable, and select it. Furthermore, the system may calculate and guide customers to the most recommended transactions (services, checkout routes) based on two pieces of information: congestion status (congestion status based on the number of staff, and actual congestion status) and efficiency by device. This calculation may be performed by any device within the sales system 1 (i.e., 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, or mobile terminal 60). Alternatively, two or more devices may share the task of performing this calculation. While the store entrance was mentioned as another possible location, other areas inside the store may also be used. This allows for guidance to be directed as needed.

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

[0132] As shown in Figure 21, the accounting area is equipped with two settlement devices 50 (settlement devices 50-1 and 50-2), four registration settlement devices 51 (registration settlement devices 51-1 to 51-4), four registration devices 53 (registration devices 53-1 to 53-4), four settlement devices 54 (settlement devices 54-1 to 54-4), and one transaction status management device 40. The registration settlement devices 51-1 to 51-4 have multiple operating modes, but registration settlement devices 51-1 and 51-2 are set to settlement-only mode, and registration settlement devices 51-3 and 51-4 are set to full self-service mode (however, this can be changed as appropriate). Furthermore, registration device 53-4 is assumed to be unattended. In Figure 21, the dotted lines KD5 to KD9 represent the accounting flow formed in the store.

[0133] (Accounting workflow KD5, KD6) The operation of each device on accounting flow path KD5 (registration device 53-1, settlement device 54-1, settlement device 54-2) and each device on accounting flow path KD6 (registration device 53-2, settlement device 54-3, settlement device 54-4) is the same as the operation of each device on accounting flow path KD1 in the above-described embodiment 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so a description is omitted.

[0134] (Accounting workflow KD7, KD8) The KD7 checkout flow is an accounting flow in which a store clerk registers products using the registration device 53-3, and the customer settles the payment for the registered products using the registration and settlement device 51-1 or the registration and settlement device 51-2. The KD8 checkout flow is an accounting flow in which the customer registers products using the registration and settlement device 51-3 or the registration and settlement device 51-4 and settles the payment.

[0135] Customers who have placed all the necessary items into their baskets on the sales floor and wish to use a semi-self-service checkout (specifically, product registration by a store employee and payment by the customer) should take their basket and enter the checkout area from the sales floor as shown in checkout route KD7. On the other hand, customers who have placed all the necessary items into their baskets on the sales floor and wish to use a fully self-service checkout (specifically, product registration and payment by the customer) should take their basket and enter the checkout area from the sales floor as shown in checkout route KD8.

[0136] In checkout route KD7, the store clerk transfers items from the basket handed to them by the customer (the basket in which the customer placed items on the sales floor) to an empty basket, while registering the items (and paid shopping bags if necessary) using the registration device 53-3. After registering the items, the store clerk selects one of the registration and payment devices 51-1 or 51-2, which are operating in payment-only mode, to be used as the payment device 51 for the registered items, and guides the customer (informing the customer of the selected registration and payment device 51). The customer then takes the basket containing the registered items, moves to the designated registration and payment device 51, and makes the payment. In other words, the registration device 53-3 registers the items based on the store clerk's operation and transmits the registration information to the registration and payment device 51 selected based on the store clerk's operation. The registration and payment device 51, having received the registration information from the registration device 53-3, makes the payment for the items registered in the registration device 53-3 based on the customer's operation. Furthermore, after paying at the registration and payment device 51, customers move to the packing area with their baskets, pack the items in the baskets into bags (reusable bags, paid shopping bags), return the empty baskets to the return area (not shown), and then move to the exit to leave the store.

[0137] Alternatively, after completing product registration, the store clerk may operate the send button instead of selecting either the registration and payment device 51-1 or the registration and payment device 51-2, and guide the customer (by informing the customer of which of the registration and payment device 51-1 or the registration and payment device 51-2 is automatically selected after the operation of the send button and notified to the store clerk as the destination for sending the registration information).

[0138] Alternatively, after registering the products, the store clerk may, instead of selecting either the registration and payment device 51-1 or the registration and payment device 51-2 or pressing the send button, print and issue a payment slip and guide the customer (informing the customer to have the payment slip read by either the registration and payment device 51-1 or the registration and payment device 51-2). Once a payment slip is issued, the customer takes the basket containing the registered products, moves to the registration and payment device 51-1 (or registration and payment device 51-2), has the payment slip read, and then makes the payment. In other words, the registration device 53-3 prints and issues a payment slip based on the store clerk's operation, and the registration and payment device 51-1 (or registration and payment device 51-2) that reads the payment slip may then settle the payment for the products registered in the registration device 53-3 based on the customer's operation.

[0139] In checkout route KD8, since there is no staff member at registration device 53-4, customers carry their baskets, pass in front of registration device 53-4, move to registration and payment device 51-3 (or registration and payment device 51-4), register their items (including paid shopping bags if needed), and pay.

[0140] In other words, the accounting method using accounting flow path KD7 in Example 2 is the same as the accounting method using the registration and settlement device 51 instead of the settlement device 54 in accounting flow path KD1 in Example 1 (and similarly in accounting flow paths KD2 in Example 1, and accounting flow paths KD and KD6 in Example 2). Also, the accounting method using accounting flow path KD8 in Example 2 is the same as the accounting method using accounting flow path KD3 in Example 1 (the method using the registration and settlement device 51), without using the registration device 53-4 which does not have a staff member.

[0141] Depending on the store's congestion level, the registration device 53-3 on checkout path KD7 may be omitted, and the items (including paid shopping bags if necessary) may be registered and settled using the registration and settlement device 51-1 (or registration and settlement device 51-2). In other words, the checkout process using checkout path KD7 may be made to resemble the checkout process using checkout path KD8. Furthermore, depending on the store's congestion level, the registration device 53-4 on checkout path KD8 may be used, and the items registered using registration device 51-3 (or registration and settlement device 51-4) may be settled using the registration and settlement device 51-3 (or registration and settlement device 51-4). In other words, the checkout process using checkout path KD8 may be made to resemble the checkout process using checkout path KD7.

[0142] Furthermore, the registration and payment device 51-1 (and the same applies to the registration and payment device 51-2) may operate in payment-only mode when a store employee is using the registration device 53-3, and in full self-service mode when a store employee is not using the registration device 53-3. Similarly, the registration and payment device 51-3 (and the same applies to the registration and payment device 51-4) may operate in payment-only mode when a store employee is using the registration device 53-4, and in full self-service mode when a store employee is not using the registration device 53-4.

[0143] For example, when registration device 53-3 reads an employee code for login, it notifies registration payment devices 51-1 and 51-2 that use has begun, and registration payment devices 51-1 (and similarly 51-2) may switch to payment-only mode when they receive the above notification from registration device 53-3 and their operating mode is not payment-only mode. Also, when an employee (for example, an employee leaving registration device 53-3) makes an operation, registration device 53-3 notifies registration payment devices 51-1 and 51-2 that use has ended, and registration payment devices 51-1 (and similarly 51-2) may switch to full self-service mode when they receive the above notification from registration device 53-3 and their operating mode is not full self-service mode. The same applies to registration device 53-4, registration payment devices 51-3 and 51-4.

[0144] (Accounting workflow KD8) The operation of each device on the accounting workflow KD9 (settlement device 50-1, settlement device 50-2) is the same as the operation of each device on the accounting workflow KD4 in the above-described embodiment 1 (Figure 20) (settlement devices 50-1 to 50-3), so the explanation is omitted.

[0145] (Example 3 of installation layout) Figure 22 shows an example of the installation layout of each device in the sales system 2 of the second embodiment (Figure 16) (Example 3 relating to the installation layout).

[0146] As shown in Figure 22, the accounting 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, the dotted lines KD10 to KD14 represent the accounting flow within the store.

[0147] (Accounting workflow KD10) The operation of each device (settlement device 50-1 to settlement device 54-6) on the accounting flow path KD10 is the same as the operation of each device (settlement device 50-1 to settlement device 50-3) on the accounting flow path KD4 in the above-described embodiment 1 (Figure 20), so the explanation is omitted. Note that the rows of settlement devices 50-1 to 54-3 and the rows of settlement devices 50-3 to 54-6 are installed back to back (so that customers in different rows face each other with the devices in between), so the accounting flow path KD10 and accounting flow path DK10 branch into two along each row. Alternatively, the accounting flow path KD10 may be routed between the rows of settlement devices 50-1 to 54-3 and the rows of settlement devices 50-3 to 54-6 so that customers in different rows operate them back to back.

[0148] (Accounting workflow KD11, KD12) The operation of each device on accounting flow path KD11 (registration device 53-1, settlement device 54-1, (settlement device 54-2)) and each device on accounting flow path KD12 (registration device 53-2, settlement device 54-3, (settlement device 54-2)) is the same as the operation of each device on accounting flow path KD1 in the above-described embodiment 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so a description will be omitted. Note that settlement device 54-2 is a device on accounting flow path KD11 and a device on accounting flow path KD12. In other words, settlement device 54-2 settles both the goods registered by registration device 53-1 and the goods registered by registration device 53-2.

[0149] (Accounting workflow KD13) The operation of each device on the accounting flow path KD13 (registration device 53-4, settlement device 54-5, settlement device 54-6) is the same as the operation of each device on the accounting flow path KD1 in the above-described embodiment 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so a description is omitted.

[0150] (Accounting workflow KD14) The operation of each device on the accounting workflow KD14 (registration device 53-3, settlement device 54-4) is the same as the operation of each device on the accounting workflow KD1 in the above-described embodiment 1 (Figure 20) (registration device 53-1, settlement device 54-1, settlement device 54-2), so a description is omitted. Note that in the accounting workflow KD13, there is only one settlement device 54. When there is only one settlement device 54, it is not necessary to select a destination for sending registration information.

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

[0152] As shown in Figure 23, the accounting 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, the dotted lines KD15 to KD20 represent the accounting routes formed within the store.

[0153] (Accounting workflow KD15, KD16, KD18, KD19, KD20) The operation of each device on accounting flow path KD15 (registration device 53-1, settlement device 54-1) is the same as the operation of each device on accounting flow path KD14 in the above-described embodiment 3 (Figure 23) (registration device 53-3, settlement device 54-4), so the explanation is omitted. The same applies to the operation of each device on accounting flow path KD16 (registration device 53-2, settlement device 54-2), the operation of each device on accounting flow path KD18 (registration device 53-3, settlement device 54-3), the operation of each device on accounting flow path KD19 (registration device 53-4, settlement device 54-4), and the operation of each device on accounting flow path KD20 (registration device 53-5, settlement device 54-5).

[0154] (Accounting workflow KD17) The operation of the device (settlement device 50-1) in accounting workflow KD17 is the same as the operation of each device (settlement devices 50-1 to 50-3) in accounting workflow KD4 of the above-described embodiment 1 (Figure 20), so the explanation is omitted. Note that two or more settlement devices 50 may be installed.

[0155] (Example 5 of installation layout) Figure 24 shows an example of the installation layout of each device in the sales system 3 of the third embodiment (Figure 17) (Example 5 relating to the installation layout).

[0156] As shown in Figure 24, the accounting 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, the dotted lines KD21 to KD25 represent the accounting flow within the store.

[0157] (Accounting workflow KD21, KD22, KD24) The operation of each device on accounting flow path KD21 (registration device 53-1, settlement device 54-1, settlement device 54-2) is the same as the operation of each device on accounting flow path KD1 in the above-described embodiment 1 (Figure 20), so a description is omitted. The same applies to the operation of each device on accounting flow path KD22 (registration device 53-2, settlement device 54-3, settlement device 54-4) and the operation of each device on accounting flow path KD24 (registration device 53-3, settlement device 54-5, settlement device 54-6).

[0158] (Accounting workflow KD23) The operation of the devices (settlement devices 50-1 and 50-2) in accounting workflow KD23 is the same as the operation of each device (settlement devices 50-1 to 50-3) in accounting workflow KD4 of the above-described embodiment 1 (Figure 20), so the explanation is omitted.

[0159] (Accounting workflow KD25) The checkout workflow KD25 is a workflow that forms the checkout process in which a store employee registers products using the registration and settlement device 59 and then settles the payment.

[0160] Customers who have placed all the necessary items into their shopping baskets and wish to have a store employee handle the payment (item registration and settlement) should take their baskets and enter the checkout area from the sales floor as shown in checkout route KD25.

[0161] In checkout route KD25, the store clerk transfers items from the basket handed to them by the customer (the basket in which the customer placed items on the sales floor) to an empty basket, registers the items (and paid shopping bags if necessary) using the registration and payment device 59, and then processes the payment. After payment at the registration and payment device 59, the customer takes the basket containing the paid items to the packing counter, packs the items in the basket into a bag (reusable bag or paid shopping bag), returns the empty basket to the return area (not shown), and then moves to the exit to leave the store.

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

[0163] Figure 25(A) is an example of a cash register management screen for managing installed cash registers. Figure 25(B) is an example of a mobile device management screen for managing mobile devices. For example, the transaction status management device 40 displays the cash register management screen shown in Figure 25(A) and the mobile device management screen shown in Figure 25(B) in a switchable manner by operating the tabs ("Cash Registers" and "Mobile Devices"). Note that Figure 25(A) is an example of a cash register management screen according to Embodiment 1 (Figure 20). Furthermore, it is assumed that there is a mix of mobile devices 60 owned by individual customers and mobile devices 60 lent by the store within the store.

[0164] (Installed POS system management screen) The transaction status management device 40 allows users to switch between displaying the installed register management screen based on layout (installation location) (hereinafter sometimes referred to as the "installed register management screen (layout display)") and displaying the installed register management screen based on function (type of device, checkout flow (lane), etc.) (hereinafter sometimes referred to as the "installed register management screen (function-based display)") by operating buttons (layout button BT401, function button BT402).

[0165] In Figure 25(A), the thick border around the layout button BT401 and the thin border around the function button BT402 indicate that the last button operated was the layout button BT401 (i.e., the layout display is selected). In other words, the installation register management screen shown in Figure 25(A) is the installation register management screen (layout display).

[0166] In the installation register management screen (layout display) shown in Figure 25(A), display area HR403 is the main display area. The transaction status management device 40 displays icons corresponding to each device installed in the accounting area in the main display area HR403, as shown in Figure 25(A), at positions corresponding to their respective installation locations in the accounting area. Icons with numbers correspond to the installed registers (devices that register or settle products). Icons with diagonal lines without numbers correspond to the transaction status management device 40.

[0167] Furthermore, in the layout display, it may be made clear that the customer stands at each device (which side of each device they stand on). For example, in the device corresponding to icon 14 in the upper right of the drawing (settlement device 50-1 shown in Figure 20), the customer stands on the side of the device corresponding to icon 9 (registration and settlement device 52-2 shown in Figure 20) (with their back to it). For example, one side of icon 14 on the side of icon 9 may be displayed in a different manner (e.g., color) than the other three sides, or a mark indicating that the customer stands on that side (e.g., an image with the word "customer" inside a circle) may be displayed. The display manner of this mark may differ depending on whether or not a customer is present (e.g., determined by a motion sensor), and for devices operated by the customer, the display manner may differ depending on whether or not the customer is operating it. Furthermore, this mark does not necessarily indicate the customer's standing position at each device, but simply indicates whether or not a customer is present or whether or not the customer is operating it.

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

[0169] In the installed register management screen (layout display) shown in Figure 25(A), the display area HR405 is the detailed information display area. 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, although this is not shown in the illustration. For example, the transaction status management device 40 displays the current operating mode if there are multiple operating modes, whether or not it is being used by a store clerk or customer, the status of the change, the status of the paper, etc., as detailed information. In addition, the installed register whose detailed information is displayed in the detailed information display area HR405 (i.e., the installed register selected by operation) may be displayed in a different display manner in the main display area HR403 than other installed registers. In this example, it is displayed with a thick border, but it may be displayed in a different color or marked.

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

[0171] (Mobile device management screen) In the mobile terminal management screen shown in Figure 25(B), the display area HR410 is the terminal count display area. The transaction status management device 40 displays the number of mobile terminals 60 currently in a transaction in the terminal count display area HR410. Mobile terminals 60 currently in a transaction are those that have started product registration but have not yet completed settlement. The transaction status management device 40 displays various information on the mobile terminal management screen based on information stored in the cloud server 20 (transaction information for each mobile terminal 60) and information stored in the headquarters server 10 (customer master, etc.).

[0172] In the mobile terminal management screen shown in Figure 25(B), the display area HR412 is the abnormal transaction terminal count display area. An abnormal transaction is, for example, a transaction that includes a held item and where subsequent settlement processing cannot be completed normally without verification by a store employee. A held item is an item whose settlement in the settlement process is temporarily suspended. Held items include, for example, unscanned items whose scanning has not been completed, NON-file items that were scanned but whose product code was not registered in the product master and therefore price and other information could not be obtained, age-verified items such as alcohol, pharmaceuticals that require explanation by a pharmacist, etc., and items with security tags. The transaction status management device 40 displays the number of mobile terminals 60 in the abnormal transaction terminal count display area HR412 that are conducting transactions and whose transactions are abnormal.

[0173] In the mobile terminal management screen shown in Figure 25(B), the display area HR414 is the normal transaction terminal count display area. A normal transaction is, for example, a transaction that does not include any held items and in which the subsequent settlement process can be completed normally without confirmation by a store employee. The transaction status management device 40 displays the number of mobile terminals 60 in which a transaction is a normal transaction in the normal transaction terminal count display area HR414.

[0174] In the mobile terminal management screen shown in Figure 25(B), display area HR423 is the main display area. The transaction status management device 40 displays a list of information about the mobile terminals 60 that are currently trading in the main display area HR423. The display selection button BT411 is a button for selecting all mobile terminals 60 that are currently trading (including both mobile terminals 60 whose transactions are abnormal and mobile terminals 60 whose transactions are 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 mobile terminals 60 whose transactions are abnormal as the mobile terminals 60 to be displayed in the main display area HR423. The display selection button BT415 is a button for selecting mobile terminals 60 whose transactions are normal as the mobile terminals 60 to be displayed in the main display area HR423. In the example shown in Figure 25(B), the display selection button BT413 is operated (the grayed-out state indicates that it has been selected), and the main display area HR423 displays a list of information regarding the mobile terminal 60 whose transaction is an abnormal transaction. If there are many mobile terminals 60 to display, each one may be displayed in a smaller size, or they may be displayed on multiple pages.

[0175] In the mobile terminal management screen shown in Figure 25(B), display area HR425 is the detailed information display area. The transaction status management device 40 displays detailed information about one mobile terminal 60 (for example, the mobile terminal 60 selected by operation in the main display area HR423) in the detailed information display area HR425, although this is not shown in the illustration. For example, the transaction status management device 40 displays the purchase history of the customer as detailed information (the purchase history of each customer may be stored in the headquarters server 10, for example). Furthermore, the mobile terminal 60 whose detailed information is displayed in the detailed information display area HR425 (i.e., the mobile terminal 60 selected by operation) may be displayed in a different display manner in the main display area HR423 than other mobile terminals 60. In this example, it is displayed with a thick border, but it may be displayed in a different color or marked.

[0176] The display of the transaction status management device 40 has been explained using Figure 25, but the management screens displayed by the transaction status management device 40 are not limited to those shown in Figure 25. For example, the above explanation described an example of switching between the installed cash register management screen (Figure 25(A)) and the mobile terminal management screen (Figure 25(B)), but instead of switching between them, or in addition to doing so, the installed cash register management screen and the mobile terminal management screen may be displayed simultaneously (for example, side by side, one above the other). When displaying them simultaneously, the system may also accept operations such as making one larger and the other smaller. The same applies to the installed cash register management screen (layout display) and the installed cash register management screen.

[0177] Furthermore, although the above describes monitoring all mobile terminals 60 uniformly without distinguishing the processing progress between the start of product registration and the completion of settlement, monitoring may be performed according to the processing progress. For example, the transaction status management device 40 may display any of the following (1) to (6) as selectable options. Alternatively, for example, each mobile terminal 60 may notify the cloud server 20 of information regarding the processing progress, and the cloud server 20 may store information regarding the processing progress in the transaction information of each mobile terminal 60, thereby allowing the transaction status management device 40 to recognize the processing progress of each mobile terminal 60 (in other words, extract the mobile terminals 60 belonging to (1) to (6)).

[0178] (1) Mobile terminal 60 after product registration has started but before product registration is complete (for example, before the display of the 2D code 605 for settlement) (i.e., mobile terminal 60 during product registration) (2) After product registration is complete, but before payment begins (for example, before the payment device 50 reads the 2D code 605 for payment) the mobile terminal 60 (i.e., the mobile terminal 60 that is in the process of moving to payment) (3) Mobile terminal 60 after the start of settlement but before settlement is completed (i.e., mobile terminal 60 during settlement) (4) Mobile terminal 60 after product registration begins but before settlement begins (i.e., (1) + (2)) (5) After product registration is complete, and before payment is completed (i.e., (2) + (3)) the mobile terminal 60 (6) After product registration begins, but before settlement is completed (i.e., (1) + (2) + (3). Example in Figure 25(B)) the mobile terminal 60

[0179] (Exit Gate) In the first embodiment (and similarly in other embodiments), an exit gate may be installed near the exit (or just before the exit) to prevent fraudulent activity such as leaving the store without paying. The exit gate may be equipped with a reader and may permit passage by reading a predetermined two-dimensional code for permission to pass through. The two-dimensional code for permission to pass through may, for example, be printed on a receipt issued after payment, or displayed on a mobile terminal 60 after payment. The exit gate may be configured to restrict movement, for example, like an automatic ticket gate at a train station, or it may simply display an information on a screen or provide audio notification. The exit gate may also be connected to a network (LAN) and managed (monitored and controlled) by a transaction status management device 40.

[0180] As described above, embodiments 1 to 3 can provide a suitable accounting workflow when multiple services coexist.

[0181] (Variations, etc.) Although embodiments have been described above, the configuration of the equipment, the data configuration, the processing flow, the display and output methods, etc., can be changed as appropriate, for example, as shown in (1), (2), ... below. Furthermore, (1), (2), ... below can be combined in any way as appropriate.

[0182] (1) In the above embodiment, the payment device 50 installed in the store in each sales system was described as a device that pays for products registered by the mobile terminal 60, but the payment device 50 may also pay for products registered by a device other than the mobile terminal 60 (for example, a registration payment device 51, a registration payment device 52, or a registration device 53). For example, the payment device 50 may receive registration information from the registration device 53, as in the payment device 54, and pay for products registered by the registration device 53. Similarly, the payment device 54 installed in the store in each sales system was described as a device that pays for products registered by the registration device 53, but the payment device 54 may also pay for products registered by a device other than the registration device 53 (for example, a registration payment device 51, a registration payment device 52, or the mobile terminal 60).

[0183] (2) In the above embodiments, the payment device 50, registration payment device 51, registration payment device 52, registration device 53, payment device 54, and registration payment device 59 were described as registration devices or payment devices installed in the store in each sales system. However, the registration devices and payment devices installed in the store in each sales system are not limited to the devices described above. As an example, a registration payment device (a registration payment device equivalent to the registration payment device 51 (or registration payment device 52) fixed in full self-service mode; hereinafter referred to as registration payment device 55) which is exclusively for customers to register and pay for goods, may be installed in the store in place of or in addition to the registration payment device 51 (or registration payment device 52). Note that the registration payment device 51 (or registration payment device 52) includes a scanner unit used by the customer and a scanner unit used by the store staff (Figure 5), but the registration payment device 55 only needs to include a scanner unit used by the customer.

[0184] (3) In the above embodiment, an example was described in which a customer registers products using a mobile terminal 60, but it 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, a tablet terminal lent by the store to the customer or a shopping cart equipped with a display unit (or a display unit that can be attached to or detached from the shopping cart) may be used to register products. The shopping cart may be equipped with an electronic tag recognition unit that recognizes the information of the 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 implemented in a device other than the device described as the entity executing the function. For example, as processing of the settlement device 50, at least some of the processing described using the sequence diagram in Figure 15 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 in input / output interfaces, etc. For example, the settlement device 50 may receive various inputs (customer operations, detection by devices such as scanners), send 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 send the processing result (updated screen information, etc.) to the settlement device 50, and then the settlement device 50 may execute an operation (display on the display unit, etc.) according to the information received from the cloud server 20. In other words, the cloud server 20 may execute a program to control the operation of the settlement device 50. The same applies to registration and settlement devices 51, 52, 53, 54, 55, and 59.

[0186] <Summary of Embodiments> [Technical field] This invention relates to a product sales data processing system. [Background technology] Multiple services related to the sale of goods may 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] [Patent Document 1] Japanese Unexamined Patent Publication No. 2016-081072 [Overview of the prefecture] [Problems the invention aims to solve] However, problems can arise in the accounting workflow when multiple services coexist. This invention has been made in view of such circumstances and aims to provide a suitable accounting workflow. [Means for solving the problem]

[0187] (1) A product sales data processing system (for example, sales systems 1, 2, and 3) that performs a registration process for registering products and a settlement process for settling payments for products registered by the registration process, comprising: a first device (for example, a registration device 53) that performs the registration process based on the operation of a store employee; a second device (for example, a settlement device 54) that performs the settlement process based on the operation of a customer for products registered by the first device; and a third device (for example, a settlement device 50) that performs the settlement process based on the operation of a customer for products registered by a portable device (for example, a mobile terminal 60) in the sales area of ​​the store based on the operation of a customer, wherein the first device, the second device, and the third device are installed such that at least a portion of a first checkout route, which is formed to include the installation point of the first device and the installation point of the second device, and a second checkout route, which is formed to include the installation points of each of the plurality of third devices, are substantially parallel to each other. In Example 1 (Figure 20), for example, at least a portion of the accounting route KD1 (first accounting route) (the portion that passes in front of the registration device 53-1) and the accounting route KD4 (second accounting route) are substantially parallel to each other. In Example 2 (Figure 21), for example, at least a portion of the accounting route KD5 (first accounting route) (the portion that passes in front of the registration device 53-1) and the accounting route KD9 (second accounting route) are substantially parallel to each other. In Example 3 (Figure 22), for example, at least a portion of the accounting route KD11 (first accounting route) (the portion that passes in front of the registration device 53-1) and the accounting route KD10 (second accounting route) are substantially parallel to each other. In Example 4 (Figure 23), for example, at least a portion of the accounting route KD15 (first accounting route) (the portion that passes in front of the registration device 53-1) and the accounting route KD17 (second accounting route) are substantially parallel to each other. In Example 5 (Figure 24), for example, at least a portion of the accounting route KD24 (first accounting route) (the portion that passes in front of the registration device 53-3) and the accounting route KD23 (second accounting route) are substantially parallel to each other. According to the configuration of (1), a suitable checkout flow can be provided. In other words, even when multiple services coexist (when there is a first checkout flow and a second checkout flow), the checkout flow within the store becomes orderly and easy to understand.

[0188] (2) The product sales data processing system according to (1), characterized in that it includes a fourth device (e.g., registration and settlement devices 51, 52, 55) that performs the registration process and the settlement process based on customer operations, the total number of the third device (e.g., settlement device 50) and the fourth device (e.g., registration and settlement devices 51, 52, 55) installed is three or more, and the total of three or more of the third device or the fourth device are installed in a row around a predetermined area. In Example 1 (Figure 20), the area C shown by the dashed line is a predetermined area (sometimes referred to as the browsing area), and registration and settlement devices 51-1 to 51-3, registration and settlement devices 52-1 to 52-4, and settlement devices 50-1 to 50-3 are set up in a row around area C. According to configuration (2), the self-service devices are arranged around a designated area, making it easier for customers to access any of the self-service devices. Monitoring and support also become easier. By grouping the settlement device 50 and the registration settlement devices 51 and 52 into one area, the same level of support and monitoring capabilities as those provided by staff during semi-self-service transactions (registration device 53 and settlement device 54) can be applied to the fully self-service devices (settlement device 50 and registration settlement devices 51 and 52). In other words, this layout enables the completion of transactions for a large number of customers with a small number of staff, thus addressing the serious labor shortage.

[0189] (3) The product sales data processing system according to (2), characterized in that the predetermined area is an enclosed region having at least two entrances and at least one exit. In Example 1 (Figure 20), area C has two entrances (accounting route KD3 and accounting route KD4) and one or two exits (either a passage to the right of the transaction status management device 40, or a passage to the left, or both). In Example 1, the registration and settlement devices 52-2 and 52-3 may be installed separately, with the passage between the two devices serving as the access route to area C (i.e., there may be three entrances to area C). Furthermore, depending on the size and shape of area C and the number of devices installed around area C, four or more entrances or three or more exits may be provided. According to the configuration in (3), by providing two entrances, it is possible to prevent customers who wish to use the settlement device 50 and customers who wish to use the registration settlement devices 51 and 52 from lining up in the same queue. Therefore, it is possible to prevent customers with different transaction methods from being mixed together. If there were only one entrance, the two groups would be mixed together, which could lead to problems (for example, customers using the settlement device 50 unnecessarily waiting 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 a single exit and placing a transaction status management device 40 and one monitoring staff member near the exit, visibility of the entire area, including the settlement devices 50 and registration settlement devices 51 and 52, is improved. This allows staff members to directly check the usage status with their own eyes, and also to check the usage status indirectly through the transaction status management device 40, thereby improving support and monitoring. Having a staff member waiting at the exit (in the direction of departure) to provide support and monitoring also has the effect of making it easier for customers to find the staff member, ask for support, and approach them. In addition, customers who use the payment terminal 50 (customers who use service A and proceed to checkout route KD4) are considered to be customers who prioritize comfort and efficiency in their shopping. Therefore, it is important to provide customers who use the payment terminal 50 with a comfortable and efficient product selection and registration experience using the in-store mobile terminal 60, as well as a comfortable and efficient checkout experience using the payment terminal, etc., so that they have a good overall impression from the moment they enter the store until they leave. Here, checkout route KD4 provides the shortest route by making the entrance, payment terminal 50, and exit almost in a straight line, so it can create a good impression not only from the entry to checkout process, but also from the checkout to exit process. Furthermore, Service A is expected to offer significant benefits to stores, as it places the least burden on staff and requires the least amount of time for equipment to be occupied. Moreover, by providing (or continuing to provide) a pleasant experience and impression (like an incentive) to customers who actually use Service A, it helps to retain the use of Service A and motivates new users through word-of-mouth (customers who use Service A are generally thought to be sensitive to various trends and have influence), making it extremely beneficial for stores seeking to expand its usage.

[0190] (4) A product sales data processing system according to either (2) or (3), comprising a monitoring device (for example, a transaction status management device 40) that monitors at least a part of the third device or the fourth device, wherein the monitoring device is installed downstream of the first accounting route or the second accounting route. For example, in Example 1 (Figure 20), the monitoring device is installed downstream of the accounting route KD4 (second accounting route). The configuration in (4) allows for optimal monitoring and support. For example, monitoring is performed downstream (towards the exit) where customers pass after payment, thus acting as a deterrent against fraud. Furthermore, since the support target is located upstream (towards the inside of the store), the support scope is also broadened.

[0191] (5) A packing table is installed downstream of the installation point of the second device in the first accounting route, and the length of the predetermined area in the direction of the first accounting route is less than or equal to the length of the first accounting route from the installation point of the first device to the installation position of the packing table, as described in any of (2) to (4). In Example 1 (Figure 20), the length of the accounting traffic path KD1 in area C, indicated by the dashed line, is shorter than the length of the accounting traffic path KD1 from the installation point of the registration device 53-1 to the installation position of the checkout counter. According to configuration (5), the length of the designated area in the direction of movement is reduced, thereby alleviating the feeling of confinement (crampedness) caused by the designated area, and also allowing for the securing of a passage of the necessary width (the passage in front of the service counter in Figure 20).

[0192] Furthermore, the processing 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 performed by recording a program for realizing the functions of each of the above-described devices on a computer-readable recording medium, loading the program recorded on this recording medium into a computer system, and executing it. Here, "loading the program recorded on the recording medium into a computer system and executing it" includes installing the program into the computer system. Here, "computer system" includes hardware such as the OS and peripheral devices. Also, "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Thus, the recording medium on which the program is stored may be a non-transient recording medium such as a CD-ROM. Furthermore, the recording medium includes internal or external recording media accessible from the distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in an executable format for the terminal device. In other words, the format in which it is stored on the distribution server is irrelevant as long as it can be downloaded from the distribution server and installed in an executable format for the terminal device. It is also acceptable for the program to be divided into multiple parts, downloaded at different times, and then combined on the terminal device, and for each of the divided programs to be distributed by a different distribution server. Moreover, "computer-readable recording medium" includes volatile memory (RAM) within computer systems that act as servers or clients when a program is transmitted over a network, which retains the program for a certain period of time. Furthermore, the program may be intended to implement only a part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [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 product sales data processing system that performs a registration process for registering products and a settlement process for settling payments for products registered through the registration process, A first device that performs the registration process and the settlement process based on customer operations, A second device that performs the registration process and the settlement process based on customer operations, A third device that performs the aforementioned settlement process based on customer operations for products registered by a portable device based on customer operations in the sales area of ​​the store, A transaction status management device that monitors the operating status of the first device, the second device, and the third device, Equipped with, The first device, the second device, the third device, and the transaction status management device are each installed in the accounting area located between the sales floor and the exit. Within the aforementioned accounting area, there is a circulating area. An access path leading from the sales floor side to the area between the first and second devices within the checkout area is formed at a position where it crosses the boundary between the sales floor side and the checkout area side. An access path leading from the sales floor side to the area between the first and third devices in the checkout area is formed at a position where it crosses the boundary between the sales floor side and the checkout area side. An exit path is formed at a position where it crosses the boundary between the accounting area and the exit side, allowing an exit to exit from the accounting area side, passing near the transaction status management device, and exiting to the exit side. The first, second, and third devices are each installed in their respective positions so that the circulation area is formed as an area enclosed by at least three sides consisting of the first, second, and third devices. The first device is installed in such a way that customers operate it facing a first direction, which is the direction of the sales floor; the second device is installed in such a way that customers operate it facing a second direction, which is perpendicular to the first direction; and the third device is installed in such a way that customers operate it facing a third direction, which is opposite to the second direction. A product sales data processing system characterized by the following features.

2. A fourth device that performs the registration process and the settlement process based on customer operations. Equipped with, The circulation area is formed as an area enclosed by the four sides of the first, second, third, and fourth devices, with each of the first, second, third, and fourth devices installed in its respective position. The fourth device is installed in such a orientation that the customer operates the fourth device while facing the fourth direction, which is opposite to the first direction. Product sales data processing system according to feature 1.

3. The second device is This includes cash handling devices that support cash payments and non-cash handling devices that do not support cash payments. A product sales data processing system according to claim 1 or 2.

Images