JP2003173400A - Joint goods sales method, its executing system, and its processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide joint goods having value exceeding a purchase price, containing goods near to a taste of a purchaser to a purchaser, and to provide technology capable of preferentially selling specific goods in which constitutional goods supplier desires sale. <P>SOLUTION: This joint goods sales method selling joint goods through a network is composed of a step accepting input designating a desirable price of the goods and a selection pattern showing a pattern selecting goods from the purchaser as a desire related to the goods desiring purchase; a step analyzing the taste of the purchaser on reference to purchasing history showing the joint goods purchased in the past by the purchaser; a step retrieving target goods DB showing information on goods which the constitutional goods supplier desires sale, and selecting goods becoming joining target from the target goods DB based on an accepted selection pattern and the taste analyzing results; and a step selecting joint goods in which the total amount of money comes within the desirable price of the purchaser from the selected goods, and deciding the constitutional goods of the joint sale. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a combination product sales system for selling combination products via a network such as the Internet. In particular, by providing the combination product as a lucky bag, both the purchaser and the product provider can benefit. The present invention relates to a technology effectively applied to a combination product sales system to be brought.

[0002]

2. Description of the Related Art Conventionally, in the case of Internet sales that provide a combination of one or more products by the name of a lucky bag, the product provider side decides the constituent products like the lucky bag sales at the store, and the purchaser At the time of making a decision considering the purchase of a lucky bag, the components of the lucky bag have already been finalized.

Incidentally, as for those related to the sale of products using the Internet, JP-A-11-134408, JP-A-10-240829, JP-A-2001-2001
No. 155070 and related to pre-ordering combination products is described in JP-A-2000-306000.

However, in the sale of a combination product such as a lucky bag, a system for receiving a request from the purchaser at the time of a purchase request and putting the product in which the buyer's preference is reflected in the lucky bag for sale has not yet been realized.

[0005]

[Problems to be Solved by the Invention] In a conventional combination product such as a lucky bag, the purchaser considers the purchase of the combination product,
At the time of making a decision, since the constituent products of the combination product have already been decided, there is a downside that the product which the buyer does not want may be included in the combination product. No consideration was given to determining a combination product for each individual.

An object of the present invention is to solve the above problems, provide a purchaser with a combination product that is more than the purchase price, and includes a product that is close to the taste of the purchaser. It is to provide a technology capable of preferentially selling a specific product that is desired to be sold.

[0007]

According to the present invention, in a combination product sales system for selling combination products via a network, a product desired to be sold on the component product provider side is assembled based on the purchaser's wishes and preferences. It is sold together.

In the combination product sales system of the present invention, a desired price of a combination product such as a lucky bag and a pattern for selecting the constituent products as a pattern for selecting products to be combined, a product to be always included are selected. Input to specify the pattern to specify and leave the rest of the selection to the system, and specify one of the patterns to specify the products you want not to include and leave the rest of the selection to the system,
It is accepted from the purchaser as a combination product purchase request that indicates the wish regarding the product to be purchased.

[0009] Next, after referring to the purchase history showing the combination products purchased by the purchaser in the past, the purchaser's taste is analyzed, and then the commodity information such as inventory goods desired to be sold by the component product provider side. Is searched, and a product to be combined is selected from the target product DB based on the received selection pattern and the preference analysis result.

[0010] Then, the total price for setting and selling the selected products as a combination product is calculated, and the combination product in which the total amount of money is within the purchaser's desired price is selected to constitute the combination product. And sell as a combination product such as a lucky bag.

[0011] By setting the total price when the product is sold as a set as the combination product to be lower than the total of the individual selling prices, the purchaser can purchase the product having a price higher than the purchase price at the desired price. In addition, it is possible to purchase after knowing that products that are close to taste are included, and also for combination product sales system providers and product providers,
Profit may be brought by registration fees and product sales.

[0012] As described above, according to the present invention, in the online sales, it is possible to trade at low cost for products etc. for which inventory is desired to be reduced directly from the manufacturer of the products or via the distributor, and the purchaser has a preference. You can purchase combination products such as lucky bags with matching products. It is also possible to expand the distribution of products.

As described above, according to the combination product sales system of the present invention, the products that the constituent product provider wants to sell are combined and sold based on the purchaser's wishes and preferences. Providing the purchaser with a combination product that is value-for-money and contains products that are close to the taste of the purchaser,
It is possible to preferentially sell a specific product that the component product provider side desires to sell.

[0014]

BEST MODE FOR CARRYING OUT THE INVENTION A combination product sales system for selling a combination product via a network will be described below.

FIG. 1 is a diagram showing a network configuration of a combination product sales system of this embodiment. As shown in FIG. 1, the combination product sales system of this embodiment includes a client 1 which is a terminal of a combination product purchaser side, a combination product sales server 2, a component product provider server 3, a payment processing system 4, and a shipping process. The system 5 is configured and physically connected by a network (hereinafter, description will be made assuming that the network connecting these is the Internet). Further, it is assumed that a plurality of component product provider servers 3 can be connected.

The client 1 is a terminal used by a purchaser when purchasing a lucky bag in the combination product sales system, and has a WWW browser 11 as an interface with the combination product sales server 2.

The component product provider server 3 is a server managed by a lucky bag component product provider. The component product provider server management DB 25 includes one or more component product provider servers 3.
Is a DB that stores the information of (1), and the information is registered in the component product provider server management DB 25 by the administrator of each component product provider server 3.

The lucky bag target product DB 24 is a DB that manages data related to products that are desired to be sold to lucky bags, and the data related to the products are registered in the lucky bag target product DB 24 by the administrator of each component product provider server 3. The product data can be deleted or changed by the administrator of the component product provider server 3.

Further, in the present embodiment, the data relating to the product to be sold for the lucky bag is the product name, the product classification,
It shall include regular price, bag price, quantity, color and size. Here, the regular price is the price based on the list price of the product when it is sold at the store or on the Internet, and the lucky bag price is the price when the product is sold as a component of the lucky bag. It is assumed that the product provider wants to reduce the inventory and wants to sell early, and the price of the product is set lower than the normal price. It is assumed that the price for use is set.

The settlement processing system 4 is a system for performing settlement processing of a combination product, and in response to a settlement processing request from the combination product sales server 2, it cooperates with a component product provider to act as an intermediary coordinator to perform settlement processing operations. The combination product sales server 2 is notified of the completion of the payment processing.

The shipping processing system 5 is a system for carrying out shipping processing of combination products, and in response to a shipping processing request from the combination product sales server 2, it cooperates with a component product provider to act as an intermediary coordinator to carry out shipping processing work. The combination product sales server 2 is notified of the completion of the shipping process.

The combination merchandise sales server 2 uses the order DB 2
1, customer DB22, lucky bag DB23, lucky bag target product DB2
4. It has a component product provider server management DB 25,
The order DB 21 is a DB that stores data regarding a request for a product sent from a purchaser. Customer DB22
Is a DB that stores customer data including purchase history data. The lucky bag DB 23 is a DB that stores data on sold lucky bags. The lucky bag target product DB 24 is a DB that stores information about products that make up the lucky bag. The component product provider server management DB 25 is a DB that manages data related to the component product provider server 3.

FIG. 2 is a diagram showing a schematic configuration of the combination product selling server 2 of this embodiment. As shown in FIG. 2, the combination product sales server 2 of the present embodiment includes an order processing unit 27, a preference analysis unit 281, a product selection unit 282, and a product determination unit 2.
And 83.

The order processing unit 27 is a processing unit that receives an input designating a desired price of a product and a selection pattern indicating a pattern for selecting the product from the purchaser as a request regarding the product desired to be purchased. The preference analysis unit 281 is a processing unit that refers to a purchase history indicating a combination product purchased by the purchaser in the past and analyzes the purchaser's preference.

The product selection section 282 is a lucky bag target product DB 24 showing information on products desired to be sold on the component product provider side.
Are searched for, and the product to be combined based on the accepted selection pattern and the preference analysis result is searched for the lucky bag product DB 24.
It is a processing unit that selects from among the above. The product determination unit 283
It is a processing unit that selects, from the selected products, a combination of products whose total price is within the purchaser's desired price and determines a component product of the combination sale.

The combination product sales server 2 is connected to the order processing unit 2
7, the program for functioning as the preference analysis unit 281, the product selection unit 282, and the product determination unit 283 is a CD-R.
After being recorded in a recording medium such as OM and stored in a magnetic disk or the like, it is loaded into a memory and executed. The recording medium for recording the program may be a recording medium other than the CD-ROM. The program may be installed in the information processing apparatus from the recording medium and used, or the recording medium may be accessed through the network to use the program.

In addition to the above databases, the combination product sales server 2 includes a WWW server 26, an order processing unit 27, a lucky bag creation engine 28, and a component product provider server management unit 2.
9, page generation unit 30, shipping processing unit 31, payment processing unit 3
Includes 2.

The order processing section 27 is an order data registration section 27.
1 and a data search unit 272, and based on a lucky bag purchase request received from the client 1 through the WWW server 26, data necessary for making a lucky bag is registered in the customer DB 22 and the order DB 21. In addition, customer DB22
The customer information is searched for, and the lucky bag creation engine 28 is started. Further, the order processing unit 27 sends a notification of completion of the lucky bag shipping process and the payment process to the shipping process unit 31 and the payment process unit 3.
It also has a role of controlling the entire order receiving process, such as activating the processing unit of the subsequent process received from step 2.

The order data registration unit 271 stores the data related to the product request among the purchase requests in the order DB 2
First, data regarding the individual of the purchaser is registered in the customer DB 22. Registration in the customer DB 22 by the order data registration unit 271 is performed when the data search unit 272 searches the customer DB 22 and determines that the lucky bag has not been purchased before.

The lucky bag making engine 28 determines the constituent goods of the lucky bag by combining the goods provided by the constituent goods provider and notifies the order processing unit 27. In addition, data regarding the constituent products that are shipped to the customer as a lucky bag is registered in the lucky bag DB 23.

The lucky bag creating engine 28 includes a preference analysis unit 28.
1, a product selection unit 282, and a product determination unit 283.

The preference analysis unit 281 indicates that the customer is in the customer DB 2
If it is registered in 2, the data of the lucky bag that the customer has purchased in the past is read from the customer DB 22, and based on the data, the configuration of the lucky bag purchased from the lucky bag DB 23 or the lucky bag target product DB 24, the color and size of the product, etc. Obtain data and analyze customer preferences.

The product selection unit 282 searches the lucky bag target product DB 24 based on the result of the preference analysis issued by the preference analysis unit 281 and selects all the products that match the customer's preference.

The product determination unit 283 further selects products from the products selected by the product selection unit 282 so that the total price of the products to be combined falls within the purchaser's desired price.
Determine the products that make up the lucky bag.

The component product provider server management unit 29 has a component product provider server information registration / deletion unit 291 and a lucky bag target product registration / deletion unit 292, and the component product provider server 3
It manages information on companies and businesses related to the component product providers and information on products provided as lucky bag component products.

Component product provider server information registration / deletion unit 2
91 is a component product provider server management DB25,
Registers, updates, or deletes information about the companies and businesses of component product providers.

The lucky bag target product registration / deletion unit 292 receives the information of the product provided as a component product of the lucky bag from the component product provider server 3 and registers or deletes it in the lucky bag target product DB 24.

Upon receipt of the lucky bag completion notification from the order processing unit 27, the shipping processing unit 31 sends the lucky bag to the shipping processing system 5.
Ask. The information on the products that make up the lucky bag is acquired from the lucky bag DB 23. In addition, the shipping processing unit 31 receives the lucky bag D from the shipping processing completion notification from the shipping processing system 5.
The shipping completion data is registered in the relevant lucky bag data in B23, and a shipping processing completion notification is passed to the order receiving processing section 27.

The settlement processing unit 32 obtains information on the corresponding commodities of the lucky bag from the lucky bag DB 23 by the notification of the completion of the shipping process from the order processing unit 27, and requests the settlement processing system 4 to perform the settlement process. In addition, the payment processing unit 32
Upon receiving the settlement processing end notification from the settlement processing system 4, the settlement completion data is registered in the corresponding lucky bag data in the lucky bag DB 23, and the settlement processing completion notice is passed to the order receiving processing unit 27.

When the page generation unit 30 receives an instruction from the order processing unit 27 in the process up to the end of all the online sales processing of the combination product, it displays a WWW page when displaying data to the client 1. Generate display data that can be displayed. For example, a page is generated to display information for confirmation of information regarding shipping processing, confirmation of information regarding settlement processing, and confirmation regarding completion of order processing.

Based on the payment processing request from the payment processing unit 32, the payment processing system 4 acts as an intermediary and coordinator between the providers of the prepared lucky bag commodities to perform the payment processing work.

In the shipping processing system 5, the shipping processing unit 31
On the basis of the shipping processing request from the company, the shipping processing business is performed as an intermediary coordinating role between the providers of the created lucky bag component products.

FIG. 3 shows a schematic flow chart of the process of actually selling lucky bags in the combination product selling system as described above.

FIG. 3 is a flow chart showing the processing procedure of the lucky bag sale processing of this embodiment. As shown in FIG. 3, when the URL of the online sale site of the combination product designated by the customer when making the purchase request for the lucky bag is accepted (step 300), the combination product sale server 2 causes the WWW server 26 to display the display request page. Page generator 3 that receives information
0 is activated (step 301). The page generation unit 30 supplies the information necessary for displaying the requested page to the WWW server 2
6 and the WWW server 26 outputs this to the client 1
(Step 302).

Next, when the WWW server 26 receives the lucky bag purchase request input by the customer in the client 1 (step 303), the combination product selling server 2 activates the order processing unit 27 (step 304). After the order processing unit 27 is activated, the order processing unit 27, the lucky bag creation engine 28, the shipping processing unit 31, and the payment processing unit 32 perform the entire process related to the purchase / sale of the lucky bag, and the order receiving process ends (step). 305).

FIG. 4 is a flow chart showing the processing procedure of the order receiving process in step 305 of this embodiment. When activated, the order processing unit 27 subsequently receives the data input by the customer at the client 1 from the WWW server 26 (step 400).

The customer inputs the information regarding the purchase request of the lucky bag from the input screen as shown in FIG. For this input data, for example, customer ID (only if known), name, address, phone number, gender, date of birth, occupation and desired price are required, and further input the data necessary for determining the commodities of the lucky bag. Prepare options to do.

In this example, it is assumed that one is selected from a pattern in which all the selection of the commodities of the lucky bag is left to the system, a pattern in which the commodities to be always included are designated, and a pattern in which the commodities to be excluded are designated. .

Product classification / data as data showing customer preference
There are various patterns for accepting more detailed requests from the purchaser, such as the desired number of items, colors, sizes, and keywords. The administrator of the combination product sales system may determine how the customer indicates the request for the component product of the lucky bag.

Next, the data search unit 272, based on the customer name and the telephone number if the customer ID is not entered,
The customer DB 22 is searched to obtain customer information. If the purchaser is a new customer who is not registered in the customer DB 22, the order data registration unit 271 automatically gives a customer ID and registers personal information such as an address and a telephone number in the customer DB 22 (step 401).

Then, the order data registration section 271 receives the customer ID obtained in step 400 or step 401,
Order DB for data related to requests for lucky bag components
21 (step 402). After that, the order processing unit 27 activates the lucky bag creation engine 28 (step 40
3) Select the commodities of the lucky bag (step 40)
4). FIG. 5 shows a flow of processing of the lucky bag creation engine 28 performed here.

When the lucky bag creation process is completed, the shipping processing unit 31 is activated for the next product shipping process (step 405).
A shipping process is performed (step 406). Shipping processing unit 31
When activated, sends a shipping processing request to the shipping processing system 5. Although the shipping-related work is performed by the shipping processing system 5, the shipping processing unit is linked with the related processing unit such as the order processing unit 27 in order to store or delete the data in the database of the combination product sales server 2. 31 does.

When the shipping processing section 31 receives the information such as the shipping date and the destination from the shipping processing system 5, the client 1 receives the information.
The customer is asked to confirm these pieces of information, and the client 1 selects any of "OK", "return", and "cancel" for confirmation of information from the screen as shown in FIG. 407).

When "OK", which indicates that the displayed information is good, is selected, the process proceeds to the next step,
When "Return" is selected, the process returns to the step where the input information regarding the order can be corrected, and when "Cancel" is selected, the order receiving process is ended.

When "OK" is selected, the shipping processing unit 31 stores a completion record of the shipping process in the lucky bag DB 23, and when "Return" or "Cancel" is selected, it is stored. The order processing unit 27 is instructed to delete the related data registered in the order processing process up to the order processing unit 2
7 deletes them (step 408).

When "OK" is selected in step 407, the payment processing unit 32 is activated for the product payment processing (step 409) and the payment processing is performed (step 410). When activated, the payment processing unit 32 issues a payment processing request to the payment processing system 4. Payment related business is payment processing system 4
However, the settlement processing unit 32 cooperates with related processing units such as the order processing unit 27 to store and delete data in the database of the combination product sales server 2.

When the settlement processing unit 32 receives the information such as the shipping fee from the settlement processing system 4, the client 1 requests the customer to confirm the information, and the client 1 confirms the information from the screen as shown in FIG. Is selected from "OK", "return", and "cancel" (step 411). The selection of the next process in step 411 is the same as in step 407. The payment processing unit 32
When “OK” is selected, the record of the completion of the payment process is stored in the lucky bag DB 23, and “Return” or “Cancel”
When is selected, the order receiving processing unit 27 is instructed to delete the related data registered in the process up to that point for the order receiving process being processed, and the order receiving processing unit 27 deletes them (step 412). .

When "OK" is selected in step 411, the order processing unit 27 instructs the page generation unit 30 to generate a page for confirming the order data (step 413), and shipping / settling. The client 1 is asked to confirm all the information including the data, and the client 1 selects "OK", "return" or "cancel" from the screen as shown in FIG. A selection is made (step 414). The selection of the next process in step 414 is the same as in step 407.

When "Return" or "Cancel" is selected, the order processing unit 27 deletes the related data registered in the process up to that point for the order case being processed (step 415).

When "OK" is selected in step 414, the order processing unit 27 causes the order processing unit 27 to process the "order processing date" in the order DB 21, the "latest purchase date" and the purchase data (lucky bag ID list) in the customer DB 22. , “Purchase date” in the lucky bag DB 23 and “Quantity” in the lucky bag target product DB 24 are registered or updated, and the order processing is completed.

FIG. 5 is a flow chart showing the processing procedure of the lucky bag creation processing in step 404 of this embodiment. When the lucky bag creation engine 28 is started, it acquires information (lucky bag ID list) about the lucky bags that the purchaser purchased in the past based on the customer ID from the customer DB 22 (step 500), and further obtains order information from the order DB 21. (Step 501)
Then, the preference analysis of the purchaser's product is executed (step 5).
02).

At the time of the taste analysis, the taste analyzing unit 281 is started up, and the taste analyzing unit 281 obtains statistics about the commodities of the lucky bag purchased by the customer from the data concerning the lucky bag purchased by the customer in the past and grasps the taste. To do.

Next, the product selection unit 282 is activated, and all products matching the customer's taste are acquired from the lucky bag target product DB 24 by product ID based on the customer's taste analysis result by the taste analysis unit 281 (step 503). ).

As an example, the purchaser C0001 selects the "leave" menu on the request screen of FIG. 12 and sets the desired price \ 1.
If you specify 0,000 (case A), you request "product you want to put in", and if you specify the desired price \ 10,000 (case B), you request "product you want not to put" and request the desired price. If you specify \ 10,000 (Case C), the lucky bag creation process (Step 500 to Step 5)
03) will be described based on the data shown in FIGS.

Case A: The preference analysis unit 281 is the customer DB 2
From 2, the lucky bag ID list is acquired based on the customer ID C0001 data, and the lucky bag constituent items (items) are acquired from the lucky bag DB 23 by the lucky bag ID.
Then, using these product IDs, the lucky bag target product DB
The classification, product name, color, and size are acquired from 24 (step 500). Also, the preference analysis unit 281 uses the order DB 2
The data related to the request for the component product of the lucky bag is acquired from 1 (step 501).

Next, the taste of the purchaser is analyzed using the data acquired in step 500 (step 502). The administrator of the combined product sales system may freely decide what kind of data statistics should be output in the analysis in step 502. For example, the manager of the combination product sales system determines whether to analyze the most purchased color or select the most recently purchased color.

By the steps up to this point, for example, preference data that the most purchased category is clothes, the product name is skirt / blouse / jacket, the color is black / white / red, and the size is M is obtained.

Furthermore, while referring to the preference data obtained in step 502, the administrator of the combination product sales system may freely decide the rule of how to select the constituent products of the lucky bag. For example, it is necessary to set rules such as not selecting the product with the most purchased color or selecting the product with the most purchased color. To decide. In accordance with this rule, a list of target products that are the product components of the lucky bag is acquired from the lucky bag target product DB 24 (step 503).

Cases B and C: Like the case A, the product is extracted from the lucky bag target product DB 24. However, in the case B, the data regarding the request for the product constituting the lucky bag, which is acquired in step 501, is always included in the lucky bag. It is necessary to set a product selection rule to be used in step 503 so that the product specified by the customer to be included in the acquisition result of step 503 is always included. In the case C, contrary to the case B, the product specified by the customer not to be put in the lucky bag is described in the product selection rule so as not to be included in the acquired data in step 503.

Next, the product determination unit 283 is activated, and the product determination unit 283 executes step 5 based on the customer's desired price data.
The product to be put in the lucky bag is selected and determined from the product ID list acquired in step 03 (step 504). FIG. 6 shows a flow of processing of the product determination unit 283 performed here. When the lucky bag component products are determined, the lucky bag creation engine 28 stores the ID list (item) of the items to be put in the lucky bag and the price of the lucky bag in the lucky bag DB 23 (step 505), and the order processing unit 27 confirms that the lucky bag is completed. Notify (Step 50)
6).

FIG. 6 is a flow chart showing the processing procedure of the lucky bag component product determination processing in step 504 of this embodiment. The product determination unit 283 receives the order DB 21 based on the order ID.
Obtain the desired price information of the lucky bag from (step 60)
0).

Next, the product ID obtained in step 503.
For the list, obtain the “regular price” and “price for lucky bag” of each product from the lucky bag target product DB 24 based on the product ID,
Based on these prices, the lucky bag component products are selected and prices are set (step 601). Step 6
In 01, it is assumed that selection processing using a calculation formula is executed,
For example, the desired price acquired in step 600 is (A), and the list of product IDs acquired in step 503 is (B).
Then: 1. Search for products for which the price for the lucky bag is (A) yen from (B). 2. If there is no (A) yen product, calculate (C) = (A) / 2 and search for the product (D) whose price for the lucky bag is close to (C) yen. 3. From the list of products subject to (D), narrow down to one item with a large difference between the regular price and the price for lucky bags. 4. Calculate (E) = (C) / 2 and the price for the lucky bag is close to (E) yen
Search for (F). 5. In the list of products subject to (F), narrow down to two items that have a large difference between the regular price and the lucky bag price.

Although the products to be put in the lucky bag are determined according to 1. or 3. and 5. above, if there are a plurality of combinations of the selected products and it is not possible to narrow down to one product at this time, the constituent product provider side For example, you can select a product with a high ranking in which you want to sell, such as a product with a large number in stock or a product that the component product provider is particularly focusing on selling, or the product with the smallest number part of the product ID. The administrator for the combination product sales system may freely set the algorithm for determining the product. For the price of the lucky bag, the total amount of the prices for the lucky bags of the constituent products is set.

For example, the customer C0001 selects the "Leave it to" menu on the request screen of FIG. 12 and sets the desired price \ 10,00.
Specify 0, and in step 503, select S0004 and S0 as lucky bag target products.
If 005 and S0006 are acquired, the price for the lucky bag of S0004 will be \ 1
Since it is 0,000, the lucky bag will only include S0004, and the lucky bag price will be \ 10,000.

Next, the product determination unit 283 notifies the lucky bag making engine 28 of a lucky bag component product decision completion notice (step 602).

FIG. 7 is a diagram showing an example of order data stored in the order DB 21 of this embodiment. Order D in Figure 7
The structure of the order data stored in B21 is shown, and the order processing unit 27 and the lucky bag creation engine 28 acquire, store, and delete the order information.

FIG. 8 is a diagram showing an example of customer data stored in the customer DB 22 of this embodiment. In FIG. 8, customer D
It shows the structure of customer data stored in B22, and the order processing unit 27 acquires, stores, and deletes customer information.

FIG. 9 is a diagram showing an example of lucky bag data stored in the lucky bag DB 23 of this embodiment. In Figure 9, lucky bag D
The configuration of the lucky bag data stored in B23 is represented, and the order processing unit 27 and the lucky bag creation engine 28 acquire, store, and delete the lucky bag information.

FIG. 10 is a lucky bag target product DB 2 of this embodiment.
4 is a diagram showing an example of lucky bag target product data stored in FIG. FIG. 10 shows the structure of the lucky bag target product data stored in the lucky bag target product DB 24. The order processing unit 27, the lucky bag creation engine 28, and the constituent product provider server management unit 2 are shown.
9 acquires, stores, and deletes the lucky bag target product information.

Here, the number of stocks of the product is stored in the item of quantity in the lucky bag target product DB 24, or information indicating that the component product provider puts particular emphasis on sales is provided as the lucky bag target product. It is also possible to store them in the DB 24 and use them as information indicating the order in which the constituent product provider wants to sell. In addition, although products classified as clothes are shown as target products of lucky bags in the present embodiment, products of different fields are received from the product providers of a plurality of different fields such as clothes, food, and travel services. May be combined as one lucky bag.

FIG. 11 is a diagram showing an example of component product provider server data stored in the component product provider server management DB 25 of this embodiment. FIG. 11 shows the configuration of the component product provider server data stored in the component product provider server management DB 25, and the component product provider server management unit 29 stores, deletes, and updates the component product provider server information. .

FIG. 12 is a diagram showing an example of a screen image input by the customer when purchasing a lucky bag of this embodiment. FIG. 12 shows a screen for inputting a request for purchasing a lucky bag and customer information.

The customer is required to enter the desired price, and there are three other patterns for determining the commodities that make up the lucky bag. You must select one of the pattern to request and the pattern to request the desired product without putting it in the lucky bag. The data requested to be input differs depending on the method of determining the products that make up the lucky bag. Therefore, the administrator of the combination product sales system can freely decide the input items, and the screen can be made appropriate.

FIG. 13 is a diagram showing an example of a screen image when the customer confirms the information regarding the delivery of the product of this embodiment. FIG. 13 shows a screen for the client 1 to confirm that the customer has no mistakes in the content, such as “O.
When "K" is selected, the process of settlement processing is started.

FIG. 14 is a diagram showing an example of a screen image when the customer confirms information regarding the purchase settlement according to the present embodiment. FIG. 14 shows a screen for the client 1 to confirm whether the customer has any mistakes in the contents.
When "K" is selected, all the information to be confirmed regarding the order receiving process is displayed and a screen (FIG. 15) for completing the order receiving process is displayed.

FIG. 15 is a diagram showing an example of a screen image when a customer confirms information regarding an order according to the present embodiment.
15 is a screen for the client 1 to check whether the customer has any mistakes in the contents, and when "OK" is selected on this screen, the action of the client 1 necessary for purchasing the lucky bag is completed.

As described above, in the combination product sales system of the present embodiment, products which the constituent product provider desires to sell and which are priced inexpensively are combined based on the customer's selection pattern or preference. Since it is sold as a lucky bag, we provide customers with combination products that are worth more than the purchase price and that include products that are close to the customer's tastes, and at the same time the specific product that the component product provider wants to sell. By setting the price setting to be lower, it is possible to promote the sale of the product.

Further, in the combination product sales system of this embodiment, the information of the configuration products is received from the plurality of configuration product provider servers 3 via the network, stored in the database in the combination product sales server 2, and the purchase request from the customer is received. Since the combination of products is determined by, it is possible to combine the products of a plurality of component product providers geographically distant and sell them as one lucky bag, and accept the customer's purchase purpose as a purchase request. It is also possible to combine products.

For example, the invention can be similarly applied to service products for travel and the like. Ticket providers for transportation means such as airplanes, trains and buses, accommodation providers for hotels such as travel destinations, travel bags. Etc., a provider of portable equipment such as toiletries for travel, etc., accepts and stores information on constituent products from a plurality of different constituent product providers,
After accepting a purchase request from a customer who wants to purchase a necessary product for a trip to a specific area, products in different fields can be combined and sold as a lucky bag for travel.

Although the present invention has been described as one of the embodiments thereof, the goods targeted for the lucky bag are not particularly limited by this embodiment, and the data field name of the database and the taste are preferred. Create a lucky bag for a variety of products by simply changing the fields to be analyzed and the method of selecting and deciding the components of the lucky bag.
It is possible to sell.

As described above, according to the combination product sales system of the present embodiment, the products that the constituent product provider wants to sell are combined and sold based on the purchaser's wishes and preferences. Providing to the purchaser a combination product that has the above-mentioned value and includes products that are close to the taste of the purchaser, and preferentially sell the specific product that the component product provider wants to sell. Is possible.

[0092]

EFFECTS OF THE INVENTION According to the present invention, since the commodities provider wishes to sell the commodities in combination based on the purchaser's wishes and preferences, there is a value higher than the purchase price and the purchaser's preference. It is possible to provide a purchaser with a combination product including a product close to the above, and preferentially sell a specific product that the component product provider side desires to sell.

[Brief description of drawings]

FIG. 1 is a diagram showing a network configuration of a combination product sales system of the present embodiment.

FIG. 2 is a diagram showing a schematic configuration of a combination product sales server 2 of the present embodiment.

FIG. 3 is a flowchart showing a processing procedure of lucky bag selling processing according to the present embodiment.

FIG. 4 is a flowchart showing a processing procedure of order receiving processing in step 305 of the present embodiment.

FIG. 5 is a flowchart showing a processing procedure of a lucky bag creation processing in step 404 of the present embodiment.

FIG. 6 is a flowchart showing a processing procedure of lucky bag component product determination processing in step 504 of the present embodiment.

FIG. 7 is a diagram showing an example of order data stored in the order DB 21 of the present embodiment.

FIG. 8 is a diagram showing an example of customer data stored in a customer DB 22 of this embodiment.

FIG. 9 is a diagram showing an example of lucky bag data stored in a lucky bag DB 23 of the present embodiment.

FIG. 10 is a diagram showing an example of lucky bag target product data stored in a lucky bag target product DB 24 of the present embodiment.

FIG. 11 is a constituent product provider server management DB of the present embodiment.
25 is a diagram showing an example of component product provider server data stored in FIG.

FIG. 12 is a diagram showing an example of a screen image input by a customer when purchasing a lucky bag of the present embodiment.

FIG. 13 is a diagram showing an example of a screen image when a customer confirms information regarding delivery of a product according to the present embodiment.

FIG. 14 is a diagram showing an example of a screen image when a customer confirms information regarding purchase settlement according to the present embodiment.

FIG. 15 is a diagram showing an example of a screen image when a customer confirms information regarding an order according to the present embodiment.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Client, 2 ... Merchandise sales server, 3 ... Component commodity provider server, 4 ... Payment processing system, 5 ... Shipment processing system, 11 ... WWW browser, 21 ... Order DB, 22
… Customer DB, 23… Lucky bag DB, 24… Lucky bag target product D
B, 25 ... Component product provider server management DB, 26 ... WW
W server, 271 ... Order data registration unit, 272 ... Data search unit, 28 ... Lucky bag creation engine, 29 ... Component product provider server management unit, 291 ... Component product provider server information registration / deletion unit, 292 ... Lucky bag target product Registration / Deletion Department, 30
... page generation unit, 31 ... shipping processing unit, 32 ... settlement processing unit, 27 ... order processing unit, 281 ... preference analysis unit, 282 ...
Product selection unit, 283 ... Product determination unit.

Claims (5)

[Claims] 1. In a combination product selling method for selling a combination product via a network, an input for designating a desired price of a product and a selection pattern indicating a pattern for selecting a product is input from a purchaser as a request regarding a product to be purchased. The step of accepting, the step of analyzing the purchaser's preference by referring to the purchase history indicating the combination product purchased by the purchaser in the past, and the target product indicating the information of the product desired to be sold by the component product provider side A step of searching the DB and selecting a product to be combined from the target product DB based on the accepted selection pattern and the preference analysis result, and the total price of the selected products is the purchaser. Of a combination product that fits within the desired price of the product, and determining a component product of the combination sales, Method. 2. A pattern for entrusting all selection of constituent products,
2. The combination product selling method according to claim 1, wherein one of a pattern for specifying a product to be included without fail and a pattern for specifying a product not to be included is accepted as the selection pattern. 3. When there are a plurality of combinations of the selected products, a combination of products having a high order of preference on the component product provider side is determined as a component product of the combination sale. The method for selling a combination product according to claim 1 or claim 2. 4. In a combination product sales system for selling combination products via a network, an input specifying a desired price of a product and a selection pattern indicating a pattern for selecting the product is input from the purchaser as a request regarding the product to be purchased. An order processing unit that receives an order, a preference analysis unit that analyzes the preferences of the purchaser by referring to a purchase history indicating a combination product purchased by the purchaser in the past, and information on products that the component product provider wants to sell Is selected from the target product DB, which selects a product to be combined from the target product DB based on the accepted selection pattern and preference analysis result. And a product determination unit that selects a combination of products whose total price is within the purchaser's desired price and determines a component product of the combination sale. The combined product sales system. 5. A program for causing a computer to function as a combination product sales system for selling combination products via a network, wherein an input designating a desired price of a product and a selection pattern indicating a pattern for selecting the product is purchased. An order processing unit that receives a request from a purchaser as to a desired product, a preference analysis unit that analyzes the purchaser's preference by referring to a purchase history indicating a combination product that the purchaser purchased in the past, and a component product provider side In the target product DB indicating the information of the product desired to be sold, a product selection unit that selects a target product for combination from the target product DB based on the accepted selection pattern and preference analysis result, From the selected products, select the combination product whose total price is within the purchaser's desired price and select the combination product. Program for causing a computer to function as a product determiner for constant.