Product sales data processing system and program

Abstract

To appropriately manage a portable terminal used for shopping by a customer at a store.SOLUTION: A commodity sales data processing system includes a portable terminal used by a customer registering a commodity in a transaction and a transaction information management device managing a transaction state. The commodity sales data processing system includes identification information output means for outputting identification information for identifying an own device in the portable terminal, counting means for counting the portable terminals outputting the identification information by the identification information output means in the transaction information management device, and notification means for making a notification when the number of portable terminals counted by the counting means satisfies a predetermined condition.SELECTED DRAWING: Figure 20

Description

[Technical Field]

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

[0002] BACKGROUND ART There is known a technology that allows customers to purchase products using a mobile device when shopping in a store (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] In the above-described shopping system in which customers use mobile devices (mobile terminals) to shop, it is preferable for a store, for example, to be able to appropriately manage the mobile terminals used in the store.

[0005] The present invention aims to enable appropriate management of mobile terminals used by customers for shopping in stores. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a product sales data processing system comprising a mobile terminal used by a customer to register a product in a transaction, and a transaction information management device that manages the transaction status, wherein the mobile terminal comprises an identification information output means that outputs identification information that identifies the device, and the transaction information management device comprises a counting means that counts the mobile terminals that have output identification information by the identification information output means, and an alert means that alerts when the number of mobile terminals counted by the counting means meets a predetermined condition.

[0007] One aspect of the present invention is a program for causing a computer serving as a server in a product sales data processing system having a mobile terminal used by a customer to register a product in a transaction and a transaction information management device that manages the transaction status to function as an identification information acquisition means that acquires identification information that identifies the mobile terminal and is output from the mobile terminal, a counting means that counts the mobile terminals whose identification information has been acquired by the identification information acquisition means, and a notification means that issues a notification when the number of mobile terminals counted by the counting means meets a predetermined condition. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of the configuration of a shopping system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of installation of a settlement device according to the present embodiment. [Figure 3] 1 is a diagram showing an example of the appearance of a settlement device according to an embodiment of the present invention; [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a settlement device according to the present embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device according to the present embodiment. [Figure 6] 1 is a diagram illustrating an example of the configuration of a transaction management device according to an embodiment of the present invention. [Figure 7] 3A to 3C are diagrams illustrating examples of customer information, store information, and cart information according to the present embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of a definition of a reserved product in the present embodiment. [Figure 9] 1 is a diagram illustrating an example of the configuration of a transaction information management device according to an embodiment of the present invention. [Figure 10] A sequence diagram showing an example of processing procedures executed by the customer terminal device, settlement device, and transaction management device in this embodiment in response to the accounting of one transaction in self-service operation. [Figure 11] FIG. 10 is a diagram showing an example of a screen of a shopping application in the present embodiment. [Figure 12]10A and 10B are diagrams showing an example of a registered product presentation screen and a screen displayed on the settlement device in this embodiment. [Figure 13] 1 is a diagram illustrating an example of the appearance of a charging device according to an embodiment of the present invention. [Figure 14] 10 is a flowchart illustrating an example of a processing procedure executed by the transaction management device in this embodiment in relation to identifying the type of customer terminal device. [Figure 15] FIG. 10 is a diagram illustrating an example of a terminal status screen according to the present embodiment. [Figure 16] FIG. 10 is a diagram showing an example of a transaction details screen in the present embodiment. [Figure 17] FIG. 10 is a diagram illustrating an example of a status confirmation screen according to the present embodiment. [Figure 18] FIG. 10 is a diagram showing an example of a product information input screen according to the present embodiment. [Figure 19] 10 is a flowchart showing an example of a processing procedure executed by the transaction management device and the transaction information management device in this embodiment in relation to notification in response to the rental terminal being taken out of the store. [Figure 20] 10 is a flowchart showing an example of a processing procedure executed by the lending terminal and the transaction information management device in relation to a notification of a non-return. DETAILED DESCRIPTION OF THE INVENTION

[0009] [Example of shopping system configuration] Fig. 1 shows an example of the configuration of a shopping system (an example of a product sales data processing system) according to this embodiment. The shopping system shown in Fig. 1 corresponds to a transaction (customer terminal device-compatible transaction) in which, for example, a customer registers the product they are purchasing by using a customer terminal device 50 (personal terminal 50A or rental terminal 50B) while removing the product from a shelf, and the same customer also uses a payment device 40 to pay for the registered product. The transaction here refers to the procedure performed for one transaction, including product registration and payment for the registered product. The shopping system of this embodiment includes a management device 10, a transaction management device 60, a settlement device 40, a customer terminal device 50, a transaction information management device 80, and a credit card settlement server 70.

[0010] The management device 10 and the settlement device 40 are installed in the store and are communicatively connected via a LAN 19 (which may be wired or wireless). The management device 10 is a business terminal used by store staff for store management, etc., and is capable of communicating with the transaction management device 60. The transaction information management device 80 is a business terminal used in the store to monitor the transaction status of customers who register items using the customer terminal device 50. The transaction status monitoring function of the transaction information management device 80 includes outputting information about the transaction status on the transaction information management device 80 by displaying it, as well as controlling transactions, such as releasing the hold status of a held item (described below) in response to a store staff member's operation. The transaction information management device 80 is capable of communicating with the transaction management device 60, and is capable of realizing the transaction status monitoring function by exchanging data with the transaction management device 60. Although four payment terminals 40 are shown in FIG. 1, the number of payment terminals 40 within one store is not particularly limited.

[0011] The customer terminal device 50 is operated by a customer (such as a shopper who is a member of the store, hereinafter simply referred to as a customer). In addition to typical communication and imaging functions (camera), the customer terminal device 50 has a recognition function that scans barcodes attached to products to read product codes, i.e., recognizes barcodes attached to products. Note that the recognition function of the customer terminal device 50 is only required to be able to read product codes, and does not necessarily have to be able to recognize which product the read product code belongs to. In other words, the customer terminal device 50 is only required to be able to read a product code from a barcode when the barcode exists as an object in an image captured by the imaging function (an image acquired as a through image).

[0012] In this embodiment, a customer can use either a personal terminal 50A or a rental terminal 50B as the customer terminal device 50 when shopping. The personal terminal 50A is a mobile terminal that is owned by the customer. Such a customer terminal device 50 may be a smartphone, tablet terminal, or the like owned by the customer. A shopping application having a function of registering products in accordance with the shopping system of this embodiment is installed on the smartphone, tablet terminal, or the like serving as the customer terminal device 50. The rental terminal 50B is a mobile terminal that is rented to a customer by the store. An application having a function of registering products in accordance with the shopping system of this embodiment is also installed in the rental terminal 50B. Furthermore, these customer terminal devices 50 may be used by customers in a manner that they are held in their hands, or may be used by customers in a state that they are attached to, for example, a shopping cart.

[0013] Furthermore, the customer terminal device 50 captures an image (e.g., releases the shutter) of the product (e.g., the surrounding area with the barcode attached) and generates the captured image (image data). The customer terminal device 50 may release the shutter in response to an operation by the customer who is the operator, but in this embodiment, it is preferable that the customer terminal device 50 releases the shutter at its own discretion.

[0014] Furthermore, the customer terminal device 50 may be equipped with an image recognition technology that extracts feature points from an image (through image, captured image) and recognizes the imaged subject (object, etc.). For example, the customer terminal device 50 may use the image recognition technology to identify (estimate) the captured product.

[0015] The settlement device 40 is a settlement device that can at least accept cash payments as a settlement method. The settlement device 40 is configured to be able to communicate with the transaction management device 60. Note that the settlement device 40 may be able to communicate with the transaction management device 60, for example, via a relay by the management device 10.

[0016] The transaction management device 60 manages transactions carried out in accordance with the shopping system of this embodiment.

[0017] The credit card payment server 70 executes payment processing corresponding to the credit card in response to a credit card payment request transmitted from the settlement device 40, the customer terminal device 50, etc.

[0018] The charging device 90 is provided in the store to charge the rental terminals 50B. The charging device 90 is configured to be able to charge, for example, a predetermined number of rental terminals 50B all at once. The charging device 90 is provided in a predetermined location, for example, at the entrance / exit of the store. Two charging devices 90 are shown in the figure. In other words, in this embodiment, multiple charging devices 90 may be installed in the store. The number of charging devices 90 to be installed may be determined according to the relationship between the number of rental terminals 50B provided in the store and the number of rental terminals 50B that can be charged by one charging device 90. When the rental terminal 50B is in a standby state and not being used by a customer, it is operated so that it is attached to the charging device 90 and is being charged.

[0019] [About the payment device] Figure 2 shows an example of the installation of the payment device 40. Figure 2(A) is a perspective view of the payment device 40 and other components as seen from the customer side. Figure 2(B) is a perspective view of the payment device 40 and other components as seen from the store clerk side. As shown in Figure 2(A), a counter is placed on the right side of the payment device 40 as seen from the customer side.

[0020] Figure 3 shows an example of the appearance of the settlement device 40. Figure 3(A) is a perspective view of the settlement device 40 as seen from the customer side. Figure 3(B) is a perspective view of the settlement device 40 as seen from the store clerk side. Fig. 4 is a diagram showing an example of the configuration of the settlement device 40. In Fig. 3 and Fig. 4, the same parts are given the same reference numerals.

[0021] An example configuration of settlement device 40 shown in Fig. 4 will be described below with reference to Fig. 3. Settlement device 40 includes a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a customer display unit 405, a customer scanner unit 406, a card payment unit 408, a change dispenser 409, a store clerk display unit 410, a key operation unit 411, a store clerk scanner unit 412, a printing unit 413, an audio output unit 414, and a communication unit 415. These can communicate with each other via a bus.

[0022] The CPU 401 is a central processing unit that controls the operation of the settlement device 40 by reading and executing programs stored in the ROM 402 . The ROM 402 is a read-only memory that stores various types of information used by the CPU 401, including programs.

[0023] The RAM 403 is a read / write memory that stores various types of information, such as information read from the ROM 402 or the hard disk 404, information acquired from the outside, and information generated during processing.

[0024] The hard disk 404 stores various types of information. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Furthermore, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information obtained from the outside, information generated during processing, and the like.

[0025] The customer-side display unit 405 is a touch display for customers, which displays various information to customers and accepts various inputs from customers. Customer-side scanner unit 406 is a scanner unit for customers, and for example, scans a barcode attached to a product to read the product code. Customer-side scanner unit 406 may also scan a code (barcode, 2D code, etc.) printed on a receipt (registered trademark) to read the information required for payment. Customer-side scanner unit 406 may also scan a code (2D code, etc.) displayed on the display unit of customer terminal device 50 to read the information required for payment.

[0026] Although customer-side scanner unit 406 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 customer-side display unit 405, the customer may operate (press) the preset key to register the product.

[0027] The card payment unit 408 is a payment mechanism that accepts various cards (credit cards, prepaid cards such as transportation cards, etc.). The card payment unit 408 of this embodiment includes a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient if it includes at least the card recognition unit. Note that the card recognition unit may also recognize various cards that are not directly used for payment (settlement) (for example, membership cards, point cards, etc.).

[0028] The change dispenser 409 (cash settlement unit) is a cash settlement mechanism that 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 dispenses the change from the output port. The change dispenser 409 faces the customer and is operated by the customer. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, the number of coins by denomination, etc.).

[0029] That is, the change dispenser 409 is used when settling the price of registered products in cash (currency) in the settlement device 40. The change dispenser 409 has a banknote insertion slot for inserting banknotes, a coin insertion slot for inserting coins, a banknote discharge slot for discharging banknotes, a coin discharge slot for discharging coins, a counting unit for counting the inserted or discharged currency, a currency transport mechanism between the insertion slot or discharge slot and the storage unit, the above-mentioned sensor, etc. The banknote insertion slot and coin insertion slot are also referred to as deposit insertion slots. The banknote discharge slot and coin discharge slot are also referred to as change discharge slots. The banknote insertion slot and banknote discharge slot may be a common unit, and the coin insertion slot and coin discharge slot may be a common unit.

[0030] The change dispenser 409 also counts the coins replenished during the closing process and stores them in the storage unit. The change dispenser 409 also counts the coins to be dispensed during the closing process and discharges them from the change discharge port. The closing process is a process of adjusting the amount of money stored in the change dispenser 409 (cash on hand / cash on hand) to a reference amount after the store has closed or before it has opened.

[0031] The store clerk's display unit 410 is a touch display for the store clerk, and displays various information to the store clerk and receives various inputs from the store clerk. The key operation unit 411 is made up of various keys (buttons) and receives various inputs from the store clerk. The store clerk scanner unit 412 is a scanner unit for store clerks, and for example, scans barcodes attached to products to read product codes. The store clerk scanner unit 412 also scans barcodes attached to store clerk name tags to read store clerk codes.

[0032] Although the clerk-side scanner unit 412 is used when the clerk registers a product, the 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 the key operation unit 411, the clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the clerk-side display unit 410, the clerk may operate that preset key to register the product.

[0033] The printing unit 413 prints and issues various media (receipts, bills, etc.). The printing unit 413 can be rotated to face from the store clerk side to the customer side, or from the customer side to the store clerk side (the direction of the media issuing port). The orientation of the printing unit 413 may be changed manually, or may be changed automatically (mechanically controlled, etc.) in response to, for example, a transition (switching) of the operating mode described below. The correct orientation of the printing unit 413 may be detected by a sensor or the like.

[0034] The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs audio guidance and the like. The communication unit 415 executes communication with other devices (other settlement devices 40 and management device 10).

[0035] In addition, the settlement device 40 of this embodiment can be switched between a total of four operating modes: a customer terminal device compatible settlement mode, which is set to perform settlement processing based on customer terminal device compatible accounting, and three accounting modes (first to third accounting modes) corresponding to three different patterns of accounting (product registration, settlement). The first payment mode is an operating mode in which a store clerk performs product registration operations and operations corresponding to payment on the payment device 40. The second payment mode is an operating mode in which a store clerk performs product registration operations on the payment device 40, and a customer performs operations corresponding to payment on the same payment device 40. The third payment mode is an operating mode in which a customer performs product registration operations and operations corresponding to payment on the payment device 40. As a result, in a store that has introduced the shopping system of this embodiment, some of the multiple payment devices 40 can be set to customer terminal device-compatible payment mode to enable customer terminal device-compatible payment, and other payment devices 40 can be set to, for example, first or second payment mode so that a store clerk can handle the payment with the customer. Note that some of the other payment devices 40 may be set to third payment mode.

[0036] [Customer terminal device configuration example] 5 shows an example of the configuration of customer terminal device 50. Customer terminal device 50 in the figure includes a CPU 501, a storage unit 502, a RAM 503, a display unit 504, an operation unit 505, an imaging unit 506, a network-compatible communication unit 507, and a positioning unit 508. The CPU 501 is a central processing unit that controls the operation of the customer terminal device 50 by reading and executing programs stored in the storage unit 502 . The storage unit 502 is an auxiliary storage device for the CPU 501, and stores various types of information used by the CPU 501, including programs. The RAM 503 is the main storage device of the CPU 501 . The display unit 504 displays images according to the display control of the CPU 501. The display unit 504 may be configured as a touch panel that allows operations to be performed on the screen. The operation unit 505 collectively indicates various operators provided on the customer terminal device 50 and various input devices connected to the customer terminal device 50 . The imaging unit 506 captures images under the control of the CPU 401. The imaging unit 506 of this embodiment can also function as a part that reads two-dimensional codes in a code reader that processes the two-dimensional codes. The network-compatible communication unit 507 is a unit that performs communication wirelessly via a network. The network-compatible communication unit 507 enables the customer terminal device 50 to communicate with the transaction management device 60. The positioning unit 508 measures its own position and acquires position information indicating its own position. The positioning unit 508 may be configured to include a device that uses a positioning system such as a GPS (Global Positioning System). The positioning unit 508 may also acquire position information indicating its own position by communicating with a wireless LAN access point in a store or a beacon.

[0037] [Example of transaction management device configuration] 6 shows an example of the configuration of transaction management device 60. Transaction management device 60 in the figure comprises a CPU 601, a storage unit 602, a RAM 603, and a network-compatible communication unit 604. The CPU 601 is a central processing unit that controls the operation of the transaction management device 60 by reading and executing programs stored in the storage unit 602 . The storage unit 602 is an auxiliary storage device for the CPU 601, and stores various types of information used by the CPU 601, including programs. The RAM 603 is the main storage device of the CPU 601 . The network-compatible communication unit 604 is a part that performs communication via a network.

[0038] The memory unit 602 of the transaction management device 60 stores customer information, store information, product information, and cart information.

[0039] [Information stored in the transaction management device] The customer information stored in the memory unit 602 is information for managing individual customers. The transaction management device 60 generates customer information when a customer is registered (it may be considered that a customer has been registered when their customer information is stored). The transaction management device 60 also updates the customer information as appropriate based on cart information, etc. The transaction management device 60 may, for example, refer to the cart information at a predetermined time every day and update the customer information.

[0040] 7(A) shows an example of customer information stored in the memory unit 602 of the transaction management device 60. The customer information in this figure includes customer identification information, customer name, customer registration date, cancellation information, customer rank, number of points, etc. The customer identification information is identification information that uniquely identifies a customer. The customer identification information may be application identification information that is uniquely assigned to each installed shopping application when the shopping application of this embodiment is installed. The application identification information may be a number that is uniquely (e.g., sequentially) assigned to each installed shopping application. Alternatively, the application identification information may be terminal identification information that is unique to the customer terminal device 50 on which the shopping application is installed.

[0041] For example, if the customer terminal device 50 is a personal terminal 50A, the terminal identification information may be hardware identification information assigned to the hardware of the customer terminal device 50 so as to be unique, such as a telephone number assigned to the customer who is the user of the personal terminal 50A, or a MAC (Media Access Control) address.

[0042] The customer name is the customer's name or nickname, etc. The customer registration date is the date and time the customer was registered. The cancellation information is information regarding the cancellation of registered products after registration. The customer rank is a rank based on the customer's purchase history. When generating customer information for a new customer, the customer identification information, customer name, and customer registration date are generated, but since this is before the start of the actual transaction (product registration), other information (cancellation information, etc.) is not generated.

[0043] The transaction management device 60 generates and stores customer identification information, for example, when a customer is registered (for example, when the customer terminal device 50 downloads or installs a shopping application from an external device (for example, a predetermined server that provides all applications, the transaction management device 60) to use the shopping service provided by the transaction management device 60). Furthermore, when a customer is registered, the transaction management device 60 acquires information entered in the name field of the registration form (input form) using the customer terminal device 50 as a personal terminal 50A, and stores it as the customer name. Furthermore, the transaction management device 60 acquires the current date and time when the customer is registered, and stores it as the customer registration date.

[0044] In addition, instead of or in addition to storing customer information in its own memory, the transaction management device 60 may store some or all of the customer information in another device (such as a file server accessible to the transaction management device 60).

[0045] 7(B) shows an example of store information stored in the memory unit 602 of the transaction management device 60. The store information in the figure includes store identification information, store name (branch name), store identification information 1, and store identification information 2. The store identification information is identification information that uniquely identifies a store. The store identification information shown in Fig. 7(B) is composed of a store (trade name) or company code and a branch code. The store name is the name of the store. The store name shown in Fig. 7(B) is composed of the store (trade name) or company name and the branch name. The store identification information 1 is information (store identification code) of a two-dimensional code (QR code (registered trademark) or the like) for identifying the store where the transaction takes place (the store where the product is bought and sold). The store identification information 2 is store location information (GPS information) for identifying the store where the transaction is to be made. In the example shown in FIG. 7(B), the store identification information and the store specifying information 1 are different, but the store identification information and the store specifying information 1 may be the same.

[0046] The transaction management device 60 may acquire and store store information from an external source (such as a server (not shown) at a headquarters that oversees each store). The transaction management device 60 may also store some or all of the store information in another device (such as a file server accessible to the transaction management device 60) instead of or in addition to storing the store information in its own memory.

[0047] The product information is information acquired from, for example, the store management device 10, and is information about products sold in the store. The product information for one product includes information such as a product code (product identifier), product name, and price.

[0048] Cart information is information used to manage individual transactions. The transaction management device 60 generates cart information at the start of a transaction. The transaction management device 60 also updates the cart information as the transaction progresses (each time a product is registered) (it may be considered that a product has been registered when it is stored in the cart information).

[0049] FIG. 7(C) is an example of cart information stored in the memory unit 602 of the transaction management device 60. The cart information in the figure includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, reserved product information, cancellation information, and the like.

[0050] The cart identification information is identification information that uniquely identifies the cart information. For example, the cart identification information includes store identification information, a date, and a serial number (for example, a serial number for each store and date). The transaction start date and time is the date and time when the transaction started. The transaction start date and time may be, for example, the date and time when the cart information was created. The transaction start date and time may also be the date and time when the first item was registered (the date and time when the registered item information (registered item 1) in FIG. 7(C) was stored). The date and time when the cart information was created and the date and time when the first item was registered may both be stored separately.

[0051] The transaction end date and time is the end date and time of the transaction. For example, the transaction start date and time may be the settlement date and time.

[0052] The customer / application identification information is either customer identification information that identifies the customer of the transaction, or application identification information that indicates the shopping application installed on the corresponding customer terminal device 50 .

[0053] When generating cart information, cart identification information, transaction start date and time, and customer identification information are generated, but other information (transaction end date and time, etc.) is not generated because the actual transaction (product registration) has not yet started. The settlement date and time may be the settlement start date and time or the settlement end date and time. Both the settlement start date and time and the settlement end date and time may be stored separately as the transaction end date and time.

[0054] Registered product information (total) is information that is updated each time a product is registered. Registered product information (total) includes the number of products (number of products), estimated subtotal amount (for example, the subtotal amount before discounts, etc. are reflected), subtotal amount, etc. Registered product information (registered product 1) is the registration information for one product item. Registered product information (registered product 2) is the registration information for two products. In the example shown in Figure 7(C), registered product information (registered product 3) to registered product information (registered product 5) are omitted from the illustration. Registered product information (N; N is an integer) includes the product code, product name (product name), price, etc.

[0055] The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management device 60 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as information to determine whether or not to apply a special offer such as a limited time offer and the effect of applying the special offer.

[0056] The reserved product information (total) is information that is updated every time a reserved product is registered. A reserved product is a product that was not registered properly due to a specific reason and is registered in a temporarily reserved state. The reserved product information (total) includes the number of reserved products (number of products), the number of reserved products that are NO-FILE, and the number of reserved products that cannot be read (check for unauthorized operations).

[0057] NO-FILE refers to a product whose barcode or product code was successfully scanned (the product code was read) at the store, but the product code is not stored in the product information (a product whose product information is not registered).

[0058] A read NG refers to a failure to scan the product code at the store (the product code could not be read), or a product whose product code failed to be scanned at the store. In other words, a read NG refers to a timeout process when it is possible to determine that the barcode has not been recognized even after the product has been imaged for a certain period of time using image recognition technology, or a product that has been timed out. For example, if the barcode cannot be correctly acquired (recognized) even though the customer has performed the operation to read it due to wrinkles in the package, blurred or dirty barcode printing, or the barcode being printed on a transparent film, it will be determined that the barcode cannot be read.

[0059] Reserved Product Information (Reserved Product 1) is information on reserved product 1. Reserved Product Information (Reserved Product 2) is information on reserved product 2. Reserved Product Information (Reserved Product 3) is information on reserved product 3.

[0060] The reserved product information (reserved product N; N is an integer) includes the reserved product type (information indicating whether the reserved product is NO-FILE or NG for reading) and image data (image data captured when reading was NG). For example, if the Nth item is a reserved product due to NO-FILE, the reserved product information (reserved product N) includes the reserved product type "1 (NO-FILE)" and image data. Also, if the Nth item is a reserved product due to reading being NG, the reserved product information (reserved product N) includes the reserved product type "2 (NG for reading)" and image data.

[0061] Furthermore, the cart information of this embodiment may be provided with a terminal type flag as shown in the figure. The terminal type flag is a flag that indicates whether the corresponding customer terminal device 50 is a personal terminal 50A or a rental terminal 50B. In the example of the figure, the terminal type flag has a value of "0" that indicates a personal terminal 50A, and a value of "1" that indicates a rental terminal 50B.

[0062] In addition, instead of or in addition to storing the cart information in its own memory, the transaction management device 60 may store some or all of the cart information in another device (such as a file server accessible to the transaction management device 60).

[0063] 8 shows an example of definition of reserved items corresponding to cart information in this embodiment. In this figure, an example is shown in which reserved items are classified into eight categories. Classification numbers "1" to "8" are assigned to each of the eight reserved item classifications. The classification of the reserved product with classification number 1 is "NON-FILE" as explained in FIG. The classification of the reserved product with classification number 2 is "reading not allowed" as explained in FIG.

[0064] The classification of the reserved product with classification number 3 is "pseudo scan input." A reserved product with "pseudo scan input" is a product for which the customer attempted to have the customer terminal device 50 read the product code, but the customer terminal device 50 was unable to read the code properly.

[0065] As a specific example, a "pseudo scan input" situation occurs when the product is brought into the imaging range of the imaging unit 506, but the product code is not brought into the imaging range of the imaging unit 506. Furthermore, "pseudo scan insertion" corresponds to a situation in which the product is brought into the imaging range of the imaging unit 506, but an image of a part without a code is captured. Furthermore, "pseudo scan insertion" refers to a situation in which a product is placed within the imaging range of the imaging unit 506 with the code portion hidden by a finger or the like. In addition, a "pseudo scan input" situation occurs when the product code is captured by the imaging unit 506, but the product is passed through the imaging range of the imaging unit 506 at a speed that the customer terminal device 50 cannot read the code.

[0066] The classification of reserved items with classification number 4 is "non-scanned entry." Reserved items with "non-scanned entry" are items that were added to the shopping cart without performing an operation to position the item within the imaging range of imaging unit 506. This non-scanning insertion can occur, for example, when the customer terminal device 50 is fixedly attached to a shopping cart and is capable of capturing an image of the inside of a shopping basket placed in the shopping cart. For example, when the customer terminal device 50 determines, based on the captured image, that a product has been placed in the shopping cart even though the product code has not been scanned, it can determine that a non-scanning insertion has occurred.

[0067] The classification of reserved items with classification number 5 is "age verification items." "Age verification items" are items such as alcohol and tobacco that require a store clerk to verify the customer's age before selling them.

[0068] The classification of reserved goods with classification number 6 is "pharmaceuticals." "Pharmaceuticals" are goods that require a qualified person, such as a pharmacist, to ask the purchaser for confirmation.

[0069] The classification of reserved items with classification number 7 is "items with security tags." "items with security tags" are items that have security tags attached and therefore require a store clerk to remove the security tags from the items when they are sold.

[0070] The classification of reserved products with classification number 8 is "cancelled products." "Cancelled products" are products that were once registered but were canceled by a customer's cancellation operation on the customer terminal device 50. "Cancelled products" are taken from the customer by a store clerk, for example, at the time of payment.

[0071] The product master is stored, for example, in the management device 10. The product master stores product information for each product sold in the store. The product information for one product includes a predetermined number of information items, including a product code and a product name. Transaction management device 60 stores the product master data acquired from management device 10. Transaction management device 60 uses the stored product master data for processes related to product registration, etc.

[0072] For reserved products that fall under classification number 1 "NON-FILE," the product code was obtained by code scanning in response to the product registration operation, but the product information associated with the obtained product code has not been registered in the product master. Therefore, it has not been determined which of the products registered in the product master the reserved product that falls under classification number 1 "NON-FILE" is. For pending products that fall into one of the three categories of classification numbers 2 to 4, "Read NG," "Pseudo scan input," and "Non-scan input," the product code failed to be acquired as a result of the code scan in response to the product registration operation. For this reason, it is not possible to identify which of the products registered in the product master the pending products that fall into one of the three categories of classification numbers 2 to 4, "Read NG," "Pseudo scan input," and "Non-scan input" are.

[0073] Unidentified products are those that fall into any of the four categories of "NON-FILE," "Read NG," "Pseudo-scanned input," and "Non-scanned input" in classification numbers 1 to 4 out of classification numbers 1 to 7. Unidentified products are products whose registration results are incomplete, for example, because it was not possible to identify which of the products registered in the product master it is. Unidentified products are further divided into code-acquired products, such as classification number 1 "NON-FILE," whose product code has been acquired through product registration operations, and code-unacquired products, such as classification numbers 2 to 4 "Read NG," "Pseudo-scan input," and "Non-scan input," whose product code has not been acquired through product registration operations.

[0074] In addition, instead of or in addition to storing the cart information in its own memory, the transaction management device 60 may store some or all of the cart information in another device (such as a file server accessible to the transaction management device 60).

[0075] [Example of configuration of transaction information management device] 9 shows an example of the configuration of transaction information management device 80. Transaction information management device 80 in the figure includes a CPU 801, a storage unit 802, a RAM 803, an in-store communication unit 804, a network-compatible communication unit 805, a display unit 806, and an operation unit 807. The CPU 801 is a central processing unit that controls the operation of the transaction information management device 80 by reading and executing programs stored in the storage unit 802 . The storage unit 602 is an auxiliary storage device for the CPU 801, and stores various types of information used by the CPU 801, including programs. The RAM 803 is the main storage device of the CPU 801 . The in-store communication unit 804 communicates with terminals such as the settlement device 40 and management device 10 within the store via the LAN 19 . Network-compatible communication unit 805 is a component that communicates with the outside via a network. In the case of transaction information management device 80, network-compatible communication unit 805 can communicate with transaction management device 60 on the cloud. The display unit 806 displays an image under the control of the CPU 801. The display unit 806 may be configured as a touch panel. The operation unit 807 collectively refers to the operators provided in the transaction information management device 80 and the input devices connected to the transaction information management device 80 .

[0076] [Example of basic processing procedure for self-operation] The sequence diagram in Figure 10 shows an example of the processing procedure executed by customer terminal device 50, settlement device 40, and transaction management device 60 in response to the accounting of one transaction in self-service operation. Specifically, the processing in Figure 10 shows an example of the processing of customer terminal device 50, settlement device 40, and transaction management device 60 from when a customer registers a product to be purchased from products displayed in the store until the payment for the registered product is completed. In addition, in explaining the same figure, an example will be given in which the customer terminal device 50 is a personal terminal 50A.

[0077] Step S1: Customer terminal device 50 acquires information identifying the store (store identification information). For example, a two-dimensional code indicating a store identification code for identifying the store may be displayed near the entrance of the store (for example, by outputting the two-dimensional code on a display screen or attaching a medium with the two-dimensional code printed on it), and a customer visiting the store may scan (read) the two-dimensional code with customer terminal device 50, thereby allowing customer terminal device 50 to acquire the store identification information. Note that when a customer visiting the store launches a shopping application, a start-up screen may be displayed instructing the customer to scan the two-dimensional code, or when a customer visiting the store scans the two-dimensional code with customer terminal device 50, the shopping application may be launched and a start-up screen may be displayed informing the customer that the transaction management device 60 is currently connected.

[0078] Also, for example, since a store is identified by its location, a customer who visits the store may obtain location information (GPS information) at the store using the customer terminal device 50 (i.e., the store's location information may be obtained as store identification information). When a customer who visits the store starts a shopping application, the location information may be obtained, and a screen may be displayed as a startup screen informing the customer that the application is currently connected to the transaction management device 60. If multiple stores are detected from the location information and it is not possible to identify one, a selection screen may be displayed to allow the customer to make a selection. Alternatively, the application may be switched to a mode in which a two-dimensional code is forcibly obtained. Also, for example, the customer terminal device 50 may acquire store-specific information by communicating with a beacon installed in a predetermined location in the store.

[0079] 11(A) shows an example of the start-up screen of the shopping application displayed on the display unit 504 of the customer terminal device 50. The start-up screen in the figure displays the store name. This store name is displayed based on the store-specific information acquired in step S1. When a customer wants to start registering a product for shopping, the customer operates a transaction start instruction button BT10 arranged on the start-up screen. In response to operation of the transaction start instruction button BT10, the customer terminal device 50 transmits a transaction start request including the acquired store identification information and customer identification information to the transaction management device 60. The transaction start request may be transmitted in response to a customer operation on the customer terminal device 50 as described above, or may be transmitted in response to the acquisition of store identification information without receiving any particular operation. Regarding customer identification information, the information entered in the name field of the registration form using the customer terminal device 50 during customer registration (when downloading or installing the shopping application on the customer terminal device 50) may be stored in the customer information of the transaction management device 60, but it may also be stored in the memory of the customer terminal device 50 in addition to the transaction management device 60. Note that when a store is identified (when the product registration initial screen described below is acquired), the store name, currently offered services (information on flyers being distributed that day), and available coupon information of the store may be displayed on a screen (the product registration initial screen or a screen separate from the product registration initial screen). Note that service and coupon information may be acquired from the transaction management device 60, for example, as screen information. The transaction start request may include application identification information that uniquely identifies the shopping application instead of the customer identification information.

[0080] In addition, the destination information (address of the transaction management device 60) may also be obtained when registering the customer (when downloading or installing the shopping application to the customer terminal device 50) and stored in the memory of the customer terminal device 50. In addition, when scanning a two-dimensional code, the destination information may also be converted into a two-dimensional code in addition to the store identification information, and by scanning the two-dimensional code with the customer terminal device 50, the customer terminal device 50 may obtain the destination information along with the store identification information.

[0081] Step S2: The transaction management device 60, which has received the customer identification information and store identification information as a transaction start request from the customer terminal device 50, generates cart information for the transaction. Note that, in the initial state of the generated cart information, the cart identification information, transaction start date and time, and customer identification information are stored, but since the actual transaction (product registration) has not yet begun, other information (transaction end date and time, product information (registered product information, pending product information), etc.) is not stored.

[0082] As described above, the transaction management device 60 stores store information such as that shown in Figure 7(B), so when it receives store identification information (it also receives customer identification information) as a transaction start request from the customer terminal device 50, if the received store identification information is a two-dimensional code, it acquires the store identification information by referring to store identification information 1, and if the received store identification information is location information (GPS information), it acquires the store identification information by referring to store identification information 2. Note that if the store identification information received from the customer terminal device 50 is a two-dimensional code of the store identification information, the transaction management device 60 can simply acquire it as is.

[0083] In other words, when the transaction management device 60 receives customer identification information and store identification information from the customer terminal device 50 as a transaction start request, it acquires the store identification information from the store identification information received from the customer terminal device 50, acquires the current date, issues (assigns) a serial number, combines the store identification information with the current date and serial number, and stores the combined information as cart identification information in the cart information. Furthermore, when the transaction management device 60 receives store identification information and customer identification information from the customer terminal device 50 as a transaction start request, it acquires the current date and time and stores the current date and time as the transaction start date and time (generation date and time) in the cart information. Furthermore, when the transaction management device 60 receives store identification information and customer identification information from the customer terminal device 50 as a transaction start request, it stores the customer identification information received from the customer terminal device 50 as customer identification information in the cart information.

[0084] Step S3: The transaction management device 60, which has generated the cart information for the transaction, generates product registration initial screen information (screen information for the product registration screen, which is the initial screen) and transmits it to the customer terminal device 50. Specifically, the transaction management device 60, for example, generates product registration initial screen information and transmits the generated product registration initial screen information to the customer terminal device 50 together with cart identification information.

[0085] Step S4: The customer terminal device 50, which has received the cart identification information and the product registration initial screen information from the transaction management device 60, stores the cart identification information and displays the registration screen on the display unit. Specifically, the customer terminal device 50 displays the product registration initial screen, for example, as shown in Figure 11(B).

[0086] Step S5: In response to a customer's operation, the customer terminal device 50 scans the barcode attached to the product and reads the product code. In the figure, it is assumed that the barcode scan was successful. Steps S5 to S9 are repeatedly executed each time the barcode attached to the product is scanned.

[0087] The customer terminal device 50 that has acquired the barcode transmits to the transaction management device 60 the cart identification information and the product registration information including the product code obtained by scanning.

[0088] Step S6: Upon receiving product registration information (cart identification information and product code) from the customer terminal device 50, the transaction management device 60 identifies the cart information for the transaction from the cart identification information contained in the received product registration information.

[0089] Step S7: The transaction management device 60 updates the product data in the identified cart information. Specifically, if the received product registration information includes a product code for item N, the transaction management device 60 stores the product code as the product code of the registered product information (registered product N) in the identified cart information, obtains the product name and price corresponding to the product code from the product information, and stores them as the product and price of the registered product information (registered product N). The transaction management device 60 also updates the registered product information (total) in the identified cart information.

[0090] Step S8: After updating the product data in the cart information, the transaction management device 60 generates product registration update screen information (screen information of the product registration screen, which is the update screen to which the registered product has been added) and transmits it to the customer terminal device 50. Specifically, the transaction management device 60 generates product registration update screen information such that the customer terminal device 50 displays a product registration update screen to which the list item of the product currently registered in the registered product list has been added, as shown in Figure 11 (C), for example, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0091] The product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the customer terminal device 50 after "XX bread" has been registered as the third product item. In other words, when "XX yogurt" is stored in the cart information as the first item, the transaction management device 60 generates product registration update screen information such that "XX yogurt" is displayed on the customer terminal device 50 and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information; when "XX chocolate" is stored in the cart as the second item, the transaction management device 60 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed on the customer terminal device 50 and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information; and when "XX bread" is stored in the cart information as the third item, the transaction management device 60 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed on the customer terminal device 50 as shown in Figure 11 (C), and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0092] In response to the registration of one product, a registered product presentation screen WD1 may be displayed, presenting the currently registered product, as shown in Fig. 12(A), for example. Furthermore, the registered product presentation screen WD1 in the same figure shows an example in which, in response to the product being available for eating in, a "Yes" button BT1 and a "No" button BT2 are displayed to confirm with the customer whether or not they wish to eat in. In this case, the price of the product will be calculated so that the consumption tax rate for the product is different when the "Yes" button BT1 is operated and when the "No" button BT2 is operated.

[0093] Step S9: The customer terminal device 50, which has received the cart identification information and product registration update screen information from the transaction management device 60, adds the product to the registration screen. Specifically, the customer terminal device 50 displays a product registration update screen such as that shown in FIG. 11(C). As described above, the product registration screen (product registration update screen) shown in FIG. 11(C) is displayed on the customer terminal device 50 after "XX bread" has been registered as the third product item.

[0094] Step S10: The customer terminal device 50 accepts a payment instruction operation as an operation by the customer, for example, by touching the "Proceed to Checkout" button shown in FIG.

[0095] Step S11: The customer terminal device 50 that has accepted the payment transition instruction operation generates a two-dimensional code. That is, the customer terminal device 50 converts information (e.g., cart identification information) required to execute the payment process for the items purchased by the customer terminal device 50 into a two-dimensional code. The customer terminal device 50 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, a code display screen with a two-dimensional code arranged as shown in FIG. 11(D) is displayed on the display unit.

[0096] Step S12: The settlement device 40 scans (reads) the two-dimensional code displayed on the display unit of the customer terminal device 50. For example, the settlement device 40 scans the two-dimensional code displayed on the display unit of the customer terminal device 50 that is pointed by the customer within the recognition range of the customer-side scanner unit 406.

[0097] Step S13: The settlement device 40 reads the two-dimensional code displayed on the display unit of the customer terminal device 50 and requests the transaction management device 60 to calculate the subtotal. For example, the settlement device 40 sends a calculation request (subtotal calculation request information) to the transaction management device 60 requesting the calculation of the subtotal, together with the cart identification information obtained from the two-dimensional code.

[0098] Step S14: The transaction management device 60 receives the cart identification information and the sub-calculation request information from the customer terminal device 50 and identifies the cart information of the transaction from the cart identification information.

[0099] Step S15: After identifying the cart, transaction management device 60 calculates the subtotal amount using information such as prices in the registered product information included in the cart information corresponding to the identified cart information.

[0100] Step S16: After calculating the subtotal, the transaction management device 60 updates the cart information (storing the subtotal (calculated subtotal)) and sends the subtotal information indicating the calculated subtotal to the settlement device 40 together with the cart identification information.

[0101] Step S17: Upon receiving the cart identification information and subtotal information from the transaction management device 60, the settlement device 40 displays the subtotal amount on the customer side display unit 405, for example, as shown in FIG. 12(B).

[0102] Step S18: The settlement device 40, which has displayed the subtotal on the customer-side display unit 405, executes the payment (settlement). Specifically, the settlement device 40 accepts the selection of the payment type. In the case of cash, it accepts the deposit, calculates the amount of change, and, if there is change, dispenses the change and issues a receipt. Furthermore, when the settlement is complete, the settlement device 40 sends settlement completion information along with the cart information to the transaction management device 60, and the transaction management device 60 stores the transaction completion date and time (settlement date and time) for that cart.

[0103] After scanning a product, the customer terminal device 50 transmits the product code to the transaction management device 60 (S5). However, the customer terminal device 50 may be configured not to transmit product codes for products (e.g., products scanned at another store) other than those scanned within the store (the store where the customer visited and displayed the product registration initial screen). For example, the customer terminal device 50 acquires and stores location information (GPS information) when the customer visits the store (or when the product registration initial screen is displayed). The customer terminal device 50 also acquires location information when scanning each product and compares the location information acquired when the customer scanned the product with the location information acquired when the customer visited the store (or when the product registration initial screen is displayed). If the two information match (or approximately match), the customer terminal device 50 may permit the product code of the product to be transmitted to the transaction management device 60. If the two information do not match (or approximately match), the customer terminal device 50 may prohibit the product code of the product from being transmitted to the transaction management device 60. This makes it possible to prevent inappropriate product registration (for example, product registration to a cart created at another store, etc.).

[0104] When the payment terminal 40 prohibits the transmission of the product code as described above, after scanning the product, the payment terminal 40 may display an error message (e.g., "Registration is not possible because the product is not in the XX store") on the customer display unit 405. The payment terminal 40 may also display the above message on the clerk display unit 410 instead of or in addition to the message on the customer display unit 405.

[0105] Furthermore, after reading the two-dimensional code displayed on the display of the customer terminal device 50, the settlement device 40 requests the transaction management device 60 to calculate a subtotal (S13). However, the settlement device 40 may not request calculation of a subtotal for products other than those scanned in the store (e.g., products scanned at other stores). For example, the settlement device 40 references the store identification information of the store (it may store and reference the store identification information of the store in its own settlement device 40, or it may reference store identification information stored in another accessible device), and when it reads the two-dimensional code displayed on the display of the customer terminal device 50, it compares the cart identification information obtained from the two-dimensional code with the store identification information of the store. The settlement device 40 may then permit the request for calculation of a subtotal if the store identification information included in the cart identification information is configured to include the store identification information of the store, but may prohibit the request for calculation of a subtotal if it is not configured to include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payments for products registered at other stores, etc.).

[0106] When the payment settlement device 40 prohibits the request for the subtotal amount as described above, after reading the two-dimensional code, the payment settlement device 40 may display an error message (e.g., "Payment cannot be made because it includes products not from store X") on the customer-side display unit 405. The payment settlement device 40 may also display the above message on the clerk-side display unit 410 instead of or in addition to the message on the customer-side display unit 405.

[0107] In the example of the processing procedure in Figure 10, the transaction management device 60 calculates the subtotal. However, for example, the settlement device 40 may acquire cart information from the transaction management device 60 and calculate the subtotal based on the acquired cart information. Alternatively, the transaction management device 60 may send cart information to the management device 10 and request calculation of the subtotal, and the management device 10 may calculate the subtotal using the received cart information and send the calculated subtotal to the settlement device 40 via the transaction management device 60.

[0108] During the settlement process, the transaction management device 60 may check the cancellation status of the customer's products based on the customer information and cart information of the customer, and determine whether or not to issue a warning against fraud. If it is determined that a warning should be issued, the transaction management device 60 may, for example, cause the settlement device 40 to issue a warning notification.

[0109] Furthermore, during the checkout process, the transaction management device 60 may determine whether the product information included in the cart information includes any reserved items, and if so, may request the checkout device 40 to issue an instruction to correct the reserved items. Upon receiving the request to issue an instruction to correct the reserved items, the checkout device 40 displays a message indicating that there are reserved items, as shown in FIG. 12(C). Upon confirming the message, the store clerk may cancel (correct) the reserved items by entering the price corresponding to the reserved items or canceling the reserved items.

[0110] In the example of the processing procedure shown in Fig. 10, each time customer terminal device 50 scans the code information of a product and reads the product code, customer terminal device 50 transmits the read product code to transaction management device 60. That is, in the example of the processing procedure shown in Fig. 10, each time customer terminal device 50 executes product registration processing in response to the reading of a product code, it transmits product registration information including the product code obtained by the product registration processing to transaction management device 60. In this case, each time product registration information is received from customer terminal device 50, transaction management device 60 stores registered product information corresponding to the product code included in the product registration information in cart information identified by cart identification information included in the product registration information.

[0111] In this embodiment, the product registration information may be processed in the following procedure, which differs from that shown in FIG. In other words, customer terminal device 50 stores the product codes acquired by the product registration process in one transaction without transmitting them until a payment instruction is issued. Then, in response to the payment instruction being issued, customer terminal device 50 transmits the product registration information, including one or more product codes, that it has stored to transaction management device 60. Transaction management device 60 stores registered product information corresponding to each of the one or more product codes included in the product registration information in cart information identified by cart identification information included in the received product registration information. In other words, customer terminal device 50 in this embodiment transmits the product registration information in bulk in response to a payment instruction. In this way, when customer terminal device 50 transmits product registration information in bulk in response to a payment transition instruction, the number of communications between customer terminal device 50 and transaction management device 60 can be reduced, thereby reducing the processing load and power consumption of customer terminal device 50. In addition, the amount of traffic between customer terminal device 50 and transaction management device 60 can also be reduced.

[0112] [About using rental devices] In the shopping system of this embodiment, a personal terminal 50A and a rental terminal 50B are available as customer terminal devices 50. By allowing customers to use rental terminal 50B, even customers who do not own a mobile terminal such as a smartphone that can be used as a personal terminal can shop using customer terminal device 50. Furthermore, even customers who own a mobile terminal such as a smartphone can actually try out a shopping application by using rental terminal 50B when considering installing it on their mobile terminal and using it for shopping.

[0113] The flow of procedures when a customer uses rental terminal 50B to make a purchase will be described. When a customer enters the store, he or she goes to the rental corner for rental terminal 50B. At the rental corner, rental terminal 50B in a standby state is placed in a state of being charged by charging device 90.

[0114] FIG. 13 shows an example of the appearance of a charging device 90. The charging device 90 in the figure shows an example in which five terminal holders 92 are provided on a main body 91. As shown in the figure, the rental terminal 50B is loaded so that it is leaned against the terminal holder 92. In this loaded state, contactless charging (wireless power supply) is performed from the terminal holder 92 to the rental terminal 50B. The contactless charging method supported by the charging device 90 is not particularly limited, and may include an electromagnetic induction method, a magnetic resonance method, etc.

[0115] The charging device 90 in the figure has five terminal holders 92, and can charge five rental terminals 50B simultaneously. Note that the number of terminal holders 92 that a charging device 90 has is not particularly limited. In other words, the number of rental terminals 50B that can be charged simultaneously by one charging device 90 is not particularly limited. Furthermore, the number of charging devices 90 installed at one rental corner may be determined according to the relationship between the number of rental terminals 50B to be prepared at that rental corner and the number of rental terminals 50B that can be charged by one charging device 90. In the case of a charging device 90 that performs contactless charging as shown in the figure, there is no need for a one-to-one correspondence between the terminal holders 92 and the rental terminals 50B. For example, when a store clerk or a customer wants to charge one rental terminal 50B, they may load the rental terminal 50B into any of the available terminal holders 92.

[0116] The customer picks up any of the rental terminals 50B set in the charging device 90. The display unit 504 of the rental terminal 50B, which has been in standby mode, displays the shopping application startup screen (FIG. 11(A)). The customer operates the transaction start instruction button BT10 on the startup screen of the rental terminal 50B that they have picked up. Thereafter, the customer can use the rental terminal 50B as the customer terminal device 50 to register products while having the product codes read as described above. Once product registration is complete, the customer performs a payment transition instruction operation to display on the rental terminal 50B a code display screen (FIG. 11(D)) on which a two-dimensional code is displayed. The customer then has the payment device 40 read the two-dimensional code displayed on the code display screen and complete the payment. When the payment is completed at the payment settlement device 40, the shopping is complete. After completing the shopping, the customer returns to the rental corner where the rental terminal 50B that they used was prepared, and places the rental terminal 50B in one of the empty terminal holders 92 in the charging device 90. This means that the rental terminal 50B has been returned.

[0117] [Management of personal and rental devices at stores] In a store where the shopping application of this embodiment is implemented, a mixture of personal terminals 50A and rental terminals 50B are used as customer terminal devices 50. For this reason, it is preferable to manage transactions performed using customer terminal devices 50 so that it is possible to identify which of personal terminals 50A and rental terminals 50B is being used. This makes it possible to distinguish and manage which of personal terminals 50A and rental terminals 50B is being used for each transaction, for example, when monitoring the current transaction status at the store using transaction information management device 80 or managing transaction records using transaction management device 60.

[0118] [Example of processing procedure for identifying the type of customer terminal device] The flowchart in Figure 14 shows an example of a processing procedure that the transaction management device 60 executes in relation to identifying the type of customer terminal device 50. Here, identifying the type of customer terminal device 50 means identifying whether the customer terminal device 50 used for product registration in the store is a personal terminal 50A or a rental terminal 50B.

[0119] Step S101: When a customer starts using customer terminal device 50, he or she operates transaction start instruction button BT10 (FIG. 11(A)) on the startup screen. In response to the operation of transaction start instruction button BT10, customer terminal device 50 transmits a transaction start request to transaction management device 60. If the customer terminal device 50 is a personal terminal 50A, the transaction start request includes customer identification information or application identification information. In the following description, an example is given in which the transaction start request sent by the personal terminal 50A includes customer identification information. On the other hand, in the case of the rental terminal 50B, the user who uses the shopping application is not identified as in the case of the personal terminal 50A. For this reason, the transaction start request sent by the rental terminal 50B includes application identification information. In step S101, the transaction management device 60 waits for a transaction start request transmitted from the personal terminal 50A or the rental terminal 50B as the customer terminal device 50 to be received.

[0120] Step S102: When the transaction start request is received, the transaction management device 60 determines whether the customer terminal device 50 to which the transaction start request is sent is the rental terminal 50B. If the received transaction start request contains application identification information, transaction management device 60 determines that the terminal is rental terminal 50B. On the other hand, if the received transaction start request contains customer identification information, transaction management device 60 determines that the terminal is personal terminal 50A.

[0121] Step S103: If it is determined that the customer terminal device 50 to which the transaction start request is sent is the rental terminal 50B, the transaction management device 60 generates cart information corresponding to the rental terminal 50B. This process corresponds to the process of generating cart information in step S2 in FIG. 10. The transaction management device 60 stores the application identification information included in the transaction start request in the customer / app identification information field in the cart information generated in step S103, and stores "1" indicating that it is the rental terminal 50B in the terminal type flag field.

[0122] Step S104: If it is determined that the customer terminal device 50 to which the transaction start request is sent is the personal terminal 50A, the transaction management device 60 generates cart information corresponding to the personal terminal 50A. This process, like step S103, corresponds to the process of step S2 in FIG. 10. The transaction management device 60 stores the customer identification information included in the transaction start request in the customer / app identification information field in the cart information generated in step S104, and stores "0" indicating that it is a personal terminal 50A in the terminal type flag field.

[0123] In this manner, in this embodiment, the cart information stores information that can identify whether the customer terminal device 50 being used in the corresponding transaction is a personal terminal 50A or a rental terminal 50B. That is, if the cart information stores customer identification information or the terminal type flag is "0," the transaction management device 60 identifies the customer terminal device 50 being used in the corresponding transaction as a personal terminal 50A. Furthermore, if the cart information stores application identification information or the terminal type flag is "1," the transaction management device 60 identifies the customer terminal device 50 being used in the corresponding transaction as a rental terminal 50B.

[0124] According to the processing of steps S103 and S104, the customer / application identification information field in the cart information stores application identification information when the destination of the transaction start request is the rental terminal 50B, and stores customer identification information when the destination is the personal terminal 50A. In this case, if the application identification information and the customer identification information have different formats, such as the number of digits and the type of characters used for each digit, it is possible to identify whether the customer terminal device 50 used for the corresponding transaction is the rental terminal 50B or the personal terminal 50A, based on the difference in the format of the identification information stored in the customer / application identification information field. In this case, the terminal type flag may be omitted. On the other hand, if the transaction start request sent by the personal terminal 50A includes application identification information instead of customer identification information, the application identification information is stored in the customer / app identification information area of ​​the cart information regardless of whether the corresponding customer terminal device 50 is a personal terminal 50A or a rental terminal 50B. In this case, the transaction management device 60 can identify whether the customer terminal device 50 is a personal terminal 50A or a rental terminal 50B by referring to the terminal type flag in the cart information.

[0125] [Identification of personal and loaned devices] 14, the result of identifying whether customer terminal device 50 is personal terminal 50A or rental terminal 50B is reflected in the cart information stored in transaction management device 60. The transaction information management device 80 is capable of displaying a terminal status screen on the display unit 806, which shows the status of the rental terminal 50B in the store and the transaction status corresponding to each personal terminal 50A in use in the store, based on the cart information stored in the transaction management device 60.

[0126] 15 shows an example of a terminal status screen displayed on display unit 806 of transaction information management device 80. The terminal status screen in the figure includes a loaned terminal status area AR10 and a personal terminal status area AR20.

[0127] The rental terminal status area AR10 is an area that displays a list of the status of each rental terminal 50B deployed in the store. Each list item IM-A placed in the rental terminal status area AR10 indicates the current status of the corresponding rental terminal 50B. In the lending terminal status area AR10, the list items IM-A are arranged in order according to the terminal numbers assigned to the lending terminals 50B. The figure shows an example in which 14 list items IM-A are arranged in order, corresponding to the terminal numbers "001" to "014." In addition, if the number of list items IM-A exceeds the number that can be displayed given the size of the lending terminal status area AR10, the remaining list items IM-A may be displayed by scrolling or changing pages in the lending terminal status area AR10.

[0128] List item IM-A displays the status of the corresponding lending terminal 50B. List item IM-A displays one of the following statuses, for example: "Rented," "Waiting," "Backup," "Powered Off," "Unavailable," and "Abandoned." Of these statuses, excluding the "Powered Off" status, the statuses "Rented," "Waiting," "Backup," "Unavailable," and "Abandoned" indicate that the power is on and the lending terminal 50B is activated.

[0129] When the status "On loan" is displayed in list item IM-A, it indicates that the corresponding rental terminal 50B is currently being loaned to a customer. For example, the status "On loan" is displayed when the corresponding rental terminal 50B is disconnected from the charging device 90.

[0130] Furthermore, when the status "on loan" is displayed, the list item IM-A displays the content according to the sub-status, either "registering," "settlement in progress," or "settlement completed." In the case of the sub-status of "Registering," for example, the start time of use, the number of registered items at the current time, and the total price (estimated total) of the registered items at the current time are displayed, such as "Started HH:MM:SS," "Number of registered items 12," and "Estimated total 2320" shown in list item IM-A for terminal number "001." The start time of use displayed in list item IM-A may be the time when the corresponding rental terminal 50B was removed from the charging device 90, or the time when the transaction started in response to operation of the transaction start instruction button BT10. The notation "HH:MM:SS" indicates the actual hours, minutes, and seconds. Furthermore, in the case of a sub-status of "Checkout in progress," for example, as in list item IM-A for terminal number "005," a display indicating the sub-status of "Checkout in progress" and "QR created HH:MM:SS" indicating the time the two-dimensional code was generated are displayed. The time the two-dimensional code was generated is the time when the corresponding rental terminal 50B generated and displayed the two-dimensional code of the cart identification information in response to the checkout transition instruction operation.

[0131] In addition, in the case of a sub-status of settlement completion, for example, as in list item IM-A for terminal number "007," a display showing the sub-status "Settlement Completed," "Settlement Completed HH:MM:SS" indicating the time of settlement completion, and "Elapsed Time HH:MM:SS" indicating the time elapsed since the time of settlement completion are displayed. For example, after completing payment, a customer may return rental terminal 50B to a location other than the charging device 90 at the designated rental corner, or may intentionally or accidentally leave rental terminal 50B in their possession. In such cases, the elapsed time in list item IM-A will be significantly longer than the time normally required for a customer to return rental terminal 50B to charging device 90 after completing payment. By looking at this elapsed time, the store clerk can determine that rental terminal 50B has not been returned to charging device 90 at the designated rental corner.

[0132] In addition, when a reserved item is registered under the sub-status of "On loan" and "Registered", the corresponding list item IM-A will display a message indicating that the registered items include a reserved item. For example, in the list item IM-A for terminal number "003", "Number of items: 12" and "Reserved: 1" are displayed, indicating that one reserved item is included in the 12 registered items (number of items). The manner in which pending products are displayed in list item IM-A for terminal number "003" is applied when the pending product registration results include product registration results for categories other than pseudo-scan input (category number 3) and non-scan input (category number 4) among the categories of pending products shown in Figure 8.

[0133] In the example shown in the figure, in the list item IM-1 corresponding to a transaction in which a fraudulent act called "basket abandonment" was detected under the sub-status of "on loan" and registration, a display indicating that "basket abandonment" has occurred is displayed. Specifically, the display of "basket" in the list item IM-1 for terminal number "002" indicates that this is a transaction in which "basket abandonment" has occurred. "Basket abandonment" applies when the product registration results include either pseudo-scan input (classification number 3) or non-scan input (classification number 4) from the classification of reserved products shown in Figure 8. In other words, in the example of the same figure, the customer's behavior when the product registration results obtained are pseudo-scan input (classification number 3) or non-scan input (classification number 4) is treated as equivalent to "basket abandonment."

[0134] When the status "Waiting" is displayed in the list item IM-A, it indicates that the corresponding rental terminal 50B is on standby. The waiting state means that the corresponding rental terminal 50B is charging by being inserted into the charging device 90 at the rental corner associated with the rental terminal 50B.

[0135] List item IM-1 for terminal number "009" shows a status of "Waiting." In list item IM-1 for terminal number "009," "Waiting: Station 2-2" is displayed, indicating that the terminal is waiting at the rental corner of Station 2-2. Furthermore, in the list item IM-1 for terminal number "009," the amount of charge of the corresponding rental terminal 50B is displayed, along with the expected usable time according to the amount of charge.

[0136] The list item IM-1 for terminal number "004" also shows a status of "Waiting." However, in the list item IM-1 for terminal number "004," an example is shown in which, in response to the low charge level of the corresponding rental terminal 50B, a message such as "Please exchange for a spare device" is displayed to encourage the user to exchange for a spare customer terminal device 50.

[0137] When the status "spare" is displayed in the list item IM-A, it indicates that the corresponding rental terminal 50B is being stored as a spare. In the figure, list item IM-1 for terminal numbers "010," "011," and "012" each indicate a status of "spare." List item IM-1 with a status of "spare" indicates the current charging state of the corresponding rental terminal 50B.

[0138] When the status "Power OFF" is displayed in the list item IM-A, it indicates that the power of the corresponding rental terminal 50B is OFF. In the figure, the list item IM-1 for terminal numbers "013" and "014" respectively displays "Power OFF (no communication)," indicating that the corresponding rental terminal 50B is powered off. In addition, the list item IM-1 for the "Power OFF" status displays the reason why the power is off, such as "Reason: Stored in spare storage" or "Reason: Under repair."

[0139] Furthermore, if the corresponding list item IM-1 is not displayed on the terminal status screen in the same figure, but the status "unavailable" is displayed in list item IM-A, this indicates that the corresponding rental terminal 50B is unusable for some reason, such as a malfunction. Furthermore, if the corresponding list item IM-1 is not located on the terminal status screen in the same figure, but the status "Abandoned" is displayed in list item IM-A, this indicates that the corresponding rental terminal 50B has been left abandoned in a location other than the corresponding rental corner.

[0140] The list item IM-A may have different borders or background colors depending on the status and sub-status, the registration of reserved items, the occurrence of "basket emptying," etc. This allows the store clerk to intuitively grasp the status of each rental terminal 50B.

[0141] The personal terminal status area AR20 on the terminal status screen is an area that displays a list of the status of each personal terminal 50A that a customer is using in the store. Each list item IM-B placed in the personal terminal status area AR20 shows the current status of the corresponding personal terminal 50A. The status of the personal terminal 50A shown in the list item IM-B is mainly the status of transactions using the corresponding personal terminal 50A.

[0142] The list items IM-B in the personal terminal status area AR20 are arranged, for example, from top to bottom in order of the start time of use closest to the current time. The start time of use is the time when the transaction started in response to the customer's operation of the transaction start instruction button BT10. When a new transaction is started using the personal terminal 50A, the corresponding list item IM-B in the personal terminal status area AR20 is newly displayed at the top of the personal terminal status area AR20, and the previously displayed list item IM-B is displayed one row lower. In addition, if the number of list items IM-B exceeds the number that can be displayed given the size of the personal terminal status area AR20, the remaining list items IM-B may be displayed by scrolling or changing pages in the personal terminal status area AR20.

[0143] In list item IM-B of personal terminal status area AR20, user identification information is shown, for example, by displaying "UID: xxxxxxx...". Furthermore, in list item IM-B, if member information is registered in a shopping application installed on the corresponding personal terminal 50A, member identification information is displayed, for example, by displaying "member identification: xxxxxxx...". Furthermore, if the member information registered in the shopping application corresponds to a general member, it is displayed, for example, as "member identification: general". Specifically, the user identification information and member identification information may be, for example, alphanumeric character strings of a predetermined number of digits.

[0144] Additionally, list item IM-B displays information indicating the progress of the corresponding transaction. For example, list item IM-1 on the first line displays "Entered the store (app launched) HH:MM:SS," indicating that the shopping application was launched at the time HH:MM:SS and the launch screen is displayed. In addition, the second line of list item IM-B displays "Shopping Started HH:MM:SS", which indicates that the corresponding transaction started at transaction start time HH:MM:SS, but no products have been registered yet. In addition, in the list item IM-B on the third line, the corresponding transaction shows the current registered number of items and the estimated total, depending on whether the product is currently being registered. When the product is currently being registered, "HH:MM:SS" may indicate the transaction start time. Additionally, in the list item IM-B on the fourth line, the display "1 reserved item" indicates that the registered items for the corresponding transaction include one reserved item. In the list item IM-B, the reserved items indicated in the above manner include unspecified items and items other than unspecified items. In other words, they include classification numbers 1 to 7 in Figure 8, "NON-FILE," "Read NG," "Pseudo-scan input," "Non-scan input," "Age verification item," "Pharmaceuticals," and "Anti-theft tag item." Additionally, the list item IM-B on the fifth and sixth lines indicates that the corresponding transaction has completed product registration, has moved to settlement, and is currently being settled. When settlement is currently being settled, the display "QR generation: HH:MM:SS" indicates the time when a two-dimensional code was generated in response to the settlement transition instruction operation and displayed on the personal terminal 50A.

[0145] The list items IM (IM-A, IM-B) also function as buttons. When a list item IM corresponding to the status of product registration is operated, the transaction information management device 80 displays a transaction details screen showing details of the corresponding transaction.

[0146] Figure 16 shows an example of a transaction details screen P1. The transaction details screen P1 in this figure is an example of a window format that is displayed superimposed on the terminal status screen. The terminal status screen in this figure also shows an example of the case where one of the list items IM-A corresponding to the lending terminal 50B is operated.

[0147] The transaction details screen P1 in the figure is arranged with a terminal status area AR2 and a registered product list area AR3.

[0148] The terminal status area AR2 is an area where the status of the corresponding customer terminal device 50 is displayed, including an outline of the transaction details and information about the status of the customer terminal device 50 itself. The terminal status area AR2 displays the rental start time, registered items, estimated total, details of registered reserved items, remaining charge, last read product code, sales floor where the customer terminal device 50 is currently located, and the coordinates of the current location of the customer terminal device 50.

[0149] The registered product list area AR3 is an area where a list of products registered by the customer terminal device 50 is presented.

[0150] If the registered products include reserved products, the list items of the reserved products are given priority and arranged from the top of the left column in the registered product list area AR3. In other words, the list items of the reserved products are arranged in order from the top in the registered product list area AR3. In the example shown in the figure, five reserved items are included among the registered items, so a reserved item list area AR31 containing list items for the five reserved items from the top left is formed in the registered item list area AR3. The list items in the reserved item list area AR31 are made to differ from the list items for other items, for example, in terms of background color, etc.

[0151] Furthermore, in the reserved product list area AR31, list items for which reserved products have been specified are arranged in order first, followed by list items corresponding to unspecified products for which no products have been specified. In other words, the reserved product list area AR31 is arranged in a separated manner, with list items corresponding to specified reserved products and list items corresponding to unspecified unspecified products for which no products have been specified.

[0152] In the registered product list area AR3, list items corresponding to successful registrations are arranged following the pending product list area AR31. In the same figure, an example is shown in which the list items corresponding to successful registrations in the registered product list area AR3 are arranged in descending order of product price. Among the list items in the registered product list area AR3, the list item corresponding to product specification displays the product name, registered quantity, price according to the registered quantity, etc. of the specified product.

[0153] A hold release declaration button BT31 is arranged in the list item for each reserved item in the reserved item list area AR31. The hold release declaration button BT31 is a button that is operated to declare the release of the reserved item for the corresponding item.

[0154] The hold release declaration button BT31 also functions as an icon indicating that the corresponding list item corresponds to a held product. The hold release declaration button BT31 shows the name of the classification of the held product to which the corresponding product falls. Specifically, for example, for age verification products (classification number 5), medicines (classification number 6), security tag products (classification number 7), and cancelled products (classification number 8), the name indicating the corresponding classification is displayed on the hold release declaration button BT31. Also, for unspecified products (classification numbers 1 to 4), the name "hold item" is displayed collectively. In the figure, the display of the hold release declaration button BT31 shows an example in which the list item on the first line is "age verification" corresponding to an age verification product (classification number 5), the list item on the second line is "security tag" corresponding to a security tag product (classification number 7), and the list item on the third line is "pharmaceuticals" corresponding to pharmaceuticals (classification number 6). Also, the list items on the fourth and fifth lines are each shown as "hold product." Thumbnail images TN are arranged in the list items on the fourth and fifth rows. The thumbnail images TN are images captured by the customer terminal device 50 when the product registration operation for the corresponding unspecified product is being performed. The thumbnail images TN may be still images or moving images. Depending on whether or not a thumbnail image TN is present, the store clerk can visually distinguish between list items corresponding to unspecified items and list items corresponding to specified items for pending items. Also, the content displayed in the thumbnail image TN allows the store clerk to understand what the item registered as an unspecified item actually was. The display indicating the corresponding classification on the hold release declaration button BT31 may be a picture such as an icon indicating the classification.

[0155] Among the list items of reserved products, for the list items corresponding to identified products such as age verification products (classification number 5), pharmaceuticals (classification number 6), and security tag products (classification number 7), the product name, registered quantity, price according to the registered quantity, etc. of the identified product are displayed. In contrast, the list item corresponding to an unidentified product displays content according to the classification of the corresponding pending product. Specifically, in the case of an unidentified product classified as NON-FILE (classification number 1), the list item on the fifth line in the figure may indicate that it is NON-FILE and also display the read product code. Furthermore, in the case of unidentified products (products for which a code has not been acquired) that are NG for reading (classification number 2), pseudo-scan input (classification number 3), or non-scan input (classification number 4), a message indicating that the product code could not be read may be displayed, as in the list item on the fourth line in the figure.

[0156] Additionally, on the transaction details screen P1, an age confirmation button BT21, a terminal call message send button BT22, and a list screen transition button BT23 are arranged. When the list screen transition button BT23 is operated, the transaction details screen P1 is cleared and the display returns to the terminal status screen.

[0157] If the registered items include reserved items, the store clerk must release the reserved items (including canceling the registration of the reserved items). The store clerk can release such reserved items by operating the payment screen displayed on the payment device 40.

[0158] Furthermore, in this embodiment, a store clerk can operate the transaction information management device 80 to process the reserved items as follows. In this case, the transaction information management device 80 is installed at the service counter. In this embodiment, if a reserved item is registered during product registration, the customer can have the store clerk release the reserved item at the service counter as long as the product registration has not yet been completed. If the customer wants the service counter to release the reserved item, the customer goes to the service counter and asks the store clerk in charge to release the reserved item.

[0159] The store clerk who receives a request to release a reserved item identifies which list item IM displayed on the terminal status screen corresponds to the customer terminal device 50 held by the customer. At this time, if the customer terminal device 50 held by the customer is a rental terminal 50B, the store clerk checks the terminal number of the rental terminal 50B and identifies the list item IM-A that displays the same terminal number. Also, if the customer terminal device 50 held by the customer is a personal terminal 50A, the store clerk identifies the stamp on which the customer's member identification information is written and the list item IM-A that displays the same member identification information. Alternatively, the list item IM may be identified by having the transaction information management device 80 read a code (two-dimensional code or barcode) indicating the terminal number of the rental terminal 50B or a code of member identification information shown on the membership card. In this case, the identified list item IM may be highlighted in a predetermined manner. In this case, the code indicating the terminal number of the rental terminal 50B may be attached to the rental terminal 50B or may be displayed on the rental terminal 50B. The code of the member identification information may be read from a membership card held by the customer. In this case, the membership card may be displayed on the shopping application of the customer terminal device 50.

[0160] The store clerk performs an operation on the list item IM identified as above to display the transaction details screen P1, and releases the reserved item as follows. When the store clerk releases a reserved item of a specific category (age verification items (classification number 5), pharmaceuticals (classification number 6), security tag items (classification number 7) among the reserved items, the store clerk performs the prescribed response work according to each category and then operates (for example, taps) the release reservation declaration button BT31 located next to the corresponding list item in the reserved item list area AR31. Note that the entire list item of reserved items may be made tappable. If the product to be released from hold is an age verification product, the store clerk will confirm that the customer is an adult as part of their customer service and then operate the hold release declaration button BT31 located in the corresponding list item. Furthermore, if the product to be released from hold is a medicine, the store clerk will, as a handling procedure, either explain the product himself / herself if he / she is a licensed pharmacist, or ask another store clerk who is a licensed pharmacist to explain the product, and then operate the release hold declaration button BT31 located in the corresponding list item. Furthermore, if the product to be released from hold has a security tag, the store clerk will, as a service procedure, remove the security tag attached to the product and operate the hold release declaration button BT31 located on the corresponding list item. When a hold is released for a reserved item in a category for which the item has been identified as described above, the display on the hold release declaration button BT31 that was operated changes from a state showing the relevant category to a state indicating that the hold has been released, such as "Confirmed" (or "Released hold").

[0161] In addition, when a store clerk wishes to release a reserved item classified as an unspecified item (NON-FILE (classification number 1), NG to read (classification number 2), pseudo-scan input (classification number 3), non-scan input (classification number 4)), the clerk first operates the release-on-hold declaration button BT31 located in the list item in the reserved item list area AR31 that corresponds to the reserved item to be released. In response to the operation of the hold release declaration button BT31 corresponding to the unspecified product, a status confirmation screen is displayed in place of the transaction details screen P1.

[0162] 17 shows an example of the status confirmation screen P10. The status confirmation screen P10 is a screen that shows the status of the unspecified product corresponding to the operated hold release declaration button BT31 when it is registered by the customer's operation of the customer terminal device 50. The status confirmation screen P10 in the figure shows an example in which the unidentified product to be released from reservation is classified as pseudo-scan input (classification number 3). The status confirmation screen P10 in the figure corresponds to a case where the customer terminal device 50 is held in a holder provided on the cart, and while held in the holder, the customer terminal device 50 is capable of capturing images of the inside of the shopping cart. The customer causes the customer terminal device 50 held in the holder to scan the product code.

[0163] On the status confirmation screen P10 in the figure, captured images G11, G12, and G13 are arranged from left to right in this order. Captured images G11, G12, and G13 are captured when the customer terminal device 50 was capturing images to scan the product code of the corresponding unspecified product.

[0164] The order of arrangement of the captured images G11, G12, and G13 from left to right corresponds to the time lapse in which the images were captured. First, the second (center) captured image G12 is an image captured when the product to be processed is within the image capturing range of the customer terminal device 50 during the product registration operation. The first captured image G11 was captured earlier than the second captured image G12, and was captured before the product to be processed fell within the image capturing range. The third captured image G13 is captured after the second captured image G12, and is captured at a timing when the product to be processed goes out of the image capturing range.

[0165] In this case, the store clerk can understand the situation at the time of the product registration operation that resulted in the unidentified product by looking at the captured images G11, G12, and G13. Specifically, in the example shown in the same figure, the store clerk can first understand from the transition from captured image G11 to captured image G12 that the product to be processed was not in the shopping cart before the product registration operation was performed. Furthermore, the store clerk can see from the captured image G12 that the product code on the product was hidden by the hand, and therefore an unidentified result was generated as a false scan input (classification number 3). Furthermore, the store clerk can determine what the product to be disposed of is from the captured image G12. Specifically, in the example shown in the figure, the store clerk determines that the product to be disposed of is a "canned yakitori." Furthermore, the store clerk can understand from the transition from captured image G12 to captured image G13 that the product to be processed was added to the shopping cart after the product registration operation was performed.

[0166] After grasping the situation during the product registration operation as described above, the store clerk operates the screen transition button BT35 to display the product information input screen. In response to the operation of the screen transition button BT35, the product information input screen is displayed in place of the status confirmation screen P10. Alternatively, a scanner unit may be provided in transaction information management device 80, and the store clerk may operate the scanner unit to read the product code of the product to be processed that has been placed in the shopping cart while status confirmation screen P10 is displayed. When transaction information management device 80 successfully reads the product code, a product information input screen is displayed.

[0167] 18 shows an example of a product information input screen P40. The product information input screen P40 is a screen on which a store clerk inputs product information for a product to be processed as an unidentified product. The product information input screen P40 may be displayed superimposed on the reserved product processing screen, similar to the status confirmation screen P10.

[0168] The product information input screen P40 includes a product information area AR41, an input operation area AR42, a registration button BT41, a cancel button BT42, and a captured image area AR43 (a target captured image area AR43-1 and a next captured image area AR43-2).

[0169] The product information area AR41 is an area where product information about the corresponding unspecified product is displayed. The product information area AR41 in the same figure displays the product name, product code, price, registered quantity, etc. The registered quantity can be input (registered) by operating the plus button and minus button arranged in the product information area AR41.

[0170] The input operation area AR42 is an area where a software keyboard and buttons for inputting product information in the product information area AR41 are arranged. In the input operation area AR42, a keyboard with a key layout suitable for numeric input and a keyboard with a key layout suitable for character input can be switched depending on the operation.

[0171] The input operation area AR42 is provided with a preset call button BT421. By operating the preset call button BT421, a preset key screen is displayed on which preset keys corresponding to each product are arranged. For example, if the unidentified product to be processed is either NG (classification number 2), pseudo-scan input (classification number 3), or non-scan input (classification number 4), and the store clerk knows the product name of the product to be processed, the store clerk may display the preset key screen. By operating the preset key of the corresponding product from among the preset keys arranged on the displayed preset key screen, the store clerk can input product information of the product to be processed into the product information area AR41.

[0172] Furthermore, the input operation area AR42 has arranged therein a product code input declaration button BT422. The product code input declaration button BT422 is a button that is operated when declaring that a product code input operation will be performed. The store clerk operates the product code input declaration button BT422, and then, for example, operates a keyboard arranged in the input operation area AR42 to input the numeric value of the product code printed or otherwise indicated on the product to be processed, thereby inputting the product code into the product information area AR41.

[0173] When the product information input screen P40 is displayed in response to a store clerk having the transaction information management device 80 read a product code, the read product code has already been entered in the product information area AR41, and if the product is an unspecified product other than NON-FILE (classification number 1), the product has been identified from the product master based on the read product code, and the product name, price, etc. have also been entered.

[0174] Furthermore, if the product to be processed is classified as NON-FILE (classification number 1), the product code is already entered in the product information area AR41 when the product information input screen P40 is displayed. In this case, the store clerk enters the product name, price, etc. in the product information area AR41 by operating the keyboard arranged in the input operation area AR42.

[0175] The register button BT41 is a button that is operated to confirm the information entered in the product information area AR41 as described above, release the reservation of the corresponding unspecified product, and make it a properly registered product. The cancel button BT42 is a button that is operated to instruct cancellation of the registration of the corresponding unspecified product.

[0176] The store clerk checks the information entered in the product information area AR41 and then presses the register button BT41. As a result, 40 releases the pending status of the unspecified product and processes it to be included in the registered products. After the registration button BT41 is operated, the product information input screen P40 disappears and the screen returns to the reserved product processing screen (FIG. 14). When the screen returns to the reserved product processing screen, the reserved product release declaration button BT31 for the list item of the product that was the subject of processing in the reserved product list area AR31 indicates that the reserved state has been released, for example by displaying "Confirmed."

[0177] Alternatively, if the store clerk determines that the product to be processed should not be registered, he or she operates the cancel button BT42 to cancel the registration and removes the product from the shopping cart. Even after the Cancel button BT42 is operated, the product information input screen P40 is cleared and the screen returns to the transaction details screen P1 (FIG. 16). When the screen returns to the transaction details screen P1, the list item of the product that was the subject of processing in the reserved product list area AR31 has changed to a predetermined state indicating that the registration has been canceled.

[0178] The status confirmation screen P10 and the product information input screen P40 may also display the classification number, classification name, etc. of the corresponding unspecified product.

[0179] In the captured image area AR43, the target captured image area AR43-1 is an area where the target captured image is displayed. The target captured image is an image captured when the unspecified product to be processed this time is a product for which a code has not been obtained and is within the image capture range during the product registration operation. The captured image displayed in the target captured image area AR43-1 may be the same as the captured image G12 displayed on the status confirmation screen P10, for example. In the captured image area AR43, the next captured image area AR43-2 is an area where the next captured image is displayed. The next captured image is an image captured during the product registration operation performed after the product registration operation corresponding to the current target product whose code has not yet been acquired. In other words, the next captured image is an image corresponding to the product registration operation in which the product code was first successfully read and the product was identified after the product registration operation corresponding to the current target product whose code has not yet been acquired. As the next captured image, if there is a captured image in which an item as a commodity is detected among the captured images obtained in response to the next commodity registration operation, the captured image including the detected commodity is selected.

[0180] When a customer performs a product registration operation for a certain product, and the customer terminal device 50 is unable to read the product code correctly and the product is registered as a product with an unacquired code, the customer often attempts to register the same product again. In such cases, the customer will perform the product registration operation for the same product twice in a row. In such cases, if the product code is successfully read during the second product registration operation, the same product will be registered twice: once as a pending product with an unacquired code, and once as a normal product registration in which the product is identified based on the read product code. In cases where duplicate registrations have occurred, the procedure for the store clerk to release the hold is to delete the registration of the reserved product as a product for which a code has not been obtained and leave the normal registration for the same product. To ensure this process is carried out smoothly, it is necessary to make it easy for the store clerk to know whether the product for which a code has not been obtained that is the target of release from hold has been registered twice.

[0181] Therefore, in this embodiment, the captured image area AR43 (target captured image area AR43-1, next captured image area AR43-2) is arranged on the product information input screen P40 to display the target captured image and the next captured image. If the target image and the next image show the same product, the store clerk can confirm that a duplicate registration has occurred. Therefore, the store clerk in this case, for example, operates the cancel button BT42 arranged on the product information input screen P40. As a result, the target product for which a code has not been obtained is deleted from the list of registered products.

[0182] Also, in the next captured image area AR43-2 in the same figure, a quantity display section NM is arranged. The quantity display section NM is an image section that indicates the quantity (registered quantity) registered by, for example, a customer's operation for a commodity that was successfully registered by the commodity registration operation when the next captured image was captured. By placing the quantity display unit NM, the store clerk can grasp the registered quantity of the unspecified product to be released from hold and the normally registered product that overlaps with the unspecified product to be released from hold at the stage of performing the hold release operation, and can accurately perform the tasks and operations related to the hold release.

[0183] If the product to be processed is an unspecified product classified as NON-FILE (classification number 1), the customer terminal device 50 will notify the customer that the product code was successfully read but the product was not identified. In this case, the customer will know that the product code was successfully read, so there is little chance that the customer will perform a product registration operation for the same product again, resulting in duplicate registration. Therefore, if the registration result of the product to be processed corresponds to NON-FILE, the captured image area AR43 (processing target image, next captured image) may not be displayed. However, some customers may mistakenly believe that reading the product code failed even if a notification is issued in response to a non-registration result as NON-FILE, and may attempt to register the product again. For this reason, even when the registration result of the product to be processed corresponds to NON-FILE, the captured image area AR43 (processing target image, next captured image) may be displayed. If the captured image area AR43 is displayed, it becomes easier for the store clerk to recognize that the same product has been registered twice as a non-registration result of NON-FILE.

[0184] The next captured image may also be displayed, for example, on the status confirmation screen P10 together with the captured images G11, G12, and G13. In this case, the store clerk can determine whether or not a duplicate registration has occurred when the status confirmation screen P10 is displayed before the product information input screen P40 is displayed.

[0185] In addition, if the transaction management device 60 is capable of acquiring location information transmitted from each customer terminal device 50 (which may be at least a rental terminal 50B), the transaction information management device 80 may be configured to display the location of the rental terminal 50B corresponding to each transaction based on the acquired location information.

[0186] [Feature to prevent rental devices from being taken outside the store] Rental terminal 50B should be returned to the rental corner in the store after the customer has finished using it. However, there is a possibility that a customer who has finished shopping using rental terminal 50B may inadvertently leave the store while still holding rental terminal 50B. Alternatively, there is a possibility that rental terminal 50B may be taken out of the store by a malicious customer. Therefore, in this embodiment, when rental terminal 50B is taken outside the store, a notification to that effect is sent by transaction information management device 80. When the notification is sent by transaction information management device 80, the store clerk monitoring the store knows that rental terminal 50B has been taken outside the store and can take action immediately. The device that notifies the user that rental terminal 50B has been taken out of the store may be, for example, management device 10, settlement device 40, or a business terminal carried by a store clerk, other than transaction information management device 80. In the following explanation, an example is given in which the notification is made by transaction information management device 80.

[0187] [Example of processing procedure for reporting items taken outside the store] An example of a processing procedure executed by the transaction management device 60 and the transaction information management device 80 in relation to a notification in response to the taking of a rental terminal 50B outside the store will be described with reference to the flowchart in Figure 19. The processing in this figure is executed by the transaction management device 60 in response to one rental terminal 50B.

[0188] First, an example of the processing procedure of the transaction management device 60 will be described. Step S201: In this embodiment, when the power is on and the lending terminal 50B is operating, the positioning unit 508 periodically positions its own position and transmits position information indicating the positioned own position to the transaction management device 60. The transaction management device 60 waits to receive the location information transmitted from the lending terminal 50B.

[0189] Step S202: When the transaction management device 60 receives the location information, it determines whether the location of the rental terminal 50B indicated by the received location information is outside the location range corresponding to the store. If it is determined that the location of the rental terminal 50B is within the location range corresponding to the store, the process in the same figure ends and the process starts from step S201.

[0190] Step S203: If it is determined in step S202 that the location of the rental terminal 50B is outside the location range corresponding to the store, the rental terminal 50B is taken out of the store. Therefore, in this case, the transaction management device 60 transmits an outside-store movement notification to the transaction information management device 80. The out-of-store movement notification is information notifying that the rental terminal 50B has moved outside the store. The out-of-store movement notification includes terminal identification information of the rental terminal 50B that has moved outside the store. Furthermore, after sending the out-of-store movement notification, the transaction management device 60 may transmit the received location information to the transaction information management device 80 each time location information transmitted from the rental terminal 50B after it has moved outside the store is received.

[0191] Next, an example of the processing procedure of the transaction information management device 80 will be described. Step S301: The transaction information management device 80 waits for the receipt of the outside-store movement notification transmitted in step S203.

[0192] Step S302: In response to receiving the notification of movement outside the store, the transaction information management device 80 executes a notification of movement outside the store. The notification of movement outside the store is a notification to a store clerk that the rental terminal 50B has moved outside the store. The notification of movement outside the store may be made, for example, by a display on the display unit 806 of the transaction information management device 80. The notification of movement outside the store may also be accompanied by an electronic sound or voice output by the transaction information management device 80, for example. In addition, if the rental terminal 50B is configured to transmit location information, the transaction information management device 80 may be configured to display on the display unit 806 the current location and movement trajectory of the rental terminal 50B that has moved outside the store based on the location information transmitted from the transaction management device 60 from the rental terminal 50B that has moved outside the store in the event of an outside-store movement notification. Furthermore, a number may be assigned to each of the rental terminals 50B, and the number of the rental terminal 50B that has been moved outside the store may be displayed in the notification of movement outside the store. In addition, the transaction information management device 80 may, for example, upon receiving a notification of movement outside the store, acquire an image from a surveillance camera capturing an image of a customer carrying the rental terminal 50B that has been moved outside the store, and display the acquired image.

[0193] In addition, for the rental terminal 50B to notify of movement outside the store using the process shown in the figure, the rental terminal 50B must periodically transmit location information. In other words, the rental terminal 50B must be powered on and have its location information transmission function turned on. Therefore, for example, if a malicious customer turns off the location information transmission function or powers off the rental terminal 50B, the rental terminal 50B will not be able to notify of movement outside the store. Therefore, the rental terminal 50B may be configured so that operations such as turning off the power or turning off the location information transmission function cannot be performed without, for example, special procedures rather than operations that are typically performed on the rental terminal 50B. Alternatively, the rental terminal 50B may be locked so that operations such as turning off the power or turning off the location information transmission function cannot be performed. Alternatively, for example, the transaction management device 60, the transaction information management device 80, or the like may be controlled so that the power returns to an on state even if the power is turned off, or the location information transmission function switches to an on state even if it is turned off.

[0194] [Regarding the return management of rental devices] When the rental terminal 50B is in a standby state and not being used by a customer, it is operated by being placed in a charging device 90 installed in the rental corner while being charged. Here, an example is given in which a store has multiple rental corners and the rental terminal 50B to be placed in each rental corner is predetermined. Accordingly, the store has established a return rule that, when a customer uses a rental terminal 50B installed in a certain rental corner to do some shopping, the customer must return the rental terminal 50B to its original rental corner after finishing their shopping by inserting it into the terminal holder 92 of the charging device 90 and leaving it in a charged state. However, not all customers who use the rental terminal 50B will necessarily return the rental terminal 50B in accordance with the above-mentioned return rules. In other words, there is a possibility that the rental terminal 50B may not be returned properly in a store due to the following cases: One possibility is that the customer leaves the rental terminal 50B at a different rental corner from the original rental corner where it was originally intended to be left (Case 1). Another possibility is that the customer leaves the terminal at the original rental corner without setting it up to be charged by the charging device 90 (Case 2). In addition, one case in which the rental terminal 50B is not returned according to the return rules is when the customer takes the rental terminal 50B outside the store, but such a case can be dealt with by the aforementioned outside-store takeout notification.

[0195] Therefore, in this embodiment, as will be described below, a notification (failed return notification) of the occurrence of a failed return mainly due to cases 1 and 2 is sent to the store clerk. This allows the store clerk to return the failed-return rental terminal 50B to a charged state at the original rental corner.

[0196] [Example of processing procedure for notifying of non-return of loaned terminal] The flowchart in FIG. 20 shows an example of a processing procedure that the rental terminal 50B and the transaction information management device 80 execute in relation to a return failure notification. First, an example of a processing procedure executed by the rental terminal 50B will be described. In explaining the figure, it is assumed that the rental terminal 50B periodically measures its own position using the positioning unit 508 and transmits position information indicating the measured position to the transaction management device 60. In addition, the rental terminal 50B is in a state where a shopping application is running.

[0197] Step S401: The rental terminal 50B on which the shopping application is running determines whether or not the rental terminal 50B has become disconnected from the charging device 90 while being charged. For example, when the rental terminal 50B detects that the rental terminal 50B has transitioned from a state in which power for charging was being supplied to a state in which the supply of power has been stopped, the rental terminal 50B determines that the rental terminal 50B has become disconnected from the charging device 90.

[0198] Step S402: If it is determined in step S401 that the rental terminal 50B has been removed from the charging device 90, the rental terminal 50B transmits a terminal removal notice to the transaction information management device 80. The terminal removal notification is information notifying that the rental terminal 50B that was being charged has been removed from the charging device 90, and that the customer has removed the rental terminal 50B from the rental corner to use for shopping. The terminal takeout notification includes the terminal identification information of the sender, the rental terminal 50B. Note that the terminal identification information of the rental terminal 50B may be the application identification information of the shopping application installed on the rental terminal 50B. In the following explanation, a case where the terminal identification information is the application identification information will be taken as an example.

[0199] Step S403: If it is determined in step S401 that the terminal has not been removed from the charging device 90, or after the processing of step S402, the rental terminal 50B determines whether charging has started by the charging device 90. If it is determined that charging has not started, the processing returns to step S401.

[0200] Step S404: If it is determined in step S403 that charging has started, the rental terminal 50B transmits a terminal return notice to the transaction information management device 80. The terminal return notification is information that notifies that the rental terminal 50B has been returned to the rental corner in response to the start of charging by the charging device 90. The terminal return notification includes the terminal identification information of the rental terminal 50B that sent it.

[0201] Next, an example of a processing procedure executed by the transaction information management device 80 will be described. Step S501: The transaction information management device 80 waits for reception of the terminal take-out notification transmitted from the rental terminal 50B in step S402.

[0202] Step S502: When the terminal removal notification is received, the transaction information management device 80 acquires the removal location. The removal location is a location corresponding to the rental corner from which the customer removed the rental terminal 50B that sent the terminal removal notification. The transaction information management device 80 stores information on the location range of each lending corner. When acquiring the take-out location, the transaction information management device 80 may acquire the take-out location by determining which lending corner's location range includes the location indicated by the location information transmitted from the same lending terminal 50B as the sender of the terminal take-out notification. The transaction information management device 80 stores the acquired take-out location in association with the terminal identification information of the lending terminal 50B that sent the terminal take-out notification. In the following description, the lending terminal 50B that is the sender of the terminal takeout notification may be referred to as the lending terminal 50B to be monitored.

[0203] Step S503: The transaction information management device 80 determines whether the customer has started product registration within a certain time period since the customer took possession of the rental terminal 50B to be monitored. This certain time period may be set based on the typical time required for the customer to operate the transaction start instruction button BT10 to start product registration after taking out the rental terminal 50B, for example. In this embodiment, the transaction management device 60 generates cart information in response to a transaction start request from a customer terminal device 50 (personal terminal 50A, rental terminal 50B). Product registration using the customer terminal device 50 can be considered to be initiated in response to the generation of cart information. In this embodiment, the transaction management device 60 transmits a product registration start notification to the transaction information management device 80 in response to the generation of cart information. The product registration start notification includes terminal identification information of the corresponding customer terminal device 50. The timing at which the take-out position is acquired in step S502 can be considered to correspond to the timing at which the rental terminal 50B to be monitored is removed from the charging device 90 by the customer. Therefore, in the process of step S503, transaction information management device 80 determines whether a product registration start notification including terminal identification information of rental terminal 50B to be monitored is received within a certain time from the time the take-out location is acquired in step S502. This allows transaction information management device 80 to determine whether product registration has started within a certain time from the time the take-out location is acquired in step S502.

[0204] Step S504: If it is determined in step S503 that product registration has started within the certain time, the transaction information management device 80 further determines whether settlement has started within the certain time from the start of product registration. The certain time here may be set based on the typical time required, for example, from when a customer starts product registration using the rental terminal 50B, to when the customer completes the product registration and has the settlement device 40 read the code displayed on the rental terminal 50B. In response to reading the code displayed on customer terminal device 50, settlement device 40 sends a subtotal request to transaction management device 60, displays a settlement screen based on the subtotal information sent from transaction management device 60, and executes settlement processing. In this embodiment, when transaction management device 60 sends subtotal information in response to receiving the subtotal request, it sends a settlement start notification to transaction information management device 80, which includes, as terminal identification information, the application identification information stored in the customer / app identification information field of the cart information used to generate the subtotal information. In step S504, transaction information management device 80 determines whether a settlement start notification including the terminal identification information of rental terminal 50B to be monitored has been received within a certain time from the time when it was determined in step S503 that product registration had started. This allows transaction information management device 80 to determine whether settlement has started within a certain time from the start of product registration.

[0205] Step S505: If it is determined in step S504 that the settlement has started within the certain time, the transaction information management device 80 further determines whether the terminal return notice sent from the rental terminal 50B in step S404 has been received within the certain time from the time it was determined that the settlement has started. The certain time may be set based on the typical time required for a customer who has registered an item using the rental terminal 50B to return the rental terminal 50B to the rental corner after starting the settlement at the settlement device 40.

[0206] Step S506: If it is determined that a terminal return notification has been received within a certain period of time from the time it was determined in step S505 that settlement had begun, the transaction information management device 80 obtains the return location of the rental terminal 50B being monitored. When obtaining the return location, the transaction information management device 80 may obtain the return location by determining which rental corner's location range the location indicated by the location information transmitted from the rental terminal 50B being monitored falls within.

[0207] Step S507: The transaction information management device 80 determines whether the take-out location acquired in step S502 and the return location acquired in step S506 correspond to the same lending corner. If it is determined that the rental terminal 50B to be monitored corresponds to the same rental corner, it means that the rental terminal 50B to be monitored has been properly returned so that it can be charged by the charging device 90 at the original rental corner after the customer has finished using it. In this case, step S508 may be skipped and the processing in the figure may end.

[0208] Step S508: If it is determined in step S507 that the take-out location acquired in step S502 and the return location acquired in step S506 correspond to different rental corners, the following state applies: In other words, in this case, the rental terminal 50B to be monitored has been returned to a rental corner that is different from the correct rental corner to which the rental terminal 50B to be monitored was assigned, and charging is being performed by the charging device 90. Therefore, in this case, transaction information management device 80 outputs a terminal movement request. The terminal movement request is a request to the store clerk to move rental terminal 50B to be monitored from the current rental corner to the correct rental corner. Specifically, the transaction information management device 80 displays, as a terminal movement request, on the display unit 806, the current location (rental corner) of the rental terminal 50B to be monitored and the correct rental corner. Then, as a terminal movement request, the transaction information management device 80 displays content instructing the store clerk to move the rental terminal 50B to be monitored to the correct rental corner. Also in this case, the number assigned to the rental terminal 50B to be monitored may be displayed. When a store clerk sees this display requesting the movement of a terminal, he or she can go to the rental corner where the rental terminal 50B to be monitored is located, pick up the rental terminal 50B to be monitored, move it to the correct rental corner, and have it charged by the charging device 90. In other words, the store clerk can return the rental terminal 50B that was placed in the wrong rental corner to the state it was in when it was correctly returned.

[0209] Step S509: If it is determined in step S503 that a certain time has passed without product registration starting, or if it is determined in step S504 that a certain time has passed without payment starting, or if it is determined in step S505 that a certain time has passed without a terminal return notification being received, the rental terminal 50B to be monitored is in the following state: In other words, the rental terminal 50B to be monitored is in the state where the customer has not completed the shopping process that would normally have been completed since the customer took it out of the rental corner, and the customer is still carrying it in the store. Therefore, in this case, transaction information management device 80 outputs a terminal status confirmation request. The terminal status confirmation request is a request to confirm the status of lending terminal 50B, which is currently the monitoring target. The request to check the terminal status may be, for example, a display showing the location of the rental terminal 50B to be monitored in the store and instructing the store clerk to check the status of the rental terminal 50B to be monitored. In this case, the number assigned to the rental terminal 50B to be monitored may also be displayed. When a store clerk sees such a display requesting confirmation of terminal status, they can go to the location of the rental terminal 50B to be monitored, as indicated in the display requesting confirmation of terminal status, check the status of the rental terminal 50B to be monitored, and respond appropriately depending on the confirmed status.

[0210] <Modification> Modifications of this embodiment will be described below. The following modifications may be combined as appropriate.

[0211] [First Modification] In addition, when the settlement device 40 completes the corresponding settlement, a transaction completion notification may be sent from the transaction management device 60 to the rental terminal 50B. By receiving the transaction completion notification, the rental terminal 50B can recognize that the corresponding transaction has been completed. In response to receiving the transaction completion notification, the rental terminal 50B may, for example, return the display to the startup screen or display a message instructing the customer to return the rental terminal 50B to the correct rental corner.

[0212] [Second Modification] 19 is issued by the transaction information management device 80, a warning may be issued to the customer at the rental terminal 50B to be monitored, for example, by remote control of the transaction information management device 80 or the transaction management device 60. The warning may be issued by display, sound (electronic sound, voice), vibration, or the like. In this case, the volume or type of the warning sound, for example, may be changed so that the level of warning increases over time as the warning starts.

[0213] [Third Modification] The rental terminal 50B may be configured to notify the transaction information management device 80 of the remaining battery power at a predetermined timing or periodically. The transaction information management device 80 may be configured to output information about the remaining battery charge by display or the like, for example, in response to the notified remaining battery charge falling below a certain level when the rental terminal 50B to be monitored is not being charged by the charging device 90. At the same time, the rental terminal 50B may also be configured to notify information about the remaining battery charge, for example. Furthermore, the transaction information management device 80 may be configured to output information regarding the remaining battery charge of each standby rental terminal 50B being charged by the charging device 90. This allows a store clerk using the transaction information management device 80 to monitor the remaining battery charge of each standby rental terminal 50B. For example, for rental terminals 50B being charged by the charging device 90 whose remaining battery charge is below a certain level, the store clerk can accurately perform an operation such as replacing the rental terminal 50B with a fully charged spare rental terminal 50B. In this case, the transaction information management device 80 may, for example, determine the current usage frequency (turnover rate) of the rental terminal 50B and calculate a threshold value of the remaining battery charge at which the rental terminal 50B needs to be replaced with a spare rental terminal 50B based on the determined usage frequency.

[0214] In addition, among the rental terminals 50B that are on standby and being charged by the charging device 90, rental terminals 50B whose remaining battery charge may reach zero before the use corresponding to a single transaction is completed may be controlled by the transaction information management device 80 or the transaction management device 60 so that they cannot be used for product registration.

[0215] [Fourth Modification] The charging device 90 may be configured to be able to charge the rental terminal 50B by a contact type connection such as a connector. In this case, communication may be possible when the charging device 90 and the rental terminal 50B are connected by the connector. When communication is performed in this manner, for example, the port number of the charging device 90 to which the rental terminal 50B is connected can be used as location information of the rental terminal 50B at the rental corner. Furthermore, by connecting the charging device 90 and the rental terminal 50B so that they can communicate with each other, for example, the battery remaining capacity status of the rental terminal 50B can be transmitted to the charging device 90, and then transmitted from the charging device 90 to the transaction information management device 80 or the transaction management device 60.

[0216] [Fifth Modification] The rental terminal 50B may be provided with an anti-theft tag or an RFID tag, which can firmly prevent the terminal from being moved outside the store.

[0217] [Sixth Modification] In addition, the output of notifications for moving outside the store, requests to move the terminal, and requests to check the terminal status may be performed not only by the transaction information management device 80, but also by devices used in the store, such as the management device 10, the settlement device 40, or a store clerk's mobile terminal carried by the store clerk.

[0218] [Seventh Modification] The terminal status screen may, for example, in one terminal status area, arrange list items IM-A of the rental terminal 50B and list items IM-B of the personal terminal 50A in a mixed manner in a predetermined order such as by transaction start time. In this case, the sort order of the list items IM may be switchable, for example, by the transaction start time, the number of registered items, the estimated total, etc.

[0219] [Eighth Modification] Rental terminal 50B may detect that it has been removed from charging device 90 based on the detection output of its own acceleration sensor, gyro sensor, or the like. If a customer uses a dedicated shopping cart having a terminal holder for mounting rental terminal 50B when shopping, rental terminal 50B may also detect that it has been mounted in the terminal holder of the shopping cart after being removed from charging device 90, and transmit that it has been mounted in the terminal holder to transaction information management device 80. In this way, even if rental terminal 50B is left unattended before the first product is registered, transaction information management device 80 can monitor the abandoned state based on the time from when rental terminal 50B is removed from charging device 90 to when it is mounted in the terminal holder.

[0220] [Ninth Variation] The product information input screen P40 in Fig. 18 may be configured to allow a search for products registered in the corresponding transaction. Furthermore, the search possible in this modification may be a fuzzy search that searches for products that "contain" the input keyword. For example, a button for instructing a fuzzy search is placed on the product information input screen P40 of this modified example. When this button is operated, a character input keyboard with, for example, the Japanese syllabary (or the alphabet) is displayed in the input operation area AR42. The store clerk operates the character input keyboard to input a keyword, which may be part of the name of the product to be searched for. At this time, it may be possible to convert the hiragana characters entered as the keyword into a word. The store clerk then operates the search execution button placed on the product information input screen P40. In response to the operation of the search execution button, the transaction information management device 80 executes a fuzzy search and displays the search results. The search results may be displayed, for example, as a pop-up screen. The search results may also display the product name, price, registered number, etc. of each searched product. The clerk identifies the unidentified product to be processed from the products presented as search results and performs an operation to select the identified product. In response to this operation, for example, the display may return to the product information input screen P40. In the displayed input operation area AR42, the product name, price, registration quantity, product code, etc. of the selected product are entered. After checking the content displayed in the input operation area AR42, the clerk operates the register button BT41. This allows the clerk to efficiently release the hold on the unidentified product without, for example, having to enter a number with many digits as a product code or narrow down the search by product category.

[0221] [Tenth Modification] For example, by operating a screen such as the status confirmation screen P10 in Figure 17 or the product information input screen P40 in Figure 18, a moving image (or a time-lapse image) of the captured image corresponding to the product registration operation when the target unspecified product is registered may be displayed. The operation to display a moving image may be, for example, an operation on a moving image display button located on the status confirmation screen P10 or the product information input screen P40, or may be, for example, an operation on the captured image G12 on the status confirmation screen P10 or the target captured image area AR43-1 or the next captured image area AR43-2 on the product information input screen P40. For example, when the next captured image is displayed, a video may be displayed from the start of the product registration operation when the target unspecified product is registered until the product corresponding to the next captured image is captured. The video may be deleted, for example, when the payment is completed. However, if the transaction is terminated without completing the payment for some reason, the video may be stored for a certain period of time after the transaction is completed so that the store clerk can review it even after the transaction is completed. The video may be stored in the transaction management device 60 or the transaction information management device 80 in association with the date, member identification information, etc. The stored video can be played back on a terminal such as the transaction information management device 80.

[0222] [Eleventh Modification] In the above embodiment, the rental terminal 50B is assigned to a specific rental corner, and the rental terminal 50B that a customer takes out of the rental corner for use is returned to the same rental corner. In contrast, in this modified example, after a customer takes a rental terminal 50B from a designated rental corner and uses it, the rental terminal 50B is stored in a collection box installed in a designated location in the store. In this case, as the rental terminal 50B is used, the collection box will contain more rental terminals 50B that have been used. For this reason, a store clerk collects the rental terminal 50B from the collection box at a certain point in time and places the collected rental terminal 50B in a charging device at the designated rental corner. As a result, the rental terminal 50B will be in a waiting state while being charged at the rental corner. In the following description, the work of a store clerk collecting the rental terminal 50B from the collection box and installing the collected rental terminal 50B in a charging device at a specified rental corner will also be referred to as "terminal collection work."

[0223] In this modified example, the processing shown in FIG. 10 is also executed by the customer terminal device 50 (including the rental terminal 50B), the settlement device, and the transaction management device 60. The rental terminal 50B may execute the processing shown in FIG. 20. The transaction information management device 80 may execute the processing in FIG. 20. The rental terminal 50B may also, for example, when generating a two-dimensional code in response to a settlement transition instruction operation, send a notification (two-dimensional code generation notification) to the transaction information management device 80 that the two-dimensional code has been generated. This allows transaction information management device 80 to manage the status of rental terminal 50B, indicating whether it is "waiting," "registering product," "generating two-dimensional code," "settling," or "settling completed." In other words, transaction information management device 80 acquires status information indicating the status of rental terminal 50B.

[0224] "Waiting" refers to a state in which the rental terminal 50B is loaded so that it can be charged by a charging device at a designated rental corner. In "waiting," the rental terminal 50B may be charging, or charging may have stopped because it has reached a fully charged state.

[0225] "Product registration in progress" is a state in which the rental terminal 50B is taken out by a customer and processing for product registration is being performed in response to an operation on the transaction start instruction button BT10.

[0226] "Two-dimensional code generation" is a state in which the rental terminal 50B displays a two-dimensional code in response to a settlement transition instruction operation being performed.

[0227] "Checkout in progress" means that the checkout device 40 is performing the checkout process in response to the customer having the 2D code read, and the rental terminal 50B has already completed the product registration process, but the product is still treated as being in the customer's possession.

[0228] "Payment completed" indicates that the payment process has been completed by the payment device 40, but the rental terminal 50B has not yet been loaded into the charging device at the specified rental corner. Among these statuses, statuses such as "item registration in progress", "payment in progress", and "payment completed" may also be used as information indicating the status of the corresponding transaction (transaction status).

[0229] Also in this modification, transaction information management device 80 may display a terminal status screen (FIG. 15) based on information such as cart information transmitted from transaction management device 60. At this time, transaction information management device 80 may display the above-mentioned status in list item IM-A for transactions handled by the above-mentioned rental terminal 50B. In other words, transaction information management device 80 in this modification obtains status information indicating the status of rental terminal 50B from transaction management device 60.

[0230] Furthermore, in this modified example, a predetermined notification may be made when the number of rental terminals 50B in a predetermined status reaches or exceeds a predetermined number, as exemplified below. In the following explanation, an example will be given in which the transaction information management device 80 determines whether the number of rental terminals 50B in a predetermined status reaches or exceeds a predetermined number, and makes a notification in accordance with the determination result.

[0231] [Notification example 1] The transaction information management device 80 may monitor (count) the number of rental terminals 50B in the "product registration in progress" state, determine whether the number of rental terminals 50B in the "product registration in progress" state has reached a certain level, and issue an alert when the number has reached a certain level.

[0232] When the number of rental terminals 50B in the "product registration in progress" state exceeds a certain level, it can be said that there is a shortage of rental terminals 50B in the "waiting" state. If the shortage of rental terminals 50B in the "waiting" state continues, soon all of the rental terminals 50B in the "waiting" state will be in use. This will lead to customers who had intended to use the rental terminal 50B giving up on using the rental terminal 50B. Furthermore, when the number of rental terminals 50B in the "product registration in progress" state exceeds a certain level, the number of rental terminals 50B stored in the collection box will also be low. For this reason, when the number of rental terminals 50B being monitored that are in the "product registration in progress" state exceeds a certain number, it is preferable to replenish the supply by placing spare rental terminals 50B in the rental corner.

[0233] Therefore, when the number of rental terminals 50B in the "product registration in progress" state reaches a certain level, the transaction information management device 80 may issue an alert to instruct a store clerk to add and deploy a spare rental terminal 50B to the rental corner, for example, because there are many terminals currently on loan.

[0234] Such notification may be displayed in a predetermined area on the device status screen, or may be displayed as a pop-up screen superimposed on the device status screen. This point may also be applied to the following notifications.

[0235] [Notification example 2] In addition, the transaction information management device 80 may monitor the number of rental terminals 50B in the "product registration completed" state, determine whether the number of rental terminals 50B in the "product registration completed" state has reached a certain level or more, and issue an alert when the number has reached a certain level or more. The "product registration completed" state corresponds to any of the states of "two-dimensional code generation," "checkout in progress," and "checkout completed." In other words, the "product registration completed" state of rental terminal 50B means that the product registration process has been completed, but the device has not yet been charged at the designated rental corner.

[0236] Even when the number of rental terminals 50B in this "product registration completed" state exceeds a certain number, it can be said that there is a shortage of rental terminals 50B in the "standby" state, just as in the "product registration in progress" state. Furthermore, when the number of rental terminals 50B in the "product registration completed" state exceeds a certain number, there is a possibility that a large number of rental terminals 50B are stored in the collection box. Therefore, when the number of rental terminals 50B in the "product registration completed" state reaches a certain number or more, the transaction information management device 80 may, for example, instruct terminal collection work, and if there are still few rental terminals 50B in standby state even after the terminal collection work has been performed, may issue an alert instructing that a spare rental terminal 50B be deployed in standby state.

[0237] [Notification example 3] Furthermore, the transaction information management device 80 may monitor the number of rental terminals 50B in the "standby" state, determine whether the number of rental terminals 50B in the "standby" state has reached a certain level, and issue an alert when the number reaches the certain level. The "standby" state corresponds to a state in which the rental terminal 50B is "charging" when it is loaded into a charging device at the rental corner. Note that the "charging" state here may refer to a state in which the rental terminal 50B is loaded into a charging device, and may also include a state in which charging has been stopped because the rental terminal 50B is fully charged.

[0238] If the number of rental terminals 50B in the "waiting" state is equal to or greater than a certain number, it means that the rental terminals 50B are not currently being used by customers very often. For example, the rental terminal 50B may be rented out with the goal of increasing the number of customers who shop using the personal terminal 50A, and with the aim of encouraging customers who have not yet used the personal terminal 50A to try shopping using the customer terminal device 50. In such a situation, when the rental terminal 50B is not being used much, it is advisable for a store clerk to encourage customers in the store to use the rental terminal 50B. Therefore, when the number of rental terminals 50B in the "waiting" state reaches a certain number or more, the transaction information management device 80 may issue an alert, for example, instructing a store clerk to encourage customers to use the rental terminal 50B.

[0239] In addition, the number of rental terminals 50B to be monitored in each of the above examples may be determined by directly recognizing the number of rental terminals 50B in the corresponding state, or by performing a calculation using the number of rental terminals 50B in two or more specific states. As an example, the number of rental terminals 50B in the "waiting" state can be calculated by subtracting the number of rental terminals 50B in each of the following states: "product registration in progress," "2D code generation," "payment in progress," and "payment completed" from the total number of rental terminals 50B currently operating in the store.

[0240] The transaction information management device 80 may be configured to issue a predetermined notification when the number of rental terminals 50B in a predetermined state falls below a certain level. For example, when the number of rental terminals 50B in the "standby" state reaches a certain level, a notification may be issued to instruct a store clerk to collect the terminals or to place a spare rental terminal 50B in the rental corner.

[0241] In addition, the transaction information management device 80 may also obtain statuses of the personal terminals 50A, such as "product registration in progress," "two-dimensional code generation," "settlement in progress," and "settlement completed," and may issue a predetermined notification according to the number of personal terminals 50A corresponding to each status.

[0242] In addition, the notification in this modified example may be made not only by the transaction information management device 80 but also by the POS register where the store clerk is operating to register the product, or by a store clerk terminal carried by the store clerk, etc.

[0243] [12th Modification] In the above-described embodiments and variations, part of the processing performed by the customer terminal device 50, transaction information management device 80, etc. may be performed by a higher-level device such as a transaction management device 60 connected via communication to the customer terminal device 50. In addition, in the above-described embodiments and variations, part of the processing performed by the settlement device 40 may be performed by a higher-level device such as a transaction management device 60 connected via communication to the settlement device 40. As one of the above aspects, the shopping system of this embodiment may be provided with the configuration of a thin client system. As an example, the transaction management device 60 may be configured as a thin client-compatible server (e.g., a cloud server), and the customer terminal device 50, transaction information management device 80, etc. may function as thin clients. In this case, the thin client terminals, such as the customer terminal device 50 and transaction information management device 80, transmit captured images and information such as commands corresponding to operations performed on them to the transaction information management device 80. The transaction information management device 80 may execute processing in response to the information received from the thin client terminal, and transmit image data or web page data, such as a screen reflecting the processing results, to the thin client terminal. The customer terminal device 50, transaction information management device 80, etc., acting as thin client terminals, display the transmitted image data or web page data using an image viewer or web browser.

[0244] <Summary of the embodiment> [Technical field] The present invention relates to a product sales data processing system and a program. [Background technology] BACKGROUND ART There is known a technology that allows customers to purchase products using a mobile device when shopping in a store (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2018-055700 A [Summary of the Invention] [Problem to be solved by the invention] In a shopping system in which customers use portable devices (portable terminals) to shop as described above, the portable terminals may be shared between a personal terminal carried by the customer and a rental terminal that is temporarily lent to the customer by the store depending on the time the customer is shopping. In such a case, it is preferable for the store, for example, to be able to manage the mobile terminals used by customers shopping at the store in a way that allows them to distinguish between personal terminals and rental terminals. The present invention aims to enable management of mobile terminals used for shopping in stores in such a way that they can be identified as either personal terminals or rental terminals.

[0245] [Means for solving the problem] (1) As described above, one aspect of this embodiment is a merchandise sales data processing system that includes a mobile terminal (e.g., rental terminal 50B) used by a customer to register a product in a transaction, and a transaction information management device (80) that manages the transaction status, and that includes, in the mobile terminal, an identification information output means that outputs identification information that identifies the device (e.g., application identification information, terminal identification information), in the transaction information management device, a counting means that counts the mobile terminals that have output identification information by the identification information output means, and a notification means that notifies when the number of mobile terminals counted by the counting means meets a predetermined condition (e.g., a predetermined number or more, or a predetermined number or less).

[0246] According to the above configuration, it is possible to instruct a store clerk to improve the deployment status of the rental terminals 50B, for example, depending on the number of rental terminals 50B. This makes it possible to appropriately manage the mobile terminals used by customers for shopping in the store.

[0247] (2) One aspect of this embodiment is a product sales data processing system as described in (1), in which the transaction information management device is provided with a status information acquisition means for acquiring status information indicating that the mobile terminal is in a predetermined state.

[0248] According to the above configuration, it is possible to instruct a store clerk to improve the deployment status of the rental terminals 50B, for example, depending on the number of rental terminals 50B in a predetermined state.

[0249] (3) One aspect of this embodiment is the product sales data processing system described in (2), wherein the notification means notifies when the number of mobile terminals that are indicated to be in a product registration state by the acquired status information satisfies a predetermined condition.

[0250] According to the above configuration, it is possible to instruct a store clerk to improve the deployment status of the rental terminals 50B, for example, depending on the number of rental terminals 50B in the product registration in progress state.

[0251] (4) One aspect of this embodiment is a product sales data processing system as described in (2) or (3), wherein the notification means notifies when the number of mobile terminals that are indicated to be in a state where product registration has been completed based on the acquired status information satisfies a predetermined condition.

[0252] According to the above configuration, it is possible to instruct a store clerk to improve the deployment status of the rental terminals 50B, for example, depending on the number of rental terminals 50B for which product registration has been completed.

[0253] (5) One aspect of this embodiment is a product sales data processing system described in any one of (2) to (4), wherein the notification means notifies when the number of the mobile terminals indicated as being charged by the acquired status information satisfies a predetermined condition.

[0254] According to the above configuration, it is possible to instruct the store staff to improve the deployment status of the rental terminals 50B, for example, depending on the number of rental terminals 50B that are in a charging state.

[0255] (6) One aspect of this embodiment is a product sales data processing system described in any one of (2) to (5), in which the transaction information management device displays information regarding instructions for deploying mobile terminals in the store based on information for each mobile terminal indicated by the acquired status information.

[0256] According to the above configuration, it is possible to determine which rental terminals 50B should be deployed in the store and how, based on the number of rental terminals 50B in a predetermined state, and then issue a notification regarding deployment instructions.

[0257] (7) One aspect of this embodiment is a program for causing a computer serving as a server in a product sales data processing system having a mobile terminal used by a customer to register a product in a transaction and a transaction information management device that manages the transaction status to function as an identification information acquisition means that acquires identification information that identifies the mobile terminal and is output from the mobile terminal, a counting means that counts the mobile terminals whose identification information has been acquired by the identification information acquisition means, and a notification means that issues a notification when the number of mobile terminals counted by the counting means meets a predetermined condition.

[0258] [Note] While the embodiments of the present invention have been described above in detail, the specific configuration is not limited to these embodiments, and the present invention also includes designs that do not deviate from the gist of the present invention.

[0259] (Appendix 1) A monitoring device (e.g., transaction information management device 80) in which a rental terminal (50B) rented to a customer by a store and a personal terminal (50A) carried by the customer are used as mobile terminals (e.g., customer terminal device 50) used by customers to register products in a store, the monitoring device (e.g., transaction information management device 80) comprising: a location information acquisition means for acquiring location information indicating the location of the mobile terminal; and a first notification means (S302) for notifying that the rental terminal is not present within a predetermined location range (e.g., a location range corresponding to within the store) when the location indicated by the location information acquired by the location information acquisition means for the rental terminal is not included in the predetermined location range (e.g., a location range corresponding to within the store).

[0260] According to the above configuration, when personal terminal 50A is moved outside the store, it is possible to notify a store clerk of this fact using, for example, transaction information management device 80. This prevents rental terminal 50B from being taken outside the store, and makes it possible to properly manage rental terminals used in the store.

[0261] (Appendix 2) One aspect of this embodiment is the monitoring device described in (Appendix 1), which is equipped with a position determination means (step S507) that determines whether the position information acquired by the position information acquisition means for the rental terminal corresponds to a specific waiting position (e.g., a position corresponding to a rental corner) within the specified position range.

[0262] According to the above configuration, it is possible to determine whether the rental terminal 50B has been returned to the correct rental corner.

[0263] (Appendix 3) One aspect of this embodiment is a monitoring device as described in (Appendix 2), which is provided with a processing status determination means for determining the processing status of the mobile terminal, and when the processing status determination means determines that processing corresponding to product registration has been executed for the rental terminal, if the waiting position determined by the position determination means is different before and after the processing corresponding to the product registration is started (S507), it is provided with a second notification means (S508) for notifying that the waiting position is different.

[0264] According to the above configuration, if the rental terminal 50B is not returned to the correct rental corner, a notification to that effect is sent, and a store clerk can immediately take action, such as moving the rental terminal 50B to the correct rental corner.

[0265] (Appendix 4) One aspect of this embodiment is a monitoring device described in any one of (Appendix 1) to (Appendix 3), comprising an identification information acquisition means (step S101) that acquires identification information that identifies the mobile terminal, and a discrimination means (S102, S103, S104) that discriminates whether the mobile terminal is a rental terminal or a personal terminal owned by a customer based on the identification information acquired by the identification information acquisition means.

[0266] According to the above configuration, in a store where a mixture of personal terminals 50A and rental terminals 50B are used as customer terminal devices 50, the personal terminals 50A and rental terminals 50B can be distinguished from each other when managing the customer terminal devices 50. Furthermore, when managing transactions taking place in the store, transactions using the personal terminals 50A and transactions using the rental terminals 50B can be distinguished from each other when managing the transactions.

[0267] (Appendix 5) One aspect of this embodiment is the monitoring device described in (Appendix 4), which is equipped with a display means that displays mobile terminals present in the store so that they can be distinguished as rental terminals and personal terminals based on the determination result by the discrimination means.

[0268] According to the above configuration, when displaying a list of transactions, for example, it is possible to visually distinguish between transactions using the personal terminal 50A and transactions using the rental terminal 50B.

[0269] (Appendix 6) One aspect of this embodiment is the monitoring device described in (Appendix 5), wherein the display means displays at least the rental terminals that are in an activated state among the rental terminals and the personal terminals that are executing processing corresponding to the transaction.

[0270] According to the above configuration, for example, a store clerk can grasp the transaction status corresponding to the personal terminal undergoing product registration and the rental terminal 50B by looking at the terminal status screen display on the transaction information management device 80. Furthermore, for the rental terminal 50B, the clerk can grasp the standby status other than during product registration, the status of spare storage, the charging status, etc.

[0271] (Appendix 7) One aspect of this embodiment is a monitoring device described in any one of (Appendix 1) to (Appendix 6), which is equipped with a location status display means for displaying the status of at least the rental terminal based on the location information acquired by the location information acquisition means.

[0272] According to the above configuration, it is possible to notify the store clerk of the location in the store of at least the rental terminal 50B as the customer terminal device 50 being used for the transaction.

[0273] (Appendix 8) One aspect of this embodiment is the monitoring device described in (Appendix 7), in which the location status display means displays a message notifying the user that the rental terminal is not present in the store when the location indicated by the location information acquired by the location information acquisition means for the rental terminal is not included in the location range corresponding to the store.

[0274] According to the above configuration, it is possible to accurately notify the store clerk by displaying a message that the rental terminal 50B has been taken out of the store.

[0275] (Appendix 9) One aspect of this embodiment is a product sales data processing system in which a rental terminal rented to a customer by a store and a personal terminal carried by the customer are used as mobile terminals used by customers to register products at the store, and the product sales data processing system is equipped with a location information acquisition means for acquiring location information indicating the location of the mobile terminal, and a notification means for notifying that the rental terminal is not present within a predetermined location range if the location indicated by the location information acquired by the location information acquisition means for the rental terminal is not included in the predetermined location range.

[0276] (Appendix 10) One aspect of this embodiment is a program that functions as a computer serving as a server that communicates with a mobile terminal used by a customer to register a product at a store, a process execution control means that causes the mobile terminal used by the customer to register a product at a store to execute a process corresponding to the product registration, a location information acquisition means that acquires location information indicating the location of the mobile terminal, and a notification means that causes a monitoring device to execute a process that notifies the customer that the mobile terminal is not present within a predetermined location range when the location indicated by the location information acquired by the location information acquisition means for the mobile terminal is not included in a predetermined location range, whether the mobile terminal is a rental terminal rented to the customer by the store or a personal terminal held by the customer.

[0277] In addition, a program for implementing the functions of the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction information management device 80, charging device 90, etc. described in each of the above embodiments may be recorded on a computer-readable recording medium, and the program may be loaded into a computer system and executed to perform processing as the management device 10, settlement device 40, customer terminal device 50, transaction management device 60, transaction information management device 80, etc. Here, "loading 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. The "computer system" may also include multiple computer devices connected via a network, including communication lines such as the Internet, a WAN, a LAN, and a dedicated line. The "computer-readable recording medium" refers to portable media such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and storage devices such as a hard disk built into a computer system. In this way, the recording medium storing the program may also be a non-transitory recording medium such as a CD-ROM. The term "recording medium" also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in a format executable by a terminal device. In other words, the format in which the program is stored on the distribution server is not important as long as it can be downloaded from the distribution server and installed in a format executable by a terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on a terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" also includes a medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be for implementing part of the functions described above.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]

[0278] 10 management device, 40 settlement device, 50 customer terminal device (50A personal terminal, 50B rental terminal), 60 transaction management device, 70 credit card settlement server, 80 transaction information management device, 90 charging device

Claims

1. A product sales data processing system including a mobile terminal used by a customer to register a product in a transaction, and a transaction information management device that manages the transaction status, The mobile terminal Identification information output means for outputting identification information for identifying the device itself Equipped with The transaction information management device a determination means for determining whether the portable terminal for which the identification information has been output by the identification information output means is a personal terminal or a rental terminal; a counting means for counting the number of mobile terminals determined to be rental terminals by the determination means; a notification means for notifying when the number of rental terminals counted by the counting means satisfies a predetermined condition; a status information acquisition means for acquiring status information indicating that the mobile terminal is in a predetermined state; Equipped with Product sales data processing system.

2. The transaction information management device comprises: The system further includes a display unit that displays information regarding instructions for distributing the mobile terminal determined by the determination unit to be a rental terminal in a store based on the information for each mobile terminal indicated by the acquired status information.

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

3. The display means displays information about the charging state of the rental terminal based on the acquired status information.

3. The merchandise sales data processing system according to claim 2.

4. The notification means notifies when the number of rental terminals indicated by the acquired status information to be in a state of product registration satisfies a predetermined condition, and when the number of rental terminals indicated by the acquired status information to be in a state of product registration having been completed satisfies a predetermined condition.

4. The merchandise sales data processing system according to claim 1.

5. A program for causing a computer to function as a transaction information management device in a product sales data processing system including a mobile terminal used by a customer to register a product in a transaction and a transaction information management device that manages a transaction status, the program comprising: The computer an identification information acquisition means for acquiring identification information output from the portable terminal, the identification information identifying the portable terminal; a determination means for determining whether the portable terminal whose identification information has been acquired by the identification information acquisition means is a personal terminal or a rental terminal; a counting means for counting the number of mobile terminals determined to be rental terminals by the determination means; a notification means for notifying when the number of rental terminals counted by the counting means satisfies a predetermined condition; a status information acquisition means for acquiring status information indicating that the mobile terminal is in a predetermined state; A program to function as a

Images