Management Server and Program

Abstract

To provide a management server and a program that reliably update management information on the management server.SOLUTION: A management server includes: a reception unit that receives, from a store server installed in a store, management information about store management stored in the store server; an intermediate storage unit that stores the received management information; an update storage unit that stores the updated management information; determination means that determines, on basis of the management information stored in the intermediate storage unit and the management information stored in the update storage unit, when the management information stored in the update storage unit is updated on the basis of the management information, whether the management information stored in the intermediate storage unit is unauthorized data that causes an error; updating means that updates, when the determination means determines that the data is not unauthorized data, the management information stored in the update storage unit on the basis of the management information stored in the intermediate storage unit; and notification means that notifies, when the determination means determines that the data is unauthorized data, the store server of the fact that the management information stored in the intermediate storage unit is unauthorized data without executing the updating means.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a management server and a program. [Background technology]

[0002] Conventionally, member management servers have been installed in stores such as shopping centers. The member management server manages various information (member information) of customers (hereinafter referred to as "members") who have member cards (e.g., point cards or credit cards) issued by the store.

[0003] On the other hand, there is a management server that manages the sales, rent, etc. of the tenants who open in the store. The management server is installed in the store or on the cloud. The management server is connected to the POS (Point of Sales) terminals installed in the tenants, and for reasons such as handling point information, it also stores member information similar to that of the member management server.

[0004] However, when updating the member information on the management server based on the member information stored in the member management server, the two pieces of member information may not be synchronized and may contain different contents. For example, the member information received from the member management server may not contain the member information stored in the management server, the member information received from the member management server may not contain information about a member whose membership has expired due to loss of a membership card, or the member information received from the member management server may not contain the member attribute information to be updated. In such cases, updating the member information on the management server based on the member information received from the member management server may result in an error, and the member information on the management server may not be updated until the error is resolved. In particular, when importing and updating a large amount of member information, it may take a long time to resolve the error.

[0005] Note that the information stored in the management server and updated includes information other than member information, such as information related to expenses. Hereinafter, information that the management server retrieves from outside and updates, including member information, will be referred to as management information. Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the present invention is to provide a management server and a program that can reliably update management information of the management server. [Means for solving the problem]

[0007] The management server of the embodiment receives from a store server installed in a store information related to store management stored in the store server. It is master information a receiving unit that receives management information; and an intermediate storage unit that stores the received management information; The management information is changed based on change information received from a product sales data processing device installed in a tenant in the store and used for registering products sold by the tenant. an update storage unit storing the management information; a determination means for determining, based on the management information stored in the intermediate storage unit and the management information stored in the update storage unit, whether the management information stored in the intermediate storage unit is invalid data that will result in an error when the management information stored in the update storage unit is updated based on the management information; an update means for updating the management information stored in the update storage unit based on the management information stored in the intermediate storage unit when the determination means determines that the management information is not invalid data; and a determination means for determining that the management information stored in the intermediate storage unit is invalid data without executing the update means when the determination means determines that the management information is invalid data. The aforementioned and a notification means for notifying the store server. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing the overall configuration of an information management system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing the hardware configuration of the POS terminal. [Figure 3] FIG. 3 is a block diagram showing the hardware configuration of the member management server. [Figure 4] FIG. 4 is a block diagram showing the hardware configuration of the management server. [Figure 5] FIG. 5 is a memory map showing the memory configuration of the member information table. [Figure 6] FIG. 6 is a memory map showing the memory configuration of the fraud information section. [Figure 7] FIG. 7 is a block diagram showing the hardware configuration of the mobile terminal. [Figure 8] FIG. 8 is a flowchart showing the flow of control processing of the POS terminal. [Figure 9] FIG. 9 is a functional block diagram illustrating the functional configuration of the management server. [Figure 10] FIG. 10 is a flowchart showing the flow of control processing of the management server. [Figure 11] FIG. 11 is a flowchart showing the flow of control processing of the member management server. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the embodiment, member information will be described as an example of management information. However, the present invention is not limited to the embodiment described below.

[0010] FIG. 1 is a configuration diagram showing the overall configuration of an information management system 10 according to an embodiment. As shown in FIG. 1, the information management system 10 has a POS (Point of Sales) terminal 1, a member management server 3, a management server 5, and a member terminal 7. The POS terminal 1 and the management server 5 are connected by a communication line 2 such as a dedicated line, a public line, or the Internet. The member management server 3 is installed in the back room of a store S, for example. The member management server 3 and the management server 5 are connected by a communication line 4 such as a dedicated line, a public line, or the Internet. The member terminal 7 is a terminal owned by a customer. The member management server 3 and the member terminal 7 are connected by a communication line 6 such as a public line or the Internet.

[0011] The POS terminal 1 is installed in each tenant T located in a store S such as a shopping center. The POS terminal 1 is a product sales data processing device that executes product registration processing and accounting processing for products sold by the tenant T. The product registration processing refers to the processing of acquiring product identification information for the products sold by the tenant T, displaying the product name and price (product information) of the product on the display unit based on the acquired product identification information, and storing the product information in the product information unit 132 (see FIG. 2). The accounting processing refers to the processing of closing the transaction based on the product information stored in the product information unit 132 in conjunction with the product registration processing, specifically, displaying the total amount, processing payment by means of cash or credit card, calculating and displaying change based on the deposit in the case of cash payment, instructing the change dispenser to issue change, and issuing a receipt from the printing unit on which product information and accounting information (such as the total amount, the deposit amount, the change amount, and point information related to the number of points the customer has) are printed.

[0012] The POS terminal 1 also transmits sales information (product information and accounting information) of the tenant T for a predetermined period (for example, one day) to the management server 5 as settlement information.

[0013] The POS terminal 1 also processes various information related to members. For example, the POS terminal 1 transmits point information related to points awarded or used in response to a transaction to the management server 5 along with a member ID that identifies the member. If a member loses their membership card, the POS terminal 1 transmits information indicating that the membership card has expired to the management server 5 along with the member ID. If a member requests to cancel their membership, the POS terminal 1 transmits information indicating that the member is no longer a member to the management server 5 along with the member ID. If new attribute information related to a member (for example, new telephone number information) is generated, the POS terminal 1 transmits the attribute information to the management server 5 along with the member ID. If any other changes are made to the member information, the POS terminal 1 transmits information on the changes to the management server 5 along with the member ID.

[0014] The management server 5 is installed in the backyard of the store S or on the cloud (in the embodiment, it is installed on the cloud). The management server 5 manages the sales of the tenants T who have opened stores in the store S, the rent (store opening rent) paid by the tenants T to the stores, expenses, etc. for each tenant T.

[0015] The management server 5 is also directly connected to the POS terminal 1 installed in each tenant T. The management server 5 generates points to be awarded to members based on transaction information processed by the POS terminal 1 for products sold by tenant T. The management server 5 has a member information table 543 (see FIG. 4) that stores member information such as transaction information and point information related to awarded points and redeemed points by member ID. The management server 5 changes the member information based on the information received from the POS terminal 1. The changed point information is sent to the member management server 3 at a predetermined timing, and the point information is shared with the member management server 3.

[0016] The management server 5 changes the member information stored in the member information table 543 based on the information received from the POS terminal 1. For example, if a member loses their member card, the management server 5 receives information about the lost card from the POS terminal 1. The management server 5 then modifies the member information for that member. Specifically, the management server 5 assigns a number to a slot in the member information related to the member ID of that member to add information about the lost card. The management server 5 determines the type of information to be stored in the assigned slot. In this case, the management server 5 determines that information about the lost card should be stored.

[0017] If the relevant slot does not exist in the member information stored in member information table 543, management server 5 generates fraudulent information indicating that information about a lost card should be entered in member management server 3. Management server 5 then cooperates with member management server 3 by sending a list of the generated fraudulent information to member management server 3. Based on the received fraudulent information, the cooperated member management server 3 changes the member information so that the information about a lost card is included in the assigned slot. Changes to the member information in member management server 3 based on the fraudulent information can be entered manually or by automatically collecting and entering information.

[0018] The member management server 3 (store server) is a member management server installed in the backroom of store S. The member management server 3 connects to member terminals 7 and registers customers as members. The member management server 3 associates the member information of customers who have become members of store S (member attribute information (member name, address, telephone number, email address, etc.), point information on points held by the member, etc.) with the member ID, and stores and manages this information for each member in the member information section 342 (see FIG. 3).

[0019] The member management server 3 also stores and manages card information (point card number, expiration date, etc.) of cards (e.g., point cards) issued by the store S. The member management server 3 also manages and analyzes the points of members based on the stored point information.

[0020] The member information stored in member management server 3 is master information. Therefore, in order to link the stored member information with management server 5, member management server 3 sends all stored member information to management server 5 at a predetermined time (for example, the 20th of each month).

[0021] Furthermore, if the member information sent to management server 5 is invalid data that would result in an error if management server 5, which received the member information, were to update the data based on the member information, member management server 3 receives an invalid information list related to the member information from management server 5. Member management server 3 then reviews and modifies the member information stored in member information unit 342 based on the received invalid information list. That is, member management server 3 assigns a new number to a new field based on the invalid information list, and enters the relevant information into the field, thereby modifying the member information stored in member information unit 342. In this way, the member information stored in member information table 543 and the member information stored in member information unit 342 are synchronized.

[0022] The member terminal 7 is a terminal owned by a member. The member terminal 7 is a portable terminal that the member can carry with them (for example, a mobile phone, smartphone, PDA (Personal Digital Assistant) or a PC installed in the member's home, etc. In this embodiment, the member terminal 7 is a portable terminal.

[0023] By installing and launching dedicated application software for viewing member information, the member terminal 7 can communicate with the member management server 3 and view the member information stored in the member information section 342.

[0024] In order to receive electronic receipt information on the member terminal 7, member registration via the member terminal 7 is required. Member registration via the member terminal 7 is performed, for example, as follows: A customer who wishes to become a member sends a blank email from the member terminal 7 to the member management server 3 via the communication line 6. The member management server 3 sends a URL (Uniform Resource Locator) indicating a page for member registration to the member terminal 7 to the received email address. The customer accesses the URL indicating the page for member registration from the member terminal 7, and an input screen is displayed on which the customer can enter the information required for member registration (name, address, telephone number, destination information (email address information of the member terminal 7, etc.)). After the customer has entered the necessary information, the member management server 3 registers the customer as a member in the member information section 342. Thereafter, the member management server 3 sends a member registration completion email including the member ID and password to the member terminal 7 (the above email address). This completes the member registration for the customer.

[0025] Next, the hardware configuration of the POS terminal 1 will be described. FIG. 2 is a block diagram showing the hardware configuration of the POS terminal 1. As shown in FIG. 2, the POS terminal 1 includes a CPU (Central Processing Unit) 11, which is an example of a microprocessor, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a memory unit 14, and the like. The CPU 11 is the main controller of the POS terminal 1. The ROM 12 stores various programs. The RAM 13 loads programs and various data. The memory unit 14 stores various programs. The CPU 11, ROM 12, RAM 13, and memory unit 14 are connected to one another via a bus 15. The CPU 11, ROM 12, and RAM 13 constitute a control unit 100. That is, the control unit 100 executes the control processing of the POS terminal 1, which will be described later, by the CPU 11 operating in accordance with the control programs stored in the ROM 12 and the memory unit 14 and loaded in the RAM 13.

[0026] The RAM 13 has a member ID section 131, a product information section 132, and a sales information section 133. The member ID section 131 stores the member ID contained in a code symbol (barcode or two-dimensional code) read by the code reader 20 and displayed on the display section 77 of the member terminal 7, for example. The product information section 132 stores product information (product code identifying the product, product name, price, etc.) for products for which product registration processing has been performed. The sales information section 133 stores product information and accounting information for products for one transaction processed by the POS terminal 1 as sales information.

[0027] The memory unit 14 is composed of a non-volatile memory such as a hard disk drive (HDD) or flash memory that retains stored information even when the power is turned off, and has a control program unit 141 that stores control programs, and a product master 142. The product master 142 stores product information for each product in association with a product code that identifies the product.

[0028] The control unit 100 is also connected to an operation unit 17, a display unit for store clerks 18, a display unit for customers 19, a code reader 20, a printing unit 21, and a card reader 22 via a bus 15 and a controller 16.

[0029] The operation unit 17 has a closing key 171. The closing key 171 is a key that is operated when advancing the POS terminal 1 from product registration processing to transaction processing. The clerk display unit 18 displays information to the operator (e.g., a store clerk) operating the POS terminal 1. The customer display unit 19 displays information to customers and members. The code reader 20 captures (or optically reads) code symbols displayed on the member terminal 7 and code symbols attached to products. The printing unit 21 issues receipts on which receipt information including product registration information and transaction information for the products that have been processed for transaction is printed. The card reader 22 reads card information from the card, for example, when transaction processing is performed using a credit card or debit card.

[0030] The controller 16 receives instructions from the control unit 100 and controls the operation unit 17, the clerk display unit 18, the customer display unit 19, the code reader 20, the printing unit 21, and the card reader 22. However, for the sake of convenience, the control performed by the controller 16 will be described as being performed by the control unit 100.

[0031] The control unit 100 is also connected to a communication unit 23 via a bus 15. The communication unit 23 is connected to a management server 5 via a communication line 2 so as to be able to communicate with each other.

[0032] Next, the hardware configuration of the member management server 3 will be described. FIG. 3 is a block diagram showing the hardware configuration of the member management server 3. As shown in FIG. 3, the member management server 3 includes a CPU 31, which is an example of a microprocessor, a ROM 32, a RAM 33, and a memory unit 34. The CPU 31 is the main controller of the member management server 3. The ROM 32 stores various programs. The RAM 33 loads programs and various data. The memory unit 34 stores various programs. The CPU 31, the ROM 32, the RAM 33, and the memory unit 34 are connected to one another via a bus 35. The CPU 31, the ROM 32, and the RAM 33 constitute the control unit 300. That is, the control unit 300 executes the control processing of the member management server 3, which will be described later, by the CPU 31 operating in accordance with the control program stored in the ROM 32 or the memory unit 34 and loaded in the RAM 33.

[0033] The RAM 33 includes a fraud information section 331. The fraud information section 331 stores information of the fraud information list received from the management server 5.

[0034] The memory unit 34 is composed of a non-volatile memory such as an HDD or flash memory that retains stored information even when the power is turned off, and has a control program unit 341 that stores a control program, a member information unit 342, and a transmission date and time unit 343. The member information unit 342 stores member information for registered members. The member information stored in the member information unit 342 is master information. The transmission date and time unit 343 stores the date and time when the member information stored in the member information unit 342 is sent to the management server 5. The transmission date and time unit 343 stores, for example, midnight on the 20th of each month.

[0035] Furthermore, control unit 300 is connected to display unit 37 and operation unit 38 via bus 35 and controller 36. Display unit 37 displays information to the operator of member management server 3. Operation unit 38 is a keyboard operated by the operator.

[0036] The controller 36 receives instructions from the control unit 300 and controls the display unit 37 and the operation unit 38. However, for convenience of explanation, the control performed by the controller 36 will be described as being performed by the control unit 300.

[0037] The control unit 300 is also connected to a communication unit 39 via a bus 35. The communication unit 39 is connected to the management server 5 via a communication line 4 so as to be able to communicate with the member terminal 7 via a communication line 6.

[0038] Next, the hardware configuration of the management server 5 will be described. FIG. 4 is a block diagram showing the hardware configuration of the management server 5. As shown in FIG. 4, the management server 5 includes a CPU 51, which is an example of a microprocessor, a ROM 52, a RAM 53, a memory unit 54, and the like. The CPU 51 is the main controller of the management server 5. The ROM 52 stores various programs. The RAM 53 loads programs and various data. The memory unit 54 stores various programs. The CPU 51, the ROM 52, the RAM 53, and the memory unit 54 are connected to one another via a bus 55. The CPU 51, the ROM 52, and the RAM 53 constitute a control unit 500. That is, the control unit 500 executes the control processing of the management server 5, which will be described later, by the CPU 51 operating in accordance with the control program stored in the ROM 52 or the memory unit 54 and loaded in the RAM 53.

[0039] The RAM 33 has a fraud information section 531. The fraud information section 531 stores information on numbers that identify assigned slots and information to be stored in the slots, listed by number. This information constitutes fraud information. The fraud information section 531 will be described later with reference to FIG. 6.

[0040] The memory unit 54 is composed of a non-volatile memory such as an HDD or flash memory that retains stored information even when the power is turned off, and has a control program unit 541 that stores a control program, an intermediate table 542, a member information table 543, and a tenant information unit 544. The intermediate table 542 (intermediate storage unit) stores member information received from the member management server 3. The member information table 543 (update storage unit) stores updated member information. The updated member information is the member information stored in the intermediate table 542 when the member information stored in the intermediate table 542 is normal data. The member information table 543 will be described later with reference to FIG. 5. The tenant information unit 544 stores sales information for products sold by tenant T for each tenant T.

[0041] The control unit 500 is also connected to a display unit 57 and an operation unit 58 via a bus 55 and a controller 56. The display unit 57 displays information to the operator of the management server 5. The operation unit 58 is a keyboard operated by the operator.

[0042] The controller 56 receives instructions from the control unit 500 and controls the display unit 57 and the operation unit 58. However, for convenience of explanation, the control performed by the controller 56 will be described as being performed by the control unit 500.

[0043] The control unit 500 is also connected to a communication unit 59 (receiving unit) via a bus 55. The communication unit 59 is connected to each POS terminal 1 via a communication line 2 so as to be able to communicate with the member management server 3 via a communication line 4.

[0044] Next, the member information table 543 will be described. Fig. 5 is a memory map showing the memory configuration of the member information table 543. As shown in Fig. 5, the member information table 543 has a member ID section 5431, a member information section 5432, and a point information section 5433. The member ID section 5431 stores a member ID that identifies each member. The member ID may be terminal information that identifies the member terminal 7 carried by the member.

[0045] Member information section 5432 stores various member information (such as name, address, telephone number, and email address of member terminal 7) for each member, in association with the member ID stored in member ID section 5431. Numbered boxes are set in member information section 5432 for each of the above-mentioned name, address, telephone number, and email address of member terminal 7. For example, if a member card is lost, a newly numbered box is set in member information section 5432, and information indicating that the member card has been lost is stored in that box. The address, telephone number, and email address of member terminal 7, etc., are attribute information.

[0046] The point information section 5433 stores point information (part of the member information) relating to points held by a member identified by the member ID stored in the member ID section 5431. When point information on points generated by the management server 5 or point information on points used at the POS terminal 1 is received from the management server 5, the point information stored in the point information section 5433 is updated to the latest information.

[0047] Next, the fraud information section 531 will be described. The fraud information section 531 stores list information related to fraud information. FIG. 6 is a memory map showing the memory configuration of the fraud information section 531. As shown in FIG. 6, the fraud information section 531 has a member ID section 5311 and a fraud memory section 5312. The member ID section 5311 stores a member ID that identifies a member for each member. The fraud memory section 5312 stores, in association with the member ID stored in the member ID section 5311, a list of the number of a slot containing fraud information among the member information related to the member, and information to be stored in that slot. For example, if member A loses his / her membership card, the fraud memory section 5312 corresponding to the member ID section 5311 in which the member ID identifying member A is stored stores list information in which the number of the assigned slot and information indicating that "card lost" should be entered in that slot are associated with each other.

[0048] Next, the hardware configuration of the member terminal 7 will be described. FIG. 7 is a block diagram showing the hardware configuration of the member terminal 7. As shown in FIG. 7, the member terminal 7 is equipped with a CPU 71, which is an example of a microprocessor, a ROM 72, a RAM 73, a memory unit 74, etc. The CPU 71 is the main controller of the member terminal 7. The ROM 72 stores various programs. The RAM 73 expands programs and various data. The memory unit 74 stores various programs. The CPU 71, ROM 72, RAM 73, and memory unit 74 are connected to one another via a bus 75. The CPU 71, ROM 72, and RAM 73 constitute a control unit 700. In other words, the control unit 700 executes control processing for the member terminal 7 by the CPU 71 operating in accordance with the control programs stored in the ROM 72 and memory unit 74 and expanded in the RAM 73.

[0049] The memory unit 74 is composed of a non-volatile memory such as an HDD or flash memory that retains stored information even when the power is turned off, and has a control program unit 741 that stores a control program, a viewing program unit 742, and a member ID unit 743. The viewing program unit 742 stores a viewing program for downloading and viewing member information from the management server 5. The member ID unit 743 stores a member ID that identifies the member who owns the member terminal 7. The member ID is also a terminal ID that identifies the member terminal 7 in which the member ID is stored.

[0050] The control unit 700 is also connected to a display unit 77 and an operation unit 78 via a bus 75 and a controller 76. The display unit 77 displays information to members. The operation unit 78 is a keyboard operated by the operator of the member terminal 7.

[0051] The controller 76 receives instructions from the control unit 700 and controls the display unit 77 and the operation unit 78. However, for convenience of explanation, the control performed by the controller 76 will be described as being performed by the control unit 700.

[0052] The control unit 700 is also connected to a communication unit 79 via a bus 75. The communication unit 79 is connected to the member management server 3 via a communication line 6 so as to be able to communicate with each other.

[0053] Next, the control of the POS terminal 1 will be described. Fig. 8 is a flowchart showing the flow of the control process of the POS terminal 1. As shown in Fig. 8, the control unit 100 of the POS terminal 1 determines whether a member ID has been input by having the code reader 20 read the code symbol displayed on the display unit 77 of the member terminal 7 (S11). If it is determined that a member ID has been input (Yes in S11), the control unit 100 stores the member ID in the member ID unit 131 (S12). The control unit 100 then ends the process and returns to S11.

[0054] Furthermore, if it is determined that the input is not a member ID (No in S11), the control unit 100 determines whether a product code that identifies the product has been acquired by the code reader 20 reading a code symbol such as a barcode attached to the product (S13). If it is determined that a product code has been acquired (Yes in S13), the control unit 100 searches the product master 142 based on the acquired product code, reads out product information (product name, product price, etc.) corresponding to the product code, and executes product registration processing (S14). Then, the control unit 100 ends the processing and returns to S11. Every time a code symbol attached to a product is read, the control unit 100 repeats the processing of S13 and S14.

[0055] If it is determined that the request is not to obtain a product code (No in S13), the control unit 100 determines whether the closing key 171 has been operated (S15). If it is determined that the closing key 171 has been operated (Yes in S15), the control unit 100 executes the transaction process based on the product information that has been registered and stored in the product information unit 132 (S16). The control unit 100 then ends the process and returns to S11.

[0056] Furthermore, if it is determined that the operation was not an operation of the closing key 171 (No in S15), the control unit 100 determines whether information to change the member information has been entered in the POS terminal 1 (S17). Information to change the member information includes, for example, information that the member has lost their member card, information that the member has requested to cancel their membership, new attribute information related to the member, etc. If it is determined that information to change the member information has been entered in the POS terminal 1 (Yes in S17), the control unit 100 transmits the changed member information to the management server 5 (S18). Then, the control unit 100 ends the processing and returns to S11. If it is determined that the input information was not to change the member information (No in S17), the control unit 100 returns to S11.

[0057] Next, we will explain the functional configuration of the management server 5. Fig. 9 is a functional block diagram showing the functional configuration of the management server 5. The control unit 500 functions as a determination unit 501, an update unit 502, a notification unit 503, and a list creation unit 504 by following a control program stored in the ROM 52 or a control program unit 541 of the memory unit 54.

[0058] Determination means 501 determines, based on the member information stored in intermediate table 542 and the member information stored in member information table 543, whether the member information stored in intermediate table 542 is invalid data that will result in an error when the member information stored in member information table 543 is updated based on the member information. Specifically, determination means 501 compares the member information stored in intermediate table 542 with the member information stored in member information table 543, and determines whether the member information is normal data in which all of the information in the boxes for inputting the information numbered as the member information stored in member information table 543 is present in the member information stored in intermediate table 542 and no error will occur when the member information stored in member information table 543 is updated with the member information stored in intermediate table 542, or whether all or part of the information in the boxes for inputting the information numbered as the member information stored in member information table 543 is not present in the member information stored in intermediate table 542 and the member information stored in member information table 543 is invalid data that will result in an error when the member information stored in member information table 543 is updated with the member information stored in intermediate table 542.

[0059] If determination means 501 determines that the data is not fraudulent, update means 502 updates the member information stored in member information table 543 based on the member information stored in intermediate table 542. In other words, if determination means 501 determines that the data is not fraudulent, update means 502 rewrites the member information stored in member information table 543 to the member information stored in intermediate table 542.

[0060] When determination means 501 determines that the data is invalid, notification means 503 notifies member management server 3 that the member information stored in intermediate table 542 is information that will cause an error, without executing update means 502. Specifically, when determination means 501 determines that the data is invalid, notification means 503 notifies member management server 3 of invalid information related to a frame that will cause an error when the member information stored in intermediate table 542 is updated to member information table 543.

[0061] The list creation means 504 creates a list of fraudulent information indicating the cause of an error in the member information stored in the intermediate table 542. The list creation means 504 creates a list that stores fraudulent information related to the member, for example, by member ID (for example, numbering information for a slot that exists in the member information stored in the member information table 543 but does not exist in the member information stored in the intermediate table 542, and the information to be stored in that slot).

[0062] Next, the control of the management server 5 will be described. FIG. 10 is a flowchart showing the flow of the control process of the management server 5. As shown in FIG. 10, the control unit 500 of the management server 5 determines whether converted member information has been received from the POS terminal 1 (S31). If it is determined that converted member information has been received from the POS terminal 1 (Yes in S31), the control unit 500 assigns a number to reserve a slot (area) for inputting the received converted member information (S32). For example, if changed member information indicating that a member card has been lost is received, the control unit 500 assigns a number to a slot indicating that the member card has expired. Furthermore, for example, if information on a member's phone number is added, the control unit 500 assigns a number to a slot for inputting the phone number related to that member. The control unit 500 then stores the reserved slot and the number identifying the slot (assigned number) in the member information table 543 (S33). The control unit 500 then ends the process and returns to S31.

[0063] Furthermore, if it is determined that the converted member information has not been received from the POS terminal 1 (No in S31), the control unit 500 determines whether member information has been received from the member management server 3 (S34).If it is determined that member information has been received from the member management server 3 (Yes in S34), the control unit 500 stores the received member information in the intermediate table 542 (S35).

[0064] Next, control unit 500 compares the member information stored in intermediate table 542 with the member information stored in member information table 543 (S36). Then, determination means 501 determines whether all of the information in the boxes for inputting the information numbered as the member information stored in member information table 543 is present in the member information stored in intermediate table 542, and whether the member information stored in member information table 543 is normal data that will not result in an error when updated with the member information stored in intermediate table 542 (i.e., the member information stored in intermediate table 542 is normal data), or whether all or part of the information in the boxes for inputting the information numbered as the member information stored in member information table 543 is not present in the member information stored in intermediate table 542, and whether the member information stored in member information table 543 is invalid data that will result in an error when updated with the member information stored in intermediate table 542 (i.e., the member information stored in intermediate table 542 is invalid data) (S37).

[0065] If the control unit 500 determines that the member information stored in the intermediate table 542 is normal data (i.e., not invalid data) (No in S37), the control unit 500 determines whether it is time to update the member information (S38). The update period for the member information is preset in the memory unit 54, and is, for example, the 1st of each month. The update period is set to a date and time that is later than the date and time (for example, the 20th of each month) when the member management server 3 transmits the member information to the management server 5. This is because, if the member information transmitted from the member management server 3 is invalid data (No in S37), time is required for the member management server 3 to correct the invalid information related to the member information and make the member information normal data before updating the member information. The control unit 500 waits until the update period arrives (No in S38). If the control unit 500 determines that it is time to update the member information (Yes in S38), the update unit 502 executes an update process to replace the member information stored in the intermediate table 542 with the member information stored in the member information table 543 (S39). The control unit 500 then terminates the process and returns to S31.

[0066] On the other hand, if it is determined that the member information stored in intermediate table 542 is invalid data (Yes in S37), list creation means 504 extracts the invalid information, creates a list of the invalid information stored by member ID, and stores the list in invalid information section 531 (S40). Then, notification means 503 sends the list stored in invalid information section 531 to member management server 3 (i.e., notifies member management server 3 that the member information stored in intermediate table 542 is information that results in an error) (S41). Then, control unit 500 ends the processing and returns to S31. Note that, if it is determined in S34 that the member information was not received from member management server 3 (No in S34), control unit 500 returns to S31.

[0067] Next, we will explain the control of the member management server 3. Figure 11 is a flowchart showing the flow of the control process of the member management server 3. As shown in Figure 11, the control unit 300 of the member management server 3 determines whether member information has been entered by the member terminal 7 (S51). If it is determined that member information has been entered, the control unit 300 executes member registration processing, in which the input member information is stored in the member information unit 342 in association with the member ID of the member in question (S52). The control unit 300 then ends the process and returns to S51.

[0068] Furthermore, if it is determined that the input is not member information (No in S51), the control unit 300 determines whether a request for a member information inquiry has been received from the member terminal 7 (S53). If it is determined that a request for a member information inquiry has been received from the member terminal 7 (Yes in S53), the control unit 300 queries the member information for that member stored in the member information unit 342 corresponding to the member ID received at the same time, so that it can be viewed from the member terminal 7 (S54). The control unit 300 then ends the process and returns to S51.

[0069] Furthermore, if it is determined that the request is not for a member information inquiry (No in S53), the control unit 300 determines whether it is a transmission date and time based on the transmission date and time (e.g., midnight on the 20th of each month) stored in the transmission date and time unit 343 (S55). If it is determined that it is a transmission date and time (Yes in S55), the control unit 300 extracts member information relating to all members stored in the member information unit 342 (S56). The control unit 300 then transmits the extracted member information to the management server 5 (S57). The control unit 300 then ends the process and returns to S51.

[0070] Furthermore, if it is determined that the date and time is not the transmission date and time (No in S55), the control unit 300 determines whether information on the fraud information list has been received from the management server 5 (S58). If it is determined that information on the fraud information list has been received from the management server 5 (Yes in S58), the control unit 300 changes the member information stored in the member information unit 342 based on the received fraud information list (S59). In S59, the control unit 300 changes the member information by adding a numbered frame to the member information of the corresponding member ID based on the fraud information included in the fraud information list and storing the necessary information in that frame. Then, the control unit 300 executes the process of S57. The process of S59 is executed based on information entered by a person based on the fraud information, for example.

[0071] Furthermore, if it is determined that the fraud information list has not been received from the management server 5 (No in S58), the control unit 300 determines whether to execute other processing (S60). If it is determined that other processing should be executed (Yes in S60), the control unit 300 executes the other processing (S61). If the other processing is, for example, point processing, in S61, the control unit 300 updates the point information included in the member information for the corresponding member ID stored in the member information unit 342 based on, for example, the latest point information transmitted from the management server 5. Then, the control unit 300 ends the processing and returns to S51. Furthermore, if it is determined that other processing should not be executed (No in S60), the control unit 300 returns to S51.

[0072] As described above, the management server 5 of the embodiment comprises a communication unit 59 that receives member information related to the management of store S stored in the member management server 3 from the member management server 3 installed in store S; an intermediate table 542 that stores the received member information; a member information table 543 that stores the updated member information; a judgment means 501 that determines, based on the member information stored in intermediate table 542 and the member information stored in member information table 543, whether the member information stored in intermediate table 542 is invalid data that will result in an error if the member information stored in member information table 543 is updated based on the member information; an update means 502 that updates the member information stored in member information table 543 based on the member information stored in intermediate table 542 if the judgment means 501 determines that the data is not invalid (it is normal data); and a notification means 503 that, if the judgment means 501 determines that the data is invalid, sends to the member management server 3 an invalid information list indicating that the member information stored in intermediate table 542 is information that will result in an error, without executing the update means 502.

[0073] The management server 5 configured as described above receives member information from the member management server 3 before updating the member information, determines whether the member information is invalid data that would result in an error if the member information table 543 were updated based on that member information, and if the data is invalid, sends an invalid information list to the member management server 3. The member management server 3 receives the invalid information list and modifies the member information. The member management server 3 then sends the modified member information to the management server 5 again. The management server 5 then determines again whether the member information is invalid based on the received member information. By repeating this determination and processing, the management server 5 repeats this determination and processing until the member information received from the member management server 3 becomes normal data, and the member information becomes normal data before the management server 5 updates the member information. If the data is determined to be normal, the member information is replaced (updated) with the member information stored in the member information table 543.

[0074] Therefore, the management server 5 of the embodiment can reliably update the member information of the management server 5 based on the member information received from the member management server 3.

[0075] Although an embodiment of the present invention has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. This embodiment can be embodied in various other forms, and various omissions, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. This embodiment and its modifications are included within the scope and spirit of the invention, and are also included in the inventions described in the claims and their equivalents.

[0076] For example, in the embodiment, the management server 5 determines whether it is time to update in the process of S38, and performs the update process if it is time to update. However, this is not limiting, and the management server 5 may be configured to immediately perform the update process (process of S39) without determining whether it is time to update (determination of S38) if the data is not invalid (determination of S37).

[0077] In addition, in the embodiment, the management server 5 does not actively share member information with the member management server 3 regarding the information on the numbered slot until it transmits the fraudulent information list in S41 of Fig. 10. However, the present invention is not limited to this. For example, just as the latest point information is immediately transmitted to the member management server 3 when point information is changed, when a slot is numbered, the numbering information for the slot and information on the contents of the slot may be actively transmitted to the member management server 3, and it may also be determined in S36 and S37 whether the data is fraudulent.

[0078] In the embodiment, the member information has been described as an example of management information, but the management information is not limited to this, and may be, for example, information such as the expenses required to operate a shopping center.

[0079] The programs executed by the management server 5 of the embodiment are provided as files in an installable or executable format recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk).

[0080] The program executed by the management server 5 of the embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. The program executed by the management server 5 of the embodiment may be provided or distributed via a network such as the Internet.

[0081] Furthermore, the programs executed by the management server 5 of the embodiment may be provided by being pre-installed in a ROM or the like. [Explanation of symbols]

[0082] 1 POS terminal 3. Membership management server 5 Management Server 7 Member terminal 10 Information Management System 100 control section 131 Member ID Department 132 Product Information Department 133 Sales Information Department 142 Product Master 300 control section 331 Fraudulent Intelligence Department 342 Member Information Department 343 Transmission date and time part 500 control section 501 Judgment means 502 Update method 503 Notification means 504 List Creation Methods 531 Fraudulent Information Department 542 Intermediate Table 543 Member Information Table 544 Tenant Information Department 700 control section 743 Member ID Department 5311 Member ID Department 5312 Incorrect Memory Unit 5431 Member ID Department 5432 Member Information Department 5433 Point Information Department [Prior art documents] [Patent documents]

[0083] [Patent Document 1] Patent Publication No. 2021-174210

Claims

1. a receiving unit that receives, from a store server installed in the store, management information that is master information related to store management stored in the store server; an intermediate storage unit that stores the received management information; an update storage unit that is installed in a tenant in the store and that stores the management information that has been changed based on change information that changes the management information and that is received from a product sales data processing device used in a registration process for products sold by the tenant; a determination means for determining, based on the management information stored in the intermediate storage unit and the management information stored in the update storage unit, whether the management information stored in the intermediate storage unit is invalid data that will result in an error when the management information stored in the update storage unit is updated based on the management information; an update means for updating the management information stored in the update storage unit based on the management information stored in the intermediate storage unit when the determination means determines that the data is not invalid; a notification means for notifying the store server that the management information stored in the intermediate storage unit is invalid data without executing the update means when the determination means determines that the data is invalid; A management server with

2. The management information is member information related to members of the store. The management server according to claim 1 .

3. the update means updates the management information stored in the update storage unit at a predetermined timing. The management server according to claim 1 .

4. a list creation unit that creates a list including invalid information indicating the cause of the management information stored in the intermediate storage unit being invalid data; The notification means transmits the created list to the store server. The management server according to claim 1 .

5. The determination means determines that the member-site information stored in the intermediate storage unit is invalid data if information on a slot numbered by the management server for storing new information in the member-site information is not included in the member-site information stored in the intermediate storage unit. The management server according to claim 2 .

6. a computer as a management server, the computer comprising: a receiving unit that receives, from a store server installed in a store, management information that is master information related to store management stored in the store server; an intermediate storage unit that stores the received management information; and an update storage unit that is installed in a tenant that opens in the store and that stores management information that has been changed based on change information that changes the management information and that is received from a product sales data processing device that is used for registering products sold by the tenant; a determination means for determining, based on the management information stored in the intermediate storage unit and the management information stored in the update storage unit, whether the management information stored in the intermediate storage unit is invalid data that will result in an error when the management information stored in the update storage unit is updated based on the management information; an update means for updating the management information stored in the update storage unit based on the management information stored in the intermediate storage unit when the determination means determines that the data is not invalid; a notification means for notifying the store server that the management information stored in the intermediate storage unit is invalid data without executing the update means when the determination means determines that the data is invalid; A program to make it function as such.

Images