JP2023181380A - Management server, management system, control method, and storage medium - Google Patents

Abstract

To provide a management server, a management system, a control method, and a program that can smoothly re-register membership cards.SOLUTION: A management server 2A includes a receiving unit 81, an extracting unit 82, and an updating unit 83. The receiving unit 81 receives a registration request S1 including the card number of a membership card from a terminal device 3A used by a member. The extracting unit 82 extracts member information corresponding to a target member from a database of member information for each member. If the card number indicated by the extracted member information and the card number included in the registration request S1 are different, the updating unit 83 updates the member information using the card number included in the registration request S1.SELECTED DRAWING: Figure 18

Description

The present invention relates to updating member information.

As a product sales system for customers who visit a store to purchase products, there is a known system in which the customer uses a mobile terminal such as a smartphone owned by the customer to read the barcode of the product, register the product, and make payment. There is. For example, Patent Document 1 describes a mobile terminal that acquires product information of a product to be purchased and sends payment information including all the acquired product information to a management server, and A self-shopping system is disclosed that includes a management server that generates and outputs sorting detail information in which product names are listed in descending order of price.

In addition, Patent Document 2 discloses that, based on payment identification information that identifies a payment and card identification information that identifies a point card, a customer who receives a service using a point card is notified of the occurrence of a past payment using a credit card or electronic money. A system for awarding points is disclosed.

Japanese Patent Application Publication No. 2013-41354 Japanese Patent Application Publication No. 2018-055564

In recent years, there have been systems that provide services that link dedicated applications and membership cards such as point cards. This type of service has the advantage of being able to check your points and other points using a dedicated application, but if you lose your membership card, it is necessary to uninstall the application and re-register as a member. Patent Document 2 discloses a method for smoothly adding points, but does not disclose a method for re-registering a membership card such as a point card when the membership card is lost.

An object of the present invention is to provide a management server, a management system, a control method, and a storage medium that allow smooth re-registration of membership cards.

One aspect of the management server is a management server, which includes a receiving unit that receives a registration request including a card number of a membership card from a terminal device used by a member, and a reception unit that receives member information corresponding to the member. If a card number different from the card number included in the registration request is not registered in the member information, an extraction means for extracting from the database does not update the member information and updates the card number indicated by the member information and the registration request. and updating means for updating the member information with the card number included in the registration request if the card number included in the request is different.

One aspect of the control method is a control method executed by a management server, in which a registration request including a card number of a membership card is received from a terminal device used by a member, and member information corresponding to the member is sent to the member. If extracted from the information database and a card number different from the card number included in the registration request is not registered in the member information, the member information is not updated and the card number indicated by the member information and the registration request are If the card number included in the registration request is different from the card number included in the registration request, the member information is updated using the card number included in the registration request.

One aspect of the program includes a receiving means for receiving a registration request including a card number of a membership card from a terminal device used by a member, and an extracting means for extracting member information corresponding to the member from a member information database. , if a card number different from the card number included in the registration request is not registered in the member information, the member information is not updated and the card number indicated by the member information and the card number included in the registration request are updated. If the member information is different, the program causes the computer to function as an updating means for updating the member information using the card number included in the registration request.

According to the present invention, it is possible to smoothly re-register a membership card by utilizing existing member information.

1 shows a configuration of a management system according to a first embodiment. A schematic configuration of a POS server is shown. The schematic configuration of the management server is shown. A schematic configuration of a mobile terminal is shown. The schematic configuration of the member server is shown below. The schematic configuration of the accounting machine is shown. It is a flowchart of product purchase processing. It is a flowchart of store entry processing. It is a flowchart of product selection processing. This is a display example of a purchased product list screen. It is a flowchart of accounting processing. This is a display example of a payment method selection screen. This is an example of a display screen of an accounting machine. An example of the data structure of the member information database is shown. An example of the data structure of the card information database is shown. This is a display example of a membership card registration screen. It is an example of a flowchart showing the procedure of card number registration processing. 7 shows a schematic configuration of a management server according to a second embodiment.

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

<First embodiment>
(1) Management system configuration
FIG. 1 shows the configuration of a management system 100 according to this embodiment. The management system 100 mainly includes a POS server 1, a management server 2, a mobile terminal 3, a member server 4, and an accounting machine 5. In the management system 100, a customer using a mobile terminal 3 reads a product barcode 7 attached to a product in a store 8 where the product is sold, thereby purchasing a product (also referred to as a "purchased product"). registration, and make payment using the accounting machine 5 in the store 8 or by electronic payment.

The POS server 1 is a server that manages various sales information such as product information including prices and inventory status of products sold at 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. Note that the POS server 1 may be one that collectively manages sales information of a plurality of affiliated stores, or may be one that exists for each store and manages only the sales information of that store.

The management server 2 is a server device that controls the mobile terminal 3 and the accounting machine 5, and is capable of communicating with the mobile terminal 3, the member server 4, and the accounting machine 5 via a network or the like. The management server 2 acquires information necessary for display control of the mobile terminal 3 from the POS server 1 and stores it. The management server 2 transmits display information for the mobile terminal 3 to display various screens to the mobile terminal 3. The above-mentioned various screens include a screen ("purchased product list screen") that displays a list of purchased products (referred to as "purchased product list") registered by the mobile terminal 3 reading product barcodes 7 together with selling prices. ) is included. The management server 2 also acquires information regarding members from the member server 4 and transmits information for updating information stored in the member server 4 to the member server 4.

Note that the management server 2 may be configured by a plurality of server devices. For example, the management server 2 is a server device that mainly performs interface operations with the mobile terminal 3 such as exchanging data with the mobile terminal 3, and stores and stores various information such as information acquired from the POS server 1 and a list of purchased products. It may also consist of a server device for management. 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 their respective assigned processes via a network or the like.

The mobile terminal 3 is a mobile terminal used by customers shopping at the store 8, and has the function of reading product barcodes 7 attached to products, and various screens such as a purchased product list screen by communicating with the management server 2. It has functions such as acquiring and displaying. Although only one mobile terminal 3 is displayed in FIG. 1 for convenience of explanation, there are actually as many mobile terminals as there are customers entering the store 8.

The member server 4 stores information regarding members and information regarding membership cards issued to members. The member server 4 is capable of communicating with the management server 2 via a network or the like. Note that the management server 2 may function as the member server 4. In this case, the management server 2 stores information related to members and membership cards stored in the member server 4.

The accounting machine 5 is a payment machine (so-called self-payment machine) for a customer to use the mobile terminal 3 to perform payment. The accounting machine 5 is capable of communicating with the management server 2, and exchanges various information necessary for settlement with the management server 2 and, if necessary, with the POS server 1. The checkout machine 5 includes a barcode reader 56 for reading a checkout barcode (described later) from the customer's mobile terminal 3, and a light 57 for calling a store clerk.

(2) Equipment configuration
Next, the configurations of the POS server 1, management server 2, mobile terminal 3, member server 4, and accounting machine 5 will be explained with reference to FIGS. 2 to 6.

(2-1) POS Server FIG. 2 shows a schematic configuration of the POS server 1. The POS server 1 mainly includes a storage section 13, a communication section 14 that performs data communication, and a control section 15. These elements are interconnected by bus lines 10.

The storage unit 13 is composed of a memory such as a hard disk or a flash memory. The storage unit 13 stores a program executed by the control unit 15 and information necessary for the control unit 15 to execute a predetermined process by executing the program. In this embodiment, the storage unit 13 includes selling price change information 17, a product information DB (Database) 18, and sales information 19 that 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, product information DB 18, and sales information 19.

The product information DB 18 is a database of information regarding products handled by the store 8 or affiliated stores including the store 8. The product information DB 18 stores various types of 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. Contains information.

Selling price change information 17 is information regarding changes in selling prices. Specifically, the selling price change information 17 includes classification discount information, bundle discount information, set discount information, total amount discount information, classification discount information, bundle discount information, set discount information, and total amount discount information. It includes at least one of arbitrary discount information or discount information such as.

The control unit 15 includes a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), etc. (not shown), and performs various controls on each component 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. Furthermore, the control unit 15 transmits information regarding the selling price change information 17 and the product information DB 18 to the management server 2 by communicating with the management server 2 via the communication unit 14 .

(2-2) Management Server FIG. 3 shows a schematic configuration of the management server 2. The management server 2 mainly includes a storage section 23, a communication section 24, and a control section 25. Each of these elements is interconnected via a bus line 20.

The storage unit 23 is constituted by a memory such as a hard disk or flash memory. The storage unit 23 stores a program executed by the control unit 25 and information necessary for the control unit 25 to execute a predetermined process by executing the program. In this embodiment, the storage unit 23 stores selling price change information 27, product information DB 28, and purchase product list DB 29.

The selling price change information 27, like the selling price change information 17, is information regarding a discount or a change in the selling price due to a discount. 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 regarding 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.

The purchased product list DB 29 is a database of purchased product lists for each mobile terminal 3 of customers shopping at the store 8 . The purchased product list is, for example, a list that includes product identification information indicating the products to be purchased and the planned purchase quantity of the products, and information that identifies the mobile terminal 3 or the customer using the mobile terminal 3 ("customer identification information"). ). The purchased product list is updated every time a purchased product is added, deleted, or the quantity is changed based on the operation of the mobile terminal 3.

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

(2-3) Mobile Terminal FIG. 4 shows a schematic configuration of the mobile terminal 3. The mobile terminal 3 mainly includes a display section 31, an input section 32, a storage section 33, a communication section 34, a control section 35, and a reading section 36. Each of these elements is interconnected via a bus line 30.

The display unit 31 displays various information such as a purchased product list and accounting barcodes under the control of the control unit 35. The input unit 32 is an interface that receives user input, and includes, for example, a touch panel, a button, a voice input device, and the like.

The storage unit 33 is constituted by a memory such as a hard disk or a flash memory. The storage unit 33 stores a program executed by the control unit 35 and information necessary for the control unit 35 to execute a predetermined process by executing the program. For example, the storage unit 33 stores an application program (hereinafter also referred to as a "dedicated application") provided by the store 8 or a company (organization) that manages the store 8. The dedicated application is activated when shopping at the store 8, and controls the display of various screens such as the purchased product list screen.

The communication unit 34 communicates with the management server 2 by wireless communication. The control unit 35 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on each component within the mobile terminal 3. The control executed by the control unit 35 will be described later.

The reading unit 36 is, for example, an optical device such as a camera, and 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 information output by the reading unit 36.

(2-4) Member Server FIG. 5 shows a schematic configuration of the member server 4. The member server 4 mainly includes a storage section 43, a communication section 44, and a control section 45. Each of these elements is interconnected via a bus line 40.

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

The member information DB 47 is a database of member information that is information for each member who has completed membership procedures. The member information includes, for example, 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 the identification number of the membership card, and the membership card is, for example, a point card that is given by applying to become a member at a counter provided in the store 8. In addition, in order to be granted a membership card, the applicant is required to fill out an application form in which personal information such as a name is written, for example. A card number assigned to the card and a personal identification number (PIN code) for determining the validity of the card number are printed on the membership card. There are two types of members: main members who are regular members who are not subordinate to other members, and family members who are in a subordinate relationship with main members, and membership cards are issued to main members. card, and a family card given to a family member. The main member and the family member share points given according to shopping, etc.

The card information DB 48 is a database regarding membership cards. For example, the card information DB 48 includes a combination of a card number assigned to a member card that can be issued and a password for authenticating the validity of the card number. Further, the card information DB 48 includes information regarding the validity of each membership card. In addition, the card number of the family card that can be issued is associated with the card number of the main membership card that shares points with the family card.

The communication unit 44 communicates with the management server 2 and the like through wired or wireless communication. The control unit 45 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on each component within the member server 4.

(2-5) Accounting Machine FIG. 6 shows a schematic configuration of the accounting machine 5. The accounting machine 5 mainly includes a display section 51, an input section 52, a storage section 53, a communication section 54, a control section 55, a barcode reader 56, a light 57, and a speaker 58. Each of these elements is interconnected via a bus line 50.

The display unit 51 displays various information such as a payment method selection screen and an end screen under the control of the control unit 55. The input unit 52 is an interface that accepts customer input, and includes, for example, a touch panel, buttons, and the like.

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

The control unit 55 includes a CPU, ROM, RAM, etc. (not shown), and performs various controls on each component within the accounting machine 5. The control executed by the control unit 55 will be described later. The barcode reader 56 reads the checkout barcode displayed on the customer's mobile terminal 3 at the time of checkout, and supplies the read information to the control unit 55. The light 57 is turned on when a malfunction occurs in the checkout machine 5 or when a clerk is called. The speaker 58 outputs operation sounds, voice messages, etc. to call attention as necessary.

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

(3-1) Store Entry Process First, the store entry process will be explained. 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 illustrating an example of store entry processing. This process is performed by the mobile terminal 3 and the management server 2.

First, upon entering the store 8, the customer reads the store barcode using the mobile terminal 3 (step S101). The store barcode is affixed to a predetermined location within the store 8, such as a wall near the entrance of the store or a card used for shopping. When the customer reads the store barcode, the mobile terminal 3 acquires the store ID from the read store barcode and transmits it to the management server (step S102). When transmitting the store ID, the mobile terminal 3 also transmits customer identification information for identifying the mobile terminal 3 or the customer using the mobile terminal 3. In addition, also in the product selection process and accounting process described below, when the mobile terminal 3 basically transmits some information to the management server 2, it also transmits customer identification information for identifying itself.

The management server 2 receives the store ID from the mobile terminal 3, and acquires the selling price list of the store from the product information DB 28 (step S104). This is because the selling prices of products differ from store to store. Then, the management server 2 transmits store information including the store name and sale information of the 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, sale information, etc. of the store are displayed on the display section 31 of the mobile terminal 3, and the customer is ready to start shopping. Note that the store information transmitted by the management server 2 includes information indicating the customer's transaction status at the store, and when the customer starts shopping anew at the store, the transaction status becomes new. On the other hand, if the customer interrupts shopping at the store for some reason, a purchased product list screen corresponding to the transaction status up to that point is displayed on the mobile terminal 3.

(3-2) Product Selection Process Next, the product selection process will be explained. The product selection process is a process in which the customer uses the mobile terminal 3 to read the product barcode attached to the product and registers it in the purchase product list. FIG. 9 is a flowchart of the product selection process. This process is executed by the mobile terminal 3 and the management server 2.

First, when a customer finds a product he/she wants to purchase, the customer puts the mobile terminal 3 into the product reading mode and reads the product barcode attached to the product using the mobile terminal 3 (step S201: Yes). The mobile terminal 3 transmits the read product identification information of the product to the management server 2 (step S202). Note that 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 purchase 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.

Next, when the customer operates the mobile terminal 3 to change the quantity of the product as necessary, the mobile terminal 3 acquires the changed quantity (step S206: Yes). When a product barcode is read for the first time, the quantity of the product is automatically set to "1", but if the customer purchases multiple of the same product, the quantity can be set by operating the mobile terminal 3. Can be changed. When 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).

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 transmits it to the mobile terminal 3 (step S209). The mobile terminal 3 receives the updated product list and displays it on the display unit 31 (step S210). As a result, the quantity change is reflected in the purchased product list.

Next, the mobile terminal 3 determines whether the customer has pressed the payment button (step S211). The payment button is a button that the customer presses when finishing shopping. If the payment button is not pressed (step S211: No), the process returns to step 201. In this way, customers can add items, change quantities, and continue shopping until they press the payment button. Then, when the payment button is pressed (step S211: Yes), the product selection process ends.

FIG. 10 shows an example of a purchase product list screen displayed on the mobile terminal 3. In this example, the purchased product list screen includes 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 cancel button. 96.

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 the product reading screen. On the product reading screen, the mobile terminal 3 displays images etc. acquired from the activated reading section 36. Thereby, the customer can read the product barcode 7 by moving the product or the mobile terminal 3 so that the product barcode 7 is located within the reading range of the reading unit 36.

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

The subtotal display field 92 displays the subtotal of the selling prices of all products in the purchased product list excluding tax, and the total amount display field 93 displays the total amount including tax of the selling prices of all products in the purchased product list. The management server 2 calculates these subtotals or totals based on the prices of the purchased products registered in the product information DB 28, specifically, based on the selling price list of the store obtained through the store entry process.

When the mobile terminal 3 detects that the home screen transition button 94 has been selected, it transmits 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 on discounts and discounts at the store 8, customer registration information on the mobile terminal 3, and the like.

When the mobile terminal 3 detects that the payment button 95 has been selected, it transmits an accounting request to the management server 2, and displays a payment screen including an accounting barcode screen, which will be described later, based on the display information received as a response. do. Further, when the mobile terminal 3 detects that the transaction stop button 96 has been selected, it transmits information notifying the transaction stop to the management server 2. In this case, the management server 2 deletes the purchased product list corresponding to the mobile terminal 3.

(3-3) Accounting processing Next, accounting processing will be explained. The accounting process is a process of paying for the product selected by the customer through the product selection process. FIG. 11 is a flowchart of accounting processing. This process is executed by the mobile terminal 3, the management server 2, and the accounting machine 5.

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

The mobile terminal 3 displays the received payment screen on the display unit 31. FIG. 12 is a display example of the payment screen. In this example, the payment screen includes an accounting barcode 37, a total amount field 38, and a completion button 39. The customer moves to the checkout machine 5 with the mobile terminal 3 on which the payment screen is displayed, and reads the checkout barcode with the barcode reader 56 (step S307). The accounting machine 5 displays a payment method selection screen based on the read accounting barcode (step S308). Specifically, the accounting machine 5 transmits the inquiry number indicated by the accounting barcode to the management server 2 and obtains payment information. Note that the payment information includes details such as the total amount and the IDs and quantities of all products included in the purchased product list. The accounting machine 5 displays a payment method selection screen based on the acquired payment information.

FIG. 13(A) shows a display 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 amount to be paid, and presses either the cash button 62 or the credit button 63 to make the payment. Thereby, the purchase price is settled (step S309). Specifically, when the customer chooses to pay in cash, the accounting machine 5 prompts the customer to insert cash into the cash slot, and when the cash is inserted, provides change as necessary. Further, if the customer chooses to pay by credit card, the accounting machine 5 prompts the customer to insert the card, prompts the customer to input a personal identification number, etc., if necessary, and performs the credit card payment.

When the payment is completed, the accounting machine 5 displays an accounting completion screen. FIG. 13(B) shows a display example of the checkout completion screen. In this example, the checkout end screen includes a payment information field 64, a receipt button 65, and an end button 66. Note that FIG. 13(B) is an example where the customer selects credit card payment, and the payment information column 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 confirming that the customer has completed the accounting process. When the customer presses the end button 66, the accounting machine 5 reports to the management server 2 that the payment has been completed, and returns the display on the display section 51 to the main menu. Note that a completion button 39 is also displayed on the payment screen shown in FIG. 12, and the customer presses the completion button 39 on the payment screen when the transaction process is completed. When the completion button 39 is pressed, the mobile terminal 3 reports to the management server 2 that the payment has been completed, and returns the display section 31 to the main menu.

In the above example, the accounting barcode is simply an inquiry number for payment information, and the accounting machine 5 uses this inquiry number to acquire payment information from the management server 2. Alternatively, the accounting barcode may include payment information. That is, the management server 2 generates an accounting barcode based on the contents of the purchased product list at that time, using information on the total amount and details of the purchased products. In this case, since the accounting machine 5 can acquire payment information by reading and decoding the accounting barcode, there is no need to communicate with the management server 2 to acquire payment information. That is, the accounting machine 5 only needs to extract the total amount from the read accounting barcode and display the payment method selection screen.

(4) Re-registration of membership card
Next, processing related to re-registration of a membership card in the management system of the first embodiment will be explained. Generally speaking, when the management server 2 receives a request to register the card number of a membership card from the mobile terminal 3 used by a member whose card number has already been registered, the management server 2 stores the member information using the card number specified by the registration request. Update. Thereby, the management server 2 can utilize existing member information when reissuing a member card to a member who has lost it, and suitably simplifies the work of registering member information again.

(4-1) Data Structure FIG. 14 shows an example of the data structure of the member information DB 47 in the first embodiment. The member information DB 47 is a database that records member information for each member, and mainly includes "card number", "membership type", "membership rank", "name", "gender", "accumulated points", "previous It has the following items: ``Card Number,'' ``Related Card Number,'' and ``Application ID.''

"Card number" indicates the card number assigned to the membership card given to the target member. "Membership type" indicates whether the target member is a primary member or a family member. “Member rank” indicates the rank (status) of the target member. Note that the membership rank is a standard for determining the point award rate, discount rate, etc. that each member is given when purchasing products at the store 8, and is determined by, for example, the purchase amount in a predetermined period (for example, annual or monthly). “Name” and “gender” indicate the name and gender of the target member, respectively.

“Accumulated points” indicates the number of points accumulated by the target member. In the example shown in Figure 14, the family member shares points with the primary member linked to the family member, and the accumulated points of the family member are the accumulated points of the primary member linked to the family member. It is summarized in For example, the accumulated points of the family member "Dainippon Hanako" are aggregated with the accumulated points of the main member "Dainippon Taro" to which the family member is dependent, so the "accumulated points" of "Dainippon Hanako" There is no record of accumulated points for the item. In addition, instead of this recording method, the management server 2 may synchronize the contents of the "accumulated points" of a family member so that they are the same as the contents of the "accumulated points" of the main member to whom the family member is dependent. good. In this case, if there is a change in the "accumulated points" of either the family member or the primary member, the management server 2 changes the "accumulated points" of the other member to have the same contents.

The "previous card number" indicates a card number assigned to a membership card that the target member possessed in the past. In other words, the "previous card number" indicates the card number recorded in the "card number" item before being updated with the card number of the reissued membership card. For example, if a member loses his or her membership card and re-registers it, the management server 2 overwrites the "card number" with the card number of the newly registered membership card and stores it in the member information DB 47 until just before. The recorded card number of the membership card is recorded in the "previous card number". In the example of FIG. 14, "Hajime Suzuki" has lost his membership card with card number "10003", so he is re-registering his membership card with card number "11347". In this case, the card number "11347" of the re-registered membership card is recorded in the "card number", and the card number "10003" of the lost membership card is recorded in the "previous card number". Note that the membership card with the card number "10003" registered in the "previous card number" is an invalid membership card that cannot be used at the store 8.

The "related card number" indicates the card number of a family member who is subordinate to the target member, or a primary member to whom the target member is subordinate if the target member is a family member. For example, in the "related card number" of the main member "Dainippon Taro", the card number "10004" of the related family member "Dainippon Hanako" is recorded. On the other hand, in the "related card number" of the family member "Dainippon Hanako", the card number "10001" of the related main member "Dainippon Taro" is recorded. In this case, for example, when registering a record of a family member to whom a family card has been issued in the member information DB 47, the management server 2 updates the "related card number" item of the main member to whom the family member is subordinate.

“App ID” is identification information of a dedicated app installed on the mobile terminal 3 used by the target member. The application ID is identification information that differs depending on the mobile terminal 3 on which the dedicated application is installed.

Here, a supplementary explanation will be given about the "application ID" registration process. The management server 2 communicates with the mobile terminal 3 that has started the dedicated application, and receives information from the mobile terminal 3 when the member using the mobile terminal 3 is first associated with the record in the member information DB 47. Register the app ID in the "App ID" field. In this case, for example, based on the information transmitted from the terminal of the store 8 when applying for a membership card, the management server 2 stores a record of membership information including the card number of the membership card to be issued and application information such as name. Register in DB47. After that, when the customer's mobile terminal 3 to which the membership card has been assigned connects to the management server 2 using the dedicated application, the management server 2 uses the information such as the card number supplied from the mobile terminal 3 to use the mobile terminal 3. A record of member information corresponding to the member is extracted from the member information DB 47. Then, the management server 2 registers the application ID acquired from the mobile terminal 3 in the extracted record.

In this way, the member information DB 47 includes items indicating general attribute information including "name" and "gender", "card number", "membership type", "membership rank", "accumulated points", and "previous "Card number", "Related card number", "App ID", and other items indicating member-specific attribute information.

Note that the data structure of the member information DB 47 shown in FIG. 14 is an example, and various changes may be made to this data structure. For example, in addition to "name" and "gender," the member information DB 47 includes items indicating various general attribute information such as date of birth, address, telephone number, email address, family composition, and occupation. Good too. Further, information corresponding to the "previous card number" and "related card number" may be included in the card information DB 48 instead of the member information DB 47. Further, instead of the "app ID", the member information DB 47 may include an item for recording identification information (for example, terminal ID) regarding the mobile terminal 3 used by the target member.

FIG. 15 is an example of the data structure of the card information DB 48. The card information DB 48 is a database that records information for each member card, and mainly includes the following items: "Card Number", "PIN Code", "Card Type", and "Status".

"Card number" indicates the card number assigned to the target membership card. The "PIN code" indicates a PIN code assigned to the target membership card, and is written, for example, on the back of the target membership card or on a piece of paper enclosed with the membership card. "Card type" indicates the type of the target membership card, and specifically indicates whether it is a primary membership card or a family membership card. “Status” indicates the status of the target membership card. For example, the card number recorded in "card number" in the member information DB 47 in FIG. 14 is set to "valid state". On the other hand, the card number linked to the member as the "previous card number" in the member information DB 47 of FIG. 14 is set to "invalid state". A membership card set to an "invalid state" cannot accumulate or use points for shopping or the like, nor can new linking of the card number to membership information can be performed. Note that in addition to "valid" and "invalid", the "status" may specify a status such as "unissued" indicating that the membership card is yet to be issued.

(4-2) Specific Example Next, operations on the mobile terminal 3 regarding re-registration of a membership card will be explained with reference to an example of a display screen of the mobile terminal 3 in FIG. 16.

FIG. 16 is a display example of a membership card registration screen displayed by the mobile terminal 3 based on the display information received from the management server 2. The membership card registration screen includes a card number input field 71, a PIN code input field 72, and a completion button 73.

First, the customer who is the user of the mobile terminal 3 has lost the issued membership card, so he has to go through the prescribed procedures at the store 8 (including filling out personal information on the application form) and become a new member. Get a card. In this case, the customer activates the dedicated application on the mobile terminal 3 and makes a predetermined menu selection on the mobile terminal 3, thereby causing the membership card registration screen shown in FIG. 16 to be displayed on the mobile terminal 3. In this case, after starting the dedicated application, the mobile terminal 3 displays a membership card registration screen based on the user input, and inputs the card number in the card number input field 71 and the PIN code (PIN code) in the PIN code input field 72. number). Note that the card number and PIN code to be input into the card number input field 71 and the PIN code input field 72 are written on the back of the reissued membership card, for example.

Note that when the mobile terminal 3 receives a request to display the membership card registration screen, instead of displaying the card number input field 71 and the PIN code input field 72, the mobile terminal 3 activates the reading unit 36 attached to the mobile terminal 3, The image etc. generated by the reading unit 36 may be displayed on the membership card registration screen. In this case, for example, a one-dimensional or two-dimensional barcode indicating the card number is attached to the membership card, and the mobile terminal 3 reads the barcode based on the information generated by the reading unit 36. You can also obtain your card number. In this case, after recognizing the card number, the mobile terminal 3 displays a membership card registration screen with the read card number displayed in the card number input field 71.

When the mobile terminal 3 detects selection of the completion button 73 with the card number and PIN code entered in the card number input field 71 and the PIN code input field 72, the mobile terminal 3 sends a signal requesting registration of the card number (" (also referred to as "card number registration request") to the management server 2. In this case, the card number registration request includes, in addition to the card number and PIN code entered in the card number input field 71 and PIN code input field 72, information for the management server 2 to identify the user using the mobile terminal 3. information (also referred to as "user identification information"). This user identification information may be an application ID, or may be any member information registered in the member information DB 47 such as a name or date of birth, or a combination thereof. When the management server 2 receives a card number registration request from the mobile terminal 3, it authenticates the card number included in the card number registration request, and updates the member information DB 47 using the card number. Details of the process executed by the management server 2 based on the card number registration request will be described in detail with reference to the process flow shown in FIG. 17.

(4-3) Processing flow
FIG. 17 is an example of a flowchart showing the procedure of card number registration processing.

First, if the user of the mobile terminal 3 has been issued a membership card by the store 8 and has the membership card at hand, the user starts the dedicated application on the mobile terminal 3, and based on the menu selection operation etc. on the dedicated application, A membership card registration screen as shown in FIG. 17 is displayed on the mobile terminal 3. Then, the mobile terminal 3 receives input of the card number of the issued membership card and a personal identification number such as a PIN code for authenticating the card number on the membership card registration screen. Note that the mobile terminal 3 may read at least one of the card number and the password of the membership card using the reading unit 36 instead of accepting the user's input.

Then, the mobile terminal 3 transmits a card number registration request including the input information input in step S401 to the management server 2 (step S402). In this case, the mobile terminal 3 may include user identification information such as the application ID in the card number registration request. Note that if the management server 2 authenticates the mobile terminal 3 immediately after starting the dedicated application, and the management server 2 has already recognized the record in the member information DB 47 corresponding to the user of the mobile terminal 3, the card The user identification information may not be included in the number registration request.

When the management server 2 receives a card number registration request from the mobile terminal 3, the management server 2 refers to the card information DB 48 and inputs the card number included in the card number registration request using the password included in the card number registration request. Authentication is performed (step S411). In this case, for example, the management server 2 refers to the card information DB 48 and determines whether the card number included in the card number registration request is valid and whether the above-mentioned password is correct. Note that if the authentication in step S411 is not successful (that is, the card number is not valid or the PIN is incorrect), the management server 2 proceeds to step S414 and sends a message indicating that the authentication was not successful. The response is sent to the mobile terminal 3.

Next, if the authentication in step S411 is successful, the management server 2 transmits the member information corresponding to the user of the mobile terminal 3 who made the card number registration request based on the user identification information included in the card number registration request. Extracted from member information DB 47. Then, the management server 2 determines whether a card number different from the card number specified in the card number registration request has been registered in the member information DB 47 (step S412). That is, the management server 2 determines whether the card number indicated by the member information extracted from the member information DB 47 is different from the card number specified in the card number registration request.

Then, if a card number different from the card number specified in the card number registration request has been registered in the member information DB 47 (step S412; Yes), the management server 2 registers the member information DB 47 corresponding to the user of the mobile terminal 3. The member information is updated with the card number specified in the card number registration request (step S413). For example, if the member information DB 47 has the data structure shown in FIG. Record the card number in the "Previous Card Number" field.

Preferably, the management server 2 considers that the card number that was recorded in the member information DB 47 until just before (previous card number) is the card number of the lost member card, and the member card with the card number is invalidated. The information to that effect is registered in the card information DB 48. Thereby, it is possible to suitably prevent a third party who has found the lost membership card from registering as a member, making purchases, etc. using the membership card.

On the other hand, if a card number different from the card number specified in the card number registration request has not been registered in the member information DB 47 (step S412; No), the management server 2 advances the process to step S414. For example, when the same card number as the card number specified by the card number registration request is registered in the member information corresponding to the user of the mobile terminal 3, the management server 2 considers that the card number has not been changed, The member information DB 47 is not updated. In another example, if the card number information is not registered in the member information corresponding to the user of the mobile terminal 3, the management server 2 transfers the card number specified by the card number registration request to the member information corresponding to the user of the mobile terminal 3. Add to information.

The management server 2 then transmits a response signal to the card number registration request to the mobile terminal 3 that is the source of the card number registration request (step S414). In this case, when the management server 2 executes step S413, the management server 2 transmits display information to the mobile terminal to display information indicating that registration of the card number of the reissued membership card in the membership information DB 47 has been completed. Send to 3. Furthermore, if the management server 2 determines in step S412 that the same card number is already registered in the member information DB 47, it displays a warning that the card number is the same as an already registered card number, for example. Display information for the purpose is transmitted to the mobile terminal 3. In addition, if the card number is not registered in the member information corresponding to the user of the mobile terminal 3 and the card number is added to the member information, the management server 2 provides information indicating that the registration of the card number has been completed. Display information for displaying is transmitted to the mobile terminal 3. Thereafter, the mobile terminal 3 displays the result of the card number registration request based on the response signal transmitted from the management server 2 in step S414 (step S403).

In this way, when the user of the mobile terminal 3 reissues the membership card, by transmitting the card number etc. written on the membership card to the management server 2 using the mobile terminal 3, the user of the mobile terminal 3 can already register the target user in the membership information DB 47. You can carry over member information linked to. In this case, the user of the mobile terminal 3 does not need to reinstall the dedicated application and/or re-register the user's personal information due to the loss of the membership card, and the user does not have to perform the work of re-registering the user's personal information, etc. It is also possible to suitably transfer benefits and the like according to the circumstances.

(5) Modification example
Next, a modification suitable for the above-described embodiment will be described. The following modifications may be applied to the above-described embodiment in any combination.

(Modification 1)
The processing executed by the management server 2 in the flowchart of FIG. 17 may be executed by the member server 4 instead. In this case, the management server 2 transfers the card number registration request sent from the mobile terminal 3 to the member server 4, and the member server 4 executes the processing of steps S411 to S414 in FIG. 17 instead of the management server 2. do. Also in this aspect, the member server 4 can suitably reflect the card number of the reissued member card in the member information DB 47 based on the card number registration request.

(Modification 2)
In step S401 of the membership card registration screen shown in FIG. 16 and the flowchart of FIG. 17, the mobile terminal 3 requests input of a personal identification number such as a PIN code in addition to the card number. Alternatively, the mobile terminal 3 may transmit a card number registration request including at least the card number to the management server 2 without requesting input of such a code number.

<Second embodiment>
FIG. 18 shows a schematic configuration of a management server 2A in the second embodiment. The management server 2A includes a receiving section 81, an extracting section 82, and an updating section 83.

The receiving unit 81 receives a registration request "S1" including the card number of the membership card from the terminal device 3A used by the member. The terminal device 3A is, for example, the mobile terminal 3 in the first embodiment. The extraction unit 82 extracts member information corresponding to the target member from the database of member information for each member. The above-mentioned registration request S1 is, for example, a card number registration request in the first embodiment, and the above-mentioned database is, for example, the member information DB 47 in the first embodiment. If the card number indicated by the extracted member information and the card number included in the registration request S1 are different, the updating unit 83 updates the member information using the card number included in the registration request S1. The receiving unit 81, the extracting unit 82, and the updating unit 83 can be the control unit 25 of the management server 2 of the first embodiment.

In this way, when the management server 2A according to the second embodiment receives the registration request S1 specifying a new card number from the terminal device 3A used by a member, the management server 2A inherits the member information of the member and updates the card number. can be updated.

In addition, part or all of each of the above embodiments (including modified examples, the same applies hereinafter) may be described as in the following supplementary notes, but is not limited to the following.

[Additional note 1]
a receiving unit that receives a registration request including a card number of a membership card from a terminal device used by the member;
an extraction unit that extracts member information corresponding to the member from a database of member information for each member;
an updating unit that updates the member information with the card number included in the registration request if the card number indicated by the member information and the card number included in the registration request are different;
A management server with

[Additional note 2]
The membership card is a membership card reissued to the member,
The management server according to supplementary note 1, wherein the card number indicated by the member information before update is the card number of a membership card issued to the member before the membership card.

[Additional note 3]
The registration request includes user identification information that identifies the user of the terminal device,
The management server according to supplementary note 1 or 2, wherein the extraction unit extracts the member information based on the user identification information.

[Additional note 4]
The management server according to appendix 3, wherein the user identification information is identification information regarding an application installed in the terminal device and provided by an issuer of the membership card.

[Additional note 5]
When updating the member information using the card number included in the registration request, the updating unit updates the member information with information on the card number indicated by the member information before update as information on the previously used member card. The management server described in any one of Supplementary Notes 1 to 4, which is included in the management server.

[Additional note 6]
When updating the member information using the card number included in the registration request, the updating unit sets the card number indicated by the member information before update to invalid, according to any one of Supplementary Notes 1 to 5. Management server listed.

[Additional note 7]
The member information includes at least one of the number of points held by the member and the card number of a family card issued to the member's family, as described in any one of Supplementary Notes 1 to 6. management server.

[Additional note 8]
The management server described in any one of Supplementary Notes 1 to 7,
A management system comprising a terminal device used by members,
The terminal device includes an acquisition unit that acquires at least a card number of a membership card owned by the member;
a transmitter that transmits a registration request including at least the card number to the management server;
management system.

[Additional note 9]
The management system according to appendix 8, wherein the acquisition unit acquires the card number by reading a barcode of the membership card.

[Additional note 10]
The acquisition unit acquires the card number and a PIN number attached to the membership card,
The transmitting unit transmits the registration request including the card number and the PIN number to the management server,
The management server is
The management system according to appendix 8 or 9, further comprising an authentication unit that authenticates the card number based on the card number and the password.

[Additional note 11]
A control method executed by a management server,
Receives a registration request including the card number of the member card from the terminal device used by the member,
extracting member information corresponding to the member from a database of member information for each member;
If the card number indicated by the member information and the card number included in the registration request are different, the member information is updated with the card number included in the registration request.

[Additional note 12]
a receiving unit that receives a registration request including a card number of a membership card from a terminal device used by the member;
an extraction unit that extracts member information corresponding to the member from a database of member information for each member;
A program that causes a computer to function as an update unit that updates the member information using the card number included in the registration request when the card number indicated by the member information and the card number included in the registration request are different.

Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. The configuration and details of the present invention can be modified in various ways that can be understood by those skilled in the art within the scope of the present invention. That is, it goes without saying that the present invention includes the entire disclosure including the claims and various modifications and modifications that a person skilled in the art would be able to make in accordance with the technical idea. In addition, the disclosures of the above cited patent documents, etc. are incorporated into this document by reference.

1 POS server 2 Management server 3 Mobile terminal 4 Member server 5 Accounting machine 100, 100A Management system

Claims (15)

receiving means for receiving a registration request including a card number of a membership card from a terminal device used by the member;
Extracting means for extracting member information corresponding to the member from a member information database;
If a card number different from the card number included in the registration request is not registered in the member information, the member information is not updated and the card number indicated by the member information and the card number included in the registration request are not updated. If different, updating means for updating the member information using the card number included in the registration request;
A management server with When the same card number as the card number included in the registration request is registered, or when the card number is not registered in the member information, the updating means is configured to update the card number different from the card number included in the registration request. The management server according to claim 1, which assumes that the card number is not registered in the member information and does not update the member information. If the same card number as the card number included in the registration request is registered, or if the card number is not registered in the member information, display information for displaying a warning is sent to the terminal device. , The management server according to claim 1 or 2. The membership card is a membership card reissued to the member,
4. The management server according to claim 1, wherein the card number indicated by the member information before update is the card number of a member card issued to the member before the member card. The registration request includes user identification information that identifies the user of the terminal device,
The management server according to claim 1, wherein the extraction means extracts the member information based on the user identification information. The management server according to claim 5, wherein the user identification information is identification information regarding an application installed on the terminal device and provided by an issuer of the membership card. When updating the member information using the card number included in the registration request, the updating means updates information on the card number indicated by the member information before update to the member information as information on the previously used membership card. The management server according to any one of claims 1 to 6, which is included in the management server. 8. The updating means, when updating the member information with the card number included in the registration request, sets the card number indicated by the member information before update to invalid. Management server described in . 9. The member information includes at least one of the number of points held by the member and the card number of a family card issued to the member's family. Management server listed. further comprising authentication means for authenticating the member based on the registration request,
The management server according to any one of claims 1 to 9, wherein if the authentication is successful, the extraction means extracts the member information from the database. A management server according to any one of claims 1 to 10,
A management system comprising a terminal device used by members,
The terminal device includes acquisition means for acquiring at least a card number of a membership card owned by the member;
Transmitting means for transmitting a registration request including at least the card number to the management server;
management system. The management system according to claim 11, wherein the acquisition means acquires the card number by reading a barcode of the membership card. The acquisition means acquires the card number and a pin number attached to the membership card,
The transmitting means transmits the registration request including the card number and the PIN number to the management server,
The management server is
The management system according to claim 11 or 12, further comprising authentication means for authenticating the card number based on the card number and the password. A control method executed by a management server,
Receives a registration request including the card number of the member card from the terminal device used by the member,
extracting member information corresponding to the member from a member information database;
If a card number different from the card number included in the registration request is not registered in the member information, the member information is not updated and the card number indicated by the member information and the card number included in the registration request are not updated. If different, the control method updates the member information with the card number included in the registration request. receiving means for receiving a registration request including a card number of a membership card from a terminal device used by the member;
Extracting means for extracting member information corresponding to the member from a member information database;
If a card number different from the card number included in the registration request is not registered in the member information, the member information is not updated and the card number indicated by the member information and the card number included in the registration request are not updated. If different, the program causes the computer to function as an updating means for updating the member information using the card number included in the registration request.

Images