Management server, management system, control method, and storage medium

Abstract

To smoothly resume shopping even if an application of a portable terminal used for shopping is terminated before settlement for some reason. [Solution] The management server 2A has a receiving unit 81, a generating unit 82, a holding unit 83, and a transmitting unit 84. The receiving unit 81 receives product identification information indicating products the customer plans to purchase at a store the customer has entered from a mobile terminal 3A used by the customer. The generating unit 82 generates a purchase product list, which is a list of products the customer plans to purchase, based on the product identification information. If the holding unit 83 detects that an application that controls the transmission of product identification information and the display of the mobile terminal 3A has been terminated while the purchase product list is in an unpaid state, it holds the purchase product list until it detects that the application has been restarted. After the application has been restarted, the transmitting unit 84 transmits information about the purchase product list to the mobile terminal 3A.

Description

[Technical Field]

[0001] The present invention relates to updating member information. [Background technology]

[0002] A known product sales system for customers visiting a store to purchase products is one in which the customer uses a mobile terminal such as a smartphone to read the barcode of the product, register the product, and then settle the payment. For example, Patent Document 1 discloses a self-shopping system that includes a mobile terminal that acquires product information about the product to be purchased and sends settlement information including all the acquired product information to a management server, and a management server that generates and outputs sorted detailed information that lists the product names in descending order of price based on the product information included in the settlement information.

[0003] Furthermore, Patent Document 2 discloses a payment server device that, in the payment of digital content, etc., determines whether or not there is a malfunction in the update process of amount information stored in a storage medium based on historical information of amount information obtained from the storage medium that communicates contactlessly with a user terminal device. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-41354 [Patent Document 2] Japanese Patent Application Publication No. 2018-110024 Summary of the Invention [Problem to be solved by the invention]

[0005] In a system in which a customer uses a mobile terminal to read the barcode of a product, register the product, and then settle the payment, if the application controlling the mobile terminal used by the customer is forcibly terminated for some reason before the payment is made, the product must be registered again. Patent Documents 1 and 2 do not disclose anything about what to do when the application on the mobile terminal is terminated before the payment is made.

[0006] An object of the present invention is to provide a management server, management system, mobile terminal, control method, and storage medium that enable smooth resumption of shopping even if the application on the mobile terminal used for shopping is terminated before payment for some reason. [Means for solving the problem]

[0007] One aspect of the management server is a management server, a receiving means for receiving product identification information from a mobile terminal used by a customer; a generating means for generating a purchase item list, which is a list of items that the customer plans to purchase, based on the item identification information; a storage means for storing the purchase item list when the end of an application that controls the display of the purchase item list on the mobile terminal is detected while the purchase item list is in an unpaid state; a storage means for storing information relating to the mobile terminal that the application has been terminated in association with information relating to the mobile terminal, if the termination of the application is based on the mobile terminal having left the store where the customer has entered; It has.

[0008] One aspect of the control method is a control method executed by a management server, Receive product identification information from a mobile device used by a customer, generating a purchase item list, which is a list of items that the customer plans to purchase, based on the item identification information; When detecting that an application that controls the display of the purchase item list on the mobile terminal has been terminated while the purchase item list is in an unpaid state, the purchase item list is retained; If the termination of the application is based on the mobile terminal leaving the store where the customer entered, information that the mobile terminal has left the store is stored in association with information about the mobile terminal.

[0009] One aspect of the program is a receiving means for receiving product identification information from a mobile terminal used by a customer; a generating means for generating a purchase item list, which is a list of items that the customer plans to purchase, based on the item identification information; a storage means for storing the purchase item list when the end of an application that controls the display of the purchase item list on the mobile terminal is detected while the purchase item list is in an unpaid state; a storage means for storing information about the mobile terminal having left the store in association with information about the mobile terminal, if the termination of the application is based on the mobile terminal having left the store where the customer has entered; It is a program that makes a computer function as a [Effects of the Invention]

[0010] According to the present invention, even if the application on the mobile terminal used for shopping is terminated for some reason before payment is made, the customer can smoothly resume shopping. [Brief explanation of the drawings]

[0011] [Figure 1] 1 shows the configuration of a management system according to a first embodiment. [Figure 2] 1 shows a schematic configuration of a POS server. [Figure 3] 1 shows a schematic configuration of a management server. [Figure 4] 1 shows a schematic configuration of a mobile terminal. [Figure 5]1 shows a schematic configuration of a member server. [Figure 6] 1 shows the schematic configuration of an accounting machine. [Figure 7] 10 is a flowchart of a product purchasing process. [Figure 8] 10 is a flowchart of a store entry process. [Figure 9] 10 is a flowchart of a product selection process. [Figure 10] 10 is a display example of a purchase product list screen. [Figure 11] 10 is a flowchart of an accounting process. [Figure 12] 10 is a display example of a payment method selection screen. [Figure 13] 10 is an example of a display screen of an accounting machine. [Figure 14] 10 is a flowchart illustrating an example of a procedure for processing unsettled payments. [Figure 15] 10 is an example of a display screen of the mobile device when the dedicated app is stopped. [Figure 16] 10 is an example of a display screen of the mobile device after the dedicated app is restarted. [Figure 17] 10 is an example of a display screen of a mobile terminal when an abnormal state in an unsettled transaction is detected. [Figure 18] 10 is an example of a display screen displayed on a mobile terminal when an electronic commerce transaction is performed using a dedicated application. [Figure 19] 10 shows a schematic configuration of a management server according to a second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

[0013] First Embodiment (1) Management system configuration 1 shows the configuration of a management system 100 according to this embodiment. The management system 100 mainly comprises a POS server 1, a management server 2, a mobile terminal 3, a member server 4, and a checkout machine 5. In the management system 100, a customer using a mobile terminal 3 registers a product to be purchased (also referred to as a "purchased product") by reading a product barcode 7 attached to the product in a store 8 that sells the product, and then pays using the checkout machine 5 in the store 8 or by electronic payment.

[0014] The POS server 1 is a server that manages various sales information such as product information including prices and inventory status of products sold in the store 8, and sales information of the store 8. The POS server 1 can communicate with the management server 2 and the accounting machine 5 via a network or the like. The POS server 1 may collectively manage the sales information of multiple affiliated stores, or may exist for each store and manage only the sales information of that store.

[0015] The management server 2 is a server device that controls the mobile terminal 3 and the payment machine 5, and is capable of communicating with the mobile terminal 3, the member server 4, and the payment machine 5 via a network or the like. The management server 2 obtains and stores information necessary for display control of the mobile terminal 3 from the POS server 1. The management server 2 transmits display information to the mobile terminal 3 for the mobile terminal 3 to display various screens. The various screens described above include a screen (also referred to as the "purchased product list screen") that displays a list of purchased products registered by the mobile terminal 3 by reading product barcodes 7 (referred to as the "purchased product list") together with their selling prices. The management server 2 also obtains information about members from the member server 4 and transmits information to the member server 4 to update the information stored in the member server 4.

[0016] The management server 2 may be configured with multiple server devices. For example, the management server 2 may be configured with a server device that mainly performs interface operations with the mobile terminal 3, such as exchanging data with the mobile terminal 3, and a server device that stores and manages various information such as information acquired from the POS server 1 and a purchase product list. In this case, the former server device functions as a so-called application server, and the latter server device functions as a so-called database server. In this case, these server devices exchange information necessary to execute the processes assigned to them via a network or the like.

[0017] The mobile terminal 3 is a mobile terminal used by customers who shop at the store 8, and has functions such as reading product barcodes 7 attached to products and acquiring and displaying various screens such as a purchase product list screen by communicating with the management server 2. Note that for the sake of convenience, only one mobile terminal 3 is shown in FIG. 1, but in reality there are as many mobile terminals as there are customers in the store 8.

[0018] The member server 4 stores information about members and information about member cards to be issued to members. The member server 4 is capable of communicating with the management server 2 via a network or the like. The management server 2 may also function as the member server 4. In this case, the management server 2 stores information about members and member cards stored in the member server 4.

[0019] The payment machine 5 is a payment machine (a so-called self-payment machine) that allows customers to settle their bills using a mobile terminal 3. The payment machine 5 can communicate with the management server 2, and exchanges various information necessary for settlement with the management server 2 and, as necessary, with the POS server 1. The payment machine 5 is equipped with a barcode reader 56 for reading a payment barcode (described below) from the customer's mobile terminal 3, and a light 57 for calling a store clerk.

[0020] (2) Equipment configuration Next, the configuration of each of the POS server 1, management server 2, mobile terminal 3, member server 4, and payment machine 5 will be described with reference to FIGS.

[0021] (2-1) POS server 2 shows a schematic configuration of the POS server 1. The POS server 1 mainly comprises a storage unit 13, a communication unit 14 for performing data communication, and a control unit 15. These elements are interconnected by a bus line 10.

[0022] The storage unit 13 is configured with a memory such as a hard disk or flash memory. The storage unit 13 stores programs executed by the control unit 15 and information necessary for the control unit 15 to execute predetermined processes by executing the programs. In this embodiment, the storage unit 13 includes selling price change information 17, a product information DB (Database) 18, and sales information 19, which is information related to product sales. Note that the storage unit 13 may store various types of sales-related information other than the selling price change information 17, the product information DB 18, and the sales information 19.

[0023] The product information DB18 is a database of information about products handled by the store 8 or affiliated stores including the store 8. The product information DB18 includes various information such as product prices, information for identifying products such as JAN (Japanese Article Number) codes (also referred to as "product identification information"), product classification information, and product inventory status.

[0024] The selling price change information 17 is information related to a change in selling price. Specifically, the selling price change information 17 includes at least one of any discount information or discount information such as category discount information, bundle discount information, set discount information, total amount discount information, category discount information, bundle discount information, set discount information, and total amount discount information.

[0025] The control unit 15 includes a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc. (not shown), and performs various controls on the components within the POS server 1. For example, the control unit 15 updates the sales information 19 by communicating with the accounting machine 5 via the communication unit 14. The control unit 15 also communicates with the management server 2 via the communication unit 14 to send the selling price change information 17 and information on the product information DB 18 to the management server 2.

[0026] (2-2) Management Server 3 shows a schematic configuration of the management server 2. The management server 2 mainly includes a storage unit 23, a communication unit 24, and a control unit 25. These elements are connected to each other via a bus line 20.

[0027] The storage unit 23 is configured with a memory such as a hard disk or a flash memory. The storage unit 23 stores programs executed by the control unit 25 and information necessary for the control unit 25 to execute predetermined processes by executing the programs. In this embodiment, the storage unit 23 stores selling price change information 27, a product information DB 28, and a purchased product list DB 29.

[0028] Like the selling price change information 17, the selling price change information 27 is information relating to changes in selling prices resulting from discounts or price reductions. The selling price change information 27 is updated regularly or irregularly under the control of the control unit 25 so as to be synchronized with the selling price change information 17 stored in the POS server 1. The product information DB 28, like the product information DB 18, is a database of information relating to products. The product information DB 28 is updated regularly or irregularly under the control of the control unit 25 so as to be synchronized with the product information DB 18 stored in the POS server 1.

[0029] The purchased item list DB29 is a database of a list of unpaid purchased items for each mobile terminal 3 of a customer who is shopping at the store 8. The purchased item list is a list that includes, for example, item identification information indicating items to be purchased (i.e., unpaid) and the planned purchase quantities of those items, and is associated with information that identifies the mobile terminal 3 or the customer who uses the mobile terminal 3 (also referred to as "customer identification information"). The customer identification information may be any information that can uniquely identify a customer, and may be the card number of a membership card given to the customer, identification information for a dedicated app described below, or information that identifies the mobile terminal 3. The purchased item list is updated each time a purchased item is added, deleted, or the quantity is changed based on the operation of the mobile terminal 3.

[0030] The storage unit 23 also stores location information expressed by absolute coordinates for specifying the area of ​​the store 8 (more specifically, the area where shopping takes place at the store 8). This location information is used to determine whether the mobile terminal 3 has left the store 8, as will be described later.

[0031] The communication unit 24 communicates with the POS server 1, the mobile terminal 3, and the payment machine 5 via wired or wireless communication. The control unit 25 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on the components within the management server 2. The processing executed by the control unit 25 will be described later.

[0032] (2-3) Mobile devices 4 shows a schematic configuration of the mobile terminal 3. The mobile terminal 3 mainly includes a display unit 31, an input unit 32, a storage unit 33, a communication unit 34, a control unit 35, and a reading unit 36. These elements are connected to each other via a bus line 30.

[0033] The display unit 31 displays various information such as a purchase item list and an accounting barcode under the control of the control unit 35. The input unit 32 is an interface that accepts user input, and includes, for example, a touch panel, buttons, and a voice input device.

[0034] The storage unit 33 is configured with a memory such as a hard disk or a flash memory. The storage unit 33 stores programs executed by the control unit 35 and information necessary for the control unit 35 to execute predetermined processes by executing the programs. For example, the storage unit 33 stores an application program (hereinafter also referred to as a "dedicated app") provided by the store 8 or the company (organization) that manages the store 8. The dedicated app is launched when shopping at the store 8 and controls the display of various screens such as a purchase item list screen.

[0035] The communication unit 34 communicates with the management server 2 via wireless communication. The control unit 35 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on the components within the mobile terminal 3. The control unit 35 controls the display unit 31, the communication unit 34, the reading unit 36, etc., and functions as an "acquisition unit," a "transmission unit," and a "display control unit." The control performed by the control unit 35 will be described later.

[0036] The reading unit 36 ​​is an optical device such as a camera, which reads the product barcode 7 attached to the product and supplies the read information to the control unit 35. In this embodiment, the control unit 35 acquires product identification information such as a JAN code from the product barcode 7 attached to the product based on the information output by the reading unit 36.

[0037] (2-4) Member Server 5 shows a schematic configuration of the member server 4. The member server 4 mainly comprises a storage unit 43, a communication unit 44, and a control unit 45. These elements are connected to each other via a bus line 40.

[0038] The storage unit 43 is configured with a memory such as a hard disk or a flash memory. The storage unit 43 stores programs executed by the control unit 45 and information necessary for the control unit 45 to execute predetermined processes by executing the programs. In this embodiment, the storage unit 43 mainly stores a member information DB 47 and a card information DB 48.

[0039] The member information DB 47 is a database of member information for each member who has completed the membership procedure. The member information includes general attribute information such as name, gender, and date of birth, as well as member-specific attribute information such as card number, member rank, and accumulated points. The card number is an identification number for the member card, and the member card is a point card issued by applying for membership at, for example, a counter in the store 8. To receive the member card, the applicant is required to fill out an application form containing personal information such as name. The member card is printed with the card number assigned to the card and a personal identification number (PIN code) used to verify the validity of the card number. Members are classified into primary members, who are not subordinate to other members, and family members, who are subordinate to the primary member. Member cards include primary member cards issued to primary members and family cards issued to family members. Primary members and family members share points awarded for shopping, etc.

[0040] The card information DB 48 is a database related to membership cards. For example, the card information DB 48 contains a combination of a card number assigned to a membership card that may be issued and a personal identification number for verifying the validity of the card number. The card information DB 48 also contains information related to the validity of each membership card. In addition, the card number of a family card that may be issued is associated with the card number of a primary membership card that shares points with the family card.

[0041] The purchase history DB 49 is a database of purchase history information generated based on a purchased product list for which payments have been made. Purchase history information is generated for each purchased product list for which payments have been made, and associates the purchased product list for which payments have been made with information about the customer (e.g., customer identification information) and information about the payment. Information about the payment includes, for example, information such as the date and time of the payment, the store where the payment was made, the price of the product at the time of payment, and the total amount. The purchase history DB 49 may be held by the management server 2 instead of the member server 4.

[0042] The communication unit 44 communicates with the management server 2 etc. via wired or wireless communication. The control unit 45 includes a CPU, ROM, RAM etc. (not shown), and performs various controls on the components in the member server 4.

[0043] (2-5) Accounting machine Figure 6 shows the schematic configuration of the payment machine 5. The payment machine 5 mainly comprises a display unit 51, an input unit 52, a memory unit 53, a communication unit 54, a control unit 55, a barcode reader 56, a light 57, and a speaker 58. These elements are interconnected via a bus line 50.

[0044] The display unit 51 displays various information such as a payment method selection screen and a closing screen under the control of the control unit 55. The input unit 52 is an interface that accepts input from the customer, and corresponds to, for example, a touch panel, buttons, etc.

[0045] The storage unit 53 is configured with a memory such as a hard disk or flash memory. The storage unit 53 stores programs executed by the control unit 55 and information necessary for the control unit 55 to execute predetermined processes by executing the programs. For example, the storage unit 53 stores a dedicated application program that operates when a customer makes a payment and performs accounting processing.

[0046] The control unit 55 is equipped with a CPU, ROM, RAM, etc. (not shown), and performs various controls on each component within the payment machine 5. The controls performed by the control unit 55 will be described later. The barcode reader 56 reads the payment barcode displayed on the customer's mobile terminal 3 during payment and supplies the read information to the control unit 55. The light 57 lights up when a malfunction occurs in the payment machine 5 or when a store clerk needs to be called. The speaker 58 outputs operation sounds and voice messages to alert the user as necessary.

[0047] (3) Product purchase processing Next, an overview of the product purchase process performed by the management system 100 will be described. The product purchase process is a process in which a customer purchases a product at a store 8 using a mobile terminal 3. FIG. 7 is a flowchart showing an overview of the product purchase process. The product purchase process can be broadly divided into a store entry process S100, a product selection process S200, and a checkout process S300. The product purchase process is mainly realized by the management server 2, the mobile terminal 3, and the checkout machine 5 each executing a program prepared in advance.

[0048] (3-1) Entry processing First, the store entry process will be described. The store entry process is a process that is performed when a customer enters the store 8 and prior to purchasing a product, and corresponds to preparation for purchasing a product. Fig. 8 is a flowchart showing an example of the store entry process. This process is performed by the mobile terminal 3 and the management server 2.

[0049] First, when a customer enters the store 8, they use their mobile terminal 3 to read the store barcode (step S101). The store barcode is attached to a predetermined location within the store 8, for example, a wall near the store entrance or on a card used for shopping. When the customer reads the store barcode, the mobile terminal 3 obtains a store ID from the read store barcode and sends it to the management server (step S102). When sending the store ID, the mobile terminal 3 also sends customer identification information that identifies the mobile terminal 3 or the customer using the mobile terminal 3. Note that in the product selection process and checkout process described below, when the mobile terminal 3 sends any information to the management server 2, it basically also sends customer identification information that identifies itself.

[0050] The management server 2 receives the store ID from the mobile terminal 3 and obtains the sales price list of that store from the product information DB 28 (step S104). This is because the sales prices of products vary from store to store. The management server 2 then transmits store information, including the store name and sales information of that store, to the mobile terminal 3 (step S105), and the mobile terminal 3 receives the store information (step S106). As a result, the current store name and sales information of that store are displayed on the display unit 31 of the mobile terminal 3, and the customer is ready to start shopping. The store information transmitted by the management server 2 includes information indicating the customer's transaction status at that store. When the customer starts a new purchase at that store, the transaction status becomes new. On the other hand, if the customer interrupts shopping at that store for some reason, a purchased product list screen corresponding to the previous transaction status is displayed on the mobile terminal 3.

[0051] (3-2) Product selection process Next, the product selection process will be described. In the product selection process, a customer reads the product barcode attached to a product using the mobile terminal 3 and registers the product in a purchase product list. Figure 9 is a flowchart of the product selection process. This process is executed by the mobile terminal 3 and the management server 2.

[0052] First, when a customer finds a product they want to purchase, they switch their mobile terminal 3 to product reading mode and use the mobile terminal 3 to read the product barcode attached to the product (Step S201: Yes). The mobile terminal 3 then transmits the read product identification information of the product to the management server 2 (Step S202). At this time, the quantity of the product is automatically set to "1". When the management server 2 receives the product identification information from the mobile terminal 3 (Step S203), it updates the purchased product list and transmits it to the mobile terminal 3 (Step S204). The mobile terminal 3 receives the updated purchased product list and displays it on the display unit 31 (Step S205). As a result, the newly added product and its quantity are added to the purchased product list and displayed on the mobile terminal 3.

[0053] Next, if necessary, the customer operates the mobile terminal 3 to change the quantity of the product, and the mobile terminal 3 acquires the changed quantity (step S206: Yes). When the product barcode is first read, the quantity of that product is automatically set to "1", but if the customer purchases multiple copies of the same product, the quantity can be changed by operating the mobile terminal 3. Once the changed quantity is set, the mobile terminal 3 transmits the product identification information of the product to be changed and the changed quantity to the management server 2 (step S207).

[0054] When the management server 2 receives the product identification information and the changed quantity from the mobile terminal 3 (step S208), it updates the purchased product list and sends it to the mobile terminal 3 (step S209). The mobile terminal 3 receives the updated purchased product list and displays it on the display unit 31 (step S210). This reflects the change in quantity in the purchased product list.

[0055] Next, the mobile terminal 3 determines whether the customer has pressed the payment button (step S211). The payment button is the button that the customer presses when finishing shopping. If the payment button has not been pressed (step S211: No), the process returns to step 201. In this way, the customer can continue shopping by adding products or changing the quantity until the payment button is pressed. Then, when the payment button is pressed (step S211: Yes), the product selection process ends.

[0056] 10 shows an example of a purchase item list screen displayed on the mobile terminal 3. In this example, the purchase item list screen has a product read button 90, a list display field 91, a subtotal display field 92, a total amount display field 93, a home screen transition button 94, a payment button 95, and a transaction cancellation button 96.

[0057] When the mobile terminal 3 detects that the product reading button 90 has been selected by a tap operation or the like, it switches the display on the display unit 31 to a product reading screen. On the product reading screen, the mobile terminal 3 displays an image or the like acquired from the activated reading unit 36. This allows the customer to move the product or the mobile terminal 3 so that the product barcode 7 is within the reading range of the reading unit 36, and read the product barcode 7.

[0058] The name, quantity, and price of each purchased item are displayed in the list display field 91. A quantity decrease button 97 and a quantity increase button 98 are also displayed for each purchased item in the list display field 91. When the mobile terminal 3 receives a change in the quantity of a purchased item using the quantity decrease button 97 or the quantity increase button 98, it transmits, for example, product identification information of the purchased item whose quantity has been changed and the changed quantity to the management server 2.

[0059] The subtotal display field 92 displays the subtotal of the sales prices of all items in the purchase list excluding tax, and the total amount display field 93 displays the total of the sales prices of all items in the purchase list including tax. The management server 2 calculates these subtotals or total amounts based on the prices of the purchased items registered in the product information DB 28, specifically, the sales price list of the store obtained by the store entry process.

[0060] When the mobile terminal 3 detects that the home screen transition button 94 has been selected, it sends a home screen display request to the management server 2 and displays a predetermined home screen based on the display information received in response. The home screen may display information about discounts and discounts at the store 8, registration information for the customer of the mobile terminal 3, etc.

[0061] When the mobile terminal 3 detects that the payment button 95 has been selected, it sends a payment request to the management server 2 and displays a payment screen including a payment barcode screen (described below) based on the display information received in response. Furthermore, when the mobile terminal 3 detects that the transaction cancel button 96 has been selected, it sends information notifying the management server 2 that the transaction has been canceled. In this case, the management server 2 deletes the purchase item list corresponding to the mobile terminal 3.

[0062] (3-3) Accounting Next, we will explain the transaction process. The transaction process is the process of making payment for the products selected by the customer in the product selection process. Figure 11 is a flowchart of the transaction process. This process is executed by the mobile terminal 3, management server 2, and payment machine 5.

[0063] First, when the payment button 95 is pressed, the mobile terminal 3 sends a payment request to the management server 2 (step S301). When the management server 2 receives the payment request (step S302), it calculates the payment amount based on the current purchase list (step S303). The management server 2 then generates a payment barcode (step S304). The payment barcode is information that uniquely identifies the purchase indicated by the current purchase list. In one example, the payment barcode can be a random code uniquely associated with the purchase at that time. In this case, the payment barcode serves as a payment information inquiry number. The management server 2 then sends a payment screen to the mobile terminal 3, including the payment amount calculated in step S303 and the payment barcode generated in step S304 (step S305).

[0064] The mobile device 3 displays the received payment screen on the display unit 31. Figure 12 is an example of the payment screen. In this example, the payment screen includes a billing barcode 37, a total amount field 38, and a complete button 39. The customer carries the mobile device 3 displaying the payment screen to the payment machine 5 and reads the billing barcode with the barcode reader 56 (step S307). The payment machine 5 displays the payment method selection screen based on the read billing barcode (step S308). Specifically, the payment machine 5 sends the inquiry number indicated by the billing barcode to the management server 2 and obtains payment information. The payment information includes the total amount and details such as the IDs and quantities of all items in the purchase list. The payment machine 5 displays the payment method selection screen based on the obtained payment information.

[0065] FIG. 13(A) shows an example of the payment method selection screen. The payment method selection screen includes a total amount field 61, a cash button 62, and a credit button 63. The customer looks at the payment method selection screen, confirms the payment amount, and presses either the cash button 62 or the credit button 63 to make the payment. This completes the payment for the purchase (step S309). Specifically, if the customer selects to pay by cash, the payment machine 5 prompts the customer to insert cash into the cash slot, and once the cash is inserted, it provides change as necessary. If the customer selects to pay by credit card, the payment machine 5 prompts the customer to insert a card and, if necessary, to enter a PIN or other information, and then completes the credit card payment.

[0066] When the payment is complete, the payment machine 5 displays a payment completion screen. Figure 13(B) shows an example of the payment completion screen. In this example, the payment completion screen includes a payment information field 64, a receipt button 65, and an end button 66. Note that Figure 13(B) shows an example in which the customer has selected credit card payment, and the payment information field 64 displays information such as the payment amount and payment method. The receipt button 65 is a button for printing out a receipt. The end button 66 is a button for the customer to confirm that the payment process has been completed. When the customer presses the end button 66, the payment machine 5 reports to the management server 2 that the payment has been completed and returns the display on the display unit 51 to the main menu. Note that a complete button 39 is also displayed on the payment screen shown in Figure 12, and the customer presses the complete button 39 on the payment screen when the payment process is complete. When the complete button 39 is pressed, the mobile terminal 3 reports to the management server 2 that the payment has been completed and returns the display unit 31 to the main menu.

[0067] In the above example, the accounting barcode is simply a payment information inquiry number, and the accounting machine 5 uses this inquiry number to obtain payment information from the management server 2. Alternatively, the accounting barcode may contain payment information. That is, the management server 2 generates the accounting barcode using the total amount and details of the purchased items based on the contents of the current purchase list. In this case, the accounting machine 5 can obtain payment information by reading and decoding the accounting barcode, eliminating the need to communicate with the management server 2 to obtain payment information. That is, the accounting machine 5 simply extracts the total amount from the scanned accounting barcode and displays the payment method selection screen.

[0068] (4) Unpaid balance processing Next, an unsettled transaction process that is performed by the management server 2 when an abnormality occurs and an unsettled purchase product list exists will be described.

[0069] (4-1) Overview When the management server 2 detects that the dedicated app on a mobile terminal 3 used by a customer for which there is an unpaid purchase item list has been terminated, the management server 2 retains the purchase item list without deleting it from the purchase item list DB 29. Then, when the management server 2 detects that the dedicated app on the target mobile terminal 3 has been restarted, it sends information about the retained unpaid purchase item list to the mobile terminal 3, thereby causing the mobile terminal 3 to display the purchase item list as of immediately before the dedicated app was terminated. In this way, even if the dedicated app is terminated for some reason while shopping, the management server 2 allows the customer to smoothly resume shopping by restarting the dedicated app.

[0070] Furthermore, if the dedicated app is terminated while there is a list of unpaid purchase items, the management server 2 causes the mobile terminal 3 to output a notification to the effect that there is a list of unpaid purchase items at predetermined time intervals until the dedicated app is restarted. This allows the management server 2 to notify the customer of the existence of a list of unpaid purchase items, and to prompt the customer to resume shopping and make payment in an appropriate manner.

[0071] Furthermore, if the list of unpaid purchased items is not updated for a predetermined period of time or more, or if the management server 2 detects that the mobile terminal 3 has left the store 8 while there is an unpaid purchased item list, the management server 2 causes the mobile terminal 3 to output a notification regarding the list of unpaid purchased items. In this way, the management server 2 causes the mobile terminal 3 to output a notification when it detects an abnormal state in an unpaid purchase.

[0072] (4-2) Processing flow Fig. 14 is an example of a flowchart showing the procedure for unpaid transactions executed by the management server 2. For example, the management server 2 executes the process of the flowchart shown in Fig. 14 for each customer who has not completed payment after executing the store entry process shown in Fig. 8. For ease of explanation, the unpaid transaction process shown in Fig. 14 includes the process executed by the management server 2 in the product selection process shown in Fig. 9.

[0073] First, the mobile terminal 3 used by the customer starts a dedicated app on the mobile terminal 3 to establish communication with the management server 2, and then performs the process of the store entry process flowchart shown in Figure 8. Then, when the customer finds a product they want to purchase, they switch the mobile terminal 3 to product reading mode and read the product barcode attached to the product using the mobile terminal 3. The mobile terminal 3 transmits the product identification information of the read product to the management server 2.

[0074] The management server 2 then determines whether or not it has received product identification information from the mobile terminal 3 (step S401). If the management server 2 has received product identification information from the mobile terminal 3 (step S401; Yes), it updates the purchased product list and transmits the updated purchased product list to the mobile terminal 3 (step S402). If the purchased product list for the target customer is not registered in the purchased product list DB 29, the management server 2 registers the purchased product list, which includes the received product identification information as an element, in association with the customer identification information of the target customer in the purchased product list DB 29. If the management server 2 receives information on the quantity to be changed together with the product identification information from the mobile terminal 3 in step S401, it changes the quantity of the product indicated by the specified product identification information in step S402. The processing in step S401 corresponds to the processing in steps S203 and S208 of the product selection processing shown in FIG. 9, and the processing in step S402 corresponds to the processing in steps S204 and S209.

[0075] Next, the management server 2 determines whether the dedicated app on the mobile terminal 3 has terminated (step S403). For example, the management server 2 determines that the dedicated app has terminated when the communication connection established with the dedicated app on the mobile terminal 3 is disconnected. In another example, the management server 2 determines that the dedicated app has terminated when information transmitted from the mobile terminal 3 is no longer received while the dedicated app is running. Note that termination of the dedicated app includes, for example, termination due to a customer's operation on the mobile terminal 3, as well as forced termination due to an interruption of another application on the mobile terminal 3 (e.g., an incoming call) or freezing of the dedicated app. Examples of termination of the dedicated app due to a customer's operation on the mobile terminal 3 include termination of the dedicated app due to an incorrect operation, or when a customer temporarily leaves their shopping cart at a service counter or the like of the store 8 due to an urgent matter, temporarily terminates the dedicated app, and leaves the store 8.

[0076] Then, when the management server 2 determines that the dedicated app on the mobile terminal 3 has been terminated (step S403; Yes), it continues to hold the list of unpaid purchased items of the target customer (step S404). Specifically, the management server 2 continues to store the purchased item list of the target customer in the purchased item list DB 29 without deleting it from the purchased item list DB 29. In this case, for example, the management server 2 may add flag information indicating that the dedicated app has been terminated to the purchased item list of the target customer.

[0077] Then, the management server 2 causes the mobile terminal 3 to output a notification at predetermined time intervals until the dedicated app on the mobile terminal 3 used by the target customer is restarted (step S405). The predetermined time intervals are, for example, predetermined time intervals and are stored in the storage unit 23 or the like. In step S405, for example, the management server 2 sends notification information to the mobile terminal 3 indicating that there is a list of unpaid purchased items, and causes the notification information to be displayed on the screen of the mobile terminal 3 using a push notification function. In this way, the management server 2 can continuously make the customer using the mobile terminal 3 aware of the existence of the list of unpaid purchased items.

[0078] The management server 2 then determines whether the dedicated app on the portable terminal 3 used by the target customer has been restarted (step S406). For example, the management server 2 determines that the dedicated app on the target portable terminal 3 has been restarted when communication with the dedicated app on the portable terminal 3 used by the target customer is re-established, or when predetermined information transmitted while the dedicated app is running is received. If the management server 2 determines that the dedicated app on the portable terminal 3 has not been restarted (step S406; No), the management server 2 continues the processing of steps S404 and S405.

[0079] On the other hand, if the management server 2 detects that the dedicated app on the mobile device 3 used by the target customer has been restarted (step S406; Yes), it sends a purchased item list corresponding to the target customer to the target mobile device 3 (step S407). In this case, the management server 2 extracts a purchased item list linked to the target customer's customer identification information from the purchased item list DB 29 and sends the information on the purchased item list to the target mobile device 3. In this case, the mobile device 3 displays a purchased item list screen on the dedicated app based on the information on the purchased item list received from the management server 2. As a result, even if the dedicated app is terminated for some reason while shopping, the customer can restart the dedicated app and continue shopping in the state it was in immediately before the dedicated app was terminated. In other words, in this case, the customer does not need to perform operations such as reading the product barcodes of the products added to the shopping cart again before the dedicated app was terminated.

[0080] After detecting the restart of the dedicated app, the management server 2 may allow the customer at the mobile terminal 3 to select whether or not to continue shopping using the list of purchased items that was in effect immediately before the dedicated app was closed. In this case, if the customer selects to continue shopping using the list of purchased items that was in effect immediately before the dedicated app was closed, the management server 2 transmits the list of purchased items in step S407. A specific example of this will be described later with reference to FIG. 16.

[0081] On the other hand, if it is determined that the dedicated app on the mobile terminal 3 has not been terminated (step S403; No), the management server 2 determines whether or not a predetermined time has elapsed since the most recent update of the purchase item list (step S408). That is, the management server 2 determines whether or not the processing of step S402 was performed within the predetermined time. The above-mentioned predetermined time is determined in advance, for example, taking into consideration the average time interval between adding items to a shopping cart when shopping.

[0082] If a predetermined time or more has passed since the most recent update of the purchase item list (step S408; Yes), the management server 2 causes the mobile terminal 3 to output a notification that there is an unpaid purchase item list (step S409). This allows the management server 2 to conveniently notify the customer of the existence of a purchase item list that has been left unpaid, and urges the customer to complete payment.

[0083] On the other hand, if a predetermined time or more has not passed since the most recent update of the purchased item list (step S408; No), the management server 2 determines whether the mobile terminal 3 has left the store 8 (step S410). In this case, for example, the management server 2 acquires location information transmitted from the mobile terminal 3 and determines whether the location indicated by the location information is within the area of ​​the store 8. The above-mentioned location information may be location information based on radio waves from a GPS, may be location information based on radio waves from a beacon terminal, or may be location information based on radio waves from a wireless LAN. Note that the location information indicating the area of ​​the store 8 is stored in advance in the storage unit 23, for example.

[0084] Then, when the management server 2 determines that the mobile terminal 3 has left the store 8 (step S410; Yes), the management server 2 causes the mobile terminal 3 to output a notification that there is an unpaid purchase item list (step S409). This allows the management server 2 to prompt the customer to preferably complete payment for the unpaid purchase item list.

[0085] In this case, the management server 2 may transmit information to a terminal used by a store clerk at the store 8, notifying the clerk that a customer with an unpaid purchase list has left the store 8. In other words, the management server 2 may notify the terminal used by the store clerk at the store 8 of the presence of the mobile terminal 3 that has left the store 8. In this case, the management server 2 may include member information recorded in a record in the member information DB 47 corresponding to the target customer in the information transmitted to the terminal used by the clerk. This allows the management server 2 to conveniently notify the clerk at the store 8 of the presence of a customer who has left the store 8 without paying.

[0086] On the other hand, if the management server 2 determines that the mobile terminal 3 has not left the store 8 (step S410; No), or after executing step S407, the management server 2 determines whether the target customer has finished shopping (step S411). In this case, the management server 2 determines that shopping has finished when it detects that payment for the purchased item list has been completed, or when it detects that cancellation of the transaction has been selected in the dedicated app. Then, if shopping has finished (step S411; Yes), the management server 2 ends the processing of the flowchart. On the other hand, if shopping has not finished (step S411; No), the management server 2 returns the processing to step S401.

[0087] (4-3) Screen example FIG. 15 is an example of a display screen that the management server 2 causes the mobile terminal 3 of the target customer to display in step S405 of FIG.

[0088] In this case, since a predetermined time interval has elapsed since the dedicated app was terminated in step S403 of Fig. 14 and the dedicated app has not been restarted, the management server 2 causes the mobile terminal 3 to output a notification using the push notification function based on step S405. In this case, based on the information received from the management server 2, the mobile terminal 3 pops up a window 71 displaying "There is a list of unpaid purchased items."

[0089] In this way, when the dedicated app on the mobile terminal 3 used by a customer who has a list of unpaid purchases is closed, the management server 2 pops up a window 71 notifying the customer that there is a list of unpaid purchases. This allows the mobile terminal 3 to prompt the customer to restart the dedicated app and resume shopping at the store 8.

[0090] FIG. 16 is an example of a display screen displayed on the mobile terminal 3 after the dedicated application is restarted from the state shown in FIG.

[0091] In this case, after restarting the dedicated app, the mobile terminal 3 displays a pop-up window 72 on the display screen of the dedicated app on the mobile terminal 3. The mobile terminal 3 displays a first button 73 and a second button 74 on the window 72 along with text information indicating that an unpaid purchase item list exists. The first button 73 is a button for specifying that shopping should be continued using the unpaid purchase item list, and the second button 74 is a button for specifying that the transaction should be canceled. When the mobile terminal 3 detects that the first button 73 has been selected, it receives information about the unpaid purchase item list (i.e., the purchase item list immediately before the dedicated app was closed) sent from the management server 2 in accordance with step S407 of FIG. 14 and redisplays the purchase item list screen. In this case, the purchase item list screen displays the purchase item list immediately before the dedicated app was closed. On the other hand, when the mobile terminal 3 detects that the second button 74 has been selected, it sends information notifying the management server 2 of the cancellation of the transaction, as when the cancel transaction button 46 is selected on the purchase item list screen. In this case, the management server 2 deletes the purchase item list corresponding to the mobile terminal 3.

[0092] FIG. 17 is an example of a display screen that the management server 2 causes the mobile terminal 3 of the target customer to display in step S409 of FIG.

[0093] In this case, the management server 2 detects that a predetermined time has passed without the list of unpaid purchased items being updated, or that the mobile terminal 3 has left the store 8 with an unpaid purchased item list, and causes a window 75 to be displayed as a notification on the purchased item list screen displayed by the dedicated app. Here, the management server 2 displays text information on the window 75 urging the user to pay for the purchased item list.

[0094] (4-4) Utilizing purchase history Preferably, the management server 2 may use information on the purchased product list for which payment has been completed in subsequent purchases of products by the same customer through e-commerce. In this case, upon completion of payment, the management server 2 generates purchase history information that associates the purchased product list for which payment has been completed, customer identification information indicating the customer who purchased the products, and information related to the payment, and stores this information in the purchase history DB 49 of the member server 4. Then, in subsequent shopping by the same customer through e-commerce, the management server 2 displays and generates a list of products to be purchased based on the purchase history information stored in the purchase history DB 49.

[0095] FIG. 18 shows an example of a display screen displayed on the mobile terminal 3 when an electronic commerce transaction is carried out using a dedicated application.

[0096] In FIG. 18 , first, the management server 2 detects, via the mobile terminal 3, a user input indicating an order to be placed based on past purchase history. In other words, the management server 2 receives, from the mobile terminal 3, a shopping request based on past purchase history through e-commerce transactions. Upon receiving the shopping request, the management server 2 extracts, from the purchase history DB 49, purchase history information indicating multiple purchases associated with the customer identification information of the customer using the mobile terminal 3. The management server 2 then generates a purchase history list 76 based on the purchase history information extracted from the purchase history DB 49 and displays the generated purchase history list 76 on the mobile terminal 3. Here, the purchase history list 76 has multiple elements corresponding to past purchases, and each element includes information such as the purchase date and time, the store where the purchase was made, the payment number, and the total amount. Each element in the purchase history list 76 is provided with a detail display button 77A-77D (77) for displaying the respective detailed purchase history.

[0097] The customer using the mobile device 3 then refers to the purchase history list 76 and selects the detail display button 77 corresponding to the purchase history they wish to view in this e-commerce transaction. In this case, the management server 2 receives information related to the selected detail display button 77 from the mobile device 3 and causes the mobile device 3 to display a purchase history detail screen corresponding to the selected detail display button 77. The detail screen may display, for example, a purchase product list, which is a list of purchased products. Preferably, the management server 2 generates a shopping list for this e-commerce transaction (i.e., a list of products to be purchased) based on the purchase product list displayed on the detail screen. That is, when the management server 2 detects an operation on the detail screen to update the purchase product list to the current shopping list, it generates a current shopping list based on the purchase product list indicated by the selected purchase history. This allows the customer to conveniently purchase products through e-commerce transactions by utilizing their past purchase history in physical stores. The terminal used by the customer for e-commerce transactions is not limited to the mobile device 3, and may be any terminal, such as a desktop computer used by the customer.

[0098] Second Embodiment 19 shows a schematic configuration of a management server 2A in the second embodiment. The management server 2A has a receiving unit 81, a generating unit 82, a holding unit 83, and a transmitting unit 84.

[0099] The receiving unit 81 receives product identification information "S1" from the mobile terminal 3A used by the customer. The receiving unit 81 is realized, for example, by the control unit 25 that controls the communication unit 24 in the first embodiment. The mobile terminal 3A is, for example, the mobile terminal 3 in the first embodiment. The generating unit 82 generates a purchase product list, which is a list of products that the customer plans to purchase, based on the product identification information S1. The generating unit 82 is realized, for example, by the control unit 25 in the first embodiment.

[0100] If the retention unit 83 detects that the application that controls the transmission of product identification information S1 and the display of the purchased product list on the mobile terminal 3A has been terminated while the purchased product list is in an unpaid state, the retention unit 83 retains the purchased product list until it detects that the application has been restarted. The retention unit 83 is realized, for example, in the first embodiment, by the control unit 25 that controls the registration and deletion of the purchased product list in the purchased product list DB 29 of the storage unit 23. After the application is restarted, the transmission unit 84 transmits the retained information "S2" regarding the purchased product list to the mobile terminal 3A. The transmission unit 84 is realized, for example, in the first embodiment, by the control unit 25 that controls the communication unit 24.

[0101] In this way, if the application on the mobile terminal 3A is terminated in the middle of shopping, the management server 2A according to the second embodiment can cause the list of purchased items that was displayed immediately before the application was terminated to be displayed again on the mobile terminal 3A when the application is restarted. This allows the customer to smoothly continue shopping by restarting the application even if the application on the mobile terminal 3A is terminated in the middle of shopping.

[0102] In addition, part or all of the above-described embodiments (including modified examples, the same applies below) can be described as, but are not limited to, the following supplementary notes.

[0103] [Appendix 1] a receiving unit that receives product identification information from a mobile terminal used by a customer; a generating unit that generates a purchase item list, which is a list of the items that the customer plans to purchase, based on the item identification information; a storage unit that stores the purchase item list when it detects that an application that controls transmission of the product identification information and display of the purchase item list in the mobile terminal has ended while the purchase item list is in an unpaid state, until it detects that the application has been restarted; a transmitting unit that transmits information about the purchased product list to the mobile terminal after the application is restarted.

[0104] [Appendix 2] The management server according to claim 1, further comprising a notification unit that notifies the mobile terminal of outstanding payments at predetermined time intervals after detecting the termination of the application until detecting the restart of the application.

[0105] [Appendix 3] 3. The management server according to claim 1, further comprising a notification unit that notifies the mobile terminal of pending payment if the purchase item list is not updated for a predetermined period of time or more while the payment is pending.

[0106] [Appendix 4] The management server described in any one of Appendices 1 to 3 has a notification unit that notifies the mobile terminal regarding the outstanding payment if it is determined that the mobile terminal has left the store while the purchase item list is outstanding.

[0107] [Appendix 5] The management server described in Appendix 4, wherein the notification unit notifies a terminal used by a store clerk of information regarding the mobile terminal that has left the store when it determines that the mobile terminal has left the store while the purchase item list is in an unpaid state.

[0108] [Appendix 6] the generation unit generates a purchase history based on a payment made for the purchased item list; the receiving unit receives a shopping request based on the purchase history through e-commerce from a terminal used by the customer; The management server according to any one of appendices 1 to 5, wherein the transmission unit transmits display information regarding the purchase history to a terminal used by the customer when the shopping request is received.

[0109] [Appendix 7] the receiving unit transmits the display information regarding the purchase history to the terminal used by the customer, and then receives information regarding the purchase history selected by the customer; The management server described in Appendix 6, wherein the generation unit generates a list of products to be purchased in the e-commerce shopping based on the purchased product list corresponding to the purchase history selected by the customer.

[0110] [Appendix 8] A management server according to any one of Supplementary Notes 1 to 7; A management system having a mobile terminal used by a customer, The mobile terminal an acquisition unit that acquires product identification information indicating a product to be purchased after launching an application that controls the mobile device in relation to shopping at the store that the customer has entered; a transmitting unit that transmits the product identification information to the management server; a display control unit that displays a purchase item list, which is a list of the items, on a display unit; The display control unit displays the purchase item list on the display unit based on information received from the management server after the application is restarted when the application is terminated while the purchase item list is in an unpaid state.

[0111] [Appendix 9] A control method executed by a management server, comprising: Receive product identification information from a mobile device used by a customer, generating a purchase item list, which is a list of the items that the customer plans to purchase, based on the item identification information; when detecting that an application that controls the transmission of the product identification information and the display of the purchase product list on the mobile terminal has been terminated while the purchase product list is in an unpaid state, the purchase product list is held until detecting that the application has been restarted; After the application is restarted, information about the purchased item list is transmitted to the mobile terminal.

[0112] [Appendix 10] a receiving unit that receives product identification information from a mobile terminal used by a customer; a generating unit that generates a purchase item list, which is a list of the items that the customer plans to purchase, based on the item identification information; a storage unit that stores the purchase item list when it detects that an application that controls transmission of the product identification information and display of the purchase item list in the mobile terminal has ended while the purchase item list is in an unpaid state, until it detects that the application has been restarted; a transmission unit that transmits information about the purchase item list to the mobile terminal after the application is restarted; A program that makes a computer function as a

[0113] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various modifications within the scope of the present invention that would be understood by those skilled in the art can be made to the configuration and details of the present invention. In other words, the present invention naturally includes various modifications and alterations that would be possible for those skilled in the art based on the entire disclosure, including the claims, and the technical ideas. Furthermore, the disclosures of the above-cited patent documents and other documents are incorporated herein by reference. [Explanation of symbols]

[0114] 1 POS server 2 Management Server 3. 3A mobile terminals 4 Member Server 5. Cashier 100, 100A Management System

Claims

1. a receiving means for receiving product identification information from a mobile terminal used by a customer; a generating means for generating a purchase item list, which is a list of items that the customer plans to purchase, based on the item identification information; a storage means for storing the purchase item list when the end of an application that controls the display of the purchase item list on the mobile terminal is detected while the purchase item list is in an unpaid state; a storage means for storing information relating to the mobile terminal that the application has been terminated in association with information relating to the mobile terminal, if the termination of the application is based on the mobile terminal having left the store where the customer has entered; A management server having:

2. 2. The management server according to claim 1, further comprising a notification unit that notifies the information stored in the storage unit to a terminal used by a store clerk in the store.

3. 3. The management server according to claim 1, further comprising a notification means for notifying the mobile terminal of an outstanding payment at predetermined time intervals after detecting that the application has been terminated until detecting that the application has been restarted.

4. The management server according to any one of claims 1 to 3, further comprising a notification means for notifying the mobile terminal of an outstanding payment if the purchase item list is not updated for a predetermined period of time while the payment is outstanding.

5. A management server as described in any one of claims 1 to 4, having a notification means for notifying the mobile terminal of an outstanding payment if the mobile terminal determines that the customer has left the store where the purchase item list is outstanding.

6. 6. The management server according to claim 1, wherein when a user selects not to continue shopping using the list of unpaid purchased items, the list of purchased items is deleted.

7. the generating means generates a purchase history based on a payment made for the purchased product list; the receiving means receives a shopping request based on the purchase history through electronic commerce from a terminal used by the customer; The management server according to any one of claims 1 to 6, further comprising a transmitting means for transmitting display information relating to the purchase history to a terminal used by the customer when the shopping request is received.

8. A management server according to any one of claims 1 to 7; A management system having a mobile terminal used by a customer, The mobile terminal an acquisition means for acquiring, in the store where the customer has entered, product identification information indicating a product to be purchased after starting an application for controlling the mobile device in relation to shopping at the store; a transmitting means for transmitting the product identification information to the management server; and a display control means for displaying a purchase item list, which is a list of the items, on a display unit.

9. A control method executed by a management server, comprising: Receive product identification information from a mobile device used by a customer, generating a purchase item list, which is a list of items that the customer plans to purchase, based on the item identification information; When detecting that an application that controls the display of the purchase item list on the mobile terminal has been terminated while the purchase item list is in an unpaid state, the purchase item list is retained; If the termination of the application is based on the mobile terminal leaving the store where the customer entered, the control method associates and stores information about the mobile terminal that the mobile terminal has left the store.

10. a receiving means for receiving product identification information from a mobile terminal used by a customer; a generating means for generating a purchase item list, which is a list of items that the customer plans to purchase, based on the item identification information; a storage means for storing the purchase item list when the end of an application that controls the display of the purchase item list on the mobile terminal is detected while the purchase item list is in an unpaid state; a storage means for storing information about the mobile terminal having left the store in association with information about the mobile terminal, if the termination of the application is based on the mobile terminal having left the store where the customer has entered; A program that makes a computer function as a

Images