JP2002163438A - Server system, transaction method, recording medium, and program product - Google Patents

Abstract

PROBLEM TO BE SOLVED: To manufacture and sell a proper number of articles by letting a buyer participate in the commercialization of a planned article. SOLUTION: A buyer's client machine 102 is informed of the number 115 of articles scheduled to be sold and the term 116 of validity of application as threshold information for enabling a purchase application, a temporary order counter 113 obtains the number of desires to buy by counting accepted purchase applications; when the total reaches the number 115 of the articles scheduled to be sold within the term 116 of validity, the articles are manufactured and sold to the buyers.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a server system, a transaction method, a recording medium, and a program product of a transaction system for online shopping through a cyber mall or virtual shop opened on the Internet.

[0002]

2. Description of the Related Art Conventionally, a product derived from a character by imitating a character (hereinafter referred to as a character) appearing in a game developed and sold by a game software vendor.
There are so-called character goods.

[0003] These character goods are sold in stores or at exhibitions such as games. For example, there are straps of the character "Bibi" appearing in Final Fantasy IX (trademark), which is a game software of Square Co., Ltd., and stuffed animals of "Burimushi".

[0004]

However, there is a difference in consciousness among creators, sellers and buyers of character goods. For this reason, character goods derived from the character that the buyer wants are not necessarily sold.

[0005] In order to amortize the production cost of a mold generated for manufacturing one character goods, one character goods is provided with a profitable number of lines (for example, 1000).
Etc.) need to be sold. For this reason, the prior art has a problem to be solved that the profit does not increase depending on the number of sales.

Accordingly, an object of the present invention is to enable a buyer to participate in the commercialization of a planned product, to manufacture an appropriate number of products,
Server system of a trading system that can be sold,
It is to provide a transaction method, a recording medium, and a program product.

[0007]

In order to achieve the above object, according to the first aspect of the present invention, there is provided a server system for accepting an application for purchase of a product from a plurality of client systems. Storage means stored in advance, and a notifying means for notifying the plurality of client systems of the product and the planned sales number,
A counting means for counting the number of purchases requested by the accepted purchase application, and a first notification of the manufacture / sales of the product when the counting result of the counting means reaches the planned sales number, A first notification unit for performing a request to the client system that has made the application, and a second notification indicating that the sale of the product is to be stopped when the counting result of the counting unit does not reach the planned sales number. And a second notification unit for making a request to the client system which has applied for the purchase.

The storage means further stores an expiration date of the purchase application, and the second notifying means outputs the expiration date before the counting result of the counting means reaches the expected sales number. In this case, the second notification is performed in the event that the notification is made.

[0009] Further, the notifying means notifies the plurality of client systems of the expiration date.

[0010] The invention according to claim 5 is a transaction method for receiving an application for purchase of a product from a plurality of client systems in a server system in which the product to be sold and the planned number of sales are stored in advance, wherein the product and the sales are provided. A notification step of notifying the planned number to the plurality of client systems; a counting step of counting the number of purchases desired by the accepted purchase application; and, when the counting result of the counting step reaches the planned sales number, A first notification step of providing a first notification to the effect that the product has been manufactured / sold to the client system that has applied for the purchase,
And a second notification step of performing a second notification to the effect that the sale of the product has been canceled to the client system that has applied for the purchase, when the count result of the counting step does not reach the planned number of sales. It is characterized by having.

Further, the server system further stores an expiration date of the purchase application, and the second notification step includes the step of expiring the expiration date before the counting result of the counting step reaches the planned sales number. In this case, the second notification is performed in the event that the notification is made.

[0012] The notifying step may further include notifying the expiration date to the plurality of client systems.

[0013] The product is a product related to a character appearing in a game.

[0014]

Embodiments of the present invention will be described below in detail with reference to the drawings. In the drawings, the same portions are denoted by the same reference numerals, and the description of the same portions will not be repeated.

In the transaction system of the present embodiment, a seller of character goods is provided with a WWW (Worl) via the Internet.
(d Wide Web) presents character merchandise planning products in WEB contents provided on the Web. Then, after setting thresholds such as the number of planned products to be sold, the expiration date of the purchase application, and so on, the customer as a buyer is invited to purchase the application. When the total number of purchase requests (hereinafter referred to as tentative orders) for the planned product reaches the planned sales number within the expiration date, the planned product is manufactured and sold.

Hereinafter, a customer who is a buyer is referred to as a customer for convenience. In addition, it is assumed that the seller side is a dot-com company that plans character goods and provides WEB contents and a manufacturer of character goods (hereinafter, referred to as a maker).

A dot-com company does not have a store or sales floor as a building, but conducts business with the world as one trade area 24 hours a day, 365 days a year, set in malls and shops opened on the Internet. This is the URL (uniform resource locato)
rs) is often referred to as a dot-com company (for example, Play Onlin
e.com Factory (tentative name)).

(System Configuration) FIG. 1 shows a system configuration of the transaction system of the present embodiment. In FIG. 1, the transaction system includes a communication network 103, a seller system, and one or more customer client systems as buyer systems.

The seller-side system includes a dot-com company server system (hereinafter simply referred to as a server system) 101 and a maker client system 104 connected thereto via a communication network 103. Server system 101 and maker client system 104
Are computer systems managed and operated by sellers.

The maker client system 104 includes:
A personal computer (hereinafter, referred to as a PC) installed in the manufacturer. The maker client system 104 includes software (hereinafter, referred to as a browser) for browsing a web page of web content,
And software for sending and receiving e-mail (hereinafter referred to as a mailer).

The customer client system is a customer PC or the like, for example, the customer client system 102 of the customer X or the like. The customer client system includes a browser, a mailer, and the like.

The communication network 103 includes the server system 101 and the maker client system 1 described above.
04. Connect a customer client system and the like. As the communication network 103, the Internet or the like is suitable. For transmitting and receiving data, HTTP (hypertext tr
ansfer protocol), SMTP (simple mail transfer)
protocol) or an ordinary protocol such as FTP (file transfer protocol).

The server system 101 performs access to stored data, data processing, and service to each client system in response to an inquiry from each client system. The server system 101
The EB content 105, server engine 106, product database 107, customer database 108, and order database 109 are stored in a storage device (not shown).

The web contents 105 are web contents provided by the seller, and each web
Consists of page data. WEB page is HTML (Hy
It is a text document described in a language called perText Markup Language).

An instruction called a tag is described on a WEB page by HTML. A tag can define a character string to be displayed on the display screen, its format, an image to be displayed, its storage location, creation of a table, a function of moving the current page to another page, and the like. The browser of each client system above, according to the definition of the above tag,
Display character strings and images.

The server engine 106 is the server system 1
01, which performs an HTTP request receiving process for accessing a WEB page specified by a URL transmitted from a browser of each client system, a database process, and other controls.

The product database 107 stores the planned product information 11 of “product ID (identifier) = A” for each planned product.
0, each of the planned product information such as the planned product information 111 of “product ID = B” is stored. Each piece of planned product information includes a product ID of the planned product, a character name, a game software name in which the character appears, a product category, a price, provisional order information, a provisional order counter, threshold information, product image data, and the like.

For example, the planned merchandise information 110 includes a merchandise ID.
= A, character name, game software name, product category "alarm clock", price, provisional order information 112, provisional order counter 113, threshold information 114, and product image data 117.

The tentative order information 112 contains the “customer ID” of the customer who has applied for the purchase of the planned product with the product ID = A.
And a temporary order record consisting of
Manage and maintain for each customer. Temporary order information 112
Updates the tentative order record each time a new customer makes a purchase application for a planned product.

The provisional order counter 113 is a total of the provisional order number in the provisional order information 112. Threshold information 1
14 includes a scheduled sales number 115 and an expiration date 116.
Based on the threshold information 114, when the count of the tentative order counter 113 reaches the planned sales number 115 within the expiration date 116, it is determined that the product with the product ID = A is manufactured and sold. The image data 117 is a WEB described later.
This is the planned product image data to be displayed on the page.

Further, the buyer recruiting merchandise information displayed on the WEB page described later is the planned merchandise information 1 of “merchandise ID = A”.
10, the planned product information 111 of "product ID = B", the planned product information of "product ID = C",...

The customer database 108 stores customer-specific information 11 of “customer ID = a” for each customer.
8. Customer specific information such as customer specific information of "customer ID = b" is stored. Each customer-specific information includes a customer ID of the customer, customer information, and the like.

For example, customer specific information 118 has customer ID = a and customer information 119. The customer information 119 includes the customer's name, address, age, telephone number, e-mail address, bank name, account number, card company,
Holds card number. The customer-specific information 118 is generated and added each time an application to purchase a planned product from a new customer occurs.

The order database 109 stores order item information 12 of “item ID = A” for each item for which manufacture and sale have been determined.
0, order product information of “product ID = X”, “product ID = Y”
.., Etc. is stored.
Each ordered product information includes a product ID, a character name, a product category, order information, a production number, and the like of the ordered product.

For example, the order product information 120 is a product ID.
= A, character name, product category "alarm clock",
It has order information 121 and a production number 122.

The order information 121 manages and holds, for each customer, an order record including “customer ID, the temporary number of orders, customer information, and billing information” of the customer who has applied for the purchase of the product with the product ID = A. The order product information 120 is added each time a new product is manufactured or sold.

In the order information 121 of the product with the product ID = A, the information of “customer ID and the number of the provisional orders” is equal to the provisional order information 112 of the planned product with the product ID = A. The total number of provisional orders in the order information 121 in this case is the production number 122.

The order information 12 of the product having the product ID = A
1, the customer information is stored in the customer database 108.
The customer information of the customer-specific information is stored for each customer ID. For example, the customer information 119 of the order record of the customer ID = a in the order information 121
Is equal to the customer information 119 of the customer specific information 118.

(Application for Purchase of Planned Goods) In the above system configuration, a case where the customer X in this embodiment applies for purchase of planned goods for character goods will be described with reference to FIGS.

The customer X receives a request from the customer client system 102 for the purchaser recruitment product page U of the WEB content 301 (see FIG. 3) inputted via the browser.
The RL is transmitted to the server system 101.

FIG. 2 shows a buyer recruiting merchandise page corresponding to the URL transmitted from the server system 101 and displayed on the browser. In FIG. 2, the purchaser recruitment product page 201 has purchaser recruitment product information and a purchase application button 206. Here, "Product ID =
This shows a case where the planned product information 110 of A ″ is purchaser recruiting product information.

The purchaser recruiting merchandise information displayed on the planned merchandise recruiting page 201 includes a planned merchandise introduction 202, an expiration date 203, a planned number of sales 204, and a desired number of purchases 205.

The planned product introduction 202 displays the product ID = A, character name, game software name, product category “alarm clock”, price, and product image data 117 in the planned product information 110 of FIG.

The expiration date 203 is the expiration date 116 in FIG.
In yy / mm / dd format (year, month, day; last two digits for year, month, day)
The planned sales number 204 is the planned sales number 115 in FIG.
, And the desired purchase total 205 displays the provisional order counter 113 of FIG.

In order to provisionally order the product displayed in the planned product introduction 202, the customer X transmits a purchase application page transmission request to the server system 101 by clicking the purchase application button 206 with a mouse. In this case, the purchase application page 301 shown in FIG. 3 is subsequently displayed on the browser.

The customer X enters the purchase application page 301
Your purchase application form will include your name, address, age,
A telephone number, an e-mail address, a bank name, an account number, a card company, a card number, and a desired purchase number 302 are input. Then, the customer X clicks the send button 303 with a mouse, and sends a tentative order request accompanied by the input information to the server system 101.

At a later date, a notification is sent to the server indicating that the product temporarily ordered by the customer X will be manufactured and sold, or that the total number of desired purchases will not reach the planned sales number within the expiration date and the product cannot be manufactured. The electronic mail is transmitted from the system 101 to the customer X.

(Server System Processing) In the above system configuration, the processing procedure of the server system 101 when the customer X applies for the purchase of the planning goods of the character goods as described above with reference to FIGS. This will be described with reference to the flowchart of FIG.

The processing procedure of (A) and (B) shown in FIG.
This is performed by executing the control program 06.
FIG. 4B shows a processing procedure in which, among the functions of the control program of the server engine 106, a module activated at a constant period (for example, every minute) is executed by the CPU of the server system 101.

Further, the CPU of the server system 101 performs database processing and other back-end processing in cooperation with HTTP requests such as page transmission requests and input data transmission from the customer client system 102, and processing at the time of periodic startup. To process the program, a well-known CGI (common gateway interface) and SSI (server
A technique such as side include) may be used.

First, the process of receiving a temporary order will be described. 4A, the CPU of the server system 101 receives the URL of the purchaser recruitment product page of the WEB content 105 from the customer client system 102 of the customer X (step S400).

After receiving the URL, the server system 101
Accesses the product database 107 and acquires the planned product information 110 as purchaser recruitment product information.
For details, product ID = A, character name, game software name, product category “alarm clock”, price, product image data 117, expiration date 116, scheduled sales number 11
5. The information of the temporary order counter 113 is obtained (step S405).

Next, the CPU of the server system 101 sends the Web contents 105 based on the received URL.
From the recruitment product page 201. And
The acquired product ID = A, character name, game software name, product category “alarm clock”, price, product image data 117, expiration date 116, and scheduled sales number 11
5. Transmit the HTML document of the buyer recruiting product page 201 on which the information of the temporary order counter 113 is placed to the customer client system 102 (step S).
410).

Subsequently, upon receiving the purchase application page transmission request, the CPU of the server system 101 searches the Web application 105 for the purchase application page 301 and transmits the HTML document to the customer client system 102 (step S415).

Next, the CPU of the server system 101 receives the tentative order request, and the name, address, age, telephone number, mail address, bank name, account number, card company, card number, Desired number of purchases 3
02 is stored in a buffer memory (not shown) (step S420).

The CPU of the server system 101 transmits customer-specific information 118 uniquely corresponding to the received tentative order request.
Is generated, and a unique ID, for example, “customer ID = a” is assigned to the customer-specific information 118 and stored. The customer X stored in the buffer memory
The customer information 119 is generated from the information of the name, address, age, telephone number, mail address, bank name, account number, card company and card number, and the customer information 119 is stored in the customer specific information 118. The customer-specific information 118 thus obtained is stored in the customer database 108 (step S425).

Further, the CPU of the server system 101 updates the information of the desired purchase number 302 stored in the buffer memory to the count of the temporary order counter 113 as an update of the planned product information 110 which is the purchaser recruitment product information in the product database 107. to add. Also, temporary order information 1
12, the temporary order record including the “customer ID = a” and the “number of temporary orders” assigned to the customer specific information 118 is additionally updated. In this case, information on the desired purchase number 302 stored in the buffer memory is stored as the temporary order number (step S430).

[0058] Planned product information 1 of product database 107
After updating 10, the CPU of the server system 101
The count of the provisional order counter 113 updated as described above is compared with the planned sales number 115.

When the count of the provisional order counter 113 is less than the planned sales number 115, the CPU of the server system 101 terminates the processing without doing anything (step S4).
35 → end). On the other hand, if the count of the provisional order counter 113 has reached the planned sales number 115, in order to manufacture and sell the planned product of the planned product information 110 which is the buyer recruiting product information, order the manufacture of the planned product to the manufacturer. The following processing is performed (steps S435 to S435).
S455).

The CPU of the server system 101 executes the order product information 1 uniquely corresponding to the plan product in the plan product information 110.
By generating and storing the order information in the order database 109, the order information of the planned product is registered (step S440). Ordered product information 120 is planned product information 110
ID = A, character name, product category “alarm clock”, order information 121, production number 1 based on
22.

The order information 121 manages and holds an order record including “customer ID, the number of temporary orders, customer information, and billing information” of the customer who has applied for the purchase of the product with the product ID = A for each customer.

In the order information 121, the information of “customer ID and the number of the provisional orders” is equal to the provisional order information 112 of the planned product with the product ID = A. Order information 1 in this case
The total of the temporary order number in 21 is the production number 122.

In the order information 121, the customer information holds customer information of customer-specific information in the customer database 108 for each customer ID. For example, the customer information 119 of the order record of the customer ID = a in the order information 121 is equal to the customer information 119 of the customer-specific information 118.

The billing information information in the order information 121 holds the billing for purchasing the product having the product ID = A by the tentative order for each customer ID. For example, the billing information 123 of the order record of the customer ID = b in the order information 121 is “Price × 3 in planned product information 110”.
(Customer ID in order information 121 = provisional order number of b) ".

Next, the CPU of the server system 101 deletes the planned product information 110 of the planned product in which the order information is registered in the order database 109 from the product database 107. As a result, the purchaser recruitment product information for displaying the web page managed by the product database 107 is sequentially updated from the planned product information 110 to the planned product information 111 (step S445).

Subsequently, the CPU of the server system 101
Transmits the order product information 120 to the maker client system 104, and orders the maker to manufacture the planned product with the product ID = A (step S450).

The order product information 120 is transmitted to the maker client system 104 by attaching the data file of the order product information 120 processed in a predetermined format to the e-mail from the server system 101 and transmitting the mail file. May be used. In addition, other well-known methods such as a method of transmitting the information of the ordered product information 120 from the server system 101 by push-type information distribution and automatically receiving the information by a browser of the maker client system 104 which is always started may be applied.

The maker receiving the order product information 120 manufactures the character merchandise planning products with the product ID = A in the number indicated by the production number 122. Then, the maker refers to each order record in the order information 121 and sends the character goods of the number equal to the provisional order number in the order record to the customer described in the customer information in the order record.

After ordering the manufacture of the planned product with the product ID = A to the maker, the CPU of the server system 101 sends a message to each customer who purchases the planned product with the product ID = A to the customer, E-mail to send character goods at a later date "
Is transmitted, and the process ends (step S455).

In step S455, the CPU of the server system 101 checks the order information 1 in the order product information 120.
Reference is made to each order record in the order record 21, and the above-mentioned e-mail is transmitted to the e-mail address described in the customer information in the order record.

The seller accesses the order database 109 of the server system 101. Then, the seller refers to each order record in the order information 121 in the ordered product information 120, obtains customer information and billing information in the order record, and generates an invoice for purchasing the character goods with the product ID = A in each customer. Send to Alternatively, settlement may be performed by a known method such as debit of each customer's bank or card settlement based on the customer information.

The process of judging the expiration date, which is performed in parallel with the above-described process of accepting the provisional order, will be described below. Here, the WE managed by the product database 107
The case where the buyer recruiting merchandise information for displaying page B is the planned merchandise information 110 will be described.

In FIG. 4B, the server system 1
The CPU 01 obtains the date from the clock function (not shown) of the server system 101 at regular intervals.
The date is set to the expiration date 116 in the plan product information 110.
Compare with

If the date does not exceed the expiration date 116, the CPU of the server system 101 ends the process without doing anything (step S460 → end). On the other hand, if the date exceeds the expiration date 116, the planned product of the planned product information 110, which is the product information for buyer recruitment, is not manufactured or sold, so the following process for canceling the application for purchase of the planned product from the customer is performed. (Step S4)
60-S470).

The CPU of the server system 101 sends to each customer who has tentatively ordered the planned product of the product ID = A of the planned product information 110 “The character goods of the product ID = A for which purchase has been applied are requested to be purchased within the expiration date. An e-mail (hereinafter, referred to as unsaleable mail) indicating that the total number has not reached the planned sales number and production has become impossible is transmitted (step S465).

Next, the CPU of the server system 101 deletes the planned product information 110 of the planned product that cannot be manufactured from the product database 107, and ends the processing. As a result, the purchaser recruitment product information for displaying the WEB page managed by the product database 107 is sequentially updated from the planned product information 110 to the planned product information 111 (step S4).
70).

(Other Embodiments) In addition to the above embodiments, the following embodiments can be implemented. 1) In the above-described embodiment, the seller is composed of a dot-com company and a character goods maker that plan character goods and provide WEB contents. However, the manufacturer and the dot-com company may be the same seller. In this case, the present invention can be applied to only one server machine without dividing the machines like a server system and a maker client. 2) In the above-described embodiment, the expiration date is set as the threshold value. However, without setting an expiration date, it is possible to simply solicit an application for purchase of a planned product until the total number of tentative orders of the planned product reaches the planned sales number. good. 3) A function of canceling the customer's purchase application once transmitted may be added to the WEB content that presents the character merchandise's planned merchandise.

[0078]

As described above, according to the present invention, the number of products to be sold and the number of products to be sold are notified to a plurality of client systems, and the number of desired purchases is calculated by the accepted purchase application. When the result reaches the number of products to be sold, the first notification to the effect that the product is manufactured / sold,
When the above-mentioned total result does not reach the above-mentioned scheduled sales number, the second notification to the effect that the sales of the product has been canceled is made to the client system which made the purchase application. Perform on the system.

Therefore, the buyer can participate in commercialization of the planned product, and can manufacture and sell an appropriate number of products.

Further, according to the present invention, the expiration date of the purchase application is further notified to a plurality of client systems.
When the expiration date has passed, acceptance of the application for purchase is stopped.

Therefore, it is possible to manufacture and sell an appropriate number of products in a timely manner.

Further, according to the present invention, the product is a product related to a character appearing in the game.

[0083] For this reason, character goods derived from the character that the buyer wants can be sold.

[Brief description of the drawings]

FIG. 1 is a block diagram of a system configuration of a transaction system according to an embodiment.

FIG. 2 is an explanatory diagram of a WEB page for making a purchase application for a planned product of the present embodiment.

FIG. 3 is an explanatory diagram of a WEB page for making a purchase application for a planned product of the embodiment.

FIG. 4 is a flowchart showing a processing procedure of the server system of the embodiment of the present invention.

[Explanation of symbols]

 101 Server System 102 Customer Client System (Customer X) 103 Communication Network 104 Maker Client System 105 Web Contents 106 Server Engine 107 Product Database 108 Customer Database 109 Order Database 110 Planned Product Information 111 Planned Product Information 112 Temporary Order Information 113 Temporary Order Counter 114 Threshold information 117 Product image data 118 Customer-specific information 119 Customer information 120 Ordered product information 121 Order information 122 Production number 123 Billing information 201 Purchaser recruitment product page 202 Planned product introduction 203 Expiration date 204 Scheduled sales number 205 Cumulative number of desired purchases 206 Purchase application button 301 Purchase application page 302 Desired number of purchases 303 Send button

Claims (16)

[Claims] 1. A server system for accepting an application for purchase of a product from a plurality of client systems, a storage means for storing in advance a product to be sold and a planned number of sales, and a storage unit for storing the product and the planned sales number to the plurality of client systems. An informing means for informing, a totaling means for totalizing the number of purchases requested by the received purchase application, and, when the totaling result of the totaling means has reached the planned sales number, a notification of production / sales of the product. A first notifying unit for performing the notification of 1 to the client system which has applied for the purchase, and, if the totaling result of the totaling unit does not reach the planned number of sales, a notification that the sale of the product is stopped. A server system comprising: a second notification unit configured to perform a second notification to a client system that has applied for a purchase. . 2. The server system according to claim 1, wherein said storage means further stores an expiration date of a purchase application, and said second notification means stores a result of said totaling means by said totaling number of said sales. A server system that performs the second notification when the expiration date has passed before the expiration date is reached. 3. The server system according to claim 2, wherein said notifying unit further notifies said plurality of client systems of said expiration date. 4. The server system according to claim 1, wherein said product is a product related to a character appearing in a game. 5. A transaction method for accepting an application for purchase of a product from a plurality of client systems in a server system in which a product to be sold and a planned number of sales are stored in advance, wherein the product and the planned number of sales are stored in the plurality of client systems. An informing step for informing the client system of the above, a totaling step of totalizing the number of desired purchases based on the received purchase application, and a manufacturing / sales of the product when the totaling result of the totaling step reaches the planned sales number. A first notification step of performing a first notification to the effect that the client system has applied for the purchase, and, if the totaled result of the totaling step does not reach the planned number of sales, the sales of the product A second notification step of performing a second notification of the cancellation to the client system that has applied for the purchase. Transaction wherein the door. 6. The transaction method according to claim 5, wherein the server system further stores an expiration date of the application for purchase, and the second notification step includes a step of determining that the total result of the total step is the number of sales scheduled. The second notification is provided when the expiration date has passed before the expiration date is reached. 7. The transaction method according to claim 6, wherein the notifying step further notifies the plurality of client systems of the expiration date. 8. The transaction method according to claim 5, wherein the product is a product related to a character appearing in a game. 9. A computer-readable recording medium in which a program for accepting an application for purchase of a product from a plurality of client systems and performing a transaction is recorded in a server system in which a product to be sold and a planned number of sales are stored in advance. The program includes: a notification step of notifying the plurality of client systems of the product and the planned sales number; a counting step of counting a desired number of purchases by accepting a purchase request; and a counting step of the counting step. A first notification step of, when the result reaches the planned sales number, performing a first notification of manufacture / sales of the product to the client system that has made the purchase application; If the result does not reach the planned number of sales, a second notification to the effect that the sale of the product has been discontinued, A computer-readable recording medium characterized in that a second notification step of performing the client system was applying for entry. 10. The recording medium according to claim 9, wherein
The server system further stores an expiration date of the application for purchase, and the second notification step includes the step of: A computer-readable recording medium for performing a second notification. 11. The computer-readable recording medium according to claim 10, wherein said notifying step further notifies the plurality of client systems of the expiration date. 12. The computer-readable recording medium according to claim 9, wherein the product is a product related to a character appearing in a game. 13. A program product for accepting an application for purchase of a product from a plurality of client systems and conducting a transaction in a server system in which a product to be sold and a planned number of sales are stored in advance. A notification step of notifying the planned number of sales to the plurality of client systems; a counting step of counting the number of purchases desired by the accepted purchase application; and a counting result of the counting step reaching the planned number of sales. A first notification step of providing a first notification to the effect that the product has been manufactured / sold to the client system that has applied for the purchase; and a case where the totaled result of the totaling step does not reach the planned sales number. And sending a second notification to the effect that the sale of the product has been canceled to the client system which has applied for the purchase. Cormorants program product, characterized in that a second notification step. 14. The program product according to claim 13, wherein said server system further stores an expiration date of an application for purchase, and said second notification step comprises: The second notification is performed when the expiration date has passed before the expiration date is reached. 15. The program product according to claim 14, wherein the notifying step further notifies the expiration date to the plurality of client systems. 16. The program product according to claim 13, wherein the product is a product related to a character appearing in a game.