program

Abstract

To make it possible to restrict the number of users who can use applications of terminal devices for use in shopping in a shop to a certain range.SOLUTION: The present invention is directed to a program for making a computer function as: identifying means for identifying a shop based on a shop specifying information; determination means for determining whether or not use of an article registration application installed into a portable terminal is permitted according to a shop identified by the identifying means; and control means for controlling, if the determination means determines that permission to use the application is necessary, the portable terminal to display a use permission processing screen responding to use permission processing for permitting use of the application and for controlling, if the determination means determines that permission to use the application is not necessary, the portable terminal to display an article registration screen corresponding to an article registration.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] The present invention relates to a program. [Background technology]

[0002] 2. Description of the Related Art There is known a self-registration system that allows a customer to register products using a smartphone or the like when shopping in a store (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] The registration of products by customers as described above is performed using a specific application installed on a mobile terminal such as a smartphone owned by the customer. For example, due to circumstances of a store, it may be necessary to limit the users who can use the specific application to a certain range.

[0005] The present invention has been made in consideration of the above circumstances, and has an object to make it possible to limit to a certain range of users who can use applications on a mobile terminal used for shopping at a specific store. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a program for causing a computer to function as control means that includes an identification means for identifying a store based on store identification information, a judgment means for judging whether or not permission to use a product registration application installed on a mobile terminal is required depending on the store identified by the identification means, and, if the judgment means determines that permission to use the application is required, controls so that a usage permission processing screen corresponding to the usage permission processing for allowing use of the application on the mobile terminal is displayed, and, if the judgment means determines that permission to use the application is not required, controls so that a product registration screen corresponding to product registration is displayed. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a shopping system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of installation of a settlement device in this embodiment. [Diagram 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 in the present embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a customer terminal device in the present embodiment. [Figure 6] 1 is a diagram illustrating an example of the configuration of a transaction management device in this embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of a store management server according to the present embodiment. [Figure 8] 3A to 3C are diagrams illustrating an example of customer information, store information, and cart information according to the present embodiment. [Figure 9] A sequence diagram showing an example of processing procedures executed by a customer terminal device, a settlement device, and a transaction management device in this embodiment in response to the accounting of one transaction in self-service operation. [Figure 10] FIG. 2 is a diagram showing an example of a screen of a shopping application in the present embodiment. [Figure 11]13A to 13C are diagrams showing an example of a registered product presentation screen and a screen displayed on a settlement device in this embodiment. [Figure 12] FIG. 13 is a diagram showing an example of a screen on which an input declaration operation of a usage permission code is performed in the embodiment; [Figure 13] FIG. 4 is a diagram showing an example of a usage permission information table in the present embodiment. [Figure 14] 11 is a flowchart showing an example of a processing procedure executed by a customer terminal device and a transaction management device in this embodiment in relation to lifting usage restrictions on a shopping application with a usage restriction function. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] First Embodiment [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 in Fig. 1 corresponds to accounting (customer terminal-compatible accounting) in which, for example, a customer takes out a product to be purchased from a product shelf, registers the taken-out product using a customer terminal device 50, and the same customer also uses a payment device 40 to settle the payment for the registered product. The accounting here refers to a procedure carried out in response to one transaction, including the registration of the product and the settlement of 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 status monitoring device 80, a store management server 90, and a credit card settlement server 70.

[0009] The management device 10 and the settlement device 40 are installed in the store and are connected to each other so as to be able to communicate with each other 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 and the like, and is capable of communicating with the transaction management device 60. The transaction status monitoring device 80 is a business terminal used in the store to monitor the transaction status of customers who register products using the customer terminal device 50. The transaction status monitoring function of the transaction status monitoring device 80 includes outputting information on the transaction status by displaying it, as well as controlling transactions such as releasing the reserved state of reserved products in response to operations by store staff, which will be described later. The transaction status monitoring device 80 is capable of communicating with the transaction management device 60, and is capable of realizing the transaction status monitoring function by sending and receiving data to and from the transaction management device 60. Although four settlement devices 40 are illustrated in FIG. 1, the number of settlement devices 40 within one store is not particularly limited.

[0010] The customer terminal device 50 is operated by customers (such as shoppers who are members of the store, hereinafter also referred to simply as customers). 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, that is, recognizes barcodes attached to products. Note that the recognition function of the customer terminal device 50 only needs to be able to read product codes, and does not need to be able to recognize which product the read product code belongs to. In other words, the customer terminal device 50 only needs to be able to read a product code from a barcode that exists as an object in an image captured by the imaging function (an image acquired as a through image).

[0011] Such a customer terminal device 50 may be a smartphone, a tablet terminal, or the like owned by a customer. A shopping application having a function of registering products in accordance with the shopping system of this embodiment is installed in the smartphone, tablet terminal, or the like serving as the customer terminal device 50.

[0012] Furthermore, the customer terminal device 50 may be, for example, a terminal loaned from a store to a customer. An application having a function of registering products in accordance with the shopping system of this embodiment is also installed in the customer terminal device 50 loaned from the store to a customer. The customer terminal device 50 loaned from the store to a customer may be one that is held by the customer or may be one that is attached to a shopping cart and used by the customer.

[0013] The customer terminal device 50 also captures an image (e.g., releases the shutter) of the product (e.g., the peripheral portion with a barcode attached) and generates a captured image (image data). The customer terminal device 50 may capture an image by releasing 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 captures an image by releasing the shutter at its own discretion.

[0014] In addition, 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 an imaged subject (object, etc.). For example, the customer terminal device 50 may use the image recognition technology to identify (estimate) an imaged product.

[0015] The settlement device 40 is a settlement device capable of at least cash payment as a settlement method. The settlement device 40 is configured to be able to communicate with the transaction management device 60. The settlement device 40 may be configured to be able to communicate with the transaction management device 60, for example, via 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 store management server 90 manages transaction records performed at the store and member information related to members registered as customers of the store. The store management server 90 may, for example, comprehensively manage the transaction records and member information of multiple stores of the same chain.

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

[0019] [About the payment device] Fig. 2 is a diagram showing an example of the installation of the settlement device 40. Fig. 2(A) is a perspective view of the settlement device 40 etc. as seen from the customer side. Fig. 2(B) is a perspective view of the settlement device 40 etc. as seen from the store clerk side. As shown in Fig. 2(A), a counter is placed on the right side of the settlement device 40 as seen from the customer side.

[0020] Fig. 3 is a diagram showing an example of the appearance of the settlement device 40. Fig. 3(A) is a perspective view of the settlement device 40 as seen from the customer side. Fig. 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 of the 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 machine 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, and 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, and stores various types of information used by the CPU 401, including programs.

[0023] The RAM 403 is a read / write memory and stores various 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 information. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information acquired 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 and reads the product code. Customer-side scanner unit 406 may also scan a code (barcode, two-dimensional code, etc.) printed on a bill (registered trademark) and read information required for payment. Customer-side scanner unit 406 may also scan a code (two-dimensional code, etc.) displayed on the display unit of customer terminal device 50 and read information required for payment.

[0026] Although the 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 the 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 uses 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 that the card payment unit 408 includes at least the card recognition unit. The card recognition unit may also recognize various cards (e.g., membership cards, point cards, etc.) that are not directly used for payment (settlement).

[0028] The change machine 409 (cash settlement unit) is a cash settlement mechanism, which has an input port for banknotes and coins, and an output port for banknotes and coins, calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. The change machine 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, detecting the number of coins by denomination, etc.).

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

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

[0031] The store clerk's display unit 410 is a touch display for the store clerk, which 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 a barcode attached to a product and reads the product code. The store clerk scanner unit 412 also scans a barcode attached to the name tag of the store clerk and reads the store clerk code.

[0032] Although the store clerk's scanner unit 412 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper) is arranged on the key operation unit 411, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 410, the store 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 freely rotate to change its orientation (direction of the media issuing port) from the clerk side to the customer side and from the customer side to the clerk side. 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 operation mode described below. The correctness of the 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 the 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-responsive settlement mode, which is set to perform settlement processing under customer terminal-responsive 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 operation mode in which the store clerk performs product registration operations and operations corresponding to payment on the payment device 40. The second payment mode is an operation mode in which the store clerk performs product registration operations on the payment device 40, and the customer performs operations corresponding to payment on the same payment device 40. The third payment mode is an operation mode in which the 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 compatible payment mode to support customer terminal compatible payment, and the other payment devices 40 can be set to, for example, the first or second payment mode so that a store clerk can handle payments in consultation with customers. Note that the other payment devices 40 may also include those set to the third payment mode.

[0036] [Example of customer terminal device configuration] 5 shows an example of the configuration of the customer terminal device 50. The 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, and a network-compatible communication unit 507. The CPU 501 is a central processing unit, and 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 a main storage device for the CPU 501 . The display unit 504 displays an image 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. Furthermore, 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 wirelessly communicates via a network. The network-compatible communication unit 507 enables the customer terminal device 50 to communicate with the transaction management device 60.

[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, and controls the operation of the transaction management device 60 by reading and executing programs stored in the memory 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 501, including programs. The RAM 603 is a main storage device for 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] [Store management server configuration example] 7 shows an example of the configuration of a store management server 90. The store management server 90 in the figure comprises a CPU 901, a storage unit 902, a RAM 903, and a network-compatible communication unit 904. The CPU 901 is a central processing unit that controls the operation of the store management server 90 by reading and executing programs stored in the storage unit 902 . The storage unit 602 is an auxiliary storage device for the CPU 901, and stores various types of information used by the CPU 901, including programs. The RAM 903 is a main storage device for the CPU 901 . The network-compatible communication unit 904 is a unit that communicates with the outside via a network. In the case of the store management server 90, the network-compatible communication unit 904 can communicate with the transaction management device 60 on the cloud.

[0040] [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 (a customer's registration may be considered to have been completed when the customer information of that customer 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 update the customer information, for example, by referring to the cart information at a specified time every day.

[0041] 8(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, for example, a number that is uniquely (for example, 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 in which the shopping application is installed. The terminal identification information may be, for example, a telephone number assigned to a customer who is the user of the customer terminal device 50, or hardware identification information that is uniquely assigned to the hardware of the customer terminal device 50, such as a MAC (Media Access Control) address. The customer name is the customer's name or nickname, etc. The customer registration date is the date and time when the customer was registered. Cancellation information is information regarding the cancellation of registered products after registration. The customer rank is a rank according to the customer's purchasing 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 actual trading (product registration), other information (cancellation information, etc.) is not generated.

[0042] The transaction management device 60 generates and stores customer identification information, for example, when registering a customer (for example, when the customer terminal device 50 downloads or installs a shopping application to use a shopping service provided by the transaction management device 60 from an external device (for example, a specified server that provides all applications, the transaction management device 60 itself)). In addition, for example, when registering a customer, the transaction management device 60 acquires information entered into the name field of a registration form (input form) using the customer terminal device 50, and stores it as the customer name. In addition, the transaction management device 60 acquires, for example, the current date and time when registering the customer, and stores it as the customer registration date.

[0043] In addition, instead of or in addition to storing the customer information in its own memory unit, 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).

[0044] 8(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. 8(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. 8(B) is composed of the store (trade name) or company 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 a store where a transaction takes place (a store where a 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 carried out. In the example shown in FIG. 8(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.

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

[0046] The product information is, for example, information acquired from 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.

[0047] Cart information is information for managing individual transactions. The transaction management device 60 generates the cart information at the start of a transaction. In addition, the transaction management device 60 updates the cart information as the transaction progresses (each time a product is registered) (the storage of a product in the cart information may be interpreted as the registration of that product).

[0048] FIG. 8(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.

[0049] 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 each date). The transaction start date and time is the date and time when the transaction starts. The transaction start date and time may be, for example, the date and time when the cart information is generated. The transaction start date and time may be the date and time when the first item of product is registered (the date and time when the registered product information (registered product 1) in FIG. 8(C) is stored). The date and time when the cart information is generated and the date and time when the first item of product is registered may both be stored separately.

[0050] 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. The customer identification information is customer identification information that identifies the customer of the transaction. When the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are generated, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, etc.) is not generated. 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.

[0051] 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 (e.g., 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 8 (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.

[0052] 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 a basis for determining whether or not a service such as a time service should be applied and the effect of the application.

[0053] The reserved product information (total) is updated each time a reserved product is registered. A reserved product is a product that was not registered properly due to a certain 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, the number of reserved products that cannot be read (check for unauthorized operations), and the like.

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

[0055] 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 has not been scanned at the store. In other words, a read NG refers to a timeout process when it is possible to determine that a product has been imaged for a certain period of time using image recognition technology but has not been able to be recognized as a barcode, or a product that has been timed out. For example, if the barcode cannot be correctly acquired (recognized) despite the customer performing an operation to have the barcode read due to wrinkles in the package, smudges or dirt on the barcode print, or the barcode being printed on a transparent film, it will be determined that the barcode cannot be read.

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

[0057] 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 cannot be read) 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 (cannot be read)" and image data.

[0058] 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 by the transaction management device 60).

[0059] [Example of basic processing procedure for self-operation] The sequence diagram in Fig. 9 shows an example of a processing procedure executed by the customer terminal device 50, the settlement device 40, and the transaction management device 60 in response to the accounting of one transaction in a self-service operation. Specifically, the processing in Fig. 9 shows an example of the processing of the customer terminal device 50, the settlement device 40, and the transaction management device 60 from when a customer registers a product to be purchased from among products displayed in the store, until the settlement of the registered product is completed.

[0060] Step S1: The customer terminal device 50 acquires information for identifying a 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 (the two-dimensional code may be output on a display screen, a medium on which the two-dimensional code is printed may be attached, etc.), and a customer who visits the store may scan (read) the two-dimensional code with the customer terminal device 50, thereby allowing the customer terminal device 50 to acquire the store identification information. When a customer who visits the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer who visits the store scans the two-dimensional code with the customer terminal device 50, the shopping application may be started, and a screen informing the customer that the transaction management device 60 is currently connected may be displayed as a start-up screen.

[0061] 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, location information may be obtained and a screen may be displayed as a start-up 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 one cannot be identified, a selection screen may be displayed to allow the customer to select. Alternatively, a mode may be switched to forcefully obtain a two-dimensional code. Also, for example, the customer terminal device 50 may acquire store-specific information by communicating with a beacon installed at a predetermined location in the store.

[0062] 10(A) shows an example of a start-up screen of a 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 wishes to start registering a product for shopping, the customer operates a transaction start button BT10 arranged on the start-up screen. In response to the operation of the transaction start instruction button BT10, the customer terminal device 50 transmits a transaction start request including the acquired store specific information and customer identification information to the transaction management device 60. The transaction start request may be transmitted in response to the customer's operation on the customer terminal device 50 as described above, or may be transmitted in response to the acquisition of store specific information without receiving any particular operation. Regarding the 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 a shopping application on the customer terminal device 50) may be stored in the customer information of the transaction management device 60, but may also be stored in the memory of the customer terminal device 50 in addition to the transaction management device 60. When a store is identified (when the product registration initial screen described below is acquired), the store name, the services being offered (flyer information distributed on that day), and available coupon information may be displayed on a screen (the product registration initial screen or a screen other than the product registration initial screen). The service and coupon information may be acquired from the transaction management device 60 as screen information, for example.

[0063] 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 to the store-specific information, the destination information may also be converted into a two-dimensional code, 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-specific information.

[0064] 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 in which the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are stored, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, product information (registered product information, pending product information), etc.) is not stored.

[0065] As described above, the transaction management device 60 stores store information such as that shown in Figure 8 (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 store identification information converted into a two-dimensional code, the transaction management device 60 need only acquire it as is.

[0066] 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, and further 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. Also, 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. Also, 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.

[0067] Step S3: The transaction management device 60, which has generated the cart information for the transaction, generates product registration initial screen information (screen information of 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 the cart identification information.

[0068] 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, for example, the product registration initial screen as shown in FIG. 10(B).

[0069] Step S5: The customer terminal device 50 scans the barcode attached to the product by the customer's operation, and reads the product code. In the figure, it is assumed that the barcode has been successfully scanned. Steps S5 to S9 are repeatedly executed every time the barcode attached to the product is scanned.

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

[0071] Step S6: The transaction management device 60 receives the product registration information (cart identification information and product code) from the customer terminal device 50 and identifies the cart information of the transaction from the cart identification information included in the received product registration information.

[0072] Step S7: The transaction management device 60 updates the product data in the identified cart information. Specifically, if the received product registration information contains a product code for the Nth item, 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.

[0073] 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 an 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 a list item of the currently registered product has been added to the registered product list, as shown in Fig. 10(C), for example, and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0074] The product registration screen (product registration update screen) shown in FIG. 10(C) is displayed on the customer terminal device 50 after "XX bread" is 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 FIG. 10(C), and transmits the generated product registration update screen information to the customer terminal device 50 together with the cart identification information.

[0075] In response to the registration of one product, a registered product display screen WD1 may be displayed to display the currently registered product, as shown in Fig. 11(A), for example. In addition, in the registered product display screen WD1 shown in the same figure, in response to the target 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 would like to eat in. In this case, the price of the target product is calculated so that the consumption tax rate for the target product is different when the "Yes" button BT1 is operated and when the "No" button BT2 is operated.

[0076] 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. 10(C). As described above, the product registration screen (product registration update screen) shown in Fig. 10(C) is displayed on the customer terminal device 50 after "XX bread" is registered as the third product item.

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

[0078] Step S11: The customer terminal device 50 that has accepted the settlement transition instruction operation generates a two-dimensional code. That is, the customer terminal device 50 converts information required to execute the settlement process for the items purchased by the customer terminal device 50 (e.g., cart identification information) 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. 10(D) is displayed on the display unit.

[0079] 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 directed by the customer within the recognition range of the customer-side scanner unit 406.

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

[0081] Step S14: The transaction management device 60, which has received the cart identification information and the sub-calculation output request information from the customer terminal device 50, identifies the cart information of the transaction from the cart identification information.

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

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

[0084] Step S17: The settlement device 40, which has received the cart identification information and the subtotal information from the transaction management device 60, displays the subtotal amount on the customer side display unit 405, for example, as shown in FIG. 11(B).

[0085] Step S18: The settlement device 40, which has displayed the subtotal on the customer 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. In addition, when the settlement is completed, the settlement device 40 sends settlement completion information together with the cart information to the transaction management device 60, and the transaction management device 60 stores the transaction end date and time (settlement date and time) for that cart.

[0086] 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 after moving to another store) other than those scanned in the store (the store when the customer visited the store 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 visits the store (or when the product registration initial screen is displayed). If the two match (or approximately match), the customer terminal device 50 may permit the transmission of the product code of the product to the transaction management device 60, and if they do not match (or approximately match), the customer terminal device 50 may prohibit the transmission of the product code of the product to the transaction management device 60. This makes it possible to prevent inappropriate product registration (for example, registering a product to a cart created in another store, etc.).

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

[0088] The settlement device 40 reads the two-dimensional code displayed on the display of the customer terminal device 50 and then requests the transaction management device 60 to calculate the subtotal amount (S13), but may not request calculation of the subtotal amount for products other than the product scanned in the store (for example, products scanned in other stores). For example, the settlement device 40 refers to the store identification information of the store (it may store and refer to the store identification information of the store in its own settlement device 40, or may refer to the 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 permit the request to calculate the subtotal amount if the store identification information included in the cart identification information includes the store identification information of the store, and may prohibit the request to calculate the subtotal amount if the store identification information does not include the store identification information of the store. This makes it possible to prevent inappropriate payments (for example, payment for products registered at other stores, etc.).

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

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

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

[0092] Furthermore, during checkout processing, the transaction management device 60 may determine whether or not the product information included in the cart information includes any reserved products, and if so, may request the checkout device 40 to provide instructions to correct the reserved products. Upon receiving a request to provide instructions to correct the reserved products, the checkout device 40 displays a message to notify the user that there are reserved products, as shown in Fig. 11(C). Upon confirming the message, the store clerk may perform an operation to release (correct) the reserved products, such as entering a price corresponding to the reserved products or canceling the reserved products.

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

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

[0095] [Restrictions on use of shopping applications] Generally, anyone can use a shopping application without any particular restrictions, provided that the application is downloaded from a download site and installed on the customer terminal device 50 .

[0096] However, for example, due to circumstances of a store, it may be desirable to restrict users who can use the shopping application to a certain range. As an example, when a store introduces the shopping system of this embodiment on a trial basis, it is not desirable for any general customer to be able to use the shopping application. In this case, the store operator would like to limit the use of the shopping application to only store clerks (employees) and some members when introducing the shopping system on a trial basis. Therefore, in this embodiment, the users who can use the shopping application can be restricted to a portion of users determined by the store, as described below. In the following description, an example will be given in which users who can use a shopping application for a specific store are restricted to store clerks and some members.

[0097] For example, a download site for a shopping application according to this embodiment provides a downloadable shopping application with a usage restriction function.

[0098] The shopping application of this embodiment, which has a usage restriction function, can be used as is without removing the restriction in a store that has no particular restrictions on users who can use the application. In contrast, in a specific store (restricted store) where restrictions are set for users who can use the application, the shopping application of this embodiment can be used at that store by the user performing an operation to remove the restrictions. Note that the operation to remove the restrictions only needs to be performed once at the first launch for a store where restrictions are set for one available user. From the second time onwards, the user can launch the shopping application and use it for shopping without performing the operation to remove the restrictions.

[0099] A store operator who wishes to introduce a shopping application while restricting the users who can use it selects users from among store clerks and members who will use the shopping application. The store operator requests the selected users to install the shopping application on their respective customer terminal devices 50. The store operator then requests the users to use the shopping application to shop at the store. The store operator also notifies each user of a usage authorization code to be entered into the shopping application by a predetermined means. The usage authorization code may be notified by email, for example. Furthermore, the usage authorization code may be notified to specific members via a member application installed on the customer terminal device 50. The usage permission code to be notified may be, for example, a character string of alphanumeric characters or the like having a predetermined number of digits, or may be a two-dimensional code (which may be a barcode) of such a usage permission code.

[0100] A user who has received a request to use the shopping application as described above installs the shopping application in his / her own customer terminal device 50. The user goes to the store carrying the customer terminal device 50 on which the shopping application has been installed. Once the user enters the store, he / she operates the customer terminal device 50 to start up the shopping application.

[0101] When a user has not registered a usage authorization code, the shopping application is prohibited from processing in response to product registration at a specific store (restricted store) associated with the usage authorization code. When a user inputs a usage authorization code, the usage restriction on the shopping application is lifted, and the shopping application can thereafter execute processing in response to product registration at the restricted store.

[0102] The following describes an example of the operation procedure for removing restrictions when a user starts using a shopping application for the first time at a restricted store. A user goes to a restricted store carrying a customer terminal device 50 on which a shopping application is installed. A usage permission code has not yet been registered in the shopping application installed on the customer terminal device 50. When a shopping application for which a usage permission code is not registered is launched at a location corresponding to a restricted store, the customer terminal device 50 first displays, for example, the startup screen of Fig. 10(A). In addition, the customer terminal device 50 on which the shopping application is launched acquires store-specific information by a process similar to that of step S1 of Fig. 9. The user operates the transaction start button BT10 arranged on the displayed startup screen.

[0103] In this case, the store indicated by the store identification information acquired by the customer terminal device 50 is a restricted store. In other words, the location where the launched shopping application will be used is a restricted store. In this case, the customer terminal device 50 displays the code input screen shown in FIG. 12(A) instead of the product registration screen in FIG. 10(B).

[0104] When the code input screen is displayed, the code scan function of the customer terminal device 50 is enabled. If the notified usage permission code is a two-dimensional code, the user causes the customer terminal device 50 to read the two-dimensional code as the usage permission code using the code scan function. In response to having the customer terminal device 50 read the two-dimensional code, the usage permission code is displayed in the input box BX30 on the code input screen as a character string indicated by the read two-dimensional code. Alternatively, if the notified use authorization code is a character string of alphanumeric characters of a predetermined number of digits, the user inputs the character string of the use authorization code into the input box BX30 by performing a character input operation. When performing a character input operation, for example, a keyboard capable of inputting at least alphanumeric characters may be displayed on the code input screen. The user can input the character string of the use authorization code into the input box BX30 by operating the displayed keyboard.

[0105] After inputting the usage permission code by reading the two-dimensional code or inputting the character string as described above, the user operates the registration button BT31 on the code input screen to register the input usage permission code. To cancel the input of the usage authorization code, the user operates the cancel button BT32 on the code input screen. When the cancel button BT32 is operated, the screen may be returned to the start-up screen of FIG. 10(A), for example.

[0106] In response to the operation of the registration button BT31, the customer terminal device 50 displays a registration confirmation screen WD30 as shown in Fig. 12(B) . The registration confirmation screen WD30 in the figure shows an example in the form of a pop-up window that is displayed superimposed on the code input screen. The registration confirmation screen WD30 displays the character string of the inputted usage permission code, and also displays a message for confirming with the user whether or not to register the usage permission code. In addition, the registration confirmation screen WD30 has a registration button BT33 and a registration cancellation button BT34 arranged thereon.

[0107] Moreover, in the code input screen displayed in the background of the registration confirmation screen WD30, a delete button BT35 is arranged in place of the cancel button BT32. The delete button BT35 is a button that is operated when deleting the usage permission code entered in the input box BX30 of the code input screen.

[0108] If the user wishes to register the inputted usage permission code, he or she operates the registration button BT32. In response to the operation of the registration button BT33, the inputted usage permission code is registered. When the usage permission code is registered, the customer terminal device 50, for example, transitions to displaying a product registration screen, for example, as shown in Fig. 10(A). In other words, the usage restriction of the shopping application is lifted, and processing according to the product registration becomes possible thereafter. This allows the user to shop at restricted stores using the shopping application.

[0109] The screen on which the authorization code is entered is not limited to the code entry screen described above. For example, the authorization code may be entered on a menu screen on which various information is presented and settings are made.

[0110] The transaction management device 60 stores a usage permission information table. The usage permission information table is a table that stores usage permission information that associates a usage permission code with a corresponding restricted store. FIG. 13A shows an example of the usage permission information table. For example, each record in the usage permission information table in the figure is usage permission information corresponding to one usage permission code. In the usage permission information of the record in the first row, the usage permission code "11111111" is associated with the store identification information (store identification code) "S000001" and the user type "store clerk." The store identification information in the usage permission information indicates a store that is subject to support restrictions. Specifically, the first record indicates that the use authorization code "11111111" is entered to enable use at the restricted store indicated by the store identification information "S000001." The first record also indicates that the user to whom the corresponding use authorization code "11111111" is assigned is a store clerk. In addition, in the usage permission information of the record in the second row in the usage permission information table in the same figure, the usage permission code "22222222" is associated with the store identification information "S000001" and the user type "member". The record on the second line indicates that entering the authorization code "22222222" enables use at the restricted store indicated by the store identification information "S000001." The record on the first line indicates that the user to whom the authorization code "22222222" is assigned is a member. In other words, at the restricted store indicated by the store identification information "S000001", a shopping application for which the store clerk has entered the permission code "11111111" and a shopping application for which the member has entered the permission code "22222222" are available for use.

[0111] Fig. 13(B) shows another example of the usage permission information table. One piece of usage permission information in the usage permission information table in this figure has a structure in which a usage permission code and store identification information are associated with each clerk number (clerk identification information) or member number (member identification information). The clerk number is a number that uniquely identifies a clerk. The member number is a number that uniquely identifies a member. In other words, the usage permission information in the usage permission information table in the figure corresponds to a case where a unique usage permission code is assigned to each store clerk or member. In addition, the usage permission information in the figure also indicates the stores that are subject to the usage restriction by the store identification information.

[0112] 13(A) and 13(B), a plurality of pieces of store identification information may be associated with one usage permission code. In other words, there may be a plurality of restricted stores at which the shopping application can be used in response to input of the usage permission code.

[0113] The following explanation of the process performed by the transaction management device 60 to remove usage restrictions will be given by taking as an example a case in which the usage permission information table has the structure shown in FIG. 13(A). Upon receiving the restriction lift request, the transaction management device 60 searches the usage permission information in the usage permission information table for usage permission information that stores the same combination of usage permission code and store identification information as that included in the received restriction lift request. If the permission information is found, the permission code included in the restriction removal request is correct, and the store where the user is attempting to use the shopping application is a restricted store corresponding to the permission code. In this case, the transaction management device 60 transmits a restriction removal response to the customer terminal device 50 indicating permission to remove the usage restriction on the shopping application.

[0114] On the other hand, when the permission information is not found, the permission code included in the restriction release request is not stored in any of the permission information in the permission information table. In this case, the transaction management device 60 transmits a restriction release response to the customer terminal device 50 indicating that the restriction on the shopping application is not to be released because the permission code entered by the user is invalid. Another case where a corresponding record is not found is when the usage permission code included in the restriction release request is stored in a certain usage permission information in the usage permission information table, but the store identification information included in the usage permission information is different from that included in the received restriction release request. In this case, the transaction management device 60 transmits a restriction release response to the customer terminal device 50 indicating that the release of the usage restriction is prohibited, because the store the user is visiting is a restricted store that does not correspond to the usage permission code entered this time.

[0115] When the customer terminal device 50 receives the restriction release response indicating permission to release the usage restriction, the customer terminal device 50 releases the restriction on the product registration function of the shopping application. This enables the customer terminal device 50 to register products in response to user operations. In other words, the user can thereafter shop at the store he or she is currently in by using the customer terminal device 50 on which the shopping application is running.

[0116] On the other hand, when the customer terminal device 50 receives a restriction lift response indicating that the lifting of the usage restriction is prohibited, the customer terminal device 50 does not lift the restriction on the product registration function of the shopping application. In this case, the customer terminal device 50 does not register products in response to the user's operation. Therefore, the user cannot use the shopping application to shop at the store he or she is currently in.

[0117] When the customer terminal device 50 lifts the restrictions on the product registration function in response to receiving a restriction lift response indicating permission to lift the usage restrictions, it may be configured to notify the user that product registration is now possible by displaying a message or the like.

[0118] Furthermore, if the customer terminal device 50 does not lift the restriction on the product registration function in response to receiving a restriction lift response indicating prohibition of lifting of the usage restriction, the customer terminal device 50 may notify the user by displaying a notice that the shopping application corresponding to the product registration is not available. At this time, the customer terminal device 50 may also notify the user of the reason why the shopping application corresponding to the product registration is not available. The reason why the shopping application for product registration is not available may be that the entered usage permission code is incorrect (reason 1), or that the entered usage permission code does not correspond to the restricted store currently entered (reason 2).

[0119] [Example of processing procedure] An example of a process procedure executed by customer terminal device 50 and transaction management device 60 in relation to lifting restrictions on the use of a shopping application will be described with reference to the flowchart of FIG.

[0120] First, an example of a processing procedure executed by the customer terminal device 50 will be described. Step S101: A user enters a store to shop using a customer terminal device 50 on which a shopping application is installed. In the store, the user performs an operation on the customer terminal device 50 to start the shopping application. The customer terminal device 50 starts the shopping application in response to the operation.

[0121] Step S102: The customer terminal device 50 on which the shopping application has been started acquires store-specific information. The process of step S102 corresponds to the process of acquiring store-specific information in step S1 of FIG.

[0122] Step S103: The customer terminal device 50 sends a store type inquiry to the transaction management device 60. The store type inquiry is a command inquiring whether the store indicated by the store identification information acquired in step S102 is a restricted store. In other words, the store type inquiry inquires whether the store the user has entered this time is a restricted store. The store type inquiry includes the store identification information acquired in step S102.

[0123] Step S104: In response to the store type inquiry sent in step S103, the transaction management device 60 sends a store type response to the customer terminal device 50. The store type response indicates whether or not the store indicated by the store identification information acquired in step S102 is a restricted store. When the customer terminal device 50 receives the store type response, it determines whether or not the received store type response indicates that the store is a restricted store.

[0124] Step S105: If the usage permission code has been registered, the customer terminal device 50 stores the usage permission code as one of the application data used by, for example, a shopping application. If the received store type response indicates that the store is a restricted store in step S104, the customer terminal device 50 determines whether the usage permission code for the shopping application has been registered.

[0125] Step S106: If the usage permission code has not been registered and the user operates the transaction start button BT10 on the start-up screen, the customer terminal device 50 displays the code input screen of FIG. 12(A). With the code input screen displayed, the user performs the operation of inputting the usage authorization code as described above. The customer terminal device 50 determines whether or not the usage permission code has been input. The determination of whether or not the usage permission code has been input may be performed, for example, by determining whether or not an operation has been performed on the registration button BT32 on the registration confirmation screen WD30. If it is determined that the authorization code has not been input, the process in the figure may be terminated. In this case, the usage restriction on the shopping application is not lifted.

[0126] Step S107: If it is determined in step S106 that the usage permission code has been input, the customer terminal device 50 stores the input usage permission code in the storage unit 502 as application data of the shopping application.

[0127] After the authorization code is stored in step S107 in this manner, when the shopping application is launched, it is determined in step S105 that the authorization code has been registered, and steps S106 and S107 can be skipped and the process proceeds to step S108. In other words, the user needs to register the authorization code in the shopping application only once, the first time.

[0128] Step S108: If it is determined in step S105 that the usage authorization code has already been registered, or after the processing of step S107, the customer terminal device 50 transmits a restriction release request to the transaction management device 60. The restriction release request includes the registered usage authorization code and the store-specific information acquired in step S102.

[0129] Step S109: In response to the transmission of the restriction lift request in step S108, the transaction management device 60 transmits a restriction lift response indicating whether the usage restriction is permitted or prohibited to be lifted. The customer terminal device 50 determines whether the received restriction lift response indicates that the restriction is permitted or not. If the received restriction lift response indicates that lifting is prohibited, then, for example, as described above, a notification is given that use of the shopping application for product registration is not possible, and the processing in FIG.

[0130] Step S110: If it is determined in step S109 that the restriction release response indicates permission to release, the customer terminal device 50 releases the usage restriction on the shopping application. In response to the use restriction being released, the customer terminal device 50 displays a product registration screen (FIG. 12(B)) on the display unit 504. Thereafter, the user can use the shopping application to shop (register products) at the store in which the user is currently located.

[0131] Next, an example of a processing procedure executed by the transaction management device 60 will be described. Step S201: The transaction management device 60 determines whether or not a store type inquiry transmitted from the customer terminal device 50 in step S103 has been received.

[0132] Step S202: When the store type inquiry is received, the transaction management device 60 performs a store type determination. That is, the transaction management device 60 determines whether the store indicated by the store identification information included in the received store type inquiry is a restricted store or a non-restricted store. The transaction management device 60 may determine whether the store is a restricted store or a non-restricted store based on whether the store identification information included in the received store type inquiry is included in any of the usage permission information in the usage permission information table.

[0133] Step S203: The transaction management device 60 transmits a store type response indicating the result of the determination in step S202.

[0134] Step S204: If no store type inquiry is received in step S201, or after the processing of step S203, the transaction management device 60 determines whether or not a restriction removal request sent from the customer terminal device 50 in step S108 is received. If it is determined that the restriction removal request has not been received, the process returns to step S201.

[0135] Step S205: In response to receiving the restriction lifting request, the transaction management device 60 determines whether or not to lift the usage restriction (permit or prohibit). To this end, the transaction management device 60 searches the usage permission information table for usage permission information that stores the same combination of usage permission code and store identification information as included in the received restriction lifting request. If the corresponding usage permission information is found, transaction management device 60 determines that the lifting of the usage restriction is permitted. If the corresponding usage permission information is not found, transaction management device 60 determines whether or not the lifting of the usage restriction is permitted by determining that the lifting of the usage restriction is prohibited.

[0136] Step S206: The transaction management device 60 transmits a restriction release response indicating whether the usage restriction is permitted to be released or prohibited from being released, depending on the result of the determination in step S205. Here, when transmitting the restriction release response indicating the prohibition of release, the transaction management device 60 may include information indicating whether the reason for the prohibition of release is the above-mentioned reason 1 or 2. After the process of step S206, the process returns to step S201.

[0137] By executing such processing, the usage restriction on the shopping application installed in the customer terminal device 50 is properly lifted. As a result, in this embodiment, it is possible to allow only limited users, such as store clerks and members who have been notified of the usage authorization code, to use the shopping application.

[0138] <Second embodiment> Next, a second embodiment will be described. In this embodiment, a store that uses the shopping application has installed a member application. The member application is an application that provides members with services such as coupons and sale information. Members can use the member application by installing the member application on their own customer terminal device 50 and registering as a member (user registration). Furthermore, in this embodiment, the member application and the shopping application are linked together as follows. For example, a store manager may want to offer a special service to customers who are registered as members, allowing only members to shop using a shopping application. In such a case, by linking the member application with the shopping application, it is possible to allow only members to use the shopping application, as follows:

[0139] In this case, a user who is a member of the store installs a member application and a shopping application on his or her customer terminal device 50. The store management server 90 manages member information for each registered member. The member information includes a member number. The member number is identification information that uniquely identifies a member. The store management server 90 issues a member number when a member is registered.

[0140] In this embodiment, a user who is a member can declare use of the shopping application by performing a predetermined operation on the member application. When the operation of declaring use of the shopping application is performed on the member application, a usage permission code is issued to the user, and the issued usage permission code is notified to the user's member application. The notified usage permission code may be written down by the user, or may be saved as an image using a screenshot function or the like. Alternatively, the usage permission code may be notified to the user by email. The usage permission code to be notified may be, for example, a character string of alphanumeric characters or the like having a predetermined number of digits, or may be a two-dimensional code (which may be a barcode) of such a usage permission code.

[0141] When a user enters a store of which he or she is a member, the user operates the customer terminal device 50 to start up a shopping application. In this case, the customer terminal device 50 and the transaction management device 60 execute a process similar to that shown in Fig. 14, for example, to release the usage restrictions on the shopping application in response to the user's input of the usage authorization code. This allows the user to shop using the shopping application at the store of which he or she is a member.

[0142] Furthermore, in this embodiment, by issuing a usage authorization code by operating the member application as described above, the membership number of the user managed by the store management server 90 is associated with the usage authorization code of the shopping application managed by the transaction management device 60. In other words, in the shopping system of this embodiment, the membership number can be associated with the user of the shopping application and managed. Note that the information associating the membership number with the usage authorization code may be stored by either the store management server 90 or the transaction management device 60, or may be stored synchronized between the store management server 90 and the transaction management device 60.

[0143] This makes it possible to apply coupons provided by a member application to shopping using a shopping application, for example. To this end, the transaction management device 60 obtains from the store management server 90 information on coupons that can be used by members who are users of the shopping application.

[0144] For example, when product registration information for a product registered in a shopping application is sent to the transaction management device 60, the transaction management device 60 requests from the store management server 90 information on coupons that can be used by the member with the membership number included in the received product registration information. When the transaction management device 60 receives coupon information from the store management server 90, for example, product registration information of a product corresponding to a coupon that has been declared for use by a user in advance is received from the customer terminal device 50, the transaction management device 60 applies the coupon, performs processing such as discounting, and stores the corresponding product data in the cart information. When the transaction management device 60 receives product registration information of a product corresponding to a coupon that has not been declared for use from the customer terminal device 50, the transaction management device 60 may display an operation screen on the customer terminal device 50 that allows the user to select whether or not to use the coupon. When the user selects to use the coupon, the transaction management device 60 may apply the coupon, performs processing such as discounting, and stores the corresponding product data in the cart information.

[0145] Furthermore, by associating the membership number with the usage authorization code, for example, the store management server 90 can obtain the transaction records of members who have made purchases using the shopping application from the transaction management device 60. This allows, for example, the store manager to perform various analyses of the shopping records using the shopping application, such as trends in purchased products, average customer spending, number of purchases per customer, payment amount, frequency of use of the shopping application by each customer, and coupon usage status when shopping using the shopping application.

[0146] In this embodiment, the membership number may be used as the usage authorization code.

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

[0148] [First Modification] In the above embodiment, the user is required to input the usage permission code notified in advance to remove the usage restriction of the shopping application. In contrast, in this modified example, the usage restriction of the shopping application is removed as follows, under the operation in which a store clerk at the service counter of the store subject to the restriction serves the user.

[0149] A user goes to a restricted store carrying a customer terminal device 50 installed with a shopping application for which a usage authorization code has not yet been registered. When the user goes to the restricted store, the user operates the customer terminal device 50 to start the shopping application. In response to the shopping application being started, the customer terminal device 50 displays the start-up screen of FIG. 10(A) on the display unit 504. The user operates the transaction start instruction button BT10 arranged on the start-up screen.

[0150] In this case, the shopping application is started and the customer terminal device 50 executes the process of steps S101 to S106 in Fig. 14, thereby determining that the store corresponding to the currently acquired store identification information is a restricted store. When the transaction start instruction button BT10 is operated in this state where it has been determined that the store is a restricted store, the customer terminal device 50 displays a usage permission guide screen.

[0151] Fig. 12(C) shows an example of the usage permission guide screen. In the usage permission guide screen in the same figure, since the usage permission registration for enabling the shopping application to be used in the restricted store that the user has entered this time has not been performed, a message is displayed guiding the user to go to the service counter to register the usage permission. In addition, the usage permission guide screen in the same figure has a confirmation button BT30. When the user operates the confirmation button BT30, the display transitions to a code input screen similar to that of Fig. 12(A), for example.

[0152] The user goes to the service counter and asks the clerk at the service counter for a usage authorization code. Here, we will take as an example a case in which the users who are permitted to use the shopping application at the restricted store are a portion of members selected in advance from all members and a portion of store clerks selected in advance from all store clerks.

[0153] The store clerk who receives the request to provide the usage authorization code, for example, asks the user to present a membership card or a store clerk ID. The store clerk checks whether the user is a member or a store clerk who is authorized to use the shopping application by comparing the member number on the presented membership card or the store clerk number on the store clerk ID with a list of member numbers and store clerk numbers authorized to use the shopping application.

[0154] When the store clerk confirms that the user is authorized to use the shopping application (a member or a store clerk), the store clerk provides the user with a usage authorization code. As a mode of providing the usage authorization code, for example, the store clerk may present a panel, card, or the like on which a two-dimensional code (or a barcode) as the usage authorization code is printed so that the user can scan it with the customer terminal device 50. Alternatively, a terminal installed at the service counter may display the two-dimensional code as the usage authorization code so that the user can scan it with the customer terminal device 50. The user scans the presented two-dimensional code as the usage permission code with the customer terminal device 50. This inputs the usage permission code into the customer terminal device 50, and alphanumeric characters of a predetermined number of digits are displayed as the usage permission code in the input box BX30 on the code input screen. The store clerk may also present alphanumeric characters of a predetermined number of digits as the usage permission code. In this case, the user may input alphanumeric characters of a predetermined number of digits as the usage permission code into the input box BX30 by entering numbers.

[0155] In addition, when a product code, for example, is scanned while the code input screen is displayed, the customer terminal device 50 may be configured to notify an error indicating that the entered code is not an authorization code. As a result, even if a user, for example, thinks that he or she can register the product as is and causes the product code to be read, the error notification as described above will make the user aware that he or she must enter the usage authorization code.

[0156] After inputting the usage permission code as described above, the user operates the registration button BT31. In response to the operation of the registration button BT31, the customer terminal device 50 displays a registration confirmation screen WD30 as shown in FIG. 12(B). The user operates the registration button BT32 arranged on the registration confirmation screen WD30 to confirm the registration of the input usage permission code. This removes the usage restriction on the shopping application at the restricted store in which the user is currently located. Thereafter, the user becomes able to use the shopping application to shop at the restricted store.

[0157] [Second modified example] When releasing the usage restriction of the shopping application, in addition to the usage authorization code, the user may be required to input a membership number or a store clerk number. In the following description, when there is no particular distinction between the membership number and the store clerk number, they are referred to as user identification information.

[0158] In this case, the code input screen displayed on the customer terminal device 50 is configured to accept input of the usage authorization code and user identification information (member number or store clerk number). In this case, the usage authorization code may be associated so as to be unique for each user identification information of a member or store clerk who is permitted to use the shopping application at the restricted store (for example, the user identification information in FIG. 13(B)), or may be common to all user identification information. In addition, in this case, on the code input screen, an input box corresponding to input of user identification information may be arranged in addition to the input box BX30 corresponding to input of the usage authorization code.

[0159] In this case, in response to a request from the customer terminal device 50 to lift the usage restriction, the transaction management device 60 determines whether or not to lift the usage restriction based on whether the combination of the usage authorization code and user identification information entered at the customer terminal device 50 is stored in the usage authorization information.

[0160] In addition, in this modification, when removing restrictions on the use of the shopping application, a usage permission code and user identification information are input, thereby identifying users who can use the shopping application. This allows, for example, the transaction management device 60 and the store management server 90 to accumulate transaction records corresponding to users who have made purchases using a shopping application at a restricted store. For example, the restricted store can analyze the accumulated transaction records and use them in consideration of the future general introduction of the shopping application. In particular, if the user is a member, it can also analyze the relationship between the rank given to the member and the usage tendency of the shopping application.

[0161] In this modified example, a usage authorization code and user identification information (member number, store clerk number) are input when lifting the usage restrictions on the shopping application, and the transaction management device 60 may use only the usage authorization code when determining whether or not to lift the usage restrictions. In this case, the user identification information input to the customer terminal device 50 when lifting the usage restrictions may be used by the transaction management device 60, etc., as information for identifying users who are allowed to shop using the shopping application.

[0162] [Third Modification] In addition, for a shopping application, if a certain period of time has passed without the shopping application being used for product registration after the use authorization code has been input and the use restriction has been released, the use authorization code may be invalidated. In other words, even if the use authorization code is input, if the shopping application is not used for a certain period of time or more thereafter, the use restriction is applied again. This makes it possible to avoid a state in which the use restriction of a shopping application that is no longer used by the user remains released. Such control may be performed, for example, by the customer terminal device 50 in which a shopping application is installed, using its own clock function. In this case, the customer terminal device 50 may erase the usage authorization code that it has stored. Alternatively, the transaction management device 60 may invalidate the corresponding usage permission code stored in the usage permission information table when a certain period of time has passed since the date and time when the last transaction was made using the shopping application. In this case, when the user performs an operation to release the usage restriction of the shopping application again, the transaction management device 60 may reissue a new usage permission code.

[0163] [Fourth Modification] In addition, some of the functions of the customer terminal device 50 in this embodiment may be executed by a higher-level device such as the transaction management device 60 or the store management server 90. As an example, the usage authorization code input by a user's operation may be stored by the transaction management device 60 or the like instead of being stored by the customer terminal device 50. In this case, for example, the determination of whether the usage authorization code has been registered in step S105 of FIG. 14 may be performed by the transaction management device 60 in response to an inquiry from the customer terminal device 50, and the determination result may be transmitted to the customer terminal device 50.

[0164] <Overview of the embodiment> [Technical field] The present invention relates to a program and a terminal device. [Background technology] 2. Description of the Related Art There is known a self-registration system that allows a customer to register products using a smartphone or the like when shopping in a store (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2016-219034 A [Summary of the Invention] [Problem to be solved by the invention] The registration of products by customers as described above is performed using a specific application installed on a terminal device such as a smartphone owned by the customer. Depending on circumstances of the store, it may be necessary to limit the users who can use the specific application to a certain range. The present invention has been made in view of the above circumstances, and has an object to make it possible to limit the users who can use applications on a terminal device used for shopping in a store to a certain range.

[0165] [Means for solving the problem] (1) As described above, one aspect of this embodiment is a program for causing a computer to function as control means that includes an identification means for identifying a store based on store-specific information, a determination means for determining whether or not permission to use a product registration application (e.g., a shopping application) installed on a mobile terminal (e.g., customer terminal device 50) is required depending on the store identified by the identification means, and, if the determination means determines that permission to use the application is required, controls the display of a usage permission processing screen (e.g., a code input guide screen, a code input screen, etc.) corresponding to the usage permission processing for allowing use of the application on the mobile terminal, and, if the determination means determines that permission to use the application is not required, controls the display of a product registration screen corresponding to product registration.

[0166] According to the above configuration, when the shopping application installed on the customer terminal device 50 is used in a store that does not require usage permission, for example, a product registration screen is displayed as is, allowing the user to register products. In contrast, when the shopping application is used in a store that requires usage permission (a restricted store), a code input guide screen, a code input screen, etc. is displayed in response to the input of a usage permission code required for usage permission (removal of usage restrictions). In a restricted store that requires the removal of usage restrictions, it is possible to prevent users who cannot enter the usage permission code from using the shopping application. This makes it possible to restrict users who can use the shopping application on a mobile terminal used for shopping at the store to a certain range.

[0167] (2) One aspect of this embodiment is the program described in (1), wherein the control means displays, as the usage permission processing screen, an input screen for inputting usage permission identification information for lifting usage restrictions, and notifies an error if identification information other than the usage permission identification information is input into the input screen.

[0168] According to the above configuration, even if a user attempts to register a product by reading a product code while the code input screen is displayed, an error is notified, and the user can understand that the product cannot be registered.

[0169] (3) One aspect of this embodiment is the program according to (2), in which the input screen is used to input user identification information (eg, a store clerk number or a membership number) together with the usage permission identification information.

[0170] According to the above configuration, when inputting a usage permission code for obtaining permission to use the restricted store, a store clerk number or a member number is input, which makes it possible to link and manage the store clerk or member as a user who is permitted to use the shopping application.

[0171] (4) One aspect of this embodiment is a program described in any one of (1) to (3), wherein the control means displays the usage permission processing screen that provides guidance on getting assistance from a store clerk to have usage of the application permitted on the mobile terminal.

[0172] In some cases, the user does not input the authorization code by himself, but instead has a store clerk at a service counter do so (i.e., the store clerk assists the user in inputting the authorization code). According to the above configuration, in order to accommodate such an operation, for example, on the code input guidance screen, it is possible to guide the user to go to the service counter to have a store clerk input the authorization code.

[0173] (5) One aspect of this embodiment is a program described in any one of (1) to (4), wherein the determination means determines whether or not permission to use is required based on a response to a query about whether permission to use is required from a specified external device (e.g., a transaction status monitoring device 80, etc.).

[0174] For example, the customer terminal device 50 may store a list of store identification information of restricted stores that require permission to use the shopping application, and check the acquired store identification information against the list to determine whether or not permission to use the shopping application is required. However, with the above configuration, the customer terminal device 50 can determine whether or not permission to use the shopping application is required based on a response from the transaction status monitoring device 80 or the like to an inquiry that includes the acquired store identification information. In this case, the customer terminal device 50 does not need to store a list of store identification information.

[0175] Further, the following supplementary notes regarding this embodiment are disclosed below. (Supplementary Note 1) One aspect of this embodiment is a program for causing a computer to function as an identification information acquisition means (S201) for acquiring identification information for enabling use of the application, the identification information being identification information (usage authorization code) input into a mobile terminal (e.g., customer terminal device 50) on which an application used by a user to register a product is installed, and as a control means (S203) for controlling whether or not to execute a function of the application related to product registration depending on whether or not the identification information has been acquired by the identification information acquisition means.

[0176] According to the above configuration, among the customer terminal devices 50 in which a shopping application used by a user to register a product is installed, the execution of a function related to product registration can be permitted only for the shopping application installed on the mobile terminal into which the identification information was input. This makes it possible to limit the users who can use the shopping application of the customer terminal device 50 used for shopping at a store to a certain range.

[0177] (Appendix 2) One aspect of this embodiment is the program described in (Appendix 1), which causes the computer to function as a specific store information acquisition means (S201) that acquires store identification information that can uniquely identify a store, and the control means controls whether or not to execute a function related to product registration of the shopping application depending on whether or not the store indicated by the store identification information acquired by the store identification information acquisition means is an available store where the shopping application can be used (S201).

[0178] According to the above configuration, it is possible to limit users who can use the shopping application to a certain range, and also to limit the stores at which the shopping application can be used.

[0179] (Appendix 3) One aspect of this embodiment is the program described in (Appendix 2), in which the store identification information acquisition means acquires, as the store identification information, a store identification code entered into a customer terminal device 50 on which the application is installed (S1).

[0180] According to the above configuration, it is possible to realize control for limiting the stores in which the shopping application can be used, by using a store identification code that identifies the store.

[0181] (Appendix 4) One aspect of this embodiment is the program described in (Appendix 2), wherein the store identification information acquisition means acquires location information indicating a location of a mobile terminal on which the application is installed as the store identification information, and the control means controls whether or not to execute a function of the application related to product registration depending on whether or not the location indicated by the location information as the store identification information acquired by the store identification information acquisition means is the available store.

[0182] According to the above configuration, it is possible to realize control for limiting the stores in which the shopping application can be used, by utilizing location information corresponding to the location of the store.

[0183] (Appendix 5) One aspect of this embodiment is a program described in any one of (Appendix 1) to (Appendix 4), wherein the control means invalidates the identification information acquired by the identification information acquisition means when a certain period of time has elapsed without the application being used after the identification information has been acquired by the identification information acquisition means.

[0184] According to the above configuration, it is possible to prevent a state in which the usage restriction of a shopping application that is no longer being used by the user remains lifted.

[0185] (Appendix 6) One aspect of this embodiment is a program described in any one of (Appendix 1) to (Appendix 5), wherein the identification information is defined to be unique to a user (e.g., a store clerk or a member) who is authorized to use the application.

[0186] According to the above configuration, users who are allowed to register products using the shopping application can be set with a high degree of freedom on an individual basis.

[0187] (Appendix 7) One aspect of this embodiment is a terminal device installed with an application that a user uses to register products, the terminal device comprising: an identification information acquisition means that is input to the terminal device and acquires identification information for enabling use of the application; and a control means that controls whether or not to execute a function of the application related to product registration depending on whether or not the identification information has been acquired by the identification information acquisition means.

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

[0189] 10 Management device, 40 Settlement device, 50 Customer terminal device, 60 Transaction management device, 70 Credit card settlement server, 80 Transaction status monitoring device, 90 Store management server

Claims

1. A computer as a device capable of registering goods, a store identification means for identifying the store based on store identification information presented in the store and uniquely identifying the store; a determination means for transmitting a store type inquiry to a transaction management device inquiring as to whether a store identified by the store identification information is a use-restricted store, and determining whether the identified store is a use-restricted store in which use of an application capable of registering products is restricted based on a store type response transmitted by the transaction management device in response to receiving the store type inquiry, the store type response indicating a result of determining whether the identified store is a use-restricted store based on store type information indicating whether each store is a use-restricted store; a control means for controlling to display, when the determination means determines that the store is a use-restricted store, a use permission guide screen that guides a store clerk to assist in allowing the use of the application and an input screen for inputting use permission identification information for use permission in response to an operation on the use permission guide screen, as a use permission processing screen corresponding to the use permission processing for allowing the restriction on the use of the application, and, when the determination means determines that the store is not a use-restricted store, a product registration screen for the application is displayed A program to function as a

2. The input screen is used to input user identification information together with the usage authorization identification information. The program according to claim 1.

3. A system comprising a registration device capable of registering a commodity and a transaction management device, The registration device includes: a store identification means for identifying the store based on store identification information that is presented in the store and that uniquely identifies the store; a determination means for determining whether or not the specified store is a restricted store in which the use of an application capable of registering products is restricted, based on a store type response sent from the transaction management device in response to sending a store type inquiry to the transaction management device inquiring whether the store specified by the store specification information is a restricted store; a control means for controlling, when the determination means determines that the store is a use-restricted store, to display, as a use permission processing screen corresponding to the use permission processing for permitting the restriction on the use of the application, a use permission guide screen for guiding a store clerk to assist in permitting the use of the application and an input screen for inputting use permission identification information for use permission in response to an operation on the use permission guide screen, and, when the determination means determines that the store is not a use-restricted store, to control so that a product registration screen for the application is displayed; The transaction management device includes: a storage unit that stores store type information indicating whether or not a store is a use-restricted store for each store; a transmission means for transmitting to the registration device a store type response indicating a result of determining whether or not the specified store is a usage-restricted store based on the store type information in response to receiving the store type inquiry transmitted from the registration device. system.

4. In a system including a registration device capable of registering goods and a transaction management device, a first program for causing a first computer to function as the registration device, and a second program for causing a second computer to function as the transaction management device, The first program causes the first computer to a store identification means for identifying the store based on store identification information presented in the store and uniquely identifying the store; a determination means for determining whether or not the specified store is a restricted store in which the use of an application capable of registering products is restricted, based on a store type response transmitted from the transaction management device in response to a store type inquiry transmitted to the transaction management device inquiring whether or not the store specified by the store specification information is a restricted store; when the determination means determines that the store is a use-restricted store, the control means controls to display, as a use permission processing screen corresponding to the use permission processing for permitting the restriction on the use of the application, a use permission guide screen that guides a store clerk to assist in permitting the use of the application, and an input screen for inputting use permission identification information for use permission in response to an operation on the use permission guide screen, and when the determination means determines that the store is not a use-restricted store, the control means controls to display a product registration screen for the application, The second program causes the second computer to and functioning as a transmitting means for transmitting to the registration device a store type response indicating the result of determining whether or not the specified store is a use-restricted store based on storing store type information indicating whether or not the specified store is a use-restricted store in response to receiving a store type inquiry transmitted from the registration device. program.

Images