In-store state management device and program
The in-store situation management device addresses the increased burden on store clerks by monitoring and displaying the status of multiple settlement devices, thereby streamlining the settlement process and enhancing efficiency in retail environments with multiple services.
Patent Information
- Application Number
- JP2025026844
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-21
- Publication Date
- 2025-05-02
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
When multiple services coexist in a retail environment, the burden on store clerks increases due to the complexity of managing various settlement methods and processes.
An in-store situation management device that monitors multiple settlement devices, including a first settlement device for items registered on other installed or portable devices, and a second settlement device for items registered on portable devices, with a display means to show the status of both devices.
The solution reduces the burden on store clerks by streamlining the settlement process, enhancing efficiency, and improving the overall management of multiple services within the store.
Smart Images

Figure 2025071275000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an in-store situation management device and a program. [Background technology]
[0002] There are cases where multiple services related to the sale of goods coexist. For example, a system that provides multiple payment methods in a store is known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2016-081072 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, when multiple services coexist, the burden on the store clerk to monitor them increases.
[0005] The present invention has been made in consideration of the above circumstances, and has an object to provide a technique for reducing the burden on store clerks. [Means for solving the problem]
[0006] One aspect of the present invention for solving the above-mentioned problems is an in-store situation management device capable of monitoring multiple settlement devices, which include a first settlement device that settles for products registered on an installed other device or on the device itself, and a second settlement device that settles for products registered on a portable other device, and the in-store situation management device is characterized in that it is equipped with a display means for displaying the status of the first settlement device and the second settlement device. [Brief description of the drawings]
[0007] [Figure 1]FIG. 1 is a conceptual diagram of a network for explaining a sales system. [Diagram 2] FIG. 2 is a diagram illustrating the external appearance of the settlement device. [Diagram 3] 2 is a configuration example of a settlement device. [Figure 4] FIG. 2 is a diagram illustrating the external appearance of the registration settlement device. [Diagram 5] 2 is a configuration example of a registration settlement device. [Figure 6] FIG. 2 is a diagram illustrating the appearance of a registration device. [Figure 7] 2 is a configuration example of a registration device. [Figure 8] FIG. 2 is a diagram illustrating the external appearance of the settlement device. [Figure 9] 2 is a configuration example of a settlement device. [Figure 10] 13 is a display example of a mobile terminal. [Figure 11] 13 is a display example of a mobile terminal. [Figure 12] 13 is an example of a display on a settlement device. [Figure 13] 13 is an example of a display on a settlement device. [Figure 14] FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 15] 11 is a sequence diagram showing an example of processing by the settlement device and the cloud server. FIG. [Figure 16] 13 is a display example of a transaction status management device. [Figure 17] 13 is a display example of a transaction status management device. [Figure 18] FIG. 2 is an explanatory diagram illustrating the display of a transaction status management device. [Figure 19] 13 is a display example of a transaction status management device. [Figure 20] 13 is a display example of a transaction status management device. [Figure 21] 13 is a display example of a transaction status management device. [Figure 22] 13 is a display example of a transaction status management device. [Diagram 23] 13 is a display example of a transaction status management device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] Fig. 1 is a conceptual diagram of a network for explaining a sales system 1 of this embodiment. The sales system 1 shown in Fig. 1 includes a headquarters server 10, a cloud server 20, a store controller 30 (e.g., a server, etc.), a transaction status management device 40 (e.g., a personal computer, etc.), a settlement device 50, a registration settlement device 51, a registration settlement device 52, a registration device 53, a settlement device 54, and a mobile terminal 60.
[0009] The store controller 30, the transaction status management device 40, the settlement device 50, the registration settlement device 51, the registration settlement device 52, the registration device 53, and the settlement device 54 are communicatively connected via a LAN 19 (which may be wired or wireless). The store controller 30 is capable of communicating with the headquarters server 10. The sales system 1 can be introduced in various stores (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).
[0010] In Fig. 1, the number of each device (terminal) is an example. For example, in Fig. 1, "..." is illustrated to the right of the transaction status management device 40, but the number of transaction status management devices 40 installed in one store may be one or more. Also, for example, in Fig. 1, two mobile terminals 60 are illustrated, but the number of mobile terminals 60 used in the store changes depending on the number of customers.
[0011] Sales system 1 provides a self-service (hereinafter, sometimes referred to as service A) in which a customer uses a mobile terminal 60 to register a product and uses a settlement device 50 to settle the payment. In other words, service A is a self-service in which a customer registers a product and settles the payment by himself / herself, using mobile terminal 60 for product registration and using settlement device 50 for settlement.
[0012] Furthermore, the sales system 1 provides other services in addition to the service A. For example, as other services, the sales system 1 can provide a service in which a customer uses the registration and settlement device 51 or the registration and settlement device 52 to register products and settle the payment, or a service in which a store clerk uses the registration device 53 to register products and a customer uses the settlement device 54 to settle the payment.
[0013] The headquarters server 10 is installed outside the store (e.g., at a head office or a data center) and is a server that manages the entire sales system 1. The headquarters server 10 stores, for example, various information required for the operation of services including service A (e.g., customer master (member master), product master, sale file, etc.) and performance information of services in the store (e.g., sales performance information, product sales performance information, etc.). The headquarters server 10 communicates with the cloud server 20 and the store controller 30. The headquarters server 10 may communicate with other devices (e.g., a transaction status management device 40, a settlement device 50, etc.). The headquarters server 10 may be composed of multiple servers.
[0014] Cloud server 20 is a server installed outside a store (e.g., in a data center, etc.) and provides service A. Cloud server 20 stores, for example, various information required for the operation of service A (e.g., product master, transaction information (also referred to as cart information), etc.). Cloud server 20 communicates with headquarters server 10 and mobile terminal 60. Cloud server 20 may also communicate with other devices (e.g., store controller 30, transaction status management device 40, etc.). Cloud server 20 may be composed of multiple servers.
[0015] The store controller 30 is a device that controls the part of the sales system 1 that is related to the store. The store controller 30 communicates with each device in the LAN 19 (e.g., the settlement device 50, etc.) and each device outside the LAN 19 (e.g., the headquarters server 10). For example, the store controller 30 receives a product master and a sale file from the headquarters server 10 and provides them to the settlement device 50.
[0016] The transaction status management device 40 is a device that mainly manages each device in the LAN 19. For example, the transaction status management device 40 communicates with each device in the LAN 19 and monitors the processing status, operation status, etc. of each device in the LAN 19. The transaction status management device 40 may also communicate with each device outside the LAN 19 (e.g., the head office server 10, the cloud server 20) (it may communicate directly or via the store controller 30). For example, the transaction status management device 40 may refer to transaction information (cart information) stored in the cloud server 20.
[0017] The mobile terminal 60 is a terminal used when registering a product in the service A. That is, the customer uses the mobile terminal 60 when registering a product in the service A. The mobile terminal 60 has a communication function, an imaging function (camera), and a recognition function for recognizing various codes (barcodes, two-dimensional codes, etc.). For example, the mobile terminal 60 recognizes a barcode attached to a product. For example, the mobile terminal 60 may extract feature points in an image captured by the imaging function (an image acquired as a through image (live view)) and recognize an object (various codes). Note that the mobile terminal 60 is assumed to be owned by an individual customer (or a corporation) who uses the service A, but may be loaned by the store.
[0018] The settlement device 50 is a device used when making a settlement in service A. That is, a customer uses the settlement device 50 when making a settlement for a product registered using a mobile terminal 60. The configuration of the settlement device 50 will be described later.
[0019] The registration and settlement device 51 is used by a store clerk or a customer. Specifically, the registration and settlement device 51 has a scanner unit on both sides (the store clerk side and the customer side) and a settlement unit on one side (the customer side). The registration and settlement device 51 has a number of switchable operating modes. The configuration of the registration and settlement device 51 will be described later.
[0020] The registration and settlement device 52 is mainly used by customers. The registration and settlement device 52 includes a scanner unit and a settlement unit, and is used for registering and settling products.
[0021] The registration device 53 is mainly used by store clerks. The registration device 53 includes a scanner unit and is used exclusively for registering products. The configuration of the registration device 53 will be described later.
[0022] The settlement device 54 is mainly used by customers. The settlement device 54 includes a settlement unit and is used exclusively for settlement. The configuration of the settlement device 54 will be described later.
[0023] The sales system 1 may be linked to other systems. For example, the transaction status management device 40 may be able to access a time attendance server that manages information related to the time attendance of employees (clerks) (for example, attendance record information, work schedule information, etc.).
[0024] (Transaction status management device 40) Although not shown in the figure, the transaction status management device 40 includes a CPU, a ROM, a RAM, a hard disk, a display unit, and a 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), and may be connectable to a device (keyboard) that includes a key operation unit. The transaction status management device 40 may be connectable to a device (printer) that includes a printing unit, a device (speaker) that includes a sound output unit, a device (scanner) that includes a scanner unit that can scan a code attached to a store clerk's name tag, or a device (card reader) that includes a card reading unit that can read a card (e.g., a store clerk card).
[0025] (Payment device 50) Fig. 2 is a diagram illustrating the external appearance of the settlement device 50. Fig. 3 shows an example of the configuration of the settlement device 50. In Fig. 2 and Fig. 3, the same parts are denoted by the same reference numerals.
[0026] Hereinafter, a configuration example of the settlement device 50 shown in FIG. 3 will be described with reference to FIG. 2. The settlement device 50 includes a CPU 101, a ROM 102, a RAM 103, a hard disk 104, a display unit 105, a scanner unit 106, a card settlement unit (non-cash settlement unit) 108, a change machine (cash settlement unit) 109, a printing unit 113, an audio output unit 114, a communication unit 115, an imaging unit (camera) 116, and a sign pole 117. These can communicate with each other via a bus. The settlement device 50 (similar to the settlement device 54) may further include a key operation unit. The settlement device 50 (similar to the registration settlement device 51, the registration settlement device 52, the registration device 53, and the settlement device 54) may further include a sensor (such as a human sensor) that detects the presence of a person.
[0027] The CPU 101 is a central processing unit, and controls the operation of the settlement device 50 by reading and executing programs stored in the ROM 102 . The ROM 102 is a read-only memory, and stores various types of information used by the CPU 101, including programs.
[0028] The RAM 103 is a read / write memory and stores various information as a main storage device. For example, the RAM 103 stores information read from the ROM 102 or the hard disk 104, information acquired from the outside, information generated during processing, and the like.
[0029] The hard disk 104 stores various information as an auxiliary storage device. For example, the hard disk 104 may store programs executed by the CPU 101 instead of the ROM 102. Also, instead of the RAM 103, the hard disk 104 may store information read from the ROM 102, information acquired from the outside, information generated in processing, etc. Note that instead of the hard disk 104, a storage device such as an SSD (Solid State Drive) may be provided.
[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 information. Specifically, the scanner unit 106 scans a code (a two-dimensional code 605 for settlement (described later)) displayed on the display unit of the mobile terminal 60, and reads information necessary for settlement processing. The scanner unit 106 may also scan codes attached to gift certificates (gift certificates, coupons, and complimentary coupons) and various cards (e.g., membership cards, point cards, etc.) and read the respective information. The scanner unit 106 may also scan a code attached to a store clerk's name tag or the like and read the store clerk code.
[0032] In addition to the above, the scanner unit 106 may scan a code attached to a product and read the product code (JAN code, etc.). The scanner unit 106 may also scan a code printed on a receipt (registered trademark) printed and issued by another device (for example, the registration settlement device 51, the registration device 53, etc.) and read information required for settlement processing.
[0033] The card payment unit 108 is a payment mechanism that uses various cards (credit cards, prepaid cards such as transportation cards, cash cards for debit payments, point cards for point payments, etc.). The card payment unit 108 includes a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient that the card payment unit 108 includes at least the card recognition unit. The card recognition unit may recognize various cards (e.g., point cards, membership cards, stockholder cards, etc.) for the purpose of providing benefits, discounts, etc.
[0034] The card payment unit 108 may be multiple members according to the cards to be read. In other words, the settlement device 50 may have multiple card payment units, such as a first card payment unit 108a for prepaid cards and a second card payment unit 108b for credit cards.
[0035] The change machine 109 is a cash settlement mechanism, which has an input port for banknotes and coins, and an output port for banknotes and coins, calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, detecting the number of coins by denomination, etc.).
[0036] The printing unit 113 prints and issues various media (receipts, etc.). The audio output unit 114 outputs audio. For example, the audio output unit 114 outputs a confirmation sound, a warning sound, audio guidance, and the like.
[0037] The communication unit 115 transmits and receives information to and from other devices (for example, the store controller 30, the transaction status management device 40, etc.). The imaging unit 116, for example, captures an image of the customer. The settlement device 50 may include two or more imaging units 116, and simultaneously capture images of the face and hands (near the insertion slot and ejection slot of the change machine 109). The sign pole 117 has a light emitting part at the tip, and notifies various information (such as calling a store clerk, operating status, etc.) depending on the light emitting state of the light emitting part.
[0038] (Registration settlement device 51) FIG. 4 is a diagram for explaining the appearance of the registration settlement device 51. FIG. 5 is a configuration example of the registration settlement device 51. In FIG. 4 and FIG. 5, the same parts are given the same reference numerals. The registration settlement device 51 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer side display unit 205, a customer side scanner unit 206, a card settlement unit (non-cash settlement unit) 208, a change machine (cash settlement unit) 209, a store clerk side display unit 210, a key operation unit 211, a store clerk side scanner unit 212, a printing unit 213, an audio output unit 214, and a communication unit 215. These can communicate with each other via a bus. The registration settlement device 51 (similar to the registration settlement device 52, the registration device 53, and the settlement device 54) may further include an imaging unit (similar to the imaging unit 116 of the settlement device 50). In addition, the registered settlement device 51 may further include a sign pole (a sign pole similar to the sign pole 117 of the settlement device 50) or the like.
[0039] The CPU 201, ROM 202, RAM 203, hard disk 204, card settlement unit 208, change machine 209, audio output unit 214, and communication unit 215 of the registered settlement device 51 are similar to the CPU 101, ROM 102, RAM 103, hard disk 104, card settlement unit 108, change machine 109, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the description will be omitted.
[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 information. Specifically, the customer-side scanner unit 206 scans the code attached to the product and reads the product code (JAN code, etc.). The customer-side scanner unit 206 may also scan the codes attached to gift certificates and various cards and read the respective information. The customer-side scanner unit 206 may also scan the code attached to the name tag of a store clerk and read the store clerk code. The customer-side scanner unit 206 may also scan the code printed on the bill and read the information required for the payment process.
[0042] Although the customer-side scanner unit 206 is used when a customer registers a product, the customer may register the product by other methods. For example, if a preset key (a button for ordering the product) corresponding to the product is displayed on the customer-side display unit 205, the customer may operate (press) the preset key to register the product.
[0043] The store clerk's display unit 210 is a touch display that displays various information to the store clerk and receives various inputs from the store clerk. Various buttons operated by a store clerk are arranged on the key operation section 211. Reference numeral 211a denotes a mode switching button for switching between operation modes.
[0044] The clerk scanner unit 212 is a scanner unit for use by clerks, and optically reads various information. Specifically, the clerk scanner unit 212 scans codes attached to products and reads product codes (JAN codes, etc.). The clerk scanner unit 212 may also scan codes attached to gift certificates and various cards and read the respective information. The clerk scanner unit 212 may also scan codes attached to clerk nametags, etc., and read the clerk code. The clerk scanner unit 212 may also scan codes printed on bills and read the information required for payment processing.
[0045] Although the store clerk's scanner unit 212 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper, etc.) is arranged on the key operation unit 211, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 210, the store clerk may operate that preset key to register the product.
[0046] The printing unit 213 prints and issues various media (receipts, bills, etc.). The printing unit 213 can freely rotate to change its orientation (direction of the media issuing port) from the store clerk side to the customer side, or from the customer side to the store clerk side. The orientation of the printing unit 213 may be changed manually, or may be changed automatically (mechanically controlled, etc.) based on, for example, a change in the operating mode. The correctness of the orientation of the printing unit 213 may be detected by a sensor, etc.
[0047] (Operation mode of the registration settlement device 51) As described above, the registration and settlement device 51 has a plurality of operation modes. The operation modes are described below. The condition for switching the operation mode is the operation of the switching button 211a as described above, but the operation mode can also be switched according to other conditions (e.g., the passage of time, reception of registration information, reading of a store clerk code, schedule, reception of an operation 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 called the face-to-face self-service mode) is an operation mode in which a store clerk registers products using one side (the store clerk side) of the registration and settlement device 51, and a customer settles the payment using the other side (the customer side) of the registration and settlement device 51. Therefore, when the operation mode is the face-to-face semi-self-service mode, the store clerk and the customer meet face to face, the store clerk registers the products, and the customer settles the payment.
[0049] (Full self mode) The full self-service mode is an operation mode in which a customer registers products and makes a payment using one side (customer side) of the registration and payment device 51. Therefore, when the operation mode is the full self-service mode, the customer registers products and makes a payment using the customer side (without using the store clerk side).
[0050] (Multiple-unit semi-self-registration mode (registration only mode)) The multiple-unit semi-self-service registration mode (also referred to as a registration-only mode) is an operation mode in which a store clerk registers products using one side (the store clerk side) of the registration and settlement device 51. Therefore, when the operation mode is the multiple-unit semi-self-service registration mode, the store clerk registers products using the store clerk side (without using the customer side).
[0051] (Multiple-unit semi-self-service payment mode (payment-only mode)) The multiple-machine semi-self-service settlement mode (also referred to as settlement-only mode) is an operation mode in which a customer settles the bill using one side (customer side) of the registered settlement device 51. Therefore, when the operation mode is the multiple-machine semi-self-service settlement mode, the customer settles the bill using the customer side (without using the store clerk side).
[0052] The registered settlement device 51 in the multiple-vehicle semi-self-service registration mode transmits (directly or indirectly via another device) registration information to the other registered settlement device 51 (specifically, the registered settlement device 51 in the multiple-vehicle semi-self-service registration mode) to cause the other registered settlement device 51 (registered settlement device 51 in the multiple-vehicle semi-self-service registration mode) to settle the merchandise registered by the registered settlement device 51 (registered settlement device 51 in the multiple-vehicle semi-self-service registration mode). In other words, the registered settlement device 51 in the multiple-vehicle semi-self-service registration mode receives (directly or indirectly via another device) registration information transmitted by the other registered settlement device 51 (specifically, the registered settlement device 51 in the multiple-vehicle semi-self-service registration mode) to settle the merchandise registered by the other registered settlement device 51 (registered settlement device 51 in the multiple-vehicle semi-self-service registration mode).
[0053] The registered settlement device 51 in the multiple-machine semi-self-service registration mode may issue a bill and have another registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode) settle the merchandise registered by that registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode). In other words, the registered settlement device 51 in the multiple-machine semi-self-service payment mode may settle the merchandise registered by the other registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode) by reading a code printed on a bill issued by the other registered settlement device 51 (registered settlement device 51 in the multiple-machine semi-self-service registration mode).
[0054] The above-mentioned operation in each operation mode is an example. For example, the registered settlement device 51 in the multiple-machine semi-self-service registration mode may transmit registration information to the registered settlement device 51 in the face-to-face semi-self-service mode or the registered settlement device 51 in the full self-service mode, or may issue a bill. In other words, the POS terminal in the face-to-face semi-self-service mode (as well as the registered settlement device 51 in the full self-service mode) may settle the product registered by the registered settlement device 51 in the multiple-machine semi-self-service registration mode. Also, for example, the registered settlement device 51 in the face-to-face semi-self-service mode may transmit registration information to the registered settlement device 51 in the full self-service mode or the registered settlement device 51 in the multiple machine semi-self-service settlement mode, or may issue a bill. In other words, the registered settlement device 51 in the full self-service mode (as well as the registered settlement device 51 in the multiple machine semi-self-service settlement mode) may settle the product registered by the registered settlement device 51 in the face-to-face semi-self-service mode. Also, for example, a registered settlement device 51 in face-to-face semi-self-service mode may transmit registration information or issue a bill to another registered settlement device 51 in face-to-face semi-self-service mode. In other words, a registered settlement device 51 in face-to-face semi-self-service mode may settle payments for products registered by another registered settlement device 51 in face-to-face semi-self-service mode.
[0055] (Registration settlement device 52) The registration and settlement device 52 is a full self-service registration and settlement device. Functionally, the registration and settlement device 52 is equivalent to the registration and settlement device 51 fixed in the full self-service mode. Whereas the registration and settlement device 51 is also intended for use by store clerks (face-to-face self-service mode, registration-only mode), the registration and settlement device 52 is not intended for use by store clerks. Therefore, the registration and settlement device 52 does not have the store clerk-side display unit, key operation unit, store clerk-side scanner unit, etc., that the registration and settlement device 51 has. As other points are common to the registration and settlement device 51, a description of the appearance and configuration example of the registration and settlement device 52, including illustrations, will be omitted.
[0056] (Registration device 53) FIG. 6 is a diagram for explaining the appearance of registration device 53. FIG. 7 is an example of the configuration of registration device 53. In FIG. 6 and FIG. 7, the same parts are given the same reference numerals. Registration device 53 includes a CPU 301, a ROM 302, a RAM 303, a hard disk 304, a customer display unit 305, a store clerk display unit 310, a key operation unit 311, a scanner unit 312, a printer unit 313, a voice output unit 314, and a communication unit 315. These can communicate with each other via a bus. Registration device 53 may further include a card settlement unit (a card settlement unit similar to card settlement unit 108 of settlement device 50) and the like.
[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 similar to the CPU 101, ROM 102, RAM 103, hard disk 104, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the explanation will be omitted.
[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 where products are registered by the store clerk, the customer-side display unit 305 does not basically accept inputs for registering products, but does accept, for example, inputs for confirming the age of the customer with respect to the products registered by the store clerk.
[0059] The store clerk's display unit 310 is a touch display that displays various information to the store clerk and receives various inputs from the store clerk. The key operation section 311 has various buttons arranged thereon that are operated by the store clerk.
[0060] Scanner unit 312 is a scanner unit for store clerks, and optically reads various information. Specifically, scanner unit 312 scans codes attached to products and reads product codes (JAN codes, etc.). Scanner unit 312 may also scan codes attached to gift certificates and various cards and read the respective information. Scanner unit 312 may also scan codes attached to the name tags, etc. of store clerks and read the store clerk codes.
[0061] Scanner unit 312 is used when a store clerk registers a product, but the store clerk may register the product by other methods. For example, if a key corresponding to a product (such as a key corresponding to a sports newspaper) is arranged on key operation unit 311, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on store clerk-side display unit 310, the store clerk may operate that preset key to register the product.
[0062] The printing unit 313, for example, prints and issues various media (e.g., receipts). Various media are issued from an issuing port 313a and handed to the customer by a store clerk. Note that the registration device 53 does not issue receipts when sending registration information to another device (such as the settlement device 54). Also, if the registration device 53 is configured to include a card payment unit, the printing unit 313 may print and issue a receipt after payment is made by the card payment unit.
[0063] (Payment device 54) FIG. 8 is a diagram for explaining the external appearance of settlement device 54. FIG. 9 is an example of the configuration of settlement device 54. In FIG. 8 and FIG. 9, the same parts are given the same reference numerals. Settlement 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 machine (cash payment unit) 409, a store clerk side display unit 410, a printing unit 413, an audio output unit 414, and a communication unit 415. These can communicate with each other via a bus.
[0064] The CPU 401, ROM 402, RAM 403, hard disk 404, card settlement unit 408, change machine 409, audio output unit 414, and communication unit 415 of the settlement device 54 are similar to the CPU 101, ROM 102, RAM 103, hard disk 104, card settlement unit 108, change machine 109, audio output unit 114, and communication unit 115 of the settlement device 50, so some or all of the description will be omitted.
[0065] Customer display unit 405 is a touch display that displays various information to the customer and accepts various inputs from the customer. For example, customer display unit 405 accepts input for confirming the amount inserted (deposited amount) (input to execute payment). In addition, if settlement device 54 is configured to include a card payment unit in addition to change machine 409, customer display unit 405 accepts input for selecting a payment method (payment type) (selection of whether to use cash payment via change machine 409 or various non-cash payments via the card payment unit).
[0066] The scanner unit 406 may, for example, scan codes attached to gift certificates and various cards to read the respective information. The scanner unit 406 may also scan codes attached to the name tags of store clerks and read the store clerk codes. The scanner unit 406 may also scan codes printed on bills and read the information required for the settlement process. The settlement device 54 is a device that settles the bill based on registration information registered by another device (e.g., the registration device 53, etc.), and for example, when adding a product, the scanner unit 406 may scan codes attached to the products and read the product codes (JAN codes, etc.).
[0067] The store clerk's display unit 410 displays various information to the store clerk. Note that the store clerk's display unit 410 may be a touch display and may receive various inputs from the store clerk. The printing unit 413 prints and issues various media (for example, receipts).
[0068] The above describes the installed cash registers (settlement device 50, registered settlement device 51, registered settlement device 52, registered device 53, settlement device 54) installed in the store, but the configuration of each installed cash register is an example. For example, in the above description, the settlement device 50 is configured to include both the card payment unit (non-cash payment unit) 108 and the change machine (cash payment unit) 109, but the settlement device 50 may be configured to include either the card payment unit 108 or the change machine 109. The same applies to the registered settlement device 51, registered settlement device 52, and settlement device 54.
[0069] (Example of display on mobile terminal 60) FIG. 10 is a display example of the mobile terminal 60. FIG. 11 is a display example of the mobile terminal 60. FIG. 10(A) is a start screen (menu screen) of service A. When using (registering) service A, the mobile terminal 60 displays a start screen such as that shown in FIG. 10(A). Various buttons are arranged on the start screen. For example, the start screen has a start shopping button BT600 that accepts an instruction to start shopping. When a customer wants to start shopping, they operate the start shopping button BT600.
[0070] Fig. 10(B) is a registration screen (registration screen before registering one item of merchandise; initial registration screen) that is displayed after the shopping start button BT600 is operated on the start screen of Fig. 10(A). The upper side of the registration screen is a captured image display area HR601 that mainly displays captured images. The lower side of the registration screen is a registration information display area HR602 that mainly displays registration information for the merchandise.
[0071] Fig. 10(C) is a registration screen when the barcode attached to the product (XXX bread) is imaged on the registration screen of Fig. 10(B). That is, when a customer registers a desired product (a product to be purchased), the barcode attached to the product is read as shown in Fig. 10(C).
[0072] FIG. 10(D) is a registration screen after the product registration is completed (registration screen after product registration). Specifically, the mobile terminal 60 transmits the product code acquired from the barcode to the cloud server 20. The cloud server 20 refers to the product master and acquires the product name "XXX bread" and the price "¥220" based on the product code. The cloud server 20 stores the product information (product code, product name "XXX bread", quantity "1", price "¥220", etc.) as transaction information (cart information) of the transaction, and transmits the product information (product name "XXX bread", price "¥220", etc.) to the mobile terminal 60. The mobile terminal 60, which has received the product information from the cloud server 20, reflects the product information of the product in the registration information display area HR602. Specifically, as shown in Fig. 10(D), the mobile terminal 60 displays the registered information of the product (product name "XX bread", quantity "1", price "¥220") (symbol a), and displays total information (estimated total "1 item ¥220") (symbol b). The mobile terminal 60 displays part of the registered information (quantity) as a quantity button BT603. The quantity button BT603 is a button for changing the quantity.
[0073] After registering a product (one item of product), the mobile terminal 60 displays an operable Proceed to Checkout button BT604 for accepting checkout instructions, as shown in Fig. 10(D). When the customer wishes to proceed to payment (checkout) (when completing product registration), the customer operates the Proceed to Checkout button BT604.
[0074] FIG. 11(A) shows a registration screen after the registration of the second item (XX Oolong Tea) is completed following the scene of FIG. 10(D). That is, the mobile terminal 60 transmits the product code obtained from the barcode attached to the second item to the cloud server 20. The cloud server 20 refers to the product master and obtains the product name "XX Oolong Tea" and the price "¥150" based on the product code. The cloud server 20 stores the product information (product code, product name "XX Oolong Tea", quantity "1", price "¥150", etc.) as transaction information of the transaction, and transmits the product information (product name "XX Oolong Tea", price "¥150", etc.) to the mobile terminal 60. The mobile terminal 60, which has received the product information from the cloud server 20, reflects the product information of the second item in the registration information display area HR602. Specifically, as shown in FIG. 11(A), the mobile terminal 60 displays (adds) the registration information for the product (product name "XX Oolong Tea", quantity "1", price "¥150") and displays (updates) the total information (estimated total "2 items ¥370")
[0075] When a certain product a becomes a reserved product (described later) in a transaction of a certain mobile terminal 60, the cloud server 20 stores information that the product a is a reserved product as transaction information of the mobile terminal 60. Therefore, the transaction status management device 40 can refer to the transaction information stored in the cloud server 20 and recognize that the product a is a reserved product in the transaction of the mobile terminal 60 (or that the product a exists as a reserved product).
[0076] FIG. 11(B) shows a two-dimensional code display screen that is displayed after the button BT604 for proceeding to checkout is operated following the scene in FIG. 11(A). The two-dimensional code display screen shows a two-dimensional code 605 for checkout. The two-dimensional code 605 for checkout is a two-dimensional code of information required for executing checkout processing. For example, the two-dimensional code 605 for checkout is a two-dimensional code of transaction identification information (cart identification information) that identifies transaction information of the transaction from among multiple pieces of transaction information stored in the cloud server 20. Note that the information to be two-dimensionally coded does not have to be transaction identification information, as long as the transaction information of the transaction can be obtained after reading. For example, the two-dimensional code 605 for checkout may be a two-dimensional code of location information of the transaction information of the transaction (a storage location in the sales system 1, such as a Uniform Resource Identifier (URI)).
[0077] Additionally, an estimated total display area HR606 and a back button BT607 are arranged on the two-dimensional code display screen. In the example of FIG. 11(B), the estimated total display area HR606 displays the estimated total "2 items ¥370." The back button BT607 is a button for returning to shopping (restarting shopping). When the back button BT607 is operated, the mobile terminal 60 displays a registration screen (the registration screen displayed immediately before the Proceed to Checkout button BT604 is operated) instead of the two-dimensional code display screen.
[0078] Fig. 11(C) shows how the settlement device 50 reads the settlement two-dimensional code 605. After completing product registration, the customer causes the settlement device 50 to read the settlement two-dimensional code 605 displayed on the mobile terminal 60, as shown in Fig. 11(C).
[0079] (Example of display on settlement device 50) 12 and 13 are examples of displays on the settlement device 50. Fig. 12 shows an initial screen. When settling the bill for service A, the settlement device 50 displays the initial screen as shown in Fig. 12.
[0080] The initial screen displays a message and a guide map to read the two-dimensional code 605 (QR code (registered trademark) in the figure) for settlement displayed on the mobile terminal 60. Also arranged on the initial screen are a store clerk call button BT501, a balance inquiry button BT502, and language switch buttons BT503 to BT505. The store clerk call button BT501 is a button for calling a store clerk. The balance inquiry button BT502 is a button for inquiring about the balance of various cards. The language switch button BT503 is a button for switching the display (text) on the initial screen from Japanese to English. The language switch button BT504 is a button for switching to Chinese. The language switch button BT505 is a button for switching to Korean.
[0081] After completing product registration, the customer follows the instructions on the initial screen and has the settlement device 50 read the two-dimensional settlement code 605 displayed on the mobile terminal 60 (FIG. 10(C)).
[0082] 13 is a product list screen displayed after reading the two-dimensional settlement code 605, following the scene in Fig. 12. That is, when the settlement device 50 reads the two-dimensional settlement code 605, it displays the product list screen as shown in Fig. 12.
[0083] The product list screen has a product list display area HR510, a product quantity by price range display area HR511, and a total display area HR512. In addition, a store clerk call button BT501 and a checkout button BT509 are arranged on the product list screen. The checkout button BT509 is a button for confirming that there are no problems with the contents displayed on the product list screen and for proceeding with the process. When the checkout button BT509 is operated, the settlement device 50 displays, for example, a payment type selection screen (not shown).
[0084] The product list display area HR510 is an area for displaying a list of products to be settled (purchased). The settlement device 50 displays, in the product list display area HR510, a list of products (product name, quantity, price) included in the transaction information acquired from the cloud server 20 by reading the settlement two-dimensional code 605. In the example of FIG. 13, the settlement device 50 displays XX bread and XX oolong tea in the product list display area HR410.
[0085] The price range item quantity display area HR511 is an area for displaying the quantity of items to be paid for (purchased) by price range (1000 yen or more, 500 yen or more but less than 1000 yen, 200 yen or more but less than 500 yen, less than 200 yen).
[0086] The total display area HR512 is an area for displaying the total of the transaction. In the example of FIG. 13, the settlement device 50 displays in the total display area HR512 a total number of items of 2 (indicated as "Total of 2 items" in the figure), an estimated total amount of 370 yen (indicated as "Estimated total (amount displayed on smartphone) 370 yen"), and a final total amount of 370 yen (indicated as "Final total (amount to be paid) 370 yen" in the figure). The estimated total amount of 370 yen is the total amount displayed on the mobile terminal 60 (i.e., the total amount before the process related to the sale price (described later) is executed). The final total amount of 370 yen is the total amount recalculated by the settlement device 50 (i.e., the total amount after the process related to the sale price (described later) is executed).
[0087] (Processing of special sale prices) When the settlement device 50 acquires transaction information from the cloud server 20 after reading the settlement two-dimensional code 605, it refers to the sale file and judges whether the product included in the transaction information matches the sale conditions (i.e., whether a sale (discount, discount, etc.) is applied). If the sale conditions match, it acquires the sale contents (sale price, etc.) from the sale file, recalculates the total amount, and reflects it in the transaction information. Specifically, the settlement device 50 stores the sale price, etc. acquired from the sale file additionally (separately) without erasing (overwriting) the product price, etc. before the sale price is applied, and stores the recalculated total amount additionally (separately) without erasing the total amount before the recalculation. In other words, the settlement device 50 refers to the sale file that was not referenced when the product was registered on the mobile terminal 60, and if the conditions for applying the sale price (sale) are met, it acquires the sale price, etc. to be applied from the sale file, recalculates the total amount, and reflects it in the transaction information. If the conditions for the sale are not met, the settlement device 50 does not apply the sale price, so the final total amount is the same as the estimated total amount. The example in Fig. 13 is a display example when the conditions for the sale are not met (when the sale price is not applied).
[0088] Fig. 14 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, the sequence diagram of Fig. 14 shows an example of the processing of the mobile terminal 60 and the cloud server 20 (product registration processing in service A) from when one product is registered on the mobile terminal 60 until the two-dimensional code for payment 605 is displayed. The left side of Fig. 14 shows the processing of the mobile terminal 60, and the right side shows the processing of the cloud server 20. It is assumed that at the start of the sequence diagram of Fig. 14 (the start of the processing of step S1 for the first time), the mobile terminal 60 displays an initial registration screen as shown in Fig. 10(B).
[0089] Step S1: The mobile terminal 60 reads the barcode attached to the product in response to a reading operation by the customer. That is, the mobile terminal 60 acquires the product code from the barcode attached to the product in response to a reading operation by the customer. Step S2: The mobile terminal 60 transmits to the cloud server 20 transaction identification information for identifying the transaction information of the transaction, and the product code acquired in step S1.
[0090] Step S3: The cloud server 20 receives the transaction identification information and the product code. Step S4: Cloud server 20 updates the transaction information of the transaction (transaction information corresponding to the transaction identification information) based on the product code. That is, cloud server 20 acquires (extracts) the product name and price corresponding to the product code received in step S3 from the product master, and stores the product code, product name, quantity (1), and price in the transaction information corresponding to the transaction identification information received in step S3.
[0091] Step S5: The cloud server 20 transmits product information (such as product name and price) of the product code to the mobile terminal 60. For example, the cloud server 20 generates screen information that reflects the contents of the updated transaction information, and transmits it to the mobile terminal 60.
[0092] Step S6: The mobile terminal 60 receives the product information (screen information) of the product code. Step S7: The mobile terminal 60 updates the registration screen based on the information (screen information) received in step S6. Steps S1 to S7 are repeatedly executed by reading the barcode attached to the product.
[0093] Step S8: The mobile terminal 60 generates a two-dimensional code 605 for payment based on the customer's payment instructions (operation of the Proceed to Payment button BT604) and displays it on the two-dimensional code display screen. Then, the sequence diagram in FIG. 9 ends.
[0094] Fig. 15 is a sequence diagram showing an example of the processing of the settlement device 50 and cloud server 20. Specifically, the sequence diagram of Fig. 15 shows an example of the processing of the settlement device 50 and cloud server 20 (settlement processing in service A) from when the settlement two-dimensional code 605 is read by the settlement device 50 to when the product list screen is displayed. The left side of Fig. 15 shows the processing of the settlement device 50, and the right side shows the processing of the cloud server 20. It is assumed that at the start of the sequence diagram of Fig. 15, the settlement device 50 is displaying an initial screen such as that shown in Fig. 12.
[0095] Step S11: In response to a reading operation by the customer, the settlement device 50 reads the settlement two-dimensional code 605 displayed on the mobile terminal 60. That is, the settlement device 50 obtains transaction identification information that identifies the transaction information of the transaction. Step S12: The settlement device 50 requests transaction information of the transaction from the cloud server 20. For example, the settlement device 50 transmits request information (transaction information acquisition request information) including transaction identification information that identifies the transaction information of the transaction to the cloud server 20.
[0096] Step S13: The cloud server 20 receives the request (transaction information acquisition request information). Step S14: In response to the request, the cloud server 20 transmits the transaction information of the transaction to the settlement device 50. For example, the cloud server 20 transmits to the settlement device 50 the transaction information corresponding to the transaction identification information included in the transaction information acquisition request information received in step S13.
[0097] Step S15: The settlement device 50 receives and stores the transaction information of the transaction. Step S16: The settlement device 50 refers to the sale file, and if the sale conditions match, obtains the details of the sale (sale price, etc.), recalculates the total amount, and reflects it in the transaction information (additionally stores it). The details of step S16 have already been explained in "Processing related to the sale price", so they will be omitted here. Step S17: The settlement device 50 displays a product list screen based on the transaction information, and the sequence diagram in FIG. 15 ends.
[0098] (Transaction status management device 40) The transaction status management device 40 displays a management screen for managing (monitoring) the installed cash registers (settlement device 50, registered settlement device 51, registered settlement device 52, registered device 53, settlement device 54) in the store and the mobile terminals (mobile terminal 60, etc.) present in the store.
[0099] In the following explanation, the settlement device 50, registration settlement device 51, registration settlement device 52, registration device 53, and settlement device 54 installed in the store are collectively referred to as installed cash registers. It is also assumed that there are 15 installed cash registers (No. 1 to No. 15 below) in the store, and one transaction status management device 40 in the store. It is also assumed that the store contains a mixture of mobile terminals 60 that are personal possessions of customers and mobile terminals 60 lent by the store (including the type fixed to shopping carts).
[0100] The types of equipment for Units 1 to 15 (alternative names in parentheses) are as follows: (1) Machines 1 to 3 are settlement devices 50 (portable settlement machines). Each of Machines 1 to 3 is equipped with a card settlement section and a cash settlement section. (2) Machines 4 to 6 are registered settlement devices 51 (multiple operation mode machines (multiple operation mode registered settlement machines)). Machines 4 and 5 are equipped with a card settlement section and a cash settlement section. Machine 6 is equipped with a card settlement section but does not have a cash settlement section. (3) Machines 7 to 9 are registration settlement devices 52 (fully self-service machines). Machines 7 and 8 are equipped with a card settlement section and a cash settlement section. Machine 9 does not have a card settlement section, but does have a cash settlement section. (4) Machines 10 and 13 are registration devices 53 (semi-self-service registration machines). (5) Machines 11, 12, 14, and 15 are adjustment devices 54 (semi-self-service adjustment machines).
[0101] The information (static information) regarding the installed cash registers (No. 1 to No. 15) described above may be stored in a device basic file that is updated when a device is introduced or removed. The device basic file may be stored in a location accessible by the transaction status management device 40 (e.g., the memory of the transaction status management device 40, the memory of the headquarters server 10). The device basic file may store images (photos, illustrations, etc.) of each device. The device basic file may store features of each device (e.g., the color of the casing, the external shape of the display screen (horizontal / vertical, size)). The device basic file may store installation information (position, orientation) of each device within the store.
[0102] In the following explanation, the current operating mode of machine 4 is assumed to be full self-service mode. The current operating modes of machines 5 and 6 are assumed to be face-to-face self-service mode. Furthermore, machine 1 is currently running short on change (500 yen coins) (near change end), and machine 5 is currently running short on receipt paper (near paper end).
[0103] The information (fluid information) about the above-mentioned installed registers (No. 1 to No. 15) can be referred to in devices that require them. For example, when the operating mode is switched in a mode-changeable installed register (No. 4 to No. 6), the installed register may notify the transaction status management device 40 of the information indicating that the operating mode has been switched. Also, for example, when the change is near-end in a device equipped with a cash settlement unit (No. 1 to No. 5, No. 7 to No. 9, No. 11, No. 12, No. 14, No. 15), the installed register may notify the transaction status management device 40 of the information indicating that the change is near-end. The same applies when the paper is near-end, etc. The same applies to the operating status of each device (in use / on standby, user (clerk, member)), etc.
[0104] 16 to 23 are examples of displays of the transaction status management device 40. The transaction status management device 40 displays a management screen for managing (monitoring) devices (installed cash registers such as the settlement device 50) installed in the store and mobile terminals (mobile terminal 60, etc.) present in the store.
[0105] The management screens of FIG. 16, FIG. 17, FIG. 19, FIG. 20, and FIG. 21 are examples of management screens (sometimes referred to as installed register management screens) for managing installed registers. FIG. 22 and FIG. 23 are examples of management screens (sometimes referred to as mobile terminal management screens) for managing mobile terminals. At the top of the management screen, "Handling person number: 9999 Handling person name: XXX 2021 / XX / XX 15:30" is displayed. The handling person number and handling person name are the clerk number and name of the clerk operating the transaction status management device 40 (i.e., the clerk displaying the management screen). "2021 / XX / XX 15:30" is the current date and time. The management screen has tabs ("Installed register" and "Mobile terminal"). The clerk operates (selects) the tab to switch between the installed register management screen and the mobile terminal management screen. In other words, the transaction status management device 40 switches between the installed register management screen and the mobile terminal management screen in response to the operation of the tab.
[0106] (Installation cash register management screen) For example, as shown in FIG. 16, the installed register management screen has multiple buttons (All button BT401, Semi-self-service machine button BT402, Full-self-service machine button BT403, Registration machine 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 for displaying all installed cash registers (cash registers 1 to 15) in the store on the installed cash register management screen. Figs. 16 and 17 show the display contents of the installed cash register management screen when the ALL button BT401 is operated. Fig. 16 shows the first page, on which information on each of cash registers 1 to 8 is displayed. Fig. 17 shows the second page, on which information on each of cash registers 9 to 15 is displayed. The arrow button BT410 is operated to switch between the first and second pages. Note that in Figs. 16 and 17, the thick frame of the ALL button BT401 indicates that the button (ALL button BT401) has been operated.
[0108] Fig. 18(A) is an enlarged view of the display area (A in the figure) relating to Unit 2 shown in Fig. 16. Fig. 18(B) is an enlarged view of the display area (B in the figure) relating to Unit 6 shown in Fig. 16.
[0109] As shown in Figure 18(A) (as well as 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 characteristics 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 Fig. 18(A), the transaction status management device 40 displays "No. 2 Portable Recording and Settlement Machine" in the device name display area HR420. In the example shown in Fig. 18(B), the transaction status management device 40 displays "No. 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 the installed cash register has a card payment section or a cash payment section. In the example shown in FIG. 18(A), the transaction status management device 40 displays "Cash: O" and "Non-cash: O" in the device name display area HR420. In the example shown in FIG. 18(B), the transaction status management device 40 displays "Cash: X" and "Non-cash: O" in the device name display area HR420. "O" indicates presence and "X" indicates absence.
[0112] Furthermore, if the installed register is an installed register (No. 4 to No. 6) having multiple operation modes, the transaction status management device 40 displays the current operation mode in the device name display area HR420. In the example shown in FIG. 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 register is in a face-to-face self-service mode, that is, an operation mode in which a store clerk and a customer face each other across the register, the store clerk registers products using one side (store clerk side) of the registration settlement device 51, and the customer settles the payment using the other side (customer side) of the registration settlement device 51. The transaction status management device 40 may receive information indicating that the operation mode has been switched from an installed register having multiple operation modes, and display the current operation mode of the installed register in the device name display area HR420.
[0113] (Operation mode operation area SR430) If the installed register is an installed register (No. 4 to No. 6) that has multiple operation modes, the transaction status management device 40 accepts operations related to the operation mode in the operation mode operation area SR430. Specifically, as shown in Fig. 18(B), if the installed register is an installed register that has multiple operation modes, the current operation mode is displayed in the operation mode operation area SR430, and a schedule button BT431 and a switch button BT432 are arranged. Note that, in the case of an installed register that does not have multiple operation modes (specifically, in the case of a device other than a multiple operation mode machine), the operation mode operation area SR430 is blank, as shown in Fig. 18(A).
[0114] The schedule button BT431 is a button for confirming (displaying) the switching schedule (switching schedule information) of the operation mode of the installed cash register. The schedule button 431 shown in FIG. 18(B) displays "Schedule (Full Self-Service in 50 Minutes)", but "(Full Self-Service in 50 Minutes)" is information based on the switching schedule information of the installed cash register, and indicates that the installed cash register is scheduled to switch to the full self-service mode in 50 minutes. The remaining time until the mode is switched 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 color of the button may be changed to highlight that the remaining time is short (the operation mode will be switched soon). Note that when there is no schedule for mode switching (or no schedule for mode switching within a predetermined time from the present (for example, within 1 hour)), the schedule button 431 simply displays "Schedule" as in the 4th and 5th machines shown in FIG. 17. Instead of simply displaying "Planned", it is possible to display "Planned (maintained)" to indicate that the current operation mode will be maintained, or to display "Planned ( )" to indicate that there is no plan by leaving the parentheses blank. Instead of or in addition to displaying the remaining time until the mode is switched, it is possible to display the time to switch the mode (in this example, "16:20", which is "50 minutes" after the current time "15:30").
[0115] The switching schedule information is a timetable including, for example, time (clock), operation mode, and person in charge (person who set it) (i.e., these can be input, modified, displayed, etc.). Note that, when the switching schedule information includes switching schedules for multiple installed cash registers, it includes the installed cash register (number), time, operation mode, and person in charge.
[0116] The switching schedule information may be stored, for example, in a location accessible by the transaction status management device 40 (for example, a memory unit of the transaction status management device 40, a memory unit of the installed register, or a memory unit of the headquarters server 10). When the Schedule button BT431 is operated, the transaction status management device 40, for example, displays a small screen in front of the installed register management screen, and displays the currently set switching schedule of the installed register's operation mode on the small screen. When the switching schedule of the installed register's operation mode is not currently set, the transaction status management device 40 may display, for example, "Not set" on the small screen. An OK button may be placed on the small screen, and the transaction status management device 40 may erase the small screen when the OK button is operated. The transaction status management device 40 may accept an operation to change the switching schedule on the small screen.
[0117] The switching button BT432 is a button for switching the operation mode of the installed cash register (specifically, the registered settlement device 51 having a plurality of operation modes). When the switching button BT432 is operated, the transaction status management device 40, for example, displays a small screen in front of the installed cash register management screen, and accepts a switching operation to another operation mode on the small screen (for example, displays a button for specifying the switching destination operation mode). When a switching operation to another operation mode is accepted on the small screen (for example, when a button for specifying one operation mode as the switching destination of the operation mode is operated), the transaction status management device 40, for example, transmits an operation mode switching command to the installed cash register to switch to the one operation mode for which the operation is accepted (directly or via another device such as the store controller 30). The transaction status management device 40 may transmit an operation mode switching command including a store clerk number (or a registered name such as a nickname). When the transaction status management device 40 accepts a switching operation to another operation mode, it erases the small screen. Also, an OK button may be placed on the small screen, and the transaction status management device 40 may erase the small screen when the OK button is operated.
[0118] The installed cash register that has received the operation mode switching command may display a message such as "You have been instructed to switch the operation mode to XX mode. Do you want to switch to XX mode?" and may display a small screen that can accept a confirmation operation for approval or disapproval (e.g., with a "Yes" button and a "No" button). The installed cash register that has received the operation mode switching command switches the operation mode in accordance with the operation mode switching command if an operation to approve the command (operation of the "Yes" button) is performed on the small screen, and does not switch the operation mode if an operation to disapproval is performed (operation of the "No" button). In other words, when remotely switching the operation mode of the installed cash register by the transaction status management device 40, the instruction (operation mode switching command) of the transaction status management device 40 is prioritized in principle, but the clerk at the installed cash register that has received the instruction (received the operation mode switching command) may not follow the instruction depending on the status of the installed cash register.
[0119] The installed cash register that has received the operation mode switching command may switch the operation mode in accordance with the operation mode switching command if no confirmation operation is performed within a certain time after the small screen starts to be displayed. As a result, for example, when the registered settlement device 51 whose current operation mode is the full self-service mode (the same applies when other devices (e.g., settlement device 54) are mode-changeable and in the full self-service mode) receives the operation mode switching command, it switches to the other operation mode after a certain time has elapsed (however, if a transaction is in progress when the certain time has elapsed, after the transaction is completed), without waiting for a confirmation operation by a store clerk. When the registered settlement device 51 whose current operation mode is the full self-service mode (the same applies when other devices are mode-changeable and in the full self-service mode) receives the operation mode switching command, it may immediately switch to the other operation mode without displaying the small screen (however, if a transaction is in progress when the certain time has elapsed, after the transaction is completed).
[0120] In addition, a cash register that receives an operation mode switching command may switch operation modes depending on the status of the cash register (for example, after a transaction is completed if a transaction is in progress) without displaying the small screen, regardless of the current operation mode (whether or not a store clerk is present).
[0121] When the installed cash register switches the operation mode in accordance with the operation mode switching command (the same applies when the operation mode is switched due to other conditions such as the passage of time), the installed cash register notifies the transaction status management device 40 of the change (directly or via another device such as the store controller 30). Note that the installed cash register may notify other devices (other store controllers 30) in addition to the transaction status management device 40. Note that the installed cash register may notify the transaction status management device 40 or the like of the current operation mode as appropriate (for example, after the transaction is completed) in addition to switching the operation mode. Note that the installed cash register may also notify the transaction status management device 40 or the like of the current operation mode even if the installed cash register does not switch the operation mode. Note that instead of or in addition to the notification from the installed cash register, the management side (the transaction status management device 40 or the like) may inquire and confirm the operation mode of the installed cash register as appropriate (for example, every 10 seconds) (in other words, the installed cash register may notify the current operation mode in response to an inquiry).
[0122] The transaction status management device 40 may refer to the operation mode switching schedule information of the installed cash register, and if the operation mode of the installed cash register is scheduled to be switched soon (for example, in 10 minutes), may display that fact in the operation mode operation area SR430. Also, if the mode switching is not performed according to the switching schedule information (for example, the operation mode is not basically switched while a transaction is ongoing), the transaction status management device 40 may display that fact in the operation mode operation area SR430.
[0123] In addition, the transaction status management device 40 has been described as displaying a small screen when the switching button BT432 is operated and accepting a switching operation to another operation mode on the small screen. However, the control may be different depending on whether or not a switching schedule is set for the installed cash register. For example, when a switching schedule is not set, the transaction status management device 40 may allow all operation modes to be designated as a switching destination after the switching button BT432 is pressed (a small screen may be displayed in which all operation modes can be designated as a switching destination based on the pressing of the switching button BT432). On the other hand, when a switching schedule is set, the transaction status management device 40 may allow only the operation mode set (scheduled) in the switching schedule to be designated as a switching destination after the switching button BT432 is pressed (a small screen may be displayed in which only the operation mode set (scheduled) in the switching schedule can be designated as a switching destination based on the pressing of the switching button BT432). In other words, when a switching schedule is set, the switchable operation modes (selection of operation modes) may be limited.
[0124] As described above, the operation mode switching schedule (switching schedule) is confirmed with the schedule button BT431, and the actual switching of the operation mode is performed by operating the switch button BT432. Therefore, even if the scheduled time arrives, the operation mode will not be switched 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 passed, the transaction status management device 40 highlights the fact on the schedule button BT431 (for example, "Schedule (full self-change time)", "Schedule (full self-change time passed)") and may display a message (for example, "The scheduled switching time has arrived. Please be careful" or "The scheduled switching time has passed. Please be careful") in a place other than the schedule button BT431 (for example, the top of the screen, a small screen). Note that "Schedule (full self-change time passed)" and "The scheduled switching time has passed. Please be careful" may also include the elapsed time and be expressed as, for example, "Schedule (full self-change time passed 10 minutes)" or "The scheduled switching time has passed 10 minutes. Please be careful." The "10 minutes" may be displayed as a count-up.
[0125] In the above, the operation mode is not automatically switched (unless the switching button BT432 is operated) even when the scheduled time in the switching schedule information is reached. However, the operation mode may be automatically switched (without the switching button BT432 being operated) based on the switching schedule information. For example, the transaction status management device 40 may transmit an operation mode switching command to a certain mobile terminal 60 without the operation of a store clerk based on the switching schedule information of the mobile terminal 60. When transmitting the operation mode switching command without the operation of a store clerk, the transaction status management device 40 may transmit an operation mode switching command including information that the command is automatically transmitted. The transaction status management device 40 may display a small screen for confirming whether or not the command can be transmitted (OK / NG) before transmitting the operation mode switching command, and may transmit the operation mode switching command after the store clerk operates OK (or after a certain time has elapsed if no confirmation operation is performed within a certain time after the start of displaying the small screen). The transaction status management device 40 may transmit an operation mode switching command including information that the store clerk operates OK (or that no confirmation operation is performed).
[0126] In an embodiment in which the operation mode is automatically switched based on the switching schedule information, the switching button BT432 may or may not be provided. When the switching button BT432 is not provided, the operation mode is switched remotely simply according to the switching schedule information. When the switching button BT432 is provided, the operation mode is switched remotely according to the operation of the switching button BT432 in addition to the switching schedule information. Also, the switching button BT432 may be displayed so as to be operable based on a predetermined condition. For example, the switching button BT432 may be displayed so as to be operable only for a predetermined period (for example, 10 minutes) after the automatic switching of the operation mode (it may be displayed so as to be hidden or inoperable outside the above-mentioned predetermined period).
[0127] Depending on whether the operation mode switching command sent by the transaction status management device 40 is a result of the operation of the switch button BT432 or an automatic transmission, the installed cash register that receives the operation mode switching command may display or not display a small screen (for example, if the operation mode switching command is a result of the operation of the switch button BT432, the small screen may not be displayed, and if the operation mode switching command is sent automatically, the small screen may be displayed. The display / not displaying may be reversed). Depending on whether the operation mode switching command automatically sent by the transaction status management device 40 is a result of the store clerk performing a confirmation operation (OK operation), the installed cash register that receives the operation mode switching command may display or not display a small screen (for example, if the operation mode switching command is a result of the confirmation operation, the small screen may not be displayed, and if the operation mode switching command is not a result of the confirmation operation, the small screen may be displayed. The display / not displaying may be reversed).
[0128] (Operation status display area HR440) The transaction status management device 40 displays the operation status of the installed cash register in the operation status display area HR440. In the example shown in FIG. 18(A), the transaction status management device 40 displays "Operation status: In use (settlement in progress)" as the operation status of the second cash register in the operation status display area HR440. In the example shown in FIG. 18(B), the transaction status management device 40 displays "Operation status: In use (settlement in progress)" as the operation status of the sixth cash register in the operation 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 operation status of the installed cash register in the device name display area HR420.
[0129] The transaction status management device 40 also displays information about the operator of the installed cash register in the operation status display area HR440. In the example shown in Fig. 18(A), the transaction status management device 40 displays "Clerk: - Customer: C2" as the operator of the second cash register in the operation status display area HR440. In the example shown in Fig. 18(B), the transaction status management device 40 displays "Clerk: T2 (18:20) Customer: C25" as the operator of the sixth cash register in the operation status display area HR440.
[0130] "Staff:-" in the operation status display area HR440 shown in FIG. 18(A) indicates that the installed register (No. 2) is not being operated by a clerk. The No. 2 register (payment settlement device 50) is basically operated by a customer, so it is basically "Staff:-". "Customer: C2" in the operation status display area HR440 shown in FIG. 18(A) indicates that a customer with a membership number (customer identification information) "C2" is operating the installed register (No. 2). For example, the transaction status management device 40 obtains a membership number from the installed register and displays it in the operation status display area HR440. The membership number of the customer who uses the payment settlement device 50 (No. 1 to No. 3) is also displayed on the product list screen (see FIG. 13) of the payment settlement device 50, the start screen of service A of the mobile terminal 60 (FIG. 10(A), etc.), and the like.
[0131] The transaction status management device 40 may display the customer (member) name (or registered name) instead of or in addition to the membership number. The transaction status management device 40 may also display transaction identification information (cart identification information) that is generated on the cloud server 20 at the start of shopping and is linked to transaction information (product information) registered thereafter, instead of or in addition to the information about the member (member number, member name, etc.) described above. If the transaction status management device 40 cannot obtain any information about the member, it displays the transaction identification information (cart identification information). The same applies to the display of the membership number on the mobile terminal management screen (FIG. 22).
[0132] "Clerk: T2 (18:20)" in FIG. 18(B) indicates that the clerk with clerk number (customer identification information) "T2" is operating the installed cash register (No. 6) (or is logged in), and that the clerk's scheduled time to leave work is "18:20". The transaction status management device 40, for example, obtains the clerk 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 clerk's scheduled attendance time from the attendance server, for example, and displays it in the operation status display area HR440. Note that the clerk's name (or registered name) may be displayed instead of or in addition to the clerk number.
[0133] In addition, the clerk may be notified that the scheduled time to leave work has arrived, that the scheduled time to leave work is approaching, or that the scheduled time to leave work has already passed. For example, a button (a working time prompt confirmation button) may be arranged in the operation status display area HR440, and when the working time prompt confirmation button is operated, the transaction status management device 40 may transmit (directly or via another device such as the store controller 30) working time prompt information to notify the scheduled time to leave work, etc., to the installed cash register. For example, in the example of the sixth machine shown in FIG. 18(B), when a clerk (e.g., a manager) using the transaction status management device 40 operates the working time prompt confirmation button, the transaction status management device 40 transmits working time prompt information for the clerk "T2" to the sixth machine. In addition, the sixth machine that receives the working time prompt information may display a message according to the time of reception. For example, if the clock-out promotion information is received at the clock-out time (18:20), it may display "It is scheduled clock-out time (18:20)," if it is received before the clock-out time (18:10), it may display "It is 10 minutes before the scheduled clock-out time (18:20)," and if it is received after the clock-out time (18:30), it may display "It has been 10 minutes since the scheduled clock-out time (18:20)." Note that if the clock-out promotion information is received before the clock-out time, it may wait until the scheduled clock-out time and display "It is scheduled clock-out time" at the scheduled clock-out time.
[0134] In the example of machine No. 5 shown in FIG. 16, as shown by "Clerk: T1 (15:00)", the scheduled time of leaving work for the clerk with clerk 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, as described above, machine No. 5 (clerk T1) is notified that the scheduled time of leaving work has already passed. The notification that the scheduled time of leaving work has already passed may be a more emphasized notification than a notification to the clerk that the scheduled time of leaving work has arrived or that the scheduled time of leaving work is approaching.
[0135] "Customer: C25" in the operation status display area HR440 shown in FIG. 18(B) indicates that a customer with membership number "C25" is operating the installed cash register (machine 2). For customers using registered settlement devices 51 (machines 4-6) (the same goes for registered settlement devices 52 (machines 7-9) etc.), the membership number can be obtained, for example, from the customer's medium (for example, a membership card). If the membership number has not been obtained, the transaction status management device 40 displays "Customer: Unknown," for example, machine 5 shown in FIG. 16 and machine 11 shown in FIG. 17.
[0136] In addition, a Details button BT441 is arranged in the operation status display area HR440. The Details button BT441 is a button for confirming (displaying) detailed information such as the operation status of the installed cash register and the operator. When the Details button BT441 is operated, the transaction status management device 40 displays, for example, details about the transaction (when the cash register is in use, the presence or absence and contents (type) of reserved items (described later), the total amount, etc.), information about the store clerk (when the store clerk is operating, the start time of the store clerk on the same day, overtime status, etc.), and information about the customer (when the customer is operating and has a membership number, the customer's purchase history, the presence or absence and number of reserved items (described later) in the past, etc.). When the Details button BT441 is operated, the transaction status management device 40 may also display an image captured by an 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 basic file and displays an image (photo, illustration, etc.) of the installed cash register in the device image display area HR450. In the example shown in Fig. 18(A), the transaction status management device 40 displays an image GA451 of cash register No. 2 in the device image display area HR450. In the example shown in Fig. 18(B), the transaction status management device 40 displays an image GA451 of cash register No. 6 in the device image display area HR450.
[0138] Further, an enlarge button BT451 is arranged in the device image display area HR450. The enlarge button BT451 is a button that accepts an operation to enlarge the image GA451. When the enlarge button BT451 is operated, the transaction status management device 40, for example, displays a small screen in front of the installed cash register management screen, and displays a large-sized image GA451 of the installed cash register on the small screen. Note that an OK button may be arranged on the small screen, and the transaction status management device 40 may erase the small screen when the OK button is operated.
[0139] Furthermore, the transaction status management device 40 displays information regarding a call for a clerk, near-end of change, near-end of paper, etc., at the installed cash register in the device image display area HR450. In the example shown in FIG. 18(A), the transaction status management device 40 displays an icon ICN453 indicating that a call for a clerk has been made at the second cash register, and an icon ICN454 indicating that the second cash register is near-end of change (500 yen coins) in the device image display area HR450. The transaction status management device 40 may receive information such as a call for a clerk from the installed cash register and display an icon in the device image display area HR450. Note that, although a call for a clerk, near-end of change, near-end of paper, etc. are notified in the device image display area HR450 in this example, they may be notified in another area.
[0140] (Feature display area HR460) The transaction status management device 40, for example, refers to the device basic file and displays the characteristics of the installed cash register in the characteristics display area HR460. In the example shown in Fig. 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 characteristics display area HR460. In the example shown in Fig. 18(B), the transaction status management device 40 displays the characteristics of machine No. 6 in the characteristics display area HR460.
[0141] Machines 4 to 6 (registered settlement devices 51) are equipped with two display units (customer display unit 205, store clerk display unit 210), and in this example, information from customer display unit 205 (screen (portrait / landscape), screen (size)) is displayed in characteristic display area HR460. Information from store clerk display unit 210 may be displayed in characteristic display area HR460 instead of or in addition to the information from customer display unit 205. The same is true for machines 7 to 9 (registered settlement devices 52), 11, 12, 14, and 15 (settlement devices 54).
[0142] Additionally, machines 10 and 13 (registration device 53) are equipped with two display units (customer display unit 305 and store clerk display unit 310), and in this example, information from store clerk display unit 310 is displayed in characteristic display area HR460. Note that information from customer display unit 305 may be displayed in characteristic display area HR460 instead of or in addition to information from store clerk display unit 310.
[0143] Furthermore, a position button BT461 is arranged in the device image display area HR450. The position button BT461 is a button for displaying (confirming) the installation position of the installed cash register within the store, etc. When the position button BT461 is operated, the transaction status management device 40 displays a layout screen (described later) and also displays on the layout screen which cash register is installed so that it can be seen at a glance (details will be described later).
[0144] The semi-self-service machine button BT402 shown in FIG. 16 and the like is a button for displaying on an installed register management screen the installed registers (No. 5, No. 6, No. 11, No. 12, No. 14, No. 15) among the installed registers (No. 1 to No. 15) in the store that are used in a mode in which a store clerk registers products and a customer settles the bill. FIG. 19 shows the display contents of the installed register management screen when the semi-self-service machine button BT402 is operated. In FIG. 19, the thick frame of the semi-self-service machine button BT402 indicates that the button (semi-self-service machine button BT402) has been operated.
[0145] In the above, the semi-self-service dedicated machines (machines No. 11, No. 12, No. 14, and No. 15) are set as the display targets when the semi-self-service machine button BT402 is operated, but they may be excluded from the display targets when the semi-self-service machine button BT402 is operated. In other words, the display targets when the semi-self-service machine button BT402 is operated may be limited to the semi-self-service multiple operation mode machines (machines No. 5 and No. 6).
[0146] The Full Self-Service Machine Button BT403 is a button for displaying on the Installed Register Management Screen the installed registers (No. 1 to No. 4, No. 7 to No. 9) that are used in the store when customers register products and make payment. FIG. 20 shows the display contents of the Installed Register Management Screen when the Full Self-Service Machine Button BT403 is operated. In FIG. 20, the thick frame of the Full Self-Service Machine Button BT403 indicates that the button (Full Self-Service Machine Button BT403) has been operated.
[0147] In the above, the portable payment machines (machines 1 to 3) are set as the display targets when the full self-service machine button BT403 is operated, but although the portable payment machines are installed registers used for the manner in which customers register products and make payment, product registration is performed using a mobile terminal 60 rather than the installed register, so they may be excluded from the display targets when the full self-service machine button BT403 is operated. Also, in the above, the fully self-service dedicated machines (machines 7 to 9) are set as the display targets when the fully self-service machine button BT403 is operated, but they may be excluded from the display targets when the fully self-service machine 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: [Full self-service multiple operation mode machine (machine number 4)], or [Full self-service multiple operation mode machine (machine number 4) + full self-service dedicated machine (machines number 7 to 9)], or [Full self-service multiple operation mode machine (machine number 4) + portable payment machine (machines number 1 to 3)].
[0148] The registration machine button BT404 is a button for displaying on the installed register management screen the installed registers (No. 4 to No. 10, No. 13) that perform product registration among the installed registers in the store. The display contents of the installed register management screen when the registration machine button BT404 is operated are not shown in the figure. Note that the inspection device 50 (No. 1 to No. 3) and the settlement device 54 (No. 11, No. 12, No. 14, No. 15) are also equipped with a scanner unit and are capable of product registration, but since they do not normally register products, they are excluded from the display when the registration machine button BT404 is operated.
[0149] The settlement machine button BT405 is a button for displaying the installed registers (No. 1 to No. 9, No. 11, No. 12, No. 14, No. 15) that are used for settlement among the installed registers in the store on the installed register management screen. The display contents of the installed register management screen when the settlement machine button BT405 is operated are not shown in the figure.
[0150] The portable payment machine button BT406 is a button for displaying on an installed register management screen the installed registers (No. 1 to No. 3) among the installed registers in the store that handle the settlement of products registered using the mobile terminal 60. The contents displayed on the installed register management screen when the portable payment machine button BT406 is operated are not shown in the figure.
[0151] The setting button BT407 is a button for arbitrarily setting an installed register to be displayed on the installed register management screen. When the setting button BT407 is operated, the transaction status management device 40, for example, displays a small screen in front of the installed register management screen, inputs (registers) a button name on the small screen, and selects (for example, selects by a check box or the like) an installed register to be displayed when the button is operated. For example, when "Distant settlement machine" is input as the button name, and No. 1, No. 7 to No. 9, No. 11, and No. 12 are selected, and the setting completion button arranged on the small screen is operated, a "Distant settlement machine" button that displays the selected installed registers (No. 1, No. 7 to No. 9, No. 11, and No. 12) is arranged on the installed register management screen. It should be noted that the transaction status management device 40 erases the small screen when the setting completion button or the like is operated. In addition to the above, it is effective to set and arrange buttons that display registers that belong to accounting area A (described later) (registers that belong to accounting area C (described later), and similarly registers that belong to accounting area C (described later)). Also, by operating setting button BT407 (for example on the small screen), an operation to change the display target of each button or an operation to erase the button itself may be accepted.
[0152] The layout button BT408 is a button for displaying information about the installation positions of installed cash registers in the store on the installed cash register management screen. Fig. 21 shows the display contents of the installed cash register management screen (sometimes also called the layout screen) when the layout button BT408 is operated. Note that in Fig. 21, the thick frame of the layout button BT408 indicates that the button (layout button BT408) has been operated.
[0153] In the installed register management screen shown in FIG. 21, the main display area (area marked with the symbol M in the figure) displays icons corresponding to each device for each installed register in the store at a position according to the installation location of each device in the store. An icon with a thick frame indicates that the installed register is in use. An icon with a thin frame indicates that the installed register is on standby. Note that the icon with diagonal lines is an icon corresponding to the transaction status management device 40.
[0154] The dashed line of the icon indicates the side on which the customer stands at the installed cash register (the installed cash register corresponding to the icon). For example, the icon corresponding to the No. 1 cash register in the upper right of the drawing has a dashed line on the left side, which indicates that the customer stands on the left side of the No. 1 cash register (standing with his back to the No. 9 cash register). For example, the icon corresponding to the No. 5 cash register displayed on the transaction status management device 40 has a dashed line on the top side, which indicates that the customer stands on the top side of the No. 5 cash register (standing with his back to the No. 8 cash register). For example, the icon corresponding to the No. 11 cash register in the lower left of the drawing has a dashed line on the bottom side, which indicates that the customer stands on the bottom side of the No. 11 cash register (standing facing the No. 10 cash register). Instead of or in addition to the above, a mark indicating that the customer stands on the side on which the customer stands (for example, an image of a circle with the word "customer" written inside it) may be displayed on the side on which the customer stands. The display mode of the mark may be different depending on whether or not a customer is actually present. The mark may be displayed differently depending on whether a customer is present (determined by, for example, a human presence sensor), and for a customer-operated installed cash register, the display mode may be different depending on whether the customer is operating the register. Note that the mark does not have to indicate the position where the customer is standing at each device, but may simply indicate whether a customer is present or not, or whether the customer is operating the register.
[0155] The area where machines 1 to 3 are installed (area marked with symbol A in the figure) is a checkout area (sometimes referred to as checkout area A) that supports a fully self-service mode in which customers register products on mobile terminal 60 and pay at a cash register installed. The area where machines 4 to 9 are installed (area marked with symbol B in the figure) is a checkout area (sometimes referred to as checkout area B) that supports or can support a fully self-service mode in which customers register products at a cash register installed and pay (machines 4 to 6 can support this mode if their operating mode is set to fully self-service mode). The area where machines 10 to 15 are installed (area marked with symbol C in the figure) is a checkout area (sometimes referred to as checkout area C) that supports a semi-self-service mode in which a store clerk registers products and the customer pays.
[0156] The main display area also displays information such as a call to a store clerk, change near end, paper near end, etc. In this example, this information is displayed in the lower left of the main display area, but it may also be displayed in association with the icon of the corresponding installed cash register.
[0157] When information about installed registers is displayed on the installed register management screen (FIG. 16, etc.), if the position button BT461 of a display area related to a certain installed register is operated, the transaction status management device 40 displays the installed register management screen (layout screen) in the same way as when the layout button BT408 is operated, and displays the installed register in the layout screen so that it can be seen at a glance which register it is. For example, when the position button BT461 of the second register shown in FIG. 16 (FIG. 18(A)) is operated, the transaction status management device 40 displays the layout screen and displays the icon corresponding to the second register by blinking on and off on the layout screen. Note that blinking is just one example, and for example, the icon corresponding to the second register may be displayed in a color different from the other icons, or a mark may be added to the icon corresponding to the second register.
[0158] (Mobile device management screen) 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, for example, information stored in the cloud server 20 (transaction information of each mobile terminal 60) and information stored in the head office server 10 (customer master, etc.).
[0159] The transaction status management device 40 displays the number of mobile terminals 60 in the total number display area HR470 that are in a transaction. A mobile terminal 60 in a transaction is a mobile terminal 60 that is in a transaction after the start of product registration and before the completion of settlement. The transaction status management device 40 displays the number of mobile terminals 60 that are abnormal transactions among the mobile terminals 60 in the transaction in the abnormal number display area HR472. An abnormal transaction is, for example, a transaction that includes a reserved product (described later) and the subsequent settlement process will not be completed normally unless a store clerk checks the transaction. The transaction status management device 40 displays the number of mobile terminals 60 that are normal transactions among the mobile terminals 60 in the transaction in the normal number display area HR474. A normal transaction is, for example, a transaction that does not include a reserved product and the subsequent settlement process will be completed normally even if a store clerk does not check the transaction.
[0160] A reserved product is a product whose payment is temporarily suspended during the payment process. Reserved products include, for example, unscanned products whose scanning has not been completed, non-file products whose information such as price could not be obtained because the product code of the product has been scanned but not registered in the product master, products requiring age verification such as alcohol, medicines that require explanation by a pharmacist, and security tag products with security tags attached.
[0161] The main display area HR480 is an area that displays information about the mobile terminals 60 that are currently trading. The select all button BT471 is a button for displaying information about all mobile terminals 60 that are currently trading in the main display area HR480. The select abnormal number button BT473 is a button for displaying information about the mobile terminals 60 that are currently trading in the main display area HR480. The select normal number button BT475 is a button for displaying information about the mobile terminals 60 that are currently trading in the main display area HR480.
[0162] In the example shown in FIG. 22, the abnormality number selection button BT473 is operated, and information about the mobile terminal 60 for which the transaction is abnormal is displayed in a list in the main display area HR480. Specifically, information about 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". Note that the bold frame display of the abnormality number selection button BT473 indicates that the button has been operated. Note that, when there are a large number of mobile terminals 60 to be displayed in the main display area HR480, each may be displayed small, or may be displayed divided into multiple pages.
[0163] In FIG. 22, in the display area "1", in addition to information (symbol a) about the first mobile terminal 60 (mobile terminal 60 used by member number "C40"), an unscanned product button BT491 is arranged. The unscanned product button BT491 is displayed (placed) when an unscanned product is included as a reserved product. In the display area "2", in addition to information (symbol b) about the second mobile terminal 60 (mobile terminal 60 used by member number "C20"), an unscanned product button BT491 and a NON-FILE product button BT492 are arranged. The NON-FILE product button BT492 is displayed when a NON-FILE product is included as a reserved product. In the display area "3", in addition to information (symbol c) about the third mobile terminal 60 (mobile terminal 60 used by member number "C1"), an age verification product button BT493 is arranged. The age verification product button BT493 is displayed when an age verification product is included as a reserved product. In display area "4", in addition to information (symbol d) about the fourth mobile terminal 60 (mobile terminal 60 used by member number "C5"), a medicine button BT494 and a security product button BT495 are arranged. The medicine button BT494 is displayed when the reserved items include medicines that require an explanation from a pharmacist or the like. The security product button BT495 is displayed when the reserved items include products with security tags. In display area "5", in addition to information (symbol e) about the fifth mobile terminal 60 (mobile terminal 60 used by member number "C18"), a NON-FILE product button BT492 is arranged.
[0164] Note that the "customer terminals" in display areas "1" to "3" and "5" indicate that they are owned by an individual (or corporation). The "store terminal" in display area "4" indicates that it is loaned by the store. Note that by storing information that identifies the mobile terminal 60 loaned by the store (for example, a subscriber-specific ID or MAC address), it is possible to distinguish whether the mobile terminal 60 used by each member is a "store terminal" (i.e., whether it is a "customer terminal" or a "store terminal").
[0165] When the unscanned product button BT491 is operated, the transaction status management device 40 displays, for example, on a small screen, a captured image when the barcode attached to the product is read (when the barcode is about to be read). For example, the mobile terminal 60 stores the captured image when the barcode is read (see FIG. 10(C)) together with information indicating whether the reading was successful (read successful / read unsuccessful). When the unscanned product button BT491 is operated, the transaction status management device 40 displays, on the small screen, the captured image stored together with information indicating the reading failure. When there are multiple unscanned products, the transaction status management device 40 displays each captured image. The mobile terminal 60 may transmit the captured images to the cloud server 20, and the transaction status management device 40 may acquire the captured images from the cloud server 20.
[0166] When the NON file product button BT492 is operated, the transaction status management device 40 displays, for example, the product code of the product on a small screen. When there are multiple NON file products, the transaction status management device 40 displays each product code. For example, the mobile terminal 60 stores the read product code together with information indicating that it is a NON file. When the NON file product button BT492 is operated, the transaction status management device 40 displays, on the small screen, the product code stored together with information indicating that it is a NON file. When there are multiple NON file products, the transaction status management device 40 displays each product code. Note that the mobile terminal 60 may transmit the product code and the like to the cloud server 20, and the transaction status management device 40 may acquire the product code from the cloud server 20. Note that the transaction status management device 40 may display a captured image when reading a barcode (when reading or when reading) instead of or in addition to the product code.
[0167] When the age verification product button BT493 is operated, the transaction status management device 40 displays the product name, etc. of the product on a small screen, for example. When there are multiple age verification products, the transaction status management device 40 displays the product names, etc. of each product. The transaction status management device 40 may obtain the product names, etc. from the cloud server 20. The same applies when the age verification product button BT493 is operated and when the crime prevention product button BT495 is operated.
[0168] When a reserved item (such as an age verification item, such as an alcoholic product) is registered on the mobile terminal 60, the transaction status management device 40 notifies, as information related to the mobile terminal 60, that there is a reserved item among the items registered on the mobile terminal 60 (mobile terminal management screen (FIG. 22)). As described above (see the explanatory portion of the DETAILS button BT441 provided in the operation status display area HR440 of the installed register management screen), the transaction status management device 40 notifies, as information related to the installed register, the presence or absence and content (type) of a reserved item (described later) (installed register management screen (FIG. 16, etc.)). In other words, for example, when an age verification item, such as an alcoholic product, is registered on the mobile terminal 60, the transaction status management device 40 notifies, on the mobile terminal management screen during product registration (before payment begins), that an age verification item has been registered on the mobile terminal 60, and after product registration, After the checkout process is completed, the transaction status management device 40 notifies the user on the installed register management screen that the age verification product has been registered on the mobile terminal 60 (the mobile terminal 60 that read the two-dimensional checkout code 605). In other words, if there is a reserved product among the products registered on the mobile terminal 60, the store clerk can check this on the mobile terminal management screen (FIG. 22) and the installed register management screen (FIG. 16, etc.) (either during product registration or after product registration). The installed registers that can notify the user of the presence of a reserved product are all installed registers, including the portable settlement machines (machines 1 to 3). Therefore, for example, if there is a reserved product among the products registered on the portable settlement machines (machines 1 to 3) and the installed registers (machines 4, 7 to 9, etc.) that are premised on self-registration, the transaction status management device 40 can notify the user of the presence of a reserved product on the installed register management screen.
[0169] In addition, although it has been described that the reserved items are displayed on the installed register management screen after the operation of the details button BT441, the reserved items may be displayed in the same manner as on the mobile terminal management screen. In other words, instead of displaying the reserved items after the operation of a certain button on the installed register management screen, the reserved items may be displayed directly on the installed register management screen (not after the operation of a button). For example, when an alcoholic product is registered in a certain installed register (for example, machine No. 7 (a fully self-service only machine) or machine No. 4 (a machine with multiple operation modes in a fully self-service mode)), the 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 the installed register on the installed register management screen (for example, display in the operation status display area HR440 or display in the device image display area HR450). When a button (such as the age verification product button BT493) related to the reserved items displayed on the installed register management screen is operated, the transaction status management device 40 may operate (display a small screen) in the same manner as when a button related to the reserved items displayed on the mobile terminal management screen is operated.
[0170] When the clerk who operates the transaction status management device 40 can see the customer who has registered the alcoholic product and judges that the customer is of a sales-allowable age, the clerk operates the transaction status management device 40 to approve (confirm) the sale of the alcoholic product (the status is changed to "clerk approved" by this operation). As a result, even if a product that requires confirmation by a clerk is registered at a register installed without the intervention of a clerk (such as No. 4, No. 7 to No. 9), the operation (process) at the register can be continued (progressed) without the clerk going to the register. In addition, for example, a "confirm" tab may be prepared for the registration of a product that requires confirmation by a clerk, and confirmation information may be displayed in a list on this tab. Note that, when the clerk who operates the transaction status management device 40 cannot see the customer who has registered the alcoholic product or can see the customer but judges that confirmation by getting closer is required, the clerk goes to the corresponding register and deals with the matter directly (when approving, the clerk performs a predetermined operation to change the status to "clerk approved" after having the clerk code read by the scanner unit of the register). In addition, the transaction status management device 40 may display images captured by cameras installed at each installed cash register (or cameras installed in various places in the store), and the store clerk may determine whether or not the person is of legal age to sell based on the captured images, instead of or in addition to visual inspection.
[0171] The detailed information display area HR481 is an area for displaying information (such as purchase history) about a customer using one of the mobile terminals 60 whose information is displayed in the main display area HR480. The purchase history of each customer may be stored, for example, in the headquarters server 10. For example, when the area of display area "4" (excluding the medicine button BT494 and the security product button BT495) in the main display area HR480 is operated (touched), the transaction status management device 40 displays, in the detailed information display area HR481, information about the customer with member number "C5" who is using the mobile terminal 60 in the display area "4", as shown in FIG. 22. The thick frame of the display area "4" indicates that the mobile terminal 60 in question has been selected.
[0172] (Control based on customer presence / absence) (1) The transaction status management device 40 grasps that a transaction of the service A has started. For example, the cloud server 20 generates transaction information (cart information) of the transaction by the mobile terminal 60 based on receiving information (service start notification) based on a predetermined operation on the mobile terminal 60. When the cloud server 20 generates the transaction information, the cloud server 20 transmits a transaction start notification including transaction identification information (cart identification information) for identifying the transaction (or a transaction start notification including the membership number of the mobile terminal 60) to the transaction status management device 40. The transaction start notification may be transmitted from the cloud server 20 to the transaction status management device 40 via the headquarters server 10, or may be transmitted from the cloud server 20 to the transaction status management device 40 without passing through the headquarters server 10. This allows the transaction status management device 40 to immediately grasp that a transaction of the service A has started (that the user of the mobile terminal 60 has entered the store). In addition, instead of sending a transaction start notification from the cloud server 20 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) and check whether the transaction has started.
[0173] (2) The transaction status management device 40 grasps that the transaction of the service A has been completed (that the settlement has been completed). For example, when the settlement of a certain transaction is completed, the cloud server 20 stores the settlement information (total amount, etc.) in the transaction information of the transaction, and transmits a transaction completion notice (settlement completion notice) including transaction identification information (cart identification information) for identifying the transaction to the transaction status management device 40. The transaction completion notice may be transmitted from the cloud server 20 to the transaction status management device 40 via the headquarters server 10, or may be transmitted from the cloud server 20 to the transaction status management device 40 without passing through the headquarters server 10. This allows the transaction status management device 40 to immediately grasp that the transaction of the service A has been completed (that the settlement of the user of the mobile terminal 60 has been completed). Note that, when the transaction information has a transaction completion time (settlement completion time) as an item, the cloud server 20 may store the transaction completion time in the transaction information of the transaction as the current time when the settlement of a certain transaction is completed. Also, in the case where the transaction information has a status as an item, the cloud server 20 may store "transaction completed (settlement completed)" as the status in the transaction information of a transaction when the settlement of the transaction is completed. Instead of transmitting a transaction completion notification from the cloud server 20 to the transaction status management device 40, the transaction status management device 40 may access the cloud server 20 (via the head office server 10 or without via the head office server 10) to check whether the transaction is completed or not. For example, the transaction status management device 40 determines that the transaction is completed when settlement information (settlement amount, etc.) or the status "transaction completed" is stored in the transaction information, and determines that the transaction is not completed when settlement information (settlement amount, etc.) or the status "transaction completed" is not stored in the transaction information.
[0174] Customers of Service A (users of mobile terminals 60, particularly beginners) require more thorough follow-up than customers of other services, but according to (1) and (2) above, the transaction status management device 40 can immediately grasp and notify (display, audio output) that a transaction for Service A has started or completed. Also, according to (1) and (2) above, the transaction status management device 40 can accurately grasp and notify (display, audio output) that there are users of Service A in the store who have not yet settled, and the number of users of Service A in the store who have not yet settled.
[0175] If the cloud server 20 generates transaction information for a transaction by the mobile terminal 60 based on a predetermined operation on the mobile terminal 60 but none of the devices (installed cash registers for settling transactions by the mobile terminal 60; portable settlement machines) used for settlement in service A are activated, the customer cannot settle the payment after registering the product. Therefore, when the cloud server 20 generates transaction information, the transaction status management device 40 may check the activation status of the portable settlement machines, and if none of the portable settlement machines are activated, may issue a warning (display, voice output, etc.). Note that when each installed cash register including a portable settlement machine goes 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 notify the transaction status management device 40 of the change in state, so that the transaction status management device 40 may store the activation status of the portable settlement machine, or may inquire about the activation status of the portable settlement machine as necessary (such as when the cloud server 20 generates transaction information). Note that the above-mentioned confirmation leading to the warning may be limited to when specific transaction information is generated. For example, if the business hours of a store are from 10:00 am to 10:00 pm and the service A is used from 10:00 am to 9:00 pm, the confirmation may be limited to the first visit of a customer of service A after 10:00 am (the time when the first transaction information is generated). The confirmation that leads to the above warning may be limited to a predetermined time. For example, if the business hours of a store are from 10:00 am to 10:00 pm and the service A is used from 10:00 am to 9:00 pm, the confirmation may be limited to the first visit of a customer of service A between 10:00 am and 10:30 am (the time when the first transaction information is generated). The same applies not only to the case where none of the machines are started, but also to the case where all the machines are not started, the machines are started but cannot be settled (for example, due to a malfunction, etc.), the case where there is a possibility that settlement cannot be made (for example, change is near end, etc.), and the case where transaction information is not generated on the cloud server 20.
[0176] In the case where the cloud server 20 generates transaction information for a transaction by the mobile terminal 60 based on a predetermined operation on the mobile terminal 60 but none of the portable settlement machines are activated, the mobile terminal 60 may be notified of this fact. This makes it possible to inform (guide) the customer in question, for example, that settlement is not possible immediately, or to a service other than service A, that is, another transaction that does not use the mobile terminal 60 (for example, a transaction by a machine exclusively for full self-service). Note that the same applies not only to the case where none of the machines are activated, but also to the case where all the machines are not activated, the machines are activated but settlement is not possible, the case where there is a possibility that settlement will not be possible, or the case where transaction information is not generated on the cloud server 20.
[0177] It is also useful in situations other than when the store is opening. For example, if the business hours of the store are from 10:00 am to 10:00 pm and the service A is available from 10:00 am to 9:00 pm, at a certain point after 9:00 pm, when the store clerk looks around the store and determines that there is no customer using the service A (a customer who has registered a product using the mobile terminal 60) in the store, the store clerk starts a closing process that involves turning off the portable settlement machine, and after the closing process starts, the customer may start a transaction using the mobile terminal 60. The transaction status management device 40 can grasp both the start-up status of the portable settlement machine (that it is not started) and that a transaction using the service A has started. Therefore, for example, the store clerk of 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. That a transaction using another method is possible) and minimize confusion. In addition, as a notice to the mobile terminal 60, a message such as "Today's transaction using the mobile terminal has ended. Please use normal transactions" can be displayed, and confusion can be minimized.
[0178] It should be noted that the cloud server 20 does not need to generate transaction information outside the usage hours of service A. In other words, when the transaction status management device 40 receives a service start notification from the mobile terminal 60 during the usage hours of service A, it may generate transaction information of the transaction by the mobile terminal 60 and transmit the transaction start notification to the transaction status management device 40, and when the transaction start notification is received from the mobile terminal 60 outside the usage hours of service A, it may transmit a predetermined notification including the membership number of the customer of the mobile terminal 60 to the transaction status management device 40 without generating transaction information. It should be noted that the operation of the transaction status management device 40 when it receives the predetermined notification may be the same as when it receives a transaction start notification.
[0179] The transaction status management device 40 can also remotely control the closing process of each installed cash register. As described above, the transaction status management device 40 can also determine whether or not there is a user of service A who has not yet settled in the store. If there is even one user of service A who has not yet settled in the store, the transaction status management device 40 may restrict (prohibit) the start of the closing process for the portable settlement machine, or may warn the store staff (by displaying, outputting voice, etc.). For example, the transaction status management device 40 may issue a notice (by displaying, outputting voice, etc.) saying "There is a customer using the portable terminal 60. Closing is not possible," to prevent the closing process from being performed.
[0180] (Release of reserved items) The transaction status management device 40 can accept an operation to release the reserved item from the reservation (sometimes simply referred to as releasing the reserved item). Specifically, the transaction status management device 40 can accept an operation to register an unscanned item.
[0181] 23 shows an example of a product information input screen 1400. The product information input screen 1400 is a screen for performing an operation to input product information. For example, a button (input screen button) may be arranged on a small screen that is displayed after operating the unscanned product button BT491 (arranged for each product when 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 is provided with a product information display area HR1410, a product specification operation reception area SR1420, a captured image display area HR1430, a confirm button BT1440, and a product cancel button BT1441.
[0183] The product information display area HR1410 is an area for displaying the product name, product code, price, registered quantity, etc. The registered quantity can be changed using the plus button and minus button in the same area.
[0184] The product identification operation reception area SR1420 is an area that receives an operation to identify (register) a product using various buttons arranged in the same area. For example, a product may be identified on a preset screen (product buttons corresponding to individual products (screen on which preset buttons are arranged)) that is displayed after operating a preset button BT1421. Also, for example, a product code may be input as a quantity after operating a PLU button BT1422 to identify a product. Note that the PLU button BT1422 is a button that declares input of a quantity using numeric buttons, but the number may be simply input using numeric buttons without providing the PLU button BT1422. Note that after identifying a product, the product name, etc. of the product are displayed (reflected) in the product information display area HR1410. Note that, in the captured image display area HR1430, a captured image of an unscanned product is displayed, as in the small screen that is displayed after operating the unscanned product button BT491, so a product may be identified while checking the 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 Confirm button BT1440. When the Confirm 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) specified by the preset buttons BT1421 or the input of the quantity to be placed. The Product Cancel button BT1441 is a button that is used to instruct the cancellation of the registration of the product.
[0186] When an unscanned product is registered and the transaction does not include the unscanned product, the unscanned product button BT491 is erased. For example, the unscanned product button BT491 is displayed in the display area "1" in FIG. 22, but the description will be given assuming that there are two unscanned products included in the transaction. When the unscanned product button BT491 in the display area "1" is operated, a small screen is displayed on which two input screen buttons and the like corresponding to the two unscanned products are arranged. When one input screen button is operated on the small screen, a product information input screen 1400 related to the product corresponding to the 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 erased, but the unscanned product button BT491 in the display area "1" is not erased (the small screen with one input screen button erased may remain displayed). When the input screen button for the remaining unscanned product is operated on the small screen, a product information input screen 1400 related to the product corresponding to the input screen button is displayed. When the registration of an unscanned product is completed via the product information input screen 1400, the product information input screen 1400 and the small screen are both cleared, and the unscanned product button BT491 in the display area "1" is also cleared.
[0187] The transaction status management device 40 may also be configured to accept an operation to release the reservation of other reserved products. As an example, the transaction status management device 40 may be configured to accept an operation to release the reservation of an age verification product. For example, if a customer has performed an operation on the mobile terminal 60 to the effect that he or she is 20 years old or older (declaration that he or she is 20 years old or older), the effect (declaration) may be displayed on the transaction status management device 40, and the reservation of the age verification product may be released by performing an approval operation on the transaction status management device 40. When releasing the reservation of the age verification product, the appearance, etc. of the customer may be confirmed from images captured by cameras installed in various places in the store. The captured image of the customer may be identified based on the position information of the customer (the mobile terminal 60), for example, and displayed on a small screen displayed when the age verification product is purchased.
[0188] When the reserved product is released, it is reflected in the transaction information of the cloud server 20. For example, when the transaction status management device 40 releases the reserved product a of a certain mobile terminal 60, it transmits information (reservation release information) indicating that the reserved product a of the certain mobile terminal 60 has been released from the reserved product a of the certain mobile terminal 60 to the cloud server 20. The cloud server 20 updates the transaction information of the certain mobile terminal 60 (releases the reserved product a) based on the above-mentioned reservation release information. In addition, the cloud server 20 may generate screen information reflecting the contents of the updated transaction information and transmit it to the mobile terminal 60. In this way, the release of the reservation in the transaction status management device 40 is appropriately reflected on the screen of the mobile terminal 60. For example, when the transaction status management device 40 confirms the age of a certain product (age verification product) in a transaction of a certain mobile terminal 60, the display of "age verification required" attached to the product on the screen of the certain mobile terminal 60 is switched to "age verification completed" (or the display of "age verification required" is erased).
[0189] The display of the transaction status management device 40 has been described above using Figures 16 to 23, but the display of the transaction status management device 40 is not limited to that described using Figures 16 to 23. For example, in the above, an example has been described in which the installed register management screen (Figures 16 to 21) and the mobile terminal management screen (Figures 22 and 23) are switched between for display, but instead of or in addition to switching between the screens, the installed register management screen and the mobile terminal management screen may be displayed simultaneously (for example, displayed side by side, one above the other, or displayed side by side). When displaying them simultaneously, an operation such as making one larger and the other smaller may be accepted.
[0190] In the above, the mobile terminals 60 "after product registration starts and before payment is completed" are uniformly monitored without distinguishing between the progress of the processing, but each of the mobile terminals 60 may be monitored for each progress of the processing. For example, the transaction status management device 40 may display any of the following (1) to (6) selectable. For example, each mobile terminal 60 may notify the cloud server 20 of information related to the progress of the processing, and the cloud server 20 may store the information related to the progress of the processing in the transaction information of each mobile terminal 60, so that the transaction status management device 40 recognizes the progress of the processing of each mobile terminal 60 (in other words, extracts the mobile terminals 60 belonging to (1) to (6)).
[0191] (1) The mobile terminal 60 after the start of product registration but before the product registration is completed (for example, before the two-dimensional code 605 for payment is displayed) (i.e., the mobile terminal 60 during product registration) (2) The mobile terminal 60 after product registration is completed (for example, after the two-dimensional settlement code 605 is displayed) and before settlement begins (for example, before the settlement device 50 reads the two-dimensional settlement code 605) (i.e., the mobile terminal 60 during settlement). (3) After the start of settlement (for example, after the settlement device 50 reads the settlement two-dimensional code 605), the portable terminal 60 before settlement is completed (i.e., the portable terminal 60 during settlement) (4) After product registration begins, but before payment begins (i.e., (1)+(2)) on the mobile terminal 60 (5) After product registration is complete, but before payment is completed (i.e., (2)+(3)) on the mobile terminal 60 (6) After product registration has started, but before payment has been completed (i.e., (1)+(2)+(3). Example of FIG. 22)
[0192] The transaction status management device 40 may display the progress of the process of each mobile terminal 60 (for example, "registering product", "transitioning to settlement", "settlement in progress", etc.) on the mobile terminal management screen shown in FIG. 22. Furthermore, for the mobile terminal 60 during settlement (the mobile terminal 60 after the settlement device 50 reads the settlement two-dimensional code 605), the transaction status management device 40 may display information about the settlement device 50 during settlement (for example, "machine 1", "machine 2", "machine 3", etc.) on the mobile terminal management screen. Furthermore, instead of or in addition to displaying information about the settlement device 50 during settlement on the mobile terminal management screen, the transaction status management device 40 may display information about the mobile terminal 60 during settlement (for example, the membership number of the customer using the mobile terminal 60) on the installed register management screen (layout screen) shown in FIG. 22.
[0193] (Exit gate device) In the first embodiment (as well as in the other embodiments), an exit gate device may be installed near the exit (or just before the exit) to prevent fraudulent behavior in which a customer leaves the store without paying. The exit gate device may, for example, include a detection unit, a reading unit, a judgment unit, and a regulation unit. The detection unit detects the entry of a person (such as a customer). The reading unit reads the identification information. The identification information may, for example, be a two-dimensional code (a two-dimensional code for passage permission) printed on a receipt issued after payment, or a two-dimensional code for passage permission displayed on the mobile terminal 60 after payment. The judgment unit judges whether or not to allow passage based on the result of reading the identification information by the reading unit. The regulation unit has a regulation member (a door, a bar, etc.) and regulates (hinders / does not hinder) passage using the regulation member based on the result of the judgment by the judgment unit.
[0194] The exit gate device may be configured to simply restrict movement as described above, but may also display information on a display or issue a voice alert. The exit gate device may also be connected to a network (LAN) and managed (monitored and controlled) by, for example, a transaction status management device 40. In other words, the transaction status management device 40 can manage devices installed in the store other than the installed cash registers and mobile terminals 60, i.e., the "situation within the store" in a broad sense.
[0195] The exit gate device may be equipped with a communication unit for communicating with other devices (e.g., transaction status management device 40) in addition to the detection unit, reading unit, judgment unit, and regulation unit. The exit gate device may also be equipped with a display unit (liquid crystal, LED, etc.) that displays the reading result by the reading unit, and an audio output unit that notifies the reading result by the reading unit by voice. The exit gate device may also be equipped with a ticket issuing unit (printing unit) that issues coupons to encourage customers to visit the store next time.
[0196] The transaction status management device 40 manages the customers who come to the store until they pass through the exit gate device and leave the store. If the exit gate device is not the object of management by the transaction status management device 40, if the performance of the display unit or the audio output unit of the exit gate device is insufficient, it is difficult to notice the notification that passage is restricted, even if the transaction status management device 40 is installed near the exit gate device (side by side). However, if the transaction status management device 40 manages the exit gate device, even if the performance of the display unit or the audio output unit of the exit gate device is insufficient, the store clerk can check it on the screen. Note that, if the transaction status management device 40 is installed near the exit gate device that is the object of monitoring, the store clerk of the transaction status management device 40 can check the status of the customers who pass through the exit gate device and leave the store through the screen or by visual inspection from a nearby position. Note that there are cases where multiple exit gate devices are installed in a store, or where they are installed scattered around the store, and this is preferable because 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 display logs, real-time operation status, and the like, in the same way as in the case of a weighing device (described later). Events (phenomena) managed as logs include, for example, the judgment result (OK, NG) of the judgment unit, and the issuance of a coupon by the ticket issuing unit. Abnormal logs include, for example, a person passing without reading the identification information, a person passing with a judgment NG of the identification information, a low remaining coupon paper, a coupon paper that has run out, a coupon paper that is jammed, and a communication abnormality with other devices (the transaction status management device 40, the 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 information that is difficult to resolve) unless a store clerk goes to the exit gate device, and information required 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 together with the time of occurrence. The transaction status management device 40 stores logs and information on operation status together with the time of occurrence in a memory unit, regardless of whether or not they are displayed on the screen (i.e. even if they are not displayed) (the same applies to logs of the weighing device (described below)).
[0198] The above describes an embodiment. According to the embodiment, when multiple services coexist, it is possible to provide an optimal transaction flow.
[0199] (Variations, etc.) Although the embodiment has been described above, the device configuration, data configuration, processing flow, display and output aspects, etc. can be appropriately changed, for example, as shown in the following (1), (2), .... In addition, the following (1), (2), ... may be appropriately combined.
[0200] (1) In the above embodiment, the transaction status management device 40 has been described as a device that is installed in the store and operated at the installed location, but the transaction information management device 40 may be a portable device that is operated at various locations in the store (e.g., various locations in the sales floor, various locations in the checkout area, back yard, etc.). For example, the transaction information management device 40 may be a laptop computer, a tablet terminal, or a stationary device with a removable display unit. If the transaction information management device 40 is a portable device, it is possible to actually meet the customer and release the hold on the reserved item. As an example, it is possible to directly check the customer's appearance at the sales floor and release the hold on the customer's age verification item.
[0201] (2) In the above embodiment, the settlement device 50 has been described as a device that settles the merchandise registered by the mobile terminal 60, but the settlement device 50 may settle the merchandise registered by a device other than the mobile terminal 60 (e.g., the registered settlement device 51, the registered settlement device 52, the registration device 53). For example, the settlement device 50 may receive registration information from the registration device 53 like the settlement device 54, and settle the merchandise registered by the registration device 53.
[0202] (3) Although the settlement device 50 (portable settlement machine) has been described as a device that settles the payments for products registered by the mobile terminal 60, a device other than the settlement device 50 (e.g., the registered settlement device 51, the registered settlement device 52, the settlement device 54) may settle the payments for products registered by the mobile terminal 60. For example, the registered settlement device 51 (as well as the registered settlement device 52 and the settlement device 54) may read the settlement two-dimensional code 605 displayed by the settlement device 50 and display it on a product list screen such as that shown in FIG. 13.
[0203] (4) In relation to the above (2) and (3), an operation mode for settling the merchandise registered by the mobile terminal 60 may be provided. For example, the settlement device 50 may have, as its operation modes, an installed register registered merchandise settlement mode for settling the merchandise registered by an installed register (such as the registration device 53) and a mobile terminal registered merchandise settlement mode for settling the merchandise registered by the mobile terminal 60. Also, for example, the registration settlement device 51 may have, as its operation mode, the mobile terminal registered merchandise settlement mode in addition to the operation modes already described (such as the face-to-face self-service mode and the full self-service mode). Note that the settlement device 50 (as well as the registration settlement device 51) may read the two-dimensional settlement code 605 when the current operation mode is the mobile terminal registered merchandise settlement mode (or may switch from another operation mode to the mobile terminal registered merchandise settlement mode by reading the two-dimensional settlement code 605).
[0204] (5) In relation to (4) above, a single device may be provided that combines the functions of the settlement device 50 and the registered settlement device 51. In other words, a registered settlement device (installed cash register) having a face-to-face self-service mode (one of the installed cash register registered product settlement modes), a full self-service mode (one of the installed cash register registered product settlement modes), a registration-only mode (one of the installed cash register registered product settlement modes), a settlement-only mode (one of the installed cash register registered product settlement modes), and a mobile terminal registered product settlement mode may be installed in the store.
[0205] (6) In the above embodiment, an example was described in which the installed cash registers include a settlement device (portable settlement device) 50, a registration settlement device (multiple operation mode device) 51, a registration settlement device (full-self-service dedicated device) 52, a registration device (semi-self-service registration device) 53, and a settlement device 54 (semi-self-service settlement device). However, the installed cash registers are not limited to this. For example, a registration settlement device (a conventional general registration settlement device, referred to as a registration settlement device 59) equipped with a scanner unit, a settlement unit (specifically, a cash settlement unit) and the like on one side (the store clerk side) and used by the store clerk may be installed. When the 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 a type that performs registration and settlement in one housing, or may be composed of, for example, a tower-type registration device 59a and a settlement device 59b equipped with a drawer.
[0206] (7) In the above embodiment, the customer registers the product using the mobile terminal 60. However, the mobile terminal 60 is not limited to the mobile terminal 60, as long as the mobile terminal is a mobile (portable) device capable of registering the product at the display location. For example, the product may be registered using a tablet terminal (which may be fixed to the shopping cart) provided by the store to the customer. Also, for example, the product may be registered using a shopping cart (or a display device detachable from the shopping cart) equipped with a display unit. In other words, the terminal provided by the store is not limited to the mobile terminal 60, and may be connected to a shopping cart equipped with an operation screen, a camera, a scale, and a battery, or may be formed integrally with the shopping cart (or may be detachable). Also, the shopping cart may be equipped with an electronic tag recognition unit that recognizes information of an electronic tag. In an aspect in which the product is registered using a shopping cart (or a display device detachable from the shopping cart), the cart number of the shopping cart may be displayed on the management screen (FIGS. 16 to 23).
[0207] The shopping cart (hereinafter, simply referred to as cart) equipped with the battery described above may charge the battery by contact (contact charging) or non-contact (non-contact charging). The charging device for the cart may be installed at a place (cart collection point) where the cart is pulled out and returned when rented. The cart may be pulled out or returned by the customer or by a store clerk. In the case of contact charging, the battery of the cart is charged by connecting a cable or the like. The number of cables or the like is prepared in the cart collection point as many as the number of carts that can be stored (the maximum number of waiting carts before rental) (if storage positions are set, they are prepared and lined up at each storage position). In the case of non-contact charging, a non-contact charging system (power supply (transmission) unit, power receiving (reception) unit) is provided on the cart side and the cart collection point side, respectively, and the power transmitted from the power supply unit on the cart collection point side is received by the power receiving unit on the cart side to charge the cart. As in the case of contact charging, the cart collection point is provided with the same number of power supply units as the number of carts that can be stored, and is arranged so that the power supply and the power reception are paired. A power supply unit capable of large-scale power transmission may be placed at the cart collection point, and power may be transmitted collectively to multiple power receiving units. As with withdrawing and returning carts, charging (contact charging or non-contact 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 charge the cart).
[0208] The transaction status management device 40 may manage (monitor, control) the cart collection point as described above. For example, the transaction status management device 40 may display the number of carts waiting at the cart collection point (the number of waiting carts) on a management screen. The transaction status management device 40 may also display the number of carts being charged at the cart collection point (the number of carts being charged) instead of or in addition to 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, a method in which a camera that images the cart collection point is used to image the carts (the number of carts) present at the cart collection point, image recognition is performed on the imaged image, the number of carts is calculated, and the number of waiting carts is obtained. The device that performs the image recognition may be the transaction status management device 40 or another device (when the other device performs the image recognition, the calculated number of carts is notified to the transaction status management device 40). Note that a transmissive or reflective optical sensor may be installed to detect carts present at the cart collection point and obtain the number of waiting carts. The number of waiting carts may be acquired by communicating with a mobile terminal 60 provided on a cart present at the cart collection point using NFC (Near Field Communication) communication or Bluetooth (registered trademark) communication. A scale may be installed on the floor of the cart collection point, and the number of carts present at the cart collection point may be calculated from the weight (total weight) and acquired as the number of waiting carts. 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 certain 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 operation of starting shopping (or scanning one item of merchandise) to the completion of the transaction. The method of the transaction status management device 40 to acquire the number of charging carts may be, for example, a method in which the cart collection point recognizes whether the cart collection point is in an electrically or magnetically powered state and notifies the transaction status management device 40, or a method in which the cart collection point acquires information that a cart is being charged by communicating with the cart and notifies the transaction status management device 40. In the case of a mode in which power is transmitted collectively to a plurality of power receiving units, the number of carts being charged may be calculated based on the amount of power transmitted collectively.Furthermore, the transaction status management device 40 may compare the number of waiting carts with the number of carts being charged, and display the comparison result (difference) on the management screen (for example, separately displaying the number of waiting carts, the number of carts being charged, and the difference). If the number of waiting carts and the number of carts being charged do not match (specifically, if the number of carts being charged 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 charging of carts at the cart collection point"). Furthermore, the transaction status management device 40 may send a similar message to a mobile terminal or the like used by a store clerk.
[0209] (8) In the above, 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 are described as objects to be managed (monitored and controlled) by the transaction status management device 40, but the objects to be managed by the transaction status management device 40 are not limited to these. For example, a weighing device as described below may be monitored. In the delicatessen sales corner in the store, weighed products (products sold by weight) may be sold. When selling products sold by weight, a weighing device (weighing pricing device) may be installed that weighs the products purchased by a store clerk or a customer (self-operation) and calculates the selling price based on the weight unit price of the product and the weighed value. Note that 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 by wireless communication (for example, Bluetooth (registered trademark)). In particular, when the weighing device is operated by the customer (self-operation), there are many cases where no store clerk is present near the weighing device (since the device is intended for self-operation), so by having the weighing device managed by the transaction status management device 40, any problems that arise can be dealt with quickly even from a remote location.
[0210] (9) In relation to the above (8), the transaction status management device 40 may display the log of the weighing device and the real-time operation status. Events (phenomena) managed as logs include, for example, operations related to the tare (tare subtraction operation, tare designation operation, etc.), product selection operation (product preset button operation, etc.), product placement (weight detection, measurement value), label printing and issuance, and status related to wireless communication with the mobile terminal 60 (establishment, disconnection of communication (Bluetooth (registered trademark)) with the mobile terminal 60, etc.). In addition, logs related to abnormalities include information such as low remaining product labels (label paper), no product labels, product labels jammed, a negative weight value, a positive weight value, a weight value exceeding the upper limit of the weight that can be measured, and communication abnormalities with other devices (transaction status management device 40, store controller 30, etc.). In addition, the transaction status management device 40 is generally installed in the checkout area, whereas the weighing device is installed in a sales area (near the prepared food sales corner) different from the checkout area. That is, the two are generally installed in separate locations. Therefore, the clerk of the transaction status management device 40 cannot rush to the weighing device immediately if something happens (at least, it takes longer for the clerk to arrive than rushing to other monitored objects (installed cash registers, etc.) installed in the accounting area). To deal with this, a clerk call button or the like may be prepared (for example, displayed on the management screen of the transaction status management device 40, or a physical button installed nearby), and the clerk call button or the like may be operated to have another clerk go directly to the weighing device. For example, when the clerk call button or the like is operated, the transaction status management device 40 may transmit information (message) to a mobile terminal carried by a clerk who is working on another task in the backyard or the like that the clerk should go directly to the weighing device, or may make an in-house announcement to the clerk who is working on another task in the backyard or the like. The area of the in-house announcement may be different depending on the range of the clerk to be called, the degree of the problem with the weighing device, etc. (therefore, for example, several types of call buttons with different broadcast areas may be prepared, or a button for switching the broadcast area may be prepared).
[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 realized in a device other than the device described as the executing entity of the function. For example, at least some of the processing described using the sequence diagram of FIG. 15 as the processing of the settlement device 50 may be executed by another device (store controller 30 or cloud server 20) instead of the settlement device 50. In addition, the settlement device 50 may display a screen generated by another device on the display unit 105 instead of a screen generated by the settlement device itself (for example, a screen provided by a web server may be browsed). In relation to the above, the settlement device 50 may function as a so-called thin client specialized for input / output interfaces, etc. For example, the settlement device 50 may accept various inputs (customer operations, detection by devices such as a scanner) and transmit the input information (operation information, detection information, etc.) to a server (e.g., cloud server 20), and then the cloud server 20 executes processing according to the information received from the settlement device 50 and transmits the processing result (updated screen information, etc.) to the settlement device 50, and then the settlement device 50 may execute an operation (display on the display unit 105, etc.) according to the information received from the cloud server 20. In other words, the cloud server 20 may execute a program for controlling the operation of the settlement device 50. The same applies to the registration settlement device 51, the registration settlement device 52, the registration device 53, the settlement device 54, the registration settlement device 59, the transaction status management device 40, etc.
[0212] <Overview of the embodiment> [Technical field] The present invention relates to an in-store situation management device and a program. [Background technology] There are cases where multiple services related to the sale of goods coexist. For example, a system that provides multiple payment methods in a store is known (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2016-081072 A [Summary of the Invention] [Problem to be solved by the invention] However, when multiple services coexist, the burden on the store clerk to monitor them increases. The present invention has been made in view of such circumstances, and has an object to provide a technique for reducing the burden on store clerks. [Means for solving the problem]
[0213] (1) A store situation management device (e.g., transaction status management device 40) capable of monitoring a plurality of settlement devices, the settlement devices being a first settlement device (e.g., settlement device 54, registered settlement device 51, registered settlement device 52, registered settlement device 59) that settles for merchandise registered on another installed device or on the device itself, and a second settlement device (e.g., settlement device 50) that settles for merchandise registered on another portable device (e.g., mobile terminal 60), the store situation management device being characterized in that it is equipped with a display means that displays the status of the first settlement device and the second settlement device (e.g., as shown in Figures 16 to 21). The in-store situation management device of (1) reduces the burden on store staff. In other words, even if multiple services coexist in a store, the multiple services can be monitored collectively, making management easier and reducing the burden on store staff.
[0214] (2) The in-store situation management device described in (1) is characterized in that the first settlement device (e.g., registered settlement device 51) has multiple operating modes (e.g., face-to-face self-service mode, full self-service mode, etc.), and the display means displays information indicating whether each settlement device is the first settlement device or the second settlement device (e.g., names such as ``portable settlement device'' or ``multiple operation mode machine''), as well as the current operating mode of the first settlement device (e.g., ``(face-to-face)'' for multiple operation mode machine (face-to-face), ``(full)'' for multiple operation mode machine (full), etc.). The in-store situation management device of (2) reduces the burden on store staff, for example, by allowing them to easily check the status of each device.
[0215] (3) The display means is an in-store situation management device described in any of (1) to (3), characterized in that it displays the status of the first settlement device and the second settlement device on a layout screen (for example, as shown in Figure 21). (3) The in-store situation management device reduces the burden on store staff.
[0216] (4) A program that causes a computer to function as an in-store situation management device capable of monitoring multiple settlement devices, the settlement devices being a first settlement device that settles for products registered on an installed other device or on the store's own device, and a second settlement device that settles for products registered on a portable other device, the program being characterized in that it causes the computer to function as a display means that displays the status of the first settlement device and the second settlement device. (4) The program reduces the burden on store staff.
[0217] In addition, a program for implementing the functions of each of the above-described devices (headquarters server 10, store controller 30, transaction status management device 40, settlement device 50, registration settlement device 51, registration settlement device 52, registration device 53, settlement device 54, registration settlement device 59, etc.) may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing of each of the above devices. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside the distribution server and accessible to distribute the program. The code of the program stored in the distribution server's recording medium may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined in the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds the program for a certain period of time, such as a volatile memory (RAM) in a computer system that becomes a server or a client when the program is transmitted via a network. The program may be for realizing part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]
[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. A store status management device capable of monitoring a plurality of payment terminals, The settlement device includes: A first settlement device that settles accounts for merchandise registered by the device itself or another installed device, and a second settlement device that settles accounts for merchandise registered by another portable device, The in-store situation management device includes: A display means for displaying the status of the first settlement device and the second settlement device is provided, The display means is An in-store situation 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 a plurality of operation modes, The display means is Displaying information indicating whether each of the settlement devices is the first settlement device or the second settlement device, as well as a current operation mode and an operator for accepting a change of the operation mode for the first settlement device.
2. The in-store situation control device according to claim 1.
3. The display means is The operation mode of the second settlement device is not displayed.
3. The in-store situation control device according to claim 2.
4. A program that causes a computer to function as a store status management device capable of monitoring a plurality of payment terminals, The settlement device includes: A first settlement device that settles accounts for merchandise registered by the device itself or another installed device, and a second settlement device that settles accounts for merchandise registered by another portable device, The computer, A display means for displaying the status of the first settlement device and the second settlement device. Function as a The display means is A program characterized by displaying whether or not the first settlement device or the second settlement device is equipped with a cash settlement unit.
Citation Information
Patent Citations
Device monitoring system
JP2014126998A
Check-out system, and control program
JP2016162108A
Merchandise sales data processing system and registration device
JP2017102728A
POS system and monitoring device
JP2019114187A
Portable terminal, sales data processing system, sales data processing method and program
JP2021012438A