Information processing system, information processing method, and information processing program

Abstract

When selling products to customers, the challenge is to efficiently understand customer attributes. [Solution] The SNS server 50 notifies the customer of the LP, and if the customer applies for the CP based on the LP, the management server 20 obtains the retail member ID from the AP server 30, generates a linked ID, and sends the linked ID to the SNS server 50 via the AP server 30. The management server 20 then obtains the manufacturer company ID, manufacturer member ID, and linked ID from the SNS server 50, and can link the retail member ID and manufacturer member ID based on the linked ID.

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and an information processing program capable of efficiently grasping customer attributes when selling products to customers.

Background Art

[0002] Conventionally, manufacturers may want to know what kind of customers are purchasing the products manufactured by the company. For example, if it is possible to grasp the fact that the products manufactured by the company are being purchased by a large number of women in their 20s, it can be utilized for new product development.

[0003] However, products manufactured by manufacturers are often sold through retail stores. And since it is not possible to identify the manufacturer's members from the ID-POS data collected at the store, the manufacturer side cannot analyze the member information held by the company in association with the ID-POS data. [[ID=!4]]

[0004] For this reason, Patent Document 1 discloses a technique in which a customer's face image is acquired at a store, customer recognition information (GID) is specified based on the face image, ID-POS data in which the GID acquired by the management server from the store is associated with the POS data is obtained, and the POS data in which the GID of the ID-POS data is converted into a manufacturer member ID is provided to the manufacturer.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, the system described in Patent Document 1 requires the acquisition of facial images, which necessitates the installation of cameras within the store. In addition, it requires the development of an interface for transmitting GID from the store terminal to the POS terminal, which increases the initial cost of system implementation.

[0007] The present invention was made to solve the problems (challenges) of the above-mentioned prior art, and aims to provide an information processing system, information processing method, and information processing program that can efficiently grasp customer attributes when selling products to customers. [Means for solving the problem]

[0008] To solve the above-mentioned problems and achieve the objective, the present invention provides an information processing system having a management device for managing a link between a first identification information that uniquely identifies a customer and a second identification information that uniquely identifies the customer, wherein the management device comprises: a first acquisition unit that acquires the first identification information from a customer terminal owned by the customer; an issuing unit that issues linked identification information for linking the first identification information and the second identification information; a storage unit that stores first combined data including the first identification information and the linked identification information; a second acquisition unit that notifies a predetermined external device of the linked identification information and acquires the second identification information and the linked identification information from the external device; and an update processing unit that performs an update process to update the first combined data stored in the storage unit to second combined data including the first identification information and the second identification information based on the linked identification information acquired by the second acquisition unit.

[0009] Furthermore, the present invention is characterized in that, in the above invention, the first identification information is identification information issued by a seller who sells the goods, and the second identification information is identification information issued by a manufacturer who manufactures the goods.

[0010] Furthermore, the present invention is characterized in that, in the above invention, the update processing unit identifies the first combined data having the linked identification information from among the one or more combined data stored in the storage unit, and performs an update processing to update the identified first combined data to the second combined data including the first combined data and the second identification information, and then stores it in the storage unit.

[0011] Furthermore, the present invention is characterized in that, in the above invention, the management device comprises a third acquisition unit that acquires the first identification information and POS data of products purchased by the customer, and a notification means that identifies the second identification information from one or more of the second combined data stored in the storage unit based on the first identification information acquired by the third acquisition unit, and notifies the manufacturer's server device of the identified second identification information and the POS data.

[0012] Furthermore, the present invention is characterized in that, in the above invention, the first acquisition unit displays application information on the input screen of the customer terminal in which the customer applies for the granting of a predetermined benefit, and the customer inputs the first identification information on the input screen and makes an application for the granting of the benefit in accordance with the application information, thereby acquiring the first identification information.

[0013] Furthermore, the present invention is characterized in that, in the above invention, the external device is an SNS server of a business operator providing social networking services.

[0014] Furthermore, the present invention is characterized in that, in the above invention, the external device is a server device of the manufacturer operated by the manufacturer.

[0015] Furthermore, the present invention relates to an information processing method in an information processing system having a management device that manages a link between a first identification information that uniquely identifies a customer and a second identification information that uniquely identifies the customer, wherein the management device includes a first acquisition step of acquiring the first identification information from a customer terminal owned by the customer; an issuance step of issuing linked identification information for linking the first identification information and the second identification information; a storage step of storing first combined data including the first identification information and the linked identification information in a predetermined storage unit; a second acquisition step of notifying a predetermined external device of the linked identification information and acquiring the second identification information and the linked identification information from the external device; and an update processing step of performing an update process to update the first combined data stored in the storage unit to second combined data including the first identification information and the second identification information based on the linked identification information acquired in the second acquisition step.

[0016] Furthermore, the present invention relates to an information processing program executed by a management device that manages a link between a first identification information that uniquely identifies a customer and a second identification information that uniquely identifies the customer, wherein the management device causes a computer to execute the following: a first acquisition procedure for acquiring the first identification information from a customer terminal owned by the customer; an issuance procedure for issuing linked identification information to link the first identification information and the second identification information; a storage procedure for storing first combined data including the first identification information and the linked identification information in a predetermined storage unit; a second acquisition procedure for notifying a predetermined external device of the linked identification information and acquiring the second identification information and the linked identification information from the external device; and an update processing procedure for updating the first combined data stored in the storage unit to second combined data including the first identification information and the second identification information based on the linked identification information acquired by the second acquisition procedure. [Effects of the Invention]

[0017] According to the present invention, manufacturers or service providers can efficiently identify customers who receive their goods or services. [Brief explanation of the drawing]

[0018] [Figure 1] Figure 1 is a diagram showing the system configuration of the information processing system according to Embodiment 1. [Figure 2] Figure 2 is a diagram showing the outline of the information processing system shown in Figure 1 (when ID is linked). [Figure 3] Figure 3 is a diagram showing the outline of the information processing system shown in Figure 1 (when POS data is transmitted). [Figure 4] Figure 4 is a functional block diagram showing the configuration of the management server shown in Figure 1. [Figure 5] Figure 5 is a diagram showing an example of manufacturer member ID data shown in Figure 4. [Figure 6] Figure 6 is a diagram showing an example of linked ID data shown in Figure 4. [Figure 7] Figure 7 is a diagram showing an example of ID-POS data shown in Figure 4. [Figure 8] Figure 8 is a diagram showing an example of POS data with manufacturer member ID shown in Figure 4. [Figure 9] Figure 9 is an explanatory diagram for explaining the update of linked ID data. [Figure 10] Figure 10 is a functional block diagram showing the configuration of the AP server shown in Figure 1. [Figure 11] Figure 11 is a functional block diagram showing the configuration of the customer terminal shown in Figure 1. [Figure 12] Figure 12 is a functional block diagram showing the configuration of the SNS server shown in Figure 1. [Figure 13] Figure 13 is a functional block diagram showing the configuration of the manufacturer server shown in Figure 1. [Figure 14] Figure 14 is a functional block diagram showing the configuration of the POS terminal shown in Figure 1. [Figure 15] Figure 15 is a sequence diagram showing the processing procedure (Part 1) when ID is linked in the information processing system according to Embodiment 1. [Figure 16]Figure 16 is a sequence diagram showing the processing procedure (part 2) when an ID is linked in the information processing system according to Embodiment 1. [Figure 17] Figure 17 is a sequence diagram showing the processing procedure when transmitting POS data in the information processing system according to Embodiment 1. [Figure 18] Figure 18 shows an overview of the information processing system according to Embodiment 2 (when IDs are linked). [Figure 19] Figure 19 is a sequence diagram showing the processing procedure (part 1) when an information processing system according to Embodiment 2 is linked to an ID. [Figure 20] Figure 20 is a sequence diagram showing the processing procedure (part 2) when an ID is linked in the information processing system according to Embodiment 2. [Figure 21] Figure 21 shows an example of a hardware configuration. [Modes for carrying out the invention]

[0019] Embodiments of the information processing system, information processing method, and information processing program according to the present invention will be described in detail below with reference to the drawings. In this embodiment, we will describe a case in which a customer purchases a product manufactured by a manufacturer. Furthermore, it is assumed that such a product is marked with a code that uniquely identifies the product. For example, it is assumed that the product is marked with a barcode that includes a JAN (Japanese Article Number) code, which is a standardized code for distribution in Japan that is based on the international standard EAN (European Article Number).

[0020] Furthermore, customers are assumed to have registered their personal information and hold accounts on multiple manufacturers' websites, apps, and social media, as well as on the websites, apps, and social media of multiple retailers (supermarkets, drugstores, department stores, convenience stores, etc.). Manufacturers are assumed to hold the personal information of customers who have registered on their own websites, apps, and official social media accounts.

[0021] [Embodiment 1] <System Configuration of Information Processing System> An overview of the information processing system according to Embodiment 1 will be described. Figure 1 is a diagram showing the system configuration of the information processing system according to Embodiment 1. As shown in Figure 1, the information processing system according to Embodiment 1 has a configuration in which a management server 20, an application server (hereinafter referred to as "AP server 30"), a customer terminal 40, an SNS server 50, a manufacturer server 60, and a plurality of POS terminals 80 are connected to a network N.

[0022] There are multiple stores named 70, and store 70-1 is equipped with POS terminals 80-1 to 80q. Store 70-p is equipped with POS terminals 80-1 to 80-r. Similarly, other stores are equipped with multiple POS terminals. p, q, and r are all positive numbers, and their values ​​may be the same or different. Hereafter, "store 70" may refer to any of stores 70-1 to 70-p, or it may refer to stores 70-1 to 70-p as a whole. Similarly, "POS terminal 80" may refer to any of POS terminals 80-1 to 80-q and POS terminals 80-1 to 80-r, or it may refer to POS terminals 80-1 to 80-q and POS terminals 80-1 to 80-r as a whole.

[0023] The management server 20 is a server device that links the identification information of retail customers (hereinafter referred to as "retail member ID") obtained from the customer terminal 40 with the manufacturer member ID on the customer's SNS, which is managed by the manufacturer server 60, based on a linked ID, and manages them as linked ID data. When a customer purchases a product at store 70 using their retail member ID, the management server 20 matches the retail member ID obtained from the POS terminal 80 with the retail member ID included in the linked ID data, extracts the target, converts the retail member ID to a manufacturer member ID, and transmits the manufacturer member ID and product information to the manufacturer server 60. The management server 20 may be installed as hardware within the company operating the management server 20, or it may be implemented as a web server or cloud server (the same applies to other servers below).

[0024] The AP server 30 is a server device that provides customers with landing pages (hereinafter abbreviated as "LP") for campaigns (hereinafter abbreviated as "CP") requested by manufacturers, companies operating the management server 20, or retailers. The LP may also include application information for customers to apply for benefits, encouraging customer participation. When a customer accesses the LP and enters their retail member ID, the AP server 30 provides the retail member ID to the management server 20 and receives the linked ID generated by the management server 20. Furthermore, upon receiving the linked ID from the management server 20, the AP server 30 transmits the manufacturer company ID and campaign ID included in the LP, along with the linked ID, to the management server 20.

[0025] The customer terminal 40 is a mobile device such as a smartphone or tablet owned by the customer, or a PC, and is a terminal device capable of accessing the HTTP server. This explanation will focus on the case where the customer uses a mobile device such as a smartphone or tablet owned by the customer. The customer terminal 40 has a customer terminal application provided by the SNS server 50 installed. The customer terminal application is a smartphone application provided to customers by the SNS operating company that operates the SNS server 50, and has functions such as sending messages to customers and announcing campaigns. The customer terminal application may be an application that is downloaded and installed on the device (a so-called "native application"), or an application that does not require downloading and runs in a browser (a so-called "web application"). In the following explanation, the customer terminal application will be described as a native application, but there will be no substantial difference compared to the case where the customer terminal application is a web application.

[0026] The SNS server 50 is a server device that provides social networking services to the customer terminal 40. The SNS server 50 also performs login processing, authorization processing for linking the customer's manufacturer member ID, and processing for sending the manufacturer member ID to the management server 20.

[0027] The manufacturer server 60 is a server device owned by the manufacturer that produces the products. It stores manufacturer member IDs and processes the reception of POS data with manufacturer member IDs transmitted from the management server 20. The manufacturer server 60 can also analyze what products manufactured by the manufacturer a customer is purchasing based on the manufacturer member IDs included in the POS data with manufacturer member IDs.

[0028] The POS terminal 80 is installed in stores 70 of retail businesses and other establishments, and is a terminal device that collects and records information about each product (product name, price, time of sale, etc.) on an individual item basis at the point of sale where the product is sold and payment is made. The POS terminal 80 can communicate with the management server 20 and the store controller (not shown).

[0029] In practice, the POS system consists of POS terminals 80 and a store controller that oversees them. The POS terminals 80 obtain information about the products handled by the stores 70 from a product database (not shown) in the store controller, and the store controller manages product inventory and other information by analyzing the data from the POS terminals 80. For the sake of simplicity, here we will assume that the POS system is composed of POS terminals 80 and that the functions of the POS system are provided by the POS terminals 80. However, some of the functions of the POS terminals 80 and the store controller may be provided by a server (not shown) at headquarters that manages multiple stores 70.

[0030] <Overview of the Information Processing System> Next, an overview of the information processing system during ID linking will be described. Figure 2 is a diagram showing an overview of the information processing system (during ID linking) shown in Figure 1. As shown in Figure 2, in the information processing system according to Embodiment 1, the SNS server 50 sends an LP notification to the customer terminal 40 (S1). It is assumed that the LP contains data for the retail company ID, manufacturer company ID, and campaign ID.

[0031] If the customer terminal 40 accesses the LP (S2), enters their retail member ID, and applies for the CP listed on the LP, the AP server 30 notifies the management server 20 of the retail company ID and retail member ID (S3). Upon receiving the retail company ID and retail member ID, the management server 20 registers the retail member ID and generates a linked ID (S4). Then, the management server 20 notifies the AP server 30 of the linked ID (S5).

[0032] When AP server 30 receives notification of the linked ID from management server 20, it notifies management server 20 of the manufacturer company ID, linked ID, and campaign ID (S6). Subsequently, management server 20 generates an SNS login URL for logging into SNS server 50 (S7). This SNS login URL includes data such as the manufacturer company ID and linked ID. Then, management server 20 notifies AP server 30 of this SNS login URL (S8).

[0033] When AP server 30 receives an SNS login URL from management server 20, it redirects to SNS server 50 based on the received SNS login URL (S9) and sends a login request to SNS server 50. When SNS server 50 is redirected with an SNS login URL from AP server 30, it sends a login screen to customer terminal 40 (S10). When customer terminal 40 has entered the login data required for login (user ID and password), it sends the login data to SNS server 50 (S11).

[0034] If the login is successful, the SNS server 50 sends a notification to the customer terminal 40 indicating whether or not it authorizes the customer to provide their manufacturer member ID (S12). If the customer terminal 40 authorizes the customer to provide their manufacturer member ID, it notifies the SNS server 50 of the authorization (S13).

[0035] When the SNS server 50 receives a permission notification, it sends an access permission code to the management server 20 to access the SNS server 50 (S14). The access permission code includes the manufacturer company ID and linked ID as parameters. The management server 20 sends a user data request with the access permission code attached (S15). The SNS server 50 then sends user data (manufacturer member ID) to the management server 20 (S16). The SNS server 50 redirects the customer by specifying the manufacturer company ID as a parameter in the login URL sent from the management server 20, and the customer performs SNS login using login data already registered in the customer terminal application (user ID and password, etc.) or login data entered by the customer on the screen. As a result, the SNS server 50 can identify user data (manufacturer member ID) that is unique to each company based on the manufacturer company ID and login data, and send it to the management server 20 as user data (manufacturer member ID) for a specific customer.

[0036] When the management server 20 receives user data from the SNS server 50, it links the manufacturer company ID and linked ID obtained as parameters of the access permission code with the user data (manufacturer member ID), searches for the linked ID data 24b, and links the manufacturer member ID and retail member ID based on the linked ID data (S17). Then, the management server 20 sends a request to the AP server 30 to display the application completion screen (S18). The AP server 30 sends an instruction to the customer terminal 40 to display the application completion screen (S19).

[0037] Next, an overview of the information processing system during POS data transmission will be described. Figure 3 shows an overview of the information processing system shown in Figure 1 (during POS data transmission). As shown in Figure 3, the customer operates the customer terminal 40 and displays the retail member ID on the operation display of the customer terminal 40 (S20). The POS terminal 80 reads the retail member ID displayed on the customer terminal 40 (S21). The retail member ID can be read using, for example, a barcode reader.

[0038] The POS terminal 80 then reads the barcode of the product purchased by the customer using a barcode reader and processes the payment for the purchased product (S22). Here, the payment processing is performed by reading the credit card information and using a payment server (not shown), etc. Alternatively, the payment processing may be done using a smartphone payment system with a two-dimensional barcode.

[0039] Once the payment processing is complete, the POS terminal 80 sends ID-POS data to the management server 20, including the store code, date and time, register number, retail member ID, product code, JAN code, and product name (S23). The management server 20 matches the retail member ID in the received ID-POS data with the retail member ID in the linked ID data and extracts the target data (S24). The management server 20 replaces the retail member ID in the target data of the ID-POS data with the manufacturer member ID (S25).

[0040] The management server 20 transmits linked ID data and POS data with manufacturer member ID, including store code, date and time, product code, JAN code, product name, and manufacturer member ID, to the manufacturer server 60 (S26).

[0041] By performing the above series of processes, the management server 20 can link the customer's retail member ID and manufacturer member ID based on the linked ID. Furthermore, when a customer purchases a product at a retail store using their retail member ID, the management server 20 matches the retail member ID included in the ID-POS data with the retail member ID in the linked ID data to extract the relevant data, replaces the retail member ID in the relevant data with the manufacturer member ID, and sends the POS data and manufacturer member ID to the manufacturer server 60. This allows the manufacturer to efficiently track the customers receiving their products.

[0042] As described above, according to Embodiment 1, when the SNS server 50 notifies a customer of an LP and the customer applies for a CP based on the LP, the management server 20 obtains the retail member ID from the AP server 30, generates a linked ID, and sends it to the SNS server 50 via the AP server 30. The management server 20 then obtains the manufacturer member ID and linked ID from the SNS server 50 and can link the retail member ID and manufacturer member ID based on the linked ID. Furthermore, the management server 20 is configured to obtain ID-POS data including the retail member ID from the POS terminal 80 when a customer purchases a product using the retail member ID, and to send POS data with the manufacturer member ID attached, in which the retail member ID has been replaced with the manufacturer member ID, to the manufacturer server 60. This allows the manufacturer to efficiently track customers who receive products.

[0043] <Configuration of Management Server 20> Next, the configuration of the management server 20 shown in Figure 1 will be described. Figure 4 is a functional block diagram showing the configuration of the management server 20 shown in Figure 1. As shown in Figure 4, the management server 20 has a display unit 21, an input unit 22, a communication I / F unit 23, a storage unit 24, and a control unit 25. The display unit 21 is a display device such as a liquid crystal panel, an organic EL (electroluminescent) display, or a display device, and the input unit 22 is an input device such as a keyboard and a mouse. The communication I / F unit 23 is a communication interface unit for communicating with the AP server 30, customer terminal 40, SNS server 50, manufacturer server 60, and POS terminal 80 via the network N.

[0044] The storage unit 24 is a storage device consisting of a hard disk drive, volatile memory, or non-volatile memory, and stores manufacturer member ID data 24a, linked ID data 24b, ID-POS data 24c, and manufacturer member ID-attached POS data 24d.

[0045] The manufacturer member ID data 24a is data of manufacturer member IDs sent from the SNS server 50. The manufacturer member ID data 24a associates, for example, the manufacturer company ID, the manufacturer member ID, and the linked ID. Figure 5 is a diagram showing an example of the manufacturer member ID data 24a shown in Figure 4. As shown in Figure 5, here the manufacturer company ID "M0001" is associated with the manufacturer member ID "1122334455" and the linked ID "XYZ999".

[0046] The linked ID data 24b is data that links retail member IDs and manufacturer member IDs based on the linked ID. Figure 6 shows an example of the linked ID data 24b shown in Figure 4. As shown in Figure 6, this shows that the retail company ID "R0001", retail member ID "1234567890", linked ID "XYZ999", manufacturer company ID "M0001", and manufacturer member ID "1122334455" are associated with the update date and time "2024 / 10 / 15 15:30:55". Note that the linked ID data 24b may be generated each time the application button is pressed, or it may be generated for each campaign ID.

[0047] ID-POS data 24c is data transmitted from the POS terminal 80 regarding the customer's retail member ID and the customer's purchased items. For example, ID-POS data 24c associates the store code, date and time, register number, retail member ID, product code, JAN code, and product name. Figure 7 shows an example of ID-POS data 24c shown in Figure 4. As shown in Figure 7, the store code "011" is associated with the date and time "2024 / 10 / 15 10:21:04", register number "003", retail member ID "1234567890", product code "MB00482", JAN code "45124569134", and product name "XX Beer".

[0048] POS data 24d with manufacturer member ID is POS data obtained by replacing the retail member ID with the manufacturer member ID in the ID-POS data 24c. Figure 8 shows an example of POS data 24d with manufacturer member ID shown in Figure 4. As shown in Figure 8, the store code "011" is associated with the date and time "2024 / 10 / 15 10:21:04", the register number "003", the manufacturer member ID "1122334455", the product code "MB00482", the JAN code "45124569134", and the product name "XX Beer".

[0049] The control unit 25 is a control unit that performs overall control of the management server 20 and includes a retail member ID acquisition unit 25a, a linked ID generation unit 25b, a linked ID registration unit 25c, an SNS login URL generation unit 25d, a manufacturer member ID acquisition unit 25e, a linked ID verification unit 25f, a linked ID update unit 25g, an ID-POS data acquisition unit 25h, an ID replacement unit 25i, and a manufacturer member ID-attached POS data transmission unit 25j. In practice, these programs are loaded into memory and executed by the CPU, causing the processes corresponding to the retail member ID acquisition unit 25a, the linked ID generation unit 25b, the linked ID registration unit 25c, the SNS login URL generation unit 25d, the manufacturer member ID acquisition unit 25e, the linked ID verification unit 25f, the linked ID update unit 25g, the ID-POS data acquisition unit 25h, the ID replacement unit 25i, and the manufacturer member ID-attached POS data transmission unit 25j to be executed.

[0050] The Retail Member ID Acquisition Unit 25a is a processing unit that acquires the Retail Member ID from the customer terminal 40. Specifically, when a customer enters their Retail Member ID into the customer terminal 40 and applies for a campaign displayed on the landing page, the unit acquires the Retail Member ID entered by the customer. The Linked ID Generation Unit 25b is a processing unit that, once the Retail Member ID has been acquired, generates a Linked ID corresponding to the Retail Member ID.

[0051] The linked ID registration unit 25c is a processing unit that associates the retail member ID with the linked ID and stores it in the storage unit 24 as linked ID data, and also transmits the generated linked ID to the AP server 30.

[0052] The SNS login URL generation unit 25d is a processing unit that generates a redirect URL for logging into the SNS server 50. When generating a redirect URL, the SNS login URL generation unit 25d adds the linked ID generated by the linked ID generation unit 25b and the manufacturer company ID as parameters.

[0053] The manufacturer member ID acquisition unit 25e is a processing unit that acquires manufacturer member IDs from the SNS server 50. Specifically, when the manufacturer member ID acquisition unit 25e receives an access permission code including the manufacturer company ID and linked ID from the SNS server 50, it sends a user data request to the SNS server 50 requesting the transmission of user data, and receives the user data transmitted from the SNS server 50.

[0054] The linked ID matching unit 25f is a processing unit that links the manufacturer member ID obtained by the manufacturer member ID acquisition unit 25e with the linked ID, and compares the linked ID associated with the retail member ID with the linked ID registered in the linked ID data 24b.

[0055] The linked ID update unit 25g is a processing unit that updates linked ID data by linking retail member IDs and manufacturer member IDs whose linked IDs match, based on the matching results of the linked ID matching unit 25f.

[0056] The ID-POS data acquisition unit 25h is a processing unit that acquires ID-POS data, including store code, date and time, register number, retail member ID, product code, JAN code, and product name, from the POS terminal 80. Specifically, when a customer presents their retail member ID and purchases a product at a retail store, the ID-POS data acquisition unit 25h acquires data, including the retail member ID and the purchased product, from the POS terminal 80 installed in the store 70.

[0057] The ID replacement unit 25i is a processing unit that matches the retail member ID included in the ID-POS data with the retail member ID included in the linked ID data, extracts the target data, replaces the retail member ID in the extracted data with the manufacturer member ID, and generates POS data 24d with manufacturer member IDs.

[0058] The manufacturer member ID-attached POS data transmission unit 25j is a processing unit that transmits the manufacturer member ID-attached POS data 24d generated by the ID replacement unit 25i to the manufacturer server 60 along with the concatenated ID data 24b. The manufacturer server 60 can analyze the number of customers who applied for the campaign but did not purchase products, the number of customers who applied for the campaign and purchased products, etc., by analyzing the manufacturer member ID-attached POS data 24d and the concatenated ID data 24b.

[0059] <Update of linked ID data 24b> Next, we will explain how to update the linked ID data 24b of the management server 20. Figure 9 is an explanatory diagram illustrating the update of linked ID data. As shown in Figure 9(a), when the management server 20 receives the retail company ID and retail member ID from the AP server 30 and generates a linked ID, the manufacturer company ID and manufacturer member ID have not yet been obtained, so the linked ID data 24b is generated with these fields blank.

[0060] This shows the situation where the update date and time "2024 / 10 / 15 15:30:55" is associated with the retail company ID "R0001", retail member ID "1234567890", linkage ID "XYZ999", manufacturer company ID "-", and manufacturer member ID "-".

[0061] As shown in Figure 9(b), when the management server 20 receives user data from the SNS server 50, including a linked ID, a manufacturer company ID, and a manufacturer member ID, it associates the linked ID, the manufacturer company ID, and the manufacturer member ID, searches for linked ID data 24b based on the linked ID, and if the linked ID is found, it updates the linked ID data 24b by adding the manufacturer company ID and manufacturer member ID to the target data.

[0062] Here, it shows a situation where the update date and time "2024 / 10 / 15 15:33:43" is associated with the retail company ID "R0001", the retail member ID "1234567890", the link ID "XYZ999", the manufacturer company ID "M0001", and the manufacturer member ID "1122334455".

[0063] <Configuration of AP Server 30> Next, the configuration of the AP server 30 shown in FIG. 1 will be described. FIG. 10 is a functional block diagram showing the configuration of the AP server 30 shown in FIG. 1. As shown in FIG. 10, the AP server 30 includes a display unit 31, an input unit 32, a communication I / F unit 33, a storage unit 34, and a control unit 35. The display unit 31 is a display device such as a liquid crystal panel, an organic EL (electroluminescence), or a display device, and the input unit 32 is an input device such as a keyboard and a mouse. The communication I / F unit 33 is a communication interface unit for communicating with the management server 20, the customer terminal 40, and the SNS server 50 via the network N. The storage unit 34 is a storage device composed of a hard disk device, a volatile memory, a non-volatile memory, or the like.

[0064] The control unit 35 is a control unit that performs overall control of the AP server 30, and includes an application processing unit 35a, a retail member ID transmission unit 35b, a link ID acquisition unit 35c, a manufacturer company ID transmission unit 35d, an SNS login URL processing unit 35e, and an application completion processing unit 35f. Actually, by loading these programs into the memory and executing them with the CPU, processes corresponding to the application processing unit 35a, the retail member ID transmission unit 35b, the link ID acquisition unit 35c, the manufacturer company ID transmission unit 35d, the SNS login URL processing unit 35e, and the application completion processing unit 35f will be executed respectively.

[0065] The application processing unit 35a is a processing unit that, when a customer accesses the LP from the customer terminal 40 and enters a retail member ID, retrieves the retail company ID included in the LP and the entered retail member ID. The retail member ID transmission unit 35b is a processing unit that transmits the retrieved retail company ID and retail member ID to the management server 20.

[0066] The linked ID acquisition unit 35c is a processing unit that acquires the linked ID transmitted from the management server 20. The manufacturer company ID transmission unit 35d is a processing unit that transmits the manufacturer company ID and campaign ID containing the LP, along with the linked ID acquired from the management server 20, to the management server 20.

[0067] The SNS login URL processing unit 35e is a processing unit that receives the SNS login URL from the management server 20 and forwards it to the SNS server 50. The application completion processing unit 35f is a processing unit that, upon receiving a request from the management server 20 to display the application completion screen, instructs the customer terminal 40 to display the application completion screen.

[0068] <Configuration of customer terminal 40> Next, the configuration of the customer terminal 40 shown in Figure 1 will be explained. Figure 11 is a functional block diagram showing the configuration of the customer terminal 40 shown in Figure 1. The customer terminal 40 is a mobile device such as a smartphone or tablet owned by the customer, and is a terminal device that can access the AP server 30 and the SNS server 50. The customer terminal 40 has the customer terminal application provided by the SNS server 50 to customers who subscribe to the information processing system installed.

[0069] When a customer launches the customer terminal application on customer terminal 40, the SNS server 50 notifies them of a landing page (LP) related to the campaign. If the customer clicks on the LP's URL, they can access the LP operated by the AP server 30. After that, if the customer enters their retail member ID on the LP and clicks the campaign application button, the retail company ID and retail member ID are notified to the management server 20.

[0070] As shown in FIG. 11, the customer terminal 40 includes an operation display unit 41, a communication I / F unit 42, a storage unit 44, and a control unit 45. The operation display unit 41 is an input / output device composed of a liquid crystal panel, an organic EL (electroluminescence), etc. The communication I / F unit 42 is an interface unit that communicates with the AP server 30, the SNS server 50, etc. via the network N. The storage unit 44 is a storage device composed of a hard disk device, a volatile memory, a non-volatile memory, etc.

[0071] The control unit 45 is a control unit that performs overall control of the customer terminal 40 and has a browser 45a. Actually, a program corresponding to the customer terminal application corresponding to the browser is stored in the storage unit 44, this customer terminal application is loaded into the memory, and executed by the CPU, thereby causing the process corresponding to the browser 45a to be executed.

[0072] The browser 45a is a browser for accessing various web pages. If the URL of the LP related to the CP is clicked, this browser 45a is launched and can access the corresponding LP in the AP server 30. If the retail member ID is input on such an LP and the CP application is made, the retail company ID included in the LP and the input retail member ID are notified from the AP server 30 to the management server 20.

[0073] <Configuration of the SNS server 50> Next, the configuration of the SNS server 50 shown in FIG. 1 will be described. FIG. 12 is a functional block diagram showing the configuration of the SNS server 50 shown in FIG. 1. The SNS server 50 is a server that provides a social networking service to customers. The SNS server 50 performs processes such as login processing for the customer's SNS service, authorization processing related to the provision of SNS account IDs, and provision of user data.

[0074] As shown in Figure 12, the SNS server 50 includes a display unit 51, an input unit 52, a communication interface unit 53, a storage unit 54, and a control unit 55. The display unit 51 is a display device such as a liquid crystal panel, an organic EL (electroluminescent) display, or a display device, and the input unit 52 is an input device such as a keyboard and a mouse. The communication interface unit 53 is a communication interface unit for communicating with the management server 20, the AP server 30, and the customer terminal 40 via the network N.

[0075] The storage unit 54 is a storage device consisting of a hard disk drive, volatile memory, or non-volatile memory, and stores manufacturer member ID data 54a. The manufacturer member ID data 54a is data of a member ID on a manufacturer's official SNS on the SNS server 50.

[0076] The control unit 55 is a control unit that performs overall control of the SNS server 50 and includes a login processing unit 55a, an authorization processing unit 55b, and a manufacturer member ID transmission unit 55c. In practice, these programs are loaded into memory and executed by the CPU, causing the login processing unit 55a, the authorization processing unit 55b, and the manufacturer member ID transmission unit 55c to execute processes corresponding to each other.

[0077] The login processing unit 55a is the processing unit that handles cases when a customer logs in to the SNS server 50. Specifically, the login processing unit 55a sends a login screen to the customer terminal 40, and once the customer enters the necessary login data such as user ID and password, it determines whether the login is permitted. If the entered data matches the registered data, it allows the customer to log in to the SNS server 50.

[0078] The authorization processing unit 55b is a processing unit that processes whether or not to authorize the provision of user data stored on the SNS server 50. Specifically, the authorization processing unit 55b sends a screen to the customer terminal 40 asking for authorization, and displays the authorization / authorization screen on the customer terminal 40. If the customer clicks "authorize" on the authorization / authorization screen, it sends an access permission code to the management server 20 to provide the user data to the management server 20. The access permission code is provided with the manufacturer company ID and the linked ID as parameters.

[0079] The manufacturer member ID transmission unit 55c is a processing unit that, when a user data request is sent from the management server 20 with an access permission code attached, transmits user data (manufacturer member ID) to the management server 20.

[0080] <Configuration of Manufacturer Server 60> Next, the configuration of the manufacturer server 60 shown in Figure 2 will be explained. Figure 13 is a functional block diagram showing the configuration of the manufacturer server 60 shown in Figure 1. The manufacturer server 60 is a server device owned by a manufacturer that produces goods. The manufacturer server 60 receives linked ID data 24b and POS data 24d with manufacturer member ID from the management server 20. The manufacturer server 60 may analyze the purchase status of the manufacturer's products based on the received data.

[0081] As shown in Figure 13, the maker server 60 includes a display unit 61, an input unit 62, a communication interface unit 63, a storage unit 64, and a control unit 65. The display unit 61 is a display device such as a liquid crystal panel, an organic EL (electroluminescent) display, or a display device, and the input unit 62 is an input device such as a keyboard and a mouse. The communication interface unit 63 is a communication interface unit for communicating with the management server 20 via the network N.

[0082] The storage unit 64 is a storage device composed of a hard disk drive, a volatile memory, a non-volatile memory, etc., and stores manufacturer member ID data 64a, POS data with manufacturer member ID 64b, and member ID conversion data 64c. The manufacturer member ID data 64a is the data of the member ID in the official SNS of a certain manufacturer on the SNS server 50. The POS data with manufacturer member ID 64b is the data of the manufacturer member ID received from the management server 20 and the data of products purchased by customers, etc. The member ID conversion data 64c is the data for converting the manufacturer member ID managed on the SNS obtained from the management server 20 and the customer ID managed by the manufacturer side. By using the member ID conversion data 64c to convert the manufacturer member ID of the POS data with manufacturer member ID to the customer ID, information such as the customer's name, gender, and attributes can be linked.

[0083] The control unit 65 is a control unit that performs overall control of the manufacturer server 60 and has a POS data reception unit 65a with manufacturer member ID. Actually, by loading these programs into the memory and executing them with the CPU, a process corresponding to the POS data reception unit 65a with manufacturer member ID will be executed.

[0084] The POS data reception unit 65a with manufacturer member ID performs the process of receiving the concatenated ID data 24b and the POS data 24d with manufacturer member ID transmitted from the management server 20. Note that the manufacturer server 60 may analyze the purchase situation in the market of the products manufactured by the manufacturer based on the received data.

[0085] <Configuration of the POS terminal 80> Next, the configuration of the POS terminal 80 shown in FIG. 1 will be described. FIG. 14 is a functional block diagram showing the configuration of the POS terminal 80 shown in FIG. 1. The POS terminal 80 is installed in a store 70 such as a retail business, and at the point of sale (sales time) where product sales and payments are made, it is a terminal device that collects and records the retail member ID presented by the customer and information about the product (product name, price, sales time, etc.) on a single product basis. [[ID=X]] [[ID=Y]]

[0086] [[ID=Z]] The POS terminal 80 uses a barcode reader to read the customer's retail member ID and also reads the barcode attached to the product to identify the JAN code. This JAN code allows the terminal to identify the product type, price, etc. Subsequently, the POS terminal 80 processes the payment using a credit card or the like and transmits the ID-POS data to the management server 20.

[0087] As shown in Figure 14, the POS terminal 80 includes an operation display unit 81, a barcode reader 82, a communication interface unit 83, a storage unit 85, and a control unit 86. The operation display unit 81 is an input / output device consisting of a liquid crystal panel, an organic EL (electroluminescent) display, etc. The barcode reader 82 is a reading unit that reads the retail member ID displayed on the customer terminal 40 and the barcode attached to the product. The communication interface unit 83 is an interface unit that communicates with the management server 20 via the network N.

[0088] The storage unit 85 is a storage device consisting of a hard disk drive, volatile memory, or non-volatile memory, and stores POS data 85a, retail member ID data 85b, and product data 85c. The POS data 85a is information about products purchased by customers (product name, price, time of sale, etc.).

[0089] Retail member ID data 85b is data obtained by reading the barcode indicating the retail member ID displayed on the customer terminal 40 using the barcode reader 82. Product data 85c is data that associates the JAN code, product name, price, etc., of products displayed in the store 70.

[0090] In this embodiment 1, we will describe the case in which a barcode indicating a retail member ID displayed on the customer terminal 40 is read, but a barcode printed on a plastic card-shaped retail member card may also be read.

[0091] The control unit 86 is a control unit that performs overall control of the POS terminal 80 and includes a barcode reading unit 86a, a payment processing unit 86b, and an ID-POS data transmission unit 86c. In practice, these programs are loaded into memory and executed by the CPU, causing the barcode reading unit 86a, the payment processing unit 86b, and the ID-POS data transmission unit 86c to execute the processes corresponding to them.

[0092] The barcode reading unit 86a is a processing unit that reads the barcode indicating the retail member ID displayed on the customer terminal 40 and the barcode attached to the product purchased by the customer, and identifies the JAN code, etc. contained in the barcode. Once the JAN code, etc. is identified, the product name and price can be identified by referring to the product data 85c.

[0093] The payment processing unit 86b is a processing unit that handles payment for goods using the customer's credit card, smartphone payment, transportation IC card, etc. The product name and price are identified based on the product data 85c and JAN code. Once the payment processing is complete, it is stored in the storage unit 85 as POS data 85a. Although this explanation describes cashless payment, payment with cash is also possible.

[0094] The ID-POS data transmission unit 86c is a processing unit that transmits the customer's retail member ID and the POS data (ID-POS data) of the products purchased by the customer to the management server 20.

[0095] <Processing procedure when linking IDs in an information processing system> Next, the processing procedure for ID linking in the information processing system according to Embodiment 1 will be described. Figures 15 and 16 are sequence diagrams showing the processing procedure for ID linking in the information processing system according to Embodiment 1. As shown in Figure 15, the SNS server 50 notifies the customer terminal 40 of the LP regarding the application for the CP (step S101).

[0096] When the customer terminal 40 receives a notification from the LP, it displays the notification. When the customer accesses the LP on the AP server using the customer terminal 40 (step S102) and enters a retail member ID, the AP server 30 sends the retail company ID and retail member ID included in the LP to the management server 20 (step S103). In addition, the AP server 30 sends customer terminal identification information to the management server 20 along with the retail company ID and retail member ID.

[0097] When the management server 20 receives the retail company ID and the retail member ID, it generates a linked ID (step S104) and sends the linked ID to the AP server 30 (step S105). When the AP server 30 receives the linked ID, it sends the manufacturer company ID included in the LP, the linked ID, and the campaign ID included in the LP to the management server 20 (step S106).

[0098] When the management server 20 receives the manufacturer company ID, linking ID, and campaign ID, it generates an SNS login URL for logging into the SNS server 50 (step S107). Here, the manufacturer company ID and linking ID are added as parameters when generating the SNS login URL. The management server 20 then notifies the AP server 30 of the SNS login URL (step S108).

[0099] When AP server 30 receives notification of the SNS login URL, it forwards the SNS login URL to SNS server 50 (step S109) and makes a login request. When SNS server 50 receives the login request, it sends a login screen to customer terminal 40 (step S110). When customer terminal 40 receives the login screen, it displays the login screen on the operation display unit 41 (step S111).

[0100] If the customer enters the login data (user ID and password) required for login into the customer terminal 40, the customer terminal 40 sends the login data to the SNS server 50 (step S112). If the customer's login is successful, the SNS server 50 sends an authorization or denial to the customer terminal 40 regarding whether or not to authorize the provision of the manufacturer member ID held by the customer (step S113). If the customer approves the authorization, the customer terminal 40 sends an authorization notification to the SNS server 50 (step S114).

[0101] When the SNS server 50 receives an authorization notification from the customer terminal 40, it sends an access permission code to the management server 20 to receive user data (step S115). The access permission code is accompanied by the manufacturer company ID and linked ID as parameters. When the management server 20 receives the access permission code, it sends a user data request to the SNS server 50 using the access permission code (step S116). When the SNS server 50 receives the user data request, it sends the user data (manufacturer member ID) to the management server 20 (step S117).

[0102] When the management server 20 receives user data, it associates the manufacturer company ID and linked ID obtained as parameters of the access permission code received from the SNS server 50 with the manufacturer member ID included in the user data, searches for linked ID data 24b, and associates the manufacturer company ID, manufacturer member ID and retail member ID based on the linked ID (step S118), and updates linked ID data 24b. After that, the management server 20 notifies the AP server 30 that the application has been completed (step S119). When the AP server 30 receives the notification of application completion, it sends an application completion screen to the customer terminal 40 (S120), the customer terminal 40 displays the application completion screen (step S121), and the series of processes ends.

[0103] Through the above series of processing steps, the management server 20 can link the customer's retail member ID and the manufacturer's member ID on the official SNS using a linked ID.

[0104] <Processing procedure when transmitting POS data in an information processing system> Next, the processing procedure for POS data transmission by the information processing system according to Embodiment 1 will be described. Figure 17 is a sequence diagram showing the processing procedure for POS data transmission by the information processing system according to Embodiment 1. Here, it is assumed that a barcode indicating the customer's retail member ID is already displayed on the operation display unit 41 of the customer terminal 40.

[0105] As shown in Figure 17, the POS terminal 80 reads the retail member ID by reading the barcode displayed on the customer terminal 40 (step S201). Then, the POS terminal 80 reads the barcode of the product the customer is purchasing and processes the payment (step S202). After that, the POS terminal 80 sends the ID-POS data (retail member ID and product data) to the management server 20 (step S203).

[0106] When the management server 20 receives ID-POS data, it searches for linked data using the retail member ID included in the ID-POS data and extracts the target data (step S204). Then, the management server 20 replaces the retail member ID in the target data with the manufacturer member ID (step S205) and stores it in the storage unit as POS data with manufacturer member ID. After that, the management server 20 sends the linked ID data and the POS data with manufacturer member ID to the manufacturer server 60 (step S206). The manufacturer server 60 receives the linked ID data and the POS data with manufacturer member ID (step S207) and terminates the series of processes.

[0107] Through the above series of processing steps, the manufacturer server 60 can obtain information on customers who applied to the CP and information on customers who purchased the manufacturer's products. By analyzing this information, the server can analyze data such as what percentage of customers who applied to the CP purchased the manufacturer's products.

[0108] As described above, in this embodiment 1, the SNS server 50 notifies the customer of the LP, and if the customer applies for the CP based on the LP, the management server 20 obtains the retail member ID from the AP server 30, generates a linked ID, and sends it to the SNS server 50 via the AP server 30. The management server 20 then obtains the manufacturer member ID and linked ID from the SNS server 50 and can link the retail member ID and manufacturer member ID based on the linked ID. Furthermore, the management server 20 is configured to obtain ID-POS data including the retail member ID from the POS terminal 80 when a customer purchases a product using the retail member ID, and to send POS data with the manufacturer member ID attached, in which the retail member ID has been replaced with the manufacturer member ID, to the manufacturer server 60. This allows the manufacturer to efficiently track customers who receive products.

[0109] In the above embodiment 1, the management server 20 was described as individually obtaining linked ID data and user data (manufacturer member ID) from the SNS server 50. However, the management server 20 may also obtain the linked ID and user data (manufacturer member ID) as an SNS set from the server 50.

[0110] [Embodiment 2] By the way, in Embodiment 1 described above, the case in which the management server 20 obtains the manufacturer member ID from the SNS server 50 was explained. However, in Embodiment 2, the case in which the manufacturer server 60 obtains the manufacturer member ID from the SNS server 50 and the management server 20 obtains the manufacturer member ID via the manufacturer server 60 will be explained.

[0111] Figure 18 shows an overview of the information processing system according to Embodiment 2 (when IDs are linked). As shown in Figure 18, in the information processing system according to Embodiment 2, the SNS server 50 sends an LP notification to the customer terminal 40 (S31). The LP is assumed to contain data for the retail company ID, manufacturer company ID, and campaign ID.

[0112] If the customer accesses the LP (S32) and enters their retail member ID to apply for the CP listed on the LP, the AP server 30 notifies the management server 20 of customer terminal identification information that identifies the customer terminal 40, along with the retail company ID and retail member ID (S33). Upon receiving the retail company ID and retail member ID, the management server 20 registers the retail member ID and generates a linked ID (S34). The management server 20 then notifies the AP server 30 of the linked ID (S35).

[0113] When AP server 30 receives notification of the linked ID, it adds the linked ID as a parameter to the URL of the manufacturer's CP screen and sends a display request to manufacturer server 90 (S36). When manufacturer server 90 receives a display request from AP server 30, it generates an SNS login URL (S37). Manufacturer server 90 sends the SNS login URL to SNS server 50 (S38).

[0114] When the SNS server 50 receives an SNS login URL, it sends a login screen to the customer terminal 40 (S39). When the customer terminal 40 has entered the login data required for login (user ID and password), it sends the login data to the SNS server 50 (S40). If the login is successful, the SNS server 50 sends an authorization or denial to the customer terminal 40 regarding whether or not to authorize the provision of the customer's manufacturer member ID (S41). If the customer terminal 40 authorizes the provision of the manufacturer member ID, it notifies the SNS server 50 of the authorization (S42).

[0115] If the SNS server 50 receives a permission notification, it sends an access permission code to the manufacturer server 60 to access the SNS server 50 (S43). The manufacturer server 60 sends a user data request to the SNS server 50 with the access permission code attached (S44). Then, the SNS server 50 sends the user data (manufacturer member ID) to the manufacturer server 60 (S45).

[0116] When the manufacturer server 60 receives user data, it sends the manufacturer company ID, manufacturer member ID, and linked ID to the management server 20 (S46). When the management server 20 receives the manufacturer company ID, manufacturer member ID, and linked ID from the manufacturer server 60, it links the manufacturer member ID and retail member ID based on the linked ID (S47). Then, the management server 20 sends a request to the manufacturer server 60 to display the application completion screen (S48). The manufacturer server 60 sends an instruction to the customer terminal 40 to display the application completion screen (S49).

[0117] <Processing procedure when linking IDs in the information processing system according to Embodiment 2> Next, the processing procedure for ID linking in the information processing system according to Embodiment 2 will be described. Figures 19 and 20 are sequence diagrams showing the processing procedure for ID linking in the information processing system according to Embodiment 2. As shown in Figure 19, the SNS server 50 notifies the customer terminal 40 of the LP regarding the application for the CP (step S301). The AP server 30 transmits the customer terminal identification information, along with the retail company ID and retail member ID, to the management server 20.

[0118] If the customer terminal 40 receives a notification from the LP, it displays the notification. If the customer uses the customer terminal 40 to access the LP on the AP server (step S302) and enters a retail member ID, the AP server 30 sends the retail company ID and retail member ID included in the LP to the management server 20 (step S303).

[0119] When the management server 20 receives the retail company ID and the retail member ID, it generates a linked ID (step S304) and sends the linked ID to the AP server 30 (step S305). When the AP server 30 receives notification of the linked ID, it adds the linked ID to the URL of the manufacturer's CP screen and sends a display request to the manufacturer server 90 (step S306).

[0120] When the manufacturer server 90 receives a display request, it generates an SNS login URL for logging into the SNS server 50 (step S307). Here, the manufacturer company ID and linked ID are added as parameters when generating the SNS login URL. The manufacturer server 90 notifies the SNS server 50 of the SNS login URL (step S308).

[0121] When the SNS server 50 receives notification of the SNS login URL, it sends a login screen to the customer terminal 40 (step S309). When the customer terminal 40 receives the login screen, it displays the login screen on the operation display unit 41 (step S310). When the customer terminal 40 has entered the login data required for login (user ID and password), it sends the login data to the SNS server 50 (step S311).

[0122] If the customer's login is successful, the SNS server 50 sends a notification to the customer terminal 40 indicating whether or not to authorize the provision of the customer's manufacturer member ID (step S312). If the customer terminal 40 approves the authorization, it sends an authorization notification to the SNS server 50 (step S313). If the SNS server 50 receives the authorization notification from the customer terminal 40, it sends an access permission code with the manufacturer company ID and linked ID as parameters so that the manufacturer server 90 can receive the user data (step S314).

[0123] If the manufacturer server 90 receives an access permission code, it sends a user data request to the SNS server 50 using the access permission code (step S315). If the SNS server 50 receives the user data request, it sends the user data (manufacturer member ID) to the manufacturer server 90 (step S316). If the manufacturer server 90 receives the user data, it sends the manufacturer company ID, manufacturer member ID, and linked ID to the management server 20 (step S317).

[0124] When the management server 20 receives the manufacturer company ID, manufacturer member ID, and linked ID, it searches for linked ID data 24b using the linked ID, links the manufacturer company ID, manufacturer member ID, and retail member ID based on the linked ID (step S318), and updates the linked ID data 24b. After that, the management server 20 notifies the manufacturer server 90 that the application has been completed (step S319). When the manufacturer server 90 receives the notification of application completion, it sends an application completion screen to the customer terminal 40 (step S320), the customer terminal 40 displays the application completion screen (step S321), and the series of processes ends.

[0125] The processing procedure for POS data transmission in the information processing system according to Embodiment 2 is the same as the processing procedure for POS data transmission in the information processing system according to Embodiment 1, so a detailed explanation is omitted.

[0126] As described above, in this embodiment 2, the SNS server 50 notifies the customer of the LP, and if the customer applies to the CP based on the LP, the management server 20 obtains customer terminal identification information and retail member ID from the AP server 30, generates a linked ID, and sends it to the AP server 30. The AP server 30 then sends a request to the manufacturer server 90 to generate an SNS login URL, attaching the customer terminal identification information and linked ID. Subsequently, the manufacturer server 90 obtains the manufacturer company ID, manufacturer member ID, and linked ID from the SNS server 50 and sends the obtained manufacturer company ID, manufacturer member ID, and linked ID to the management server 20. The management server 20 can then link the retail member ID and the manufacturer member ID based on the linked ID. Furthermore, the management server 20 is configured to acquire ID-POS data including the retail member ID from the POS terminal 80 when a customer purchases a product using their retail member ID, and to send POS data with the manufacturer member ID (where the retail member ID is replaced with the manufacturer member ID) to the manufacturer server 60. This allows manufacturers to efficiently track which customers are receiving products.

[0127] Furthermore, an access permission code is required to retrieve user data from the SNS server 50. If this access permission code is made public, it could be possible to obtain the target manufacturer's user data without authorization, which could pose a problem from the perspective of information leakage. Therefore, if a manufacturer does not want to disclose this access permission code to a third party, they will be required to generate the login URL and retrieve the user data themselves. The mechanism of this embodiment 2 can fulfill this requirement.

[0128] In the above embodiment 2, the case in which the manufacturer server 90 individually obtains linked ID data and user data (manufacturer member ID) from the SNS server 50 was described, but the manufacturer server 90 may also obtain the linked ID and user data (manufacturer member ID) as a set from the SNS server 50.

[0129] <Relationship with hardware> Next, the correspondence between the management server 20 of the information processing system according to this embodiment 1 and the main hardware configuration of the computer will be described. Figure 19 is a diagram showing an example of the hardware configuration.

[0130] Generally, a computer consists of components such as a CPU 101, ROM 102, RAM 103, and non-volatile memory 104, connected by a bus 105. A hard disk drive may be provided instead of the non-volatile memory 104. For the sake of explanation, only the basic hardware configuration is shown.

[0131] Here, the ROM 102 or non-volatile memory 104 stores programs necessary for starting the operating system (hereinafter simply referred to as "OS"), and the CPU 101 reads and executes the OS program from the ROM 102 or non-volatile memory 104 when the power is turned on.

[0132] On the other hand, various application programs executed on the OS are stored in non-volatile memory 104, and the CPU 101 executes the application programs using RAM 103 as main memory, thereby executing the processes corresponding to the applications.

[0133] Furthermore, the information processing program for the management server 20 of the information processing system according to this embodiment 1 is stored in non-volatile memory 104 or the like, just like other application programs, and the CPU 101 loads and executes such management program. In the case of the management server 20 of the information processing system according to this embodiment 1, the linked ID program, which includes routines corresponding to the retail member ID acquisition unit 25a, linked ID generation unit 25b, linked ID registration unit 25c, SNS login URL generation unit 25d, manufacturer member ID acquisition unit 25e, linked ID verification unit 25f, linked ID update unit 25g, ID-POS data acquisition unit 25h, ID replacement unit 25i, and manufacturer member ID-attached POS data transmission unit 25j shown in Figure 4, is stored in non-volatile memory 104 or the like. When the CPU 101 loads and executes the information processing program, information processing processes corresponding to the retail member ID acquisition unit 25a, linked ID generation unit 25b, linked ID registration unit 25c, SNS login URL generation unit 25d, manufacturer member ID acquisition unit 25e, linked ID verification unit 25f, linked ID update unit 25g, ID-POS data acquisition unit 25h, ID replacement unit 25i, and manufacturer member ID-attached POS data transmission unit 25j are generated.

[0134] In the above embodiments 1 and 2, the case where the customer has a manufacturer member ID was described. However, if the customer does not have a manufacturer member ID, after the customer logs in to the SNS server 50, the SNS server 50 may send a screen for the procedure to obtain a new manufacturer member ID, and the customer may register for a new manufacturer member ID.

[0135] Furthermore, while embodiments 1 and 2 described above explain the case in which customers apply to the campaign via notification distribution from the SNS server 30, it is also possible to display a two-dimensional barcode created based on the LP URL in the store, and customers can scan the two-dimensional barcode to access the LP and apply. Alternatively, retailers and manufacturers may distribute the URL via email newsletters or other media operated by their company to encourage applications.

[0136] While embodiments 1 and 2 described above illustrate the linking of retail member IDs for supermarkets and other retailers with manufacturer member IDs, the present invention is not limited to these examples. For instance, it can be applied to various cases, such as linking the member IDs of restaurants with the manufacturer member IDs of manufacturers that supply prepared meals to restaurants, linking the member IDs of automobile dealers with the manufacturer member IDs of automobile manufacturers, or linking the member IDs of medical institutions with the manufacturer member IDs of manufacturers that supply medical-related products to medical institutions.

[0137] The configurations illustrated in each of the above embodiments are functional schematics and do not necessarily have to be physically represented as shown. In other words, the distributed and integrated forms of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions. [Industrial applicability]

[0138] The information processing system, information processing method, and information processing program according to the present invention are suitable for efficiently understanding customer attributes when selling products to customers. [Explanation of symbols]

[0139] 20 Management Server 21 Display section 22 Input section 23 Communication I / F Section 24 Memory section 24a Manufacturer Member ID Data 24b Linked ID Data 24c ID-POS data 24d POS data with manufacturer member ID 25 Control Unit 25a Retail Member ID Acquisition Section 25b Concatenated ID generation section 25c Linked ID Registration Section 25d SNS Login URL Generation Unit 25e Manufacturer Member ID Acquisition Department 25f Linked ID Verification Unit 25g Consolidated ID update section 25h ID-POS Data Acquisition Unit 25i ID replacement section 25j Manufacturer Member ID POS Data Transmission Unit 30 AP servers 31 Display section 32 Input section 33 Communication I / F Section 34 Storage section 35 Control Unit 35a Application Processing Section 35b Retail Member ID Transmission Section 35c Consolidated ID acquisition part 35d Manufacturer / Company ID Transmission Section 35e SNS Login URL Processing Unit 35e Application Completion Processing 40 Customer terminals 41 Operation display section 42 Communication I / F Section 44 Memory section 45 Control Unit 45a Browser 50 SNS servers 51 Display section 52 Input section 53 Communication I / F Section 54 Memory section 54a Manufacturer Member ID Data 55 Control Unit 55a Login Processing Unit 55b Authorization Processing Unit 55c Manufacturer Member ID Transmission Section 60 Manufacturer Servers 61 Display section 62 Input section 63 Communication I / F Section 64 Storage section 64a Manufacturer Member ID Data 64b POS data with manufacturer member ID 64c Member ID conversion data 65 Control Unit 65a POS data receiving unit with manufacturer member ID 70, 70-1, 70-p Store 80, 80-1, 80-q, 80-r POS terminals 81 Operation display section 82 Barcode readers 83 Communication I / F Section 85 Memory section 85a POS data 85b Retail Member ID Data 85c Product Data 86 Control Unit 86a Barcode reader 86b Payment Processing Unit 86c ID-POS Data Transmission Unit 90 Manufacturer Servers 101 CPU 102 ROM 103 RAM 104 Non-volatile memory 105 Bus

Claims

1. An information processing system having a management device that links and manages first identification information that uniquely identifies a customer and second identification information that uniquely identifies the customer, The aforementioned control device is A first acquisition unit that acquires the first identification information from a customer terminal owned by the customer, An issuing unit that issues linked identification information for linking the first identification information and the second identification information, A storage unit that stores first combined data including the first identification information and the linked identification information, A second acquisition unit that notifies a predetermined external device of the linked identification information and acquires the second identification information and the linked identification information from the external device, An update processing unit performs an update operation to update the first combined data stored in the storage unit to second combined data that includes the first identification information and the second identification information, based on the linked identification information acquired by the second acquisition unit. An information processing system characterized by having the following features.

2. The first identification information is identification information issued by a seller who sells the goods, The second identification information is identification information issued by the manufacturer of the product. The information processing system according to claim 1.

3. The update processing unit, The information processing system according to claim 1, characterized in that it performs an update process to identify a first combined data having the linked identification information from among one or more combined data stored in the storage unit, and to update the identified first combined data to a second combined data including the first combined data and the second identification information, and then store it in the storage unit.

4. The aforementioned control device is A third acquisition unit that acquires the first identification information and the POS data of the products purchased by the customer, Based on the first identification information acquired by the third acquisition unit, a notification means identifies the second identification information from one or more of the second combined data stored in the storage unit, and notifies the manufacturer's server device of the identified second identification information and the POS data. The information processing system according to claim 2, characterized by comprising:

5. The first acquisition unit is, The information processing system according to claim 1, characterized in that it displays application information on the input screen of the customer terminal in which the customer applies for the granting of a predetermined benefit, and the customer inputs the first identification information on the input screen and makes an application for the granting of the benefit in accordance with the application information, thereby obtaining the first identification information.

6. The external device is, The information processing system according to claim 1, characterized in that it is an SNS server of a business operator providing social networking services.

7. The external device is, The information processing system according to claim 2, characterized in that it is a server device of the manufacturer operated by the aforementioned manufacturer.

8. An information processing method in an information processing system having a management device that links and manages first identification information that uniquely identifies a customer and second identification information that uniquely identifies the customer, The management device performs a first acquisition step of acquiring the first identification information from a customer terminal owned by the customer, An issuance step of issuing linked identification information for linking the first identification information and the second identification information, A storage step of storing first combined data, which includes the first identification information and the linked identification information, in a predetermined storage unit, A second acquisition step involves notifying a predetermined external device of the linked identification information and obtaining the second identification information and the linked identification information from the external device. An update processing step, which performs an update process based on the linked identification information obtained in the second acquisition step, to update the first combined data stored in the storage unit to second combined data that includes the first identification information and the second identification information. An information processing method characterized by including

9. An information processing program executed by a management device that manages a link between a first identification information that uniquely identifies a customer and a second identification information that uniquely identifies the customer, The management device performs a first acquisition procedure to obtain the first identification information from a customer terminal owned by the customer, An issuance procedure for issuing linked identification information to link the first identification information and the second identification information, A storage procedure for storing first combined data, which includes the first identification information and the linked identification information, in a predetermined storage unit, A second acquisition procedure for notifying a predetermined external device of the linked identification information and obtaining the second identification information and the linked identification information from the external device, An update processing procedure that performs an update processing to update the first combined data stored in the storage unit to second combined data including the first identification information and the second identification information, based on the linked identification information obtained by the second acquisition procedure. An information processing program characterized by causing a computer to execute it.

Images