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

Abstract

To provide a technique for simply providing more useful information about a commodity not purchased yet or a commodity purchased, and offering an incentive for introduction.SOLUTION: A product description support system includes: an access receiving unit which receives an access of an access identifier included in a code associated in advance with a commodity; a content modification unit which modifies a content to be associated with the access identifier in accordance with whether the commodity has been purchased or not; a content transmission unit which displays the content on a terminal of a customer; and a privilege offering unit which issues an introduction code including the access identifier, to a terminal of a referrer, i.e., a customer who purchased the commodity, and offers, when receiving an access with the introduction code, a privilege to the commodity, the referrer or a referred person.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] Patent Document 1 discloses an agency management server that receives proxy management of the two-dimensional code and the content via a terminal of a product provider that provides a product attached with a two-dimensional code in which access information for accessing content including voice is embedded. The agency management server includes: a two-dimensional code designation reception unit that receives designation of the two-dimensional code provided to the product provider from the terminal of the product provider; a management information reception unit that receives input of management information for the product provider to confirm the content of the designated two-dimensional code from the terminal of the product provider; a content reception unit that receives upload of one or more contents associated with the designated two-dimensional code from the terminal of the product provider; a storage unit that stores the designated two-dimensional code, the management information, and the content in association with each other; a management information transmission unit that transmits information for confirming the correspondence between the two-dimensional code, the management information, and the content to the terminal of the product provider; and a distribution unit that distributes the content corresponding to the read two-dimensional code to the terminal of the end user in response to the end user's terminal reading the two-dimensional code.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the above technology, it is possible to provide a server that manages by associating a barcode with content according to the instructions of a product provider. However, even if a potential customer in the store picks up a product displayed in the store and shows interest, just the package description, POP description, or the above-mentioned content provided uniformly may not lead to the feeling of wanting to buy. Also, even when the product is purchased, there are cases where the usage method is not well understood when actually trying to use it, and the satisfaction with the product cannot be obtained, so the effect is not great in this regard.

[0005] An object of the present invention is to provide a technology that gives an incentive for introduction while easily providing more useful information about a product before or after purchase.

Means for Solving the Problem

[0006] This application includes a plurality of means for solving at least a part of the above problems. For example, it is as follows. A product description support system according to an aspect of the present invention is a product description support system executed by a computer system including a management server, and includes an access reception unit that receives an access executed by a customer's user terminal using an access identifier included in a code pre-associated with a product, a content change unit that changes content data associated with the access identifier according to whether the customer has purchased the product, a content transmission unit that causes the changed content data to be displayed viewably on the customer's user terminal, and a privilege granting unit that issues an introduction code including an access identifier for introducing the product to another customer, a referred customer, to the customer who has purchased the product as an introducer, and grants a predetermined privilege to any one of the introduced product, the introducer, or the referred customer when receiving an access executed using the access identifier.

[0007] In addition, in the above-described product description support system, the privilege granting unit issues an introduction code in which at least the introducer, the access identifier, and a predetermined privilege applied at the time of purchasing the product are associated with the user terminal of the introducer. When receiving access executed by a person being introduced different from the introducer using the access identifier included in the introduction code, an introduction purchase image code in which at least the introducer, the person being introduced, the access identifier, and the predetermined privilege are associated is issued, and the predetermined privilege is granted to any one of the product purchased using the introduction purchase code, the introducer, or the person being introduced.

[0008] In addition, in the above-described product description support system, the privilege granting unit may assign an access identifier different from the access identifier assigned to the introducer to the person being introduced.

[0009] In addition, in the above-described product description support system, the predetermined privilege may be to discount the selling price of the product.

[0010] In addition, in the above-described product description support system, the predetermined privilege may be a predetermined financial privilege regarding purchases after the next time for either or both of the introducer and the person being introduced.

[0011] In addition, in the above-described product description support system, when the person being introduced purchases the product, the privilege granting unit may issue the introduction code in which at least the person being introduced, the product, and the predetermined privilege applied at the time of purchasing the product are associated to the person being introduced.

[0012] In addition, in the above-described product description support system, the content change unit may change the content data associated with the access identifier according to whether the customer has introduced the product to the person being introduced.

[0013] Further, in the above-described product description support system, the content change unit may change the content data associated with the access identifier according to whether the customer has experience in introducing another product different from the product.

[0014] Further, in the above-described product description support system, the content change unit may change the content data associated with the access identifier according to whether the access identifier included in the introduction code has been accessed.

[0015] Further, a product description support method according to another aspect of the present invention is a product description support method executed by a computer system including a management server, and includes an access reception procedure for receiving, by a customer's user terminal, an access executed using an access identifier included in a code pre-associated with a product, a content change procedure for changing content data associated with the access identifier according to whether the customer has purchased the product, a content transmission procedure for displaying the changed content data so as to be viewable on the customer's user terminal, and a privilege granting procedure for issuing, to the customer who has purchased the product as an introducer, an introduction code including an access identifier for introducing the product to another customer as an introducee, and granting a predetermined privilege to any one of the introduced product, the introducer, or the introducee when receiving an access executed using the access identifier.

[0016] Also, a product description support program according to another aspect of the present invention is a product description support program for causing a management server to support product description, and causes the management server to receive, by a customer's user terminal, an access executed using an access identifier included in a code pre-associated with a product; a content change procedure for changing content data associated with the access identifier according to whether the customer has purchased the product; a content transmission procedure for displaying the changed content data so that it can be viewed on the customer's user terminal; and, when the customer who has purchased the product is used as a referrer, issuing a referral code including an access identifier for the referrer to refer the product to another customer who is the referred customer, and when receiving an access executed using the access identifier, executing a privilege granting procedure for granting a predetermined privilege to any one of the referred product, the referrer, or the referred customer.

Advantages of the Invention

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

[0018] Problems, configurations, and effects other than those described above will be clarified by the description of the following embodiments.

Brief Description of the Drawings

[0019]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Modes for Carrying Out the Invention

[0020] Next, a product description support system 1 to which an embodiment according to an aspect of the present invention is applied will be described with reference to the drawings. In the following embodiments, when necessary for convenience, the description will be divided into a plurality of sections or embodiments. However, unless otherwise specified, they are not unrelated to each other, and one is related to a modification, details, supplementary explanation, etc. of a part or all of the other.

[0021] Also, in the following embodiments, when referring to the number of elements, etc. (including the number, numerical value, quantity, range, etc.), unless otherwise specified or clearly limited to a specific number in principle, it is not limited to that specific number, and it may be more than or less than the specific number.

[0022] Furthermore, in the following embodiments, it goes without saying that the components (including element steps, etc.) are not necessarily essential unless otherwise specified or clearly considered essential in principle.

[0023] Similarly, in the following embodiments, when referring to the shape, positional relationship, etc. of components, etc., unless otherwise specified or clearly considered not to be the case in principle, it includes those substantially approximate or similar to the shape, etc. This also applies to the above numerical values and ranges.

[0024] Also, in all the drawings for explaining the embodiments, the same members are basically given the same reference numerals, and the repeated description thereof is omitted.

[0025] <First Embodiment> FIG. 1 is a configuration diagram of a product description support system 1 according to the present embodiment. The product description support system 1 includes a management server 100, a seller terminal 200, and a user terminal 300. A store clerk of a store uses the seller terminal 200, and a customer uses a user terminal 300 such as his or her own smartphone. Both the seller terminal 200 and the user terminal 300 read a QR code, an image, etc. printed or pasted on a package, a pamphlet, a flyer, a publicity image, etc. of product A 400 or the like, and access the domain (contents such as a web page) of the management server 100. In the present embodiment and the following embodiments, an example using a QR code is described. However, the present invention is not limited to this, and a code (an object including a code) that enables reading of information included in a terminal equipped with a reading device may be used. For example, a one-dimensional barcode, a two-dimensional code such as a stack type or a matrix type may be used. Further, an electronic tag capable of reading information by wireless short-range communication such as NFC or RFID may be used.

[0026] The seller terminal 200 and the user terminal 300 are information processing devices such as smartphones, personal computers, and tablet devices. However, other wearable terminals such as smartwatches, headsets, gloves, and chokers may be used.

[0027] The seller terminal 200 and the user terminal 300 communicate with the management server 100 using a data communication network such as a carrier network or the Internet, using a predetermined data transmission protocol (Http (Hyper Text Transfer Protocol), Https (Http (Hyper Text Transfer Protocol Secure)), etc.). The seller terminal 200 and the user terminal 300 perform transmission and reception of web contents using a URL (Uniform Resource Locator), so-called web browsing. For example, the seller terminal 200 and the user terminal 300 cause a display (not shown) or the like to display a company homepage or web contents obtained by requesting the management server 100.

[0028] The management server 100 responds to various requests by the data transmission protocols from the seller terminal 200 and the user terminal 300. For example, the management server 100 causes the seller terminal 200 and the user terminal 300 that access through web browsing by reading a QR code provided on the product A400 or the like to reproduce content data including a predetermined video or the like.

[0029] FIG. 2 is a diagram showing an example of a QR code (registered trademark). The QR code 500 is a design QR code (with decorations around the QR code) called "Look at this QR code". The QR code 500 is a sticker that is attached later to a blister pack (packaging) of the product A400 or the like. By making it a "Look at this QR code" sticker, it is intended to attract the attention of a customer who picks up the product A400.

[0030] In addition, the QR code 500 may be a "Look at this QR code" with a different design. For example, the QR code 501 is an example that adopts a deformed animal character for the "Look at this QR code". Also for example, the QR code 502 is an example that adopts a deformed human character for the "Look at this QR code". Here, it is called a "Look at this QR code", but it may also be called an "Enjoyment code", "Full of happiness", etc., and can be a QR code that is displayed together with a copy that attracts attention.

[0031] FIG. 3 is a diagram showing a configuration example of the 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 issuance unit 113, an access reception 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] Figure 4 is a diagram showing an example of the data structure of product information, QR code information, and access history information. The product information 121 includes a product ID, a JAN code (including a business operator code, a product item code, etc.), product attributes, and purchaser attributes. The product attributes include product types such as home appliances, games, kitchen supplies, clothing, food, and housing supplies, product specifications such as the size, weight, dimensions, and color of the product, the sales region, the product replacement period, the usage frequency, the usage location, the distinction between consumables and durable goods, the sales form (special sale products or event products), etc. The purchaser attributes include the target layer of the product (male, female, age group, etc.). That is, it can be said that the product information 121 is information in which the sales region is associated with each product. Also, it can be said that the product information 121 is information in which purchaser target attributes including at least one of gender, age group, and occupation are 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 (relative directory from the domain + root path) and parameters. The parameters include, for example, the JAN code of the product and other additional data.

[0034] Here, as the configuration of the access URL in the present embodiment, a URL that is considered easy to analyze access and is likely to match various search engines is adopted. Specifically, It is desirable to use a URL such as 「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 host name + domain name part, 「g-code」 is the delimiter character 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」 indicates a unique code for special sales, events, sales regions, etc. Although not shown here, codes indicating sizes such as siz=xl can be added. Also, by using the design classification code defined in the examination criteria of the Design Law and the like for the product classification code, it is possible to achieve unity.

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

[0036] The access history information 123 includes the QR code ID, the access URL, and the access history for each session. The access history for each session includes the access date and time, the content ID displayed, the stay time (display time) of the content, and for videos, the display time ratio with respect to the total video time, the access region, etc. The access region is information estimated from the IP address and the like of the region where the seller terminal 200 and the user terminal 300 accessed by reading the QR code. Also, the accessed region includes not only the base station unit but also regions such as prefecture units.

[0037] FIG. 5 is a diagram showing an example of the data structure of content information, content provision condition information, and content association information. The content information 124 includes an 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 URI of a website) from which the content data can be acquired.

[0038] The content provision condition information 125 includes a content ID, a provision condition, and a target. The provision condition includes combinations of various provision conditions and the content IDs to be provided according to the combinations. Various combinations of the provision conditions can be considered. For example, even for the same product with the same product ID, there may be cases for products for region X (local model) and products for region Y. In such cases, since it is necessary to provide content corresponding to each region, it includes information in which the provision region for providing the content data is associated with each content data.

[0039] Also, it is considered that the information the customer wants to know is different before and after purchasing a product. In that case, since it is considered that the access is from a storefront before purchase and from outside the storefront such as at home after purchase, the content data can be associated with each according to the access region as a provision condition.

[0040] Also, it is considered that the information the customer wants to know is different for the first access, the second and subsequent accesses, or the access after a predetermined period. In that case, the content data can be associated with each according to the access count or the elapsed period from the first access as a provision condition. Not limited to these, the content data can be associated with each using various types of information such as a JAN code, product attributes, purchaser attributes, and the time zone of access as provision conditions.

[0041] For example, as a provision condition, the time zone when the content data is provided may be associated, or the provision area of the content data may be associated with the sales area of the product. Alternatively, as a provision condition, purchaser attributes including at least one of gender, age group, and occupation may be associated.

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

[0043] Note that preferably, the more the number of times of provision to a predetermined customer, the more detailed description of the product is included in the associated content data. Alternatively, it is desirable to specify the average viewing time (average of past display times) of the video related to past accesses on the customer's user terminal and set the content data of the video having a playback time corresponding to the average viewing time as a provision condition. Or, it may be good to specify the viewing time ratio (ratio of the display time to the total time of the past video) of the video related to past accesses on the customer's user terminal and set the content data of the video having a playback time corresponding to the viewing time ratio as a provision condition.

[0044] In the "aim", a sentence explaining the aim of setting the provision condition for the content is stored. By referring to the "aim", the seller can confirm the intention of providing the content to the customers who satisfy the provision condition.

[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 that identifies the respective HTTP sessions of the seller terminal 200 and the user terminal 300 that are simultaneously connected to the management server 100. The management server 100 pseudo-secures a state by sharing the session ID in order to ensure continuous processing transitions in the session stateless HTTP protocol. Then, the management server 100 controls the content to be provided for each of the seller terminal 200 and the user terminal 300 by appropriately rewriting the content ID to be displayed on the individual seller terminal 200 and user terminal 300 in association with the session ID. Note that the content ID associated with the QR code ID is not limited to one, and a plurality of content IDs may be associated with the order so that video content is sequentially played back.

[0046] The product information registration unit 111 receives input of information to be stored in the product information 121 and registers it in the product information 121. The content registration unit 112 receives content data (Web page or video) and registers it in the content information 124 and the content providing condition information 125. The QR code issuing unit 113 issues a QR code including the access URL and the product ID.

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

[0048] The access history management unit 115 records the provision history for each 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 manages the change of the content data associated with the URL included in the QR code for each session by selecting from among a plurality of pre-stored content data according to a predetermined provision condition. More specifically, the content change unit 116 identifies the product associated with the URL used for the URL access, and selects the content data that satisfies the predetermined provision condition from among the plurality of content data associated with the identified product, thereby changing the content data associated with the URL. When there are a plurality of contents that satisfy the provision condition, one content is selected according to a predetermined priority order and used as the content data associated with the URL. The priority order includes, for example, the order of the largest number of matching conditions, the order of the latest creation date and time of the content, and 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 the content data from among the plurality of content data for which the current time corresponds to the provision time zone.

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

[0052] In addition, the content change unit 116 uses the information of the QR code information 122 to identify the product associated with the URL used for the access, identifies the purchaser target attribute of the identified product, and selects the content data from among the plurality of content data for which the purchaser target attribute satisfies the provision target attribute.

[0053] In addition, the content change unit 116 may select content data whose number of times of provision satisfies a predetermined number from among a plurality of content data. That is, the content change unit 116 may select content with a high playback frequency.

[0054] In addition, when the content change unit 116 can obtain information on whether a product has been purchased, such as when the QR code information 122 includes purchase history information (product ID, purchase store, purchase date and time, number of purchases) indicating that the product has been purchased, the content data to be selected can be made different before and after the purchase. For example, before purchasing a product, content data for promoting the sale of the product, in which "before purchase" is specified in the provision conditions, is selected. On the other hand, after purchasing the product, content data for explaining the specific usage method of the product, in which "after purchase" is specified in the provision conditions, is selected.

[0055] Note that the content change unit 116 may select content that satisfies all of the provision conditions including time, sales area, purchaser attribute, number of times of provision, etc. as described above. Alternatively, the content change unit 116 may select content that satisfies any one or more of the provision conditions. If there are a plurality of selected contents, as described above, one content is selected according to a predetermined priority order and used as content data 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 with the QR code attached during a predetermined time period in order to display the content that is most desired to be introduced at present.

[0057] The content transmission unit 117 transmits the content data changed by the content change unit 116 to the user terminal 300 and causes it to be displayed viewable on the user terminal 300.

[0058] The user account management unit 118 assigns a user ID that can distinguish a user (customer) 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 other Internet or the like.

[0060] Figure 6 is a diagram showing a hardware configuration example of the 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 includes a processor 101, a memory 102, a storage device 103, a communication device 104, and a bus connecting the respective devices.

[0061] The processor 101 is an arithmetic device such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit).

[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 such as a so-called hard disk (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory that can store digital information.

[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 issuance unit 113, access reception 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, storage device 103, or a ROM device (not shown), loaded onto the memory 102 during execution, and executed by the processor 101.

[0066] Also, the storage unit 120 of the management server 100 is realized by the memory 102 and the storage device 103. Further, the communication unit 150 is realized by the communication device 104. The above is an example of the hardware configuration of the management server 100.

[0067] The configuration of the management server 100 can be further classified into more components according to the processing content. Also, one component can be classified to execute more processes.

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

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

[0070] FIG. 7 is a diagram showing an example of the flow of the QR code issuance process. When the management server 100 is operating, the QR code issuance process is in a standby state and is started when a login request is received from the seller terminal 200.

[0071] First, the seller terminal 200 logs in to the management server 100 (step S001). Regarding the login process, any general authentication (such as password authentication, biometric authentication, passcode authentication, image authentication, etc.) may be used. When the login is confirmed, the product information registration unit 111 starts the registration process (step S002). Specifically, the product information registration unit 111 displays a seller input screen 600, which will be described later, on the seller terminal 200.

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

[0073] Then, when the seller terminal 200 sends a QR code issuance request (step S008), the QR code issuance unit 113 issues a QR code using each piece of information received in steps S003 to S006 (step S009). Specifically, the QR code issuance unit 113 generates a QR code image using an existing encoding algorithm for a character string including an access URL and a product ID and displays it on the seller terminal 200. Note that the QR code issuance request may be made at the timing required by the user of the seller terminal 200, and it 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] Note that the processing of each seller terminal 200 may be performed not only by the seller but also by the manufacturer. Before product manufacturing or shipment, a "Look at Me QR Code" may be attached to the product (e.g., package or main body) through similar processing. Furthermore, for customers who have already registered as members, the "Look at Me QR Code" may be sent as an image, for example, via email magazine.

[0076] The above is the content of the QR code issuance process. According to the QR code issuance process, a QR code corresponding to product information, namely, a "Look at Me QR Code" that can dynamically distribute various content data according to the provision conditions, can be easily created and printed.

[0077] FIG. 8 is a diagram showing an example of screen transition at the time of QR code issuance. On the seller terminal 200, a seller input screen 600 transmitted from the management server 100 is displayed in step S002 of the QR code issuance process. The seller input screen 600 includes fields for receiving input of product information, content information, condition information for content provision, content association information, an upload button 601 for uploading content information, and a QR code issuance 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 issuance button 602 receives input, it transmits the input product information, condition information for content provision, and content association information to the management server 100 and causes the screen to transition to a QR code issuance result screen 650.

[0078] On the QR code issuance result screen 650, a QR code ID, a QR code image, an access URL, and a product ID are displayed. Also, on the QR code issuance result screen 650, a download button 651 for receiving an operation to download the QR code image for printing is displayed. When the download button 651 receives an input, it downloads "Take a look at the QR code" and outputs the print data to the printer. The QR code issuance unit 113 may display options 652 with a design including "Take a look at the QR code" and send the "Take a look at the QR code" of the selected design to the seller terminal 200.

[0079] Figure 9 is a diagram showing an example of the flow of content providing processing. The content providing processing enters a standby state when the management server 100 operates and starts when there is an access from the user terminal 300.

[0080] First, the user terminal 300 reads the QR code 500 of "Take a look at the QR code", identifies the included URL, and accesses the identified URL (step S101). When the access reception unit 114 receives the access, it refers to the access history information 123 of the URL to be accessed (step S102). Then, based on the access history information 123 and the content providing condition information 125, the content change unit 116 identifies the content ID associated with the target URL 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 reason the content transmission unit 117 "starts" the transmission of the content data is that the content may be for streaming playback of a video. In the case of content data that does not perform streaming playback, the content transmission unit 117 transmits the content data at once.

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

[0082] Note that when the streaming playback of the content data ends, the content transmission unit 117 may continue to play other content data as long as the viewing continues.

[0083] The above is the content of the content providing process. According to the content providing process, the customer (user) can view the content data according to the content providing conditions and also according to the access history. Therefore, it can be said that useful information can be easily obtained for the product before purchase or the product after purchase.

[0084] FIG. 10 is a diagram showing an example of content selection (time zone). In the example of FIG. 10, the content data provided from the management server 100 changes in the time zones before 13:00 and after 13:00. For example, when the "Watch QR code" is for the product "cabbage peeler" and the user terminal 300 accesses the management server 100 at 10:20, the content data includes a video introducing how to use the cabbage peeler, information on the ongoing time sale, or a video introducing lunch recipes. However, when the user terminal 300 accesses the management server 100 at 15:00, the content data includes a video introducing dinner recipes using the cabbage peeler.

[0085] FIG. 11 is a diagram showing an example of content selection (region). In the example of FIG. 11, the content data provided from the management server 100 changes according to the region where the product is sold. For example, when the "Look at this QR code" belongs to the product "Cabbage Peeler", if it is a QR code including the JAN code for the X region (for example, Hokkaido region) as a parameter, when the user terminal 300 accesses the management server 100, the information of the time sale being carried out limited to the X region is included in the content data. However, if it is a QR code including the JAN code for the Y region (for example, Okinawa region) as a parameter, when the user terminal 300 accesses the management server 100, the information of the time sale being carried out limited to the Y region is included in the content data.

[0086] FIG. 12 is a diagram showing an example of content selection (number of accesses to the same URL). In the example of FIG. 12, the content data provided from the management server 100 changes according to the number of accesses to the same URL. Here, the number of accesses to the same URL is the number of accesses to the same URL used for access for each user terminal 300. Typically, the number of times of accessing the management server 100 by reading the same "Look at this QR code" from the same user terminal 300 is the number of accesses to the same URL.

[0087] For example, when the "Look! QR Code" belongs to the product "Cabbage Slicer", it is conceivable to peel off the "Look! QR Code" from the cabbage slicer and reattach it to furniture or the like (for example, a refrigerator) and access it multiple times. Depending on the number of accesses, if it is the 1st to 3rd time, when accessing the management server 100 from the user terminal 300, information of display type 1 (for example, tips on how to easily shred cabbage) is included in the content data. If it is the 4th time, when accessing the management server 100 from the user terminal 300, information of display type 2 (for example, tips on how to cut well) is included in the content data. If it is the 5th time, when accessing the management server 100 from the user terminal 300, information of display type 3 (for example, how to cut vegetables other than cabbage) is included in the content data. If it is 6th time or later, when accessing the management server 100 from the user terminal 300, information of display type 4 (for example, simple recipes using the cabbage slicer) is included in the content data.

[0088] More specifically, in the content data of display type 1, in the case of tips on how to easily shred cabbage, mainly using videos, it provides information with text, pictures, arrows, onomatopoeia, etc. added to the main video of easy-to-use (ready-to-use) methods within 1 to 2 minutes. This is content aimed at guiding users not to make mistakes in usage, enabling them to understand that the product is easy to use and convenient, and if possible, sharing its goodness with others (prompting sharing on SNS implicitly if possible) to lead to information dissemination and product promotion. Then, at the end of the video, a set phrase "Next, new information will be provided. 'Also, look!' " is inserted. The description content of the video includes specific operation procedures of the product such as (1) choose a heavy cabbage, (2) cut it in half along the core direction, (3) place your thumb on the core and hold it, (4) tilt the blade at 45°, and (5) pull it forward with a long stroke, as well as a concise summary and organized explanation.

[0089] In addition, for the content data of display type 2, in the case of the know-how of good cutting methods, mainly using videos, when referring after getting used to the usage, it is content that promotes more positive and better usage methods and provides information that can make the users become more fans. Here too, at the end of the video, put the set phrase "Next, new information will be provided. 'Also, take a look!'". The description content of the video includes (1) as the way to pull the cabbage peeler, when cutting thinly, pull it gently without applying force to the index finger, when cutting short, pull it short like scraping, etc., specific operation procedures, and (2) as the way to prevent the leaves from falling apart, pull while stroking the periphery, cut off the extra leaves, etc., specific operation procedures, and as a summary, a concise and organized explanation.

[0090] In addition, for the content data of display type 3, in the case of cutting methods other than cabbage, for access after being satisfied with shredding cabbage, it is content that promotes more general usage methods and provides information that can make the users become more fans. Here too, at the end of the video, put the set phrase "Next, new information will be provided. 'Also, take a look!'". The description content of the video includes (1) when shaving daikon thinly, specific operation procedures such as shaving long, shaving diagonally, shaving while turning, etc., (2) when shaving cucumber, specific operation procedures such as shaving long, shaving diagonally, shaving vertically, etc., (3) when shaving other ingredients, specific operation procedures in the case of carrots, celery, etc., and as a summary, a concise and organized explanation.

[0091] In addition, for the content data of display type 4, in the case of simple recipes using a cabbage peeler, on the premise of being used to the usage method, it is content that promotes more applied and effective usage methods and provides information that can make the users become more fans. Here too, at the end of the video, put the set phrase "Next, new information will be provided. 'Also, take a look!'". The description content of the video includes (1) cabbage shredding recipes, (2) daikon thin slicing recipes, (3) vinegar dish recipes, etc., and as a summary, a concise and organized explanation.

[0092] The above is the product description support system 1. According to the product description support system 1 as in the above embodiment, it is possible to simply provide more useful information about various information regarding the product before purchase or after purchase.

[0093] Note that the content change unit 116 may vary the content to be selected according to the user level of the customer. Specifically, in the storage unit of the management server 100, information in which a level indicating proficiency is associated is stored for each content data. The content change unit 116 manages the user level indicating the proficiency with respect to the product specified by the QR code (URL) of each customer. Then, each time the number of accesses to the URL used for access in the customer's user terminal 300 increases, the content change unit 116 raises the user level. On the other hand, when the content change unit 116 is requested by the customer to display content data at a level lower than the current user level, the content change unit 116 lowers the user level of the customer to the level associated with the content data for which the display is requested. And the content change unit 116 selects content data according to the user level from among a plurality of content data.

[0094] The present invention is not limited to the above embodiment. Various modifications are possible within the scope of the technical idea of the present invention for the above embodiment. Specifically, when selecting content data in step S103 of the above-described content providing process, POS (Point Of Sales) data possessed by the store may be used to select content data. For example, more suitable content data may be selected according to the sales volume and the attributes of the purchasers for each sales area using the POS data. Note that the POS data includes sales information such as JAN code, sales date, sales area, store, sales volume, purchaser attributes, sales price, and the like.

[0095] In addition, the content change unit 116 may select content data according to the order of the high purchase rate of the product within a predetermined time after viewing the content, using the POS data. By doing so, content data that can obtain a higher sales promotion effect can be provided.

[0096] In addition, the content change unit 116 may identify the current time and identify the product associated with the URL used for access and its sales area. Then, the content change unit 116 may select content data according to the order of the high purchase rate of the product within a predetermined time after viewing the content, using the POS data, among the content data in which the sales area of the identified product corresponds to the provided area and the current time corresponds to the content-providing time zone. By doing so, content data that can obtain a higher sales promotion effect can be provided.

[0097] <Second Embodiment> In addition, 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 the second embodiment. Note that since the second embodiment is basically the same as the first embodiment, the description will focus on the differences.

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

[0099] FIG. 14 is a diagram showing an example of the flow of content providing processing according to the second embodiment. First, the user terminal 300 reads the QR code 500 of "Check this out QR code", identifies the included URL, and accesses the identified URL (step S201). At this 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 the content ID associated with the target URL based on the cookie information 160, the access history information 123, and the content providing condition information 125, and performs a process of registering it in the content association information 126 related to the session (step S203).

[0100] Specifically, the content change unit 116 obtains the number of accesses to the URL used for access in the user terminal 300, which is the same URL access count, from the cookie information 160, selects content data whose same URL access count satisfies the provision count from among a plurality of content data, and registers it in the content association information 126 related to the session. At this time, content data for which a more detailed explanation is to be given may be selected according to the same URL access count. For example, at the time of the first access, content data for which an outline explanation such as the purpose, usage scenario, and effects is given, and at the time of the second and subsequent accesses, content data for which a detailed function explanation is given, etc.

[0101] Alternatively, the content change unit 116 may obtain 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 according to the elapsed time from the most recent access date and time or the first access date and time. By doing so, it is possible to provide appropriate content data to users who access frequently or to users for whom a predetermined period (for example, one month) has elapsed since the first access.

[0102] When the display of content data is completed on the user terminal 300 (step S106), the access history management unit 115 updates the history of the access, 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] In addition, when the streaming playback of content data ends, the content transmission unit 117 may continue to play other content data as long as the viewing continues.

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

[0105] <Third Embodiment> In addition, the user terminal 300 may be made to hold an application software corresponding to the product description support system 1 (hereinafter sometimes referred to as an "app") so that it can be executed. The management server 100 holds user account information and access history for each customer, and may select content data using the account information when there is an access. This will be described below as the third embodiment. Since the third embodiment is basically the same as the first embodiment, the description will focus on the different points.

[0106] FIG. 15 is a diagram showing an example of user account information in the third embodiment (app usage). 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, gender, age, address, etc. of the user (customer). The name, gender, age, address, etc. of the user (customer) are stored as those input by the user (customer) himself / herself on the app of the user terminal 300. Also, when the user inputs name, gender, age, address, etc. on the app of the user terminal 300, the user account management unit 118 assigns a user ID that can distinguish the user (customer) from other users, and generates the user account information 127 and the user-specific history information 128.

[0107] In the user-specific history information 128, a user ID, an access history, and a product purchase history are stored in association with each other. The access history includes the access date and time, the displayed content ID, the stay time, the cumulative access count, etc. for each URL accessed by the "Check it out QR code". Note that the product purchase history includes the product ID of the product purchased in the past, the purchase date and time, the purchase store, the number of purchases, etc. The product purchase history will be described later in the fourth embodiment.

[0108] FIG. 16 is a diagram showing an example of the flow of content providing processing in the third embodiment. First, the app of the user terminal 300 reads the QR code 500 of the "Check it out QR code", identifies the included URL, and accesses the identified URL (step S301). At that time, the user ID set in the app is transmitted together.

[0109] Then, instead of step S103, the content change unit 116 identifies the content ID 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 providing condition information 125, and performs a process of registering it in the content association information 126 related to the session (step S303).

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

[0111] Alternatively, the content change unit 116 may obtain the most recent access date and time to the URL used for access in the user terminal 300, or the first access date and time, from the user-specific history information 128, and select content data according to the elapsed time from the most recent access date and time or the first access date and time. By doing so, it is possible to provide appropriate content data to users who access frequently or to users for whom a predetermined period (for example, one month) has elapsed since the first access.

[0112] Alternatively, the content change unit 116 may obtain at least one of gender, age group, and occupation from the user information in the user account information 127, and select content data that satisfies the attributes of the target recipient. By doing so, it is possible to provide appropriate content data according to the user attributes.

[0113] Alternatively, the content change unit 116 may obtain the average viewing time of videos related to past accesses on the user terminal 300 and select content data of a video having a playback time corresponding to the average viewing time. By doing so, it is possible to provide appropriate content data according to the user's video viewing tendency (such as how long the viewing time is before watching to the end). That is, content data including videos with a long playback time can be provided to users who tend to watch long videos, and content data including videos with a short playback time can be provided to users who do not tend to watch long videos.

[0114] Then, when the streaming playback of the content data ends, the content transmission unit 117 may continue to play other content data as long as the viewing continues.

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

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

[0117] <Fourth Embodiment> Next, the fourth embodiment will be described below. Since the fourth embodiment is basically the same as the first embodiment, the description will focus on the different points.

[0118] The fourth embodiment is characterized by providing different content to the user before and after purchasing a product. Therefore, the management server 100 stores the purchase history of products for each user in the user-specific history information 128.

[0119] FIG. 17 shows an example of the flow of processing for collecting the purchase history of products.

[0120] First, an example is shown in which a dedicated app for performing a purchase process 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 receiving a purchase process request from the user, the user terminal accesses the URL included in the QR code and requests the management server to perform a process of updating 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, it is also assumed that there is no seller terminal 200 in the store. Therefore, the user terminal 300 displays a screen for accepting an input of the presence or absence of the seller terminal 200 in the store. The user, who is a customer, inputs "Yes" if the seller terminal 200 exists in the store and "No" if it does not. When the seller terminal 200 is input as "No" (in step S503, "No"), the user terminal 300 displays a purchase confirmation and then ends the process as a provisional purchase process (step S511).

[0122] On the one hand, when the user account management unit 118 of the management server 100 receives a request for a process to update purchase history information from the user terminal 300, it acquires the customer's user ID and identifies the product ID based on the URL to which access has been received. Then, the QR code issuing unit 113 of the management server 100 generates a purchase QR code including the product ID, the user ID, and the URL of the access destination, and sends it to the user terminal 300 (step S504). Here, the URL of the access destination is the URL used when the seller terminal 200 accesses the management server, and includes the host name and domain name of the management server 100.

[0123] When the user terminal 300 receives the purchase QR code from the management server 100 when the seller terminal 200 inputs "Yes" (Yes in step S503), it 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, for example, it is possible to add processes such as reduction of points for purchased products and discount processing. When the payment process is completed, the seller terminal 200 accesses the URL included in the read QR code and sends purchase completion information (including the user ID, product ID, purchase store, purchase date and time, purchase quantity, etc.) indicating that the purchase has been made to the management server 100 (step S507).

[0124] In response to this, the user account management unit 118 of the management server 100 acquires the user ID, product ID, purchase store, purchase date and time, purchase quantity, etc. from the purchase completion information, and stores the product ID, purchase store, purchase date and time, purchase quantity, etc. in the product purchase history of the corresponding user ID in the user-specific 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 a 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 ("Purchase Confirmation" display) (step S511). Also, the user terminal 300 also displays information indicating that the purchase history has been updated and the purchase has been completed ("Purchase Confirmation" display) (step S512). For example, when purchasing the corresponding product on the Internet such as an EC site, by transmitting the purchase QR code or URL to the corresponding EC site at the time of purchase, 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 the purchase confirmation process (steps S506 to S510). In this way, by introducing the functions of the seller terminal (such as a cash register) 200 into the EC site, the same process can be performed even on the EC site.

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

[0127] The above describes the collection process of the purchase history information.

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

[0129] Note that 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 included in the new QR code is the same as the information included in the above-mentioned "look at me QR code", but can further include information indicating that the product has been purchased. Alternatively, when the QR code issuing unit 113 issues a new QR code, it can associate the QR code information 122 with purchase history information (user ID of the purchasing user, product ID, purchasing store, purchase date and time, number of purchases) indicating that the product has been purchased.

[0130] When the seller terminal 200 receives a new purchased QR code, for example, it can be printed on a card with a magnet attached and handed to the customer. Of course, the customer can also print it. The customer can stick it on a refrigerator or the like for storage and, when wanting to view the content, can easily view useful content by reading the QR code.

[0131] <Modification Example of the Fourth Embodiment> In the above-described fourth embodiment, the user terminal 300 transmitted a request for pre-purchase processing to the management server 100 by means of the installed dedicated application. However, not limited to this, in the user terminal 300 in which the dedicated application is not installed, pre-purchase processing of a product may be performed using cookie information.

[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 by the processing of steps S102, S203, and S104 shown in FIG. 14 above. The content data includes content that enables the reception of a request for pre-purchase processing by, for example, displaying a "Pre-purchase processing button" on a web page.

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

[0135] Here, it is also assumed that there is no seller terminal 200 in the store. Therefore, the management server 100 displays a screen on the browser of the user terminal 300 or the like to receive an input regarding the presence or absence of the seller terminal 200 in the store. The user, who is a customer, inputs "Yes" if the seller terminal 200 exists in the store, and inputs "No" if it does not exist. The subsequent processing is the same as the processing of steps S504 to S512 described above. However, since the dedicated application 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 sends cookie information including the purchase history to the user terminal 300, and the user terminal 300 stores the received cookie information.

[0136] Through such processing, even if the dedicated application is not installed, the purchase history information of the product can be stored in the management server 100, and it is possible to determine whether a specific product has been purchased by a specific user.

[0137] <Fifth Embodiment> In the fourth embodiment described above, the customer could obtain content from the management server 100 using the user terminal 300. However, this is not the only case, and other predetermined privileges (for example, discounts on purchased products or financial benefits obtained in subsequent purchases) may be obtained. Such an embodiment will be described below as the fifth embodiment. Since the fifth embodiment is basically the same as the fourth embodiment, the description will focus on the differences.

[0138] The management server 100 according to the fifth embodiment includes a privilege granting unit that issues an introduction image code (a QR code or various other codes that can be displayed on a plane, also referred to as an introduction code) in which at least the user ID of the first customer who is a customer who has purchased a product, the product ID of the purchased product, the access URL, and a predetermined privilege applied when the introduced customer purchases the product are associated with the user terminal 300 of the first customer. This privilege granting unit may be the above-described QR code issuing unit 113.

[0139] In addition, when the privilege granting unit receives an access executed by a second customer (the introduced customer) different from the first customer (the introducer) using the access URL included in the introduction image code, the privilege granting unit issues an introduction purchase image code (also referred to as an introduction purchase code) in which at least the first customer, the second customer, the product, and the predetermined privilege are associated. Note that in issuing the introduction purchase image code, the privilege granting unit assigns an access identifier different from the access identifier assigned to the introducer to the introduced customer. Thereby, the introduced customer can perform the product purchase procedure without having to perform operations such as procedures for user registration.

[0140] Then, the privilege granting unit grants a predetermined privilege to either the product purchased using the referral purchase image code, the first customer, or the second customer.

[0141] In addition, when the second customer (the referred person) purchases a product, the privilege granting unit issues a referral image code associating at least the second customer, the product, and a predetermined privilege applicable at the time of product purchase.

[0142] FIG. 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 conclusion privilege (ticket), a referral hierarchy, and a referral code are stored in association with each other.

[0143] The user ID stores a user ID that identifies the referrer (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 for accessing content data related to the product. In the discount rate (amount), information indicating the degree of discount of the selling price applied when the referred person purchases the product is specified and stored by a ratio or an absolute amount.

[0144] The conclusion privilege (ticket) stores information specifying the content of the financial preferential treatment obtained in subsequent purchases applicable to either or both of the referrer and the referred person when the referred person purchases a product. The referral hierarchy stores information specifying the nest (hierarchy) of the referrer. For example, the number of times of referral + 1 may be regarded as the nest, such that a person who purchases through referral by a certain referrer (level 1) is level 2, and a person who purchases through referral by a referrer at level 2 is level 3. The referral code stores an identifier associating the user ID, the product ID, the QR code ID, the discount rate (amount), the conclusion privilege (ticket), and the referral hierarchy.

[0145] Figure 19 is a diagram showing an example of the flow of product introduction processing. First, the privilege granting section of the management server 100 encodes the introduction information to issue an introduction QR code, and sends it to the user terminal 300 of the customer (the first customer) who purchased the product (step S601). Here, the URL of the access destination specified by the QR code ID included in the introduction information is the URL used when the seller terminal 200 and the referred person terminal 300' used by the referred person access the management server 100, and includes the host name and domain name of the management server 100. Also, the introduction hierarchy includes the nesting of the referrer.

[0146] The user terminal 300 displays the sent introduction QR code (step S602). Then, when the referred person terminal 300' reads the introduction QR code, the referred person terminal 300' accesses the product site using the access URL included in the introduction QR code (step S603). Thereafter, the management server 100 performs the above-described content providing process (step S604).

[0147] Figure 20 is a diagram showing an example of the flow of product introduction and purchase processing. The product introduction and purchase processing starts after the content is provided in S604 by the same processing as the above-described product introduction processing, when the referred person terminal 300' receives a purchase request for the product (step S605).

[0148] The privilege granting section of the management server 100 that has received the purchase request issues an introduction and purchase QR code including a discount amount or discount rate, and sends it to the referred person terminal 300' of the referred person (the second customer) (step S606). Here, the introduction and purchase QR code is basically the same as the introduction QR code, but the user ID of the referred person (the second customer) is added to the user ID.

[0149] The referred terminal 300´ displays the sent QR code for introduced purchase (step S607). When the seller terminal 200 reads the QR code for introduced purchase, the seller terminal 200 (the store's cash register terminal) performs the same settlement process as steps S506 to S508 above (steps S608 to S508). At this time, for the selling price of the product, the discount rate or discount amount included in the QR code for introduced purchase is applied. Also, for example, when the referred person purchases the corresponding product on the Internet such as an EC site, by inputting the purchase QR code or URL on the EC site where the purchase is made at the time of purchase, the corresponding EC site side transmits the purchase completed information to the management server 100 and performs purchase privilege processing etc. (steps S608 to S508, S509 to S601). In this way, it can be handled by introducing the function of the seller terminal (such as a cash register) 200 to the EC site.

[0150] Also, the user account management unit 118 of the management server 100 acquires the user ID, product ID, purchase store, purchase date and time, purchase quantity, etc. of the referred person from the purchase completed information, and stores the product ID, purchase store, purchase date and time, purchase quantity, etc. in the product purchase history of the corresponding user ID in the user-specific history information 128 (step S509).

[0151] When the user account management unit 118 of the management server 100 updates the product purchase history, it performs introduced purchase privilege processing (step S609). The introduced purchase privilege processing is a process of granting a financial privilege obtained in subsequent purchases to either or both of the introducer and the referred person. Specifically, it grants a discount coupon ticket, points that can be used as product price, etc. to either or both of the introducer and the referred person. Note that the user account management unit 118 may follow the nest of the introducer and apply the same or slightly modified (varying the privilege according to the distance of the nest) purchase privilege to the introduced persons within a predetermined hierarchy (for example, three hierarchies). By doing so, it becomes possible to further increase the incentive to become an introducer.

[0152] Then, the privilege granting unit of the management server 100 encodes the introduction information, issues an introduction QR code, and sends it to the introduced person terminal 300' of the customer (the second customer) who purchased the product (step S601). By doing so, it becomes possible to recursively realize the introduction process. That is, the introduced person can become an introducer and introduce the product to a new different introduced person.

[0153] Note that the content change unit 116 may change the content data associated with the URL according to whether the accessing customer has introduced the product to any introduced person. For those who have been an introducer of the purchased product, it becomes possible to select content that is useful for appealing to others, such as including a catchphrase that simply expresses functionality, so that it can support actively introducing.

[0154] Also, the content change unit may change the content data associated with the URL according to whether the accessing customer has experience in introducing other products different from the product (for example, whether they have introduced other products purchased in the recent few months). For those with experience in being an introducer of other products, it becomes possible to select content that clearly shows the points and sales points of the introduction, so that it can support actively introducing.

[0155] Also, the content change unit may change the content data associated with the URL according to whether it has been accessed using the access identifier included in the introduction image code. Since an introduced person may have heard an overview from the introducer, it becomes possible to select content that explains the function and usage method in detail, so that it can support actively purchasing.

[0156] The above described the referral purchase process. Through the referral purchase process, in the product description support system 1 according to the fifth embodiment, a customer who has purchased a product can obtain a predetermined privilege (for example, a discount on the purchased product or a financial privilege obtained in subsequent purchases) by introducing the product to another customer (the referred customer). Also, the purchaser can newly become a referrer and introduce the product to other customers, thus realizing a chain of referrals.

[0157] Also, in the fifth embodiment, in the referral purchase process, an example was shown where the seller terminal 200 reads the referral purchase QR code and performs settlement processing such as payment. However, it is not limited to this. For example, the referred customer terminal 300´ may read the referral purchase QR code transmitted in step S606 and perform settlement processing such as payment. By doing so, the referred customer can directly make a purchase without visiting the store.

[0158] The above is the fifth embodiment. Note that for all of the above embodiments, the information shown as the access URL is an example, and it may be an identifier (access identifier) including a description format other than the URL description format. Also, the URL shown above can be handled more simply by using a shortened URL.

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

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

[0161] The above described the present invention mainly with reference to the embodiments.

Description of Reference Numerals

[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 change 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 description support system executed by a computer system including a management server, an access reception unit that receives access executed by a customer's user terminal using an access identifier included in a code pre-associated with a product, a content change unit that changes content data associated with the access identifier according to whether the customer has purchased the product, a content transmission unit that causes the changed content data to be displayed viewably on the customer's user terminal, a privilege granting unit that, when the customer who has purchased the product is used as a referrer, issues a referral code including an access identifier for the referrer to introduce the product to a referred person who is another customer, and when receiving access executed using the access identifier, grants a predetermined privilege to any one of the introduced product, the referrer, or the referred person; A product description support system characterized by comprising the above.

2. The product description support system according to claim 1, wherein the privilege granting unit issues a referral code associating at least the referrer, the access identifier, and a predetermined privilege applied at the time of purchasing the product to the user terminal of the referrer, and when receiving access executed by the referred person using the access identifier included in the referral code, issues a referral purchase code associating at least the referrer, the referred person, the access identifier, and the predetermined privilege, and grants the predetermined privilege to any one of the product purchased using the referral purchase code, the referrer, or the referred person; A product description support system characterized by the above.

3. The product description support system according to claim 1, wherein the privilege granting unit assigns an access identifier different from the access identifier assigned to the referrer to the referred person; A product description support system characterized by the above.

4. The product description support system according to claim 1, wherein the predetermined privilege is to discount the selling price of the product; A product description support system characterized by the above.

5. The product description support system according to claim 1, wherein the predetermined privilege is a predetermined financial privilege regarding subsequent purchases for either or both of the referrer and the referred person; A product description support system characterized by the above.

6. The product description support system according to claim 1, wherein when the person being introduced purchases the product, the privilege granting unit issues to the person being introduced the introduction code associating at least the person being introduced, the product, and a predetermined privilege applied at the time of purchasing the product. A product description support system characterized by the above.

7. The product description support system according to claim 1, wherein the content changing unit changes the content data associated with the access identifier according to whether the customer has introduced the product to the person being introduced. A product description support system characterized by the above.

8. The product description support system according to claim 1, wherein the content changing unit changes the content data associated with the access identifier according to whether the customer has experience in introducing another product different from the product. A product description support system characterized by the above.

9. The product description support system according to claim 1, wherein the content changing unit changes the content data associated with the access identifier according to whether access has been made using the access identifier included in the introduction code. A product description support system characterized by the above.

10. A product description support method executed by a computer system including a management server, the method comprising: an access reception procedure of receiving, by a user terminal of a customer, an access executed using an access identifier included in a code pre-associated with a product; a content change procedure of changing content data associated with the access identifier according to whether the customer has already purchased the product; a content transmission procedure of displaying the changed content data so as to be viewable on the user terminal of the customer; a privilege granting procedure of, when the customer who has purchased the product is set as an introducer, issuing to the introducer an introduction code including an access identifier for introducing the product to a person being introduced who is another customer, and granting a predetermined privilege to any one of the introduced product, the introducer, or the person being introduced when receiving an access executed using the access identifier; A product description support method characterized by implementing the above.

11. A product description support program for causing a management server to support product description, the program causing the management server to An access reception procedure for receiving an access executed using an access identifier included in a code pre-associated with a product by a customer's user terminal, A content change procedure for changing content data associated with the access identifier according to whether the customer has purchased the product, A content transmission procedure for displaying the changed content data so that it can be viewed on the customer's user terminal, A privilege granting procedure for issuing an introduction code including an access identifier for introducing the product to another customer, who is the introduced party, to the introducer, who is the customer who has purchased the product, and granting a predetermined privilege to any one of the introduced product, the introducer, or the introduced party when receiving an access executed using the access identifier, A product description support program characterized by causing the above to be executed.

Images