Store status management device and program

Abstract

To reduce the burden on store staff. [Solution] An in-store status management device capable of monitoring multiple payment devices, wherein the payment devices include a first payment device that settles payments for goods registered by other stationary devices or the device itself, and a second payment device that settles payments for goods registered by other portable devices, and the in-store status management device includes display means for displaying the status of the first payment device and the second payment device.

Description

Technical Field

[0001] The present invention relates to an in-store situation management device and a program.

Background Art

[0002] There are cases where a plurality of services related to the sale of goods coexist. For example, a system that provides a plurality of settlement 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, the burden on the store staff for monitoring when a plurality of services coexist increases.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technology for reducing the burden on store staff.

Means for Solving the Problems

[0006] One aspect of the present invention for solving the above-described problems is an in-store situation management device capable of monitoring a plurality of settlement devices, wherein the settlement devices include a first settlement device that settles for goods registered in an installed other device or the self-device, and a second settlement device that settles for goods registered in a portable other device, and the in-store situation management device is characterized by including display means for displaying the states of the first settlement device and the second settlement device.

Brief Description of the Drawings

[0007] [Figure 1]This is a conceptual diagram of a network used to explain the sales system. [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] This is a sequence diagram illustrating an example of processing between a mobile device and a cloud server. [Figure 15] This is a sequence diagram showing an example of processing by a payment device and a cloud server. [Figure 16] This is an example of the display from the transaction status management device. [Figure 17] This is an example of the display from the transaction status management device. [Figure 18] This is an explanatory diagram describing the display of the transaction status management device. [Figure 19] This is an example of the display from the transaction status management device. [Figure 20] This is an example of the display from the transaction status management device. [Figure 21] This is an example of the display from the transaction status management device. [Figure 22] This is an example of the display from the transaction status management device. [Figure 23] This is an example of the display from the transaction status management device.

Best Mode for Carrying Out the Invention

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

[0009] The store controller 30, the transaction status management device 40, the settlement device 50, the registration settlement device 51, the registration settlement device 52, the registration device 53, and the settlement device 54 are communicably connected via a LAN 19 (which may be wired or wireless). The store controller 30 is communicable with the head office server 10. The sales system 1 can be introduced into various stores (such as supermarkets, convenience stores, drugstores, home centers, home appliance mass retailers, etc.).

[0010] In FIG. 1, the number of each device (terminal) is an illustration. For example, in FIG. 1, "..." is illustrated on the right side of the transaction status management device 40, but the number of the transaction status management device 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 which the customer himself / herself performs product registration and settlement, but uses 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 customers register and pay for products using registration and payment devices 51 and 52, or a service in which store employees register products using registration device 53 and customers pay using 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, 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 payment device 51 is used by store staff or customers. Specifically, the registration and payment device 51 is equipped with scanner units on both sides (store staff side and customer side) and a payment unit on one side (customer side). The registration and payment device 51 has multiple switchable operating modes. The configuration of the registration and payment device 51 will be described later.

[0020] The registration and settlement device 52 is primarily used by customers. The registration and settlement device 52 comprises a scanner unit and a settlement unit and is used for registering and settling payments for goods.

[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] Furthermore, the sales system 1 may be linked with other systems. For example, the transaction status management device 40 may be able to access an attendance server that manages information related to employee (store clerk) attendance (e.g., attendance record information, work schedule information, etc.).

[0024] (Transaction status management device 40) Although not shown in the diagram, the transaction status management device 40 includes a CPU, ROM, RAM, hard disk, display unit, and communication unit. These can communicate with each other via a bus. The transaction status management device 40 may further include a key operation unit consisting of various keys (buttons), or it may be possible to connect a device (keyboard) equipped with a key operation unit. The transaction status management device 40 may also be possible to connect a device (printer) equipped with a printing unit, a device (speaker) equipped with an audio output unit, a device (scanner) equipped with a scanner unit capable of scanning codes attached to employee name tags, etc., and a device (card reader) equipped with a card reader unit capable of reading cards (e.g., employee cards).

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

[0026] 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) may further include a key operation unit. The payment device 50 (and the registered payment device 51, registered payment device 52, registered device 53, and payment device 54) may further include a sensor (such as a motion sensor) to detect the presence of a person.

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

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

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

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

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

[0032] 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 device 53, etc.) and read the information necessary for settlement processing.

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

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

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

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

[0037] 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 also 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 by the way the light-emitting part is illuminated.

[0038] (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. The registration and settlement device 51 (and similarly the registration and settlement devices 52, registration device 53, and settlement device 54) may further include an imaging unit (an imaging unit similar to the imaging unit 116 of the settlement device 50). Furthermore, the registration and settlement device 51 may also be equipped with a signpost (similar to the signpost 117 of the settlement device 50), etc.

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

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

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

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

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

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

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

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

[0047] (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, schedule, reception of an operating mode switching command transmitted from another device, etc.).

[0048] (Face-to-face semi-self mode (face-to-face self mode)) The face-to-face semi-self-service mode (also referred to as face-to-face self-service 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.

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

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

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

[0052] 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).

[0053] 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).

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

[0055] (Registration and settlement device 52) The registration and payment device 52 is a fully self-service registration and payment device. Functionally, the registration and payment device 52 is equivalent to the registration and payment device 51, which is fixed in fully self-service mode. While the registration and payment device 51 is also intended for use by store staff (face-to-face self-service mode, registration-only mode), the registration and payment device 52 is not intended for use by store staff. Therefore, the registration and payment device 52 does not have the store staff-side display unit, key operation unit, store staff-side scanner unit, etc. that the registration and payment device 51 has. Other aspects are the same as the registration and payment device 51, so the appearance and configuration examples of the registration and payment device 52 will not be explained, including in illustrations.

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

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

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

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

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

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

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

[0063] (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 card payment unit (non-cash payment unit) 408, a change dispenser (cash payment unit) 409, a staff-side display unit 410, a printing unit 413, an audio output unit 414, and a communication unit 415. These components can communicate with each other via a bus.

[0064] The CPU 401, ROM 402, RAM 403, hard disk 404, card payment unit 408, change dispenser 409, voice output unit 414, and communication unit 415 of the payment device 54 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.

[0065] 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).

[0066] 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.).

[0067] 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).

[0068] The above describes the cash registers installed in the store (settlement device 50, registration settlement device 51, registration settlement device 52, registration device 53, settlement device 54), but the configuration of each settlement device is just one example. For example, in the above description, settlement device 50 was described as having both a card payment section (non-cash payment section) 108 and a change dispenser (cash payment section) 109, but settlement device 50 may also have a configuration that includes either the card payment section 108 or the change dispenser 109. The same applies to registration settlement devices 51, 52, and 54.

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

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

[0071] 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).

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

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

[0074] 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").

[0075] 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).

[0076] 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)).

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

[0078] 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).

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

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

[0081] 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)).

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

[0083] 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).

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

[0085] 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).

[0086] 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)).

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

[0088] 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).

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

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

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

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

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

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

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

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

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

[0098] (Transaction status management device 40) The transaction status management device 40 displays a management screen for managing (monitoring) the cash registers installed in the store (settlement device 50, registration settlement device 51, registration settlement device 52, registration device 53, settlement device 54) and the mobile terminals (mobile terminal 60, etc.) located within the store.

[0099] In the following description, the payment devices 50, registration payment devices 51, registration payment devices 52, registration devices 53, and payment devices 54 installed in the store will be collectively referred to as the installed cash registers. Furthermore, it will be assumed that there are 15 installed cash registers in the store (numbered 1 to 15 below) and 1 transaction status management device 40. Additionally, it will be assumed that the store contains a mix of personal mobile terminals 60 owned by individual customers and mobile terminals 60 lent by the store (including those fixed to shopping carts).

[0100] The types of equipment for Units 1 through 15 (alternative names in parentheses) are as follows: (1) Units 1 to 3 are payment devices 50 (portable payment machines). Units 1 to 3 are each equipped with a card payment section and a cash payment section. (2) Units 4 to 6 are registered settlement devices 51 (multiple operation mode machines (multiple operation mode registered settlement machines)). Units 4 and 5 are equipped with a card settlement section and a cash settlement section. Unit 6 is equipped with a card settlement section but not a cash settlement section. (3) Machines 7 through 9 are registered payment devices 52 (fully self-service only machines). Machines 7 and 8 are equipped with a card payment section and a cash payment section. Machine 9 is not equipped with a card payment section but is equipped with a cash payment section. (4) Units 10 and 13 are registration devices 53 (semi-self registration machines). (5) Units 11, 12, 14, and 15 are payment machines 54 (semi-self payment machines).

[0101] The information (fixed information) regarding the installed cash registers (units 1 to 15) mentioned above may be stored in a basic device file that is updated when the devices are installed or removed. The basic device file may be stored in a location accessible by the transaction status management device 40 (for example, the memory unit of the transaction status management device 40, or the memory unit of the headquarters server 10). The basic device file may also store images (photographs, illustrations, etc.) of each device. The basic device file may also store characteristics of each device (for example, the color of the casing, the shape of the display screen (landscape / portrait orientation, size)). The basic device file may also store installation information (location, orientation) of each device within the store.

[0102] Furthermore, in the following explanation, it will be assumed that the current operating mode of machine No. 4 is full self-service mode. The current operating modes of machines No. 5 and No. 6 will be face-to-face self-service mode. In addition, it will be assumed that machine No. 1 is currently running low on change (500 yen coins) (near-end change), and machine No. 5 is currently running low on receipt paper (near-end paper).

[0103] The information (fluid information) regarding the installed cash registers (units 1 to 15) described above shall be accessible to devices that require it. For example, if the operating mode of a mode-changeable installed cash register (units 4 to 6) is switched, the cash register may notify the transaction status management device 40 of the change. Also, for example, if a device equipped with a cash settlement unit (units 1 to 5, 7 to 9, 11, 12, 14, and 15) is nearing the end of the change payment, the cash register may notify the transaction status management device 40 of the change payment. The same applies when the paper payment is nearing the end of the transaction. The same also applies to the operating status of each device (in use / standby, user (employee, member)), etc.

[0104] Figures 16 to 23 show examples 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 the cash registers of the settlement device 50) and mobile terminals present in the store (such as the mobile terminals 60).

[0105] Figures 16, 17, 19, 20, and 21 show examples of management screens for managing installed cash registers (sometimes referred to as installed cash register management screens). Figures 22 and 23 show examples of management screens for managing mobile devices (sometimes referred to as mobile device management screens). At the top of the management screen, it displays "Operator Number: 9999 Operator Name: xxxx 2021 / XX / XX 15:30". The Operator Number and Operator Name are the employee number and name of the employee operating the transaction status management device 40 (i.e., the employee displaying the management screen). "2021 / XX / XX 15:30" is the current date and time. The management screen has tabs ("Installed Cash Registers" and "Mobile Devices"). Employees switch between the installed cash register management screen and the mobile device management screen by operating (selecting) the tabs. In other words, the transaction status management device 40 switches between the installed cash register management screen and the mobile device management screen according to the operation of the tabs.

[0106] (Installed POS system management screen) For example, as shown in Figure 16, the installed register management screen has multiple buttons (all button BT401, semi-self-service button BT402, fully self-service button BT403, registration button BT404, payment machine button BT405, portable payment machine button BT406, settings button BT407, layout button BT408). The store clerk operates (selects) these buttons to switch the display content of the installed register management screen. In other words, the transaction status management device 40 switches the display content of the installed register management screen in response to the operation of these buttons.

[0107] The All Button BT401 is a button that displays information for all installed cash registers (cash registers 1 through 15) in the store on the installed cash register management screen. Figures 16 and 17 show the contents of the installed cash register management screen when the All Button BT401 is operated. Figure 16 is page 1, displaying information for each of cash registers 1 through 8. Figure 17 is page 2, displaying information for each of cash registers 9 through 15. The arrow button BT410 is used to switch between page 1 and page 2. In Figures 16 and 17, the thick border around the All Button BT401 indicates that the button (All Button BT401) has been operated.

[0108] Figure 18(A) is a magnified view of the display area (indicated as A in the figure) for Unit 2 shown in Figure 16. Figure 18(B) is a magnified view of the display area (indicated as B in the figure) for Unit 6 shown in Figure 16.

[0109] As shown in Figure 18(A) (and similarly in Figure 18(B)), the display area for each installed cash register includes a device name display area HR420, an operation mode operation area SR430, an operation status display area HR440, a device image display area HR450, and a feature display area HR460.

[0110] (Device name display area HR420) The transaction status management device 40, for example, refers to the device basic file and displays the device name and type of the installed cash register in the device name display area HR420. In the example shown in Figure 18(A), the transaction status management device 40 displays "Unit 2 Portable Recording and Settlement Machine" in the device name display area HR420. In the example shown in Figure 18(B), the transaction status management device 40 displays "Unit 6 Multiple Operation Mode Machine" in the device name display area HR420.

[0111] Furthermore, the transaction status management device 40, for example, refers to the device basic file and displays in the device name display area HR420 whether or not the installed cash register has a card payment section and a cash payment section. In the example shown in Figure 18(A), the transaction status management device 40 displays "Cash: ○" and "Non-cash: ○" in the device name display area HR420. In the example shown in Figure 18(B), the transaction status management device 40 displays "Cash: ×" and "Non-cash: ○" in the device name display area HR420. Note that "○" indicates presence and "×" indicates absence.

[0112] Furthermore, if the installed cash register is one of several cash registers (Nos. 4 to 6) with multiple operating modes, the transaction status management device 40 displays the current operating mode in the device name display area HR420. In the example shown in Figure 18(B), the transaction status management device 40 displays "(Face-to-face)" in the device name display area HR420. "(Face-to-face)" in the device name display area HR420 indicates that the installed cash register is in face-to-face self-service mode, that is, the cashier and the customer face each other across the device, the cashier registers the goods using one side of the registration and settlement device 51 (the cashier's side), and the customer settles the payment using the other side of the registration and settlement device 51 (the customer's side). The transaction status management device 40 may, for example, receive information indicating that the operating mode has switched from an installed cash register with multiple operating modes, and display the current operating mode of the installed cash register in the device name display area HR420.

[0113] (Operating mode, operating area SR430) If the installed cash register is one of several operating modes (machines 4 to 6), the transaction status management device 40 accepts operations related to the operating mode in the operating mode operation area SR430. Specifically, as shown in Figure 18(B), if the installed cash register is one of several operating modes, the current operating mode is displayed in the operating mode operation area SR430, and the scheduled button BT431 and the switching button BT432 are placed there. In the case of an installed cash register that does not have several operating modes (specifically, a device other than a machine with multiple operating modes), the operating mode operation area SR430 is blank, as shown in Figure 18(A).

[0114] The schedule button BT431 is used to check (display) the operating mode switching schedule (switching schedule information) for the installed cash register. The schedule button 431 shown in Figure 18(B) displays "Schedule (Full Self-Service in 50 Minutes)," where "(Full Self-Service in 50 Minutes)" is information based on the switching schedule information for the installed cash register, indicating that the installed cash register is scheduled to switch to full self-service mode in 50 minutes. The remaining time until the mode switch is counted down. In this example, the countdown is displayed as "49 minutes," "48 minutes," etc., every minute that passes. When the remaining time reaches a predetermined time (for example, 5 minutes), the button color may be changed to highlight that there is little time remaining (that the operating mode will switch soon). If there is no scheduled mode switch (or if there is no scheduled mode switch within a predetermined time from now (for example, within 1 hour)), the schedule button 431 simply displays "Schedule," as shown in machines 4 and 5 in Figure 17. In addition, instead of simply displaying "Scheduled," you may indicate that the current operating mode will be maintained by displaying "Scheduled (Maintained)," or you may indicate that there is no scheduled activity by leaving the parentheses blank, such as "Scheduled ( )." In addition, instead of displaying the remaining time until the mode switch, you may also display the mode switch time (in this example, "16:20," which is "50 minutes" after the current time "15:30").

[0115] Switching schedule information is a timetable that includes, for example, time (time), operating mode, and person in charge (setting person) (i.e., it is possible to input, modify, and display these). If the switching schedule information includes switching schedules for multiple installed cash registers, it will also include the installed cash register (machine name), time, operating mode, and person in charge.

[0116] The switching schedule information can be stored in a location accessible to the transaction status management device 40 (for example, the memory unit of the transaction status management device 40, the memory unit of the installed cash register, or the memory unit of the headquarters server 10). When the scheduled button BT431 is operated, the transaction status management device 40 displays a small screen in front of the installed cash register management screen, and displays the currently set switching schedule for the operating mode of the installed cash register on that small screen. If the operating mode switching schedule for the installed cash register is not currently set, the transaction status management device 40 may display "Not set" on the small screen. An OK button may be placed on the small screen, and the transaction status management device 40 may clear the small screen when the OK button is operated. The transaction status management device 40 may also accept an operation to change the switching schedule on the small screen.

[0117] The switch button BT432 is a button for switching the operating mode of the installed cash register (specifically, the registered settlement device 51 which has multiple operating modes). When the switch button BT432 is operated, the transaction status management device 40 displays a small screen in front of the installed cash register management screen and accepts an operation to switch to another operating mode on the small screen (for example, by displaying a button for specifying the destination operating mode). When the small screen accepts an operation to switch to another operating mode (for example, when a button for specifying one operating mode as the destination operating mode is operated), the transaction status management device 40 sends an operating mode switching command to the installed cash register to switch to the operating mode for which the operation was accepted (either directly or via another device such as the store controller 30). The transaction status management device 40 may also send an operating mode switching command that includes the employee number (or a registered name such as a nickname). When the transaction status management device 40 accepts an operation to switch to another operating mode, it clears the small screen. Alternatively, an OK button may be placed on the small screen, and the transaction status management device 40 may clear the small screen when the OK button is pressed.

[0118] A cash register that receives an operating mode switching command may display a small screen that shows a message such as, "You have been instructed to switch the operating mode to XX mode. Do you want to switch to XX mode?" and allows the user to confirm their acceptance or rejection (for example, by placing "Yes" or "No" buttons). If the cash register that receives the operating mode switching command has made an operation to allow the switch (by pressing the "Yes" button), it will switch the operating mode according to the operating mode switching command. If it has made an operation to reject the switch (by pressing the "No" button), it will not switch the operating mode. In other words, while the remote operation mode switching by the transaction status management device 40 for a cash register generally takes precedence over the instructions (operating mode switching command) of the transaction status management device 40, the cashier at the cash register that has received the instruction (the operating mode switching command) may choose not to follow the instruction depending on the situation at that cash register.

[0119] Furthermore, if a cash register that has received an operating mode switching command does not receive a confirmation operation within a certain period of time after the small screen display begins, it may switch the operating mode according to the operating mode switching command. For example, if a registered payment device 51 whose current operating mode is full self-service mode (the same applies if another device (e.g., payment device 54) is capable of changing modes and is in a full self-service mode) receives an operating mode switching command, it will switch to another operating mode after a certain period of time has elapsed (however, if a transaction was in progress when the certain period of time elapsed, it will switch after the transaction has finished) without waiting for a confirmation operation from a store employee. Alternatively, if a registered payment device 51 whose current operating mode is full self-service mode (the same applies if another device is capable of changing modes and is in a full self-service mode) receives an operating mode switching command, it may be configured to switch to another operating mode immediately without displaying the small screen (however, if a transaction was in progress when the certain period of time elapsed, it will switch after the transaction has finished).

[0120] Furthermore, a cash register that receives a command to switch operating modes may, regardless of its current operating mode (whether or not there is a cashier present), switch its operating mode according to the status of the cash register (for example, after a transaction is completed if a transaction was in progress), without displaying a small screen.

[0121] When a cash register switches its operating mode in accordance with an operating mode switching command (or when it switches due to other conditions such as the passage of time), it notifies the transaction status management device 40 of this fact (either directly or via another device such as the store controller 30). In addition to the transaction status management device 40, other devices (other store controllers 30) may also be notified. Furthermore, in addition to when the operating mode is switched, the cash register may also notify the transaction status management device 40 of its current operating mode at appropriate times (for example, after a transaction is completed). Similarly, if the cash register does not switch its operating mode, it may also notify the transaction status management device 40 of this fact. In addition to or instead of notification from the cash register, the management side (transaction status management device 40, etc.) may inquire about and confirm the operating mode of the cash register at appropriate times (for example, every 10 seconds) (in other words, the cash register may notify the current operating mode in response to the inquiry).

[0122] The transaction status management device 40 may refer to the switching schedule information for the operating mode of the installed cash register, and if the operating mode of the installed cash register is scheduled to switch soon (for example, in 10 minutes), it may display a message to that effect on the operating mode operation area SR430. Furthermore, if the mode switch has not been performed according to the switching schedule information (for example, the operating mode is not generally switched when a transaction is ongoing), the transaction status management device 40 may display a message to that effect on the operating mode operation area SR430.

[0123] It has been explained that the transaction status management device 40 displays a small screen when the switch button BT432 is operated and accepts a switch operation to another operating mode on that small screen. However, the control may be made different depending on whether or not a switch schedule is set for the installed cash register. For example, if no switch schedule is set, the transaction status management device 40 may allow all operating modes to be specified as the switch destination after the switch button BT432 is pressed (it may display a small screen that allows all operating modes to be specified as the switch destination based on the press of the switch button BT432). On the other hand, if a switch schedule is set, the transaction status management device 40 may allow only the operating modes set (planned) in the switch schedule to be specified as the switch destination after the switch button BT432 is pressed (it may display a small screen that allows only the operating modes set (planned) in the switch schedule to be specified as the switch destination based on the press of the switch button BT432). In other words, if a switch schedule is set, the switchable operating modes (selection of operating modes) may be restricted.

[0124] As described above, the scheduled operation mode switch (switching schedule) is confirmed using the scheduled button BT431, and the actual switching of the operation mode is performed by operating the switch button BT432. Therefore, even when the scheduled time arrives, the operation mode will not switch unless the switch button BT432 is operated. In relation to the above, when the scheduled time arrives (when the remaining time becomes zero) or when the scheduled time has elapsed, the transaction status management device 40 may highlight this fact on the scheduled button BT431 (for example, "Scheduled (Full Self Change Time)", "Scheduled (Full Self Change Time Elapsed)") and also display a message (for example, "The scheduled time for switching has arrived. Please be careful", "The scheduled time for switching has elapsed. Please be careful") in a location other than the scheduled button BT431 (for example, the top of the screen, a small screen). Note that "Scheduled (Full Self Change Time Elapsed)" and "The scheduled time for switching has elapsed. Please be careful" may also include the elapsed time, for example, "Scheduled (Full Self Change Time 10 Minutes Elapsed)" and "The scheduled time for switching has elapsed. Please be careful". The "10 minutes" may be displayed as a count-up.

[0125] In the above description, the operating mode does not automatically switch (unless the switching button BT432 is operated) even when the scheduled time in the switching schedule information arrives. However, the operating mode may be switched automatically based on the switching schedule information (without operating the switching button BT432). For example, the transaction status management device 40 may send an operating mode switching command to a mobile terminal 60 based on the switching schedule information of the mobile terminal 60 without the need for an employee to operate the terminal. When the transaction status management device 40 sends an operating mode switching command without the need for an employee to operate the terminal, it may send an operating mode switching command that includes information indicating that it is an automatic transmission. The transaction status management device 40 may display a small screen to confirm whether the command can be sent (OK / NG) before sending the operating mode switching command, and may send the operating mode switching command after the employee has performed an OK operation (or after a certain period of time has elapsed if no confirmation operation is performed within a certain period of time after the small screen is displayed). The transaction status management device 40 may send an operating mode switching command that includes information indicating that the employee has performed an OK operation (or that no confirmation operation was performed).

[0126] In a configuration where the operating mode is automatically switched based on switching schedule information, the switching button BT432 may or may not be provided. If the switching button BT432 is not provided, the operating mode is simply switched remotely according to the switching schedule information. If the switching button BT432 is provided, the operating mode is switched remotely according to the operation of the switching button BT432 in addition to the switching schedule information. Furthermore, the switching button BT432 may be displayed as operable based on predetermined conditions. For example, the switching button BT432 may be displayed as operable only for a predetermined period (e.g., 10 minutes) after the automatic switching of the operating mode (it may be hidden or displayed as inoperable outside of the above predetermined period).

[0127] Furthermore, depending on whether the operation mode switching command transmitted by the transaction status management device 40 was sent by operating the switching button BT432 or was sent automatically, the installed cash register that received the operation mode switching command may decide whether or not to display the small screen (for example, if it was sent by operating the switching button BT432, the small screen may not be displayed, but if it was sent automatically, the small screen may be displayed. The opposite may also be true). Also, depending on whether or not the operation mode switching command automatically transmitted by the transaction status management device 40 was sent after a confirmation operation (OK operation) by a store clerk, the installed cash register that received the operation mode switching command may decide whether or not to display the small screen (for example, if it was sent after a confirmation operation, the small screen may not be displayed, but if it was not sent after a confirmation operation, the small screen may be displayed. The opposite may also be true).

[0128] (Operating status display area HR440) The transaction status management device 40 displays the operating status of the installed cash register in the operating status display area HR440. In the example shown in Figure 18(A), the transaction status management device 40 displays "Operating status: In use (Settling)" as the operating status of machine No. 2 in the operating status display area HR440. In the example shown in Figure 18(B), the transaction status management device 40 displays "Operating status: In use (Settling)" as the operating status of machine No. 6 in the operating status display area HR440. The transaction status management device 40 may, for example, receive information indicating the progress of processing from the installed cash register and display the operating status of the installed cash register in the device name display area HR420.

[0129] Furthermore, the transaction status management device 40 displays information about the operator of the installed cash register in the operating status display area HR440. In the example shown in Figure 18(A), the transaction status management device 40 displays "Clerk: - Customer: C2" in the operating status display area HR440 as the operator of machine No. 2. In the example shown in Figure 18(B), the transaction status management device 40 displays "Clerk: T2 (18:20) Customer: C25" in the operating status display area HR440 as the operator of machine No. 6.

[0130] In Figure 18(A), the "Staff:-" in the operation status display area HR440 indicates that the cash register (unit 2) is not being operated by a staff member. Since unit 2 (settlement device 50) is primarily operated by customers, it will basically display "Staff:-". In Figure 18(A), the "Customer:C2" in the operation status display area HR440 indicates that the customer with membership number (customer identification information) "C2" is operating the cash register (unit 2). For example, the transaction status management device 40 may obtain the membership number from the cash register and display it in the operation status display area HR440. The membership number of the customer using the settlement device 50 (units 1 to 3) is also displayed on the product list screen of the settlement device 50 (see Figure 13) and on the service A start screen of the mobile terminal 60 (Figure 10(A), etc.).

[0131] The transaction status management device 40 may display the customer (member) name (or registered name) in place of or in addition to the member number. Furthermore, the transaction status management device 40 may display transaction identification information (cart identification information), which is generated on the cloud server 20 at the start of a purchase and linked to the transaction information (product information) registered thereafter, in place of or in addition to the member information described above (member number, member name, etc.). If the transaction status management device 40 cannot obtain any member information, it will display the transaction identification information (cart identification information). The same applies to the display of the member number on the mobile terminal management screen (Figure 22).

[0132] In Figure 18(B), "Employee: T2 (18:20)" indicates that employee number (customer identification information) "T2" is operating (or logged into) the installed cash register (machine 6), and that the employee's scheduled departure time is "18:20". The transaction status management device 40, for example, obtains the employee number from the installed cash register and displays it in the operation status display area HR440. The transaction status management device 40 also obtains the employee's scheduled attendance time from the attendance server and displays it in the operation status display area HR440. The employee name (or registered name) may be displayed in place of or in addition to the employee number.

[0133] Furthermore, the system may notify the employee when their scheduled departure time has arrived, when their scheduled departure time is approaching, or when their scheduled departure time has already passed. For example, a button (departure time confirmation button) may be placed in the operation status display area HR440, and when the departure time confirmation button is pressed, the transaction status management device 40 may transmit departure time promotion information to the register in question (either directly or via another device such as the store controller 30) to notify the employee when their scheduled departure time has arrived. For example, in the example of machine 6 shown in Figure 18(B), when an employee (e.g., a manager) using the transaction status management device 40 operates the departure time confirmation button, the transaction status management device 40 transmits departure time promotion information to machine 6 directed at employee "T2". Furthermore, machine 6, upon receiving the departure time promotion information, may display a message corresponding to the time of reception. For example, if the message is received at the scheduled end time (18:20), it could display "It is now the scheduled end time (18:20)." If it is received before the scheduled end time (18:10), it could display "It is 10 minutes before the scheduled end time (18:20)." If it is received after the scheduled end time (18:30), it could display "It is now 10 minutes past the scheduled end time (18:20)." If the message is received before the scheduled end time, it may wait until the scheduled end time and then display "It is now the scheduled end time."

[0134] In the example of machine No. 5 shown in Figure 16, as indicated by "Employee: T1 (15:00)", the scheduled departure time for employee number (customer identification information) "T1" is "15:00". Also, as shown at the top of the management screen, the current time is "15:30". Therefore, machine No. 5 (employee T1) is notified, as described above, that the scheduled departure time has already passed. The notification that the scheduled departure time has already passed may be more emphatic than the notification that the employee's scheduled departure time has arrived or that the scheduled departure time is approaching.

[0135] The "Customer: C25" in the operation status display area HR440 shown in Figure 18(B) indicates that the customer with membership number "C25" is operating the installed cash register (unit 2). For customers using the registration and settlement devices 51 (units 4 to 6) (the same applies to registration and settlement devices 52 (units 7 to 9), etc.), the membership number can be obtained, for example, from the customer's medium (e.g., membership card). If the membership number has not been obtained, the transaction status management device 40 will display "Customer: Unknown," for example, as shown in unit 5 in Figure 16 and unit 11 in Figure 17.

[0136] Furthermore, a details button BT441 is located in the operation status display area HR440. The details button BT441 is a button for checking (displaying) detailed information such as the operation status and operator of the installed cash register. When the details button BT441 is operated, the transaction status management device 40 displays, for example, details related to the transaction (if in use, the presence and content (type) of held items (described later), total amount, etc.), information about the store clerk (if the store clerk is operating, the clerk's arrival time on that day, overtime status, etc.), and information about the customer (if the customer is operating and has obtained a membership number, the customer's purchase history, presence and number of past held items (described later), etc.). In addition, when the details button BT441 is operated, the transaction status management device 40 may also display an image captured by the imaging unit of the installed cash register.

[0137] (Device image display area HR450) The transaction status management device 40, for example, refers to the device's basic file and displays an image (photograph, illustration, etc.) of the installed cash register in the device image display area HR450. In the example shown in Figure 18(A), the transaction status management device 40 displays the image GA451 of machine number 2 in the device image display area HR450. In the example shown in Figure 18(B), the transaction status management device 40 displays the image GA451 of machine number 6 in the device image display area HR450.

[0138] Furthermore, an enlargement button BT451 is located in the device image display area HR450. The enlargement button BT451 is a button that accepts operation to enlarge the image GA451. When the enlargement button BT451 is operated, the transaction status management device 40 displays a small screen, for example, in front of the installed register management screen, and displays a larger image of the installed register GA451 on the small screen. Alternatively, an OK button may be placed on the small screen, and the transaction status management device 40 may clear the small screen when the OK button is operated.

[0139] Furthermore, the transaction status management device 40 displays information regarding staff calls, change near-ends, paper near-ends, etc., at the installed cash register in the device image display area HR450. In the example shown in Figure 18(A), the transaction status management device 40 displays an icon ICN453 indicating that there is a staff call at machine No. 2, and an icon ICN454 indicating that machine No. 2 is near-end (500 yen coins) at change. The transaction status management device 40 may, for example, receive information such as staff calls from the installed cash register and display icons in the device image display area HR450. In this example, staff calls, change near-ends, paper near-ends, etc., are reported in the device image display area HR450, but they may also be reported in other areas.

[0140] (Feature display area HR460) The transaction status management device 40, for example, refers to the device's basic file and displays the characteristics of the installed cash register in the characteristic display area HR460. In the example shown in Figure 18(A), the transaction status management device 40 displays the characteristics of machine No. 2 (casing (color), casing (height), screen (portrait / landscape), screen (size), presence or absence of a sign pole) in the characteristic display area HR460. In the example shown in Figure 18(B), the transaction status management device 40 displays the characteristics of machine No. 6 in the characteristic display area HR460.

[0141] Note that machines 4 through 6 (registered payment devices 51) are equipped with two display units (customer-side display unit 205 and employee-side display unit 210), but in this example, the information from the customer-side display unit 205 (screen (portrait / landscape orientation), screen (size)) is displayed in the feature display area HR460. Alternatively, the information from the employee-side display unit 210 may be displayed in the feature display area HR460 in lieu of or in addition to the information from the customer-side display unit 205. The same applies to machines 7 through 9 (registered payment devices 52), 11, 12, 14, and 15 (payment devices 54).

[0142] Furthermore, units 10 and 13 (registration device 53) are equipped with two display units (customer-side display unit 305 and employee-side display unit 310), but in this example, the information from the employee-side display unit 310 is displayed in the feature display area HR460. Alternatively, the information from the customer-side display unit 305 may be displayed in the feature display area HR460 in lieu of or in addition to the information from the employee-side display unit 310.

[0143] Furthermore, a location button BT461 is located in the device image display area HR450. The location button BT461 is used to display (confirm) the installation location of the cash register within the store. When the location button BT461 is pressed, the transaction status management device 40 displays a layout screen (described later) and indicates which cash register is being used at a glance (details will be described later).

[0144] The semi-self-service button BT402 shown in Figure 16, etc., is a button used to display information on the installed register management screen for installed registers (numbers 5, 6, 11, 12, 14, and 15) in a store where a store employee registers the products and the customer pays. Figure 19 shows the display content on the installed register management screen when the semi-self-service button BT402 is operated. In Figure 19, the thick border around the semi-self-service button BT402 indicates that the button (semi-self-service button BT402) has been operated.

[0145] In the above, the machines designated as semi-self-service only (machines 11, 12, 14, and 15) are included in the display targets when the semi-self-service button BT402 is operated, but they may be excluded from the display targets when the semi-self-service button BT402 is operated. In other words, the display targets when the semi-self-service button BT402 is operated may be limited to machines with multiple operation modes in semi-self-service mode (machines 5 and 6).

[0146] The Full Self-Service Button BT403 is a button used to display information on the installed register management screen for installed registers (registers 1-4 and 7-9) within a store where customers register and pay for their items. Figure 20 shows the display content on the installed register management screen when the Full Self-Service Button BT403 is operated. In Figure 20, the thick border around the Full Self-Service Button BT403 indicates that the button (Full Self-Service Button BT403) has been operated.

[0147] In the above, portable payment machines (machines 1 to 3) are included in the display target when the full self-service button BT403 is operated. However, although portable payment machines are installed cash registers used for customers to register and pay for their products, product registration is done using the portable terminal 60 rather than the installed cash register itself. Therefore, they may be excluded from the display target when the full self-service button BT403 is operated. Also, in the above, dedicated full self-service machines (machines 7 to 9) are included in the display target when the full self-service button BT403 is operated. However, they may be excluded from the display target when the full self-service button BT403 is operated. In other words, the display target when the full self-service machine button BT403 is operated may be any of the following: [Multiple operation mode machines in full self-service mode (machine No. 4)], [Multiple operation mode machines in full self-service mode (machine No. 4) + full self-service only machines (machines No. 7 to 9)], or [Multiple operation mode machines in full self-service mode (machine No. 4) + portable payment machines (machines No. 1 to 3)].

[0148] The registration button BT404 is a button that displays information on the installed register management screen for the installed registers (registers 4-10 and 13) that perform product registration within the store. The content displayed on the installed register management screen when the registration button BT404 is operated is not shown in the diagram. Note that the verification devices 50 (registers 1-3) and settlement devices 54 (registers 11, 12, 14, and 15) are also equipped with scanner units and can register products, but they are not normally used for product registration and are therefore excluded from the display when the registration button BT404 is operated.

[0149] The payment machine button BT405 is a button that displays information on the installed cash register management screen for the cash registers that perform payment processing (cash registers 1-9, 11, 12, 14, and 15) installed in the store. The content displayed on the installed cash register management screen when the payment machine button BT405 is operated is not shown in the diagram.

[0150] The portable payment button BT406 is a button used to display information on the installed cash register management screen for installed cash registers (cash registers 1 to 3) that process payments for items registered using the portable terminal 60 within the store. The content displayed on the installed cash register management screen when the portable payment button BT406 is operated is not shown in the diagram.

[0151] The setting button BT407 is a button for arbitrarily setting which installed cash registers are to be displayed on the installed cash register management screen. When the setting button BT407 is operated, the transaction status management device 40 displays a small screen in front of the installed cash register management screen, and on this small screen, the user enters (registers) a button name and selects the installed cash registers to be displayed when the button is operated (for example, by selecting with checkboxes). For example, if the button name is entered as "Distant Cash Register", and cash registers 1, 7-9, 11, and 12 are selected, and the setting completion button placed on the small screen is operated, the "Distant Cash Register" button, which displays the selected installed cash registers (1, 7-9, 11, and 12), will be placed on the installed cash register management screen. The transaction status management device 40 will then clear the small screen when the setting completion button or the like is operated. In addition to the above, it is also a good idea to set and place buttons that target the cash registers located in accounting area A (described later) (the same applies to cash registers located in accounting area C (described later) and cash registers located in accounting area C (described later)). Furthermore, it is possible to enable operations to change the display target of each button or to hide the buttons themselves by operating the setting button BT407 (for example, on the small screen described above).

[0152] The layout button BT408 is used to display information about the installation location of cash registers within a store on the cash register management screen. Figure 21 shows the display content of the cash register management screen (sometimes referred to as the layout screen) when the layout button BT408 is operated. In Figure 21, the thick border around the layout button BT408 indicates that the button (layout button BT408) has been operated.

[0153] In the installed register management screen shown in Figure 21, the main display area (area labeled M in the figure) displays icons corresponding to each installed register in the store, positioned according to their respective installation locations within the store. Icons with thick borders indicate that the installed register is in use. Icons with thin borders indicate that the installed register is in standby mode. Icons with diagonal lines correspond to the transaction status management device 40.

[0154] The dashed line on the icon indicates the side on which the customer stands at the installed cash register (the cash register corresponding to the icon). For example, the icon corresponding to machine 1 in the upper right of the drawing has a dashed line on the left, indicating that the customer stands on the left side at machine 1 (with their back to machine 9). Also, for example, the icon corresponding to machine 5 displayed above the transaction status management device 40 has a dashed line on the top, indicating that the customer stands on the top side at machine 5 (with their back to machine 8). Also, for example, the icon corresponding to machine 11 in the lower left of the drawing has a dashed line on the bottom, indicating that the customer stands on the bottom side at machine 11 (facing machine 10). Alternatively or in addition to the above, a mark indicating that it is the side on which the customer stands (for example, an image with the word "customer" inside a circle) may be displayed on the side on which the customer stands. The display of this mark may vary depending on whether or not there is actually a customer. The mark may be displayed differently depending on whether a customer is present or not (determined, for example, by a motion sensor), and for customer-operated cash registers, the mark may be displayed differently depending on whether a customer is operating it or not. Furthermore, the mark may not indicate the customer's standing position in each device, but simply indicate whether a customer is present or not, or whether a customer is operating it or not.

[0155] The area where machines 1 through 3 are installed (area labeled A in the diagram) is a checkout area (sometimes referred to as Checkout Area A) that supports full self-service, where customers register items using a mobile terminal 60 and pay at the installed register. The area where machines 4 through 9 are installed (area labeled B in the diagram) is a checkout area (sometimes referred to as Checkout Area B) that supports, or is capable of supporting (machines 4 through 6 can support this if their operating mode is set to full self-service mode), where customers register items and pay at the installed register. The area where machines 10 through 15 are installed (area labeled C in the diagram) is a checkout area (sometimes referred to as Checkout Area C) that supports semi-self-service, where a store employee registers the items and the customer pays.

[0156] The main display area also shows information such as staff call notifications, change near-end notifications, and paper near-end notifications. In this example, this information is displayed in the lower left of the main display area, but it could also be displayed associated with the icons of the installed cash registers.

[0157] Furthermore, when the installed register management screen is displaying information about installed registers (e.g., Figure 16), if the position button BT461 for a display area related to a particular installed register is operated, the transaction status management device 40 will display the installed register management screen (layout screen) in the same way as when the layout button BT408 is operated, and will display the layout screen in a way that makes it immediately clear which installed register it is. For example, if the position button BT461 for machine No. 2 shown in Figure 16 (Figure 18(A)) is operated, the transaction status management device 40 will display the layout screen and flash the icon corresponding to machine No. 2 within the layout screen. Note that flashing is just one example; for example, the icon corresponding to machine No. 2 may be displayed in a different color from the other icons, or a mark may be added to the icon corresponding to machine No. 2.

[0158] (Mobile device management screen) For example, as shown in Figure 22, the mobile terminal management screen is provided with a total number display area HR470, an abnormal number display area HR472, a normal number display area HR474, a main display area HR480, and a detailed information display area HR481. The mobile terminal management screen also has a total number selection button BT471, an abnormal number selection button BT473, and a normal number selection button BT475. 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 of each mobile terminal 60) and information stored in the headquarters server 10 (customer master, etc.).

[0159] The transaction status management device 40 displays the number of mobile terminals 60 currently in a transaction in the total display area HR470. Mobile terminals 60 currently in a transaction are those that have started registering goods but have not yet completed settlement. The transaction status management device 40 displays the number of mobile terminals 60 currently in a transaction whose transaction is an abnormal transaction in the abnormal number display area HR472. An abnormal transaction is, for example, a transaction that includes held goods (described later) and for which the subsequent settlement process cannot be completed normally without confirmation by a store employee. The transaction status management device 40 displays the number of mobile terminals 60 currently in a transaction whose transaction is a normal transaction in the normal number display area HR474. A normal transaction is, for example, a transaction that does not include held goods and for which the subsequent settlement process can be completed normally even without confirmation by a store employee.

[0160] A held item is an item whose settlement process is temporarily suspended. Examples of held items include unscanned items whose scanning has not been completed, non-file items that were scanned but whose product code is not registered in the product master and therefore price and other information could not be obtained, age-recognized items such as alcohol, pharmaceuticals that require explanation from a pharmacist, and items with security tags.

[0161] The main display area HR480 is the area that displays information about the mobile terminals 60 that are currently trading. The All Selection button BT471 is a button that displays information about all mobile terminals 60 that are currently trading in the main display area HR480. The Abnormal Number Selection button BT473 is a button that displays information about the mobile terminals 60 whose transactions are abnormal in the main display area HR480. The Normal Number Selection button BT475 is a button that displays information about the mobile terminals 60 whose transactions are normal in the main display area HR480.

[0162] In the example shown in Figure 22, the abnormal number selection button BT473 is operated, and information regarding the mobile terminal 60 whose transaction is an abnormal transaction is displayed in a list in the main display area HR480. Specifically, information regarding each of the five corresponding mobile terminals 60 (indicated by symbols a to e in the figure) is displayed in each of the display areas "1" to "5". The thick border around the abnormal number selection button BT473 indicates that the button has been operated. If there are many mobile terminals 60 to display in the main display area HR480, each one may be displayed in a smaller size, or they may be displayed on multiple pages.

[0163] In Figure 22, display area "1" contains information (code a) about the first mobile terminal 60 (the mobile terminal 60 used by member number "C40"), as well as the unscanned product button BT491. The unscanned product button BT491 is displayed (placed) when the pending items include unscanned products. Display area "2" contains information (code b) about the second mobile terminal 60 (the mobile terminal 60 used by member number "C20"), as well as the unscanned product button BT491 and the non-filed product button BT492. The non-filed product button BT492 is displayed when the pending items include non-filed products. Display area "3" contains information (code c) about the third mobile terminal 60 (the mobile terminal 60 used by member number "C1"), as well as the age verification product button BT493. The age verification product button BT493 is displayed when the pending items include age verification products. Display area "4" contains information (code d) regarding the fourth mobile terminal 60 (the mobile terminal 60 used by member number "C5"), as well as the pharmaceutical button BT494 and the anti-theft product button BT495. The pharmaceutical button BT494 is displayed when the held product includes pharmaceuticals that require explanation from a pharmacist or other professional. The anti-theft product button BT495 is displayed when the held product includes anti-theft tag products. Display area "5" contains information (code e) regarding the fifth mobile terminal 60 (the mobile terminal 60 used by member number "C18"), as well as the NON-File product button BT492.

[0164] Note that "Customer terminal" in display areas "1" to "3" and "5" indicates that it is owned by an individual (or corporation). "Store terminal" in display area "4" indicates that it is lent by the store. Alternatively, by storing information that identifies the mobile terminal 60 lent by the store (for example, a subscriber-specific ID or MAC address), it may be possible to distinguish whether the mobile terminal 60 used by each member is a "store terminal" or not (i.e., whether it is a "customer terminal" or a "store terminal").

[0165] When the unscanned product button BT491 is pressed, the transaction status management device 40 displays, for example, the image captured when reading (or attempting to read) the barcode attached to the product on a small screen. For example, the mobile terminal 60 stores the image captured when reading the barcode (see Figure 10(C)) along with information indicating whether the reading was successful or unsuccessful. When the unscanned product button BT491 is pressed, the transaction status management device 40 displays the stored image along with information indicating that the reading failed on the small screen. If there are multiple unscanned products, the transaction status management device 40 displays the image of each of them. The mobile terminal 60 may also transmit the above-mentioned images to the cloud server 20, and the transaction status management device 40 may retrieve the above-mentioned images from the cloud server 20.

[0166] When the NON-file product button BT492 is operated, the transaction status management device 40 displays the product code of the product, for example, on a small screen. If there are multiple NON-file products, the transaction status management device 40 displays the product code of each product. For example, the mobile terminal 60 stores the scanned product code along with information indicating that it is a NON-file product. When the NON-file product button BT492 is operated, the transaction status management device 40 displays the stored product code along with information indicating that it is a NON-file product on the small screen. If there are multiple NON-file products, the transaction status management device 40 displays the product code of each product. The mobile terminal 60 may also transmit the above product code, etc., to the cloud server 20, and the transaction status management device 40 may retrieve the above product code from the cloud server 20. The transaction status management device 40 may also display, in lieu of or in addition to the product code, the captured image when reading the barcode (when attempting to read it, or when it has been read).

[0167] When the age verification product button BT493 is operated, the transaction status management device 40 displays the product name, etc., of the product in question, for example, on a small screen. If there are multiple age verification products, the transaction status management device 40 displays the product name, etc., of each product. The transaction status management device 40 may also obtain the product name, etc., from the cloud server 20. The same applies when the age verification product button BT493 is operated, or when the anti-theft product button BT495 is operated.

[0168] Furthermore, if a reserved item (such as an age-verification item like an alcohol product) is registered on the mobile terminal 60, the transaction status management device 40 will notify the mobile terminal 60 that there is a reserved item among the items registered on the mobile terminal 60 (mobile terminal management screen (Figure 22)). Also, as described above (see the explanation of the details button BT441 located in the operation status display area HR440 of the installed register management screen), after the details button BT441 is operated, the transaction status management device 40 will notify the installed register of the presence and content (type) of the reserved item (described later) (installed register management screen (Figure 16, etc.)). In other words, for example, if an age-verification item like an alcohol product is registered on the mobile terminal 60, the transaction status management device 40 will notify the mobile terminal management screen that an age-verification item has been registered on the mobile terminal 60 during product registration (before settlement), and after product registration... (After the settlement process is complete) the installed register management screen will notify that an age-verified product has been registered on the mobile terminal 60 (the mobile terminal 60 that read the settlement 2D code 605). In other words, if there are any reserved items among the products registered on the mobile terminal 60, the store clerk can confirm this on both the mobile terminal management screen (Figure 22) and the installed register management screen (Figure 16, etc.) (both during and after product registration). Note that all installed registers, including the portable payment machines (units 1-3), are capable of notifying that there are reserved items. Therefore, for example, if there are reserved items among the products registered on the portable payment machines (units 1-3) as well as on the installed registers designed for self-registration (units 4, 7-9, etc.), the transaction status management device 40 can notify the installed register management screen that there are reserved items on that register.

[0169] Although it was explained that the installed register management screen displays information about held items after the operation of the details button BT441, it is also possible to display information about held items in the same way as the mobile terminal management screen. In other words, instead of displaying information about held items after the operation of a button on the installed register management screen, it is also possible to display information about held items directly on the installed register management screen (not after the operation of a button). For example, if an alcohol product is registered at a certain installed register (e.g., machine No. 7 (full self-service only machine), machine No. 4 (multiple operation mode machine with full self-service mode)), this fact is notified (sent) to the transaction status management device 40, and the transaction status management device 40 may display the age verification product button BT493 for that installed register on the installed register management screen (e.g., displayed in the operation status display area HR440, displayed in the device image display area HR450). When a button related to held items displayed on the installed register management screen (such as the age verification product button BT493) is operated, the transaction status management device 40 may operate in the same way as when a button related to held items displayed on the mobile terminal management screen is operated (display a small screen).

[0170] If a store employee operating the transaction status management device 40 can visually confirm that a customer who has registered an alcohol product is of legal age, the transaction status management device 40 will operate to indicate that the sale of the alcohol product has been approved (confirmed) (this operation changes the status to "store employee approved"). This allows the operation (processing) at a non-store employee-operated cash register (such as machine 4, 7-9, etc.) to continue (proceed) even if a product requiring store employee confirmation is registered, without the store employee having to go to that cash register. Alternatively, a tab such as "Confirmation" may be provided for the registration of products requiring store employee confirmation, and the confirmation information may be displayed in a list on that tab. If the store employee operating the transaction status management device 40 cannot visually confirm the customer who has registered an alcohol product, or if they can see the customer but determine that close-up confirmation is required, the store employee will go to the relevant cash register and deal with the matter directly (if approving, the store employee will have the scanner unit of the cash register read the store employee code and then perform the prescribed operation to change the status to "store employee approved"). Furthermore, the transaction status management device 40 displays images captured by cameras installed at each cash register (or cameras installed in various locations within the store), and store employees may, in lieu of or in addition to visual inspection, determine whether or not the customer is of saleable age based on these captured images.

[0171] The detailed information display area HR481 is an area that displays information (such as purchase history) about a customer using a mobile terminal 60 whose information is displayed in the main display area HR480. The purchase history of each customer may be stored in, for example, the headquarters server 10. For example, when the display area "4" (excluding the pharmaceutical button BT494 and the security product button BT495) in the main display area HR480 is operated (touched), the transaction status management device 40 displays information about the customer with membership number "C5" who is using the mobile terminal 60 in display area "4" in the detailed information display area HR481, as shown in Figure 22. The thick border around display area "4" indicates that the mobile terminal 60 has been selected.

[0172] (Control based on the presence or absence of customers) (1) The transaction status management device 40 recognizes that a transaction for service A has been initiated. For example, the cloud server 20 generates transaction information (cart information) for a transaction made by the mobile terminal 60 based on information (service commencement notification) received from the mobile terminal 60 based on a predetermined operation on the mobile terminal 60. When the cloud server 20 generates transaction information, it sends a transaction commencement notification (or a transaction commencement notification including the member number of the mobile terminal 60) that includes transaction identification information (cart identification information) that identifies the transaction to the transaction status management device 40. The transaction commencement notification may be sent from the cloud server 20 to the transaction status management device 40 via the headquarters server 10, or it may be sent from the cloud server 20 to the transaction status management device 40 without going through the headquarters server 10. This allows the transaction status management device 40 to immediately recognize that a transaction for service A has been initiated (that the user of the mobile terminal 60 has entered the store). Alternatively, instead of the cloud server 20 sending a transaction start notification to the transaction status management device 40, the transaction status management device 40 may access the cloud server 20 (either via the headquarters server 10 or without going through the headquarters server 10) to confirm whether or not a transaction has started.

[0173] (2) The transaction status management device 40 recognizes that a transaction for Service A has been completed (that settlement has been completed). For example, when the settlement of a transaction is completed, the cloud server 20 stores the settlement information (total amount, etc.) in the transaction information for that transaction and sends a transaction completion notification (settlement completion notification) containing transaction identification information (cart identification information) that identifies the transaction to the transaction status management device 40. The transaction completion notification may be sent from the cloud server 20 to the transaction status management device 40 via the headquarters server 10, or it may be sent from the cloud server 20 to the transaction status management device 40 without going through the headquarters server 10. This allows the transaction status management device 40 to immediately recognize that a transaction for Service A has been completed (that settlement has been completed by the user of the mobile terminal 60). If the transaction information has a transaction completion time (settlement completion time) as an item, the cloud server 20 may store the current time in the transaction completion time in the transaction information for a transaction when the settlement of that transaction is completed. Furthermore, if the transaction information has a status as an item, the cloud server 20 may store "Transaction Completed (Settlement Completed)" in the status of the transaction information when the settlement of a transaction is completed. Alternatively, instead of the cloud server 20 sending a transaction completion notification to the transaction status management device 40, the transaction status management device 40 may access the cloud server 20 (either via the headquarters server 10 or without going through the headquarters server 10) to check whether the transaction has been completed or not. For example, the transaction status management device 40 may determine that the transaction is complete if settlement information (settlement amount, etc.) or the "Transaction Completed" status is stored in the transaction information, and determine that the transaction is not complete if settlement information (settlement amount, etc.) or the "Transaction Completed" status is not stored in the transaction information.

[0174] Customers of Service A (users of mobile terminal 60, especially beginners) require more attentive support than customers of other services. According to (1) and (2) above, the transaction status management device 40 can immediately ascertain and notify (display, voice output) when a transaction for Service A has started or has been completed. Furthermore, according to (1) and (2) above, the transaction status management device 40 can accurately ascertain and notify (display, voice output) when there are users of Service A who have not yet settled their accounts in the store, and the number of users of Service A who have not yet settled their accounts in the store.

[0175] If, despite the cloud server 20 generating transaction information for a transaction made by the mobile terminal 60 based on a predetermined operation on the mobile terminal 60, none of the devices used for settlement in Service A (installed cash registers for settling transactions made by the mobile terminal 60; portable payment machines) are activated, the customer will not be able to settle their payment after registering their goods. Therefore, when the cloud server 20 generates transaction information, the transaction status management device 40 may check the activation status of the portable payment machines and issue a warning (display, audio output, etc.) if none are activated. In addition, each installed cash register, including the portable payment machines, may notify the transaction status management device 40 of the change in status when it changes from a non-activated state to an activated state, or from an activated state to a non-activated state. The transaction status management device 40 may then store the activation status of the portable payment machines, or may inquire about the activation status of the portable payment machines as needed (e.g., when the cloud server 20 generates transaction information). In addition, the confirmation leading to the above warning may be limited to the generation of specific transaction information. For example, if the store's business hours are from 10:00 AM to 10:00 PM and the service A is available from 10:00 AM to 9:00 PM, the warning may be limited to the first customer visit for service A after 10:00 AM (when the first transaction information is generated). Furthermore, the confirmation leading to the above warning may be limited to a specified time frame. For example, if the store's business hours are from 10:00 AM to 10:00 PM and the service A is available from 10:00 AM to 9:00 PM, the warning may be limited to the first customer visit for service A between 10:00 AM and 10:30 AM (when the first transaction information is generated). The same applies not only when none of the machines are running, but also when all machines are not running, when machines are running but cannot process payments (e.g., due to malfunction), when there is a possibility that payment may not be possible (e.g., near-end change), or when transaction information is not generated on the cloud server 20.

[0176] If the cloud server 20 generates transaction information for a transaction made by the mobile terminal 60 based on a predetermined operation on the mobile terminal 60, but none of the mobile payment machines are activated, the mobile terminal 60 may be notified of this fact. This allows the customer in question to be informed, for example, that immediate settlement is not possible, or to be guided to a service other than service A, i.e., another transaction that does not use the mobile terminal 60 (for example, a transaction using a fully self-service machine). The same applies not only when none of the machines are activated, but also when all machines are not activated, when machines are activated but settlement is not possible, when there is a possibility that settlement will not be possible, or when transaction information is not generated on the cloud server 20.

[0177] It is also useful in situations other than when the store is open. For example, if the store's business hours are from 10:00 AM to 10:00 PM and the usage time for Service A is from 10:00 AM to 9:00 PM, at some point after 9:00 PM, if a store employee looks around the store and determines that there are no customers using Service A (customers who have registered products using the mobile terminal 60) in the store, they will initiate a closing process that involves turning off the power to the portable payment machine. After the closing process has started, there is a possibility that a customer may start a transaction using the mobile terminal 60. The transaction status management device 40 can grasp both the status of the portable payment machine (that it is not running) and whether a transaction for Service A has started. Therefore, for example, the store employee using the transaction status management device 40 can explain the situation to the customer (for example, that the transaction using the mobile terminal 60 has ended, and that transactions can be made by other means) and minimize confusion. In addition, a message such as "Transactions using the mobile terminal for today have ended. Please use the normal transaction method" can be displayed to the mobile terminal 60 to minimize confusion.

[0178] Furthermore, when it is outside the operating hours of Service A, the cloud server 20 does not need to generate transaction information. In other words, if the transaction status management device 40 receives a service start notification from the mobile terminal 60 during the operating hours of Service A, it may generate transaction information for the transaction made by the mobile terminal 60 and send the transaction start notification to the transaction status management device 40. If it receives a service start notification from the mobile terminal 60 outside the operating hours of Service A, it may not generate transaction information and instead send a predetermined notification including the customer's membership number for the mobile terminal 60 to the transaction status management device 40. Furthermore, the operation of the transaction status management device 40 when it receives a predetermined notification may be the same as when it receives a transaction start notification.

[0179] Furthermore, the transaction status management device 40 can remotely control the closing process of each installed cash register. As mentioned above, the transaction status management device 40 can also determine whether or not there are any users of service A who have not yet paid in the store. If there is even one user of service A who has not yet paid in the store, the transaction status management device 40 may restrict (prohibit) the start of the closing process for the portable payment machine, or it may warn the store staff (display, voice output, etc.). For example, the transaction status management device 40 may notify (display, voice output, etc.) that "There is a customer using the portable terminal 60. Closing is not possible," and prevent the closing process from being performed.

[0180] (Release of held items) The transaction status management device 40 can accept an operation to release a held item (sometimes simply called releasing a held item). Specifically, the transaction status management device 40 can accept an operation to register an item that has not yet been scanned.

[0181] Figure 23 shows an example of the product information input screen 1400. The product information input screen 1400 is a screen used to input product information. For example, a button (input screen button) may be placed on a small screen that appears after the operation of the unscanned product button BT491 (a button may be placed for each product if multiple displays exist), and the transaction status management device 40 may display the product information input screen 1400 when the input screen button is operated.

[0182] The product information input screen 1400 includes a product information display area HR1410, a product identification operation reception area SR1420, an image capture display area HR1430, a confirmation button BT1440, and a product cancellation button BT1441.

[0183] The product information display area HR1410 is for displaying the product name, product code, price, registered quantity, etc. The registered quantity can be changed using the plus and minus buttons in this area.

[0184] The product identification operation reception area SR1420 is an area that accepts operations to identify (register) products using various buttons located in this area. For example, one may identify a product by operating the preset button BT1421 and then displaying the preset screen (a screen with product buttons corresponding to individual products, where the preset buttons are located). Alternatively, one may identify a product by operating the PLU button BT1422 and then entering the product code. Note that the PLU button BT1422 is a button that declares the input of a number using a numeric keypad, but it is also possible to simply input a number using numeric keypads without the PLU button BT1422. After identifying a product, the product name and other information of that product are displayed (reflected) in the product information display area HR1410. Note that the captured image display area HR1430 displays the captured image related to the unscanned product, similar to the small screen displayed after operating the unscanned product button BT491, so one may identify a product while checking this captured image.

[0185] The store clerk checks the information displayed in the product information display area HR1410, and if there are no problems, operates the confirmation button BT1440. When the confirmation button BT1440 is operated, the transaction status management device 40 registers the product using the product information (information displayed in the product information display area HR1410) identified by the preset button BT1421 or the quantity input. The product cancellation button BT1441 is a button that instructs the cancellation of the registration of the product.

[0186] If an unscanned product is registered and the transaction does not include any unscanned products, the unscanned product button BT491 is deleted. For example, in display area "1" in Figure 22, the unscanned product button BT491 is displayed, but let's assume there are two unscanned products included in the transaction. When the unscanned product button BT491 in display area "1" is operated, a small screen is displayed with two input screen buttons corresponding to each of the two unscanned products. When one input screen button is operated on the small screen, the product information input screen 1400 for the product corresponding to that input screen button is displayed. When the registration of the unscanned product is completed via the product information input screen 1400, the product information input screen 1400 is deleted, but the unscanned product button BT491 in display area "1" is not deleted (the small screen with one input screen button deleted may remain displayed). When the input screen button for the remaining unscanned product is operated on the small screen, the product information input screen 1400 for the product corresponding to that input screen button is displayed. If the registration of an unscanned product is completed via the product information input screen 1400, both the product information input screen 1400 and the sub-screen will be cleared, and the unscanned product button BT491 in display area "1" will also be cleared.

[0187] Furthermore, the transaction status management device 40 may also accept operations to release other held items. For example, the transaction status management device 40 may also accept operations to release age verification items. For example, if a customer has made an operation on their mobile terminal 60 indicating that they are 20 years of age or older (a declaration that they are 20 years of age or older), this declaration may be displayed on the transaction status management device 40, and the age verification item may be released by an approval operation on the transaction status management device 40. When releasing an age verification item, the customer's appearance may be confirmed from images captured by cameras installed throughout the store. The captured images of the customer may be identified, for example, based on the customer's (mobile terminal 60's) location information and displayed on a small screen that appears when an age verification item is being processed.

[0188] When a held item is released from hold, this is reflected in the transaction information on the cloud server 20. For example, if the transaction status management device 40 releases the hold on a held item a on a mobile terminal 60, it sends information (release information) from the mobile terminal 60 indicating that the hold on the held item a has been released (release information). Based on the release information, the cloud server 20 updates the transaction information on the mobile terminal 60 (releases the hold on held item a). The cloud server 20 may also generate screen information reflecting the updated transaction information and send it to the mobile terminal 60. This ensures that the release of the hold in the transaction status management device 40 is reflected on the screen of the mobile terminal 60 as appropriate. For example, if the transaction status management device 40 verifies the age of a certain item (age verification item) in a transaction on a mobile terminal 60, the display of "Age Verification Required" attached to the item on the screen of the mobile terminal 60 changes to "Age Verified" (or the "Age Verification Required" display disappears).

[0189] The display of the transaction status management device 40 has been explained above using Figures 16 to 23, but the display of the transaction status management device 40 is not limited to what has been explained using Figures 16 to 23. For example, the above explanation described an example of switching between the installed cash register management screen (Figures 16 to 21) and the mobile terminal management screen (Figures 22 and 23), 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). Furthermore, when displaying them simultaneously, the device may accept operations such as making one larger and the other smaller.

[0190] 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)).

[0191] (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 (for example, after the payment 2D code 605 is displayed) and before payment begins (for example, before the payment device 50 reads the payment 2D code 605) the mobile terminal 60 (i.e., the mobile terminal 60 that is in the process of moving to payment) (3) After the start of settlement (for example, after the settlement device 50 reads the settlement 2D code 605) and before the settlement is completed (i.e., the mobile terminal 60 in the process of 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 has started but before settlement is completed (i.e., (1) + (2) + (3). Example in Figure 22) the mobile terminal 60

[0192] Furthermore, the transaction status management device 40 may display the processing progress of each mobile terminal 60 (for example, "Product Registration in Progress," "Transitioning to Settlement," "Settlement in Progress," etc.) on the mobile terminal management screen shown in Figure 22. In addition, for mobile terminals 60 that are being settled (mobile terminals 60 after the settlement device 50 has read the settlement 2D code 605), the transaction status management device 40 may display information about the settlement device 50 that is being settled (for example, "Unit 1," "Unit 2," "Unit 3," etc.) on the mobile terminal management screen. Alternatively, instead of or in addition to displaying information about the settlement device 50 that is being settled on the mobile terminal management screen, the transaction status management device 40 may display information about the mobile terminal 60 that is being settled (for example, the membership number of the customer using the mobile terminal 60, etc.) on the installed register management screen (layout screen) shown in Figure 22.

[0193] (Exit gate device) In the first embodiment (and similarly in other embodiments), an exit gate device 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 device may, for example, comprise a detection unit, a reading unit, a determination unit, and a regulating unit. The detection unit detects the entry of a person (customer, etc.). The reading unit reads identification information. The identification information may be, for example, a two-dimensional code (a two-dimensional code for permission to pass) printed on a receipt issued after payment, or a two-dimensional code for permission to pass displayed on a mobile terminal 60 after payment. The determination unit determines whether or not to allow passage based on the reading result of the identification information by the reading unit. The regulating unit has a regulating member (door, bar, etc.) and restricts (hinders / does not hinder) passage using the regulating member based on the determination result by the determination unit.

[0194] As described above, the exit gate device may simply be configured to restrict movement, but it may also include a display or audio notification. Furthermore, the exit gate device may be connected to a network (LAN) and managed (monitored and controlled) by, for example, the transaction status management device 40. In other words, the transaction status management device 40 can manage devices installed in the store other than the cash registers and mobile terminals 60, that is, it can broadly manage the "situation inside the store".

[0195] The exit gate device may include a detection unit, a reading unit, a judgment unit, and a regulation unit, as well as a communication unit for communicating with other devices (for example, a transaction status management device 40). The exit gate device may also include a display unit (such as an LCD or LED) for displaying the reading results from the reading unit, and an audio output unit for announcing the reading results from the reading unit by voice. The exit gate device may also include a ticket issuing unit (printing unit) for issuing coupons to encourage customers to visit again.

[0196] The transaction status management device 40 manages the customer's journey from entering the store until they pass through the exit gate device and leave the store. If the transaction status management device 40 does not manage the exit gate device, and the display and audio output functions of the exit gate device are insufficient, it may be difficult to notice notifications such as restrictions on passage, even if the transaction status management device 40 is installed near (next to) the exit gate device. However, if the transaction status management device 40 does manage the exit gate device, even if the display and audio output functions of the exit gate device are insufficient, the store staff can check the status on the screen. Furthermore, if the transaction status management device 40 is installed near the exit gate device being monitored, the store staff of the transaction status management device 40 can check the status of customers leaving the store through the exit gate device, either via the screen or by visually observing from a close position. It is also preferable to have multiple exit gate devices installed in the store, or to have them scattered throughout the store, as the status of each exit gate device can be managed by the transaction status management device 40.

[0197] The transaction status management device 40 may also display logs, real-time operation status, etc., as in the case of the weighing device (described later). Events (phenomena) managed as logs include, for example, the judgment result of the judgment unit (OK, NG) and the issuance of coupons by the ticketing unit. Examples of abnormal log events include, for example, a person passing through without reading identification information, a person passing through despite a NG judgment of identification information, low remaining coupon paper, running out of coupon paper, a coupon paper jam, and communication abnormalities with other devices (transaction status management device 40, store controller 30, etc.). In addition to the above, the transaction status management device 40 may also display as logs information that cannot be resolved (or is difficult to resolve) unless a store employee goes to the exit gate device, and information necessary for later analysis (the same applies to the logs of the weighing device (described later)). The transaction status management device 40 may display these logs on the screen along with the time of occurrence. Regardless of whether or not the transaction status is displayed on the screen (i.e., even if it is not displayed), the transaction status management device 40 stores log and operation status information along with the time of occurrence in its storage unit (the same applies to logs of the weighing device (described later)).

[0198] As described above, the embodiments can provide a suitable accounting workflow when multiple services coexist.

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

[0200] (1) In the above embodiment, the transaction status management device 40 was described as a device installed in the store and operated at its installation location. However, the transaction information management device 40 may be a portable device operated in various locations within the store (for example, various locations on the sales floor, various locations in the checkout area, the back room, etc.). For example, the transaction information management device 40 may be a laptop computer, a tablet terminal, or a stationary device with a detachable display. If the transaction information management device 40 is a portable device, it is possible to release the hold on a reserved item by actually interacting with the customer. For example, the appearance of the customer can be directly confirmed at the sales floor, and the hold on the reserved item for the customer's age can be released.

[0201] (2) In the above embodiment, the settlement device 50 was described as a device that settles the payment for products registered by the mobile terminal 60. However, the settlement device 50 may settle the payment for products registered by a device other than the mobile terminal 60 (for example, a registration settlement device 51, a registration settlement device 52, or a registration device 53). For example, the settlement device 50 may receive registration information from the registration device 53, as in the settlement device 54, and settle the payment for products registered by the registration device 53.

[0202] (3) Although the settlement device 50 (portable settlement machine) has been described as a device for settling items registered by the mobile terminal 60, a different device from the settlement device 50 (for example, a registration settlement device 51, a registration settlement device 52, or a settlement device 54) may also settle items registered by the mobile terminal 60. For example, the registration settlement device 51 (and the same applies to the registration settlement devices 52 and 54) may read the settlement 2D code 605 displayed by the settlement device 50 and display it on a product list screen as shown in Figure 13.

[0203] (4) In relation to (2) and (3) above, an operating mode for settling products registered by the mobile terminal 60 may be provided. For example, the settlement device 50 may have an operating mode for settling products registered by a settling register (registration device 53, etc.) and a mobile terminal registered product settlement mode for settling products registered by the mobile terminal 60. Also, for example, the registration settlement device 51 may have the above-mentioned mobile terminal registered product settlement mode in addition to the operating modes already described (face-to-face self-service mode, full self-service mode, etc.). The settlement device 50 (and the registration settlement device 51) may read the settlement 2D code 605 when the current operating mode is the mobile terminal registered product settlement mode (or it may switch from another operating mode to the mobile terminal registered product settlement mode by reading the settlement 2D code 605).

[0204] (5) In relation to (4) above, a single device that combines the functions of a settlement device 50 and a registration settlement device 51 may be provided. In other words, a registration settlement device (settlement register) may be installed in the store that has face-to-face self-service mode (one of the set-up register registered product settlement modes), full self-service mode (one of the set-up register registered product settlement modes), registration-only mode (one of the set-up register registered product settlement modes), settlement-only mode (one of the set-up register registered product settlement modes), and mobile terminal registered product settlement mode.

[0205] (6) In the above embodiment, an example was described in which a settlement device (portable settlement machine) 50, a registration settlement device (multiple operation mode machine) 51, a registration settlement device (full self-service only machine) 52, a registration device (semi-self-service registration machine) 53, and a settlement device 54 (semi-self-service settlement machine) exist as the installed cash register, but the installed cash register is not limited to these. For example, a registration settlement device (a conventional general registration settlement machine; referred to as registration settlement device 59) may be installed on one side (the employee side) equipped with a scanner unit, a settlement unit (specifically, a cash settlement unit), etc., and used by the employee. When a registration settlement device 59 is installed, the transaction status management device 40 may manage (monitor and control) the registration settlement device 59. The registration settlement device 59 may be of a type that performs registration and settlement in a single enclosure, or it may consist of, for example, a tower-type registration device 59a and a settlement device 59b equipped with a drawer.

[0206] (7) 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, products may be registered using a tablet terminal (which may be a type fixed to a shopping cart) that the store lends to customers. Alternatively, products may be registered using a shopping cart equipped with a display unit (or a display unit that can be attached to or detached from a shopping cart). In other words, the terminal that the store lends is not limited to a mobile terminal 60, and may be connected to a shopping cart equipped with an operation screen, camera, scale, and battery, or it may be integrally formed with the shopping cart (it may be detachable). Furthermore, the shopping cart may be equipped with an electronic tag recognition unit that recognizes the information of the electronic tag. In the embodiment in which products are registered using a shopping cart (or a display unit that can be attached to or detached from a shopping cart), the cart number of the shopping cart may be displayed on the management screen (Figures 16 to 23).

[0207] Shopping carts equipped with the aforementioned batteries (hereinafter simply referred to as "carts") may be charged by contact (contact charging) or non-contact (non-contact charging). The cart charging equipment may be installed at the place where customers retrieve and return the carts (cart storage area). Retrieving and returning the carts may be done by customers or by store staff. In the case of contact charging, a cable or similar device is connected to the cart's battery to charge it. The cart storage area should have the same number of cables or similar devices as the number of carts that can be stored (the maximum number of carts waiting before rental) (if storage locations are set, they should be arranged in their respective storage locations). In the case of non-contact charging, a non-contact charging system (power supply (transmitting) unit, power receiving (receiving) unit) is installed on both the cart side and the cart storage area side. Power is transmitted from the power supply unit on the cart storage area side and received by the power receiving unit on the cart side to charge it. Similar to contact charging, the cart storage area should have the same number of power supply units as the number of carts that can be stored, arranged so that power supply and power receiving units form pairs. Furthermore, a large power supply unit capable of transmitting power may be placed at the cart collection point, and power may be transmitted collectively to multiple receiving units. Similar to the retrieval and return of carts, charging (contact charging, contactless charging) may be done by the customer (the store may ask the customer to charge) or by the store staff (the store staff may periodically check the collection point and manually put the carts into a charging state).

[0208] The transaction status management device 40 may also manage (monitor and control) the cart storage area as described above. For example, the transaction status management device 40 may display the number of carts waiting in the cart storage area (number of waiting carts) on the management screen. Alternatively, the transaction status management device 40 may display the number of carts charging in the cart storage area (number of charging carts) in addition to or instead of the number of waiting carts. The method by which the transaction status management device 40 obtains the number of waiting carts may be, for example, by using a camera that images the cart storage area to capture images of the carts (number of carts) present in the cart storage area, performing image recognition on the captured images to calculate the number of carts, and obtaining this as the number of waiting carts. The device that performs image recognition may be the transaction status management device 40 or another device (if another device performs image recognition, it will notify the transaction status management device 40 of the calculated number of carts). Alternatively, a transmissive or reflective optical sensor may be installed to detect carts present in the cart storage area and obtain this as the number of waiting carts. Alternatively, the number of waiting carts may be obtained by communicating with a mobile terminal 60 attached to a cart in the cart storage area using NFC (Near Field Communication) communication or Bluetooth® communication. Alternatively, a scale may be installed on the floor of the cart storage area, and the number of carts present in the cart storage area may be calculated from the total weight and obtained as the number of waiting carts. Alternatively, the number of waiting carts may be calculated (or calculated as an estimate) by subtracting the number of carts currently in use from the total number of carts. Whether a cart is in use may be determined based on the transaction status. For example, the transaction status management device 40 may determine that a cart is in use during the period from the start of shopping (or scanning of one item) to the completion of the transaction. The method by which the transaction status management device 40 obtains the number of carts being charged may be, for example, by the cart storage area recognizing whether it is electrically or magnetically powered and notifying the transaction status management device 40, or by the cart storage area obtaining information that a cart is being charged through communication with the cart and notifying the transaction status management device 40. In cases where power is transmitted to multiple receiving units in a batch, the number of carts being charged may be calculated based on the amount of power.Furthermore, the transaction status management device 40 may compare the number of waiting carts with the number of carts currently charging and display the comparison result (difference) on the management screen (for example, displaying the number of waiting carts, the number of carts currently charging, and the difference separately). If the number of waiting carts and the number of carts currently charging do not match (specifically, if the number of carts currently charging is less than the number of waiting carts), the transaction status management device 40 may determine that charging is not being performed correctly and display a message on the management screen (for example, "Please check the cart charging at the cart collection point"). The transaction status management device 40 may also send a similar message to a mobile terminal used by a store employee.

[0209] (8) In the above description, the objects of management (monitoring and control) of the transaction status management device 40 were described as the installed cash register, the mobile terminal 60 (including the tablet terminal etc. shown in (7) above), the exit gate device, and the cart storage area. However, the objects of management of the transaction status management device 40 are not limited to these. For example, a weighing device as described below may also be monitored. In the prepared food sales corner of the store, weighed products (products sold by weight) may be sold. When selling products by weight, a weighing device (weighing and pricing device) may be installed that weighs the product to be purchased by a store employee or by customer operation (self-service operation) and calculates the selling price based on the unit price by weight and the weighed value of the product. The weighing device prints and issues pricing information including the selling price as a product label for customers who do not use the mobile terminal 60 (customers of services other than Service A). For customers who use the mobile terminal 60 (customers of Service A), the weighing device transmits pricing information including the selling price to the mobile terminal 60 via wireless communication (e.g., Bluetooth®). In particular, in the case of customer operation (self-service), there are often no staff members present around the weighing device (because it is intended for self-service and therefore staff are not typically present), so by making it subject to the management of the transaction status management device 40, any problems that arise can be responded to quickly even from a distance.

[0210] (9) In relation to (8) above, the transaction status management device 40 may display logs of the weighing device and real-time operation status. Events (phenomena) managed as logs include, for example, operations related to tare (tare operation, tare specification operation, etc.), product selection operations (operation of product preset buttons, etc.), product placement (weight detection, weighing value), label printing and issuance, and status related to wireless communication with the mobile terminal 60 (establishment and disconnection of communication (Bluetooth®) with the mobile terminal 60, etc.). Logs related to abnormal systems include, for example, that the remaining amount of product labels (label paper) is low, that the product labels have run out, that the product labels are jammed, that the weighing value remains negative, that the weighing value remains positive, that the weighing value exceeds the upper limit of the weighable value, and communication abnormalities with other devices (transaction status management device 40, store controller 30, etc.). Generally, the transaction status management device 40 is installed in the accounting area, while the weighing device is installed in a sales area different from the accounting area (near the prepared food sales corner). In other words, the two are generally installed in separate locations. Therefore, the staff of the transaction status management device 40 cannot immediately rush to the weighing device if something happens (at least it will take longer to arrive than rushing to other monitored items (such as cash registers) installed in the checkout area). To address this, a staff call button or the like may be provided (for example, displayed on the management screen of the transaction status management device 40, or a physical button installed nearby), and by operating the staff call button or the like, another staff member may go directly to the weighing device. For example, when the staff call button or the like is operated, the transaction status management device 40 may send information (message) to a mobile terminal carried by a staff member who is working on another task in the back room, etc., instructing them to go directly to the weighing device, or it may make an announcement over the intercom to the staff member working on another task in the back room, etc. The area of ​​the intercom may vary depending on the range of staff members to be called and the severity of the problem at the weighing device (therefore, for example, several types of call buttons with different broadcast areas may be provided, or a button to switch between broadcast areas may be provided).

[0211] (10) 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 another device (store controller 30 or cloud server 20) instead of the settlement device 50. Also, the settlement device 50 may display a screen generated by another device on the display unit 105, rather than a screen generated by itself (for example, it may browse a screen provided by a web server). 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 accepts various inputs (customer operations, detection by devices such as scanners), and sends the input information (operation information, detection information, etc.) to a server (for example, a cloud server 20). Subsequently, the cloud server 20 performs processing according to the information received from the settlement device 50 and sends the processing result (updated screen information, etc.) back to the settlement device 50. Subsequently, the settlement device 50 may perform actions according to the information received from the cloud server 20 (such as displaying information on the display unit 105). In other words, the cloud server 20 may execute a program to control the operation of the settlement device 50. The same applies to the registered settlement device 51, registered settlement device 52, registration device 53, settlement device 54, registered settlement device 59, transaction status management device 40, etc.

[0212] <Summary of Embodiments> [Technical field] This invention relates to an in-store status management device and program. [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, the burden on store staff to monitor multiple services coexisting increases. This invention has been made in view of these circumstances and aims to provide a technology that reduces the burden on store staff. [Means for solving the problem]

[0213] (1) An in-store status management device (for example, a transaction status management device 40) capable of monitoring multiple settlement devices, wherein the settlement devices include a first settlement device (for example, settlement device 54, registered settlement device 51, registered settlement device 52, registered settlement device 59) that settles for goods registered by other stationary devices or the device itself, and a second settlement device (for example, settlement device 50) that settles for goods registered by other portable devices (for example, a mobile terminal 60), and the in-store status management device is characterized by comprising a display means for displaying the status of the first settlement device and the second settlement device (for example, as shown in Figures 16 to 21). (1) The in-store situation management device reduces the burden on store staff. In other words, even when multiple services coexist within a store, it is possible to monitor all services comprehensively, making management easier and reducing the burden on store staff.

[0214] (2) The in-store status management device according to (1), characterized in that the first payment device (for example, the registered payment device 51) is equipped with a plurality of operating modes (for example, face-to-face self-service mode, full self-service mode, etc.), and the display means displays for each of the payment devices information indicating whether it is the first payment device or the second payment device (for example, a name such as "portable payment machine" or "multiple operating mode machine"), along with the current operating mode for the first payment device (for example, "(face-to-face)" for the multiple operating mode machine (face-to-face), "(full)" for the multiple operating mode machine (full), etc.). (2) The in-store status management device reduces the burden on store staff. For example, the status of each device can be easily checked, thus reducing the burden on store staff.

[0215] (3) The in-store status management device according to any one of (1) to (3), characterized in that the display means displays the status of the first payment device and the second payment device on the layout screen (for example, as shown in Figure 21). (3) The in-store situation management device reduces the burden on store employees.

[0216] (4) A program that causes a computer to function as an in-store status management device capable of monitoring multiple payment devices, wherein the payment devices include a first payment device that settles payments for goods registered by other stationary devices or the device itself, and a second payment device that settles payments for goods registered by other portable devices, and the program is characterized in that the computer functions as a display means for displaying the status of the first payment device and the second payment device. According to program (4), the burden on store employees will be reduced.

[0217] 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 59, etc.) may be performed by recording a program for realizing the functions of each device 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 implemented in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [Explanation of Symbols]

[0218] 1…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. An in-store status management device capable of monitoring multiple payment devices, The settlement device is, There is a first settlement device for settling payments for products registered on other stationary devices or on the device itself, and a second settlement device for settling payments for products registered on other portable devices. The in-store status management device is, The system includes a display means for displaying the status of the first settlement device and the second settlement device, The aforementioned display means is An in-store status management device characterized by displaying whether or not the first settlement device or the second settlement device is equipped with a cash settlement unit.

2. The first settlement device has multiple operating modes, The aforementioned display means is For each of the aforementioned payment devices, information indicating whether it is the first payment device or the second payment device is displayed, along with the current operating mode and an operator for accepting changes to the operating mode for the first payment device. The in-store condition management device according to feature 1.

3. The aforementioned display means is The operating mode of the second payment device is not displayed. The in-store condition management device according to feature 2.

4. A program that enables a computer to function as an in-store status management device capable of monitoring multiple payment devices, The settlement device is, There is a first settlement device for settling payments for products registered on other stationary devices or on the device itself, and a second settlement device for settling payments for products registered on other portable devices. The aforementioned computer, Display means for displaying the status of the first settlement device and the second settlement device. To make it function as, The aforementioned display means is A program characterized by displaying whether the first settlement device or the second settlement device is equipped with a cash settlement unit.

Images