JP7525944B1 - How to get the giver to honor the gift - Google Patents

Abstract

[Problem] To provide a gift asset product that can be given by attaching it to some kind of tangible object, and can be given easily without being bulky for the recipient. [Solution] A gift asset product that commercializes a gift asset that can be exchanged for a product or service by the recipient operating a recipient terminal 7 to access a gift site provided by a server 4 on the Internet 1, comprises a mount 1 and a sticker 2 affixed to the mount 1, and a code symbol 3 that symbolizes access information to the gift site is printed on the sticker 2. The symbolized access information includes authentication information used in a program for exchanging the gift asset for a product or service selected by the giver on the gift site, or for the recipient to select and exchange from multiple products or services set up on the gift site. [Selected Figure] Figure 1

Description

The present invention relates to products and systems used when presenting gifts.

On special occasions such as weddings, funerals, and other celebrations, as well as to express gratitude and greetings, various gifts are purchased by the giver and presented to the recipient (recipient). Gifts can be tangible goods, but can also be some kind of service (intangible goods). In recent years, ordering (purchasing) these gifts has become more common on websites, and there are now specialized websites that deal only with gifts.

In the presentation of such gifts, rather than the gift itself, there are cases where rights (claims) that can be exchanged for goods or services are presented. A typical example of this is the so-called gift catalog. With regard to such gifts, the use of IT has also progressed, and services that provide catalog-style gifts on websites have also appeared. Also, since the exchange for exchangeable goods is carried out on a website, card-style gift catalogs that list access information to the website and an ID for the exchange are also known (Patent Document 1). In the following explanation, rights that can be exchanged for goods or services and that are presented as gifts are called gift assets, and those that are sold as goods are called gift asset goods. Furthermore, with regard to gift assets, goods or services that can be exchanged are called exchangeable goods.

A gift catalog is a set that includes a booklet (catalog) introducing the items to be exchanged, and an application form for the exchange (postcard with separate charges) attached. There are several courses to choose from for gift catalogs. A course is a selection of products or services of a certain value, for example a 3000 yen course, a 5000 yen course, or a 7000 yen course. The 3000 yen course means that you can choose from products or services worth 3000 yen. This amount is essentially the sales price of the gift catalog, but as it includes a handling fee, the value of the actual product or service exchanged will be a little less than that.

On the other hand, gift asset products in the form of casual gifts, which are not catalog gifts, are also sold. An example of this is shown in Non-Patent Document 1. This type of gift asset product can be purchased on a website by credit card payment, etc., and the purchased gift asset product can be sent to the recipient's terminal (smartphone, etc.) via SNS, email, etc. The gift asset here is a right (claim) that can be exchanged for a specific product or service selected by the giver, and what is sent to the recipient is a code for the exchange. The code is a code symbol such as a barcode, and an image of the code symbol is sent via SNS, etc. The recipient (recipient) who receives the code symbol displays the code symbol on a terminal at the store and presents it to a store clerk, who then reads the code symbol with a reader to confirm the right and provides the recipient with the product or service that is the subject of the gift.

In addition, B2C gifts are also often given. These gifts are for sales promotion or as a thank you for a purchase. Novelty items are given as a thank you to customers who inquire about products or visit showrooms.
Hereinafter, a gift asset that can be exchanged for one specific product or service will be referred to as a single-type gift asset, and a gift asset that can be selected from a plurality of products or services and exchanged, such as a catalog gift, will be referred to as a selection-type gift asset.

Patent No. 6741320

https://giftee.com/

There is a need to present these various types of gift asset products in the form of attachments to some tangible object. When giving a gift as a return gift (thank-you gift), it is often the case that a thank-you letter is attached to the gift, which can be said to be an attachment to the thank-you letter (since the main purpose of the letter is to convey gratitude).
In such a case, if you want to give the above-mentioned catalog gift as a thank you, you would have to send the thank you letter and the catalog gift (catalog booklet) to the recipient (recipient) via courier, but it would be bulky and troublesome. With a card-type catalog gift, there is no problem with the bulkiness, but if you forget to put the card in, the important gift will not arrive and it would be rude.

Casual gifts exchanged between smartphones do not have the above problems, but it cannot accommodate requests such as conveying a message in a handwritten letter or giving a gift along with some kind of tangible item.
Also, in the case of B2C gifts, for example, visitors to a showroom may be asked to take a catalog home with them, but if they are asked to take a novelty item home with them in addition to that, the items will be bulky and customers may be reluctant to take them home.

In order to solve the above problems, this specification discloses a method for making a giver give a gift and a gift asset product sales system. The disclosed method for making a giver give a gift is a method for making a giver give a gift by having a recipient access a gift site provided by a server on a network using a recipient's terminal to give a gift asset that is a commercialized gift asset that can be exchanged for a product or service.
The gift assets are exchanged for a single product or service selected by the giver on the gift site, or for a product or service selected by the recipient from among multiple products or services set out on the gift site.
The method according to the disclosed invention comprises:
A process of creating an image file for printing;
Seal printing process
have.
The print image file creation step is a step in which the program creates a print image file including a code symbol that symbolizes access information to the gift site.
The sticker printing process is a process for producing a gift asset product consisting of a mount and a sticker affixed to the mount, by printing an image file for printing on an unprinted sticker with a printer, resulting in an image including the code symbol being printed on the sticker affixed to the mount.
The symbolized access information includes authentication information used in a program to allow the giver to exchange the gift for one product or service selected on the gift site, or for the recipient to select and exchange from among multiple products or services set up on the gift site.
In this method, the sticker printed with an image including a code symbol has adhesiveness that allows it to be peeled off the mount and reattached to another object, and the giver who is provided with the sticker attached to the mount reattaches the sticker to another object and hands the other object over to the recipient, thereby presenting the sticker as a gift.
In addition, in order to solve the above problem, the disclosed invention relates to a method of having a gift presented to a giver , in which an exchange deadline date is set for the exchange, and the exchange deadline date is printed on the sticker in addition to the code symbol.
In addition, in order to solve the above problem, the disclosed invention relates to a method of having a giver give a gift , which is a gift asset product in which a single giver gives gift assets to multiple recipients, and in which the stickers are affixed to a backing sheet in the number equal to the number of recipients, and the code symbol printed on each sticker includes an asset ID that identifies each gift asset in the authentication information.
In the method for allowing a giver to give a gift having the above configuration, the name of the recipient may be printed on each sticker.
In order to solve the above problem, in the method for allowing a giver to present a gift according to the disclosed invention , the code symbol may be a two-dimensional code symbol.
In order to solve the above problems, this specification discloses a gift presentation system. The gift presentation system according to the disclosed invention is a system including a server that is accessed by access information included in a code symbol printed on a sticker in the method of the disclosed invention for allowing a gift giver to give a gift .
This gift presentation system has a configuration in which a code symbol is read on a recipient terminal operated by the recipient, a program is executed, and when a request for exchange for a product or service is sent from the recipient terminal, an exchange request acceptance program is implemented on a server which receives the request and enables the recipient to acquire the product or service.

In order to solve the above problems, this specification discloses a method for making a giver give a gift and a gift asset product sales system. The disclosed method for making a giver give a gift is a method for making a giver give a gift by having the giver operate a gift site provided by a server on a network to access the gift asset, which is exchangeable for a product or service, and exchanging the gift asset for a product or service by having the giver access the gift site using the giver's terminal.
The gift assets are exchanged for a single product or service selected by the giver on the gift site, or for a product or service selected by the recipient from among multiple products or services set out on the gift site.
The method according to the disclosed invention comprises:
A process of creating an image file for printing;
and a seal printing process.
The print image file creation step is a step in which a computer executes a creation program to create a print image file including a code symbol that symbolizes access information to the gift site.
The sticker printing process is a process for producing a gift asset product consisting of a mount and a sticker affixed to the mount, by printing an image file for printing on an unprinted sticker with a printer, resulting in an image including the code symbol being printed on the sticker affixed to the mount.
The symbolized access information includes authentication information used in a login program when the gift recipient's terminal logs in to the gift site to exchange the gift for one product or service selected by the giver on the gift site , or for the gift recipient to select and exchange from a plurality of products or services set on the gift site .
In this method, the sticker printed with an image including a code symbol has adhesive properties that enable it to be peeled off from the backing and reattached to another object, and the giver who is provided with the sticker attached to the backing reattaches the sticker to another object and hands the other object to the recipient, who then operates the recipient's terminal to read the code symbol on the reattached sticker and accesses the gift site on the server, thereby exchanging the one product or service for the gift asset, or exchanging the gift asset for a product or service selected by the recipient from the multiple products or services, thereby allowing the giver to gift the gift.
In addition, in order to solve the above problem, the disclosed invention relates to a method for allowing a gift to be presented to a giver , and the method may be configured such that an exchange deadline date is set for the exchange, and the exchange deadline date is printed on the sticker in addition to the code symbol.
In addition, in order to solve the above problem, the disclosed invention relates to a method of having a giver give a gift, which is a gift asset product in which a single giver gives gift assets to multiple recipients, and in which the stickers are affixed to a backing sheet in the number equal to the number of recipients, and the code symbol printed on each sticker includes an asset ID that identifies each gift asset in the authentication information.
In the method for allowing a giver to give a gift having the above configuration, the name of the recipient may be printed on each sticker.
In order to solve the above problem, in the method of allowing a giver to present a gift according to the disclosed invention, the code symbol may be a two-dimensional code symbol.
In order to solve the above problems, this specification discloses a gift-presenting system. The gift-presenting system according to the disclosed invention is a system including a server that is accessed by access information included in a code symbol printed on a sticker in the method for allowing a gift giver to give a gift according to the disclosed invention.
This gift presentation system has a configuration in which a code symbol is read on a recipient terminal operated by the recipient, a program is executed, and when a request for exchange for a product or service is sent from the recipient terminal, an exchange request acceptance program is implemented on a server which receives the request and enables the recipient to acquire the product or service.

As described below, according to the disclosed gift asset product or gift presentation system, a gift asset can be presented to a recipient by simply attaching a sticker to some object and handing it to the recipient, and the giver does not need to prepare a gift item. This makes it extremely easy to present a gift.
In addition, in the case where the gift recipient selects and acquires a product or service set on the gift site, the giver does not need to think about what kind of gift to prepare, which makes gift giving even easier.
In addition, if a deadline is set for exchange, the recipient can be prevented from missing the deadline by printing the exchange deadline on the sticker.
In addition, a configuration in which stickers are attached to the backing sheet in the number of recipients and the code symbol printed on each sticker contains an asset ID that identifies each gift asset makes it suitable for presenting exchangeable items to multiple recipients at the same time.
In the above configuration, the name of the recipient is printed on each sticker, which is effective in ensuring that the gift assets are presented to the recipient without error, and is particularly suitable when different gift assets are presented to one recipient and another recipient.

FIG. 2 is a schematic diagram of a gift asset product according to an embodiment. 1 is a schematic diagram of a gift presentation system according to an embodiment; FIG. 2 is a schematic diagram showing an example of a top page of a gift site provided by a gift server. FIG. 13 is a schematic diagram showing an example of an introduction page for a sticker-type gift asset product. FIG. 13 is a schematic diagram showing an example of a purchase page. FIG. 2 is a schematic diagram showing an example of a structure of a sales information file. FIG. 2 is a schematic diagram showing an example of a structure of an asset information file. FIG. 13 is a schematic diagram showing the contents of a template file. 2 is a schematic diagram showing the state in which the two-dimensional code symbol printed on the sticker of the sticker-type gift asset product shown in FIG. 1 is executed on the recipient terminal. FIG. 13 is a schematic diagram showing an example of a replaceable item introduction page.

Next, a description will be given of a mode (embodiment) for carrying out the present invention. The following description includes a description of an embodiment of the invention of a method for allowing a gift giver to give a gift, as well as a description of an embodiment of the invention of a gift asset product. Figure 1 is a schematic diagram of the gift asset product according to the embodiment.
The gift asset product of the embodiment is a commercialized gift asset that can be exchanged for a product or service by the recipient operating the recipient's terminal to access a gift site provided by a server on a network after being presented by the giver. The server is for accepting access for selling the gift asset product or exchanging it for an exchangeable item, and is hereinafter referred to as a gift server. Note that an Internet is assumed as the network.

As shown in Fig. 1, this gift asset product has a mount 1 and a sticker 2 affixed to the mount 1. Hereinafter, the sheet consisting of the mount 1 and the sticker 2 affixed to the mount 1 will be referred to as a gift sheet 10. The gift asset product is in a form in which the gift sheet 10 is placed in a packaging bag 11. An instruction manual (not shown) may be enclosed in the packaging bag 11.
A code symbol 3, which is a symbol of access information to a gift server, is printed on the sticker 2 of the gift sheet 10. In this embodiment, the code symbol 3 is a two-dimensional code symbol such as a QR code (a registered trademark of Denso Wave Inc.).

The configuration of the code symbol 3 printed on the sticker 2 is shown in a speech bubble in FIG. 1. The code symbol 3 contains authentication information used in the program for exchange with the exchanged item. As shown in FIG. 1, the access information symbolized in the code symbol 3 in this example contains a URL 31 consisting of the computer name or domain name given to the gift server, and an execution code 32 of the program on the gift server. In addition to the program name, the execution code 32 contains an ID and a password as arguments. In this embodiment, the code symbol 3 contains two types of IDs, one is a sales ID and the other is an asset ID. These IDs and passwords correspond to the authentication information in this example. Each ID will be described later.

In this embodiment, a plurality of stickers 2 are attached to a single mount 1. The code symbols 3 in each sticker 2 are the same (common) except for the arguments included in the execution code 32. Among the IDs as arguments, the sales ID is the same in each sticker 2, but the asset ID and password are different in each sticker 2.
The execution code 32 included in the code symbol 3 is an execution code for a program that logs in to the gift server and displays a top page for requesting an exchange for an item to be exchanged (hereinafter referred to as the exchange top page).

As shown in Fig. 1, each sticker 2 has a portion on which text information relating to the gift asset is printed (hereinafter, the text information printed portion). In this example, the text information printed portion is a deadline printed portion 21 on which an exchange deadline is printed. In this embodiment, exchange with an exchangeable item is subject to a deadline, and exchange is not possible after the deadline has passed. The deadline printed portion 21 is the portion on which the exchange deadline is printed.
A description of the gift asset product and information about the sales company (gift vendor) are printed on the mount 1. The description of the gift asset product includes how to use the sticker 2 and how to exchange it for an exchangeable item. If there is a large amount of information, it is printed on the back side of the mount 1 (the side opposite to the side on which the sticker 2 is affixed).

Next, an embodiment of the gift presentation system will be described. Figure 2 is a schematic diagram of the gift presentation system according to the embodiment.
The invention of the gift presentation system is a system used when selling the above-mentioned gift asset products or exchanging them for exchangeable goods. Therefore, the gift presentation system can be configured as a system for selling gift asset products, and can also be configured as a system for exchanging gift asset products for exchangeable goods. The embodiment of the gift presentation system described below has both of these functions. However, the invention of the gift presentation system may be a system that has only one of the functions. The invention of the gift asset sales system can be understood as a system for manufacturing gift asset products.

As shown in Fig. 2, the gift presentation system includes a gift server 4 and a memory unit 40. The gift server 4 is a server that accepts applications for selling gift asset products and exchanging them for exchangeable items over the Internet 9, and is a web server. The gift server 4 is operated by a business operator (hereinafter referred to as a gift business operator) that operates a gift service business including selling gift asset products and exchanging them for exchangeable items. Note that the gift server 4 does not need to be a single server, and the gift server 4 may be configured by multiple server computers.
The memory unit 40 is a storage such as a hard disk provided in the gift server 4, but may be provided in a server other than the gift server 4, such as a storage server. The memory unit 40 does not need to be only one, and multiple storages may be used as the memory unit 40, and may be provided in different locations.

First, the function of the gift server 4 for selling gift asset products will be described.
The gift business sells various products (gift products) that are given as gifts, including the gift asset product of the embodiment. The gift business provides a website for selling various gift products on a gift server 4. As shown in Fig. 2, the gift server 4 is assumed to be accessed by a gift giver terminal 5 operated by a gift giver who is about to purchase a gift product. Thus, each page of the gift site is displayed on the gift giver terminal 5 by the browser of the gift giver terminal 5.
In addition, booklet-type catalog gifts and card-type catalog gifts are also gift products that are assets to be exchanged for exchanged items, and therefore are also gift asset products. Since gift businesses also sell these gift asset products, the gift asset product of the embodiment will be referred to as a sticker-type gift asset product below for the sake of distinction.

Figure 3 is a schematic diagram showing an example of the top page of a gift site provided by the gift server 4. Although Figure 3 shows a page for a PC version, it can of course be a page for a smartphone version. As shown in Figure 3, the top page has link buttons to pages introducing various gift products. Some of these are link buttons (hereinafter, sticker type product buttons) 51, 52 to pages introducing sticker type gift asset products. This gift site has sticker type product button 51 for sticker type gift asset products that are sticker type catalog gifts, and sticker type product button 52 for sticker type gift asset products that are not catalog gifts but that the giver selects an exchangeable item to give as a gift. In the following explanation, a sticker type gift asset product that is sticker type catalog gifts will be explained as an example.

Fig. 4 is a schematic diagram showing an example of an introduction page for sticker-type gift asset products (hereinafter, sticker-type product page). When the sticker-type product button 51 shown in Fig. 3 is clicked or tapped, the sticker-type product page shown in Fig. 4 is displayed on the gift giver terminal 5. As shown in Fig. 4, the sticker-type product page contains text explaining the sticker-type gift asset products, the price of each sticker-type gift asset product, actual photos (sample stickers), etc.
In the example of Fig. 4, several sticker-type gift asset products with different prices are listed. In addition, sticker-type gift asset products with the same price but different lineups of exchangeable items (groups of exchangeable products or services) may be sold on the gift site. Next to the price of each sticker-type gift asset product, a button 53 for viewing exchangeable items entitled "View exchangeable items" is provided. The button 53 for viewing exchangeable items is linked to a page for viewing exchangeable items.

The Exchangeable Item Viewing Page is a page that introduces the products and services that the recipient can obtain with the selected sticker-type gift asset product. The Exchangeable Item Viewing Page displays a list of frames introducing each exchangeable product and service, and each list includes a photo of the product or service. In the case of a service, a photo of the service being provided or a photo of the ticket for receiving the service is displayed. The Exchangeable Item Viewing Page has a field for selecting a genre, and may be implemented to introduce exchangeable items for each selected genre.

The memory unit 40 stores an exchangeable item information file (not shown) that records information on exchangeable items for each sticker-type gift asset product. Therefore, in this embodiment, being recorded in a file stored in the memory unit 40 corresponds to "being set on the gift site." In addition, a group of exchangeable items may be selected by some program on the gift server 4, and the conditions for this selection may be set. The conditions may be constants (predetermined conditions) in the program, or they may be conditions selected by the giver by inputting them into the giver terminal 5.

Next to each exchange item viewing button 53, a selection button 54 labeled "Select" is provided. The selection buttons 54 are link buttons to a purchase page for the selected sticker-type gift asset product. When any of the selection buttons 54 is pressed, the product ID of the selected sticker-type gift asset product is stored in a variable, and the purchase page is displayed on the gift giver terminal 5.
Fig. 5 is a schematic diagram showing an example of a purchase page. As shown in Fig. 5, the purchase page has a field displaying the price of the selected sticker-type gift asset product, as well as a field 555 for inputting the number of recipients and a purchase button 56. The purchase button 56 is linked to a settlement page. Also, as shown in Fig. 5, the purchase page has a redemption viewing button 53.

The number of recipients input field 55 is a field for inputting information on how many recipients can obtain exchange items for the purchased sticker-type gift asset product. In other words, this is a field for inputting information on how many gift assets are included in one purchase of the sticker-type gift asset product.
The displayed price of the sticker-type gift asset product is the price per recipient of that sticker-type gift asset consumable product. In other words, it is the price (unit price) of one gift asset of that sticker-type gift asset product. Therefore, the amount actually paid by the giver is the displayed price (unit price) x the number entered in the number of recipients input field 55. The price of one gift asset may include the gift business operator's commission (so-called system commission). However, the system commission may be set at one system commission for one sale.

The storage unit 40 stores HTML files (not shown) for providing such top page, sticker-type product page, purchase page, etc. to the gift sender terminal 5. In response to a request from the gift sender terminal 5, the gift server 4 transmits each page to the gift sender terminal 5 for display.
The payment page linked to the purchase button 56 includes a field for inputting the sender's personal information such as the name and address (recipient), a field for selecting the payment method (credit card payment, cash on delivery, convenience store payment, etc.), and a payment button for confirming the purchase. The payment button is an execution button for a payment program (not shown). These configurations can be configured in the same way as a normal online shopping site (EC site), so a detailed description will be omitted.

A sales information registration program 41 is implemented in the gift server 4 as a program called from the payment program. The storage unit 40 also stores a sales information file 401 that records sales information of sticker-type gift asset products.
Fig. 6 is a schematic diagram showing an example of the structure of the sales information file 401. As shown in Fig. 6, the sales information file 401 is a database file consisting of fields such as "Sales ID", "Product ID", "Number of recipients", "Sales date", "Member ID", "Name", "Address", "Sticker printing completed or not", etc. However, as long as this information can be recorded, it does not have to be a database file.

"Sales ID" is a field in which an ID for identifying each sale of a sticker-type gift asset product is recorded. One sales ID is issued and recorded for each sale of a sticker-type gift asset product.
The gift site sells several sticker-type gift asset products with different prices and exchangeable item lineups, and the "product ID" is a field in which IDs for identifying them are recorded. The storage unit 40 stores a sticker-type gift asset product information file 402 that records information on each sticker-type gift asset product. The sticker-type gift asset product information file 402 is a database file made up of records that are uniquely identified by product IDs, and the product IDs here and the product IDs in the sales information file 401 are common and associated with each other.
The sticker-type gift asset product information file 402 has a "price" field. The price recorded here is the price displayed on the purchase page, etc., and is the price per recipient.

In this embodiment, the gift site invites gift givers and gift recipients to register as members. Although gift items can be purchased and exchanged for exchange items without registering as a member, various benefits are given to those who register as a member, and so member registration is encouraged. The memory unit 40 stores a member information file 403 that records member registration information. Although not shown in the figure, the member information file 403 is a database file that records personal information such as the member ID, name, address, telephone number, and email address. The "member ID" in the sales information file 401 is the same as that in the member information file and is associated with it.

When the payment program completes normally, it calls and executes the sales information registration program 41. The sales information registration program 41 generates a new sales ID and adds a new record to the sales information file 401, recording the generated sales ID, the product ID of the selected sticker-type gift asset product, and the input number of recipients in the respective fields. If the payment is made while logged in to the gift site, the member ID held at the time of login is recorded in "member ID". If not logged in, the name, address, etc. input on the payment page are recorded in the respective fields. The program also records the execution date of the program in "sales date".
The "Sticker Printing Completed" field is a field in which whether or not the sticker printing for the production of the gift asset product is completed is recorded, and the default value is a false value. As will be described later, sticker printing is performed by the management terminal using a printer, and when this is completed, a true value is recorded in the "Sticker Printing Completed" field.

The sales information registration program 41 is programmed to perform a process of creating a new asset information file 404 and storing it in the storage unit 40 after recording each piece of information in the sales information file 401. Fig. 7 is a schematic diagram showing an example of the structure of the asset information file 404.
The asset information file 404 is a file created for each sales ID, and is given a file name that can be specified by the sales ID. For example, the file name may be made up of the sales ID and an identifier.
7, the asset information file 404 is a database file consisting of fields such as "asset ID", "password", "exchange deadline date", "exchange date", etc. The "asset ID" is a field in which an ID that identifies each record in the asset information file 404 is recorded.

"Password" is a field in which information serving as an encryption key corresponding to the asset ID is recorded, and information generated in advance to prevent unauthorized access is recorded.
The number of records in the asset information file 404 is set to the number of recipients in the sale to which the corresponding sales ID is assigned. The asset ID is an ID generated by, for example, assigning a branch number to the sales ID. If the branch number starts with 1, the number of the last branch number is equal to the number of recipients.
The "exchange deadline" is a field in which the date by which the gift asset can be exchanged with the exchanged item is recorded. The exchange deadline is set to a uniform deadline, for example, six months from the date of sale.
The "Exchange Date" is a field in which the date on which the recipient applied for an exchange of the gift asset and the shipment of the exchanged item was completed is recorded. The record (gift asset) on which the exchange date is recorded is considered to have been exercised as a claim, so the asset value is zero.

After creating a new asset information file 404, the sales information registration program 41 adds records for the number of recipients, sequentially generates asset IDs and records them in the "asset ID" of each record. It also sequentially generates passwords corresponding to each asset ID and records them in the "password". It then records a certain deadline from the date of sale in the "exchange deadline date" of each record. It then updates the file, stores it in the storage unit 40, and terminates the program.

The gift sales system equipped with such a gift server 4 and memory unit 40 includes a sticker printing means as an element that cooperates with the sales information file 401 stored in the memory unit 40. The sticker printing means is composed of a printer 61 that prints stickers, and a print command output unit that outputs a print command to the printer 61.

Although there are several possible configurations for the print command output unit, in this embodiment, a computer that can access the memory unit 40 serves as the print command output unit. More specifically, in this embodiment, a management terminal 62 that has special access authority to the gift server 4 and the memory unit 40 is provided.
The management terminal 62 is a terminal operated by a person in charge of the gift business. The printing machine 61 is connected to the management terminal 62, and serves as a peripheral device for the management terminal 62 or is connected via an internal network of the gift business.

The management terminal 62 is equipped with a sticker printing program 63 that creates and prints an image file for sticker printing according to the sales information file 401 and the corresponding asset information file 404. The sticker printing program 63 is a program that is executed using a sales ID as an argument, and includes code for creating an image file for printing and code for outputting a print of the created image file to the printer 61.
For example, an application program (not shown) for viewing the sales information file 401 is installed in the management terminal 62. This application program is programmed so that the viewing screen includes an execution button for executing the sticker printing program 63 using the sales ID of a record whose "sticker printing completion status" is a false value as an argument.

A template file 64 that is the basis of a print image file is stored in the storage unit of the management terminal 62. Fig. 8 is a schematic diagram showing the contents of the template file.
The template file 64 is a file in which printing information (such as a description of the gift asset product and information on the gift vendor) other than the printing information for each sticker 2 in the gift asset product shown in Fig. 1 is pre-installed. For the sake of convenience, hereinafter, the unprinted sheets fed into the printer 61 will be referred to as "sheet material." The sheet material consists of a mount 1 and a predetermined number of unprinted stickers affixed to the mount 1.

The template file 64 sets the size of the mount 1 for the gift asset product shown in FIG. 1, the attachment positions of each unprinted sticker, and the size of the unprinted sticker. In FIG. 8, the attachment positions are indicated by x's, and the size of the unprinted sticker is indicated by a dashed circle. In this example, three attachment positions are set horizontally, and four attachment positions are set vertically. Therefore, this example assumes that a sheet material with a total of 12 unprinted stickers attached will be used.

When the sticker printing program 63 is started, it first opens the template file 64. It then accesses the gift server 4 and opens the asset information file 404 corresponding to the argument sales ID. It then obtains the asset ID, password, and exchange deadline date of the first record, and generates an image of the code symbol 3. The URL of the gift server 4 is given to the sticker printing program 63 as a constant. The sticker printing program 63 creates access information by combining constants with the asset ID and password obtained from the sales ID and the first record of the asset information file 404, and converts this into a two-dimensional image code to create an image of the code symbol 3 (hereinafter referred to as the symbol image). The symbol image is temporarily stored in a variable.

Next, the sticker printing program 63 prepares print data for the text information printing section. In this embodiment, the text information printing section is the expiration date printing section 21, so the replacement expiration date as a variable and the "replacement expiration date" as text (constant) are combined into image data to create an image for the expiration date printing section 21. Then, an image file (hereinafter, sticker-unit image file) is created that incorporates these and is printed on one sticker 2. The created sticker-unit image file is then incorporated into the initial attachment position of the template file 64. That is, according to the size of the mount 1 set in the template file 64, the sticker-unit image file is incorporated into the coordinates of the attachment position at the left end of the top row.

The sticker printing program 63 then obtains the asset ID and password from the next record in the asset information file 404, and similarly combines the sales ID with a constant to generate access information. This is then converted into a code symbol to create a symbol image, which is then incorporated together with the image for the expiration date printing unit 21 to create a sticker-unit image file. The image for the expiration date printing unit 21 may be created by obtaining the replacement expiration date from the record, but as this is the same as for the first asset ID, it may also be stored in a variable and read out from there and incorporated. The sticker printing program 63 incorporates the created sticker-unit image file into the next pasting position. For example, it may be incorporated into the position immediately to the right of the first pasting position.

In this way, the sticker printing program 63 obtains the asset ID and password from each record in the asset information file 404, combines the sales ID with a constant to generate access information and convert it into a code symbol, combines this image with an image for the expiration date printing unit 21, and incorporates the created sticker unit image file into each attachment position. When processing has been completed for all records in the asset information file 404, the incorporation of the image of the code symbol 3 for one sales ID is complete, and the print image file is complete. The sticker printing program 63 temporarily saves the print image file under a file name different from the template file 64, and then outputs the print image file to the printer 61 and instructs it to print. As a result, the stickers are printed as shown in FIG. 1.

In this example, a sheet material with 12 unprinted stickers attached to one mount 1 is used, so if the number of records (number of recipients) in the asset information file 404 is less than 12, stickers that remain unprinted (unprinted stickers) will be produced. If the number of records exceeds 12, the sticker printing program 63 is programmed to print on the unprinted stickers attached to the second mount 1 from the 13th record onwards. That is, for the 13th and subsequent records, a new template file 64 is opened, and a code symbol is generated by combining the asset ID and password with a constant in the same manner while giving the file a different name from the first one, and the image file is incorporated into each attachment position. Then, after processing the last record in the asset information file 404, the completed print image file is temporarily saved and then output to the printer 61 for printing. If the number of records exceeds 24 and printing material from the third sheet onwards is required, this process is repeated.

After processing one sales ID in this way (manufacturing one sticker-type gift asset product), the sticker printing program 63 changes the value of the "Sticker printing completed or not" field of the corresponding record in the sales information file 401 to a true value. It then checks the value of the "Sticker printing completed or not" field of the next record, and if it is false, it obtains the sales ID, opens the corresponding asset information file 404, and repeats the same process. When this process has been performed up to the last record in the sales information file 401, the sticker printing program 63 ends.

The print command output unit may be configured as described above by providing a management terminal 62 with access rights in the memory unit 40, or the gift server 4 may be responsible for this configuration. Specifically, the printer 61 is provided within the gift business operator's company, but has network capabilities and is connected to the gift server 4 via the Internet 9, and is in a state where it can accept control from the gift server 4. A sticker printing program 63 is implemented in the gift server 4 as a program that is called from the sales information registration program 41 or executed by a command from the management terminal 62. In this case, a template file 64 is pre-stored in the memory unit 40.

For example, the sales information registration program 41 records each piece of information in the sales information file 401 as described above, creates the asset information file 404, records each piece of information in records for the number of recipients, and then executes the sticker printing program 63. The sticker printing program 63 similarly opens the template file 64, reads the asset ID and password for each record in the asset information file 404, creates a code symbol 3, and incorporates the files of each code symbol 3 to create an image file for printing. The image file for printing is then sent to the printer 61 along with a print command to cause printing.

In addition, in a different configuration, the printer 61 may not be located in the gift business company. For example, sticker printing may be outsourced to another company (printing company). In this case, the printer 61 may be configured to receive control from the gift server 4, or a print command output unit may be installed in the printing company. That is, the printing company may have a computer for controlling the printer 61, and the image file for printing may be input thereto. In this case, the image file for printing is created as described above on the management terminal 62 of the gift business company and provided to the printing company in the form of email transmission, cloud sharing, or the like. Alternatively, the template file 64 and the program for creating the image file for printing may be stored in the memory unit on the computer for controlling the printer 61, and the image file for printing may be created on the computer for controlling the printer 61. In this case, the computer for controlling the printer 61 is given access rights to the sales information file 401 and the asset information file 404 on the memory unit 40.

The finished product sheet 10, with stickers printed on the sheet material in this way, is then placed in an appropriate packaging bag 11 to complete a sticker-type gift asset product. For example, the product sheet 11 is placed in a transparent packaging bag 10, instructions, etc. are attached as necessary, and the bag is sealed to complete a sticker-type gift asset product. The completed sticker-type gift asset product is delivered to the giver by courier service, mail, etc.

Next, a configuration for exchanging such a sticker-type gift asset product with an exchangeable item regarding the gift asset will be described.
Fig. 9 is a schematic diagram showing a state where the code symbol 3 printed on the sticker 2 of the sticker-type gift asset product shown in Fig. 1 is executed on the recipient terminal. In the example of Fig. 9, the recipient terminal 7 is a smartphone, and the code symbol 3 is read and executed by the smartphone, but it is also possible that the code symbol 3 is read and executed by a camera on a desktop PC or a notebook PC.

As mentioned above, the gift site includes an area for exchanging gift assets with exchangeable goods, and the gift server 4 is also a server that hosts each page of this area. The code symbol 3 is a symbolized code that displays the top page of the area for exchanging exchangeable goods (hereinafter, abbreviated as exchange top) in a logged-in state. That is, as mentioned above, the code symbol 3 includes an execution code 32 of a login program with a sales ID, asset ID, and password as arguments. The login program searches the sales information file 401 with the sales ID to confirm that there is a record in which the sales ID is recorded, then opens the asset information file 404 corresponding to the sales ID, searches with the asset ID, and determines whether the "password" value of the corresponding record matches the password of the argument. If they match, the program is programmed to permit login, store the sales ID and asset ID in session variables, and then send the HTML file of the exchange top to the recipient terminal 7 to display it.

As shown in Fig. 9, the exchange top page displays the sales ID, giver, and exchange deadline for confirmation. The script included in the exchange top HTML file is coded to search the sales information file 401 with the sales ID stored at the time of login, obtain the giver's name from the corresponding record, and obtain the exchange deadline from the corresponding record in the asset information file 404, and display each of them. The exchange deadline is temporarily stored in a variable.
The exchange top page is provided with an exchangeable item introduction button 71 labeled "View exchangeable items." An HTML file of an exchangeable item introduction page is stored in the memory unit 40. The exchangeable item introduction button 71 is linked to the exchangeable item introduction page. Figure 10 is a schematic diagram showing an example of the exchangeable item introduction page.

10, in the exchangeable item introduction page, a photo of each exchangeable item, name, and other text are embedded in a column (frame) introducing each exchangeable item. Each column is a hyperlink, and the exchangeable item ID is embedded and linked to a delivery destination input page. When any column is tapped or clicked, the delivery destination input page is sent to the recipient terminal 7 and displayed with the embedded exchangeable item ID held as a variable. The delivery destination input page has a column for inputting the name and address of the delivery destination of the exchangeable item, and has an OK button. The OK button is linked to a confirmation page. The confirmation page is a page that displays the selected exchangeable item for confirmation and displays the input delivery destination for confirmation (not shown). The gift server 4 is implemented with an exchange application acceptance program 12. The confirmation page has a send button for confirming the exchange application, and the send button is an execution button for the exchange application acceptance program 12.

The exchange application acceptance program 12 is a program that is executed with the sales ID, asset ID, exchanged item ID, and each piece of information entered on the delivery destination input page as arguments. The exchange application acceptance program 12 obtains the exchange deadline date from the variables and checks whether the program execution date is past the exchange deadline date. If it has passed, it sends a message to the recipient terminal 7 to the effect that the deadline has passed and the exchange is not possible, and ends the program. If it has not passed, the exchange application acceptance program 12 searches the asset information file 404 by asset ID and determines whether a value (date) is recorded in the "exchange date" of the corresponding record. If it has been recorded, it sends a message to the recipient terminal 7 to the effect that the exchange has already been made and further exchange applications are not possible, and ends the program.
If the exchange deadline has not passed and an exchange date has not been recorded, the exchange application acceptance program 12 executes a delivery information output module that outputs information for shipping the exchanged product, records the execution date of the program in the "exchange date" of the record, and terminates the program.

The memory unit 40 stores a delivery information file 405 for the delivery of each exchanged item. The delivery information file 405 is a database file that records the exchanged item ID of the exchanged item selected on the exchange application page and the delivery destination information (name, address, etc.) entered on the delivery destination input page, and each piece of information is recorded by the delivery information output module. The exchanged item is delivered by the gift business in accordance with the delivery information file 405. The gift business purchases the exchanged item from another business (in the case of a service, they purchase a voucher for the service, etc.), but the item may also be sent directly from the other business to the recipient.

The method of using the sticker-type gift asset product and the operation of the gift presentation system according to the embodiment of the present invention will be described below. The following description includes a description of an embodiment of the invention of a method of manufacturing a sticker-type gift asset product.
The giver wants to give a gift to the recipient and browses the gift site on the giver terminal 5. He then finds that there is a sticker-type gift asset product, and thinking that this is a good idea since it allows gift assets to be given in the simple method of sticking a sticker on the gift, he presses the sticker-type product button 51 to display the sticker-type product page on the giver terminal 5. The giver presses the exchangeable item view button 53 to check the lineup of exchangeable items, and then, taking into consideration the price (budget), selects one sticker-type gift asset product and presses the selection button 54 to display the purchase page.

The giver enters the number of recipients (number of gift assets) in the number of recipients input field 55 and presses the purchase button 56. Then, confirming the payment amount displayed on the payment page, they enter personal information such as their name, address (recipient) and email address, select the payment method, and press the payment button to make the payment. Note that if the giver is a registered member on the gift site, their name and address will be automatically displayed as their registered member information, so there is no need to enter them unless there have been changes. Once the payment has been completed, a message to that effect is displayed and a confirmation email is sent.

On the other hand, when payment is completed, the payment program calls up the sales information registration program 41 on the gift server 4 to execute. The sales information registration program 41 opens the sales information file 401 on the storage unit 40, adds a new record, and generates and records a sales ID. It also records in each field the personal information entered on the payment page, the product ID held when the purchase page was displayed, the number of recipients entered on the purchase page, etc. The program also records the execution date of the program as the sale date.

Then, the sales information registration program 41 creates a new asset information file 404 with a file name that can be specified by the sales ID, and adds new records for the number of recipients. It then generates asset IDs and passwords for the number of recipients, and records them in each record. It also records a date a certain period of time after the program execution date (for example, six months later) in the "exchange deadline date" of each record.

In this way, the giver uses the giver terminal 5 to carry out the purchase procedure for the sticker-type gift asset product on the gift server 4. The gift server 4 accepts purchase procedures from multiple givers, sales information for each giver is recorded in the sales information file 401, and an asset information file 404 is created for each sale to record information on each gift asset in each sale.

Meanwhile, the person in charge at the gift business operates the management terminal 62 to access the memory unit 40 periodically (for example, once a business day) and check the contents of the sales information file 401. Then, after setting the sheet material in the printer 61 in advance, the person in charge checks the value of the "Whether sticker printing is completed" field, and executes the sticker printing program 63 on the management terminal 62 for the sales ID for which the value is confirmed to be a false value. For example, after confirming that "Whether sticker printing is completed" is a false value on the viewing screen of the sales information file 401, the person in charge presses the execute button for the sticker printing program 63. This causes the sticker printing program 63 to be executed with the sales ID of the record in question as an argument.

After opening the template file 64, the sticker printing program 63 opens the asset information file 404 corresponding to the sales ID passed as an argument, generates an image file of the code symbol 3 and an image of the text information printing section for each record, and combines them to create a sticker-unit image file. Each sticker-unit image file is incorporated into the attachment position set in the template file 64, and a print image file is created. The sticker printing program 63 then sends the print image file to the printer 61 along with a print command to print. This results in a gift sheet 10 with the code symbol 3 and text information printing section printed on each sticker 2. Printing is performed on the second and subsequent sheet materials depending on the number of recipients, and multiple gift sheets 10 are obtained.

The person in charge places one or more gift sheets 10 in a packaging bag 11, encloses an instruction manual as necessary, and completes the sticker-type gift asset product. The completed sticker-type gift product is then sent by courier or mail to the name and address recorded in the sales information file 401 (or the member information file).
A giver who receives the sticker type gift asset product peels off the sticker 2 from the mount 1, sticks the sticker 2 on an arbitrary object, and hands the object over to the recipient to present the gift asset to the recipient.

The recipient operates the recipient terminal 7 to read the code symbol 3 on the seal 2 and access the gift site. Then, on the exchange top page displayed on the recipient terminal 7, the recipient presses the exchange item introduction button 71 to display the exchange item introduction page. The recipient then selects any exchange item and displays the delivery destination input page. On the delivery destination input page, the recipient enters the name, address, etc., presses the OK button, and on the confirmation page, presses the send button. This executes the exchange application acceptance program 12, which executes the delivery information output module, and records the program execution date in the "exchange date" of the record in the asset information file 404. The person in charge at the gift business follows the delivery information output by the delivery information output module to pack the exchange item and send it to the recipient by courier or mail, and the recipient receives the exchange item. This completes the presentation of the gift (exchange item) using the sticker-type gift asset product.

To explain a more specific gift-giving situation, a person receives something and in return gives a gift asset along with a thank-you letter. After writing the thank-you letter, the person attaches sticker 2 to the letter and mails it. The thank-you letter states that the gift can be obtained from the gift site by reading code symbol 3 with a smartphone.
According to the sticker-type gift asset product of the embodiment, there is no need to take the time to prepare a gift, and since the recipient can choose and acquire the gift at will on the gift site, the giver does not need to think about what gift to prepare. Therefore, it is possible to give a gift in return very easily.

The sticker-type gift asset product of the embodiment is also extremely well-suited for presenting gifts to multiple recipients at once. That is, stickers 2 with printed code symbols 3 are printed for each recipient, and gifts can be presented simply by attaching each sticker 3 to an object and handing it to each recipient. There is no need to purchase and prepare gifts for each recipient; a single purchase of the sticker-type gift asset product can be made on the gift site. This makes it easy to present gifts to a large number of recipients.

The sticker-type gift asset product of the embodiment is also suitable for use in ceremonial occasions. For example, it is suitable for use in presenting gifts to guests at a wedding reception. In this case, sticker 2 is affixed to, for example, the place cards given to each guest. After the reception, each guest operates the recipient terminal 7 to read the code symbol 3, accesses the gift site, and receives the exchanged item (gift). In the case of mourning events such as funerals and memorial services, sticker 2 is affixed to a thank-you letter for attendance as a gift.

In the case of a wedding reception, if the bride and groom try to present items they have prepared themselves as gifts to each guest at the reception hall as wedding favors without relying on the reception hall provider (a hotel or wedding hall company), they may be charged a bring-in fee. However, with the sticker-type gift asset product of the embodiment, they simply stick sticker 2 on the place cards and do not bring in any items, so it is unlikely that a bring-in fee will be charged. In this respect, it is a convenient gift-presenting method for the bride and groom.

When giving a token of gratitude or a ceremonial item as a gift, food or home appliances may be given in addition to a letter, catalog, or letter of appreciation, or a gift asset product such as a catalog gift or other gift items may be given as a secondary prize. Also, at weddings and other events, place cards are prepared for each guest in attendance, and a message of gratitude is generally written on the back of the place card. The configuration of the embodiment is based on the idea of attaching a code symbol that can be exchanged as a gift to letters, catalogs, letters of appreciation, and other items that do not have asset value in themselves, making them valuable as gifts. This creates the convenience of being able to freely choose the item to be exchanged without having to prepare a secondary prize or the like. Also, by attaching a sticker gift to the back of a wedding place card, the place card becomes a catalog-style gift, which can be taken home as is, and the unique code symbol on items with clear names such as place cards can prevent mistakes such as giving them to the wrong person.

The sticker-type gift asset product of the embodiment can also be used for business purposes, such as presenting gifts to customers (or potential customers) for the purpose of sales promotion. For example, a car dealer selling new cars may present the sticker-type gift asset product of the embodiment to potential customers who visit their showroom as a thank you for visiting. For example, when handing over a new car catalog, sticker 2 may be affixed to the catalog and presented as a thank you for visiting. The potential customer similarly reads code symbol 3 on sticker 2 with recipient terminal 7 such as a smartphone, accesses a gift site, and receives the exchangeable item as a promotional item.

Conventionally, gifts to thank visitors for visiting were prepared in advance in the showroom and handed out to visitors along with catalogs, etc., but ordering was time-consuming and required space for inventory, which was cumbersome. By using the sticker-type gift asset product of the embodiment, it is extremely easy to store the sheet-like items and simply attach them to catalogs, etc., when visitors arrive and present them, and no storage space is required. In the past, visitors would accept items they did not really need because they were free, and they would end up discarding them without being used effectively. With the sticker-type gift asset product of the embodiment, visitors can select the items to be exchanged on the gift site, so they can receive promotional items that they need most and do not go to waste. This makes it an excellent promotional tool.

In addition, the sticker-type gift asset product of the embodiment has a deadline printing section 21 on the sticker 2, which prints the exchange deadline, preventing the recipient from missing the deadline. The exchange deadline can be made known to the giver, for example, by printing it on the backing paper 1. When the giver affixes sticker 2 and hands it over to the recipient, they can inform the recipient of the exchange deadline verbally or in a note, but if they forget to inform the recipient, the recipient will likely miss the exchange deadline. The sticker-type gift asset product of the embodiment is preferable in that it prevents this from happening.

The above explanation is based on an example in which the giver purchases a sticker-type gift asset product, which is a selectable gift asset, but the same can be implemented for single-type gift assets. In the above embodiment, on the top page shown in FIG. 3, the sticker-type product button 52 labeled "Product Designated Sticker Gift" is pressed, and the linked sticker-type product page is displayed on the giver's terminal 5. On this page, the giver can select any exchangeable item at will, and the price of the exchangeable item is paid on the payment page to purchase it. The sales information registration program 41, which is read out from the payment program, records the ID of the selected exchangeable item as the product ID in the sales information file 401. When the recipient reads the code symbol 3 of the sticker 2 with the recipient's terminal 7 and logs in, the introduction page for the exchangeable item is displayed on the recipient's terminal 7, where the recipient can enter their name, address, etc. to apply for an exchange.

In the case of sticker-type gift asset products, which are single-type gift assets, the effect of being able to give gifts easily can be obtained without the trouble of the giver having to purchase and prepare them in advance, and then pack and send them together with a thank-you letter, etc. Also, for business use, the effect of not needing the trouble of purchasing gifts in advance and storing them as inventory, and not needing storage space, can be obtained.

As described above, in the sticker-type gift asset product of the embodiment, a plurality of stickers 2 are attached to the above-mentioned one mount 1, and each sticker 2 is printed with a code symbol 3. In this configuration, the configuration in which the code symbol 3 of each sticker 2 contains an asset ID is particularly significant. In a configuration in which stickers 2 with printed code symbols 3 are attached in the same number as the number of recipients, the present invention can be implemented even if each code symbol 3 only contains a common sales ID (even if it does not contain an asset ID). However, in this case, if a recipient who has obtained an object with a certain sticker 2 attached reads the code symbol 3 with the recipient terminal 7 and applies for an exchange of the exchanged item once, and then reads the code symbol 3 again to apply for an exchange, the exchange application can be made. The exchange application acceptance program 12 may be programmed so that the number of exchange applications is limited to the number of recipients, but even in this case, if the same person applies for exchange multiple times, other recipients will not be able to apply for an exchange.
On the other hand, in the sticker-type gift asset product of the embodiment, the code symbol 3 of each sticker 2 contains an asset ID, and when an exchange request is made for a certain asset ID, the exchange date is recorded in the asset information file 404, and no further exchange requests can be made thereafter. Therefore, there is no problem as described above. Instead of recording the exchange date, information indicating that the asset has been exchanged may be recorded.

In a configuration in which gift assets are presented to multiple recipients at the same time, it is preferable that the recipient's name is printed as the text information printing section on each sticker 2. If the recipient's name is printed, it is possible to reliably attach a sticker to the object to be given to each recipient without forgetting it.
To print the recipient's name on the sticker 2, a file recording the recipient's name is stored in the storage unit 40, and the sticker printing program 63 is programmed to create a sticker-unit image file by referring to this file. For example, the asset information file 404 is provided with a "recipient's name" field, and a recipient's name input field is provided on the purchase screen for a sticker-type gift asset product. The sales information registration program 41 is programmed to record the name entered in the recipient's name input field in the "recipient's name" of the asset information file 404. If there are multiple recipients, a field for entering the number of names is provided, and each entered name is recorded in the "recipient's name" of the record. The sticker printing program 63 is programmed as a character information printing unit to obtain the recipient's name from the asset information file 404, combine it with the character "sama" as a constant, and visualize it as a character information printing unit.

In relation to the configuration in which the recipient's name is printed, in a configuration in which gift assets are presented to multiple recipients, each gift asset can be a different asset. In the above explanation, each gift asset is a selectable gift asset with the same unit price, but they may be selectable gift assets with different unit prices. Even in the case of a single type gift asset, gift assets with different prices for the exchange items may be presented to one recipient and another recipient.

In the case of a configuration in which a different gift asset is presented to each recipient, the giver's page on the gift site has a selection field for the gift asset to be presented to the recipient (hereinafter, product selection field) corresponding to the recipient's name input field in which the recipient's name is entered. The product selection field is a field for selecting either a selectable gift asset of a certain price or a single-type gift asset for a certain exchangeable item. Link buttons to the introduction pages of each selectable gift asset and each exchangeable item are provided near the product selection field, and the name of the gift asset selected on the linked page is displayed in the product selection field, and the product ID identifying the gift asset is stored in a variable. The product ID of the selected gift asset is then recorded in the same record in the asset information file 404 together with the recipient's name.

In this way, in a configuration in which different product IDs are recorded for each asset ID recorded in the asset information file 404 and different gift assets are presented, it is important to avoid affixing sticker 2 incorrectly. For example, in a configuration in which selectable gift assets are presented as return gifts to funeral attendees, selectable gift assets of different prices may be presented depending on the amount of condolence money paid by the attendee. In this case, if sticker 2 is affixed incorrectly, a low-priced return gift may arrive to someone who has received a high-priced condolence money, or a high-priced return gift may arrive to someone who has received a low-priced condolence money. In such cases, if the name of the recipient is printed on sticker 2, sticker 2 can be affixed while checking it against the address of the thank-you letter to be sent to that recipient, preventing affixing the sticker incorrectly.

In the above embodiment, it is preferable to allow the giver to check (view) whether the recipient who received the tangible item with the sticker 2 applied for exchange within the deadline. To achieve this, a password is issued corresponding to the sales ID, and the giver is notified of the sales ID and password so that he or she can log in to the gift server 4 as the giver. A page is implemented in the gift server 4 that allows the giver to view the contents of the asset information file 404 created corresponding to the sales ID and stored in the storage unit 40, and a program (script) that displays the name of each recipient and the exchange application date is embedded in the HTML file that displays this page. With this configuration, the giver can contact (by email, phone, etc.) recipients who have not applied for exchange even though the exchange deadline is approaching, and encourage them to exchange. This prevents the gift assets from becoming worthless because the exchange deadline has passed without an exchange application. The configuration for viewing the exchange status is also disclosed in Patent Publication No. 6741320, and can be referenced.

The text information printing section may contain both the exchange deadline date and the name of the recipient, and may also include the name of the giver. In this case, the sticker printing program 63 obtains the giver's name from the sales information file 401, and creates an image by combining the constant characters "Giver:" with the obtained giver's name.

In the above embodiment, each sticker 2 in the sticker-type gift asset product is circular, but the shape of the sticker 2 may be oval or square. Also, there is no need for multiple stickers 2 to be affixed to the backing 1. If there is only one recipient, there may be a sticker-type gift asset product in which only one sticker 2 is affixed to the backing 1. Also, stickers 2 may be affixed in a row vertically and horizontally on the backing 1, or in a single row. In this case, a strip-shaped backing may be used.

In addition, in the above embodiment, the code symbol 3 includes the execution code 32 of a program on the gift server 4, and the execution code 32 includes authentication information, but other configurations are possible. For example, a program that transmits authentication information to the gift server 4 may be installed as an app on the recipient terminal 7, and the code symbol 3 may include execution code that starts this app. When the app starts, the read authentication information is sent to the gift server 4.

Also, the code symbol 3 may not be an execution code for a program, but may simply contain authentication information. For example, the app on the recipient terminal 7 may be equipped with a module that reads the code symbol 3, and may be programmed to display a reading page for the code symbol 3. The recipient may display this page on the recipient terminal 7, and when the camera of the recipient terminal 7 reads the code symbol 3, the app may obtain the sales ID, asset ID, and password as authentication information, which may then be sent to the gift server 4 by a program on the app to log in, and the exchange top page may be displayed on the recipient terminal 7.

The code symbol may be a two-dimensional code symbol or a one-dimensional code symbol such as a barcode. However, if a widely used two-dimensional code symbol is used, the recipient terminal 7 is often equipped with a function for reading such code symbols, which is preferable since there is no need to implement any additional functions in the recipient terminal.

The sticker type gift asset product of the present invention may be sold at a gift site provided by the gift server 4 as described above, or may be sold at a store such as a convenience store. In this case, the sales ID and asset ID included in each code symbol are activated at the time of sale of the sticker type gift asset product. When the sticker type gift asset product is shipped from the gift business, the sales information file 401 is recorded and the asset information file 402 is created and recorded with information, but at this point, it is in a provisional registration state and has not yet been activated. In other words, the "sale date" of the record in the sales information file is not recorded. In addition, the asset information file is provided with a "status" field, and a value meaning invalid is recorded at the shipping stage. When the sticker type gift asset product is sold at a store, the date of the sale is recorded in the "sale date" of the sales information file, and a value meaning valid is recorded in the "status" of each record in the corresponding asset information file. When accessed from the recipient terminal, if the value of the "status" is a value meaning invalid, the exchange application acceptance program outputs an error message and terminates, and only if the value means valid, the exchange application is accepted. In this case, a sales terminal installed at a store such as a convenience store is given the authority to apply for activation to the gift server 1. After the store clerk confirms receipt of the payment, he or she operates the terminal to send the activation request to the gift server 1. A code symbol for the activation process may be provided on the mount 1, etc.

Exchange requests may also be made using a terminal other than the recipient terminal 7, such as a terminal inside a convenience store. For example, the code symbol 3 may be read by a terminal at the convenience store's cash register, which may then log in to the gift server 1 and accept the exchange request for the exchanged item. A suitable example of this configuration is the case of a sticker-type gift asset product that is a single-type gift asset, and the exchanged item selected by the giver is also a product sold at the convenience store. For example, if the exchanged item is a soft drink, the recipient can easily receive the soft drink as a gift on the spot by presenting the object with sticker 2 affixed to the clerk at the convenience store's cash register.

1 Mount 10 Product sheet 2 Sticker 3 Code symbol 32 Execution code 4 Gift server 40 Memory unit 401 Sales information file 404 Asset information file 41 Sales information registration program 42 Exchange application acceptance program 5 Gifter terminal 61 Printer 61
62 Management terminal 63 Sticker printing program 64 Template file 7 Recipient terminal 9 Internet

Claims (7)

A method for allowing a gift recipient to exchange gift assets exchangeable for goods or services by having the gift recipient operate a terminal of the gift recipient to access a gift site provided by a server on a network and exchange the gift assets for goods or services , comprising :
The exchange of gift assets is for a single product or service selected by the giver on the gift site, or for a product or service selected by the recipient from among multiple products or services set out on the gift site;
A process of creating an image file for printing;
A seal printing process is also included.
The printing image file creating step is a step of creating a printing image file including a code symbol that symbolizes access information to the gift site by executing a creating program by a computer ;
The sticker printing process is a process for producing a gift asset product consisting of a mount and a sticker affixed to the mount by printing an image file for printing on an unprinted sticker with a printer, so that an image including the code symbol is printed on the sticker affixed to the mount,
The symbolized access information includes authentication information used in a login program when the gift recipient's terminal logs in to the gift site in order to exchange the gift for one product or service selected by the gift giver on the gift site , or for the gift recipient to select and exchange from among a plurality of products or services set on the gift site;
The sticker on which the image including the code symbol is printed has adhesiveness enabling it to be peeled off from the backing and reattached to another object, and the giver who is provided with the sticker on the backing reattaches the sticker to another object and hands the other object to the recipient, who then has the recipient operate the recipient's terminal to read the code symbol on the reattached sticker and access the gift site on the server to exchange the one product or service for the gift asset, or exchange the gift asset for a product or service selected by the recipient from the multiple products or services, thereby allowing the giver to give the gift. 2. The method for allowing a giver to give a gift according to claim 1, wherein a deadline for the exchange is set, and the deadline for the exchange is printed on the sticker in addition to the code symbol. A method for having a giver give a gift, as described in claim 1, characterized in that the gift asset product is a commercialized gift asset that is given by a single giver to multiple recipients, the stickers are affixed to the backing sheet in the number of recipients, and the code symbol printed on each sticker includes an asset ID that identifies each gift asset in the authentication information. The method for allowing a giver to give a gift according to claim 3, characterized in that the name of the recipient is printed on each sticker. 5. The method for allowing a giver to give a gift according to claim 1, wherein the code symbol is a two-dimensional code symbol. 5. The method for having a giver give a gift according to any one of claims 1 to 4, wherein the other object is a place card at a wedding reception. 5. The method for causing a giver to give a gift according to claim 1, wherein the other object is an object given to a customer or a potential customer for sales promotion.

Images