Product explanation support system, product explanation support method, and product explanation support program

Abstract

To provide a technique for providing an incentive for introduction while conveniently providing useful information about a product before or after purchase. [Solution] The product explanation support system comprises an access receiving unit that receives access using an access identifier included in a code previously associated with the product, a content changing unit that changes the content associated with the access identifier depending on whether the product has been purchased or not, and a content sending unit that displays the content on a customer's terminal, and is characterized in having a bonus granting unit that issues an introduction code including the access identifier to the terminal of an introducer, who is a customer who has purchased the product, and grants a bonus to the product, the introducer, or the person introduced when access using the introduction code is accepted.

Description

[Technical field]

[0001] The present invention relates to a product explanation support system, a product explanation support method, and a product explanation support program. [Background technology]

[0002] Patent Document 1 describes an agency management server that accepts agency management of a two-dimensional code and content via a terminal of a product provider that provides a product to which a two-dimensional code is attached, the two-dimensional code having access information embedded therein for accessing content including audio, and that includes a two-dimensional code designation receiving unit that receives, from the product provider's terminal, a designation of the two-dimensional code provided to the product provider; a management information receiving unit that receives, from the product provider's terminal, an input of management information for the product provider to confirm the contents of the designated two-dimensional code; a content receiving unit that receives, from the product provider's terminal, an upload of one or more contents corresponding to the designated two-dimensional code; a memory unit that stores the designated two-dimensional code, the management information, and the content in association with each other; a management information transmitting unit that transmits information confirming the association between the two-dimensional code, the management information, and the content to the product provider's terminal; and a distribution unit that distributes content corresponding to the read two-dimensional code to the end user's terminal in response to the end user's terminal reading the two-dimensional code. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-004463 A Summary of the Invention [Problem to be solved by the invention]

[0004] The above technology can provide a server that manages the correspondence between barcodes and content according to instructions from product providers. However, even if a potential customer picks up a product on display and becomes interested in it, the package explanation, POP explanation, and the uniformly provided content mentioned above may not motivate them to buy it, and even if they do purchase the product, they may not understand how to use it, resulting in a lack of satisfaction with the product, so this technology is not very effective.

[0005] An object of the present invention is to provide a technology that provides an incentive for referrals while conveniently providing useful information about a product before or after purchase. [Means for solving the problem]

[0006] The present application includes a plurality of means for solving at least part of the above problems, examples of which are as follows: A product explanation support system according to one aspect of the present invention is a product explanation support system executed by a computer system including a management server, and is characterized in that it comprises an access receiving unit that receives an access executed by a customer's user terminal using an access identifier included in a code previously associated with a product, a content changing unit that changes content data associated with the access identifier depending on whether the customer has purchased the product, a content sending unit that displays the changed content data so that it can be viewed on the customer's user terminal, and a bonus granting unit that issues an introduction code including an access identifier to an introducer who has purchased the product, the introducer, for introducing the product to an introduced customer who is another customer, and grants a predetermined bonus to the introduced product, the introducer, or the introduced customer upon receiving an access executed using the access identifier.

[0007] In addition, in the above-mentioned product explanation support system, the bonus granting unit may issue to the user terminal of the introducer a referral code that associates at least the introducer, the access identifier, and a specified bonus to be applied when the product is purchased, and upon receiving an access made by an introduced person different from the introducer using the access identifier included in the referral code, issue an image code for referral purchase that associates at least the introducer, the introduced person, the access identifier, and the specified bonus, and grant the specified bonus to either the product, the introducer, or the introduced person purchased using the referral purchase code.

[0008] In the above-mentioned product explanation support system, the benefit granting section may grant the introduced person an access identifier different from an access identifier granted to the introducer.

[0009] In the above-mentioned product explanation support system, the predetermined benefit may be a discount on the selling price of the product.

[0010] In the above-mentioned product explanation support system, the predetermined benefit may be a predetermined monetary benefit for either the introducer or the introduced person, or both, in relation to a next or subsequent purchase.

[0011] In addition, in the above-mentioned product explanation support system, the bonus granting unit may issue to the introduced person, when the introduced person purchases the product, the referral code that associates at least the introduced person, the product, and a specified bonus that is applied when the product is purchased.

[0012] In addition, in the above-mentioned product description support system, the content change unit may change the content data associated with the access identifier depending on whether or not the customer has introduced the product to the introduced person.

[0013] In addition, in the above-mentioned product description support system, the content change unit may change the content data associated with the access identifier depending on whether or not the customer has had experience of being introduced to a product other than the product in question.

[0014] In addition, in the above-mentioned product description support system, the content change unit may change the content data to be associated with the access identifier depending on whether or not the access is made using an access identifier included in the referral code.

[0015] Furthermore, a product explanation support method according to another aspect of the present invention is a product explanation support method executed by a computer system including a management server, and is characterized by carrying out an access acceptance procedure for accepting access made by a customer's user terminal using an access identifier included in a code previously associated with a product, a content modification procedure for modifying content data associated with the access identifier depending on whether the customer has purchased the product, a content transmission procedure for displaying the modified content data so that it can be viewed on the customer's user terminal, and a bonus granting procedure for issuing an introduction code including an access identifier to an introducer who has purchased the product, the introducer being the introducer, for introducing the product to another customer who is an introduced party, and, upon receiving access made using the access identifier, granting a predetermined bonus to either the introduced product, the introducer, or the introduced party.

[0016] Furthermore, a product explanation support program according to another aspect of the present invention is a product explanation support program that causes a management server to assist in product explanation, and is characterized in that it causes the management server to execute an access acceptance procedure for accepting access made by a customer's user terminal using an access identifier included in a code previously associated with a product, a content modification procedure for modifying content data associated with the access identifier depending on whether the customer has purchased the product, a content transmission procedure for displaying the modified content data so that it can be viewed on the customer's user terminal, and a bonus granting procedure for issuing an introduction code including an access identifier to an introducer who has purchased the product, the introducer, for introducing the product to another customer who is an introduced, and, upon receiving access made using the access identifier, granting a predetermined bonus to either the introduced product, the introducer, or the introduced person. Effect of the Invention

[0017] According to the present invention, it is possible to provide a technique for easily providing useful information about a product before or after purchase while giving an incentive for introduction.

[0018] Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0019] [Figure 1] 1 is a configuration diagram of a product explanation support system according to an embodiment. [Diagram 2] FIG. 1 is a diagram showing an example of a QR code (registered trademark). [Diagram 3] FIG. 2 illustrates an example of the configuration of a management server. [Figure 4] 11A to 11C are diagrams illustrating example data structures of product information, QR code information, and access history information. [Diagram 5] 3A to 3C are diagrams illustrating examples of data structures of content information, content provision condition information, and content association information. [Figure 6]FIG. 2 illustrates an example of a hardware configuration of a management server. [Figure 7] FIG. 11 is a diagram illustrating an example of a flow of a QR code issuing process. [Figure 8] FIG. 11 is a diagram illustrating an example of a screen transition when a QR code is issued. [Figure 9] FIG. 11 is a diagram illustrating an example of the flow of a content providing process. [Figure 10] FIG. 13 is a diagram showing an example of content selection (time zone). [Figure 11] FIG. 13 is a diagram showing an example of content selection (area). [Figure 12] FIG. 13 is a diagram showing an example of content selection (number of times the same URL is accessed). [Figure 13] FIG. 13 is a diagram illustrating an example of cookie information in the second embodiment (using cookies). [Figure 14] FIG. 11 illustrates an example of a flow of a content providing process according to the second embodiment; [Figure 15] FIG. 13 is a diagram illustrating an example of user account information in the third embodiment (application use). [Figure 16] FIG. 13 illustrates an example of the flow of a content providing process according to the third embodiment. [Figure 17] FIG. 13 illustrates an example of a flow of a process for collecting product purchase history according to the fourth embodiment; [Figure 18] FIG. 23 is a diagram illustrating an example of introduction information according to the fifth embodiment. [Figure 19] FIG. 13 is a diagram illustrating an example of a flow of a product introduction process. [Figure 20] FIG. 13 is a diagram illustrating an example of the flow of a product referral purchase process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] A product explanation support system 1 to which an embodiment according to one aspect of the present invention is applied will be described below with reference to the drawings. In the following embodiment, when necessary for convenience, the description will be divided into a number of sections or embodiments, but unless otherwise specified, they are not unrelated to each other, and one is a partial or complete modification, detail, supplementary explanation, etc. of the other.

[0021] In addition, in the following embodiments, when referring to the number of elements (including the number, numerical values, quantities, ranges, etc.), unless specifically stated or clearly limited to a specific number in principle, the number is not limited to that specific number and may be more than or less than a specific number.

[0022] Furthermore, in the following embodiments, the components (including element steps, etc.) are not necessarily essential unless specifically stated otherwise or considered to be clearly essential in principle.

[0023] Similarly, in the following embodiments, when referring to the shapes, positional relationships, etc. of components, etc., unless otherwise specified or considered to be obviously different in principle, it includes those that are substantially similar or similar to the shapes, etc. The same applies to the above numerical values ​​and ranges.

[0024] In addition, in all the drawings for explaining the embodiments, the same members are generally given the same reference numerals, and repeated explanations thereof will be omitted.

[0025] First Embodiment 1 is a configuration diagram of a product explanation support system 1 according to this embodiment. The product explanation support system 1 includes a management server 100, a seller terminal 200, and a user terminal 300. A sales clerk at a sales store uses the seller terminal 200, and a customer uses a user terminal 300 such as their own smartphone. Both the seller terminal 200 and the user terminal 300 read QR codes or images printed or attached to packages, pamphlets, flyers, promotional images, etc. of a product A400, etc., and access the domain (contents such as web pages) of the management server 100. In the present embodiment and the following embodiment, an example using a QR code is described. However, the present invention is not limited to this, and may be a code (or an object including a code) that allows the included information to be read by a terminal equipped with a reading device. For example, it may be a one-dimensional barcode, or a two-dimensional code such as a stack type or matrix type. It may also be an electronic tag that allows information to be read by wireless short-range communication such as NFC or RFID.

[0026] The seller terminal 200 and the user terminal 300 are information processing devices such as smartphones, personal computers, and tablet devices, but may also be wearable devices such as smart watches, headsets, gloves, and chokers.

[0027] The seller terminal 200 and the user terminal 300 communicate with the management server 100 using a predetermined data transmission protocol (Http (Hyper Text Transfer Protocol), Https (Hyper Text Transfer Protocol Secure), etc.) via a data communication network such as a carrier network or the Internet. The seller terminal 200 and the user terminal 300 send and receive Web content using URLs (Uniform Resource Locators), that is, perform so-called Web browsing. For example, the seller terminal 200 and the user terminal 300 request a company homepage or Web content from the management server 100 and display it on a display (not shown).

[0028] The management server 100 responds to various requests based on a data transmission protocol from the seller terminal 200 and the user terminal 300. For example, the management server 100 reads a QR code provided on a product A400 or the like and causes the seller terminal 200 and the user terminal 300 accessed by web browsing to play content data including a predetermined video or the like.

[0029] Fig. 2 is a diagram showing an example of a QR code (registered trademark). QR code 500 is a designed QR code (a QR code with decorations around it) called a "Look at this QR code." QR code 500 is a sticker that is attached to the blister pack (packaging) of product A400 or the like after it has been placed on the product. The aim of making it a "Look at this QR code" sticker is to attract the attention of customers who pick up product A400.

[0030] Alternatively, QR code 500 may be a "Look at this QR code" with a different design. For example, QR code 501 is an example of a "Look at this QR code" that uses a deformed animal character. Also, for example, QR code 502 is an example of a "Look at this QR code" that uses a deformed human character. Here, it is a "Look at this QR code", but it could also be a "fun code" or "full of fun", and it can be a QR code that is displayed with an attention-grabbing copy.

[0031] 3 is a diagram showing an example of the configuration of a management server. The management server 100 includes a processing unit 110, a storage unit 120, and a communication unit 150. The storage unit 120 includes product information 121, QR code information 122, access history information 123, content information 124, content provision condition information 125, content association information 126, user account information 127, and user-specific history information 128. The processing unit 110 includes a product information registration unit 111, a content registration unit 112, a QR code issuing unit 113, an access receiving unit 114, an access history management unit 115, a content change unit 116, a content transmission unit 117, and a user account management unit 118.

[0032] FIG. 4 is a diagram showing an example of data structure of product information, QR code information, and access history information. Product information 121 includes a product ID, a JAN code (including a business code, a product item code, etc.), a product attribute, and a purchaser attribute. Product attributes include product types such as home appliances, games, kitchenware, clothing, food, and household goods, product specifications such as product size, weight, size, and color, sales area, product replacement period, frequency of use, place of use, consumable / durable goods, sales form (special sale product, event product), etc. Purchaser attributes include a target demographic (male, female, age, etc.) of the product, etc. That is, the product information 121 can be said to be information in which a sales area is associated with each product. Also, the product information 121 can be said to be information in which a purchase target attribute including at least one of gender, age group, and occupation is associated with each product.

[0033] The QR code information 122 includes a QR code ID, a QR code image, an access URL, and an attached product ID. The access URL includes a content URL (a relative directory from the domain and root path) and parameters. The parameters include, for example, the JAN code of the product and other additional data.

[0034] In this embodiment, the access URL is configured in such a way that it is easy to analyze and match with various search engines. It is recommended to use a URL like "https: / / xxx.co.jp / laben-ECS / g-code / C6-00313 / jan=4988760012036 / col=green / no=001 / peeler.html". "xxx.co.jp / laben-ECS" is the hostname + domain name portion, "g-code" is a delimiter indicating the product code, "C6-00313 / jan=4988760012036" is the product classification code and JAN code, "col=green" is the color classification, and "no=001" is a unique code for special sales, events, sales regions, etc. Although not shown here, codes indicating size such as siz=xl can be added. Also, product classification codes can be unified by using the design classification code established in the examination criteria of the Design Law.

[0035] The attached product ID includes the product ID of the product to which the QR code is attached. That is, the QR code information 122 stores information in which a URL and a plurality of content data are associated with each product.

[0036] The access history information 123 includes a QR code ID, an access URL, and an access history by session. The access history by session includes, for each HTTP session, the access date and time, the displayed content ID, the duration of stay in the content (display time), and, for videos, the display time ratio to the total video time, the access area, etc. The access area is information estimated from the IP address, etc., of the area accessed by the seller terminal 200 and the user terminal 300 after reading the QR code. In addition, the accessed area includes not only base station units, but also prefecture units, for example.

[0037] 5 is a diagram showing an example of the data structure of content information, content provision condition information, and content association information. Content information 124 includes association between a content ID and content data. The content data is the content data itself (e.g., a web page, an image, a video, etc.) or a path (such as a web site URI) by which the content data can be acquired.

[0038] The content provision condition information 125 includes a content ID, a provision condition, and an aim. The provision conditions include a combination of various provision conditions and a content ID to be provided according to the combination. There are various possible combinations of the various provision conditions, but as an example, even if the product ID is the same, if there is a product for region X (local model) and a product for region Y, it is necessary to provide content appropriate for each region, so the information includes information that associates each content data with the provision region in which the content data is provided.

[0039] In addition, it is possible that the information a customer wants to know before and after purchasing a product may differ. In that case, it is possible that the customer will access the product from the store before purchasing and from outside the store such as at home after purchasing. Therefore, it is possible to associate content data with each of the access areas as a provision condition.

[0040] It is also possible that the information customers want to know differs between the first access and the second or subsequent access, or between accesses after a certain period of time. In such cases, content data can be associated with each of the conditions for provision, such as the number of accesses or the period of time since the first access. In addition, content data can be associated with various information such as JAN code, product attributes, purchaser attributes, and the time period of access, as well as other conditions for provision.

[0041] For example, the provision conditions may correspond to a time period when the content data is provided, or the provision area of ​​the content data may correspond to a sales area of ​​the product, or the provision conditions may correspond to purchaser attributes including at least one of gender, age group, and occupation.

[0042] Furthermore, content data whose number of times of provision included in the access history information 123 that records the history of provision of each content data satisfies a predetermined number may be selectively associated.

[0043] Preferably, the more times a product is provided to a given customer, the more detailed the content data containing the product description is associated with the product. Alternatively, it is preferable to specify the average viewing time (average past display time) of videos related to past accesses on the customer's user terminal, and set the content data of videos having a playback time corresponding to the average viewing time as the provision condition. Alternatively, the viewing time ratio of videos related to past accesses on the customer's user terminal (ratio of display time to the total time of past videos) may be specified, and the content data of videos having a playback time corresponding to the viewing time ratio may be set as the provision condition.

[0044] The "purpose" field stores a sentence that explains the purpose of setting the provision conditions for the content. By referring to the "purpose," the seller can confirm the intention of providing the content to customers who meet the provision conditions.

[0045] The content association information 126 includes a QR code ID, an access URL, an attached product ID, a session ID, and a content ID. The session ID is information for identifying each HTTP session of the seller terminal 200 and the user terminal 300 simultaneously connected to the management server 100. In order to ensure continuous processing transition in the session stateless HTTP protocol, the management server 100 shares a session ID to pseudo-secure a state. The management server 100 then controls the content provided for each seller terminal 200 and user terminal 300 by appropriately rewriting the content ID to be displayed on each seller terminal 200 and user terminal 300 in association with the session ID. Note that the number of content IDs associated with a QR code ID is not limited to one, and multiple content IDs may be associated with each other along with an order so that video content is played in sequence.

[0046] The product information registration unit 111 accepts input of information to be stored in the product information 121, and registers the information in the product information 121. The content registration unit 112 accepts content data (web pages and videos), and registers the information in the content information 124 and the content provision condition information 125. The QR code issuing unit 113 issues a QR code including an access URL and a product ID.

[0047] The access receiving unit 114 receives an access made using a URL included in a QR code. Specifically, the access receiving unit 114 receives an access (HTTP request or HTTPs request) from a user terminal 300 or seller terminal 200 that has picked up a product A400 in a store, and the access is made to a URL included in a QR code attached to the product in advance.

[0048] The access history management unit 115 records the history of provision for each piece of content data. Specifically, the access history management unit 115 stores the access history in the access history information 123.

[0049] The content change unit 116 changes and manages the content data associated with the URL included in the QR code for each session by selecting from a plurality of pre-stored content data according to a predetermined provision condition. More specifically, the content change unit 116 specifies a product associated with the URL used for URL access, and selects content data that satisfies the predetermined provision condition from a plurality of content data associated with the specified product, thereby changing the content data associated with the URL. If there are a plurality of contents that satisfy the provision condition, one content is selected according to a predetermined priority order, and is set as the content data to be associated with the URL. The priority order may be, for example, the order of the most matching conditions, the order of the most recent creation date and time of the content data, or the order of the shortest playback time of the content data.

[0050] More specifically, for example, the content change unit 116 identifies the current time, and uses the content provision condition information 125 to select, from among a plurality of content data, content data whose provision time period corresponds to the current time.

[0051] Furthermore, the content change unit 116 uses information in the QR code information 122 to identify a product associated with the URL used for access, uses product information 121 to identify a sales region of the identified product, and selects, from among the multiple content data, content data whose identified sales region corresponds to a provision region. Alternatively, the content change unit 116 uses an IP address included in the network connection information of the access from the user terminal 300 to identify the access region of the user terminal 300, and selects, from among the multiple content data, content data whose access region corresponds to a provision region.

[0052] In addition, the content change unit 116 uses the information in the QR code information 122 to identify a product associated with the URL used for access, identifies the purchaser target attributes of the identified product, and selects, from among multiple content data, content data whose purchaser target attributes satisfy the provided target attributes.

[0053] Furthermore, the content modification unit 116 may select content data that has been provided a predetermined number of times from among a plurality of content data. That is, the content modification unit 116 may select content that has been reproduced frequently.

[0054] Furthermore, if the content change unit 116 is able to acquire information as to whether or not a product has been purchased, such as when the QR code information 122 contains purchase history information (product ID, purchase store, purchase date and time, number of items purchased) indicating that the product has been purchased, the content change unit 116 can select different content data depending on whether the product has been purchased or not. For example, before a product is purchased, content data for promoting the sale of the product, with "before purchase" specified as the provision condition, is selected. On the other hand, after a product has been purchased, content data explaining a specific method of using the product, with "after purchase" specified as the provision condition is selected.

[0055] As described above, the content modification unit 116 may select content that satisfies all of the provision conditions including time, sales region, purchase target attribute, number of times of provision, etc. Alternatively, the content modification unit 116 may select content that satisfies one or more of the provision conditions. When there are multiple selected contents, one content is selected according to a predetermined priority order as described above, and is set as content data to be associated with the URL.

[0056] In addition, the content change unit 116 may select content data of related products in the same category as the product to which the QR code is attached during a predetermined time period in order to display the content that is currently most desired to be introduced.

[0057] The content transmission unit 117 transmits the content data changed by the content change unit 116 to the user terminal 300, and displays the content data on the user terminal 300 so that the content data can be viewed.

[0058] The user account management unit 118 assigns to each user (customer) a user ID that allows the user to be distinguished from other users, and generates user account information 127 and user-specific history information 128.

[0059] The communication unit 150 communicates with the seller terminal 200 and the user terminal 300 via a data communication network and the Internet or the like.

[0060] 6 is a diagram showing an example of the hardware configuration of a management server. The management server 100 has a hardware configuration realized by the housing of a so-called server device, a workstation, a personal computer, a smartphone, or a tablet terminal. The management server 100 has a processor 101, a memory 102, a storage device 103, a communication device 104, and a bus connecting each device.

[0061] The processor 101 is an arithmetic device such as a central processing unit (CPU) or a graphics processing unit (GPU).

[0062] The memory 102 is a memory device such as a RAM (Random Access Memory).

[0063] The storage device 103 is a non-volatile storage device capable of storing digital information, such as a so-called hard disk drive, a solid state drive (SSD), or a flash memory.

[0064] The communication device 104 is a network interface card (NIC) or the like that communicates with other devices via the data communication network 50 .

[0065] The product information registration unit 111, content registration unit 112, QR code issuing unit 113, access receiving unit 114, access history management unit 115, content change unit 116, content transmission unit 117, and user account management unit 118 of the management server 100 described above are realized by a program that causes the processor 101 to perform processing. This program is stored in the memory 102, the storage device 103, or a ROM device (not shown), and is loaded onto the memory 102 for execution and executed by the processor 101.

[0066] Moreover, the storage unit 120 of the management server 100 is realized by the memory 102 and the storage device 103. Moreover, the communication unit 150 is realized by the communication device 104. An example of the hardware configuration of the management server 100 has been described above.

[0067] The configuration of the management server 100 can be further divided into components according to the processing content, or can be divided so that one component performs further processing.

[0068] Furthermore, each processing unit (product information registration unit 111, content registration unit 112, QR code issuing unit 113, access receiving unit 114, access history management unit 115, content modification unit 116, content transmission unit 117, user account management unit 118) may be constructed with dedicated hardware (ASIC, GPU, etc.) that realizes each function. Furthermore, the processing of each processing unit may be executed by a single piece of hardware, or may be executed by multiple pieces of hardware. Furthermore, the seller terminal 200 and the user terminal 300 also have basically the same hardware configuration as the management server 100.

[0069] Next, the operation of the product explanation support system 1 in this embodiment will be described.

[0070] 7 is a diagram showing an example of the flow of the QR code issuing process. The QR code issuing process goes into a standby state when the management server 100 starts operation, and starts when a login request is made from the seller terminal 200.

[0071] First, the seller terminal 200 logs in to the management server 100 (step S001). The login process may involve general authentication (password authentication, biometric authentication, passcode authentication, image authentication, etc.). Once the login is confirmed, the product information registration unit 111 starts the registration process (step S002). Specifically, the product information registration unit 111 causes the seller terminal 200 to display a seller input screen 600, which will be described later.

[0072] Then, when the product information is received from the seller terminal 200, the product information registration unit 111 registers the product information in the product information 121 (steps S003 and S007). Then, when the content information is received from the seller terminal 200, the content registration unit 112 registers the content information in the content information 124 (steps S004 and S007). Then, when the content association information is received from the seller terminal 200, the content registration unit 112 registers the content association information in the content association information 126 (steps S005 and S007). Then, when the condition information for providing the content is received from the seller terminal 200, the content registration unit 112 registers it in the content providing condition information 125 (steps S006 and S007).

[0073] Then, when the seller terminal 200 transmits a request to issue a QR code (step S008), the QR code issuing unit 113 issues a QR code using the information received in steps S003 to S006 (step S009). Specifically, the QR code issuing unit 113 generates a QR code image from a character string including the access URL and the product ID using an existing encoding algorithm, and displays the QR code image on the seller terminal 200. The request to issue a QR code may be made at any time required by the user of the seller terminal 200, and may be made multiple times.

[0074] Then, the seller terminal 200 prints the QR code on a sticker or the like and attaches it to the product (step S010).

[0075] The processing of each seller terminal 200 may be performed not only by the seller but also by the manufacturer, and the "Look at this QR code" may be attached to the product (e.g., the package or the product itself) by similar processing during product manufacturing or before shipping. Furthermore, the "Look at this QR code" may be sent as an image to customers who have already registered as members, for example, in an e-mail newsletter.

[0076] The above is the content of the QR code issuing process. According to the QR code issuing process, it is possible to easily create and print a "Check it out QR code" that is a QR code corresponding to product information and can dynamically display various content data according to the provision conditions.

[0077] 8 is a diagram showing an example of screen transitions when issuing a QR code. On the seller terminal 200, a seller input screen 600 transmitted from the management server 100 in step S002 of the QR code issuing process is displayed. The seller input screen 600 includes fields for receiving input of product information, content information, condition information for providing the content, and content association information, an upload button 601 for uploading content information, and a QR code issue button 602 for issuing a QR code. When the upload button 601 receives input, it uploads and transmits the input content information to the management server 100. When the QR code issue button 602 receives input, it transmits the input product information, condition information for providing the content, and content association information to the management server 100, and transitions the screen to a QR code issuance result screen 650.

[0078] The QR code issuance result screen 650 displays the QR code ID, QR code image, access URL, and product ID. The QR code issuance result screen 650 also displays a download button 651 that accepts an operation to download the QR code image for printing. When the download button 651 accepts an input, it downloads the "Check it out QR code" and outputs the print data to a printer. The QR code issuing unit 113 may display design options 652 including the "Check it out QR code", and transmit the "Check it out QR code" of the selected design to the seller terminal 200.

[0079] 9 is a diagram showing an example of the flow of the content provision process. When the management server 100 starts operation, the content provision process goes into a standby state, and is started when the user terminal 300 accesses the content provision process.

[0080] First, the user terminal 300 reads the QR code 500 of the "Check it out QR code", identifies the URL included therein, and accesses the identified URL (step S101). When the access acceptance unit 114 accepts the access, it refers to the access history information 123 of the URL to be accessed (step S102). Then, the content change unit 116 identifies a content ID to be associated with the target URL based on the access history information 123 and the content provision condition information 125, and registers it in the content association information 126 related to the session (step S103). Then, the content transmission unit 117 starts transmitting the content data of the registered content ID to the user terminal 300 (step S104). Note that the content transmission unit 117 "starts" transmitting the content data because the content may be a streaming video. If the content data is not a streaming video, the content transmission unit 117 transmits the content data at once.

[0081] Then, the user terminal 300 displays the content data (step S105) until the display is terminated (step S106). The access history management unit 115 stores the access history information, including the displayed content data ID, in the access history information 123 (step S107).

[0082] When the streaming reproduction of the content data is completed, the content transmitting unit 117 may continue to reproduce other content data as long as the viewing continues.

[0083] The above is the content of the content provision process. The content provision process allows customers (users) to view content data according to the content provision conditions and according to their access history. Therefore, it can be said that customers can easily obtain useful information about products before or after purchase.

[0084] Fig. 10 is a diagram showing an example of content selection (time period). In the example of Fig. 10, the content data provided by the management server 100 changes between the time period before 13:00 and the time period after 13:00. For example, if the "Look at this QR code" is for the product "Cabbage Peela," when the management server 100 is accessed from the user terminal 300 at 10:20, the content data includes a video introducing how to use Cabbage Peela, information on a limited-time sale currently being held, or a video introducing a lunch recipe. However, when the management server 100 is accessed from the user terminal 300 at 15:00, the content data includes a video introducing a dinner recipe using Cabbage Peela.

[0085] FIG. 11 is a diagram showing an example of content selection (region). In the example of FIG. 11, the content data provided by the management server 100 changes depending on the region where the product is sold. For example, if the "Check it out QR code" is for the product "Cabbage Peela," and if the QR code contains a JAN code for region X (e.g., Hokkaido region) in its parameters, when the management server 100 is accessed from the user terminal 300, information on a limited-time sale being held only in region X is included in the content data. However, if the QR code contains a JAN code for region Y (e.g., Okinawa region) in its parameters, when the management server 100 is accessed from the user terminal 300, information on a limited-time sale being held only in region Y is included in the content data.

[0086] Fig. 12 is a diagram showing an example of content selection (number of times the same URL is accessed). In the example of Fig. 12, the content data provided by the management server 100 changes depending on the number of times the same URL is accessed. Here, the number of times the same URL is accessed means the number of times the same URL is accessed for each user terminal 300. Typically, the number of times the same user terminal 300 reads the same "Check it out QR code" and accesses the management server 100 is the number of times the same URL is accessed.

[0087] For example, if the "Look at this QR code" is for a product "cabbage peeler," it is conceivable that the "Look at this QR code" is peeled off the cabbage peeler and reattached to furniture or the like (e.g., a refrigerator) and accessed many times. Depending on the number of accesses, if it is the first to third access, when the management server 100 is accessed from the user terminal 300, information of display type 1 (e.g., tips on how to make simple shredded cabbage) is included in the content data. If it is the fourth access, when the management server 100 is accessed from the user terminal 300, information of display type 2 (e.g., tips on how to shred well) is included in the content data. If it is the fifth access, when the management server 100 is accessed from the user terminal 300, information of display type 3 (e.g., how to cut vegetables other than cabbage) is included in the content data. If it is the sixth access or later, when the management server 100 is accessed from the user terminal 300, information of display type 4 (e.g., simple recipes using the cabbage peeler) is included in the content data.

[0088] More specifically, in the case of content data for display type 1, for tips on how to make simple shredded cabbage, the main focus is on video, providing simple usage (ready-to-use usage) in a 1-2 minute video with text, diagrams, arrows, onomatopoeia, etc. This content aims to first guide the user to use the product correctly, to understand that it is an easy-to-use and convenient product, and if possible, to share its merits with others (implicitly encouraging users to post on social media), leading to the spread of information and sales. At the end of the video, a standard phrase is included, "Next time, we will provide new information. Please watch again!" The video explanation includes specific product operation procedures such as (1) how to select a cabbage, choose a heavy one, (2) cut it in half toward the core, (3) hold the core with your thumbs, (4) tilt the blade at a 45° angle, and (5) pull it toward you in long strokes, as well as a concise, organized explanation as a summary.

[0089] In addition, in the case of content data for display type 2, in the case of tips (know-how) on how to peel well, the content will be mainly video, and when users understand how to use it, the content will encourage them to use it more proactively and well, and provide information that will make them more of a fan. Again, at the end of the video, the standard phrase "Next, we will provide new information. Please watch again!" will be included. The explanatory content of the video includes (1) specific operating procedures for how to peel a cabbage, such as when cutting thinly, pulling with a stroking motion without applying pressure to the index finger, and when cutting short, pulling short, as if gouging, and (2) specific operating procedures for how to peel a cabbage so that the leaves do not come apart, such as pulling with a stroking motion around the edges and tearing off any excess leaves, as well as a concise, organized explanation as a summary.

[0090] In addition, in the content data for display type 3, when cutting methods other than cabbage are used, the content will provide information that will encourage more general use and make the user more of a fan when accessing the video after the user is satisfied with shredding the cabbage. Again, at the end of the video, the standard phrase "Next, we will provide new information. Watch again!" is included. The video's explanation includes (1) specific operating procedures for shaving radish thinly, such as shaving it long, shaving it diagonally, and shaving while rotating, (2) specific operating procedures for shaving cucumber, such as shaving it long, shaving it diagonally, and shaving it vertically, and (3) specific operating procedures for shaving other ingredients, such as carrots, celery, etc., as well as a concise, organized explanation as a summary.

[0091] In addition, in the case of content data for display type 4, in the case of a simple recipe using a cabbage peeler, the content provides information that encourages more practical and effective use of the product, on the assumption that the user is already familiar with how to use it, and will make the user a bigger fan. Again, at the end of the video, the standard phrase "Next time, we will provide new information. Please watch again!" is included. The explanatory content of the video includes (1) a recipe for shredding cabbage, (2) a recipe for thinly slicing daikon radish, and (3) a recipe for vinegared dishes, etc., along with a concise, organized summary.

[0092] The above is the product explanation support system 1. As in the above embodiment, the product explanation support system 1 can easily provide useful information regarding various items of information related to a product before or after purchase.

[0093] The content modification unit 116 may select different content depending on the customer's user level. Specifically, the storage unit of the management server 100 stores information in which a level indicating proficiency is associated with each piece of content data. The content modification unit 116 manages the user level indicating the customer's proficiency with a product identified by a QR code (URL). The content modification unit 116 then raises the user level each time the number of times the URL used for access on the customer's user terminal 300 is accessed increases. On the other hand, when the content modification unit 116 receives a request from the customer to display content data at a level lower than the current user level, it lowers the user level of the customer to the level associated with the content data requested to be displayed. The content modification unit 116 then selects content data according to the user level from among the multiple content data.

[0094] The present invention is not limited to the above embodiment. The above embodiment can be modified in various ways within the scope of the technical concept of the present invention. Specifically, when selecting content data in step S103 of the above content provision process, content data may be selected using POS (Point Of Sales) data held by the store. For example, more suitable content data may be selected according to the sales volume for each sales area and the attributes of the purchaser using the POS data. The POS data includes sales information such as JAN code, sales date, sales area, store, sales volume, purchaser attributes, and sales price.

[0095] The content change unit 116 may also use POS data to select content data in descending order of the purchase rate of the product within a predetermined time after viewing the content. In this way, content data that can achieve a higher sales promotion effect can be provided.

[0096] The content change unit 116 may also specify the current time and specify the product and its sales region associated with the URL used for access.Then, the content change unit 116 may select content data in descending order of the purchase rate of the product within a predetermined time after viewing the content, using POS data, from among content data in which the specified product sales region corresponds to the product provision region and the current time corresponds to the content provision time zone.In this way, content data that can achieve a higher sales promotion effect can be provided.

[0097] Second Embodiment Alternatively, cookie information may be stored in the user terminal 300, and content data may be selected using the cookie information. This will be described below as a second embodiment. Note that the second embodiment is basically the same as the first embodiment, so differences will be mainly described.

[0098] Fig. 13 is a diagram showing an example of cookie information in the second embodiment (using cookies). Cookie information 160 stores a user ID, an access history, and a product purchase history in association with each other. The access history includes the access date and time, the displayed content ID, the stay time, the cumulative number of accesses, etc. for each URL accessed by the "Look at this QR code". The product purchase history includes the product ID, purchase date and time, the purchase store, the number of purchases, etc. of products purchased in the past. The product purchase history will be described later in the fourth embodiment.

[0099] 14 is a diagram showing an example of the flow of content provision processing in the second embodiment. First, the user terminal 300 reads the QR code 500 of the "Check it out QR code", identifies the URL contained therein, and accesses the identified URL (step S201). At that time, the cookie information 160 stored in the storage unit of the user terminal 300 is transmitted. Then, instead of step S103, the content change unit 116 identifies a content ID to be associated with the target URL based on the cookie information 160, the access history information 123, and the content provision condition information 125, and performs processing to register the content ID in the content association information 126 related to the session (step S203).

[0100] Specifically, the content change unit 116 acquires the same URL access count, which is the number of times the URL used for access in the user terminal 300 is accessed, from the cookie information 160, selects from among the multiple content data the content data whose same URL access count satisfies the number of times provided, and registers the selected content data in the content association information 126 related to the session. At this time, content data that provides a more detailed explanation may be selected according to the same URL access count. For example, content data that provides an overview of the purpose, usage scenario, effects, etc. may be selected for the first access, and content data that provides a detailed explanation of the functions may be selected for the second or subsequent access.

[0101] Alternatively, the content change unit 116 may acquire the most recent access date and time or the first access date and time to the URL used for access in the user terminal 300 from the cookie information 160, and select content data based on the time that has elapsed since the most recent access date and time or the first access date and time. In this way, appropriate content data can be provided to a user who frequently accesses the content or a user who has not accessed the content for a predetermined period of time (for example, one month) since the first access.

[0102] Then, when the display of the content data ends on the user terminal 300 (step S106), the access history management unit 115 updates the access history, regenerates the cookie information 160, and transmits it to the user terminal 300 (step S207). The user terminal 300 stores the received cookie information in a predetermined storage unit (step S208).

[0103] When the streaming reproduction of the content data is completed, the content transmitting unit 117 may continue to reproduce other content data as long as the viewing continues.

[0104] The above is the processing content of the content provision processing of the second embodiment. According to the content provision processing of the second embodiment, a customer (user) can view content data according to the content provision conditions and based on the access history of the customer's own user terminal 300, that is, content data that is more likely to be desired by the customer. Therefore, it can be said that more useful information about a product before or after purchase can be easily obtained.

[0105] <Third embodiment> Alternatively, application software (hereinafter sometimes referred to as "app") compatible with the product explanation support system 1 may be stored in an executable manner in the user terminal 300, and the management server 100 may store user account information and access history for each customer, and upon access, content data may be selected using the account information. This will be described below as the third embodiment. Note that the third embodiment is basically the same as the first embodiment, so differences will be mainly described.

[0106] FIG. 15 is a diagram showing an example of user account information in the third embodiment (application use). In the user account information 127, a user ID and user information are stored in association with each other. The user information includes the name, sex, age, address, etc. of the user (customer). The name, sex, age, address, etc. of the user (customer) are input by the user (customer) himself / herself on the application of the user terminal 300 and are stored. In addition, when the name, sex, age, address, etc. are input on the application of the user terminal 300, the user account management unit 118 assigns a user ID to the user (customer) that can be distinguished from other users, and generates the user account information 127 and the user-specific history information 128.

[0107] The user history information 128 stores a user ID, an access history, and a product purchase history in association with each other. The access history includes, for each URL accessed by the "Look at this QR code", the access date and time, the displayed content ID, the stay time, the cumulative number of accesses, etc. The product purchase history includes the product ID, purchase date and time, the purchase store, the purchase quantity, etc. of products purchased in the past. The product purchase history will be described later in the fourth embodiment.

[0108] 16 is a diagram showing an example of a flow of a content provision process according to the third embodiment. First, the application of the user terminal 300 reads the QR code 500 of the "Check it out QR code", identifies the URL contained therein, and accesses the identified URL (step S301). At that time, the user ID set in the application is also transmitted.

[0109] Then, instead of step S103, the content change unit 116 identifies a content ID to be associated with the target URL based on the user account information 127, the user-specific history information 128, the access history information 123, and the content provision condition information 125, and performs a process of registering the content ID in the content association information 126 related to the session (step S303).

[0110] Specifically, the content change unit 116 acquires the same URL access count, which is the number of times the URL used for access in the user terminal 300 has been accessed, from the user history information 128, selects from among the multiple content data the content data whose same URL access count satisfies the number of times provided, and registers the selected content data in the content association information 126 related to the session. At this time, content data that provides a more detailed explanation may be selected according to the number of same URL accesses. For example, content data that provides an overview of the purpose, usage scenario, effects, etc. may be selected for the first access, and content data that provides a detailed explanation of the functions may be selected for the second or subsequent access.

[0111] Alternatively, the content change unit 116 may acquire the most recent access date and time or the first access date and time to the URL used for access in the user terminal 300 from the user history information 128, and select content data based on the time that has elapsed since the most recent access date and time or the first access date and time. In this way, appropriate content data can be provided to users who frequently access content or users who have been accessing content for a predetermined period of time (for example, one month) since their first access.

[0112] Alternatively, the content change unit 116 may acquire at least one of the gender, age group, and occupation from the user information of the user account information 127, and select content data that satisfies the attributes of the target user. In this way, appropriate content data can be provided according to the user attributes.

[0113] Alternatively, the content change unit 116 may acquire an average viewing time of videos related to past accesses in the user terminal 300, and select content data of videos having a playback time corresponding to the average viewing time. In this way, appropriate content data can be provided according to the user's tendency to watch videos (e.g., how long a viewing time is required to watch to the end). That is, content data including videos with long playback times can be provided to users who tend to watch long videos, and content data including videos with short playback times can be provided to users who tend not to watch long videos.

[0114] Then, when the streaming reproduction of the content data is completed, the content transmitting unit 117 may continue to reproduce other content data as long as the viewing continues.

[0115] After the process of step S107, the access history management unit 115 stores the information of the access history, including the displayed content data ID, in the user-specific history information 128 (step S308).

[0116] The above is the processing content of the content provision processing of the third embodiment. According to the content provision processing of the third embodiment, a customer (user) can view content data according to the content provision conditions and based on the access history of the customer's own user terminal 300, that is, content data that the customer is more likely to want. Therefore, it can be said that it is possible to easily obtain more useful information about a product before or after purchase.

[0117] <Fourth embodiment> Next, a fourth embodiment will be described below. Note that the fourth embodiment is basically similar to the first embodiment, so the following description will focus on the differences.

[0118] The fourth embodiment is characterized in that the content provided to the user is different before and after purchasing a product. To this end, the management server 100 stores the product purchase history for each user in the user-specific history information 128.

[0119] FIG. 17 shows an example of a process flow for collecting product purchase history.

[0120] First, an example will be shown in which a dedicated application for carrying out purchase processing is installed on the user terminal 300. The user terminal 300 reads the "Check it out QR code" attached to the product to be purchased (step S501). After that, when a purchase processing request is received from the user, the user terminal 300 accesses the URL included in the QR code and requests the management server to perform processing to update the purchase history information (step S502). At this time, the user terminal 300 also transmits the user ID to the management server 100.

[0121] Here, since it is assumed that the store may not have a seller terminal 200, the user terminal 300 displays a screen that accepts input as to whether or not a seller terminal 200 is present in the store. If a seller terminal 200 is present in the store, the customer inputs "yes," and if not, inputs "no." If "no" is input for a seller terminal 200 ("no" in step S503), the user terminal 300 displays a purchase confirmation (step S511) and ends the process as a provisional purchase process.

[0122] Meanwhile, when the user account management unit 118 of the management server 100 receives a request from the user terminal 300 to update the purchase history information, it acquires the customer's user ID and identifies the product ID based on the URL that was accessed. The QR code issuing unit 113 of the management server 100 then generates a purchasing QR code including the product ID, user ID, and the URL to be accessed, and sends it to the user terminal 300 (step S504). The URL to be accessed is the URL used by the seller terminal 200 to access the management server, and includes the host name and domain name of the management server 100.

[0123] If the seller terminal 200 has input "Yes" (step S503: "Yes") and the user terminal 300 receives a purchase QR code from the management server 100, the user terminal 300 displays the received purchase QR code on the display (step S505). The seller terminal 200 (the store's cash register terminal) reads the purchase QR code displayed on the user terminal 300 (step S506). At this time, it is possible to add processing such as points or other rewards for the purchased item or a discount. When the seller terminal 200 completes the payment process, it accesses the URL included in the read QR code and sends purchased information (including the user ID, product ID, purchase store, purchase date and time, number of items purchased, etc.) indicating that the purchase has been completed to the management server 100 (step S507).

[0124] In response, the user account management unit 118 of the management server 100 obtains the user ID, product ID, purchase store, purchase date and time, number of items purchased, etc. from the purchased information, and stores the product ID, purchase store, purchase date and time, number of items purchased, etc. in the product purchase history of the corresponding user ID in the user history information 128 (step S509).

[0125] When the user account management unit 118 of the management server 100 updates the product purchase history, it transmits information indicating that the purchase record has been made to the seller terminal 200 and the user terminal 300 (step S510). In response to this, the seller terminal 200 displays information indicating that the purchase history has been updated and the purchase has been completed (displays "purchase confirmation") (step S511). The user terminal 300 also displays information indicating that the purchase history has been updated and the purchase has been completed (displays "purchase confirmation") (step S512). For example, when purchasing a product on the Internet, such as an EC site, a purchase QR code or URL is transmitted to the EC site at the time of purchase, and the EC site receives the purchase QR code or URL and transmits the purchased information to the management server 100, so that the management server 100 can perform purchase confirmation processing (steps S506 to S510). In this way, by introducing the function of the seller terminal (such as a cash register) 200 into the EC site, the same processing can be performed even on an EC site.

[0126] In addition, when a product is returned, the seller terminal 200 requests the management server 100 to cancel the purchase history of the corresponding product. In response, the user account management unit 118 of the management server 100 deletes the purchase history of the corresponding product.

[0127] The process of collecting purchase history information has been described above.

[0128] Through the above process, the content change unit 116 of the management server 100 can determine before and after the purchase (whether or not the purchase has been made) of a specific product by the user (customer) of a specific user ID by referring to the purchase history information of that user ID. Therefore, when updating the content association information 126, the content change unit 116 can select different content data depending on whether the product was purchased before or after it was purchased. For example, before the product is purchased, content data for promoting the sale of the product, with "before purchase" specified as the provision condition, is selected. On the other hand, after the product is purchased, content data explaining the specific method of using the product, with "after purchase" specified as the provision condition is selected.

[0129] When the purchase history is updated in step S508, the QR code issuing unit 113 of the management server 100 may issue a new QR code indicating that the product has been purchased, and transmit it to the user terminal 300 or the seller terminal 200. The information contained in the new QR code is the same as the information contained in the above-mentioned "Check it out QR code," but it may also include information indicating that the product has been purchased. Alternatively, when the QR code issuing unit 113 issues a new QR code, it may associate the QR code information 122 with purchase history information indicating that the product has been purchased (user ID of the purchasing user, product ID, purchase store, purchase date and time, and number of items purchased).

[0130] When the seller terminal 200 receives a new QR code for a purchased item, it can print it on a card with a magnet and hand it to the customer. Of course, the customer can also print it out. The customer can store it by sticking it on the refrigerator, and when they want to view the content, they can easily view the useful content by reading the QR code.

[0131] <Modification of the fourth embodiment> In the above fourth embodiment, the user terminal 300 transmits a request for pre-purchase processing to the management server 100 by using an installed dedicated app. However, the present invention is not limited to this, and a pre-purchase processing of a product may be performed by using cookie information in a user terminal 300 in which a dedicated app is not installed.

[0132] Specifically, the user terminal 300 reads the "Check it out QR code" attached to the product to be purchased (step S501), identifies the URL included in the QR code, and uses the identified URL to access the management server 100. At that time, the user terminal 300 transmits cookie information including the user ID and the like to the management server 100.

[0133] The management server 100 transmits content data to the user terminal 300 through the processes of steps S102, S203, and S104 shown in Fig. 14 above. The content data includes content that is displayed so as to be able to accept a pre-purchase processing request, for example by displaying a "pre-purchase processing button" on a Web page.

[0134] When the user terminal 300 receives a pre-purchase processing request from a user who has decided to purchase a product, the user terminal 300 transmits the request to the management server 100 .

[0135] Here, since it is assumed that the store does not have a seller terminal 200, the management server 100 displays a screen on the browser of the user terminal 300, for example, for accepting input of the presence or absence of a seller terminal 200 in the store. If a seller terminal 200 is present in the store, the user, who is a customer, inputs "yes" and if not, inputs "no". The subsequent processing is the same as the processing of steps S504 to S512 described above. However, since a dedicated app is not installed in the user terminal 300, the management server 100 transmits information for display to the user terminal 300 and causes it to be displayed. The management server 100 transmits cookie information including a purchase history to the user terminal 300, and the user terminal 300 stores the received cookie information.

[0136] By this process, even if a dedicated application is not installed, the management server 100 stores product purchase history information, and it is possible to determine whether or not a specific user has already purchased a specific product.

[0137] <Fifth embodiment> In the above fourth embodiment, the customer can obtain content from the management server 100 through the user terminal 300. However, this is not limited to the above, and other predetermined benefits (for example, a discount on a purchased product, or a financial benefit on subsequent purchases) may also be obtained. Such an embodiment will be described below as the fifth embodiment. Note that the fifth embodiment is basically the same as the fourth embodiment, and therefore differences will be mainly described.

[0138] The management server 100 according to the fifth embodiment includes a reward provision unit that issues, to the user terminal 300 of a first customer who has purchased a product, a referral image code (QR code or any other code that can be displayed on a flat surface, also referred to as a referral code) that associates at least the user ID of the first customer, the product ID of the purchased product, an access URL, and a specific reward that is applied when the referred customer purchases the product. This reward provision unit may be the QR code issuing unit 113 described above.

[0139] Furthermore, when the benefit granting unit accepts access made by a second customer (introducer) different from the first customer (introducer) using the access URL included in the referral image code, it issues an image code for referral purchase (also referred to as a referral purchase code) that associates at least the first customer, the second customer, the product, and a specified benefit. In issuing the image code for referral purchase, the benefit granting unit grants the referred person an access identifier different from the access identifier granted to the introducer. This allows the referred person to complete the product purchase procedure without having to complete procedures such as user registration.

[0140] The reward giving unit then gives a predetermined reward to either the product purchased using the referral-purchase image code, the first customer, or the second customer.

[0141] Furthermore, when a second customer (introduced person) purchases a product, the benefit granting unit issues a referral image code that associates at least the second customer, the product, and a predetermined benefit that is applied at the time of purchasing the product.

[0142] 18 is a diagram showing an example of referral information in the fifth embodiment. In the referral information 129, a user ID, a product ID, a QR code ID, a discount rate (amount), a contract benefit (ticket), a referral tier, and a referral code are stored in association with each other.

[0143] The user ID stores a user ID that identifies the introducer (the person who purchased the product), and the product ID stores a product ID that identifies the purchased product. The QR code ID stores a URL that accesses content data related to the product. The discount rate (amount) stores information that indicates the degree of discount on the sales price applied when the introduced person purchases the product, specified as a percentage or absolute amount.

[0144] The contract benefit (ticket) stores information specifying the content of the monetary benefit that will be given to either the introducer or the introducee, or both, in subsequent purchases when the introduced person purchases a product. The referral hierarchical level stores information specifying the nesting (hierarchical level) of the introducer. For example, a person who purchases after being introduced by a certain introducer (hierarchical level 1) is in hierarchical level 2, a person who purchases after being introduced by an introducer in hierarchical level 2 is in hierarchical level 3, and so on, where the nesting level is the number of times the introduction was made plus 1. The referral code stores an identifier that associates a user ID, a product ID, a QR code ID, a discount rate (amount), a contract benefit (ticket), and the referral hierarchical level.

[0145] Fig. 19 is a diagram showing an example of the flow of a product introduction process. First, the benefit granting unit of the management server 100 encodes the introduction information to issue a QR code for introduction, and sends it to the user terminal 300 of the customer (first customer) who purchased the product (step S601). Here, the access destination URL specified by the QR code ID included in the introduction information is a URL used when the seller terminal 200 and the introduced customer terminal 300' used by the introduced customer access the management server 100, and includes the host name and domain name of the management server 100. Also, the introduction hierarchy includes a nest of introducers.

[0146] The user terminal 300 displays the sent introduction QR code (step S602). Then, when the introduction QR code is read by the introduced party terminal 300', the introduced party terminal 300' accesses the product site using the access URL included in the introduction QR code (step S603). After that, the management server 100 performs the above-mentioned content provision process (step S604).

[0147] 20 is a diagram showing an example of the flow of the introduction and purchase process of a product. The introduction and purchase process of a product is started when the introduced terminal 300′ accepts a purchase request for the product (step S605) after the content is provided in S604 by the same process as the introduction process of the product described above.

[0148] The reward granting unit of the management server 100 that has received the purchase request issues a QR code for referral purchase including the discount amount or discount rate, and transmits it to the introduced person's (second customer's) terminal 300' (step S606). Here, the QR code for referral purchase is basically the same as the referral QR code, but the user ID of the introduced person (second customer) is added to the user ID.

[0149] The introduced party's terminal 300' displays the QR code for the introduced purchase that has been sent (step S607). Then, when the seller terminal 200 reads the QR code for the introduced purchase, the seller terminal 200 (store's cash register terminal) performs the same settlement process as in steps S506 to S508 described above (steps S608 to S508). At that time, the discount rate or discount amount included in the QR code for the introduced purchase is applied to the selling price of the product. Also, for example, when the introduced party purchases the product on the Internet, such as an EC site, the QR code for purchase or URL is entered at the time of purchase on the EC site, and the EC site sends the purchase information to the management server 100 and performs purchase benefit processing, etc. (steps S608 to S508, S509 to S601). In this way, it is possible to deal with this by introducing the functions of the seller terminal (cash register, etc.) 200 into the EC site.

[0150] In addition, the user account management unit 118 of the management server 100 obtains the introduced person's user ID, product ID, purchase store, purchase date and time, number of items purchased, etc. from the purchased information, and stores the product ID, purchase store, purchase date and time, number of items purchased, etc. in the product purchase history of the corresponding user ID in the user history information 128 (step S509).

[0151] When the management server 100 updates the product purchase history, the user account management unit 118 performs a referral purchase benefit process (step S609). The referral purchase benefit process is a process of granting a monetary benefit that can be obtained in the next purchase onward, which is applied to either or both of the introducer and the introduced person. Specifically, a discount coupon ticket, points that can be applied to the product price, etc. are granted to either or both of the introducer and the introduced person. The user account management unit 118 may follow the nesting of the introducer and apply the same or slightly modified (different benefits depending on the nesting distance) purchase benefit to the introducer-related parties within a predetermined hierarchy (e.g., three hierarchical levels). In this way, it is possible to further increase the incentive to become an introducer.

[0152] Then, the reward granting unit of the management server 100 encodes the introduction information, issues an introduction QR code, and sends it to the introduced customer terminal 300' of the customer (second customer) who purchased the product (step S601). In this way, it is possible to realize the introduction process recursively. That is, the introduced person can become an introducer and introduce the product to another introduced person.

[0153] The content change unit 116 may change the content data associated with the URL depending on whether the customer who accessed the URL has introduced the product to any person who has been introduced. For people who have introduced the product, it is possible to select content that is useful for appealing the product to others, such as by including a catchphrase that succinctly expresses the functionality, thereby supporting active introduction.

[0154] The content change unit may change the content data associated with the URL depending on whether or not the accessing customer has experience introducing other products different from the relevant product (for example, whether or not the customer has introduced other products purchased in the last few months). For those who have introduced other products, content that clearly shows the main points or selling points of the introduction can be selected, which can support active introduction.

[0155] The content change unit may change the content data associated with the URL depending on whether the access identifier included in the introduction image code is used to access the product. If the person being introduced has heard about the product from the introducer, the person being introduced may be able to select content that provides detailed information about the product's functions and usage, which can encourage the person to make a purchase.

[0156] The introduction purchase process has been described above. In the product explanation support system 1 according to the fifth embodiment, the introduction purchase process allows a customer who has purchased a product to obtain a specific benefit (for example, a discount on the purchased product or a monetary benefit on subsequent purchases) by introducing the product to other customers (introduced customers). In addition, a purchaser can become a new introducer and introduce the product to other customers, realizing a chain of introductions.

[0157] In the fifth embodiment, the seller terminal 200 reads the QR code for the referred purchase and performs the settlement process such as payment in the referred purchase process, but the present invention is not limited to this, and for example, the introduced person terminal 300' may read the QR code for the referred purchase transmitted in step S606 and perform the settlement process such as payment. In this way, the introduced person can make a purchase directly without going to the store.

[0158] The above is the fifth embodiment. Note that in all of the above embodiments, the information shown as the access URL is only an example, and an identifier (access identifier) ​​including a description format other than the URL description format may be used. In addition, the above-mentioned URL can be handled more easily by using a shortened URL.

[0159] Furthermore, the functions of the management server 100 may be realized by a system configured with one or more computers.

[0160] Furthermore, the technical elements of the above-described embodiments may be applied independently, or may be divided into a plurality of parts, such as program parts and hardware parts, and then applied.

[0161] The present invention has been described above mainly with reference to the embodiment. [Explanation of symbols]

[0162] 1···Product description support system, 100···Management server, 110···Processing unit, 111···Product information registration unit, 112···Content registration unit, 113···QR code issuing unit, 114···Access reception unit, 115···Access history management unit, 116···Content modification unit, 117···Content transmission unit, 118···User account management unit, 120···Memory unit, 121···Product information, 122···QR code information, 123···Access history information, 124···Content information, 125···Content provision condition information, 126···Content association information, 127···User account information, 128···User-specific history information, 129···Introduction information, 150···Communication unit.

Claims

1. A product explanation support system executed by a computer system including a management server, an access receiving unit that receives an access made by a customer's user terminal using an access identifier included in a code that is previously associated with the product; a content change unit that changes content data associated with the access identifier depending on whether the customer has already purchased the product; a content transmission unit for displaying the changed content data on the user terminal of the customer so that the data can be viewed; a reward provision section which provides an introduction access identifier to the introducer who has purchased the product to introduce the product to another customer who is the introducer, issues an introduction code including the introduction access identifier, and, upon receiving an access made using the introduction access identifier, provides a predetermined reward to the introduced product, the introducer, or the introducer; A storage unit that stores, for each customer, product purchase history information by which the customer has purchased the product; a user account management unit that, when the customer executes a purchase process for the product, receives the product purchase history information including the purchased product and the date and time of purchase, and stores the information in the storage unit; Equipped with the content change unit changes content data associated with the access identifier and the referral access identifier depending on whether the customer has already purchased the product and depending on whether an access made using the access identifier or the referral access identifier has been accepted. A product explanation support system.

2. A product explanation support system executed by a computer system including a management server, an access receiving unit that receives an access made by a customer's user terminal using an access identifier included in a code that is previously associated with the product; a content change unit that changes content data associated with the access identifier depending on whether the customer has already purchased the product; a content transmission unit for displaying the changed content data on the user terminal of the customer so that the data can be viewed; a reward provision section which provides an introduction access identifier to the introducer who has purchased the product to introduce the product to another customer who is the introducer, issues an introduction code including the introduction access identifier, and, upon receiving an access made using the introduction access identifier, provides a predetermined reward to the introduced product, the introducer, or the introducer; A storage unit that stores, for each customer, product purchase history information by which the customer has purchased the product; a user account management unit that, when the customer executes a purchase process for the product, receives the product purchase history information including the purchased product and the date and time of purchase, and stores the information in the storage unit; Equipped with the content change unit changes the content data associated with the access identifier and the referral access identifier depending on whether the customer has already purchased the product and depending on whether the customer has received an access to another product different from the product, the access being performed using the referral access identifier related to the product; A product explanation support system.

3. A product explanation support system executed by a computer system including a management server, an access receiving unit that receives an access made by a customer's user terminal using an access identifier included in a code that is previously associated with the product; a content change unit that changes content data associated with the access identifier depending on whether the customer has already purchased the product; a content transmission unit for displaying the changed content data on the user terminal of the customer so that the data can be viewed; a reward provision section which provides an introduction access identifier to the introducer who has purchased the product to introduce the product to another customer who is the introducer, issues an introduction code including the introduction access identifier, and, upon receiving an access made using the introduction access identifier, provides a predetermined reward to the introduced product, the introducer, or the introducer; A storage unit that stores, for each customer, product purchase history information by which the customer has purchased the product; a user account management unit that, when the customer executes a purchase process for the product, receives the product purchase history information including the purchased product and the date and time of purchase, and stores the information in the storage unit; Equipped with the content change unit changes content data associated with the access identifier and the referral access identifier depending on whether the customer has already purchased the product and depending on whether the access is performed using the access identifier or the referral access identifier. A product explanation support system.

4. A product explanation support method executed by a computer system including a management server, an access acceptance step for accepting an access made by a customer's user terminal using an access identifier included in a code previously associated with the product; a content change procedure for changing content data associated with the access identifier depending on whether the customer has already purchased the product; a content transmission step of displaying the changed content data on the customer's user terminal so that the data can be viewed; a reward provision step of granting an access identifier for introduction to the introducer, who is the customer who has purchased the product, to introduce the product to another customer who is the introducer, issuing an introduction code including the access identifier for introduction, and granting a predetermined reward to the introduced product, the introducer, or the introducer when an access made using the access identifier for introduction is accepted; Implemented the following: The management server includes a storage unit that stores product purchase history information of the customer who has purchased the product, for each customer; a user account management step of receiving, when the customer executes a purchase process for the product, the product purchase history information including the purchased product and the date and time of purchase, and storing the product purchase history information in the storage unit; Implemented the following: in the content change step, content data corresponding to the access identifier and the referral access identifier are changed depending on whether the customer has already purchased the product and depending on whether an access made using the access identifier or the referral access identifier has been accepted; A product explanation support method comprising the steps of:

Images