JPH08235115A - Customer information management device - Google Patents

Abstract

(57) [Summary] [Object] The present invention relates to a customer information management device, wherein a customer responds to a purchase request for a product by e-mail, online, or the like, and dynamically assigns an ID and a password associated with each product. The purpose is to prevent the leak of the ID and the password by generating and registering them and notifying the customer and purchasing the product by using the notified unique ID and password. [Structure] In response to a purchase request for a product having a plurality of management forms via a line, a means for generating a unique ID and password according to the management form of the product, and a generated unique ID and password Means to notify the customer,
And a means for executing processing in a corresponding management form based on the unique ID or password.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a customer information management device for managing customer information in association with products.

[0002]

2. Description of the Related Art Conventionally, when a product is purchased from a center by electronic mail or online, the product is downloaded or delivered when the ID and password are entered and the product is OK. At this time, the customer ID
And the password is decided and registered in the center, or the center decides the ID, and the customer arbitrarily decides and registers the password in the center.

For example, the ID is "company code + employee number"
The password was set as "employee number + company code", and the password was decided uniformly.

[0004]

For this reason, when a customer purchases a product from the center by e-mail or online, the ID and password are uniformly determined and registered regardless of the product to be purchased. Due to this uniformity, there is a problem in that the ID and password are guessed by another person and the product is stolen or purchased by mistake.

The present invention solves these problems.
When a customer responds to a purchase request for a product by e-mail or online, the ID and password associated with each product are dynamically generated and registered, and the customer is notified and the customer is notified of the unique ID. The purpose is to purchase a product using an ID and a password and prevent leakage of the ID and the password.

[0006]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the terminal 1
Is a terminal where a customer requests the center 2 to purchase products by e-mail or online via a line.

The center 2 generates a unique ID and password in response to a purchase request for a product from a customer, and registers and notifies them. Here, the assigning means 5, the registering means 6, The notification means 7 is included.

[0008] The assigning means 5 has a unique I
This is to generate and give D and a password. The registration unit 6 registers and stores the ID and password generated by the addition unit 5.

The notifying means 7 notifies the customer of the unique ID and password generated in association with the product.

[0010]

In the present invention, as shown in FIG. 1, in response to a request for purchase of a product from the terminal 1 via the line by e-mail or online, the unique assigning means 5 of the center 2 associates the product with the unique product. The ID and password are dynamically generated, and the registration means 6 registers and stores them, and the notification means 7 notifies the terminal 1 of the generated unique ID and password, and the customer receives the notified unique ID and password. The center 2 downloads or delivers the product through the line in response to the purchase request for the product through the line using the password and the notification of the unique ID and password.

At this time, in response to the purchase request for the product by e-mail, the ordering number of the product and the product management number of the product are dynamically used as the unique ID and password associated with the product by the assigning means 5 of the center 2. I am trying to generate it.

In addition, in response to an online product purchase request, the assigning means 5 of the center 2 uses a communication ID and an online purchase number as a unique ID and password associated with the product.

Further, when the product is improved and released, the information and ID and password of the improved product are transmitted to the customer by e-mail based on the registered unique ID and password. There is.

Therefore, in response to a purchase request for a product by e-mail or online, the customer dynamically and uniquely generates and registers an ID and a password associated with each product, and notifies the customer of this. Notified unique I
By using the D and the password to purchase the product, it becomes possible to dynamically generate a unique ID and password when purchasing the product and prevent leakage.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

FIG. 1 is a block diagram showing one embodiment of the present invention.
In FIG. 1, a terminal 1 is a terminal that is operated by a customer and requests the center 2 to purchase products by e-mail or online via a line.

The center 2 generates and registers a unique ID and password in response to a customer's purchase request for a product notified from the terminal 1 through the line, or the unique I
You can send D and password to terminal 1 or use this unique ID
It downloads or delivers a product in response to a purchase request for the product using a password and a password. The management device 3, the product entity DB 11, the order number master 1
2, product number master 13, order / purchase management DB 14, customer ID management DB 15, due date DB 16, message DB 1
7, 18, an input device 19, an output device 20, and the like.

The management device 3 performs various kinds of management, and comprises a discrimination means 4, a granting means 5, a registration means 6, a notification means 7, a purchase form identification means 8, a distribution notification means 9 and the like. Is.

The discriminating means 4 discriminates which purchase mode (for example, purchase order ordered by e-mail or online purchase request) from the terminal 1 via the line. It is a thing.

The assigning means 5 assigns a unique ID and password to each product. The registration unit 6 registers the unique ID and password for each product given by the giving unit 5.

The notifying means 7 uses a unique I for each given product.
The D and password are transmitted to the terminal 1. The purchase form identification means 8 identifies the purchase form of the customer who has received the purchase request (for example, the purchase form ordered by e-mail or the purchase form such as a direct purchase request online), and processes according to the identified purchase form. The distribution notifying means 9 is caused to perform.

The distribution notifying means 9 distributes the purchase forms identified by the purchase form identifying means 8 according to the purchase forms and notifies the purchase forms. Product entity DB1
Item 1 is a product that is registered for easy retrieval (see FIG. 6).

The order number master 12 manages the order numbers of the ordered products (see FIG. 7). The product number master 13 manages product numbers of products (see FIG. 8).

The order / purchase management DB 14 manages order reception and purchase of merchandise (see FIG. 9). Customer ID
The management DB 15 manages the ID and password of each product purchased by the customer (see FIG. 11).

The due date DB 16 manages due dates such as the sale of products (see FIG. 12). Message DB1
Reference numerals 7 and 18 manage various messages.

The input device 19 is for inputting various inputs (for example, a keyboard, a mouse, etc.). The output device 20 performs various outputs (for example, a display device, a printing device, etc.).

Next, the operation of the configuration of FIG. 1 will be described in detail with reference to the flowcharts of FIGS. In FIG. 2, the customer accesses the network in S1. For this, the customer operates the terminal 1 of FIG. 1 to connect to the center 2 via the line and access.

In step S2, the purchase form of the customer is checked.
This checks the purchase form of the customer who has accessed and requested in S1 (for example, whether the purchase order is made by e-mail or directly purchased online). When ordering by e-mail, steps S3 to S7 are performed. On the other hand, when directly purchasing online, steps S8 to S14 are performed.

In S3, since it is found that the order is made by electronic mail in S2, the name and address, the mail address, and the product name and quantity are read from the electronic mail. In S4, the order number is read from the order number master 12, and the product management number and unit price of each product are read from the product number master 13.

In step S5, the order number, name, address, mail address (communication ID) for each product and the product management number for each product are registered in the order / purchase management DB 14.
Further, the billed amount (unit price), quantity, and total billed amount are calculated and registered for each product.

In step S6, the product is mailed. In S7, an ID and a password are given to each product. Here, ID ← order number ・ password ← product management number is assigned to each product.

Through the above steps S3 to S7, when an order is placed by e-mail, it becomes possible to give an order number and a product management number for each product as an ID and a password.

At S8, the customer inputs the ID and password because the purchase was directly made online at S2. S9
The purchaser specifies the product name and quantity.

In step S10, the product management number and unit price of each product are read from the product number master 13. In S11, the online purchase number for each product is read from the product number master 13.

In step S12, a mail address (communication ID) for each product and an online purchase number for each product are registered in the order / purchase management DB 14. Further, the billed amount (unit price), quantity, and total billed amount are calculated and registered for each product.

In step S13, the product is downloaded from the product entity DB 11. In S14, an ID and a password are given to each product. Here, ID ← communication ID password ← online purchase number is assigned to each product.

Through the above steps S8 to S14, when directly purchasing online, it becomes possible to give a communication ID and an online purchase number as an ID and a password for each product.

In step S15, an ID (order number or communication ID) and a password (item management number or online purchase number) are stored in the customer ID management DB 15 for each item.

S16 is a new edition product corresponding to the old edition product (package upgrade version, upgrade version,
A revised manual etc.) is registered in the product entity DB 11.
In S17, the product ID, product name, unit price, product management number, and online purchase number of the new edition product are stored in the product number master 1
Register to 3.

In S18, the new edition product ID and its due date information are registered in the due date DB 16 in association with the old edition product ID.
By the above S15 to S18, the customer (I) receives the ID (order number or communication ID) and password (product management number or online purchase number) assigned to each product.
Register in the D management DB 15. Then, the new version product corresponding to the old version product is registered in the product entity DB 11, the product ID, product name, unit price, product management number, and online purchase number of this new version product are registered in the product number master 13, and the old version product I.
Corresponding to D, the new edition product ID and its due date information is due date DB
Register at 16. With these registrations, when the customer orders or purchases directly, the ID and password for each product are registered, and when a new edition product is released, S1 to be described later.
From 9 to S27, the preparation for automatically notifying the customer of the new edition product to the customer who ordered or purchased directly on the release date is completed.

In S19 of FIG. 3, the due date information is checked. As a result of this check, when it is determined that the date has been reached, the process proceeds to S20. S20 is the due date DB16
Customer ID management DB1 with the same product ID as the old version product ID
Read the ID and password in 5.

At step S21, the customer's mail address (or communication ID) in the order / purchase management DB 14 is read with the above ID (order number or communication ID) and password (commodity management number or online purchase number), and the ID is read.
Notification of (order number or communication ID) and password (product management number or online purchase number) is sent to the customer by e-mail.

In S22, it is determined whether or not the next purchase will be made.
In the case of YES, the process returns to S1 of FIG. 2 and is repeated. on the other hand,
If NO, the process proceeds to S23. In S23, the operation manager issues an instruction from the terminal to "email an e-mail for each purchase form" of a certain product.

In step S24, all the IDs of purchasers of the product are referenced from the customer ID management DB 15. S25 is I
Check the purchase form of the customer from D. As a result of the check, if it is identified that the order is made by e-mail, S26
The notification process is performed to the customer who "ordered by e-mail."
On the other hand, as a result of the check, if it is identified that the product was directly purchased online, in S27, a notification process is performed to the customer who directly purchased online.

By the above steps S19 to S27, when the date of sale of the new edition product comes, it becomes possible to automatically notify the customer who purchased the old edition product of the information of the new edition product by e-mail. .

FIG. 4 shows an example of the contents of the ordering electronic mail according to the present invention. This is an example of the contents of the electronic mail for order sent to the center 2 by the customer operating the terminal 1 in S1 of FIG. Example 1 is an example of the content of an electronic mail in which the following items shown in the figure are set.

<Destination> ・ Name: Kenichi Kurata ・ Address: Chiba City, Chiba ・ ・ ・ ・ Email address: ABC00351 ・ <Order details> ・ Product name: A system ・ Quantity: 3 ・ Product name: B manual ・ Quantity : 1 In Example 2, the items shown in the figure are set as in Example 1.

FIG. 5 shows an example of contents to be purchased online according to the present invention. This is an example of the contents when the customer operates the terminal 1 to connect to the center 2 online to purchase directly in S1 of FIG.

Example 1 is an example of contents in which the following items shown in the figure are set.・ Communication ID: DEF00017 ・ Communication password: ×××××××× ・ Product name: A system ・ Quantity: 2 Here, if you purchase the communication ID and communication password from the beginning, obtain an application in advance. Access the product with the communication ID and communication password for personal computer communication. Further, the product name and the quantity are specified by displaying the product online on the screen when the product is purchased and selecting the product to be purchased from the screen.

In Example 2, the following items shown in the figure are also set.・ Communication ID: GHI00803 ・ Communication password: ×××××××× ・ Product name: A system ・ Quantity: 1 ・ Product name: C system ・ Quantity: 2 FIG. 6 shows an example of a product entity DB of the present invention. . The product entity DB 11 is a schematic representation of a DB in which the entity of a product is registered, and is set as shown below.

Header: A00001 Product entity: A system entity Here, the header has a product ID (for example, A00001).
Set. The product entity (for example, a program module in the case of a package) is set in the product entity.

FIG. 7 shows an example of the order number master of the present invention. When an order for a product is received by e-mail, the order number master 12 sets an issue flag in association with an order number that is uniquely issued for each order of the item, and manages the issue / non-issue of the issue. It is a thing. For example, it is set as shown below.

Order number issue flag JC000001 1 (1: represents issued) JC000003 0 (0: represents unissued) Here, the order number is an order by e-mail (delivery)
Issue only, and issue uniquely for each order regardless of the type and number of products. The issue flag is set to 1 (issued) when the order is issued by e-mail, and initially set to 0.
(Not yet issued).

FIG. 8 shows an example of the product number master of the present invention. The product number master 13 sets and manages the following items shown in the figure. -Product ID-Product name-Unit price-Product management number-Issue flag: 1 (issued), 0 (unissued) -Online purchase number-Issue flag: 1 (issued), 0 (unissued) Where, product The management number is issued for each product and paid information. Issued to attach to the product label only at the time of purchase by shipment. An online purchase number is issued for each product and paid information. Issued only when purchasing online (downloading).

FIG. 9 shows an example of the order / purchase management DB of the present invention. The order / purchase management DB 14 sets and manages the following items shown in the figure.・ Product ID ・ Order number ・ Online purchase number ・ Product management number ・ Name ・ Address ・ Email address (or communication ID) ・ Billing amount Here, as shown in the figure, one online purchase unit or order number unit, online For each purchase number or product management number, set it in the necessary items such as name, address, email address, and billing amount. For example, in the case of online direct purchase, an email address (or communication ID), for each online purchase number, for each online purchase unit,
Set it in the billing amount column. When ordering by e-mail, the product management number, name, address, e-mail address, and billing amount are set for each order number. Then, the quantity and the total billing amount are set for each online purchase unit or order number unit.

FIG. 10 is a conceptual explanatory view of the arrangement of the ID and password corresponding to the type of customer of the present invention. This is an easy-to-understand summary of the concept of how to decide the ID and password of the customer type (purchase form) described above.
Here, it is determined as shown below.

Customer type ID password Customer ordered by e-mail and purchased by delivery Order number Product management number Customer directly purchased online Communication ID Online purchase number FIG. 11 shows an example of a customer ID management DB of the present invention. The customer ID management DB 15 sets and manages the following items as illustrated.

-Product ID-ID-Password Here, the head of the ID "JC" represents the order number, and the head of the ID "other than JC" represents the communication ID. A password beginning with "OL" represents an online purchase number, and a password beginning with "other than OL" represents a product management number.

Further, the product IDs are "A00001" and "B".
In "00002", there is the same ID and password, but there is no problem because the products are different. Since one order corresponds to a unique purchaser, different customers do not have the same ID and password. .

FIG. 12 shows an example of the due date DB of the present invention. The date DB 16 sets and manages the following items as illustrated. -Old edition product ID-New edition product ID-Due date information Here, the old edition product ID is a product ID of a product (for example, packaged software) already provided to the purchaser or paid information (for example, manual). The new edition product ID is a product ID such as a version-up version or a level-up version of a product already provided to the purchaser or a revision of paid information. The due date information is the date when the customer who purchased the old version is notified of the ID and password for downloading and providing the new version.

FIG. 13 shows an example of notification to the purchaser who ordered by electronic mail and purchased by delivery according to the present invention. This is an example of the notification in S26 in FIG. 3 described above, and is the following example shown in the figure that is automatically extracted as a message by being taken out from the message DB 17 in FIG.

For those who ordered by e-mail and purchased by delivery There was a mistake in the description of the payment method attached to the delivered item of the xxx system. The details of the modification are as follows.

.. FIG. 14 shows an example of notification to a purchaser who purchased directly online according to the present invention. This is an example of the notification in S27 of FIG. 3 described above, and is the following example shown in the figure, which is automatically extracted as a message from the message DB 18 of FIG.

For people who purchased directly online, for payment of purchased xxx system, zz card can be used in addition to conventional yy card.

If you have a zz card and would like to switch to payment with this card, follow the instructions below ... Next, refer to the flowcharts of FIGS. 15 to 17. According to the order shown, the operation of the configuration of FIG. 1 when initially ordering by e-mail and purchasing by delivery will be described in detail.

In FIG. 15, in S31, the customer uses the terminal 1
To send an ordering e-mail in which <Address> and <Order details> are entered. S32 is transmitted in S31 <
The center 2 receives an ordering e-mail in which the address> and the <order content> are described via the line.

In step S33, the purchase form of the customer is checked. Here, since this corresponds to the purchase form when ordering by e-mail, the process proceeds to S34. On the other hand, in the case of direct online purchase, the process proceeds to S63 of FIG. 18 described later.

In S34 ', the name and address in <address> of the electronic mail, the mail address, and the product name and quantity in <order content> are read. In step S34, the order number master 12 reads the young order number with the issue flag of 0 and sets the issue flag to 1.

In S35, from the product number master 13, the product management numbers corresponding to the respective products in the <order content> of the previous e-mail are read out in quantity corresponding to a small number with the issuing flag being 0, and each issuance is issued. Set 1 to the flag.
Furthermore, the unit price of each product is also read.

In S36, the order number, the name of <address> of the previous electronic mail, the address, and the mail address (communication ID) are set for each product in the order / purchase management DB 14, and for each number. Also set the product control number. Further, the charge amount (unit price), the quantity, and the total charge amount are calculated and set for each product.

In step S37, a delivery instruction is made for each product in the order / purchase management DB 14 by using the name and address of the product.
In S38, each product is packed in a box (packaging).

At S39, the product is delivered. In S40, the customer who receives the delivery in S39 receives the product and the bill. S41
Gives an ID and password for each product.

In S42, the customer ID management DB 15 stores the ID and password for each product. In S43 of FIG. 16, the new edition product corresponding to the old edition product is registered in the product entity DB 11 using the product ID as a header.

In S44, the product ID, product name, unit price, product management number (newly unissued), and online purchase number (newly unissued) of the new edition product are considerable (eg, 10, 0).
Only 00) are registered in the product number master 13.

In step S45, the new edition product ID and its due date information are set in the due date DB 16 in association with the old edition product ID.
In S46, the due date information is checked. When that date is reached, the process proceeds to S47.

In S47, the product ID is the same as the old product ID in the date DB 16, and the ID and password in the customer ID management DB 15 are read. S48 is the previous ID (order number)
Order / purchase management DB1 with password and password (product management number)
The customer's mail address (communication ID) in 4 is read, and the notification of the ID and password is sent to the customer by e-mail.

In S49, the terminal 1 receives the electronic mail transmitted in S48. In S50, the ID and password of the electronic mail received in S49 are saved in a file.

At S51, the customer operates the terminal 1 to access the network. In S52, the center 2 checks the purchase form of the customer. Here, it is determined that the online purchase is to be performed directly, so the process proceeds to S53.

A step S53 requests a notification ID and a communication password. In S54, the customer operates the terminal 1 in response to the request in S53, and transmits the communication ID and the communication password.

In step S55, the communication ID and communication password are confirmed. S56 prompts access to the database. In S57, the customer operates the terminal to instruct selection of the product.

S58 is an ID for accessing the product
And ask for a password. In S59, the terminal is S50
Send the ID and password saved in. S60 of FIG. 17 is a customer ID management DB with ID and password.
15, the product ID is read, and the corresponding new-version product ID is read using the product ID as the old-version product ID.

In step S61, the online purchase number of the new edition product ID is read from the product number master 13 and the issuing flag is set to "1". Furthermore, the unit price of the product is read.

In S62, the order / purchase management DB 14 is set with the product ID, the mail address (communication ID), and the online purchase number for each number. The billing amount (unit price) and the total billing amount are also calculated and set (in this case, the quantity is only 1).

In S63, the product is downloaded based on the instruction from the customer. In S64, the terminal receives the product. In S65, an ID and a password are added. Here, ID-email address (communication ID) -password-online purchase number are given.

In S66, the ID and password are stored in the customer ID management DB15. In S67, the new edition product corresponding to the old edition product is registered in the product entity DB 11. S68 is
The product ID, product name, unit price, and product management number (newly unissued) and online purchase number (newly unissued) of the new edition product are registered in the product number master 13 in a considerable number (for example, 10,000). .

In S69, the new edition product ID and its due date information are set in the due date DB 16 in association with the old edition product ID.
In S70, the due date information is checked. When the deadline is reached, the process proceeds to S71.

In S71, the product ID is the same as the old product ID in the due date DB 16, and the ID and password in the customer ID management DB 15 are read. In S72, the customer's mail address (communication ID) in the order / purchase management DB 14 is read with the previous ID and password, and a notification of the ID and password is sent to the customer by electronic mail.

In S73, the notification of the ID and the password transmitted from the terminal 1 in S72 is received by electronic mail.
In S74, the ID and password received in S73 are saved in a file.

By the above S31 to S74, the operation in the case of ordering by e-mail and purchasing by delivery is explained in detail. Next, according to the order shown in the flowcharts of FIGS. 18 to 20, the operation of the configuration of FIG. 1 when directly purchasing online from the beginning will be described in detail.

In FIG. 18, in S81, the customer uses the terminal 1
To access the network and connect to the center 2. In S82, the center 2 checks the customer's purchase form. Here, it is determined that the product is directly purchased online, so the process proceeds to S83. On the other hand, when it is determined that the order is made by e-mail, S34 of FIG. 15 already described.
Proceed to.

In step S83, the communication ID and the communication password are requested. In S84, the customer operates the terminal 1 to perform communication I.
Send D and communication password.

In S85, the center 2 confirms the ID and password transmitted in S84. S86 prompts access to the database. In S87, the customer selects and instructs the product and quantity displayed on the terminal 1.

S88 is an ID for accessing the product
And ask for a password. In S89, the customer uses the terminal 1
Is operated to transmit the ID as a communication ID and the password as a communication password for new purchase.

In S90, based on the ID and password transmitted in S89, the issue flag is set from the product number master 13 in the online purchase number corresponding to each product in the <order details> of the previous electronic mail. A small number of 0s is read for the quantity, and 1 is set to each issuing flag. Furthermore, the unit price of each product is also read.

In S91, a mail address (communication ID) is set for each product in the order / purchase management DB 14, and an online purchase number is also set for each number. Further, the charge amount (unit price), the quantity, and the total charge amount are calculated and set for each product.

In step S92, the product is downloaded based on the instruction from the customer. In S93, the terminal 1 receives the product downloaded in S92. In S94, an ID and a password are assigned to each product. For example: ・ ID ← email address (communication ID) ・ Password ← online purchase number.

In S95, the ID and password for each product are stored in the customer ID management DB15. In S96 of FIG. 19, the new edition product corresponding to the old edition product is registered in the product entity DB 11 using the product ID as a header.

In S97, the product ID, product name, unit price, product management number (newly unissued) and online purchase number (newly unissued) of the new edition product are considerable (eg, 10, 0).
Only 00) are registered in the product number master 13.

In S98, the new edition product ID and its due date information are set in the due date DB 16 in association with the old edition product ID.
S99 checks the due date information. When that date is reached, the process proceeds to S100.

S100 is the old product ID of the due date DB16
With the same product ID as, the ID and password in the customer ID management DB 15 are read. In S101, the customer's email address (communication ID) in the order / purchase management DB 14 is read with the above ID (email address (communication ID)) and password (online purchase number), and the notification of the ID and password is sent to the customer electronically. Send by email.

S102 is the ID transmitted in S101.
The terminal 1 receives the notification of the password by e-mail.
In S103, the ID and password of the electronic mail received in S102 are saved in a file.

At S104, the customer operates the terminal 1 to access the network. In S105, the center 2 checks the purchase form of the customer. Here, it is determined that the online purchase is to be performed directly, so the process proceeds to S106.

In step S106, the notification ID and the communication password are requested. In S107, the customer operates the terminal 1 in response to the request in S106, and transmits the communication ID and the communication password.

At step S108, the communication ID and the communication password are confirmed. S109 prompts access to the database. In S110, the customer operates the terminal to instruct selection of a product.

S111 is an I for access to the product.
Request D and password. In S112, the terminal is S
The ID and password stored in 103 are transmitted.

In S113 of FIG. 20, the customer ID management DB 15 is referenced with the ID and password to read the product ID,
The corresponding new edition product ID is read using the product ID as the old edition product ID.

In step S114, the issue number master 13 reads the younger issue number of the issue flag 0 in the online purchase number of the new edition item ID, and sets 1 to the issue flag. Furthermore, the unit price of the product is read.

In S115, the order / purchase management DB 14 is stored with the product ID, mail address (communication ID),
Then, an online purchase number is set for each number. Billing amount (unit price) and total billing amount are also calculated and set (in this case,
The quantity is only 1).

At S116, based on the instruction from the customer,
Download the product. In S117, the terminal receives the product. In S118, an ID and a password are added. Here, ID-email address (communication ID) -password-online purchase number are given.

In S119, the ID and password are the customer ID.
Store in the management DB 15. In S120, the new edition product corresponding to the old edition product is registered in the product entity DB 11. S12
1 is the product number master 13 of the product number, product name, unit price, product management number (newly unissued), and online purchase number (newly unissued) of the new edition product. Register with.

At S122, the old edition product ID is associated with
The new edition product ID and its due date information are set in the due date DB 16. In S123, the due date information is checked. When the deadline is reached, the process proceeds to S124.

S124 is the old product ID of the due date DB16.
With the same product ID as, the ID and password in the customer ID management DB 15 are read. In S125, the customer's mail address (communication ID) in the order / purchase management DB 14 is read with the above ID and password, and a notification of the ID and password is sent to the customer by e-mail.

In step S126, the notification of the ID and the password transmitted from the terminal 1 in step S125 is received by electronic mail. In S127, the ID and password received in S126 are saved in a file.

The above-described steps S81 to S127 provide a detailed description of the operation for making a direct online purchase from the beginning. Next, according to the order shown in the flowchart of FIG. 21, the operation of the configuration of FIG. 1 in the case of identifying the purchase form from the ID and the password and sending an e-mail will be described in detail.

In FIG. 21, S131 is the old edition product I.
Designate D and instruct mail notification for each purchase type. In S132, the center 2 receives the notification of S131 together with the old product ID.

In S133, the customer ID management DB 15 is referred to for all the IDs corresponding to the previous old product ID. In S134, the purchase form of the customer is checked. Here, if it is identified that the order is made by e-mail (for example, I
It is determined whether the head of D = “JC” is set) or the case of directly purchasing online (the head of ID ≠ “JC” is set). I
If the head of D is set to "JC" and it is identified that the order is placed by e-mail, the process proceeds to S135. On the other hand, if the head of the ID is set to something other than “JC” and it is identified as a direct purchase online, the process proceeds to S137.

In step S135, since the order is identified by the e-mail in step S134, the e-mail content for the "order by e-mail" purchaser is read. In S136, the order / purchase management DB 14 transmits the ID (order number) and the mail address (communication ID) corresponding to the password (product management number) to the purchaser.

On the other hand, in S137, since the online purchase was identified in S134, the contents of the electronic mail for the "online direct purchase" purchaser are read. S13
8 transmits to the purchaser by ID (mail address (communication ID)).

By the above S131 to S138, I
It becomes possible to identify the purchase form from the D and the password, and to send a message for that (form ordered by e-mail or form purchased directly online) to the customer.

[0120]

As described above, according to the present invention,
When a customer responds to a purchase request for a product by e-mail or online, a unique ID and password associated with each product are dynamically generated and registered for each customer, and the customer is notified and the customer is notified of this. Since the product is purchased using the unique ID and password, it is possible to dynamically generate the unique ID and password when purchasing the product and prevent leakage.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is an overall flowchart (continuation) of the present invention.

FIG. 3 is an overall flowchart (continuation) of the present invention.

FIG. 4 is an example of contents of an ordering electronic mail according to the present invention.

FIG. 5 is an example of contents to be purchased online according to the present invention.

FIG. 6 is an example of a product entity DB of the present invention.

FIG. 7 is an example of an order number master of the present invention.

FIG. 8 is an example of a product number master of the present invention.

FIG. 9 is an example of an order / purchase management DB of the present invention.

FIG. 10 is a conceptual explanatory diagram of arrangement of ID and password corresponding to the type of customer of the present invention.

FIG. 11 is an example of a customer ID management DB of the present invention.

FIG. 12 is an example of a due date DB according to the present invention.

FIG. 13 is an example of notification to a purchaser who ordered by e-mail and purchased by delivery according to the present invention.

FIG. 14 is an example of notification to a purchaser who purchased directly online according to the present invention.

FIG. 15 is a flow chart (continuation) in the case of ordering by electronic mail and purchasing by delivery according to the first embodiment of the present invention.

FIG. 16 is a flowchart (continuation) in the case where the first embodiment of the present invention is to order by electronic mail and purchase by delivery.

FIG. 17 is a flowchart (continuation) in the case of ordering by electronic mail and purchasing by delivery according to the first embodiment of the present invention.

FIG. 18 is a flowchart (continuation) for directly purchasing online from the beginning of the present invention.

FIG. 19 is a flowchart (continuation) for directly purchasing online from the beginning of the present invention.

FIG. 20 is a flowchart (continuation) for directly purchasing online from the beginning of the present invention.

FIG. 21 is a flowchart in the case of identifying the purchase form from the ID and password of the present invention and sending an electronic mail.

[Explanation of symbols]

 1: Terminal 2: Center 3: Management device 4: Discrimination means 5: Granting means 6: Registration means 7: Notification means 8: Purchase form identification means 9: Distribution notification means 11: Product entity DB 12: Order number master 13: Product number master 14: Order / purchase management DB 15: Customer ID management DB 16: Date DB 17, 18: Message DB 19: Input device 20: Output device

Claims (4)

[Claims] 1. A means for generating a unique ID and a password corresponding to a management form of a product in response to a purchase request for a product having a plurality of management forms via a line, and the generated unique ID. And a means for notifying the customer of the password, and a means for executing processing in a corresponding management form based on the unique ID or password. 2. The customer information management device according to claim 1, wherein when a purchase request for a product is made by electronic mail, the order ID and product management number of the product are used as the unique ID and password. 3. The customer information management apparatus according to claim 1, wherein a communication ID and an online purchase number are used as the unique ID and password when an online product purchase request is made. 4. When the product is improved and released,
4. A means for transmitting information of the improved product and a unique ID and password to the customer by e-mail based on the registered unique ID and password. Any of the listed customer information management devices.