Multi-level marketing computer network server

Background to the Invention:

The recent rapid development of the Internet has opened many opportunities for new forms of commerce. This invention was initially conceived as a way to serve the part of the software development community that has been giving away software in the form of "shareware". Shareware is promoted by word-of-mouth on the basis of the impression of value to the users and is circulated free of initial charge with the expectation that prospective users who try the product will willingly pay for the right to continue to use the product. This invention uses the monetary incentive of multi-level marketing to augment "impression of value" to promote the word-of-mouth marketing, and this invention uses direct payment and individualized installation to augment "willingness" as a means for developers to receive payment. The individualized installation can prevent copying the product to other computers and can be built in such a way that prospective customers can have a trial period prior to making the payment and with a reinstallation upon payment. This provides all of the flexibility of shareware with significantly reduced risk to the product developer.

As a note: multi-level marketing is a method of sales promotion in which a commission is paid not only to the seller responsible for making the sale, but also to several levels of sellers that were responsible for distributing knowledge of the product to the seller making the current sale. For instance: a piece of software is sold for $25 and pays commissions of $5 to the person making the sale (the level 1 seller), $3 to the person who informed him of the product (the level 2 seller), $1.50 to the person who informed him (level 3), and $0.50 to the person who informed him (level 4). If the purchaser encourages two sales to people who each encourage two sales to people who each encourage two sales, then the original purchaser receives more money back in commissions than he originally paid for the product, and the product developer gets paid every time.

The usefulness of this invention as a multi-level marketing server includes automatic shipping of hardcopy documentation and other types of products using an automatic shipping system for distribution.

Although many organizations have used computers to calculate commissions for multi-level marketing, non has set forth an invention that provides access directly to the customer to make purchases via a computer network from his own computer. All related prior art has required the involvement of a registered seller or operator with privileges to make sales entries to the computer.

Prior art has also included direct purchases via electronic computer network [1], both those delivered directly via the network and those delivered by automatic shipping systems. None of these direct sales via the network have a multi-level marketing commission capability.

These purchases via the network have involved the use of credit card accounts and/or electronic transfer of funds directly to and/or from bank accounts [2]. They have also used a form of currency that is considered cash on the network. Use of these various forms of cash and credit are simply identified as Method of Payment (from purchaser) and Method of Pay (to sellers and other payees).

Summary of the Invention:

The invention is a server which can be attached to an electronic computer network, such as the Internet, and which accepts purchase requests and payment via the network directly from a customer's computer and vends a product directly to the customer's computer via the network, with the key feature that it calculates and pays multi-level commissions. (see Diagram 1) Herein, this server is called the Sales Support Server. As part of its on-line service, the Sales Support Server accepts purchase requests, acquires the payment, transfers the product, calculates commissions (using a multi-level marketing commission structure), pays the commissions and fees, and adds registration data to the multi-level sales database. The generation of receipts and reports is not within the scope of the invention but is expected to be a part of every implementation of the invention.

The complementary invention is the client application which runs on a customer's general purpose computer attached to the network and which allows a customer to purchase a product via the network. Herein, this client application is called the Sales App. The Sales App allows the customer to view catalog files to extract product information directly from catalog files and/or to make direct entry of product reference information to prepare for a purchase. The Sales App provides the purchase request and any seller registration data to a Sales Support Server. It receives the product, and performs the installation of the product on the customer's computer. Installation can include the setting of some security measures to frustrate improper use of the product. The security measures are not within the scope of the invention. The preferred embodiment for the Sales App is as a plug-in app to a network browser.

The catalog files are owned by a seller and must reside on a network server that the Sales App can locate and use. The catalog not only provides information to the prospective customer regarding the products, but also provides Sale Data direct to the Sales App. This Sale Data includes information on how to contact the Sales Support Server and information to identify the product and the seller. The catalog files are not within the scope of the invention.

Another complementary invention, called a Product Loader, runs on a product developer's general purpose computer and functions as a tool to interface to the Sales Support Server. The Product Loader allows the product developer to prepare a product for distribution by the Sales Support Server by allowing the product developer to identify the product files, to designate the price, multi-level commission structure, and fees, and their recipients. He also uses the Product Loader to transfer the product files and information to the Sales Support Server. The Product Loader could also provide preliminary linkage of the product files with security measures that can be locked by the Sales App during installation to prevent execution of the product if copied to another computer or if used after a free trial period. Linkage of product files and security measures are not within the scope of the invention.

Use of the Invention:

The users that would be involved with this invention and its adjunct applications are the product developers, the Sales Support Server providers, the sellers, and the purchasers. Typical use of the invention involves (1) uploading a product to the Sales Support Server, (2) uploading an initial catalog description page to a network service, (3) purchase of a product using the Sales App, (4) registration of a seller, and (5) calculation and distribution of commissions and fees.

(1) Uploading a Product to the Sales Support Server:

Uploading a product to the Sales Support Server involves the product developer, the product files, the Product Loader, and a Sales Support Server. If the product developer does not have his own Sales Support Server, he must arrange with a Sales Support Server provider for use of one. A typical arrangement with a Sales Support Server provider might include a per sale foe to be paid to the Sales Support Server provider which is shared with other payees the provider designates. The operator of the Sales Support Server designates the fees and the Payee Registration Data that reflect these arrangements to the Sales Support Server.

The operator performs the following steps: <ul id="ul0001" list-style="bullet" compact="compact"><li>Start "preset new product" function of Sales Support Server,</li><li>For any payees not registered on Sales Support Server: <ul id="ul0002" list-style="bullet" compact="compact"><li>Enter Payee Personal Identification Data</li><li>Enter Payee Method of Pay Information</li></ul></li><li>For each payee to be associated with new product: <ul id="ul0003" list-style="bullet" compact="compact"><li>Select payee from list,</li><li>Enter amount of fee,</li></ul></li><li>When done record Product Reference ID and total of fees.</li></ul>

The Sales Support Server provider gives the product developer the Sales Support Server Contact Information and the new Product Reference ID. With the completed product files, the price, and commission structure information, the information from the Sales Support Server provider, and the Product Loader, the product developer is ready to upload the product to the Sales Support Server.

The product developer then performs the following steps: <ul id="ul0004" list-style="bullet" compact="compact"><li>Establish a network connection,</li><li>If the purchaser does not have a Product Loader, download Product Loader,</li><li>Start the Product Loader,</li><li>Designate the Sales Support Server connection information,</li><li>Designate the Product Reference ID,</li><li>Designate the Product Data: <ul id="ul0005" list-style="bullet" compact="compact"><li>Designate the product name,</li><li>Enter the file names of the product files,</li><li>Designate the product price,</li><li>Designate the number of commission levels to be paid,</li><li>For each level, designate the amount of commission,</li><li>Designate the number of additional payees,</li><li>For each additional payee: <ul id="ul0006" list-style="bullet" compact="compact"><li>Designate the amount to be paid payee,</li><li>Designate the payee's Personal Identification Data,</li><li>Designate the payee's Method of Pay Information,</li></ul></li><li>Designate the developer's Personal Identification Data,</li><li>Designate the developer's Method of Pay Information,</li></ul></li><li>Verify the Product Data and Payee Registration Data,</li><li>Authorize initiation of product upload, and</li><li>Upon receiving the upload complete signal, exit Product Loader.</li></ul>

After uploading a product to the Sales Support Server, the developer should upload a catalog description page to a network service and make a test purchase.

(2) Uploading a Catalog Description Page to a Network Service:

Uploading a catalog description page is done by developers and sellers from their computer to a general purpose network server. If a developer or seller does not have his own network server he will need to arrange with a provider that has this service. The original Product Description is written by the developer. Later the Product Description is either written by the seller or acquired from a similar catalog description page for the same product.

The seller should perform the following actions: <ul id="ul0007" list-style="bullet" compact="compact"><li>Prepare a catalog description page with the Sale Data in the header,</li><li>Uploads the catalog description page to his network service,</li><li>Edits his catalog contents page to include a reference to the new catalog description page,</li><li>Uploads the catalog contents page to his network service,</li></ul>

(3) Purchase of a Product:

Purchasing a product directly through the network involves the purchaser, a Sales App, a catalog description page with the Sale Data, and a Sales Support Server with the product of interest. The purchaser must also have the Method of Payment.

To purchase a product the purchaser performs the following steps: <ul id="ul0008" list-style="bullet" compact="compact"><li>Establish a network connection,</li><li>If the purchaser does not have a Sales App, download Sales App,</li><li>Start Sales App,</li><li>If first time using the Sales App: <ul id="ul0009" list-style="bullet" compact="compact"><li>Enter Personal Identification Data, and</li><li>Enter Method of Payment information, (e.g. Credit Card Number)</li></ul></li><li>Find a catalog description page of interest,</li><li>Request Sales App to "purchase item",</li><li>Validate purchase data which includes: <ul id="ul0010" list-style="bullet" compact="compact"><li>Product Name,</li><li>Price, and</li><li>Method of Payment information,</li></ul></li><li>Authorize purchase transaction to proceed,</li><li>(Transaction completes)</li><li>Exit Sales App or request to register as a seller (see (5) Registration of a Seller).</li></ul>

When the transaction is complete, the product has been downloaded and installed and the payment has been made.

(4) Registration of a Seller:

The registration of a seller involves the prospective seller, the Sales App, and the Sales Support Server. The registration of a seller can be performed in conjunction with a purchase or separate from a purchase. The seller will need to have a Method of Pay which will in most cases be a bank account to which the Sales Support Server can transfer funds.

To register as a seller the seller performs the following steps: <ul id="ul0011" list-style="bullet" compact="compact"><li>Start a network connection,</li><li>Start Sales App,</li><li>If Sales App Local Records are incomplete, enter: <ul id="ul0012" list-style="bullet" compact="compact"><li>Personal Identification Data, and</li><li>Method of Pay Information,</li></ul></li><li>If not a continuation of a purchase, select or enter the Sale Data of interest,</li><li>Validate Registration Data,</li><li>Authorize registration,</li><li>When registration is complete, exit Sales App.</li></ul>

(5) Calculation and Distribution of Commissions and Fees:

The calculation and distribution of commissions and fees are two processes that are performed by the Sales Support Server after the connection with the purchaser is complete. The calculation of commissions and fees is internal to the Sales Support Server in the preferred configuration. The distribution of commissions and fees involves the Sales Support Server and the designated accounts of the payees, sellers, and developer.

When contacted by the Sales Support Server, the payee's account designated in the Method of Pay, performs the following action: <ul id="ul0013" list-style="bullet" compact="compact"><li>Receive the designated amount.</li></ul>

Drawing Descriptions:

Drawing 1 is a block diagram of the primary items transfered through the network during normal operations.

Diagrams 2A - 2E are flow diagrams showing the sequence of items that are transfered during each functional operation of the Sales Support Server.

Detailed Description:

Sales Support Server:

The Sales Support Server is a general purpose computer network server which has the capability to handle commercial transactions and which has the following data structures and functionality.

The data structures used by the Sales Support Server include: <ul id="ul0014" list-style="bullet" compact="compact"><li>Payee Selection List - file record</li><li>Product Data - file record</li><li>Seller (Payee) Registration Data - file record</li><li>Purchase Request - communication record</li><li>Seller Registration - communication record</li></ul>

The functionality provided by the Sales Support Server includes: <ul id="ul0015" list-style="bullet" compact="compact"><li>"preset new product" function,</li><li>"product upload" connection response,</li><li>"sale" connection response,</li><li>"registration" connection response, and</li><li>"calculate commissions" function.</li></ul>

On the Sales Support Server there is one Payee Selection List, and there are as many Product Data records as there are products that the Sales Support Server vends. A Product Reference ID designates a Product Data record. There is one Seller Registration Data record for each seller of each product. A seller can be any person or organization that registers with the Sales Support Server to sell one of the products the server vends. The Seller Registration Data contain a Next Level Seller Reference ID. A Seller Reference ID is the reference to a Seller Registration Data record. These Next Level Seller Reference IDs form a tree for each product which eventually connect back to the developer's Seller Registration Data. There is also one Seller Registration Data record for each person or organization that is to be paid a fee based on a sale. Payee Registration Data is identical to Seller Registration but does not contain information in its Product Reference ID or Next Level Seller Reference ID. These file records have at least the follow information:

Payee Selection List:

<ul id="ul0016" list-style="bullet" compact="compact"><li>Payee 1 Reference ID</li><li>Payee 2 Reference ID</li><li>Payee 3 Reference ID</li><li>etc.</li></ul>

Product Data:

<ul id="ul0017" list-style="bullet" compact="compact"><li>Product Name (for verification)</li><li>Basic Price</li><li>Number of Product Files <ul id="ul0018" list-style="bullet" compact="compact"><li>Filename 1</li><li>Filename 2</li><li>Filename 3</li><li>etc.</li></ul></li><li>Number of Paid Fees <ul id="ul0019" list-style="bullet" compact="compact"><li>Payee 1 Fee ( amount of Price )</li><li>Payee 1 Reference ID</li><li>Payee 2 Fee ( amount of Price )</li><li>Payee 2 Reference ID</li><li>etc.</li></ul></li><li>Number of Paid Commission Levels <ul id="ul0020" list-style="bullet" compact="compact"><li>Level 1 Seller Commission ( amount of Price )</li><li>Level 2 Seller Commission ( amount of Price )</li><li>Level 3 Seller Commission ( amount of Price )</li><li>Level 4 Seller Commission ( amount of Price )</li><li>etc.</li></ul></li><li>Developer's Reference ID</li></ul>

Seller (Payee) Registration Data:

<ul id="ul0021" list-style="bullet" compact="compact"><li>Personal Identification Data</li><li>Method of Pay Information</li><li>Product Reference ID (null for Payee)</li><li>Next Level Seller Reference ID (null for Payee)</li></ul>

The Sale Data is originally produced by the Product Loader from data supplied by the "upload product" connection response of the Sales Support Server or by the Sale App from data supplied by the "registration" connection response of the Sales Support Server. In either case the seller will place his personal version of the Sale Data in a catalog description page, and a customer operated Sales App will access this data from the catalog description page and use the information to contact the Sales Support Server and to make the Purchase Request.

Sale Data:

<ul id="ul0022" list-style="bullet" compact="compact"><li>Product Name (for verification)</li><li>Sales Support Server Contact Information</li><li>Seller Reference ID</li><li>Product Reference ID</li></ul>

The Purchase Request is comprised of two sets of communication records which could be transferred from the Sales App to the Sales Support Server separately, but they must both be provided for the "sale" connection. The Method of Payment information is entered once by a purchaser into the Sales App which saves the information locally. There is one Purchase Request transferred from the Sales App to the Sales Support Server for each sale.

Purchase Request:

<ul id="ul0023" list-style="bullet" compact="compact"><li>Sale Data</li><li>Method of Payment</li></ul>

The Seller Registration is comprised of three sets of communication records which could be transferred from the Sales App to the Sales Support Server separately, but they must all be provided for the "registration" connection. The Personal Identification Data and Method of Pay Information are entered once by a purchaser into the Sales App which saves the information locally. One Seller Registration is transferred from the Sales App to the Sales Support Server for each seller of each product. The same data is used for a Payee Registration which is provided directly by the Sales Support Server operator or is transfered from the Product Loader. Payee Registration is accompanied by fee information.

Seller Registration:

<ul id="ul0024" list-style="bullet" compact="compact"><li>Sale Data</li><li>Personal Identification Data</li><li>Method of Pay Information</li></ul>

The Sales Support Server provides the "preset new product" function for the local operator. This function allows the Sales Support Server provider to assign payee information so that the provider designated fees get paid automatically with each sale. It also allows the provider to set up the Sales Support Server for new products as needed. The Sales Support Server provides the "product upload" connection response for interaction with the Product Loader which is operated by the developer. The combination of the "preset new product" function and the "product upload" connection response provide all the functionality needed to prepare the Sales Support Server to sell a product.

When the Sales Support Server has an operator execute a "preset new product" function, it performs the following actions (see Diagram 2A): <ul id="ul0025" list-style="bullet" compact="compact"><li>Prepare a new Product Data record,</li><li>Prompt for new payee registration data,</li><li>For each new Payee: <ul id="ul0026" list-style="bullet" compact="compact"><li>Prompt for Payee Personal Identification Data</li><li>Prompt for Payee Method of Pay Information</li><li>Create Payee Registration Data record,</li><li>Add Payee Reference ID to Payee Selection List,</li></ul></li><li>When entry of new payee data is complete, display selection list of Personal Identification Data using Payee Selection List,</li><li>For each payee selected by the operator: <ul id="ul0027" list-style="bullet" compact="compact"><li>Prompt for amount of fee,</li><li>Store Payee Reference ID and associated Fee in the new Product Data record,</li><li>Redisplay Personal Identification Data for more selections,</li></ul></li><li>Report the new Product Reference ID and total of fees.</li></ul>

When the Sales Support Server receives a "product upload" connection, it performs the following actions (see Diagram 2B): <ul id="ul0028" list-style="bullet" compact="compact"><li>Request the new Product Reference ID from the Product Loader,</li><li>If the Product Reference ID is invalid: <ul id="ul0029" list-style="bullet" compact="compact"><li>The upload process is immediately aborted.</li></ul></li><li>Receive uploaded Product Data and Payee Registration Data from Product Loader,</li><li>Store uploaded Product Data and Payee Registration Data with the Payee Registration Data entered by the Sales Support Server provider, (Payee Registration Data includes developer's Seller Registration Data.)</li><li>Receive product files from the Product Loader,</li><li>Store uploaded product files,</li><li>Report the Seller Reference ID assigned to the developer,</li><li>Signal Product Loader that upload is complete,</li><li>Wait for connection to close, and</li><li>Designate product as ready for first purchase.</li></ul>

The Sales Support Server provides the "sale" connection response and "registration" connection response for direct interaction with the Sales App. The "sale" connection response is executed when a customer uses a Sales App to purchase a product. The "registration" connection response is executed when a prospective seller uses a Sales App to register to sell a specific product. When a "registration" connection response occurs in direct conjunction to a "sale" connection response, the original Sale Data can be carried over.

In response to a "sale" connection the Sales Support Server performs the following actions (see Diagram 2C): <ul id="ul0030" list-style="bullet" compact="compact"><li>Accept Sale Data from Sales App,</li><li>Validate that product is available and that seller is registered,</li><li>Send Price to Sales App,</li><li>Receive Method of Payment information from Sales App,</li><li>Verify funds available with Method of Payment,</li><li>Using the file names in the Product Data record, download the product files to the Sales App,</li><li>Upon receiving the signal that the installation has completed, acquire the payment using the Method of Payment,</li><li>Signal the shipping and handling system to send documentation,</li><li>Signal the Sales App that payment is received,</li><li>Receive transaction complete signal,</li><li>If a connection change to a "registration" connection is requested, change connection and give Sale Data,</li><li>If a connection is closed, call "calculate commissions" function giving the Product Reference ID, the Seller Reference ID, and the amount paid.</li></ul>

In response to a "registration" connection, the Sales Support Server performs the following actions (see Diagram 2D): <ul id="ul0031" list-style="bullet" compact="compact"><li>If not a continuation of a "sale" connection: <ul id="ul0032" list-style="bullet" compact="compact"><li>Accept original Sale Data associated with registration,</li><li>Validate that product and seller identified in Sale Data are registered,</li><li>Send verification to Sales App,</li></ul></li><li>Set a Temporary Next Level Seller Reference ID from the original Sale Data,</li><li>Accept rest of Seller Registration from Sales App,</li><li>Create new Seller Registration Data record with information from Seller Registration,</li><li>Set the Next Level Seller Reference ID from the Temporary Next Level Seller Reference ID,</li><li>Send new Seller Reference ID to the Sales App.</li><li>Send a registration complete signal to the Sales App.</li><li>If this connection began as a continuation of a "sale" connection, when connection is closed, call "calculate commissions" function giving the Product Reference ID, the original Seller Reference ID, and the amount paid.</li></ul>

The Sales Support Server provides the "calculate commissions" function which is called internally. In the preferred embodiment, this function is called immediately after closing a connection that involved a sale, but with the addition of pending calculations data it could be called less frequently (e.g. once a day). With the addition of a summation of all commission payments and fees for each seller and payee in a given period prior to dispersement, the number of transactions could be reduced slightly or even altered to a monthly paycheck style of pay.

The Sales Support Server calls on its own "calculate commissions" function which performs the following actions (see Diagram 2E): <ul id="ul0033" list-style="bullet" compact="compact"><li>Given the Product Reference ID, the Seller Reference ID, and the amount paid,</li><li>Use the Product Reference ID to find the Fees and Commissions,</li><li>For each of the Paid Fees: <ul id="ul0034" list-style="bullet" compact="compact"><li>Use the Payee Fee to determine amount to be paid,</li><li>Use the Payee Reference ID to find the Payee Registration Data,</li><li>Use the Payee Registration Data record to get the Personal Identification Data and Method of Pay,</li><li>Disperse the determined amount to the payee's account designated by the Method of Pay.</li></ul></li><li>Use the Seller Reference ID to find the Seller Registration Data,</li><li>For each of the Paid Commission Levels: <ul id="ul0035" list-style="bullet" compact="compact"><li>Use the Level Seller Commission to determine amount to be paid,</li><li>Use the Seller Registration Data record to get the Personal Identification Data and Method of Pay,</li><li>Disperse the determined amount to the seller's account designated by the Method of Pay.</li><li>Use the Next Level Seller Reference ID to find the next Seller Registration Data,</li><li>If the developer's Seller Registration Data is reached the remaining commissions are assigned to the developer.</li></ul></li><li>Use the Developer's Reference ID to find the developer's Seller Registration Data,</li><li>Use the Seller Registration Data record to get the Personal Identification Data and Method of Pay,</li><li>Disperse the remaining amount to the developer's account designated by the Method of Pay.</li></ul>

Sales App:

The Sales App is a plug-in to a network browser which has the capability to transfer files and some form of credit or electronic cash and which has the following data structures and functionality.

The data structures used by the Sales App include: <ul id="ul0036" list-style="bullet" compact="compact"><li>Sales App Local Records - file record</li><li>Sale Data - communication record</li><li>Purchase Request - communication record</li><li>Seller Registration - communication record</li></ul>

The functionality provided by the Sales App includes: <ul id="ul0037" list-style="bullet" compact="compact"><li>"purchase item" request function and</li><li>"register seller" request function.</li></ul>

The Sales App maintains a local file, the Sales App Local Records. The Purchase History has a Registration Status which identifies either that the Sale Data contains the original Seller Reference ID or that the Sale Data contains a personal Seller Reference ID. The original Seller Reference ID is used to register as a seller for the product, and the personal Seller Reference ID is used to establish a catalog description page for the product.

Sales App Local Records:

<ul id="ul0038" list-style="bullet" compact="compact"><li>Personal Identification Data</li><li>Method of Payment (for Purchase)</li><li>Method of Pay Information (for Sale)</li><li>Number of Products (Purchase History) <ul id="ul0039" list-style="bullet" compact="compact"><li>Product 1 Sale Data</li><li>Product 1 Registration Status</li><li>Product 2 Sale Data</li><li>Product 2 Registration Status</li><li>etc.</li></ul></li></ul>

The communications records used by the Sales App, Sale Data, Purchase Request, and Seller Registration, are described in the detailed description of the Sales Support server above.

The Sales App provides the "purchase item" request and the "register seller" request for direct interaction with the Sales Support Server. The "purchase item" request is used by a customer to purchase a product. The "register seller" request is used by a prospective seller to register to sell a specific product. The "purchase item" request and the "register seller" request can either be executed sequentially or seperately.

In response to the "purchase item" request, the Sales App performs the following actions (see Diagram 2C): <ul id="ul0040" list-style="bullet" compact="compact"><li>If the Sales App Local Records are incomplete: <ul id="ul0041" list-style="bullet" compact="compact"><li>Prompt for Personal Identification Data, and</li><li>Prompt for Method of Payment information, (e.g. Credit Card Number)</li></ul></li><li>If a catalog description page is available, use catalog description page for Sale Data,</li><li>If a catalog description page not is available, prompt purchaser for Sale Data,</li><li>Establish a "sale" connection with the Sales Support Server,</li><li>Use Sale Data to construct Purchase Request,</li><li>Send Purchase Request to Sales Support Server,</li><li>Abort sale if Sales Support Server does not have a product and seller that match Sale Data,</li><li>Receive Price from Sales Support Server,</li><li>Display purchase data which includes: <ul id="ul0042" list-style="bullet" compact="compact"><li>Product Name,</li><li>Price, and</li><li>Method of Payment information,</li></ul></li><li>Accept authorization to proceed,</li><li>Send Method of Payment information to Sales Support Server,</li><li>Receive and store the product files,</li><li>Install the product,</li><li>Signal the Sales Support Server that the installation is complete,</li><li>Upon receiving the signal that the payment was received, issue a receipt to the purchaser,</li><li>Assemble and store the Sale Data in the Sales App Local Records,</li><li>Signal the Sales Support Server that the transaction is complete,</li><li>Prompt the purchaser to register as a seller, • If user wants to register as a seller: <ul id="ul0043" list-style="bullet" compact="compact"><li>Go to "register seller" request,</li></ul></li><li>If user does not want to register as a seller: <ul id="ul0044" list-style="bullet" compact="compact"><li>Close the connection to the Sales Support Server.</li></ul></li></ul>

In response to the "register seller" request the Sales App performs the following actions (see Diagram 2D): <ul id="ul0045" list-style="bullet" compact="compact"><li>If Sales App Local Records are incomplete, prompt for: <ul id="ul0046" list-style="bullet" compact="compact"><li>Personal Identification Data, and</li><li>Method of Pay Information,</li></ul></li><li>Establish (or change to) a "registration" connection with the Sales Support Server,</li><li>If not a continuation of a "purchase item" request: <ul id="ul0047" list-style="bullet" compact="compact"><li>Display list of Sale Data from Purchase History,</li><li>Accept selection of original Sale Data,</li><li>Verify Registration Data with seller,</li><li>Send the Sale Data to the Sales Support Server for verification,</li></ul></li><li>Send rest of Seller Registration to the Sales Support Server,</li><li>Receive new Seller Reference ID,</li><li>Display Sale Data with new Seller Reference ID for a catalog description page,</li><li>Store the new Sale Data and set Product Registration Status to indicate the seller is registered for this product,</li><li>Upon receiving registration complete signal, notify seller.</li><li>Close connection with server.</li></ul>

Product Loader:

The Product Loader is an application method that runs on a general purpose computer which has a network connection, FTP capabilities, and the product files. The Product Loader has the following data structures and functionality.

The data structures used by the Product Loader includes: <ul id="ul0048" list-style="bullet" compact="compact"><li>Product Data - communication record</li><li>Seller (Payee) Registration Data - communication record</li></ul>

The functionality provided by the Product Loader includes: <ul id="ul0049" list-style="bullet" compact="compact"><li>"execute" function.</li></ul>

The communications records used by the Product Loader, the Product Data and the Seller Registration Data, are described in the detailed description of the Sales Support server above.

The Product Loader runs the "execute" function for the developer. This function allows the Product Loader to upload Product Files and Product Data information to the Sales Support Server.

When the "execute" function is run, the Product Loader performs the following actions (see Diagram 2B): <ul id="ul0050" list-style="bullet" compact="compact"><li>Prompt for the Sales Support Server connection information,</li><li>Establish a "product upload" connection with the Sales Support Server,</li><li>Prompt for the Product Reference ID,</li><li>Verify the Product Reference ID with the Sales Support Server,</li><li>Prompt for the other Product Data and any additional Payee Registration Data,</li><li>Validate entered data,</li><li>Upload the Product Data and additional Payee Registration Data to the Sales Support Server,</li><li>Upload the product files to the Sales Support Server,</li><li>Request and acquire the developer's Seller Reference ID from the Sales Support Server,</li><li>Assemble and display Sale Data for a catalog description page,</li><li>Store the Sale Data locally for later use,</li><li>Display the upload complete signal, and</li><li>Close Sales Support Server connection.</li></ul>

The preceeding descriptions of the invention and the several variations mentioned above are illustrative and do not restrict the invention. For example different embodiments of this invention could include variations such as but not restricted to: <ul id="ul0051" list-style="bullet" compact="compact"><li>The separation and/or reorganization of data in file records and/or communication records,</li><li>The addition of other kinds of data to file records and/or communication records,</li><li>Altering terms used in the data structure (eg. calling the "next" seller the "prior seller in the tree of sellers.)</li><li>The delegation of data files to a separate server,</li><li>The addition of other methods to the Sales Support Server, the Sales App, and/or the Product Loader,</li><li>The separation of the steps of a method into sub methods or separate methods which in combination perform the same function,</li><li>The delegation of performance of methods to a separate server,</li><li>The substitution of payment handling methods which acquire a delayed (credit) payment or make a delayed payment of a fee or commission,</li><li>The delegation of accounting methods for acquiring a payment or paying a fee or commission to a separate system, or</li><li>The vending of the physical parts of a product by delegating the distribution of those parts to a separate automatic shipping system.</li></ul>

All such variations and combinations of such variations are within the spirit of this invention.

References:

<ul id="ul0052" list-style="none"><li>[1] "Netscape Merchant System - Netscape White Papers", http://home.netscape.com/comprod/products/iapps/capps/mersys_white_paper.html, Netscape Communications Corporation, 1996.</li><li>[2] "Netscape LivePayment - Netscape White Papers", http://home.netscape.com/comprod/products/iapps/livepay_white_paper.html, Netscape Communications Corporation, 1996.</li></ul>