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

Abstract

To smoothly resume shopping at a store where commodities are purchased using a portable terminal.SOLUTION: The management server 2A includes an acquiring unit 81, an extracting unit 82, and a transmitting unit 83. The acquisition unit 81 acquires store identification information indicating a store in which a customer enters and customer identification information indicating the customer. When the shopping information S1 associated with the shop identification information and the customer identification information acquired by the acquirer 81 is present in the database 84 of the unsettled shopping information associated with the shop identification information and the customer identification information, the extractor 82 extracts the shopping information S1 from the database 84. A transmission part 83 transmits display information S1 based on the shopping information S2 extracted by the extraction part 82 to a mobile terminal 3A used by the customer.SELECTED DRAWING: Figure 19

Description

[Technical Field]

[0001] The present invention relates to purchasing products using a mobile terminal. [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. [Prior art documents] [Patent documents]

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

[0004] 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 customer closes the shopping application and temporarily leaves the store before making the payment, the product must be registered again as a general rule. Patent Document 1 does not disclose anything about the process when a customer temporarily leaves the store before making the payment.

[0005] An object of the present invention is to provide a management server, a management system, a control method, and a storage medium that enable smooth resumption of shopping at a store where products are purchased using a mobile terminal. [Means for solving the problem]

[0006] One aspect of the management server is a management server that has: an acquisition means for acquiring store identification information indicating the store where a customer has entered and customer identification information indicating the customer; a generation means for generating an accounting code based on the payment information if unsettled payment information associated with the customer identification information acquired by the acquisition means exists in a database of shopping information associated with the customer identification information; and a transmission means for transmitting display information including the accounting code to a mobile device used by the customer when the acquisition means receives the store identification information and the customer identification information.

[0007] One aspect of the control method is a control method executed by a management server, which acquires store identification information indicating the store where a customer has entered and customer identification information indicating the customer, and if unsettled payment information associated with the acquired customer identification information exists in a database of shopping information associated with the customer identification information, generates an accounting code based on the payment information, and when the store identification information and the customer identification information are received, sends display information including the accounting code to a mobile device used by the customer.

[0008] One aspect of the program is a program that causes a computer to function as: an acquisition means for acquiring store identification information indicating the store where a customer has entered and customer identification information indicating the customer; a generation means for generating an accounting code based on the payment information if unsettled payment information associated with the customer identification information acquired by the acquisition means exists in a database of shopping information associated with the customer identification information; and a transmission means for transmitting display information including the accounting code to a mobile device used by the customer when the acquisition means receives the store identification information and the customer identification information. [Effects of the Invention]

[0009] According to the present invention, if the shopping information generated before the customer left the store is stored in the database, the mobile device used by the customer can display information based on that shopping information, allowing the customer to smoothly resume shopping. [Brief explanation of the drawings]

[0010] [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 an example of a flowchart showing a detailed procedure of a store entry process including how to deal with a customer who temporarily leaves the store without making a payment. [Figure 15] 10 is an example of a store barcode reading screen. [Figure 16] This is an example of a screen displayed by the dedicated app after reading the store barcode when there is a list of unpaid purchases from the same store as the entered store. [Figure 17] This is an example of a screen displayed by the dedicated app after reading the store barcode when there is unsettled payment information at the same store as the entered store. [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

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

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

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

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

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

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

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

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

[0019] (2) Device 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.

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

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

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

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

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

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

[0026] 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, a purchased product list DB 29, and a payment information DB 30.

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

[0028] 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), the planned purchase quantity of the item, and the selling price of the item. The purchased item list recorded in the purchased item list DB29 is associated with information identifying the mobile terminal 3 or the customer who uses the mobile terminal 3 (also referred to as "customer identification information") and identification information of the store 8 where the customer is shopping (also referred to as "store ID"). The customer identification information may be any information that can uniquely identify a customer, and may be the card number of a membership card issued 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.

[0029] The payment information DB30 is a database of payment information that is generated when a checkout request is received from the mobile terminal 3 of a customer who is shopping at the store 8. The payment information includes, for example, the total payment amount calculated based on the purchase list at the time the checkout request is received from the mobile terminal 3, and details such as the IDs, quantities, and sales prices of all purchased items included in the purchase list. The payment information recorded in the payment information DB30 is associated with the customer identification information of the customer who is shopping and the store ID where the shopping is being done.

[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 is located within 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 performed by the control unit 25 will be described later. The control unit 25 functions as an acquisition unit, extraction unit, transmission unit, update unit, selling price determination unit, and a computer that executes programs.

[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 40.

[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 and functions as a transmitter and a receiver. 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. The controls 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 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, a card information DB 48, and a purchase history DB 49.

[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 number of 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 determine 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 process 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) Overview of store entry processing First, an overview of the store entry process will be explained. The store entry process is a process that is carried out 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 carried out by the mobile terminal 3 and the management server 2. Note that the store entry process that takes into consideration the presence of customers who have left the store 8 without paying for their purchase list and then re-entered the store is described in "(4) Store entry process details This is explained in more detail in the " section.

[0049] First, when a customer enters a store 8, the customer reads a store barcode using the mobile terminal 3 (step S101). The store barcode is a one-dimensional or two-dimensional barcode that indicates a store ID. The barcode is attached to a predetermined location within the store 8, such as a wall near the store entrance or a shopping cart. When a customer reads the store barcode, the mobile terminal 3 acquires a store ID from the read store barcode and transmits the acquired store ID to the management server (step S102). When transmitting the store ID, the mobile terminal 3 also transmits 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 transmits any information to the management server 2, it also transmits customer identification information that identifies itself.

[0050] The management server 2 receives the store ID and customer identification information from the mobile terminal 3 (step S103). Then, the management server 2 references the selling price change information 27 and the product information DB 28 to acquire a price list for the target store 8 (step S104). The selling price list is a list of product prices that will be applied at the time of processing in step S104 when purchasing a product at the target store 8. Generally, product prices vary from store to store. Here, the selling price list acquired in step S104 reflects price changes due to discounts or discounts indicated in the selling price change information 27. The management server 2 then transmits store information, including the store name and sales information for 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 for that store are displayed on the display unit 31 of the mobile terminal 3, allowing the customer to start shopping. The store information sent by the management server 2 includes information indicating the customer's transaction status at the store, and when the customer starts shopping at the store for the first time, the transaction status becomes "new." On the other hand, if the customer stops shopping at the store for some reason, a purchased product list screen or the like corresponding to the transaction status up to that point 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 product quantity 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). Here, if the purchased product list for the target customer is not registered in the purchased product list DB29, the management server 2 registers the purchased product list, which includes the received product identification information as an element, in the purchased product list DB29 in association with the customer identification information of the target customer.

[0053] The mobile terminal 3 receives the updated purchased item list and displays it on the display unit 31 (step S205). As a result, the newly added items and their quantities are added to the purchased item list and displayed on the mobile terminal 3.

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

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

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

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

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

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

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

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

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

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

[0064] 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 item list (step S303). The management server 2 then generates payment information including the calculated payment amount, and stores the generated payment information in the payment information DB 30 in association with customer identification information identifying the target customer and the store ID identifying the store where the shopping is taking place (step S304). Furthermore, in step S304, the management server 2 generates a payment barcode based on the generated payment information. The payment barcode is information that uniquely identifies the purchase indicated by the current purchase item list. In one example, the payment barcode is a one- or two-dimensional barcode that indicates a number (called an "inquiry number") uniquely associated with the target payment information. The management server 2 transmits to the mobile terminal 3 display information for the payment screen, including the payment amount calculated in step S303 and the accounting barcode generated in step S304 (step S305).

[0065] The mobile device 3 receives the payment screen display information and displays the payment screen on the display unit 31 based on the received display information (Step S306). Figure 12 shows 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 of all purchased items in the purchase list, such as the IDs, quantities, and sales prices. The payment machine 5 displays the payment method selection screen based on the obtained payment information.

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

[0067] When the payment is completed, the payment machine 5 sends a payment completion notice to the management server 2 (step S310). In this case, the payment completion notice includes, for example, an inquiry number for identifying the payment information. In this case, the management server 2 receives the payment completion notice from the payment machine 5 and updates the database stored in the memory unit 23 (step S311). In this case, the management server 2 deletes the payment information for which the payment has been completed, which is identified by the payment completion notice, from the payment information DB 30. The management server 2 also deletes from the purchase item list DB 29 the purchase item list corresponding to the customer identification information and store ID associated with the payment information to be deleted.

[0068] After notifying the management server 2 that the payment is complete, the payment device 5 displays a payment completion screen (step S312). 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 is complete. When the customer presses the end button 66, the payment device 5 reports the payment completion to the management server 2 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 the payment completion to the management server 2 and returns the display unit 31 to the main menu.

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

[0070] (4) Store entry process details Next, details of the store entry process will be described, taking into consideration the presence of customers who have left the store 8 without paying for their purchase list and then re-entered the store. (4-1) Overview When the management server 2 receives the store ID and customer identification information transmitted by the mobile terminal 3 by scanning the store barcode, it determines whether there is an unpaid purchase item list or payment information associated with the store ID and customer identification information. If there is an unpaid purchase item list or payment information (collectively referred to as "shopping information"), the management server 2 transmits display information based on the existing unpaid shopping information to the mobile terminal 3. In this case, the mobile terminal 3 redisplays the payment screen or purchase item list screen that was displayed immediately before the customer left the store 8 based on the display information received from the management server 2. This allows the management server 2 to smoothly resume shopping for a customer who temporarily left the store 8 without making a payment. Furthermore, the mobile terminal 3 may set the selling price of the product in this case to the selling price based on the price before the customer left the store 8, or the selling price based on the price at the time of re-entering the store 8, or it may set the selling price to the lower of these two.

[0071] (4-2) Processing flow 14 is an example of a flowchart showing detailed processing procedures for store entry processing, including how to deal with a customer who temporarily leaves the store 8 without making a payment. The management server 2 repeatedly executes the processing of the flowchart shown in FIG.

[0072] First, the management server 2 determines whether or not it has received a store ID and customer identification information from the portable terminal 3 that read the store barcode (step S401). If the management server 2 has received the store ID and customer identification information from the portable terminal 3 that read the store barcode (step S401; Yes), it acquires a sales price list for the store indicated by the received store ID (step S402). On the other hand, if the management server 2 has not received the store ID and customer identification information from the portable terminal 3 that read the store barcode (step S401; No), the management server 2 continues to make the determination in step S401. Steps S401 and S402 correspond to steps S103 and S104, respectively, in the flowchart of FIG. 8, which shows an overview of the store entry process.

[0073] Next, the management server 2 determines whether there is any outstanding payment information at the same store 8 where the target customer entered (step S403). In this case, the management server 2 determines whether payment information associated with the store ID and customer identification information received in step S401 is registered in the payment information DB 30. If there is outstanding payment information at the same store for the target customer (step S403; Yes), the management server 2 generates a transaction barcode based on the payment information (step S404). The management server 2 then sends display information for a payment screen to the mobile terminal 3, including the payment amount indicated in the payment information and the transaction barcode generated in step S404 (step S405). This allows the management server 2 to display a payment screen including the transaction barcode on the mobile terminal 3 for a customer who temporarily leaves the store 8 without making a payment after the transaction barcode was issued, allowing for a smooth transaction. That is, in this case, even if the customer leaves the shopping cart at a service counter or the like and temporarily leaves the store 8, there is no need to perform operations such as reading the product barcodes of the products in the shopping cart again after re-entering the store 8. After determining in step S403 that there is unsettled payment information for the target customer at the same store, the management server 2 may accept an input from the customer to select whether or not to carry over the unsettled payment information. An example of this display will be described later.

[0074] On the other hand, if there is no payment information for an unpaid purchase at the same store for the target customer (step S403; No), the management server 2 determines whether there is a purchase list for an unpaid purchase at the same store for the target customer (step S406). In this case, the management server 2 determines whether a purchase list associated with the store ID and customer identification information received in step S401 is registered in the purchase list DB29. If there is a purchase list for an unpaid purchase at the same store for the target customer (step S406; Yes), the management server 2 extracts the purchase list from the purchase list DB29 and transmits the extracted purchase list, etc. to the mobile terminal 3 (step S407). Specifically, the management server 2 transmits display information for displaying a purchase list screen showing the purchase list extracted from the purchase list DB29 to the target mobile terminal 3. This allows the management server 2 to allow a customer who temporarily leaves the store 8 for some reason with an unpaid purchase list to continue shopping in the state they were in immediately before leaving. In this case, the customer does not need to perform operations such as reading the product barcodes of the products they put in their shopping cart again after re-entering store 8. After determining in step S406 that there is a list of unpaid purchases for the target customer at the same store, management server 2 may accept an input from the customer to select whether or not to continue the list of unpaid purchases. An example of this display will be described later.

[0075] On the other hand, if there is no list of unpaid purchases at the same store 8 that the target customer entered (step S406; No), the management server 2 determines that there is no unpaid shopping information at the store 8 that the target customer entered, and sends the store information to the target mobile terminal 3 (step S408). The processing of step S408 corresponds to step S105 in the flowchart of Fig. 8 that shows an overview of the store entry processing.

[0076] In steps S403 and S406 described above, the management server 2 determines whether there is any unpaid shopping information based on the store ID transmitted from the mobile terminal 3 upon entering the store, in addition to the customer identification information. This allows the management server 2 to effectively prevent a customer who has unpaid shopping information from one store from fraudulently transferring that shopping information even when that customer enters another store. The management server 2 can also appropriately determine whether a customer who has unpaid shopping information from multiple stores will re-enter each store. The management server 2 can then effectively display on the mobile terminal 3 a purchase item list screen or a payment screen based on the unpaid shopping information corresponding to the store where the customer re-enters.

[0077] Here, a supplementary explanation will be given of the method for determining the selling price of each purchased product to be displayed on the purchased product list screen in step S407.

[0078] In a first example, the management server 2 sets the selling price of each purchased item to be displayed on the purchased item list screen in step S407 to the selling price of each purchased item included in the purchased item list extracted from the purchased item list DB 29. That is, in this case, the selling price of each purchased item displayed on the purchased item list screen is the selling price of each purchased item indicated in the selling price list of store 8 (referred to as the "old selling price list") that the management server 2 acquired in step S402 when the target customer entered the store before re-entering. Note that in this case, the management server 2 does not update the purchased item list extracted from the purchased item list DB 29.

[0079] In the second example, the management server 2 determines the selling price of each purchased item to be displayed on the purchased item list screen in step S407 based on the selling price list of the store 8 acquired in the previous step S402 (referred to as the "new selling price list"). In this case, the management server 2 updates the selling price information for each purchased item in the purchased item list extracted from the purchased item list DB29.

[0080] In a third example, the management server 2 determines the selling price of each purchased item to be displayed on the purchased item list screen in step S407 based on both the old selling price list and the new selling price list. In this case, for example, the management server 2 sets the selling price of a purchased item whose selling price differs between the old selling price list and the new selling price list to the lower of these selling prices. Then, based on the determined selling prices of each purchased item, the management server 2 updates the selling price information for each purchased item in the purchased item list extracted from the purchased item list DB29.

[0081] Similarly, management server 2 calculates the payment amount to be displayed on the payment screen in step S405 using the selling prices of each purchased item determined based on either the old selling price list or the new selling price list, or both. Furthermore, if the payment amount indicated by the payment information extracted from payment information DB30 differs from the calculated payment amount, management server 2 updates the payment information extracted from payment information DB30 based on the calculated payment amount.

[0082] (4-3) Screen example Next, specific examples of screens displayed by the mobile terminal 3 (FIGS. 15 to 17) will be described in detail with reference to the flowchart of FIG.

[0083] Fig. 15 is an example of a store barcode reading screen displayed on the mobile terminal 3. In the example of Fig. 15, a customer enters the store 8 and starts a dedicated app on the mobile terminal 3, causing the screen shown in Fig. 15 to be displayed on the mobile terminal 3.

[0084] 15, the mobile terminal 3 displays a window 70 showing a message instructing the user to start shopping by reading a store barcode provided near the entrance of the store 8, and a start reading button 71. When the mobile terminal 3 detects that the start reading button 71 has been selected, it activates the reading unit 36 ​​and starts reading the store barcode provided near the entrance of the store 8. When the mobile terminal 3 acquires a store ID by reading the store barcode with the reading unit 36, it transmits the acquired store ID and customer identification information of the customer using the mobile terminal 3 to the management server 2. Thereafter, in step S401, the management server 2 determines that it has received the store ID and customer identification information from the mobile terminal 3, and proceeds to step S402.

[0085] FIG. 16 is an example of a screen displayed by a dedicated app on the mobile terminal 3 after reading the store barcode when there is a list of unpaid purchase items from the same store 8 that the customer has entered.

[0086] In this case, in step S406 of FIG. 14, the management server 2 determines that, for the customer of the mobile terminal 3 that transmitted the store ID and customer identification information, a list of unpaid purchases from the same store as the store indicated by the store ID is recorded in the purchase item list DB29. The management server 2 then pops up a window 72 on the mobile terminal 3 to prompt the customer to select whether or not to continue shopping using the unpaid purchase item list. The window 72 includes a first button 73 for selecting to continue shopping using the unpaid purchase item list (i.e., the purchase item list immediately before leaving the store 8), and a second button 74 for selecting to make a new purchase. When the management server 2 detects that the first button 73 has been selected, it then transmits display information for the purchase item list associated in the purchase item list DB29 with the target customer identification information and store ID to the target mobile terminal 3 based on step S407 of FIG. 14. As a result, the management server 2 displays on the mobile terminal 3 a purchase item list screen showing the list of purchased items immediately before leaving the store 8, allowing the customer to resume shopping from the state immediately before leaving the store 8. Therefore, even if the customer leaves the shopping cart at a service counter or the like and temporarily leaves the store 8 for some reason, the customer can resume shopping from the state immediately before leaving the store 8 by scanning the store barcode when entering the store 8.

[0087] Furthermore, when the management server 2 detects that the second button 74 has been selected, it determines that the transaction for the unsettled purchase item list should be canceled, and deletes the target purchase item list from the purchase item list DB 29, just as when the transaction cancel button 96 is selected on the purchase item list screen in Fig. 10. After that, when the management server 2 receives product identification information from the target mobile terminal 3 in response to the product selection process shown in Fig. 9, it registers a new purchase item list associated with the target customer identification information and store ID in the purchase item list DB 29.

[0088] FIG. 17 is an example of a screen displayed by a dedicated app on the mobile terminal 3 after reading the store barcode when there is payment information for an outstanding transaction at the same store.

[0089] In this case, in step S403 of FIG. 14, the management server 2 determines that the payment information DB 30 contains unsettled payment information for the same store identified by the store ID for the customer of the mobile device 3 that transmitted the store ID and customer identification information. The management server 2 then pops up a window 75 on the mobile device 3, prompting the customer to select whether or not to display a transaction barcode based on the payment information. The window 75 includes a third selection button 76 for selecting whether to display the transaction barcode based on the unsettled payment information and a fourth button 77 for selecting to make a new purchase. If the management server 2 detects that the third selection button 76 has been selected, it generates a transaction barcode to identify the unsettled payment information in step S404 of FIG. 14. In step S405 of FIG. 14, the management server 2 then sends display information for a payment screen (see FIG. 12) showing the generated transaction barcode to the mobile device 3. The mobile device 3 then displays a payment screen based on the list of items purchased immediately before the customer left the store 8. This means that even if a customer leaves the shopping cart at a service counter or the like and temporarily leaves the store 8 after the payment screen is displayed, the customer can resume shopping from the state just before leaving the store 8 by scanning the store barcode when entering the store 8.

[0090] Furthermore, when the management server 2 detects that the fourth button 77 has been selected, it determines that the transaction for the unsettled payment information should be canceled and deletes the payment information from the payment information DB 30. The management server 2 also deletes the purchase item list corresponding to the deleted payment information from the purchase item list DB 29. Thereafter, when the management server 2 receives product identification information from the target mobile terminal 3 in response to the product selection process shown in FIG. 9, it registers a new purchase item list in the purchase item list DB 29 associated with the target customer identification information and store ID based on the received product identification information.

[0091] (4-4) Handling temporary termination of the dedicated app Next, we will provide additional information on how to handle the termination of the dedicated app when a customer temporarily leaves the facility.

[0092] Even when the management server 2 detects that the dedicated app on the mobile terminal 3 used by a customer for whom there is unpaid shopping information has been terminated, the management server 2 retains the unpaid shopping information without erasing it from the database. Specifically, when the management server 2 determines that the dedicated app on the mobile terminal 3 has been terminated, the management server 2 continues to store the purchase item list of the target customer in the purchase item list DB29 without deleting it from the purchase item list DB29. Similarly, when payment information of the target customer exists, the management server 2 continues to store the payment information DB30 without deleting it from the payment information DB30. In this case, for example, the management server 2 may add flag information indicating that the dedicated app has been terminated to the purchase item list and payment information of the target customer.

[0093] Generally, when a customer temporarily leaves the store 8, they close the dedicated app and leave the store 8 with unpaid shopping information remaining, and when they return to the store 8, they restart the dedicated app to read the store barcode and register purchased items. Taking the above into consideration, even when the dedicated app is closed due to the customer's temporary exit from the store 8, the management server 2 retains the unpaid shopping information without deleting it from the database. This allows the management server 2 to suitably retain information necessary to re-display the payment screen or purchased item list screen that was displayed on the mobile terminal 3 immediately before the customer left the store 8, and to generate display information for the payment screen or purchased item list screen described above.

[0094] The management server 2 determines that the dedicated app has terminated, for example, when the communication connection established with the dedicated app of 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. The 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 (for example, an incoming call) or freezing of the dedicated app. Examples of the dedicated app being terminated 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.

[0095] (4-5) 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.

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

[0097] 18, the management server 2 detects a user input indicating that an order is to be placed based on past purchase history, and extracts purchase history information indicating multiple purchases associated with the customer identification information of the customer using the mobile terminal 3 from the purchase history DB 49. The management server 2 then generates a purchase history list 78 based on the purchase history information extracted from the purchase history DB 49, and displays the generated purchase history list 78 on the mobile terminal 3. Here, the purchase history list 78 has multiple elements corresponding to the 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 constituting the purchase history list 78 is provided with a detail display button 79A to 79D (79) for displaying the respective detailed purchase history.

[0098] The customer using the mobile terminal 3 then refers to the purchase history list 78 and selects the detail display button 79 corresponding to the purchase history they wish to view in this e-commerce transaction. In this case, the management server 2 causes the mobile terminal 3 to display a purchase history detail screen corresponding to the selected detail display button 79. The detail screen may display, for example, a purchase product list, which is a list of purchased products. Furthermore, the management server 2 preferably 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 terminal 3, and may be any terminal, such as a desktop computer used by the customer.

[0099] (4-6) Notification output The management server 2 may cause the mobile terminal 3 to output a notification when an abnormal state in an unsettled transaction is detected.

[0100] In a first example, when the dedicated app is terminated while there is unpaid shopping information, the management server 2 may output a notification to the mobile terminal 3 at predetermined time intervals until the dedicated app is restarted, indicating that there is unpaid shopping information. For example, the management server 2 may send notification information to the mobile terminal 3 indicating that there is an unpaid purchase item list, and use a push notification function to display the notification information on the screen of the mobile terminal 3. In this way, the management server 2 notifies the customer of the existence of an unpaid purchase item list or payment information, and prompts the customer to resume shopping and make payment in an appropriate manner.

[0101] In a second example, if the list of unpaid purchased items is not updated for a predetermined time or more, the management server 2 may output a notification to the mobile terminal 3 that there is a list of unpaid purchased items. In a third example, if the payment is not made even after a predetermined time or more has passed since the payment information was generated (if a payment completion notification is not received from the cash register 5), the management server 2 may output a notification to the mobile terminal 3 that the payment is not completed.

[0102] In a fourth example, when the management server 2 detects that the mobile device 3 has left the store 8 with unpaid purchases, the management server 2 may cause the mobile device 3 to output a notification regarding the list of unpaid purchases. In this case, for example, the management server 2 acquires location information transmitted from the mobile device 3 and determines whether the location indicated by the location information is within the area of ​​the store 8. The location information may be based on GPS radio waves, radio waves from a beacon terminal, or radio waves from a wireless LAN. The location information indicating the area of ​​the store 8 may be stored in advance in the storage unit 23, for example. In this case, the management server 2 may further transmit information to a terminal used by a store clerk of the store 8 notifying the store clerk that a customer with an unpaid purchase list 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 customer in the information transmitted to the terminal used by the store clerk. This allows the management server 2 to conveniently notify the store clerk or other personnel of the store 8 of the presence of a customer who has left the store 8 without paying.

[0103] In this way, the management server 2 may prompt the customer of the mobile terminal 3 to complete the payment by outputting a notification to the mobile terminal 3 when various abnormal states in an unsettled payment are detected.

[0104] (4-7) Variations In step S401 of Figure 14, the management server 2 detects a customer's visit to the store 8 indicated by the store ID by receiving the store ID, etc. from the mobile terminal 3 that read the store barcode, but the method by which the management server 2 detects a customer's visit is not limited to this.

[0105] For example, the management server 2 may detect a customer's visit to the store 8 identified by the store ID by receiving from the mobile terminal 3 a store ID or the like that indicates the store specified by user input. In this case, for example, when the mobile terminal 3 starts up a dedicated app, it displays an input screen for specifying the store where the shopping will be performed, and transmits the store ID that indicates the store specified by user input on the input screen together with customer identification information to the management server 2. Then, when the management server 2 receives the store ID and customer identification information from the mobile terminal 3, it proceeds to step S402 in FIG.

[0106] In another example, the management server 2 receives location information of the mobile terminal 3 based on radio waves from a GPS, a beacon terminal, or wireless LAN from the mobile terminal 3, and compares it with pre-stored location information indicating the area of ​​each store 8. Then, when the management server 2 determines that the mobile terminal 3 has entered the area of ​​any store 8, it performs processing from step S402 onwards based on the store ID of that store and the customer identification information of the customer using the mobile terminal 3.

[0107] In these examples, management server 2 can also appropriately recognize the store 8 that the customer has entered and accurately determine whether there is any shopping information for which payment has not yet been made at that store 8. Similarly, management server 2 may acquire customer identification information of a customer who has entered store 8 by performing biometric authentication such as facial recognition on the customer based on the output of a sensor such as a camera installed in store 8. In this case, management server 2 identifies the customer identification information of the customer who has entered the store through biometric authentication by referring to a database that associates feature information (authentication information) obtained by biometric authentication for each customer with customer identification information. This database may be stored in management server 2 or in another device that can communicate with management server 2.

[0108] Second Embodiment 19 shows a schematic configuration of a management server 2A in the second embodiment. The management server 2A includes an acquisition unit 81, an extraction unit 82, and a transmission unit 83.

[0109] The acquisition unit 81 acquires store identification information indicating the store where the customer entered and customer identification information indicating the customer. The acquisition unit 81 is realized, for example, by the control unit 25 that controls the communication unit 24 in the first embodiment. The store identification information is, for example, the store ID in the first embodiment. The acquisition unit 81 may acquire the store identification information and the customer identification information based on step S401 in FIG. 14, or may acquire the store identification information and the customer identification information based on the above-mentioned "(4-7) Modified Example."

[0110] If shopping information "S1" associated with the store identification information and customer identification information acquired by the acquisition unit 81 exists in a database 84 of unpaid shopping information associated with the store identification information and customer identification information, the extraction unit 82 extracts the shopping information S1 from the database 84. The extraction unit 82 is realized, for example, by the control unit 25 in the first embodiment. The database 84 corresponds, for example, to at least one of the purchased item list DB29 and the payment information DB30 in the first embodiment.

[0111] The transmitting unit 83 transmits the display information "S2" based on the shopping information S1 extracted by the extracting unit 82 to the mobile terminal 3A used by the customer. The mobile terminal 3A is, for example, the mobile terminal 3 in the first embodiment. The transmitting unit 83 is realized, for example, by the control unit 25 that controls the communication unit 24 in the first embodiment.

[0112] In this way, when the management server 2A according to the second embodiment detects that a customer with pending shopping information has entered the same store, it transmits display information S2 based on the pending shopping information to the mobile terminal 3A. This allows the customer to smoothly continue shopping when they return to the store, even if they temporarily leave the store in the middle of shopping.

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

[0114] [Appendix 1] an acquisition unit that acquires, when a customer enters a store where a product is purchased using a mobile terminal, store identification information that indicates the store that the customer entered and customer identification information that indicates the customer; an extraction unit that extracts, when shopping information associated with the store identification information and the customer identification information acquired by the acquisition unit exists in a database of unpaid shopping information associated with the store identification information and the customer identification information, the shopping information from the database; a transmitting unit that transmits display information based on the shopping information extracted by the extracting unit to a mobile terminal used by the customer; A management server having:

[0115] [Appendix 2] The shopping information includes a purchase item list, which is a list of items to be purchased; The management server described in Appendix 1, wherein the transmission unit transmits to the mobile terminal display information for displaying a purchased item list associated in the database with the store identification information and the customer identification information acquired by the acquisition unit.

[0116] [Appendix 3] The shopping information includes payment information indicating at least the amount to be paid for the product to be purchased; the transmitting unit transmits to the mobile terminal barcode display information that allows the payment machine to identify payment information associated in the database with the store identification information and the customer identification information acquired by the acquiring unit.

[0117] [Appendix 4] The management server according to any one of appendices 1 to 3, further comprising an update unit that, if the database does not contain shopping information associated with the store identification information and the customer identification information acquired by the acquisition unit, adds to the database shopping information generated based on product identification information received from the mobile terminal, which is identification information indicating a product to be purchased at the store, in association with the store identification information and the customer identification information acquired by the acquisition unit.

[0118] [Appendix 5] The management server described in any one of Appendices 1 to 4 has an update unit that, when it is determined that the payment by the customer has been completed, deletes from the database shopping information associated with customer identification information indicating the customer and store identification information indicating the store where the payment was made.

[0119] [Appendix 6] The management server described in any one of Appendices 1 to 5 further comprises a selling price determination unit that, when it is determined that shopping information associated with the store identification information and the customer identification information acquired by the acquisition unit exists in the database, determines the selling price of the product to be purchased indicated by the shopping information based on the selling price of the product at the store at the time it is determined that the shopping information exists in the database.

[0120] [Appendix 7] The management server described in Appendix 6, wherein the selling price determination unit determines the selling price of the product to be purchased indicated by the shopping information to be the lower of the selling price of the product at the store at the time it is determined that the shopping information exists in the database and the selling price of the product at the store at the time the shopping information is generated.

[0121] [Appendix 8] The management server described in any one of Appendices 1 to 7 further has a storage unit that, when it detects the termination of an application on the mobile terminal used for the shopping when there is unpaid shopping information associated with the customer's customer identification information in the database, stores the shopping information in the database until it detects that the application is restarted.

[0122] [Appendix 9] A management server according to any one of Supplementary Notes 1 to 8; A management system having a mobile terminal used by a customer, The mobile terminal a transmitting unit that, when the customer enters a store where a product is purchased using a mobile terminal, transmits to the management server store identification information that indicates the store that the customer entered and customer identification information that indicates the customer; a receiving unit that receives display information based on the shopping information transmitted by the transmitting unit when the shopping information associated with the store identification information and the customer identification information transmitted by the transmitting unit exists in a database of unpaid shopping information associated with the store identification information and the customer identification information; a display unit that performs display based on the display information; A management system having:

[0123] [Appendix 10] A control method executed by a management server, comprising: When a customer enters a store where a product is purchased using a mobile terminal, store identification information indicating the store where the customer entered and customer identification information indicating the customer are acquired; If the shopping information associated with the acquired store identification information and customer identification information exists in a database of unpaid shopping information associated with the store identification information and customer identification information, the shopping information is extracted from the database; A control method in which display information based on the shopping information is sent to a mobile terminal used by the customer.

[0124] [Appendix 11] an acquisition unit that acquires, when a customer enters a store where a product is purchased using a mobile terminal, store identification information that indicates the store that the customer entered and customer identification information that indicates the customer; an extraction unit that extracts, when shopping information associated with the store identification information and the customer identification information acquired by the acquisition unit exists in a database of unpaid shopping information associated with the store identification information and the customer identification information, the shopping information from the database; A program that causes a computer to function as a transmission unit that transmits display information based on the shopping information extracted by the extraction unit to a mobile terminal used by the customer.

[0125] 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]

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

Claims

1. an acquisition means for acquiring store identification information indicating a store where a customer has entered and customer identification information indicating the customer; a generating means for generating an accounting code based on unsettled payment information associated with the customer identification information acquired by the acquiring means when the unsettled payment information associated with the customer identification information exists in a database of shopping information associated with the customer identification information; a transmitting means for transmitting display information including the accounting code to a mobile terminal used by the customer when the acquiring means receives the store identification information and the customer identification information; A management server having:

2. The method further includes receiving means for receiving information indicating whether or not to take over the outstanding payment information, 2. The management server according to claim 1, wherein said generating means generates an accounting code based on said payment information when said receiving means receives information indicating a selection to carry over said unsettled payment information.

3. The shopping information includes a purchase item list, which is a list of items to be purchased; 3. The management server according to claim 1, wherein the transmitting means transmits to the mobile terminal display information of a purchased product list associated in the database with the customer identification information acquired by the acquiring means.

4. The management server according to any one of claims 1 to 3, further comprising an update means for, if the database does not contain shopping information associated with the store identification information and the customer identification information acquired by the acquisition means, adding to the database shopping information, which is identification information indicating a product to be purchased at the store and which is generated based on product identification information received from the mobile terminal, in association with the store identification information and the customer identification information acquired by the acquisition means.

5. A management server as described in any one of claims 1 to 4, further having a storage means for storing shopping information in the database when the termination of an application on the mobile terminal used for shopping is detected while there is unpaid shopping information associated with the customer's customer identification information in the database, until the restart of the application is detected.

6. A management server according to any one of claims 1 to 5; A management system having a mobile terminal used by a customer, The mobile terminal a transmitting means for transmitting store identification information indicating the store where the customer entered and customer identification information indicating the customer to the management server; a receiving means for receiving, from the management server, display information including an accounting code based on unsettled payment information associated with the customer identification information transmitted by the transmitting means, when the unsettled payment information associated with the customer identification information transmitted by the transmitting means exists in a database of shopping information associated with the customer identification information; a display means for displaying the accounting code based on the display information; A management system having:

7. A control method executed by a management server, comprising: Obtain store identification information indicating the store where the customer entered and customer identification information indicating the customer; If there is unsettled payment information associated with the acquired customer identification information in a database of shopping information associated with the customer identification information, an accounting code is generated based on the payment information; a control method for transmitting, when the store identification information and the customer identification information are received, display information including the accounting code to a mobile terminal used by the customer;

8. an acquisition means for acquiring store identification information indicating a store where a customer has entered and customer identification information indicating the customer; a generating means for generating an accounting code based on unsettled payment information associated with the customer identification information acquired by the acquiring means when the unsettled payment information associated with the customer identification information exists in a database of shopping information associated with the customer identification information; a transmitting means for transmitting, when the acquiring means receives the store identification information and the customer identification information, display information including the accounting code to a mobile terminal used by the customer; A program that makes a computer function as a

Images